516 files changed, 18681 insertions, 116112 deletions

diff --git a/website/content/en/status/README b/website/content/en/status/README
deleted file mode 100644
index 70484c96f9..0000000000
--- a/website/content/en/status/README
+++ /dev/null
@@ -1,151 +0,0 @@
-ompiling status reports - best practices
-
-Quarterly status reports git repository:
-https://github.com/freebsd/freebsd-quarterly
-
-E-mail address for report submissions:
-quarterly-submissions@FreeBSD.org
-
-0) Timeline
-  - The months of January, April, July and October are dedicated to
-    putting together the reports submitted during the precedent month.
-    This can include waiting for late submissions.
-  - portmgr@ entries default to the extended headline, because of the
-    overlap between quarterly reports and quarterly ports branches.
-  - All entries can have the deadline extended by emailing
-    quarterly-submissions@ up until the extended deadline.
-  - Quarterly status report publication is done during the same months
-    as soon as the report is ready.
-
-  - First Quarter:
-      - First call for reports: March 1st
-      - 2 weeks left reminder: March 15th
-      - Last reminder: March 24th
-      - Standard deadline: March 31st
-      - Extended deadline: April 8th
-
-  - Second Quarter:
-      - First call for reports: June 1st
-      - 2 weeks left reminder: June 15th
-      - Last reminder: June 24th
-      - Standard deadline: June 30th
-      - Extended deadline: July 8th
-
-  - Third Quarter:
-      - First call for reports: September 1st
-      - 2 weeks left reminder: September 15th
-      - Last reminder: September 24th
-      - Standard deadline: September 30th
-      - Extended deadline: October 8th
-
-  - Fourth Quarter:
-      - First call for reports: December 1st
-      - 2 weeks left reminder: December 15th
-      - Last reminder: December 24th
-      - Standard deadline: December 31st
-      - Extended deadline: January 8th
-
-1) Call for reports
-  - Send calls to the freebsd-quarterly-calls@ mailing list, to all
-    submitters of last quarterly status reports (they may have updates
-    or further improvements), and, depending on the season:
-      - Various conference organizers:
-        - AsiaBSDCon (secretary@asiabsdcon.org) March (First Quarter);
-        - BSDCan (info@bsdcan.org) May (Second Quarter);
-        - EuroBSDcon September - October (Third-Fourth Quarter).
-	  EuroBSDcon as an organization is not interested in writing
-	  reports for FreeBSD (at least it was not in October 2019:
-	  its reason is that the conference is not FreeBSD specific),
-	  so reports about this event should be asked of members of the
-	  FreeBSD community that attended it;
-      - Google Summer of Code students and their mentors: soc-students@
-        and soc-mentors@ (Second and Third Quarter).
-  - The easiest way to send calls for quarterly status reports is to use
-    the sendcalls perl script in the tools directory of the git
-    repository. It can also be used through a cron job, for example:
-
-    0	0	1,15,24	3,6,9,12	*	cd ~/freebsd-quarterly/tools && ./sendcalls -s 'Daniel Ebdrup Jensen'
-
-    If you are indeed using a cron job, please run it on freefall and
-    sign it with your name so that it is possible to infer who has
-    configured the cronjob, in case something goes wrong.
-    The script automatically sends calls to freebsd-quarterly-calls@, last
-    quarter submitters and other recipients depending on the season.
-  - It may also be worth making a call for reports on the forums as was
-    done here:
-    https://forums.freebsd.org/threads/call-for-freebsd-2014q4-october-december-status-reports.49812/
-  - The AsciiDoctor template is at:
-    https://www.freebsd.org/news/status/report-sample.adoc
-  - Reporting howto is at: https://www.freebsd.org/news/status/howto.html.
-    It contains a great deal of useful hints for the submitters on how
-    to write good reports.  It also helps to forward all the completed
-    reports to developers for reference, and point to the latest report
-    in the CFR.
-
-2) Building the report:
-  - Review and merge pull requests as well as those submitted via email,
-    as they come in.
-  - For each newly merged report, add its filename to the local Makefile:
-    put it in the variable corresponding to the section where you want
-    the report to appear. Sort the variables content as you want to sort
-    the reports in the corresponding section.
-  - While the reports are being updated, other doc-committers (wblock,
-    pluknet, and bjk, for example) may review the individual entries and
-    propose fixes.
-  - Write an introduction in the _index.adoc file.
-    It should be usually the last step in the process; a good introduction
-    can be only written once all the reports have been collected.
-  - theraven may be poked for composing a nice introduction for the
-    reports.
-    wblock suggests that we ask different people to write introductions to
-    add variety.  Different people will bring different viewpoints and
-    help keep it fresh.
-  - Once all the reports have come in, make any final adjustsments and copy
-    the contents of the directory to
-    doc/website/content/en/status/report-yyyy-mm-yyyy-mm/
-
-3) Committing it:
-
-  - Files to edit and commit:
-
-    The quarterly report itself, found in:
-      doc/website/content/en/status/report-yyyy-mm-yyyy-mm/
-
-    Update the next due date on the status report page and
-    add a link to the new report below that:
-      doc/website/content/en/status/_index.adoc
-
-    The news entry for the main website page:
-      doc/website/data/en/news/news.toml
-
-    Sample for the news entry (may need to add month):
-	[[news]]
-	date = "2021-01-16"
-	title = "October-December 2020 Status Report"
-	description = "The <a href=\"https://www.FreeBSD.org/status/report-2020-10-2020-12.html\">October to December 2020 Status Report</a> is now available with 42 entries."
-
-  - After the html version of the report has been built and is online,
-    use w3m to dump the website as plain-text, something like the following:
-    w3m -cols 80 -dump https://www.freebsd.org/status/report-2021-01-2021-03/ > /tmp/report-2021-01-2021-03.txt
-
-    w3m has full proper unicode support, and as w3m(1) explains, -dump simply
-    outputs text rendering of the html that can then have a few elements
-    snipped, while -cols ensures that everything is wrapped to 80 columns.
-
-  - Send out
-    To: announce@
-    Subject: FreeBSD Quarterly Status Report - <First> Quarter <year>
-
-    This one must be approved, so find someone (mail postmaster) who can
-    do that before starting.
-
-    Send a separate mail:
-
-    To: hackers
-    CC: current, stable
-    BCC: developers
-
-    Note: Remember to toggle disposition (attachment or inlining), as well as
-    recoding in the MUA.
-
-4) Repeat.
diff --git a/website/content/en/status/_index.adoc b/website/content/en/status/_index.adoc
index ee3bf1f92f..604e0fd9a3 100644
--- a/website/content/en/status/_index.adoc
+++ b/website/content/en/status/_index.adoc
@@ -3,26 +3,52 @@ title: "FreeBSD Status Reports"
 sidenav: about
 ---
 
+include::shared/en/urls.adoc[]
+
 = FreeBSD Status Reports
 
-== Next Quarterly Status Report submissions (October - December) due: December 30th, 2021
+== Next Quarterly Status Report submissions (April -- June) due: June 30th, 2025
 
-Submit your entries as Pull Requests from your fork of link:https://github.com/freebsd/freebsd-quarterly[FreeBSD Status Report GitHub repo] or submit them via e-mail to quarterly-submissions@FreeBSD.org, using the link:https://github.com/freebsd/freebsd-quarterly/blob/master/report-sample.adoc[report-sample.adoc template].
+If you are interested in submitting status reports or you are curious about how the publication process works, please see our link:{freebsd-status-report-process}[status report process description].
 
 '''''
 
 One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree.
 
-The FreeBSD Development Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information.
-
-For more exact guidelines on how to write good status reports, please consult link:howto/[our recommendations].
+The FreeBSD Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information.
 
 Periodically, special status reports are prepared and published. One of those are the developer summit reports. Developer summits are places where developers meet in person to discuss issues related to the project. They are definitely worth attending if one is interested in making significant contributions to the Project and they are open to anybody!
 
 These status reports may be reproduced in whole or in part, as long as the source is clearly identified and appropriate credit given.
 
+== 2025
+
+* link:report-2025-01-2025-03/[January, 2025 - March, 2025]
+
+== 2024
+
+* link:report-2024-10-2024-12/[October, 2024 - December, 2024]
+* link:report-2024-07-2024-09/[July, 2024 - September, 2024]
+* link:report-2024-04-2024-06/[April, 2024 - June, 2024]
+* link:report-2024-01-2024-03/[January, 2024 - March, 2024]
+
+== 2023
+
+* link:report-2023-10-2023-12/[October, 2023 - December, 2023]
+* link:report-2023-07-2023-09/[July, 2023 - September, 2023]
+* link:report-2023-04-2023-06/[April, 2023 - June, 2023]
+* link:report-2023-01-2023-03/[January, 2023 - March, 2023]
+
+== 2022
+
+* link:report-2022-10-2022-12/[October, 2022 - December, 2022]
+* link:report-2022-07-2022-09/[July, 2022 - September, 2022]
+* link:report-2022-04-2022-06/[April, 2022 - June, 2022]
+* link:report-2022-01-2022-03/[January, 2022 - March, 2022]
+
 == 2021
 
+* link:report-2021-10-2021-12/[October, 2021 - December, 2021]
 * link:report-2021-07-2021-09/[July, 2021 - September, 2021]
 * link:report-2021-04-2021-06/[April, 2021 - June, 2021]
 * link:report-2021-01-2021-03/[January, 2021 - March, 2021]
diff --git a/website/content/en/status/categories-desc.adoc b/website/content/en/status/categories-desc.adoc
new file mode 100644
index 0000000000..35edaa8343
--- /dev/null
+++ b/website/content/en/status/categories-desc.adoc
@@ -0,0 +1,19 @@
+:FreeBSD-Team-Reports-desc: Entries from the various official and semi-official teams, as found in the link:../../administration/[Administration Page].
+
+:projects-desc: Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects.
+
+:userland-desc: Changes affecting the base system and programs in it.
+
+:kernel-desc: Updates to kernel subsystems/features, driver support, filesystems, and more.
+
+:architectures-desc: Updating platform-specific features and bringing in support for new hardware platforms.
+
+:cloud-desc: Updating cloud-specific features and bringing in support for new cloud platforms.
+
+:documentation-desc: Noteworthy changes in the documentation tree, manual pages, or new external books/documents.
+
+:ports-desc: Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves.
+
+:third-Party-Projects-desc: Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions.
+
+:miscellaneous-desc: Objects that defy categorization.
diff --git a/website/content/en/status/howto.adoc b/website/content/en/status/howto.adoc
deleted file mode 100644
index 33c6364f14..0000000000
--- a/website/content/en/status/howto.adoc
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "How to Write FreeBSD Status Reports"
-sidenav: about
----
-
-= How to Write FreeBSD Status Reports
-
-FreeBSD status reports are published quarterly and provide the general public with a view of what is going on in the Project, and they are often augmented by special reports from Developer Summits. As they are one of our most visible forms of communication, they are very important. This page will provide some advice on writing status report entries from mailto:theraven@FreeBSD.org[David Chisnall], experienced in technical writing.
-
-_Do not worry if you are not a native English speaker. The team handling status reports, `quarterly@FreeBSD.org`, will check your entries for spelling and grammar, and fix it for you._
-
-== Introduce Your Work
-
-_Do not assume that the person reading the report knows about your project._
-
-The status reports have a wide distribution. They are often one of the top news items on the FreeBSD web site and are one of the first things that people will read if they want to know a bit about what FreeBSD is. Consider this example:
-
-....
-abc(4) support was added, including frobnicator compatibility.
-....
-
-Someone reading this, if they are familiar with UNIX man pages, will know that `abc(4)` is some kind of device. But why should the reader care? What kind of device is it? Compare with this version:
-
-....
-A new driver, abc(4), was added to the tree, bringing support for
-Yoyodyne's range Frobnicator of network interfaces.
-....
-
-Now the reader knows that abc is a network interface driver. Even if they do not use any Yoyodyne products, you have communicated that FreeBSD's support for network devices is improving.
-
-== Show the Importance of Your Work
-
-_Status reports are not just about telling everyone that things were done, they also need to explain why they were done._
-
-Carry on with the previous example. Why is it interesting that we now support Yoyodyne Frobnicator cards? Are they widespread? Are they used in a specific popular device? Are they used in a particular niche where FreeBSD has (or would like to have) a presence? Are they the fastest network cards on the planet? Status reports often say things like this:
-
-....
-We imported Cyberdyne Systems T800 into the tree.
-....
-
-And then they stop. Maybe the reader is an avid Cyberdyne fan and knows what exciting new features the T800 brings. This is unlikely. It is far more likely that they have vaguely heard of whatever you have imported (especially into the ports tree: remember that there are over 20,000 other things there too...). List some of the new features, or bug fixes. Tell them why it is a good thing that we have the new version.
-
-== Tell Us Something New
-
-_Do not recycle the same status report items._
-
-Bear in mind that status reports are not just reports on the status of the project, they are reports on the change of status of the project. If there is an ongoing project, spend a couple of sentences introducing it, but then spend the rest of the report talking about the new work. What progress have been made since the last report? What is left to do? When is it likely to be finished (or, if "finished" does not really apply, when is it likely to be ready for wider use, for testing, for deployment in production, and so on)?
-
-== Sponsorship
-
-_Do not forget about your sponsors._
-
-If you or your project has received sponsorship, a scholarship from somebody or you have been already working as a contractor or an employee for a company, please include it. Sponsors always certainly appreciate if you thank them for their funding, but it is also beneficial for them to show that they are actively supporting the Project this way. Last, but not least, this helps FreeBSD to learn more about its important consumers.
-
-== Open Items
-
-_If help is needed, make this explicit!_
-
-Is there any help needed with something? Are there tasks other people can do? There are two ways in which you can use the open items part of the status report: to solicit help, or to give a quick overview of the amount of work left. If there is already enough people working on the project, or it is in a state where adding more people would not speed it up, then the latter is better. Give some big work items that are in progress, and maybe indicate who is focussing on each one.
-
-List tasks, with enough detail that people know if they are likely to be able to do them, and invite people to get in contact.
-
-link:../[Back to the main page]
diff --git a/website/content/en/status/report-2001-06.html b/website/content/en/status/report-2001-06.html
deleted file mode 100644
index 960b506f7f..0000000000
--- a/website/content/en/status/report-2001-06.html
+++ /dev/null
@@ -1,749 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>One of the benefits of the FreeBSD development model is a focus
-    on centralized design and implementation, in which the operating
-    system is maintained in a central repository, and discussed on
-    centrally maintained lists. This allows for a high level of
-    coordination between authors of various components of the system,
-    and allows policies to be enforced over the entire system, covering
-    issues ranging from architecture to style. However, as the FreeBSD
-    developer community has grown, and the rate of both mailing list
-    traffic and tree modifications has increased, making it difficult
-    even for the most dedicated developer to remain on top of all the
-    work going on in the tree.</p><p>The FreeBSD Monthly Development Status Report attempts to
-    address this problem by providing a vehicle that allows developers
-    to make the broader community aware of their on-going work on
-    FreeBSD, both in and out of the central source repository. This is
-    the first issue, and as such is an experiment. For each project and
-    sub-project, a one paragraph summary is included, indicating
-    progress since the last summary (in this case, simply recent
-    progress, as there have been no prior summaries).</p><p>This status report may be reproduced in whole or in part, as
-    long as the source is clearly identified and appropriate credit
-    given.</p><h1>Future Editions</h1><p>Assuming there is some positive feedback on this idea, and that
-    future submissions get made such that there is content for future
-    issues, the goal is to release a development status report once a
-    month. As such, the next deadline will be July 31, 2001, with a
-    scheduled publication date in the first week of August. This will
-    put the status report on a schedule in line with the calendar, as
-    well as providing a little over a month until the next deadline,
-    which will include a number of pertinent events, including the
-    Annual USENIX Technical Conference in Boston, MA. Submissions
-    should be e-mailed to:</p><p>Many submitters will want to wait until the last week of July so
-    as to provide the most up-to-date status report; however,
-    submissions will be accepted at any time prior to that date.</p><p>
-      <i>-- Robert Watson &lt;
-      <a href="mailto:rwatson@FreeBSD.org" shape="rect">rwatson@FreeBSD.org</a>
-
-      &gt;</i>
-    </p><hr /><ul><li><a href="#Binary-Updater-Project">Binary Updater Project</a></li><li><a href="#CVSROOT-script-rewrite/tidy">CVSROOT script rewrite/tidy</a></li><li><a href="#DEVFS">DEVFS</a></li><li><a href="#digi-driver">digi driver</a></li><li><a href="#Diskcheckd">Diskcheckd</a></li><li><a href="#if_fxp-driver">if_fxp driver</a></li><li><a href="#Java-Project">Java Project</a></li><li><a href="#Kernel-Graphics-Interface-port">Kernel Graphics Interface port</a></li><li><a href="#libh-Project">libh Project</a></li><li><a href="#Mount(2)-API">Mount(2) API</a></li><li><a href="#OLDCARD-pccard-implementation">OLDCARD pccard implementation</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#PPP">PPP</a></li><li><a href="#Problem-Reports">Problem Reports</a></li><li><a href="#pseudofs">pseudofs</a></li><li><a href="#RELNOTESng">RELNOTESng</a></li><li><a href="#SMPng-mbuf-allocator">SMPng mbuf allocator</a></li><li><a href="#SMPng-Project">SMPng Project</a></li><li><a href="#Sparc64-Port">Sparc64 Port</a></li><li><a href="#TrustedBSD">TrustedBSD</a></li><li><a href="#TrustedBSD-Capabilities">TrustedBSD Capabilities</a></li><li><a href="#TrustedBSD-MAC-and-Object-Labeling">TrustedBSD MAC and Object Labeling</a></li><li><a href="#TrustedBSD:-ACLs">TrustedBSD: ACLs</a></li></ul><hr /><h2><a name="Binary-Updater-Project" href="#Binary-Updater-Project" id="Binary-Updater-Project">Binary Updater Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~murray/updater.html" title="http://people.FreeBSD.org/~murray/updater.html"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~murray/updater.html" title="">http://people.FreeBSD.org/~murray/updater.html</a></td></tr></table><p>
-	Contact:
-          Eric
-
-          Melville
-         &lt;<a href="mailto:eric@FreeBSD.org">eric@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Binary Updater Project aims to provide a secure
-      mechanism for the distribution of binary updates for FreeBSD.
-      This project is complementary to the Open Packages and libh
-      efforts and there should be very little overlap with those
-      projects. The system uses a client / server mechanism that allows
-      clients to install any known "profile" or release of FreeBSD over
-      the network. Where a specific profile might contain a specific
-      set of FreeBSD software to install, additional packages, and
-      configuration actions that make it more ideal for a specific
-      environment (ie FreeBSD 4.3 Secure Web Server Profile)</p>
-
-      <p>The system can currently be used to install a FreeBSD system
-      or perform the most simple of upgrades but many features are
-      absent. In particular, the client is in its infancy and much work
-      remains to be done. We need additional developers so please get
-      in touch with us at
-      <a href="mailto:updater@osd.bsdi.com" shape="rect">updater@osd.bsdi.com</a>
-
-      if you are interested in spending some cycles on this.</p>
-    <hr /><h2><a name="CVSROOT-script-rewrite/tidy" href="#CVSROOT-script-rewrite/tidy" id="CVSROOT-script-rewrite/tidy">CVSROOT script rewrite/tidy</a></h2><p>
-	Contact:
-          Josef
-
-          Karthauser
-         &lt;<a href="mailto:joe@FreeBSD.org">joe@FreeBSD.org</a>&gt;
-	</p>
-      <p>I'm in the process of rewriting the CVSROOT/scripts to make
-      them more clean and configurable. A lot of other projects also
-      use these and so it makes sense to make them as easy to use in
-      other environments as possible.</p>
-
-      <p>Status: work in progress. There is now a configuration file,
-      but not all the scripts use it yet.</p>
-    <hr /><h2><a name="DEVFS" href="#DEVFS" id="DEVFS">DEVFS</a></h2><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is progressing on implementing true cloning devices in
-      DEVFS. Brian Somers and Poul-Henning Kamp are working to make
-      if_tun the first truly cloning driver in the system. Next will be
-      the pty driver and the bpf driver.</p>
-
-      <p>From July 1st DEVFS will be standard in -current.</p>
-    <hr /><h2><a name="digi-driver" href="#digi-driver" id="digi-driver">digi driver</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@FreeBSD.org">brian@FreeBSD.org</a>&gt;
-	</p>
-      <p>Added the digi driver. Initial work was done by John Prince
-      &lt;johnp@knight-trosoft.com&gt;, but all the modular stuff was
-      done by me and initial work on supporting Xe and Xi cards (ala
-      dgb) was done by me. I'm now awaiting an Xe card being sent from
-      joerg@ (almost a donation) so that I can get that side of things
-      working properly.</p>
-    <hr /><h2><a name="Diskcheckd" href="#Diskcheckd" id="Diskcheckd">Diskcheckd</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://phantom.cris.net/freebsd/projects/viewproj.php?p_id=15" title="http://phantom.cris.net/freebsd/projects/viewproj.php?p_id=15"></a></td><td>
-	    URL: <a href="http://phantom.cris.net/freebsd/projects/viewproj.php?p_id=15" title="">http://phantom.cris.net/freebsd/projects/viewproj.php?p_id=15</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>Ben Smithurst has written a "diskcheckd" daemon which will
-      read all sectors on the disks over a configured period. With
-      recent increases in disksizes it is by no means a given that disk
-      read errors will be discovered before they are fatal. This daemon
-      will hopefully result in the drive firmware being able to
-      relocate bad sectors before they become unreadable. This code is
-      now committed to 5.0-CURRENT.</p>
-    <hr /><h2><a name="if_fxp-driver" href="#if_fxp-driver" id="if_fxp-driver">if_fxp driver</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the last month (May-June), the new fxp driver was brought
-      into -stable. This new driver uses the common MII code, so
-      support for new PHYs is easy to add. Support for the new Intel
-      82562 chips was added. The driver was updated to add VLAN support
-      and a workaround for a bug affecting Intel 815-based boards.</p>
-    <hr /><h2><a name="Java-Project" href="#Java-Project" id="Java-Project">Java Project</a></h2><p>
-	Contact:
-          Greg
-
-          Lewis
-         &lt;<a href="mailto:glewis@eyesbeyond.com">glewis@eyesbeyond.com</a>&gt;
-	</p>
-      <p>The FreeBSD Java Project has continued its "behind the scenes"
-      work over the last month. Progress was made both technically,
-      with the help of Bill Huey (of Wind River), on a port of JDK
-      1.3.1 and legally, with Nate Williams continuing negotiations
-      with Sun on a mutually acceptable license to release a binary
-      Java 2 SDK under. The JDK 1.2.2 port has also seen some
-      development, with a new patchset likely to be released soon which
-      includes JPDA and NetBSD support (the latter courtesy of Scott
-      Bartram).</p>
-    <hr /><h2><a name="Kernel-Graphics-Interface-port" href="#Kernel-Graphics-Interface-port" id="Kernel-Graphics-Interface-port">Kernel Graphics Interface port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://kgi.sourceforge.net/" title="http://kgi.sourceforge.net/"></a></td><td>
-	    URL: <a href="http://kgi.sourceforge.net/" title="">http://kgi.sourceforge.net/</a></td></tr></table><p>
-	Contact:
-          Nicolas
-
-          Souchu
-         &lt;<a href="mailto:nsouch@fr.alcove.com">nsouch@fr.alcove.com</a>&gt;
-	</p>
-      <p>The Kernel Graphics Interface project has worked for several
-      years to provide a framework for graphic drivers under Linux
-      receiving input from other groups like the UDI project. Currently
-      the KGI core implementation is quite settled, as is the driver
-      coding model as a whole. Work is being done to newbussify KGI and
-      produce a kld, as part of a future redesign of the graphics
-      subsystem in FreeBSD. KGI will be an alternative for graphic card
-      producers that don't accept the XFree86 model of userland graphic
-      adapters and will also provide accelerated support for any other
-      graphic alternative.</p>
-    <hr /><h2><a name="libh-Project" href="#libh-Project" id="libh-Project">libh Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~alex/libh/" title="http://people.FreeBSD.org/~alex/libh/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~alex/libh/" title="">http://people.FreeBSD.org/~alex/libh/</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Langer
-         &lt;<a href="mailto:alex@FreeBSD.org">alex@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Nathan
-
-          Ahlstrom
-         &lt;<a href="mailto:nra@FreeBSD.org">nra@FreeBSD.org</a>&gt;
-	</p>
-      <p>The libh project is a next generation sysinstall. It is
-      written in C++ using QT for its graphical frontend and tvision
-      for its console support. The menus are scriptable via an embedded
-      tcl interpreter. It has been growing functionality quite a bit
-      lately, including a new disklabel editor. Current work is on
-      installation scripts for CDROM, FTP, ... installs as well as a
-      fully functional standalone disk-partition and label editor. The
-      GUI API was extended a little and many bugs were fixed. There
-      seems to be some interest in i18n work.</p>
-    <hr /><h2><a name="Mount(2)-API" href="#Mount(2)-API" id="Mount(2)-API">Mount(2) API</a></h2><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>Maxime Henrion is working on implementing a new and more
-      extensible mount(2) systemcall, mainly to overcome the 32 bits
-      for mountoptions limit, secondary goal to make it possible to
-      mount filesystems from inside the kernel.</p>
-    <hr /><h2><a name="OLDCARD-pccard-implementation" href="#OLDCARD-pccard-implementation" id="OLDCARD-pccard-implementation">OLDCARD pccard implementation</a></h2><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the last two months, the OLDCARD pccard implementation was
-      rototilled to within an inch of its life. Many new pci cardbus
-      bridges were added. Power handling was improved. PCI Card cardbus
-      bridges are nearly supported and should be committed in early
-      June to the tree. This will likely be the last major work done on
-      OLDCARD. After pci cards are supported, work will shift to
-      improving NEWCARD.</p>
-    <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-          Benno
-
-          Rice
-         &lt;<a href="mailto:benno@FreeBSD.org">benno@FreeBSD.org</a>&gt;
-	</p>
-      <p>The PowerPC port is proceeding well. All seems to be working
-      in pmap.c after a number of problems encountered where FreeBSD
-      passes a vm_page_t to a NetBSD-derived function that expects a
-      vm_offset_t. Then after debugging the atomic operations code, I'm
-      now at the point where VM appears to be initialized and it's now
-      hanging while in sys/kern/kern_malloc.c:kmeminit(). Progress
-      continues. =)</p>
-    <hr /><h2><a name="PPP" href="#PPP" id="PPP">PPP</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@FreeBSD.org">brian@FreeBSD.org</a>&gt;
-	</p>
-      <p>Developing full MPPE support for Andre Opperman @ Monzoon in
-      Switzerland. Work is now complete and will eventually be brought
-      into -current, but no dates are yet known.</p>
-    <hr /><h2><a name="Problem-Reports" href="#Problem-Reports" id="Problem-Reports">Problem Reports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://phk.freebsd.dk/Gnats/" title="http://phk.freebsd.dk/Gnats/"></a></td><td>
-	    URL: <a href="http://phk.freebsd.dk/Gnats/" title="">http://phk.freebsd.dk/Gnats/</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>Poul-Henning Kamp kicked off a drive to get our GNATS PR
-      database cleaned up so the wheat can be sorted from the chaff.
-      Progress is good, but there is still a lot of work to do. Give a
-      hand if you can. Remember: every unhandled PR is a pissed off
-      contributor or user.</p>
-    <hr /><h2><a name="pseudofs" href="#pseudofs" id="pseudofs">pseudofs</a></h2><p>
-	Contact:
-          Dag-Erling
-
-          Smorgrav
-         &lt;<a href="mailto:des@FreeBSD.org">des@FreeBSD.org</a>&gt;
-	</p>
-      <p>Pseudofs is a framework for pseudo-filesystems, like procfs
-      and linprocfs. The goal of pseudofs is twofold:</p>
-
-      <ul>
-        <li>eliminate code duplication between (and within) procfs and
-        linprocfs</li>
-
-        <li>isolate procfs and linprocfs from the complexities of the
-        vfs system to simplify maintenance and further
-        development.</li>
-      </ul>
-
-      <p>Pseudofs has reached the point where it is sufficiently
-      functional and stable that linprocfs has been almost fully
-      reimplemented on top of it; the only bit that's missing is the
-      proc/&lt;pid&gt;/mem file.</p>
-
-      <p>The primary to-do item for pseudofs right now is to add
-      support for writeable files (which are required for procfs, and
-      are quite a bit less trivial to handle than read-only files). In
-      addition, pseudofs needs either generic support for raw
-      (non-sbuf'ed, possibly mmap'able) files, or failing that,
-      special-case code to handle proc/&lt;pid&gt;/mem.</p>
-    <hr /><h2><a name="RELNOTESng" href="#RELNOTESng" id="RELNOTESng">RELNOTESng</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmah/relnotes/" title="http://people.FreeBSD.org/~bmah/relnotes/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmah/relnotes/" title="">http://people.FreeBSD.org/~bmah/relnotes/</a></td></tr></table><p>
-	Contact:
-          Bruce
-
-          A. Mah
-         &lt;<a href="mailto:bmah@FreeBSD.org">bmah@FreeBSD.org</a>&gt;
-	</p>
-      <p>RELNOTESng is the name I've given to the rewrite of the *.TXT
-      files that typically accompany a FreeBSD release. The information
-      from these files (which include, among other things, the release
-      notes and the supported hardware list) have been reorganized and
-      converted to SGML. This helps us produce the documentation in
-      various formats, as well as facilitating the maintenance of
-      documentation for multiple architectures. This work was recently
-      committed to -CURRENT, and I intend to MFC it to 4-STABLE before
-      4.4-RELEASE.</p>
-    <hr /><h2><a name="SMPng-mbuf-allocator" href="#SMPng-mbuf-allocator" id="SMPng-mbuf-allocator">SMPng mbuf allocator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" title="http://people.FreeBSD.org/~bmilekic/code/mb_slab/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" title="">http://people.FreeBSD.org/~bmilekic/code/mb_slab/</a></td></tr></table><p>
-	Contact:
-          Bosko
-
-          Milekic
-         &lt;<a href="mailto:bmilekic@FreeBSD.org">bmilekic@FreeBSD.org</a>&gt;
-	</p>
-      <p>mb_alloc is a new specialized allocator for mbufs and mbuf
-      clusters. Presently, it offers various important advantages over
-      the old (status quo) mbuf allocator, particularly for MP
-      machines. Additionally, it is designed with the possibility of
-      future enhancements in mind.</p>
-
-      <p>Presently in initial review &amp; testing stages, most of the
-      code is already written.</p>
-    <hr /><h2><a name="SMPng-Project" href="#SMPng-Project" id="SMPng-Project">SMPng Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~jasone/smp/" title="http://www.FreeBSD.org/~jasone/smp/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jasone/smp/" title="">http://www.FreeBSD.org/~jasone/smp/</a></td></tr></table><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Jake
-
-          Burkholder
-         &lt;<a href="mailto:jake@FreeBSD.org">jake@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          SMP
-
-          Mailing list
-         &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The SMPng project aims to provide multithreaded support for
-      the FreeBSD kernel. Currently the kernel still runs almost
-      exclusively under the Giant kernel lock. Recently, progress has
-      been made in locking the process group and session structures as
-      well as file descriptors by Seigo Tanimura-san. Alfred Perlstein
-      has also added in a giant lock around the entire virtual memory
-      (VM) subsystem which will eventually be split up into several
-      smaller locks. The locking of the VM subsystem has proved tricky,
-      and some of the current effort is focused on finding and fixing a
-      few remaining bugs in on the alpha architecture.</p>
-    <hr /><h2><a name="Sparc64-Port" href="#Sparc64-Port" id="Sparc64-Port">Sparc64 Port</a></h2><p>
-	Contact:
-          Jake
-
-          Burkholder
-         &lt;<a href="mailto:jake@FreeBSD.org">jake@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has (re)started on a port of FreeBSD to the UltraSPARC
-      architecture, specifically targeting PCI based workstations. Jake
-      Burkholder will be porting the kernel, and Ade Lovett has
-      expressed an interest in working on userland. Recent work on the
-      project includes:</p>
-
-      <ul>
-        <li>built a gnu cross toolchain targeting sparc64</li>
-
-        <li>obtained remote access to an ultra 5 development machine
-        (thanks to emmy)</li>
-
-        <li>developed a minimal set of headers and source files to
-        allow the kernel to be compiled and linked</li>
-
-        <li>implemented a mini-loader which relocates the kernel, maps
-        it into the tlbs and calls it</li>
-
-        <li>nabbed Benno Rice's openfirmware console driver which
-        allows printf and panic to work</li>
-      </ul>
-
-      <p>At this point the kernel can be net-booted and prints the
-      FreeBSD copyright before calling code that is not yet
-      implemented. I am currently working on a design for the pmap
-      module and plan to begin implementation in the next few days.</p>
-    <hr /><h2><a name="TrustedBSD" href="#TrustedBSD" id="TrustedBSD">TrustedBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/"></a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project seeks to improve the security of the
-      FreeBSD operating system by adding new security features, many
-      derived from common trusted operating system requirements. This
-      includes Access Control Lists (ACLs), Fine-grained Event Logging
-      (Audit), Fine-grained Privileges (Capabilities), Mandatory Access
-      Control (MAC), and other architecture features, including file
-      system extended attributes, and improved object labeling.</p>
-
-      <p>Individual feature status reports are documented separately
-      below; in general, basic features (such as EAs, ACLs, and kernel
-      support for Capabilities) will be initially available in
-      5.0-RELEASE, conditional on specific kernel options. A
-      performance-enhanced version of EAs is currently being targeted
-      at 6.0-RELEASE, along with an integrated capability-aware
-      userland, and MAC support.</p>
-    <hr /><h2><a name="TrustedBSD-Capabilities" href="#TrustedBSD-Capabilities" id="TrustedBSD-Capabilities">TrustedBSD Capabilities</a></h2><p>
-	Contact:
-          Thomas
-
-          Moestl
-         &lt;<a href="mailto:tmm@FreeBSD.org">tmm@FreeBSD.org</a>&gt;
-	</p>
-      <p>The kernel part of the capability implementation is mostly
-      finished; all uses of suser() and suser_xxx() and nearly all
-      comparisons of uid's with 0 have been converted to use the newly
-      introduced cap_check() call. Some details still need
-      clarification. More documentation for this needs to be done.</p>
-
-      <p>POSIX.2c-compatible getfcap and setfcap programs have been
-      written. Experimental capability support in su(1), login(1),
-      install(1) and bsd.prog.mk is being tested.</p>
-
-      <p>Support for capabilities, ACL's, capabilities and MAC labels
-      in tar(1) is being developed; only the capability part is tested
-      right now. Generic support for extended attributes is planned,
-      this will require extensions to the current EA interface, which
-      are written and will probably be committed to -CURRENT in a few
-      weeks. A port of these features to pax(1) is planned.</p>
-    <hr /><h2><a name="TrustedBSD-MAC-and-Object-Labeling" href="#TrustedBSD-MAC-and-Object-Labeling" id="TrustedBSD-MAC-and-Object-Labeling">TrustedBSD MAC and Object Labeling</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/"></a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>An initial prototype of a Mandatory Access Control
-      implementation was completed earlier this year, supporting
-      Multi-Level Security, Biba Integrity protection, and a more
-      general jail-based access control model. Based on that
-      implementation, I'm now in the process of improving the FreeBSD
-      security abstractions to simplify both the implementation and
-      integration of MAC support, as well as increase the number of
-      kernel objects protected by both discretionary and mandatory
-      protection schemes. Generic object labeling introduces a
-      structure not dissimilar in properties to the kernel ucred
-      structure, only it is intended to be associated with kernel
-      objects, rather than kernel subjects, permitting the creation of
-      generic security protection routines for objects. This would
-      allow the easy extension of procfs and devfs to support ACLs and
-      MAC, for example. A prototype is underway, with compiling and
-      running code and simple protections now associated with
-      sysctl's.</p>
-    <hr /><h2><a name="TrustedBSD:-ACLs" href="#TrustedBSD:-ACLs" id="TrustedBSD:-ACLs">TrustedBSD: ACLs</a></h2><p>
-	Contact:
-          Chris
-
-          D. Faulhaber
-         &lt;<a href="mailto:jedgar@FreeBSD.org">jedgar@FreeBSD.org</a>&gt;
-	</p>
-      <p>Patches are now available to add ACL support to cp(1) and
-      mv(1) along with preliminary support for install(1). Ilmar's i18n
-      patches for getfacl(1) and setfacl(1) need to be updated for the
-      last set of changes and committed. Some other functional
-      improvements are also in the pipeline.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2001-07.html b/website/content/en/status/report-2001-07.html
deleted file mode 100644
index 5e053d7d78..0000000000
--- a/website/content/en/status/report-2001-07.html
+++ /dev/null
@@ -1,940 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Last month's status report was apparently a great success: I
-    received countless e-mails with comments, questions, and
-    suggestions. I've tried to incorporate any suggestions and address
-    any problems from these e-mails in this month's report, which
-    captures a far more extensive snapshot of FreeBSD activity in the
-    last month. Unlike last month's report, it does a better job of
-    reflecting non-development activity, such as on-going conference
-    planning, documentation, and so on. This is a trend I hope to see
-    improve in future months as well.</p><p>On the topic of conferences, in the future I'd like to report
-    more on publication activities relating to FreeBSD, including
-    online journals with articles relating to FreeBSD, paper journals,
-    conference papers, and so on. Likewise, I would be interested in
-    including references to Call for Papers relating to FreeBSD. I'll
-    take this opportunity to plug both registration and paper
-    submission for BSDCon Europe in November, which has status included
-    in this report, and for the general BSD Conference being hosted by
-    USENIX in February. Your attendance and submissions make these
-    conferences "happen", and promote FreeBSD as a platform for new
-    research, feature development, and application products. Work of
-    extremely high calibre is performed on FreeBSD, and we need to get
-    the word out.</p><h1>Submission for Future Editions</h1><p>Next month, we're maintaining much the same submission
-    requirements: reports should be one or two paragraphs long, sent by
-    e-mail, and approximate the layout of the entries this month
-    (Project, Contact, URL, and text). I'll send out reminders again
-    over the week before the deadline, with more specific instructions.
-    An area where I'd like to explore improvement lies in the
-    coordination of related status reports for larger projects, such as
-    new architectural work or platform ports. This might even have the
-    effect of encouraging communication within these projects :-). I'd
-    like to continue to focus on pulling in a broader range of groups
-    and their activities, including the Security Officer, Release
-    Engineer, and Core Team.</p><p>
-      <i>-- Robert Watson &lt;
-      <a href="mailto:rwatson@FreeBSD.org" shape="rect">rwatson@FreeBSD.org</a>
-
-      &gt;</i>
-    </p><hr /><ul><li><a href="#ACPI">ACPI</a></li><li><a href="#ARM-Port">ARM Port</a></li><li><a href="#BIND-9">BIND 9</a></li><li><a href="#binup">binup</a></li><li><a href="#BSDCon-Europe">BSDCon Europe</a></li><li><a href="#CAM">CAM</a></li><li><a href="#Documentation-Project">Documentation Project</a></li><li><a href="#Fibre-Channel-Support">Fibre Channel Support</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#FreeBSD-Monthly-Development-Status-Reports">FreeBSD Monthly Development Status Reports</a></li><li><a href="#FreeBSD/sparc64-kernel-loader">FreeBSD/sparc64 kernel loader</a></li><li><a href="#Hardware-Watchpoints-in-the-Kernel-Debugger">Hardware Watchpoints in the Kernel Debugger</a></li><li><a href="#ifconfig-support-for-IEEE-802.11-wireless-devices">ifconfig support for IEEE 802.11 wireless devices</a></li><li><a href="#jailNG">jailNG</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#Kernel-Summit---Usenix-2001">Kernel Summit - Usenix 2001</a></li><li><a href="#KSE-threading-the-kernel">KSE threading the kernel</a></li><li><a href="#NetBSD-rc.d-port">NetBSD rc.d port</a></li><li><a href="#Netgraph-ATM">Netgraph ATM</a></li><li><a href="#network-device-cloning">network device cloning</a></li><li><a href="#Next-Generation-POSIX-threads-(NGPT)">Next Generation POSIX threads (NGPT)</a></li><li><a href="#OLDCARD-upgrade-to-support-PCI-cards">OLDCARD upgrade to support PCI cards</a></li><li><a href="#Open-Runtime-Platform-(ORP)">Open Runtime Platform (ORP)</a></li><li><a href="#OpenPackages">OpenPackages</a></li><li><a href="#PAM">PAM</a></li><li><a href="#Porting-ppp-to-hurd-&amp;-linux">Porting ppp to hurd &amp; linux</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#PPP-IPv6-Support">PPP IPv6 Support</a></li><li><a href="#pppoed">pppoed</a></li><li><a href="#PRFW---Hooks-within-the-FreeBSD-kernel">PRFW - Hooks within the FreeBSD kernel</a></li><li><a href="#Problem-Reports">Problem Reports</a></li><li><a href="#SCSI-Tape-Support">SCSI Tape Support</a></li><li><a href="#SMPng">SMPng</a></li><li><a href="#SMPng-mbuf-allocator">SMPng mbuf allocator</a></li><li><a href="#sparc64-port">sparc64 port</a></li><li><a href="#SYN-cache-implementation-for-FreeBSD">SYN cache implementation for FreeBSD</a></li><li><a href="#TrustedBSD-Project">TrustedBSD Project</a></li></ul><hr /><h2><a name="ACPI" href="#ACPI" id="ACPI">ACPI</a></h2><p>
-	Contact:
-          Mike
-
-          Smith
-         &lt;<a href="mailto:msmith@FreeBSD.org">msmith@FreeBSD.org</a>&gt;
-	</p>
-      <p>ACPI (Advanced Configuration and Power Interface) is an
-      industry standard which obsoletes APM, Intel MPS, PnPBIOS, and
-      other Intel PC firmware interface standards. It is also used on
-      the IA64 platform. More information on ACPI is available at</p>
-
-      <a href="http://developer.intel.com/technology/iapc/acpi" shape="rect">
-      http://developer.intel.com/technology/iapc/acpi</a>
-
-      <p>The FreeBSD ACPI subsystem project is based heavily on the
-      Intel ACPI Component Architecture. This status report outlines
-      the current state of the project; future updates will focus on
-      changes as they occur.</p>
-
-      <p>The Intel ACPI interpreter is fully integrated, although bugs
-      are still coming out of the woodwork occasionally.</p>
-
-      <ul>
-        <li>PCI bus detection and interrupt routing are functional, but
-        power management interaction will require work on the core PCI
-        subsystem.</li>
-
-        <li>Non-PCI motherboard peripheral probing is implemented, but
-        believed to have problems on some systems.</li>
-
-        <li>A power policy manager has been implemented. The initial
-        policy manager has two modes, "performance" and "economy".</li>
-
-        <li>CPU speed throttling is integrated with the platform power
-        policy.</li>
-
-        <li>System thermal monitoring is implemented, but fan control
-        is believed to have problems.</li>
-
-        <li>Pushbutton suspend and power-off is implemented.</li>
-
-        <li>System timekeeping using the ACPI timer is supported.</li>
-
-        <li>Battery status monitoring is implemented.</li>
-      </ul>
-
-      <p>Work is ongoing in the following areas:</p>
-
-      <ul>
-        <li>System suspend and resume.</li>
-
-        <li>Timekeeper accuracy/reliability.</li>
-
-        <li>Power profiles.</li>
-
-        <li>User-level management interfaces.</li>
-
-        <li>PCI power management.</li>
-
-        <li>Bug-hunting.</li>
-      </ul>
-    <hr /><h2><a name="ARM-Port" href="#ARM-Port" id="ARM-Port">ARM Port</a></h2><p>
-	Contact:
-          Stephane
-
-          Potvin
-         &lt;<a href="mailto:septovin@videotron.ca">septovin@videotron.ca</a>&gt;
-	</p>
-      <p>The ARM port is currently going pretty well. The kernel is
-      compiling and is able to boot to the point where it panics trying
-      to initialize the network subsystem. The current reference
-      platform is the Netwinder but this may change as many people
-      expressed interest in a more broadly available platform. Things
-      that need to be done before it can get further includes adding
-      footbridge, timer and interrupt supports. The pmap module is not
-      completed yet either.</p>
-    <hr /><h2><a name="BIND-9" href="#BIND-9" id="BIND-9">BIND 9</a></h2><p>
-	Contact: Doug Barton &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jeroen Ruigrok &lt;<a href="mailto:asmodai@FreeBSD.org">asmodai@FreeBSD.org</a>&gt;
-	</p>
-      <p>Now that BIND 8.2.4 is finally imported the time has come to
-      look at getting BIND 9 imported into CURRENT. The current idea is
-      to have it imported alongside BIND 8 so that people can play with
-      either one until all import problems have been taken care of and
-      people have tested it a bit.</p>
-    <hr /><h2><a name="binup" href="#binup" id="binup">binup</a></h2><p>
-	Contact: Eric Melville &lt;<a href="mailto:eric@FreeBSD.org">eric@FreeBSD.org</a>&gt;
-	</p>
-      <p>Although gaining a new name, the project has been at a
-      standstill due to both resource availability during the move
-      between BSDi and Wind River, and other commitments of the
-      developers. The project should obtain an official mailing list,
-      as well as return to an active state after the dust settles.</p>
-    <hr /><h2><a name="BSDCon-Europe" href="#BSDCon-Europe" id="BSDCon-Europe">BSDCon Europe</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdconeurope.org" title="http://www.bsdconeurope.org"></a></td><td>
-	    URL: <a href="http://www.bsdconeurope.org" title="">http://www.bsdconeurope.org</a></td></tr></table><p>
-	Contact: Paul Richards &lt;<a href="mailto:paul@freebsd-services.co.uk">paul@freebsd-services.co.uk</a>&gt;
-	<br />
-	Contact: Josef Karthauser &lt;<a href="mailto:joe@tao.org.uk">joe@tao.org.uk</a>&gt;
-	</p>
-      <p>The conference will take place at the Thistle Hotel, Brighton,
-      UK from 9-11 November 2001.</p>
-
-      <p>The aim of the conference is to provide a focal point for
-      European users and developers of all the BSD derived operating
-      systems. The format will be similar to other conferences, with 2
-      days of technical sessions over the Saturday and Sunday.</p>
-
-      <p>We'll be finalizing the schedule towards the end of the month
-      and anybody who is interested in doing a talk should contact us
-      ASAP. There are no restrictions on the use of talks; if it's been
-      done before we may still be interested in having it presented to
-      an European audience, and we make no claims to the talks so
-      speakers are free to present the talks again at other
-      conferences.</p>
-
-      <p>We're also still looking for sponsors.</p>
-
-      <p>We had 80 pre-registrations in the first week so we're
-      expecting a good turnout.</p>
-    <hr /><h2><a name="CAM" href="#CAM" id="CAM">CAM</a></h2><p>
-	Contact: Matthew Jacob &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Justin Gibbs &lt;<a href="mailto:gibbs@FreeBSD.org">gibbs@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new CAM transport code is starting to get supported in
-      more HBAs and to get refined so that it does the intended
-      per-protocol support. No progress on doing any SMPng work for CAM
-      has been made yet. This is a fairly high priority.</p>
-    <hr /><h2><a name="Documentation-Project" href="#Documentation-Project" id="Documentation-Project">Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/docs.html" title="http://www.FreeBSD.org/docs.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/docs.html" title="">http://www.FreeBSD.org/docs.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/docproj/index.html" title="http://www.FreeBSD.org/docproj/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/docproj/index.html" title="">http://www.FreeBSD.org/docproj/index.html</a></td></tr></table><p>
-	Contact: Documentation Project &lt;<a href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work continues (in large part sponsored by WRS) on updating
-      the Handbook ready for the second print edition. There has been a
-      flurry of activity in this area recently, and the ToDo list can
-      be seen at</p>
-
-      <p>
-        <a href="http://www.FreeBSD.org/docproj/handbook.html" shape="rect">
-        http://www.FreeBSD.org/docproj/handbook.html</a>
-      </p>
-
-      <p>Dima and others are doing a stellar job of keeping up with the
-      steady flow of incoming PRs relating to the documentation
-      project.</p>
-
-      <p>The Developers' Handbook,</p>
-
-      <p>
-        <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/index.html" shape="rect">
-        http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/index.html</a>
-      </p>
-
-      <p>is a year old; it contains a wealth of useful content for
-      developers developing on, or for, FreeBSD. As ever, more
-      contributions are always required, not only for the developers'
-      handbook, but for all of the FreeBSD documentation set.</p>
-    <hr /><h2><a name="Fibre-Channel-Support" href="#Fibre-Channel-Support" id="Fibre-Channel-Support">Fibre Channel Support</a></h2><p>
-	Contact: Matthew Jacob &lt;<a href="mailto:mjacob@feral.com">mjacob@feral.com</a>&gt;
-	</p>
-      <p>The basic design hasn't changed and this project mainly is in
-      the phase of continued hardening and test case development. The
-      next major feature will be to fully integrate into the new CAM
-      TRAN code and to fully support on the fly device addition and
-      removal. The only HBA supported is QLogic at this time. Future
-      support for the QLogic line is planned to have 2300 (2Gb) and IP
-      support before October.</p>
-    <hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java/" title="http://www.FreeBSD.org/java/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java/" title="">http://www.FreeBSD.org/java/</a></td></tr></table><p>
-	Contact: Greg Lewis &lt;<a href="mailto:glewis@eyesbeyond.com">glewis@eyesbeyond.com</a>&gt;
-	</p>
-      <p>The main development in the FreeBSD Java Project over the last
-      month was the release of an initial "Developers Only" patchset
-      for the JDK 1.3.1. Since that release progress had been made
-      towards a much more usable alpha quality patchset which is
-      likely to be turned into a port, as per the current JDK 1.2.2
-      patchset. This new patchset will feature a number of bugfixes,
-      which essentially get the JDK to a working state for early
-      adopters, and an initial implementation of "native threads" based
-      on FreeBSD's userland pthreads. Unfortunately this implementation
-      isn't fully functional, but is included in the hope of
-      getting more eyeballs on the code (particularly experienced
-      pthread programmers). We'd also like to welcome Fuyuhiko
-      Maruyama-san as a new committer, the usual punishment for too
-      many good patches.</p>
-    <hr /><h2><a name="FreeBSD-Monthly-Development-Status-Reports" href="#FreeBSD-Monthly-Development-Status-Reports" id="FreeBSD-Monthly-Development-Status-Reports">FreeBSD Monthly Development Status Reports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/news/status/" title="http://www.FreeBSD.org/news/status/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/news/status/" title="">http://www.FreeBSD.org/news/status/</a></td></tr></table><p>
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org&gt;">rwatson@FreeBSD.org&gt;</a>&gt;
-	<br />
-	Contact: Chris Costello &lt;<a href="mailto:chris@FreeBSD.org">chris@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Monthly Development Status Report aims to keep
-      users and developers up-to-date on the latest goings-on in the
-      FreeBSD project by providing summaries of each project and its
-      status. At the time of this writing, the July 2001 status report
-      is being prepared and is very near release. The FreeBSD Web site
-      now has a Status Reports section, which, when the July 2001
-      report is released, will be updated to include a link to an
-      HTML-ified version.</p>
-    <hr /><h2><a name="FreeBSD/sparc64-kernel-loader" href="#FreeBSD/sparc64-kernel-loader" id="FreeBSD/sparc64-kernel-loader">FreeBSD/sparc64 kernel loader</a></h2><p>
-	Contact: Robert Drehmel &lt;<a href="mailto:robert@ferrari.de">robert@ferrari.de</a>&gt;
-	</p>
-      <p>The sparc64 loader is functional enough to boot an ELF binary
-      from an UFS filesystem using the existent openfirmware library,
-      which has been revised to work flawlessly on 32-bit and 64-bit
-      architectures. Support for netbooting and modules will be
-      implemented next, followed by a better openfirmware mapping
-      strategy.</p>
-    <hr /><h2><a name="Hardware-Watchpoints-in-the-Kernel-Debugger" href="#Hardware-Watchpoints-in-the-Kernel-Debugger" id="Hardware-Watchpoints-in-the-Kernel-Debugger">Hardware Watchpoints in the Kernel Debugger</a></h2><p>
-	Contact: Brian Dean &lt;<a href="mailto:bsd@FreeBSD.org">bsd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Hardware watchpoints are now available for kernel debugging on
-      the IA32 (i386) architecture. One can now set hardware
-      watchpoints using the new ddb command 'hwatch', which is
-      analogous to the existing 'watch' command. Alternatively, if
-      greater flexibility is required, direct access to the debug
-      registers is available using the ddb 'set' command which allows
-      complete control over the processor hardware debug facilities.
-      Hardware watchpoints are very useful in tracking down those
-      elusive memory overwrite bugs in the kernel. Hardware watchpoints
-      can even be used to set a code breakpoint in ROM, which is
-      commonly found in embedded systems.</p>
-    <hr /><h2><a name="ifconfig-support-for-IEEE-802.11-wireless-devices" href="#ifconfig-support-for-IEEE-802.11-wireless-devices" id="ifconfig-support-for-IEEE-802.11-wireless-devices">ifconfig support for IEEE 802.11 wireless devices</a></h2><p>
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for configuring IEEE 802.11 wireless devices via
-      ifconfig has been committed to -current and -stable. It contains
-      most of the functionality needed to configure an wireless device.
-      Some missing features are being worked on including integrated
-      support for DHCP so a single entry in /etc/rc.conf can be used to
-      fully configure a wireless device on a DHCP lan and setting the
-      CTS/RTS threshold. Currently the an(4) and wi(4) drivers are
-      supported in -current and -stable with the awi(4) device
-      supported in -current. Further work is needed to support
-      Frequency Hopping devices such as ray(4).</p>
-    <hr /><h2><a name="jailNG" href="#jailNG" id="jailNG">jailNG</a></h2><p>
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>jailNG is a from-scratch rewrite of the popular jail(8)
-      service, focusing on improved management functions, as well as
-      more fine-grained configurability. An initial prototype has been
-      written, based on explicitly named and configured jails, and work
-      is proceeding on userland integration. Currently, it's not clear
-      if the timeline for this will be 5.0-RELEASE, or 5.1-RELEASE.</p>
-    <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/"></a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact: Japanese Man Page Project &lt;<a href="mailto:man-jp@jp.FreeBSD.org">man-jp@jp.FreeBSD.org</a>&gt;
-	</p>
-      <p>We have been working to provide Japanese version of FreeBSD
-      online manuals, since 1996. Currently, RELENG_4 manuals are
-      based. Translated versions are placed on doc/ja_JP.eucJP/man and
-      provided to users using ports/japanese/man-doc. Also, we discuss
-      about related commands (e.g. ports/japanese/man and
-      ports/japanese/groff).</p>
-    <hr /><h2><a name="Kernel-Summit---Usenix-2001" href="#Kernel-Summit---Usenix-2001" id="Kernel-Summit---Usenix-2001">Kernel Summit - Usenix 2001</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~jhb/summit/usenix01/" title="http://www.FreeBSD.org/~jhb/summit/usenix01/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jhb/summit/usenix01/" title="">http://www.FreeBSD.org/~jhb/summit/usenix01/</a></td></tr></table><p>
-	Contact: John Baldwin &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The first FreeBSD kernel summit meeting was held June 29-30,
-      2001 in Boston, MA at the Usenix 2001 Annual Technical
-      Conference. Links to a variety of files are posted on the web
-      site.</p>
-
-      <p>Note: I (jhb) am still working on writing up a general summary
-      of the meeting. When that is completed it will be posted here and
-      mailed to the -hackers mailing list.</p>
-    <hr /><h2><a name="KSE-threading-the-kernel" href="#KSE-threading-the-kernel" id="KSE-threading-the-kernel">KSE threading the kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~jasone/kse/" title="http://people.FreeBSD.org/~jasone/kse/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~jasone/kse/" title="">http://people.FreeBSD.org/~jasone/kse/</a></td></tr></table><p>
-	Contact: Julian Elischer &lt;<a href="mailto:julian@elischer.org">julian@elischer.org</a>&gt;
-	</p>
-      <p>I'm working on multithreading the kernel. So far I have over
-      400KB of diffs relative to today's -current (I'm keeping my tree
-      updated with changes as they occur rather than get hit with a big
-      update at the end).</p>
-
-      <p>I have split the proc structure and am changing most of the
-      kernel to pass around a thread identifier instead of a proc
-      structure.</p>
-
-      <p>The following interfaces have been changed so far:</p>
-
-      <ul>
-        <li>device devsw entries</li>
-
-        <li>vfs calls</li>
-
-        <li>mutexes</li>
-
-        <li>events</li>
-
-        <li>system calls</li>
-
-        <li>scheduler</li>
-
-        <li>+ a lot of code in between.</li>
-      </ul>
-
-      <p>I have still a lot of work to go with a lot of "dumb editing"
-      (s/struct proc \*p/struct thread \*td/) usually I change a few
-      items and then fix everything that breaks when I try compile it.
-      I'd like to check it in on a branch so others can help the
-      editing but haven't worked out the best way to do it yet.</p>
-
-      <p>I have implemented changes to the scheduler so that KSE's are
-      scheduled instead of processes, and threads sleep, letting the
-      KSE pick up a new thread. but it's not anywhere ready yet (heck
-      it doesn't compile yet :-)</p>
-
-      <p>Note that I have not yet updated the document listed above..
-      everywhere it mentions "ksec" or "KSE-context", the code uses the
-      word "thread". I will update it soon as Jason has sent me the
-      source.</p>
-    <hr /><h2><a name="NetBSD-rc.d-port" href="#NetBSD-rc.d-port" id="NetBSD-rc.d-port">NetBSD rc.d port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://groups.yahoo.com/group/FreeBSD-rc" title="http://groups.yahoo.com/group/FreeBSD-rc"></a></td><td>
-	    URL: <a href="http://groups.yahoo.com/group/FreeBSD-rc" title="">http://groups.yahoo.com/group/FreeBSD-rc</a></td></tr></table><p>
-	Contact: Doug Barton &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Sheldon Hearn &lt;<a href="mailto:sheldonh@FreeBSD.org">sheldonh@FreeBSD.org</a>&gt;
-	</p>
-      <p>The NetBSD rc.d port aims to improve the FreeBSD startup
-      process by porting Luke Mewburn's rc.d work from NetBSD to
-      FreeBSD. This will score FreeBSD startup and shutdown
-      dependencies without losing the traditional and much loved
-      monolithic configuration filesystem.</p>
-
-      <p>Luke Mewburn's USENIX paper and slides on the system as
-      implemented in NetBSD are available here:</p>
-
-      <p>
-        <a href="http://groups.yahoo.com/group/FreeBSD-rc/message/3" shape="rect">
-        http://groups.yahoo.com/group/FreeBSD-rc/message/3</a>
-      </p>
-
-      <p>Interested parties are urged to study this material before
-      joining the discussion list.</p>
-
-      <p>The intention at this stage is to decide on an approach that
-      will ensure that the differences between the NetBSD rc.d system
-      and the system as ported to FreeBSD will be kept to a minimum.
-      This will probably involve discussions with Luke around those
-      areas of the system that are identified as areas for potential
-      improvement.</p>
-    <hr /><h2><a name="Netgraph-ATM" href="#Netgraph-ATM" id="Netgraph-ATM">Netgraph ATM</a></h2><p>
-	Contact: Hartmut Brandt &lt;<a href="mailto:brandt@fokus.gmd.de">brandt@fokus.gmd.de</a>&gt;
-	</p>
-      <p>The goal of this project is the implementation of ATM
-      signalling and other ATM protocols by means of the netgraph(4)
-      framework. This should provide an easily extensible architecture
-      for using ATM on FreeBSD. Currently the full UNI4.0 stack (except
-      for the LIJ capability) has been implemented, including ILMI and
-      a first version of the ATM Forum API for UNI. An implementation
-      of Classical IP over ATM is also available. Drivers have been
-      implemented for the Fore PCA200E and Fore HE-155 cards.</p>
-    <hr /><h2><a name="network-device-cloning" href="#network-device-cloning" id="network-device-cloning">network device cloning</a></h2><p>
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Network device cloning support has been imported from NetBSD.
-      This allows virtual devices to be allocated on demand rather then
-      being statically allocated at compile time. Our implementation
-      differs slightly from that of NetBSD's in that we allow both the
-      creation of specific devices (i.e. gif0) and arbitrary devices
-      instead of just allowing specific devices. Currently, the only
-      device in the tree which has been converted is the gif(4) device
-      which has been converted in both -current and -stable. Work is
-      ongoing to convert all other virtual network devices with work in
-      progress on faith, stf, and vlan interfaces. In general this
-      conversion is accompanied by appropriate modifications to make
-      these devices fully modular.</p>
-    <hr /><h2><a name="Next-Generation-POSIX-threads-(NGPT)" href="#Next-Generation-POSIX-threads-(NGPT)" id="Next-Generation-POSIX-threads-(NGPT)">Next Generation POSIX threads (NGPT)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://oss.software.ibm.com/developerworks/opensource/pthreads/" title="http://oss.software.ibm.com/developerworks/opensource/pthreads/"></a></td><td>
-	    URL: <a href="http://oss.software.ibm.com/developerworks/opensource/pthreads/" title="">http://oss.software.ibm.com/developerworks/opensource/pthreads/</a></td></tr></table><p>
-	Contact: Arun Sharma &lt;<a href="mailto:arun@sharma.dhs.org">arun@sharma.dhs.org</a>&gt;
-	</p>
-      <h4>Porting NGPT (next generation pthreads) to FreeBSD</h4>
-
-      <p>NGPT is an effort led by IBM engineers to implement MxN
-      threads (also known as many user threads to one kernel thread
-      mapping) on Linux. I have ported it to FreeBSD to use
-      rfork(2).</p>
-
-      <p>The port is right here:</p>
-
-      <p>
-        <a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29239" shape="rect">
-        http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29239</a>
-      </p>
-    <hr /><h2><a name="OLDCARD-upgrade-to-support-PCI-cards" href="#OLDCARD-upgrade-to-support-PCI-cards" id="OLDCARD-upgrade-to-support-PCI-cards">OLDCARD upgrade to support PCI cards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~imp/oldcard-status.html" title="http://people.FreeBSD.org/~imp/oldcard-status.html"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~imp/oldcard-status.html" title="">http://people.FreeBSD.org/~imp/oldcard-status.html</a></td></tr></table><p>
-	Contact: Warner Losh &lt;<a href="mailto:imp@village.org">imp@village.org</a>&gt;
-	</p>
-      <p>
-        <i>Funded by: Monzoon Networking, LLC</i>
-      </p>
-
-      <p>This month has been a month of conventration and
-      consolidation. Much of the changes from current have been
-      migrating into stable. I've improved power support,
-      suspend/resume interactions, interrupt handling, and ability to
-      work after windows/NEWCARD has run. Interrupt routing continues
-      to be a locking issue for a complete MFC. Current patches are
-      available at the above website. I'm racing to get this done
-      before 4.4 is released.</p>
-    <hr /><h2><a name="Open-Runtime-Platform-(ORP)" href="#Open-Runtime-Platform-(ORP)" id="Open-Runtime-Platform-(ORP)">Open Runtime Platform (ORP)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.intel.com/research/mrl/orp/" title="http://www.intel.com/research/mrl/orp/"></a></td><td>
-	    URL: <a href="http://www.intel.com/research/mrl/orp/" title="">http://www.intel.com/research/mrl/orp/</a></td></tr></table><p>
-	Contact: Arun Sharma &lt;<a href="mailto:arun@sharmas.dhs.org">arun@sharmas.dhs.org</a>&gt;
-	<br />
-	Contact: eGroups: ORP &lt;<a href="mailto:orp@egroups.com">orp@egroups.com</a>&gt;
-	</p>
-      <p>Information on Intel ORP - a BSD licensed Java VM is right
-      here:</p>
-
-      <p>
-        <a href="http://www.intel.com/research/mrl/orp/" shape="rect">
-        http://www.intel.com/research/mrl/orp/</a>
-      </p>
-
-      <p>A FreeBSD patch has been tested to work with NGPT and
-      submitted to the ORP project. The patch is available here:</p>
-
-      <p>
-        <a href="http://www.sharma-home.net/~adsharma/projects/orp/orp-freebsd-1.0.5.patch.txt.gz" shape="rect">
-        http://www.sharma-home.net/~adsharma/projects/orp/orp-freebsd-1.0.5.patch.txt.gz</a>
-      </p>
-
-      <p>There are some issues to be ironed out to make it work with
-      FreeBSD's default (user level) pthread implementation.</p>
-    <hr /><h2><a name="OpenPackages" href="#OpenPackages" id="OpenPackages">OpenPackages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openpackages.org/" title="http://openpackages.org/"></a></td><td>
-	    URL: <a href="http://openpackages.org/" title="">http://openpackages.org/</a></td></tr></table>
-      <p>OpenPackages intends to create a software packaging system
-      that will allow third-party programs to be installed, without
-      operating system dependent changes, on as many platforms as are
-      feasible. OpenPackages was originally based on code from the BSD
-      ports systems, and has been improved and extended by developers
-      of many heritages.</p>
-
-      <p>The OpenPackages Project is pleased to release the Milestone 2
-      codebase. This release contains a working package building system
-      and a single test package. OP currently is known to build on
-      certain instances of the following operating systems: FreeBSD,
-      HP/UX, IRIX, Linux (Debian, Red Hat, Suse, Mandrake, TurboLinux,
-      Caldera, etc.), NetBSD, OpenBSD, Solaris</p>
-    <hr /><h2><a name="PAM" href="#PAM" id="PAM">PAM</a></h2><p>
-	Contact: Mark R V Murray &lt;<a href="mailto:mark@grondar.za">mark@grondar.za</a>&gt;
-	</p>
-      <p>(First report)</p>
-
-      <p>Large cleanup and extension of FreeBSD PAM modules. All
-      modules are to be documented, consistent in style (style(9) used)
-      and as complete as possible WRT functionality. Mostly done.</p>
-    <hr /><h2><a name="Porting-ppp-to-hurd-&amp;-linux" href="#Porting-ppp-to-hurd-&amp;-linux" id="Porting-ppp-to-hurd-&amp;-linux">Porting ppp to hurd &amp; linux</a></h2><p>
-	Contact: Brian Somers &lt;<a href="mailto:brian@Awfulhak.org">brian@Awfulhak.org</a>&gt;
-	</p>
-      <p>Patches have been submitted to get ppp working under HURD, and
-      mostly under Linux. There are GPL copyright problems that need to
-      be addressed.</p>
-    <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact: Benno Rice &lt;<a href="mailto:benno@FreeBSD.org">benno@FreeBSD.org</a>&gt;
-	</p>
-      <p>We now have the rudiments of device support. We have a nexus
-      driver for OpenFirmware machines, along with support for the
-      Apple UniNorth PCI/AGP host bridge. I'm currently trying to get
-      the USB hardware working so that I can get closer to having a
-      console driver independent of OpenFirmware, then I'll be trying
-      to get the system to get to single-user mode using NFS.</p>
-    <hr /><h2><a name="PPP-IPv6-Support" href="#PPP-IPv6-Support" id="PPP-IPv6-Support">PPP IPv6 Support</a></h2><p>
-	Contact: Brian Somers &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>Work has begun, but nothing has yet been committed. The NCP
-      addresses used by ppp have been abstracted and initial support
-      has been added to the filter set for ipv6 addresses. NCP
-      negotiation hasn't yet been started.</p>
-    <hr /><h2><a name="pppoed" href="#pppoed" id="pppoed">pppoed</a></h2><p>
-	Contact: Brian Somers &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>Making pppoed function in a production environment. Most of
-      the work is complete and committed. Additional work includes
-      adding a -l option where ``-l label'' is shorthand for ``-e exec
-      ppp -direct label'' and discovering why rogue child processes are
-      being left around.</p>
-    <hr /><h2><a name="PRFW---Hooks-within-the-FreeBSD-kernel" href="#PRFW---Hooks-within-the-FreeBSD-kernel" id="PRFW---Hooks-within-the-FreeBSD-kernel">PRFW - Hooks within the FreeBSD kernel</a></h2><p>
-	Contact: Evan Sarmiento &lt;<a href="mailto:ems@open-root.org">ems@open-root.org</a>&gt;
-	</p>
-      <p>PRFW is a set of hooks which I have integrated into the
-      FreeBSD kernel. This allows modules to easily intercept system
-      calls with less overhead. It also supports per-pid restrictions,
-      which means, one process may not be able to use X function in Y
-      manner, but another process may.</p>
-
-      <p>Progress: I was working on this in 4.3-RELEASE, but now I'm
-      merging it into current. I will be submitting a patch to the
-      mailing lists in about a week.</p>
-    <hr /><h2><a name="Problem-Reports" href="#Problem-Reports" id="Problem-Reports">Problem Reports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://phk.freebsd.dk/Gnats/" title="http://phk.freebsd.dk/Gnats/"></a></td><td>
-	    URL: <a href="http://phk.freebsd.dk/Gnats/" title="">http://phk.freebsd.dk/Gnats/</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>Thanks to various outstanding individual efforts, we are now
-      down to just below 2300 open bug-reports. This means that we have
-      fought our way back to the level we had around march 2000.</p>
-    <hr /><h2><a name="SCSI-Tape-Support" href="#SCSI-Tape-Support" id="SCSI-Tape-Support">SCSI Tape Support</a></h2><p>
-	Contact: Matthew Jacob &lt;<a href="mailto:mjacob@feral.com">mjacob@feral.com</a>&gt;
-	</p>
-      <p>This driver is currently not working well under -current and
-      is undergoing some work at this time. No major design or feature
-      changes are planned. There was some notion of adding TapeAlert
-      support, but HP supports that as a binary product via a user
-      library and it was felt that it'd be more politically prudent to
-      leave it alone.</p>
-    <hr /><h2><a name="SMPng" href="#SMPng" id="SMPng">SMPng</a></h2><p>
-	Contact: Peter Wemm &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;
-	<br />
-	Contact: John Baldwin &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <h4>Development</h4>
-
-      <p>In the 'smpng' p4 branch there is code to make the ast()
-      function loop to close the race when an AST is triggered while we
-      are handling previously triggered AST's.</p>
-
-      <p>In the 'jhb_preemption' p4 branch work is being done to make
-      the kernel fully preemptive. It is reportedly stable on UP x86,
-      but SMP x86 locks up, UP alpha has problems during shutdown and
-      can recurse indefinitely until it exhausts its stack.</p>
-
-      <h4>Management</h4>
-
-      <p>We are using a perforce repository for live development work,
-      which can track multiple separate long-lived works-in-progress
-      and collaborate between multiple developers at the same time on
-      the same change set.</p>
-
-      <p>FreeBSD-current is being imported into p4 hourly, for easy
-      tracking of the moving -current tree.</p>
-
-      <p>I haven't written up a good primer yet, but we're able to open
-      this up to the general developer community. NEWCARD work looks
-      like it will be done here too. Perforce is ideal for tracking
-      this sort of long-lived project without having to resort to
-      passing patches around.</p>
-
-      <p>KSE work is now being checked into a kse p4 branch - thanks
-      Julian!</p>
-
-      <p>KSE work is focusing on getting the main API changes into the
-      base tree well before 5.0.</p>
-    <hr /><h2><a name="SMPng-mbuf-allocator" href="#SMPng-mbuf-allocator" id="SMPng-mbuf-allocator">SMPng mbuf allocator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" title="http://people.FreeBSD.org/~bmilekic/code/mb_slab/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" title="">http://people.FreeBSD.org/~bmilekic/code/mb_slab/</a></td></tr></table><p>
-	Contact: Bosko Milekic &lt;<a href="mailto:bmilekic@FreeBSD.org">bmilekic@FreeBSD.org</a>&gt;
-	</p>
-      <p>mb_alloc is a specialized allocator for mbufs and mbuf
-      clusters. It offers various important advantages over the old
-      mbuf allocator, particularly for MP machines. Additionally, it
-      is designed with the possibility of important future
-      enhancements in mind.</p>
-
-      <p>The mb_alloc code has been committed to -CURRENT a month ago
-      and appears to be holding up well. Prior to committing it,
-      preliminary performance measurements were done merely to ensure
-      that it is not significantly worse than the old allocator, even
-      with Giant still in place. Results were promising
-      <a href="http://people.FreeBSD.org/~bmilekic/code/mb_alloc/results.html" shape="rect">
-      [http://people.FreeBSD.org/~bmilekic/code/mb_alloc/results.html]</a>
-
-      - also see jlemon's results (link at the bottom of accompanying
-      text). Since the commit, Matt Jacob has provided useful feedback
-      and bugfixes. Work is now being done to re-enable mbtypes
-      statistics and make appropriate changes to netstat(1) and
-      systat(1).</p>
-    <hr /><h2><a name="sparc64-port" href="#sparc64-port" id="sparc64-port">sparc64 port</a></h2><p>
-	Contact: Jake Burkholder &lt;<a href="mailto:jake@FreeBSD.org">jake@FreeBSD.org</a>&gt;
-	</p>
-      <p>The sparc64 port has been committed to the FreeBSD repository.
-      As such further development will occur in cvs, rather than as a
-      separately maintained patch set. Significant progress has been
-      made since the last status report, including; support for kernel
-      debugging with ddb, much more complete pmap support, support for
-      context switching and process creation, and filling out of
-      important machine dependent data structures. Thomas Moestl has
-      shown a strong interest in working on the port and is in the
-      process of implementing support for saving and restoring a
-      process's floating point context. I look forward to working with
-      him and any other developers that happen to fall out of the wood
-      works.</p>
-    <hr /><h2><a name="SYN-cache-implementation-for-FreeBSD" href="#SYN-cache-implementation-for-FreeBSD" id="SYN-cache-implementation-for-FreeBSD">SYN cache implementation for FreeBSD</a></h2><p>
-	Contact: Jonathan Lemon &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project brings a SYN cache implementation to FreeBSD, in
-      order to make it more robust to DoS attacks. A SYN cookie
-      approach was considered, but ultimately rejected because it does
-      not conform to the TCP protocol. The SYN cache will work with
-      T/TCP, IPV6 and IPSEC, and the size of each cache element is
-      currently is less than 1/5th the size of a normal TCP control
-      block.</p>
-    <hr /><h2><a name="TrustedBSD-Project" href="#TrustedBSD-Project" id="TrustedBSD-Project">TrustedBSD Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/"></a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>It's been a busy month, with a number of relevant news items.
-      Not least important is that NAI Labs was awarded a $1.2M contract
-      from the US Defense Advanced Research Projects Agency (DARPA) to
-      work on a variety of components relevant to the TrustedBSD
-      Project, including support for pluggable security models, and
-      supporting features such as improving the extended attributes
-      implementation, simple crypto support for swap and filesystems,
-      documentation, and much more.</p>
-
-      <p>On the features side, progress continues on Mandatory Access
-      Control, object labeling, and improving the consistency of kernel
-      access control mechanisms--in particular, with regard to
-      inter-process authorization and credential management. Work has
-      begun on porting LOMAC, NAI Labs' Low-Watermark Mandatory Access
-      Control scheme, from Linux to FreeBSD, and it has been
-      re-licensed under a BSD license. We hope to have an initial port
-      complete in time for 5.0-RELEASE later this year.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2001-08.html b/website/content/en/status/report-2001-08.html
deleted file mode 100644
index 6b0c7b80e0..0000000000
--- a/website/content/en/status/report-2001-08.html
+++ /dev/null
@@ -1,1131 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The FreeBSD Project made substantial progress in the month of
-    August, 2001, both on continuing the development of the RELENG_4
-    line (4.x-STABLE and 4.x-RELEASE), and on 5.0-CURRENT, the main
-    development branch. During this month, the decision was made to
-    push the release of 5.0-CURRENT back so that KSE (support for
-    fine-grained user threads) could be completed in time for the
-    release, rather than postponing that support for 6.0. As such, the
-    lifespan of the RELENG_4 line will be extended, with new features
-    continuing to be backported to that branch. 4.4-RELEASE went into
-    final beta during this month, and will also be available
-    shortly.</p><p>This month's edition of the status report has been written with
-    the assistance of Nik Clayton and Chris Costello.</p><h1>Future submissions</h1><p>For next month, the submission procedures remain the same:
-    reports should be between one and two paragraphs long, sent by
-    e-mail, and in a format approximately that of this month's
-    submissions (Project, Contact, URL, and text). Reminders will be
-    mailed to the hackers@FreeBSD.org and developers@FreeBSD.org
-    mailing lists at least a week before the deadline; complete
-    submission instructions may be found in those reminders.</p><p>-- Robert Watson</p><hr /><ul><li><a href="#aac-driver">aac driver</a></li><li><a href="#ARM-port">ARM port</a></li><li><a href="#BSDCon-Europe">BSDCon Europe</a></li><li><a href="#CAM">CAM</a></li><li><a href="#Compressed-TCP-state">Compressed TCP state</a></li><li><a href="#CVSROOT-script-rewrite/tidy">CVSROOT script rewrite/tidy</a></li><li><a href="#Documentation-Project">Documentation Project</a></li><li><a href="#fbsd-nvdriver">fbsd-nvdriver</a></li><li><a href="#Fibre-Channel-Support">Fibre Channel Support</a></li><li><a href="#floppy-driver-overhaul">floppy driver overhaul</a></li><li><a href="#FreeBSD-core-secretary">FreeBSD core-secretary</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#FreeBSD-PAM">FreeBSD PAM</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#FreeBSD/sparc64-port">FreeBSD/sparc64 port</a></li><li><a href="#GNOME-Desktop-for-FreeBSD">GNOME Desktop for FreeBSD</a></li><li><a href="#ia64-Port">ia64 Port</a></li><li><a href="#Improved-TCP-Initial-Sequence-Numbers">Improved TCP Initial Sequence Numbers</a></li><li><a href="#Intel-Gigabit-Ethernet">Intel Gigabit Ethernet</a></li><li><a href="#IP-Multicast-Routing-support">IP Multicast Routing support</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KAME">KAME</a></li><li><a href="#KSE">KSE</a></li><li><a href="#libh-Project">libh Project</a></li><li><a href="#LOMAC">LOMAC</a></li><li><a href="#Mbuf-SMPng-allocator">Mbuf SMPng allocator</a></li><li><a href="#Netgraph-ATM">Netgraph ATM</a></li><li><a href="#network-device-cloning">network device cloning</a></li><li><a href="#Network-device-nodes">Network device nodes</a></li><li><a href="#Network-SMP-locking">Network SMP locking</a></li><li><a href="#OLDCARD-improvements">OLDCARD improvements</a></li><li><a href="#Porting-ppp-to-hurd-&amp;-linux">Porting ppp to hurd &amp; linux</a></li><li><a href="#PPP-IPv6-Support">PPP IPv6 Support</a></li><li><a href="#pppoa">pppoa</a></li><li><a href="#pppoed">pppoed</a></li><li><a href="#PRFW---hooks-for-the-FreeBSD-kernel">PRFW - hooks for the FreeBSD kernel</a></li><li><a href="#Problem-Reports">Problem Reports</a></li><li><a href="#RAIDframe-for-FreeBSD">RAIDframe for FreeBSD</a></li><li><a href="#RELNOTESng">RELNOTESng</a></li><li><a href="#SCSI-Tape-Support">SCSI Tape Support</a></li><li><a href="#SMPng">SMPng</a></li><li><a href="#sppp(4)-merge">sppp(4) merge</a></li><li><a href="#SYN-cache-implementation-for-FreeBSD">SYN cache implementation for FreeBSD</a></li><li><a href="#TrustedBSD">TrustedBSD</a></li><li><a href="#TrustedBSD-Capabilities">TrustedBSD Capabilities</a></li></ul><hr /><h2><a name="aac-driver" href="#aac-driver" id="aac-driver">aac driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~scottl/aac" title="http://people.FreeBSD.org/~scottl/aac"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~scottl/aac" title="">http://people.FreeBSD.org/~scottl/aac</a></td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>The aac driver has been given a lot of attention lately and is
-      now nearly feature complete. Changes include crashdump support,
-      correct handling of controller initiated commands, and more
-      complete management interface support. The Linux RAID management
-      tool available from Dell and HP now fully works; a FreeBSD native
-      version of the tool is also in the works. These changes have been
-      checked into -current, and will appear in -stable once 4.4 has
-      been released.</p>
-    <hr /><h2><a name="ARM-port" href="#ARM-port" id="ARM-port">ARM port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pages.infinit.net/sepotvin/" title="http://pages.infinit.net/sepotvin/"></a></td><td>
-	    URL: <a href="http://pages.infinit.net/sepotvin/" title="">http://pages.infinit.net/sepotvin/</a></td></tr></table><p>
-	Contact:
-          Stephane
-
-          Potvin
-         &lt;<a href="mailto:sepotvin@videotron.ca">sepotvin@videotron.ca</a>&gt;
-	</p>
-      <p>Basic footbridge support is now functional and the kernel is
-      now able to probe the pci bus. Access primitives for the bus are
-      still missing so I can't attach any drivers yet.</p>
-    <hr /><h2><a name="BSDCon-Europe" href="#BSDCon-Europe" id="BSDCon-Europe">BSDCon Europe</a></h2><p>
-	Contact:
-          Paul
-
-          Richards
-         &lt;<a href="mailto:paul@freebsd-services.com">paul@freebsd-services.com</a>&gt;
-	</p>
-      <p>Planning for BSDCon Europe is going well. We're still
-      accepting proposals for talks but the schedule is starting to
-      fill up so we may not be for much longer.</p>
-
-      <p>An update of the site that includes accommodation information,
-      a preliminary schedule, a list of speakers and an online payment
-      page will be launched on Wednesday 19 September.</p>
-
-      <p>The fee will be �150 for individuals and �250 for
-      corporations. The individual pricing is valid only until the end
-      of September, the price will rise to �200 for October and
-      late registrations in November will be �250.</p>
-
-      <p>The updated website will include a list of sponsorship
-      options, we're still looking for more sponsorship.</p>
-    <hr /><h2><a name="CAM" href="#CAM" id="CAM">CAM</a></h2><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Justin
-
-          Gibbs
-         &lt;<a href="mailto:gibbs@FreeBSD.org">gibbs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Kenneth
-
-          Merry
-         &lt;<a href="mailto:ken@FreeBSD.org">ken@FreeBSD.org</a>&gt;
-	</p>
-      <p>No change since last status. Some discussion amongst all of us
-      occurred, but lack of time and commitment to FreeBSD has meant
-      little has actually been committed to the tree. SMPng work will
-      be left to those who seem to have a notion about what needs to be
-      done.</p>
-    <hr /><h2><a name="Compressed-TCP-state" href="#Compressed-TCP-state" id="Compressed-TCP-state">Compressed TCP state</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>State information for TCP connections is primarily kept in the
-      TCP/IP control blocks in the kernel. Not all of the TCP states
-      make use of the entire structure, and significant memory savings
-      can be had by using a cut-down version of the state in some
-      cases. The first phase of this project will address connections
-      that are in the TIME_WAIT state by moving them into a smaller
-      structure.</p>
-
-      <p>This project has completed the initial research and rough
-      design phases, with actual code development starting
-      immediately.</p>
-    <hr /><h2><a name="CVSROOT-script-rewrite/tidy" href="#CVSROOT-script-rewrite/tidy" id="CVSROOT-script-rewrite/tidy">CVSROOT script rewrite/tidy</a></h2><p>
-	Contact:
-          Josef
-
-          Karthauser
-         &lt;<a href="mailto:joe@FreeBSD.org">joe@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is still progressing to make all of the perl scripts run
-      using perl's 'strict' mode, and to migrate all FreeBSD specific
-      options into the configuration file (CVSROOT/cfg.pm). I'll be
-      looking for help soon to write a guide on how to make use of
-      these scripts for use in your own repository. Anyone interested
-      in helping should contact me at the above email address.</p>
-    <hr /><h2><a name="Documentation-Project" href="#Documentation-Project" id="Documentation-Project">Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/docs.html" title="http://www.FreeBSD.org/docs.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/docs.html" title="">http://www.FreeBSD.org/docs.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/docproj/index.html" title="http://www.FreeBSD.org/docproj/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/docproj/index.html" title="">http://www.FreeBSD.org/docproj/index.html</a></td></tr></table><p>
-	Contact:
-          Nik
-
-          Clayton
-         &lt;<a href="mailto:nik@FreeBSD.org">nik@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Documentation Project
-         &lt;<a href="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Handbook has been the main focus of activity this month.
-      Due to go to the printers on the 15th a vast amount of new
-      content has been submitted and committed. This includes a
-      complete rewrite of the "Installing FreeBSD", which massively
-      expands the amount of information available to people new to
-      FreeBSD. It even includes screenshots.</p>
-
-      <p>
-        <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html" shape="rect">
-        http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html</a>
-      </p>
-
-      <p>Comments, and contributions are, of course, welcome.</p>
-    <hr /><h2><a name="fbsd-nvdriver" href="#fbsd-nvdriver" id="fbsd-nvdriver">fbsd-nvdriver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://fbsd-nvdriver.sourceforge.net" title="http://fbsd-nvdriver.sourceforge.net"></a></td><td>
-	    URL: <a href="http://fbsd-nvdriver.sourceforge.net" title="">http://fbsd-nvdriver.sourceforge.net</a></td></tr></table><p>
-	Contact:
-          Erik
-
-          Greenwald
-         &lt;<a href="mailto:erik@floatingmind.com">erik@floatingmind.com</a>&gt;
-	<br />
-	Contact:
-          Joel
-
-          Willson
-         &lt;<a href="mailto:siigorny@linuxsveeden.borkborkbork">siigorny@linuxsveeden.borkborkbork</a>&gt;
-	</p>
-      <p>NVIDIA Corporation releases Linux drivers by using a
-      combination of binary object files and source (under a
-      constrictive license). The FreeBSD NVIDIA driver project aimed to
-      completely replace the source component of the driver using code
-      targeting FreeBSD 4.3 and released under the BSD license. The
-      binary module provided is supposedly the same module used on
-      Windows, BeOS, and OS/2, so it should be portable between
-      different i80x86 based OS's.</p>
-
-      <p>The project is currently on indefinite hold. Our contact at
-      NVIDIA seemed enthusiastic about the project, and was fairly
-      quick about returning email, but when we discovered issues that
-      prevented porting without changes to the binary component or
-      error codes we needed deciphered, Nick (the contact) said he'd
-      look into it and never got back. The first major problem was the
-      ioctl interface, the NVIDIA driver passes a pointer and depends
-      on the kernel side to copyout the right amount, where FreeBSD
-      expect the parameters to be correct and the copyout is performed
-      by the subsystem. This was worked around using Dave Rufinos
-      "ioctl tunnel" idea. After that, we found that X refused to load
-      and traced it down to an ioctl defined in the binary component
-      erroring. We cannot tell what that ioctl is, were told that we
-      could not sign an NDA for source to that component, and have been
-      waiting a month for Nick to "look into it". Therefore progress is
-      impossible (without breaking the license) and we believe that the
-      flaws make the driver unportable to any *nix other than
-      Linux.</p>
-    <hr /><h2><a name="Fibre-Channel-Support" href="#Fibre-Channel-Support" id="Fibre-Channel-Support">Fibre Channel Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.feral.com/isp.html" title="http://www.feral.com/isp.html"></a></td><td>
-	    URL: <a href="http://www.feral.com/isp.html" title="">http://www.feral.com/isp.html</a></td></tr></table><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>2 Gigabit support was integrated on 8/31/2001 (QLogic
-      2300/2312 cards). Because of the author's shrinking time
-      commitment for FreeBSD, the previously planned "next step" which
-      would have been more complete new CAM Transport integration is
-      now probably just the addition of an FC-IP adjunct (as this can
-      benefit many platforms simultaneously).</p>
-    <hr /><h2><a name="floppy-driver-overhaul" href="#floppy-driver-overhaul" id="floppy-driver-overhaul">floppy driver overhaul</a></h2><p>
-	Contact:
-          Joerg
-
-          Wunsch
-         &lt;<a href="mailto:j@uriah.heep.sax.de">j@uriah.heep.sax.de</a>&gt;
-	</p>
-      <p>As part of some ongoing development activity, the floppy
-      driver (fdc(4)) enjoyed some overhaul in the past which is part
-      of an ongoing process. Automatic density selection will come
-      next, something i meant to implement for years now. As part of
-      that, the entire density selection stuff has been rewritten. 2.88
-      MB floppies are on the wishlist as well, but I need a working
-      2.88 drive before attempting to implement that.</p>
-    <hr /><h2><a name="FreeBSD-core-secretary" href="#FreeBSD-core-secretary" id="FreeBSD-core-secretary">FreeBSD core-secretary</a></h2><p>
-	Contact:
-          Alan
-
-          Clegg
-         &lt;<a href="mailto:abc@FreeBSD.org">abc@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:core-secretary@FreeBSD.org">core-secretary@FreeBSD.org</a>&gt;
-	</p>
-      <p>The position of Core Secretary was filled by Alan Clegg
-      &lt;abc@FreeBSD.org&gt; The first core-secretary report should be
-      available the second week in September and will cover the issues
-      discussed by core during August 2001.</p>
-    <hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java/" title="http://www.FreeBSD.org/java/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java/" title="">http://www.FreeBSD.org/java/</a></td></tr></table><p>
-	Contact:
-          Greg
-
-          Lewis
-         &lt;<a href="mailto:glewis@eyesbeyond.com">glewis@eyesbeyond.com</a>&gt;
-	</p>
-      <p>Most of the work this month has focused on development of the
-      native JDK 1.3.1 patchset. The 3rd patchset is out and has been
-      accompanied with the creation of a FreeBSD "port". This has
-      allowed early adopters much easier access to the code and
-      naturally resulted in a number of bugs being found. Development
-      work has mostly focused on fixing these problems and the project
-      is now set to release fourth patchset over the weekend, which
-      should see the JDK in a reasonably usable state. One of the big
-      challenges left is producing a working HotSpot JVM, which looks
-      like it will require some heavy hacking.</p>
-
-      <p>We also welcome OpenBSD's Heikki Korpela to the porting team
-      :)</p>
-    <hr /><h2><a name="FreeBSD-PAM" href="#FreeBSD-PAM" id="FreeBSD-PAM">FreeBSD PAM</a></h2><p>
-	Contact:
-          Mark
-
-          Murray
-         &lt;<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>&gt;
-	</p>
-      <p>Development is continuing; pam_unix has gained the ability to
-      change passwords, login(1) has had PAM made compulsory (and is
-      going to have more PAM-capable features handed over to PAM).</p>
-    <hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><p>
-	Contact:
-          FreeBSD Release Engineer Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD release engineering process for FreeBSD 4.4
-      started to ramp up around August 1st when the "code slush" took
-      affect. During this time all commits to the RELENG_4 branch were
-      reviewed by re@FreeBSD.org (over 250 code snippets had to be
-      reviewed). After the first release candidate on August 15th, all
-      submissions were scrutinized under a more strict potential risk
-      vs benefit curve. The best way to help get involved with the
-      release engineering process is to simply follow the low volume
-      freebsd-qa mailing list, help out with the neverending supply of
-      PRs related to our installation tools (sysinstall), or to work on
-      a possible next-generation replacement for our installation
-      technology, such as the libh or OpenPackages projects.</p>
-
-      <p>Many companies donated equipment, network access, or paychecks
-      to finance these activities. Including Compaq, Yahoo!, Wind River
-      Systems, and many more.</p>
-    <hr /><h2><a name="FreeBSD/sparc64-port" href="#FreeBSD/sparc64-port" id="FreeBSD/sparc64-port">FreeBSD/sparc64 port</a></h2><p>
-	Contact:
-          Jake
-
-          Burkholder
-         &lt;<a href="mailto:jake@FreeBSD.org">jake@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Thomas
-
-          Moestl
-         &lt;<a href="mailto:tmm@FreeBSD.org">tmm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Robert
-
-          Drehmel
-         &lt;<a href="mailto:robert@FreeBSD.org">robert@FreeBSD.org</a>&gt;
-	</p>
-      <p>Sparc64 development is still continuing rapidly and we're
-      making some excellent progress. Of note, some problems with the
-      way the pmap module implements copy-on-write mappings have been
-      fixed and fork() now works as expected, support for signals has
-      been added, and the port has been updated for KSE in the perforce
-      repository. Thomas Moestl has begun work on pci bus support, and
-      a basic nexus bus for sparc64 has been written. The driver for
-      the Sun `Psycho' and `Sabre' UPA-to-PCI bridges and associated
-      code has been ported from NetBSD (the Sabre is the on-chip
-      version found in the UltraSparc IIi and IIe). PCI configuration,
-      I/O and memory space accesses do already work, as well as
-      interrupt assignment and delivery for devices attached directly
-      to the bridge, and the first PCI device drivers can attach and
-      seem to work mostly. Interrupt routing and busdma support still
-      need much work.</p>
-    <hr /><h2><a name="GNOME-Desktop-for-FreeBSD" href="#GNOME-Desktop-for-FreeBSD" id="GNOME-Desktop-for-FreeBSD">GNOME Desktop for FreeBSD</a></h2><p>
-	Contact:
-          Maxim
-
-          Sobolev
-         &lt;<a href="mailto:sobomax@FreeBSD.org">sobomax@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeBSD GNOME Team
-         &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>Getting GNOME Fifth-Toe metaport ready for 4.4-RELEASE was the
-      main focus of activity this month. In the process many components
-      were updated, many bugs were tracked down and solved, which
-      allowed to make this 97-component meta-package building and
-      working properly.</p>
-
-      <p>Next month the project will be focused on organizing work of
-      the FreeBSD GNOME Team as well as on attempts to increase amount
-      of people participating in the team (anybody who is willing to
-      participate is welcome to drop a note to gnome@FreeBSD with a
-      short explanation of how he/she could help).</p>
-    <hr /><h2><a name="ia64-Port" href="#ia64-Port" id="ia64-Port">ia64 Port</a></h2><p>
-	Contact:
-          Doug
-
-          Rabson
-         &lt;<a href="mailto:dfr@FreeBSD.org">dfr@FreeBSD.org</a>&gt;
-	</p>
-      <p>Current status is that the ia64 kernel builds and runs in a
-      simulator environment up to single user mode and has been tested
-      lightly in that environment. My current focus is on completing
-      the ia64 loader so that I can start to get kernels working on the
-      real hardware. The loader is coming along well and I expect to be
-      able to load kernels (but not necessary execute them) soon.</p>
-    <hr /><h2><a name="Improved-TCP-Initial-Sequence-Numbers" href="#Improved-TCP-Initial-Sequence-Numbers" id="Improved-TCP-Initial-Sequence-Numbers">Improved TCP Initial Sequence Numbers</a></h2><p>
-	Contact:
-          Mike
-
-          Silbersack
-         &lt;<a href="mailto:silby@silby.com">silby@silby.com</a>&gt;
-	</p>
-      <p>In mid March, 2001, Tim Newsham of Guardent identified an
-      attack possible against the initial sequence number generation
-      scheme of FreeBSD (and other OSes.) In order to guard against
-      this threat, a randomized sequence number generation scheme was
-      ported over from OpenBSD and included in 4.3-release.
-      Unfortunately, non-monotonic generation was found to cause major
-      problems with applications which initiate continuous, rapid
-      connections to a single host.</p>
-
-      <p>In order to restore proper operation under such circumstances
-      while still providing strong resistance against sequence number
-      prediction, FreeBSD 4.4 uses the algorithm specified in RFC 1948.
-      This algorithm hashes together host and port information with a
-      piece of secret data to generate a unique sequence number space
-      for each connection. As a result, outgoing initial sequence
-      numbers are again monotonic, but also unguessable by an
-      attacker.</p>
-    <hr /><h2><a name="Intel-Gigabit-Ethernet" href="#Intel-Gigabit-Ethernet" id="Intel-Gigabit-Ethernet">Intel Gigabit Ethernet</a></h2><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>No new status to report. This driver will be worked on again
-      soon and cleaned up to work better.</p>
-    <hr /><h2><a name="IP-Multicast-Routing-support" href="#IP-Multicast-Routing-support" id="IP-Multicast-Routing-support">IP Multicast Routing support</a></h2><p>
-	Contact:
-          Bill
-
-          Fenner
-         &lt;<a href="mailto:fenner@FreeBSD.org">fenner@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD's IP Multicast Routing support was recently updated in
-      several ways. One big change is that it's now able to be loaded
-      as a KLD instead of statically compiled into the kernel; this is
-      especially useful for experimentation or updating of an existing
-      system. It also now coexists nicely with the kernel IP
-      encapsulation infrastructure, so that multicast tunnels can
-      better coexist with MobileIP, certain IPSec tunnels and generic
-      IPv4-in-IPv4 tunnels.</p>
-    <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/"></a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-          Kazuo
-
-          Horikawa
-         &lt;<a href="mailto:horikawa@psinet.com">horikawa@psinet.com</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:man-jp@jp.FreeBSD.org">man-jp@jp.FreeBSD.org</a>&gt;
-	</p>
-      <p>Targeting 4.4-RELEASE, one team has been translating newly
-      MFC'ed section [125678] manpages. The other team has been
-      updating section 3 since May and one third (1/3) is finished. The
-      port ja-groff is updated to be groff-1.17.2 based, and now it has
-      the same functionality as base system does. The port ja-man is
-      updated to have the search capability under an architecture
-      subdirectory, as base system does. The doc/ja_JP.eucJP/man
-      hierarchy update (adding architecture subdirectories) is planned
-      after 4.4-RELEASE.</p>
-    <hr /><h2><a name="KAME" href="#KAME" id="KAME">KAME</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.kame.net/" title="http://www.kame.net/"></a></td><td>
-	    URL: <a href="http://www.kame.net/" title="">http://www.kame.net/</a></td></tr></table><p>
-	Contact:
-          Munechika
-
-          Sumikawa
-         &lt;<a href="mailto:sumikawa@FreeBSD.org">sumikawa@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KAME project (http://www.kame.net/) has merged its IPv6
-      and IPsec implementation as of July 2001 to FreeBSD CURRENT and
-      STABLE, in cooperation with some contributors of the project. The
-      latest code includes a number of bug fixes, has been fully tested
-      in FreeBSD STABLE, and will appear in FreeBSD 4.4 RELEASE. Thus,
-      the new RELEASE version will be quite stable in terms of IPv6 and
-      IPsec.</p>
-
-      <p>The project has assigned a talented guy to be responsible for
-      merge from KAME to FreeBSD, so future merge efforts will be
-      smoother.</p>
-    <hr /><h2><a name="KSE" href="#KSE" id="KSE">KSE</a></h2><p>
-	Contact:
-          Julian
-
-          Elischer
-         &lt;<a href="mailto:julian@elischer.org">julian@elischer.org</a>&gt;
-	<br />
-	Contact:
-          Peter
-
-          Wemm
-         &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Matt
-
-          Dillon
-         &lt;<a href="mailto:dillon@FreeBSD.org">dillon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work in adding supporting infrastructure to the kernel for KSE
-      threading support has reached "milestone 2".</p>
-
-      <p>Milestone 2 is where the kernel source consistently refers to
-      its resources in terms of per-thread and per-process resources,
-      in the way that it will need to when there are &gt; 1 threads per
-      process, but the LOGICAL changes to such things as the scheduler,
-      and fork and exit, have not yet been made to allow more than one
-      thread to be created. (nor have new threading syscalls been added
-      yet). This is an important milestone as it represents the last
-      point where the kernel has only "mechanical" changes. To go
-      further we must start adding new algorithms and functions.</p>
-
-      <p>The kernel for milestone 2 is reliable and has no noticeable
-      performance degradations when compared to a matching -current
-      kernel. (the differences are less than the margin of error, so
-      that sometimes the new kernel actually fractionally beats the
-      unaltered kernel).</p>
-
-      <p>We hope that by the time this is published, the KSE patches
-      will have been committed. The Major effect for most developers
-      will be only that the device driver interface requires a 'thread'
-      pointer instead of a Proc pointer in the open, close and ioctl
-      entrypoints.</p>
-
-      <p>I'm sure there will be small teething problems but we are not
-      expecting great problems at the commit.</p>
-    <hr /><h2><a name="libh-Project" href="#libh-Project" id="libh-Project">libh Project</a></h2><p>
-	Contact:
-          Alexander
-
-          Langer
-         &lt;<a href="mailto:alex@FreeBSD.org">alex@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Nathan
-
-          Ahistrom
-         &lt;<a href="mailto:nra@FreeBSD.org">nra@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have access to the libh CVS repo again and am testing a new,
-      OBJDIR capable build structure at the moment. Done that, I'm
-      going to continue testing the package library and implement the
-      missing functionality. Currently, import of libh into the base
-      system is under discussion (arch mailinglist). Now that
-      5.0-RELEASE has been shifted, I want 5.0 ship with a libh
-      installer and package system. We can really need people who are
-      good in C++, are able to understand what the current
-      implementation does and also feel that working on libh is fun and
-      thus are willing to help.</p>
-    <hr /><h2><a name="LOMAC" href="#LOMAC" id="LOMAC">LOMAC</a></h2><p>
-	Contact:
-          Brian
-
-          Feldman
-         &lt;<a href="mailto:green@FreeBSD.org">green@FreeBSD.org</a>&gt;
-	</p>
-      <p>The port of LOMAC to FreeBSD is progressing well, and already
-      has a very high level of stability (no known outstanding bugs!).
-      Aspects which have already been implemented include a stacking
-      filesystem overlay with fully-functional access controls (for
-      files and directories) based on path names, access controls for
-      sending signals, and file-backed-memory revocation for
-      processes.</p>
-    <hr /><h2><a name="Mbuf-SMPng-allocator" href="#Mbuf-SMPng-allocator" id="Mbuf-SMPng-allocator">Mbuf SMPng allocator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" title="http://people.FreeBSD.org/~bmilekic/code/mb_slab/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmilekic/code/mb_slab/" title="">http://people.FreeBSD.org/~bmilekic/code/mb_slab/</a></td></tr></table><p>
-	Contact:
-          Bosko
-
-          Milekic
-         &lt;<a href="mailto:bmilekic@FreeBSD.org">bmilekic@FreeBSD.org</a>&gt;
-	</p>
-      <p>The allocator appears to be stable. Mbtypes statistics have
-      been re-activated thanks, in part, to Jiangyi Liu
-      &lt;jyliu@163.net&gt; although the diff has not yet been
-      committed (I'm just in the process of cleaning it up a little and
-      final testing). More work to come: cleanups, follow TODO from the
-      original commit, and perhaps an eventual generalization of the
-      allocator for various network-related allocations (in a more
-      distant future).</p>
-    <hr /><h2><a name="Netgraph-ATM" href="#Netgraph-ATM" id="Netgraph-ATM">Netgraph ATM</a></h2><p>
-	Contact:
-          Hartmut
-
-          Brandt
-         &lt;<a href="mailto:brandt@fokus.gmd.de">brandt@fokus.gmd.de</a>&gt;
-	</p>
-      <p>The ATM stack has been tested with a number of FreeBSD
-      machines and a Marconi ATM switch and seems to be quite stable
-      running CLIP. Multi port support for the native ATM API has been
-      implemented but needs some testing.</p>
-    <hr /><h2><a name="network-device-cloning" href="#network-device-cloning" id="network-device-cloning">network device cloning</a></h2><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for cloning vlan devices via ifconfig has been
-      committed to -current and will be MFC'd after further testing.
-      Additionally, Maksim Yevmenkin submitted code to allow cloning of
-      tap and vmnet devices on devfs systems. Code for faith and stf
-      should be committed shortly.</p>
-    <hr /><h2><a name="Network-device-nodes" href="#Network-device-nodes" id="Network-device-nodes">Network device nodes</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently, all network devices (fxp0, lo0, etc) exist in their
-      own namespace, and are accessed through a socket interface. This
-      project creates device nodes in /dev for network devices, and
-      allows control and access in that fashion.</p>
-
-      <p>This is experimental work, and suggestions for APIs and
-      functionality are strongly encouraged and welcomed. In is not
-      clear whether it will be possible (or desirable) to provide the
-      exact same set of operations that can be done through the socket
-      interface.</p>
-
-      <p>Benefits of approach include the fact that a kqueue filter can
-      be attached to a network device for monitoring purposes. Initial
-      code exists to send a kq event whenever the network link status
-      changes. Other benefits may include better access control by
-      using filesystem ACLs to control access to the device.</p>
-    <hr /><h2><a name="Network-SMP-locking" href="#Network-SMP-locking" id="Network-SMP-locking">Network SMP locking</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>For 5.0, the goal is for the network stack to run without the
-      Giant lock. Initial development in this area may focus on
-      partitioning the code and data structures into distinct areas of
-      responsibilities. A first pass of locking may involve using a
-      several smaller mini-giant code locks in order to reduce the
-      problem to a manageable size.</p>
-
-      <p>Progress for this month includes the creation of a perforce
-      repository to officially track the locking changes, and the
-      initial submission of locks for the &amp;ifnet list. Some code
-      cleanup has also been done to the main tree in order to better
-      support future locking additions.</p>
-    <hr /><h2><a name="OLDCARD-improvements" href="#OLDCARD-improvements" id="OLDCARD-improvements">OLDCARD improvements</a></h2><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The OLDCARD improvements have been completed, except for a few
-      edge cases for older laptops with CL-PD6729/30 chips and some pci
-      bios issues. Some minor work will continue, but after 4.4R is
-      released, only a few remaining bugs will be fixed before the
-      author moves on to greener fields of NEWCARD development.</p>
-    <hr /><h2><a name="Porting-ppp-to-hurd-&amp;-linux" href="#Porting-ppp-to-hurd-&amp;-linux" id="Porting-ppp-to-hurd-&amp;-linux">Porting ppp to hurd &amp; linux</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>Status is unchanged since last month. Patches have been
-      submitted to get ppp working under HURD, and mostly under Linux.
-      There are GPL copyright problems that need to be addressed. Many
-      conflicts are expected after the commit of IPv6 support in
-      ppp.</p>
-    <hr /><h2><a name="PPP-IPv6-Support" href="#PPP-IPv6-Support" id="PPP-IPv6-Support">PPP IPv6 Support</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>The software has been committed to -current and seems
-      functional. Outstanding issues include dealing with IPV6CP events
-      (linkup &amp; linkdown scripts) and allocating site-local and
-      global addresses (currently, ``iface add'' is the only way to
-      actually use the link).</p>
-    <hr /><h2><a name="pppoa" href="#pppoa" id="pppoa">pppoa</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>I looked at bringing PPPoA into the base system, but could not
-      because of an overly restrictive distribution license on the
-      Alcatel Speedtouch modem firmware. It has been committed as a
-      port instead and is running live at a FreeBSD Services client
-      site.</p>
-    <hr /><h2><a name="pppoed" href="#pppoed" id="pppoed">pppoed</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>Making pppoed function in a production environment. All known
-      problems have been fixed and committed.</p>
-    <hr /><h2><a name="PRFW---hooks-for-the-FreeBSD-kernel" href="#PRFW---hooks-for-the-FreeBSD-kernel" id="PRFW---hooks-for-the-FreeBSD-kernel">PRFW - hooks for the FreeBSD kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freesoftware.fsf.org/jailuser" title="http://www.freesoftware.fsf.org/jailuser"></a></td><td>
-	    URL: <a href="http://www.freesoftware.fsf.org/jailuser" title="">http://www.freesoftware.fsf.org/jailuser</a></td></tr></table><p>
-	Contact:
-          Evan
-
-          Sarmiento
-         &lt;<a href="mailto:ems@open-root.org">ems@open-root.org</a>&gt;
-	</p>
-      <p>PRFW is a set of hooks for the FreeBSD kernel. It allows users
-      to insert code into system calls, for such purposes as creating
-      extended security features. Last week, PRFW reached 0.1.0, with
-      many bugfixes and cleaning. I urge anyone who is interested to
-      please visit the site, join the mailing list. Also take a peek at
-      lsm.immunix.org, the Linux hooks. It will be a good contrast.</p>
-    <hr /><h2><a name="Problem-Reports" href="#Problem-Reports" id="Problem-Reports">Problem Reports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://phk.freebsd.dk/Gnats/" title="http://phk.freebsd.dk/Gnats/"></a></td><td>
-	    URL: <a href="http://phk.freebsd.dk/Gnats/" title="">http://phk.freebsd.dk/Gnats/</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are making some progress, we are now down to 2170 open PR's
-      down from an all time high of 3270 just 3 months ago. The aim is
-      still to get rid of all the dead-wood in the PR database so only
-      relevant PRs in the database. A big thanks from me to the people
-      who have made this happen!</p>
-    <hr /><h2><a name="RAIDframe-for-FreeBSD" href="#RAIDframe-for-FreeBSD" id="RAIDframe-for-FreeBSD">RAIDframe for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~scottl/rf" title="http://people.FreeBSD.org/~scottl/rf"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~scottl/rf" title="">http://people.FreeBSD.org/~scottl/rf</a></td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>After two months of little progress, RAIDframe work is gearing
-      up again. The port to -stable has some known bugs but is fairly
-      stable. The port to -current was recently completed and patches
-      will be released soon. RAIDframe is a multi-platform RAID
-      subsystem designed at CMU. This is a port of the NetBSD version
-      by Greg Oster.</p>
-    <hr /><h2><a name="RELNOTESng" href="#RELNOTESng" id="RELNOTESng">RELNOTESng</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmah/relnotes/" title="http://people.FreeBSD.org/~bmah/relnotes/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmah/relnotes/" title="">http://people.FreeBSD.org/~bmah/relnotes/</a></td></tr></table><p>
-	Contact:
-          Bruce
-
-          Mah
-         &lt;<a href="mailto:bmah@FreeBSD.org">bmah@FreeBSD.org</a>&gt;
-	</p>
-      <p>RELNOTESng, the DocBook-ified set of release documentation
-      files, has been merged to the RELENG_4 branch. 4.4-RELEASE will
-      be the first release of FreeBSD with the new-style release notes,
-      hardware list, etc. Some of these documents are being translated
-      by the Japanese and Russian translation teams.</p>
-
-      <p>Snapshots of RELNOTESng for CURRENT and 4-STABLE in HTML,
-      text, and PDF are available at the above URL and are updated
-      irregularly but frequently. Dima Dorfman &lt;dd@FreeBSD.org&gt;
-      and Nik Clayton &lt;nik@FreeBSD.org&gt; have been working to have
-      automatically-generated snapshots on the main FreeBSD web
-      site.</p>
-
-      <p>On my TODO list: 1) Resynchronize the FreeBSD installation
-      document with the installation chapter in the Handbook. 2) Update
-      the hardware lists (with particular emphasis on PCCARD and USB
-      devices). 3) Update the infrastructure to allow the
-      architecture-dependent parts of RELNOTESng to scale to more
-      hardware platforms.</p>
-    <hr /><h2><a name="SCSI-Tape-Support" href="#SCSI-Tape-Support" id="SCSI-Tape-Support">SCSI Tape Support</a></h2><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>A major update to error handling was done on 8/28/2001 which
-      should correct most of the EOM detection problems that have been
-      around for a while. There are several things to fix. The
-      principle thing to fix next is the establishment of a loader(8)
-      mediated device quirks method.</p>
-    <hr /><h2><a name="SMPng" href="#SMPng" id="SMPng">SMPng</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~jasone/smp/" title="http://www.FreeBSD.org/~jasone/smp/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jasone/smp/" title="">http://www.FreeBSD.org/~jasone/smp/</a></td></tr></table><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Peter
-
-          Wemm
-         &lt;<a href="mailto:wemm@FreeBSD.org">wemm@FreeBSD.org</a>&gt;
-	</p>
-      <p>Updates to things from last month:
-      <ul>
-        <li>The ast() fixes were committed last month.</li>
-
-        <li>The work on the preemptive kernel is stalled for the time
-        being. It is still unstable on Alpha and SMP systems.</li>
-      </ul>
-      </p>
-
-      <p>New stuff since last month:
-      <ul>
-        <li>sx locks now support upgrades and downgrades.</li>
-
-        <li>Witness now supports lock upgrades and downgrades.</li>
-
-        <li>Jason Evans has committed a semaphore implementation.</li>
-
-        <li>Matt Dillon has pushed Giant down into all of the
-        syscalls.</li>
-
-        <li>John Baldwin has been working on proc locking in a p4
-        'jhb_proc' branch.</li>
-
-        <li>John is also currently working on making the ktrace code
-        use a work thread to asynchronously write trace data out to the
-        trace file. This will make ktrace safe almost completely MP
-        safe with the exception that a few ktrace events need Giant in
-        order to call malloc(9) and that ktrgenio() is still
-        synchronous. Specifically, however, ktrpsig(), ktrsysret(), and
-        ktrcsw() no longer need Giant.</li>
-
-        <li>Jonathan Lemon has started work on locking the network
-        stack in a p4 'netlock' branch.</li>
-      </ul>
-      </p>
-    <hr /><h2><a name="sppp(4)-merge" href="#sppp(4)-merge" id="sppp(4)-merge">sppp(4) merge</a></h2><p>
-	Contact:
-          Joerg
-
-          Wunsch
-         &lt;<a href="mailto:j@uriah.heep.sax.de">j@uriah.heep.sax.de</a>&gt;
-	</p>
-      <p>sppp(4) should be merged with the ISDN4BSD offspring variant.
-      This will merge some features and bugfixes from the i4b branch
-      (like VJ compression), and eventually end up in a single sppp(4)
-      in the tree. While being at that, incorporating many changes and
-      bugfixes from NetBSD is considered as well.</p>
-    <hr /><h2><a name="SYN-cache-implementation-for-FreeBSD" href="#SYN-cache-implementation-for-FreeBSD" id="SYN-cache-implementation-for-FreeBSD">SYN cache implementation for FreeBSD</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The syncache implementation is completed, and currently under
-      testing and review. The code should be committed to -current in
-      the near future, and a patchset for -stable made available.</p>
-    <hr /><h2><a name="TrustedBSD" href="#TrustedBSD" id="TrustedBSD">TrustedBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/"></a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD project continues to move ahead, with progress
-      made in the ACL, Capability, and MAC implementations. In
-      addition, support from DARPA is permitting new work to improve
-      the extended attribute code, improve security abstractions, and
-      work on security documentation. Due to the push-back of the
-      FreeBSD 5.0 release, it should now be possible to include a
-      complete MAC implementation in that release. Specific status
-      reports appear for components where substantial progress is being
-      made.</p>
-    <hr /><h2><a name="TrustedBSD-Capabilities" href="#TrustedBSD-Capabilities" id="TrustedBSD-Capabilities">TrustedBSD Capabilities</a></h2><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Thomas
-
-          Moestl
-         &lt;<a href="mailto:tmm@FreeBSD.org">tmm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>Capabilities support is currently being committed to the base
-      FreeBSD tree--userland libraries are now fully committed, and
-      kernel infrastructure is being integrated.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2001-09.html b/website/content/en/status/report-2001-09.html
deleted file mode 100644
index 0ceb55d3c3..0000000000
--- a/website/content/en/status/report-2001-09.html
+++ /dev/null
@@ -1,818 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>In the month of September, the FreeBSD Project continued its
-    investment in long-term projects, including continuing work on a
-    fine-grained SMP implementation, support for Kernel Schedulable
-    Entities (KSE) supporting highly efficient threading, and
-    broadening support for modern hardware platforms, including Intel's
-    new IA64 architecture, UltraSparc, and PowerPC. Additional focus
-    was placed on the release process, including work on the release
-    notes infrastructure, support for DVD releases, and work on a
-    binary updating tool.</p><p>Due to the delay in getting the September report out the door,
-    the November status report will also cover October. During the
-    month of November, we look forward to BSDCon Europe, the first such
-    event outside the continental United States. The USENIX conference
-    paper submission deadlines are also in November, and FreeBSD users
-    and developers are encouraged to submit to the general and FREENIX
-    tracks. Please see www.usenix.org for more information.</p><hr /><ul><li><a href="#binup">binup</a></li><li><a href="#Compressed-TCP-state">Compressed TCP state</a></li><li><a href="#Fibre-Channel-Support">Fibre Channel Support</a></li><li><a href="#FreeBSD-C99/POSIX-Conformance-Project">FreeBSD C99/POSIX Conformance Project</a></li><li><a href="#FreeBSD-DVD-generation">FreeBSD DVD generation</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#FreeBSD-libh-Project">FreeBSD libh Project</a></li><li><a href="#FreeBSD/sparc64-port">FreeBSD/sparc64 port</a></li><li><a href="#Improving-FreeBSD-startup-scripts">Improving FreeBSD startup scripts</a></li><li><a href="#Intel-Gigabit-driver">Intel Gigabit driver</a></li><li><a href="#Intel-Gigabit-Ethernet">Intel Gigabit Ethernet</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KSE">KSE</a></li><li><a href="#Multiple-console-support">Multiple console support</a></li><li><a href="#Netgraph-ATM">Netgraph ATM</a></li><li><a href="#Network-console">Network console</a></li><li><a href="#Network-device-nodes">Network device nodes</a></li><li><a href="#Network-SMP-locking">Network SMP locking</a></li><li><a href="#New-Mount(2)-API">New Mount(2) API</a></li><li><a href="#Porting-ppp-to-hurd-&amp;-linux">Porting ppp to hurd &amp; linux</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#PPP-IPv6-Support">PPP IPv6 Support</a></li><li><a href="#PRFW">PRFW</a></li><li><a href="#RELNOTESng">RELNOTESng</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#SYN-cache-implementation-for-FreeBSD">SYN cache implementation for FreeBSD</a></li><li><a href="#TIRPC">TIRPC</a></li></ul><hr /><h2><a name="binup" href="#binup" id="binup">binup</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/updater.html" title="http://www.FreeBSD.org/projects/updater.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/updater.html" title="">http://www.FreeBSD.org/projects/updater.html</a></td></tr></table><p>
-	Contact:
-          Eric
-
-          Melville
-         &lt;<a href="mailto:eric@FreeBSD.org">eric@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project has gained a mailing list,
-      freebsd-binup@FreeBSD.org - and the source tree has been moved
-      into the projects/ directory in the FreeBSD CVS repository.
-      Current work is focusing on extending the FreeBSD package
-      framework, and the client library should be rewritten and
-      completed by the end of the year.</p>
-
-      <p>TODO: make the projects/ hierarchy into a cvsup distribution
-      and add it to cvs-all. Then update distrib.self.</p>
-    <hr /><h2><a name="Compressed-TCP-state" href="#Compressed-TCP-state" id="Compressed-TCP-state">Compressed TCP state</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Development on this project has been slowed, pending the
-      commit of the syncache code, as this builds on part of that
-      work.</p>
-    <hr /><h2><a name="Fibre-Channel-Support" href="#Fibre-Channel-Support" id="Fibre-Channel-Support">Fibre Channel Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.feral.com/isp.html" title="http://www.feral.com/isp.html"></a></td><td>
-	    URL: <a href="http://www.feral.com/isp.html" title="">http://www.feral.com/isp.html</a></td></tr></table><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>Bug fixing and move to -STABLE of 2Gb support.</p>
-    <hr /><h2><a name="FreeBSD-C99/POSIX-Conformance-Project" href="#FreeBSD-C99/POSIX-Conformance-Project" id="FreeBSD-C99/POSIX-Conformance-Project">FreeBSD C99/POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mike/c99/" title="http://people.FreeBSD.org/~mike/c99/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mike/c99/" title="">http://people.FreeBSD.org/~mike/c99/</a></td></tr></table><p>
-	Contact:
-          Mike
-
-          Barcroft
-         &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeBSD-Standards Mailing List
-         &lt;<a href="mailto:freebsd-standards@bostonradio.org">freebsd-standards@bostonradio.org</a>&gt;
-	</p>
-      <p>The FreeBSD C99/POSIX Conformance Project aims to implement
-      all requirements of the C99 Standard and the latest 1003.1-200x
-      POSIX draft (currently Draft 7). In cases where aspects of the
-      standard cannot be followed, those aspects will be documented in
-      the c99(7) or posix(7) manuals. It is also an aim of this project
-      to implement regression tests to ensure correctness whenever
-      possible.</p>
-
-      <p>Patches that implement the &lt;stdint.h&gt; and
-      &lt;inttypes.h&gt; headers, and modifications to printf(3) have
-      been developed and will be committed shortly. They will allow us
-      to use some of the new types C99 introduces, such as intmax_t and
-      the printf(3) conversion specifier "%j".</p>
-    <hr /><h2><a name="FreeBSD-DVD-generation" href="#FreeBSD-DVD-generation" id="FreeBSD-DVD-generation">FreeBSD DVD generation</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>A two disc set has been mastered and sent for pressing. There
-      are a few surprises with this release - details will be given in
-      the official announcement (at BSDConEurope).</p>
-    <hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java/" title="http://www.FreeBSD.org/java/">Official FreeBSD Java Project site.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java/" title="Official FreeBSD Java Project site.">http://www.FreeBSD.org/java/</a></td></tr></table><p>
-	Contact:
-          Greg
-
-          Lewis
-         &lt;<a href="mailto:glewis@eyesbeyond.com">glewis@eyesbeyond.com</a>&gt;
-	</p>
-      <p>The project has moved forward on JDK 1.3.1 development this
-      month, with the release of two more patchsets. The team is
-      reasonably confident that the latest patchset is a stable release
-      of the core JDK 1.3.1 tools and classes, when the default "green"
-      threads subsystem is used. This is mostly thanks to hard work by
-      Fuyuhiko Maruyama to stabilize and fix the code. Bill Huey has
-      also been progressing with his work on the "native" threads
-      subsystem, although this hasn't yet reached the stability of
-      "green" threads. Another (arguably the) major highlight of the
-      latest patchset was the integration of NetBSD support by Scott
-      Bartram and Alistair Crooks (the latter of NetBSD packages fame).
-      Hopefully OpenBSD support will follow, making it truly a united
-      BSD Java Project.</p>
-    <hr /><h2><a name="FreeBSD-libh-Project" href="#FreeBSD-libh-Project" id="FreeBSD-libh-Project">FreeBSD libh Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/libh.html" title="http://www.FreeBSD.org/projects/libh.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/libh.html" title="">http://www.FreeBSD.org/projects/libh.html</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Langer
-         &lt;<a href="mailto:alex@FreeBSD.org">alex@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Nathan
-
-          Ahlstrom
-         &lt;<a href="mailto:nra@FreeBSD.org">nra@FreeBSD.org</a>&gt;
-	</p>
-      <p>The build process is now creating four different versions of
-      the libs, which include support for TVision, Qt, both or none. I
-      created some first packages from existing ports and installed
-      those libh packages on my system only using libh's tools,
-      including registering all the files in the package database,
-      recording their checksums etc. Patches to the disk editor have
-      been submitted, which include functionality to write the changes
-      in the fdisk part and initial support for a disk label editor.
-      We'll soon have a new committer.</p>
-    <hr /><h2><a name="FreeBSD/sparc64-port" href="#FreeBSD/sparc64-port" id="FreeBSD/sparc64-port">FreeBSD/sparc64 port</a></h2><p>
-	Contact:
-          Jake
-
-          Burkholder
-         &lt;<a href="mailto:jake@FreeBSD.org">jake@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Thomas
-
-          Moestl
-         &lt;<a href="mailto:tmm@FreeBSD.org">tmm@FreeBSD.org</a>&gt;
-	</p>
-      <p>I am pleased to announce that as of 1 AM Friday October 19th,
-      the sparc64 port boots to single user mode. A few binaries from
-      the base system have been built and verified to work properly.
-      Much of this work is still in review for commit, but will be
-      integrated into the cvs tree as soon as possible. EBus support
-      has been ported from NetBSD, and ISA support has been written.
-      The PCI host bridge code has stabilized, and busdma seems to work
-      correctly now. The sio driver has had EBus support added, and the
-      ATA driver has been modified so that it works on big-endian
-      systems and uses the busdma API. With these changes, a root file
-      system can now be successfully mounted from ATA disks on sparc64,
-      even in DMA mode. The gem driver, which supports Sun GEM and ERI
-      and Apple GMAC and GMAC2 ethernet adaptor, has been ported from
-      NetBSD but has not yet had sufficient testing.</p>
-    <hr /><h2><a name="Improving-FreeBSD-startup-scripts" href="#Improving-FreeBSD-startup-scripts" id="Improving-FreeBSD-startup-scripts">Improving FreeBSD startup scripts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://groups.yahoo.com/group/FreeBSD-rc/" title="http://groups.yahoo.com/group/FreeBSD-rc/">Improving FreeBSD startup scripts</a></td><td>
-	    URL: <a href="http://groups.yahoo.com/group/FreeBSD-rc/" title="Improving FreeBSD startup scripts">http://groups.yahoo.com/group/FreeBSD-rc/</a></td></tr><tr><td><a href="http://www.cs.rmit.edu.au/~lukem/bibliography.html" title="http://www.cs.rmit.edu.au/~lukem/bibliography.html">Luke Mewburn's papers</a></td><td>
-	    URL: <a href="http://www.cs.rmit.edu.au/~lukem/bibliography.html" title="Luke Mewburn's papers">http://www.cs.rmit.edu.au/~lukem/bibliography.html</a></td></tr><tr><td><a href="http://www.netbsd.org/Documentation/rc/" title="http://www.netbsd.org/Documentation/rc/">NetBSD Initialization and Services Control</a></td><td>
-	    URL: <a href="http://www.netbsd.org/Documentation/rc/" title="NetBSD Initialization and Services Control">http://www.netbsd.org/Documentation/rc/</a></td></tr></table><p>
-	Contact:
-          Doug
-
-          Barton
-         &lt;<a href="mailto:DougB@FreeBSD.org">DougB@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Gordon
-
-          Tetlow
-         &lt;<a href="mailto:gordont@gnf.org">gordont@gnf.org</a>&gt;
-	</p>
-      <p>This group is for discussion about the startup scripts in
-      FreeBSD, primarily the scripts in /etc/rc*. Primary focus will be
-      on improvements and importation of NetBSD's excellent work on
-      this topic.</p>
-
-      <p>Alright folks, I finally got off my butt last night and put
-      together a roadmap for the migration to the new rc.d init scripts
-      that were imported from NetBSD a long time ago and just sat in
-      the tree.</p>
-
-      <p>M1 (Patch included)
-      <br clear="none" />
-
-      Setup infrastructure
-      <br clear="none" />
-
-      Make rcorder compile
-      <br clear="none" />
-
-      Hook rc.subr into the distribution (and mergemaster)
-      <br clear="none" />
-
-      Hook rcorder into the world
-      <br clear="none" />
-
-      Add toggle in rc.conf to switch between rc_ng and current boot
-      scripts</p>
-
-      <p>M2
-      <br clear="none" />
-
-      Get FreeBSD to boot with the new boot scripts
-      <br clear="none" />
-
-      Rewrite the /etc/rc.d scripts to work with FreeBSD</p>
-
-      <p>M3
-      <br clear="none" />
-
-      Add some FreeBSD specific support into rc.subr</p>
-
-      <p>M4
-      <br clear="none" />
-
-      Add true dependency checking to the infrastructure so that
-      starting nfsd will start mountd and rpcbind
-      <br clear="none" />
-
-      add support into rc.subr
-      <br clear="none" />
-
-      Add dependencies into rc.d scripts</p>
-
-      <p>I'd like a couple of people to take a look at this and then
-      I'll submit a pr for it if there aren't too many objections. I'm
-      expecting M2 to run into quite a bikeshed, but hey, I got my nice
-      shiny asbestos back from the cleaners.</p>
-    <hr /><h2><a name="Intel-Gigabit-driver" href="#Intel-Gigabit-driver" id="Intel-Gigabit-driver">Intel Gigabit driver</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The gx driver has finally been committed to the tree. The
-      driver provides support for the Intel PRO/1000 cards, both fiber
-      and copper variants. The driver supports VLAN tagging and TCP/IP
-      checksum offload.</p>
-    <hr /><h2><a name="Intel-Gigabit-Ethernet" href="#Intel-Gigabit-Ethernet" id="Intel-Gigabit-Ethernet">Intel Gigabit Ethernet</a></h2><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>Quite a lot of cleanup of this driver. Bug fixes and some
-      performance enhancements. However, this driver is likely to be
-      removed shortly and replaced by one from Intel itself.</p>
-    <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/"></a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:man-jp@jp.FreeBSD.org">man-jp@jp.FreeBSD.org</a>&gt;
-	</p>
-      <p>We have finished updating section [125678] manpages to
-      4.4-RELEASE based, 1 week after 4.4-RELEASE is announced. To
-      finish this update, OKAZAKI Tetsurou has imported Ex/Rv macro
-      support on ja-groff-1.17.2_1. SUZUKI Koichi did most Ex/Rv
-      changes on Japanese manpages. He also find some issues of these
-      macro usage on some original manpages and filed a PR. For
-      post-4.4-RELEASE, now we target 4.5-RELEASE. Section 3 update is
-      also in progress.</p>
-    <hr /><h2><a name="KSE" href="#KSE" id="KSE">KSE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~jasone/kse/" title="http://www.FreeBSD.org/~jasone/kse/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jasone/kse/" title="">http://www.FreeBSD.org/~jasone/kse/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/~julian" title="http://www.FreeBSD.org/~julian"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~julian" title="">http://www.FreeBSD.org/~julian</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the last month, not a lot has happened other than settling
-      in of the big August commit. Largely due to me having a sudden
-      increased workload at work, and a need for increased time to be
-      spent elsewhere. However some design work has proceeded. The API
-      has firmed up somewhat and several people have been reading
-      through what has been done already in order to be able to help in
-      the next phase.</p>
-
-      <p>Milestone 3 will be to have the ability to generate and remove
-      multiple threads/KSEs per process. Milestone 3 will NOT require
-      that doing so will be safe. (especially in SMP systems), i.e.
-      locking issues will not be fully addressed, so while some testing
-      will be possible, it will not be possible to actually run in this
-      mode with any load.</p>
-
-      <p>This will require allocators and destructors for the new
-      structures. Creation of the syscalls. Generation of an accurate
-      written API for the userland crew. Writing of the upcall launch
-      code. Production of a userland test program (not a full thread
-      scheduler). Resolution of some of the more glaring
-      incompatibilities (e.g. the scheduler) in a backwards compatible
-      manner. (i.e. if there are no multi threaded processes on a
-      system it should behave the same as now (and be as
-      reliable)).</p>
-
-      <p>Criteria for knowing when we have reached Milestone 3 is the
-      ability for a simple process on an unloaded system to perform a
-      series of blocking syscalls reliably. e.g. open 2 sockets, and
-      send data on one, after having done a read on another, and then
-      'respond' in like manner..</p>
-    <hr /><h2><a name="Multiple-console-support" href="#Multiple-console-support" id="Multiple-console-support">Multiple console support</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently, a single device may act as a console at any time,
-      which requires the user to choose the console device at boot
-      time. With the upcoming network console support, it is desirable
-      to allow multiple console devices which behave identically, and
-      to alter consoles while the kernel is running.</p>
-
-      <p>The code is completed, and needs some final polishing to clean
-      up the rough edges. Console output can be sent to both syscons
-      and sio, (as well as the network) and when in ddb, input can be
-      taken from any input source. A small control program allows
-      adding and removing consoles on the fly.</p>
-    <hr /><h2><a name="Netgraph-ATM" href="#Netgraph-ATM" id="Netgraph-ATM">Netgraph ATM</a></h2><p>
-	Contact:
-          Harti
-
-          Brandt
-         &lt;<a href="mailto:brandt@fokus.gmd.de">brandt@fokus.gmd.de</a>&gt;
-	</p>
-      <p>ATM-Forum LAN-emulation version 2.0 without support for QoS
-      has been implemented and tested. The ILMI daemon has been
-      modularized into a general mini-SNMP daemon, an ILMI module and a
-      not yet finished IPOA (IP over ATM) module.</p>
-    <hr /><h2><a name="Network-console" href="#Network-console" id="Network-console">Network console</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project's goal is to add low level network functionality
-      to FreeBSD. The initial target is to make a network console
-      available for remote debugging with ddb or gdb. A secondary
-      target is to utilize the code to perform network crash dumps. The
-      design assumes that the network card and driver are working, but
-      does not rely on other parts of the kernel.</p>
-
-      <p>Initial development has been fairly rapid, and a minimal
-      TCP/IP stack has been written. It is currently possible to telnet
-      to a machine which is at the ddb&gt; prompt and interact with the
-      debugger.</p>
-    <hr /><h2><a name="Network-device-nodes" href="#Network-device-nodes" id="Network-device-nodes">Network device nodes</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Network devices now support aliases in the form of /dev/netN,
-      where N is the interface index. Devices may be wired down to a
-      specific index number by entries in /boot/device.hints of
-      either:</p>
-
-      <p>hint.net.&lt;ifindex&gt;.dev="devname"
-      hint.net.&lt;ifindex&gt;.ether="ethernet address"</p>
-
-      <p>Additionally, ifconfig has been updated so that it will accept
-      the alias name when configuring a device.</p>
-    <hr /><h2><a name="Network-SMP-locking" href="#Network-SMP-locking" id="Network-SMP-locking">Network SMP locking</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Not much progress has been made this month, with other
-      projects occupying most of my time. However, reviewing all the
-      code and data structures had a side benefit; a hash table for
-      inet addresses has been added. This will significantly speed up
-      interface address lookups in the case where there are a larger
-      number of interface aliases.</p>
-    <hr /><h2><a name="New-Mount(2)-API" href="#New-Mount(2)-API" id="New-Mount(2)-API">New Mount(2) API</a></h2><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Maxime
-
-          Henrion
-         &lt;<a href="mailto:mux@qualys.com">mux@qualys.com</a>&gt;
-	</p>
-      <p>We've made some good progress now, and the new nmount(2)
-      syscall is nearly finished. There is still some work to do to
-      have a working kernel_mount() and to convert all filesystems to
-      use this new API for their VFS_MOUNT() functions.</p>
-    <hr /><h2><a name="Porting-ppp-to-hurd-&amp;-linux" href="#Porting-ppp-to-hurd-&amp;-linux" id="Porting-ppp-to-hurd-&amp;-linux">Porting ppp to hurd &amp; linux</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>Status is unchanged since last month. Patches have been
-      submitted to get ppp working under HURD, and mostly under Linux.
-      There are GPL copyright problems that need to be addressed. Many
-      conflicts are expected after the commit of IPv6 support in
-      ppp.</p>
-    <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-          Benno
-
-          Rice
-         &lt;<a href="mailto:benno@FreeBSD.org">benno@FreeBSD.org</a>&gt;
-	</p>
-      <p>There have been a few major successes in the PowerPC port this
-      month. Mark Peek has succeeded in getting the FreeBSD/PowerPC
-      kernel cross compiled on FreeBSD and booting under the PSIM
-      simulator (now in /usr/ports/emulators/psim-freebsd). I have
-      succeeded in getting the FreeBSD loader to load and execute
-      kernels using the OpenFirmware found on Apple Macintosh hardware.
-      Mark is now working on completing some of the startup and pmap
-      code, while I am taking advantage of the simulator to work on
-      some interrupt and device issues.</p>
-    <hr /><h2><a name="PPP-IPv6-Support" href="#PPP-IPv6-Support" id="PPP-IPv6-Support">PPP IPv6 Support</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@freebsd-services.com">brian@freebsd-services.com</a>&gt;
-	</p>
-      <p>The software has been committed to -current and seems
-      functional. Outstanding issues include dealing with IPV6CP events
-      (linkup &amp; linkdown scripts) and allocating site-local and
-      global addresses (currently, ``iface add'' is the only way to
-      actually use the link). A bug exists in -stable (running the
-      not-yet-MFC'd ppp code) whereby routing entries are disappearing
-      after a time (around 12 or 24 hours). No further details are yet
-      available.</p>
-    <hr /><h2><a name="PRFW" href="#PRFW" id="PRFW">PRFW</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freesoftware.fsf.org/jailuser/" title="http://www.freesoftware.fsf.org/jailuser/"></a></td><td>
-	    URL: <a href="http://www.freesoftware.fsf.org/jailuser/" title="">http://www.freesoftware.fsf.org/jailuser/</a></td></tr></table><p>
-	Contact:
-          Evan
-
-          Sarmiento
-         &lt;<a href="mailto:evms@csa.bu.edu">evms@csa.bu.edu</a>&gt;
-	</p>
-      <p>PRFW provides hooks in the FreeBSD kernel, allowing users to
-      insert their own checks in system calls and various kernel
-      functions. PRFW is nearing 0.5, which will incorporate numerous
-      structural changes such as, much faster per-process hooks, kernel
-      function hooks, plus, a new way of adding hooks which would
-      enable users to reference hooks by a string.</p>
-    <hr /><h2><a name="RELNOTESng" href="#RELNOTESng" id="RELNOTESng">RELNOTESng</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmah/relnotes/" title="http://people.FreeBSD.org/~bmah/relnotes/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmah/relnotes/" title="">http://people.FreeBSD.org/~bmah/relnotes/</a></td></tr></table><p>
-	Contact:
-          Bruce A.
-
-          Mah
-         &lt;<a href="mailto:bmah@FreeBSD.org">bmah@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD 4.4-RELEASE was the first release of FreeBSD with its
-      new-style release documentation. Both English and Japanese
-      versions of these documents were created. Regularly-built
-      snapshots of -CURRENT and 4-STABLE release documentation are now
-      available on the Web site, but they require a little HTML
-      infrastructure to make them viewer-friendly. I intend to continue
-      updating my snapshot site at the URL above, at least for a little
-      while.</p>
-
-      <p>Call for help: The hardware compatibility lists need to be
-      updated in the areas of the Alpha architecture, USB devices, and
-      PCCARD devices. I'm looking for volunteers to help; interested
-      parties should contact me at the email address above. DocBook
-      experience is not required; familiarity with the hardware above
-      would be very helpful.</p>
-    <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~jasone/smp/" title="http://www.FreeBSD.org/~jasone/smp/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jasone/smp/" title="">http://www.FreeBSD.org/~jasone/smp/</a></td></tr></table><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Some progress has been made on the proc locking this month.
-      Also, a new LOCK_DEBUG macro was defined to allow some locking
-      infrastructure to be more efficient. Kernels now only include the
-      filenames of files calling mutex, sx, or semaphore lock
-      operations if the filenames are needed. Also, mutex operations
-      are no longer inlined if any debugging options are turned on. The
-      ucred API was also overhauled to be more locking friendly. A
-      group has also started investigating the tty subsystem to design
-      and possibly implement a locking strategy.</p>
-    <hr /><h2><a name="SYN-cache-implementation-for-FreeBSD" href="#SYN-cache-implementation-for-FreeBSD" id="SYN-cache-implementation-for-FreeBSD">SYN cache implementation for FreeBSD</a></h2><p>
-	Contact:
-          Jonathan
-
-          Lemon
-         &lt;<a href="mailto:jlemon@FreeBSD.org">jlemon@FreeBSD.org</a>&gt;
-	</p>
-      <p>No new status to report, the code is still waiting to be
-      committed. It is likely that this code will be expanded to
-      include syn cookies as a further fallback mechanism.</p>
-    <hr /><h2><a name="TIRPC" href="#TIRPC" id="TIRPC">TIRPC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.attic.ch/tirpc.html" title="http://www.attic.ch/tirpc.html"></a></td><td>
-	    URL: <a href="http://www.attic.ch/tirpc.html" title="">http://www.attic.ch/tirpc.html</a></td></tr></table><p>
-	Contact:
-          Martin
-
-          Blapp
-         &lt;<a href="mailto:mb@imp.ch">mb@imp.ch</a>&gt;
-	</p>
-      <p>As you know, in march 2001 the version 2.3 of TIRPC has been
-      committed together with many userland changes. Alfred Perlstein
-      and Ian Dowse have helped me a lot with the porting effort and if
-      I had problems with understanding the code.</p>
-
-      <p>Most bugs are now fixed, some remaining areas to fix are
-      secure RPC (keyserv) and unix domain support. I've patches for
-      these area available. Ian Dowse fixed a lot of outstanding bugs
-      in the rpcbind binary itself. Thank you Ian !</p>
-
-      <p>The plan is now to migrate slowly towards TIRPC 2.8, which is
-      threadsafe for the server- and clientside. One first patch I've
-      made available on my URL. TIRPC 2.8 is licensed under the "Sun
-      Standards License Version 1.0" and we have to add some license
-      lines and the license itself to all modified files.</p>
-
-      <p>A example is timed_clnt_create.diff which can be found on the
-      homepage.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2001-11.html b/website/content/en/status/report-2001-11.html
deleted file mode 100644
index 0955899638..0000000000
--- a/website/content/en/status/report-2001-11.html
+++ /dev/null
@@ -1,838 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This months report covers activity during the second half of
-    October, and the month of November. During these months,
-    substantial work was performed to improve system performance and
-    stability, in particular addressing concerns regarding regressions
-    in network performance for the TCP protocol, and via the
-    introduction of polled network device driver support. Work
-    continues on long-term architectural projects for 5.0, including
-    KSEs, NEWCARD, and TrustedBSD, as well as the cleaning up of
-    long-standing problems in FreeBSD, such as PAM integration.
-    Administrative changes are also documented, including work to
-    redefine and formalize the release engineering process, and the
-    approval of a new portmgr group which will administer the ports
-    collection.</p><p>FreeBSD users and developers are strongly encouraged to attend
-    the USENIX BSD Conference in February of next year; it is expected
-    that this will be a useful forum both for learning about FreeBSD
-    and on-going work, as well as providing an opportunity for
-    developers to work more closely and act as a vehicle for discussion
-    and round-the-clock hacking. More information is available at the
-    USENIX web site.</p><p>Robert Watson</p><hr /><ul><li><a href="#ATA-Project-Status-Report">ATA Project Status Report</a></li><li><a href="#Device-Polling">Device Polling</a></li><li><a href="#Fibre-Channel-Support">Fibre Channel Support</a></li><li><a href="#FreeBSD-4.5-Release-Engineering">FreeBSD 4.5 Release Engineering</a></li><li><a href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></li><li><a href="#FreeBSD-in-Bulgarian">FreeBSD in Bulgarian</a></li><li><a href="#FreeBSD-NVIDIA-Driver-Port">FreeBSD NVIDIA Driver Port</a></li><li><a href="#GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></li><li><a href="#Improving-FreeBSD-startup-scripts">Improving FreeBSD startup scripts</a></li><li><a href="#Intel-Gigabit-Driver:-wx-desupported">Intel Gigabit Driver: wx desupported</a></li><li><a href="#jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KSEs">KSEs</a></li><li><a href="#LOMAC-Status-Report">LOMAC Status Report</a></li><li><a href="#Network-interface-cloning-and-modularity">Network interface cloning and modularity</a></li><li><a href="#New-mount(2)-API">New mount(2) API</a></li><li><a href="#NEWCARD/OLDCARD-Status-report">NEWCARD/OLDCARD Status report</a></li><li><a href="#Pluggable-Authentication-Modules">Pluggable Authentication Modules</a></li><li><a href="#Ports-Manager-Team-(portmgr)">Ports Manager Team (portmgr)</a></li><li><a href="#RELNOTESng">RELNOTESng</a></li><li><a href="#Revised-{mode,log}page-support-for-camcontrol">Revised {mode,log}page support for camcontrol</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#Status-Report:-mb_alloc-(-CURRENT-mbuf-allocator)">Status Report: mb_alloc (-CURRENT mbuf allocator)</a></li><li><a href="#TCP-Performance-Improvements">TCP Performance Improvements</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-Project">TrustedBSD Project</a></li><li><a href="#UDF-Filesystem">UDF Filesystem</a></li><li><a href="#Web-site-conversion-to-XML">Web site conversion to XML</a></li></ul><hr /><h2><a name="ATA-Project-Status-Report" href="#ATA-Project-Status-Report" id="ATA-Project-Status-Report">ATA Project Status Report</a></h2><p>
-	Contact:
-          S�ren Schmidt
-         &lt;<a href="mailto:sos@FreeBSD.org">sos@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is underways to support failing mirror disks better and
-      handle hotswapping in a new replacement disk and have it rebuild
-      automagically.</p>
-
-      <p>Support for the Promise TX4 is now working in my lab, seems
-      they did the PCI-PCI bridging in the not so obvious way.</p>
-
-      <p>Plans are in the works to backport the -current ATA driver to
-      -stable with hotswap and the works. Now that -current is delayed
-      I'm working on ways to give me time to get this done, since I've
-      had lots of requests lately and we really can't let down our
-      customers :).</p>
-
-      <p>SMART support is being worked on, but no timelines yet.</p>
-
-      <p>Although not strictly ATA, Promise has equipped me with a
-      couple SuperTrak sx6000 RAID controllers, they take 6 ATA disks
-      and does RAID0-5 in hardware. I have done a driver (its an I2O
-      device) for both -current and -stable and it works beautifully with
-      hotswap the works. It will enter the tree when it is more mature,
-      and I have an agreement with Promise on how we handle userland
-      control util etc. BTW it seems it can also be used as a normal 6
-      channel PCI ATA controller, a bit on the expensive side
-      maybe...</p>
-    <hr /><h2><a name="Device-Polling" href="#Device-Polling" id="Device-Polling">Device Polling</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/polling/" title="http://info.iet.unipi.it/~luigi/polling/">Web page with code and detailed description.</a></td><td>
-	    URL: <a href="http://info.iet.unipi.it/~luigi/polling/" title="Web page with code and detailed description.">http://info.iet.unipi.it/~luigi/polling/</a></td></tr></table><p>
-	Contact:
-          Luigi
-
-          Rizzo
-         &lt;<a href="mailto:luigi@iet.unipi.it">luigi@iet.unipi.it</a>&gt;
-	</p>
-      <p>This work uses a mixed interrupt-polling architecture to
-      handle network device drivers, giving the system substantial
-      improvements in terms of stability and robustness to overloads,
-      as well as the ability to control the sharing of CPU between
-      network-related kernel processing and other user/kernel tasks.
-      Last not least, you might even see a moderate (up to 20-30%,
-      machine dependent) performance improvement.</p>
-    <hr /><h2><a name="Fibre-Channel-Support" href="#Fibre-Channel-Support" id="Fibre-Channel-Support">Fibre Channel Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.feral.com/isp.html" title="http://www.feral.com/isp.html">Qlogic ISP Host Adapter Software</a></td><td>
-	    URL: <a href="http://www.feral.com/isp.html" title="Qlogic ISP Host Adapter Software">http://www.feral.com/isp.html</a></td></tr></table><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@feral.com">mjacob@feral.com</a>&gt;
-	</p>
-      <p>Ongoing bug fixes. Work is underway, to be integrated shortly,
-      that makes the cross platform endian support easier and will
-      prepare the FreeBSD version for eventual sparc64 and PowerPC
-      usage.</p>
-    <hr /><h2><a name="FreeBSD-4.5-Release-Engineering" href="#FreeBSD-4.5-Release-Engineering" id="FreeBSD-4.5-Release-Engineering">FreeBSD 4.5 Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/internal/releng.html" title="http://www.FreeBSD.org/internal/releng.html">FreeBSD Release Engineering.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/internal/releng.html" title="FreeBSD Release Engineering.">http://www.FreeBSD.org/internal/releng.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/internal/releng45.html" title="http://www.FreeBSD.org/internal/releng45.html">FreeBSD 4.5 Release Process / Schedule.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/internal/releng45.html" title="FreeBSD 4.5 Release Process / Schedule.">http://www.FreeBSD.org/internal/releng45.html</a></td></tr></table><p>
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	</p>
-      <p>Release engineering activities for FreeBSD 4.5 have begun. An
-      overview of the entire process has been added to the FreeBSD web
-      site, along with a specific schedule for 4.5. The code freeze is
-      scheduled to start on December 20. The team responsible for
-      responding to MFC requests sent to re@FreeBSD.org for this
-      release is: Murray Stokely, Robert Watson, and John Baldwin. Some
-      of our many goals for this release include closing more
-      installation-related problem reports, being more conservative
-      with our approval of changes during the code freeze, and
-      continuing to document the entire process. For suggestions or
-      questions about FreeBSD 4.5 release activities, please subscribe
-      to the public freebsd-qa@FreeBSD.org mailing list.</p>
-    <hr /><h2><a name="FreeBSD-C99-&amp;-POSIX-Conformance-Project" href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project" id="FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mike/c99/" title="http://people.FreeBSD.org/~mike/c99/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mike/c99/" title="">http://people.FreeBSD.org/~mike/c99/</a></td></tr></table><p>
-	Contact:
-          Mike
-
-          Barcroft
-         &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeBSD-Standards Mailing List
-         &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on the FreeBSD C99 &amp; POSIX Conformance Project is
-      progressing nicely. Since the last status report, two new headers
-      have been added [&lt;stdint.h&gt; and &lt;inttypes.h&gt;],
-      several new functions implemented [atoll(3), imaxabs(3),
-      imaxdiv(3), llabs(3), lldiv(3), strerror_r(3), strtoimax(3), and
-      strtoumax(3)], and changes to assert(3) and printf(3) were made
-      to support C99. More printf(3) changes are in the works to
-      support the remaining C99 and POSIX requirements. Additionally,
-      research was done into our POSIX Utility conformance and a list
-      of tasks was derived from that research.</p>
-
-      <p>Several other interesting events occurred during November and
-      the beginning of December. The project mailing list was moved to
-      the FreeBSD.org domain, and is now available at
-      standards@FreeBSD.org. On December 6, 2001, the IEEE Standards
-      Board approved the Austin Group Specification as IEEE Std
-      1003.1-2001, thus making the work we're doing ever more
-      important.</p>
-    <hr /><h2><a name="FreeBSD-in-Bulgarian" href="#FreeBSD-in-Bulgarian" id="FreeBSD-in-Bulgarian">FreeBSD in Bulgarian</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD-bg.ringlet.net/" title="http://www.FreeBSD-bg.ringlet.net/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD-bg.ringlet.net/" title="">http://www.FreeBSD-bg.ringlet.net/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~roam/bg/" title="http://people.FreeBSD.org/~roam/bg/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~roam/bg/" title="">http://people.FreeBSD.org/~roam/bg/</a></td></tr></table><p>
-	Contact:
-          Peter
-
-          Pentchev
-         &lt;<a href="mailto:roam@FreeBSD.org">roam@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD in Bulgarian project aims to bring a more
-      comfortable working environment to Bulgarian users of the FreeBSD
-      OS. This includes, but is not limited to, font, keymap and locale
-      support, translation of the FreeBSD documentation into Bulgarian,
-      local user groups and various forms of on-line help channels and
-      discussion forums to help Bulgarians adopt and use FreeBSD.</p>
-
-      <p>Bulgarian locale support has been committed to FreeBSD
-      5.0-CURRENT (and later merged into 4.x-STABLE on December 10th).
-      A local CVS repository for the translation of the FreeBSD
-      documentation into Bulgarian has been created.</p>
-    <hr /><h2><a name="FreeBSD-NVIDIA-Driver-Port" href="#FreeBSD-NVIDIA-Driver-Port" id="FreeBSD-NVIDIA-Driver-Port">FreeBSD NVIDIA Driver Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="ftp://ftp.jurai.net/users/winter/nvidia/NEWS" title="ftp://ftp.jurai.net/users/winter/nvidia/NEWS">News and Status.</a></td><td>
-	    URL: <a href="ftp://ftp.jurai.net/users/winter/nvidia/NEWS" title="News and Status.">ftp://ftp.jurai.net/users/winter/nvidia/NEWS</a></td></tr><tr><td><a href="ftp://ftp.jurai.net/users/winter/nvidia/" title="ftp://ftp.jurai.net/users/winter/nvidia/">FTP directory.</a></td><td>
-	    URL: <a href="ftp://ftp.jurai.net/users/winter/nvidia/" title="FTP directory.">ftp://ftp.jurai.net/users/winter/nvidia/</a></td></tr></table><p>
-	Contact:
-          Matthew
-
-          N.
-
-          Dodd
-         &lt;<a href="mailto:mdodd@FreeBSD.org">mdodd@FreeBSD.org</a>&gt;
-	</p>
-      <p>The port of the driver is around 90% feature complete. AGP
-      support and "Registry" support via sysctl need to be
-      finished/implemented. The NVIDIA guys are working on a build of
-      the X11 libs and extensions for FreeBSD; once this is done
-      hardware accelerated direct rendering should work. The previous
-      version this driver is no longer available. I'm planning on
-      making a snapshot of my code once I chase out a few more
-      bugs.</p>
-
-      <p>Please note that development is taking place under -CURRENT
-      right now; a port to -STABLE will be available at some later
-      time.</p>
-    <hr /><h2><a name="GEOM---generalized-block-storage-manipulation" href="#GEOM---generalized-block-storage-manipulation" id="GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~phk/Geom/" title="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~phk/Geom/" title="Old concept paper here.">http://www.FreeBSD.org/~phk/Geom/</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is now finally underway, thanks to DARPA and NAI
-      getting a sponsorship lined up. The infrastructure code and data
-      structures are currently taking form inside a userland simulation
-      harness.</p>
-    <hr /><h2><a name="Improving-FreeBSD-startup-scripts" href="#Improving-FreeBSD-startup-scripts" id="Improving-FreeBSD-startup-scripts">Improving FreeBSD startup scripts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://groups.yahoo.com/group/FreeBSD-rc/" title="http://groups.yahoo.com/group/FreeBSD-rc/">Improving FreeBSD startup scripts</a></td><td>
-	    URL: <a href="http://groups.yahoo.com/group/FreeBSD-rc/" title="Improving FreeBSD startup scripts">http://groups.yahoo.com/group/FreeBSD-rc/</a></td></tr><tr><td><a href="http://www.cs.rmit.edu.au/~lukem/bibliography.html" title="http://www.cs.rmit.edu.au/~lukem/bibliography.html">Luke Mewburn's papers</a></td><td>
-	    URL: <a href="http://www.cs.rmit.edu.au/~lukem/bibliography.html" title="Luke Mewburn's papers">http://www.cs.rmit.edu.au/~lukem/bibliography.html</a></td></tr><tr><td><a href="http://www.netbsd.org/Documentation/rc/" title="http://www.netbsd.org/Documentation/rc/">NetBSD Initialization and Services Control</a></td><td>
-	    URL: <a href="http://www.netbsd.org/Documentation/rc/" title="NetBSD Initialization and Services Control">http://www.netbsd.org/Documentation/rc/</a></td></tr></table><p>
-	Contact:
-          Doug Barton
-
-          Committer
-         &lt;<a href="mailto:DougB@FreeBSD.org">DougB@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Gordon Tetlow
-
-          Contributor
-         &lt;<a href="mailto:gordont@gnf.org">gordont@gnf.org</a>&gt;
-	</p>&lt;-- from http://groups.yahoo.com/group/FreeBSD-rc/ --&gt;
-    <p>This group is for discussion about the startup scripts in
-    FreeBSD, primarily the scripts in /etc/rc*. Primary focus will be
-    on improvements and importation of NetBSD's excellent work on this
-    topic.</p>
-
-    &lt;-- from Gordon Tetlow's ranting --&gt;
-    <p>Due to personal commitments by the folks working on this project
-    we have been unable to spend much time porting the rc.d
-    infrastructure into the FreeBSD boot framework.</p>
-
-    <p>Currently, the system will boot (with a little fudging) just
-    before network utilization. There are patches floating around for
-    this (see the -arch list from September).</p>
-    <hr /><h2><a name="Intel-Gigabit-Driver:-wx-desupported" href="#Intel-Gigabit-Driver:-wx-desupported" id="Intel-Gigabit-Driver:-wx-desupported">Intel Gigabit Driver: wx desupported</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@feral.com">mjacob@feral.com</a>&gt;
-	</p>
-      <p>The wx driver is desupported and removed from -current. No
-      further support for wx in -stable is planned. Newer and better
-      drivers are now in the tree.</p>
-    <hr /><h2><a name="jp.FreeBSD.org-daily-SNAPSHOTs-project" href="#jp.FreeBSD.org-daily-SNAPSHOTs-project" id="jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://snapshots.jp.FreeBSD.org/" title="http://snapshots.jp.FreeBSD.org/">Project Webpage</a></td><td>
-	    URL: <a href="http://snapshots.jp.FreeBSD.org/" title="Project Webpage">http://snapshots.jp.FreeBSD.org/</a></td></tr><tr><td><a href="ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/" title="ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/">Anonymous FTP</a></td><td>
-	    URL: <a href="ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/" title="Anonymous FTP">ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/</a></td></tr></table><p>
-	Contact:
-          Makoto
-
-          Matsushita
-         &lt;<a href="mailto:matusita@jp.FreeBSD.org">matusita@jp.FreeBSD.org</a>&gt;
-	</p>
-      <p>jp.FreeBSD.org daily SNAPSHOTs project is yet another
-      snapshots server that provides latest 4-stable and 5-current
-      distribution. You also find installable ISO image, live
-      filesystem, HTMLed source code with search engine, and more;
-      please check project webpage for more details.</p>
-    <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">User and developer information (in Japanese).</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="User and developer information (in Japanese).">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-          Kazuo
-
-          Horikawa
-         &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-      <p>Targeting 4.5-RELEASE, we continued to revising
-      doc/ja_JP.eucJP/man/man[1256789] to catch up with RELENG_4.
-      Section 3 updating has 45% finished.</p>
-    <hr /><h2><a name="KSEs" href="#KSEs" id="KSEs">KSEs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~julian/" title="http://www.FreeBSD.org/~julian/">My web-page with links</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~julian/" title="My web-page with links">http://www.FreeBSD.org/~julian/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/~jasone/kse/" title="http://www.FreeBSD.org/~jasone/kse/">Jason Evans' KSE page.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jasone/kse/" title="Jason Evans' KSE page.">http://www.FreeBSD.org/~jasone/kse/</a></td></tr></table><p>
-	Contact:
-          Julian
-
-          Elischer
-         &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have been working behind the scenes on design rather than
-      programming for this last month. I have been working however in
-      the p4 tree to make the system run with the thread structure NOT
-      a part of the proc structure (a prerequisite for threading)</p>
-    <hr /><h2><a name="LOMAC-Status-Report" href="#LOMAC-Status-Report" id="LOMAC-Status-Report">LOMAC Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://opensource.nailabs.com/lomac/" title="http://opensource.nailabs.com/lomac/">NAI Labs' LOMAC page</a></td><td>
-	    URL: <a href="http://opensource.nailabs.com/lomac/" title="NAI Labs' LOMAC page">http://opensource.nailabs.com/lomac/</a></td></tr></table><p>
-	Contact:
-          Brian
-
-          Feldman
-         &lt;<a href="mailto:green@FreeBSD.org">green@FreeBSD.org</a>&gt;
-	</p>
-      <p>A FreeBSD -CURRENT snapshot with LOMAC is currently being
-      prepared, with aid of Perforce on the "green_lomac" branch. Very
-      soon there should be a working demonstration installation CD of
-      FreeBSD with LOMAC, including the ability to enable LOMAC in
-      rc.conf with sysinstall, being a legitimate "out-of-the-box"
-      FreeBSD experience. Actual release build is pending debugging
-      issues with program start-up (especially xdm).</p>
-    <hr /><h2><a name="Network-interface-cloning-and-modularity" href="#Network-interface-cloning-and-modularity" id="Network-interface-cloning-and-modularity">Network interface cloning and modularity</a></h2><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for VLAN cloning has been merged from current and will
-      ship with 4.5-RELEASE. Additionally, new rc.conf support for
-      cloning interfaces at boot has been MFD'd. Work is ongoing to MFC
-      stf and faith cloning as well as adding cloning for ppp devices
-      and enhancing VLAN modularity.</p>
-    <hr /><h2><a name="New-mount(2)-API" href="#New-mount(2)-API" id="New-mount(2)-API">New mount(2) API</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.sneakerz.org/~mux/mount.diff" title="http://www.sneakerz.org/~mux/mount.diff"></a></td><td>
-	    URL: <a href="http://www.sneakerz.org/~mux/mount.diff" title="">http://www.sneakerz.org/~mux/mount.diff</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Maxime
-
-          Henrion
-         &lt;<a href="mailto:mux@qualys.com">mux@qualys.com</a>&gt;
-	</p>
-      <p>There is now some code ready for the new mount API, which has
-      to be reviewed and tested. If it is adopted, we will probably
-      start converting all the filesystems, as well as other code in
-      the kernel, to make them use it. If you want to play with it, the
-      patch is available at the above URL.</p>
-    <hr /><h2><a name="NEWCARD/OLDCARD-Status-report" href="#NEWCARD/OLDCARD-Status-report" id="NEWCARD/OLDCARD-Status-report">NEWCARD/OLDCARD Status report</a></h2><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Not much to report. A number of minor bugs in OLDCARD have
-      been corrected. A larger number of machines now work. Additional
-      work on ToPIC support has been committed, but continued lack of a
-      suitable ToPIC machine has left the author unable to do much
-      work. A few stubborn machines still need to be supported (the
-      author has an example of one such machine, so there is hope for
-      it being fixed. Some pci related issues remain for both OLDCARD
-      and NEWCARD.</p>
-
-      <p>NEWCARD work is ramping up, while OLDCARD work is ramping
-      down. A number of things remain to be done for NEWCARD, including
-      suspend/ resume support, generic device arrival/removal daemon
-      and hopefully automatic loading of drivers. A number of current
-      pccard drivers still need to be converted to NEWBUS. Several
-      Chipset issues remain, as does the merging of isa pccard bridge
-      code with the pccbb code.</p>
-    <hr /><h2><a name="Pluggable-Authentication-Modules" href="#Pluggable-Authentication-Modules" id="Pluggable-Authentication-Modules">Pluggable Authentication Modules</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~des/diary/2001.html" title="http://people.FreeBSD.org/~des/diary/2001.html"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~des/diary/2001.html" title="">http://people.FreeBSD.org/~des/diary/2001.html</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Murray
-         &lt;<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Dag-Erling
-
-          Sm�rgrav
-         &lt;<a href="mailto:des@FreeBSD.org">des@FreeBSD.org</a>&gt;
-	</p>
-      <p>On the code side, a number of libpam bugs have been fixed; a
-      new PAM module,
-      <tt>pam_self(8)</tt>
-
-      , has been written; and preparations have been made for
-      the transition from
-      <tt>/etc/pam.conf</tt>
-
-      to
-      <tt>/etc/pam.d</tt>
-
-      .</p>
-
-      <p>On the documentation side, new manual pages have been written
-      for
-      <tt>pam_ssh(8)</tt>
-
-      ,
-      <tt>pam_get_item(3)</tt>
-
-      and
-      <tt>pam_set_item(3)</tt>
-
-      , and work has started on a longer article about PAM which is
-      expected to be finished by the end of the year.</p>
-
-      <p>A lot of work still remains to be done to integrate PAM more
-      tightly with the FreeBSD base system&#8212;particularly the
-      <tt>passwd(1)</tt>
-
-      ,
-      <tt>chpass(1)</tt>
-
-      etc. utilities&#8212;and ports collection.</p>
-    <hr /><h2><a name="Ports-Manager-Team-(portmgr)" href="#Ports-Manager-Team-(portmgr)" id="Ports-Manager-Team-(portmgr)">Ports Manager Team (portmgr)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bento.FreeBSD.org/" title="http://bento.FreeBSD.org/">Ports build cluster</a></td><td>
-	    URL: <a href="http://bento.FreeBSD.org/" title="Ports build cluster">http://bento.FreeBSD.org/</a></td></tr></table><p>
-	Contact:
-          Will
-
-          Andrews
-         &lt;<a href="mailto:will@FreeBSD.org">will@FreeBSD.org</a>&gt;
-	</p>
-      <p>After a discussion with the Core Team about our status
-      regarding the ports collection, we heard from them that they'd
-      decided to recognize us as the final authority for approving
-      ports committers. We've spent the last few weeks working on our
-      ports build cluster (see the link) and trying to find ways to
-      improve it for the ports development community. We've also
-      handled a few minor issues in the ports collection.</p>
-    <hr /><h2><a name="RELNOTESng" href="#RELNOTESng" id="RELNOTESng">RELNOTESng</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmah/relnotes/" title="http://people.FreeBSD.org/~bmah/relnotes/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmah/relnotes/" title="">http://people.FreeBSD.org/~bmah/relnotes/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/relnotes.html" title="http://www.FreeBSD.org/relnotes.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/relnotes.html" title="">http://www.FreeBSD.org/relnotes.html</a></td></tr></table><p>
-	Contact:
-          Bruce
-
-          Mah
-         &lt;<a href="mailto:bmah@FreeBSD.org">bmah@FreeBSD.org</a>&gt;
-	</p>
-      <p>I've been working on making the Hardware Notes less
-      i386-centric. This will be especially important for -CURRENT as
-      the ia64 and sparc ports reach maturity; most of this work should
-      be completed in time to be MFC-ed for FreeBSD 4.5-RELEASE. I
-      encourage any interested parties to review the release
-      documentation and send me comments or patches.</p>
-    <hr /><h2><a name="Revised-{mode,log}page-support-for-camcontrol" href="#Revised-{mode,log}page-support-for-camcontrol" id="Revised-{mode,log}page-support-for-camcontrol">Revised {mode,log}page support for camcontrol</a></h2><p>
-	Contact:
-          Kelly
-
-          Yancey
-         &lt;<a href="mailto:kbyanc@FreeBSD.org">kbyanc@FreeBSD.org</a>&gt;
-	</p>
-      <p>Extending camcontrol's page definition file format to include
-      both modepage and logpage definitions; adding support to
-      camcontrol to query and reset log page parameters. Consideration
-      is being made to possibly include support for diagnostic and
-      vital product data pages, but that is outside the current project
-      scope. New page definition file format includes capability to
-      conditionally include page definitions based on SCSI INQUIRY
-      results allowing vendor-specific pages to be described also.
-      Approximately 80% complete.</p>
-    <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>October ended up being a bit busier than November for
-	SMPng. During October, Peter Wemm finally finished the
-	ambitious task of unwinding all the macros in NFS and
-	splitting it up into two halves: client and server.  Andrew
-	Reiter also submitted some code to add locks to taskqueues,
-	and the folks working on the TTY subsystem designed the
-	locking strategy they will be using.  Per-thread ucred
-	references were also added for user traps and syscalls.  Once
-	the necessary locking on the process ucred references is
-	committed, this will allow kernel code to access the
-	credentials of the current thread without needing locks while
-	also ensuring that a thread has constant credentials for the
-	lifetime of a syscall.  November only saw a few small bug fixes
-	unfortunately, but December is already shaping up to be a very
-	active month, so next month's report should be a bit more
-	interesting.</p>
-
-      <p>In non-coding news, the website for the SMPng project has
-	moved from its old location to the new location above.  Also,
-	I have completed a paper I am presenting for BSDCon regarding
-	the SMPng project.  The paper will be available in the
-	conference proceedings and will be available online after the
-	conference as well.</p>
-    <hr /><h2><a name="Status-Report:-mb_alloc-(-CURRENT-mbuf-allocator)" href="#Status-Report:-mb_alloc-(-CURRENT-mbuf-allocator)" id="Status-Report:-mb_alloc-(-CURRENT-mbuf-allocator)">Status Report: mb_alloc (-CURRENT mbuf allocator)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~bmilekic/code/mb_alloc/" title="http://www.FreeBSD.org/~bmilekic/code/mb_alloc/">Code Dump and Preliminary Results</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~bmilekic/code/mb_alloc/" title="Code Dump and Preliminary Results">http://www.FreeBSD.org/~bmilekic/code/mb_alloc/</a></td></tr></table><p>
-	Contact:
-          Bosko
-
-          Milekic
-         &lt;<a href="mailto:bmilekic@FreeBSD.org">bmilekic@FreeBSD.org</a>&gt;
-	</p>
-      <p>Presently re-style(9)ing mbuf code with the help of Bruce
-      (bde). The next larger step is approaching: to better
-      performance, as initially planned, not have reference counters
-      for clusters allocated separately via malloc(9). Rather, use some
-      of the [unused] space at the end of each cluster as a counter;
-      since this space is totally unused and since ref. counter
-      &lt;--&gt; mbuf cluster is a one-to-one relationship, this is
-      most convenient.</p>
-    <hr /><h2><a name="TCP-Performance-Improvements" href="#TCP-Performance-Improvements" id="TCP-Performance-Improvements">TCP Performance Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Matthew
-
-          Dillon
-         &lt;<a href="mailto:dillon@FreeBSD.org">dillon@FreeBSD.org</a>&gt;
-	</p>
-      <p>A number of serious TCP bugs effecting throughput snuck into
-      the system over the last few releases and have finally been
-      fixed. TCP performance should be greatly improved for a number of
-      cases, including TCP/NFS.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project Homepage</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project Homepage">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          John
-
-          Doe
-         &lt;<a href="mailto:trustedbsd-audit@trustedbsd.org">trustedbsd-audit@trustedbsd.org</a>&gt;
-	</p>
-      <p>Currently, we are exploring a variety of strategies to learn
-      about the implementation and performance issues in order to have
-      a solid design. One of our main goals will be to use a
-      standardized interface to the system, whether it be POSIX.1e, or
-      another of the other standards, because as they say "Standards
-      are great because you have so many to choose from." Hopefully
-      within the next month or so, we will populate the perforce
-      TrustedBSD tree with an agreed upon framework that is ready for
-      serious final work.</p>
-    <hr /><h2><a name="TrustedBSD-Project" href="#TrustedBSD-Project" id="TrustedBSD-Project">TrustedBSD Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Home Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Home Page">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project continued focusing development efforts
-      on fine-grained Capabilities and Mandatory Access Control this
-      month. Kernel support for capabilities is essentially complete,
-      and efforts are underway to adapt userland applications to use
-      Capabilities. The login process has been updated to allow users
-      to run with additional privilege based on /etc/capabilities. The
-      MAC implementation work has also been active, with improved
-      support for the labeling of IPC objects, including better
-      integration into the network stack. Both development trees have
-      been updated to work with recent KSE-related developments, as
-      well as exist more happily in a fine-grained SMP kernel. Initial
-      audit-related work appears in a separate entry.</p>
-
-      <p>Development of TrustedBSD source code was moved to the FreeBSD
-      Perforce repository, permitting better source code management. As
-      such, the TrustedBSD development trees will now be available via
-      cvsup.</p>
-    <hr /><h2><a name="UDF-Filesystem" href="#UDF-Filesystem" id="UDF-Filesystem">UDF Filesystem</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~scottl/udf" title="http://people.FreeBSD.org/~scottl/udf">UDF Filesystem.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~scottl/udf" title="UDF Filesystem.">http://people.FreeBSD.org/~scottl/udf</a></td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Modest gains have been made on the UDF filesystem since the
-      last report. Reading of files from DVD-ROM now works (and is
-      fast, according to some reports), and there is preliminary
-      support for reading from CD-RW media. The CD-RW support has only
-      been tested against CD's created with Adaptec/ Roxio DirectCD,
-      and much, much more testing is needed. Once this support is
-      solid, I plan to check it into the tree and start work on making
-      the filesystem writable.</p>
-    <hr /><h2><a name="Web-site-conversion-to-XML" href="#Web-site-conversion-to-XML" id="Web-site-conversion-to-XML">Web site conversion to XML</a></h2><p>
-	Contact:
-          Nik
-
-          Clayton
-         &lt;<a href="mailto:nik@FreeBSD.org">nik@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is (slowly) progressing on converting the web site to use
-      pages marked up in a simple XML schema, and then generating HTML
-      and other output formats using XSLT style sheets. The work so far
-      can be tested by doing "cvs checkout -r XML_XSL_XP www" and then
-      "cd www/en; make index.html". Take a look at index.page in the
-      same directory to see the source XML. The CVS logs for index.page
-      contain detailed instructions explaining how index.page was
-      generated from its earlier form.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2001-12-2002-01.html b/website/content/en/status/report-2001-12-2002-01.html
deleted file mode 100644
index 51d4d4f2c6..0000000000
--- a/website/content/en/status/report-2001-12-2002-01.html
+++ /dev/null
@@ -1,679 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This bi-monthly report covers development activities on the FreeBSD
-      Project for December 2001 and January 2002.  A variety of
-      accomplishments have been made over the last couple of months,
-      including strong progress relating to the KSE project, which
-      brings Scheduler Activations to the FreeBSD kernel, as well
-      as less visible infrastructure projects such as improvements
-      to the mount interface, PAM integration work, and translation
-      efforts.  Shortly following the deadline for this status
-      report, the BSD Conference and FreeBSD Developer Summit were
-      held, and will be covered in the next bi-monthly report at
-      the end of March.  Plans are already under way for the USENIX
-      Annual Technical Conference in Monterey, CA, later this year,
-      and all and sundry are encouraged to attend to get further
-      insight in FreeBSD development.</p><p>Robert Watson</p><hr /><ul><li><a href="#&quot;GEOM&quot;---generalized-block-storage-manipulation">"GEOM" - generalized block storage manipulation</a></li><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph
-    implementation)</a></li><li><a href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></li><li><a href="#FreeBSD-in-Bulgarian">FreeBSD in Bulgarian</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KAME">KAME</a></li><li><a href="#KSE-Status-Report">KSE Status Report</a></li><li><a href="#Netgraph-ATM">Netgraph ATM</a></li><li><a href="#New-mount(2)-API">New mount(2) API</a></li><li><a href="#Pluggable-Authentication-Modules">Pluggable Authentication Modules</a></li><li><a href="#Revised-{mode,log}page-support-for-camcontrol">Revised {mode,log}page support for camcontrol</a></li><li><a href="#SMPng">SMPng</a></li><li><a href="#TrustedBSD-ACLs">TrustedBSD ACLs</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-MAC-Implementation">TrustedBSD MAC Implementation</a></li><li><a href="#USB-stack-maintenance">USB stack maintenance</a></li></ul><hr /><h2><a name="&quot;GEOM&quot;---generalized-block-storage-manipulation" href="#&quot;GEOM&quot;---generalized-block-storage-manipulation" id="&quot;GEOM&quot;---generalized-block-storage-manipulation">"GEOM" - generalized block storage manipulation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~phk/Geom/" title="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~phk/Geom/" title="Old concept paper here.">http://www.FreeBSD.org/~phk/Geom/</a></td></tr></table><p>
-	Contact:
-	  Poul-Henning
-
-	  Kamp
-	 &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is now finally underway, thanks to DARPA and NAI
-      getting a sponsorship lined up. The infrastructure code and data
-      structures are currently taking form inside a userland simulation
-      harness. Basic MBR and BSD methods have been written and device
-      attach/taste/dettach algorithms been implemented and
-      validated.</p>
-    <hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph
-    implementation)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Maksim
-
-	  Yevmenkin
-	 &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-      <p>The project is making progress. The goal is to design and
-      implement Host Controller Interface (HCI) and Link Layer Control
-      and Adaptation Protocol (L2CAP) layers using Netgraph framework.
-      More distant goal is to write support for Service Discovery
-      Protocol (SDP) and RFCOMM protocol (Serial port emulation over
-      Bluetooth link) . All information was obtained from Bluetooth
-      Specification Book v1.1.</p>
-
-      <p>Project status: In progress. 1) Design: mostly complete, there
-      are some minor issues to be resolved. 2) Implementation: Kernel -
-      HCI and L2CAP Netgraph nodes have been implemented; 3) User space
-      (API, library, utilities) - in progress. 4) Testing: In progress.
-      I do not have real Bluetooth hardware at this point, so i wrote
-      some tools that allow me to test the code. Some of them will be
-      used as foundation for future user space utilities.</p>
-
-      <p>Issues: 1) Bluetooth hardware; I do not have real Bluetooth
-      hardware, so if people can donate hardware/specs it would be
-      great. I promise to write all required drivers and make them
-      available. I also promise to return hardware/specs on first
-      request. 2) Project name; I would like to see the name that
-      reflects the following: it is a Bluetooth stack, implementation
-      is for FreeBSD and implementation is based on Netgraph
-      framework</p>
-    <hr /><h2><a name="FreeBSD-C99-&amp;-POSIX-Conformance-Project" href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project" id="FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mike/c99/" title="http://people.FreeBSD.org/~mike/c99/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mike/c99/" title="">http://people.FreeBSD.org/~mike/c99/</a></td></tr></table><p>
-	Contact:
-	  Mike
-
-	  Barcroft
-	 &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  FreeBSD-Standards Mailing List
-	 &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-      <p>A significant amount of progress was made in December and
-      January, particularly in the area of utility conformance. Several
-      utilities were updated to conform to SUSv3, they include: at(1),
-      mailx(1), pwd(1), split(1), and uudecode(1). Several patches have
-      been submitted to increase conformance in other utilities, they
-      include: fold(1), patch(1), m4(1), nice(1), pr(1), renice(1),
-      wc(1), and xargs(1). These are in the process of being reviewed
-      and committed. Two new utilities have been written, specifically
-      pathchk(1) and tabs(1). These are also being reviewed and will be
-      committed shortly.</p>
-
-      <p>A patch which implements most of the requirements of scanf(3) is
-      being reviewed and is expected to be committed shortly. This will
-      allow us to MFC a number of new functions and headers.
-      Additionally, work has started on wide string and complex number
-      support.</p>
-    <hr /><h2><a name="FreeBSD-in-Bulgarian" href="#FreeBSD-in-Bulgarian" id="FreeBSD-in-Bulgarian">FreeBSD in Bulgarian</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD-bg.ringlet.net/" title="http://www.FreeBSD-bg.ringlet.net/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD-bg.ringlet.net/" title="">http://www.FreeBSD-bg.ringlet.net/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~roam/bg/" title="http://people.FreeBSD.org/~roam/bg/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~roam/bg/" title="">http://people.FreeBSD.org/~roam/bg/</a></td></tr></table><p>
-	Contact:
-	  Peter
-
-	  Pentchev
-	 &lt;<a href="mailto:roam@FreeBSD.org">roam@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD in Bulgarian project aims to bring a more
-      comfortable working environment to Bulgarian users of the FreeBSD
-      OS. This includes, but is not limited to, font, keymap and locale
-      support, translation of the FreeBSD documentation into Bulgarian,
-      local user groups and various forms of on-line help channels and
-      discussion forums to help Bulgarians adopt and use FreeBSD.</p>
-
-      <p>A guide for using FreeBSD with Bulgarian settings has been put
-      up on the project's website. The CVS repository will be made
-      public shortly, linked to on the URL's above.</p>
-
-      <p>An independent project for making FreeBSD easier to use by
-      Bulgarians has appeared, <a href="http://www.FreeBSD-bg.org/" shape="rect">http://www.FreeBSD-bg.org/</a>.
-      It also hosts a mailing list for discussions of FreeBSD in
-      Bulgarian, <a href="mailto:stable@FreeBSD-bg.org" shape="rect">
-      stable@FreeBSD-bg.org</a>. For more information about the mailing
-      list, send an e-mail with "help" in the message body to
-      <a href="mailto:majordomo@FreeBSD-bg.org" shape="rect">
-      majordomo@FreeBSD-bg.org</a>.</p>
-    <hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java" title="http://www.FreeBSD.org/java"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java" title="">http://www.FreeBSD.org/java</a></td></tr></table><p>
-	Contact:
-	  Greg
-
-	  Lewis
-	 &lt;<a href="mailto:glewis@eyesbeyond.com">glewis@eyesbeyond.com</a>&gt;
-	</p>
-      <p>The past two months have been an exciting time in the FreeBSD
-      Java Project with the signing of a license between the FreeBSD
-      Foundation and Sun allowing us access to updated JDK source code
-      and the Java Compatibility Kit (JCK). This license will also
-      allow the project to release a binary version of both the JDK and
-      JRE once JCK testing is complete. Work on this testing is under
-      way with the project hopeful of being able to make a binary
-      release in the not too distant future.</p>
-
-      <p>In lieu of the binary release which was hoped for with FreeBSD
-      4.5 the project will release an updated source patchset this
-      weekend. This patchset will feature further work on the FreeBSD
-      "native" threads subsystem from Bill Huey. Also, thanks to hard
-      work by Joe Kelsey and Fuyuhiko Maruyama, the patchset will for
-      the first time feature a working Java browser plugin!</p>
-    <hr /><h2><a name="jp.FreeBSD.org-daily-SNAPSHOTs-project" href="#jp.FreeBSD.org-daily-SNAPSHOTs-project" id="jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://snapshots.jp.FreeBSD.org/" title="http://snapshots.jp.FreeBSD.org/">Project Webpage</a></td><td>
-	    URL: <a href="http://snapshots.jp.FreeBSD.org/" title="Project Webpage">http://snapshots.jp.FreeBSD.org/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/snapshots/notes.html" title="http://www.jp.FreeBSD.org/snapshots/notes.html">SNAPSHOTs Notes (in Japanese)</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/snapshots/notes.html" title="SNAPSHOTs Notes (in Japanese)">http://www.jp.FreeBSD.org/snapshots/notes.html</a></td></tr></table><p>
-	Contact:
-	  Makoto
-
-	  Matsushita
-	 &lt;<a href="mailto:matusita@jp.FreeBSD.org">matusita@jp.FreeBSD.org</a>&gt;
-	</p>
-      <p>I've update OS of buildboxes to the latest FreeBSD 5-current
-      and 4-stable. Everything goes fine. From January 2002, I've
-      started a webzine, SNAPSHOTS Notes (only Japanese version is
-      available). SNAPSHOTs Notes pickups tips and information
-      especially for the people living with FreeBSD 5-current/4-stable.
-      Article or idea for SNAPSHOTs notes are always welcome (you don't
-      need to write in Japanese :-).</p>
-    <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project (in Japanese)</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project (in Japanese)">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-	  Kazuo
-
-	  Horikawa
-	 &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-      <p>For 4.5-RELEASE, port ja-man-doc-4.5.tgz is in sync with base
-      system except for OpenSSH pages (OpenSSH 2.3 based instead of
-      2.9) and perl5 pages (jpman project do not maintain). Section 3
-      updating has 55% finished.</p>
-
-      <p>OKAZAKI Tetsurou has incorporated changes on base system's
-      groff into port japanese/groff. MORI Kouji has fixed two bugs of
-      port japanese/man.</p>
-    <hr /><h2><a name="KAME" href="#KAME" id="KAME">KAME</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.kame.net/" title="http://www.kame.net/"></a></td><td>
-	    URL: <a href="http://www.kame.net/" title="">http://www.kame.net/</a></td></tr></table><p>
-	Contact:
-	  KAME core team
-
-
-
-	 &lt;<a href="mailto:core@kame.net">core@kame.net</a>&gt;
-	</p>
-      <p>The KAME project is currently focusing on the scoped
-      addressing architecture, the advanced API implementation, NATPT
-      and the mobile ipv6 implementation. Though these stuffs are not
-      stable enough to be merge into the FreeBSD tree, you can get and
-      try them from the above URL.</p>
-    <hr /><h2><a name="KSE-Status-Report" href="#KSE-Status-Report" id="KSE-Status-Report">KSE Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~julian/" title="http://www.FreeBSD.org/~julian/">Links from here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~julian/" title="Links from here.">http://www.FreeBSD.org/~julian/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/~jasone/kse/" title="http://www.FreeBSD.org/~jasone/kse/">Links from here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jasone/kse/" title="Links from here.">http://www.FreeBSD.org/~jasone/kse/</a></td></tr></table><p>
-	Contact:
-	  Julian
-
-	  Elischer
-	 &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KSE project (an attempt to support scalable thread in
-      FreeBSD using kernel support), has reached What I call "milestone
-      3". At this milestone it is possible to run a multithreaded
-      program on a single CPU but with full concurrency of threads on
-      that CPU. In other words the kernel supports the fact that one
-      thread can block by allowing another thread to run in its place.
-      A test program that demonstrates this is available at the above
-      website.</p>
-
-      <p>Milestone 4 will be to allow threads from the same program to
-      run on multiple CPUs but may require more input from the SMPng
-      project. I am at the moment (Feb 6) getting ready to commit a
-      first set of changes for milestone 3, that have no real effect
-      but serve to drastically reduce the complexity of the remaining
-      diff so that others can read it more easily. After changes to
-      libkvm to support this diff have been added it should be possible
-      to run 'ps' and look at multiple threads in a treaded process. I
-      will be demonstrating KSE/M3 at BSDcon.</p>
-    <hr /><h2><a name="Netgraph-ATM" href="#Netgraph-ATM" id="Netgraph-ATM">Netgraph ATM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="ftp://ftp.fokus.gmd.de/pub/cc/cats/usr/harti/ngatm/" title="ftp://ftp.fokus.gmd.de/pub/cc/cats/usr/harti/ngatm/"></a></td><td>
-	    URL: <a href="ftp://ftp.fokus.gmd.de/pub/cc/cats/usr/harti/ngatm/" title="">ftp://ftp.fokus.gmd.de/pub/cc/cats/usr/harti/ngatm/</a></td></tr></table><p>
-	Contact:
-	  Harti
-
-	  Brandt
-	 &lt;<a href="mailto:brandt@fokus.gmd.de">brandt@fokus.gmd.de</a>&gt;
-	</p>
-      <p>The Netgraph ATM package has been split into a number of
-      smaller packages: bsnmp is a general-purpose SNMP daemon with
-      support for loadable modules. Two modules come with it: one
-      implementing the standard network-interface and IP related parts
-      of MIB-2 and one for interfacing other modules to the NetGraph
-      sub-system. ngatmbase contains the drivers for the ATM hardware,
-      the ng_atm netgraph type and a few test tools. This package
-      allows one to use ATM PVCs. It should be possible, for example,
-      to do PPP over ATM with this package. Both bsnmp and ngatmbase
-      are available in version 1.0 under the link above. Two other
-      modules will be released in February: ngatmsig containing the
-      UNI-4.0 signalling stack as netgraph nodes and ngatmip containing
-      CLIP and LANE-2.0.</p>
-    <hr /><h2><a name="New-mount(2)-API" href="#New-mount(2)-API" id="New-mount(2)-API">New mount(2) API</a></h2><p>
-	Contact:
-	  Poul-Henning
-
-	  Kamp
-	 &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Maxime
-
-	  Henrion
-	 &lt;<a href="mailto:mux@sneakerz.org">mux@sneakerz.org</a>&gt;
-	</p>
-      <p>Now that the patch has been mailed to the
-      freebsd-arch@FreeBSD.org mailing list, and that there were no
-      objections, the commit will happen soon. Poul is currently
-      testing it in his own tree. After it has been committed, it will
-      be time to modify the filesystems in the tree to use VFS_NMOUNT
-      instead of VFS_MOUNT. Mount(8) will also need some modifications.
-      Some new manpages -- nmount(2) and kernel_vmount(9) -- are being
-      created in the meantime.</p>
-    <hr /><h2><a name="Pluggable-Authentication-Modules" href="#Pluggable-Authentication-Modules" id="Pluggable-Authentication-Modules">Pluggable Authentication Modules</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openpam.sourceforge.net/" title="http://openpam.sourceforge.net/">OpenPAM</a></td><td>
-	    URL: <a href="http://openpam.sourceforge.net/" title="OpenPAM">http://openpam.sourceforge.net/</a></td></tr></table><p>
-	Contact:
-	  Mark
-
-	  Murray
-	 &lt;<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Dag-Erling
-
-	  Sm�rgrav
-	 &lt;<a href="mailto:des@FreeBSD.org">des@FreeBSD.org</a>&gt;
-	</p>
-      <p>OpenPAM, a new library intended to replace Linux-PAM in
-      FreeBSD, has been written and is undergoing integration testing.
-      It is available for download from the URL listed above.</p>
-
-      <p>In addition to this, a couple of new modules have been written
-      (pam_lastlog(8), pam_login_access(8)), and the pam_unix(8) module
-      has been extended to perform most of the tasks normally performed
-      by login(1), which is now fully PAMified.</p>
-
-      <p>The PAM FDP article has been put on hold until OpenPAM
-      replaces Linux-PAM in CVS, to avoid wasting effort on soon-to-be
-      obsolete documentation.</p>
-    <hr /><h2><a name="Revised-{mode,log}page-support-for-camcontrol" href="#Revised-{mode,log}page-support-for-camcontrol" id="Revised-{mode,log}page-support-for-camcontrol">Revised {mode,log}page support for camcontrol</a></h2><p>
-	Contact:
-	  Kelly
-
-	  Yancey
-	 &lt;<a href="mailto:kbyanc@FreeBSD.org">kbyanc@FreeBSD.org</a>&gt;
-	</p>
-      <p>Extending camcontrol's page definition file format to include
-      both modepage and logpage definitions; adding support to
-      camcontrol to query and reset log page parameters. Consideration
-      is being made to possibly include support for diagnostic and
-      vital product data pages, but that is outside the current project
-      scope. New page definition file format includes capability to
-      conditionally include page definitions based on SCSI INQUIRY
-      results allowing vendor-specific pages to be described also.
-      Approximately 90% complete.</p>
-    <hr /><h2><a name="SMPng" href="#SMPng" id="SMPng">SMPng</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	smp@FreeBSD.org
-	 &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Alfred Perlstein committed file descriptor locking code
-	which was definitely a good push towards trying to lock down
-	some important pieces of global data.  Peter Wemm has made
-	progress on pmap cleanups for x86 SMP TLB shootdowns.  Matt
-	Dillon and John Baldwin have made progress on getting patches
-	done for moving accesses to ucred's out from under Giant's
-	protection.  John Baldwin has also made some commits in order
-	to get the alpha port's SMP working.  Matt Dillon has plans
-	for hunting down fileops locking issues in order to continue
-	his previous Giant pushdown work.</p>
-    <hr /><h2><a name="TrustedBSD-ACLs" href="#TrustedBSD-ACLs" id="TrustedBSD-ACLs">TrustedBSD ACLs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fxp.org/jedgar/ACL/" title="http://www.fxp.org/jedgar/ACL/"></a></td><td>
-	    URL: <a href="http://www.fxp.org/jedgar/ACL/" title="">http://www.fxp.org/jedgar/ACL/</a></td></tr></table><p>
-	Contact:
-	  Chris
-
-	  Faulhaber
-	 &lt;<a href="mailto:jedgar@FreeBSD.org">jedgar@FreeBSD.org</a>&gt;
-	</p>
-      <p>Patches for cp(1), ls(1), and mv(1) to bring in
-      POSIX.1e-compliant Access Control List support have been updated
-      to patch against builds of -CURRENT. Other system utilities are
-      currently being evaluated for ACL support including install(1)
-      (patch available) and mtree(8). Work is in progress to verify the
-      native getfacl(1), setfacl(1), and other utilities build and work
-      correctly on other ACL-enabled systems (e.g. Linux w/ACL patches)
-      and to help verify POSIX-compliance of the continuing TrustedBSD
-      work along with other systems. Finally, experimental Perl and PHP
-      modules are available allowing limited access to native ACLs for
-      languages other than C.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD project website</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD project website">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-	  trustedbsd-discuss
-	 &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>Robert Watson created the TrustedBSD audit perforce tree,
-      which is a branch from the TrustedBSD base tree, in order to
-      start pushing development efforts towards using a revision
-      control system. Andrew Reiter started to merge in some framework
-      related code for generation of audit records, enqueueing writes,
-      and handling data writing. There is a great deal of work to be
-      done with updates and discussion on the
-      trustedbsd-discuss@TrustedBSD.org mailing list.</p>
-    <hr /><h2><a name="TrustedBSD-MAC-Implementation" href="#TrustedBSD-MAC-Implementation" id="TrustedBSD-MAC-Implementation">TrustedBSD MAC Implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project Web Site</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project Web Site">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-	  Robert
-
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Substantial progress has been made towards a working MAC
-      implementation. The focus over the last two months has been
-      moving from a hard-coded series of MAC policies to a more
-      flexible implementation. A pluggable policy framework has been
-      created (and is still under development), supporting Biba, MLS,
-      TE, a "BSD Extended" model, and a sample mac_none module. Some
-      modules must be compiled in or loaded prior to boot; others may
-      be introduced at run-time. Support for networking has improved,
-      with improved handling of IP fragmentation in IPv4, support for
-      various pseudo-interfaces such as if_tun and if_tap, improved
-      integration into userland, NFS-related fixes, moving the VFS
-      enforcement out of individual filesystems, support for a
-      'multilevel' mount flag, support for explicit labeling in procfs
-      and devfs, addition of an 'extattrctl lsattr' argument to list
-      EAs on a filesystem, support for label ranges in the Biba and MAC
-      policies, and much more.</p>
-
-      <p>Targets for the next two months include more universal
-      enforcement of VFS-related calls, improved support for
-      alternative ABIs, improved flexibility of in-kernel subject and
-      object labels, support for IPv6 and IPsec, and improved support
-      for NFS serving.</p>
-
-      <p>Development continues in the FreeBSD Perforce repository,
-      which may be accessed using cvsup.</p>
-    <hr /><h2><a name="USB-stack-maintenance" href="#USB-stack-maintenance" id="USB-stack-maintenance">USB stack maintenance</a></h2><p>
-	Contact:
-	  Josef
-
-	  Karthauser
-	 &lt;<a href="mailto:joe@FreeBSD.org">joe@FreeBSD.org</a>&gt;
-	</p>
-      <p>I've been working to integrate recent improvements in the
-      NetBSD usb stack to FreeBSD -current. Both NetBSD and OpenBSD
-      currently share the same source, as FreeBSD did too at once point
-      before it diverged. The goal is to get back to that state, but
-      there are many improvements on both sides that need to be merged
-      before this is complete.</p>
-
-      <p>I'm currently looking for someone to help maintain usb in
-      -stable. Please let me know if you're interested.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2002-02-2002-04.html b/website/content/en/status/report-2002-02-2002-04.html
deleted file mode 100644
index 1c9601e388..0000000000
--- a/website/content/en/status/report-2002-02-2002-04.html
+++ /dev/null
@@ -1,1034 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD development activities from February,
-	2002 through April, 2002.  It's been a busy few months -- BSDCon
-	in San Francisco, the FreeBSD Developer Summit, a first development
-	preview of 5.0-CURRENT, not to mention lots of progress on the
-	5.0 feature set (SMPng, sparc64, GEOM, ... the list goes on).</p><p>In the next two months, the USENIX ATC occurs (highly recommended
-	event for both developers and users), and a number of new software
-	components will hit the tree, including UFS2 and the TrustedBSD
-	MAC framework.  We'll also complete the elections for the FreeBSD
-	Core Team, and should have the next Core Team online by the time
-	the next report rolls around.  Stay tuned for more!</p><p>Robert Watson</p><hr /><ul><li><a href="#&quot;GEOM&quot;---generalized-block-storage-manipulation">"GEOM" - generalized block storage manipulation</a></li><li><a href="#Athlon-MTRR-Problems">Athlon MTRR Problems</a></li><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph implementation)</a></li><li><a href="#Fibre-Channel">Fibre Channel</a></li><li><a href="#FreeBSD-ARM-Port">FreeBSD ARM Port</a></li><li><a href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></li><li><a href="#FreeBSD-Developer-Summit">FreeBSD Developer Summit</a></li><li><a href="#FreeBSD-Package-building-Cluster">FreeBSD Package-building Cluster</a></li><li><a href="#FreeBSD/KGI">FreeBSD/KGI</a></li><li><a href="#GCC-3.1">GCC 3.1</a></li><li><a href="#GNOME-Project">GNOME Project</a></li><li><a href="#IA64-Port">IA64 Port</a></li><li><a href="#Improving-FreeBSD-Startup-Scripts">Improving FreeBSD Startup Scripts</a></li><li><a href="#IPMI-Tools-for-FreeBSD">IPMI Tools for FreeBSD</a></li><li><a href="#jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KAME">KAME</a></li><li><a href="#KSE">KSE</a></li><li><a href="#Libh">Libh</a></li><li><a href="#locking-up-pcb's-in-the-networking-stack">locking up pcb's in the networking stack</a></li><li><a href="#Netgraph-ATM">Netgraph ATM</a></li><li><a href="#Network-interface-cloning-and-modularity">Network interface cloning and modularity</a></li><li><a href="#New-mount(2)-API">New mount(2) API</a></li><li><a href="#NEWCARD">NEWCARD</a></li><li><a href="#OpenSSH">OpenSSH</a></li><li><a href="#PAM">PAM</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#ppp-RADIUS/MS-CHAP-support">ppp RADIUS/MS-CHAP support</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#SMPng">SMPng</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-MAC">TrustedBSD MAC</a></li><li><a href="#UMA">UMA</a></li><li><a href="#Universal-Disk-Filesystem-for-FreeBSD">Universal Disk Filesystem for FreeBSD</a></li><li><a href="#Wi-Hostap">Wi Hostap</a></li><li><a href="#Zero-Copy-Sockets">Zero Copy Sockets</a></li></ul><hr /><h2><a name="&quot;GEOM&quot;---generalized-block-storage-manipulation" href="#&quot;GEOM&quot;---generalized-block-storage-manipulation" id="&quot;GEOM&quot;---generalized-block-storage-manipulation">"GEOM" - generalized block storage manipulation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~phk/Geom/" title="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~phk/Geom/" title="Old concept paper here.">http://www.FreeBSD.org/~phk/Geom/</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>The GEOM code has gotten so far that it beats our current code
-	in some areas while still lacking in others.  Work continues on
-	a generalized interface for "magic data" (boot blocks, disklabels
-	MBR's etc) manipulation from userland.</p>
-      <p>With GEOM enabled in the kernel any FreeBSD platform will now
-	recognize PC style MBR's, i386 disklabels, alpha disklabels,
-	PC98 extended MBRs and SUN/Solaris style disklabels.</p>
-
-    <hr /><h2><a name="Athlon-MTRR-Problems" href="#Athlon-MTRR-Problems" id="Athlon-MTRR-Problems">Athlon MTRR Problems</a></h2><p>
-	Contact:
-          David
-
-          Malone
-         &lt;<a href="mailto:dwmalone@FreeBSD.org">dwmalone@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD MTRR code has been made more robust against
-	unexpected values sometimes found in the Athlon's Memory
-	Type Range Registers. Problems with these values had prevented
-	XFree 4.2 running on some motherboards. Experimentation indicates
-	that these undocumented values may control the mapping of
-	BIOS/ROMs or have something to do with SMM. If anyone can provide
-	details of what these values mean, can they
-	please let me know, so the MTRR code can be completed. </p>
-    <hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph implementation)</a></h2><p>
-	Contact:
-          Maksim
-          Yevmenkin
-         &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-
-      <p>I'm slowly making progress. The second engineering release is
-        available for download at
-        http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020506.tar.gz</p>
-
-      <p>This release includes support for H4 UART transport layer, Host
-        Controller Interface (HCI), Link Layer Control and Adaptation
-        Protocol (L2CAP) and Bluetooth sockets layer. It also comes
-        with several user space utilities that can be used to configure
-        and test Bluetooth devices.</p>
-
-      <p>I'm currently working on RFCOMM protocol implementation (Serial
-        port emulation over Bluetooth link). My next goal is to port
-        Service Discovery Protocol (SDP) implementation from BlueZ
-        (http://bluez.sf.net). I'm also thinking about adding USB device
-        support (as soon as i find/buy hardware).</p>
-
-      <p>Issues: 1) Bluetooth hardware; I have couple PC-CARDs that i use
-        for development and testing purposes, but i'd love to have more.
-        2) Time; My regular day job kicked in, so i will be spending more
-        time doing stuff i'm getting paid for.</p>
-
-    <hr /><h2><a name="Fibre-Channel" href="#Fibre-Channel" id="Fibre-Channel">Fibre Channel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mjacob/fibre_channel.html" title="http://people.FreeBSD.org/~mjacob/fibre_channel.html">Project Status Page.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mjacob/fibre_channel.html" title="Project Status Page.">http://people.FreeBSD.org/~mjacob/fibre_channel.html</a></td></tr></table><p>
-	Contact:
-          Matthew
-          Jacob
-           &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>Continued bug fixing and hardening for this last few months.</p>
-        <p>Future work will include making target mode work correctly and fast.</p>
-        <p>The LSI-Logic chipset's MPT Fusion driver is also being evaluated.</p>
-    <hr /><h2><a name="FreeBSD-ARM-Port" href="#FreeBSD-ARM-Port" id="FreeBSD-ARM-Port">FreeBSD ARM Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pages.infinit.net/sepotvin" title="http://pages.infinit.net/sepotvin"></a></td><td>
-	    URL: <a href="http://pages.infinit.net/sepotvin" title="">http://pages.infinit.net/sepotvin</a></td></tr></table><p>
-	Contact:
-          Stephane E.
-          Potvin
-         &lt;<a href="mailto:sepotvin@videotron.ca">sepotvin@videotron.ca</a>&gt;
-	</p>
-      <p>Since the last progress report, the initialization code was much
-	cleaned (thanks to NetBSD's acort32 port) and partial DDB support as
-	been added.  I'm now struggling to put the pmap module into a
-	working state.  The latest patch set only includes the
-	initialization changes.  I did some tries to get what I had so far
-	working on my iPAQ without much successes (downloading a kernel
-	over a serial link is way too painful). If anyone has had success in
-	getting any iPAQ to work as a USB storage device under *BSD please
-	contact me.</p>
-    <hr /><h2><a name="FreeBSD-C99-&amp;-POSIX-Conformance-Project" href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project" id="FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/c99/" title="http://www.FreeBSD.org/projects/c99/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/c99/" title="">http://www.FreeBSD.org/projects/c99/</a></td></tr></table><p>
-	Contact:
-          Mike
-
-          Barcroft
-         &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeBSD-Standards Mailing List
-         &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report, two developers working on utility
-        conformance were given commit access to the FreeBSD CVS repository
-        to help expedite development.  As a result, the following utilities
-        have been brought up to conformance, they include: csplit(1),
-        env(1), expr(1), fold(1), join(1), m4(1), mesg(1), paste(1),
-        patch(1), pr(1), uuencode(1), uuexpand(1), and xargs(1).  The
-        printf(1) utility was brought up to conformance with the 1992
-        edition of POSIX.2, with further development planned.</p>
-
-      <p>On the header front, much progress has been made.  Specifically,
-        infrastructure to control visibility of components of a header, based
-        on the standard requested by an application, has been added to
-        &lt;sys/cdefs.h&gt;.  Some work has been completed on renovating the
-        way types are defined.  This has lead to the creation of
-        &lt;sys/_types.h&gt;.  Further improvements such as the merger of
-        &lt;machine/ansi.h&gt; and &lt;machine/types.h&gt; are planned.
-        Additionally, the headers: &lt;strings.h&gt;, &lt;string.h&gt;, and
-        &lt;sys/un.h&gt; have been made to conform to POSIX.1-2001.</p>
-
-      <p>On the API front, scanf(3) has received support for 5 new length
-        modifiers (hh, j, ll, t, and z).  A patch to implement two
-        additional conversion specifiers (j and z) has been developed for
-        printf(9) and is expected to be committed soon.</p>
-
-      <p>In other news, the project's web site has been moved to the main
-        FreeBSD site.  It is now available at the URL at the top of this
-        status report.  Please update your bookmarks.</p>
-    <hr /><h2><a name="FreeBSD-Developer-Summit" href="#FreeBSD-Developer-Summit" id="FreeBSD-Developer-Summit">FreeBSD Developer Summit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/events/2002/bsdcon-devsummit.html" title="http://www.FreeBSD.org/events/2002/bsdcon-devsummit.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/events/2002/bsdcon-devsummit.html" title="">http://www.FreeBSD.org/events/2002/bsdcon-devsummit.html</a></td></tr></table><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The second FreeBSD Developer Summit, held following the BSD
-	Conference in San Francisco in February, was a great success.  Around
-	40 developers attended in person, another five by phone, and many
-	others by webcast.  During a marathon-esque eight hour session, a
-	variety of development topics were discussed, including adding
-	inheritance to the KOBJ system, ports to new architectures,
-	adaptations of the toolchain for new architectures, the GEOM
-	extensible storage device framework, upcoming changes to the network
-	stack, TrustedBSD features, KSE, SMPng, and the release engineering
-	schedule.  This event was sponsored by DARPA and NAI Labs, with
-	webcasting provided by Joe Karthauser, bandwidth provided by Yahoo!.
-	Planning for future such events is now underway; a summary/transcript
-	of discussion may be found at the URL above.</p>
-    <hr /><h2><a name="FreeBSD-Package-building-Cluster" href="#FreeBSD-Package-building-Cluster" id="FreeBSD-Package-building-Cluster">FreeBSD Package-building Cluster</a></h2><p>
-	Contact:
-	  Kris
-	  Kennaway
-	 &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-      <p>Packages are built from the FreeBSD Ports Collection on a
-	cluster of i386 and alpha machines using scripts available in
-	/usr/ports/Tools/portbuild/.  Over the past few months I have
-	been cleaning up and extending these scripts to improve
-	efficiency and allow for greater flexibility in how package
-	builds are performed.  Major improvements so far have been:
-	cleaning up and modularizing the scripts to avoid code
-	duplication and reduce the need for ongoing maintenance;
-	optimizing the build process and making it much more robust
-	against client machine failure; and allowing package builds to
-	be restarted if they are interrupted.  The i386 package
-	cluster is currently running FreeBSD 5.0-CURRENT, and it has
-	proven to be a useful testing ground for exposing kernel bugs,
-	especially those which only manifest under system load.</p>
-
-      <p>Future plans include the ability to perform incremental
-	package rebuilds which only build packages that have changed
-	since the last run.  This will allow packages to be made
-	available on the FTP site within an hour or two of the CVS
-	commit to the ports collection.  We also hope to set up a
-	sparc64 package cluster in the near future, but this is
-	contingent on suitable hardware.</p>
-    <hr /><h2><a name="FreeBSD/KGI" href="#FreeBSD/KGI" id="FreeBSD/KGI">FreeBSD/KGI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="http://www.FreeBSD.org/~nsouch/ggiport.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="">http://www.FreeBSD.org/~nsouch/ggiport.html</a></td></tr></table><p>
-	Contact:
-          Nicholas
-
-          Souchu
-         &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-      <p> FreeBSD/KGI started last year after the port of GGI to VGL.
-        KGI (Kernel Graphic Interface) is a kernel infrastructure providing user
-        applications with access to hardware graphic resources (dma,
-        irqs, mmio). KGI is already available under Linux as a separate
-        project. The FreeBSD/KGI project aims at integrating KGI
-        in the FreeBSD kernel. Mostly a port for now, but optimized for
-        FreeBSD in the future. Currently FreeBSD/KGI is under development
-        and the code is only available for reading, compiling but not running.
-        More interesting are design hints found at the project URL.</p>
-
-    <hr /><h2><a name="GCC-3.1" href="#GCC-3.1" id="GCC-3.1">GCC 3.1</a></h2><p>
-	Contact:
-          David
-          O'Brien
-         &lt;<a href="mailto:obrien@FreeBSD.org">obrien@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of Thur May 9th, 2002 FreeBSD 5-CURRENT is now using a GCC 3.1
-	prerelease snapshot as the system C compiler.  At this time of
-	cutting over, the compiler is working well on i386, Alpha, Sparc64,
-	and IA-64 for building world.  There is a known problem with our
-	atomic ops on Alpha that prevents a GCC 3.1 built kernel from
-	booting.</p>
-
-      <p>Currently the C++ support libraries (libstdc++, et.al.) does not
-	build and thus prevents the system C++ compiler from being used.</p>
-    <hr /><h2><a name="GNOME-Project" href="#GNOME-Project" id="GNOME-Project">GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome" title="http://www.FreeBSD.org/gnome">FreeBSD GNOME Project homepage.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome" title="FreeBSD GNOME Project homepage.">http://www.FreeBSD.org/gnome</a></td></tr></table><p>
-	Contact:
-          Joe
-
-          Marcus
-         &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	</p>
-      <p>The GNOME project has seen quite a few changes lately.  For one,
-        the author of this update has recently been given "The Bit."
-        Joe Marcus Clarke now has CVS access, and is working primarily
-        on the GNOME project.  Joe has been closing a good deal of GNOME
-        PRs, as well as patching some of the existing GNOME 1.4
-        components.</p>
-
-      <p>The GNOME 2 porting effort continues on.  We have completed porting
-        of the GNOME 2.0 API, and are 75% complete on porting the full
-        GNOME 2.0 desktop.  When complete, GNOME 1.4 and GNOME 2.0 will
-        be co-resident in the ports tree.  Both APIs can be installed
-        concurrently in the same PREFIX, but the respective desktops
-        will remain mutually independent.  Maxim Sobolev is working
-        on adapting bsd.gnome.mk to handle both versions of the desktop
-        in an elegant fashion.</p>
-
-      <p>Not to be left out, the existing GNOME 1.4 components have received
-        numerous updates to keep them in sync with the stable distfiles
-        on gnome.org.  We have seen many "1.0" milestone releases including
-        the most recent AbiWord 1.0.0.  In the next few weeks, we will be
-        making sure all the GNOME 1.4 components build correct packages
-        on bento so that GNOME 1.4 will be on the 4.6-RELEASE CD.</p>
-    <hr /><h2><a name="IA64-Port" href="#IA64-Port" id="IA64-Port">IA64 Port</a></h2><p>
-	Contact:
-          Peter
-          Wemm
-         &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;
-	</p>
-
-      <p>IA64 has had a busy few months.  Aside from gcc, we are now fully
-	self hosting on IA64.  Doug Rabson has performed his magic and
-	implemented the execution of 32 bit i386 application binaries
-	although more work remains to be done to make ld-elf.so.1 happy
-	with the different underlying page size.  We have been using the
-	i386 perforce binary to do actual development work and submit from
-	the ia64 systems themselves.  Marcel Moolenaar has been working on
-	SMP and machine-check support.  We have been running SMP kernels
-	amazingly reliably on our development boxes for quite some time now.
-	syscons is now functional.  We have produced a self-booting
-	run-root-on-cdrom ISO image (idea taken from the sparc64 folks) that
-	has been used to manually self install an IA64 system from a blank
-	disk.  Aside from a few minor loose ends we now have complete 'make
-	world' functionality.  sysinstall works on ia64.  We plan on
-	producing a semi-respectable boot/install cdrom image shortly.</p>
-    <hr /><h2><a name="Improving-FreeBSD-Startup-Scripts" href="#Improving-FreeBSD-Startup-Scripts" id="Improving-FreeBSD-Startup-Scripts">Improving FreeBSD Startup Scripts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://home.pacbell.net/makonnen/rcng.html" title="http://home.pacbell.net/makonnen/rcng.html"></a></td><td>
-	    URL: <a href="http://home.pacbell.net/makonnen/rcng.html" title="">http://home.pacbell.net/makonnen/rcng.html</a></td></tr><tr><td><a href="http://groups.yahoo.com/group/FreeBSD-rc/" title="http://groups.yahoo.com/group/FreeBSD-rc/"></a></td><td>
-	    URL: <a href="http://groups.yahoo.com/group/FreeBSD-rc/" title="">http://groups.yahoo.com/group/FreeBSD-rc/</a></td></tr><tr><td><a href="http://www.mewburn.net/luke/bibliography.html" title="http://www.mewburn.net/luke/bibliography.html"></a></td><td>
-	    URL: <a href="http://www.mewburn.net/luke/bibliography.html" title="">http://www.mewburn.net/luke/bibliography.html</a></td></tr><tr><td><a href="http://www.netbsd.org/Documentation/rc/" title="http://www.netbsd.org/Documentation/rc/"></a></td><td>
-	    URL: <a href="http://www.netbsd.org/Documentation/rc/" title="">http://www.netbsd.org/Documentation/rc/</a></td></tr></table><p>
-	Contact:
-          Doug
-          Barton
-         &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-          Mike
-          Makonnen
-         &lt;<a href="mailto:makonnen@pacbell.net">makonnen@pacbell.net</a>&gt;
-	</p><p>
-	Contact:
-          Gordon
-          Tetlow
-         &lt;<a href="mailto:gordont@gnf.org">gordont@gnf.org</a>&gt;
-	</p>
-      <p>Mike Makonnen has done quite a bit of excellent work on porting the
-        scripts from FreeBSD into the NetBSD framework. The next step seems
-        to be to try to reduce the amount of diffs between our implementation
-        and the original set from NetBSD.</p>
-    <hr /><h2><a name="IPMI-Tools-for-FreeBSD" href="#IPMI-Tools-for-FreeBSD" id="IPMI-Tools-for-FreeBSD">IPMI Tools for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~dwhite/ipmi/" title="http://www.FreeBSD.org/~dwhite/ipmi/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~dwhite/ipmi/" title="">http://www.FreeBSD.org/~dwhite/ipmi/</a></td></tr></table><p>
-	Contact:
-          Doug
-
-          White
-         &lt;<a href="mailto:dwhite@FreeBSD.org">dwhite@FreeBSD.org</a>&gt;
-	</p>
-      <p>IPMI Tools for FreeBSD is a collection of C and Python
-	applications and modules for exploring the information available
-	via the Intelligent Platform Management Interface (IPMI), as
-	implemented on server motherboards by Intel and HP. IPMI is an
-	open standard with patent protection for adopters which defines
-	standard interfaces to on-board management hardware. The
-	management hardware consists of a CPU, sensors such as temperature
-	probes and fan speeds, and repositories such as the System Event
-	Log and Field-Replaceable Unit (FRU) inventory, and other system
-	information. </p>
-
-      <p>A basic set of tools was recently made available which uses the
-	KCS and SMIC system interfaces to retrieve the System Event Log,
-	FRU repository, and system sensors. Additional features are
-	currently under research. Suggestions for additional features and
-	programs are greatly appreciated. </p>
-
-    <hr /><h2><a name="jp.FreeBSD.org-daily-SNAPSHOTs-project" href="#jp.FreeBSD.org-daily-SNAPSHOTs-project" id="jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://snapshots.jp.FreeBSD.org/" title="http://snapshots.jp.FreeBSD.org/">Project Webpage</a></td><td>
-	    URL: <a href="http://snapshots.jp.FreeBSD.org/" title="Project Webpage">http://snapshots.jp.FreeBSD.org/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/snapshots/" title="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese)</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/snapshots/" title="Project Webpage (in Japanese)">http://www.jp.FreeBSD.org/snapshots/</a></td></tr></table><p>
-	Contact:
-          Makoto
-          Matsushita
-         &lt;<a href="mailto:matusita@jp.FreeBSD.org">matusita@jp.FreeBSD.org</a>&gt;
-	</p>
-      <p>There are several new topics, including: Source Code Tour is now
-	separated into kernel part and userland part, yet another snapshots
-	from RELENG_4_x branch (currently 4.5-RELEASE-p4), add several
-	packages including XFree86 4.x to installation CD-ROM, new
-	cdboot-only ISO image, fix breakage of duplex.iso, etc.  See also
-	the project webpage for more detail.  Also, I have a plan to add
-	FreeBSD/alpha distribution to this project -- stay tuned.</p>
-    <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project page both for users and developers (in Japanese)</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project page both for users and developers (in Japanese)">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-          Kazuo
-          Horikawa
-         &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-      <p>4.5-RELEASE Japanese manpage package, ja-man-doc-4.5.tgz, once
-	published with OpenSSH 2.3 (as reported by previous status
-	report) on January 31, is replaced with new package with OpenSSH
-	2.9 based manpages on March 3.  Since then, we have been
-	updating Japanese manpages for 4.6-RELEASE.  For new translation
-	and massive update, we have been making a lot of effort.</p>
-      <p>Continuing section 3 updating has 73% finished.</p>
-    <hr /><h2><a name="KAME" href="#KAME" id="KAME">KAME</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.kame.net/" title="http://www.kame.net/">KAME Project Home Page</a></td><td>
-	    URL: <a href="http://www.kame.net/" title="KAME Project Home Page">http://www.kame.net/</a></td></tr><tr><td><a href="http://www.kame.net/roadmap-2002.html" title="http://www.kame.net/roadmap-2002.html">KAME Project Roadmap</a></td><td>
-	    URL: <a href="http://www.kame.net/roadmap-2002.html" title="KAME Project Roadmap">http://www.kame.net/roadmap-2002.html</a></td></tr></table><p>
-	Contact:
-          Shinsuke
-          SUZUKI
-         &lt;<a href="mailto:suz@kame.net">suz@kame.net</a>&gt;
-	</p>
-      <p> KAME Project has been extended until March 2004, and we decided the project
-	roadmap for these two years.  The first one year is for implementation, and the
-	remaining year is for feedback of our results into other BSD projects (please refer
-	to the above URL for further detail).
-	Great change is lack of NAT-PT support due to a lack of human resource, although
-	KAME snap still contains it as it is.</p>
-
-      <p> SUZUKI Shinsuke (suz@kame.net) has begun working for KAME and FreeBSD merge task in
-	cooperation with Umemoto-san (ume@FreeBSD.org).
-	Some of KAME stuff (critical bug fix, newest ports for pim6sd and racoon, etc)
-	has been merged into 4-stable in this April.</p>
-    <hr /><h2><a name="KSE" href="#KSE" id="KSE">KSE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~julian/" title="http://www.FreeBSD.org/~julian/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~julian/" title="">http://www.FreeBSD.org/~julian/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/~jasone/kse/" title="http://www.FreeBSD.org/~jasone/kse/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jasone/kse/" title="">http://www.FreeBSD.org/~jasone/kse/</a></td></tr></table><p>
-	Contact:
-          Julian
-
-          Elischer
-         &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jonthan
-	  Mini
-	 &lt;<a href="mailto:mini@FreeBSD.org">mini@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KSE project had floundered due to lack of development
-        time for awhile, but has been picked up recently by
-        Jonathan Mini. Currently, the main focus is to prepare
-        the "milestone 3" code for inclusion into -CURRENT.</p>
-
-      <p>The project is still working towards "milestone 4"
-	(allowing threads from the same process to run on
-	multiple CPUs), which should be significantly easier
-	now due to work done by the SMPng project over the past
-	several months.</p>
-
-      <p>Help could be used in several areas of the project,
-	especially with porting the libc_r (pthreads) library
-	to KSE's threading model.</p>
-
-    <hr /><h2><a name="Libh" href="#Libh" id="Libh">Libh</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/libh.html" title="http://www.FreeBSD.org/projects/libh.html">Main project page.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/libh.html" title="Main project page.">http://www.FreeBSD.org/projects/libh.html</a></td></tr></table><p>
-	Contact:
-          Antoine
-          Beaupr&#351;
-         &lt;<a href="mailto:anarcat@anarcat.ath.cx">anarcat@anarcat.ath.cx</a>&gt;
-	<br />
-	Contact:
-          Alexander
-          Langer
-         &lt;<a href="mailto:alex@FreeBSD.org">alex@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Nathan
-          Ahlstrom
-         &lt;<a href="mailto:nra@FreeBSD.org">nra@FreeBSD.org</a>&gt;
-	</p>
-      <p>We now have a loadable mfsroot floppy. It contains just the
-	diskeditor (which is really a disk partitioner) which has been
-	enhanced and is probably in its final form. It's been geared
-	towards making the newfs(1) and mount(1) steps separate dialogs, so
-	it reduceed its complexity. A basic fstab class has been
-	implemented to manipulate /etc/fstab and mountpoint. This might
-	find a use outside libh, by the way. Libh package format is still
-	incomplete and somehow buggy, so it's my next target.</p>
-
-      <p>There is a API documentation effort underway with the help of
-	doxygen(1), so there's now more documentation for people that want
-	to get started with libh.</p>
-
-      <p>All this lead me to prepare the release of another alpha
-	preview of libh that will shortly be available in the ports
-	collection (0.2.2). Also, a new committer (okumoto) has joined the
-	project (as well as I) and he is currently working on cleaning up
-	the build system. It's been a few months without news, so this
-	probably seemed a bit long, but don't worry, we still need your
-	help to really get this going!</p>
-
-    <hr /><h2><a name="locking-up-pcb's-in-the-networking-stack" href="#locking-up-pcb's-in-the-networking-stack" id="locking-up-pcb's-in-the-networking-stack">locking up pcb's in the networking stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Jeffrey
-
-          Hsu
-         &lt;<a href="mailto:hsu@FreeBSD.org">hsu@FreeBSD.org</a>&gt;
-	</p>
-      <p>I've been mentoring someone on locking up the protocol control
-	blocks in the networking stack.  She has already finished TCP and
-	UDP and I'm currently reviewing the patch with her and going over
-	some networking lock order issues.  Locking up raw protocol
-	interface control blocks follows next.</p>
-
-    <hr /><h2><a name="Netgraph-ATM" href="#Netgraph-ATM" id="Netgraph-ATM">Netgraph ATM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html" title="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html">Introduction to NgAtm</a></td><td>
-	    URL: <a href="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html" title="Introduction to NgAtm">http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html</a></td></tr></table><p>
-	Contact:
-          Harti
-
-          Brandt
-         &lt;<a href="mailto:brandt@fokus.fhg.de">brandt@fokus.fhg.de</a>&gt;
-	</p>
-      <p>Version 1.1 for FreeBSD-current is now available. It includes
-        the SNMP-daemon package bsnmp, the driver package ngatmbase,
-        the UNI4.0 signaling package ngatmsig and the network emulation
-        package ngatmnet. NgAtm allows both to build applications running
-        directly on top of ATM and to use ATM-Forum LAN emulation to
-        use IP over ATM. Currently we are working on a simple switch module,
-        that implements the network side signaling and ILMI as well as
-        simple routing and call admission control.</p>
-    <hr /><h2><a name="Network-interface-cloning-and-modularity" href="#Network-interface-cloning-and-modularity" id="Network-interface-cloning-and-modularity">Network interface cloning and modularity</a></h2><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for stf(4), faith(4), and loopback interfaces has been
-	committed to current.  The stf and faith support has been MFC'd.
-	In current the API has changed to move unit allocation into the
-	generic cloning code reducing the amount of support code required
-	in each driver.  Code improvements to increase our API
-	compatibility with NetBSD will be committed soon along with cloning
-	support for discard interfaces and ppp(4) interfaces.</p>
-      <p>Thanks to <email>mux@FreeBSD.org</email> for the loopback support
-	and unit allocation cleanups.</p>
-    <hr /><h2><a name="New-mount(2)-API" href="#New-mount(2)-API" id="New-mount(2)-API">New mount(2) API</a></h2><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Maxime
-
-          Henrion
-         &lt;<a href="mailto:mux@FreeBSD.org">mux@FreeBSD.org</a>&gt;
-	</p>
-      <p>The patch for the new mount API has now been committed to the
-        tree.  Several filesystems also have been converted to this
-        new mount API, namely procfs, linprocfs, fdescfs and devfs.
-        I'm working on converting more filesystems to nmount, and
-        actually already have UFS done.  It has not been committed yet
-        to avoid conflicting with the UFS2 work, but it should hit the
-        tree soon.  Manpages are still missing at the moment because
-        I had to modify the API slightly.  I hope to have them done
-        soon now.</p>
-    <hr /><h2><a name="NEWCARD" href="#NEWCARD" id="NEWCARD">NEWCARD</a></h2><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>NEWCARD support tried to merge CardBus functions with PCI
-	functions, but that failed to properly route interrupts.  A
-	branch for the merge was created and will be merged into the
-	main line at a later date.  Too many other things going on in my
-	life to make much progress.</p>
-    <hr /><h2><a name="OpenSSH" href="#OpenSSH" id="OpenSSH">OpenSSH</a></h2><p>
-	Contact:
-          Dag-Erling
-	  Sm&#370;rgrav
-         &lt;<a href="mailto:des@FreeBSD.org">des@FreeBSD.org</a>&gt;
-	</p>
-      <p>OpenSSH has been upgraded to 3.1, and the kinks seem to have
-        been worked out by now.  OpenSSH will now use PAM for both ssh1
-        and ssh2 authentication.</p>
-    <hr /><h2><a name="PAM" href="#PAM" id="PAM">PAM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~des/pam/pam-2002-03.html" title="http://people.FreeBSD.org/~des/pam/pam-2002-03.html">March 2002 PAM activity report.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~des/pam/pam-2002-03.html" title="March 2002 PAM activity report.">http://people.FreeBSD.org/~des/pam/pam-2002-03.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~des/pam/pam-2002-04.html" title="http://people.FreeBSD.org/~des/pam/pam-2002-04.html">April 2002 PAM activity report.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~des/pam/pam-2002-04.html" title="April 2002 PAM activity report.">http://people.FreeBSD.org/~des/pam/pam-2002-04.html</a></td></tr></table><p>
-	Contact:
-          Mark
-          Murray
-         &lt;<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Dag-Erling
-	  Sm&#370;rgrav
-         &lt;<a href="mailto:des@FreeBSD.org">des@FreeBSD.org</a>&gt;
-	</p>
-      <p>The painful parts are now completed, with all authentication-
-	related utilities converted to PAM (except for those cases where
-	it doesn't make sense, like Kerberos- or OPIE-specific
-	commands).  OpenPAM is complete (except for a few missing man
-	pages) and seems to work well.</p>
-
-      <p>For more details, see the activity reports linked to above.</p>
-    <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeamland.net/~benno/powerpc-boot.txt" title="http://jeamland.net/~benno/powerpc-boot.txt">Current boot messages.</a></td><td>
-	    URL: <a href="http://jeamland.net/~benno/powerpc-boot.txt" title="Current boot messages.">http://jeamland.net/~benno/powerpc-boot.txt</a></td></tr></table><p>
-	Contact:
-          Benno
-
-          Rice
-         &lt;<a href="mailto:benno@FreeBSD.org">benno@FreeBSD.org</a>&gt;
-	</p>
-      <p>The PowerPC port is moving ahead.  It can now mount a root file system
-	and exec init, but fails when trying to map init's text segment in.  I'm
-	hoping to have it starting my fake "Hello, world!" init soon, after which
-	I plan to try and get some libc bits in place so that I can build /bin
-	and /sbin and try to get to actual single-user.</p>
-    <hr /><h2><a name="ppp-RADIUS/MS-CHAP-support" href="#ppp-RADIUS/MS-CHAP-support" id="ppp-RADIUS/MS-CHAP-support">ppp RADIUS/MS-CHAP support</a></h2><p>
-	Contact:
-          Brian
-
-          Somers
-         &lt;<a href="mailto:brian@FreeBSD.org">brian@FreeBSD.org</a>&gt;
-	</p>
-      <p>libradius now supports RADIUS vendor attribute extensions and
-	user-ppp is now capable of doing MS-CHAP authentication via a RADIUS
-	server.  A new net/freeradius port has been created for support of
-	MS-CHAP in a RADIUS server.</p>
-
-      <p>MS-CHAPv2 support will be added soon.</p>
-
-      <p>The work is sponsored by Monzoon.</p>
-    <hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-          Release Engineering
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The release engineering team released FreeBSD <a href="http://www.FreeBSD.org/releases/5.0R/DP1/announce.html" shape="rect">5.0-DP1</a>
-	on 8 April 2002.  This Developer Preview gives developers and
-	other interested parties a chance to help test some of the new
-	features to appear in 5.0-RELEASE.  This distribution has known
-	bugs and areas of instability, and should only be used for
-	(non-production) testing and development.</p>
-
-      <p>The next releases of FreeBSD will be 4.6-RELEASE (scheduled for
-	1 June 2002) and 5.0-DP2 (scheduled for 25 June 2002).
-	Information on the release schedules and more can be found on
-	the team's new area on the FreeBSD Web site (see the URL
-	above).</p>
-
-      <p>Finally, the team has gained two new members: Brian Somers and
-	Bruce A. Mah.</p>
-
-    <hr /><h2><a name="SMPng" href="#SMPng" id="SMPng">SMPng</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The SMPng project has been picking up steam in the last few
-        months thankfully.  In February, Seigo Tanimura-san committed
-        the first round of process group and session locking.  Alfred
-        Perlstein also added locking to most of the pipe
-        implementation.  In March, Alfred fixed several problems with
-        the locking for select() and pushed down Giant some in several
-        system calls.  Andrew Reiter added locking for kernel module
-        metadata, and Jeff Roberson wrote a new SMP-friendly slab
-        allocator to replace both the zone allocator and the in-kernel
-        malloc().  The use of the critical section API was cleaned up
-        to not be abused as replacements for disabling and enabling
-        interrupts.  Also, Matt Dillon optimized the MD portion of the
-        critical section code on the i386 architecture.  Several other
-        subsystems were also locked in April as well.  See the SMPng
-        website and todo list for more details.</p>
-
-      <p>Some of the current works in progress include locking for the
-        kernel linker by Andrew Reiter and light-weight interrupt
-        threads for the i386 by Bosko Milekic.  Seigo Tanimura-san,
-        Alfred Perlstein, and Jeffrey Hsu are also working on locking
-        down various pieces of the networking stack.  Alan Cox has
-        started working on fixing the existing locking in the VM
-        subsystem and moving bits of it out from under Giant.  John
-        Baldwin has written an implementation of turnstiles as well as
-        adaptive mutexes in the jhb_lock Perforce branch.  The
-        adaptive mutexes appear to be stable on i386, alpha, and
-        sparc64, but the turnstile code still contains several tricky
-        lock order reversals.  John also plans to commit the
-        p_canfoo() API change to use td_ucred in the very near future
-        and then finish the task of making ktrace(4) use a worker
-        thread.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD main web page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD main web page">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Reiter
-         &lt;<a href="mailto:arr@FreeBSD.org">arr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  TrustedBSD Audit Mailing List
-	 &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <p>Over the past couple of months, progress has pretty much stopped
-	until very recently.  The past few changes to the audit code were
-	update the usage of zones to UMA zones, cleanup some old cruft,
-	and start toying with the idea of having an audit write thread
-	implemented as an ithd.  The next step is to decide two realistic
-	approaches to the where the records will be dumped -- whether that
-	is to a local disk or fed up to userland and then dealt with.
-	After that, the goal will be to expand the number of events that
-	are being audited, while also working in some performance testing
-	procedures.  I will be posting to trustedbsd-audit about the recent
-	changes shortly.</p>
-    <hr /><h2><a name="TrustedBSD-MAC" href="#TrustedBSD-MAC" id="TrustedBSD-MAC">TrustedBSD MAC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD main web page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD main web page">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  TrustedBSD Discussion Mailing List
-	 &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>Over the last three months, there has been a lot of activity
-	in the TrustedBSD MAC tree.  An initial commit of the SEBSD
-	code (NSA FLASK and SELinux implementation) was made; many
-	MAC policies previously linked directly to the kernel via
-	kernel options were moved to kernel modules; the flexibility
-	of the framework was improved relating to the life cycle of
-	object labels; additional labeling and access control hooks
-	were introduced; new policies were introduced to demonstrate
-	the flexibility of the framework (including a cleanup of
-	inter-process authorization, additional VFS hooks, improved
-	support for multilabel filesystems, network booting, IPv6,
-	IPsec, support for "peer" labels on stream sockets).
-	Current modules include Biba integrity policy, MLS
-	confidentiality policy, Type Enforcement, "BSD Extended"
-	(permitting firewall-like rulesets for filesystem protection),
-	"ifoff" (limit interface communication by policy),
-	mac_seeotheruids (limit visibility of processes/etc of other
-	users), "babyaudit" (a simple audit implementation), and
-	SEBSD (FLASK/SELinux port).</p>
-      <p>Over the next month, a final move to completely dynamic
-	labeling will be made, permitting policies to introduce new
-	state relating to process credentials, vnodes, sockets,
-	mounts, interfaces, and mbufs at run-time, allowing a broad
-	range of flexible label-driven policies to be developed.
-	In addition, application APIs will be re-designed and
-	re-implemented so as to better support a fully dynamic
-	policy framework.  We plan to make an initial prototype
-	patchset available for review in June, with the intent of
-	committing that patchset in mid-June.</p>
-      <p>Updated prototype code may be retrieved from the TrustedBSD
-	CVS trees on cvsup10.FreeBSD.org.</p>
-    <hr /><h2><a name="UMA" href="#UMA" id="UMA">UMA</a></h2><p>
-	Contact:
-	  Jeff
-	  Roberson
-	 &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD's new kernel memory allocator has been committed to
-	5.0.  UMA is a slabs derived allocator that supports memory
-	reclaiming, object caching, type stable storage, and per CPU
-	free lists for optimal SMP performance.  It has both a
-	malloc(9) interface and a zone style interface for specific
-	object types. uma(9) will be available shortly.</p>
-    <hr /><h2><a name="Universal-Disk-Filesystem-for-FreeBSD" href="#Universal-Disk-Filesystem-for-FreeBSD" id="Universal-Disk-Filesystem-for-FreeBSD">Universal Disk Filesystem for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~scottl/udf" title="http://people.FreeBSD.org/~scottl/udf">UDF Homepage.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~scottl/udf" title="UDF Homepage.">http://people.FreeBSD.org/~scottl/udf</a></td></tr></table><p>
-	Contact:
-          Scott
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Jeroen
-          Ruigrok
-         &lt;<a href="mailto:asmodai@wxs.nl">asmodai@wxs.nl</a>&gt;
-	</p>
-      <p>Read-only support for UDF filesystems was checked into the 5-CURRENT
-        branch in April.  Backporting for 4-STABLE is being conducted by
-        Jeroen.  The next phase is to write a newfs_udf, then move on to
-        adding write support to the filesystem.  I'm still looking for a
-        volunteer to handle read and write support for write-once media
-        (e.g. CD-R).</p>
-    <hr /><h2><a name="Wi-Hostap" href="#Wi-Hostap" id="Wi-Hostap">Wi Hostap</a></h2><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on the host access point support for the Prism2 and
-        Prism2.5 based wireless cards has been integrated into the
-        kernel.  This work is largely based on Thomas Skibo's initial
-        implementation.</p>
-    <hr /><h2><a name="Zero-Copy-Sockets" href="#Zero-Copy-Sockets" id="Zero-Copy-Sockets">Zero Copy Sockets</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~ken/zero_copy/" title="http://people.FreeBSD.org/~ken/zero_copy/">Zero copy patches and information.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~ken/zero_copy/" title="Zero copy patches and information.">http://people.FreeBSD.org/~ken/zero_copy/</a></td></tr></table><p>
-	Contact:
-          Ken
-
-          Merry
-         &lt;<a href="mailto:ken@FreeBSD.org">ken@FreeBSD.org</a>&gt;
-	</p>
-      <p> I have released a new zero copy sockets snapshot, the first since
-        November, 2000.  The code has been ported up to the latest
-        -current, and the jumbo code now has mutex protection.  Also, zero
-        copy send and receive can be selectively turned on and off via sysctl
-        to make it easier to compare performance with and without zero copy.
-        Reviews and comments are welcome.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2002-05-2002-06.html b/website/content/en/status/report-2002-05-2002-06.html
deleted file mode 100644
index 8d5cbef8f8..0000000000
--- a/website/content/en/status/report-2002-05-2002-06.html
+++ /dev/null
@@ -1,1166 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>May and June were remarkably busy months for the FreeBSD Project--
-      FreeBSD developers met in Monterey, CA in June for FreeBSD
-      Developer Summit III to discuss strategy for the FreeBSD 5.0
-      release later this year, for the USENIX Annual Technical
-      conference and for the FreeBSD BoF.  Substantial technical progress
-      was made on FreeBSD 5.0, and FreeBSD 4.6-RELEASE was cut on the
-      RELENG_4 branch in June.</p><p>The remainder of the summer will continue to be busy.  Final
-      components and features for 5.0-RELEASE will go into the tree,
-      and the development direction will change from new features
-      to stability, performance, and production-readiness.  With
-      additional 5.0 development previews late in the summer, we
-      hope to broaden the tester base for the -CURRENT branch,
-      and start to get early adopters digging out any potential
-      problems in their test environments.  I encourage both FreeBSD
-      Developers and FreeBSD Users to give 5.0-DP2 a spin (on a machine
-      without critical data!) and let us know how it goes.  The more
-      testing that happens before the release, the less fixing we have
-      to do afterwards!</p><p>Robert Watson</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph implementation)</a></li><li><a href="#BSDCon-2003">BSDCon 2003</a></li><li><a href="#Fast-IPSEC-Status">Fast IPSEC Status</a></li><li><a href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></li><li><a href="#FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#FreeBSD-Security-Officer-Team">FreeBSD Security Officer Team</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#FreeBSD/KGI-Status-Report">FreeBSD/KGI Status Report</a></li><li><a href="#GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></li><li><a href="#Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></li><li><a href="#Improving-FreeBSD-Startup-Scripts">Improving FreeBSD Startup Scripts</a></li><li><a href="#IP-Routing-Table-Replacement">IP Routing Table Replacement</a></li><li><a href="#ipfw2">ipfw2</a></li><li><a href="#jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KAME-Project">KAME Project</a></li><li><a href="#KSE-(Kernel-schedulable-Entity)-thread-support">KSE (Kernel schedulable Entity) thread support </a></li><li><a href="#Libh-Status-Report">Libh Status Report</a></li><li><a href="#Lightweight-Interrupt-Scheduling">Lightweight Interrupt Scheduling</a></li><li><a href="#locking-up-pcb's-in-the-networking-stack">locking up pcb's in the networking stack</a></li><li><a href="#mb_alloc-updates">mb_alloc updates</a></li><li><a href="#NATD-rewrite">NATD rewrite</a></li><li><a href="#NEWCARD">NEWCARD</a></li><li><a href="#OLDCARD">OLDCARD</a></li><li><a href="#OpenOffice.org-for-FreeBSD">OpenOffice.org for FreeBSD</a></li><li><a href="#Single-UNIX-Specification-conformant-SCCS-suite">Single UNIX Specification conformant SCCS suite</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#TCP-Hostcache">TCP Hostcache</a></li><li><a href="#TCP-Metrics-Measurement">TCP Metrics Measurement</a></li><li><a href="#TIRPC-port-for-BSD-sockets">TIRPC port for BSD sockets</a></li><li><a href="#TrustedBSD-MAC">TrustedBSD MAC</a></li><li><a href="#UFS2---Extended-attribute-and-large-size-support-for-UFS">UFS2 - Extended attribute and large size support for UFS</a></li><li><a href="#Userland-Regression-Tests">Userland Regression Tests</a></li><li><a href="#Zero-Copy-Sockets-status-report">Zero Copy Sockets status report</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph implementation)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	Maksim
-	Yevmenkin
-       &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-
-    <p>
-Not much to report. Another engineering snapshot is available
-for download at
-http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020709.tar.gz.
-If anyone has Bluetooth hardware and spare time please join in and help
-me
-with testing.
-    </p>
-
-    <p>
-This snapshot includes basic support for USB devices and manual pages.
-The HCI layer now has support for multiple control hooks. All HCI
-transport
-drivers (H4, BT3C and UBT) has been changed to provide consistent
-interface
-to the rest of the world. Some userspace utilities have been changed as
-well.
-    </p>
-
-    <p>
-Still no support for RFCOMM (Serial port emulation over Bluetooth link)
-and
-SDP (Service Discovery Protocol). Several design flaws have been
-discovered
-and it might take some time to resolve these issues.
-    </p>
-  <hr /><h2><a name="BSDCon-2003" href="#BSDCon-2003" id="BSDCon-2003">BSDCon 2003</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.usenix.org/events/bsdcon03/cfp/" title="http://www.usenix.org/events/bsdcon03/cfp/">Call for papers</a></td><td>
-	    URL: <a href="http://www.usenix.org/events/bsdcon03/cfp/" title="Call for papers">http://www.usenix.org/events/bsdcon03/cfp/</a></td></tr></table><p>
-	Contact:
-	  Gregory
-	  Shapiro
-	 &lt;<a href="mailto:gshapiro@FreeBSD.org">gshapiro@FreeBSD.org</a>&gt;
-	</p>
-<p>The BSDCon 2003 Program Committee invites you to contribute original
-and innovative papers on topics related to BSD-derived systems and
-the Open Source world. Topics of interest include but are not limited
-to:
-</p>
-<ul>
-      <li> Embedded BSD application development and deployment</li>
-      <li> Real world experiences using BSD systems</li>
-      <li> Using BSD in a mixed OS environment</li>
-      <li> Comparison with non-BSD operating systems; technical,
-	practical, licensing (GPL vs. BSD)</li>
-      <li> Tracking open source development on non-BSD systems</li>
-      <li> BSD on the desktop</li>
-      <li> I/O subsystem and device driver development</li>
-      <li> SMP and kernel threads</li>
-      <li> Kernel enhancements</li>
-      <li> Internet and networking services</li>
-      <li> Security</li>
-      <li> Performance analysis and tuning</li>
-      <li> System administration</li>
-      <li> Future of BSD</li>
-</ul>
-<p> Submissions in the form of extended abstracts are due by April 1, 2003.
-Be sure to review the extended abstract expectations before submitting.
-Selection will be based on the quality of the written submission and
-whether the work is of interest to the community.  </p>
-<p> We look forward to receiving your submissions!  </p>
-<hr /><h2><a name="Fast-IPSEC-Status" href="#Fast-IPSEC-Status" id="Fast-IPSEC-Status">Fast IPSEC Status</a></h2><p>
-	Contact:
-  Sam
-  Leffler
-   &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-  <p>The main goal of this project is to modify the IPSEC protocols to use
-the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). A
-secondary goal is to do general performance tuning of the IPSEC
-protocols.</p>
- <p>Basic functionality is operational for IPv4 protocols. IPv6 support is
-coded but not yet tested. Hardware assisted cryptographic operations are
-working with good performance improvements. Operation with software-based
-cryptographic calculations appears to be at least as good as the existing
-implementation.  Numerous opportunities for performance improvements have
-been identified.</p>
-  <p>This work is currently being done in the -stable tree.  A port to
-the -current tree is about to start.</p>
-  <hr /><h2><a name="FreeBSD-C99-&amp;-POSIX-Conformance-Project" href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project" id="FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/c99/" title="http://www.FreeBSD.org/projects/c99/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/c99/" title="">http://www.FreeBSD.org/projects/c99/</a></td></tr></table><p>
-	Contact:
-	Mike
-
-	Barcroft
-       &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	FreeBSD-Standards Mailing List
-       &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-    <p>Since the last status report, the following utilities have been
-      brought up to conformance (at least to some degree) with POSIX.1-2001,
-      they include: asa(1), cd(1), compress(1), ctags(1), ls(1), newgrp(1),
-      nice(1), od(1), pathchk(1), renice(1), tabs(1), tr(1), uniq(1), wc(1),
-      and who(1).  In addition, development is taking place on bringing the
-      BSD SCCS suite up to date with newer standards.</p>
-
-    <p>On the API front, printf(9) has been given support for the `j' and
-      'n' flags, waitpid(2) now supports the WCONTINUED option, and an
-      implementation of fstatvfs() and statvfs() has been committed.  An
-      implementation of utmpx is in progress, which has an aim to address
-      some of the major problems with the current utmp.  Several headers
-      have been brought up to conformance with POSIX.1-2001, they include:
-      &lt;netinet/in.h&gt;, &lt;pwd.h&gt;, &lt;sys/statvfs.h&gt;, and
-      &lt;sys/wait.h&gt;.</p>
-  <hr /><h2><a name="FreeBSD-GNOME-Project" href="#FreeBSD-GNOME-Project" id="FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Homepage.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project Homepage.">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-	Joe
-
-	Marcus
-       &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Maxim
-
-	Sobolev
-       &lt;<a href="mailto:sobomax@FreeBSD.org">sobomax@FreeBSD.org</a>&gt;
-	</p>
-    <p>Things are going well with the FreeBSD GNOME Project.  We have just
-      finished porting the GNOME 2.0 Final development platform and desktop
-      to FreeBSD!  We hope to be able to make GNOME 2.0 the default for
-      5.0-DP2 and 4.7-RELEASE.  In the meantime, we're working to port more
-      GNOME 2.0 applications.</p>
-
-    <p>In order to allow GNOME 1.4.1 applications to work with GNOME 2.0,
-      we are revamping the GNOME porting infrastructure.  GNOME 1.4.1 based
-      ports are being converted to use the new GNOMENG porting structure.
-      The specifics of this new system will be written up in the GNOME
-      porting guide found on the FreeBSD GNOME project homepage.</p>
-
-  <hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java/" title="http://www.FreeBSD.org/java/">FreeBSD Java Project</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java/" title="FreeBSD Java Project">http://www.FreeBSD.org/java/</a></td></tr></table><p>
-	Contact:
-	Greg
-	Lewis
-       &lt;<a href="mailto:glewis@FreeBSD.org">glewis@FreeBSD.org</a>&gt;
-	</p>
-    <p>
-    The BSD Java Porting Team has been making slow but steady progress
-    on a number of fronts in the last few months.  Unfortunately most
-    of this has occurred behind the scenes, meaning this is a good
-    opportunity to bring the community up to date.
-    <ul>
-       <li>Bill Huey has gotten the Java HotSpot Virtual Machine up and
-	   running on FreeBSD!  While dubbing the code of alpha quality,
-	   Bill has been working hard and is able to run major examples
-	   such as the Java 2D demo.  This code has hit the repository
-	   and will soon be available.</li>
-       <li>The port of the 1.4 J2SDK has commenced.  The first commits
-	   have gone into the tree, although a first patchset is a
-	   way off yet.</li>
-       <li>Progress continues with the TCK compliance testing.  The
-	   current status has the JDK down to 19 compiler failures
-	   and 183 runtime failures.  As we edge closer to compliance
-	   its hoped that example code will be released to allow the
-	   community to pull together through the final few bugs.</li>
-       <li>A new patchset for JDK 1.3.1 is imminent.  This patchset
-	   will include HotSpot for the first time.</li>
-    </ul>
-    </p>
-  <hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng" title="http://www.FreeBSD.org/releng"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng" title="">http://www.FreeBSD.org/releng</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-
-    <p>Over the past few months the FreeBSD Release Engineering Team
-      oversaw a release process that culminated in the release of
-      FreeBSD 4.6 for the i386 and Alpha architectures on June 15.
-      The RE team is currently working concurrently on FreeBSD 4.6.1
-      and 5.0 DP2.  4.6.1 is a minor point release with an updated SSH
-      and BIND, fixes for some of the reported ata(4) problems, and
-      assorted security enhancements that will be detailed in the
-      release notes.  The release engineering activities for 4.6.1 are
-      taking place on the RELENG_4_6 branch in CVS, while the work on
-      5.0 DP2 is taking place in Perforce so as not to disturb ongoing
-      -CURRENT development.  We are still committed to FreeBSD 5.0 on
-      or around November 15, 2002.  For more information about
-      upcoming release schedules, please see our website above.  The
-      RE team would like to thank Sentex Communications for providing
-      the release builders with access to a fast i386 build machine.
-      Compaq also donated a couple of fast Alpha build machines to the
-      project.</p>
-
-  <hr /><h2><a name="FreeBSD-Security-Officer-Team" href="#FreeBSD-Security-Officer-Team" id="FreeBSD-Security-Officer-Team">FreeBSD Security Officer Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/security" title="http://www.FreeBSD.org/security"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/security" title="">http://www.FreeBSD.org/security</a></td></tr></table><p>
-	Contact:
-	Jacques
-
-	Vidrine
-       &lt;<a href="mailto:nectar@FreeBSD.org">nectar@FreeBSD.org</a>&gt;
-	</p>
-
-  <p>After an outstanding job serving the project as Security Officer
-  for over a year, Kris stepped down in January in order to focus more
-  of his time pursuing his PhD.  I offered to attempt to fill the vacant
-  role.</p>
-
-  <p>This is the first report by the SO Team.  Notable events since
-  the beginning of 2002 follow.</p>
-
-  <p>28 FreeBSD Security Advisories have been issued, 16 of which
-  were regarding the base system.  Of those sixteen, 8 affected only
-  FreeBSD.</p>
-
-  <p>FreeBSD Security Notices were introduced, and four have been
-  issued so far.  The Security Notices cover issues that are not
-  regarded as critical enough to warrant a Security Advisory.  So far
-  only Ports Collection issues (i.e. vulnerabilities in optional 3rd
-  party packages) have been reported in Security Notices.  The first
-  four Security Notices covered 53 individual issues.</p>
-
-  <p>Issues reported to the SO team are now being tracked using a
-  RequestTracker ticket database.</p>
-
-  <p>The SO team has undergone membership changes, as well as some
-  changes in internal organization.  The membership and organization
-  has also been made publicly visible on the FreeBSD Security Officer
-  web page.</p>
-
-  <hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~peter/ia64/" title="http://people.FreeBSD.org/~peter/ia64/">IA64 project updates and information.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~peter/ia64/" title="IA64 project updates and information.">http://people.FreeBSD.org/~peter/ia64/</a></td></tr></table><p>
-	Contact:
-	Peter
-	Wemm
-       &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;
-	</p>
-    <p>IA64 has been progressing slowly.  We have access to a prototype
-      4-way Itaninum2 system from Intel and have managed to get it up and
-      running to the point of being able to access disk and network with
-      SMP enabled.  We have a big problem with ACPI2.0 and PCI routing
-      table entries behind pci-pci bridges with no short-term solution
-      in sight.  Various WIP items have been committed to CVS, namely
-      more complete support for executing 32bit i386 binaries as well
-      as Marcel Moolenaar's prototype EFI GPT tools.</p>
-  <hr /><h2><a name="FreeBSD/KGI-Status-Report" href="#FreeBSD/KGI-Status-Report" id="FreeBSD/KGI-Status-Report">FreeBSD/KGI Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="http://www.FreeBSD.org/~nsouch/ggiport.html">Project URL</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="Project URL">http://www.FreeBSD.org/~nsouch/ggiport.html</a></td></tr></table><p>
-	Contact:
-	Nicholas
-
-	Souchu
-       &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-    <p>Progression is slow, but the effort is maintained. Most of fb over KGI has been
-	written in parallel with a KGI display driver based on fb.
-	DDC/DDC2 is being discussed for Plug &amp; Play monitor support. KGI aims at providing
-	a generic OS independent interface which would take advantage of FreeBSD I2C (iic(4))
-	infrastructure.
-	</p>
-
-  <hr /><h2><a name="GEOM---generalized-block-storage-manipulation" href="#GEOM---generalized-block-storage-manipulation" id="GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~phk/Geom/" title="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~phk/Geom/" title="Old concept paper here.">http://www.FreeBSD.org/~phk/Geom/</a></td></tr></table><p>
-	Contact:
-	Poul-Henning
-
-	Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-    <p>
-	The GEOM code has gotten so far that it beats our current code
-	in some areas while still lacking in others.  The goal is for
-	GEOM to be the default in 5.0-RELEASE.
-    </p>
-    <p>
-	Currently work on a cryptographic module which should be able
-	to protect a diskpartition from practically any sort of attack
-	is progressing.
-    </p>
-
-  <hr /><h2><a name="Hardware-Crypto-Support-Status" href="#Hardware-Crypto-Support-Status" id="Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></h2><p>
-	Contact:
-  Sam
-  Leffler
-   &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-  <p>The goal of this project is to import the OpenBSD kernel-level crypto
-subsystem. This facility provides kernel- and user-level access to hardware
-crypto devices for the calculation of cryptographic hashes, ciphers, and
-public key operations. The main clients of this facility are the kernel RNG
-(/dev/random), network protocols (e.g. IPSEC), and OpenSSL (through the
-/dev/crypto device).</p>
-  <p>The software has been available as a patch against the -stable tree for
-about six months. The core crypto support is tested, including device
-drivers for the Hifn 7951, and Broadcom 5805, 5820, and 5821 parts.  Recent
-work has concentrated on fixing device driver bugs, fixing support for Hifn
-7811 parts, adding support for public key operations, and adding
-flow-control between the crypto layer and device drivers. Future work
-includes porting this facility to the -current tree.</p>
-  <hr /><h2><a name="Improving-FreeBSD-Startup-Scripts" href="#Improving-FreeBSD-Startup-Scripts" id="Improving-FreeBSD-Startup-Scripts">Improving FreeBSD Startup Scripts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://groups.yahoo.com/group/FreeBSD-rc/links/" title="http://groups.yahoo.com/group/FreeBSD-rc/links/">The Yahoo! group site for discussion of this project</a></td><td>
-	    URL: <a href="http://groups.yahoo.com/group/FreeBSD-rc/links/" title="The Yahoo! group site for discussion of this project">http://groups.yahoo.com/group/FreeBSD-rc/links/</a></td></tr></table><p>
-	Contact:
-	Doug
-	Barton
-       &lt;<a href="mailto:DougB@FreeBSD.org">DougB@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-	Mike
-	Makonnen
-       &lt;<a href="mailto:makonnen@pacbell.net">makonnen@pacbell.net</a>&gt;
-	</p><p>
-	Contact:
-	Gordon
-	Tetlow
-       &lt;<a href="mailto:gordont@FreeBSD.org">gordont@FreeBSD.org</a>&gt;
-	</p>
-    <p>We are making excellent progress. There is a fully functioning
-    implementation imported to -current now. We need as many people as
-    possible to rc_ng equal to YES in /etc/rc.conf.</p>
-    <p>The next step is to set the default to YES, which we plan to do
-    before DP 2.</p>
-  <hr /><h2><a name="IP-Routing-Table-Replacement" href="#IP-Routing-Table-Replacement" id="IP-Routing-Table-Replacement">IP Routing Table Replacement</a></h2><p>
-	Contact:
- Andre
- Oppermann
-  &lt;<a href="mailto:oppermann@pipeline.ch">oppermann@pipeline.ch</a>&gt;
-	<br />
-	Contact:
- Claudio
- Jeker
-  &lt;<a href="mailto:jeker@n-r-g.com">jeker@n-r-g.com</a>&gt;
-	</p>
- <p>The current Patricia Trie routing table in BSD UNIX is not very
- efficient and wastes an enormous amount of space for every node (more
- than 256 bytes) (A full Internet view of 110k routes takes 33 MByte
- of KVM). Another problem are pointers from and to everywhere
- in the routing table. This makes replacing the table very hard and
- also significantly increases the table maintenance burden (for example
- for some kinds of updates the entire PCB has to be searched linearly).
- Also this is a heavy burden for SMP locking. The rewrite focuses on
- untangling the pointer mess, making the routing table replaceable
- and providing a more IP optimized table (5 MByte for 110k routes).
- Other new options include policy routing and some structural alignments
- in the network stack for clarity, simplicity and flexibility.</p>
- <p>The rewritten IP routing table will be ready for committing in
- October.</p>
-<hr /><h2><a name="ipfw2" href="#ipfw2" id="ipfw2">ipfw2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.iet.unipi.it/~luigi/" title="http://www.iet.unipi.it/~luigi/"></a></td><td>
-	    URL: <a href="http://www.iet.unipi.it/~luigi/" title="">http://www.iet.unipi.it/~luigi/</a></td></tr></table><p>
-	Contact:
-	Luigi
-
-	Rizzo
-       &lt;<a href="mailto:luigi@FreeBSD.org">luigi@FreeBSD.org</a>&gt;
-	</p>
-    <p>In summer 2002 the native FreeBSD firewall has been completely
-      rewritten in a form that uses BPF-like instructions
-      to perform packet matching in a more effective way. The external
-      user interface is completely backward compatible, though you can
-      make use of some newer
-      match patterns (e.g. to handle sparse sets of IP addresses) which
-      can dramatically simplify the writing of ruleset (and speed up
-      their processing).
-      The new firewall, called ipfw2, is much faster and easier to
-      extend than the old one. It has been already included in
-      FreeBSD-CURRENT, and patches for FreeBSD-STABLE are available
-      from the author.
-      </p>
-
-  <hr /><h2><a name="jp.FreeBSD.org-daily-SNAPSHOTs-project" href="#jp.FreeBSD.org-daily-SNAPSHOTs-project" id="jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://snapshots.jp.FreeBSD.org/" title="http://snapshots.jp.FreeBSD.org/">Project Webpage</a></td><td>
-	    URL: <a href="http://snapshots.jp.FreeBSD.org/" title="Project Webpage">http://snapshots.jp.FreeBSD.org/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/snapshots/" title="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese )</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/snapshots/" title="Project Webpage (in Japanese )">http://www.jp.FreeBSD.org/snapshots/</a></td></tr><tr><td><a href="http://snapshots.jp.FreeBSD.org:8021" title="http://snapshots.jp.FreeBSD.org:8021">SNAPSHOTs anonftp area on the web</a></td><td>
-	    URL: <a href="http://snapshots.jp.FreeBSD.org:8021" title="SNAPSHOTs anonftp area on the web">http://snapshots.jp.FreeBSD.org:8021</a></td></tr><tr><td><a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD/releases/i386/" title="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD/releases/i386/">Release branch snapshots for FreeBSD/i386</a></td><td>
-	    URL: <a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD/releases/i386/" title="Release branch snapshots for FreeBSD/i386">ftp://daemon.jp.FreeBSD.org/pub/FreeBSD/releases/i386/</a></td></tr></table><p>
-	Contact:
-    Makoto
-    Matsushita
-    &lt;<a href="mailto:matusita@jp.FreeBSD.org">matusita@jp.FreeBSD.org</a>&gt;
-	</p>
-  <p>
-  I spent busy days in last two months, many new topics are emerged
-  from the project.  We now support FreeBSD/alpha 5-current
-  distribution by cross-compiling on the x86 PC.  Anonymous ftp area
-  is now exported to the yet another web server.  Our release branch
-  snapshots are relocated to daemon.jp.FreeBSD.org because of our
-  CPU/network bandwidth problem.
-  </p>
-  <p>
-  I'm seriously considering to solve the lack of CPU and network
-  resources for the project's future evolution.  Maybe the bandwidth
-  problem can be resolved (several bandwidth offers have been received!),
-  but there is no answer about CPU problems (I have a plan to upgrade
-  our PCs from P3-500MHz to P4 or better).
-  If you have interested in donating PCs to the project, please email me
-  for more detail.
-  </p>
- <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-	Kazuo
-	Horikawa
-       &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-    <p>For 4.6-RELEASE, we announced the package ja-man-doc-4.6.tgz
-      which is in sync with 4.6-RELEASE base system manual pages
-      except for perl5 pages (jpman project do not maintain them).
-      Continuing section 3 updating has 88% finished.</p>
-  <hr /><h2><a name="KAME-Project" href="#KAME-Project" id="KAME-Project">KAME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.kame.net/" title="http://www.kame.net/">KAME Project Web Page</a></td><td>
-	    URL: <a href="http://www.kame.net/" title="KAME Project Web Page">http://www.kame.net/</a></td></tr><tr><td><a href="http://www.interop.jp/eng/exhibition/ipv6_showcase.html" title="http://www.interop.jp/eng/exhibition/ipv6_showcase.html">IPv6 Showcase at Network+Interop2002</a></td><td>
-	    URL: <a href="http://www.interop.jp/eng/exhibition/ipv6_showcase.html" title="IPv6 Showcase at Network+Interop2002">http://www.interop.jp/eng/exhibition/ipv6_showcase.html</a></td></tr><tr><td><a href="http://www.interop.jp/jp/exhibition/ipv6_showcase.html" title="http://www.interop.jp/jp/exhibition/ipv6_showcase.html">IPv6 Showcase at Network+Interop2002 (detailed, but in Japanase)</a></td><td>
-	    URL: <a href="http://www.interop.jp/jp/exhibition/ipv6_showcase.html" title="IPv6 Showcase at Network+Interop2002 (detailed, but in Japanase)">http://www.interop.jp/jp/exhibition/ipv6_showcase.html</a></td></tr><tr><td><a href="http://www.sfc.wide.ad.jp/~say/n+i/" title="http://www.sfc.wide.ad.jp/~say/n+i/">Pictures of IPv6 Showcase</a></td><td>
-	    URL: <a href="http://www.sfc.wide.ad.jp/~say/n+i/" title="Pictures of IPv6 Showcase">http://www.sfc.wide.ad.jp/~say/n+i/</a></td></tr></table><p>
-	Contact:
-	SUZUKI
-
-	Shinsuke
-       &lt;<a href="mailto:core@kame.net">core@kame.net</a>&gt;
-	</p>
-    <p>I'm afraid KAME Project does not work actively with regard to FreeBSD in these two month, since
-    we are too busy with the demonstration of our IPv6 implementation at Networld+Interop 2002 Tokyo.
-    (Thanks to a great effort, the demonstration was quite successful) </p>
-
-    <p>We are aware of netinet6-related bug reports regarding socket handling, fine-grain locking, ip6fw etc.
-    Regret to say, we could not answer them right now due to the above situation, however we'll discus
-    these issues internally and determine what to do. </p>
-  <hr /><h2><a name="KSE-(Kernel-schedulable-Entity)-thread-support" href="#KSE-(Kernel-schedulable-Entity)-thread-support" id="KSE-(Kernel-schedulable-Entity)-thread-support">KSE (Kernel schedulable Entity) thread support </a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.ord/~julian/" title="http://www.freebsd.ord/~julian/">Some info here.</a></td><td>
-	    URL: <a href="http://www.freebsd.ord/~julian/" title="Some info here.">http://www.freebsd.ord/~julian/</a></td></tr></table><p>
-	Contact:
-	Julian
-
-	Elischer
-       &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Dan
-
-	Eischen
-       &lt;<a href="mailto:deischen@FreeBSD.org">deischen@FreeBSD.org</a>&gt;
-	</p>
-    <p>
-	The project took a major step at the beginning of July when
-	Milestone-III was committed. Milestone-III allows a simple test
-	program (available at /usr/src/tools/KSE/ksetest/)
-	to run multiple threads, using kernel support. It does not yet
-	allow the ability to allow these threads to run on different CPUs
-	simultaneously. Milestone IV will be to allow this, however
-	Milestone-III should allow Dan to start (with any interested
-	parties) to start prototyping the userland part of the
-	system. Milestone-III is only currently usable on x86, and
-	does not include some of the
-	requirements for full thread-control, suspension etc. that
-	will be required later. </p>
-     <p>
-	Before M-IV is started some small tweaking is likely
-	in the central sources on M-III as we discover issues
-	as we try to get the userland jumpstarted. These will have no
-	effect on non-KSE processes, (i.e. all of them :-) and
-	should not be an issue for other developers. </p>
-     <p>
-	A tex/fig-&gt;html guru is needed to help maintain the
-	KSE web page (not mentioned above as it is broken).
-    </p>
-  <hr /><h2><a name="Libh-Status-Report" href="#Libh-Status-Report" id="Libh-Status-Report">Libh Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/libh.html" title="http://www.FreeBSD.org/projects/libh.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/libh.html" title="">http://www.FreeBSD.org/projects/libh.html</a></td></tr><tr><td><a href="http://usw4.FreeBSD.org/~libh/" title="http://usw4.FreeBSD.org/~libh/">libh new development web page.</a></td><td>
-	    URL: <a href="http://usw4.FreeBSD.org/~libh/" title="libh new development web page.">http://usw4.FreeBSD.org/~libh/</a></td></tr><tr><td><a href="http://usw4.FreeBSD.org/~libh/screenshots" title="http://usw4.FreeBSD.org/~libh/screenshots">First snapshots of the diskeditor in action</a></td><td>
-	    URL: <a href="http://usw4.FreeBSD.org/~libh/screenshots" title="First snapshots of the diskeditor in action">http://usw4.FreeBSD.org/~libh/screenshots</a></td></tr></table><p>
-	Contact:
-	Antoine
-
-	Beaupre
-       &lt;<a href="mailto:antoine@usw4.FreeBSD.org">antoine@usw4.FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-	Alexander
-
-	Langer
-       &lt;<a href="mailto:alex@FreeBSD.org">alex@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-	Nathan
-
-	Ahlstrom
-       &lt;<a href="mailto:nra@FreeBSD.org">nra@FreeBSD.org</a>&gt;
-	</p>
-    <p>Max has been busy cleaning up the user interface dark side, and has
-	come up with a plan to improve the build system (using an automated
-	Makefile dependency generator); the UI design and the TCL glue magic
-	(using Swig). A development page has been created on usw4, publishing
-	a lot of information about the current project status, a Changelog,
-	screenshots, documentation, etc. A new listbox widget has been
-	implemented, making diskeditor look nicer and more usable. The package
-	system backend is being inspected and redesigned to conform to a standard
-	that is itself being re-thought. Indeed, the old sysinstall2.txt text has
-	been SGML-ized and enhanced and now provides a good (although rough) overview
-	of libh package system. This allowed the document to be enhanced with diagrams
-	of how different procedures work. We are therefore getting closer to a
-	real pkgAPI specification document. The package management tools have been
-	slightly enhanced and should be a bit more usable, and we started committing
-	regression test suites in the tree, mostly to test and maintain pkg API
-	conformance.</p>
-
-    <p>So work continues on libh. I plan to take a look at the rhtvision port
-	to see if it would be better to use it for the tvision backend. I'll keep
-	on working on the package system to make it really trustworthy, while Max
-	is continuing his great work on the UI subsystem. I hope to make a new libh
-	alpha release soon. Note that from now on, libh progress will be published
-	on the development page.</p>
-  <hr /><h2><a name="Lightweight-Interrupt-Scheduling" href="#Lightweight-Interrupt-Scheduling" id="Lightweight-Interrupt-Scheduling">Lightweight Interrupt Scheduling</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~peter/p4db/chb.cgi?FSPC=//depot/projects/interrupt/sys/..." title="http://people.FreeBSD.org/~peter/p4db/chb.cgi?FSPC=//depot/projects/interrupt/sys/...">The interrupt p4 branch</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~peter/p4db/chb.cgi?FSPC=//depot/projects/interrupt/sys/..." title="The interrupt p4 branch">http://people.FreeBSD.org/~peter/p4db/chb.cgi?FSPC=//depot/projects/interrupt/sys/...</a></td></tr></table><p>
-	Contact:
-	Bosko
-	Milekic
-       &lt;<a href="mailto:bmilekic@FreeBSD.org">bmilekic@FreeBSD.org</a>&gt;
-	</p>
-    <p>The lightweight interrupt scheduling code makes scheduling an
-    interrupt on i386 without having to grab the sched_lock possible,
-    and also avoids a full-blown context switch.</p>
-
-    <p>Currently, the code in the p4 branch works, although needs a
-    little bit of cleanup and, most importantly, requires a merge to
-    post-KSE III.  Now that stuff seems to have stabilized a bit, I'm
-    waiting to get a little time (and nerve) to do the merge.  Also,
-    looking forward for some KSE interface that will allow for "KSE
-    borrowing," which would make this cleaner with regards to KSE and
-    lightweight interrupts.  This is a 5.0 feature.</p>
-  <hr /><h2><a name="locking-up-pcb's-in-the-networking-stack" href="#locking-up-pcb's-in-the-networking-stack" id="locking-up-pcb's-in-the-networking-stack">locking up pcb's in the networking stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	Jeffrey
-
-	Hsu
-       &lt;<a href="mailto:hsu@FreeBSD.org">hsu@FreeBSD.org</a>&gt;
-	</p>
-    <p>Jennifer Yang's patch was committed June 10 for the BSD Summit.
-	After a few bugs which were reported initially and
-	fixed that same week, networking in -current
-	has been stable, including the parts that were not locked up,
-	like IPv6.  Work is on-going to lock up the rest of the stack.</p>
-  <hr /><h2><a name="mb_alloc-updates" href="#mb_alloc-updates" id="mb_alloc-updates">mb_alloc updates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bmilekic/code/mb_alloc/" title="http://people.FreeBSD.org/~bmilekic/code/mb_alloc/">Some [Old] mb_alloc stuff</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bmilekic/code/mb_alloc/" title="Some [Old] mb_alloc stuff">http://people.FreeBSD.org/~bmilekic/code/mb_alloc/</a></td></tr></table><p>
-	Contact:
-	Bosko
-	Milekic
-       &lt;<a href="mailto:bmilekic@FreeBSD.org">bmilekic@FreeBSD.org</a>&gt;
-	</p>
-    <p>mb_alloc is getting some updates and a couple of optimizations.
-    A new allocator interface routine should already be committed by
-    the time this report is "published:" m_getcl() allocates an mbuf
-    and a cluster in one shot.  This is the result of months
-    (literally) of requests from Alfred and, recently, Luigi - who,
-    coincidentally, is the author of the same [upcoming] routine in -STABLE.</p>
-
-    <p>Other than that, mb_alloc is being shown how to perform
-    multi-mbuf or cluster allocations without dropping the cache lock in
-    between (m_getcl() and m_getm() will use this).  Finally, work is
-    being done to optimize ext_buf ref. count allocations and to provide
-    support for jumbo (&gt; 9K) clusters.</p>
-  <hr /><h2><a name="NATD-rewrite" href="#NATD-rewrite" id="NATD-rewrite">NATD rewrite</a></h2><p>
-	Contact:
- Claudio
- Jeker
-  &lt;<a href="mailto:jeker@n-r-g.com">jeker@n-r-g.com</a>&gt;
-	<br />
-	Contact:
- Andre
- Oppermann
-  &lt;<a href="mailto:oppermann@pipeline.ch">oppermann@pipeline.ch</a>&gt;
-	</p>
- <p>The current natd is pretty powerful in translating different kinds
- of traffic but not very powerful in configuration. This project
- rewrites natd and parts of libalias to give it a configuration set as
- powerful and expressive as the ones in ipf (ipnat) and pf. In addition
- it'll use kqueue and will support aliasing to multiple IP
-addresses.</p>
- <p>The rewritten natd will be ready for committing in early
-September.</p>
-<hr /><h2><a name="NEWCARD" href="#NEWCARD" id="NEWCARD">NEWCARD</a></h2><p>
-	Contact:
-	Warner
-	Losh
-       &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-    <p>A devd daemon, to replace pccardd and usbd, has been designed.
-A few minor bugs have been fixed in NEWCARD.  NEWCARD is now the
-default in -current.  There is an experimental pci/cardbus bus code
-merge available as a branch which will be merged into current as soon
-as it is stable.</p>
-
-<p>Status: The ed driver, for non-ne2000 clones, is broken and won't
-probe.  The ata driver won't attach.  The sio driver hangs on the
-first character.  The wi driver is known to work well.  Cardbus cards
-are generally known to work well, except for some de based cards,
-which unfortunately includes the popular Xircom cards.  Many systems
-fail to work because acpi fails to route interrupts correctly for
-non-root pci bridges.</p>
-  <hr /><h2><a name="OLDCARD" href="#OLDCARD" id="OLDCARD">OLDCARD</a></h2><p>
-	Contact:
-	Warner
-	Losh
-       &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-    <p>A major power bug was fixed in oldcard.  This caused many
-problems for people using PCI interrupts having their machines hang on
-boot.  This fix has made it into 4.6.1.</p>
-
-    <p>Cardbus power is now used on all cardbus bridges that support
-it.  This means that we now support 3.3V cards on all cardbus
-bridges.  Before, we only supported them on some of the bridges
-because every bridge uses different 3.3V power control when programmed
-through the ExCA registers.  Now that we're going through the CardBus
-bridge's power control register, 3.3V cards work.  In fact, for
-CardBus bridges, the so called X.XV and Y.YV cards will work in those
-bridges that support them.  However, X.XV and Y.YV haven't been
-defined yet, and no bridges support them (but the bridge interface
-define it).  Obviously this latter part is untested.</p>
-
-    <p>CL-PD6722 support has been augmented slightly.  Now it is
-possible to instruct the driver which type of 3.3V card detection
-strategy to use.  There are three choices: none, do it like the
-CL-PD6710 does it and do it like the CL-PD6722 does it.</p>
-
-    <p>Preliminary support for the CL-PD6729 on a PCI card using PCI
-interrupts has been committed.  However, it fails for at least one of
-the cards like this the author has.</p>
-
-    <p>Client drivers can now ask for the manufacturer and model
-number of the card without parsing the CIS directly.</p>
-
-    <p>Except for fixing bugs and updating pccard.conf entries, no
-additional work is planned on the OLDCARD system.</p>
-  <hr /><h2><a name="OpenOffice.org-for-FreeBSD" href="#OpenOffice.org-for-FreeBSD" id="OpenOffice.org-for-FreeBSD">OpenOffice.org for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://projects.imp.ch/openoffice" title="http://projects.imp.ch/openoffice">OpenOffice.org FreeBSD port Homepage</a></td><td>
-	    URL: <a href="http://projects.imp.ch/openoffice" title="OpenOffice.org FreeBSD port Homepage">http://projects.imp.ch/openoffice</a></td></tr></table><p>
-	Contact:
-	Martin
-	Blapp
-       &lt;<a href="mailto:mbr@FreeBSD.org">mbr@FreeBSD.org</a>&gt;
-	</p>
-    <p>The port of openoffice 1.0 has been finished. Most showstopper issues
-       with rtld, libc and our toolchain have been fixed. There is one remaining
-       deadlock in the web-browser code of OO.org. If anybody like to help
-       us with fixing this bug (may be another libc_r bug as it looks like)
-       just mail me! Unfortunately gcc2 support got broken again with the import
-       of gcc2.95.4 in STABLE. Exceptions support seems to be broken again; we get
-       internal compiler errors with c++ exceptions code. You'll have to use gcc31
-       again.</p>
-
-    <p>Since our package cluster is outdated and can not build OO.org packages
-       anytime soon, I did my own little package cluster and can now offer
-       packages for 4.6R for 16 different languages. They can be found on the
-       project homepage.</p>
-
-    <p>Porting of OpenOffice1.0.1 is on it's way. A beta port and a package have
-       been made available on the project homepage.</p>
-
-  <hr /><h2><a name="Single-UNIX-Specification-conformant-SCCS-suite" href="#Single-UNIX-Specification-conformant-SCCS-suite" id="Single-UNIX-Specification-conformant-SCCS-suite">Single UNIX Specification conformant SCCS suite</a></h2><p>
-	Contact:
-	Juli
-
-	Mallett
-       &lt;<a href="mailto:jmallett@FreeBSD.org">jmallett@FreeBSD.org</a>&gt;
-	</p>
-    <p>The final version of SCCS distributed by CSRG has been integrated
-      into the projects CVS repository, and worked on extensively to the
-      point where essential functionality works on FreeBSD (and other
-      operating systems).  Some standards-related functionality has been
-      implemented</p>
-  <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  John
-
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The SMPng project has continued to make steady progress in
-	the past two months.  Jeff Roberson completed the switch over
-	to UMA for the general kernel malloc() and free() pushing down
-	Giant appropriately so that callers of malloc() and free() are
-	no longer required to hold Giant.  Alan Cox continues to clean
-	up the locking in the VM system pushing down Giant in several
-	of the VM related system calls.  Jeffrey Hsu committed locking
-	for TCP/IP protocol control blocks in the network stack.  John
-	Baldwin committed the changes to the p_canfoo() API to use
-	thread credentials for subject threads and added appropriate
-	locking for the targer process credentials.  Support for
-	adaptive mutexes on SMP systems as well as the new IA32 PAUSE
-	instruction were also committed in May.  The kernel tracing
-	facility KTRACE also received an overhaul such that the
-	majority of its work was pushed out into a worker thread
-	allowing trace points to no longer require Giant.  Andrew
-	Reiter has also been pushing down Giant in several system
-	calls.</p>
-
-      <p>Bosko continues to work on light-weight interrupt threads
-	for i386.  Most of the bugs in the turnstile code have been
-	found and fixed; however, the turnstile and preemption
-	patches have temporarily been put on hold so that more
-	emphasis can be placed on fixing bugs and making -current
-	more stable in preparation for 5.0 release in November.
-	Alan Cox and Andrew Reiter are continuing the work mentioned
-	above.  Jeff Roberson is also working on fixing the current
-	vnode locking in VFS.  Peter Wemm has also started to tackle
-	TLB issues on SMP in the i386 pmap again as well.</p>
-    <hr /><h2><a name="TCP-Hostcache" href="#TCP-Hostcache" id="TCP-Hostcache">TCP Hostcache</a></h2><p>
-	Contact:
- Andre
- Oppermann
-  &lt;<a href="mailto:oppermann@pipeline.ch">oppermann@pipeline.ch</a>&gt;
-	</p>
- <p>The current cache for the TCP metrics is embedded directly into
- the routing table route objects. This is highly inefficient as every
- route has an empty 56 Byte large metrics structure in it. TCP is the
- only consumer (except the MTU and Expiry field) of the structure. A
- full view of the Internet routes (110k routes) has more than 6 Mbyte
- of unused overhead due to it. The hit rate today is at only approx.
- 10% in webserver applications. The TCP hostcache will move this entire
- metrics structure from the routing table to the TCP stack. Every entry
- is a host entry so a simple hash table is sufficient to keep the
- entries. Its implementation is much like the TCP Syncache.</p>
- <p>The hostcache is going through testing on our servers and will
- be ready for committing in September. The results of the TCP metrics
- measurement will be used to tune the cache.</p>
-<hr /><h2><a name="TCP-Metrics-Measurement" href="#TCP-Metrics-Measurement" id="TCP-Metrics-Measurement">TCP Metrics Measurement</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www-t.zhwin.ch/pa02_2/diplomarbeiten2002.pdf" title="http://www-t.zhwin.ch/pa02_2/diplomarbeiten2002.pdf">Diploma Thesis of ZHWIN students, look for Olivier Mueller and Daniel Graf</a></td><td>
-	    URL: <a href="http://www-t.zhwin.ch/pa02_2/diplomarbeiten2002.pdf" title="Diploma Thesis of ZHWIN students, look for Olivier Mueller and Daniel Graf">http://www-t.zhwin.ch/pa02_2/diplomarbeiten2002.pdf</a></td></tr></table><p>
-	Contact:
- Andre
- Oppermann
-  &lt;<a href="mailto:oppermann@pipeline.ch">oppermann@pipeline.ch</a>&gt;
-	<br />
-	Contact:
- Olivier
- Mueller
-  &lt;<a href="mailto:omueller@8304.ch">omueller@8304.ch</a>&gt;
-	</p>
- <p>These students will analyse the tcpdumps of five major Swiss
- newspaper websites which give a representative overview of the
- user structure in Switzerland. The nice thing about Switzerland
- is that is has a very good mix of Modem/ISDN, leased line, Cable,
- ADSL and 3G/GSM/GPRS users. Every Internet access technology is
- represented. The goal is to analyze the behavior of all TCP
- sessions to the monitored sites. Parameters to be analyzed include
- TCP session RTT, RTT variance, in/outbound BDP, MSS changes, flow
- control behavior, packet loss, packet retransmit and
- timing of HTTP traffic to find optimal TCP parameter caching
-method.</p>
- <p>If you have any other metrics you think is useful please contact
- me so I can put that into the job description for the Students. The
- study will be made in September and October.</p>
-<hr /><h2><a name="TIRPC-port-for-BSD-sockets" href="#TIRPC-port-for-BSD-sockets" id="TIRPC-port-for-BSD-sockets">TIRPC port for BSD sockets</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.attic.ch/tirpc" title="http://www.attic.ch/tirpc">TIRPC for FreeBSD Homepage</a></td><td>
-	    URL: <a href="http://www.attic.ch/tirpc" title="TIRPC for FreeBSD Homepage">http://www.attic.ch/tirpc</a></td></tr><tr><td><a href="http://www.attic.ch/tirpc" title="http://www.attic.ch/tirpc"></a></td><td>
-	    URL: <a href="http://www.attic.ch/tirpc" title="">http://www.attic.ch/tirpc</a></td></tr></table><p>
-	Contact:
-	Martin
-	Blapp
-       &lt;<a href="mailto:mbr@FreeBSD.org">mbr@FreeBSD.org</a>&gt;
-	</p>
-    <p>
-       A lot of remaining PR's and Bugs have been closed. All relevant rpc
-       concerning patches have been committed. Thanks go to Alfred and Ian Dowese.
-    </p>
-    <p>Jean-Luc Richier &lt;Jean-Luc.Richier@imag.fr&gt; has made a patch
-       available which adds IPv6 support to all remaining rpc servers.
-       See ftp://ftp.imag.fr/pub/ipv6/NFS/NFS_IPV6_FreeBSD5.0.gz and
-       ftp://ftp.imag.fr/pub/ipv6/NFS/0README_NFS_IPV6_FreeBSD5.0
-       We will check his code and add it to CURRENT ASAP.</p>
-
-    <p>A first commit part from TIRPC99 has been done. I'm working now
-       on porting the remaining parts so when FreeBSD 5.0 gets released,
-       it will be TIRPC99 based. This will happen together with the NetBSD
-       project, as they use the same codebase as we do.
-    </p>
-
-  <hr /><h2><a name="TrustedBSD-MAC" href="#TrustedBSD-MAC" id="TrustedBSD-MAC">TrustedBSD MAC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD main web page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD main web page">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  TrustedBSD Discussion Mailing List
-	 &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project has been busy in May and June,
-        developing new features, presenting on the technology at
-        the FreeBSD Developer Summit, and improving the readiness
-        of the MAC branch for integration into the main FreeBSD
-        tree.  The migration to dynamic labeling in the TrustedBSD
-	MAC framework is complete, with all policies now making
-	use of dynamic labels in the kernel.  This permits policies
-	to associate arbitrary additional security data with a
-	variety of kernel objects at run-time.  Implement mac_test,
-	a sanity checking module.  Pass labels as well as objects
-	to each policy entry point to reduce knowledge of label
-	storage in the policies.  Implement mac_partition, a simple
-	jail-like policy.  Adapt the MAC framework for process locking.
-	</p>
-
-	<p>
-	Improve support for sockets: provide a peerlabel maintained for
-	stream sockets (unix domain, tcp), entry points for accept,
-	bind, connect, listen.  Improve support for IPv4 and IPv6 by
-	labeling IP fragment reassembly queues, and providing entry
-	points to instrument fragment matching, update, reassembly, etc.
-	Locally disable KAME if_loop mbuf contiguity hack because it
-	drops labels on mbufs: we need to make sure the label is
-	propagated.  Label pipes and provide access control for them.
-	Improve vnode labeling: now handle labeling for devfs, pseudofs,
-	procfs.  Fix interactions between MAC and ACLs relating to the
-	new VAPPEND flag.</p>
-
-	<p> SELinux policy tools now ported to SEBSD.  SEBSD now labels
-	subjects and file system objects.
-	Provide ugidfw, a tool for managing rules for the mac_bsdextended
-	policy.</p>
-
-	<p> Massive diff reduction.  KSEIII merged.  Main tree integration
-	will begin shortly.</p>
-
-	<p>Updated prototype code may be retrieved from the TrustedBSD
-	CVS trees on cvsup10.FreeBSD.org.</p>
-    <hr /><h2><a name="UFS2---Extended-attribute-and-large-size-support-for-UFS" href="#UFS2---Extended-attribute-and-large-size-support-for-UFS" id="UFS2---Extended-attribute-and-large-size-support-for-UFS">UFS2 - Extended attribute and large size support for UFS</a></h2><p>
-	Contact:
-	Poul-Henning
-	Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Kirk
-	Mckusick
-       &lt;<a href="mailto:mckusick@FreeBSD.org">mckusick@FreeBSD.org</a>&gt;
-	</p>
-    <p>
-	UFS2 is an extension to the well-known UFS filesystem which
-	using a new inode format adds support for "64bit everywhere"
-	and later for extended attribute support, in addition to the
-	current UFS features: soft-updates and snapshots.
-    </p>
-    <p>
-	The basic UFS2 code has been committed and work on the extended
-	attribute interface and vnode operations will continue.
-    </p>
-
-  <hr /><h2><a name="Userland-Regression-Tests" href="#Userland-Regression-Tests" id="Userland-Regression-Tests">Userland Regression Tests</a></h2><p>
-	Contact:
-	Juli
-
-	Mallett
-       &lt;<a href="mailto:jmallett@FreeBSD.org">jmallett@FreeBSD.org</a>&gt;
-	</p>
-    <p>Regression tests for many bugs fixed in text manipulation utilities
-      have been added, as well as tests for various non-standard versions
-      of functionality that FreeBSD users should expect.  A library of
-      m4 macros for creating the tests themselves has been added.</p>
-  <hr /><h2><a name="Zero-Copy-Sockets-status-report" href="#Zero-Copy-Sockets-status-report" id="Zero-Copy-Sockets-status-report">Zero Copy Sockets status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~ken/zero_copy/" title="http://people.FreeBSD.org/~ken/zero_copy/">Zero copy patches and information.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~ken/zero_copy/" title="Zero copy patches and information.">http://people.FreeBSD.org/~ken/zero_copy/</a></td></tr></table><p>
-	Contact:
-	Ken
-
-	Merry
-       &lt;<a href="mailto:ken@FreeBSD.org">ken@FreeBSD.org</a>&gt;
-	</p>
-    <p> The zero copy sockets code was committed to FreeBSD-current on June
-	25th, 2002.  I'm not planning on doing any more patches, although
-	I will leave the web page up as it contains useful information. </p>
-    <p>
-	Many thanks to the folks who have tested and reviewed the code over
-	the years. </p>
-  <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2002-07-2002-08.html b/website/content/en/status/report-2002-07-2002-08.html
deleted file mode 100644
index 9edd07dd62..0000000000
--- a/website/content/en/status/report-2002-07-2002-08.html
+++ /dev/null
@@ -1,932 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Throughout July and August, the FreeBSD Project has been working on
-      pulling together the last few major pieces of new functionality for
-      FreeBSD 5.0-RELEASE.  At this point, the release appears to be on track
-      for late November or early December.  Work on fine-grained locking
-      continues, especially in the VFS, as with improved support for threading
-      through the KSE work;  features such as GEOM, UFS2, and TrustedBSD MAC are
-      maturing, and the new ia64 and sparc64 hardware ports are approaching
-      production quality.  In the next two months, we have a lot to look forward
-      to: additional 5.0 developer preview snapshots, additional locking and
-      threading improvements, and many cleanups on the new supported
-      architectures. Firewire support has been imported into the main tree, and
-      substantial cleanup of the ACPI/legacy PCI code is also in the works.
-      Also, expect the import of new IPsec hardware acceleration support in the
-      near future.</p><p>When new developer previews are posted, please give them a try!  While we
-      know that 5.0-RELEASE will be for "early adopters", the more testing we
-      get out of the way now, the less we have to tidy up later.  The new
-      features are extremely exciting, and understanding when and how to deploy
-      them properly will be important.  In the next two months, among other
-      things, the release engineering team will post updated release schedules,
-      as well as guidance for FreeBSD consumers as to how to decide what
-      releases of FreeBSD will be right for them.  Keep an eye out for this, and
-      provide us with feedback.</p><p>Also, for those of you in Europe -- we look forward to seeing you at
-      BSDCon Europe in a couple of months!</p><p>Scott Long, Robert Watson</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)"> Bluetooth stack for FreeBSD (Netgraph implementation)</a></li><li><a href="#ATAPI/CAM-Status-Report">ATAPI/CAM Status Report</a></li><li><a href="#BSDCon-2003">BSDCon 2003</a></li><li><a href="#Fast-IPsec-Status">Fast IPsec Status</a></li><li><a href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></li><li><a href="#FreeBSD-Donations-Team">FreeBSD Donations Team</a></li><li><a href="#FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></li><li><a href="#FreeBSD-Security-Officer-Team">FreeBSD Security Officer Team</a></li><li><a href="#French-FreeBSD-Documentation-Project">French FreeBSD Documentation Project</a></li><li><a href="#GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></li><li><a href="#Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></li><li><a href="#jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KSE">KSE</a></li><li><a href="#Libh-Status-Report">Libh Status Report</a></li><li><a href="#Lottery-Scheduler-for-FreeBSD--STABLE">Lottery Scheduler for FreeBSD -STABLE</a></li><li><a href="#Netgraph-ATM">Netgraph ATM</a></li><li><a href="#Network-interface-cloning-and-modularity">Network interface cloning and modularity</a></li><li><a href="#New-SCSI-Target-Emulator">New SCSI Target Emulator</a></li><li><a href="#RAIDFrame-for-FreeBSD">RAIDFrame for FreeBSD</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#The-FreeBSD-Brazilian-Portuguese-Documentation-Project">The FreeBSD Brazilian Portuguese Documentation Project</a></li><li><a href="#TrustedBSD-Mandatory-Access-Control-(MAC)">TrustedBSD Mandatory Access Control (MAC)</a></li><li><a href="#UFS2---64bit-UFS-with-native-extended-attributes">UFS2 - 64bit UFS with native extended attributes</a></li><li><a href="#VM-issues-in--stable">VM issues in -stable</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)"> Bluetooth stack for FreeBSD (Netgraph implementation)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz" title="http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz">Latest snapshot</a></td><td>
-	    URL: <a href="http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz" title="Latest snapshot">http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz</a></td></tr><tr><td><a href="http://bluez.sf.net" title="http://bluez.sf.net">Linux BlueZ stack</a></td><td>
-	    URL: <a href="http://bluez.sf.net" title="Linux BlueZ stack">http://bluez.sf.net</a></td></tr></table><p>
-	Contact:
-
-          Maksim
-
-
-
-          Yevmenkin
-
-       &lt;<a href="mailto:&#10;        m_evmenkin@yahoo.com&#10;      ">
-        m_evmenkin@yahoo.com
-      </a>&gt;
-	</p>
-    <p>I'm very pleased to announce that another engineering
-      release is available for download at
-      http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz</p>
-    <p>This release features several major changes and includes
-      support for H4 UART and H2 USB transport layers, Host
-      Controller Interface (HCI), Link Layer Control and
-      Adaptation Protocol (L2CAP) and Bluetooth sockets layer.
-      It also comes with several user space utilities that
-      can be used to configure and test Bluetooth devices.
-      Also there are several man pages.</p>
-    <p>Service Discovery Protocol (SDP) is now supported. This
-      release includes SDP daemon, configuration tool and user
-      space library (ported from BlueZ-sdp-0.7).</p>
-    <p>RFCOMM is now supported. This release includes rfcommd
-      daemon that provides RFCOMM service via pseudo ttys.
-      Not very useful for legacy application, but it is possible
-      to run PPP over Bluetooth now. This was ported from old
-      BlueZ-rfcommd-1.1 (no longer supported by BlueZ) and
-      still has some bugs in it.</p>
-    <p>Next step is to fix current RFCOMM support and work on
-      new in-kernel RFCOMM and BNEP (Bluetooth Network
-      Encapsulation Protocol) implementation. Also user space
-      need more work (better tools, libraries, documentation
-      etc.).</p>
-  <hr /><h2><a name="ATAPI/CAM-Status-Report" href="#ATAPI/CAM-Status-Report" id="ATAPI/CAM-Status-Report">ATAPI/CAM Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cuivre.fr.eu.org/~thomas/atapicam/" title="http://www.cuivre.fr.eu.org/~thomas/atapicam/"></a></td><td>
-	    URL: <a href="http://www.cuivre.fr.eu.org/~thomas/atapicam/" title="">http://www.cuivre.fr.eu.org/~thomas/atapicam/</a></td></tr></table><p>
-	Contact:
-	Thomas
-
-	Quinot
-       &lt;<a href="mailto:thomas@FreeBSD.org">thomas@FreeBSD.org</a>&gt;
-	</p>
-    <p>The ATAPI/CAM module allows ATAPI devices (CD-ROM, CD-RW, DVD
-    drives, floppy drives such as Iomega Zip, tape drives) to
-    be accessed through the SCSI subsystem (CAM). ATAPI/CAM has been
-    integrated in -CURRENT. The code should be fairly functional (it
-    has been used by many testers as patches against -STABLE and
-    -CURRENT over the past eight months), but there are pending issues
-    on SMP machines. Testers most welcome.</p>
-    <p>A MFC of this feature will probably happen after the end
-    of the 4.7 code freeze.</p>
-  <hr /><h2><a name="BSDCon-2003" href="#BSDCon-2003" id="BSDCon-2003">BSDCon 2003</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.usenix.org/events/bsdcon03/cfp/" title="http://www.usenix.org/events/bsdcon03/cfp/">BSDCon 2003 Call For Papers</a></td><td>
-	    URL: <a href="http://www.usenix.org/events/bsdcon03/cfp/" title="BSDCon 2003 Call For Papers">http://www.usenix.org/events/bsdcon03/cfp/</a></td></tr></table><p>
-	Contact:
-	Gregory
-	Shapiro
-       &lt;<a href="mailto:gshapiro@FreeBSD.org">gshapiro@FreeBSD.org</a>&gt;
-	</p>
-
-    <p>The BSDCon 2003 Program Committee invites you to contribute
-    original and innovative papers on topics related to BSD-derived
-    systems and the Open Source world. Topics of interest include
-    but are not limited to:</p>
-
-    <ul>
-      <li>Embedded BSD application development and deployment</li>
-      <li>Real world experiences using BSD systems</li>
-      <li>Using BSD in a mixed OS environment</li>
-      <li>Comparison with non-BSD operating systems; technical,
-      practical, licensing (GPL vs. BSD)</li>
-      <li>Tracking open source development on non-BSD systems</li>
-      <li>BSD on the desktop</li>
-      <li>I/O subsystem and device driver development</li>
-      <li>SMP and kernel threads</li>
-      <li>Kernel enhancements</li>
-      <li>Internet and networking services</li>
-      <li>Security</li>
-      <li>Performance analysis and tuning</li>
-      <li>System administration</li>
-      <li>Future of BSD</li>
-    </ul>
-
-    <p>Submissions in the form of extended abstracts are due by
-    April 1, 2003. Be sure to review the extended abstract
-    expectations before submitting. Selection will be based on the
-    quality of the written submission and whether the work is of
-    interest to the community.</p>
-
-    <p>We look forward to receiving your submissions!</p>
-
-  <hr /><h2><a name="Fast-IPsec-Status" href="#Fast-IPsec-Status" id="Fast-IPsec-Status">Fast IPsec Status</a></h2><p>
-	Contact:
-          Sam
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>The main goal of this project is to modify the IPsec protocols to use
-      the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). A
-      secondary goal is to do general performance tuning of the IPsec
-      protocols.</p>
-    <p>Recent work focused on increasing performance. Support is still limited
-      to IPv4 protocols, with IPv6 support coded but not yet tested. </p>
-    <p>Import of this work into the -current tree has started.  A publicly
-      available patch against 4.7 will be released once 4.7 ships.</p>
-  <hr /><h2><a name="FreeBSD-C99-&amp;-POSIX-Conformance-Project" href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project" id="FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/c99/" title="http://www.FreeBSD.org/projects/c99/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/c99/" title="">http://www.FreeBSD.org/projects/c99/</a></td></tr></table><p>
-	Contact:
-	Mike
-
-	Barcroft
-       &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        FreeBSD-Standards Mailing List
-       &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-    <p>On the API front, fmtmsg(3) was implemented, glob(3) was given support
-      for new flags, ulimit(3) was implemented, and wide character/string
-      support was significantly improved with the addition of 30 new functions
-      (see the project status board for details).  Work is progressing on
-      adding the C99 restrict type-qualifier to functions throughout the
-      system.  This allows the compiler to make additional optimizations based
-      on the knowledge that a restrict-qualified argument is the only reference
-      to a given object (ie. it doesn't overlap with another argument).</p>
-    <p>Several headers have been brought up to conformance with POSIX.1-2001,
-      they include: &lt;fmtmsg.h&gt;, &lt;poll.h&gt;, &lt;sys/mman.h&gt;, and
-      &lt;ulimit.h&gt;.  The header &lt;cpio.h&gt; was implemented.  The
-      headers &lt;machine/ansi.h&gt; and &lt;machine/types.h&gt; were merged
-      into a single header to help simplify the way variable types are
-      created.</p>
-    <p>The sh(1) built-in, command(1), was reimplemented to conform with
-      POSIX.  Additionally, several utilities which were previously brought
-      up to conformance were merged into the 4-STABLE branch.</p>
-  <hr /><h2><a name="FreeBSD-Donations-Team" href="#FreeBSD-Donations-Team" id="FreeBSD-Donations-Team">FreeBSD Donations Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/donations/index.html" title="http://www.FreeBSD.org/donations/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/donations/index.html" title="">http://www.FreeBSD.org/donations/index.html</a></td></tr></table><p>
-	Contact:
-	Michael
-
-	Lucas
-       &lt;<a href="mailto:donations@FreeBSD.org">donations@FreeBSD.org</a>&gt;
-	</p>
-    <p>The Donations team started rolling in the last couple of
-      months.  Offers of equipment are coming in, and we are
-      allocating them to FreeBSD committers as quickly as possible.
-      We now have a "Committer Want List" available in our section of
-      the Web site.  Several small items, such as network cards, have
-      been routed to people who are willing to write the code to
-      support them.  We have a few larger donations (i.e., actual
-      servers) ready to go to developers, once shipping information is
-      straightened out.</p>
-  <hr /><h2><a name="FreeBSD-GNOME-Project" href="#FreeBSD-GNOME-Project" id="FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Homepage.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project Homepage.">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-	Joe
-
-	Marcus
-       &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Maxim
-
-	Sobolev
-       &lt;<a href="mailto:sobomax@FreeBSD.org">sobomax@FreeBSD.org</a>&gt;
-	</p>
-    <p>The GNOME 2 desktop port has reach version 2.0.2rc1 with an expected
-      2.0.2 release before 4.7-RELEASE.  Mozilla 1.1 has been ported,
-      and is resident in the tree with Mozilla 1.0.1.  The GNOMENG porting
-      effort is going well.  A good deal of ports have been moved to the
-      new infrastructure with the help of
-      Edwin Groothuis.  We are now working on
-      smoothing out some of the rough edges, then, once all the work is done,
-      make GNOMENG the default.</p>
-    <p>A long-standing annoyance in Nautilus has also been recently
-      corrected.  The desktop is no longer cluttered with volume icons, and
-      removable media (such as CDs) should now be handled correctly.</p>
-
-  <hr /><h2><a name="FreeBSD-Security-Officer-Team" href="#FreeBSD-Security-Officer-Team" id="FreeBSD-Security-Officer-Team">FreeBSD Security Officer Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/security/" title="http://www.FreeBSD.org/security/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/security/" title="">http://www.FreeBSD.org/security/</a></td></tr></table><p>
-	Contact:
-	Jacques
-
-	Vidrine
-       &lt;<a href="mailto:nectar@FreeBSD.org">nectar@FreeBSD.org</a>&gt;
-	</p>
-
-  <p>The Security Team continues to be very busy.  The
-    security-officer mailing list traffic for the months of June, July,
-    and August consisted of 1,230 messages (over 13 messages a day).
-    This is well over 50% of the freebsd-hackers traffic volume in the
-    same period!</p>
-  <p>Since June (the time of our last report), 9 new Security
-    Advisories were published, and one Security Notice was published
-    covering 25 Ports Collection issues.</p>
-  <p>FreeBSD 4.6.2-RELEASE was released on August 15th.  This marked
-    the first time a point release was created from the security branch.
-    The process went smoothly from the Security Team perspective, despite
-    a schedule slippage due to newly discovered bugs, and a snafu which
-    resulted in 4.6.1-RELEASE being skipped.</p>
-  <p>In September, the FreeBSD Security Officer published a new PGP
-    key (ID 0xCA6CDFB2, found on the FTP site and in the Handbook).
-    This aligned the set of those who possess the corresponding private
-    key with the membership of the security-officer alias published on
-    the FreeBSD Security web site.  It also worked around an issue with
-    the deprecated PGP key being found corrupted on some public key
-    servers.</p>
-  <hr /><h2><a name="French-FreeBSD-Documentation-Project" href="#French-FreeBSD-Documentation-Project" id="French-FreeBSD-Documentation-Project">French FreeBSD Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd-fr.org" title="http://www.freebsd-fr.org">The French FreeBSD Documentation Project.</a></td><td>
-	    URL: <a href="http://www.freebsd-fr.org" title="The French FreeBSD Documentation Project.">http://www.freebsd-fr.org</a></td></tr><tr><td><a href="http://www.freebsd-fr.org/index-trad.html" title="http://www.freebsd-fr.org/index-trad.html">The FreeBSD Web Server translate in French.</a></td><td>
-	    URL: <a href="http://www.freebsd-fr.org/index-trad.html" title="The FreeBSD Web Server translate in French.">http://www.freebsd-fr.org/index-trad.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/" title="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/">Translation of the Hanbook.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/" title="Translation of the Hanbook.">http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/</a></td></tr></table><p>
-	Contact:
-	Sebastien
-	Gioria
-       &lt;<a href="mailto:gioria@FreeBSD.org">gioria@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Marc
-	Fonvieille
-       &lt;<a href="mailto:blackend@FreeBSD.org">blackend@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Stephane
-	Legrand
-       &lt;<a href="mailto:stephane@FreeBSD-fr.ORG">stephane@FreeBSD-fr.ORG</a>&gt;
-	</p>
-    <p>We've got currently almost 50% of the new handbook translated (all the
-      installation part is translated). Most of the articles are translated
-      too.</p>
-    <p>The web site in on the way, see the Web Server. We need now to
-      integrate it on the US CVS tree.</p>
-    <p>One of the big job now, is to translate the latest FAQ and the very
-      big project will be the manual pages</p>
-  <hr /><h2><a name="GEOM---generalized-block-storage-manipulation" href="#GEOM---generalized-block-storage-manipulation" id="GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~phk/Geom/" title="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~phk/Geom/" title="Old concept paper here.">http://www.FreeBSD.org/~phk/Geom/</a></td></tr></table><p>
-	Contact:
-	Poul-Henning
-
-	Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-    <p>The GEOM code has gotten so far that it beats our current code
-      in some areas while still lacking in others.  The goal is for
-      GEOM to be the default in 5.0-RELEASE.</p>
-    <p>Currently work on a cryptographic module which should be able
-      to protect a diskpartition from practically any sort of attack
-      is progressing.</p>
-
-  <hr /><h2><a name="Hardware-Crypto-Support-Status" href="#Hardware-Crypto-Support-Status" id="Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></h2><p>
-	Contact:
-          Sam
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>The goal of this project is to import the OpenBSD kernel-level crypto
-      subsystem. This facility provides kernel- and user-level access to
-      hardware crypto devices for the calculation of cryptographic hashes,
-      ciphers, and public key operations. The main clients of this facility
-      are the kernel RNG (/dev/random), network protocols (e.g. IPSEC), and
-      OpenSSL (through the /dev/crypto device).</p>
-    <p>OpenSSL 0.9.7 beta 3 was imported and patched with fixes from OpenBSD's
-      source tree.  This permits any user-level application that use -lcrypto to
-      automatically get hardware crypto acceleration.  Otherwise the core crypto
-      support is stable and has been in production use on -stable machines for
-      several months.</p>
-    <p>Import of this work into the -current tree has started.  A publicly
-      available patch against 4.7 will be released once 4.7 ships. Integration
-      of this work into the -stable source tree is planned for 4.8.</p>
-  <hr /><h2><a name="jp.FreeBSD.org-daily-SNAPSHOTs-project" href="#jp.FreeBSD.org-daily-SNAPSHOTs-project" id="jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://snapshots.jp.FreeBSD.org/" title="http://snapshots.jp.FreeBSD.org/">Project Webpage</a></td><td>
-	    URL: <a href="http://snapshots.jp.FreeBSD.org/" title="Project Webpage">http://snapshots.jp.FreeBSD.org/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/snapshots/" title="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese )</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/snapshots/" title="Project Webpage (in Japanese )">http://www.jp.FreeBSD.org/snapshots/</a></td></tr></table><p>
-	Contact:
-    Makoto
-    Matsushita
-    &lt;<a href="mailto:matusita@jp.FreeBSD.org">matusita@jp.FreeBSD.org</a>&gt;
-	</p>
-  <p>The project runs as it should be.  New security-branch snapshots are
-    available for both 4.5 and 4.6(.2).  I've update buildboxes OS to
-    the latest 5-current/4-stable without any errors.  Also current
-    problem, less CPU power for the future, is not solved yet -- but
-    situation is not so bad, I hope I'll show a good news in the next
-    report.</p>
- <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-	Kazuo
-	Horikawa
-       &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-    <p>We have been updating RELENG_4 targeting for 4.7-RELEASE.
-      When port ja-man-1.1j_5 was broken around the end of July,
-      Kumano-san and Mori-san tried to update the port to be based
-      on a newer FreeBSD base system's man commands.
-      But, we decided only to fix the port ja-man-1.1j_5 to be buildable,
-      as the new one was not complete at that time.</p>
-  <hr /><h2><a name="KSE" href="#KSE" id="KSE">KSE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~julian" title="http://www.FreeBSD.org/~julian">poor description</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~julian" title="poor description">http://www.FreeBSD.org/~julian</a></td></tr></table><p>
-	Contact:
-          Julian
-          Elischer
-         &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Jonathon
-          Mini
-         &lt;<a href="mailto:mini@FreeBSD.org">mini@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Dan
-          Eischen
-         &lt;<a href="mailto:deischen@FreeBSD.org">deischen@FreeBSD.org</a>&gt;
-	</p>
-      <p> David Xu and I have been working on cleaning up some of the work done
-        in KSE-III and Jonathon and Dan have been working on the userland
-        interface.  The userland library will be committed soon in a
-        prototypical state and a working test program using that interface will
-        hopefully accompany it. I have just committed a rework of the run
-        states for kernel threads that simplifies or solves some problems that
-        were being seen recently.</p>
-      <p>Hopefully in the next few weeks we will be able to run threads on
-        separate processors. The basics of Signal support are presently
-        evolving. Archie Cobbs will also be assisting with some of this work.
-        I have a mail alias for all the developers at kse@elischer.org. It is
-        managed by hand at the moment.</p>
-    <hr /><h2><a name="Libh-Status-Report" href="#Libh-Status-Report" id="Libh-Status-Report">Libh Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/libh.html" title="http://www.FreeBSD.org/projects/libh.html">Project's home page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/libh.html" title="Project's home page">http://www.FreeBSD.org/projects/libh.html</a></td></tr></table><p>
-	Contact:
-	Antoine
-
-	Beaupr�
-       &lt;<a href="mailto:anarcat@anarcat.ath.cx">anarcat@anarcat.ath.cx</a>&gt;
-	<br />
-	Contact:
-	Alexander
-
-	Langer
-       &lt;<a href="mailto:alex@FreeBSD.org">alex@FreeBSD.org</a>&gt;
-	</p>
-    <p>The primary libh development box, where the CVS repo and
-      development webpage was living, is dead. The server has crashed
-      after a system upgrade and has never came back to life. We had
-      to pull the drives out of it to make proper backups. We will
-      setup another box in place of this one and hope for the best. So
-      right now, the port is broken because the CVS is unaccessible,
-      as the development web page. We're working on it, please bear
-      with us.</p>
-    <p>On a brighter note, Max started implementing the changes he
-      proposed to the build system and the TCL API; LibH is switching
-      to SWIG for its TCL bindings, which should simplify the system a
-      lot, and shorten build times. The Hui subsystem is therefore
-      being completely re-written. On my side, I made a few tests in
-      building and running LibH under rhtvision, and it didn't fulfill
-      the promises I thought it would, so I just put aside that
-      idea. Work on libh stalled during July because I completely lost
-      network access for the whole month. So right now, LibH is in a
-      bit of a mess, but we have high hopes of settling everything
-      down to a new release pretty soon, which will make full use of
-      the new SWIG bindings.</p>
-  <hr /><h2><a name="Lottery-Scheduler-for-FreeBSD--STABLE" href="#Lottery-Scheduler-for-FreeBSD--STABLE" id="Lottery-Scheduler-for-FreeBSD--STABLE">Lottery Scheduler for FreeBSD -STABLE</a></h2><p>
-	Contact:
-	M�rio S�rgio Fujikawa
-
-	Ferreira
-       &lt;<a href="mailto:lioux@FreeBSD.org">lioux@FreeBSD.org</a>&gt;
-	</p>
-    <p>Yet another implementation of Lottery Scheduling devised by
-      Carl Waldspurger et. al. is being developed against FreeBSD
-      -STABLE branch.  It is being developed as part of a graduation
-      project in Computer Science at Universidade de Bras�lia
-      in Brazil.  Therefore, other implementations have not yet
-      been verified to avoid plagiarization but will be checked in
-      a later stage of this project searching for better implementation
-      ideas.  Currently, part of the necessary scheduling kernel
-      structure has been mapped and work has progressed despite the
-      general lack of kernel documentation.  Further outcomes of
-      this project will be a simple documentation of the kernel
-      scheduler structure of -STABLE branch, a port of the Lottery
-      Scheduler to -CURRENT branch and additional implementations
-      of other scheduling disciplines from Carl Waldspurger et. al.
-      Members of the FreeBSD community have been and will continue
-      to be instrumental in both testing and providing feedback for
-      ideas implemented here.</p>
-  <hr /><h2><a name="Netgraph-ATM" href="#Netgraph-ATM" id="Netgraph-ATM">Netgraph ATM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html" title="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html">Introduction to NgAtm</a></td><td>
-	    URL: <a href="http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html" title="Introduction to NgAtm">http://www.fokus.fhg.de/research/cc/cats/employees/hartmut.brandt/ngatm/index.html</a></td></tr></table><p>
-	Contact:
-	Harti
-
-	Brandt
-       &lt;<a href="mailto:brandt@fokus.fhg.de">brandt@fokus.fhg.de</a>&gt;
-	</p>
-    <p>Version 1.2 has been released recently. It should compile and work
-      an any recent FreeBSD-current. Support to manipulate SUNI registers
-      has been added to the ATM drivers (to switch between SONET and SDH
-      modes, for example). The ngatmsig package now includes a small and
-      simple call control module that may be used to build a simple ATM
-      switch. The netgraph stuff has been patched to use the official
-      netgraph locking.</p>
-  <hr /><h2><a name="Network-interface-cloning-and-modularity" href="#Network-interface-cloning-and-modularity" id="Network-interface-cloning-and-modularity">Network interface cloning and modularity</a></h2><p>
-	Contact:
-	Brooks
-
-	Davis
-       &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-    <p>Cloning support for ppp(4) and disc(4) interfaces has been
-      committed.  A man page for disc has been created and the disc
-      devices now appear as disc# instead of ds#.  Some work is still
-      needed on pppd to make it understand cloning though it should work
-      as long as the devices are created beforehand.</p>
-    <p>On the API front, management of mandatory interfaces (i.e. lo0)
-      is handled by the generic cloning code so if_clone_destroy has the
-      same API as NetBSD again and &lt;if&gt;_modevent doesn't need to create
-      the necessary devices manually.</p>
-    <p>At this point, all pseudo interfaces have been converted to the
-      cloning API or already did their own cloning (sl(4) for example
-      uses it's own mechanism).  Some devices such as tun(4) and
-      tap/vmware should probably be converted to use the cloning API
-      instead of their current ad-hoc, devfs based cloning system.  This
-      would be a good junior kernel hacker task.  Also, the handbook and
-      FAQ could use some general cloning documentation prior to 5.0
-      release.</p>
-  <hr /><h2><a name="New-SCSI-Target-Emulator" href="#New-SCSI-Target-Emulator" id="New-SCSI-Target-Emulator">New SCSI Target Emulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.root.org/~nate/freebsd/" title="http://www.root.org/~nate/freebsd/"></a></td><td>
-	    URL: <a href="http://www.root.org/~nate/freebsd/" title="">http://www.root.org/~nate/freebsd/</a></td></tr></table><p>
-	Contact:
-	Nate
-
-	Lawson
-       &lt;<a href="mailto:nate@root.org">nate@root.org</a>&gt;
-	</p>
-
-    <p>The existing SCSI target code has been rewritten.  The kernel driver is
-      much simpler, deferring all functionality to usermode and simply passing
-      CCBs to and from the SIM.  The supplied usermode emulates a disk (RBC)
-      with IO going to a backing file.  It replaces /sys/cam/scsi/scsi_target*
-      and /usr/share/examples/scsi_target.</p>
-    <p>The code is definitely alpha quality and has known problems on
-      -current although it appears to work ok on -stable.  See the included
-      README for how to install and test.  Feedback is welcome!</p>
-
-  <hr /><h2><a name="RAIDFrame-for-FreeBSD" href="#RAIDFrame-for-FreeBSD" id="RAIDFrame-for-FreeBSD">RAIDFrame for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~scottl/rf" title="http://people.FreeBSD.org/~scottl/rf">Project homepage</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~scottl/rf" title="Project homepage">http://people.FreeBSD.org/~scottl/rf</a></td></tr></table><p>
-	Contact:
-	Scott
-
-	Long
-       &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-    <p>Work on RAIDFrame stalled for quite a bit, then it picked up in
-      early summer, then it stalled, and now it's going again.  A
-      significant amount of work has been done to make the locking
-      SMPng-friendly and to cut down on kernel stack abuse.  I'm happy
-      to say that it's starting to work reliably when used with file-
-      backed 'md' disks.  Even more exciting is that it's finally starting
-      to work on real disks, too.  A lot of cleanup is still needed, and
-      a few gross hacks still exist, but it might actually be ready for
-      the FreeBSD 5.0 release.  Patches for FreeBSD 5-current and 4-stable
-      are available from the website.  The 4-stable patches are a year old
-      but still apply and perform well.</p>
-  <hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-    <p>The Release Engineering (RE) Team completed and released FreeBSD
-      4.6.2.  This ``point release'' fixes several important bugs in
-      the ATA subsystem, as well as addressing a number of security
-      issues in the base system that surfaced shortly after FreeBSD
-      4.6 was released.  The release documentation distributed with
-      FreeBSD 4.6.2 contains more details.  (Note: Some earlier
-      documents and reports referred to this release as version
-      4.6.1.)  The next release in the 4.X series will be FreeBSD 4.7,
-      which has a scheduled release date of 1 October 2002.</p>
-    <p>Concurrently, work is continuing on the 5.0-DP2 developer
-      preview snapshot, an important milestone along the release path
-      of FreeBSD 5.0, which is scheduled for release on 20 November.
-      As 5.0 draws closer, we are focusing more on getting the system
-      stabilized, as opposed to adding new functionality.  To help us
-      with this effort, developers should discuss with us any new
-      features planned for -CURRENT, beginning 1 October.</p>
-  <hr /><h2><a name="The-FreeBSD-Brazilian-Portuguese-Documentation-Project" href="#The-FreeBSD-Brazilian-Portuguese-Documentation-Project" id="The-FreeBSD-Brazilian-Portuguese-Documentation-Project">The FreeBSD Brazilian Portuguese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fugspbr.org/" title="http://www.fugspbr.org/">FUG-BR Grupo de Usu�rios FreeBSD - Brasil</a></td><td>
-	    URL: <a href="http://www.fugspbr.org/" title="FUG-BR Grupo de Usu�rios FreeBSD - Brasil">http://www.fugspbr.org/</a></td></tr></table><p>
-	Contact:
-	Edson
-
-	Brandi
-       &lt;<a href="mailto:ebrandi.home@uol.com.br">ebrandi.home@uol.com.br</a>&gt;
-	<br />
-	Contact:
-	M�rio S�rgio Fujikawa
-
-	Ferreira
-       &lt;<a href="mailto:lioux@FreeBSD.org">lioux@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Ricardo Nascimento
-
-	Ferreira
-       &lt;<a href="mailto:nightwish@techemail.com">nightwish@techemail.com</a>&gt;
-	<br />
-	Contact:
-	Diego
-
-	Linke
-       &lt;<a href="mailto:gamk@gamk.com.br">gamk@gamk.com.br</a>&gt;
-	<br />
-	Contact:
-	Jean Milanez
-
-	Melo
-       &lt;<a href="mailto:jmelo@freebsdbrasil.com.br">jmelo@freebsdbrasil.com.br</a>&gt;
-	<br />
-	Contact:
-	Patrick
-
-	Tracanelli
-       &lt;<a href="mailto:eksffa@freebsdbrasil.com.br">eksffa@freebsdbrasil.com.br</a>&gt;
-	<br />
-	Contact:
-	Alexandre
-
-	Vasconcelos
-       &lt;<a href="mailto:alexandre@sspj.go.gov.br">alexandre@sspj.go.gov.br</a>&gt;
-	</p>
-    <p>The FreeBSD Brazilian Portuguese Documentation Project is
-      merging with a translation group formed by members of the
-      FUG-BR FreeBSD Brazilian user group.  The Brazilian Project
-      decided to become an official group under FUG-BR after receiving
-      continued excellent contributions from them.  They have managed
-      to complete the translation of the FreeBSD FAQ which is
-      currently undergoing both proofing and SGML"fication" stages.
-      Work is progressing fast: the Handbook has been half translated
-      and articles are under way.  The previous Brazilian Project
-      is proud to become part of such a dedicate group.  The contacts
-      above represent the current official contacts for the new
-      translation group.  We hope to have at least part of this
-      work ready for the FreeBSD 4.7 Release.</p>
-  <hr /><h2><a name="TrustedBSD-Mandatory-Access-Control-(MAC)" href="#TrustedBSD-Mandatory-Access-Control-(MAC)" id="TrustedBSD-Mandatory-Access-Control-(MAC)">TrustedBSD Mandatory Access Control (MAC)</a></h2><p>
-	Contact:
-	Robert
-	Watson
-       &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	TrustedBSD Discussion Mailing List
-       &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-    <p>It's been a busy few months, with a variety of development,
-      documentation, and public relations activities.  The MAC Framework,
-      our pluggable kernel access control mechanism for FreeBSD, has
-      matured substantially, and large parts of it were merged to the
-      main FreeBSD tree over July and August.</p>
-    <p>A variety of entry point changes were made, including: component
-      names are now passed to VFS namespace VOPs; aggressive caching
-      of MAC labels in vnodes; mmap memory access downgrades on subject
-      relabel; check for access()/eaccess(); checks for vnode read,
-      write, ioctl, pool, permitting revocation post-open() by aware
-      policies; labeling and access control checks for pipe IPC objects,
-      clean up of socket/visibility checks; checks for socket bind,
-      connect, listen, ....; many locking improvements and assertions,
-      especially for vnodes, processes; framework now supports partial
-      label updates on subjects and objects; credential management in
-      'struct file' improved so that active_cred and file_cred are
-      more carefully distinguished and passed to MAC framework
-      explicitly; accounting system uses cached credentials for
-      write operations now; socreate() can use cached credential to
-      label sockets fixing deferred nfs socket connections and
-      reconnections with TCP; kse interactions with proc1 fixed;
-      IO_NOMACCHECK flag to vn_rdwr() for internal use to avoid
-      redundant or incorrect MAC checks on aio vnode operations;
-      mac_syscall() policy function demux; su no longer changes MAC
-      labels by default; mac_get_pid() to support ps and getpmac -p pid;
-      mmap revocation defaults to "fail stop"; MAC_DEBUG wraps atomic
-      label counters; UFS2 extended attributes supported; initial
-      port of LOMAC to the MAC framework; update all policies for all
-      these changes; merge of KSE III; merge of nmount(); upgrade of
-      ugidfw to speak user and group names; libugidfw; many namespace
-      and naming consistency improvements; module dependencies on
-      MAC framework; large scale merging of MAC functionality to the
-      main FreeBSD tree.  KDE interfaces to common management
-      activities.</p>
-    <p>Wrote and taught full-day MAC framework tutorial at STOS
-      BSD and Darwin Security Symposium; first draft of MAC framework
-      architecture and API guide.  This is now in the Developer's
-      Handbook.</p>
-    <p>Next couple of months will bring continued maturity improvements,
-      labeling and protection of more objects; VFS performance
-      improvements; better support for UFS2 EAs and separate EA
-      entries for each policy; improved support for LOMAC; MLS
-      compartments; IPsec security association labeling; improved
-      SEBSD FLASK/TE port; and much more.</p>
-  <hr /><h2><a name="UFS2---64bit-UFS-with-native-extended-attributes" href="#UFS2---64bit-UFS-with-native-extended-attributes" id="UFS2---64bit-UFS-with-native-extended-attributes">UFS2 - 64bit UFS with native extended attributes</a></h2><p>
-	Contact:
-	Poul-Henning
-
-	Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Kirk
-
-	McKusick
-       &lt;<a href="mailto:mckusick@FreeBSD.org">mckusick@FreeBSD.org</a>&gt;
-	</p>
-    <p>The UFS2 filesystem approaches feature completion:  Extended
-      attribute functionality have been added, including a new
-      compound modification API and basic testing has been passed.</p>
-
-  <hr /><h2><a name="VM-issues-in--stable" href="#VM-issues-in--stable" id="VM-issues-in--stable">VM issues in -stable</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://apollo.backplane.com/FreeBSD/wiring_patch_03.diff" title="http://apollo.backplane.com/FreeBSD/wiring_patch_03.diff">VM corruption patch for -stable.</a></td><td>
-	    URL: <a href="http://apollo.backplane.com/FreeBSD/wiring_patch_03.diff" title="VM corruption patch for -stable.">http://apollo.backplane.com/FreeBSD/wiring_patch_03.diff</a></td></tr></table><p>
-	Contact:
-	Matthew
-
-	Dillon
-       &lt;<a href="mailto:dillon@FreeBSD.org">dillon@FreeBSD.org</a>&gt;
-	</p>
-    <p>Work is in progress to MFC a number of bug fixes related
-    to vm_map corruption into -stable.  This work is probably
-    too involved to make it into the 4.7 release but is expected to
-    be committed just after the freeze is lifted.  The corruption
-    in question typically occurs in large-memory systems under heavy
-    loads and typically panics or KPFs (kernel-page-fault's) the machine
-    in a vm_map related function.</p>
-  <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2002-09-2002-10.html b/website/content/en/status/report-2002-09-2002-10.html
deleted file mode 100644
index 8cc5e7fbae..0000000000
--- a/website/content/en/status/report-2002-09-2002-10.html
+++ /dev/null
@@ -1,949 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction:</h1><p>Another busy pair of months at the FreeBSD Project have brought
-    substantial maturity and feature completeness to the fledgeling
-    5.0-CURRENT branch.  And just in time too, because by the time
-    you read the next status report, we hope that you'll have
-    FreeBSD 5.0 running on your desktop!  Over the past two months,
-    we've seen an upgrade of sparc64 to Tier 1 (Fully Supported)
-    status, integration of a high quality storage encryption module,
-    the commit of hardware-accelerated IPsec support, the addition of
-    a general-purpose "Device Daemon" to process hardware
-    attach/detach events to replace earlier single-purpose and
-    bus-specific daemons, the commit of RAIDFrame, and the improved
-    maturity of the TrustedBSD work.  We've also seen another
-    successful release of the 4.x branch, 4.7-RELEASE, which will
-    continue to be the production supported platform as 5.X is brought
-    in for landing.</p><p>Over the next two months, the FreeBSD Project will be focused
-    almost entirely on making 5.0 a success: improving system
-    stability and performance, as well as increasing the pool of
-    applications that build and run on 5.0.  The Release Engineering
-    team will have announced the 5.0 code freeze, and released DP2 by
-    the time you read this.  Following DP2 will be a series of Release
-    Candidates (RC's), and then the release itself.  If you're
-    interested in getting involved in the testing process, please lend
-    a hand -- a spare box and a copy of the DP and RC ISOs burnt onto
-    CD will make a difference.  The normal caveats associated with
-    pre-release versions of operating systems apply!  You may also be
-    interested in reading the Early Adopter's guide produced by the
-    Release Engineering team to help determine when a transition from
-    the 4.x branch to the 5.x branch will be appropriate for you and
-    your organization.</p><p>Thanks,</p><p>Robert Watson, Scott Long</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph implementation)</a></li><li><a href="#BSDCon-2003">BSDCon 2003</a></li><li><a href="#C99-&amp;-POSIX-Conformance-Project">C99 &amp; POSIX Conformance Project</a></li><li><a href="#DEVD-Status-Report">DEVD Status Report</a></li><li><a href="#Fast-IPsec-Status">Fast IPsec Status</a></li><li><a href="#FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#FreeBSD/MIPS">FreeBSD/MIPS</a></li><li><a href="#FreeBSD/sparc64-Status-Report">FreeBSD/sparc64 Status Report</a></li><li><a href="#GBDE---Geom-Based-Disk-Encryption">GBDE - Geom Based Disk Encryption</a></li><li><a href="#GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></li><li><a href="#Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></li><li><a href="#jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KDE-FreeBSD-Project">KDE FreeBSD Project</a></li><li><a href="#KSE-Project-Status">KSE Project Status</a></li><li><a href="#LibH">LibH</a></li><li><a href="#NEWCARD-Status-Report">NEWCARD Status Report</a></li><li><a href="#OSF-DCE-1.1-RPC-UUIDs">OSF DCE 1.1 RPC UUIDs</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#RAIDFrame-for-FreeBSD">RAIDFrame for FreeBSD</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#TrustedBSD-Project">TrustedBSD Project</a></li><li><a href="#Wireless-Networking-Status">Wireless Networking Status</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">Bluetooth stack for FreeBSD (Netgraph implementation)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.geocities.com/m_evmenkin/" title="http://www.geocities.com/m_evmenkin/">Latest snapshot</a></td><td>
-	    URL: <a href="http://www.geocities.com/m_evmenkin/" title="Latest snapshot">http://www.geocities.com/m_evmenkin/</a></td></tr><tr><td><a href="http://bluez.sf.net" title="http://bluez.sf.net">Linux BlueZ stack</a></td><td>
-	    URL: <a href="http://bluez.sf.net" title="Linux BlueZ stack">http://bluez.sf.net</a></td></tr><tr><td><a href="http://sourceforge.net/projects/openobex" title="http://sourceforge.net/projects/openobex">OpenOBEX</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/openobex" title="OpenOBEX">http://sourceforge.net/projects/openobex</a></td></tr></table><p>
-	Contact:
-        Maksim
-        Yevmenkin
-       &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-    <p>I'm very pleased to announce that another engineering release is
-    available for download at
-    http://www.geocities.com/m_evmenkin/ngbt-fbsd-20021104.tar.gz</p>
-
-    <p>This release features minor bug fixes and new OpenOBEX library
-    port. The snapshot includes support for H4 UART and H2 USB transport
-    layers, Host Controller Interface (HCI), Link Layer Control and
-    Adaptation Protocol (L2CAP) and Bluetooth sockets layer. It also
-    comes with several user space utilities that can be used to configure
-    and test Bluetooth devices. Also there are several man pages.</p>
-
-    <p>Service Discovery Protocol (SDP) port has been updated to
-    version 0.8. (ported from BlueZ-sdp-0.8). Most of the RFCOMM
-    issues have been resolved and now rfcommd works with Windows
-    (3COM, Xircom and Widcomm) and Linux stacks.</p>
-
-    <p>New supported USB device - EPoX BT-DG02 dongle. Also I have
-    received successful report about Mitsumi USB dongle and C413S
-    Bluetooth enabled cell phone (L2CAP and SDP works, waiting on
-    RFCOMM report).</p>
-
-    <p>I'm currently working on OBEX server (Push and File Transfer
-    profiles) which will be based on OpenOBEX library (included
-    in the snapshot).</p>
-  <hr /><h2><a name="BSDCon-2003" href="#BSDCon-2003" id="BSDCon-2003">BSDCon 2003</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.usenix.org/events/bsdcon03/cfp/" title="http://www.usenix.org/events/bsdcon03/cfp/">BSDCon 2003 Call For Papers</a></td><td>
-	    URL: <a href="http://www.usenix.org/events/bsdcon03/cfp/" title="BSDCon 2003 Call For Papers">http://www.usenix.org/events/bsdcon03/cfp/</a></td></tr></table><p>
-	Contact:
-        Gregory
-        Shapiro
-       &lt;<a href="mailto:gshapiro@FreeBSD.org">gshapiro@FreeBSD.org</a>&gt;
-	</p>
-
-    <p>The BSDCon 2003 Program Committee invites you to contribute
-    original and innovative papers on topics related to BSD-derived
-    systems and the Open Source world. Topics of interest include
-    but are not limited to:</p>
-
-    <ul>
-      <li>Embedded BSD application development and deployment</li>
-      <li>Real world experiences using BSD systems</li>
-      <li>Using BSD in a mixed OS environment</li>
-      <li>Comparison with non-BSD operating systems; technical,
-      practical, licensing (GPL vs. BSD)</li>
-      <li>Tracking open source development on non-BSD systems</li>
-      <li>BSD on the desktop</li>
-      <li>I/O subsystem and device driver development</li>
-      <li>SMP and kernel threads</li>
-      <li>Kernel enhancements</li>
-      <li>Internet and networking services</li>
-      <li>Security</li>
-      <li>Performance analysis and tuning</li>
-      <li>System administration</li>
-      <li>Future of BSD</li>
-    </ul>
-
-    <p>Submissions in the form of extended abstracts are due by
-    April 1, 2003. Be sure to review the extended abstract
-    expectations before submitting. Selection will be based on the
-    quality of the written submission and whether the work is of
-    interest to the community.</p>
-
-    <p>We look forward to receiving your submissions!</p>
-
-  <hr /><h2><a name="C99-&amp;-POSIX-Conformance-Project" href="#C99-&amp;-POSIX-Conformance-Project" id="C99-&amp;-POSIX-Conformance-Project">C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/c99/" title="http://www.FreeBSD.org/projects/c99/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/c99/" title="">http://www.FreeBSD.org/projects/c99/</a></td></tr></table><p>
-	Contact:
-        Mike
-        Barcroft
-       &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        FreeBSD-Standards Mailing List
-       &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-    <p>October 10, 2002 marked the one year anniversary of our project.
-    During that time we have made significant advances in FreeBSD's
-    standards conformance.  FreeBSD 5.0-RELEASE will be the showcase
-    for most of our hard work.  We hope that our tireless effort has
-    had a positive effect on FreeBSD and software vendors that
-    maintain or are considering porting their software to FreeBSD.</p>
-
-    <p>On the API front, _Exit(3) (an alias for _exit(2)) was added,
-    sysconf(3) was update for POSIX.1-2001, and some of the glob(3)
-    additions were MFC'd.  The insque(), lsearch(), and remque()
-    family of functions were reimplemented and moved to libc from
-    libcompat.  Several wide character functions were implemented,
-    including all printf() and scanf() variants.  Finally, support
-    for wide character format types (%C, %S, %lc, %ls) were added to
-    printf(3).</p>
-
-    <p>Work on utility conformance continued as getconf(1)'s compliance
-    was updated, c99(1) (a new version of c89(1)) was implemented,
-    and cd(1) and command(1) changes were MFC'd.</p>
-
-    <p>Almost 20 headers were brought up to conformance with applicable
-    standards.  Not much work remains to fix conformance issues in
-    the remaining standard headers.  Work in this area, as well as
-    others, has slowed down in preparation for 5.0-RELEASE.</p>
-  <hr /><h2><a name="DEVD-Status-Report" href="#DEVD-Status-Report" id="DEVD-Status-Report">DEVD Status Report</a></h2><p>
-	Contact:
-        Warner
-        Losh
-       &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-    <p>DEVD has been integrated into FreeBSD current.  It was
-    integrated in an incomplete state.  However, it is useful in the
-    state that it is in for doing simple things like running
-    camcontrol rescan when a SCSI pcmcia card is inserted, or running
-    /etc/pccard_ether with an ethernet card is inserted.  The more
-    sophisticated regular expression matching is not yet complete.
-    Devd only does actions on device arrival and departure, but does
-    not yet do anything with unknown devices.  In addition to
-    listening for device events, there is some desire to have
-    /dev/devctl also allow for some direct control of the device
-    tree.</p>
-  <hr /><h2><a name="Fast-IPsec-Status" href="#Fast-IPsec-Status" id="Fast-IPsec-Status">Fast IPsec Status</a></h2><p>
-	Contact:
-        Sam
-        Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-  <p>The main goal of this project is to modify the IPsec protocols to use
-  the kernel-level crypto subsystem imported from OpenBSD (see elsewhere). A
-  secondary goal is to do general performance tuning of the IPsec
-  protocols.</p>
-
-  <p>This work was committed to -current.  To configure it for use specify
-  options FAST_IPSEC in your system configuration file.  At present support is
-  limited to IPv4.</p>
-  <hr /><h2><a name="FreeBSD-GNOME-Project" href="#FreeBSD-GNOME-Project" id="FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Homepage.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project Homepage.">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-        Joe
-        Marcus
-       &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Maxim
-        Sobolev
-       &lt;<a href="mailto:sobomax@FreeBSD.org">sobomax@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Adam
-        Weinberger
-       &lt;<a href="mailto:adamw@FreeBSD.org">adamw@FreeBSD.org</a>&gt;
-	</p>
-    <p>These last two months have seen quite a lot of GNOME activity.
-    GNOME has started releasing development snapshots of the upcoming
-    GNOME 2.2 desktop.  FreeBSD porting has begun outside of the
-    main ports tree in the
-    <a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi" shape="rect">MarcusCom
-    CVS repository</a>.  If you are interested in testing the new
-    desktop, follow the instructions on the aforementioned cvsweb
-    URL, and checkout the "ports" module.</p>
-
-    <p>Evolution 1.2 is also close at hand.  Ximian has posted its
-    first release candidate, 1.1.90, which has been ported to FreeBSD,
-    and is available from the MarcusCom CVS repo listed above.  As
-    soon as Ximian officially releases Evolution 1.2, it will be placed in
-    the FreeBSD ports tree.</p>
-
-    <p>The Mozilla ports have received numerous updates.  We are now
-    tracking all three released Mozilla versions.  The mozilla-vendor
-    port is tracking the 1.0.x branch, mozilla is tracking 1.1.x, and
-    mozilla-devel is tracking 1.2.x.  The mozilla-devel port now
-    has support for anti-aliased fonts as well as a GTK+-2 interface</p>
-
-    <p>Finally, the GNOME team would like to welcome its newest
-    team member, Adam Weinberger.  Adam has been submitting patches for
-    both GNOME ports as well as documentation.  Currently, he has been
-    active in the GNOME 2.2 porting effort.  We are happy to have him.</p>
-  <hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java/" title="http://www.FreeBSD.org/java/">FreeBSD Java Project</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java/" title="FreeBSD Java Project">http://www.FreeBSD.org/java/</a></td></tr></table><p>
-	Contact:
-        Greg
-        Lewis
-       &lt;<a href="mailto:glewis@FreeBSD.org">glewis@FreeBSD.org</a>&gt;
-	</p>
-    <p>Since the last status report the BSD Java Porting Team has continued
-    to make steady progress.  The most exciting news we have is courtesy
-    of our newest team member, Alexey Zelkin of FreeBSD committer fame.
-
-    <ul>
-      <li>Thanks to a lot of hard work, primarily by Alexey, the project
-      is very close to being able to release our first patch set for
-      the 1.4 JDK.  Things are reportedly working quite well under
-      -CURRENT, with -STABLE support being only marginally behind (thanks
-      in part to the libc_r MFC by Max Khon).</li>
-      <li>The project has released another patchset for the 1.2.2 JDK, mainly
-      to add support for OpenBSD and for JPDA.  Most of the projects
-      energy at the moment is focused on 1.3 and 1.4, however we still
-      hope to back port relevant fixes if appropriate to 1.2.2.</li>
-      <li>Nate Williams has been hard at work behind the scenes migrating
-      us to a new CVS server which has kindly been donated by the
-      FreeBSD Foundation.  The Project appreciates the continued
-      support of the Foundation.  Please support them so they can
-      continue to support us and other important FreeBSD efforts!</li>
-    </ul>
-    </p>
-  <hr /><h2><a name="FreeBSD/MIPS" href="#FreeBSD/MIPS" id="FreeBSD/MIPS">FreeBSD/MIPS</a></h2><p>
-	Contact:
-        Juli
-        Mallett
-       &lt;<a href="mailto:jmallett@FreeBSD.org">jmallett@FreeBSD.org</a>&gt;
-	</p>
-    <p>A mailing list was created, freebsd-mips, and a Perforce branch
-    was created in //depot/projects/mips.  Changes which will be
-    necessary to allow multiple MIPS (and PowerPC) metaports to exist
-    under one architecture port were made, and are being pushed back
-    into the main FreeBSD tree.  Some preliminary header work has been
-    done, and porting the ARCBIOS interfaces to the kernel has begun.
-    The toolchain in tree was updated and modified in places to support
-    a FreeBSD/MIPS (Big Endian) target, in the Perforce branch.  Some
-    early boot code has proven the GDB MIPS simulator to work, for at
-    least R3000 code, though whether R3000 will be supported has been
-    under discussion.  Some initial architectural decisions were also
-    made, to steer current work.</p>
-  <hr /><h2><a name="FreeBSD/sparc64-Status-Report" href="#FreeBSD/sparc64-Status-Report" id="FreeBSD/sparc64-Status-Report">FreeBSD/sparc64 Status Report</a></h2><p>
-	Contact:
-        Jake
-        Burkholder
-       &lt;<a href="mailto:jake@FreeBSD.org">jake@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Thomas
-        Moestl
-       &lt;<a href="mailto:tmm@FreeBSD.org">tmm@FreeBSD.org</a>&gt;
-	</p>
-    <p>A lot has happened recently for the sparc64 port.  Sysinstall and
-    make release work and can be used to build installable snapshots.
-    The gdb5.3 port now works, and, thanks to Thomas Moestl, kernel crash
-    dumps are supported which can be analyzed by gdb.  These 2 items are
-    the last things considered necessary by the Core team for FreeBSD/sparc64
-    to be a Tier 1 architecture, which means that 5.0-RELEASE for sparc64
-    will be officially supported by the release engineering team and by the
-    security officer team.</p>
-
-    <p>Recently Jake Burkholder has been working on alternate installation
-    methods other than bootable iso, including a mini-root filesystem which
-    can be written to the swap partition of an existing machine.  Thomas
-    Moestl has been putting some finishing touches on the release process,
-    ensuring that the release documentation can be built properly, and that
-    the port readme files can be generated by the release process.</p>
-
-    <p>An experimental iso built with make release is now available on the
-    freebsd ftp site and mirrors in
-    /pub/FreeBSD/development/sparc64/5.0-20021031-SNAP.  It is expected that
-    by the middle of November new 5.0-SNAP releases will be available every
-    few days for download and for ftp install, cpu power and bandwidth
-    permitting.</p>
-  <hr /><h2><a name="GBDE---Geom-Based-Disk-Encryption" href="#GBDE---Geom-Based-Disk-Encryption" id="GBDE---Geom-Based-Disk-Encryption">GBDE - Geom Based Disk Encryption</a></h2><p>
-	Contact:
-        Poul-Henning
-        Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-    <p>GBDE has been committed to -current.</p>
-
-    <p>The "Geom Based Disk Encryption" module provides a mechanism for
-    very strong encryption of a GEOM "disk".  The algorithm has passed
-    informal review by a couple of seasoned crypto heavy-weights.
-    Any GEOM device can be protected with GBDE, entire physical disks,
-    MBR slices, BSD partitions etc etc.  Booting from an encrypted
-    partition is not possible, however.</p>
-
-    <p>The focus of GBDE is to protect a "cold" disk media.  (FreeBSD is
-    not equipped well for protecting key material on a running system
-    from being compromised.)
-    For a cold media, the only feasible attack on a GBDE protected
-    media is guessing the pass-phrase.</p>
-
-    <p>Summary of the GBDE multilevel protection scheme:  Up to four
-    separate pass-phrases can unlock their own separate copies of
-    the 2048 bit masterkey.  The master-keys are protected using
-    AES/256/CBC keyed with a SHA-2 hash derived from the pass-phrase.
-    A salted MD5 hash over the sectoroffset "cherry-picks" which masterkey
-    bytes participate in the MD5 hash which generates the "kkey"
-    for each particular sector.  The kkey AES/128/CBC encrypts the PRNG
-    produced single-use key which AES/128/CBC encrypts the actual
-    sector data.</p>
-
-    <p>GBDE has features for master-key destruction and pass-phrase
-    invalidation.</p>
-
-    <p>See gbde(4) and gbde(8) for more details.</p>
-
-    <p>This software was developed for the FreeBSD Project by
-    Poul-Henning Kamp and NAI Labs, the Security Research
-    Division of Network Associates, Inc.  under DARPA/SPAWAR
-    contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA
-    CHATS research program.</p>
-  <hr /><h2><a name="GEOM---generalized-block-storage-manipulation" href="#GEOM---generalized-block-storage-manipulation" id="GEOM---generalized-block-storage-manipulation">GEOM - generalized block storage manipulation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~phk/Geom/" title="http://www.FreeBSD.org/~phk/Geom/">Old concept paper here.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~phk/Geom/" title="Old concept paper here.">http://www.FreeBSD.org/~phk/Geom/</a></td></tr></table><p>
-	Contact:
-        Poul-Henning
-        Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-    <p>The GEOM code is now the default on most (if not all ?) architectures
-    and the few remaining issues in libdisk/sysinstall is being hashed
-    out.</p>
-
-    <p>Although we are far from finished developing GEOM, its current feature
-    set is a significant step forward for FreeBSD, providing not only
-    immediate relief for new architectures (sparc64, ia64 etc) but also
-    because it is designed as SMPng code from the start.</p>
-
-    <p>This software was developed for the FreeBSD Project by
-    Poul-Henning Kamp and NAI Labs, the Security Research
-    Division of Network Associates, Inc.  under DARPA/SPAWAR
-    contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA
-    CHATS research program.</p>
-  <hr /><h2><a name="Hardware-Crypto-Support-Status" href="#Hardware-Crypto-Support-Status" id="Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></h2><p>
-	Contact:
-        Sam
-        Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>The goal of this project is to import the OpenBSD kernel-level crypto
-    subsystem. This facility provides kernel- and user-level access to hardware
-    crypto devices for the calculation of cryptographic hashes, ciphers, and
-    public key operations. The main clients of this facility are the kernel RNG
-    (/dev/random), network protocols (e.g. IPsec), and OpenSSL (through the
-    /dev/crypto device).</p>
-
-    <p>This work was committed to the -current tree.  To configure it for use
-    specify device crypto in your system configuration file or you can load the
-    crypto module.  The /dev/crypto device support is brought in with device
-    cryptodev or by loading the cryptodev module. Two crypto device drivers
-    exist: ubsec for Broadcom-based PCI hardware and hifn for Hifn-based PCI
-    hardware.</p>
-
-    <p>Integration of this work into the -stable source tree should be
-    completed by the time this report is published.</p>
-  <hr /><h2><a name="jp.FreeBSD.org-daily-SNAPSHOTs-project" href="#jp.FreeBSD.org-daily-SNAPSHOTs-project" id="jp.FreeBSD.org-daily-SNAPSHOTs-project">jp.FreeBSD.org daily SNAPSHOTs project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://snapshots.jp.FreeBSD.org/" title="http://snapshots.jp.FreeBSD.org/">Project Webpage</a></td><td>
-	    URL: <a href="http://snapshots.jp.FreeBSD.org/" title="Project Webpage">http://snapshots.jp.FreeBSD.org/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/snapshots/" title="http://www.jp.FreeBSD.org/snapshots/">Project Webpage (in Japanese)</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/snapshots/" title="Project Webpage (in Japanese)">http://www.jp.FreeBSD.org/snapshots/</a></td></tr></table><p>
-	Contact:
-        Makoto
-        Matsushita
-       &lt;<a href="mailto:matusita@jp.FreeBSD.org">matusita@jp.FreeBSD.org</a>&gt;
-	</p>
-    <p>Recent 5-current release procedure troubles prevent the
-    project from releasing a new snapshots.  But 5-current FreeBSD/i386
-    release is back again in late Oct/2002!  I have a plan to build
-    daily FreeBSD/sparc64 snapshots for 5-current.  Stay tuned...</p>
- <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project">http://www.jp.FreeBSD.org/man-jp/</a></td></tr><tr><td><a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-4.7.0/ja-man-doc-4.7.tgz" title="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-4.7.0/ja-man-doc-4.7.tgz">package ja-man-doc-4.7.tgz</a></td><td>
-	    URL: <a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-4.7.0/ja-man-doc-4.7.tgz" title="package ja-man-doc-4.7.tgz">ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-4.7.0/ja-man-doc-4.7.tgz</a></td></tr></table><p>
-	Contact:
-        Kazuo
-        Horikawa
-       &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-    <p>For 4.7-RELEASE, we privately published package ja-man-doc-4.7.tgz
-    which consists of man[1256789] entries 10 days after the 4.7-RELEASE
-    release date.  Man3 update god no progress, as updating other sections
-    busied us.  We decided to suspend man3 update officially, as we need to
-    spend most of our time to catch up with the forthcoming 5.0-RELEASE.</p>
-  <hr /><h2><a name="KDE-FreeBSD-Project" href="#KDE-FreeBSD-Project" id="KDE-FreeBSD-Project">KDE FreeBSD Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freebsd.kde.org" title="http://freebsd.kde.org">KDE/FreeBSD Website</a></td><td>
-	    URL: <a href="http://freebsd.kde.org" title="KDE/FreeBSD Website">http://freebsd.kde.org</a></td></tr><tr><td><a href="http://rabarber.fruitsalad.org/" title="http://rabarber.fruitsalad.org/">KDE/FreeBSD Build Server</a></td><td>
-	    URL: <a href="http://rabarber.fruitsalad.org/" title="KDE/FreeBSD Build Server">http://rabarber.fruitsalad.org/</a></td></tr></table><p>
-	Contact:
-        Will
-        Andrews
-       &lt;<a href="mailto:will@FreeBSD.org">will@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        KDE-FreeBSD
-        Mailinglist
-       &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-    <p>The KDE/FreeBSD team has been working on two major goals during the last
-    two months, Maintenance of the KDE 3.0.x ports and Preparing the
-    upcoming KDE 3.1 Release.</p>
-
-    <p>Maintenance KDE 3.0 conducted by Alan Eldrige: September started with
-    the Removal of the KDE 2.x Ports from the FreeBSD-Repository. Later
-    Packages of KDE 3.0.4 were released and the FreeBSD Ports were updated.</p>
-
-    <p>Preparing for KDE 3.1 conducted by Will Andrews: A lot of effort was
-    spent on Improving the Fruitsalad-Build-System. We are now able to
-    create packages directly from the KDE CVS.</p>
-  <hr /><h2><a name="KSE-Project-Status" href="#KSE-Project-Status" id="KSE-Project-Status">KSE Project Status</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~julian" title="http://www.FreeBSD.org/~julian">some links</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~julian" title="some links">http://www.FreeBSD.org/~julian</a></td></tr></table><p>
-	Contact:
-        Julian
-        Elischer
-       &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        David
-        Xu
-       &lt;<a href="mailto:davidxu@FreeBSD.org">davidxu@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Jonathon
-        Mini
-       &lt;<a href="mailto:mini@FreeBSD.org">mini@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Daniel
-        Eischen
-       &lt;<a href="mailto:deischen@FreeBSD.org">deischen@FreeBSD.org</a>&gt;
-	</p>
-    <p>The KSE code has now all the basic kernel functionality
-    to start being used by the userland. There are still things
-    to be done for testing and familiarization.</p>
-
-    <p>General system utilities have not yet been changed.
-    e.g. ps and top etc. need to know about threads.</p>
-
-    <p>There is quite a lot of code in the kernel that still
-    assumes that there is one thread in a process. Signals are
-    not yet handled in the final manner (though they are
-    delivered to a random thread in the process :-/ ).</p>
-
-    <p>The system calls and datastructures are now however in
-    place. The test program successfully starts several threads
-    that can be scheduled on different processors, and closes
-    them down again. The userland is probably going to be able
-    to do simple scheduling of pthread threads using KSE by the
-    time that this report is published.</p>
-
-    <p>I still need someone to take over the "official" web page
-    since jason left. LaTeX sure isn't my thing. </p>
-    <hr /><h2><a name="LibH" href="#LibH" id="LibH">LibH</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/libh.html" title="http://www.FreeBSD.org/projects/libh.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/libh.html" title="">http://www.FreeBSD.org/projects/libh.html</a></td></tr><tr><td><a href="http://rtp1.slowblink.com/~libh/" title="http://rtp1.slowblink.com/~libh/">LibH development page</a></td><td>
-	    URL: <a href="http://rtp1.slowblink.com/~libh/" title="LibH development page">http://rtp1.slowblink.com/~libh/</a></td></tr></table><p>
-	Contact:
-        Antoine
-        Beaupr�
-       &lt;<a href="mailto:anarcat@anarcat.ath.cx">anarcat@anarcat.ath.cx</a>&gt;
-	<br />
-	Contact:
-        Alexander
-        Langer
-       &lt;<a href="mailto:alex@FreeBSD.org">alex@FreeBSD.org</a>&gt;
-	</p>
-    <p>Not much since the last status report, except that we now have
-    the repo and development web page back online, thanks to the
-    services of John De Boskey who freely provided the necessary
-    hardware and bandwidth to host the project. We have also ported
-    LibH to GCC 3.x, so that it can compile on -CURRENT
-    correctly. This, however, broke tvision, which doesn't compile
-    under GCC 3.x, so we moved to rhtvision but this caused linking
-    problems so we're stuck with no console front end, for now.</p>
-
-    <p>Work on a Hui rewrite and SWIG bindings stalled. Alex was able
-    to come up with a simple patch to make the ports system use
-    LibH's pkg_create script to build libh packages, so we're
-    getting closer to a real pkg_create(1) drop-in replacement. I
-    rewrote the milestone list to show a bit more relevant and
-    encouraging tasks that will be dealt with in order to really
-    push LibH forward.</p>
-  <hr /><h2><a name="NEWCARD-Status-Report" href="#NEWCARD-Status-Report" id="NEWCARD-Status-Report">NEWCARD Status Report</a></h2><p>
-	Contact:
-        Warner
-        Losh
-       &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-    <p>Work on newcard continues.  A number of bugs have been fixed in
-    the last few months.  You are now able to load and unload drivers
-    (including the bridge) to test changes to pccard and/or cardbus
-    bus code.  It is now possible to load a driver that has a pccard
-    attachment and have a previously inserted card probe and attach.
-    This is also true for CardBus.  A number of issues remain to be
-    solved before 5.0.  However, with the integration of devd into the
-    tree nearly all of old functionality of OLDCARD is now present in
-    NEWCARD (the biggest remaining parts are power control for the
-    sockets, as well as pccardc dumpcis).</p>
-  <hr /><h2><a name="OSF-DCE-1.1-RPC-UUIDs" href="#OSF-DCE-1.1-RPC-UUIDs" id="OSF-DCE-1.1-RPC-UUIDs">OSF DCE 1.1 RPC UUIDs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/lib/libc/uuid" title="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/lib/libc/uuid"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/lib/libc/uuid" title="">http://www.FreeBSD.org/cgi/cvsweb.cgi/src/lib/libc/uuid</a></td></tr></table><p>
-	Contact:
-        Marcel
-        Moolenaar
-       &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	</p>
-    <p>Universally Unique Identifiers (UUIDs) are 128 bit values that may
-    be generated independently on separate nodes (hosts), which result in
-    globally unique strings.  UUIDs are also known as Globally Unique
-    Identifiers (GUIDs).  The UUID support for FreeBSD (libc) conforms to the
-    DCE 1.1 RPC specification.</p>
-
-    <p>UUID support has been added to FreeBSD -CURRENT, and will be available
-    in version 5.0.  It is being extensively used in GPT partition handling
-    for IA-64 platform.  For now, a simple manual page has been provided,
-    which outlines information about the provided uuid routines.  Many
-    documentation additions and enhancements to uuidgen(1) are in the
-    pipeline.</p>
-  <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-        Peter
-        Grehan
-       &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-    <p>The PowerPC port has been running diskless on NewWorld G3/G4
-    machines for a while now. A GEOM module to support Apple Partition
-    Maps is being written. There should be an installable ISO image
-    available in the near future.</p>
-  <hr /><h2><a name="RAIDFrame-for-FreeBSD" href="#RAIDFrame-for-FreeBSD" id="RAIDFrame-for-FreeBSD">RAIDFrame for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~scottl/rf" title="http://people.FreeBSD.org/~scottl/rf">Project homepage</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~scottl/rf" title="Project homepage">http://people.FreeBSD.org/~scottl/rf</a></td></tr></table><p>
-	Contact:
-        Scott
-        Long
-       &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-    <p>RAIDFrame was imported into FreeBSD-current in late October, a
-    major milestone after 18 months.  It is still very experimental and
-    not suitable for production environments.  The website contains a
-    lengthy TODO list which I hope to start attending to soon.  Still,
-    I encourage everyone to try it out and report bugs back to me.</p>
-  <hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/relnotes.html" title="http://www.FreeBSD.org/relnotes.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/relnotes.html" title="">http://www.FreeBSD.org/relnotes.html</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-    <p>The Release Engineering (RE) team completed and released
-    FreeBSD 4.7 on 10 October 2002.  This release features updates
-    for a number of contributed software programs in the base
-    system, as well as all of the security and bug fixes from
-    FreeBSD 4.6.2.  The next release in the 4.X series will be
-    FreeBSD 4.8, which has a scheduled release date of 1 February
-    2003.</p>
-
-    <p>Before that time, however, will be the release of FreeBSD 5.0.
-    Thus far, we have not been able to release the 5.0-DP2 developer
-    snapshot due to various stability issues.  Thanks to much effort
-    from many of our fellow developers, we believe that most of
-    these have been resolved.  The RE team wishes to emphasize that
-    FreeBSD 5.0 will involve new code and features that have not
-    seen widespread testing, and that more conservative users may
-    wish to continue to track the 4.X series for the near-term
-    future.  To provide more information on these issues, we have
-    added an Early Adopter's Guide to the release documentation for
-    5.0.</p>
-
-    <p>Brian Somers has resigned from the RE team due to increased
-    time pressures.  We thank him for all of his help with FreeBSD
-    4.5, 4.6, 4.6.2, and 4.7, and we hope to continue working with
-    him as a fellow developer.</p>
-
-    <p>Scott Long has graciously offered to help improve the
-    communication between the RE team and the rest of the developer
-    community.  We greatly appreciate his assistance.</p>
-  <hr /><h2><a name="TrustedBSD-Project" href="#TrustedBSD-Project" id="TrustedBSD-Project">TrustedBSD Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD web site</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD web site">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-        Robert
-        Watson
-       &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        TrustedBSD Discussion Mailing List
-       &lt;<a href="mailto:trustedbsd-discuss@FreeBSD.org">trustedbsd-discuss@FreeBSD.org</a>&gt;
-	</p>
-    <p>Most progress on TrustedBSD over the last two months related
-    to improving the maturity of the ACL and MAC implementations,
-    and merging new aspects of those features into the primary
-    FreeBSD CVS Repository for inclusion in FreeBSD 5.0.  This
-    included fixes to run better on sparc64, improved tuning
-    of what system objects are mediated, locking fixes and
-    optimizations especially relating to the vnode and pipe
-    implementations, improved support for MAC labeling on symlinks,
-    support for asynchronous process label changes as required
-    in some locking situations, remove use of "temporary labels"
-    and prefer use of object type specific labels reducing
-    redundant and/or confusing label management code in policies,
-    improve avoidance of memory allocation in M_NOWAIT scenarios
-    for socket allocation in the syncache, mediation of link
-    operations, race condition fixes for devfs involving label
-    creation, improve handling of VM events such as mmaping,
-    improve mediation of socket send/receive events (as
-    distinguished from socket transmit/deliver events), support
-    for manipulating EAs on symlinks using new system calls,
-    support for MNT_ACLS and MNT_MULTILABEL flags at mount time,
-    as well as FS_ACLS and FS_MULTILABEL superblock flags to
-    key useful defaults using tunefs, correction of a memory leak
-    in the UFS ACL code, enable UFS ACL support by default in
-    GENERIC, mediation points for file creation, deletion, and
-    rename, support for a mac_execve() execution interface in
-    the style of SELinux's execve_secure() permitting a label
-    transition request as part of the exec operation for policies
-    that support it, more consistent handling of NFS lookups,
-    support for labeling of multicast encapsulated packets, ATM
-    packet labeling, FDDI packet labeling, STF packet labeling,
-    revised label interface that avoids userland parsing of
-    per-policy elements, reducing us to a single instance of
-    parsing and printing for each policy (and further abstracting
-    policy implementation details from the library code).</p>
-
-    <p>Also, change to single-level sockets for Biba and MLS
-    policies, support for partial label updates for Biba and MLS,
-    addition of mac.9 man page, revised user API system calls,
-    implementation of mac_get_pid(), and various other related
-    bits, creation of mac.conf(5) to specify label defaults,
-    checks for various system operations including swapon(),
-    settime(), and sysctl(), reboot(), acct(), introduction of
-    command line utilities for maintaining file and process labels,
-    support for user labels tied to login class, su support for
-    label changes, ifconfig support for interface labels, ps
-    support for process labels, ls support for file labels, ftpd
-    support for login labels, development of the Biba and MLS
-    notions of privilege, and a move to C99 sparse structure
-    initialization, restoring full type checking for policy entry
-    points.</p>
-  <hr /><h2><a name="Wireless-Networking-Status" href="#Wireless-Networking-Status" id="Wireless-Networking-Status">Wireless Networking Status</a></h2><p>
-	Contact:
-        Sam
-        Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>The goal of this project is to improve the wireless networking support
-    in the system.  The initial work will incorporate the 802.11 link layer
-    done by Atsushi Onoe for NetBSD.  This core support code implements the
-    basic 802.11 protocols required for Station and AP operation in BSS, IBSS,
-    and Ad Hoc modes of operation. Wireless device drivers will then be revised
-    to use this common code instead of their private implementations.</p>
-
-    <p>Following this initial stage the wireless networking support will be
-    extended to support functionality needed for workgroup, enterprise, and
-    metropolitan (e.g. mesh) networking environments.  This will include full
-    power management support, the 802.1D spanning tree protocol for running
-    multiple AP's in a bridged configuration, QoS support, and enhanced
-    security protocols (LEAP, AES, EAP). Support for new hardware devices is
-    also planned.</p>
-  <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2002-11-2002-12.html b/website/content/en/status/report-2002-11-2002-12.html
deleted file mode 100644
index 1608e801ae..0000000000
--- a/website/content/en/status/report-2002-11-2002-12.html
+++ /dev/null
@@ -1,818 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction:</h1><p>At long last, FreeBSD 5.0 is here.  Along with putting the final
-      polish on the tree, FreeBSD developers somehow found the time to
-      work on other things too.  IA64 took some major steps towards
-      working on the Itanium2 platform, an effort was started to
-      convert all drivers to use busdma and ban vtophys(), hardware
-      crypto support and DEVD hit the tree, NewReno was fixed and
-      effort began on locking down the network layer of the kernel.
-      Also high performance, modular scheduler started taking shape
-      and will be a welcome addition to the kernel soon.</p><p>Looking forward, the focus will be on stabilizing and
-      improving the performance of 5.0.  The RELENG_5 (aka 5-STABLE)
-      branch will be created once we've reached our goals in this
-      area, so hopefully we will get there quickly.  Meanwhile,
-      preparations for the next release from the 4.x series, 4.8,
-      will begin soon.  Of course, the best way to get 5.x to
-      stabilize os to install and run it!</p><p>Thanks,</p><p>Scott Long, Robert Watson</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-    Bluetooth stack for FreeBSD (Netgraph implementation)
-  </a></li><li><a href="#busdma-driver-conversion-project">busdma driver conversion project</a></li><li><a href="#DEVD">DEVD</a></li><li><a href="#Donations-Team-Status-Report">Donations Team Status Report</a></li><li><a href="#Fast-IPsec-Status">Fast IPsec Status</a></li><li><a href="#FFS-volume-label-support">FFS volume label support</a></li><li><a href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></li><li><a href="#FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></li><li><a href="#FreeBSD-Package-Cluster-work">FreeBSD Package Cluster work</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#FreeBSD/ia64-Status">FreeBSD/ia64 Status</a></li><li><a href="#French-FreeBSD-Documentation-Project">French FreeBSD Documentation Project</a></li><li><a href="#Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KGI/FreeBSD-Status-Report">KGI/FreeBSD Status Report</a></li><li><a href="#SMP-aware-scheduler">SMP aware scheduler</a></li><li><a href="#SMP-locking-for-network-stack">SMP locking for network stack</a></li><li><a href="#TCP-congestion-control">TCP congestion control</a></li><li><a href="#TrustedBSD-Project:-Access-Control-Lists">TrustedBSD Project: Access Control Lists</a></li><li><a href="#TrustedBSD-Project:-MAC-Framework">TrustedBSD Project: MAC Framework</a></li><li><a href="#Wireless-Networking-Status">Wireless Networking Status</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-    Bluetooth stack for FreeBSD (Netgraph implementation)
-  </a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.geocities.com/m_evmenkin/" title="http://www.geocities.com/m_evmenkin/">Latest snapshot</a></td><td>
-	    URL: <a href="http://www.geocities.com/m_evmenkin/" title="Latest snapshot">http://www.geocities.com/m_evmenkin/</a></td></tr><tr><td><a href="http://bluez.sf.net" title="http://bluez.sf.net">Linux BlueZ stack</a></td><td>
-	    URL: <a href="http://bluez.sf.net" title="Linux BlueZ stack">http://bluez.sf.net</a></td></tr><tr><td><a href="http://sourceforge.net/projects/openobex" title="http://sourceforge.net/projects/openobex">OpenOBEX</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/openobex" title="OpenOBEX">http://sourceforge.net/projects/openobex</a></td></tr></table><p>
-	Contact:
-        Maksim
-        Yevmenkin
-       &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-    <p>I'm very pleased to announce that all kernel modules and few userland
-      tools made it to the FreeBSD source tree. Many thanks to Julian
-      Elischer.</p>
-
-    <p>Unfortunately no big changes since the last report. Some minor problems
-      have been discovered and patches are available on request. I will prepare
-      all the patches and submit them to Julian for review.</p>
-
-    <p> OBEX server and client (based on OpenOBEX library) is almost complete.
-      I'm currently doing interoperability testing. If anyone has hardware and
-      time please contact me. The HCI security daemon has been implemented and
-      tested with Sony Ericsson T68i cell phone and Windows stack. It is now
-      possible to setup secure Bluetooth connections.</p>
-
-    <p>A few people have complained about RFCOMM daemon. These individuals want
-      to use GPRS and Bluetooth enabled cell phone to access Internet. If you
-      have this problem please contact me for possible workaround. My next goal
-      is to get robust RFCOMM implementation to address all these issues.</p>
-  <hr /><h2><a name="busdma-driver-conversion-project" href="#busdma-driver-conversion-project" id="busdma-driver-conversion-project">busdma driver conversion project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/busdma/" title="http://www.FreeBSD.org/projects/busdma/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/busdma/" title="">http://www.FreeBSD.org/projects/busdma/</a></td></tr></table><p>
-	Contact:
-	Maxime
-
-	Henrion
-       &lt;<a href="mailto:mux@FreeBSD.org">mux@FreeBSD.org</a>&gt;
-	</p>
-    <p>This project has been coming along pretty well.  The amd(4) and
-      xl(4) drivers have now been converted to use the busdma API,
-      sparc64 got the bus_dmamap_load_mbuf() and bus_dmamap_load_uio()
-      functions, and the gem(4) and hme(4) drivers have been updated
-      to use bus_dmamap_load_mbuf() instead of bus_dmamap_load().</p>
-
-    <p>A lot more still needs to be done, as shown on the project's
-      page.  A fair number of conversions are on their way though,
-      and we can expect a fair number of drivers to be converted
-      soon, thanks to all the developers who are working on this
-      project.</p>
-  <hr /><h2><a name="DEVD" href="#DEVD" id="DEVD">DEVD</a></h2><p>
-	Contact:
-	Warner
-	Losh
-       &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-    <p>Devd has been integrated into FreeBSD 5.0-RELEASE.  The
-    integrated code supports a range of configuration options.  The
-    config files are fully parsed now and their actions are
-    performed.</p>
-
-    <p>Future work in this area is likely to be limited to improving
-     the devctl interface.  /dev/devctl likely will be a cloneable
-     device in future versions.  Individual device control via devctl
-     is also planned.</p>
-  <hr /><h2><a name="Donations-Team-Status-Report" href="#Donations-Team-Status-Report" id="Donations-Team-Status-Report">Donations Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/donations/" title="http://www.FreeBSD.org/donations/">Donations main page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/donations/" title="Donations main page">http://www.FreeBSD.org/donations/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/donations/wantlist.html" title="http://www.FreeBSD.org/donations/wantlist.html">FreeBSD developer wantlist</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/donations/wantlist.html" title="FreeBSD developer wantlist">http://www.FreeBSD.org/donations/wantlist.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/donations/donors.html" title="http://www.FreeBSD.org/donations/donors.html">completed donations</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/donations/donors.html" title="completed donations">http://www.FreeBSD.org/donations/donors.html</a></td></tr></table><p>
-	Contact:
-	Michael
-	Lucas
-       &lt;<a href="mailto:donations@FreeBSD.org">donations@FreeBSD.org</a>&gt;
-	</p>
-    <p>The Donations project expedited several dozen donations during
-      2002, and was able to place most of what was offered.  We still
-      are in dire need of SMP and Sparc systems.  You can see
-      information on our needs and donations that have been handled by
-      the team on the donations web page.</p>
-
-    <p>We are relying increasingly upon the developer wantlist to
-      place items offered to the Project, and using the commit
-      statistics to help place items.  As such, active committers who
-      ask for what they want beforehand have a decent chance of
-      getting it.  Less active committers, and committers who do not
-      ask for what they want, will be lower in our priorities but will
-      not be excluded.</p>
-
-    <p>We are in the process of streamlining the tax deduction process
-      for donations, and hope to have news on that shortly.  We are
-      also always working to accelerate and reduce our internal
-      processes, to get the most equipment in the hands of the most
-      people as quickly as possible.</p>
-
-    <p>I especially want to thank David O'Brien and Tom Rhodes for
-      stepping up and making the team far more successful.  Also, the
-      FreeBSD Foundation has been quite helpful in handling
-      tax-deductible contributions.</p>
-  <hr /><h2><a name="Fast-IPsec-Status" href="#Fast-IPsec-Status" id="Fast-IPsec-Status">Fast IPsec Status</a></h2><p>
-	Contact:
-        Sam
-        Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>The main goal of this project is to modify the IPsec protocols to use
-      the kernel-level crypto subsystem imported from OpenBSD (see elsewhere).
-      A secondary goal is to do general performance tuning of the IPsec
-      protocols.</p>
-
-    <p>This work will be part of the 5.0 release.  Performance has been improved
-      due to work on the crypto subsystem.</p>
-  <hr /><h2><a name="FFS-volume-label-support" href="#FFS-volume-label-support" id="FFS-volume-label-support">FFS volume label support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~gordon/patches/volume.diff" title="http://people.FreeBSD.org/~gordon/patches/volume.diff">Current patch set.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~gordon/patches/volume.diff" title="Current patch set.">http://people.FreeBSD.org/~gordon/patches/volume.diff</a></td></tr></table><p>
-	Contact:
-	Gordon
-	Tetlow
-       &lt;<a href="mailto:gordon@FreeBSD.org">gordon@FreeBSD.org</a>&gt;
-	</p>
-    <p>The goal of the project is to use a small amount of space in the FFS
-      superblock to store a volume label of the user's choice. A GEOM module
-      will then expose the volume labels into a namespace in devfs.  The idea
-      is to make it easier to manage filesystems across disk swaps and
-      movement from system to system.</p>
-
-    <p>At this point, everything pretty much works. I've submitted parts of
-      the patch to respective subsystem maintainers for review. There are some
-      issues with namespace collision that I haven't addressed yet, but the
-      basic functionality is there</p>
-  <hr /><h2><a name="FreeBSD-C99-&amp;-POSIX-Conformance-Project" href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project" id="FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/c99/" title="http://www.FreeBSD.org/projects/c99/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/c99/" title="">http://www.FreeBSD.org/projects/c99/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~schweikh/posix-utilities.html" title="http://people.FreeBSD.org/~schweikh/posix-utilities.html"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~schweikh/posix-utilities.html" title="">http://people.FreeBSD.org/~schweikh/posix-utilities.html</a></td></tr></table><p>
-	Contact:
-	Mike
-        Barcroft
-       &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        FreeBSD-Standards Mailing List
-       &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-    <p>The POSIX Utility Conformance in FreeBSD list (link above) has
-      been updated to reflect current reality.  Not much work remains
-      to complete base utility conformance.</p>
-
-    <p>On the API front, grantpt(), posix_openpt(), unlockpt(),
-      wordexp(), and wordfree() were implemented.  The header
-      &lt;wordexp.h&gt; was added.</p>
-
-    <p>There are currently about 40 unassigned tasks on our project's
-      status board ranging from documentation, utilities, to kernel
-      hacking.  We would encourage any developers looking for something
-      to work on to check out the status board and see if anything
-      interests them.</p>
-  <hr /><h2><a name="FreeBSD-GNOME-Project" href="#FreeBSD-GNOME-Project" id="FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Homepage.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project Homepage.">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-	Joe
-	Marcus
-       &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Maxim
-	Sobolev
-       &lt;<a href="mailto:sobomax@FreeBSD.org">sobomax@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Adam
-	Weinberger
-       &lt;<a href="mailto:adamw@FreeBSD.org">adamw@FreeBSD.org</a>&gt;
-	</p>
-    <p>Since the ports tree has been frozen for most of this reporting period,
-      there have not been too many GNOME updates going into the official CVS
-      tree.  However, development has not stopped.  GNOME 2.2 is nearing
-      completion, and quite a few FreeBSD users have stepped up to test the
-      GNOME 2.1 port sources from the
-      <a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi" shape="rect">MarcusCom
-      CVS repository</a>.  If anyone else is interested, follow the
-      instructions on the aforementioned cvsweb URL, and checkout the "ports"
-      module.</p>
-
-    <p>The upcoming FreeBSD 5.0-RELEASE will be the first release to have the
-      GNOME 2.0 desktop as the default GNOME desktop choice.  During the
-      previously mentioned ports freeze, all the GNOME 2 ports were fixed up
-      so that they build and package on both i386 and Alpha platforms.  Alas,
-      the one port that will not make the cut for Alpha is Mozilla.  There are
-      still problems with the xpcom code, but work is ongoing to get a working
-      Alpha port.</p>
-
-    <p>Finally, the FreeBSD Mono (an OpenSource C# runtime) port has also
-      received some new life.  Mono has been updated to 0.17 (the latest
-      released version), and Juli Mallett has ported gtk-sharp (GTK+ bindings
-      for C#).</p>
-  <hr /><h2><a name="FreeBSD-Package-Cluster-work" href="#FreeBSD-Package-Cluster-work" id="FreeBSD-Package-Cluster-work">FreeBSD Package Cluster work</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bento.FreeBSD.org/" title="http://bento.FreeBSD.org/"></a></td><td>
-	    URL: <a href="http://bento.FreeBSD.org/" title="">http://bento.FreeBSD.org/</a></td></tr></table><p>
-	Contact:
-	Kris
-	Kennaway
-       &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-    <p>The 3 FreeBSD package clusters (i386, alpha, sparc64) have been
-      unified to run from the same master machine, instead of using 3
-      separate masters.  This has freed up some machine resources to
-      use as additional client machine, as well as simplifying
-      administrative overheads.  Build logs for all 3 architectures
-      can now be found on the http://bento.FreeBSD.org webpage.  The
-      sparc64 package cluster now has 3 build machines (an u5 and two
-      u10s), and an ia64 cluster is about to be created.</p>
-
-    <p>Package builds now keep track of how many sequential times a
-      port has failed to build (html summaries are available on the
-      bento website).  This allows tracking of ports which have
-      suddenly become broken (e.g. due to a bad upgrade, or due to
-      changes in the FreeBSD source tree), and in the future will be
-      used to send out notifications to port maintainers when their
-      port fails to build 5 times in a row.  This feature is currently
-      experimental, and further code changes will be needed to
-      stabilize it.</p>
-  <hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/index.html" title="http://www.FreeBSD.org/releng/index.html">Release Engineering Homepage</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/index.html" title="Release Engineering Homepage">http://www.FreeBSD.org/releng/index.html</a></td></tr></table><p>
-	Contact:
-	Scott
-	Long
-       &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-    <p>November and December were especially busy for the release engineering
-      team.  Scott Long joined the team to help with secretary and
-      communications tasks while Brian Somers bowed out to focus on other
-      projects.</p>
-
-    <p>FreeBSD 5.0-DP2 was released in November after much delay and
-      anticipation, and marked the final milestone needed for 5.0 to
-      become a reality.  Shortly after that, we imposed a code freeze on
-      the HEAD branch of CVS and released 5.0-RC1.  Creation of the
-      RELENG_5_0 branch came next, followed by the release of 5.0-RC2 from
-      this branch.  At this point, enough critical problems still existed
-      that we scheduled an RC3 release for the new year, and pushed the
-      final 5.0-RELEASE date to mid-January.  By the time this is published,
-      FreeBSD 5.0-RELEASE should be a reality.</p>
-
-    <p>For the time being, there will not be a RELENG_5 (aka 5-STABLE)
-      branch.  FreeBSD 4.x releases will continue, with 4.8 being
-      scheduled for March 2003.  Release in the 4.x series will be
-      lead by Murray Stokely, and releases in the 5.x series will be
-      lead by Scott Long.  Once HEAD has reached acceptable performance
-      and stability goals, the RELENG_5 branch will be created and HEAD
-      will move towards 6.0 development.  We hope to reach this with
-      the 5.1 release this spring.</p>
-  <hr /><h2><a name="FreeBSD/ia64-Status" href="#FreeBSD/ia64-Status" id="FreeBSD/ia64-Status">FreeBSD/ia64 Status</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~peter/ia64.diff" title="http://people.FreeBSD.org/~peter/ia64.diff"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~peter/ia64.diff" title="">http://people.FreeBSD.org/~peter/ia64.diff</a></td></tr><tr><td><a href="http://www.FreeBSD.org/platforms/ia64/" title="http://www.FreeBSD.org/platforms/ia64/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/platforms/ia64/" title="">http://www.FreeBSD.org/platforms/ia64/</a></td></tr></table><p>
-	Contact:
-	Peter
-	Wemm
-       &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Marcel
-	Moolenaar
-       &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	</p>
-    <p>The ia64 port is up and running on the new Itanium2 based hp
-      machines thanks to a lot of hard work by Marcel Moolenaar.  So
-      far we are running on the hp rx2600 as these were the machines
-      graciously donated by Hewlett-Packard and Intel.  We had a
-      prototype Intel Tiger4 system for a while, but we had to return
-      the machine and we do not know if it currently runs.  Most of
-      the changes necessary to run these are sitting in the perforce
-      tree and are not in the -current or RELENG_5 cvs tree.  As a
-      result, the cvs derived builds (-current and the 5.0-RC series
-      and presumably 5.0-RELEASE) are only usable on obsolete Itanium1
-      systems.</p>
-
-    <p>Lots of other stability and functionality fixes have been made
-      over the last few months, including initial libc_r support.  The
-      OS appears to be stable enough for sustained workloads - it is
-      building packages now, for example.  We still do not have gdb
-      support, even for reading core files.</p>
-  <hr /><h2><a name="French-FreeBSD-Documentation-Project" href="#French-FreeBSD-Documentation-Project" id="French-FreeBSD-Documentation-Project">French FreeBSD Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd-fr.org" title="http://www.freebsd-fr.org">The French FreeBSD Documentation Project.</a></td><td>
-	    URL: <a href="http://www.freebsd-fr.org" title="The French FreeBSD Documentation Project.">http://www.freebsd-fr.org</a></td></tr><tr><td><a href="http://www.freebsd-fr.org/index-trad.html" title="http://www.freebsd-fr.org/index-trad.html">The FreeBSD Web Server translated in French.</a></td><td>
-	    URL: <a href="http://www.freebsd-fr.org/index-trad.html" title="The FreeBSD Web Server translated in French.">http://www.freebsd-fr.org/index-trad.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/" title="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/">Translation of the hanbook.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/" title="Translation of the hanbook.">http://people.FreeBSD.org/~blackend/doc/fr_FR.ISO8859-1/books/handbook/</a></td></tr><tr><td><a href="http://www.FreeBSD-fr.info" title="http://www.FreeBSD-fr.info">French Daemon News like web site.</a></td><td>
-	    URL: <a href="http://www.FreeBSD-fr.info" title="French Daemon News like web site.">http://www.FreeBSD-fr.info</a></td></tr></table><p>
-	Contact:
-        Sebastien
-        Gioria
-       &lt;<a href="mailto:gioria@FreeBSD.org">gioria@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Marc
-        Fonvieille
-       &lt;<a href="mailto:blackend@FreeBSD.org">blackend@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        St�phane
-        Legrand
-       &lt;<a href="mailto:stephane@FreeBSD.org">stephane@FreeBSD.org</a>&gt;
-	</p>
-    <p>Most of the articles are translated too.  Marc is still translating the
-      handbook, 60% is currently translated.  St�phane has began the
-      integration of our French localization web site in the US CVS Tree.
-      S�bastien is still maintaining the Release Notes.</p>
-
-    <p>We launched a new site, www.FreeBSD-fr.info, consisting in a French
-      Daemon News like site.  Netasq have donated our new server; we will
-      install it in a new hosting provider in the few next weeks.  One of the
-      big job now is the translation of the FAQ, and the big
-      project will be the manual pages.</p>
-  <hr /><h2><a name="Hardware-Crypto-Support-Status" href="#Hardware-Crypto-Support-Status" id="Hardware-Crypto-Support-Status">Hardware Crypto Support Status</a></h2><p>
-	Contact:
-        Sam
-        Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>The goal of this project is to import the OpenBSD kernel-level crypto
-      subsystem. This facility provides kernel- and user-level access to
-      hardware crypto devices for the calculation of cryptographic hashes,
-      ciphers, and public key operations. The main clients of this facility
-      are the kernel RNG (/dev/random), network protocols (e.g. IPsec), and
-      OpenSSL (through the /dev/crypto device).</p>
-
-    <p>This work will be part of the 5.0 release and has been committed to
-      the -stable source tree for inclusion in the 4.8 release.</p>
-
-    <p>Recent work has focused on improving performance. System statistics are
-      now maintained and an optional profiling facility was added for
-      analyzing performance. Using this facility the overhead for using the
-      crypto API has been significantly reduced.</p>
-
-    <p>The ubsec (Broadcom) driver was changed to significantly improve
-      performance under load. In addition several memory leaks were fixed in
-      the driver and the public key support was enabled for use.</p>
-
-    <p>Upcoming work will focus on load-balancing requests across multiple
-      crypto devices and integrating OpenSSL 0.9.7 which will automatically
-      enable application use of crypto hardware.</p>
-  <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-	Kazuo
-	Horikawa
-       &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-     <p>We have been updating our Japanese translated manual pages to
-       RELENG_5 based.  All existing entries have been updated, but 15
-       exceptions are not, most of which require massive update.  We
-       will also need to add translations which did not exist on RELENG_4.</p>
-  <hr /><h2><a name="KGI/FreeBSD-Status-Report" href="#KGI/FreeBSD-Status-Report" id="KGI/FreeBSD-Status-Report">KGI/FreeBSD Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="http://www.FreeBSD.org/~nsouch/ggiport.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="">http://www.FreeBSD.org/~nsouch/ggiport.html</a></td></tr><tr><td><a href="http://www.kgi-project.org" title="http://www.kgi-project.org"></a></td><td>
-	    URL: <a href="http://www.kgi-project.org" title="">http://www.kgi-project.org</a></td></tr></table><p>
-	Contact:
-	Nicholas
-	Souchu
-       &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-    <p>KGI (Kernel Graphic Interface) is a kernel infrastructure providing user
-      applications with means to access hardware graphic resources (dma,
-      irqs, mmio). KGI is already available under Linux as a separate
-      standalone project. The KGI/FreeBSD project aims at integrating KGI
-      in the FreeBSD kernel.</p>
-
-    <p>KGI/FreeBSD has been recently donated 2 PCI graphic cards (Matrox
-      Millennium II and a coming Mach64) and other have been proposed.
-      Please see the FreeBSD web pages for details.  Thanks to donation@ for
-      organizing and promoting donations. Thanks to the donators for their
-      contribution to KGI/FreeBSD.</p>
-
-    <p>KGI/FreeBSD progressed fine the last months. Most of the VM issues for
-      mapping HW resources in user space have been addressed and a first
-      attempt of coding was made. This prototyping raised some API
-      compatibility problems with the current Linux implementation and was
-      discussed heavily on the kgi devel lists. Ask if you're
-      interested in such issues, I'll be pleased to share them.</p>
-
-    <p>Most of coding is now done. Let's start debugging!</p>
-  <hr /><h2><a name="SMP-aware-scheduler" href="#SMP-aware-scheduler" id="SMP-aware-scheduler">SMP aware scheduler</a></h2><p>
-	Contact:
-	Jeff
-	Roberson
-       &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-    <p>A new scheduler will be available as an optional component along side
-      the current scheduler in the 5.1 release.  It has been designed to
-      work well with KSE and SMP.  Some ideas have been borrowed from solaris
-      and linux along with many novel approaches.  It has O(1) performance
-      with regard to the number of processes in the system.  It also has
-      cpu affinity which should provide a speed boost for many applications.</p>
-
-    <p>The scheduler has a few loose ends and lots of tuning before it is
-      production quality although it is quite stable.  Please see the post
-      to arch and subsequent discussion for more details.</p>
-  <hr /><h2><a name="SMP-locking-for-network-stack" href="#SMP-locking-for-network-stack" id="SMP-locking-for-network-stack">SMP locking for network stack</a></h2><p>
-	Contact:
-        Jeffrey
-        Hsu
-       &lt;<a href="mailto:hsu@FreeBSD.org">hsu@FreeBSD.org</a>&gt;
-	</p>
-    <p> Work is ongoing to continue to lock up the network stack.
-      Recently, the focus has been on the IP stack.  The plan there
-      involves a series of inter-related pieces to lock up the
-      ifaddr ref count, the inet list, the ifaddr uses, the ARP code,
-      the routing tree, and the routing entries.  We are over 3/5 of
-      the way done down this path.</p>
-
-    <p>In addition to TCP and UDP, the other networking protocols
-      such as raw IP, IPv6, AppleTalk, and XNS need to be locked up.
-      Around 1/4 these remaining protocols have been locked and
-      will be committed after the IP stack is locked.</p>
-
-    <p>The protocol independent socket layer needs to be locked and
-      operating correctly with the protocol dependent locks.  This
-      part is mostly done save for much needed testing and code cleanup.</p>
-
-    <p>Finally, a pass will be need to be made to lock up the devices drivers
-      and various statistics counters.</p>
-  <hr /><h2><a name="TCP-congestion-control" href="#TCP-congestion-control" id="TCP-congestion-control">TCP congestion control</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-        Jeffrey
-        Hsu
-       &lt;<a href="mailto:hsu@FreeBSD.org">hsu@FreeBSD.org</a>&gt;
-	</p>
-    <p>This effort fixes some outstanding problems in our TCP
-      stack with regard to congestion control.  The first
-      item is to fix our NewReno implementation.  Following that,
-      the next urgent correction is to fix a problem involving window updates
-      and dupack counts.  When that stabilizes, we will then change
-      the recovery code to make use of SACK information.
-      Eventually, this project will update the BSD stack to add Limited Transmit
-      and other new internet standards and standards-track improvements.</p>
-  <hr /><h2><a name="TrustedBSD-Project:-Access-Control-Lists" href="#TrustedBSD-Project:-Access-Control-Lists" id="TrustedBSD-Project:-Access-Control-Lists">TrustedBSD Project: Access Control Lists</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-	Robert
-
-	Watson
-       &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	TrustedBSD Discussion List
-       &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-    <p>Largely bug-fixing and userland application tweaks; new
-      interfaces were added to manipulate ACLs on extended attributes;
-      bugs were fixed in ls relating to ACL flagging.  Patches to
-      teach cp, mv, gzip, bzip, and other apps about ACL preservation
-      are in testing and review.  tunefs flags were added to ease
-      configuration of ACLs, especially on UFS2 file systems.</p>
-    <p>Possible changes to make use of Linux/Solaris umask semantics
-      are under consideration: right now we implement verbatim
-      POSIX.1e/IRIX merging of the umask, ACL mask, and requested
-      creation mode during file, device, fifo, and directory creation.
-      Solaris and the most recent Linux patches ignore the umask in
-      the context of a default ACL; this requires some rearrangement
-      of umask handling in our VFS, although the results would be
-      quite useful.  We're exploring how to do this in a low impact
-      way.</p>
-  <hr /><h2><a name="TrustedBSD-Project:-MAC-Framework" href="#TrustedBSD-Project:-MAC-Framework" id="TrustedBSD-Project:-MAC-Framework">TrustedBSD Project: MAC Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-	Robert
-
-	Watson
-       &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	TrustedBSD Discussion List
-       &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-    <p>Framework changes:</p>
-    <p>Instrument KLD system calls (module and kld load, unload, stat)
-      Instrument NFSd system call.  Instrument swapoff(2).
-      Instrument per-architecture privileged parts of sysarch().
-      Make use of condition variables to allow callers to wait for the
-      framework to "unbusy" when loading/unloading policies, rather than
-      returning EBUSY.  Store mount pointer in devfs_mount structure for
-      use by policies.  Improve handling of labels in loopback interface
-      "re-align" packet copy case.  Provide full paths on devfs object
-      creations to help policies label them properly (not merged).
-      Experimentation with moving MAC labels into m_tags (not merged).
-      NFS server now uses real ucreds, not hacked up ucreds,
-      meaning we can start laying the groundwork for enforcement on
-      NFS operations. (not merged)</p>
-
-    <p>Policy changes</p>
-    <p>LOMAC: mac_lomac replaces lomac (LOMAC now uses the MAC Framework),
-      SEBSD: Improved support for devfs labeling based on SELinux genfs.
-      Handling of hard link checks.  Support export of process transition
-      information for login and others using sysctl.  Login now prompts
-      for roles.  Allow policy reload. TTY labeling.  Locking adaptation
-      from Linux.  Many, many policy adaptations and fixes.  We can
-      now boot in enforcing mode!  mac_bsdextended: fix a bug in which
-      VAPPEND wasn't mapped to VWRITE, so opens with the O_APPEND bug
-      failed improperly.</p>
-
-    <p>Userland changes</p>
-    <p>setfmac(8) now supports a setfsmac(8) execution mode, which accepts
-      initial labeling specification files.  Supports an SELinux compatibility
-      mode so it can accept SELinux label specfiles using the SEBSD module.
-      sendmail(8) now sets user labels as part of the context switch for mail
-      delivery.</p>
-
-    <p>Documentation changes</p>
-    <p>Man page updates for MAC command line tools, modules, admin hints, etc.
-      Updates to the FreeBSD Developer's Handbook chapter on MAC policies
-      and entry points.  MAC section in FreeBSD Handbook.</p>
-  <hr /><h2><a name="Wireless-Networking-Status" href="#Wireless-Networking-Status" id="Wireless-Networking-Status">Wireless Networking Status</a></h2><p>
-	Contact:
-          Sam
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-  <p>The goal of this project is to improve the wireless networking support in
-    the system.  By the time of this report the 802.11 link layer code should
-    be committed.  A version of the wi driver that uses this code should be
-    committed shortly.  Conversion of other drivers is planned as are drivers
-    for new devices.</p>
-
-  <p>Support for 802.1x/EAP is the next planned milestone (both as a
-    supplicant and authenticator).</p>
-  <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2003-01-2003-02.html b/website/content/en/status/report-2003-01-2003-02.html
deleted file mode 100644
index cf65a31797..0000000000
--- a/website/content/en/status/report-2003-01-2003-02.html
+++ /dev/null
@@ -1,703 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction:</h1><p>Another busy two months have passed in the FreeBSD project.  With
-      5.0 released, attention is focusing on making it faster via more
-      fine-grained locking, adding more high-end features like large
-      memory (PAE) support for i386, and further progress on many other
-      projects.  FreeBSD 5.1 is expected to ship in late May or early
-      June, with 5.2 following at the end of summer.  A roadmap for
-      the push to 5-STABLE is available at <a href="http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html" shape="rect">
-      http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html</a>.  Although
-      the 5.x series isn't expected to fully stabilize until the 5.2
-      release, 5.1 promises to be an exciting release and a significant
-      improvement over 5.0 in terms of speed and stability.</p><p>Not to be forgotten, FreeBSD 4.8, the latest in the 4-STABLE
-      series, is nearing release.  Lots of last minute work is going
-      into to it to deliver features like XFree86 4.3.0, Intel
-      HyperThreading(tm) support, and of course many more bug fixes.
-      Don't forget to support the FreeBSD vendors and developers by
-      buying a copy of the CD set when it comes out!.</p><p>Thanks,</p><p>Scott Long, Robert Watson</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-    Bluetooth stack for FreeBSD (Netgraph implementation)
-  </a></li><li><a href="#BSDCon-2003">BSDCon 2003</a></li><li><a href="#Buffer-Cache-lockdown">Buffer Cache lockdown</a></li><li><a href="#Disk-I/O-improvements">Disk I/O improvements</a></li><li><a href="#FreeBSD-4.8-Release-Engineering">FreeBSD 4.8 Release Engineering</a></li><li><a href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></li><li><a href="#FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></li><li><a href="#FreeBSD-Security-Officer-Team">FreeBSD Security Officer Team</a></li><li><a href="#FreeBSD/MIPS-Status-Report">FreeBSD/MIPS Status Report</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KGI/FreeBSD-Status-Report">KGI/FreeBSD Status Report</a></li><li><a href="#New-Doceng-Body-Formed">New Doceng Body Formed</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#Read-ahead-performance">Read-ahead performance</a></li><li><a href="#SMP-locking-for-network-stack">SMP locking for network stack</a></li><li><a href="#Status-Report-for-Newbus-lockdown">Status Report for Newbus lockdown</a></li><li><a href="#Support-for-PAE-and-&gt;4G-ram-on-x86">Support for PAE and &gt;4G ram on x86</a></li><li><a href="#TCP-congestion-control">TCP congestion control</a></li><li><a href="#ULE-Scheduler">ULE Scheduler</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-    Bluetooth stack for FreeBSD (Netgraph implementation)
-  </a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.geocities.com/m_evmenkin/" title="http://www.geocities.com/m_evmenkin/">Latest snapshot</a></td><td>
-	    URL: <a href="http://www.geocities.com/m_evmenkin/" title="Latest snapshot">http://www.geocities.com/m_evmenkin/</a></td></tr><tr><td><a href="http://bluez.sf.net" title="http://bluez.sf.net">Linux BlueZ stack</a></td><td>
-	    URL: <a href="http://bluez.sf.net" title="Linux BlueZ stack">http://bluez.sf.net</a></td></tr><tr><td><a href="http://sourceforge.net/projects/openobex/" title="http://sourceforge.net/projects/openobex/">OpenOBEX</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/openobex/" title="OpenOBEX">http://sourceforge.net/projects/openobex/</a></td></tr></table><p>
-	Contact:
-        Maksim
-        Yevmenkin
-       &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-    <p>I'm very pleased to announce that another release is available for
-    download at <a href="http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz" shape="rect">
-    http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz</a></p>
-
-    <p>This release features new in-kernel RFCOMM implementation that
-    provides SOCK_STREAM sockets interface. This makes old user-space
-    RFCOMM daemon obsolete. People should not use old user-space
-    RFCOMM daemon any longer. The release features new RFCOMM PPP
-    daemon that supports DUN and LAN profiles. Note: PPP patch
-    (support for chat scripts in -direct mode) is required for DUN
-    support. Look for it in the mailing list archive or contact me
-    directly. People with Bluetooth enabled cell phones can now
-    use them to access Internet.</p>
-
-    <p>The Bluetooth sockets layer has been cleaned up. People should not
-    see any WITNESS complaints with new code. Locking issues have been
-    revisited and code in much better shape now, although it probably
-    is not 100% SMP ready just yet. The code should work on SMP system
-    anyway because sockets layer is still under Giant.</p>
-
-    <p>The simple OBEX server and client (based on OpenOBEX library) is
-    complete. OBEX File Push and OBEX File Transfer profiles work and
-    have been tested with Sony Ericsson T68i cell phone and Bluetooth
-    3COM stack on Windows2K. It is now possible to send pictures,
-    address book and calendar entries from the cell phone via
-    Bluetooth. Minor bug in OpenOBEX library has been fixed and OPEX
-    Put-Empty command now works.</p>
-
-    <p>Due to changes in API userland tools must be in sync with the
-    kernel. People should install new include files, recompile and
-    reinstall all userland tools as part of upgrade. I'm sorry about
-    that.</p>
-  <hr /><h2><a name="BSDCon-2003" href="#BSDCon-2003" id="BSDCon-2003">BSDCon 2003</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.usenix.org/events/bsdcon03/cfp/" title="http://www.usenix.org/events/bsdcon03/cfp/">BSDCon 2003 Call For Papers</a></td><td>
-	    URL: <a href="http://www.usenix.org/events/bsdcon03/cfp/" title="BSDCon 2003 Call For Papers">http://www.usenix.org/events/bsdcon03/cfp/</a></td></tr></table><p>
-	Contact:
-        Gregory
-        Shapiro
-       &lt;<a href="mailto:gshapiro@FreeBSD.org">gshapiro@FreeBSD.org</a>&gt;
-	</p>
-
-    <p>The BSDCon 2003 Program Committee invites you to contribute
-      original and innovative papers on topics related to BSD-derived
-      systems and the Open Source world. Topics of interest include
-      but are not limited to:</p>
-
-    <ul>
-      <li>Embedded BSD application development and deployment</li>
-      <li>Real world experiences using BSD systems</li>
-      <li>Using BSD in a mixed OS environment</li>
-      <li>Comparison with non-BSD operating systems; technical, practical, licensing (GPL vs. BSD)</li>
-      <li>Tracking open source development on non-BSD systems</li>
-      <li>BSD on the desktop</li>
-      <li>I/O subsystem and device driver development</li>
-      <li>SMP and kernel threads</li>
-      <li>Kernel enhancements</li>
-      <li>Internet and networking services</li>
-      <li>Security</li>
-      <li>Performance analysis and tuning</li>
-      <li>System administration</li>
-      <li>Future of BSD</li>
-    </ul>
-
-    <p>Submissions in the form of extended abstracts are due by
-      April 1, 2003. Be sure to review the extended abstract
-      expectations before submitting. Selection will be based on the
-      quality of the written submission and whether the work is of
-      interest to the community.</p>
-
-    <p>We look forward to receiving your submissions!</p>
-
-  <hr /><h2><a name="Buffer-Cache-lockdown" href="#Buffer-Cache-lockdown" id="Buffer-Cache-lockdown">Buffer Cache lockdown</a></h2><p>
-	Contact:
-	Jeff
-	Roberson
-       &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-    <p>Most of the file system buffer cache has been reviewed and protected.
-      The vnode interlock was extended to cover some buffer flag fields so
-      that a separate interlock was not required.  The global buffer queue
-      data structures were locked and counters were converted to atomic ops.
-      The BUF_*LOCK functions grew an interlock argument so that buffers
-      could be safely removed from the vnode clean and dirty lists.  The
-      lockmgr lock is now required for all access to buf fields.  This was
-      not strictly followed before because splbio provided the needed
-      protection.</p>
-
-    <p>There are a few areas of code that need to be protected and cleaned up
-      before giant can be pushed down.  Most notably the background write
-      code is currently unsafe without giant.  Also, many of the VM bits that
-      the buffer cache relies on are not safe.  This work has been done with
-      the expectation that the VM and VFS subsystems will be giant free
-      soon.</p>
-  <hr /><h2><a name="Disk-I/O-improvements" href="#Disk-I/O-improvements" id="Disk-I/O-improvements">Disk I/O improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	Poul-Henning
-	Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-    <p>We have the first disk device driver (aac) out from under Giant
-      now, and in certain scenarios it gives improvements up to 20%.
-      The device driver API was pruned to reflect that NO_GEOM
-      compatibility is unnecessary, this resulted in approx 1000
-      lines less source code, the majority of which were removed
-      from the device drivers.  The new API for cdevsw is a lot simpler
-      and hopefully less likely to confuse people.  The ability to
-      automatically allocate a device major number has been introduced
-      and is already used by a handful of drivers.  Checks introduced
-      with this facility has shown that the uniqueness of manually
-      allocated major numbers had already broken down.<p>
-
-    </p>Work continues on the statistics collection API and on a unified
-      API for manual configuration of GEOM nodes.</p>
-  <hr /><h2><a name="FreeBSD-4.8-Release-Engineering" href="#FreeBSD-4.8-Release-Engineering" id="FreeBSD-4.8-Release-Engineering">FreeBSD 4.8 Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releases/4.8R/schedule.html" title="http://www.FreeBSD.org/releases/4.8R/schedule.html">FreeBSD 4.8 Release Schedule.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/4.8R/schedule.html" title="FreeBSD 4.8 Release Schedule.">http://www.FreeBSD.org/releases/4.8R/schedule.html</a></td></tr></table><p>
-	Contact:
-	Murray
-	Stokely
-       &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-    <p>The FreeBSD 4.8 Release Process is well underway.  The RELENG_4
-      branch has been under code freeze since February 15, and
-      the first release candidates were made available in early March.
-      A testing guide has been put together and is available from
-      http://www.FreeBSD.org/releases/4.8R/qa.html.</p>
-
-    <p>Developers should coordinate with re@FreeBSD.org about any
-      changes they would like to include in this release, and users
-      are encouraged to try out the release candidates and help find
-      as many bugs as possible now, before the final release is
-      made.</p>
-
-    <p>FreeBSD 4.8 represents the newest production release from the
-      stable '4.X' branch.  It does not include all of the features
-      that were made available in the "new technology" 5.0
-      release in January.</p>
-  <hr /><h2><a name="FreeBSD-C99-&amp;-POSIX-Conformance-Project" href="#FreeBSD-C99-&amp;-POSIX-Conformance-Project" id="FreeBSD-C99-&amp;-POSIX-Conformance-Project">FreeBSD C99 &amp; POSIX Conformance Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/c99/" title="http://www.FreeBSD.org/projects/c99/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/c99/" title="">http://www.FreeBSD.org/projects/c99/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~schweikh/posix-utilities.html" title="http://people.FreeBSD.org/~schweikh/posix-utilities.html"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~schweikh/posix-utilities.html" title="">http://people.FreeBSD.org/~schweikh/posix-utilities.html</a></td></tr></table><p>
-	Contact:
-	Mike
-	Barcroft
-       &lt;<a href="mailto:mike@FreeBSD.org">mike@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        FreeBSD-Standards Mailing List
-       &lt;<a href="mailto:standards@FreeBSD.org">standards@FreeBSD.org</a>&gt;
-	</p>
-    <p>January and February were quiet months that saw with them the
-      addition of some C99 math functions and macros, which include:
-      fpclassify(), isfinite(), isgreater(), isgreaterequal(), isinf(),
-      isless(), islessequal(), islessgreater(), isnan(), isnormal(),
-      and signbit().  Additional C99 math library support is in the
-      works.</p>
-  <hr /><h2><a name="FreeBSD-GNOME-Project" href="#FreeBSD-GNOME-Project" id="FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Homepage.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project Homepage.">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-	Joe
-	Marcus
-       &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	Maxim
-	Sobolev
-       &lt;<a href="mailto:sobomax@FreeBSD.org">sobomax@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Adam
-	Weinberger
-       &lt;<a href="mailto:adamw@FreeBSD.org">adamw@FreeBSD.org</a>&gt;
-	</p>
-    <p>FreeBSD 4.8-RELEASE will continue in the tradition of
-      5.0-RELEASE, and include GNOME 2 as the default GNOME desktop.
-      This means that 4.8 will ship with GNOME 2.2.</p>
-
-    <p>Following on the heels of the recent GNOME 2.2 release, GNOME 2.3
-      snapshots are gearing up.  The development schedule is
-      available from <a href="http://www.gnome.org/start/2.3/" shape="rect">
-      http://www.gnome.org/start/2.3/</a>.  Ports will be
-      made available the same way they were for the 2.1 development
-      releases.  Stay tuned to freebsd-gnome@ for more details.</p>
-
-    <p>We are currently in another ports freeze in preparation for
-      4.8-RELEASE.  Following the freeze, a new bsd.gnome.mk will
-      be committed that effectively removes the USE_GNOMENG macro.
-      This new version will add support for GNOME 2 as well as
-      setup backward compatibility for ports that have not yet
-      been converted to the new GNOME infrastructure.  People
-      interested in testing this new Mk file, can check out
-      the ``ports'' module following the instructions at
-      <a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi" shape="rect">
-      http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>.</p>
-  <hr /><h2><a name="FreeBSD-Security-Officer-Team" href="#FreeBSD-Security-Officer-Team" id="FreeBSD-Security-Officer-Team">FreeBSD Security Officer Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/security/" title="http://www.FreeBSD.org/security/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/security/" title="">http://www.FreeBSD.org/security/</a></td></tr></table><p>
-	Contact:
-	Jacques
-	Vidrine
-       &lt;<a href="mailto:nectar@FreeBSD.org">nectar@FreeBSD.org</a>&gt;
-	</p>
-    <p>In the period from September 2002 through February 2003, the
-      FreeBSD Security Team email aliases saw 1297 messages, a much
-      smaller volume than over the summer (remember the Apache and OpenSSL
-      worms? 4.6.1 oops I mean 4.6.2-RELEASE?).</p>
-
-    <p>Also during this period: 95 items were added to the SO
-      issue-tracking database; 39 of these involved the FreeBSD base
-      system while the rest involved ports.  9 new Security Advisories
-      were published, 2 of which covered issues unique to FreeBSD.</p>
-
-      <p>In January, the SO published a new PGP key (ID 0xCA6CDFB2, found
-      on the FTP site and in the Handbook).  This aligned the set of those
-      who possess the corresponding private key with the membership of the
-      security-officer alias published on the FreeBSD Security web site.
-      It also worked around an issue with the deprecated PGP key being
-      found corrupted on some public key servers.</p>
-
-    <p>In February, Mike Tancsa of Sentex donated two machines to
-      the Security Officer.  These have been a great help already in
-      testing the security branches, preparing patches, and generating
-      updated binaries.  Thank you very much, Mike!</p>
-  <hr /><h2><a name="FreeBSD/MIPS-Status-Report" href="#FreeBSD/MIPS-Status-Report" id="FreeBSD/MIPS-Status-Report">FreeBSD/MIPS Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/mips/" title="http://www.FreeBSD.org/projects/mips/">FreeBSD/MIPS project page.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/mips/" title="FreeBSD/MIPS project page.">http://www.FreeBSD.org/projects/mips/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/platforms/mips.html" title="http://www.FreeBSD.org/platforms/mips.html">FreeBSD/MIPS platform page.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/platforms/mips.html" title="FreeBSD/MIPS platform page.">http://www.FreeBSD.org/platforms/mips.html</a></td></tr></table><p>
-	Contact:
-	Juli
-	Mallett
-       &lt;<a href="mailto:jmallett@FreeBSD.org">jmallett@FreeBSD.org</a>&gt;
-	</p>
-    <p>Large portions of headers have been filled in, all have been stubbed
-      out.  Minimal functions and data elements have been stubbed out or
-      filled in.  Machinery added to support some requisite tunables for
-      building real kernels.  GCC fixed to generate correct local label
-      prefixes making it possible to link real kernels.  Work begun on
-      providing enough to create and boot real kernels, on real hardware.
-      Decision to only support MIPS-III and above made.</p>
-  <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project">http://www.jp.FreeBSD.org/man-jp/</a></td></tr><tr><td><a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.0.0/ja-man-doc-5.0.tbz" title="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.0.0/ja-man-doc-5.0.tbz">package ja-man-doc-5.0.tbz</a></td><td>
-	    URL: <a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.0.0/ja-man-doc-5.0.tbz" title="package ja-man-doc-5.0.tbz">ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.0.0/ja-man-doc-5.0.tbz</a></td></tr></table><p>
-	Contact:
-	Kazuo
-	Horikawa
-       &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-    <p>We have released Japanese translation of 5.0-RELEASE online manual
-      pages on February 2nd.  Most of entries which did not exist on RELENG_4
-      were not yet translated.  I hope we can finish such entries soon.</p>
-  <hr /><h2><a name="KGI/FreeBSD-Status-Report" href="#KGI/FreeBSD-Status-Report" id="KGI/FreeBSD-Status-Report">KGI/FreeBSD Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="http://www.FreeBSD.org/~nsouch/ggiport.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/ggiport.html" title="">http://www.FreeBSD.org/~nsouch/ggiport.html</a></td></tr><tr><td><a href="http://kgi-wip.sf.org" title="http://kgi-wip.sf.org"></a></td><td>
-	    URL: <a href="http://kgi-wip.sf.org" title="">http://kgi-wip.sf.org</a></td></tr></table><p>
-	Contact:
-	Nicholas
-	Souchu
-       &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-    <p>The later months have been very busy on KGI. Most of the framework
-      has been debugged for typical usage (fb, no accel). I got
-      KII (the input interface) connected to syscons through atkbd. Opening
-      /dev/graphic works and framebuffer resource access is permitted.
-      Finally, the KGIM (KGI module) framework has a better building
-      tree for board / monitor drivers and board drivers are now loading
-      with resource allocation.</p>
-
-    <p>Most important on the TODO list:
-      5.0-RELEASE move (I currently work with a May-2002 5.0-current).
-      Most of debug is now done. Let's validate!</p>
-
-    <p>Note that KGI project homepage has changed since the last report.</p>
-  <hr /><h2><a name="New-Doceng-Body-Formed" href="#New-Doceng-Body-Formed" id="New-Doceng-Body-Formed">New Doceng Body Formed</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/internal/doceng.html" title="http://www.FreeBSD.org/internal/doceng.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/internal/doceng.html" title="">http://www.FreeBSD.org/internal/doceng.html</a></td></tr></table><p>
-	Contact:
-        Murray
-        Stokely
-       &lt;<a href="mailto:doceng@FreeBSD.org">doceng@FreeBSD.org</a>&gt;
-	</p>
-    <p>The doceng@ team is a new body to handle some of the
-      meta-project issues associated with the FreeBSD Documentation
-      Project. The main responsibilities of this team are to grant
-      approval of new doc committers, to manage the doc release
-      process, to ensure the documentation toolchains are functional,
-      to maintain the doc project primer, and to maintain the sanctity
-      of the doc/ and www/ trees.  The current members of this team
-      are Nik Clayton, Ruslan Ermilov, Jun Kuriyama, Bruce A. Mah, and
-      Murray Stokely.</p>
-  <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-        Peter
-        Grehan
-       &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-    <p>Work on PowerPC is progressing steadily. The system can now boot
-      multi-user from the net and disk. ATA-DMA is being integrated with
-      the ATAng code, and support for older G3 machines is being added.</p>
-  <hr /><h2><a name="Read-ahead-performance" href="#Read-ahead-performance" id="Read-ahead-performance">Read-ahead performance</a></h2><p>
-	Contact:
-	Jeff
-	Roberson
-       &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-    <p>Some improvements have been made to the clustered read ahead code.  They
-      allow for many more outstanding IO requests when an application does
-      sequential access.  This has a larger impact on RAID systems than on
-      single disk systems.  The maximum number of file system blocks that we
-      will read ahead is tunable via the 'vfs.read_max' sysctl.  This
-      optimization has shown a 20% improvement in simple tests.</p>
-  <hr /><h2><a name="SMP-locking-for-network-stack" href="#SMP-locking-for-network-stack" id="SMP-locking-for-network-stack">SMP locking for network stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-        Jeffrey
-        Hsu
-       &lt;<a href="mailto:hsu@FreeBSD.org">hsu@FreeBSD.org</a>&gt;
-	</p>
-    <p>The list of subsystems locked up include IP, UDP, TCP,
-      ifaddr reference counting, syncache, the ifnet list, routing
-      radix trees, and ARP.  These have already been committed into the tree.
-      In addition, SMP locking for raw IP, divert socket processing,
-      and Unix domain sockets have also recently been completed and tested.
-      Work is currently being done in some of the subsystems required
-      to make parallel networking processing SMP-safe.</p>
-  <hr /><h2><a name="Status-Report-for-Newbus-lockdown" href="#Status-Report-for-Newbus-lockdown" id="Status-Report-for-Newbus-lockdown">Status Report for Newbus lockdown</a></h2><p>
-	Contact:
-	Warner
-	Losh
-       &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-    <p>Locking of the non-obj parts of newbus is nearing completion.
-      A single lock is used for the device tree.  Minimal changes to
-      subr_bus have so far been necessary to make this work, however
-      some lock order issues remain.  After this
-      work, it will no longer be necessary to hold Giant to call
-      device_* routines safely.  kobj work is being done by others and
-      will likely require more extensive design work to make SMP
-      friendly.</p>
-  <hr /><h2><a name="Support-for-PAE-and-&gt;4G-ram-on-x86" href="#Support-for-PAE-and-&gt;4G-ram-on-x86" id="Support-for-PAE-and-&gt;4G-ram-on-x86">Support for PAE and &gt;4G ram on x86</a></h2><p>
-	Contact:
-	Jake
-	Burkholder
-       &lt;<a href="mailto:jake@FreeBSD.org">jake@FreeBSD.org</a>&gt;
-	</p>
-    <p>Support for PAE is mostly complete, and has been checked into the
-      jake_pae branch.  The approach that is being taken to add support for
-      PAE is to allow the pmap module to view the page table directory as 4
-      pages instead of 1, and to avoid using the 3rd level structure, the page
-      directory pointer table, as much as possible.  Due to its small size, 32
-      bytes, the PDPT cannot be uniformly recursively mapped, and as such does
-      not provide a regular multi level structure like the page tables used by
-      the alpha or x86-64 architectures.  What remains to be done for PAE
-      support is to develop an API for manipulating page table entries which
-      will allow idempotent 64 bit loads and stores to be used where
-      necessary.</p>
-
-    <p>Experimental support for &gt;4G ram using PAE has been developed and
-      checked into the jake_pae_test branch in Perforce.  This involved adding
-      a physical address type separate from virtual addresses, for use by the
-      vm system and bus code which needs to use physical addresses directly.
-      Initial testing has shown good results with device drivers that can dma
-      to 64 bit physical addresses.</p>
-
-    <p>Funding for this project is being provided by DARPA and Network
-      Associate Laboratories, and hardware support by
-      <a href="http://www.freebsdsystems.com" shape="rect">FreeBSD Systems</a>.</p>
-  <hr /><h2><a name="TCP-congestion-control" href="#TCP-congestion-control" id="TCP-congestion-control">TCP congestion control</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-        Jeffrey
-        Hsu
-       &lt;<a href="mailto:hsu@FreeBSD.org">hsu@FreeBSD.org</a>&gt;
-	</p>
-    <p>The objective of this effort is to improve the performance, stability,
-      and correctness of the BSD networking stack by adding support for
-      new standards and standards track proposals while maintaining compliance
-      with existing specifications.  The upcoming 4.8 and 5.1 releases will
-      be the first ones using the new NewReno logic.  Recently, we
-      implemented the Limited Transmit algorithm (RFC 3042) which benefits
-      connections with small congestion windows, as happens, for example,
-      on many short web connections.  We also recently added support for larger
-      sized starting congestion windows as described in RFC 3390.  This helps
-      short TCP connections as well as those with large round-trip delays,
-      such as those over satellite links.</p>
-  <hr /><h2><a name="ULE-Scheduler" href="#ULE-Scheduler" id="ULE-Scheduler">ULE Scheduler</a></h2><p>
-	Contact:
-	Jeff
-	Roberson
-       &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-    <p>The ULE scheduler has been committed to the 5.0-CURRENT branch.  Early
-      adopters and experimenters are welcome to try it and submit bug
-      reports.  It has shown noticeable performance improvements over the old
-      scheduler under some workloads.  There are currently problems with
-      nice fairness but otherwise the interactive performance is very good.
-      More work to improve the load balancing algorithm is required as well.
-      This should be ready for use by the general FreeBSD user base in the
-      next month or so.</p>
-  <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2003-03-2003-09.html b/website/content/en/status/report-2003-03-2003-09.html
deleted file mode 100644
index e992235ff8..0000000000
--- a/website/content/en/status/report-2003-03-2003-09.html
+++ /dev/null
@@ -1,881 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction:</h1><p>The FreeBSD Bi-monthly status reports are back!  In this edition, we
-      catch up on seven highly productive months and look forward to
-      the end of 2003.</p><p>As always, the FreeBSD development crew has been hard at work.  Support
-      for the AMD64 platform quickly sprang up and is nearly complete.  KSE
-      has improved greatly since the 5.1 release and will soon become the
-      default threading package in FreeBSD.  Many other projects are in the
-      works to improve performance, enhance the user experience, and expand
-      FreeBSD into new areas.  Take a look below at the impressive summary of
-      work!</p><p>Scott Long, Robert Watson</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-     Bluetooth stack for FreeBSD (Netgraph implementation)
-   </a></li><li><a href="#ACPI-Status-Report">ACPI Status Report</a></li><li><a href="#AMD64-Porting">AMD64 Porting</a></li><li><a href="#ATAPI/CAM-Status-Report">ATAPI/CAM Status Report</a></li><li><a href="#Binary-security-updates-for-FreeBSD">Binary security updates for FreeBSD</a></li><li><a href="#bsd.java.mk-version-2.0">bsd.java.mk version 2.0</a></li><li><a href="#Compile-FreeBSD-with-Intels-C-compiler-(icc)">Compile FreeBSD with Intels C compiler (icc)</a></li><li><a href="#Cryptographic-Support">Cryptographic Support</a></li><li><a href="#Device_t-locking">Device_t locking</a></li><li><a href="#Disk-I/O">Disk I/O</a></li><li><a href="#Dynamically-Linked-Root-Support">Dynamically Linked Root Support</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#KDE-FreeBSD-Project">KDE FreeBSD Project</a></li><li><a href="#kgi4BSD-Status-Report">kgi4BSD Status Report</a></li><li><a href="#KSE">KSE</a></li><li><a href="#Network-Subsystem-Locking-and-Performance">Network Subsystem Locking and Performance</a></li><li><a href="#Porting-OpenBSD's-pf">Porting OpenBSD's pf</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#Release-Engineering-Status">Release Engineering Status</a></li><li><a href="#Rescue-build-infrastructure">Rescue build infrastructure</a></li><li><a href="#uart(4)">uart(4)</a></li><li><a href="#VideoBSD">VideoBSD</a></li><li><a href="#WifiBSD-Status-Report">WifiBSD Status Report</a></li><li><a href="#Wireless-Networking-Support">Wireless Networking Support</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-     Bluetooth stack for FreeBSD (Netgraph implementation)
-   </a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.geocities.com/m_evmenkin/" title="http://www.geocities.com/m_evmenkin/">Latest snapshot</a></td><td>
-	    URL: <a href="http://www.geocities.com/m_evmenkin/" title="Latest snapshot">http://www.geocities.com/m_evmenkin/</a></td></tr><tr><td><a href="http://bluez.sf.net" title="http://bluez.sf.net">Linux BlueZ stack</a></td><td>
-	    URL: <a href="http://bluez.sf.net" title="Linux BlueZ stack">http://bluez.sf.net</a></td></tr><tr><td><a href="http://sourceforge.net/projects/openobex/" title="http://sourceforge.net/projects/openobex/">OpenOBEX</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/openobex/" title="OpenOBEX">http://sourceforge.net/projects/openobex/</a></td></tr></table><p>
-	Contact:
-         Maksim
-         Yevmenkin
-        &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-     <p>I'm very pleased to announce that another release is available for
-       download at
-       http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030908.tar.gz.
-       I have also prepared patch for the FreeBSD source tree. The patch
-       was submitted for review to the committers.</p>
-
-     <p>Fixed few bugs in kernel modules. The ng_hci(4) and ng_l2cap(4)
-       modules were changed to fix issue with Netgraph timeouts. The
-       ng_ubt(4) module was changed to fix compilation issue on -current.</p>
-
-     <p>Improved user-space utilities. Implemented new libsdp(3). Added
-       new sdpcontrol(8) utility. The rfcomm_sppd(1), rfcomm_pppd(8) and
-       obexapp(1) were changed and now can obtain RFCOMM channel via SDP
-       from the server. The hccontorol(8) utility now has four new
-       commands. The hcsecd(8) daemon now saves link keys on the disk.</p>
-
-     <p>I've been recently contacted by few individuals who whould like to
-       port current FreeBSD Bluetooth code to other BSD systems (OpenBSD
-       and NetBSD). The work is slowly progressing towards
-       un-Netgraph'ing current code. In the mean time Netgraph version
-       will be the primary supported version of the code.</p>
-   <hr /><h2><a name="ACPI-Status-Report" href="#ACPI-Status-Report" id="ACPI-Status-Report">ACPI Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.root.org/~nate/freebsd/" title="http://www.root.org/~nate/freebsd/"></a></td><td>
-	    URL: <a href="http://www.root.org/~nate/freebsd/" title="">http://www.root.org/~nate/freebsd/</a></td></tr></table><p>
-	Contact:
-	Nate
-	Lawson
-       &lt;<a href="mailto:njl@FreeBSD.org">njl@FreeBSD.org</a>&gt;
-	</p>
-    <p>Work is continuing on updating ACPI with new features as well
-      as bugfixing.  A new embedded controller driver was written in
-      July with support for the ACPI 2.0 ECDT as well as more robust
-      polling support.  Also, a buffer overflow in the ACPICA resource list
-      handling that caused panics for some users was fixed.  Marcel
-      helped get acpidump(8) tested and basically working on ia64.</p>
-
-    <p>Upcoming work includes integrating ACPI notifies with devd(8),
-      committing user-submitted drivers for ASUS and Toshiba hotkeys,
-      Cx processor sleep states (so my laptop doesn't burn my lap), and
-      power resource support for intelligently powering down unused or idle
-      devices.</p>
-
-    <p>Users who have problems with ACPI are encouraged to submit a PR
-      and email its number to acpi-jp@jp.FreeBSD.org.  Bug reports
-      of panics or crashes have first priority and non-working features
-      or missing devices (except suspend/resume problems) second.
-      Reports of failed suspend/resume should NOT be submitted as PRs
-      at this time due to most of them being a result of incomplete
-      device support that is being addressed.  However, feel free
-      to mail them to the list as any information is helpful.</p>
-  <hr /><h2><a name="AMD64-Porting" href="#AMD64-Porting" id="AMD64-Porting">AMD64 Porting</a></h2><p>
-	Contact:
-	Peter
-	Wemm
-       &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;
-	</p>
-    <p>The last known bug that prevented AMD64 machines completing a
-      full release has been fixed - one single character error that
-      caused ghostscript to crash during rendering diagrams.  SMP work
-      is nearing completion and should be committed within the next few
-      days. The SMP code uses the ACPI MADT table based on John Baldwin's
-      work-in-progress there for i386.  We need to spend some time on
-      low level optimization because there are several suboptimal places
-      that have been ignored for simplicity, context switching in
-      particular.  MTRR support has been committed and XFree86 can use
-      it.  cvsup now works but the ezm3 port has not been updated yet.
-      The default data segment size limit is 8GB instead of 512M, and
-      the (primitive) i386 binary emulation support knows how to lower
-      the rlimits for executing 32 bit binaries.</p>
-
-    <p>Notable things missing still: Hardware debug register support
-      needs to be written; gdb is still being done as an external
-      set of patches relative to the not-yet-released FSF gdb tree;
-      DDB does not disassemble properly; DDB cannot do stack traces
-      without -fno-omit-frame-pointer - a stack unwinder is needed;
-      i386 and amd64 linux binary emulation is needed, and the i386
-      FreeBSD binary emulation still needs work - removing the
-      stackgap code in particular.</p>
-
-    <p>The platform in general is very reliable although a couple of
-      problems have been reported over the last week.  One appears to
-      be a stuck interrupt, but all that code has been redone for SMP
-      support.</p>
-
-  <hr /><h2><a name="ATAPI/CAM-Status-Report" href="#ATAPI/CAM-Status-Report" id="ATAPI/CAM-Status-Report">ATAPI/CAM Status Report</a></h2><p>
-	Contact:
-	Thomas
-	Quinot
-       &lt;<a href="mailto:thomas@FreeBSD.org">thomas@FreeBSD.org</a>&gt;
-	</p>
-    <p>With the introduction of ATAng, some users of ATAPI/CAM have
-      experienced various problems. These have been mostly tracked down
-      to issues in the new ATA code, as well as two long-standing problems
-      in portions of the CAM layer that are rarely exercised with
-      "real" SCSI SIMs. This has also been an occasion to cleanup
-      ATAPI/CAM to make it more robust, and to enable DMA for devices
-      accessed through it, resulting in improved performances.</p>
-
-  <hr /><h2><a name="Binary-security-updates-for-FreeBSD" href="#Binary-security-updates-for-FreeBSD" id="Binary-security-updates-for-FreeBSD">Binary security updates for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-update/" title="http://www.daemonology.net/freebsd-update/"></a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-update/" title="">http://www.daemonology.net/freebsd-update/</a></td></tr></table><p>
-	Contact:
-        Colin
-        Percival
-       &lt;<a href="mailto:cperciva@daemonology.net">cperciva@daemonology.net</a>&gt;
-	</p>
-    <p>FreeBSD Update is a system for tracking the FreeBSD release
-      (security) branches.  In addition to being faster and more
-      convenient than source updates, FreeBSD Update also requires
-      less bandwidth and is more secure than source updates via
-      CVSup.  However, FreeBSD Update is limited; it can only
-      update files which were installed from an official RELEASE
-      image and not recompiled locally.  Right now I'm publishing
-      binary updates for 4.7-RELEASE and 4.8-RELEASE; since my
-      only available box takes 3.5 hours to buildworld, I don't
-      have enough resources to do any more than that.</p>
-
-    <p>In the near future, I'd like to: Find someone who is
-      willing to donate a faster buildbox; start building updates
-      for other releases (at a minimum, for all "supported" FreeBSD
-      releases); add warnings if a file would have been updated
-      but can't be updated because it was recompiled locally; add
-      code to compare the local system against a list of "valid"
-      MD5 hashes for intrusion detection purposes; and add support
-      for cross-signing, whereby several machines could build
-      updates independently to protect against buildbox
-      compromise.</p>
-  <hr /><h2><a name="bsd.java.mk-version-2.0" href="#bsd.java.mk-version-2.0" id="bsd.java.mk-version-2.0">bsd.java.mk version 2.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html" title="http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html">Project homepage</a></td><td>
-	    URL: <a href="http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html" title="Project homepage">http://www.esil.univ-mrs.fr/~hquiroz/freebsd/bsd.java.mk-2.0.html</a></td></tr></table><p>
-	Contact:
-        Ernst
-        De Haan
-       &lt;<a href="mailto:znerd@FreeBSD.org">znerd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Herve
-        Quiroz
-       &lt;<a href="mailto:herve.quiroz@esil.univ-mrs.fr">herve.quiroz@esil.univ-mrs.fr</a>&gt;
-	</p>
-    <p>The FreeBSD Java community has started an effort to improve the
-      current framework for Java-based ports. The main objective is the
-      automation of JDK/JRE build and run dependency checking.</p>
-    <p>The original version was aimed to ease the life of porters.  Although
-      it has proved to be useful and reliable to a great extend, we are
-      currently working on a new version. We intend to reach a high degree
-      of flexibility to cope with the recent increase of available JDK/JRE
-      flavors.  Furthermore, the new version will be easier to maintain,
-      which means improved reliability, and hopefully more frequent
-      updates.</p>
-  <hr /><h2><a name="Compile-FreeBSD-with-Intels-C-compiler-(icc)" href="#Compile-FreeBSD-with-Intels-C-compiler-(icc)" id="Compile-FreeBSD-with-Intels-C-compiler-(icc)">Compile FreeBSD with Intels C compiler (icc)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.Leidinger.net/FreeBSD/" title="http://www.Leidinger.net/FreeBSD/">Some patches.</a></td><td>
-	    URL: <a href="http://www.Leidinger.net/FreeBSD/" title="Some patches.">http://www.Leidinger.net/FreeBSD/</a></td></tr></table><p>
-	Contact:
-	Alexander
-	Leidinger
-       &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-    <p>Since I ported icc to FreeBSD I wanted to build FreeBSD with icc. Now
-      with icc 7.1 (and some patches) it is possible. There are still some bugs,
-      e.g. NFS doesn't work with an icc compiled kernel, IP seems to be fragile,
-      and some advanced optimizations trigger an ICE (Intel is working on it).
-      At the moment I'm waiting for our admins to install icc on the FreeBSD
-      cluster (we got a commercial license from Intel, so we are allowed to
-      distribute binaries which are compiled with icc), after that I will try
-      to convince some people with more knowledge of the IP and NFS parts of
-      the kernel to debug the remaining problems. When the icc compiled kernel
-      seems to work mostly bugfree the userland will get the porting focus.
-      Interested people may try to do a build of the ports tree with icc
-      independently from the status of the porting of the userland... if this
-      happens at the FreeBSD cluster, we would also be allowed to distribute
-      the binaries.</p>
-    <p>Benefits include: another set of compiler errors (debugging help),
-      more portable source, and code which is better optimized for a P4 (gcc
-      has some drawbacks in this area)</p>
-  <hr /><h2><a name="Cryptographic-Support" href="#Cryptographic-Support" id="Cryptographic-Support">Cryptographic Support</a></h2><p>
-	Contact:
-	Sam
-	Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>Support for several new crypto devices was added. The SafeNet 1141 is a
-      medium performance part that is not yet available on retail products.  The
-      Hifn 7955 and 7956 parts are starting to appear on retail products that
-      should be available by the end of the year.  Both devices support AES
-      encryption.  Support for public key operations for the SafeNet devices was
-      recently done for OpenBSD and will be backported. Public key support for
-      the Hifn parts is planned.</p>
-
-    <p>A paper about the performance work done on the cryptographic subsystem
-      was presented at the Usenix BSDCon 2003 conference and received the best
-      paper award.</p>
-
-    <p>NetBSD recently imported the cryptographic subsystem.</p>
-  <hr /><h2><a name="Device_t-locking" href="#Device_t-locking" id="Device_t-locking">Device_t locking</a></h2><p>
-	Contact:
-	Warner
-	Losh
-       &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-    <p>A number of races have been identified in locking device_t.
-      Most of the races have been identified in making device_t have to
-      do with how drivers are written.  Efforts are underway to identify
-      all the races, and to contact the authors of subsystems that can
-      help the drivers.  Of special concern is the need for the driver
-      to ensure that all threads are completely out of the driver code
-      before detach() finishes.  Of additional concern is making sure
-      that all sleepers are woken up before certain routines are called
-      so that other subsystems can ensure the last condition and leave
-      no dangling references.  Locking device_t is relatively straight
-      forward apart from these issues.  Towards the end of proper
-      locking, sample strawmen drivers are being used to work out what,
-      exactly proper is.  Once these issues are all known and documented
-      in the code, efforts will be made to update relevant documentation
-      in the tree.  There are many problems with driver locking that has
-      been done to date, but until we nail down how to write a driver in
-      current, it will be premature to contact specific driver writers
-      with specific concerns.</p>
-
-  <hr /><h2><a name="Disk-I/O" href="#Disk-I/O" id="Disk-I/O">Disk I/O</a></h2><p>
-	Contact:
-	Poul-Henning
-	Kamp
-       &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-    <p>The following items are in progress in the Disk I/O area:
-      Turn scsi_cd.c into a GEOM driver.  (Patch out for review).
-      Turn atapi-cd.c into a GEOM driver.
-      Turn fd.c into a GEOM driver.
-      Move softupdates and snapshot processing from SPECFS to UFS/FFS.
-      Move userland access to device drivers out of vnodes.</p>
-    <p>Once these preliminaries are dealt with, scatter/gather and
-      mapped/unmapped support will be added to struct bio/GEOM.</p>
-  <hr /><h2><a name="Dynamically-Linked-Root-Support" href="#Dynamically-Linked-Root-Support" id="Dynamically-Linked-Root-Support">Dynamically Linked Root Support</a></h2><p>
-	Contact:
-	Gordon
-	Tetlow
-       &lt;<a href="mailto:gordon@FreeBSD.org">gordon@FreeBSD.org</a>&gt;
-	</p>
-    <p>Support for a dynamically linked /bin and /sbin has been committed,
-      although it is not turned on by default. Adventurous users can try it
-      out by building /bin and /sbin using the WITH_DYNAMICROOT make flag.
-      More testing is needed to determine if this is going to be default for
-      5.2-RELEASE. If anyone would like to benchmark worldstones with and
-      without dynamically linked /bin and /sbin, please feel free to do so
-      and submit the results.</p>
-  <hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java/" title="http://www.FreeBSD.org/java/">FreeBSD Java Project</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java/" title="FreeBSD Java Project">http://www.FreeBSD.org/java/</a></td></tr></table><p>
-	Contact:
-	Greg
-	Lewis
-       &lt;<a href="mailto:glewis@FreeBSD.org">glewis@FreeBSD.org</a>&gt;
-	</p>
-    <p>The BSD Java Porting Team has recently reached an exciting milestone
-      with the release of the first "Diablo" JDK and JRE courtesy of the
-      FreeBSD Foundation.  The release of Diablo Caffe and Diablo Latte
-      1.3.1 was the first binary release of a native FreeBSD JDK since
-      1.1.8 and marks an important step forward in FreeBSD Java support.</p>
-
-    <p>The team is continuing development work, with a focus on achieving
-      a compliant JDK 1.4 release in the near future.</p>
-  <hr /><h2><a name="FreeBSD-ports-monitoring-system" href="#FreeBSD-ports-monitoring-system" id="FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html" title="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html" title="FreeBSD ports monitoring system">http://lonesome.dyndns.org:4802/bento/errorlogs/index.html</a></td></tr></table><p>
-	Contact:
-	Mark
-	Linimon
-       &lt;<a href="mailto:linimon_at_lonesome_dot_com">linimon_at_lonesome_dot_com</a>&gt;
-	</p>
-    <p>Several months ago, I took it upon myself to to try present the
-      information contained on <a href="http://bento.FreeBSD.org" shape="rect">the bento
-      build cluster</a> to be presented in a more user-friendly fashion; that
-      is, to be browsed by error type, by maintainer, and so forth.  An early
-      addition was code to attempt to classify ports PRs by either "existing
-      port" (after assiging the most likely category and portname); "new port";
-      "framework" (e.g. bsd.port.mk changes); and "unknown".  Various columns
-      about the ports PRs were added to the reports.</p>
-
-    <p>The initial intent of this was to make life easier for ports
-      maintainers; however, the "general" reports are also useful to anyone who
-      just wants to, e.g., find out if a particular port is working on their
-      particular architecture and OS combination before downloading it.  Those
-      with that general interest should start with the
-      <a href="http://lonesome.dyndns.org:4802/bento/errorlogs/portoverview.py" shape="rect">
-      overview of one port</a>.</p>
-  <hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/platforms/ia64/index.html" title="http://www.FreeBSD.org/platforms/ia64/index.html">Project home page.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/platforms/ia64/index.html" title="Project home page.">http://www.FreeBSD.org/platforms/ia64/index.html</a></td></tr></table><p>
-	Contact:
-	Marcel
-	Moolenaar
-       &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	</p>
-    <p>Much has happened since the last bi-monthly report, which was more
-      than half a year ago. FreeBSD 5.0 and FreeBSD 5.1 have been released
-      for example. With FreeBSD 5.2 approaching quickly, we're not going
-      to look back too far when it comes to our achievements. There's too
-      much ahead of us...</p>
-    <p>Two milestones have been reached after FreeBSD 5.1. The first is the
-      ability to support both Intel and HP machines with sources in CVS.
-      This due to a whole new driver for serial ports, or UARTs. Unfortunately
-      this still implies that syscons is not configured. That's another task
-      for another time, but keep an eye on KGI/FreeBSD...
-      The second milestone is the completion of KSE support. Both M:N and
-      1:1 threading is functional on ia64 and the old libc_r library has been
-      obsoleted. Testing has shown that KSE (i.e. M:N) may well become the
-      default threading model. It's looking good.</p>
-    <p>The ABI hasn't changed after 5.1 and the expectation is that it won't
-      change much. This means that we can think about becoming a tier 1
-      platform. This also means we need gdb(1) support. Work on it has been
-      started but the road is bumpy and long.
-      Kernel stability also has improved significantly and we typically have
-      one kernel panic remaining: VM fault on no fault entry. This will be
-      addressed with the long awaited PMAP overhaul (see below).</p>
-    <p>Most work for FreeBSD 5.2 will be "sharpening the saw". Get those
-      loose ends tied. This is a slight change of plan made possible by a
-      slip in the release schedule. The 5.2 release is not going to be the
-      start of the -stable branch; it has been moved to 5.3. So, we use the
-      extra time to prepare the ground for 5.3.</p>
-    <p>The planned PMAP overhaul will probably be finished after 5.2. This
-      should address all known issues with SMP and fix those last panics.
-      As a side-effect, major performance improvements can be expected. More
-      news about this in the next status reports.</p>
-  <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project">http://www.jp.FreeBSD.org/man-jp/</a></td></tr><tr><td><a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.1.0/ja-man-doc-5.1.tbz" title="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.1.0/ja-man-doc-5.1.tbz">package ja-man-doc-5.1.tbz</a></td><td>
-	    URL: <a href="ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.1.0/ja-man-doc-5.1.tbz" title="package ja-man-doc-5.1.tbz">ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.1.0/ja-man-doc-5.1.tbz</a></td></tr></table><p>
-	Contact:
-	Kazuo
-	Horikawa
-       &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-     <p>We have released Japanese translation of 5.1-RELEASE online manual
-       pages on June 10.</p>
-  <hr /><h2><a name="KDE-FreeBSD-Project" href="#KDE-FreeBSD-Project" id="KDE-FreeBSD-Project">KDE FreeBSD Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freebsd.kde.org/" title="http://freebsd.kde.org/"></a></td><td>
-	    URL: <a href="http://freebsd.kde.org/" title="">http://freebsd.kde.org/</a></td></tr></table><p>
-	Contact:
-	KDE-FreeBSD
-	Mailinglist
-       &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-    <p>The FreeBSD ports were updated to KDE 3.1.4, another bug- and
-      security-fixes release. With this update, the QT port was updated
-      to version 3.2. Both will be included in FreeBSD 4.9.
-      Significant work was spent to fix KDE on FreeBSD-CURRENT after the
-      removal of the gcc -pthread Option. Automatic package builds from
-      KDE CVS continued to ensure and improve the quality of the upcoming
-      KDE 3.2 release.</p>
-
-    <p>Future: Work is in progress to setup a new server for hosting the
-      KDE-FreeBSD Website, Repository and another KDE CVS mirror. With
-      help from Marcel Moolenaar the project will try to make KDE compile
-      and working on the Intel IA64. And last but not least efforts are
-      being made to fix the currently broken kdesu program.</p>
-  <hr /><h2><a name="kgi4BSD-Status-Report" href="#kgi4BSD-Status-Report" id="kgi4BSD-Status-Report">kgi4BSD Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="http://www.FreeBSD.org/~nsouch/kgi4BSD">Project URL</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="Project URL">http://www.FreeBSD.org/~nsouch/kgi4BSD</a></td></tr></table><p>
-	Contact:
-	Nicholas
-	Souchu
-       &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-    <p>A lot of work done since last report: site reworked completely (see new
-      URL), console design with console message in text or graphic modes
-      implemented, implementation of a compatibility layer to compile Linux
-      fbdev drivers with more or less changes in the original driver
-      (experimental).</p>
-
-    <p>Except some memory allocation bugs, X (XGGI based on XFree 3.3.6) is
-      now working with the same driver as the console. A basic terminal has
-      now to be implemented.</p>
-
-    <p> Volunteers are welcome to the project...</p>
-
-  <hr /><h2><a name="KSE" href="#KSE" id="KSE">KSE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	Dan
-	Eischen
-       &lt;<a href="mailto:deischen@FreeBSD.org">deischen@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        David
-        Xu
-       &lt;<a href="mailto:davidxu@FreeBSD.org">davidxu@FreeBSD.org</a>&gt;
-	</p>
-    <p>KSE seems to be working well on x86, amd64, and ia64.  The
-      alpha userland bits are done, but a couple of functions are
-      unimplemented in the kernel.  For sparc64, the necessary
-      functions are implemented in the kernel, but the userland
-      context switching functions need more attention.</p>
-
-    <p>Since 5.1, efficient scope system threads (no upcalls when they block)
-      have been implemented, and KSE based pthread library can have both POSIX
-      scope process threads and scope system threads. It is also possible
-      that KSE based pthread library can implement pthread both in 1:1 and M:N
-      mode, I know Dan has such Makefile file patch for libkse not yet
-      committed.</p>
-
-    <p>KSE program now can work under ULE scheduler, its efficient should be
-      improved under the new scheduler in future. BSD scheduler is still the
-      best scheduler for current KSE implement.</p>
-  <hr /><h2><a name="Network-Subsystem-Locking-and-Performance" href="#Network-Subsystem-Locking-and-Performance" id="Network-Subsystem-Locking-and-Performance">Network Subsystem Locking and Performance</a></h2><p>
-	Contact:
-        Sam
-        Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>The purpose of this project is to improve performance of the network
-      subsystem.  A major part of this work is to complete the locking of the
-      networking subsystem so that it no longer depends on the "Giant lock"
-      for proper operation.  Removing the use of Giant will improve
-      performance and permit multiple instances of the network stack to
-      operate concurrently on multiprocessor systems.</p>
-
-   <p>This project started in August.  The emphasis has been on locking the
-     "lower half" of the networking code so that packet forwarding through the
-     IPv4 path can operate without the Giant lock as part of the 5.2 release.
-     To this end locking was added to several network interface drivers and
-     much of the "middleware" code in the network was locked (e.g. ipfw,
-     dummynet, then routing table, multicast routing support, etc). Work
-     towards this goal is still ongoing but should be ready for 5.2.  A
-     variety of test systems have been running for several months without the
-     Giant lock in the network drivers and IP layer.</p>
-
-   <p>Past the 5.2 release Giant will be removed from the "upper half" of the
-     network subsystem and the socket layer.  Once this is done the plan is to
-     measure and improve performance (though some work of this sort is always
-     happening). The ultimate goal is a system that performs at least as well
-     as 4.x for normal use on uniprocessor systems.  On multiprocessor systems
-     we expect to see significantly better performance than 4.x due to greater
-     concurrency and reduced latency.</p>
-
-  <hr /><h2><a name="Porting-OpenBSD's-pf" href="#Porting-OpenBSD's-pf" id="Porting-OpenBSD's-pf">Porting OpenBSD's pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pf4freebsd.love2party.net" title="http://pf4freebsd.love2party.net">http://pf4freebsd.love2party.net</a></td><td>
-	    URL: <a href="http://pf4freebsd.love2party.net" title="http://pf4freebsd.love2party.net">http://pf4freebsd.love2party.net</a></td></tr><tr><td><a href="http://www.benzedrine.cx/pf.html" title="http://www.benzedrine.cx/pf.html">PF homepage</a></td><td>
-	    URL: <a href="http://www.benzedrine.cx/pf.html" title="PF homepage">http://www.benzedrine.cx/pf.html</a></td></tr><tr><td><a href="http://openbsd.org/faq/pf/index.html" title="http://openbsd.org/faq/pf/index.html">PF FAQ</a></td><td>
-	    URL: <a href="http://openbsd.org/faq/pf/index.html" title="PF FAQ">http://openbsd.org/faq/pf/index.html</a></td></tr></table><p>
-	Contact:
-	Max
-	Laier
-       &lt;<a href="mailto:max@love2party.net">max@love2party.net</a>&gt;
-	<br />
-	Contact:
-	Pyun
-	YongHyeon
-       &lt;<a href="mailto:yongari@kt-is.co.kr">yongari@kt-is.co.kr</a>&gt;
-	</p>
-    <p>The project started this spring and released version 1.0 with a port
-      installation (security/pf) in may 2003. Version 2.0 is on the doorstep
-      as OpenBSD 3.4 will be released. Due to the porting efforts we were
-      able to reveal some bugs in the OpenBSD code and provided locking for
-      the PFIL_HOOKS, which we utilize. Tarball installation of a loadable
-      kernel module for testing can be found on the project homepage, a
-      patchset is in the making.</p>
-
-    <p>PF was started at OpenBSD as a substitute for ipfilter and provides
-      the same function set. However, in the two years it exists now, it has
-      gained many superior features that no other packet filter has. For a
-      impression take a look at the pf FAQ.</p>
-
-    <p>We hope to be eventually integrated into the base system. Before that
-      we have to resolve some issues with tcpdump and kame.</p>
-  <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-        Peter
-        Grehan
-       &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-    <p>Work has restarted after a hiatus. Current focus is on getting
-      loadable modules working, NEWBUSing the NetBSD dbdma code, and
-      completing the BMAC ethernet driver.</p>
-
-    <p>There is a huge amount of work to do. Volunteers more than welcome!</p>
-  <hr /><h2><a name="Release-Engineering-Status" href="#Release-Engineering-Status" id="Release-Engineering-Status">Release Engineering Status</a></h2><p>
-	Contact:
-        Scott
-        Long
-       &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-    <p>The release of 4.9 is just around the corner and offers Physical Address
-      Extensions (PAE) for x86 along with the same world-class stability and
-      performance that is expected from the 4-STABLE series.  As always, don't
-      forget to purchase a copy of the CD set from your favorite FreeBSD
-      vendor.</p>
-
-    <p>FreeBSD 5.1 was released in June and offered vastly improved
-      stability over 5.0 along with a working implementation of Kernel
-      Scheduled Entities, allowing for true multithreading of applications
-      across multiple CPUs.  FreeBSD 5.2 will be released by the end of 2003
-      and will focus on improved network and overall performance.</p>
-
-  <hr /><h2><a name="Rescue-build-infrastructure" href="#Rescue-build-infrastructure" id="Rescue-build-infrastructure">Rescue build infrastructure</a></h2><p>
-	Contact:
-	Gordon
-	Tetlow
-       &lt;<a href="mailto:gordon@FreeBSD.org">gordon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-        Tim
-        Kientzle
-       &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	</p>
-    <p>The rescue build infrastructure has been committed. There is one
-      known issue with make using both the '-s' and '-j' flags that appears
-      to be a bug in make. Anyone interested in tracking down should contact
-      us.</p>
-  <hr /><h2><a name="uart(4)" href="#uart(4)" id="uart(4)">uart(4)</a></h2><p>
-	Contact:
-	Marcel
-	Moolenaar
-       &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	</p>
-    <p>The uart(4) project was born out of the need to have a working
-      serial interface (i.e. an RS-232-C interface) in a legacy-free
-      configuration and after an unsuccessful attempt to convert sio(4).
-      The biggest problem with sio(4) is that it has been intertwined
-      in many ugly ways into the kernel's core. Conversion could not
-      happen without breaking something that invariably affects some
-      group of people negatively. With sio(4) as a good bad example
-      and a strong desire to solve multiple problems at once, the
-      idea of an UART (Universal Asynchronuous Receiver/Transmitter)
-      device that, given its generic name, could handle different
-      flavors of UART hardware started to settle firmly in the authors
-      mind.</p>
-    <p>The biggest challenge was of course solving the problem of the
-      low-level console access prior to the initialization of the bus
-      infrastructure and still have a driver that uses the bus access
-      exclusively. Along the way the problem of having an UART function
-      as the keyboard on sparc64 was solved with the introduction of
-      system devices, which also encapsulated the console as a system
-      device.</p>
-    <p>The uart(4) driver can be enhanced to support the various UART
-      hardware on pc98 and this is currently being worked on. Keyboard
-      support on sparc64 is underway as well. Plans exist for a rewrite
-      of the remote gdb support that uses a generic interface to allow
-      various drivers, including uart(4), to register itself as a
-      communications channel. And since uart(4) does not support multi-
-      port cards by itself, we likely need to either enhance puc(4) or
-      otherwise introduce other umbrella drivers</p>
-  <hr /><h2><a name="VideoBSD" href="#VideoBSD" id="VideoBSD">VideoBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~jmg/videobsd.html" title="http://people.FreeBSD.org/~jmg/videobsd.html">Documentation of VideoBSD</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~jmg/videobsd.html" title="Documentation of VideoBSD">http://people.FreeBSD.org/~jmg/videobsd.html</a></td></tr></table><p>
-	Contact:
-	John-Mark
-	Gurney
-       &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-    <p>Still in the planning stage.  Working on creating an extensible
-      interface that is usable for both userland and kernel implementations
-      for device drivers.  Deciding on how to interface userland implemented
-      device drivers with applications.</p>
-  <hr /><h2><a name="WifiBSD-Status-Report" href="#WifiBSD-Status-Report" id="WifiBSD-Status-Report">WifiBSD Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.wifibsd.org" title="http://www.wifibsd.org">www.wifibsd.org</a></td><td>
-	    URL: <a href="http://www.wifibsd.org" title="www.wifibsd.org">http://www.wifibsd.org</a></td></tr></table><p>
-	Contact:
-	Jon
-	Disnard
-       &lt;<a href="mailto:masta@wifibsd.org">masta@wifibsd.org</a>&gt;
-	</p>
-    <p>WifiBSD is a miniture version of FreeBSD for wireless applications.
-      Originally for the Soekris Net45xx line of main-boards, but is now
-      capable of being targeted to any hardware/architecture FreeBSD itself
-      supports.  Although not feature complete, WifiBSD is expected to be
-      ready for 5.2-RELEASE.  The design goal is to meet, or exceed, the
-      functionality of commercial/consumer 802.11 wireless gear.  Features
-      that need attention (to name just a few) are: http interface, consol
-      menu interface, and installation.  Volunters are welcome.</p>
-  <hr /><h2><a name="Wireless-Networking-Support" href="#Wireless-Networking-Support" id="Wireless-Networking-Support">Wireless Networking Support</a></h2><p>
-	Contact:
-        Sam
-        Leffler
-       &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-    <p>Numerous bugs have been fixed since the last status report (and of
-      course a few new ones added).  Progress on improved security has been
-      slowed by other work.  But new features and fixes are coming in from
-      other groups that are now sharing the code.  In particular NetBSD
-      recently imported the revised 802.11 layer and the Linux-based MADWIFI
-      project is using it too (albeit in an older form).  The MADWIFI users
-      have already contributed features such as fragmentation reassembly of
-      802.11 frames and improved signal monitoring.  Power save polling and
-      an improved rate control algorothm are expected to come in from the
-      NetBSD folks.  WPA support is still in the plans; the best estimate is
-      that work on that will start in January.</p>
-
-  <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2003-10-2003-12.html b/website/content/en/status/report-2003-10-2003-12.html
deleted file mode 100644
index 20db6ae1eb..0000000000
--- a/website/content/en/status/report-2003-10-2003-12.html
+++ /dev/null
@@ -1,1187 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction:</h1><p>The FreeBSD status reports are back again with the 2003 year-end
-      edition.  Many new projects are starting up and gaining momentum,
-      including XFS, MIPS, PowerPC, and networking locking and
-      multithreading.  The end of 2003 also saw the release of FreeBSD 4.9,
-      the first stable release to have greater than 4GB support for the
-      ia32 platform.  Work on FreeBSD 5.2 also finished up and was released
-      early in January of 2004.  Many thanks to all of the people who
-      worked so hard on these releases and made them happen.</p><p>This is the largest status report ever, so read and enjoy!</p><p>Scott Long, Robert Watson</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-      Bluetooth stack for FreeBSD (Netgraph implementation)
-    </a></li><li><a href="#ACPI">ACPI</a></li><li><a href="#AGP-3.0-Support">AGP 3.0 Support</a></li><li><a href="#Binary-security-updates-for-FreeBSD">Binary security updates for FreeBSD</a></li><li><a href="#Compile-FreeBSD-with-Intels-C-compiler-(icc)">Compile FreeBSD with Intels C compiler (icc)</a></li><li><a href="#Donations-Team">Donations Team</a></li><li><a href="#DVB-ASI-Support">DVB-ASI Support</a></li><li><a href="#FreeBSD-MIDI">FreeBSD MIDI</a></li><li><a href="#FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></li><li><a href="#FreeBSD/MIPS-Status-Report">FreeBSD/MIPS Status Report</a></li><li><a href="#FreeBSD/powerpc-on-PPCBug-based-embedded-boards">FreeBSD/powerpc on PPCBug-based embedded boards</a></li><li><a href="#jpman-project">jpman project</a></li><li><a href="#Kernel-Tunables-Documentation-Project">Kernel Tunables Documentation Project</a></li><li><a href="#kgi4BSD-Status-Report">kgi4BSD Status Report</a></li><li><a href="#KSE">KSE</a></li><li><a href="#libarchive,-bsdtar">libarchive, bsdtar</a></li><li><a href="#Network-interface-naming-changes">Network interface naming changes</a></li><li><a href="#Network-Subsystem-Locking-and-Performance">Network Subsystem Locking and Performance</a></li><li><a href="#Porting-OpenBSD's-pf">Porting OpenBSD's pf</a></li><li><a href="#Publications-Page-Update">Publications Page Update</a></li><li><a href="#SGI-XFS-port-for-FreeBSD">SGI XFS port for FreeBSD</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#The-FreeBSD-Russian-Documentation-Project">The FreeBSD Russian Documentation Project</a></li><li><a href="#TrustedBSD-&quot;Security-Enhanced-BSD&quot;----FLASK/TE-Port">TrustedBSD "Security-Enhanced BSD" -- FLASK/TE Port</a></li><li><a href="#TrustedBSD-Access-Control-Lists-(ACLs)">TrustedBSD Access Control Lists (ACLs)</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-Documentation">TrustedBSD Documentation</a></li><li><a href="#TrustedBSD-Mandatory-Access-Control-(MAC)">TrustedBSD Mandatory Access Control (MAC)</a></li><li><a href="#Wireless-Networking-Support">Wireless Networking Support</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-      Bluetooth stack for FreeBSD (Netgraph implementation)
-    </a></h2><p>
-	Contact:
-
-            Maksim
-
-
-
-            Yevmenkin
-
-         &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-      <p>Not much to report. Bluetooth code was integrated into the FreeBSD
-        source tree. Bluetooth kernel modules appear to be stable. I have
-        received few success stories from the users.</p>
-
-      <p>During last few months the efforts were to make Bluetooth code
-        more user friendly. Bluetooth Service Discovery Procotol daemon
-        sdpd was reimplemented under BSD-style license and committed. The
-        next step is to integrate existing Bluetooth utilities with SDP.</p>
-
-      <p>Thanks to Matt Peterson &lt;matt at peterson dot org&gt; I now have
-        Bluetooth keyboard and mouse for development. I'm currently
-        working on Bluetooth HID profile implementation.</p>
-
-      <p>Dave Sainty &lt;dave at dtsp dot co dot nz&gt; from NetBSD project
-        offered his help in porting Bluetooth stack to NetBSD.</p>
-    <hr /><h2><a name="ACPI" href="#ACPI" id="ACPI">ACPI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.root.org/~nate/freebsd/" title="http://www.root.org/~nate/freebsd/">ACPI TODO</a></td><td>
-	    URL: <a href="http://www.root.org/~nate/freebsd/" title="ACPI TODO">http://www.root.org/~nate/freebsd/</a></td></tr><tr><td><a href="http://home.jp.FreeBSD.org/mail-list/acpi-jp/" title="http://home.jp.FreeBSD.org/mail-list/acpi-jp/">ACPI-JP Mailing List</a></td><td>
-	    URL: <a href="http://home.jp.FreeBSD.org/mail-list/acpi-jp/" title="ACPI-JP Mailing List">http://home.jp.FreeBSD.org/mail-list/acpi-jp/</a></td></tr></table><p>
-	Contact:
-          Nate
-
-          Lawson
-         &lt;<a href="mailto:njl@FreeBSD.org">njl@FreeBSD.org</a>&gt;
-	</p>
-      <p>The updated acpi_cpu driver was committed in November.  Work is
-        ongoing to finish support for _CST re-evaluation, which makes it
-        possible for laptops based on processors like the Centrino to use
-        varying CPU idle states when on or off AC power.  5.2-RELEASE also
-        went out with support for _CID packages, which fixed mouse probing
-        for Compaq users.  Control of CPU idle states and throttling can
-        now be done through rc.conf(5) settings for the /etc/power_profile
-        script, which switches between performance/economy levels when
-        the AC status changes.</p>
-
-      <p>One huge task underway is the cpufreq project, a framework for
-        detecting and controlling various frequency/voltage technologies
-        (SpeedStep, LongRun, ACPI Performance states, etc.)  The ACPI
-        performance states driver is working and the framework is being
-        implemented.  It requires newbus attachments for CPUs so some
-        ground work needs to go in before the driver can be committed.</p>
-
-      <p>ACPI-CA was updated to 20031203 in early December and with a few
-        patches is reasonably stable.  An ACPI debugging how-to has been
-        written and is being DocBooked by trhodes@.  Ongoing work on fixing
-        interrupt storms due to various ways of setting up the SCI
-        is being done by jhb@.</p>
-
-      <p>I'd like to welcome Philip Paeps (philip@) to the FreeBSD team.
-        Philip has written an ACPI ASUS driver that will be committed soon
-        and has been very helpful on the mailing lists.  We've also had
-        a lot of help from jhb@, marcel@, imp@, and peter@.  We're hoping
-        to see the return of takawata@ and iwasaki@, who have been very
-        helpful in the past.
-        If any developers are interested in assisting with ACPI, please
-        see the ACPI TODO and send us an email.</p>
-    <hr /><h2><a name="AGP-3.0-Support" href="#AGP-3.0-Support" id="AGP-3.0-Support">AGP 3.0 Support</a></h2><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Simple support AGP 3.0 including support for AGP 8x mode was
-        added.  The support is simple in that it still assumes only one
-        master and one target.  The main gain is the ability to use AGP
-        8x with drm modules that support it.</p>
-    <hr /><h2><a name="Binary-security-updates-for-FreeBSD" href="#Binary-security-updates-for-FreeBSD" id="Binary-security-updates-for-FreeBSD">Binary security updates for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-update/" title="http://www.daemonology.net/freebsd-update/"></a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-update/" title="">http://www.daemonology.net/freebsd-update/</a></td></tr></table><p>
-	Contact:
-          Colin
-
-          Percival
-         &lt;<a href="mailto:cperciva@daemonology.net">cperciva@daemonology.net</a>&gt;
-	</p>
-      <p>Thanks to recent donations, I am now building binary security
-        updates for FreeBSD {4.7, 4.8, 4.9, 5.0, 5.1, 5.2}-RELEASE.
-        (Note that FreeBSD 4.7 and 5.0 are no longer officially
-        supported; any advisories which are not reflected in the CVS
-        tree will likewise not result in binary updates.)</p>
-
-      <p>The current version (1.5) of FreeBSD Update will warn about
-        locally modified files and will, by default, leave them
-        untouched; if a "distribution branch", (i.e. crypto, nocrypto,
-        krb4, or krb5) is specified, FreeBSD Update can be forced to
-        "update" files which have been compiled locally.</p>
-
-      <p>The only major issue remaining with FreeBSD Update is the
-        single-point-of-failure of the update building process; I
-        would like to resolve this in the future by having several
-        machines cross-verify and cross-sign, but this will require
-        a significant investment of time, and will probably have to
-        wait until I've finished writing my DPhil thesis.</p>
-    <hr /><h2><a name="Compile-FreeBSD-with-Intels-C-compiler-(icc)" href="#Compile-FreeBSD-with-Intels-C-compiler-(icc)" id="Compile-FreeBSD-with-Intels-C-compiler-(icc)">Compile FreeBSD with Intels C compiler (icc)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.Leidinger.net/FreeBSD/" title="http://www.Leidinger.net/FreeBSD/">Some patches</a></td><td>
-	    URL: <a href="http://www.Leidinger.net/FreeBSD/" title="Some patches">http://www.Leidinger.net/FreeBSD/</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD kernel now builds and runs fine with icc v7 (only GENERIC
-        and a custom kernel tested so far). A review on arch@ revealed no
-        major concerns and some src committers are willing to commit the
-        patches.  As icc v8 is out and defines __GNUC__ I want to rework the
-        patches before they get committed so an icc v8 compiled kernel DTRT
-        too.</p>
-      <p>A complete build of the ports collection (as of start of December)
-        finished and is under review to determine the reason of build
-        failures.  Current <emph>icc</emph> stats:
-        <ul>
-          <li>1108 failed builds (excluding build failures because of failed
-            dependencies)</li>
-          <li>3535 successfully build packages (~ 1.7 GB)</li>
-        </ul>
-        A parallel build with <emph>gcc</emph> on the same snapshot of the
-        ports collection has:
-        <ul>
-          <li>520 failed builds (excluding build failures because of failed
-            dependencies)</li>
-          <li>7261 successfully build packages (~ 4.8 GB)</li>
-        </ul>
-      </p>
-      <p>The above mentioned build of the ports collection was run on a P4
-        with a icc compiled kernel (optimized for a P4). No kernel panics or
-        other strange behavior was noticed. The ports collection was build
-        with a CPUTYPE of p4 and CFLAGS set to "-Os -pipe -mfpmath=sse -msse2"
-        in the gcc and "-O2" in the icc case. No package is tested for correct
-        run-time behavior so far.</p>
-    <hr /><h2><a name="Donations-Team" href="#Donations-Team" id="Donations-Team">Donations Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/donations/" title="http://www.FreeBSD.org/donations/">FreeBSD Donations Project</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/donations/" title="FreeBSD Donations Project">http://www.FreeBSD.org/donations/</a></td></tr></table><p>
-	Contact:
-          Michael
-
-          Lucas
-         &lt;<a href="mailto:donations@FreeBSD.org">donations@FreeBSD.org</a>&gt;
-	</p>
-      <p>2003 was quite successful for the Donations team.  We
-        shepherded over 200 items from donors into the hands of
-        developers.  Some high points include: a small cluster for the
-        security team, assorted laptop hardware for our cardbus work,
-        and documentation for our standards group.  In the main FreeBSD.org
-        cluster we were able to replace 8 DEC Miata machines with 6
-        Alpha DS10s (21264).  Every committer doing SMP work now has
-        multi-processor testing hardware.</p>
-
-      <p>We have smoothed out the tax deduction process with the FreeBSD
-        Foundation, and can ship donated items directly to the
-        recipients instead of tying up Foundation time handling
-        shipping.</p>
-
-      <p>Current team membership is: Michael Lucas, David O'Brien, and
-        Tom Rhodes.  Wilko Bulte has replaced Robert Watson as the Core
-        Team representative.</p>
-    <hr /><h2><a name="DVB-ASI-Support" href="#DVB-ASI-Support" id="DVB-ASI-Support">DVB-ASI Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://proxy.6wind.com/~jardin/dvb/" title="http://proxy.6wind.com/~jardin/dvb/">Home page and source code</a></td><td>
-	    URL: <a href="http://proxy.6wind.com/~jardin/dvb/" title="Home page and source code">http://proxy.6wind.com/~jardin/dvb/</a></td></tr><tr><td><a href="http://www.computermodules.com/broadcast/broadcast-dvb.shtml" title="http://www.computermodules.com/broadcast/broadcast-dvb.shtml">Computer Modules</a></td><td>
-	    URL: <a href="http://www.computermodules.com/broadcast/broadcast-dvb.shtml" title="Computer Modules">http://www.computermodules.com/broadcast/broadcast-dvb.shtml</a></td></tr><tr><td><a href="http://www.dvb.org/" title="http://www.dvb.org/"></a></td><td>
-	    URL: <a href="http://www.dvb.org/" title="">http://www.dvb.org/</a></td></tr></table><p>
-	Contact:
-          Vincent
-
-          Jardin
-         &lt;<a href="mailto:Vincent.Jardin@6wind.com">Vincent.Jardin@6wind.com</a>&gt;
-	</p>
-      <p>DVB ASI stands for Digital Video Broadcast - Asynchronous Serial
-        Interface.  It is the standard defined to send and receive DVB stream
-        from Satellite (DVB-S), Terrestrial link (DVB-T), and TV Cable
-        (DVB-C).  This standard was developed in Europe to transport 188-byte
-        MPEG cells and 204-byte MPEG cells. However it can be used to carry IP
-        over DVB too.</p>
-
-      <p>The FreeBSD driver uses the newbus amd the bus-dma API. It means that it
-        could be easily ported to all the BSD flavors (NetBSD, OpenBSD).</p>
-
-      <p>It uses the same API than the Linux DVB ASI support from
-        ComputerModules that is based on the following devices:
-        <ul>
-          <li>/dev/asitxN for the transmit stream (only open, write, select,
-            close and ioctl are supported)</li>
-          <li>/dev/asirxN for the receive stream (only open, read, select, close
-            and ioctl are supported)</li>
-        </ul>
-        It means that software such as Videolan that support DVB-ASI
-        broadcasting could be supported by this driver.</p>
-
-      <p>Special thanks to Tom Thorsteinson from Computer Modules who helped
-        6WIND to port their driver. It is used by 6WIND in order to provide
-        IPv4, IPv6, Ethernet and our network services over DVB.</p>
-
-      <p>Copyright 2003-2004, 6WIND</p>
-    <hr /><h2><a name="FreeBSD-MIDI" href="#FreeBSD-MIDI" id="FreeBSD-MIDI">FreeBSD MIDI</a></h2><p>
-	Contact:
-          Mathew
-
-          Kanner
-         &lt;<a href="mailto:matk@FreeBSD.org">matk@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project aims to update the current MIDI implementation.  We
-        are currently looking at removing the current code sometime in
-        February and importing the new version soon after.  I'm currently
-        working on a kernel/timidity bridge for those without external
-        hardware.</p>
-
-    <hr /><h2><a name="FreeBSD-ports-monitoring-system" href="#FreeBSD-ports-monitoring-system" id="FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html" title="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://lonesome.dyndns.org:4802/bento/errorlogs/index.html" title="FreeBSD ports monitoring system">http://lonesome.dyndns.org:4802/bento/errorlogs/index.html</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon_at_lonesome_dot_com">linimon_at_lonesome_dot_com</a>&gt;
-	</p>
-      <p>Enhancements continue to be made to the system.  Several,
-        including improvements to the PR classification algorithm, the
-        ability to more correctly guess when a PR has been updated, and
-        better handling of errors in both port Makefiles and the bento
-        builds, are invisible to end-users.  However, the addition of
-        a "repocopy" classification is notable, as is the allowing the
-        wildcard search in "overview of one port" (thanks to edwin@ for
-        the shove in that direction.)  Additionally, logic has been
-        added to identify the proposed category/portname of new ports,
-        with the goal being to quickly identify possible duplications
-        of effort.  (Some SQL performance was sacrificed to this goal,
-        leading to some pages to load more slowly; this needs to be
-        fixed.)</p>
-
-      <p>The other work has been on an email back-end to allow the
-        occasional sending of email to maintainers.  Two functions are
-        currently available: "remind maintainers of their ports that
-        are marked BROKEN", and "remind maintainers of PRs that they
-        may not have seen."  A recent run of the former got generally
-        good response, especially as changing some cases of BROKEN to
-        IGNORE (PR ports/61090) had removed almost all the annoying
-        false positives.  However, work remains to try to find out why
-        a few allegedly broken ports only fail in certain environments
-        (including the bento cluster).</p>
-
-      <p>The next plan is to use the proposed DEPRECATED Makevar (see
-        ports/59362) to create a new report to allow querying of "ports
-        currently slated to be removed".  This report could also be
-        posted to ports@ periodically with minimal work.  The author
-        believes that doing this would allow the port deprecation process
-        to be much more visible to the general FreeBSD user community.</p>
-    <hr /><h2><a name="FreeBSD/MIPS-Status-Report" href="#FreeBSD/MIPS-Status-Report" id="FreeBSD/MIPS-Status-Report">FreeBSD/MIPS Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/mips/" title="http://www.FreeBSD.org/projects/mips/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/mips/" title="">http://www.FreeBSD.org/projects/mips/</a></td></tr></table><p>
-	Contact:
-          Juli
-
-          Mallett
-         &lt;<a href="mailto:jmallett@FreeBSD.org">jmallett@FreeBSD.org</a>&gt;
-	</p>
-      <p>TLB support code and PMAP have come along nicely.  GCC and related
-        have been kept up to date with the main tree.  An evaluation board
-        from Broadcom was donated and initial work on that platform has been
-        occurring.  Much old and obsolete code brought from NetBSD for
-        bootstrapping the effort has been cleaned up.  The system has been
-        seen to get to the point of trying to initialize filesystems, but
-        there are still bugs even before that milestone.</p>
-    <hr /><h2><a name="FreeBSD/powerpc-on-PPCBug-based-embedded-boards" href="#FreeBSD/powerpc-on-PPCBug-based-embedded-boards" id="FreeBSD/powerpc-on-PPCBug-based-embedded-boards">FreeBSD/powerpc on PPCBug-based embedded boards</a></h2><p>
-	Contact:
-          Rafal
-
-          Jaworowski
-         &lt;<a href="mailto:rafal.jaworowski@motorola.com">rafal.jaworowski@motorola.com</a>&gt;
-	</p>
-      <p>The direct objective is to make FreeBSD/powerpc work on Motorola
-        MCP750 and similar (single board computer that is compliant with
-        Compact PCI standard) Based on this work it would be easy to bring it
-        to other embedded systems.</p>
-
-      <p>1. loader(8): it is based on the existing loader for FreeBSD/powerpc
-        port but binding to OpenFirmware was removed and replaced with PPCBug
-        firmware binding.  It only supports netbooting for the moment, so disk
-        (compact flash) support needs to be done one day. The loader is the
-        only piece that relies onPPCBug system calls - once the kernel starts
-        it doesn't need firmware support any longer.</p>
-
-      <p>2. kernel: it is now divorced from OpenFirmware dependencies; most of
-        the groundwork finished includes: nexus stuff is sorted out (resources
-        management is ok except interrupts assignment); host to PCI bridge low
-        level routines are finished so configuration of and access to PCI
-        devices works; the only important thing missing is the IRQ management
-        (Raven MPIC part is done, but the board has the second PIC,
-        8259-compatible that needs to be set up, but here the existing code
-        from x86 arch will be adopted).</p>
-
-      <p>Once the IRQ management is cleared out, most of the devices on board
-        would work straight away since they are pretty standard chips with
-        drivers already implemented in the tree (e.g. if_de).</p>
-
-      <p>At the moment work is on hold (don't have physical access to the
-        device) but will resume when I'm back home (late Feb).</p>
-
-    <hr /><h2><a name="jpman-project" href="#jpman-project" id="jpman-project">jpman project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.jp.FreeBSD.org/man-jp/" title="http://www.jp.FreeBSD.org/man-jp/">jpman project</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/man-jp/" title="jpman project">http://www.jp.FreeBSD.org/man-jp/</a></td></tr></table><p>
-	Contact:
-          Kazuo
-          Horikawa
-         &lt;<a href="mailto:horikawa@FreeBSD.org">horikawa@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have been updating existing Japanese translations
-        of manual pages to meet the 5.2-RELEASE schedule.
-        Also, 22 new translations were complete during this period.</p>
-    <hr /><h2><a name="Kernel-Tunables-Documentation-Project" href="#Kernel-Tunables-Documentation-Project" id="Kernel-Tunables-Documentation-Project">Kernel Tunables Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=docs/44034" title="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=docs/44034">The problem report which kicked this project in action</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=docs/44034" title="The problem report which kicked this project in action">http://www.FreeBSD.org/cgi/query-pr.cgi?pr=docs/44034</a></td></tr></table><p>
-	Contact:
-          Tom
-          Rhodes
-         &lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD has well over a few hundred tunables without
-        documentation.  This project aims at designing an
-        automated process to rip all available tunables and generate
-        a manual page based on the selected kernel options.
-        The ideal implementation, however; would gather tunables
-        from the LINT kernels as well.  This would provide a
-        default manual page for all supported architectures.
-        A simple tool has been forged from the various off-list
-        and on-list discussions and is waiting review from the
-        -doc team.  Anyone interesting in reviewing my current
-        work is requested to get in contact with me.</p>
-    <hr /><h2><a name="kgi4BSD-Status-Report" href="#kgi4BSD-Status-Report" id="kgi4BSD-Status-Report">kgi4BSD Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="http://www.FreeBSD.org/~nsouch/kgi4BSD"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="">http://www.FreeBSD.org/~nsouch/kgi4BSD</a></td></tr><tr><td><a href="http://www.kgi-project.org" title="http://www.kgi-project.org"></a></td><td>
-	    URL: <a href="http://www.kgi-project.org" title="">http://www.kgi-project.org</a></td></tr></table><p>
-	Contact:
-          Nicholas
-
-          Souchu
-         &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most of the console blocks are in place with nice results
-        (see screenshots on the site). Boot console and virtual
-        terminals are working with 8bit rendering and perfect integration
-        of true graphic drivers in the kernel.</p>
-
-      <p>Now it is time to bring it to end user and a precompiled R5.2 GENERIC
-        kernel is available for this (see the site news). In parallel,
-        after providing a last tarball/patch for R5.2, everything will
-        move to Perforce.</p>
-
-      <p>As always, volunteers are welcome. The task is huge but very
-        exciting.</p>
-    <hr /><h2><a name="KSE" href="#KSE" id="KSE">KSE</a></h2><p>
-	Contact:
-          Daniel
-
-          Eischen
-         &lt;<a href="mailto:deischen@FreeBSD.org">deischen@FreeBSD.org</a>&gt;
-	</p>
-      <p>The libkse library will shortly be renamed to libpthread and
-        be made the default thread library.  This includes making the
-        GCC -pthread option link to -lpthread instead of libc_r and
-        changing PTHREAD_LIBS to -lpthread.  David Xu has been working
-        on GDB support and has it working with the GDB currently in our
-        tree.  The next step is to make a libpthread_db and get it working
-        with GDB 6.0 which marcel has imported into the perforce tree.</p>
-    <hr /><h2><a name="libarchive,-bsdtar" href="#libarchive,-bsdtar" id="libarchive,-bsdtar">libarchive, bsdtar</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~kientzle/libarchive/" title="http://people.FreeBSD.org/~kientzle/libarchive/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~kientzle/libarchive/" title="">http://people.FreeBSD.org/~kientzle/libarchive/</a></td></tr></table><p>
-	Contact:
-          Tim
-          Kientzle
-         &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	</p>
-      <p>The libarchive library, which reads and writes tar and cpio
-        archives, is about ready to commit to the tree.  The bsdtar
-        program, built on libarchive, is also nearing completion and
-        should soon be a worthwhile successor to our aging GNU tar.  I
-        plan a gradual transition during which "bsdtar" and "gtar" will
-        coexist in the tree.</p>
-
-      <p>Oddly enough, libarchive and bsdtar are the first fruits of a
-        project to completely rewrite the pkg tools.  I've started
-        architecting a libpkg library for handling routine package
-        management and have a prototype pkg_add that is three times faster
-        than the current version.</p>
-    <hr /><h2><a name="Network-interface-naming-changes" href="#Network-interface-naming-changes" id="Network-interface-naming-changes">Network interface naming changes</a></h2><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>At the end of October, the if_name and if_unit members of struct
-        ifnet were replaced with if_xname from NetBSD and if_dname and
-        if_dunit.  These represent the name of the interface and the
-        driver name and instance of the interface respectively.  Other then
-        breaking IPFilter for a few weeks due to the userland being on the
-        vendor branch, this change went quite well.  A few ports needed
-        minor changes, but otherwise nothing changed from the user
-        perspective.</p>
-
-      <p>The purpose of this change was the lay the groundwork for support
-        for network interface renaming and to allow the implementation of
-        more interesting pseudo interface cloning support.  An example of
-        interesting cloning support would be using "ifconfig fxp0.20
-        create" to create and configure a vlan interface on fxp0 that
-        handled frames marked with the tag 20.  Interface
-        renaming is being worked on in Perforce at the moment with a
-        working version expected for review soon.  Support for enhanced
-        device cloning is still in the planing stage.</p>
-    <hr /><h2><a name="Network-Subsystem-Locking-and-Performance" href="#Network-Subsystem-Locking-and-Performance" id="Network-Subsystem-Locking-and-Performance">Network Subsystem Locking and Performance</a></h2><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>The purpose of this project is to improve performance of the network
-        subsystem.  A major part of this work is to complete the locking of
-        the networking subsystem so that it no longer depends on the "Giant
-        lock" for proper operation.  Removing the use of Giant will improve
-        performance and permit multiple instances of the network stack to
-        operate concurrently on multiprocessor systems.</p>
-
-      <p>Locking of the network subsystem is largely complete.  Network
-        drivers, middleware layers (e.g. ipfw, dummynet, bridge, etc.), the
-        routing tables, IPv4, NFS, and sockets are locked and operating
-        without the use of Giant.  Much of this work was included in the 5.2
-        release, but not enabled by default.  The remaining work (mostly
-        locking of the socket layer) will be committed to CVS as soon as we
-        can resolve how to handle "legacy protocols" (i.e. those protocols
-        that are not locked).  The code can be obtained now from the Perforce
-        database.  A variety of test and production systems have been running
-        this code for several months without any obvious issues.</p>
-
-      <p>Performance analysis and tuning is ongoing. Initial results indicate
-        SMP performance is already better than 4.x systems but UP performance
-        is still lagging (though improved over -current). The removal of Giant
-        from the network subsystem has reduced contention on Giant and
-        highlighted performance bottlenecks in other parts of the system.</p>
-
-      <p>This work was supported by the FreeBSD Foundation.</p>
-    <hr /><h2><a name="Porting-OpenBSD's-pf" href="#Porting-OpenBSD's-pf" id="Porting-OpenBSD's-pf">Porting OpenBSD's pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pf4freebsd.love2party.net" title="http://pf4freebsd.love2party.net"></a></td><td>
-	    URL: <a href="http://pf4freebsd.love2party.net" title="">http://pf4freebsd.love2party.net</a></td></tr><tr><td><a href="http://www.benzedrine.cx/pf.html" title="http://www.benzedrine.cx/pf.html">PF homepage</a></td><td>
-	    URL: <a href="http://www.benzedrine.cx/pf.html" title="PF homepage">http://www.benzedrine.cx/pf.html</a></td></tr><tr><td><a href="http://openbsd.org/faq/pf/index.html" title="http://openbsd.org/faq/pf/index.html">PF FAQ</a></td><td>
-	    URL: <a href="http://openbsd.org/faq/pf/index.html" title="PF FAQ">http://openbsd.org/faq/pf/index.html</a></td></tr></table><p>
-	Contact:
-          Max
-          Laier
-         &lt;<a href="mailto:max@love2party.net">max@love2party.net</a>&gt;
-	<br />
-	Contact:
-          Pyun
-          YongHyeon
-         &lt;<a href="mailto:yongari@kt-is.co.kr">yongari@kt-is.co.kr</a>&gt;
-	</p>
-      <p>Much work has been invested into getting release 2.00 stable. It
-        provides the complete OpenBSD 3.4 function set, as well as fine
-        grained locking to work with a giant free network stack.</p>
-      <p>pf provides: IPv6 filtering and normalization, "syn-proxy"
-        to protect (web)server against SYN-floods, passive OS detection, fast
-        and modular address tables, source/policy routing, stateful filter and
-        normalization engine, structured rulesets via anchors and many many
-        more. Especially in connection with ALTQ, pf can help to harden
-        against various flood attacks and improve user experience.</p>
-      <p>New features from OpenBSD-Current like: state synchronization over wire
-        and enhanced support for cloned interfaces require patches to the
-        kernel.  We are trying to resolve this issue and start
-	OpenBSD-Current tracking again as soon as possible.</p>
-    <hr /><h2><a name="Publications-Page-Update" href="#Publications-Page-Update" id="Publications-Page-Update">Publications Page Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemon.li/freebsd/" title="http://www.daemon.li/freebsd/">Updated Publications Page</a></td><td>
-	    URL: <a href="http://www.daemon.li/freebsd/" title="Updated Publications Page">http://www.daemon.li/freebsd/</a></td></tr></table><p>
-	Contact:
-          Josef
-
-          El-Rayes
-         &lt;<a href="mailto:josef@daemon.li">josef@daemon.li</a>&gt;
-	</p>
-      <p>I did a xml/xslt conversion of the html files to make maintaining
-        of the page more comfortable.  I removed the cdsets, which might be
-        kept in CVS or some kind of archive for historical reasons.  The books
-        got an update, and were categorized in respect to the language they
-        are written in. As soon as I get my access on the cvs repository I
-        will commit the updates.  People are encouraged to add local FreeBSD
-        books, I missed, especially in the asian area.  Feel free to send me
-        links to books to add.</p>
-    <hr /><h2><a name="SGI-XFS-port-for-FreeBSD" href="#SGI-XFS-port-for-FreeBSD" id="SGI-XFS-port-for-FreeBSD">SGI XFS port for FreeBSD</a></h2><p>
-	Contact:
-          Alexander
-
-          Kabaev
-         &lt;<a href="mailto:kan@FreeBSD.org">kan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Russell
-
-          Cattelan
-         &lt;<a href="mailto:cattelan@thebarn.com">cattelan@thebarn.com</a>&gt;
-	</p>
-      <p>A project was started to revive a stalled effort to port SGI XFS
-        journaling filesystem to FreeBSD.  The project is based on Linux
-        development sources from SGI and is currently being kept in a
-        private Perforce repository. The work is progressing slowly due
-        to lack of free time.  At the moment we have XFS kernel module
-        which is capable of mounting XFS filesystems read-only, with a
-        panic or two happening infrequently, that need to be isolated and
-        fixed. Semi-working metadata updates with full transaction support
-        are there too, but will probably have to be rewritten to minimize
-        the amount of custom kernel changes required.</p>
-
-      <p>We seek volunteers to help with userland part of the port. Namely,
-        existing xfsprogs port needs to be cleaned up, incompletely ported
-        utilities brought into a working shape. xfs_dump/xfs_restore and
-        as much from xfstests suite as possible need to be ported too. We do
-        not need testers for now, so please to not ask for module sources
-        just yet.</p>
-
-    <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is progressing on SMPng on several different fronts.  Sam
-        Leffler and several other folks have been working on locking the
-        network stack as mentioned elsewhere in this update.  Several
-        infrastructure improvements have been made in the past few months
-        as well.</p>
-
-      <p>The low-level interrupt code for the i386 architecture has been
-        redesigned to allow for a runtime selection between different types
-        of interrupt controllers.  This work allows the Advanced Programmable
-        Interrupt Controllers (APICs) to be used instead of the AT 8259A PIC
-        without having to compile a separate kernel to do so.  It also allows
-        the APIC to be used in a UP kernel as well as on a UP box.  Together,
-        all these changes allow an SMP kernel to work on a UP box and thus
-        allowed SMP to be enabled in GENERIC as it already is on all of the
-        other supported architectures.  This work also reworked the APIC
-        support to correctly route PCI interrupts when using an APIC to
-        service device interrupts.  This work was also used to add SMP support
-        to the amd64 port.</p>
-
-      <p>A turnstile implementation was committed that implemented a queue
-        of threads blocked on a resource along with priority inheritance of
-        blocked threads to the owner of the resource.  Turnstiles were then
-        used to replace the thread queue built into each mutex object which
-        shrunk the size of each mutex as well as reduced the use of the
-        sched_lock spin mutex.</p>
-    <hr /><h2><a name="The-FreeBSD-Russian-Documentation-Project" href="#The-FreeBSD-Russian-Documentation-Project" id="The-FreeBSD-Russian-Documentation-Project">The FreeBSD Russian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ru/index.html" title="http://www.FreeBSD.org/ru/index.html">The FreeBSD Project [Russian]</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ru/index.html" title="The FreeBSD Project [Russian]">http://www.FreeBSD.org/ru/index.html</a></td></tr></table><p>
-	Contact:
-          Andrey
-
-          Zakhvatov
-         &lt;<a href="mailto:andy@FreeBSD.org">andy@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Russian Documentation Project aims to provide FreeBSD
-        Documentation translated to Russian.  Already done: FAQ, Porters
-        Handbook, WWW (partially synched with English version), some
-        articles.</p>
-
-      <p>We working at Handbook (and more docs) translation and synchronization
-        with English versions and need more translators (or financial aid  to
-        continue our work.  If you can help, please, contact us at
-        ru-cvs-committers@FreeBSD.org.ua (or andy@FreeBSD.org).</p>
-    <hr /><h2><a name="TrustedBSD-&quot;Security-Enhanced-BSD&quot;----FLASK/TE-Port" href="#TrustedBSD-&quot;Security-Enhanced-BSD&quot;----FLASK/TE-Port" id="TrustedBSD-&quot;Security-Enhanced-BSD&quot;----FLASK/TE-Port">TrustedBSD "Security-Enhanced BSD" -- FLASK/TE Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/sebsd.html" title="http://www.TrustedBSD.org/sebsd.html">TrustedBSD SEBSD page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/sebsd.html" title="TrustedBSD SEBSD page">http://www.TrustedBSD.org/sebsd.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Discussion Mailing List
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>TrustedBSD "Security-Enhanced BSD" (SEBSD) is a port of NSA's
-        SELinux FLASK security architecture, Type Enforcement (TE)
-        policy engine and language, and sample policy to FreeBSD using
-        the TrustedBSD MAC Framework.  SEBSD is available as a loadable
-        policy module for the MAC Framework, along with a set of
-        userspace extensions support security-extended labeling calls.
-        In most cases, existing MAC Framework functions provide the
-        necessary abstractions for SEBSD to plug in without SEBSD-specific
-        changes, but some extensions to the MAC Framework have been
-        required; these changes are developed in the SEBSD development
-        branch, then merged to the MAC branch as they mature, and then
-        to the FreeBSD development tree.</p>
-
-      <p>Unlike other MAC Framework policy modules, the SEBSD module
-        falls under the GPL, as it is derived from NSA's
-        implementation.  However, the eventual goal is to support
-        plugging SEBSD into a base FreeBSD install without any
-        modifications to FreeBSD itself.</p>
-
-      <p>TrustedBSD SEBSD development branch in Perforce integrated
-        to 5.2-RELEASE.  Other changes in the MAC branch, including
-        restructuring of MAC Framework files also integrated, and a
-        move to zone allocation for labels.  See the TrustedBSD MAC
-        Framework report for more detail on these and other MAC
-        changes that also affect the SEBSD work.</p>
-
-      <p>FreeBSD PTY code modified so that the MAC Framework and SEBSD
-        module can create pty's with the label of the process trying
-        to access them.  Improves compatibility with the SELinux
-        sample policy.  (Not yet merged)</p>
-
-      <p>SEBSD now loads its initial policy in the boot loader rather
-        than using a dummy policy until the root file system is
-        mounted, and then loading it using VFS operations.  This
-        avoids initial labeling and access control conditions during
-        the boot.</p>
-
-      <p>security_load_policy() now passes a memory buffer and length
-        to the kernel, permitting the policy reload mechanisms to
-        be shared between the early boot load and late reloads.  The
-        kernel SEBSD code now no longer needs to perform direct file
-        I/O relating to reading the policy.  checkpolicy now mmap's
-        the policy before making the system call.</p>
-
-      <p>SEBSD now enforces protections on System V IPC objects and
-        methods.  Shared memory, semaphores, and message queues are
-        labeled, and most operations are controlled.  The sample
-        policy has been updated.</p>
-
-      <p>The TrustedBSD MAC Framework now controls mount, umount, and
-        remount operations.  A new MAC system call, mac_get_fs() can
-        be used to query the mountpoint label.  lmount() system call
-        allows a mount label to be explicitly specified at mount
-        time.  The SEBSD policy module has been updated to reflect
-        this functionality, and sample TE policy has been updated.
-        (Not yet merged)</p>
-
-      <p>SEBSD now enforces protections on POSIX semaphores; the sample
-        policy has been updated to demonstrate how to label and control
-        sempahores.  This includes sample rules for PostgreSQL.</p>
-
-      <p>The SEBSD sample policy, policy syntax, and policy tools have
-        been updated to the SELinux code drop from August.  Bmake these
-        pieces so we don't need gmake.</p>
-
-      <p>Provide file ioctl() MAC Framework entry point and SEBSD
-        implementation.</p>
-
-      <p>A large number of sample policy tweaks and fixes.  The policy
-        has been updated to permit cron to operate properly.  It has
-        been updated for FreeBSD 5.2 changes, including dynamically
-        linked root.  Teach the sample policy about FreeBSD's sendmail
-        wrapper.</p>
-
-      <p>Adapt sysinstall and install process for SEBSD pieces.  Teach
-        sysinstall, newfs, et al, about multilabel file systems, install
-        SEBSD sample policy pieces, build policy.  Automatically load
-        the SEBSD module on first boot after install.</p>
-
-      <p>Allow "ls -Z" to print out labels without long format.</p>
-    <hr /><h2><a name="TrustedBSD-Access-Control-Lists-(ACLs)" href="#TrustedBSD-Access-Control-Lists-(ACLs)" id="TrustedBSD-Access-Control-Lists-(ACLs)">TrustedBSD Access Control Lists (ACLs)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.trustedbsd.org/components.html#acls" title="http://www.trustedbsd.org/components.html#acls">TrustedBSD ACLs page</a></td><td>
-	    URL: <a href="http://www.trustedbsd.org/components.html#acls" title="TrustedBSD ACLs page">http://www.trustedbsd.org/components.html#acls</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Discussion Mailing List
-
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>TrustedBSD Access Control Lists (ACLs) provide extended
-        discretionary access control support for the UFS and UFS2
-        file systems on FreeBSD.  They implement POSIX.1e ACLs with
-        some extensions, and meet the Common Criteria CAPP
-        requirements.  Most ACL-related work is complete, with
-        remaining tasks associated with userspace integration, third
-        party applications, and compatibility</p>
-
-      <p>Prototyped Solaris/Linux semantics for combining ACLs and
-        the umask: if an default ACL mask is defined, substitute that
-        mask for the umask, permitting ACLs to override umasks.  (Not
-        merged)</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.trustedbsd.org/components.html#audit" title="http://www.trustedbsd.org/components.html#audit">TrustedBSD Audit Page</a></td><td>
-	    URL: <a href="http://www.trustedbsd.org/components.html#audit" title="TrustedBSD Audit Page">http://www.trustedbsd.org/components.html#audit</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Audit Discussion List
-         &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-
-      <p>The TrustedBSD Project is producing an implementation of CAPP
-        compliant Audit support for use with FreeBSD.  Little progress
-        was made on this implementation between October and December
-        other than an update to the existing development tree.  However,
-        in January, work began on porting the Darwin Audit
-        implementation to FreeBSD.  Details on this work will appear in
-        the next report; more information is available on the TrustedBSD
-        audit discussion list.  Perforce messages may be seen on the
-        trustedbsd-cvs mailing list.</p>
-
-    <hr /><h2><a name="TrustedBSD-Documentation" href="#TrustedBSD-Documentation" id="TrustedBSD-Documentation">TrustedBSD Documentation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/docs.html" title="http://www.TrustedBSD.org/docs.html">TrustedBSD Documentation Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/docs.html" title="TrustedBSD Documentation Page">http://www.TrustedBSD.org/docs.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Discussion Mailing List
-
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project is implementing many new features
-        for the FreeBSD Project.  It also provides documentation for
-        users, administrators, and developers.</p>
-
-      <p>mac_support.4 added -- documents TrustedBSD MAC Framework
-        feature compatibility.  See also the MAC Framework report.</p>
-
-      <p>FreeBSD security architecture updated and corrections/additions
-        made.</p>
-
-      <p>A variety of documentation updates relating to API changes,
-        including the socket-related API changes in libc/mac(3).</p>
-    <hr /><h2><a name="TrustedBSD-Mandatory-Access-Control-(MAC)" href="#TrustedBSD-Mandatory-Access-Control-(MAC)" id="TrustedBSD-Mandatory-Access-Control-(MAC)">TrustedBSD Mandatory Access Control (MAC)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.trustedbsd.org/mac.html" title="http://www.trustedbsd.org/mac.html">TrustedBSD MAC page</a></td><td>
-	    URL: <a href="http://www.trustedbsd.org/mac.html" title="TrustedBSD MAC page">http://www.trustedbsd.org/mac.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Discussion Mailing List
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Mandatory Access Control (MAC) Framework
-        permits the FreeBSD kernel and userspace access control
-        policies to be adapted at compile-time, boot-time, or
-        run-time.  The MAC Framework provides common infrastructure
-        components, such as policy-agnostic labeling, making it
-        possible to easily development and distribute new access
-        control policy modules.  Sample modules include Biba, MLS,
-        and Type Enforcement, as well as a variety of system
-        hardening policies.</p>
-
-      <p>TrustedBSD MAC development branch in Perforce integrated
-        to 5.2-RELEASE.</p>
-
-      <p>The TrustedBSD MAC Framework now enforces protections on System
-        V IPC objects and methods.  Shared memory, semaphores, and
-        message queues are labeled, and most operations are controlled.
-        The Biba, MLS, Test, and Stub policies have been updated for
-        System V IPC.  (Not yet merged)</p>
-
-      <p>The TrustedBSD MAC Framework now enforces protections on POSIX
-        semaphore objects and methods.  The Biba, MLS, Test, and Stub
-        policies have been updated.  (Not yet merged)</p>
-
-      <p>The TrustedBSD MAC Framework's central kernel implementation
-        previously existed in one large file, src/sys/kern/kern_mac.c.
-        It is now broken out into a series of by-service files in
-        src/sys/security/mac.  src/sys/security/mac/mac_internal.h
-        specifies APIs, structures, and variables used internally
-        across the different parts of the framework.  System calls
-        and registration still occur in kern_mac.c.  This permits
-        more easy maintenance of locally added object types.  (Merged)</p>
-
-      <p>Break out mac_policy_list into two different lists, one to
-        hold "static" policy modules -- ones loaded prior to kernel
-        initialization, and that may not be loaded, and one for
-        "dynamic" policy modules -- that are either loaded later in
-        boot, or may be unloaded.  Perform less synchronization when
-        using static modules only, reducing overhead for entering
-        the framework when not using dynamic modules.  (Merged)</p>
-
-      <p>Introduced a kernel option, MAC_STATIC, which permits only
-        statically registered policy modules to be loaded at boot
-        or compiled into the kernel.  When running with MAC_STATIC,
-        no internal synchronization is required in the MAC Framework,
-        lowering the cost of MAC Framework entry points.  (Not yet
-        merged)</p>
-
-      <p>Make mac.h userland API definition C++-happy.  (Merged)</p>
-
-      <p>Created mac_support.4, a declaration of what kernel and
-        userspace features are (and aren't) supported with MAC.
-        (Not yet merged)</p>
-
-      <p>Stale SEBSD module deleted from MAC branch; SEBSD module will
-        solely be developed in the SEBSD branch from now on.  See
-        the TrustedBSD SEBSD report for more detail.</p>
-
-      <p>Use only pointers to 'struct label' in various kernel objects
-        outside the MAC Framework, and use a zone allocator to allocate
-        label storage.  This permits label structures to have their
-        size changed more easily without changing the normal kernel
-        ABI.  This also lowers the non-MAC memory overhead for base
-        kernel structures.  This also simplifies handling and storage
-        of labels in some of the edge cases where labels are exposed
-        outside of the Framework, such as in execve().  Include files
-        outside of the Framework are substantially simplified and now
-        frequently no longer require _label.h.  (Merged)</p>
-
-      <p>Giant pushed down into the MAC Framework in a number of MAC
-        related system calls, as it is not required for almost all
-        of the MAC Framework.  The exceptions are areas where the
-        Framework interacts with pieces of the kernel still covered
-        by MAC and relies on Giant to protect label storage in those
-        structures.  However, even in those cases, we can push Giant
-        in quite a bit past label internalization/externalization/
-        storage allocation/deallocation.  This substantially simplifies
-        file descriptor-based MAC label system calls.  (Merged)</p>
-
-      <p>Remove unneeded mpo_destroy methods for Biba, LOMAC, and MLS
-        since they cannot be unloaded.  (Merged)</p>
-
-      <p>Biba and MLS now use UMA zones for label allocation, which
-        improves storage efficiency and enhances performance.  (Merged)</p>
-
-      <p>Bug fix for mac_prepare_type() to better support arbitrary
-        object label definitions in /etc/mac.conf.  (Merged)</p>
-
-      <p>Labels added to 'struct inpcb', which represents TCP and UDP
-        connections at the network layer.  These labels cache socket
-        labels at the application layer so that the labels may be
-        accessed without application layer socket locks.  When a label
-        is changed on the socket, it is pushed down to the network
-        layer through additional entry points.  Biba, MLS policies
-        updated to reflect this change.  (Merged)</p>
-
-      <p>SO_PEERLABEL socket option fixed so that peer socket labels
-        may be retrieved.  (Merged)</p>
-
-      <p>mac_get_fd() learns to retrieve local socket labels, providing
-        a simpler API than SO_LABEL with getsockopt().  mac_set_fd()
-        learns about local socket labels, providing a simpler API than
-        SO_LABEL with setsockopt().  This also improves the ABI by not
-        embedding a struct label in the socket option arguments, instead
-        using the copyin/copyout routine for labels used for other object
-        types.  (Merged)</p>
-
-      <p>Some function names simplified relating to socket options.
-        (Merged)</p>
-
-      <p>Library call mac_get_peer() implemented in terms of getsockopt()
-        with SO_PEERLABEL to improve API/ABI for networked applications
-        that speak MAC.  (Merged)</p>
-
-      <p>mac_create_cred() renamed to mac_cred_copy(), similar to other
-        label copying methods, allowing policies to implement all the
-        label copying method with a single function, if desired.  This
-        also provides a better semantic match for the crdup() behavior.
-        (Merged)</p>
-
-      <p>Support "id -M", similar to Trusted IRIX.  (Not yet merged)</p>
-
-      <p>TCP now uses the inpcb label when responding in timed wait,
-        avoiding reaching up to the socket layer for label information
-        in otherwise network-centric code.</p>
-
-      <p>Numerous bug fixes, including assertion fixes in the MAC
-        test policy relating to execution and relabeling.  (Merged)</p>
-    <hr /><h2><a name="Wireless-Networking-Support" href="#Wireless-Networking-Support" id="Wireless-Networking-Support">Wireless Networking Support</a></h2><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work to merge the NetBSD and MADWIFI code bases is almost complete.
-        This brings in new features and improves sharing which will enable
-        future development.  Support was added for 802.1x client
-        authentication (using the open1x xsupplicant program) and for shared
-        key authentication (both client and AP) which improves interopability
-        with systems like OS X. The awi driver was updated to use the common
-        802.11 layer and the Atheros driver received extensive work to support
-        hardware multi-rate retry.  Kismet now works with the
-        device-independent radiotap capture format.  All of this work is still
-        in Perforce but should be committed to CVS soon.  </p>
-
-      <p>Work has begun on full 802.1x and WPA support.</p>
-
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2004-01-2004-02.html b/website/content/en/status/report-2004-01-2004-02.html
deleted file mode 100644
index 2feb6f4139..0000000000
--- a/website/content/en/status/report-2004-01-2004-02.html
+++ /dev/null
@@ -1,850 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction:</h1><p>2004 started with another exciting two months for the project.
-      FreeBSD 5.2 was released in early January and then quickly followed
-      in February with the 5.2.1 bug-fix release.  Looking forward, we
-      are expecting a late-April release date for FreeBSD 4.10, and
-      mid-summer date for FreeBSD 5.3.  And don't forget to support the
-      FreeBSD vendors and developers by buying a copy of the latest CD
-      or DVD sets.</p><p>Thanks,</p><p>Scott Long</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-      Bluetooth stack for FreeBSD (Netgraph implementation)
-    </a></li><li><a href="#Automatic-sizing-of-TCP-send-buffers">Automatic sizing of TCP send buffers</a></li><li><a href="#Compile-FreeBSD-with-Intels-C-compiler-(icc)">Compile FreeBSD with Intels C compiler (icc)</a></li><li><a href="#Disk-and-device-I/O">Disk and device I/O</a></li><li><a href="#FreeBSD-GNOME-Project-Report">FreeBSD GNOME Project Report</a></li><li><a href="#FreeBSD-Package-Grid">FreeBSD Package Grid</a></li><li><a href="#FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></li><li><a href="#FreeBSD/arm-Status-Report">FreeBSD/arm Status Report</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#FreeSBIE">FreeSBIE</a></li><li><a href="#kgi4BSD">kgi4BSD</a></li><li><a href="#libarchive/bsdtar">libarchive/bsdtar</a></li><li><a href="#Move-ARP-out-of-routing-table">Move ARP out of routing table</a></li><li><a href="#NanoBSD">NanoBSD</a></li><li><a href="#Network-interface-naming-changes">Network interface naming changes</a></li><li><a href="#Network-Stack-Locking">Network Stack Locking</a></li><li><a href="#Porting-OpenBSD's-pf">Porting OpenBSD's pf</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#SGI-XFS-port-for-FreeBSD">SGI XFS port for FreeBSD</a></li><li><a href="#Testbed-for-testing-and-qualification-of-TCP-performance">Testbed for testing and qualification of TCP performance</a></li><li><a href="#The-FreeBSD-Dutch-Documentation-Project.">The FreeBSD Dutch Documentation Project.</a></li><li><a href="#The-FreeBSD-Simplified-Chinese-Project">The FreeBSD Simplified Chinese Project</a></li><li><a href="#Verify-source-reachability-option-for-ipfw2">Verify source reachability option for ipfw2</a></li><li><a href="#vinum-+-GEOM">vinum + GEOM</a></li><li><a href="#Weekly-cvs-src-summaries">Weekly cvs-src summaries</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-      Bluetooth stack for FreeBSD (Netgraph implementation)
-    </a></h2><p>
-	Contact:
-          Maksim
-          Yevmenkin
-         &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-      <p>Not much to report. Bluetooth Service Discovery Procotol daemon
-        sdpd was integrated with existing Bluetooth utilities. From now
-        on users should not use GNU sdpd (Linux BlueZ port).</p>
-      <p>Bluetooth HID profile implementation is almost complete. Thanks
-        to Matt Peterson &lt; matt at peterson dot org &gt; for giving me
-        Bluetooth keyboard and mouse for development.</p>
-    <hr /><h2><a name="Automatic-sizing-of-TCP-send-buffers" href="#Automatic-sizing-of-TCP-send-buffers" id="Automatic-sizing-of-TCP-send-buffers">Automatic sizing of TCP send buffers</a></h2><p>
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The current TCP send and receive buffers are static and set to a
-        conservative value to preserve kernel memory.  This is sub-optimal
-        for connections with a high bandwidth*delay product because the
-        size of the TCP send buffer determines how big the send window
-        can get.  For high bandwidth trans-continental links this seriously
-        limits the maximum transfer speed per TCP connection.  For example
-        a 170ms RTT and a 32kB send buffer limit the speed to approximately
-        1.5Mbit per second even thought you might have a 10Mbit pipe.</p>
-      <p>This project makes the TCP send buffer to automatically adapt to
-        the optimal buffer size for maximal link usage.  In the case
-        above this would be a buffer of approximately 220kB.  The main
-        challenge is to have a stable and reliable measurement of the link
-        parameters and manage the kernel memory properly and in a fair way.
-        We don't want to have a few connections to monopolize all available
-        socket buffer space and many edge cases have to be considered.  The
-        first implementation will be tuned conservatively but even that
-        will provide significantly better performance than the static
-        buffers currently.  Work on this project is already in
-        progress.</p>
-    <hr /><h2><a name="Compile-FreeBSD-with-Intels-C-compiler-(icc)" href="#Compile-FreeBSD-with-Intels-C-compiler-(icc)" id="Compile-FreeBSD-with-Intels-C-compiler-(icc)">Compile FreeBSD with Intels C compiler (icc)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.Leidinger.net/FreeBSD/" title="http://www.Leidinger.net/FreeBSD/">Some patches.</a></td><td>
-	    URL: <a href="http://www.Leidinger.net/FreeBSD/" title="Some patches.">http://www.Leidinger.net/FreeBSD/</a></td></tr></table><p>
-	Contact:
-          Alexander
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>If nothing bad happened, the icc patches got committed around
-        the date of the deadline for submissions of this report. Please
-        search the archives of -current and/or cvs-all for more
-        information.</p>
-
-      <p>The next steps in this project are to
-        <ul>
-          <li>fix the kernel to also run without problems when compiled
-            with icc v8</li>
-          <li>fix the kernel if some problems surface after more people
-            give it a try</li>
-          <li>get some ports to compile with icc</li>
-        </ul>
-      </p>
-    <hr /><h2><a name="Disk-and-device-I/O" href="#Disk-and-device-I/O" id="Disk-and-device-I/O">Disk and device I/O</a></h2><p>
-	Contact:
-          Poul-Henning
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the overall area of disk and device I/O, a significant
-        milestone was reached with the implementation of proper
-        reference counting on dev_t.  We are now able to properly
-        allocate and free dev_t.  Cloning device drivers also had
-        the job made easier for them with the addition of the unit
-        number management routines.</p>
-      <p>It is not quite decided which will be the next step in
-        the quest for a truly SMPng I/O subsystem, but a leading
-        candidate is to implement the device-access vnode bypass
-        to get more concurrency in the system:  Instead of taking
-        the tour through the vnodes for each i/o operation on a
-        device we will go directly from the file descriptor layer to
-        DEVFS/SPECFS.  In addition to Giant-less disk I/O,
-        this should enable us to pull the entire tty subsystem
-        and the PTY driver out from under Giant and we expect that
-        to improve the "snappiness" of the system measurably.</p>
-    <hr /><h2><a name="FreeBSD-GNOME-Project-Report" href="#FreeBSD-GNOME-Project-Report" id="FreeBSD-GNOME-Project-Report">FreeBSD GNOME Project Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Site.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project Site.">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-          FreeBSD
-          GNOME Team
-         &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>It has been a year since our last status report, but we
-        haven't slowed down. Since the last report, Alexander
-        Nedotsukov (bland) and Pav Lucistnik (pav) have joined the
-        FreeBSD GNOME team. GNOME 2.4 was released back in September
-        2003, followed by 2.4.1 and 2.4.2. We are actively working on
-        getting GNOME 2.6.0 out the door at the end of March. GNOME 2.6
-        Beta releases can be obtained via the project URL above.</p>
-
-      <p>To help make GNOME 2.6.0 our best release to date, we have
-        created a script to automate the upgrade from GNOME 2.4. We
-        also have a new GNOME
-        <a href="http://www.marcuscom.com/tinderbox/" shape="rect">package build
-        server</a>
-        that builds and serves i386 packages for all supported FreeBSD
-        releases. We plan on having the GNOME 2.6.0 packages available
-        the moment 2.6.0 hits the ports tree.</p>
-
-      <p>Included in the release of GNOME 2.6 is GTK+ 2.4, the next
-        installment in the GTK+ 2 series. Because GTK+ 2 has become
-        very stable over the past few years, the FreeBSD GNOME Team is
-        pushing for GTK+ 2 support to be included by default in all
-        applications that support it. This has already been done with
-        Mozilla, Firefox, and Thunderbird. A complete GNOME Desktop and
-        application environment can already be built using only GTK+ 2.
-        The ultimate goal is to phase GTK+ 1 out of the ports tree.</p>
-    <hr /><h2><a name="FreeBSD-Package-Grid" href="#FreeBSD-Package-Grid" id="FreeBSD-Package-Grid">FreeBSD Package Grid</a></h2><p>
-	Contact:
-          Kris
-          Kennaway
-         &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-
-      <p>Distributed package builds are currently done using a set of
-        home-grown shell scripts for managing, scheduling and
-        dispatching of package builds on the client machines.  This has
-        been sufficient for our needs in the past, but has a number of
-        significant shortcomings that limit future growth.  I am
-        rewriting the package build scripts to work on top of Sun
-        GridEngine (ports/sysutils/sge), as a client application of a
-        "FreeBSD package grid".  Some of the design goals for the new
-        system are:</p>
-
-      <ul>
-        <li>Better robustness against machine failure, and more efficient
-          scheduling of build jobs</li>
-        <li>Support for remote build machines, to make better use of machine
-          resources and clusters that are not on the same LAN as the
-          build master</li>
-        <li>Ability for other committers to submit port build jobs to the
-          system, for testing of changes, new ports, etc.</li>
-      </ul>
-
-    <hr /><h2><a name="FreeBSD-ports-monitoring-system" href="#FreeBSD-ports-monitoring-system" id="FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://portsmon.firepipe.net/index.html" title="http://portsmon.firepipe.net/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.firepipe.net/index.html" title="FreeBSD ports monitoring system">http://portsmon.firepipe.net/index.html</a></td></tr></table><p>
-	Contact:
-          Mark
-          Linimon
-         &lt;<a href="mailto:linimon_at_lonesome_dot_com">linimon_at_lonesome_dot_com</a>&gt;
-	</p>
-      <p>Thanks to the loan of a box by Will Andrews, the system has
-        been moved into production.  The previous installation
-        at lonesome.com now refers you to the new system.  As part of
-        the installation, a preliminary
-        <a href="http://portsmon.firepipe.net/faq.html" shape="rect">FAQ</a> was
-        added.</p>
-      <p>The database is updated once per hour.</p>
-      <p>New reports available include ones about ports marked DEPRECATED,
-        since that function has now been incorporated into bsd.port.mk.
-       (The author hopes that this will allow the port deprecation process
-       to be much more visible to the general FreeBSD user community.)  In
-       addition, a report for ports marked FORBIDDEN was added (the code
-       was essentially the same).</p>
-      <p>The next topic of interest is to try to identify ports which are
-        slave ports because the status of these ports is not currently
-        being updated automatically.  This problem also affects
-        FreshPorts.  PR ports/63683 is an attempt to address this problem.
-        Also, preliminary work has been done on creating some graphs and
-        charts for various statistics, and in creating a tool to browse
-        port dependencies for the entire ports tree.</p>
-      <p>Some general observations about the trends in ports PRs can be
-        made:
-        <ul>
-          <li>In the past 6 months, the amount of time to get ports PRs
-            committed has dropped dramatically.  (This is especially
-            true of PRs for new ports.)</li>
-          <li>The queue of PRs for existing ports that are unmaintained
-            has similarly been trimmed.  Both of these two items are due
-            in large part to a few very active committers (how do they
-            ever get their "real" work done?)  Thanks, guys, you know who
-            you are.</li>
-          <li>There is still a fairly high number of PRs (~400/~750) which
-            apply to existing ports, and have been assigned to a FreeBSD
-            committer.  This represents around 370 individual ports. We
-            seem to have a much harder time getting these numbers to go
-            down; basically, we just hold our own most weeks.  This is
-            somewhat disappointing.</li>
-          <li>The number of ports marked BROKEN has jumped dramatically,
-            currently standing at over 250 (for i386-current).  This
-            represents less a sudden problem as it does Kris' effort to
-            bring existing brokenness to people's attention -- thus, a
-            much larger percentage of ports with build errors are now
-            labeled as BROKEN.</li>
-          <li>Approximately two-thirds of the port build errors are still
-            due to compilation problems, primarily from the gcc3.3 import.
-            Another 10% fail to install correctly.  The reasons for the
-            others are more varied.</li>
-        </ul>
-      </p>
-    <hr /><h2><a name="FreeBSD/arm-Status-Report" href="#FreeBSD/arm-Status-Report" id="FreeBSD/arm-Status-Report">FreeBSD/arm Status Report</a></h2><p>
-	Contact:
-          Olivier
-          Houchard
-         &lt;<a href="mailto:cognet@FreeBSD.org">cognet@FreeBSD.org</a>&gt;
-	</p>
-      <p>Development goes reasonably fast, right now it boots single user.
-        It is still very simics-centric, and it deserves a huge cleanup
-        and a few bug fixes, but there's already a decent amount of code
-        to work with, mostly taken from NetBSD. I now plan to work on real
-        hardware support (as soon as I can get some), to get the missing
-        userland bits (mainly rtld and the pthread libs) so that I can
-        build a full world.</p>
-    <hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/platforms/ia64/index.html" title="http://www.FreeBSD.org/platforms/ia64/index.html">Home page.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/platforms/ia64/index.html" title="Home page.">http://www.FreeBSD.org/platforms/ia64/index.html</a></td></tr></table><p>
-	Contact:
-          Marcel
-          Moolenaar
-         &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on the PMAP overhaul has been put into gear. A lot of issues
-        will be addressed, including support for sparse physical memory
-        and of course SMP. Performance will be addressed to the extend
-        possible, but functionality has priority. The redesign will lay
-        the foundation for NUMA support where possible. An example of this
-        is limiting TLB shootdowns to processors that actually have or had
-        TLBs belonging to the PMAP loaded. Of course, without NUMA
-        hardware the implementation of NUMA support is quite limited.</p>
-    <hr /><h2><a name="FreeSBIE" href="#FreeSBIE" id="FreeSBIE">FreeSBIE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freesbie.org" title="http://www.freesbie.org">FreeSBIE Home</a></td><td>
-	    URL: <a href="http://www.freesbie.org" title="FreeSBIE Home">http://www.freesbie.org</a></td></tr><tr><td><a href="mailto:freesbie@gufi.org" title="mailto:freesbie@gufi.org">FreeSBIE Mailing List</a></td><td>
-	    URL: <a href="mailto:freesbie@gufi.org" title="FreeSBIE Mailing List">mailto:freesbie@gufi.org</a></td></tr><tr><td><a href="http://www.freesbie.org/?section=mirror-en" title="http://www.freesbie.org/?section=mirror-en">FreeSBIE Mirror List</a></td><td>
-	    URL: <a href="http://www.freesbie.org/?section=mirror-en" title="FreeSBIE Mirror List">http://www.freesbie.org/?section=mirror-en</a></td></tr></table><p>
-	Contact:
-          FreeSBIE
-          Staff
-         &lt;<a href="mailto:staff@FreeSBIE.org">staff@FreeSBIE.org</a>&gt;
-	</p>
-      <p>The FreeSBIE Project aims to develop a set of scripts that allow
-        anyone to create their own FreeBSD Bootable Cdrom, with their own
-        set of installed packages.  The Project releases an ISO builded
-        with FreeSBIE scripts, to show what they can do. On Sunday 29
-        February 2004, FreeSBIE 1.0 was released and it had a great
-        success, as there were post on Slashdot.org, OSnews, DaemonNews
-        and BSDForums. Thanks to the huge amount of feedback they got,
-        FreeSBIE Developers are now developing new features such as
-        support for archs different from i386. Website redesign is on the
-        way too.</p>
-    <hr /><h2><a name="kgi4BSD" href="#kgi4BSD" id="kgi4BSD">kgi4BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="http://www.FreeBSD.org/~nsouch/kgi4BSD">Project URL</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="Project URL">http://www.FreeBSD.org/~nsouch/kgi4BSD</a></td></tr></table><p>
-	Contact:
-          Nicholas
-          Souchu
-         &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-      <p>Move to Perforce is done. I spent some time on building a
-        common compilation tree with Linux: until now drivers were
-        build in a FreeBSD makefile tree, not compatible with Linux.</p>
-
-      <p>The next priorities are ANSI support and keymaps in the
-        KGC Kernel Graphic Console system.</p>
-    <hr /><h2><a name="libarchive/bsdtar" href="#libarchive/bsdtar" id="libarchive/bsdtar">libarchive/bsdtar</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~kientzle/" title="http://people.FreeBSD.org/~kientzle/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~kientzle/" title="">http://people.FreeBSD.org/~kientzle/</a></td></tr></table><p>
-	Contact:
-          Tim
-          Kientzle
-         &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	</p>
-      <p>libarchive, with complete documentation, has been committed to
-        -CURRENT.  bsdtar should follow soon.  For a few months, gtar
-        and bsdtar will both be available in the base system.  Once
-        bsdtar is in the tree, I hope to resume work on libpkg and my
-        pkg_add rewrite.</p>
-
-      <p>Note that bsdtar is not an exact replacement for gtar: it does
-        some things better (reads/writes standard formats, archive ACLs
-        and file flags, detects format and compression automatically),
-        some things worse (does not handle multi-volume archives or
-        sparse files) and a few things just different (writes POSIX-format
-        archives by default, not GNU-format).  The command lines are
-        sufficiently similar that most users should have no problems
-        with the transition.  However, people who rely on peculiar
-        options or capabilities of gtar may have to look to ports.</p>
-    <hr /><h2><a name="Move-ARP-out-of-routing-table" href="#Move-ARP-out-of-routing-table" id="Move-ARP-out-of-routing-table">Move ARP out of routing table</a></h2><p>
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ARP IP address to MAC address mapping does not belong into
-        the routing table (FIB) as it is currently done.  This will move
-        it to its own hash based structure which will be instantiated
-        per each 802.1 broadcast domain.  With this change it is possible
-        to have more than one interface in the same IP subnet and layer 2
-        broadcast domain.  The ARP handling and the routing table will be
-        quite a bit simplified afterwards.  As an additional benefit full
-        MAC address based accosting will be provided.  Work on this
-        project is already in progress.</p>
-    <hr /><h2><a name="NanoBSD" href="#NanoBSD" id="NanoBSD">NanoBSD</a></h2><p>
-	Contact:
-          Poul-Henning
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>NanoBSD, src/tools/tools/nanobsd, is a tool for stuffing FreeBSD
-        onto small disk media (like CompactFlash) for embedded
-        applications.  The disk image is built with three partitions, two
-        for software images and one for configuration files.  Having two
-        software partitions means that new software can be uploaded to the
-        non-active partition while running off the active partition.</p>
-      <p> The first really public version has been committed and many
-        suggestions and offers of patches have started pouring in.</p>
-    <hr /><h2><a name="Network-interface-naming-changes" href="#Network-interface-naming-changes" id="Network-interface-naming-changes">Network interface naming changes</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>The first actual feature related to the if_xname conversion was
-        committed in early February.  Network interfaces can now be
-        renamed with "ifconfig &lt;if&gt; name &lt;newname&gt;".</p>
-
-      <p>Work is slowly progressing on a new network interface cloning API
-        to enable interesting cloners like auto-configurating vlans.
-        This work is taking place in the perforce repository under:
-        //depot/user/brooks/xname/...</p>
-    <hr /><h2><a name="Network-Stack-Locking" href="#Network-Stack-Locking" id="Network-Stack-Locking">Network Stack Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Sam
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Robert
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is aimed at converting the FreeBSD network stack from
-        running under the single Giant kernel lock to permitting it to
-        run in a fully parallel manner on multiple CPUs (i.e., a fully
-        threaded network stack).  This will improve performance/latency
-        through reentrancy and preemption on single-processor machines,
-        and also on multi-processor machines by permitting real
-        parallelism in the processing of network traffic.  As of FreeBSD
-        5.2, it was possible to run low level network functions, as well
-        as the IP filtering and forwarding plane, without the Giant lock,
-        as well as "process to completion" in the interrupt handler.</p>
-
-      <p>Work continues to improve the maturity and completeness of
-        the locking (and performance) of the network stack for 5.3. The
-        network stack locking development branch has been updated to the
-        latest CVS HEAD, tracking a variety of FreeBSD changes, including
-        tracking and driving changes in the interface and device cloning
-        APIs, push-down and fixes to locking in the Berkeley Packet
-        Filter, consistency improvements in allocation flags for network
-        objects, diagnosis of excessive acquisition of Giant in various
-        system callouts and timeouts, removal of Giant from several
-        system callouts, "const"-ification of a number of global
-        variables in the network stack (IPv4, IPv6, elsewhere) as part of
-        ananalysis of locking requirements, fine-grain locking of a
-        number of pseudo-interfaces (disc, loopback, faith, stf, gif, tap,
-        tun), IP encapsulation and tunneling, initial review and locking
-        of parts of PPP and SLIP, experimentation with PCB assertions on
-        IPv6, additional socket locking assertions, graphing of the FreeBSD
-        sockets layer to support locking analysis, merging of theMT_TAG to
-        m_tag conversion to improve the ability to queue packets, moving
-        of the debug.mpsafenet tunable to controlling Giant over the
-        forwarding plane to Giant over the entire stack("dual-mode" to
-        support non-MPSAFE protocols), adaption of existing network lock
-        assertions to also assert Giant when running non-MPSAFE, analysis
-        of high cost of select() locking, improved locking and
-        synchronization annotations, TCP callouts run MPSAFE, logtimeout()
-        runs MPSAFE, uma_timeout() runs MPSAFE, callout sampling
-        instrumentation, loadav() runs MPSAFE, AppleTalk locking begun:
-        AARP locked down and DDP analysis, rawcb list locked, locking
-        analysis of mrouter and IP ID code, IGMP locked, IPv6 analysis
-        begun, IPX/SPX analysis begun, PPP timeouts converted to callouts,
-        Netgraph analysis begun.  Many of these changes have not yet been
-        merged to the main FreeBSDtree, but this is a work in progress.</p>
-
-      <p>In related work on Pipe IPC (not quite network stack locking),
-        substantial time was invested in diagnosing an increase in the
-        cost of pipe allocation since FreeBSD 4.x, as well as coalescing
-        the several allocations needed to create a pipe, as well as moving
-        to slab allocation so as to amortize the cost of pipe
-        initialization.  Future work here will include caching the VM
-        structures supporting pipe buffers.</p>
-
-      <p>Recent contributors include Robert Watson, Sam Leffler, MaxLaier,
-        Maurycy Pawlowski-Wieronski, Brooks Davis, and many others who are
-        omitted here only by accident.</p>
-    <hr /><h2><a name="Porting-OpenBSD's-pf" href="#Porting-OpenBSD's-pf" id="Porting-OpenBSD's-pf">Porting OpenBSD's pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pf4freebsd.love2party.net/" title="http://pf4freebsd.love2party.net/"></a></td><td>
-	    URL: <a href="http://pf4freebsd.love2party.net/" title="">http://pf4freebsd.love2party.net/</a></td></tr><tr><td><a href="http://www.benzedrine.cx/pf.html" title="http://www.benzedrine.cx/pf.html">PF homepage</a></td><td>
-	    URL: <a href="http://www.benzedrine.cx/pf.html" title="PF homepage">http://www.benzedrine.cx/pf.html</a></td></tr><tr><td><a href="http://openbsd.org/faq/pf/index.html" title="http://openbsd.org/faq/pf/index.html">PF FAQ</a></td><td>
-	    URL: <a href="http://openbsd.org/faq/pf/index.html" title="PF FAQ">http://openbsd.org/faq/pf/index.html</a></td></tr><tr><td><a href="http://www.rofug.ro/projects/freebsd-altq/" title="http://www.rofug.ro/projects/freebsd-altq/">ALTQ</a></td><td>
-	    URL: <a href="http://www.rofug.ro/projects/freebsd-altq/" title="ALTQ">http://www.rofug.ro/projects/freebsd-altq/</a></td></tr></table><p>
-	Contact:
-          Max
-          Laier
-         &lt;<a href="mailto:max@love2party.net">max@love2party.net</a>&gt;
-	<br />
-	Contact:
-          Pyun
-          YongHyeon
-         &lt;<a href="mailto:yongari@kt-is.co.kr">yongari@kt-is.co.kr</a>&gt;
-	</p>
-      <p>The sources were imported from OpenBSD 3.4R and patched with
-        diffs obtained from the port. Since March the 8th it is linked
-        to the build and install. There is some more work to be done in
-        order make pf a home inside the tree, but the biggest hunk of
-        work was lifted during the past two month.</p>
-      <p>OpenBSD 3.5 is scheduled for early May, so we might see an update
-        before 5.3R. Work towards integration of the - often requested
-        - ALTQ framework is in progress also, though it is not yet clear
-        how well it goes along with the ongoing work towards a giant free
-        net stack.</p>
-    <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-          Peter
-          Grehan
-         &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>After a slow time at the end of last year due to a disk crash,
-        the project is moving along rapidly. The loader is fully
-        functional with Forth support. Syscons has been integrated.
-        New Powerbook models are supported. Work is starting on a
-        G5 port.</p>
-
-      <p>There's still lots to do, so as usual volunteers are most
-        welcome.</p>
-    <hr /><h2><a name="SGI-XFS-port-for-FreeBSD" href="#SGI-XFS-port-for-FreeBSD" id="SGI-XFS-port-for-FreeBSD">SGI XFS port for FreeBSD</a></h2><p>
-	Contact:
-          Alexander
-          Kabaev
-         &lt;<a href="mailto:kan@FreeBSD.org">kan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Russell
-          Cattelan
-         &lt;<a href="mailto:cattelan@thebarn.com">cattelan@thebarn.com</a>&gt;
-	</p>
-      <p>Not much has changed since last report was submitted. The
-        read-only access XFS volumes is quite stable now. The work is
-        underway to rewrite xfs_buf layer to minimize local changes
-        intrusiveness. Initial attempt to make XFS code to compile and
-        run on amd64 is in progress too.</p>
-      <p>We really need a care-taker for our userland tools.</p>
-    <hr /><h2><a name="Testbed-for-testing-and-qualification-of-TCP-performance" href="#Testbed-for-testing-and-qualification-of-TCP-performance" id="Testbed-for-testing-and-qualification-of-TCP-performance">Testbed for testing and qualification of TCP performance</a></h2><p>
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The TCP performance test and qualification testbed is an automated
-        environment that simulates various common and uncommon end-to-end
-        network and link characteristics such as delay, bandwidth
-        limitations, congestion, packet drops, packet corruption and out
-        of order arrival.  The testbed automatically steps through all
-        link types and tests various TCP optimizations and parameter
-        adjustments.  In the end all data is graphically arranged and
-        compared against standard behaviour and each other to judge the
-        positive or negative effects of the modifications.  Work on this
-        project has just started and is based on FreeBSDs dummynet.</p>
-    <hr /><h2><a name="The-FreeBSD-Dutch-Documentation-Project." href="#The-FreeBSD-Dutch-Documentation-Project." id="The-FreeBSD-Dutch-Documentation-Project.">The FreeBSD Dutch Documentation Project.</a></h2><p>
-	Contact:
-          Remko
-          Lodder
-         &lt;<a href="mailto:remko@elvandar.org">remko@elvandar.org</a>&gt;
-	</p>
-      <p>The Dutch Documentation Project is a ongoing project in
-        translating the handbook and other documentation to the dutch
-        language. Currently there is 1 active person (me) translating the
-        documentation. I am currently working on the handbook/basics
-        section. But i can use some more hands, please drop me an email if
-        you wish to help out so that the dutch translation will speed up
-        and be ready in some time.  Contact remko@elvandar.org for
-        information.</p>
-    <hr /><h2><a name="The-FreeBSD-Simplified-Chinese-Project" href="#The-FreeBSD-Simplified-Chinese-Project" id="The-FreeBSD-Simplified-Chinese-Project">The FreeBSD Simplified Chinese Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org.cn" title="http://www.FreeBSD.org.cn">The FreeBSD Simplified Chinese Project (In Simplified Chinese)</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org.cn" title="The FreeBSD Simplified Chinese Project (In Simplified Chinese)">http://www.FreeBSD.org.cn</a></td></tr><tr><td><a href="http://www.FreeBSD.org.cn/snap/zh_CN/" title="http://www.FreeBSD.org.cn/snap/zh_CN/">Translated Website Snapshot</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org.cn/snap/zh_CN/" title="Translated Website Snapshot">http://www.FreeBSD.org.cn/snap/zh_CN/</a></td></tr><tr><td><a href="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/" title="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/">Translated Handbook Snapshot</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/" title="Translated Handbook Snapshot">http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/</a></td></tr></table><p>
-	Contact:
-          Dong
-          LI
-         &lt;<a href="mailto:ld@FreeBSD.org.cn">ld@FreeBSD.org.cn</a>&gt;
-	<br />
-	Contact:
-          Xin
-          LI
-         &lt;<a href="mailto:delphij@frontfree.net">delphij@frontfree.net</a>&gt;
-	</p>
-      <p>The project is a joint effort of volunteers, which focus in
-        the internationalization and localization of the FreeBSD
-        Operating System and applications running on FreeBSD. All of the
-        work resulted in this project will be contributed back to the
-        FreeBSD project.</p>
-      <p>Thanks to many volunteers' help, by this time of writing, we
-        have finished more than 60% of the translation of the FreeBSD
-        Handbook. We plan to submit a preliminary translation of the
-        FreeBSD website as well as the FreeBSD Handbook when most part of
-        them were finished, which is expected to happen in a couple of
-        months. The snapshot of the documentation translation effort
-        could be accessed through the URL listed above.</p>
-      <p>The project also supported individual efforts on porting
-        applications (especially software that supports Simplified
-        and/or Traditional Chinese) to FreeBSD. We are also doing some
-        research on making FreeBSD kernel and base system more
-        i18n-aware.</p>
-    <hr /><h2><a name="Verify-source-reachability-option-for-ipfw2" href="#Verify-source-reachability-option-for-ipfw2" id="Verify-source-reachability-option-for-ipfw2">Verify source reachability option for ipfw2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff" title="http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff"></a></td><td>
-	    URL: <a href="http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff" title="">http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff</a></td></tr></table><p>
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The verify source reachability option for ipfw2 checks if the
-        source IP address of a packet entering the machine is reachable
-        at all.  Thus if we can't send a packet back because we don't
-        have a route back we don't have to forward it because two way
-        communication isn't possible anyway.  It is more than likely
-        that such a packet is spoofed.  This option is almost the same as
-        what is known on Cisco IOS as "ip verify unicast source
-        reachable-via [any|ifn]".  Using this option only makes sense
-        when you don't have a default route which naturally always
-        matches.  So this is useful for machines acting as routers with
-        a default-free view of the entire Internet as common when running
-        a BGP daemon (Zebra/Quagga or OpenBSD bgpd).</p>
-      <p>One useful way of enabling it globally on a router looks like
-        this: ipfw add xxxx deny ip from any to any not versrcreach or for
-        an individual interface only: ipfw add xxxx deny ip from any to
-        any not versrcreach recv fxp0</p>
-    <hr /><h2><a name="vinum-+-GEOM" href="#vinum-+-GEOM" id="vinum-+-GEOM">vinum + GEOM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mailbox.univie.ac.at/~le/geom_vinum.tar.gz" title="http://mailbox.univie.ac.at/~le/geom_vinum.tar.gz"></a></td><td>
-	    URL: <a href="http://mailbox.univie.ac.at/~le/geom_vinum.tar.gz" title="">http://mailbox.univie.ac.at/~le/geom_vinum.tar.gz</a></td></tr></table><p>
-	Contact:
-          Lukas
-          Ertl
-         &lt;<a href="mailto:le@FreeBSD.org">le@FreeBSD.org</a>&gt;
-	</p>
-      <p>The "geomification" of vinum has made some progress.  I now have
-        all basic setups working (concatenated plexes, striped plexes,
-        RAID5 plexes, and RAID1), but I still have to implement correct
-        error handling and status change handling.</p>
-      <p>Still missing is a userland tool, so currently you still have to
-        use "old-style" vinum to configure your setup.</p>
-    <hr /><h2><a name="Weekly-cvs-src-summaries" href="#Weekly-cvs-src-summaries" id="Weekly-cvs-src-summaries">Weekly cvs-src summaries</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://excel.xl0.org/FreeBSD/" title="http://excel.xl0.org/FreeBSD/"></a></td><td>
-	    URL: <a href="http://excel.xl0.org/FreeBSD/" title="">http://excel.xl0.org/FreeBSD/</a></td></tr><tr><td><a href="http://mocart.pinco.pl/FreeBSD/" title="http://mocart.pinco.pl/FreeBSD/">Polish translations</a></td><td>
-	    URL: <a href="http://mocart.pinco.pl/FreeBSD/" title="Polish translations">http://mocart.pinco.pl/FreeBSD/</a></td></tr></table><p>
-	Contact:
-          Mark
-          Johnston
-         &lt;<a href="mailto:mark@xl0.org">mark@xl0.org</a>&gt;
-	</p>
-      <p>I have been producing weekly summaries of commits and the
-        surrounding discussions as reported on the cvs-src mailing list.
-        These summaries are posted to -current on Sunday evenings and
-        archived on the Web.  The reception has been overwhelmingly good.
-        As of the end of February, Polish translations are being produced
-        by Lukasz Dudek and Szymon Roczniak; they are also
-        planning to translate the older summaries.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2004-03-2004-04.html b/website/content/en/status/report-2004-03-2004-04.html
deleted file mode 100644
index 4cef807032..0000000000
--- a/website/content/en/status/report-2004-03-2004-04.html
+++ /dev/null
@@ -1,1035 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>2004 continues on with wonderful progress.  Work continues on locking
-      down the network stack, ACPI made more great strides, an ARM port
-      appeared in the tree, and the FreeBSD 4.10 release cycle wrapped up.
-      Once 4.10 is released, the next big focus will be FreeBSD 5.3.  We
-      expect this is be the start of the 5-STABLE branch, meaning that not
-      only will it be stable for production use, it will also be largely
-      feature complete and stable from an internal API standpoint.  We expect
-      to release 5.3 in mid-summer, and we encourage everyone to download the
-      latest snapshots from <url href="ftp://snapshots.jp.FreeBSD.org"></url>
-      for a preview.</p><p>Thanks,</p><p>Scott Long</p><hr /><ul><li><a href="#ACPI">ACPI</a></li><li><a href="#ATA-project-Status-Report">ATA project Status Report</a></li><li><a href="#Automatic-sizing-of-TCP-send-buffers">Automatic sizing of TCP send buffers</a></li><li><a href="#Binary-security-updates-for-FreeBSD">Binary security updates for FreeBSD</a></li><li><a href="#Book:-The-Design-and-Implementation-of-the-FreeBSD-Operating-System">Book: The Design and Implementation of the FreeBSD Operating System</a></li><li><a href="#CAM-lockdown-and-threading">CAM lockdown and threading</a></li><li><a href="#Convert-ipfw2-to-use-PFIL_HOOKS-mechanism">Convert ipfw2 to use PFIL_HOOKS mechanism</a></li><li><a href="#Cronyx-Tau-ISA-driver">Cronyx Tau-ISA driver</a></li><li><a href="#FreeBSD-Dutch-Documentation-Project">FreeBSD Dutch Documentation Project</a></li><li><a href="#FreeBSD-threading-support">FreeBSD threading support</a></li><li><a href="#FreeBSD/arm">FreeBSD/arm</a></li><li><a href="#GEOM-Gate">GEOM Gate</a></li><li><a href="#Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></li><li><a href="#libarchive/bsdtar">libarchive/bsdtar</a></li><li><a href="#Move-ARP-out-of-routing-table">Move ARP out of routing table</a></li><li><a href="#Network-interface-naming-changes">Network interface naming changes</a></li><li><a href="#Network-Stack-Locking">Network Stack Locking</a></li><li><a href="#OpenOffice.org-porting-status">OpenOffice.org porting status</a></li><li><a href="#PCI-Powerstates-and-Resource">PCI Powerstates and Resource</a></li><li><a href="#Porting-OpenBSD's-packet-filter">Porting OpenBSD's packet filter</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#Status-Report">Status Report </a></li><li><a href="#Sync-protocols-(Netgraph-and-SPPP)">Sync protocols (Netgraph and SPPP)</a></li><li><a href="#The-FreeBSD-Simplified-Chinese-Project">The FreeBSD Simplified Chinese Project</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-Mandatory-Access-Control-(MAC)">TrustedBSD Mandatory Access Control (MAC)</a></li><li><a href="#TrustedBSD-Security-Enhanced-BSD-(SEBSD)-port">TrustedBSD Security-Enhanced BSD (SEBSD) port</a></li><li><a href="#Verify-source-reachability-option-for-ipfw2">Verify source reachability option for ipfw2</a></li></ul><hr /><h2><a name="ACPI" href="#ACPI" id="ACPI">ACPI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.root.org/~nate/freebsd/" title="http://www.root.org/~nate/freebsd/">ACPI TODO</a></td><td>
-	    URL: <a href="http://www.root.org/~nate/freebsd/" title="ACPI TODO">http://www.root.org/~nate/freebsd/</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-acpi" title="http://lists.freebsd.org/mailman/listinfo/freebsd-acpi">ACPI Mailing List</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-acpi" title="ACPI Mailing List">http://lists.freebsd.org/mailman/listinfo/freebsd-acpi</a></td></tr></table><p>
-	Contact:
-          Nate
-          Lawson
-         &lt;<a href="mailto:njl@FreeBSD.org">njl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Much of the ACPI project is waiting for architectural changes to be
-        completed.  For instance, the cpufreq driver requires newbus
-        attachments for CPUs.  Support code for this should be committed
-        at the time of publication.  Other architectural changes needed
-        include rman support for memory/port resources and a generic hotkey
-        and extras driver.  Important work in other areas of the kernel
-        including PCI powerstate support and APIC support have been
-        invaluable in improving ACPI on modern platforms.  Thanks go to
-        Warner Losh and John Baldwin for this work.</p>
-
-      <p>Code which is mostly completed and will go in once the groundwork
-        is finished includes the cpufreq framework, an ACPI floppy controller
-        driver, and full support for dynamic Cx states.</p>
-
-      <p>ACPI-CA was updated to 20040402 in early April.  This has some GPE
-        issues that persist in 20040427 that will hopefully be resolved by
-        the date of publication.</p>
-
-      <p>I'd like to welcome Mark Santcroos (marks@) to the FreeBSD team.
-        He has helped in the past with debugging ACPI issues.
-        If any developers are interested in assisting with ACPI, please
-        see the ACPI TODO and send us an email.</p>
-    <hr /><h2><a name="ATA-project-Status-Report" href="#ATA-project-Status-Report" id="ATA-project-Status-Report">ATA project Status Report</a></h2><p>
-	Contact:
-          S�ren
-          Schmidt
-         &lt;<a href="mailto:sos@FreeBSD.org">sos@FreeBSD.org</a>&gt;
-	</p>
-      There is finally support (except for RAID5) for the Promise SX4/SX4000
-      line of controllers. The support is rudimentary still, and doesn't
-      really make any good use of the cache/sequencer HW yet. The Silicon
-      Image 3114 support has been completed. Lots of bug fixes and cleanups.
-      Future work now concentrates on new controller chips (Marvell SATA
-      chips probably the most prominent) and getting the SATA support
-      finished so that hotswap etc works with SATA HW as well. Also ATA RAID
-      is about to get rewritten to take advantage of the features that the
-      ATA subsystem now offers, including support for the HW on
-      Promise/Marvell and the like controllers. A number of new RAID metadata
-      <p>formats (Intel, AMI) is also in the works.</p>
-    <hr /><h2><a name="Automatic-sizing-of-TCP-send-buffers" href="#Automatic-sizing-of-TCP-send-buffers" id="Automatic-sizing-of-TCP-send-buffers">Automatic sizing of TCP send buffers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Automatic-sizing-of-TCP-send-buffers" title="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Automatic-sizing-of-TCP-send-buffers"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Automatic-sizing-of-TCP-send-buffers" title="">http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Automatic-sizing-of-TCP-send-buffers</a></td></tr></table><p>
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The current TCP send and receive buffers are static and set to a
-        conservative value to preserve kernel memory.  This is sub-optimal
-        for connections with a high bandwidth*delay product because the
-        size of the TCP send buffer determines how big the send window can
-        get.  For high bandwidth trans-continental links this seriously
-        limits the maximum transfer speed per TCP connection.  A moredetailed
-        description from the last status report can be found with the link
-        above.</p>
-      <p>Work on this project has been stalled due to some other network stack
-        projects with higher precedence (ipfw2 to pfil_hooks and
-        ip_input/ip_output cleanups).</p>
-    <hr /><h2><a name="Binary-security-updates-for-FreeBSD" href="#Binary-security-updates-for-FreeBSD" id="Binary-security-updates-for-FreeBSD">Binary security updates for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-update/" title="http://www.daemonology.net/freebsd-update/"></a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-update/" title="">http://www.daemonology.net/freebsd-update/</a></td></tr></table><p>
-	Contact:
-          Colin
-          Percival
-         &lt;<a href="mailto:cperciva@daemonology.net">cperciva@daemonology.net</a>&gt;
-	</p>
-      <p>Having recently passed its first birthday, FreeBSD Update is
-        now being used on about 170 machines every day; on a typical
-        day, around 60 machines will download updates (the others being
-        already up to date).  To date, over 157000 files have been
-        updated on over 4200 machines.</p>
-    <hr /><h2><a name="Book:-The-Design-and-Implementation-of-the-FreeBSD-Operating-System" href="#Book:-The-Design-and-Implementation-of-the-FreeBSD-Operating-System" id="Book:-The-Design-and-Implementation-of-the-FreeBSD-Operating-System">Book: The Design and Implementation of the FreeBSD Operating System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mckusick.com/FreeBSDbook.html" title="http://www.mckusick.com/FreeBSDbook.html"></a></td><td>
-	    URL: <a href="http://www.mckusick.com/FreeBSDbook.html" title="">http://www.mckusick.com/FreeBSDbook.html</a></td></tr></table><p>
-	Contact:
-          Kirk
-          McKusick
-         &lt;<a href="mailto:mckusick@FreeBSD.org">mckusick@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          George
-          Neville-Neil
-         &lt;<a href="mailto:gnn@neville-neil.com">gnn@neville-neil.com</a>&gt;
-	</p>
-      <p>The new Book "The Design and Implementation of the FreeBSD Operating
-        System" is the successor of the legendary "The Design and
-        Implementation of 4.4BSD" book which has become the de-facto standard
-        for teaching of Operating System internals in universities
-        world-wide.</p>
-      <p>This new and completely reworked edition is based on FreeBSD 5.2 and
-        the upcoming FreeBSD 5.3 releases and contains in-details looks into
-        all areas (from virtual memory management to interprocess
-        communication and network stack) of the operating system on 700
-        pages.</p>
-      <p>It is now in final production by Addison-Wesley and will be available
-        in early August 2004.  The ISBN is 0-201-70245-2.</p>
-    <hr /><h2><a name="CAM-lockdown-and-threading" href="#CAM-lockdown-and-threading" id="CAM-lockdown-and-threading">CAM lockdown and threading</a></h2><p>
-	Contact:
-          Scott
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has begun on locking down the CAM subsystem.  The project is
-        divided into several steps:
-      </p>
-      <ul>
-        <li>Separation of the SCSI probe peripheral from cam_xpt.c to
-          scsi_probe.c</li>
-        <li>Threading of the device probe sequence.</li>
-        <li>Locking and reference counting the peripheral drivers.</li>
-        <li>Locking the XPT and device queues.</li>
-        <li>Locking one or more SIMs and devising a way for non-locked drivers
-          to function.</li>
-      </ul>
-
-      <p>While the immediate goal of this work is to lock CAM, it also points
-        us in the direction of separating out the SCSI-specific knowledgefrom
-        the core.  This will allow other transports to be written, such as
-        SAS, iSCSI, and ATA.</p>
-
-      <p>Progress is being tracked in the FreeBSD Perforce server in the
-        camlock branch.  I will make public patches available once it has
-        progressed far enough for reasonable testing.  So far, the first two
-        items are being worked on.</p>
-    <hr /><h2><a name="Convert-ipfw2-to-use-PFIL_HOOKS-mechanism" href="#Convert-ipfw2-to-use-PFIL_HOOKS-mechanism" id="Convert-ipfw2-to-use-PFIL_HOOKS-mechanism">Convert ipfw2 to use PFIL_HOOKS mechanism</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/ipfw-pfilhooks-and-more-20040510.diff" title="http://www.nrg4u.com/freebsd/ipfw-pfilhooks-and-more-20040510.diff"></a></td><td>
-	    URL: <a href="http://www.nrg4u.com/freebsd/ipfw-pfilhooks-and-more-20040510.diff" title="">http://www.nrg4u.com/freebsd/ipfw-pfilhooks-and-more-20040510.diff</a></td></tr></table><p>
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>ipfw2 is built directly into ip_input() and ip_output() and it makes
-        these functions more complicated.  For some time now we have the
-        generic packet filter mechanism PFIL_HOOKS which are used by IPFILTER
-        and the new OpenBSD PF firewall packages to hook themselves into the
-        IP input and output path.</p>
-      <p>This patch makes ipfw2 fully self contained and callable through the
-        PFIL_HOOKS.  This is still work in progress and DUMMYNET and IPDIVERT
-        plus Layer2 firewall are not yet fully functional again but normal
-        firewalling with it works just fine.</p>
-      <p>The patch contains some more cleanups of ip_input() and ip_output()
-        that is work in progress too.</p>
-    <hr /><h2><a name="Cronyx-Tau-ISA-driver" href="#Cronyx-Tau-ISA-driver" id="Cronyx-Tau-ISA-driver">Cronyx Tau-ISA driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cronyx.ru/hardware/wan.html" title="http://www.cronyx.ru/hardware/wan.html">Cronyx WAN Adapters.</a></td><td>
-	    URL: <a href="http://www.cronyx.ru/hardware/wan.html" title="Cronyx WAN Adapters.">http://www.cronyx.ru/hardware/wan.html</a></td></tr></table><p>
-	Contact:
-          Roman
-          Kurakin
-         &lt;<a href="mailto:rik@FreeBSD.org">rik@FreeBSD.org</a>&gt;
-	</p>
-      <p>ctau(4) driver for Cronyx Tau-ISA was added. Cronyx Tau-ISA is family
-        of synchronous WAN adapters with various set of interfaces such as
-        V.35, RS-232, RS-530(449), E1 (both framed and unframed). This is a
-        second family of Cronyx adapters that is supported by FreeBSD now. The
-        first one was Cronyx Sigma-ISA, cx(4).</p>
-
-      <p>Cronyx Tau-PCI family will become a third one. The peculiarity of this
-        driver that it contains private code. This code is distributed as
-        obfuscated source code with usual open source license agreement.Since
-        code is protected by obfuscation it is satisfy needs of commerce. On
-        the other hand it still stays a source code and thus it becomes closer
-        to open source projects. I hope this form of private code distribution
-        will become a real alternative to object form.</p>
-    <hr /><h2><a name="FreeBSD-Dutch-Documentation-Project" href="#FreeBSD-Dutch-Documentation-Project" id="FreeBSD-Dutch-Documentation-Project">FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.evilcoder.org/index.cgi?i=nav&amp;t=freebsd" title="http://www.evilcoder.org/index.cgi?i=nav&amp;t=freebsd">Status and download of the documentation (not yet complete)</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/index.cgi?i=nav&amp;t=freebsd" title="Status and download of the documentation (not yet complete)">http://www.evilcoder.org/index.cgi?i=nav&amp;t=freebsd</a></td></tr></table><p>
-	Contact:
-          Remko
-          Lodder
-         &lt;<a href="mailto:remko@elvandar.org">remko@elvandar.org</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation Project is a ongoing project in
-        translating the handbook and other documentation to the Dutch
-        language. Currently we have a small team of individuals who
-        translate, check other's work, and publish them on the internet.
-        You can view the current status on the webpage (listed above).
-        Still we can use more people helping out, since we have a long
-        way to go. Every hand that wants to help, contact me, and i will
-        provide you details on how we work etc. Currently the project has
-        translated the handbook pages of: The X Windows System, and
-        Configuration and Tuning, they only need to be checked before
-        publishing.</p>
-    <hr /><h2><a name="FreeBSD-threading-support" href="#FreeBSD-threading-support" id="FreeBSD-threading-support">FreeBSD threading support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~marcel/tls.html" title="http://people.freebsd.org/~marcel/tls.html">basic data on TLS</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~marcel/tls.html" title="basic data on TLS">http://people.freebsd.org/~marcel/tls.html</a></td></tr></table><p>
-	Contact:
-          David
-          Xu
-         &lt;<a href="mailto:davidxu@FreeBSD.org">davidxu@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Doug
-          Rabson
-         &lt;<a href="mailto:dfr@FreeBSD.org">dfr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Julian
-          Elischer
-         &lt;<a href="mailto:julian@FreeBSD.org">julian@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Marcel
-          Moolinar
-         &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Dan
-          Eischen
-         &lt;<a href="mailto:deischen@FreeBSD.org">deischen@FreeBSD.org</a>&gt;
-	</p>
-      <p>
-        Threading developers have been active behind the scenes
-        though not much has been visible. Real Life(TM) has been
-        hard on us as a group however.</p>
-      <p> Marcel and Davidxu have both (individually)
-        been looking at the support
-        for debugging threaded programs. David has a set of
-        patches that allow gdb to correctly handle KSE programs and
-        patches are being considered for libthr based processes.
-        Marcel added a Thread ID to allow debugging code to unambiguously
-        specify a thread to debug. He has also been looking at corefile
-        support.  Both sets of patches are preliminary.</p>
-      <p>Dan Eischen continues to support people migrating to
-        libpthreads and it seems to be going well.</p>
-      <p>Doug Rabson has done his usual miracle work and produced
-        a set of preliminary patches to implement TLS (Thread
-        Local Storage) for the i386 platform.</p>
-      <p>Julian Elischer is investigating some refactoring of the kernel
-        support code.</p>
-      <p>Platforms:</p>
-      <p>i386, amd64, ia64  libpthread works.</p>
-      <p>alpha, sparc64   not implemented.</p>
-    <hr /><h2><a name="FreeBSD/arm" href="#FreeBSD/arm" id="FreeBSD/arm">FreeBSD/arm</a></h2><p>
-	Contact:
-          Olivier
-          Houchard
-         &lt;<a href="mailto:cognet@FreeBSD.org">cognet@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD/arm is now in the FreeBSD CVS tree. Dynamic libraries now work,
-        and NO_CXX=true NO_RESCUE=true buildworld works too (with patches for
-        toolchain that will live outside the tree for now). Now the focus
-        should be on xscale support.</p>
-    <hr /><h2><a name="GEOM-Gate" href="#GEOM-Gate" id="GEOM-Gate">GEOM Gate</a></h2><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>GEOM Gate class is now committed as well as ggatec(8), ggated(8)
-        and ggatel(8) utilities. It makes distribution of disk devices
-        through the network possible, but on the disk level (don't confuse
-        it with NFS, which provides exporting data on the file system
-        level).</p>
-    <hr /><h2><a name="Improved-Multibyte/Wide-Character-Support" href="#Improved-Multibyte/Wide-Character-Support" id="Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></h2><p>
-	Contact:
-          Tim
-          Robbins
-         &lt;<a href="mailto:tjr@FreeBSD.org">tjr@FreeBSD.org</a>&gt;
-	</p>
-      <p>New locales: Unicode UTF-8 locales have been added to the base system.
-        All of the locales previously supported by FreeBSD now have a
-        corresponding UTF-8 version, along with one or two new ones --
-        53 in all.</p>
-      <p>Library changes: The restartable conversion functions (mbrtowc(),
-        wcrtomb(), etc.) in the C library have been updated to handle partial
-        characters in the way prescribed by the C99 standard.
-        The &lt;wctype.h&gt; functions have been optimized for handling
-        large, fragmented character sets like Unicode and GB18030.
-        Documentation has been improved.</p>
-      <p>Utilities: The ls utility has been modified to work with wide
-        characters internally when determining whether a character in a
-        filename is printable, and how many column positions it takes on
-        the screen. Character handling in the wc utility has been made
-        more robust. Other text-processing utilities (expand, fold, unexpand,
-        uniq) have been modified, but these changes have not been committed
-        until the performance impact can be evaluated. Work on a POSIX-style
-        localedef utility has started, with the aim to have it replace
-        the current mklocale and colldef utilities in FreeBSD 6.
-        (It is currently on the back-burner awaiting a response to a POSIX
-        defect report.)</p>
-      <p>Future directions: wide character handling functions need to be
-        optimized so that they are more competitive with the single-byte
-        functions when dealing with 8-bit character sets. Utilities need to
-        be modified to handle multibyte characters, but with a careful eye
-        on performance. Localedef needs to be finished.</p>
-    <hr /><h2><a name="libarchive/bsdtar" href="#libarchive/bsdtar" id="libarchive/bsdtar">libarchive/bsdtar</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~kientzle/" title="http://people.freebsd.org/~kientzle/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~kientzle/" title="">http://people.freebsd.org/~kientzle/</a></td></tr></table><p>
-	Contact:
-          Tim
-          Kientzle
-         &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	</p>
-      <p>Both bsdtar and libarchive are now part of -CURRENT.
-        A few minor problems have been reported and addressed,
-        including performance issues with many hard-links, and
-        options required by certain packages.
-        For now, the "tar" command is still an alias for "gtar."
-        Those who would like to use bsdtar as the default system tar
-        can define WITH_BSDTAR to make "tar" be an alias for
-        "bsdtar."</p>
-
-      <p>My current plan is to make bsdtar be the default in -CURRENT in
-        about another month, probably after the 5-STABLE split, and remove
-        gtar from -CURRENT sometime later.  It's still open if and when
-        this switch will occur in 5-STABLE.  On the one hand, I see
-        potential problems if 5-STABLE and 6-CURRENT have different tar
-        commands; on the other hand, switching could be disruptive for
-        some users.</p>
-
-    <hr /><h2><a name="Move-ARP-out-of-routing-table" href="#Move-ARP-out-of-routing-table" id="Move-ARP-out-of-routing-table">Move ARP out of routing table</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html" title="">http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html</a></td></tr></table><p>
-	Contact:
-          Luigi
-          Rizzo
-         &lt;<a href="mailto:luigi@FreeBSD.org">luigi@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ARP IP address to MAC address mapping does not belong into
-        the routing table (FIB) as it is currently done.  This will move
-        it to its own hash based structure which will be instantiated per
-        each 802.1 broadcast domain.  With this change it is possible to
-        have more than one interface in the same IP subnet and layer 2
-        broadcast domain.  The ARP handling and the routing table will be
-        quite a bit simplified afterwards.  As an additional benefit full
-        MAC address based accounting will be provided.</p>
-      <p>Luigi has become the driver of this project and posted a first
-        implementation for comments on 25. April 2004 (see link).</p>
-    <hr /><h2><a name="Network-interface-naming-changes" href="#Network-interface-naming-changes" id="Network-interface-naming-changes">Network interface naming changes</a></h2><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>An enhanced network interface cloning API has been created.  It
-        allows interfaces to support more complex names than the current
-        name# style.  This functionality has been used to enable
-        interesting cloners like auto-configuring vlan interfaces.  Other
-        features include locking of cloner structures and the ability of
-        drivers to reject destroy requests.  A patch has been posted to
-        the freebsd-net mailing list for review and will be committed in
-        early May.  This work is taking place in the perforce repository
-        under: //depot/user/brooks/xname/...</p>
-    <hr /><h2><a name="Network-Stack-Locking" href="#Network-Stack-Locking" id="Network-Stack-Locking">Network Stack Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.watson.org/~robert/freebsd/netperf/" title="http://www.watson.org/~robert/freebsd/netperf/">Robert's Network Stack Locking Page</a></td><td>
-	    URL: <a href="http://www.watson.org/~robert/freebsd/netperf/" title="Robert's Network Stack Locking Page">http://www.watson.org/~robert/freebsd/netperf/</a></td></tr></table><p>
-	Contact:
-          Robert
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is aimed at converting the FreeBSD network stack from
-        running under the single Giant kernel lock to permitting it to run
-        in a fully parallel manner on multiple CPUs (i.e., a fully threaded
-        network stack). This will improve performance/latency through
-        reentrancy and preemption on single-processor machines, and also on
-        multi-processor machines by permitting real parallelism in the
-        processing of network traffic. As of FreeBSD 5.2, it was possible to
-        run low level network functions, as well as the IP filtering and
-        forwarding plane, without the Giant lock, as well as "process to
-        completion" in the interrupt handler.</p>
-
-      <p>Work continues to improve the maturity and completeness of the
-        locking (and performance) of the network stack for 5.3.  The network
-        stack development branch has been updated to the latest CVS HEAD,
-        as well as the following and more:</p>
-
-      <ul>
-        <li>Review of socket flag and socket buffer flag locking;
-          so_state broken out into multiple fields covered by different
-          locks to avoid lock orders in frobbing the so_state field.
-          Work in progress.</li>
-        <li>WITNESS now includes hard ordering for many network locks to
-          improve lock order debugging process.</li>
-        <li>MAC Framework modified to use pcbs instead of sockets in a
-          great many situations to avoid socket locking in network layer,
-          especially when generating new mbufs.</li>
-        <li>New annotations relating to socket and interface locking.</li>
-        <li>Began NetGraph review and corrected NetGraph socket locking
-          problems.</li>
-        <li>sendfile() locking appears now to be fixed, albeit holding
-          Giant more than strictly necessary.</li>
-        <li>if_ppp global variable locking performed and merged.</li>
-        <li>A variety of race conditions and bugs in soreceive() locking
-          fixed, including existing race conditions triggered only rarely
-          in -HEAD and -STABLE that triggered easily with SMP and Giant-free
-          operation.</li>
-        <li>Locking of socket buffer and socket fields from fifofs.
-          Proposed patch to correct lock order problem between vnode
-          interlock and socket buffer lock order problems.  fifofs
-          interactions with UNIX domain sockets cleaned up.</li>
-        <li>Research into KQueue issues.  Feedback to KQueue locking
-          patch authors.</li>
-        <li>netatalk AARP locked down, MPSAFE, and merged to CVS.</li>
-        <li>Lock order issues between socket, socket buffer, and UNIX domain
-          socket locks corrected.  Race conditions and potential deadlocks
-          removed.</li>
-        <li>if_gif recursion cleanups, if_gif is much more MPSAFE.</li>
-        <li>First pass MPSAFE locking of NFS server uses an NFS server
-          subsystem lock to allow so_upcall() from socket layer without
-          Giant.  This closes race conditions in the NFS server when
-          operating Giant free.  Second pass for data based locking is
-          also in testing.</li>
-        <li>if_sl.c (SLIP) fine-grained locking completed and merged to
-          CVS.</li>
-        <li>if_tun.c (tunnel) fine-grained locking completed and merged to
-          CVS.</li>
-        <li>Merge of conditional Giant locking on debug.mpsafenet to CVS;
-          semantics now changed so that Giant isn't just twiddled over
-          the forwarding path, but the entire stack.  Must be used with
-          caution unless running with our patches.  Callouts also
-          convered to conditional safety.</li>
-        <li>if_gif, if_gre global variables locked and merged to CVS.</li>
-        <li>netatalk DDP cleanup (break out PCB from protocol code),
-          largely locked down at the PCB level.  Some work remains to
-          be done before patches can be distributed for testing, but close
-          to MPSAFE.</li>
-        <li>Began review of netipx, netinet6 code for locking requirements,
-          some bugs corrected.</li>
-        <li>Race conditions in handling of socket so_comp, so_incomp
-          debugged and hopefully closed through new locking of these
-          fields.</li>
-        <li>Many new locking annotations, field documentation, lock order
-          documentation.</li>
-      </ul>
-      <p>Netperf patches are proving to be quite stable in a broad variety
-        of environment, as long as non-MPSAFE chunks are avoided.  Kqueue,
-        IPv6, and ifnet locking remain the most critical areas where
-        additional functionality is required.  Focus is shifting from new
-        development to in depth testing, performance measurement, and
-        interactions with other subsystems.</p>
-      <p>This work would not be possible without contributions from the
-        following people (and no doubt many others):
-        John Baldwin, Bob Bishop, Brooks Davis, Pawel Jakub Dawidek, Matthew
-        Dodd, Julian Elischer, Ruslan Ermilov, John-Mark Gurney, Jeffrey Hsu,
-        Kris Kennaway, Roman Kurakin, Max Laier, Sam Leffler, Scott Long, Rick
-        Maklem, Bosko Milekic, George Neville-Neil, Andre Oppermann, Luigi
-        Rizzo, Jeff Roberson, Tim Robbins, Mike Silberback, Bruce Simpson,
-        Seigo Tanimura, Hajimu UMEMOTO, Jennifer Yang, Peter Wemm.  We hope to
-        present these patches on arch@ within a few days, although some
-        elements required continued refinement (especially socket locking).</p>
-    <hr /><h2><a name="OpenOffice.org-porting-status" href="#OpenOffice.org-porting-status" id="OpenOffice.org-porting-status">OpenOffice.org porting status</a></h2><p>
-	Contact:
-          NAKATA
-          Maho
-         &lt;<a href="mailto:maho@FreeBSD.org">maho@FreeBSD.org</a>&gt;
-	</p>
-      <p>After almost three years efforts for porting OpenOffice.org 1.0.x and
-        1.1.0 for FreeBSD by Martin Blapp (mbr@FreeBSD.org) and other
-        contributors, There are four version of OpenOffice.org (OOo) in ports
-        tree.  1.1.1: stable version, 1.1.2: next stable, 2.0: developer and
-        1.0.3: legacy.
-      </p>
-
-      <p>Stable version 1.1.1 in /usr/ports/editors/openoffice-1.1/
-        builds/installs/works fine for 5.2.1-RELEASE.  Packages for
-        5.2.1-RELEASE, 26 localized versions and 4.10-PRELEASE only English
-        version, are available at
-        http://oootranslation.services.openoffice.org/pub/OpenOffice.org/ooomisc/
-        (note: source of OOo 1.1.1.RC3 is identical OOo 1.1.1)</p>
-
-      <p>Patches needed to build are currently 18 for 1.1.1, and 161 for 1.0.3
-        the number of patches are greatly reduced.</p>
-
-      <p>OOo 1.1.2, the next stable version in
-        /usr/ports/editors/openoffice-1.1-devel is also builds/installs/works
-        fine for 5.2.1-RELEASE. We are planning to upgrade this port as soon
-        as 1.1.2 will be released.</p>
-
-      <p>Next major release, 2.0 (planned to be released at January 2005
-        according to
-        http://development.openoffice.org/releases/OpenOffice_org_trunk.html),
-        /usr/ports/editors/openoffice-2.0-devel, now compiles for
-        5.2.1-RELEASE but have big problem that prohibits to remove BROKEN.</p>
-
-      <p>Legacy version, OOo 1.0.3: /usr/ports/editors/openoffice-1.0/ I'm not
-        interested in this port. We hope someone else will maintain this.</p>
-
-      <p>For builds, my main environment is 5.2.1-RELEASE, and I have no access
-        to 4-series, so several build problems had been reported for 5-current
-        and 4-stable, however, they now seems to be fixed. Please make sure
-        your Java and/or kernel are up-to-date.</p>
-
-      <p>For version 1.1.1, yet we have serious reproducible core dumps, this
-        means OOo cannot pass the Quality Assurance protocol of OpenOffice.org
-        (http://qa.openoffice.org), so we cannot release OOo as quality
-        assured package.  It seems to be FreeBSD's userland bug, since some
-        reports show that there are no problem for 4-stable but we still
-        searchingthe reason.</p>
-
-      <p>Note that developers should sign JCA (Joint Copyright Assignment)
-        before submitting patches via PR or e-mail, otherwise patches won't be
-        integrated to OOo's source tree.  We seriously need more developers,
-        testers and builders.</p>
-    <hr /><h2><a name="PCI-Powerstates-and-Resource" href="#PCI-Powerstates-and-Resource" id="PCI-Powerstates-and-Resource">PCI Powerstates and Resource</a></h2><p>
-	Contact:
-          Warner
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Lazy allocation of pci resources has been merged into the main
-        tree.  These changes allow FreeBSD to run on computers where PnP
-        OS is set to true.  In addition, the saving and restoring of the
-        resources across suspend/resume has helped some devices come
-        back from suspend.</p>
-
-      <p>Future work will focus on bus numbering.</p>
-    <hr /><h2><a name="Porting-OpenBSD's-packet-filter" href="#Porting-OpenBSD's-packet-filter" id="Porting-OpenBSD's-packet-filter">Porting OpenBSD's packet filter</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pf4freebsd.love2party.net/" title="http://pf4freebsd.love2party.net/"></a></td><td>
-	    URL: <a href="http://pf4freebsd.love2party.net/" title="">http://pf4freebsd.love2party.net/</a></td></tr><tr><td><a href="http://www.benzedrine.cx/pf.html" title="http://www.benzedrine.cx/pf.html"></a></td><td>
-	    URL: <a href="http://www.benzedrine.cx/pf.html" title="">http://www.benzedrine.cx/pf.html</a></td></tr><tr><td><a href="http://openbsd.org/faq/pf/index.html" title="http://openbsd.org/faq/pf/index.html"></a></td><td>
-	    URL: <a href="http://openbsd.org/faq/pf/index.html" title="">http://openbsd.org/faq/pf/index.html</a></td></tr><tr><td><a href="http://www.rofug.ro/projects/freebsd-altq/" title="http://www.rofug.ro/projects/freebsd-altq/"></a></td><td>
-	    URL: <a href="http://www.rofug.ro/projects/freebsd-altq/" title="">http://www.rofug.ro/projects/freebsd-altq/</a></td></tr></table><p>
-	Contact:
-          Max
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Daniel
-          Hartmeier
-         &lt;<a href="mailto:dhartmei@FreeBSD.org">dhartmei@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Pyun
-          YongHyeon
-         &lt;<a href="mailto:yongari@kt-is.co.kr">yongari@kt-is.co.kr</a>&gt;
-	</p>
-      <p>The two months after the import was done were actually rather quiet.
-        We imported a couple of minor fixes from the OpenBSD stable branch.
-        The import of tcpdump 3.8.3 and libpcap 0.8.3 done by Bruce M.Simpson
-        in late March finally put us into the position to build a working
-        pflogd(8) and provide rc.d linkage for it. Tcpdump now understandsthe
-        pflog(4) pseudo-NIC packet format and can be used to read the
-        log-files.</p>
-
-      <p>There has also been work behind the scenes to prepare an import of
-        the OpenBSD 3.5 sources. The patches are quite stable already andwill
-        be posted shortly. Altq is in the making as well and going alongquite
-        well based on the great work from rofug.ro, but as it needs
-        modifications to every network driver which have to be tested
-        thoroughly it needs more time.</p>
-    <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          John
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Several folks continue to work on the locking the network stack
-        as noted elsewhere in this report.  Outside of the network stack,
-        the following items were worked on during the March and April time
-        frame.  Giant was pushed down in the fork, exit, and wait system
-        calls as far as possible.  Alan Cox (alc@) continues to lock the
-        VM subsystem and push down Giant where appropriate.  A few system
-        calls and callouts were marked MP safe as well.</p>
-
-      <p>A few changes were made to the interrupt thread infrastructure.
-        Interrupt thread preemption was finally enabled on the Alpha
-        architecture with the help of the recently added support to the
-        scheduler for pinning threads to a specific CPU.  An optimization
-        to reduce context switches during heavy interrupt load was added
-        as well as rudimentary interrupt storm protection.</p>
-    <hr /><h2><a name="Status-Report" href="#Status-Report" id="Status-Report">Status Report </a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wleiden.webweaving.org:8080/svn/node-config/other/enh-sec-patch/README" title="http://wleiden.webweaving.org:8080/svn/node-config/other/enh-sec-patch/README"></a></td><td>
-	    URL: <a href="http://wleiden.webweaving.org:8080/svn/node-config/other/enh-sec-patch/README" title="">http://wleiden.webweaving.org:8080/svn/node-config/other/enh-sec-patch/README</a></td></tr><tr><td><a href="http://bsd.slashdot.org/article.pl?amp;sid=03/12/27/2035245&amp;mode=thread&amp;tid=122&amp;tid=126&amp;tid=137&amp;tid=172&amp;tid=185&amp;tid=190&amp;tid=193" title="http://bsd.slashdot.org/article.pl?amp;sid=03/12/27/2035245&amp;mode=thread&amp;tid=122&amp;tid=126&amp;tid=137&amp;tid=172&amp;tid=185&amp;tid=190&amp;tid=193"></a></td><td>
-	    URL: <a href="http://bsd.slashdot.org/article.pl?amp;sid=03/12/27/2035245&amp;mode=thread&amp;tid=122&amp;tid=126&amp;tid=137&amp;tid=172&amp;tid=185&amp;tid=190&amp;tid=193" title="">http://bsd.slashdot.org/article.pl?amp;sid=03/12/27/2035245&amp;mode=thread&amp;tid=122&amp;tid=126&amp;tid=137&amp;tid=172&amp;tid=185&amp;tid=190&amp;tid=193</a></td></tr></table><p>
-	Contact:
-          Roland
-          van Laar
-         &lt;<a href="mailto:the_mip_rvl@myrealbox.com">the_mip_rvl@myrealbox.com</a>&gt;
-	</p>
-      <p>This patch if for if_wi current. It enables you to disable the ssid
-        broadcasting and it also allows you to disable clients connecting
-        with a blank ssid.</p>
-    <hr /><h2><a name="Sync-protocols-(Netgraph-and-SPPP)" href="#Sync-protocols-(Netgraph-and-SPPP)" id="Sync-protocols-(Netgraph-and-SPPP)">Sync protocols (Netgraph and SPPP)</a></h2><p>
-	Contact:
-          Roman
-          Kurakin
-         &lt;<a href="mailto:rik@FreeBSD.org">rik@FreeBSD.org</a>&gt;
-	</p>
-      <p>As part of my work on synchronous protocol stack a ng_sppp driver was
-        added to the system. This driver allows to use sppp as a Netgraph
-        node.  Now I plan to update sppp driver as much as possible to make it
-        in sync with Cronyxs one (PPP part). Also I work on FRF.12 support in
-        FreeBSD (now I have FRF.12 support for Netgraph and SPPP (and for
-        Cronyx linux fr driver) but only End-to-End). I plan to test it by my
-        self within a week and after that I plan to make full support of
-        FRF.12.</p>
-      <p>If you want to get current version and test it, please feel free to
-        contact me.</p>
-    <hr /><h2><a name="The-FreeBSD-Simplified-Chinese-Project" href="#The-FreeBSD-Simplified-Chinese-Project" id="The-FreeBSD-Simplified-Chinese-Project">The FreeBSD Simplified Chinese Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org.cn" title="http://www.FreeBSD.org.cn">The FreeBSD Simplified Chinese Project (In Simplified Chinese)</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org.cn" title="The FreeBSD Simplified Chinese Project (In Simplified Chinese)">http://www.FreeBSD.org.cn</a></td></tr><tr><td><a href="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/" title="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/">Translated Handbook Snapshot</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/" title="Translated Handbook Snapshot">http://www.FreeBSD.org.cn/snap/doc/zh_CN.GB2312/books/handbook/</a></td></tr><tr><td><a href="http://www.freebsd.org.cn/cndocs/translations.html" title="http://www.freebsd.org.cn/cndocs/translations.html">Translation status</a></td><td>
-	    URL: <a href="http://www.freebsd.org.cn/cndocs/translations.html" title="Translation status">http://www.freebsd.org.cn/cndocs/translations.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org.cn/snap/zh_CN/" title="http://www.FreeBSD.org.cn/snap/zh_CN/">Translated Website Snapshot</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org.cn/snap/zh_CN/" title="Translated Website Snapshot">http://www.FreeBSD.org.cn/snap/zh_CN/</a></td></tr></table><p>
-	Contact:
-          Xin
-          LI
-         &lt;<a href="mailto:delphij@frontfree.net">delphij@frontfree.net</a>&gt;
-	</p>
-      <p>We have finished about 75% of the Handbook translation work.
-        In the last two months we primarily worked on bringing the
-        handbook chapters more up to date. To make the translation
-        more high quality we are also doing some revision on it.</p>
-      <p>We are still looking for manpower on SGML'ifying the FAQ
-        translation which has been done last year by several volunteers.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Discussion List
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project is producing an implementation of CAPP
-        compliant Audit support for use with FreeBSD based on the Apple
-        Darwin implementation.</p>
-
-      <p>Experimentally integrated the XNU audit implementation from Apple's
-        Darwin 7.2 into Perforce.</p>
-
-      <p>Adapted audit framework to compile into FreeBSD -- required
-        modifying memory allocation and synchronization to use FreeBSD
-        SMPng primitives instead of Mach primitives.
-        Pushed down the Giant lock out of most of the audit code, various
-        other FreeBSD adaptations such as suser() API changes, using BSD
-        threads, td-&gt;td_ucred, etc.</p>
-
-      <p>Adapted per-thread audit data to map to FreeBSD threads</p>
-
-      <p>Cleaned up userspace/kernel API interactions, including udev_t/
-        dev_t inconsistencies between Darwin and FreeBSD.</p>
-
-      <p>Use vn_fullpath() instead of vn_getpath(), which is a less
-        complete solution we'll need to address in the future.</p>
-
-      <p>Basic kernel framework now operates on FreeBSD; praudit
-        tool written that can parse FreeBSD BSM and Solaris BSM.</p>
-
-    <hr /><h2><a name="TrustedBSD-Mandatory-Access-Control-(MAC)" href="#TrustedBSD-Mandatory-Access-Control-(MAC)" id="TrustedBSD-Mandatory-Access-Control-(MAC)">TrustedBSD Mandatory Access Control (MAC)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Discussion List
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Mandatory Access Control (MAC) Framework
-        permits the FreeBSD kernel and userspace access control
-        policies to be adapted at compile-time, boot-time, or
-        run-time.  The MAC Framework provides common infrastructure
-        components, such as policy-agnostic labeling, making it
-        possible to easily development and distribute new access
-        control policy modules.  Sample modules include Biba, MLS,
-        and Type Enforcement, as well as a variety of system
-        hardening policies.</p>
-
-      <p>The TrustedBSD MAC development branch in Perforce was
-        integrated to the most recent 5-CURRENT.</p>
-
-      <p>mdmfs(8) -l to create multi-label mdmfs file systems (merged).</p>
-
-      <p>Diskless boot updated to support MAC.</p>
-
-      <p>Re-arrangement of MAC Framework code to break out mac_net.c
-        into mac_net.c, mac_inet.c, mac_socket.c (merged).</p>
-
-      <p>libugidfw(3) grows bsde_add_rule(3) to automatically allocate
-        rule numbers (merged).  ugidfw(8) grows 'add' to use this
-        (merged).</p>
-
-      <p>pseudofs(4) no longer requires MAC localizations.</p>
-
-      <p>BPF fine-grained locking now used to protect BPD descriptor
-        labels instead of Giant (merged).</p>
-
-      <p>Prefer inpcb's as the source of labels over sockets when
-        creating new mbufs throughout the network stack, reducing
-        socket locking issues for labels.</p>
-    <hr /><h2><a name="TrustedBSD-Security-Enhanced-BSD-(SEBSD)-port" href="#TrustedBSD-Security-Enhanced-BSD-(SEBSD)-port" id="TrustedBSD-Security-Enhanced-BSD-(SEBSD)-port">TrustedBSD Security-Enhanced BSD (SEBSD) port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Discussion List
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-
-      <p>TrustedBSD "Security-Enhanced BSD" (SEBSD) is a port of NSA's
-        SELinux FLASK security architecture, Type Enforcement (TE)
-        policy engine and language, and sample policy to FreeBSD using
-        the TrustedBSD MAC Framework.  SEBSD is available as a loadable
-        policy module for the MAC Framework, along with a set of
-        userspace extensions support security-extended labeling calls.
-        In most cases, existing MAC Framework functions provide the
-        necessary abstractions for SEBSD to plug in without SEBSD-specific
-        changes, but some extensions to the MAC Framework have been
-        required; these changes are developed in the SEBSD development
-        branch, then merged to the MAC branch as they mature, and then
-        to the FreeBSD development tree.</p>
-
-      <p>Unlike other MAC Framework policy modules, the SEBSD module
-        falls under the GPL, as it is derived from NSA's
-        implementation.  However, the eventual goal is to support
-        plugging SEBSD into a base FreeBSD install without any
-        modifications to FreeBSD itself.</p>
-
-      <p>Integrated to latest FreeBSD CVS and MAC branch.</p>
-
-      <p>New FreeBSD code drop updated for capabilities in preference
-        to superuser checks.</p>
-
-      <p>Installation instructions now available!</p>
-
-    <hr /><h2><a name="Verify-source-reachability-option-for-ipfw2" href="#Verify-source-reachability-option-for-ipfw2" id="Verify-source-reachability-option-for-ipfw2">Verify source reachability option for ipfw2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Verify-source-reachability-option-for-ipfw2" title="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Verify-source-reachability-option-for-ipfw2"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Verify-source-reachability-option-for-ipfw2" title="">http://www.freebsd.org/news/status/report-jan-2004-feb-2004.html#Verify-source-reachability-option-for-ipfw2</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=ipfw&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+5.2-current&amp;format=html" title="http://www.freebsd.org/cgi/man.cgi?query=ipfw&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+5.2-current&amp;format=html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=ipfw&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+5.2-current&amp;format=html" title="">http://www.freebsd.org/cgi/man.cgi?query=ipfw&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+5.2-current&amp;format=html</a></td></tr></table><p>
-	Contact:
-          Andre
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The verify source reachability option for ipfw2 has been committed
-        on 23. April 2004 to FreeBSD-CURRENT.  For more information see the
-        links above.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2004-05-2004-06.html b/website/content/en/status/report-2004-05-2004-06.html
deleted file mode 100644
index 1d2b8f041f..0000000000
--- a/website/content/en/status/report-2004-05-2004-06.html
+++ /dev/null
@@ -1,982 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This installment of the Bi-Monthly Status Report is a few days late,
-      but I'm pleased to say that it is chocked full of over 30 articles.
-      May and June were yet again busy months; the Netperf project passed
-      major milestones and can now be run with the debug.mpsafenet tunable
-      turned on from sources in CVS.  The ARM, MIPS, and PPC ports saw quite
-      a bit of progress, as did several other SMPng and Netgraph projects.
-      FreeBSD 5.3 is just around the corner, so don't hesitate to grab a
-      snapshot and test the progress!</p><p>On a more serious note, it's very important to remember that code
-      freeze for FreeBSD 5.3 will happen on August 15, 2004.  This is only
-      a few weeks away and there is still a lot to do.  The TODO list for
-      the release can be found at
-      <a href="http://www.freebsd.org/releases/5.3R/todo.html" shape="rect">
-      http://www.freebsd.org/releases/5.3R/todo.html</a>.  If
-      you are looking for a way to contribute to the release, this TODO list
-      has several items that are in urgent and in need of attention.
-      Testing is also very important.  The tree has had some stability
-      stability problems in the past few weeks, but there are work-arounds
-      that should allow everyone to continue testing and using FreeBSD.  We
-      absolutely must have FreeBSD 5.3 be a rock-solid release, so every
-      little bit of contributed effort helps!</p><p>Thanks,</p><p>Scott Long</p><hr /><ul><li><a href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-      Bluetooth stack for FreeBSD (Netgraph implementation)
-    </a></li><li><a href="#ALTQ-import">ALTQ import</a></li><li><a href="#Buf-Junta-project">Buf Junta project</a></li><li><a href="#CAM-Lockdown">CAM Lockdown</a></li><li><a href="#Cronyx-Adapters-Drivers">Cronyx Adapters Drivers</a></li><li><a href="#EuroBSDCon-2004-registration-now-open">EuroBSDCon 2004 registration now open</a></li><li><a href="#FreeBSD-Brazilian-Documentation-Project">FreeBSD Brazilian Documentation Project</a></li><li><a href="#FreeBSD-Dutch-Documentation-Project">FreeBSD Dutch Documentation Project</a></li><li><a href="#FreeBSD-Handbook,-3rd-Edition,-Volume-II:-Administrator-Guide">FreeBSD Handbook, 3rd Edition, Volume II: Administrator Guide</a></li><li><a href="#FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></li><li><a href="#FreeBSD-profile.sh">FreeBSD profile.sh</a></li><li><a href="#FreeBSD/arm">FreeBSD/arm</a></li><li><a href="#FreeBSD/MIPS-Status-Report">FreeBSD/MIPS Status Report</a></li><li><a href="#HP-Network-Scanjet-5">HP Network Scanjet 5</a></li><li><a href="#i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing">i386 Interrupt Code &amp; PCI Interrupt Routing</a></li><li><a href="#Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></li><li><a href="#IPFilter-Upgraded-to-3.4.35">IPFilter Upgraded to 3.4.35</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#kgi4BSD">kgi4BSD</a></li><li><a href="#Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></li><li><a href="#Network-interface-naming-changes">Network interface naming changes</a></li><li><a href="#Network-Stack-Locking">Network Stack Locking</a></li><li><a href="#Packet-Filter---pf">Packet Filter - pf</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#Project-Mini-Evil">Project Mini-Evil</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#Sync-protocols-(Netgraph-and-SPPP)">Sync protocols (Netgraph and SPPP)</a></li><li><a href="#TTY-subsystem-realignment">TTY subsystem realignment</a></li><li><a href="#Various-GEOM-classes-and-geom(8)-utility">Various GEOM classes and geom(8) utility</a></li><li><a href="#VuXML-and-portaudit">VuXML and portaudit</a></li></ul><hr /><h2><a name="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" href="#Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)" id="Bluetooth-stack-for-FreeBSD-(Netgraph-implementation)">
-      Bluetooth stack for FreeBSD (Netgraph implementation)
-    </a></h2><p>
-	Contact:
-          Maksim
-          Yevmenkin
-         &lt;<a href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;
-	</p>
-      <p>Bluetooth code was marked as non-i386 specific. It is now possible
-        to build it on all supported platforms. Please help with testing.
-        Other then this there was not much progress during last few months.
-        I've been very busy with Real Life.</p>
-    <hr /><h2><a name="ALTQ-import" href="#ALTQ-import" id="ALTQ-import">ALTQ import</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ" title="http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ">ALTQ homepage.</a></td><td>
-	    URL: <a href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ" title="ALTQ homepage.">http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ</a></td></tr><tr><td><a href="http://www.rofug.ro/projects/freebsd-altq/" title="http://www.rofug.ro/projects/freebsd-altq/">ALTQ integration in FreeBSD project.</a></td><td>
-	    URL: <a href="http://www.rofug.ro/projects/freebsd-altq/" title="ALTQ integration in FreeBSD project.">http://www.rofug.ro/projects/freebsd-altq/</a></td></tr><tr><td><a href="http://people.freebsd.org/~mlaier/ALTQ_driver/" title="http://people.freebsd.org/~mlaier/ALTQ_driver/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mlaier/ALTQ_driver/" title="">http://people.freebsd.org/~mlaier/ALTQ_driver/</a></td></tr></table><p>
-	Contact:
-          Max
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ALTQ framework is part of KAME for more than 4 years and has
-        been adopted by Net- and OpenBSD since more than 3 years. It
-        provides means of managing outgoing packets to do QoS and bandwidth
-        limitations.  OpenBSD developed a different way to interact with
-        ALTQ using pf, which was adopted by KAME as the "default for
-        everyday use".</p>
-
-      <p>The Romanian FreeBSD Users Group has had a project to work towards
-        integration of ALTQ into FreeBSD, which provided a very good
-        starting point for the final import. The import only provides the
-        "pf mode" configuration and classification API as the older ALTQ3
-        API does not suit to our SMP approach.</p>
-
-      <p>A reworked configuration API (decoupled from pf) is in the making
-        as are additional driver modifications. Both should be done before
-        5-STABLE is branched, although additional drivers can be imported
-        during the lifetime of 5-STABLE as well.</p>
-    <hr /><h2><a name="Buf-Junta-project" href="#Buf-Junta-project" id="Buf-Junta-project">Buf Junta project</a></h2><p>
-	Contact:
-          Poul-Henning
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>The buf-junta project is underway, I am trying to bisect the code
-        such that we get a struct bufobj which is the handle and method
-        carrier for a buffer-cache object.  All vnodes contain a bufobj, but
-        as filesystems get migrated to GEOM backing, bufobj's will exist
-        which do not have an associated vnode.  The work is ongoing.</p>
-    <hr /><h2><a name="CAM-Lockdown" href="#CAM-Lockdown" id="CAM-Lockdown">CAM Lockdown</a></h2><p>
-	Contact:
-          Scott
-          Long
-         &lt;<a href="mailto:scottl@freebsd.org">scottl@freebsd.org</a>&gt;
-	</p>
-      <p>Not much coding has taken place on this lately, with the recent
-        focus being on refining the design.  We are currently investigating
-        per-CPU completion queues and threads in order to reduce locks and
-        increase concurrency.  Also reviewing the BSD/OS CAM lockdown to see
-        what ideas can be shared.  Work should hopefully puck back up in late
-        July.  Development is taking place in the FreeBSD Perforce repository
-        under the <tt>//depot/projects/scottl-camlock/...</tt> branch for now.</p>
-    <hr /><h2><a name="Cronyx-Adapters-Drivers" href="#Cronyx-Adapters-Drivers" id="Cronyx-Adapters-Drivers">Cronyx Adapters Drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cronyx.ru/hardware/wan.html" title="http://www.cronyx.ru/hardware/wan.html">Cronyx WAN Adapters.</a></td><td>
-	    URL: <a href="http://www.cronyx.ru/hardware/wan.html" title="Cronyx WAN Adapters.">http://www.cronyx.ru/hardware/wan.html</a></td></tr></table><p>
-	Contact:
-          Roman
-          Kurakin
-         &lt;<a href="mailto:rik@FreeBSD.org">rik@FreeBSD.org</a>&gt;
-	</p>
-      <p>cp(4) driver for Cronyx Tau-PCI was added. Cronyx Tau-PCI is family
-        of synchronous WAN adapters with various set of interfaces such as
-        V.35, RS-232, RS-530(449), X.21, E1, E3, T3, STS-1. This is a third
-        family of Cronyx adapters that is supported by FreeBSD now. Now all
-        three drivers cx(4), ctau(4) and cp(4) are on both major branches
-        (HEAD and RELENG_4).</p>
-      <p>Busdma conversion was recently finished. Current work is
-        concentrated on locking both for adapters drivers and for sppp (see
-        my other report for additional information).</p>
-    <hr /><h2><a name="EuroBSDCon-2004-registration-now-open" href="#EuroBSDCon-2004-registration-now-open" id="EuroBSDCon-2004-registration-now-open">EuroBSDCon 2004 registration now open</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon2004.de/" title="http://www.eurobsdcon2004.de/">EuroBSDCon 2004 official website</a></td><td>
-	    URL: <a href="http://www.eurobsdcon2004.de/" title="EuroBSDCon 2004 official website">http://www.eurobsdcon2004.de/</a></td></tr></table><p>
-	Contact:
-          Patrick M.
-          Hausen
-         &lt;<a href="mailto:hausen@punkt.de">hausen@punkt.de</a>&gt;
-	</p>
-      <p>Registration for EuroBSDCon 2004 taking place in Karlsruhe, Germany,
-        from Oct. 29th to 31st has just opened.  An early bird discount will
-        be offered to all registering until Aug. 15th. Please see the
-        conference website for details.</p>
-    <hr /><h2><a name="FreeBSD-Brazilian-Documentation-Project" href="#FreeBSD-Brazilian-Documentation-Project" id="FreeBSD-Brazilian-Documentation-Project">FreeBSD Brazilian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.fugspbr.org" title="http://doc.fugspbr.org"></a></td><td>
-	    URL: <a href="http://doc.fugspbr.org" title="">http://doc.fugspbr.org</a></td></tr><tr><td><a href="http://lists.fugspbr.org/listinfo.cgi/doc-fugspbr.org" title="http://lists.fugspbr.org/listinfo.cgi/doc-fugspbr.org"></a></td><td>
-	    URL: <a href="http://lists.fugspbr.org/listinfo.cgi/doc-fugspbr.org" title="">http://lists.fugspbr.org/listinfo.cgi/doc-fugspbr.org</a></td></tr><tr><td><a href="http://developer.berlios.de/projects/doc-br/" title="http://developer.berlios.de/projects/doc-br/"></a></td><td>
-	    URL: <a href="http://developer.berlios.de/projects/doc-br/" title="">http://developer.berlios.de/projects/doc-br/</a></td></tr></table><p>
-	Contact:
-          DOC-BR
-          Discussion List
-         &lt;<a href="mailto:doc@fugspbr.org">doc@fugspbr.org</a>&gt;
-	</p>
-      <p>The FreeBSD Brazilian Documentation Project is an effort of
-        the Brazilian FreeBSD Users Group (FUG-BR) to translate the
-        available documentation to pt_BR. We are proud to announce
-        that we've finished the Handbook and FDP Primer translation and
-        they are being revised. Both should be integrated to the FreeBSD
-        CVS repository shortly.</p>
-      <p>There are many other articles being translated and their status
-        can be checked at our website. If you want to help please
-        create an account at BerliOS, since our CVS repository is being
-        hosted there, and contact us through our mailing list. Any help is
-        welcome!</p>
-    <hr /><h2><a name="FreeBSD-Dutch-Documentation-Project" href="#FreeBSD-Dutch-Documentation-Project" id="FreeBSD-Dutch-Documentation-Project">FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.evilcoder.org/freebsd_html" title="http://www.evilcoder.org/freebsd_html">Preview html documentation</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd_html" title="Preview html documentation">http://www.evilcoder.org/freebsd_html</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd/handbook.tbz" title="http://www.evilcoder.org/freebsd/handbook.tbz">Preview documentation tree</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd/handbook.tbz" title="Preview documentation tree">http://www.evilcoder.org/freebsd/handbook.tbz</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd/html.tbz" title="http://www.evilcoder.org/freebsd/html.tbz">Preview html in in tbz</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd/html.tbz" title="Preview html in in tbz">http://www.evilcoder.org/freebsd/html.tbz</a></td></tr></table><p>
-	Contact:
-          Remko
-          Lodder
-         &lt;<a href="mailto:remko@elvandar.org">remko@elvandar.org</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation project is a ongoing project
-        translating the FreeBSD handbook {and others} to  the dutch
-        language. We are still on the look for translators and people
-        that are willing to check the current html documentation.
-        If you are interested, contact me at the email address shown
-        above. We currently are reading for some checkups and then
-        insert the first documents into the documentation tree.</p>
-    <hr /><h2><a name="FreeBSD-Handbook,-3rd-Edition,-Volume-II:-Administrator-Guide" href="#FreeBSD-Handbook,-3rd-Edition,-Volume-II:-Administrator-Guide" id="FreeBSD-Handbook,-3rd-Edition,-Volume-II:-Administrator-Guide">FreeBSD Handbook, 3rd Edition, Volume II: Administrator Guide</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/docproj/handbook3.html" title="http://www.freebsd.org/docproj/handbook3.html">FreeBSD Handbook 3rd Edition Task List.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/docproj/handbook3.html" title="FreeBSD Handbook 3rd Edition Task List.">http://www.freebsd.org/docproj/handbook3.html</a></td></tr></table><p>
-	Contact:
-          Murray
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Third Edition of the FreeBSD Handbook has been split
-        into two volumes.  The first volume, the User Guide, has been
-        published.  Work is progressing on the second volume.  The
-        following chapters are included in the second volume :
-        advanced-networking, network-servers, config, boot, cutting-edge,
-        disks, l10n, mac, mail, ppp-and-slip, security, serialcomms,
-        users, vinum, eresources, bibliography, mirrors.  Please see the
-        Task List for information about what work remains to be done.  In
-        addition to technical and grammatical review, a number of HTML
-        output assumptions in the document need to be corrected.</p>
-    <hr /><h2><a name="FreeBSD-ports-monitoring-system" href="#FreeBSD-ports-monitoring-system" id="FreeBSD-ports-monitoring-system">FreeBSD ports monitoring system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://portsmon.firepipe.net/index.html" title="http://portsmon.firepipe.net/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.firepipe.net/index.html" title="FreeBSD ports monitoring system">http://portsmon.firepipe.net/index.html</a></td></tr></table><p>
-	Contact:
-          Mark
-          Linimon
-         &lt;<a href="mailto:linimon_at_lonesome_dot_com">linimon_at_lonesome_dot_com</a>&gt;
-	</p>
-      <p>The system continues to function well.  The accuracy of the
-        automatic classification algorithm has been improved by
-        assigning a higher priority to port names found in pieces of
-        Makefiles.</p>
-      <p>Several bugs had to be fixed due to the transition from bento to
-        pointyhat.  For about two weeks the URLs to the build errors
-        were wrong.  This has now been corrected (but note that some of the
-        pointyhat summary pages themselves still show the broken
-        links.)</p>
-      <p>A report was added to show only PRs in the 'feedback' state, so
-        that committers can focus on maintainer and/or responsible timeouts.
-        (As a reminder, the policy is 2 weeks).  Another report on 'ports
-        that are in ports/MOVED, but still exist' has also been added to the
-        Anomalies page.  Sometimes these are actual errors but not always.</p>
-      <p>Here are my latest observations about the trends in ports PRs:</p>
-      <ul>
-        <li>We were (very briefly) down to 650 ports PRs.  From looking
-          at the graphs, this appears to be the lowest number since 2001.
-          This is despite the fact that between the two time periods the
-          number of ports had increased 70%.</li>
-        <li>We have made a little bit of progress on the number of PRs
-          which apply to existing ports and have been assigned to a FreeBSD
-          committer, from 400 to around 350.  This is partly due to some
-          committers going through the database, putting old PRs into the
-          'feedback' state, and then later invoking the 'maintainer timeout'
-          rule mentioned above.  (In some cases the PRs are now too old to
-          still apply, and those are just closed.)</li>
-        <li>A few maintainers are currently responsible for one-third of
-          those 350.  Please, if you feel that you are over committed,
-          consider asking for new volunteers to maintain these ports.</li>
-        <li>In terms of build errors, there is some new breakage from
-          the preliminary testing with gcc3.4, which is even stricter with
-          respect to the code it will accept than was gcc3.3.  Many of these
-          errors are shown as 'unknown' by the classification script.  I
-          have submitted a patch to fix this.</li>
-        <li>The majority of the build errors are still due to compilation
-          problems, primarily from the gcc upgrades.  Since FreeBSD tends to
-          be at the forefront of gcc adaptation, this is to be expected, but
-          IMHO we should really try to fix as many of these as possible
-          before 5.3 is released.</li>
-        <li>The next highest number of build errors are caused by code
-          that does not build on our 64-bit architectures due to the
-          assumption that "all the world's a PC".
-          <a href="http://portsmon.firepipe.net/ploticus/uniqueerrorcounts.html" shape="rect">
-          Here is the entire list</a>; the individual bars are
-          clickable.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-profile.sh" href="#FreeBSD-profile.sh" id="FreeBSD-profile.sh">FreeBSD profile.sh</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://projects.fsck.ch/profile/" title="https://projects.fsck.ch/profile/"></a></td><td>
-	    URL: <a href="https://projects.fsck.ch/profile/" title="">https://projects.fsck.ch/profile/</a></td></tr></table><p>
-	Contact:
-          Tobias
-
-          Roth
-         &lt;<a href="mailto:ports@fsck.ch">ports@fsck.ch</a>&gt;
-	</p>
-      <p>FreeBSD profile.sh is an enhancement to the FreeBSD 5 rcng boot
-        system, targeted at laptops. One can configure multiple network
-        environments (eg, home, work, university). After this initial
-        configuration, the laptop detects automatically in what environment
-        it is started and configures itself accordingly. Not only network
-        settings, but almost everything from under /etc can be configured
-        per environment.  It is also possible to suspend the machine in one
-        environment and wake it up in a different one, and reconfiguration
-        will happen automatically.</p>
-    <hr /><h2><a name="FreeBSD/arm" href="#FreeBSD/arm" id="FreeBSD/arm">FreeBSD/arm</a></h2><p>
-	Contact:
-          Olivier
-          Houchard
-         &lt;<a href="mailto:cognet@FreeBSD.org">cognet@FreeBSD.org</a>&gt;
-	</p>
-      Not much to report, Xscale support is in progress, and should
-      boot at least single user really soon on an Intel IQ31244
-      <p>Evaluation board.</p>
-    <hr /><h2><a name="FreeBSD/MIPS-Status-Report" href="#FreeBSD/MIPS-Status-Report" id="FreeBSD/MIPS-Status-Report">FreeBSD/MIPS Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/mips/" title="http://www.FreeBSD.org/projects/mips/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/mips/" title="">http://www.FreeBSD.org/projects/mips/</a></td></tr><tr><td><a href="http://www.mdstud.chalmers.se/~md1gavan/mips64emul/" title="http://www.mdstud.chalmers.se/~md1gavan/mips64emul/">mips64emul</a></td><td>
-	    URL: <a href="http://www.mdstud.chalmers.se/~md1gavan/mips64emul/" title="mips64emul">http://www.mdstud.chalmers.se/~md1gavan/mips64emul/</a></td></tr></table><p>
-	Contact:
-          Juli
-          Mallett
-         &lt;<a href="mailto:jmallett@FreeBSD.org">jmallett@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the past two months, opportunities to perform a good chunk of
-        work on FreeBSD/MIPS have arisen and significant issues with
-        context switching, clocks, interrupts, and kernel virtual memory
-        have been resolved.  A number of issues with caches were fixed,
-        however those are far from complete and at last check, there
-        were issues when running cached which would prevent booting
-        sometimes.
-        Due to toolchain issues in progress, current kernels are no
-        longer bootable on real hardware.</p>
-      <p>A 64-bit MIPS emulator has arisen giving the ability to test and
-        debug in an emulator, and much testing has taken place in it.
-        It has been added to the FreeBSD ports tree, and the port will be
-        actively tracking the main codebase as possible.  In general,
-        FreeBSD/MIPS kernels should run fine in it.</p>
-      <p>Before toolchain and cache issues, the first kernel threads would
-        run, busses and some devices would attach, and the system would
-        boot to a mountroot prompt.</p>
-    <hr /><h2><a name="HP-Network-Scanjet-5" href="#HP-Network-Scanjet-5" id="HP-Network-Scanjet-5">HP Network Scanjet 5</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://berklix.com/scanjet/" title="http://berklix.com/scanjet/">HP Network Scanjet 5 Running FreeBSD Inside</a></td><td>
-	    URL: <a href="http://berklix.com/scanjet/" title="HP Network Scanjet 5 Running FreeBSD Inside">http://berklix.com/scanjet/</a></td></tr></table><p>
-	Contact:
-          Julian
-          Stacey
-         &lt;<a href="mailto:jhs@FreeBSD.org">jhs@FreeBSD.org</a>&gt;
-	</p>
-      <p>HP Network Scanjet 5 can unobtrusively run FreeBSD <i>inside</i> the
-        scanner.  Those who miss their Unix at work can have a FreeBSD box,
-        un-noticed &amp; un-challenged by blinkered managers who block any
-        non Microsoft PC in the building.  http://berklix.com/scanjet/</p>
-    <hr /><h2><a name="i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing" href="#i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing" id="i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing">i386 Interrupt Code &amp; PCI Interrupt Routing</a></h2><p>
-	Contact:
-          John
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for programming the polarity and trigger mode of
-        interrupt sources at runtime was added.  This includes a
-        mini-driver for the ELCR register used to control the
-        configuration for ISA and EISA interrupts.  The atpic driver
-        reprograms the ELCR as necessary, while the apic driver
-        reprograms the interrupt pin associated with an interrupt
-        source as necessary.  The information about which
-        configuration to use mostly comes from ACPI.  However,
-        non-ACPI systems also force any ISA interrupts used to route
-        PCI interrupts to use active-low polarity and level
-        trigger.</p>
-
-      <p>Support for suspend and resume on i386 was also slightly
-        improved.  Suspend and resume support was added to the ELCR,
-        $PIR, and apic drivers.</p>
-
-      <p>The ACPI PCI-PCI bridge driver was fixed to fall back to the
-        PCI-PCI bridge swizzle method for routing interrupts when a
-        routing table was not provided by the BIOS.</p>
-
-      <p>Mixed mode can now be disabled or enabled at boot time via a
-        loader tunable.</p>
-    <hr /><h2><a name="Improved-Multibyte/Wide-Character-Support" href="#Improved-Multibyte/Wide-Character-Support" id="Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></h2><p>
-	Contact:
-          Tim
-          Robbins
-         &lt;<a href="mailto:tjr@FreeBSD.org">tjr@FreeBSD.org</a>&gt;
-	</p>
-      <p>Many more text-processing utilities in the FreeBSD base system have
-        been updated to work with multibyte characters, including comm, cut,
-        expand, fold, join, paste, unexpand, and uniq. New versions of GNU
-        grep and GNU sort (from coreutils) have been imported, together with
-        multibyte support patches from developers at IBM and Red Hat.</p>
-      <p>Future work will focus on modifying the regular expression
-        functions to work with multibyte characters, improving performance
-        of the C library routines, and updating the remaining utilities (sed
-        and tr are two important ones still remaining).</p>
-    <hr /><h2><a name="IPFilter-Upgraded-to-3.4.35" href="#IPFilter-Upgraded-to-3.4.35" id="IPFilter-Upgraded-to-3.4.35">IPFilter Upgraded to 3.4.35</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://coombs.anu.edu.au/~avalon/ip-filter.html" title="http://coombs.anu.edu.au/~avalon/ip-filter.html">IPFilter home page</a></td><td>
-	    URL: <a href="http://coombs.anu.edu.au/~avalon/ip-filter.html" title="IPFilter home page">http://coombs.anu.edu.au/~avalon/ip-filter.html</a></td></tr></table><p>
-	Contact:
-          Darren Reed
-         &lt;<a href="mailto:darrenr@FreeBSD.org">darrenr@FreeBSD.org</a>&gt;
-	</p>
-      <p>IPFilter has been upgraded in both FreeBSD-current and 4-STABLE
-        (post 4.10) from version 3.4.31 to 3.4.35.</p>
-    <hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freebsd.kde.org" title="http://freebsd.kde.org"></a></td><td>
-	    URL: <a href="http://freebsd.kde.org" title="">http://freebsd.kde.org</a></td></tr></table><p>
-	Contact:
-          Michael
-          Nottebrock
-         &lt;<a href="mailto:lofi@FreeBSD.org">lofi@FreeBSD.org</a>&gt;
-	</p>
-      <p>The work on converting the build switches/OPTIONS
-        currently present in the ports of the main KDE modules into
-        separate ports in order to make packages available for the
-        software/features they provide is progressing. Porting of
-        KOffice 1.3.2 are nearly completed. The Swedish FreeBSD
-        snapshot server <a href="http://snapshots.se.freebsd.org" shape="rect">
-	http://snapshots.se.freebsd.org</a>,
-        operated and maintained by members of the KDE/FreeBSD team,
-        is back up and running at full steam. Additional amd64
-        hardware has been added and amd64 snapshots will be available
-        soon.</p>
-    <hr /><h2><a name="kgi4BSD" href="#kgi4BSD" id="kgi4BSD">kgi4BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="http://www.FreeBSD.org/~nsouch/kgi4BSD">Project URL</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~nsouch/kgi4BSD" title="Project URL">http://www.FreeBSD.org/~nsouch/kgi4BSD</a></td></tr></table><p>
-	Contact:
-          Nicholas
-          Souchu
-         &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-      <p>KGI is going slowly but surely. The port of the KGI/Linux accel to
-        FreeBSD is in progress. It's no more than a double buffering API for
-        graphic command passing to the HW engine.</p>
-
-      <p>Most of the work in the past months was about console management
-        and more especially dual head console. Otherwise a new driver
-        building tree is now ready to compile Linux and FreeBSD drivers in
-        the same tree.</p>
-
-      <p>Documentation about KGI design is in progress.</p>
-    <hr /><h2><a name="Low-overhead-performance-monitoring-for-FreeBSD" href="#Low-overhead-performance-monitoring-for-FreeBSD" id="Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement/">A best-in-class performance monitoring system for FreeBSD built over the hardware performance monitoring facilities of modern CPUs.</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="A best-in-class performance monitoring system for FreeBSD built over the hardware performance monitoring facilities of modern CPUs.">http://people.freebsd.org/~jkoshy/projects/perf-measurement/</a></td></tr></table><p>
-	Contact:
-          Joseph
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>The current design attempts to support both per-process and
-        system-wide statistical profiling and per-process "virtual"
-        performance counters.  The userland API libpmc(3) is somewhat
-        stable now, but the kernel module's design is being redone to
-        handle MP better.  Initial development is targeting the AMD
-        Athlon CPUs, but the intent is to support all the CPUs that
-        FreeBSD runs on.</p>
-
-      <p>An early prototype is available under Perforce [under
-        //depot/user/jkoshy/projects/pmc/].</p>
-    <hr /><h2><a name="Network-interface-naming-changes" href="#Network-interface-naming-changes" id="Network-interface-naming-changes">Network interface naming changes</a></h2><p>
-	Contact:
-          Brooks
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>An enhanced network interface cloning API has been committed.  It
-        allows interfaces to support more complex names then the current
-        <code>name#</code> style.  This functionality has been used to
-        enable interesting cloners like auto-configuring vlan interfaces.
-        Other features include locking of cloner structures and the ability
-        of drivers to reject destroy requests.</p>
-      <p>Work on userland support for this functionality is ongoing.</p>
-    <hr /><h2><a name="Network-Stack-Locking" href="#Network-Stack-Locking" id="Network-Stack-Locking">Network Stack Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.watson.org/~robert/freebsd/netperf/" title="http://www.watson.org/~robert/freebsd/netperf/">Netperf Web Page</a></td><td>
-	    URL: <a href="http://www.watson.org/~robert/freebsd/netperf/" title="Netperf Web Page">http://www.watson.org/~robert/freebsd/netperf/</a></td></tr></table><p>
-	Contact:
-          Robert
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is aimed at converting the FreeBSD network stack from
-        running under the single Giant kernel lock to permitting it to
-        run in a fully parallel manner on multiple CPUs (i.e., a fully
-        threaded network stack).  This will improve performance/latency
-        through reentrancy and preemption on single-processor machines, and
-        also on multi-processor machines by permitting real parallelism in
-        the processing of network traffic. As of FreeBSD 5.2, it was
-        possible to run low level network functions, as well as the IP
-        filtering and forwarding plane, without the Giant lock, as well as
-        "process to completion" in the interrupt handler.  This permitted
-        both inbound and outbound traffic to run in parallel across
-        multiple interfaces and CPUs.</p>
-
-      <p>Work continues to improve the maturity and completeness of the
-        locking (and performance) of the network stack for 5.3. The network
-        stack development branch has been updated to the latest CVS HEAD,
-        as well as the following and more.  Many but not all of these
-        changes have been merged to the FreeBSD CVS tree as of the writing
-        of this report.  Complete details and more minor changes are
-        documented in the README file on the netperf web page.</p>
-
-      <ul>
-        <li>Addition of hard-coded WITNESS lock orders for socket-related
-          locks, route locks, interface locks, file descriptor locks,
-          SLIP, and PCB locks for various protocols (UDP, TCP, UNIX
-          domain sockets).  (Merged)</li>
-        <li>Modified MAC Framework to use inpcbs as the source for mbuf
-          labels rather than reaching up to the socket layer, avoiding the
-          additional acquisition of socket locks.  Locked access to
-          so_label and so_peerlabel using the socket lock throughout;
-          assert socket lock in the MAC Framework where depended on.  MAC
-          Framework now makes a copy of the socket label before
-          externalizing to prevent a copyout while holding the label lock
-          (and potentially seeing an inconsistent label). (Merged)</li>
-        <li>Extensive annotation of locking state throughout the network
-          stack, especially relating to sockets.</li>
-        <li>Several locking fixes for ng_base.c, the basic Netgraph
-          infrastructure. (Merged)</li>
-        <li>Global accept filter list locking, especially during registration.
-          (Partially merged)</li>
-        <li>Revise locking in socket state transition helpers, such as
-          soisconnecting(), soisconnected(), etc, to simplify lock
-          handling. (Merged)</li>
-        <li>Fix bugs in netatalk DDP locking, merge all netatalk locking to
-          CVS. (Merged)</li>
-        <li>soref() socket locking assertions and associated fixes.
-          (Merged)</li>
-        <li>Fifofs now uses its own mutex instead of the vnode interlock to
-          synchronize fifo operations, avoiding lock order issues with
-          socket buffer locking. (Merged)</li>
-        <li>Cleanup of locking related to file descriptor close and Giant
-          requirements.  Experimentation with reducing locking here.</li>
-        <li>Review and fix several instances of socket locking in the TCP
-          code.  (Merged)</li>
-        <li>NFS server locking merged to FreeBSD CVS.  (Merged)</li>
-        <li>Accept locking merged to rwatson_netperf, and to FreeBSD CVS.
-          A new global mutex, accept_mtx, now protects all socket related
-          accept queue and state fields (SS_COMP, SS_INCOMP), and flags
-          relating to accept are moved from the generic so_state field to
-          so_qstate.  accept1() rearranged, as with sonewconn() as a result,
-          and a file descriptor leak fixed.  Close a variety of races in
-          socket referencing during accept.  soabort() and other partially
-          connected socket related functions updated to take locking into
-          account.  (Merged)</li>
-        <li>Issue associated with non-atomic setting of SS_NBIO in fifofs
-          resolved by adding MSG_NBIO.  (Merged)</li>
-        <li>Several flags from so_state moved to sb_state so they can be
-          locked properly using the socket buffer mutex.  (Merged)</li>
-        <li>Socket locks are now not held over calls into the protocol
-          preventing many lock order issues between socket and protocol
-          locks, and avoiding a substantial amount of conditional locking.
-          (Merged)</li>
-        <li>mbuma, the UMA-based mbuf allocator, is merged to CVS.  This
-          reduces the kernel to one widely used memory allocator, improves
-          performance, and allows memory from mbufs to be reclaimed and
-          reused for other types of storage when pressure lowers.
-          (Merged)</li>
-        <li>sb_flags now properly locked.  (Merged)</li>
-        <li>Global MAC label ifnet lock introduced to protect labels on
-          network interfaces.  (Merged)</li>
-        <li>Rewrites of parts of soreceive() and sosend() to improve
-          MP safety merged to CVS, including modifications to make sure
-          socket buffer cache state is consistent when locks are released.
-          sockbuf_pushsync() added to guarantee consistency of cached
-          pointers.  (Merged)</li>
-        <li>UNIX domain socket locking revised to use a subsystem lock due
-          to inconsistencies in lock order and inconsistent coverage ofunpcb
-          fields.  Cleanup of global variable locking in UNIX domain
-          sockets, Giant handling when entering VFS.  All UNIX domain socket
-          locking merged to CVS.  (Merged)</li>
-        <li>netisr dispatch introduced in the routing code such that routing
-          socket message delivery is performed asynchronously from routing
-          events to avoid lock order issues.  (Merged)</li>
-        <li>IGMP and multicast locking merged to CVS.  (Merged)</li>
-        <li>Cleanup of lasting recursive Giant acquisition left over from
-          forwarding/bridging plane only locking.  (Merged)</li>
-        <li>ALTQ imported into the FreeBSD in a locked state.  (Merged)</li>
-        <li>Conditional locking in sbdrop(), sbdroprecord(), sbrelease(),
-          sbflush(), spappend(), sbappendstream(), sbappendrecord(),
-          sbinsertoob(), sbappendaddr(), sbappendcontrol() eliminated.
-          (Merged)</li>
-        <li>Some cleanup of IP stack management ioctls and lock order issues.
-          (Merged)</li>
-        <li>Cleanup and annotation of sorflush() use of a temporary stack held
-          socket buffer during flush.  (Merged)</li>
-        <li>Substantial cleanup of socket wakeup mechanisms to drop locks in
-          advance of wakeup, avoid holding locks over upcalls, and
-          assertions of proper lock state.  (Merged)</li>
-        <li>With the integration of revised ifnet cloning, cloning data
-          structures are now better locked.  (Merged)</li>
-        <li>Socket locking for portalfs.  (Merged)</li>
-        <li>Global so_global_mtx introduced to protect generation numbers and
-          socket counts.  (Merged)</li>
-        <li>KAME IPSEC and FAST_IPSEC now use rawcb_mtx to protect raw socket
-          list integration.  More work required here.  (Merged)</li>
-        <li>Socket locking around SO_SNDLOWAT and SO_RCVLOWAT.  (Merged)</li>
-        <li>soreserve() and sbreserve() reformulation to improve locking and
-          consistency.  Similar cleanup in the use of reservation
-          functions in tcp_mss().  (Merged)</li>
-        <li>Locking cost reduction in sbappend*().  (Merged)</li>
-        <li>Global locking for a number of Netgraph modules, including
-          ng_iface, ng_ppp, ng_socket, ng_pppoe, ng_frame_relay, ng_tty,
-          ng_eiface.  (Merged)</li>
-        <li>IPv6 inpcb locking.  Resulting cleanup of inpcb locking
-          assertions, and enabling of inpcb locking assertions by default
-          even with IPv6 compiled in.</li>
-        <li>if_xl now MPSAFE.  (Merged)</li>
-        <li>soreceive() non-inline OOB support placed in its own function.
-          (Merged)</li>
-        <li>NFS client socket locking.  (Merged)</li>
-        <li>SLIP now uses a asynchronous task queue to prevent Giant-free
-          entrance of the TTY code.</li>
-        <li>E-mail sent to current@ providing Giant-free operation guidelines
-          and details.</li>
-      </ul>
-    <hr /><h2><a name="Packet-Filter---pf" href="#Packet-Filter---pf" id="Packet-Filter---pf">Packet Filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.benzedrine.cx/pf.html" title="http://www.benzedrine.cx/pf.html">The pf homepage.</a></td><td>
-	    URL: <a href="http://www.benzedrine.cx/pf.html" title="The pf homepage.">http://www.benzedrine.cx/pf.html</a></td></tr></table><p>
-	Contact:
-          Max
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Daniel
-          Hartmeier
-         &lt;<a href="mailto:dhartmei@FreeBSD.org">dhartmei@FreeBSD.org</a>&gt;
-	</p>
-      <p>We imported pf as of OpenBSD 3.5 stable on June, 17th which will be
-        the base for 5-STABLE pf (according to the current schedule).  The
-        most important improvement in this release is the new interface
-        handling which makes it possible to write pf rule sets for
-        hot-pluggable devices and pseudo cloning devices, before they exist.
-        The import of the ALTQ framework enabled us to finally provide the
-        related pf functions as well.</p>
-
-      <p>Before 5-STABLE we will import some bug fixes from OpenBSD-current,
-        which have not been merged to their stable branch, as well as some
-        FreeBSD specific features. The planned ALTQ API make-over will also
-        affect pf.</p>
-
-      <p>We are (desperately) looking for non-manpage documentation for
-        FreeBSD pf and somebody to write it. Few things have changed
-        so a port of the excellent "PF FAQ" on the OpenBSD homepage should
-        be fitting. There are, however, a couple of points that need
-        conversion.  A simple tutorial how to setup a NAT gateway with pf
-        would also help.  The in-kernel NAT engine is very easy to use, we
-        should tell people about this alternative. This is even more true
-        since the pf module now plugs into GENERIC without modifications.</p>
-    <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-          Peter
-          Grehan
-         &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>The port has been moving along steadily. There have been
-        reports of buildworld running natively. Works is almost complete
-        on make release so there will be bootable CD images in the near
-        future.</p>
-    <hr /><h2><a name="Project-Mini-Evil" href="#Project-Mini-Evil" id="Project-Mini-Evil">Project Mini-Evil</a></h2><p>
-	Contact:
-          Scott
-          Long
-         &lt;<a href="mailto:scottl@freebsd.org">scottl@freebsd.org</a>&gt;
-	</p>
-      <p>Project Mini-Evil is an attempt to extend Bill Paul's 'Project Evil'
-        Windows NDIS wrapper layer to the SCSI MiniPort and StorePort layers.
-        While drivers exist for most storage controllers that are on the
-        market today, many companies are integrating software RAID into their
-        products but not providing any source code or design specs.  Instead
-        of constantly reverse-engineering these raid layers and attempting to
-        shoehorn them into the ata-raid driver, Project Mini-Evil will run
-        the Windows drivers directly.  It will hopefully also run most any
-        SCSI/ATA/RAID drivers that conform to the SCSI Miniport or Storeport
-        specification.</p>
-      <p>Work on this project is split between making the NDIS wrapper code
-        more general and implementing the new APIs.  Development is taking
-        place in the FreeBSD Perforce repository under the
-        //depot/projects/sonofevil/... branch.</p>
-    <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          John
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Not a lot happened on the SMPng front outside of the work on
-        locking the network stack (which is a large amount of work).
-        The priorities of the various software interrupt threads were
-        corrected and locking for taskqueues was improved.  The return
-        value of the sema_timedwait() function was adjusted to be more
-        consistent with cv_timedwait().  A small fix was made to the
-        sleepqueue code to shorten the amount of time that a
-        sleepqueue chain lock is held when waking up threads.  Some
-        simple debug code for profiling the hash tables used in the
-        sleep queue and turnstile code was added.  This will allow
-        developers to measure the impact of any tweaks to the hash
-        table sizes or the hash algorithm.</p>
-    <hr /><h2><a name="Sync-protocols-(Netgraph-and-SPPP)" href="#Sync-protocols-(Netgraph-and-SPPP)" id="Sync-protocols-(Netgraph-and-SPPP)">Sync protocols (Netgraph and SPPP)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/~rik" title="http://www.freebsd.org/~rik">Current code, ideas, problems.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/~rik" title="Current code, ideas, problems.">http://www.freebsd.org/~rik</a></td></tr></table><p>
-	Contact:
-          Roman
-          Kurakin
-         &lt;<a href="mailto:rik@FreeBSD.org">rik@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently I work on two directions: if_spppfr.c and sppp locking
-        (on behalf of netperf). At the moment of writing this sppp locking
-        is not ready yet. But it would be ready in couple of days. Also you
-        may find as a part of this work some user space fixes for rwatson
-        netperf code (Only that I was able to catch while world compilation.
-        If you know some others let me know and I'll try to fix them
-        too).</p>
-
-      <p>Since sppp code is quite big and state machine is very complicated,
-        it would be difficult to test all code paths. I will glad to get
-        any help in testing all this stuff. More tester more probability to
-        test all possible cases.</p>
-
-      <p>Work on FRF.12 (ng_frf12) is frozen since of low interest and
-        lack of time. Current state of stable code: support of FRF.12
-        End-to-End fragmentation. Support of FRF.12 Interface (UNI and NNI)
-        fragmentation is not tested.</p>
-    <hr /><h2><a name="TTY-subsystem-realignment" href="#TTY-subsystem-realignment" id="TTY-subsystem-realignment">TTY subsystem realignment</a></h2><p>
-	Contact:
-          Poul-Henning
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>An effort to get the tty subsystem out from under Giant has
-        morphed into an more general effort to eliminate a lot of
-        code which have been improperly copy &amp; pasted into device
-        drivers.  In an ideal world, tty drivers would never get
-        near a cdevsw, but since some drivers are more than just
-        tty drivers (for instance sync) a more sensible compromise
-        must be reached.  The work is ongoing.</p>
-    <hr /><h2><a name="Various-GEOM-classes-and-geom(8)-utility" href="#Various-GEOM-classes-and-geom(8)-utility" id="Various-GEOM-classes-and-geom(8)-utility">Various GEOM classes and geom(8) utility</a></h2><p>
-	Contact:
-          Pawel Jakub
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>I'm working on various GEOM classes. Some of them are already
-        committed and ready for use (GATE, CONCAT, STRIPE, LABEL, NOP). The
-        MIRROR class is finished in 90% and will be committed in very near
-        future.  Next I want to work on RAID3 and RAID5 implementations.
-        Userland utility to control GEOM classes (geom(8)) is already in
-        the tree.</p>
-    <hr /><h2><a name="VuXML-and-portaudit" href="#VuXML-and-portaudit" id="VuXML-and-portaudit">VuXML and portaudit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.vuxml.org" title="http://www.vuxml.org">VuXML DTD and more information</a></td><td>
-	    URL: <a href="http://www.vuxml.org" title="VuXML DTD and more information">http://www.vuxml.org</a></td></tr><tr><td><a href="http://vuxml.FreeBSD.org" title="http://vuxml.FreeBSD.org">Rendered contents of FreeBSD VuXML</a></td><td>
-	    URL: <a href="http://vuxml.FreeBSD.org" title="Rendered contents of FreeBSD VuXML">http://vuxml.FreeBSD.org</a></td></tr><tr><td><a href="http://www.freebsd.org/ports/portaudit/" title="http://www.freebsd.org/ports/portaudit/">Rendered version of portaudit.txt</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/portaudit/" title="Rendered version of portaudit.txt">http://www.freebsd.org/ports/portaudit/</a></td></tr></table><p>
-	Contact:
-          Tom
-          Rhodes
-         &lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;
-	</p>
-      <p>The portaudit utility is currently an add-on to FreeBSD
-        designed to give administrators and users a heads up
-        with regards to security vulnerabilities in third
-        party software.  The VuXML database keeps a record
-        of these security vulnerabilities along with internal
-        security holes.  When installed, the portaudit utility
-        periodically downloads a database with known issues and
-        checks all installed ports or packages against it; should
-        it find vulnerable software installed the administrator
-        or user is notified during the daily run output of the
-        periodic scripts.</p>
-
-      <p>These utilities are considered to be of production
-        quality and discussion is taking place over whether or not
-        they should be included as part of the base system.  All
-        ports committers are urged to add entries when when a
-        vulnerability is discovered; any questions may be sent to
-        eik@ or myself.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2004-07-2004-12.html b/website/content/en/status/report-2004-07-2004-12.html
deleted file mode 100644
index f855dc9377..0000000000
--- a/website/content/en/status/report-2004-07-2004-12.html
+++ /dev/null
@@ -1,1636 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" src="../../layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The FreeBSD status report is back again after another small break.  The
-    second half of 2004 was incredibly busy; FreeBSD 5.3 was released, the
-    6-CURRENT development branch started, and EuroBSDCon 2004 was a huge
-    success, just to name a few events.  This report is packed with an
-    impressive 44 submissions, the most of any report ever!</p><p>It's also my pleasure to welcome Max Laier and Tom Rhodes to the status
-    report team.  They kindly volunteered to help keep the reports on time
-    and help improve their quality.  Max in particular is responsible for
-    the reports being divided up into topics for easier browsing.  Many
-    thanks to both for their help!</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Common-Address-Redundancy-Protocol---CARP">Common Address Redundancy Protocol - CARP</a></li><li><a href="#Dingo-Monthly-Report">Dingo Monthly Report</a></li><li><a href="#FreeBSD-profile.sh">FreeBSD profile.sh</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#FreeSBIE-Status-Report">FreeSBIE Status Report</a></li><li><a href="#Funded-FreeBSD-kernel-development">Funded FreeBSD kernel development</a></li><li><a href="#Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></li><li><a href="#Project-Frenzy-(FreeBSD-based-Live-CD)">Project Frenzy (FreeBSD-based Live-CD)</a></li><li><a href="#Secure-Updating">Secure Updating</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Hardware-Notes">Hardware Notes</a></li><li><a href="#The-FreeBSD-Dutch-Documentation-Team">The FreeBSD Dutch Documentation Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ATA-Driver-Status-Report">ATA Driver Status Report</a></li><li><a href="#CPU-Cache-Prefetching">CPU Cache Prefetching</a></li><li><a href="#i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing">i386 Interrupt Code &amp; PCI Interrupt Routing</a></li><li><a href="#kgi4BSD">kgi4BSD</a></li><li><a href="#Layer-2-PFIL_HOOKS">Layer 2 PFIL_HOOKS</a></li><li><a href="#Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></li><li><a href="#Move-ARP-out-of-routing-table">Move ARP out of routing table</a></li><li><a href="#Network-Stack-Locking">Network Stack Locking</a></li><li><a href="#New-Modular-Input-Device-Layer">New Modular Input Device Layer</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#Sync-Protocols-(SPPP-and-NETGRAPH)">Sync Protocols (SPPP and NETGRAPH)</a></li><li><a href="#TCP-Cleanup-and-Optimizations">TCP Cleanup and Optimizations</a></li><li><a href="#TCP-Reassembly-Rewrite-and-Optimization">TCP Reassembly Rewrite and Optimization</a></li><li><a href="#TTCPv2:-Transactional-TCP-version-2">TTCPv2: Transactional TCP version 2</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Xen">FreeBSD on Xen</a></li><li><a href="#FreeBSD/arm-status-report">FreeBSD/arm status report</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-GNOME-Project-Status-Report">FreeBSD GNOME Project Status Report</a></li><li><a href="#OpenOffice.org-port-status">OpenOffice.org port status</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#ALTQ">ALTQ</a></li><li><a href="#Cronyx-Adapters-Drivers">Cronyx Adapters Drivers</a></li><li><a href="#OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#EuroBSDCon-2004-submitted-papers-are-online">EuroBSDCon 2004 submitted papers are online</a></li><li><a href="#EuroBSDCon-2005---Basel-/-Switzerland">EuroBSDCon 2005 - Basel / Switzerland</a></li><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#FreeBSD-Source-Repository-Mirror-for-svn/svk">FreeBSD Source Repository Mirror for svn/svk</a></li><li><a href="#Wiki-with-new-software">Wiki with new software</a></li></ul><ul><li><a href="#Atheros-Wireless-Support">Atheros Wireless Support</a></li><li><a href="#ifconfig-Overhaul">ifconfig Overhaul</a></li><li><a href="#New-DHCP-Client">New DHCP Client</a></li><li><a href="#Wireless-Networking-Support">Wireless Networking Support</a></li></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Common-Address-Redundancy-Protocol---CARP" href="#Common-Address-Redundancy-Protocol---CARP" id="Common-Address-Redundancy-Protocol---CARP">Common Address Redundancy Protocol - CARP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~mlaier/CARP/" title="http://people.freebsd.org/~mlaier/CARP/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mlaier/CARP/" title="">http://people.freebsd.org/~mlaier/CARP/</a></td></tr></table><p>
-	Contact: 
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p>
-      <p>CARP is an alternative to VRRP. In contrast to VRRP it has full
-      support for IPv6 and uses crypto to protect the advertisements. It
-      was developed by OpenBSD due to concerns that the HSRP patent might
-      cover VRRP and CISCO might defend its patent. CARP has, since then,
-      improved a lot over VRRP.</p>
-
-      <p>CARP is implemented as an in-kernel multicast protocol and
-      displays itself as a pseudo interface to the user. This makes
-      configuration and administration very simple. CARP also
-      incorporates MAC based load-balancing.</p>
-
-      <p>Patches for RELENG_5 and recent HEAD are available from the URL
-      above. I plan to import these patches in the course of the next two
-      to four month. RELENG_5 has all necessary ABI to support CARP and I
-      might MFC it for release 5.4 or 5.5 - depending how well the HEAD
-      import goes.</p>
-    <h3>Open tasks:</h3><ol><li>Please test and send feedback!</li><li>Write documentation.</li><li>Import newest OpenBSD changes.</li></ol><hr /><h2><a name="Dingo-Monthly-Report" href="#Dingo-Monthly-Report" id="Dingo-Monthly-Report">Dingo Monthly Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/projects/dingo/index.html" title="http://www.freebsd.org/projects/dingo/index.html">Network Stack Cleanup Project.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/dingo/index.html" title="Network Stack Cleanup Project.">http://www.freebsd.org/projects/dingo/index.html</a></td></tr></table><p>
-	Contact: 
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the last month we set up the project page noted above and
-      also created a p4 branch for those of us who use p4 to do work
-      outside of CVS.</p>
-    <hr /><h2><a name="FreeBSD-profile.sh" href="#FreeBSD-profile.sh" id="FreeBSD-profile.sh">FreeBSD profile.sh</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://projects.fsck.ch/profile" title="https://projects.fsck.ch/profile">FreeBSD profile.sh site</a></td><td>
-	    URL: <a href="https://projects.fsck.ch/profile" title="FreeBSD profile.sh site">https://projects.fsck.ch/profile</a></td></tr></table><p>
-	Contact: 
-          Tobias
-
-          Roth
-         &lt;<a href="mailto:ports@fsck.ch">ports@fsck.ch</a>&gt;
-	</p>
-      <p>FreeBSD profile.sh is targeted at laptops. It allows to define
-      multiple network environments (eg, home, work), and will then
-      detect in which environment the laptop is started and configure it
-      accordingly. Almost everything from under /etc can be configured
-      per environment, and only the overrides to the default /etc have to
-      be defined. Suspending in one environment and resuming in a
-      different one is also supported.</p>
-
-      <p>Proper integration into the acpi/apm and several small
-      improvements are underway. More testing with different system
-      configurations is needed.</p>
-    <hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng" title="http://www.FreeBSD.org/releng"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng" title="">http://www.FreeBSD.org/releng</a></td></tr></table><p>
-	Contact: 
-          Scott
-
-          Long
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>At long last, FreeBSD 5.3 was released in November of 2004. This
-      marked the start of the RELENG_5/5-STABLE branch and the beginning
-      of the 6-CURRENT development branch. Many thanks to the tireless
-      efforts of the FreeBSD developer and user community for making this
-      release a success.</p>
-
-      <p>FreeBSD 4.11 release engineering is also now in progress. This
-      will be the final release from the 4.x series and is mainly
-      incremental bug fixes and a handful of feature additions. Of note
-      is that the IBM ServeRAID 'IPS' driver is now supported on 4.x and
-      will be included in this release, and the Linux emulation layer has
-      been updated to support a RedHat 8.0 userland. The release is
-      expected to be available on January 24.</p>
-
-      <p>Looking forward, there will be several FreeBSD 5.x releases in
-      the coming year. FreeBSD 5.4 release engineering will start in
-      March, and FreeBSD 5.5 release engineering will likely start in
-      June. These releases are expected to be more conservative than
-      previous 5.x releases and will follow the same philosophy as
-      previous -STABLE branches of fixing bugs and adding incremental
-      improvements while maintaining API stability.</p>
-
-      <p>For the 6-CURRENT development branch as well as all future
-      development and stable branches, we are planning to move to a
-      schedule with fixed timelines that move away from the uncertainty
-      and wild schedule fluctuations of the previous 5.x releases. This
-      means that major branches will happen at 18 month intervals, and
-      releases from those branches will happen at 4 month intervals.
-      There will also be a dedicated period of testing and bug fixing at
-      the beginning of each branch before the first release is cut from
-      that branch. With the shorter and more defined release schedules,
-      we hope to lessen the problem of needed features not reaching users
-      in a reasonable time, as happened too often with 5.x. This is a
-      significant change in our strategy, and we look forward to
-      realizing the benefits of it. This will kick off with the RELENG_6
-      branch happing in June of 2005, followed by the 6.0 release in
-      August of 2005.</p>
-
-      <p>Also on the roadmap is a plan to combine the live-iso disk2 and
-      the install distributions of disk1 into a single disk which can be
-      used for both installation and for recovery. 3rd party packages
-      that currently reside on disc1 will be moved to a disk2 that will
-      be dedicated to these packages. This move will allow us to deal
-      with the ever growing size of packages and also provide more
-      flexibility to vendors that wish to add their own packages to the
-      releases. It also opens the door to more advanced installers being
-      put in place of sysinstall. Anyone interested in helping with this
-      is encouraged to contact us.</p>
-    <hr /><h2><a name="FreeSBIE-Status-Report" href="#FreeSBIE-Status-Report" id="FreeSBIE-Status-Report">FreeSBIE Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeSBIE.org" title="http://www.FreeSBIE.org">FreeSBIE Website</a></td><td>
-	    URL: <a href="http://www.FreeSBIE.org" title="FreeSBIE Website">http://www.FreeSBIE.org</a></td></tr><tr><td><a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="http://liste.gufi.org/mailman/listinfo/freesbie">FreeSBIE Mailing List</a></td><td>
-	    URL: <a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="FreeSBIE Mailing List">http://liste.gufi.org/mailman/listinfo/freesbie</a></td></tr></table><p>
-	Contact: 
-          FreeSBIE
-
-          Staff
-         &lt;<a href="mailto:staff@FreeSBIE.org">staff@FreeSBIE.org</a>&gt;
-	</p>
-      <p>FreeSBIE is a Live-CD based on the FreeBSD Operating system, or
-      even easier, a FreeBSD-based operating system that works directly
-      from a CD, without touching your hard drive.</p>
-
-      <p>On December, 6th, 2004, FreeSBIE Staff released FreeSBIE 1.1,
-      based on FreeBSD 5.3-RELEASE. Some of the innovations are: a
-      renewed series of scripts to support power users in the use of
-      FreeSBIE 1.1, an installer to let users install FreeSBIE 1.1 on
-      their hard drives, thus having a powerful operating system such as
-      FreeBSD, but with all the personalizations FreeSBIE 1.1 carries,
-      the presence of the best open source software, chosen and
-      personalized, such as X.Org 6.7, XFCE 4.2RC1, Firefox 1.0 and
-      Thunderbird 0.9.2.</p>
-
-      <p>For a complete list of the included software, please consult:
-      <a href="http://www.freesbie.org/doc/1.1/FreeSBIE-1.1-i386.pkg_info.txt" shape="rect">
-      http://www.freesbie.org/doc/1.1/FreeSBIE-1.1-i386.pkg_info.txt</a>
-      </p>
-
-      <p>At EuroBSDCon 2004 in Karlsruhe, Germany, people from the
-      FreeSBIE staff gave a talk, deeping into FreeSBIE scripts
-      implementation and use.</p>
-    <h3>Open tasks:</h3><ol><li>Translating website and documentation</li></ol><hr /><h2><a name="Funded-FreeBSD-kernel-development" href="#Funded-FreeBSD-kernel-development" id="Funded-FreeBSD-kernel-development">Funded FreeBSD kernel development</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html" title="http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html">Long winded status report.</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html" title="Long winded status report.">http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html</a></td></tr></table><p>
-	Contact: 
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>A longish status report for the 6 months of funded development
-      was posted on announce, rather than repeat it here, you can find it
-      at the link provided.</p>
-    <hr /><h2><a name="Improved-Multibyte/Wide-Character-Support" href="#Improved-Multibyte/Wide-Character-Support" id="Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></h2><p>
-	Contact: 
-          Tim
-
-          Robbins
-         &lt;<a href="mailto:tjr@FreeBSD.org">tjr@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for multibyte characters has been added to many more
-      base system utilities, including basename, col, colcrt, colrm,
-      column, fmt, look, nl, od, rev, sed, tr, and ul. As a result of
-      changes to the C library (see below), most utilities that perform
-      regular expression matching or pathname globbing now support
-      multibyte characters in these aspects.</p>
-
-      <p>The regular expression matching and pathname globbing routines
-      in the C library have been improved and now recognize multibyte
-      characters. Various performance improvements have been made to the
-      wide character I/O functions. The obsolete 4.4BSD "rune" interface
-      and UTF2 encoding have been removed from the 6-CURRENT branch.</p>
-
-      <p>Work is progressing on implementations of the POSIX iconv and
-      localedef interfaces for potential inclusion into the FreeBSD 6.0
-      release.</p>
-    <hr /><h2><a name="Project-Frenzy-(FreeBSD-based-Live-CD)" href="#Project-Frenzy-(FreeBSD-based-Live-CD)" id="Project-Frenzy-(FreeBSD-based-Live-CD)">Project Frenzy (FreeBSD-based Live-CD)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://frenzy.osdn.org.ua/" title="http://frenzy.osdn.org.ua/">Official web site</a></td><td>
-	    URL: <a href="http://frenzy.osdn.org.ua/" title="Official web site">http://frenzy.osdn.org.ua/</a></td></tr><tr><td><a href="http://frenzy.osdn.org.ua/eng/" title="http://frenzy.osdn.org.ua/eng/">English version</a></td><td>
-	    URL: <a href="http://frenzy.osdn.org.ua/eng/" title="English version">http://frenzy.osdn.org.ua/eng/</a></td></tr></table><p>
-	Contact: 
-          Sergei
-
-          Mozhaisky
-         &lt;<a href="mailto:technix@ukrpost.com.ua">technix@ukrpost.com.ua</a>&gt;
-	</p>
-      <p>Frenzy is a "portable system administrator toolkit," Live-CD
-      based on FreeBSD. It generally contains software for hardware
-      tests, file system check, security check and network setup and
-      analysis. Current version 0.3, based on FreeBSD 5.2.1-RELEASE,
-      contains almost 400 applications in 200MB ISO-image.</p>
-
-      <p>Tasks for next release: script for installation to HDD; unified
-      system configuration tool; updating of software collection.</p>
-    <hr /><h2><a name="Secure-Updating" href="#Secure-Updating" id="Secure-Updating">Secure Updating</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/portsnap/" title="http://www.daemonology.net/portsnap/">Portsnap</a></td><td>
-	    URL: <a href="http://www.daemonology.net/portsnap/" title="Portsnap">http://www.daemonology.net/portsnap/</a></td></tr><tr><td><a href="http://www.daemonology.net/freebsd-update/" title="http://www.daemonology.net/freebsd-update/">FreeBSD Update</a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-update/" title="FreeBSD Update">http://www.daemonology.net/freebsd-update/</a></td></tr></table><p>
-	Contact: 
-          Colin
-
-          Percival
-         &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>In my continuing quest to secure the mechanisms by which FreeBSD
-      users keep their systems up to date, I've added a new tool:
-      Portsnap. Available as sysutils/portsnap in the ports tree, this
-      utility securely downloads and updates a compressed snapshot of the
-      ports tree; this can then be used to extract or update an
-      uncompressed ports tree. In addition to operating in an end-to-end
-      secure manner thanks to RSA signatures, portsnap operates entirely
-      over HTTP and can use under one tenth of the bandwidth of cvsup for
-      users who update their ports tree more than once a week.</p>
-
-      <p>FreeBSD Update -- my utility for secure and efficient binary
-      tracking of the Security/Errata branches -- continues to be widely
-      used, with over 100 machines downloading security or errata updates
-      daily.</p>
-
-      <p>At some point in the future I intend to bring both of these
-      utilities into the FreeBSD base system, probably starting with
-      portsnap.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Hardware-Notes" href="#Hardware-Notes" id="Hardware-Notes">Hardware Notes</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releases/5.3R/hardware-i386.html" title="http://www.FreeBSD.org/releases/5.3R/hardware-i386.html">FreeBSD/i386 5.3-RELEASE Hardware Notes</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/5.3R/hardware-i386.html" title="FreeBSD/i386 5.3-RELEASE Hardware Notes">http://www.FreeBSD.org/releases/5.3R/hardware-i386.html</a></td></tr><tr><td><a href="http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html" title="http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html">FreeBSD/i386 6.0-CURRENT Hardware Notes</a></td><td>
-	    URL: <a href="http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html" title="FreeBSD/i386 6.0-CURRENT Hardware Notes">http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html</a></td></tr></table><p>
-	Contact: 
-          Simon L.
-
-          Nielsen
-         &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Christian
-
-          Brueffer
-         &lt;<a href="mailto:brueffer@FreeBSD.org">brueffer@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Hardware Notes have been (mostly) converted to being
-      directly generated from the driver manual pages. This makes it much
-      simpler to maintain the Hardware Notes, so they should be more
-      accurate. The Hardware Notes for FreeBSD 5.3 use this new
-      system.</p>
-    <hr /><h2><a name="The-FreeBSD-Dutch-Documentation-Team" href="#The-FreeBSD-Dutch-Documentation-Team" id="The-FreeBSD-Dutch-Documentation-Team">The FreeBSD Dutch Documentation Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.evilcoder.org/content/section/6/39/" title="http://www.evilcoder.org/content/section/6/39/">The project's webpage.</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/content/section/6/39/" title="The project's webpage.">http://www.evilcoder.org/content/section/6/39/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/nl/books/handbook/" title="http://www.FreeBSD.org/doc/nl/books/handbook/">The officially released documentation.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/nl/books/handbook/" title="The officially released documentation.">http://www.FreeBSD.org/doc/nl/books/handbook/</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd_html/" title="http://www.evilcoder.org/freebsd_html/">Preview of the documentation.</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd_html/" title="Preview of the documentation.">http://www.evilcoder.org/freebsd_html/</a></td></tr></table><p>
-	Contact: 
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:Remko@FreeBSD.org">Remko@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation Project is a ongoing project to
-      translate the documentation into the Dutch language. Currently we
-      are mainly focused on the Handbook, which is progressing pretty
-      well. However, lots need to be translated and checked before we
-      have a 'complete' translation ready. So if you are willing to help
-      out, please checkout our website and/or contact me.</p>
-    <h3>Open tasks:</h3><ol><li>Translating the Handbook</li><li>Checking the grammar of the Dutch Handbook</li><li>Translate the rest of the documentation</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="ATA-Driver-Status-Report" href="#ATA-Driver-Status-Report" id="ATA-Driver-Status-Report">ATA Driver Status Report</a></h2><p>
-	Contact: 
-          S�ren
-
-          Schmidt
-         &lt;<a href="mailto:sos@FreeBSD.org">sos@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ATA driver is undergoing quite a few important changes,
-      mainly it is being converted into modules so it can be
-      loaded/unloaded at will, and just the pieces for wanted
-      functionality need be present.</p>
-
-      <p>This calls for ata-raid to finally be rewritten. This is almost
-      done for reading metadata so arrays defined in the BIOS can be
-      used, and its grown quite a few new metadata formats. This also
-      paves the way for ataraid to finally be able to take advantage of
-      some of the newer controllers "RAID" abilities. However this needs
-      more work to materialize but now its finally possible</p>
-
-      <p>There is also support coming for a few new chipsets as
-      usual.</p>
-
-      <p>The work is just about finished enough that it can be released
-      as patches to sort out eventual problems before hitting current.
-      The changes are pretty massive as this touches all over the driver
-      infrastructure, so lots of old bugs and has also been spotted and
-      fixed during this journey</p>
-    <hr /><h2><a name="CPU-Cache-Prefetching" href="#CPU-Cache-Prefetching" id="CPU-Cache-Prefetching">CPU Cache Prefetching</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" title="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch"></a></td><td>
-	    URL: <a href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" title="">http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch</a></td></tr></table><p>
-	Contact: 
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>Modern CPU's can only perform to their maximum if their working
-      code is in fast L1-3 cache memory instead of the bulk main memory.
-      All of today's CPU's support certain L1-3 cache prefetching
-      instructions which cause data to be retrieved from main memory to
-      the cache ahead of the time that it is already in place when it is
-      eventually accessed by the CPU.</p>
-
-      <p>CPU Cache Prefetching however is not a golden bullet and has to
-      be used with extreme care and only in very specific places to be
-      beneficial. Incorrect usage can lead to massive cache pollution and
-      a drop in effective performance. Correct and very carefully usage
-      on the other can lead to drastic performance increases in common
-      operations.</p>
-
-      <p>In the linked patch CPU cache prefetching has been used to
-      prefetch the packet header (OSI layer 2 to 4) into the CPU caches
-      right after entering into the network stack. This avoids a complete
-      CPU stall on the first access to the packet header because packets
-      get DMA'd into main memory and thus never are already pre-cache in
-      the CPU caches. A second use in the patch is in the TCP input code
-      to prefetch the entire struct tcpcb which is very large and used
-      with a very high probability. Use in both of these places show a
-      very significant performance gain but not yet fully quantified.</p>
-
-      <p>The final patch will include documentation and a guide to
-      evaluate and assess the use of CPU cache prefetch instructions in
-      the kernel.</p>
-    <hr /><h2><a name="i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing" href="#i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing" id="i386-Interrupt-Code-&amp;-PCI-Interrupt-Routing">i386 Interrupt Code &amp; PCI Interrupt Routing</a></h2><p>
-	Contact: 
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ACPI PCI link support code was reworked to work around some
-      limitations in the previous implementation. The new version more
-      closely matches the current non-ACPI $PIR link support.
-      Enhancements include disabling unused link devices during boot and
-      using a simpler and more reliable algorithm for choosing ISA IRQs
-      for unrouted link devices.</p>
-
-      <p>Support for using the local APIC timer to drive the kernel
-      clocks instead of the ISA timer and i8254 clock is currently being
-      worked on in the jhb_clock perforce branch. It is mostly complete
-      and will probably hit the tree in the near future. By letting each
-      CPU use its own private timer to drive the kernel clocks, the
-      kernel no longer has to IPI all the other CPUs in the system every
-      time a clock interrupt occurs.</p>
-    <hr /><h2><a name="kgi4BSD" href="#kgi4BSD" id="kgi4BSD">kgi4BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/~nsouch/kgi4BSD" title="http://www.freebsd.org/~nsouch/kgi4BSD">Homepage</a></td><td>
-	    URL: <a href="http://www.freebsd.org/~nsouch/kgi4BSD" title="Homepage">http://www.freebsd.org/~nsouch/kgi4BSD</a></td></tr><tr><td><a href="http://wiki.daemon.li/moin.cgi/KGI" title="http://wiki.daemon.li/moin.cgi/KGI"></a></td><td>
-	    URL: <a href="http://wiki.daemon.li/moin.cgi/KGI" title="">http://wiki.daemon.li/moin.cgi/KGI</a></td></tr></table><p>
-	Contact: 
-          Nicholas
-
-          Souchu
-         &lt;<a href="mailto:nsouch@FreeBSD.org">nsouch@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project was very quiet (but still alive!) and mostly
-      dedicated to testing by volunteers. New documentation at
-      <a href="http://wiki.daemon.li/moin.cgi/KGI" shape="rect">
-      http://wiki.daemon.li/moin.cgi/KGI</a>
-
-      .</p>
-    <h3>Open tasks:</h3><ol><li>Help improving the documentation</li></ol><hr /><h2><a name="Layer-2-PFIL_HOOKS" href="#Layer-2-PFIL_HOOKS" id="Layer-2-PFIL_HOOKS">Layer 2 PFIL_HOOKS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html" title="http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html" title="">http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html</a></td></tr></table><p>
-	Contact: 
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>IPFW2 has been converted to use PFIL_HOOKS for the IP[46]
-      in/output path. (See link.) Not converted yet is the Layer 2
-      Etherfilter functionality of IPFW2. It is still directly called
-      from the ether_input/output and bridging code.</p>
-
-      <p>Layer 2 PFIL_HOOKS provide a general abstraction for packet
-      filters to hook into the Layer 2 packet path and filter or
-      manipulate such packets. This makes it possible to use not only
-      IPFW2 but also PF and others for Layer 2 filtering.</p>
-    <hr /><h2><a name="Low-overhead-performance-monitoring-for-FreeBSD" href="#Low-overhead-performance-monitoring-for-FreeBSD" id="Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement/">A best-in-class performance monitoring system for FreeBSD built over the hardware performance monitoring facilities of modern CPUs.</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="A best-in-class performance monitoring system for FreeBSD built over the hardware performance monitoring facilities of modern CPUs.">http://people.freebsd.org/~jkoshy/projects/perf-measurement/</a></td></tr></table><p>
-	Contact: 
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>System-wide and process-virtual counting-mode performance
-      monitoring counters are now supported for the AMD Athlon and Intel
-      P4 CPUs. SMP works, but is prone to freezes. Immediate next steps
-      include: (1) implementing the system-wide and process-virtual
-      sampling modes, (2) debugging, (3) writing a test suite and (4)
-      improving the project's documentation.</p>
-    <hr /><h2><a name="Move-ARP-out-of-routing-table" href="#Move-ARP-out-of-routing-table" id="Move-ARP-out-of-routing-table">Move ARP out of routing table</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html" title="">http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html</a></td></tr></table><p>
-	Contact: 
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Qing
-
-          Li
-         &lt;<a href="mailto:qingli@speackeasy.net">qingli@speackeasy.net</a>&gt;
-	</p>
-      <p>The ARP IP address to MAC address mapping does not belong into
-      the routing table (FIB) as it is currently done. This will move it
-      to its own hash based structure which will be instantiated per each
-      802.1 broadcast domain. With this change it is possible to have
-      more than one interface in the same IP subnet and layer 2 broadcast
-      domain. The ARP handling and the routing table will be quite a bit
-      simplified afterwards. As an additional benefit full MAC address
-      based accounting will be provided.</p>
-
-      <p>Qing Li has become the driver and implementor of this project
-      and is expected to post a first patch for comments shortly in
-      February 2005.</p>
-    <hr /><h2><a name="Network-Stack-Locking" href="#Network-Stack-Locking" id="Network-Stack-Locking">Network Stack Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/projects/netperf/" title="http://www.freebsd.org/projects/netperf/">FreeBSD Project Netperf project web page.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/netperf/" title="FreeBSD Project Netperf project web page.">http://www.freebsd.org/projects/netperf/</a></td></tr><tr><td><a href="http://www.watson.org/~robert/freebsd/netperf/" title="http://www.watson.org/~robert/freebsd/netperf/">Robert Watson's personal Netperf web page.</a></td><td>
-	    URL: <a href="http://www.watson.org/~robert/freebsd/netperf/" title="Robert Watson's personal Netperf web page.">http://www.watson.org/~robert/freebsd/netperf/</a></td></tr></table><p>
-	Contact: 
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The netperf project is working to enhance the performance of the
-      FreeBSD network stack. This work grew out of the SMPng Project,
-      which moved the FreeBSD kernel from a "Giant Lock" to more
-      fine-grained locking and multi-threading. SMPng offered both
-      performance improvement and degradation for the network stack,
-      improving parallelism and preemption, but substantially increasing
-      per-packet processing costs. The netperf project is primarily
-      focused on further improving parallelism in network processing
-      while reducing the SMP synchronization overhead. This in turn will
-      lead to higher processing throughput and lower processing latency.
-      Tasks include completing the locking work, optimizing locking
-      strategies, amortizing locking costs, introducing new
-      synchronization primitives, adopting non-locking synchronization
-      strategies, and improving opportunities for parallelism through
-      additional threading.</p>
-
-      <p>Between July, 2004, and December, 2004, the Netperf project did
-      a great deal of work, for which there is room only to include
-      limited information. Much more information is available by visiting
-      the URLS above, including information on a variety of on-going
-      activities. Accomplishments include:</p>
-
-      <p>July, 2004: A variety of improvements to PCB locking in the IPv6
-      implementation; locking for the if_xl driver; socket locking for
-      the NFS client; cleanup of the soreceive() code path including
-      structural improvements, assertions, and locking fixes; cleanup of
-      the IPX/SPX code in preparation for locking; additional locking and
-      locking assertions for the TCP implementation; bug fixes for
-      locking and memory allocation in raw IP;
-      <em>netatalk cleanup and locking merged to FreeBSD CVS</em>
-
-      ;
-      <em>locking for many netgraph nodes merged to FreeBSD CVS</em>
-
-      ; SLIP structural improvements; experimental locking for netatalk
-      ifaddrs; BPF locking optimizations (merged); Giant assertions for
-      VFS to check VFS/network stack boundaries; UNIX domain socket
-      locking optimizations; expansion of lock order documentation in
-      WITNESS, additional NFS server code running MPSAFE; pipe locking
-      optimizations to improve pipe allocation performance; Giant no
-      longer required for fstat on sockets and pipes (merged); Giant no
-      longer required for socket and pipe file descriptor closes
-      (merged);
-      <em>IFF_NEEDSGIANT interface flag added to support compatibility
-      operation for unlocked device drivers (merged)</em>
-
-      ; merged accept filter locking to FreeBSD CVS; documented uidinfo
-      locking strategy (merged); Giant use reduced in fcntl().</p>
-
-      <p>August, 2004: UMA KTR tracing (merged); UDP broadcast receive
-      locking optimizations (merged); TCP locking cleanup and
-      documentation; IPv6 inpcb locking, cleanup, and structural
-      improvements;
-      <em>IPv6 inpcb locking merged to FreeBSD CVS</em>
-
-      ; KTR for systems calls added to i386;
-      <em>substantial optimizations of entropy harvesting synchronization
-      (merged)</em>
-
-      ; callout(9) sampling converted to KTR (merged); inpcb socket
-      option locking (merged); GIANT_REQUIRED removed from netatalk in
-      FreeBSD CVS;
-      <em>merged ADAPTIVE_GIANT to FreeBSD CVS, resulting in substantial
-      performance improvements in many kernel IPC-intensive
-      benchmarks</em>
-
-      ; prepend room for link layer headers to the UDP header mbuf to
-      avoid one allocation per UDP send (merged); a variety of UDP bug
-      fixes (merged); additional network interfaces marked MPSAFE; UNIX
-      domain socket locking reformulated to protect so_pcb pointers;
-      <em>MP_WATCHDOG, a facility to dedicate additional HTT logical CPUs
-      as watchdog CPUs developed (merged)</em>
-
-      ; annotation of UNIX domain socket locking merged to FreeBSD CVS;
-      <em>kqueue locking developed and merged by John-Mark Gurney</em>
-
-      ; task list for netinet6 locking created; conditional locking
-      relating to kqueues and socket buffers eliminated (merged); NFS
-      server locking bugfixes (merged); in6_prefix code removed from
-      netinet6 by George Neville-Neil, lowering the work load for
-      netinet6 (merged); unused random tick code in netinet6 removed
-      (merged);
-      <em>ng_tty, IPX, KAME IPSEC now declare dependence on Giant using
-      compile-time declaration NET_NEEDS_GIANT("component") permitting
-      the kernel to detect unsafe components and automatically acquire
-      the Giant lock over network stack operation if needed (merged)</em>
-
-      ; additional locking optimizations for entropy code (merged); Giant
-      disabled by default in the netperf development branch (merged).</p>
-
-      <p>September, 2004: bugs fixed relating to Netgraph's use of the
-      kernel linker while not holding Giant (merged);
-      <em>merged removal of Giant over the network stack by default to
-      FreeBSD CVS</em>
-
-      ; races relating to netinet6 and if_afdata corrected (merged);
-      annotation of possible races in the BPF code; BPF code converted to
-      queue(3) (merged); race in sopoll() corrected (merged).</p>
-
-      <p>October, 2004: IPv6 netisr marked as MPSAFE; TCP timers locked,
-      annotated, and asserted (merged); IP socket option locking and
-      cleanup (merged); Netgraph ISR marked MPSAFE; netatalk ISR marked
-      MPSAFE (merged); some interface list locking cleanup (merged); use
-      after free bug relating to entropy harvesting and ethernet fixed
-      (merged); soclose()/sofree() race fixed (merged); IFF_LOCKGIANT()
-      and IFF_UNLOCKGIANT() added to acquire Giant as needed when
-      entering the ioctls of non-MPSAFE network interfaces.</p>
-
-      <p>November, 2004: cleanup of UDPv6 static global variables
-      (merged);
-      <em>FreeBSD 5.3 released! First release of FreeBSD with an MPSAFE
-      and Giant-free network stack as the default configuration!</em>
-
-      ; additional TCP locking documentation and cleanup (merged);
-      <em>optimization to use file descriptor reference counts instead of
-      socket reference counts for frequent operations results in
-      substantial performance optimizations for high-volume send/receive
-      (merged)</em>
-
-      ; an accept bug is fixed (merged) experimental network polling
-      locking introduced;
-      <em>substantial measurement and optimization of mutex and locking
-      primitives (merged)</em>
-
-      ;
-      <em>experimental modifications to UMA to use critical sections to
-      protect per-CPU caches instead of mutexes yield substantial
-      micro-benchmark benefits when combined with experimental critical
-      section optimizations</em>
-
-      ; FreeBSD Project Netperf page launched; performance
-      micro-benchmarks benchmarks reveal IP forwarding latency in 5.x is
-      measurably better than 4.x on UP when combined with optional
-      network stack direct dispatch; several NFS server locking bugfixes
-      (merged);
-      <em>development of new mbufqueue primitives and substantial
-      experimentation with them permits development of amortized cost
-      locking APIs for handoff between the network stack and network
-      device drivers (work in collaboration with Sandvine, Inc)</em>
-
-      ; Linux TCP_INFO API added to allow user-space monitoring of TCP
-      state (merged); SMPng task list updated; UDP static/global fixes
-      merged to RELENG_5.</p>
-
-      <p>December, 2004: UDP static/global fixes developed for
-      multi-threaded in-bound UDP processing (merged); socket buffer
-      locking fixes for urgent TCP input processing (merged); lockless
-      read optimizations for IF_DEQUEUE() and IF_DRAIN(); Giant-free
-      close for sockets/pipes/... merged to FreeBSD CVS; optimize
-      mass-dequeues of mbuf chains in netisr processing; netrate tool
-      merged to RELENG_5; TCP locking fixes merged to RELENG_5; "show
-      alllocks" added to DDB (merged); IPX locking bugfixes (merged);
-      IPX/SPX __packed fixes (merged); IPX/SPX moved to queue(9)
-      (merged); TCP locking fixes and annotations merged to FreeBSD CVS;
-      IPX/SPX globals and pcb locking (merged);
-      <em>IPX/SPX marked MPSAFE (merged)</em>
-
-      ; IP socket options locking merged to FreeBSD; SPPP locked by Roman
-      Kurakin (merged); UNIX domain socket locking fixes by Alan Cox
-      (merged).</p>
-
-      <p>On-going work continues with regard to locking down network
-      stack components, including additional netinet6 locking, mbuf queue
-      facilities and operations; benchmarking; moving to critical
-      sections or per-CPU mutexes for UMA per-CPU caches; moving to
-      critical sections or per-CPU mutexes for malloc(9) statistics;
-      elimination of separate mbuf allocator statistics; additional
-      interface locking; a broad variety of cleanups and documentation of
-      locking; a broad range of optimizations.</p>
-    <hr /><h2><a name="New-Modular-Input-Device-Layer" href="#New-Modular-Input-Device-Layer" id="New-Modular-Input-Device-Layer">New Modular Input Device Layer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html" title="http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html" title="">http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html</a></td></tr></table><p>
-	Contact: 
-          Philip
-
-          Paeps
-         &lt;<a href="mailto:philip@FreeBSD.org">philip@FreeBSD.org</a>&gt;
-	</p>
-      <p>Following a number of mailing lists discussions on the topic,
-      work has been progressing on the development of a new modular input
-      device layer for FreeBSD. The purpose of this is twofold:</p>
-
-      <ul>
-        <li>Easier development of new input device drivers.</li>
-
-        <li>Support for concurrent use of multiple input devices,
-        particularly the hot-pluggable kind.</li>
-      </ul>
-
-      <p>Currently, implementing support for new input devices is a
-      painful process and there is great potential for code-duplication.
-      The new input device layer will provide a simple API for developers
-      to send events from their hardware on to the higher regions of the
-      kernel in a consistent way, much like the 'input-core' driver in
-      the Linux kernel.</p>
-
-      <p>Using multiple input devices at the moment is painful at best.
-      With the new input device layer, events from different devices will
-      be properly serialized before they are sent to other parts of the
-      kernel. This will allow one to easily use, for instance, multiple
-      USB keyboards in a virtual terminal.</p>
-
-      <p>The work on this is still in very rudimentary state. It is
-      expected that the first visible changes will be committed to
-      -CURRENT around late February or early March.</p>
-    <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact: 
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:smp@FreeBSD.org">smp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Lots of changes happened inside the network stack that will
-      hopefully be covered by a separate report. Outside of the network
-      stack, several changes were made however including changes to proc
-      locking, making the kernel thread scheduler preemptive, fixing
-      several priority inversion bugs in the scheduler, and a few
-      performance tweaks in the mutex implementation.</p>
-
-      <p>Locking work on struct proc and its various substructures
-      continued with locking added where needed for struct uprof, struct
-      rusage, and struct pstats. This also included reworking how the
-      kernel stores process time statistics to store the raw struct
-      bintime and tick counts internally and only compute the more user
-      friendly values when requested via getrusage() or wait4().</p>
-
-      <p>Support for kernel thread preemption was added to the scheduler.
-      Basically, when a thread makes another thread runnable, it may
-      yield the current CPU to the new thread if the new thread has a
-      more important priority. Previously, only interrupt threads
-      preempted other threads and the implementation would occasionally
-      trigger spurious context switches. This change exposed bugs in
-      other parts of the kernel and was turned off by default in
-      RELENG_5. Currently, only the i386, amd64, and alpha platforms
-      support native preemption.</p>
-
-      <p>Several priority inversion bugs present in the scheduler due to
-      various changes to the kernel from SMPng were also fixed. Most of
-      the credit for these fixes belongs Stephan Uphoff who has recently
-      been added as a new committer. Fixes include: closing a race in the
-      turnstile wakeup code, changing the sleep queue code to store
-      threads in FIFO order so that the sleep queue wakeup code properly
-      handles having a thread's priority changes, and abstracting the
-      concept of priority lending so that the thread scheduler is now
-      able to properly track priority inheritance and handle priority
-      changes for threads blocked on a turnstile.</p>
-
-      <p>Works in progress include separating critical sections from spin
-      mutexes some so that bare critical sections become very cheap as
-      well as continuing to change the various ABI compatibility layers
-      to use in-kernel versions of system calls to reduce stackgap usage
-      and make the system call wrappers MPSAFE.</p>
-    <hr /><h2><a name="Sync-Protocols-(SPPP-and-NETGRAPH)" href="#Sync-Protocols-(SPPP-and-NETGRAPH)" id="Sync-Protocols-(SPPP-and-NETGRAPH)">Sync Protocols (SPPP and NETGRAPH)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/~rik" title="http://www.freebsd.org/~rik">My FreeBSD home page. You could find here some results of my work. Unfortunately I do not update this page often.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/~rik" title="My FreeBSD home page. You could find here some results of my work. Unfortunately I do not update this page often.">http://www.freebsd.org/~rik</a></td></tr></table><p>
-	Contact: 
-          Roman
-
-          Kurakin
-         &lt;<a href="mailto:rik@FreeBSD.org">rik@FreeBSD.org</a>&gt;
-	</p>
-      <p>sppp(4) was updated (in 6.current) to be able to work in mpsafe
-      mode. For compatibility if an interface is unable to work in mpsafe
-      mode, sppp will not use mpsafe locks.</p>
-
-      <p>Support of FrameRelay AnnexD was added as a historical commit.
-      Many of Cronyx users were expecting this commit for a long long
-      time, and most of them still prefer sppp vs netgraph because of
-      simplicity of its configuration (especially for ppp (vs mpd) and fr
-      (vs a couple of netgraph modules). After MFCing this I'll finally
-      close a PR 21771, from 2000/10/05</p>
-    <hr /><h2><a name="TCP-Cleanup-and-Optimizations" href="#TCP-Cleanup-and-Optimizations" id="TCP-Cleanup-and-Optimizations">TCP Cleanup and Optimizations</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpcleanup.html" title="http://people.freebsd.org/~andre/tcpcleanup.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpcleanup.html" title="">http://people.freebsd.org/~andre/tcpcleanup.html</a></td></tr></table><p>
-	Contact: 
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The TCP code in FreeBSD has evolved significantly since the fork
-      from 4.4BSD-Lite2 in 1994 primarily due to new features and
-      refinements of the TCP specifications.</p>
-
-      <p>The TCP code now needs a general overhaul, streamlining a
-      cleanup to make it easily comprehensible, maintainable and
-      extensible again. In addition there are many little optimizations
-      that can be done during such an operation propelling FreeBSD back
-      at the top of the best performing TCP/IP stacks again, a position
-      it has held for the longest time in the 90's.</p>
-
-      <p>This overhaul is a very involved and delicate matter and needs
-      extensive formal and actual testing to ensure no regressions
-      compared to the current code. The effort needed for this work is
-      about two man-month of fully focused and dedicated time. To get it
-      done I need funding to take time off my day job and to dedicate me
-      to FreeBSD work much the way PHK did with his buffer cache and
-      vnode rework projects.</p>
-
-      <p>In February 2005 I will officially announce the funding request
-      with a detailed description of the work and how the funding works.
-      In general I can write invoices for companies wishing to sponsor
-      this work on expenses. Tax exempt donations can probably be
-      arranged through the FreeBSD foundation. Solicitations of money are
-      already welcome, please contact me on the email address above.</p>
-    <h3>Open tasks:</h3><ol><li>Funding for two man-month equivalents of my time.</li><li>If you want or intend to sponsor US$1k or more please contact
-      me in advance already now.</li></ol><hr /><h2><a name="TCP-Reassembly-Rewrite-and-Optimization" href="#TCP-Reassembly-Rewrite-and-Optimization" id="TCP-Reassembly-Rewrite-and-Optimization">TCP Reassembly Rewrite and Optimization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" title="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch"></a></td><td>
-	    URL: <a href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" title="">http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" title="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" title="">http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html</a></td></tr></table><p>
-	Contact: 
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently TCP segment reassembly is implemented as a linked list
-      of segments. With today's high bandwidth links and large
-      bandwidth*delay products this doesn't scale and perform well.</p>
-
-      <p>The rewrite optimizes a large number of operational aspects of
-      the segments reassembly process. For example it is very likely that
-      the just arrived segment attaches to the end of the reassembly
-      queue, so we check that first. Second we check if it is the missing
-      segment or alternatively attaches to the start of the reassembly
-      queue. Third consecutive segments are merged together (logically)
-      and are skipped over in one jump for linear searches instead of
-      each segment at a time.</p>
-
-      <p>Further optimizations prototyped merge consecutive segments on
-      the mbuf level instead of only logically. This is expected to give
-      another significant performance gain. The new reassembly queue is
-      tracking all holes in the queue and it may be beneficial to
-      integrate this with the scratch pad of SACK in the future.</p>
-
-      <p>Andrew Gallatin was able to get 3.7Gb/sec TCP performance on
-      dual-2Gbit Myrinet cards with severe packet reordering (due to a
-      firmware bug) with the new TCP reassembly code. See second
-      link.</p>
-    <hr /><h2><a name="TTCPv2:-Transactional-TCP-version-2" href="#TTCPv2:-Transactional-TCP-version-2" id="TTCPv2:-Transactional-TCP-version-2">TTCPv2: Transactional TCP version 2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" title="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" title="">http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html</a></td></tr></table><p>
-	Contact: 
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The old TTCP according to RFC1644 was insecure, intrusive,
-      complicated and has been removed from FreeBSD &gt;= 5.3. Although
-      the idea and semantics behind it are still sound and valid.</p>
-
-      <p>The rewrite uses a much easier and more secure system with 24bit
-      long client and server cookies which are transported in the TCP
-      options. Client cookies protect against various kinds of blind
-      injection attacks and can be used as well to generally secure TCP
-      sessions (for BGP for example). Server cookies are only exchanged
-      during the SYN-SYN/ACK phase and allow a server to ensure that it
-      has communicated with this particular client before. The first
-      connection is always performing a 3WHS and assigning a server
-      cookie to a client. Subsequent connections can send the cookie back
-      to the server and short-cut the 3WHS to SYN-&gt;OPEN on the
-      server.</p>
-
-      <p>TTCPv2 is fully configurable per-socket via the setsockopt()
-      system call. Clients and server not capable of TTCPv2 remain fully
-      compatible and just continue using the normal 3WHS without any
-      delay or other complications.</p>
-
-      <p>Work on implementing TTCPv2 is done to 90% and expected to be
-      available by early February 2005. Writing the implementation
-      specification (RFC Draft) has just started.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Xen" href="#FreeBSD-on-Xen" id="FreeBSD-on-Xen">FreeBSD on Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fsmware.com/xenofreebsd/" title="http://www.fsmware.com/xenofreebsd/">binaries + source + slightly out of date HOWTO</a></td><td>
-	    URL: <a href="http://www.fsmware.com/xenofreebsd/" title="binaries + source + slightly out of date HOWTO">http://www.fsmware.com/xenofreebsd/</a></td></tr><tr><td><a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" title="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/">Xen project page</a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" title="Xen project page">http://www.cl.cam.ac.uk/Research/SRG/netos/xen/</a></td></tr></table><p>
-	Contact: 
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@fsmware.com">kmacy@fsmware.com</a>&gt;
-	</p>
-      <p>FreeBSD 5.2.1 is stable on the stable branch of Xen as a guest.
-      FreeBSD 5.3 runs on the stable branch of Xen as a guest, but a
-      couple of bugs need to be tracked down.</p>
-    <h3>Open tasks:</h3><ol><li>FreeBSD support for running in Domain 0 (host)</li><li>FreeBSD support for VM checkpoint and migration</li></ol><hr /><h2><a name="FreeBSD/arm-status-report" href="#FreeBSD/arm-status-report" id="FreeBSD/arm-status-report">FreeBSD/arm status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/platforms/arm" title="http://www.freebsd.org/platforms/arm">FreeBSD/arm project page.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/platforms/arm" title="FreeBSD/arm project page.">http://www.freebsd.org/platforms/arm</a></td></tr></table><p>
-	Contact: 
-          Olivier
-
-          Houchard
-         &lt;<a href="mailto:cognet@FreeBSD.org">cognet@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD/arm made some huge progress. It can boot multiuser, and
-      run things like "make world" and perl on the IQ31244 board. It also
-      now has support for various things, including DDB, KTR, ptrace and
-      kernel modules. A patch is available for early gdb support, and the
-      libpthread almost works.</p>
-    <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/~grehan/miniinst.iso" title="http://www.freebsd.org/~grehan/miniinst.iso">Miniinst ISO.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/~grehan/miniinst.iso" title="Miniinst ISO.">http://www.freebsd.org/~grehan/miniinst.iso</a></td></tr><tr><td><a href="http://www.freebsd.org/~grehan/miniinst.txt" title="http://www.freebsd.org/~grehan/miniinst.txt">Miniinst relnotes.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/~grehan/miniinst.txt" title="Miniinst relnotes.">http://www.freebsd.org/~grehan/miniinst.txt</a></td></tr></table><p>
-	Contact: 
-          Peter
-
-          Grehan
-         &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>A natively built 6.0-CURRENT miniinst ISO is available at the
-      above link. It runs best on G4 Powermacs, but may run on other
-      Newworld machines. See the release notes for full details.</p>
-
-      <p>As usual, lots of help is needed. This is a great project for
-      those who want to delve deeply into FreeBSD kernel internals.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-GNOME-Project-Status-Report" href="#FreeBSD-GNOME-Project-Status-Report" id="FreeBSD-GNOME-Project-Status-Report">FreeBSD GNOME Project Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact: 
-          Joe
-
-          Marcus
-         &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	</p>
-      <p>We haven't produced a status report in a while, but that's just
-      because we've been busy. Since our last report in March 2004, we
-      have added three new team members: Koop Mast (kwm), Jeremy
-      Messenger (mezz), and Michael Johnson (ahze). Jeremy has been quite
-      helpful in GNOME development porting while Michael and Koop have
-      been focusing on improving GNOME multimedia, especially GStreamer.
-      The stable release of GNOME is now up to 2.8.2, and we are actively
-      working on the GNOME 2.9 development branch with is slated to
-      become 2.10 on March 9 of this year.</p>
-
-      <p>The
-      <a href="http://www.FreeBSD.org/gnome/docs/faq2.html#q21" shape="rect">GNOME
-      Tinderbox</a>
-
-      is still cranking away, and producing packages for both the stable
-      and development releases of GNOME for all supported i386 versions
-      of FreeBSD.</p>
-
-      <p>Thanks to Michael Johnson, the FreeBSD GNOME team has recently
-      been given
-      <a href="http://people.FreeBSD.org/~ahze/firefox_thunderbird-approved.txt" shape="rect">
-      permission to use the Firefox and Thunderbird names</a>
-
-      , official icons, and to produce officially branded builds. Mozilla
-      has also been very interested in merging our local patches back
-      into the official source tree. This should greatly improve the
-      quality of Firefox and Thunderbird on FreeBSD moving forward.</p>
-
-      <p>Finally, Adam Weinberger (adamw) has been pestering the team
-      for photos so that we can finally show the community who we are. It
-      is still unclear as to whether or not this will attract more
-      FreeBSD GNOME users, or land us on the Homeland Security no-fly
-      list.</p>
-    <h3>Open tasks:</h3><ol><li>Need help porting
-      <a href="http://www.freedesktop.org/wiki/Software_2fhal" shape="rect">HAL</a>
-
-      to FreeBSD (contact
-      <a href="mailto:marcus@FreeBSD.org" shape="rect">marcus@FreeBSD.org</a>
-
-      )</li><li>Need help porting
-      <a href="http://www.freedesktop.org/wiki/Software_2fburn" shape="rect">
-      libburn</a>
-
-      to FreeBSD (contact
-      <a href="mailto:bland@FreeBSD.org" shape="rect">bland@FreeBSD.org</a>
-
-      )</li><li>Anyone interested in reviving
-      <a href="http://www.gnomemeeting.org/" shape="rect">Gnome Meeting</a>
-
-      should contact
-      <a href="mailto:kwm@FreeBSD.org" shape="rect">kwm@FreeBSD.org</a>
-      </li></ol><hr /><h2><a name="OpenOffice.org-port-status" href="#OpenOffice.org-port-status" id="OpenOffice.org-port-status">OpenOffice.org port status</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://porting.openoffice.org/freebsd/" title="http://porting.openoffice.org/freebsd/">FreeBSD OpenOffice.org porting status page</a></td><td>
-	    URL: <a href="http://porting.openoffice.org/freebsd/" title="FreeBSD OpenOffice.org porting status page">http://porting.openoffice.org/freebsd/</a></td></tr><tr><td><a href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/" title="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/">Stable OOo Packages for FreeBSD</a></td><td>
-	    URL: <a href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/" title="Stable OOo Packages for FreeBSD">http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/</a></td></tr><tr><td><a href="http://sourceforge.jp/projects/waooo/files/" title="http://sourceforge.jp/projects/waooo/files/">Some volatile WIP status of packages</a></td><td>
-	    URL: <a href="http://sourceforge.jp/projects/waooo/files/" title="Some volatile WIP status of packages">http://sourceforge.jp/projects/waooo/files/</a></td></tr></table><p>
-	Contact: 
-          Maho
-
-          Nakata
-         &lt;<a href="mailto:maho@FreeBSD.org">maho@FreeBSD.org</a>&gt;
-	</p>
-      <p>OpenOffice.org 2.0 status
-      <ul>
-        <li>OpenOffice.org 2.0 is planned to be released in March 2005.
-        Currently developer snapshot versions are available. Now one of
-        the developer version has been ported, and committed to ports
-        tree (/usr/ports/editors/openoffice-2.0-devel).</li>
-
-        <li>Packages for 5.3-RELEASE are available at
-        <a href="http://sourceforge.jp/projects/waooo/files/asOOo_1.9m71_FreeBSD53Intel_install_en-US.tbz" shape="rect">
-        http://sourceforge.jp/projects/waooo/files/asOOo_1.9m71_FreeBSD53Intel_install_en-US.tbz</a>
-
-        etc., and soon it will also available at :
-        <a href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/" shape="rect">
-        http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/</a>
-
-        with the language pack.</li>
-
-        <li>Almost all of the patches required to build will be
-        integrated to master.
-        <a href="http://www.openoffice.org/issues/show_bug.cgi?id=40187" shape="rect">
-        http://www.openoffice.org/issues/show_bug.cgi?id=40187</a>
-        </li>
-
-        <li>Now we have three external ports : lang/gcc-ooo,
-        devel/bison-devel and devel/epm. To avoid regressions and bugs of
-        gcc, we use the exactly same gcc as Hamburg team (former
-        StarDivision) uses. We need bison later than 1.785a. Note this
-        port CONFLICTS with devel/bison. Epm is a package manager which
-        now OpenOffice.org uses.</li>
-      </ul>
-
-      OpenOffice.org 1.1 status
-      <ul>
-        <li>1.1.4 has been ported and committed to ports tree.</li>
-
-        <li>Packages are available at
-        <a href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/" shape="rect">
-        http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/</a>
-
-        .</li>
-
-        <li>Now recognizes Linux version of Java JDKs.</li>
-      </ul>
-
-      General
-      <ul>
-        <li>Invoking OpenOffice.org from command line has been changed.
-        Now `.org' is mandatory. e.g. openoffice-1.1.4 -&gt;
-        openoffice.org-1.1.4. Since the name of the software is
-        OpenOffice.org, not OpenOffice. We are also considering the name
-        of the ports (/usr/ports/editors/openoffice-2.0-devel -&gt;
-        openoffice.org2-devel etc)</li>
-
-        <li>Now marked as BROKEN OOo ports for prior than 5.3-RELEASE and
-        4.11-RELEASE. These ports have been suffering from a minor
-        implementation difference of rtld.c between FreeBSD and Linux,
-        Solaris, NetBSD. We have been applying a patch adding _end in
-        mapfile. We need this since rtld depend on existence of _end
-        symbol in obj_from_addr_end, unfortunately this seem to induce
-        hard-to-solve errors. A great progress has been made kan, rtld
-        now do not depend on _end. A fix was committed 2004/02/25
-        17:06:16,
-        <a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/libexec/rtld-elf/rtld.c.diff?r1=1.91&amp;r2=1.92&amp;f=h" shape="rect">
-        http://www.freebsd.org/cgi/cvsweb.cgi/src/libexec/rtld-elf/rtld.c.diff?r1=1.91&amp;r2=1.92&amp;f=h</a>
-
-        .</li>
-
-        <li>Benchmark test! Building OOo requires huge resources. We just
-        would like to know the build timings, so that how your machine is
-        well tuned for demanding jobs.
-        <a href="http://porting.openoffice.org/freebsd/benchmark.html" shape="rect">
-        http://porting.openoffice.org/freebsd/benchmark.html</a>
-
-        . Currently, GOTO daichi (daichi)'s Pentium 4 3.0GHz machine
-        build fastest. Just 1h25m22.42s for second build of OOo 1.1.4,
-        using ccache.</li>
-
-        <li>SDK tutorial is available at
-        <a href="http://porting.openoffice.org/freebsd/sdk.html" shape="rect">
-        http://porting.openoffice.org/freebsd/sdk.html</a>
-        </li>
-
-        <li>Still implementation test and quality assurance have not yet
-        been done. Even systematic documentations are not yet available
-        for FreeBSD.
-        <a href="http://porting.openoffice.org/freebsd/testing.html" shape="rect">
-        http://porting.openoffice.org/freebsd/testing.html</a>
-
-        and
-        <a href="http://porting.openoffice.org/freebsd/QA.html" shape="rect">
-        http://porting.openoffice.org/freebsd/QA.html</a>
-
-        for details.</li>
-      </ul>
-
-      Acknowledgments Two persons contributed in many aspects. Pavel
-      Janik (reviewing and giving me much advice) and Kris Kennaway
-      (extremely patient builder). and (then, alphabetical order by first
-      name). daichi, Eric Bachard, kan, lofi, Martin Hollmichel, nork,
-      obrien, Sander Vesik, sem, Stefan Taxhet, and volunteers of
-      OpenOffice.org developers (esp. SUN Microsystems, Inc.) for
-      cooperation and warm encouragements.</p>
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">The FreeBSD ports collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="The FreeBSD ports collection">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://portsmon.firepipe.net/index.html" title="http://portsmon.firepipe.net/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.firepipe.net/index.html" title="FreeBSD ports monitoring system">http://portsmon.firepipe.net/index.html</a></td></tr></table><p>
-	Contact: 
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon_at_FreeBSD_dot_org">linimon_at_FreeBSD_dot_org</a>&gt;
-	<br />
-	Contact: 
-          Erwin
-
-          Lansing
-         &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last report on the Ports Collection, much has changed.
-      Organizationally, the portmgr team saw the departure of some of the
-      long-term members, and the addition of some newer members, Oliver
-      Eikemeier, Kirill Ponomarew and Mark Linimon. Later on, portmgr
-      also had to say goodbye to Will Andrews. In addition, we have
-      gained quite a few new ports committers during this time period,
-      and their contributions are quite welcome!</p>
-
-      <p>Most effort was devoted to two releases. The 5.3 release saw an
-      especially long freeze period, but due to the good shape of the
-      ports tree, the freeze for the 4.11 could be kept to a minimum.
-      Several iterations of new infrastructure changes were tested on the
-      cluster and committed. Also, the cluster now builds packages for
-      6-CURRENT, increasing the total number of different build
-      environment to 10.</p>
-
-      <p>Additionally, several sweeps through the ports tree were made to
-      bring more uniformity in variables used in the different ports and
-      their values, e.g.
-      <tt>BROKEN</tt>
-
-      ,
-      <tt>IGNORE</tt>
-
-      ,
-      <tt>DEPRECATED</tt>
-
-      ,
-      <tt>USE_GCC</tt>
-
-      , and others.</p>
-
-      <p>In technical terms, the largest change was moving to the X.org
-      codebase as our default X11 implementation. At the same time, code
-      was committed to be able to select either the X.org code or the
-      XFree86 code, which also saw an update during that time. Due to
-      some hard work by Eric Anholt, new committer Dejan Lesjak, and Joe
-      Marcus Clarke, all of this happened more smoothly than could have
-      reasonably been expected.</p>
-
-      <p>As well, GNOME and KDE saw updates during this time, as did Perl
-      and the Java framework. Further, there were some updates to the
-      Porter's Handbook, but more sections are still in need of updates
-      to include recent changes in practices. Also, during this time,
-      Bill Fenner was able to fix a bug in his
-      <a href="http://people.FreeBSD.org/~fenner/portsurvey" shape="rect">distfile
-      survey</a>
-
-      .</p>
-
-      <p>Shortly before the release for 4.11 our existing linux_base was
-      marked forbidden due to security issues. A lot of effort was spent
-      to upgrade the default version to 8 from 7 to ship 4.11 with a
-      working linuxolator.</p>
-
-      <p>Due to stability problems in the April-May timeframe, the
-      package builds for the Alpha were dropped. After Ken Smith and
-      others put some work into the Alphas in the build cluster, package
-      builds for 4.X were reenabled late in 2004.</p>
-
-      <p>Ports QA reminders -- portmgr team members are now sending out
-      periodic email about problems in the Ports Collection. The current
-      set includes:
-      <ul>
-        <li>a public list of all ports to be removed due to security
-        problems, build failures, or general obsolescence, unless they
-        are fixed first</li>
-
-        <li>private email to all maintainers of the affected ports
-        (including ports dependent on the above)</li>
-
-        <li>private email to all maintainers of ports that are marked
-        <tt>BROKEN</tt>
-
-        and/or
-        <tt>FORBIDDEN</tt>
-        </li>
-
-        <li>private email to maintainers who aren't committers, who have
-        PRs filed against their ports (to flag PRs that might never have
-        been Cc:ed to them)</li>
-
-        <li>public email about port commits that break building of
-        <tt>INDEX</tt>
-        </li>
-
-        <li>public email about port commits that send the revision
-        metadata backwards (and thus confuse tools like portupgrade)</li>
-      </ul>
-
-      The idea behind each of these reminders is to try to increase the
-      visibility of problems in the Ports Collection so that problems can
-      be fixed faster.</p>
-
-      <p>Finally, it should be noted that we passed yet another milestone
-      and the Ports Collection now contains over 12,000 ports.</p>
-    <h3>Open tasks:</h3><ol><li>The majority of our build errors are still due to compilation
-      problems, primarily from the gcc upgrades. Thanks to the efforts of
-      many volunteers, these are decreasing, but there is still much more
-      work to be done.</li><li>The next highest number of build errors are caused by code
-      that does not build on our 64-bit architectures due to the
-      assumption that "all the world's a PC."
-      <a href="http://portsmon.firepipe.net/ploticus/uniqueerrorcounts.html" shape="rect">
-      Here is the entire list</a>
-
-      ; the individual bars are clickable. This will become more and more
-      important now that the amd64 port has been promoted to tier-1
-      status.</li><li>A lot of progress has been meed to crack down on ports that
-      install files outside the approved directories and/or do not
-      de-install cleanly (see "Extra files not listed in PLIST" on
-      <a href="http://pointyhat.FreeBSD.org/errorlogs/" shape="rect">pointyhat</a>
-
-      ) and this will remain a focus area.</li></ol><hr /><h2><a name="Update-of-the-Linux-userland-infrastructure" href="#Update-of-the-Linux-userland-infrastructure" id="Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></h2><p>
-	Contact: 
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The default linux_base port port was changed from the RedHat 7
-      based emulators/linux_base to the RedHat 8 based
-      emulators/linux_base-8 just in time for FreeBSD 4.11-Release
-      because of a security problem in emulators/linux_base. In the
-      conversion process several problems where fixed in some Linux
-      ports.</p>
-
-      <p>Both RedHat 7 and 8 are at their end of life, so expect an
-      update to a more recent Linux distribution in the future. For QA
-      reasons this update wasn't scheduled before FreeBSD
-      4.11-Release.</p>
-    <hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="ALTQ" href="#ALTQ" id="ALTQ">ALTQ</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~mlaier/ALTQ_driver/" title="http://people.freebsd.org/~mlaier/ALTQ_driver/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mlaier/ALTQ_driver/" title="">http://people.freebsd.org/~mlaier/ALTQ_driver/</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=altq&amp;manpath=FreeBSD+6.0-current&amp;format=html" title="http://www.freebsd.org/cgi/man.cgi?query=altq&amp;manpath=FreeBSD+6.0-current&amp;format=html">ALTQ(4) man-page.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=altq&amp;manpath=FreeBSD+6.0-current&amp;format=html" title="ALTQ(4) man-page.">http://www.freebsd.org/cgi/man.cgi?query=altq&amp;manpath=FreeBSD+6.0-current&amp;format=html</a></td></tr></table><p>
-	Contact: 
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p>
-      <p>ALTQ is part of FreeBSD 5.3 release and can be used to do
-      traffic shaping and classification with PF. In CURRENT IPFW gained
-      the ability to do ALTQ classification as well. A steadily
-      increasing number of NIC drivers has been converted to support
-      ALTQ. For details see the ALTQ(4) man-page.</p>
-    <h3>Open tasks:</h3><ol><li>Convert/test more NIC drivers.</li><li>Write documentation.</li></ol><hr /><h2><a name="Cronyx-Adapters-Drivers" href="#Cronyx-Adapters-Drivers" id="Cronyx-Adapters-Drivers">Cronyx Adapters Drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cronyx.ru/software" title="http://www.cronyx.ru/software">Cronyx Software download page.</a></td><td>
-	    URL: <a href="http://www.cronyx.ru/software" title="Cronyx Software download page.">http://www.cronyx.ru/software</a></td></tr></table><p>
-	Contact: 
-          Roman
-
-          Kurakin
-         &lt;<a href="mailto:rik@FreeBSD.org">rik@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently FreeBSD supports three family of Cronyx sync adapters:
-      Tau-PCI - cp(4), Tau-ISA - ctau(4) and Sigma - cx(4). All these
-      drivers were updated (in 6.current) and now they are Giant free.
-      However, this is true only for sppp(4). If you are using Netgraph
-      or async mode (for Sigma) you may need to turn mpsafenet off for
-      that driver with appropriate kernel variable.</p>
-    <h3>Open tasks:</h3><ol><li>Now all these drivers and sppp(4) are using recursive lock.
-      So the first task is to make these locks non recursive.</li><li>Second task is to check/make drivers workable in
-      netgraph/async mode.</li><li>I think about ability to switch between sppp/netgraph mode at
-      runtime. For now you should recompile module/kernel to change
-      mode.</li></ol><hr /><h2><a name="OpenBSD-packet-filter---pf" href="#OpenBSD-packet-filter---pf" id="OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pf4freebsd.love2party.net/" title="http://pf4freebsd.love2party.net/">PF4FreeBSD Homepage</a></td><td>
-	    URL: <a href="http://pf4freebsd.love2party.net/" title="PF4FreeBSD Homepage">http://pf4freebsd.love2party.net/</a></td></tr></table><p>
-	Contact: 
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Daniel
-
-          Hartmeier
-         &lt;<a href="mailto:dhartmei@FreeBSD.org">dhartmei@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD 5.3 is the first release to include PF. It went out
-      okay, but some bugs were discovered too late to make it on the CD.
-      It is recommend to update `src/sys/contrib/pf' to RELENG_5. The
-      specific issues addressed are:</p>
-
-      <ul>
-        <li>Possible NULL-deref with user/group rules.</li>
-
-        <li>Crash with binat on dynamic interfaces.</li>
-
-        <li>Silent dropping of IPv6 packets with option headers.</li>
-
-        <li>Endless loops with `static-port' rules.</li>
-      </ul>
-
-      <p>Most of these issues were discovered by FreeBSD users and got
-      fed back to OpenBSD. This is a prime example of open source at
-      work.</p>
-
-      <p>The Handbook's Firewall section was modified to mention PF as an
-      alternative to IPFW and IPF.</p>
-    <h3>Open tasks:</h3><ol><li>Write more documentation/articles.</li><li>Write an IPFilter to PF migration guide/tool.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="EuroBSDCon-2004-submitted-papers-are-online" href="#EuroBSDCon-2004-submitted-papers-are-online" id="EuroBSDCon-2004-submitted-papers-are-online">EuroBSDCon 2004 submitted papers are online</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon2004.de/papers.html" title="http://www.eurobsdcon2004.de/papers.html">Papers/Presentations Download Page</a></td><td>
-	    URL: <a href="http://www.eurobsdcon2004.de/papers.html" title="Papers/Presentations Download Page">http://www.eurobsdcon2004.de/papers.html</a></td></tr></table><p>
-	Contact: 
-          Patrick M.
-
-          Hausen
-         &lt;<a href="mailto:hausen@punkt.de">hausen@punkt.de</a>&gt;
-	</p>
-      <p>Finally all of the papers and presentations are online for
-      download from our conference website. Thanks again to all who
-      helped make EuroBSDCon 2004 a success.</p>
-    <hr /><h2><a name="EuroBSDCon-2005---Basel-/-Switzerland" href="#EuroBSDCon-2005---Basel-/-Switzerland" id="EuroBSDCon-2005---Basel-/-Switzerland">EuroBSDCon 2005 - Basel / Switzerland</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon.org/" title="http://www.eurobsdcon.org/">EuroBSDCon Homepage</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org/" title="EuroBSDCon Homepage">http://www.eurobsdcon.org/</a></td></tr></table><p>
-	Contact: 
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p>
-      <p>This year's EuroBSDCon will be held at the University of Basel,
-      Switzerland from 25th through 27th November. The call for papers
-      should happen shortly. Please consider attending or even
-      presenting. Check the conference homepage for more information.</p>
-    <hr /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/">FreeBSD Security Information</a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="FreeBSD Security Information">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/security/charter.html" title="http://www.freebsd.org/security/charter.html">FreeBSD Security Officer Charter</a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/charter.html" title="FreeBSD Security Officer Charter">http://www.freebsd.org/security/charter.html</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam">FreeBSD Security Team members</a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="FreeBSD Security Team members">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/">FreeBSD VuXML web site</a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="FreeBSD VuXML web site">http://vuxml.freebsd.org/</a></td></tr><tr><td><a href="http://cvsweb.freebsd.org/ports/security/portaudit/" title="http://cvsweb.freebsd.org/ports/security/portaudit/">portaudit</a></td><td>
-	    URL: <a href="http://cvsweb.freebsd.org/ports/security/portaudit/" title="portaudit">http://cvsweb.freebsd.org/ports/security/portaudit/</a></td></tr></table><p>
-	Contact: 
-          Jacques
-
-          Vidrine
-         &lt;<a href="mailto:nectar@FreeBSD.org">nectar@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Security Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Security Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>During 2004, there were several notable changes and events
-      related to the FreeBSD Security Officer role and Security Team.</p>
-
-      <p>The charter for the Security Officer (SO) as approved by Core in
-      2002 was finally published on the web site. This document describes
-      the mission, responsibilities, and authorities of the SO. (The
-      current SO is Jacques Vidrine.)</p>
-
-      <p>The SO is supported by a Deputy SO and the Security Team. In
-      April, Chris Faulhaber resigned as Deputy SO and Dag-Erling
-      Smorgrav was appointed in his place. Also during the year, the
-      following team members resigned: Julian Elischer, Bill Fumerola,
-      Daniel Harris, Trevor Johnson, Kris Kennaway, Mark Murray, Wes
-      Peters, Bruce Simpson, and Bill Swingle; while the following became
-      new members: Josef El-Rayes, Simon L. Nielsen, Colin Percival, and
-      Tom Rhodes. A huge thanks is due to all past and current members!
-      The current Security Team membership is published on the web
-      site.</p>
-
-      <p>With the release of FreeBSD 4.8, the SO began extended support
-      for some FreeBSD releases and their corresponding security
-      branches. "Early adopter" branches, such as FreeBSD 5.0
-      (RELENG_5_0), are supported for at least six months. "Normal"
-      branches are supported for at least one year. "Extended" branches,
-      such as FreeBSD 5.3 (RELENG_5_3), are supported for at least two
-      years. The currently supported branches and their estimated "end of
-      life" (EoL) dates are published on the FreeBSD Security Information
-      web page. In 2004, four releases "expired": 4.7, 4.9, 5.1, and
-      5.2.</p>
-
-      <p>With the releases of FreeBSD 4.10 and 5.3, the SO and the
-      Release Engineering team extended the scope of security branches to
-      incorporate critical bug fixes unrelated to security issues.
-      Currently, separate Errata Notices are published for such fixes. In
-      the future, Security Advisories and Errata Notices will be merged
-      and handled uniformly.</p>
-
-      <p>17 Security Advisories were published in 2004, covering 8 issues
-      specific to FreeBSD and 9 general issues.</p>
-
-      <p>2004 also saw the introduction of the Vulnerabilities and
-      Exposures Markup Language (VuXML). VuXML is a markup language
-      designed for the documentation of security issues within a single
-      package collection. Over 325 security issues in the Ports
-      Collection have been documented already in the FreeBSD Project's
-      VuXML document by the Security Team and other committers. This
-      document is currently maintained in the ports repository, path
-      ports/security/vuxml/vuln.xml. The contents of the document are
-      made available in a human-readable form at the FreeBSD VuXML web
-      site. The "portaudit" tool can be used to audit your local system
-      against the listed issues. Starting in November, the popular
-      FreshPorts.org web site also tracks issues documented in VuXML.</p>
-    <hr /><h2><a name="FreeBSD-Source-Repository-Mirror-for-svn/svk" href="#FreeBSD-Source-Repository-Mirror-for-svn/svk" id="FreeBSD-Source-Repository-Mirror-for-svn/svk">FreeBSD Source Repository Mirror for svn/svk</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.clkao.org/svnweb/freebsd/" title="http://svn.clkao.org/svnweb/freebsd/">Repository browser.</a></td><td>
-	    URL: <a href="http://svn.clkao.org/svnweb/freebsd/" title="Repository browser.">http://svn.clkao.org/svnweb/freebsd/</a></td></tr><tr><td><a href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/" title="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/">RSS for RELENG_5 commits.</a></td><td>
-	    URL: <a href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/" title="RSS for RELENG_5 commits.">http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/</a></td></tr><tr><td><a href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/" title="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/">RSS for CURRENT commits.</a></td><td>
-	    URL: <a href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/" title="RSS for CURRENT commits.">http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/</a></td></tr><tr><td><a href="http://svk.elixus.org/" title="http://svk.elixus.org/">svk homepage.</a></td><td>
-	    URL: <a href="http://svk.elixus.org/" title="svk homepage.">http://svk.elixus.org/</a></td></tr></table><p>
-	Contact: 
-          Kao
-
-          Chia-liang
-         &lt;<a href="mailto:clkao@FreeBSD.org">clkao@FreeBSD.org</a>&gt;
-	</p>
-      <p>A public Subversion mirror of the FreeBSD repository is provided
-      at svn://svn.clkao.org/freebsd/. This is intended for people who
-      would like to try the svk distributed version control system.</p>
-
-      <p>svk allows you to mirror the whole repository and commit when
-      offline. It also provides history-sensitive branching, merging, and
-      patches. Non-committers can easily maintain their own branch and
-      track upstream changes while their patches are being reviewed.</p>
-    <hr /><h2><a name="Wiki-with-new-software" href="#Wiki-with-new-software" id="Wiki-with-new-software">Wiki with new software</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/" title="http://wiki.freebsd.org/">Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/" title="Wiki">http://wiki.freebsd.org/</a></td></tr></table><p>
-	Contact: 
-          Josef
-
-          El-Rayes
-         &lt;<a href="mailto:josef@FreeBSD.org">josef@FreeBSD.org</a>&gt;
-	</p>
-      <p>After experiencing spam attacks on the old wiki-engine caused by
-      non-existent authentification mechanism, I had to replace it with a
-      more advanced software. Instead of usemod, we now run moinmoin. As
-      a consequence it's no longer just a 'browse &amp; edit', but you
-      have to sign up and let someone who is already in the ACL group
-      'developers' add you to the group. So it is a 'developers-only'
-      resource now. The old wiki is found at
-      <a href="http://wiki2.daemon.li" shape="rect">http://wiki2.daemon.li</a>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Move content from old wiki to new one.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2005-01-2005-03.html b/website/content/en/status/report-2005-01-2005-03.html
deleted file mode 100644
index 39be80069d..0000000000
--- a/website/content/en/status/report-2005-01-2005-03.html
+++ /dev/null
@@ -1,1475 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The first quarter of 2005 has been extremely active in both
-    FreeBSD-CURRENT and -STABLE. With FreeBSD 5.4 in the final RC stage
-    and an anticipated branch of FreeBSD-6 this summer we have seen a lot
-    of performance improvements in 5 and a couple of exciting new
-    features in 6.</p><p>The report turnout was extremely good and it seems that the
-    webform provided by Julian Elischer has made it more enjoyable to
-    write reports. Many thanks to Julian for providing this.  We also
-    like to get your attention to the open tasks section provided in some
-    reports.</p><p>On special note, please take a look at the report about the
-    upcoming BSDCan in Ottawa. There will be lots of interesting FreeBSD
-    related talks and activities. If you enjoy reading these reports, you
-    will love the conference. See you there!</p><p>Thanks to all the reporters, we hope you enjoy reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Common-Address-Redundancy-Protocol---CARP">Common Address Redundancy Protocol - CARP</a></li><li><a href="#FreeBSD-Java-Project">FreeBSD Java Project</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#GELI---GEOM-class-for-providers-encryption">GELI - GEOM class for providers encryption</a></li><li><a href="#GSHSEC---GEOM-class-for-handling-shared-secret">GSHSEC - GEOM class for handling shared secret</a></li><li><a href="#Secure-Updating">Secure Updating</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Dutch-Documentation-Project">FreeBSD Dutch Documentation Project</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ATAPI/CAM">ATAPI/CAM</a></li><li><a href="#Coverity-Code-Analysis">Coverity Code Analysis</a></li><li><a href="#cpufreq">cpufreq</a></li><li><a href="#drm">drm</a></li><li><a href="#Filesystem-journalling-for-UFS">Filesystem journalling for UFS</a></li><li><a href="#Infrastructure-Cleanup">Infrastructure Cleanup</a></li><li><a href="#Interrupt-Latency">Interrupt Latency</a></li><li><a href="#Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></li><li><a href="#Many-subdirs-for-UFS">Many subdirs for UFS</a></li><li><a href="#Status-Report-for-FreeBSD-ATA-driver-project">Status Report for FreeBSD ATA driver project</a></li><li><a href="#Storage-driver-SMPng-locking">Storage driver SMPng locking</a></li></ul><h3><a href="#Network-infrastructure">Network infrastructure</a></h3><ul><li><a href="#Dingo">Dingo</a></li><li><a href="#IPv6-Support-for-IPFW">IPv6 Support for IPFW</a></li><li><a href="#Move-ARP-out-of-routing-table">Move ARP out of routing table</a></li><li><a href="#netgraph(4)-status-report">netgraph(4) status report</a></li><li><a href="#New-Wireless-Drivers">New Wireless Drivers</a></li><li><a href="#Removable-interface-improvements.">Removable interface improvements.</a></li><li><a href="#Support-for-telephone-hardware-(aka-Zaptel)">Support for telephone hardware (aka Zaptel)</a></li><li><a href="#Wireless-Networking-Support">Wireless Networking Support</a></li></ul><h3><a href="#Userland-programs">Userland programs</a></h3><ul><li><a href="#libthread">libthread</a></li><li><a href="#Pipe-namespace-added-to-portalfs">Pipe namespace added to portalfs</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#ARM-Support-for-TS-7200">ARM Support for TS-7200</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li><li><a href="#XenFreeBSD---FreeBSD-on-Xen">XenFreeBSD - FreeBSD on Xen</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></li><li><a href="#twa-driver">twa driver</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan">BSDCan</a></li><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#IMUNES---a-FreeBSD-based-kernel-level-network-topology-emulator">IMUNES - a FreeBSD based kernel-level network topology
-    emulator</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Common-Address-Redundancy-Protocol---CARP" href="#Common-Address-Redundancy-Protocol---CARP" id="Common-Address-Redundancy-Protocol---CARP">Common Address Redundancy Protocol - CARP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=carp&amp;manpath=FreeBSD+6.0-current" title="http://www.freebsd.org/cgi/man.cgi?query=carp&amp;manpath=FreeBSD+6.0-current"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=carp&amp;manpath=FreeBSD+6.0-current" title="">http://www.freebsd.org/cgi/man.cgi?query=carp&amp;manpath=FreeBSD+6.0-current</a></td></tr><tr><td><a href="http://people.freebsd.org/~mlaier/CARP/" title="http://people.freebsd.org/~mlaier/CARP/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mlaier/CARP/" title="">http://people.freebsd.org/~mlaier/CARP/</a></td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-          Gleb
-
-          Smirnoff
-         &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>CARP is an alternative to VRRP. In contrast to VRRP it has full
-      support for IPv6 and uses crypto to protect the advertisements. It
-      was developed by OpenBSD due to concerns that the HSRP patent might
-      cover VRRP and CISCO might defend its patent. CARP has, since then,
-      improved a lot over VRRP.</p>
-
-      <p>CARP has been committed to HEAD and MFCed to RELENG_5. It will
-      be available in upcoming 5.4-RELEASE.</p>
-
-      <p>Big thanks to all users who provided testing and reported bugs
-      to Max and Gleb. Daniel Seuffert has donated hardware to Max for
-      this project. Gleb's work was sponsored by
-      <a href="http://www.rambler.ru" shape="rect">Rambler</a>
-
-      .</p>
-    <h3>Open tasks:</h3><ol><li>Improve vlan(4) support. Test ng_eiface(4).</li><li>Improve locking, consider removing interface layer.</li></ol><hr /><h2><a name="FreeBSD-Java-Project" href="#FreeBSD-Java-Project" id="FreeBSD-Java-Project">FreeBSD Java Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/java/" title="http://www.FreeBSD.org/java/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/java/" title="">http://www.FreeBSD.org/java/</a></td></tr></table><p>
-	Contact:
-          Greg
-
-          Lewis
-         &lt;<a href="mailto:glewis@FreeBSD.org">glewis@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexey
-
-          Zelkin
-         &lt;<a href="mailto:phantom@FreeBSD.org">phantom@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Java Project released its initial support for JDK
-      1.5.0 with patch set 1 "Sabretooth" in January. The initial release
-      featured support for both FreeBSD 5.3/i386 and 5.3/amd64. Since
-      then preliminary support for FreeBSD 4.11/i386 has been added and
-      several bug fixes have been made. Updates in the coming months will
-      add support for the browser plug in and Java Web Start, which were
-      not in the initial release.</p>
-    <h3>Open tasks:</h3><ol><li>Volunteers to look into some serious problems with JDK 1.5.0
-      on FreeBSD 4.x</li></ol><hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/releng" title="http://www.freebsd.org/releng"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releng" title="">http://www.freebsd.org/releng</a></td></tr></table><p>
-	Contact:
-          RE
-          Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD 4.11, the final formal release of the 4.x series, was
-      released on 25 Jan 2005.  Many thanks to the all of the developers
-      and users over the past 5 years who made it successful.  While no
-      more releases are planned, the security team will continue to
-      support it through security update patches until 2007.  Developers
-      are also free to commit bug fixes and low-risk features to the
-      RELENG_4 branch for the foreseeable future.</p>
-      <p>FreeBSD 5.4 is going through its final release candidate stages
-      and is expected to be released in late April.  Its focus is mostly
-      bug fixes and minor feature and performance improvements, so it is
-      an excellent target for those looking to upgrade from previous
-      versions or to give FreeBSD a try for the first time.  FreeBSD 5.5
-      will be release in about 4-6 months after 5.4.</p>
-      <p>FreeBSD 6.0 is rapidly approaching also.  In contrast to FreeBSD
-      5.0, the goal is to take a more incremental approach to major
-      changes, and not wait for years to get as many features in as
-      possible.  FreeBSD 6.0 will largely be an evolutionary change from
-      the 5.x series, with the largest changes centered around
-      multi-threading and streamlining the filesystem and device layers.
-      Feature freeze and code freeze for 6.0 are coming up in May and
-      June, and we hope to have 6.0 stable and ready for release in July
-      or August.</p>
-      <p>The release engineering team has also started doing monthly
-      informal snapshots of the 6-CURRENT and 5-STABLE trees.  These are
-      intended to increase the exposure of new features and get more
-      users involved in testing and providing feedback.  Snapshots can
-      be found at <a href="http://www.freebsd.org/snapshots" shape="rect">
-      http://www.freebsd.org/snapshots</a>.</p>
-    <hr /><h2><a name="GELI---GEOM-class-for-providers-encryption" href="#GELI---GEOM-class-for-providers-encryption" id="GELI---GEOM-class-for-providers-encryption">GELI - GEOM class for providers encryption</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sys/geom/eli&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sys/geom/eli&amp;HIDEDEL=NO">Kernel module.</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sys/geom/eli&amp;HIDEDEL=NO" title="Kernel module.">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sys/geom/eli&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sbin/geom/class/eli&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sbin/geom/class/eli&amp;HIDEDEL=NO">Userland configuration utility.</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sbin/geom/class/eli&amp;HIDEDEL=NO" title="Userland configuration utility.">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/geom%5fclasses/sbin/geom/class/eli&amp;HIDEDEL=NO</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>GELI is a GEOM class used for GEOM providers encryption. I
-      decided to work on this, as I needed some feature, which cannot be
-      found in similar projects. Here is the list of features, I found
-      interesting:</p>
-
-      <ul>
-        <li>makes use of crypto(9)</li>
-
-        <li>if there is a crypto hardware available, GELI will run
-        cryptography on it automatically; if not, it starts dedicated
-        kernel thread and do crypto software work in there</li>
-
-        <li>supports many cryptographic algorithms (AES, Blowfish,
-        3DES)</li>
-
-        <li>is able to take key components from many sources at once
-        (user entered passphrase, random bits from a file, etc.)</li>
-
-        <li>allows to encrypt root partition</li>
-
-        <li>user will be asked for the passphrase before root file system
-        is mounted</li>
-
-        <li>uses "PKCS #5: Password-Based Cryptography Specification
-        Version 2.0" for user passphrase protection (optional)</li>
-
-        <li>allows to use two independent keys (e.g. "user key" and
-        "company key")</li>
-
-        <li>is fast</li>
-
-        <li>GELI does simple sector-to-sector encryption</li>
-
-        <li>allows to backup/restore Master Keys, so when user have to
-        quickly destroy keys, it is able to get the data back by
-        restoring keys from the backup</li>
-
-        <li>provider can be configured at attach time to automatically
-        detach on last close (so user don't have to remember to detach
-        after unmounting file system)</li>
-
-        <li>allows to attach provider with a random, one-time keys</li>
-
-        <li>useful for swap partitions and temporary file systems</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Code audit/review is more than welcome!</li></ol><hr /><h2><a name="GSHSEC---GEOM-class-for-handling-shared-secret" href="#GSHSEC---GEOM-class-for-handling-shared-secret" id="GSHSEC---GEOM-class-for-handling-shared-secret">GSHSEC - GEOM class for handling shared secret</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=gshsec&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+6.0-current&amp;format=html" title="http://www.freebsd.org/cgi/man.cgi?query=gshsec&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+6.0-current&amp;format=html">Manual page.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=gshsec&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+6.0-current&amp;format=html" title="Manual page.">http://www.freebsd.org/cgi/man.cgi?query=gshsec&amp;apropos=0&amp;sektion=0&amp;manpath=FreeBSD+6.0-current&amp;format=html</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>GSHSEC is a GEOM class used for handling shared secret data
-      between multiple GEOM providers. For every write request, SHSEC
-      class splits the data using XOR operation with random data, so N-1
-      providers gets just random data and one provider gets the data
-      XORed with the random data from the other providers. All of the
-      configured providers must be present in order to reveal the secret.
-      The class is already committed to HEAD and RELENG_5 branches.</p>
-    <hr /><h2><a name="Secure-Updating" href="#Secure-Updating" id="Secure-Updating">Secure Updating</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/portsnap/" title="http://www.daemonology.net/portsnap/"></a></td><td>
-	    URL: <a href="http://www.daemonology.net/portsnap/" title="">http://www.daemonology.net/portsnap/</a></td></tr><tr><td><a href="http://www.daemonology.net/freebsd-update/" title="http://www.daemonology.net/freebsd-update/"></a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-update/" title="">http://www.daemonology.net/freebsd-update/</a></td></tr></table><p>
-	Contact:
-          Colin
-
-          Percival
-         &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>Shortly before the ports freeze for FreeBSD 5.4, I released a
-      new version of Portsnap. In addition to being secure and more
-      efficient than CVSup, this latest version distributes INDEX,
-      INDEX-5, and INDEX-6 files, thereby eliminating the need to run
-      "make fetchindex" and ensuring that the ports INDEX will match the
-      existing ports tree. In addition, portsnap builds have now moved
-      onto hardware managed by the FreeBSD project, thereby sharply
-      increasing portsnap's chances of survival if I get hit by a
-      bus.</p>
-
-      <p>In early February hardware problems caused both FreeBSD Update
-      and Portsnap to stop functioning for a few days, but those were
-      resolved thanks to a server donated by layeredtech.com.</p>
-
-      <p>I intend bring Portsnap into the FreeBSD base system before the
-      end of the month, followed by FreeBSD Update a few months
-      later.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="FreeBSD-Dutch-Documentation-Project" href="#FreeBSD-Dutch-Documentation-Project" id="FreeBSD-Dutch-Documentation-Project">FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/doc/nl/books/handbook" title="http://www.freebsd.org/doc/nl/books/handbook">FreeBSD Dutch Handbook</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/nl/books/handbook" title="FreeBSD Dutch Handbook">http://www.freebsd.org/doc/nl/books/handbook</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd_html/" title="http://www.evilcoder.org/freebsd_html/">FreeBSD Dutch Handbook preview</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd_html/" title="FreeBSD Dutch Handbook preview">http://www.evilcoder.org/freebsd_html/</a></td></tr><tr><td><a href="http://www.evilcoder.org/content/section/6/39/" title="http://www.evilcoder.org/content/section/6/39/">The Project Page</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/content/section/6/39/" title="The Project Page">http://www.evilcoder.org/content/section/6/39/</a></td></tr></table><p>
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation Project is a ongoing project in
-      translating the English documentation to the Dutch language.
-      Currently we have translated almost the entire handbook, and more
-      to come. If you want to help out by review the Dutch documents, or
-      you want to help translating the remainders of the handbook or
-      other documents, feel free to contact me at
-      <a href="mailto:remko@FreeBSD.org" shape="rect">remko@FreeBSD.org</a>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Translate the English handbook, then review the Dutch
-      handbook</li><li>Translate the English FAQ, then review the Dutch FAQ</li><li>Translate the English Articles, then review the Dutch
-      Articles</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="ATAPI/CAM" href="#ATAPI/CAM" id="ATAPI/CAM">ATAPI/CAM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Thomas
-
-          Quinot
-         &lt;<a href="mailto:thomas@FreeBSD.org">thomas@FreeBSD.org</a>&gt;
-	</p>
-      <p>ATAPI/CAM integration with the new ATA (mkIII) framework is now
-      completed. ATAPI/CAM is now available as a loadable module
-      (atapicam.ko). It is also independent from the native ATAPI drivers
-      again, as was the case before mkIII.</p>
-
-      <p>Thanks to Scott Long and S�ren Schmidt for their
-      participation in the integration work.</p>
-    <hr /><h2><a name="Coverity-Code-Analysis" href="#Coverity-Code-Analysis" id="Coverity-Code-Analysis">Coverity Code Analysis</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.coverity.com/" title="http://www.coverity.com/"></a></td><td>
-	    URL: <a href="http://www.coverity.com/" title="">http://www.coverity.com/</a></td></tr></table><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>There has been an ongoing effort to review the kernel source
-      code using Coverity's source code analysis tools
-      (http://www.coverity.com). These tools check for a variety of
-      problems such as null pointer dereference, use-after-free of
-      allocated variables, invalid array references, etc. This work is a
-      joint project between FreeBSD and Coverity.</p>
-
-      <p>Two passes have been completed over the 6-current kernel source
-      code base and all significant problems have been corrected. These
-      runs were done in February and March of this year. A few reports of
-      minor problems await response from outside groups and will be
-      resolved in time for the first 6.x release. Another analysis run
-      over the kernel will happen soon. We are looking for a way to use
-      these tools on a regular basis as they have been helpful in
-      improving the code base.</p>
-
-      <p>Thanks to Coverity for their help and especially Ted Unangst.
-      Several developers have been especially helpful in resolving
-      reports: Poul-Henning Kamp, David Schultz, Pawel Jakub Dawidek,
-      George V. Neville-Neil, and Matthew Dodd.</p>
-    <hr /><h2><a name="cpufreq" href="#cpufreq" id="cpufreq">cpufreq</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=cpufreq&amp;manpath=FreeBSD+6.0-current&amp;format=html" title="http://www.freebsd.org/cgi/man.cgi?query=cpufreq&amp;manpath=FreeBSD+6.0-current&amp;format=html">cpufreq man page</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=cpufreq&amp;manpath=FreeBSD+6.0-current&amp;format=html" title="cpufreq man page">http://www.freebsd.org/cgi/man.cgi?query=cpufreq&amp;manpath=FreeBSD+6.0-current&amp;format=html</a></td></tr></table><p>
-	Contact:
-          Nate
-
-          Lawson
-         &lt;<a href="mailto:njl">njl</a>&gt;
-	</p>
-      <p>The cpufreq project was committed to 6-CURRENT in early February
-      and has undergone bugfixes and updates. It will soon be MFCd to
-      5-STABLE.</p>
-
-      <p>The cpufreq driver provides a unified kernel and user interface
-      to CPU frequency control drivers. It combines multiple drivers
-      offering different settings into a single interface of all possible
-      levels. Users can access this interface directly via sysctl(8), by
-      indicating to power_profile that it should switch settings when the
-      AC line state changes, or by using powerd(8).</p>
-
-      <p>For example, an absolute driver offering frequencies of 1000 Mhz
-      and 750 Mhz combined with a relative driver offering settings of
-      100% and 50% would result in cpufreq providing levels of 1000, 750,
-      500, and 375 Mhz.</p>
-
-      <p>Colin Percival helped with powerd(8), which provides automatic
-      control of CPU frequencies. The adaptive mode is especially
-      interesting since it attempts to respond to changes in system load
-      while reducing power consumption.</p>
-
-      <p>Current hardware drivers include acpi_perf (ACPI CPU performance
-      states), est (Intel Enhanced SpeedStep for Pentium-M), ichss
-      (Intel's original SpeedStep for ICH), and powernow (AMD Powernow!
-      K7 and K8 support). Other drivers for relative hardware include
-      acpi_throttle (ACPI CPU throttling) and p4tcc (Pentium 4 Thermal
-      Control Circuitry)</p>
-
-      <p>Thanks to Bruno Ducrot for the powernow driver, Colin Percival
-      for the est driver, and the many testers who have sent in
-      feedback.</p>
-    <h3>Open tasks:</h3><ol><li>We'd appreciate someone with a Transmeta CPU converting the
-      existing longrun driver to the cpufreq framework. It would also be
-      good if someone wrote a VIA Longhaul driver. See the Linux
-      arch/i386/kernel/cpu/cpufreq directory for examples.</li><li>Various other architectures, including ARM, have CPU power
-      control that could be implemented as a cpufreq driver.</li><li>The powerd(8) algorithm is rather simple and we'd appreciate
-      more help in testing it and alternative algorithms with various
-      workloads. The -v flag causes powerd to report frequency
-      transitions and print a summary of total energy used upon
-      termination. This should help testers profile their
-      algorithms.</li></ol><hr /><h2><a name="drm" href="#drm" id="drm">drm</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://r300.sourceforge.net/" title="http://r300.sourceforge.net/">ATI R300 DRI project</a></td><td>
-	    URL: <a href="http://r300.sourceforge.net/" title="ATI R300 DRI project">http://r300.sourceforge.net/</a></td></tr></table><p>
-	Contact:
-          Eric
-
-          Anholt
-         &lt;<a href="mailto:anholt@FreeBSD.org">anholt@FreeBSD.org</a>&gt;
-	</p>
-      <p>A DRM update was finally committed to -current on 2005-04-15,
-      after jhb@ did the necessary fix to vm_mmap. New development
-      drivers were added for mach64 and r300 (see URL for info). The
-      nearly-finished code for savage and i915 were also added, but left
-      disconnected from the build. However, the most visible change is
-      likely the support for texture tiling, color tiling, and HyperZ on
-      Radeons, which (with updated userland) likely provide a 50-75%
-      framerate increase in many applications.</p>
-    <h3>Open tasks:</h3><ol><li>Find someone with newbus knowledge to figure out why the i915
-      won't attach to drmsub0.</li><li>Finish porting the savage driver.</li><li>Integrate busdma code from Tonnerre (NetBSD).</li></ol><hr /><h2><a name="Filesystem-journalling-for-UFS" href="#Filesystem-journalling-for-UFS" id="Filesystem-journalling-for-UFS">Filesystem journalling for UFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/scottl/ufsj" title="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/scottl/ufsj"></a></td><td>
-	    URL: <a href="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/scottl/ufsj" title="">http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/scottl/ufsj</a></td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>It's time to bite the bullet and admit that fsck is no longer
-      scalable for modern storage capacities. While a healthy debate can
-      still be had on the merits and data integrity guarantees of
-      journalling vs. SoftUpdates, the fact that SoftUpdates still
-      requires a fsck to ensure consistency of the filesystem metadata
-      after an unclean shutdown means uptime is lost. While background
-      fsck is available, it saps system performance and stretched the
-      fsck time out to hours.</p>
-
-      <p>Journalling provides a way to record transactions that might not
-      have fully been written to disk before the system crashed, and then
-      quickly recover the system back to a consistent state by replaying
-      these transactions. It doesn't guarantee that no data will be lost,
-      but it does guarantee that the filesystem will be back to a
-      consistent state after the replay is performed. This contrasts to
-      SoftUpdates that re-arranges metadata updates so that
-      inconsistencies are minimized and easy to recover from, though
-      recovery still requires the traditional full filesystem scan.</p>
-
-      <p>Journalling is a key feature of many modern filesystems like
-      NTFS, XFS, JFS, ReiserFS, and Ext3, so the ground is well covered
-      and the risks for UFS/FFS are low. I'm aware that groups from CMU
-      and RPI have attempted similar work in the past, but unfortunately
-      the work is either very outdates, or I haven't had any luck in
-      contacting the groups. Is this absence, I've decided to work on
-      this project myself in hopes of having a functional prototype in
-      time for FreeBSD 6.0.</p>
-
-      <p>The approach is simple and journals full metadata blocks instead
-      of just deltas or high-level operations. This greatly simplifies
-      the replay code at the cost of requiring more disk space for the
-      journal and more work within the filesystem to identify discreet
-      update points. An important design consideration is whether to make
-      the journal data and code compatible with the UFS2 filesystem, or
-      to start a new UFS3 derivative. Since the latter presents a very
-      high barrier to adoption for most people, I'm going to try to make
-      it a compatible option for UFS2. This means that the journal blocks
-      will likely appear as an unlinked file to legacy filesystem and
-      fsck code, and will be treated as such. This will allow seamless
-      fallback to using fsck, though once the unlinked journal data
-      blocks are reclaimed by fsck, the user will have to take action to
-      re-create the journal file again.</p>
-
-      <p>One key piece of journalling is ensuring that each journal
-      transaction is fully written to disk before the associated metadata
-      blocks are written to the filesystem. I plan to adopt the buffer
-      'pinning' mechanism from Alexander Kabaev's XFS work to assist with
-      this. This will allow the journalling subsystem fine-grained
-      control over which blocks get flushed to disk by the buffer daemon
-      without having to further complicate the UFS/FFS code. One
-      consideration is how Softupdates falls into this and whether it is
-      mutually exclusive of journalling or if it can help provide
-      transaction ordering functionality to the journal. Research here is
-      on-going.</p>
-
-      <p>Some preliminary work can be found in Perforce in the
-      //depot/user/scottl/ufsj/... tree or at the URL provided. Hopefully
-      this will quickly accelerate.</p>
-    <hr /><h2><a name="Infrastructure-Cleanup" href="#Infrastructure-Cleanup" id="Infrastructure-Cleanup">Infrastructure Cleanup</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Takahashi
-
-          Yoshihiro
-         &lt;<a href="mailto:nyan@FreeBSD.org">nyan@FreeBSD.org</a>&gt;
-	</p>
-      <p>Unglamorous cleanup of the code base continues. The focus of
-      recent efforts have been to reduce the number of machine #ifdefs
-      that are in the machine independent code. In addition, we're also
-      trying to increase code sharing between pc98 and i386 ports and
-      reduce the number of #ifdef PC98 instances in the tree.</p>
-
-      <p>In addition, a number of cleanup tasks are underway for
-      different parts of the kernel that are more complicated than
-      necessary. Recently, the pccard code's allocation routines were
-      simplified to reassign ownership of resources more directly than
-      before. The search is on for other areas that can benefit from
-      cleanup.</p>
-    <h3>Open tasks:</h3><ol><li>On pc98, there's no such thing as an ISA bus. It is desirable
-      to move to having cbus appear in the probe messages. This would
-      also allow for additional segregation of pc98 specific code in the
-      drivers and eliminate many ifdefs. Ideally, isa and cbus would
-      share a common newbus ancestor class so their similarities can be
-      exploited (they both have PNPBIOS enumeration methods, for
-      example).</li><li>cbus devices can have complicated resources. There's support
-      for vectors of resources. Yet there's no support for populating a
-      vector of resources from the plug and play information. Doing so
-      would help the complex world of pc98 a lot, and the odd edge cases
-      in i386 (floppy, ata) a little.</li><li>The hints mechanism provides a way to associate hardware with
-      drivers and resource that would otherwise be completely unknown to
-      the system. A refinement in the hints mechanism to allow matching
-      of driver instances to resources is desirable. This would allow one
-      to hardwire sio0 to 0x2f8, even when the serial device in the plug
-      and play resource list (or acpi resource list) is listed second. A
-      further refinement could also be wiring sio0 to "port B" as defined
-      by acpi or some other enumeration method. Chances are good that
-      these seemingly related concepts may need separate implementations
-      due to the decision points for unit assignment.</li><li>Pccard, cardbus and usb probe their devices after interrupts
-      are enabled. It would be desirable to hook into new kernel APIs to
-      allow the mounting of root to be put off until those systems know
-      that they are done with their initial probe of the devices present
-      at boot.</li></ol><hr /><h2><a name="Interrupt-Latency" href="#Interrupt-Latency" id="Interrupt-Latency">Interrupt Latency</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>I've setup a test system to measure interrupt latency on FreeBSD
-      5.3 and current. So far I've measured the baseline latency for a
-      300MHz embedded cyrix based single board computer. I've tried a
-      number of different strategies to optimize the interrupt path. Most
-      of these strategies resulted in some improvement of the time it
-      takes to get from the start of the interrupt servicing to the
-      driver's ISR. These improvements turned out to be about 1-2% of the
-      processing times on this single board computer, but a wash on
-      faster machines. However, the time between when the interrupt
-      should happen, and when FreeBSD starts to service the interrupt is
-      the dominant factor in these measurements. Despite the fact that
-      these are fast interrupt handlers (so the scheduler is out of the
-      loop), I routinely see average latencies of 18us, with large
-      variations (on the order of 5us standard deviation).</p>
-    <h3>Open tasks:</h3><ol><li>I need to measure the latencies with 4.x and current to
-      characterize the differences more precisely. I'm especially
-      interested in the effects on interrupt latency that the elimination
-      of mixed mode will cause.</li><li>I need to characterize different parts of our ISR routines to
-      see if some of the variation I've seen so far can be reduced by
-      improved coding techniques.</li><li>I need to re-run my tests with 5.4 and summarize my results
-      in a paper.</li></ol><hr /><h2><a name="Low-overhead-performance-monitoring-for-FreeBSD" href="#Low-overhead-performance-monitoring-for-FreeBSD" id="Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement">Project home page</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="Project home page">http://people.freebsd.org/~jkoshy/projects/perf-measurement</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Many modern CPUs have on-chip performance monitoring counters
-      (PMCs) that can be used to count low-level hardware events like
-      instruction retirals, branch mispredictions, cache and TLB misses
-      and the like. PMC architectures and capabilities vary between CPU
-      vendors and between CPU generations from the same vendor, making
-      the creation of portable applications difficult. This project
-      attempts to provide a uniform API for applications to use, and the
-      necessary infrastructure to "virtualize" and manage the available
-      PMC hardware resources. The creation of performance analysis tools
-      that use this infrastructure is also part of the project's
-      goals.</p>
-
-      <p>Work since the last status report:</p>
-
-      <ul>
-        <li>Support for Intel
-        Pentium-Pro/Pentium-II/Pentium-III/Pentium-M/Celeron style PMCs
-        has been added.</li>
-
-        <li>The Pentium-4/HTT machine dependent layer has been
-        overhauled.</li>
-
-        <li>A Python language interface to the C library interface pmc(3)
-        has been written.</li>
-
-        <li>Many bugs have been fixed and documentation has been
-        updated.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>The code needs to be tested on Intel Pentium-M, Celeron,
-      Pentium II and Pentium Pro CPUs.</li></ol><hr /><h2><a name="Many-subdirs-for-UFS" href="#Many-subdirs-for-UFS" id="Many-subdirs-for-UFS">Many subdirs for UFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://groups-beta.google.com/group/muc.lists.freebsd.fs/browse_frm/thread/a36d1143d695287e/40cad00cf2c0823b?hl=en#40cad00cf2c0823b" title="http://groups-beta.google.com/group/muc.lists.freebsd.fs/browse_frm/thread/a36d1143d695287e/40cad00cf2c0823b?hl=en#40cad00cf2c0823b">Thread on freebsd-fs</a></td><td>
-	    URL: <a href="http://groups-beta.google.com/group/muc.lists.freebsd.fs/browse_frm/thread/a36d1143d695287e/40cad00cf2c0823b?hl=en#40cad00cf2c0823b" title="Thread on freebsd-fs">http://groups-beta.google.com/group/muc.lists.freebsd.fs/browse_frm/thread/a36d1143d695287e/40cad00cf2c0823b?hl=en#40cad00cf2c0823b</a></td></tr></table><p>
-	Contact:
-          David
-
-          Malone
-         &lt;<a href="mailto:dwmalone@FreeBSD.org">dwmalone@FreeBSD.org</a>&gt;
-	</p>
-      <p>I'm currently looking at the limit on the number of
-      subdirectories a directory can have in UFS. There is currently a
-      limit of 32K subdirectories because of the 16 bit link count field
-      in both struct stat and the on-disk inode format. The thread above
-      shows that dirhash provides acceptable performance for directories
-      with 100k subdirectories using a prototype patch. Two options for
-      allowing many subdirectories seem to exist: changing the link
-      counting scheme for directories and expanding the link count field.
-      The prototype patch implements the first scheme and there are plans
-      to investigate the second scheme (which may require an ABI
-      change).</p>
-    <hr /><h2><a name="Status-Report-for-FreeBSD-ATA-driver-project" href="#Status-Report-for-FreeBSD-ATA-driver-project" id="Status-Report-for-FreeBSD-ATA-driver-project">Status Report for FreeBSD ATA driver project</a></h2><p>
-	Contact:
-          S�ren
-
-          Schmidt
-         &lt;<a href="mailto:sos@FreeBSD.org">sos@FreeBSD.org</a>&gt;
-	</p>
-      <p>ATA mkIII has been committed to -current after a couple of month
-      testing as patches post on -current and 5-stable. I will continue
-      to provide patches for 5-stable for those that need up-to-date ATA
-      support there.</p>
-
-      <p>Here a short rehash of what mkIII brings:</p>
-
-      <p>ATA is now fully modular so each part can be loaded/unloaded at
-      will to provided the wanted functionality.</p>
-
-      <p>Much improved SATA support that support hotplug events on
-      controllers that support it (Promise, SiS, nVidia so far) ie the
-      system will automagically detect when SATA devices come and go and
-      add/delete device entries etc.</p>
-
-      <p>Much improved ATA RAID support. The ata-raid driver has been
-      largely rewritten to take advantage of the features the improved
-      infrastructure provides, including composite ATA operations etc.
-      The rebuild functionality has been changed to rebuild on userland
-      reads, so a simple dd of the entire array will get it rebuild (what
-      atacontrol now does). This means that the resources used for this
-      can be better tailored to the actually usage pattern if needed. ATA
-      RAID now supports 10+ different RAID metadata formats, so most BIOS
-      defined ATA RAID arrays can be picked up and used. The number of
-      metadata formats that can be created from within FreeBSD is still
-      limited though and is not a high priority feature right now.</p>
-
-      <p>The lowlevel infrastructure of the ATA driver has been refined
-      even further to support "strange" chipsets much more easily and in
-      most case transparent to the higher levels. This to easy ports to
-      new platforms where ATA controllers doesn't necessarily have the
-      x86 legacy layout.</p>
-
-      <p>Lots of bug fixes and corrections all over the driver proper.
-      The rework of the infrastructure has revealed bugs and deficiencies
-      that has been fixed in the process of modulerising ATA and making
-      the infrastructure more generic, and hopefully easier to
-      understand.</p>
-
-      <p>The work continues to keep ATA on top of new chipsets and other
-      advancements in the ATA camp. SATA ATAPI support is in the works
-      and so are support for NCA/TCQ (tags). Donations of unsupported
-      hardware is the way to get it supported as I'm way out of my budget
-      for new hardware for the next decade or so according to my wife
-      :)</p>
-    <h3>Open tasks:</h3><ol><li>Lots of testing wanted, especially SATA and RAID
-      support</li></ol><hr /><h2><a name="Storage-driver-SMPng-locking" href="#Storage-driver-SMPng-locking" id="Storage-driver-SMPng-locking">Storage driver SMPng locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Several storage drivers have been taken out from under the Giant
-      mutex in the past few months. Thanks to sponsorship from
-      <a href="http://www.freebsdsystems.com" shape="rect">FreeBSD Systems, Inc</a>
-
-      and
-      <a href="http://www.imp.ch" shape="rect">ImproWare, AG, Switzerland</a>
-
-      , the LSI MegaRAID (AMR) and IBM/Adaptec ServeRAID (IPS) drivers
-      have been locked. SMPng locking is a key step in improving the
-      performance of system drivers in FreeBSD 5.x and beyond, and both
-      of these drivers are showing the benefits of this. FreeBSD 5.4 will
-      contains these improvements when it is released.</p>
-
-      <p>Similar work is ongoing with the 3WARE Escalade (TWE) driver,
-      and preliminary patches have been made available to testers. I hope
-      to have this driver complete in time for the next FreeBSD
-      release.</p>
-
-      <p>Unfortunately, most benefits can only be gained from pure block
-      storage drivers such as the ones mentioned here due to the SCSI
-      subsystem in FreeBSD (CAM) not be locked itself at this time. It is
-      possible, however, to lock a CAM sub-driver and bring the driver's
-      interrupt handler out from under Giant for a partial gain. The Sun
-      FAS366 SCSI driver (ESP) operates like this. Volunteers to lock
-      other drivers or to tackle locking CAM are gladly accepted, so
-      please contact me if you are interested.</p>
-    <hr /><br /><h1><a name="Network-infrastructure" href="#Network-infrastructure" id="Network-infrastructure">Network infrastructure</a></h1><br /><h2><a name="Dingo" href="#Dingo" id="Dingo">Dingo</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~gnn/Dingo/notebook/60.html" title="http://people.freebsd.org/~gnn/Dingo/notebook/60.html">Project page (out of date)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~gnn/Dingo/notebook/60.html" title="Project page (out of date)">http://people.freebsd.org/~gnn/Dingo/notebook/60.html</a></td></tr><tr><td><a href="http://zoo.unixdaemons.com/index.php?blog=7" title="http://zoo.unixdaemons.com/index.php?blog=7">Blog covering test framework</a></td><td>
-	    URL: <a href="http://zoo.unixdaemons.com/index.php?blog=7" title="Blog covering test framework">http://zoo.unixdaemons.com/index.php?blog=7</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@neville-neil.com">gnn@neville-neil.com</a>&gt;
-	</p>
-      <p>On the protocol conformance tool I have finally made some
-      progress getting a scriptable packet library using libnet, and
-      SWIG. This will hopefully become a port that can then be used to do
-      conformance testing on protocol stack changes. Qing Li has
-      separately taken up the ARP rewrite and that will be taken out of
-      the Dingo project pages.</p>
-    <h3>Open tasks:</h3><ol><li>Many :-)</li></ol><hr /><h2><a name="IPv6-Support-for-IPFW" href="#IPv6-Support-for-IPFW" id="IPv6-Support-for-IPFW">IPv6 Support for IPFW</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-all/2005-April/116671.html" title="http://lists.freebsd.org/pipermail/cvs-all/2005-April/116671.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-all/2005-April/116671.html" title="">http://lists.freebsd.org/pipermail/cvs-all/2005-April/116671.html</a></td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>In April 18th, I committed support for IPv6 to IPFW. This
-      support was written by two student of Luigi's, Mariano Tortoriello
-      and Raffaele De Lorenzo. I updated it to use PFIL_HOOKS and fixed a
-      few minor issues. As of this commit, IP6FW should be considered
-      deprecated in favor of IPFW. It should be possible to MFC this
-      change to 5.x, but that is not currently planned.</p>
-    <h3>Open tasks:</h3><ol><li>Testing.</li><li>IP6FW to IPFW migration guide.</li><li>Patches relative to 5-STABLE.</li></ol><hr /><h2><a name="Move-ARP-out-of-routing-table" href="#Move-ARP-out-of-routing-table" id="Move-ARP-out-of-routing-table">Move ARP out of routing table</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~qingli/" title="http://people.freebsd.org/~qingli/">containing the patch</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~qingli/" title="containing the patch">http://people.freebsd.org/~qingli/</a></td></tr></table><p>
-	Contact:
-          Qing
-
-          Li
-         &lt;<a href="mailto:qingli@FreeBSD.org">qingli@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have finished the basic functionality for both IPv4 and IPv6.
-      The userland utilities ("arp" and "ndp") have been updated. I have
-      tested the changes with "make buildworld". I have been testing the
-      new code in a production environment and things appear to be
-      stable. Gleb Smirnoff (glebius@FreeBSD.org) has provided review
-      comments and I have incorporated these feedback into the patch. I
-      have discussed the IPv6 changes with two of the core KAME
-      developers during the last IETF meeting in March 2005. They
-      indicated that these changes may result in divergence from the KAME
-      project but that is not necessarily a bad thing.</p>
-    <h3>Open tasks:</h3><ol><li>I am waiting for review feedback from my mentor Andre. I need
-      locking experts to help me fix my giant-lock shortcut. I am hoping
-      to send out the code for wider review soon.</li></ol><hr /><h2><a name="netgraph(4)-status-report" href="#netgraph(4)-status-report" id="netgraph(4)-status-report">netgraph(4) status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=ng_netflow&amp;manpath=FreeBSD+6.0-current" title="http://www.freebsd.org/cgi/man.cgi?query=ng_netflow&amp;manpath=FreeBSD+6.0-current">ng_netflow(4)</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=ng_netflow&amp;manpath=FreeBSD+6.0-current" title="ng_netflow(4)">http://www.freebsd.org/cgi/man.cgi?query=ng_netflow&amp;manpath=FreeBSD+6.0-current</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=ng_ipfw&amp;manpath=FreeBSD+6.0-current" title="http://www.freebsd.org/cgi/man.cgi?query=ng_ipfw&amp;manpath=FreeBSD+6.0-current">ng_ipfw(4)</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=ng_ipfw&amp;manpath=FreeBSD+6.0-current" title="ng_ipfw(4)">http://www.freebsd.org/cgi/man.cgi?query=ng_ipfw&amp;manpath=FreeBSD+6.0-current</a></td></tr><tr><td><a href="http://people.freebsd.org/~glebius/totest/ng_nat/" title="http://people.freebsd.org/~glebius/totest/ng_nat/">ng_nat work in progress</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~glebius/totest/ng_nat/" title="ng_nat work in progress">http://people.freebsd.org/~glebius/totest/ng_nat/</a></td></tr></table><p>
-	Contact:
-          Gleb
-
-          Smirnoff
-         &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>This report covers period since August 2004 until April
-      2005.</p>
-
-      <p>New nodes. Two new nodes have been added to base FreeBSD
-      distribution. ng_netflow(4) node, which implements NetFlow version
-      5 accounting of IPv4 packets. ng_ipfw(4) node, which diverts
-      packets from ipfw(4) to netgraph(4) and back. A well known
-      ng_ipacct node has been added to ports tree.</p>
-
-      <p>SMP. Nodes, which need to allocate unique names have been
-      protected with mutex in RELENG_5, and subr_unit allocator in HEAD.
-      Nodes, which need to run periodical jobs were reworked to use
-      mpsafe ng_callout() API. ng_tty(4) node has been overhauled to be
-      compatible with debug.mpsafenet=1. NetGraph ISR and callout are now
-      declared MPSAFE in HEAD.</p>
-
-      <p>NetGraph flow control. Two nodes ng_ether(4) and ng_cisco(4)
-      have been improved to emit flow control messages to upstream node,
-      when state of link changes. New link failure detection method have
-      been introduced in ng_one2many(4) node - listening to these flow
-      control messages from downstream.</p>
-    <h3>Open tasks:</h3><ol><li>more SMP testing of many nodes</li><li>review locking of graph restructuring</li><li>ng_nat node - an in-kernel natd(8)</li><li>make ng_bridge(4) multithreaded</li></ol><hr /><h2><a name="New-Wireless-Drivers" href="#New-Wireless-Drivers" id="New-Wireless-Drivers">New Wireless Drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ipw2100.sourceforge.net/firmware.php?fid=4" title="http://ipw2100.sourceforge.net/firmware.php?fid=4"></a></td><td>
-	    URL: <a href="http://ipw2100.sourceforge.net/firmware.php?fid=4" title="">http://ipw2100.sourceforge.net/firmware.php?fid=4</a></td></tr><tr><td><a href="http://ralink.rapla.net/" title="http://ralink.rapla.net/"></a></td><td>
-	    URL: <a href="http://ralink.rapla.net/" title="">http://ralink.rapla.net/</a></td></tr></table><p>
-	Contact:
-          Damien
-
-          Bergamini
-         &lt;<a href="mailto:damien@FreeBSD.org">damien@FreeBSD.org</a>&gt;
-	</p>
-      <p>Four new wireless drivers were imported:</p>
-
-      <p>
-      <em>ipw</em>
-
-      : driver for Intel PRO/Wireless 2100 adapters (MiniPCI).
-      <br clear="none" />
-
-      <em>iwi</em>
-
-      : driver for Intel PRO/Wireless 2200BG/2225BG/2915ABG adapters (PCI
-      or MiniPCI).
-      <br clear="none" />
-
-      <em>ral</em>
-
-      : driver for Ralink RT2500 wireless adapters (PCI or CardBus).
-      <br clear="none" />
-
-      <em>ural</em>
-
-      : driver for Ralink RT2500USB wireless USB 2.0 adapters.</p>
-
-      <p>The ipw and iwi drivers require firmwares to operate.
-      <br clear="none" />
-
-      These firmwares can't be redistributed with the base system due to
-      license restrictions.
-      <br clear="none" />
-
-      See firmware licensing terms here:
-      <a href="http://ipw2100.sourceforge.net/firmware.php?fid=4" shape="rect">
-      http://ipw2100.sourceforge.net/firmware.php?fid=4</a>
-
-      .
-      <br clear="none" />
-      </p>
-
-      <p>Ports which include the firmware images as well as the firmware
-      loader are being worked on.
-      <br clear="none" />
-
-      A list of adapters supported by ral and ural can be found here:
-      <a href="http://ralink.rapla.net/" shape="rect">http://ralink.rapla.net/</a>
-
-      .</p>
-    <h3>Open tasks:</h3><ol><li>Create ports for ipw and iwi firmwares.</li><li>Add IBSS support to iwi.</li><li>Add WPA (802.11i) support to ipw and iwi.</li><li>Add hardware encryption (WEP, TKIP and CCMP) support in ral
-      and ural.</li><li>Add automatic rate adaptation support to ural.</li></ol><hr /><h2><a name="Removable-interface-improvements." href="#Removable-interface-improvements." id="Removable-interface-improvements.">Removable interface improvements.</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" title="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" title="">http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/</a></td></tr><tr><td><a href="http://www.freebsd.org/projects/dingo/" title="http://www.freebsd.org/projects/dingo/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/dingo/" title="">http://www.freebsd.org/projects/dingo/</a></td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is an attempt to clean up handling of network
-      interfaces in order to allow interfaces to be removed reliably.
-      Current problems include panics if Dummynet is delaying packets to
-      an interface when it is removed.</p>
-
-      <p>I am currently working to remove struct ifnet's from device
-      driver structures to allow them to be managed properly upon device
-      removal. I believe I have removed all known instances of casting a
-      struct ifnet pointer to something else (except that that are just
-      magic values and not real struct ifnets.) I will begin committing
-      these changes to the tree shortly and will then add a new function
-      if_alloc() that will allocate struct ifnets. if_detach() will be
-      modified to destroy them.</p>
-    <hr /><h2><a name="Support-for-telephone-hardware-(aka-Zaptel)" href="#Support-for-telephone-hardware-(aka-Zaptel)" id="Support-for-telephone-hardware-(aka-Zaptel)">Support for telephone hardware (aka Zaptel)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.digium.com/index.php?menu=hardware_products" title="http://www.digium.com/index.php?menu=hardware_products"></a></td><td>
-	    URL: <a href="http://www.digium.com/index.php?menu=hardware_products" title="">http://www.digium.com/index.php?menu=hardware_products</a></td></tr></table><p>
-	Contact:
-          Maxim
-
-          Sobolev
-         &lt;<a href="mailto:sobomax@FreeBSD.org">sobomax@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Oleksandr
-
-          Tymoshenko
-         &lt;<a href="mailto:gonzo@pbxpress.com">gonzo@pbxpress.com</a>&gt;
-	<br />
-	Contact:
-          Max
-
-          Khon
-         &lt;<a href="mailto:fjoe@FreeBSD.org">fjoe@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last 2 months lot of progress has been made. Existing
-      support for TDM400 (FXO/FXS) has been significantly improved.
-      Drivers for PRI and BRI cards have been added and now should be
-      considered beta-quality.</p>
-    <h3>Open tasks:</h3><ol><li>More testing of PRI/BRI drivers.</li><li>Add support for channelized DS3 card(s).</li></ol><hr /><h2><a name="Wireless-Networking-Support" href="#Wireless-Networking-Support" id="Wireless-Networking-Support">Wireless Networking Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>Several new drivers by by Damien Bergamini were brought into the
-      tree: iwi, ipw, ral, and ural.</p>
-
-      <p>WPA-PSK support for the ndis driver was contributed by Arvind
-      Srinivasa.</p>
-
-      <p>A new tx rate control algorithm for the ath driver was
-      contributed by John Bicket. It will become the default algorithm
-      shortly.</p>
-
-      <p>Work on multi-bss support is going on outside the cvs tree. A
-      presentation on this work will be given at BSDCan 2005 and the
-      slides for the talk will be made available after.</p>
-    <h3>Open tasks:</h3><ol><li>Drivers other than ath and ndis need updates to support the
-      new security protocols.</li><li>hostapd needs work to support the IAPP and 802.11i
-      preauthentication protocols (these are simple conversions of
-      existing Linux code).</li><li>The OpenBSD dhclient program has been ported but needs a
-      developer that will maintain it once it is brought into cvs.</li></ol><hr /><br /><h1><a name="Userland-programs" href="#Userland-programs" id="Userland-programs">Userland programs</a></h1><br /><h2><a name="libthread" href="#libthread" id="libthread">libthread</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          David
-
-          Xu
-         &lt;<a href="mailto:davidxu@FreeBSD.org">davidxu@FreeBSD.org</a>&gt;
-	</p>
-      <p>libthread is a pure 1:1 threading library, it had stayed in my
-      perforce branch for a long time, recent it was imported into source
-      tree and replaced libthr. The purpose of the work is to improve 1:1
-      threading on FreeBSD, the library is designed in mind that simplest
-      is best, currently it can run almost all of the applications
-      libpthread can run, but gives you better SMP performance. The
-      library size is smaller than libpthread.</p>
-
-      <p>Currently it supports i386, AMD64, sparc64 and ia64 and may
-      support alpha, powerpc and arm. I didn't do many tests on sparc64
-      and ia64, I only tested it on FreeBSD cluster machines. For i386, I
-      always used LDT, but know that Peter committed GDT code, and now
-      there is no 8191 threads limitation anymore.</p>
-
-      <p>libthread_db was updated to support debugging the new libthr. It
-      is an assistant library used by gdb to debug threaded process, that
-      understands internal detail of thread libraries. I have improved it
-      a bit to support event reports for libthr, currently it can report
-      thread creation and death events. That means a thread that was
-      created and died will be reported to the user regardless if you are
-      tracking it or not.</p>
-    <h3>Open tasks:</h3><ol><li>I am working on thread creation performance, currently it
-      needs considerable number of libc functions and syscalls to create
-      a thread, I would like to introduce a syscall to create a thread in
-      atomically. That means one syscall will setup thread entry, tls, and
-      signal mask and PTHREAD_SCOPE_PROCESS/SYSTEM; in future maybe even
-      CPU affinity masks, when userland entry code is executed, the
-      thread is already fully setup.</li><li>Process shareable synchronization objects. In Current FreeBSD
-      does not support this specification. The idea about the shareable
-      mutex and others is like other systems did, one can use mmap() to
-      create a shared memory page, and put a pthread synchronization
-      object in the page, multiple processes use the shared object to
-      control resource access. I am not working on it, if someone is
-      interested, please let me know.</li></ol><hr /><h2><a name="Pipe-namespace-added-to-portalfs" href="#Pipe-namespace-added-to-portalfs" id="Pipe-namespace-added-to-portalfs">Pipe namespace added to portalfs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.spinellis.gr/blog/20050413/index.html" title="http://www.spinellis.gr/blog/20050413/index.html"></a></td><td>
-	    URL: <a href="http://www.spinellis.gr/blog/20050413/index.html" title="">http://www.spinellis.gr/blog/20050413/index.html</a></td></tr></table><p>
-	Contact:
-          Diomidis
-
-          Spinellis
-         &lt;<a href="mailto:dds@FreeBSD.org">dds@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new sub-namespace, called pipe, has been added to portalfs.
-      The pipe namespace executes the named command, starting back at the
-      root directory. The command's arguments can be provided after the
-      command's name, by separating them with spaces or tabs. Files
-      opened for reading in the pipe namespace will receive their input
-      from the command's standard output; files opened for writing will
-      send the data of write operations to the command's standard input.
-      The pipe namespace allows us to perform scatter gather operations
-      without using temporary files, create non-linear pipelines, and
-      implement file views using symbolic links.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="ARM-Support-for-TS-7200" href="#ARM-Support-for-TS-7200" id="ARM-Support-for-TS-7200">ARM Support for TS-7200</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.embeddedarm.com/epc/ts7200-spec-h.html" title="http://www.embeddedarm.com/epc/ts7200-spec-h.html">TS-7200 Board</a></td><td>
-	    URL: <a href="http://www.embeddedarm.com/epc/ts7200-spec-h.html" title="TS-7200 Board">http://www.embeddedarm.com/epc/ts7200-spec-h.html</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO">Perforce Code Location</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO" title="Perforce Code Location">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://people.freebsd.org/~jmg/dmesg.ts7200" title="http://people.freebsd.org/~jmg/dmesg.ts7200">FreeBSD/arm TS-7200 dmesg output</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jmg/dmesg.ts7200" title="FreeBSD/arm TS-7200 dmesg output">http://people.freebsd.org/~jmg/dmesg.ts7200</a></td></tr></table><p>
-	Contact:
-          John-Mark
-
-          Gurney
-         &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have been working on getting FreeBSD/arm running on the
-      TS-7200. So far the board boots, and has somewhat working ethernet
-      (some unexplained packet loss). I can netboot from a FreeBSD/i386
-      machine, and I can also mount msdosfs's on CF.</p>
-    <h3>Open tasks:</h3><ol><li>Figuring out why some small packets transmit with
-      error</li><li>EP93xx identification information to properly attach various
-      onboard devices</li></ol><hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><p>
-	Contact:
-          Peter
-
-          Grehan
-         &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>Progress continues. X.Org 6.8.1 server has been up and running
-      on a number of different Macs, and the work is being merged into
-      6.8.2. There have been successful installs on Mac Minis</p>
-    <hr /><h2><a name="XenFreeBSD---FreeBSD-on-Xen" href="#XenFreeBSD---FreeBSD-on-Xen" id="XenFreeBSD---FreeBSD-on-Xen">XenFreeBSD - FreeBSD on Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" title="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/">Xen project page</a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" title="Xen project page">http://www.cl.cam.ac.uk/Research/SRG/netos/xen/</a></td></tr><tr><td><a href="http://xen.bkbits.net/" title="http://xen.bkbits.net/">Xen changeset logs</a></td><td>
-	    URL: <a href="http://xen.bkbits.net/" title="Xen changeset logs">http://xen.bkbits.net/</a></td></tr></table><p>
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@fsmware.com">kmacy@fsmware.com</a>&gt;
-	</p>
-      <p>FreeBSD 5.3 runs on the stable and the development branches of
-      xen and is now checked into both trees. Over the next couple of
-      weeks I will be adding improvements for better batching of page
-      table updates and SMP support.</p>
-    <h3>Open tasks:</h3><ol><li>FreeBSD support for running as Domain 0, i.e. running as the
-      hosting operating system.</li><li>FreeBSD support for VM checkpoint and migration.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freshports.org/" title="http://www.freshports.org/">FreshPorts</a></td><td>
-	    URL: <a href="http://www.freshports.org/" title="FreshPorts">http://www.freshports.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>This is the first status report for FreshPorts. FreshPorts
-      started in early 2000 and now contains over 170,000 commits.
-      FreshPorts is primarily concerned with port commits, but actually
-      processes and records all commits to the FreeBSD source tree. Its
-      sister site,
-      <a href="http://www.freshsource.org/" shape="rect">FreshSource</a>
-
-      uses the same database as FreshPorts but has a wider reporting
-      scope. In recent months, FreshPorts has been enhanced to process
-      and include
-      <a href="http://www.vuxml.org/freebsd/" shape="rect">VuXML</a>
-
-      information. In addition, RESTRICTED and NO_CDROM have been added
-      to list of things that FreshPorts keeps track of. For unmaintained
-      ports, we recently added this message:
-      <p>
-        <em>There is no maintainer for this port.
-        <br clear="none" />
-
-        Any concerns regarding this port should be directed to the
-        FreeBSD Ports mailing list via ports@FreeBSD.org</em>
-      </p>
-
-      FreshPorts, with direct and indirect support from the FreeBSD
-      community, continues to evolve and to provide a great tool for
-      users and developers alike.</p>
-    <h3>Open tasks:</h3><ol><li>Provide a copy/paste method for updating watch lists</li><li>improvement of query times for "People watching this port,
-      also watch"</li><li>pagination of commits within a port</li><li>pagination of watch lists</li><li>create an RSS feed for individual watch lists</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD ports collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD ports collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://portsmon.firepipe.net/index.html" title="http://portsmon.firepipe.net/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.firepipe.net/index.html" title="FreeBSD ports monitoring system">http://portsmon.firepipe.net/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>As this report was being written, the 5.4 release was
-      ongoing.</p>
-
-      <p>A new charter for the Ports Management (portmgr) team was
-      approved by core and has been posted at the URL above. In addition,
-      two other new pages describe the policies of the team, and the
-      range of QA activities both during and between releases.</p>
-
-      <p>Due to being absent from email discussions for some time, Oliver
-      Eikemeier (eik) was moved to non-voting status on portmgr.</p>
-
-      <p>We have added several new and very active committers recently;
-      this is helping us to keep the PR count low even with the large
-      numbers of new ports that have been added.</p>
-
-      <p>Several more iterations of infrastructure changes have been
-      tested on the cluster and committed; see /usr/ports/CHANGES for
-      details.</p>
-
-      <p>Updates have occurred to x.org, GNOME, KDE, and perl.</p>
-
-      <p>There have been some updates to the Porter's Handbook, but more
-      sections are still in need of updates to include recent changes in
-      practices.</p>
-
-      <p>The ports collection now contains almost 12,750 ports.</p>
-    <h3>Open tasks:</h3><ol><li>Further progress has been made in cracking down on ports that
-      install files outside the approved directories and/or do not
-      deinstall cleanly (see "Extra files not listed in PLIST" on
-      <a href="http://pointyhat.freebsd.org/errorlogs/" shape="rect">pointyhat</a>
-
-      ) and this will remain a focus area. We appreciate everyone who has
-      sent in PRs or committed fixes.</li><li>Demand for new features and revisions for bsd.port.mk is
-      still very high and the portmgr team is trying to work through them
-      all.</li><li>We still have a large number of PRs that have been assigned
-      to committers for some time (in fact, they constitute the
-      majority). One goal of portmgr in the coming months is to try to
-      reduce this number, and we would like to ask our committers to help
-      us out as much as possible.</li></ol><hr /><h2><a name="Update-of-the-Linux-userland-infrastructure" href="#Update-of-the-Linux-userland-infrastructure" id="Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Emulation
-
-          Mailinglist
-         &lt;<a href="mailto:freebsd-emulation@FreeBSD.org">freebsd-emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>The update to RedHat 8 as discussed in the last status report
-      went smoothly (just some minor glitches which got resolved
-      fast).</p>
-
-      <p>As a next step a cleanup/streamlining and the possibility of
-      overriding the default Linux base is in progress. This depends on
-      changes which need at least one testrun on the ports build cluster,
-      so the final date for those changes depends upon the availability
-      of the cluster resources.</p>
-    <h3>Open tasks:</h3><ol><li>Refactoring the common RPM code into bsd.rpm.mk.</li><li>Determining which up-to-date Linux distribution to use as the
-      next default Linux base. Important criteria:
-      <ul>
-        <li>RPM based (to be able to use the existing
-        infrastructure)</li>
-
-        <li>good track record regarding availability of security
-        fixes</li>
-
-        <li>packages available from several mirror sites</li>
-
-        <li>available for several hardware architectures (e.g. i386,
-        amd64, sparc64; Note: not all architectures have a working
-        linuxolator for their native bit with, but as long as there are
-        no userland bits available, no motivation regarding writing the
-        kernel bits will arise)</li>
-      </ul>
-      </li><li>Moving the linuxolator userland to an up-to-date version (see
-      above).</li></ol><hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="OpenBSD-packet-filter---pf" href="#OpenBSD-packet-filter---pf" id="OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pf4freebsd.love2party.net/" title="http://pf4freebsd.love2party.net/">pf4FreeBSD Homepage</a></td><td>
-	    URL: <a href="http://pf4freebsd.love2party.net/" title="pf4FreeBSD Homepage">http://pf4freebsd.love2party.net/</a></td></tr><tr><td><a href="http://people.freebsd.org/~mlaier/pf37/" title="http://people.freebsd.org/~mlaier/pf37/">pf 3.7 patches</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mlaier/pf37/" title="pf 3.7 patches">http://people.freebsd.org/~mlaier/pf37/</a></td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p>
-      <p>OpenBSD is about to release
-      <a href="http://www.openbsd.org/37.html" shape="rect">version 3.7</a>
-
-      . There are
-      <a href="http://people.freebsd.org/~mlaier/pf37/" shape="rect">patches</a>
-
-      available to catch up with the development done in OpenBSD 3.6 and
-      3.7. These patches are in an early stage, but ready for testing,
-      please help.</p>
-
-      <p>Otherwise there was not much activity on pf, as it already is
-      quite stable. Other work, such as CARP and if_bridge are having
-      impact on pf in FreeBSD however, please see the respective
-      reports.</p>
-    <h3>Open tasks:</h3><ol><li>Alpha/Betatesting of the 3.7 import</li><li>Testing with if_bridge</li></ol><hr /><h2><a name="twa-driver" href="#twa-driver" id="twa-driver">twa driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twa/" title="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twa/">source code</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twa/" title="source code">http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twa/</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twa/" title="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twa/">source code</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twa/" title="source code">http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twa/</a></td></tr></table><p>
-	Contact:
-          Vinod
-
-          Kashyap
-         &lt;<a href="mailto:vkashyap at amcc.com">vkashyap at amcc.com</a>&gt;
-	</p>
-      <p>A newly re-architected twa(4) driver was committed to 6 -CURRENT
-      on 04/12/2005. Highlights of this release are:</p>
-
-      <ol>
-        <li>The driver has been re-architected to use a "Common Layer"
-        (all tw_cl* files), which is a consolidation of all
-        OS-independent parts of the driver. The FreeBSD OS specific
-        portions of the driver go into an "OS Layer" (all tw_osl* files).
-        This re-architecture is to achieve better maintainability,
-        consistency of behavior across OS's, and better portability to
-        new OS's (drivers for new OS's can be written by just adding an
-        OS Layer that's specific to the OS, by complying to a "Common
-        Layer Programming Interface (CLPI)" API. If there's interest in
-        porting the 3ware driver to any other OS, you may contact ctchu
-        at amcc.com to get a copy of the CLPI specifications.</li>
-
-        <li>The driver takes advantage of multiple processors. It does
-        not need to be Giant protected anymore.</li>
-
-        <li>The driver has a new firmware image bundled, the new features
-        of which include Online Capacity Expansion and multi-lun support,
-        among others. More details about 3ware's 9.2 release can be found
-        here:
-        <a href="http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_Notes_Web.pdf" shape="rect">
-        http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_Notes_Web.pdf</a>
-        </li>
-      </ol>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan" href="#BSDCan" id="BSDCan">BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/" title="http://www.bsdcan.org/"></a></td><td>
-	    URL: <a href="http://www.bsdcan.org/" title="">http://www.bsdcan.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>BSDCan made a strong debut in
-      <a href="http://www.bsdcan.org/2004/" shape="rect">2004</a>
-
-      . The favorable reception gave us a strong incentive for
-      <a href="http://www.bsdcan.org/2005/" shape="rect">2005</a>
-
-      . We have been rewarded with a very interesting
-      <a href="http://www.bsdcan.org/2005/schedule.php" shape="rect">program</a>
-
-      and a higher rate of registrations. Percentage-wise, we have more
-      Europeans than last year as they have decided that the trip across
-      the Atlantic is worth taking. We know they won't be disappointed.
-      See you at BSDCan 2005!</p>
-    <h3>Open tasks:</h3><ol><li>volunteers needed for the conference</li></ol><hr /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In January 2005, Warner Losh (Security Officer Emeritus) stepped
-      down from the FreeBSD Security Team in order to better devote his
-      time to other projects. In March, Colin Percival was named as a
-      second Deputy Security Officer, joining Dag-Erling Sm�rgrav in
-      that position. The current Security Team membership is published on
-      the web site.</p>
-
-      <p>So far in 2005, four security advisories have been issued
-      concerning problems in the base system of FreeBSD, three of which
-      were specific to FreeBSD. The Vulnerabilities and Exposures Markup
-      Language (VuXML) document has continued to be updated by the
-      Security Team and the Ports Committers documenting new
-      vulnerabilities in the FreeBSD Ports Collection. As of April 17,
-      127 entries have been added in 2005 bringing the FreeBSD VuXML file
-      up to a total of 422 entries.</p>
-
-      <p>In the past months both the
-      <a href="http://vuxml.FreeBSD.org/" shape="rect">VuXML web site</a>
-
-      and the
-      <a href="http://www.FreshPorts.org/" shape="rect">FreshPorts</a>
-
-      VuXML integration have been improved. The VuXML web site has had a
-      face lift and, among other things, each package now has a separate
-      web page which lists all documented vulnerabilities for the
-      particular package.
-      <a href="http://cve.mitre.org/" shape="rect">CVE</a>
-
-      information is now also included directly on the VuXML web
-      site.</p>
-
-      <p>Finally, the first few months of 2005 also saw FreeBSD 4.8 --
-      the first release to be offered "extended support" -- reach its
-      designated End of Life. The currently supported releases are
-      FreeBSD 4.10, 4.11, and 5.3.</p>
-    <hr /><h2><a name="IMUNES---a-FreeBSD-based-kernel-level-network-topology-emulator" href="#IMUNES---a-FreeBSD-based-kernel-level-network-topology-emulator" id="IMUNES---a-FreeBSD-based-kernel-level-network-topology-emulator">IMUNES - a FreeBSD based kernel-level network topology
-    emulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.imunes.net/" title="http://www.imunes.net/"></a></td><td>
-	    URL: <a href="http://www.imunes.net/" title="">http://www.imunes.net/</a></td></tr></table><p>
-	Contact:
-          Miljenko
-
-          Mikuc
-         &lt;<a href="mailto:miljenko@tel.fer.hr">miljenko@tel.fer.hr</a>&gt;
-	<br />
-	Contact:
-          Marko
-
-          Zec
-         &lt;<a href="mailto:zec@tel.fer.hr">zec@tel.fer.hr</a>&gt;
-	</p>
-      <p>IMUNES is a scalable kernel-level network topology emulator
-      based on FreeBSD. In IMUNES each virtual node operates on its
-      private instance of network stack state variables, such as routing
-      tables, interface addresses, sockets, ipfw rules etc. Most if not
-      all existing FreeBSD application binaries, including routing
-      protocol daemons such as quagga or XORP, can run unmodified within
-      the context of virtual nodes with no noticeable performance
-      penalty. Complex network topologies can be constructed by
-      connecting the virtual nodes through netgraph-based link-layer
-      paths. A GUI tool allows for simple and intuitive network topology
-      specification, deployment and management. The current version of
-      IMUNES is based on FreeBSD 4.11-RELEASE and supports IPv4.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2005-03-2005-06.html b/website/content/en/status/report-2005-03-2005-06.html
deleted file mode 100644
index 1709b33b44..0000000000
--- a/website/content/en/status/report-2005-03-2005-06.html
+++ /dev/null
@@ -1,1489 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The second quarter of 2005 has again been very exciting. The
-    BSDCan and MeetBSD conferences were both very interesting and the
-    sources of very good times. I highly recommend attending them again
-    next year.</p><p>The Google Summer of Code project has also generated quite a bit
-    of excitement. FreeBSD has been granted 19 funded mentorship spots,
-    the fourth most of all of participating organizations. Projects being
-    worked on range from UFS Journaling to porting the new BSD Installer
-    to redesigning the venerable www.FreeBSD.org website. We are quite
-    pleased to be working with so many talented students, and eagerly
-    await the results of their work. More information and status can be
-    found at the Wiki site at
-    <a href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005" shape="rect">
-    http://wiki.freebsd.org/moin.cgi/SummerOfCode2005</a>
-
-    .</p><p>The FreeBSD 6.0 release cycle is also starting up. The purpose of
-    quickly jumping from 5.x to 6.0 is to reduce the amount of transition
-    pain that most users and developers felt when switching from 4-STABLE
-    to 5.x. 6.0 will feature improved performance and stability over 5.x,
-    experimental PowerPC support, and many new WiFi/802.11 features. The
-    5.x series will continue for at least one more release this fall, and
-    will then be supported by the security team for at least 2 years
-    after that. We encourage everyone to give the 6.0-BETA snapshots a
-    try and help us make it ready for production. We hope to release
-    FreeBSD 6.0 by the end of August.</p><p>Thanks again to everyone who submitted reports, and thanks to Max
-    Laier for running the show and putting the reports together. Enjoy
-    reading!</p><hr /><h3><a href="#Google-summer-of-code">Google summer of code</a></h3><ul><li><a href="#FreeBSD-Summer-of-Code">FreeBSD Summer of Code</a></li><li><a href="#FreeBSD-website-improvements">FreeBSD website improvements</a></li><li><a href="#FreeSBIE-toolkit-integration">FreeSBIE toolkit integration</a></li><li><a href="#gjournal">gjournal</a></li><li><a href="#gvinum-'move',-'rename'">gvinum 'move', 'rename'</a></li><li><a href="#Improve-libalias">Improve libalias</a></li><li><a href="#Integrate-the-BSD-Installer-into-FreeBSD">Integrate the BSD Installer into FreeBSD</a></li><li><a href="#launchd(8)-for-FreeBSD">launchd(8) for FreeBSD</a></li><li><a href="#Network-Interface-API-Cleanup">Network Interface API Cleanup</a></li><li><a href="#Nsswitch-/-Caching-daemon">Nsswitch / Caching daemon</a></li><li><a href="#SEBSD">SEBSD</a></li><li><a href="#UFSJ----Journaling-for-UFS">UFSJ -- Journaling for UFS</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Fundraising---TCP-&amp;-IP-Routing-Optimization">Fundraising - TCP &amp; IP Routing Optimization</a></li><li><a href="#GEOM-Gate-rewrite">GEOM Gate rewrite</a></li><li><a href="#TODO-list-for-volunteers">TODO list for volunteers</a></li><li><a href="#VFS-SMP">VFS SMP</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Autotuning-of-the-page-queue-coloring-algorithm">Autotuning of the page queue coloring algorithm</a></li><li><a href="#CPU-Cache-Prefetching">CPU Cache Prefetching</a></li><li><a href="#libmemstat(3),-UMA(9)-and-malloc(9)-statistics">libmemstat(3), UMA(9) and malloc(9) statistics</a></li><li><a href="#Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></li><li><a href="#Removable-interface-improvements">Removable interface improvements</a></li><li><a href="#SMP-Network-Stack">SMP Network Stack</a></li><li><a href="#Transparent-support-for-superpages-in-the-FreeBSD-Kernel">Transparent support for superpages in the FreeBSD
-    Kernel</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li></ul><h3><a href="#Network-infrastructure">Network infrastructure</a></h3><ul><li><a href="#Dingo">Dingo</a></li><li><a href="#if_bridge">if_bridge</a></li><li><a href="#IPv6-Support-for-IPFW">IPv6 Support for IPFW</a></li><li><a href="#Move-ARP-out-of-routing-table">Move ARP out of routing table</a></li><li><a href="#TCP-Reassembly-Rewrite-and-Optimization">TCP Reassembly Rewrite and Optimization</a></li><li><a href="#TTCPv2:-Transactional-TCP-version-2">TTCPv2: Transactional TCP version 2</a></li><li><a href="#Wireless-Networking-Support">Wireless Networking Support</a></li></ul><h3><a href="#Userland-programs">Userland programs</a></h3><ul><li><a href="#OpenBSD-dhclient-import.">OpenBSD dhclient import.</a></li><li><a href="#Removing-of-old-basesystem-files-and-directories">Removing of old basesystem files and directories</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#PowerPC-Port">PowerPC Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#Porting-v9-of-Intels-C/C++-Compiler">Porting v9 of Intels C/C++ Compiler</a></li><li><a href="#Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan">BSDCan</a></li><li><a href="#EuroBSDCon-2005---Basel">EuroBSDCon 2005 - Basel</a></li><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#TrustedBSD-SEBSD">TrustedBSD SEBSD</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-summer-of-code" href="#Google-summer-of-code" id="Google-summer-of-code">Google summer of code</a></h1><br /><h2><a name="FreeBSD-Summer-of-Code" href="#FreeBSD-Summer-of-Code" id="FreeBSD-Summer-of-Code">FreeBSD Summer of Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005" title="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005" title="">http://wiki.freebsd.org/moin.cgi/SummerOfCode2005</a></td></tr></table><p>
-	Contact:
-          Summer of Code
-
-          Mentors
-         &lt;<a href="mailto:soc-mentors@FreeBSD.org">soc-mentors@FreeBSD.org</a>&gt;
-	</p>
-      <p>Google has generously funded 19 students to spend the summer
-      working on FreeBSD related projects. Each student is working with
-      one or more mentors to learn about how open source software
-      development is done with FreeBSD. This development work is
-      happening in the Perforce repository as //depot/projects/soc2005.
-      This tree will soon be exported via CVSup -- check the Wiki for
-      more information.</p>
-    <hr /><h2><a name="FreeBSD-website-improvements" href="#FreeBSD-website-improvements" id="FreeBSD-website-improvements">FreeBSD website improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Emily
-
-          Boyd
-         &lt;<a href="mailto:soc-emily@freebsd.org">soc-emily@freebsd.org</a>&gt;
-	</p>
-      <p>As part of the Google Summer of Code, I'm working on
-      improvements to the FreeBSD website (including a proposed website
-      redesign). My mentor for this project is Murray Stokely.</p>
-    <hr /><h2><a name="FreeSBIE-toolkit-integration" href="#FreeSBIE-toolkit-integration" id="FreeSBIE-toolkit-integration">FreeSBIE toolkit integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freesbie.org" title="http://www.freesbie.org">FreeSBIE main site</a></td><td>
-	    URL: <a href="http://www.freesbie.org" title="FreeSBIE main site">http://www.freesbie.org</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/DarioFreni" title="http://wiki.freebsd.org/moin.cgi/DarioFreni">My page on FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/DarioFreni" title="My page on FreeBSD wiki">http://wiki.freebsd.org/moin.cgi/DarioFreni</a></td></tr></table><p>
-	Contact:
-          Dario
-
-          Freni
-         &lt;<a href="mailto:saturnero@freesbie.org">saturnero@freesbie.org</a>&gt;
-	</p>
-      <p>My Summer of Code project is reengineering and rewrite of
-      FreeSBIE toolkit, in order to include it in the source tree. Let's
-      call it FreeSBIE 2</p>
-
-      <p>Before being accepted, I worked hard on the FreeSBIE 1 toolkit
-      to make it more flexible. It now supports amd64 and PowerPC
-      architecture. The built filesystem can now boot from almost every
-      media, from DVD to compact flash or hard disk. Also on i386 it is now
-      possible to include the BSD Installer on the livefs. We've received
-      reports that our toolkit is successfully used for the install CD of
-      <a href="http://www.pfsense.com" shape="rect">pfSense</a>
-
-      and
-      <a href="http://www.pcbsd.org" shape="rect">PC-BSD</a>
-
-      projects.</p>
-
-      <p>My future goals are to make the toolkit even more flexible,
-      capable to build embedded images (like nanoBSD) or big Live-DVD
-      systems, depending on user's choice, to support all the
-      architectures supported by FreeBSD and to write a set of tools for
-      making a netboot server with a FreeSBIE image.</p>
-    <hr /><h2><a name="gjournal" href="#gjournal" id="gjournal">gjournal</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/gjournal" title="http://wiki.freebsd.org/moin.cgi/gjournal">gjournal wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/gjournal" title="gjournal wiki">http://wiki.freebsd.org/moin.cgi/gjournal</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@gmail.com">ivoras@gmail.com</a>&gt;
-	</p>
-      <p>The schedule (as stated on the wiki page) is honoured, which
-      means that the development has started, but there's not enough code
-      for testing. Many details have been thought-out and the development
-      is ongoing.</p>
-    <hr /><h2><a name="gvinum-'move',-'rename'" href="#gvinum-'move',-'rename'" id="gvinum-'move',-'rename'">gvinum 'move', 'rename'</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename" title="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename">gvinum 'move', 'rename' wiki entry</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename" title="gvinum 'move', 'rename' wiki entry">http://wiki.freebsd.org/moin.cgi/GvinumMoveRename</a></td></tr></table><p>
-	Contact:
-          Chris
-
-          Jones
-         &lt;<a href="mailto:soc-cjones@freebsd.org">soc-cjones@freebsd.org</a>&gt;
-	</p>
-      <p>With the releases of FreeBSD 5.3 and 5.4, FreeBSD has been
-      moving away from "old-style" vinum towards GEOM-enabled gvinum for
-      logical volume management. While gvinum is a mostly
-      feature-complete replacement for vinum, it does not implement the
-      'move' or 'rename' verbs which are rather useful when reorganizing
-      one's volume layout, the alternative being a tedious process of
-      deleting and recreating subdisks, plexes, or volumes. Additionally,
-      gvinum is nearly completely undocumented, which contributes to the
-      perception of gvinum as an unfinished project.</p>
-
-      <p>I'm working on implementing 'move' (being able to move a subdisk
-      from one drive to another) and 'rename' (being able to rename an
-      subdisk, plex, volume, or drive), as well as on documentation for
-      gvinum.</p>
-
-      <p>So far, I've come up with a plan of attack with le@ and phk@,
-      and implemented the bulk of the userland code for gvinum 'move' and
-      'rename'. Still to come are the kernel-side code and
-      documentation.</p>
-    <h3>Open tasks:</h3><ol><li>'move' and 'rename' userland implementation</li><li>'move' and 'rename' kernel-side implementation</li><li>Outline new handbook section and man page</li><li>Implement new handbook section and man page</li></ol><hr /><h2><a name="Improve-libalias" href="#Improve-libalias" id="Improve-libalias">Improve libalias</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/PaoloPisati" title="http://wiki.freebsd.org/moin.cgi/PaoloPisati">Wiki page about libalias work.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/PaoloPisati" title="Wiki page about libalias work.">http://wiki.freebsd.org/moin.cgi/PaoloPisati</a></td></tr></table><p>
-	Contact:
-          Paolo
-
-          Pisati
-         &lt;<a href="mailto:soc-pisati@freebsd.org">soc-pisati@freebsd.org</a>&gt;
-	</p>
-      <p>My SoC project is about improving libalias and integrating it
-      with ipfw2, adding nat support into the firewall. Till now I ported
-      libalias (as a kld) and ng_nat to 4.x and 5.x branches, and I've
-      already a first working patchset that adds 'nat' action into ipfw.
-      Next step will be to add a complete syntax to ipfw that will let us
-      manipulate libalias operations, much like we already do with queue
-      and pipes for dummynet. In the end the entire work will compile and
-      work out of the box for 4.x, 5.x and 6.x. More details about the
-      project and its status are available on wiki page.</p>
-    <hr /><h2><a name="Integrate-the-BSD-Installer-into-FreeBSD" href="#Integrate-the-BSD-Installer-into-FreeBSD" id="Integrate-the-BSD-Installer-into-FreeBSD">Integrate the BSD Installer into FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdinstaller.org" title="http://www.bsdinstaller.org">The BSD Installer</a></td><td>
-	    URL: <a href="http://www.bsdinstaller.org" title="The BSD Installer">http://www.bsdinstaller.org</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="http://wiki.freebsd.org/moin.cgi/BSDInstaller">BSD Installer Wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="BSD Installer Wiki page">http://wiki.freebsd.org/moin.cgi/BSDInstaller</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2005/bsdinstaller" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2005/bsdinstaller">BSD Installer Perforce tree</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2005/bsdinstaller" title="BSD Installer Perforce tree">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2005/bsdinstaller</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Turner
-         &lt;<a href="mailto:soc-andrew@FreeBSD.org">soc-andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Progress towards integrating the BSD Installer for Google's
-      Summer of Code is coming along nicely. The installation CD will
-      boot to multi-user mode and run both the front and back ends. It
-      can then partition a hard drive, install the base distribution and
-      make the disk bootable.</p>
-    <h3>Open tasks:</h3><ol><li>Test in non-i386</li><li>Investigate installing from other media</li><li>Many more tasks</li></ol><hr /><h2><a name="launchd(8)-for-FreeBSD" href="#launchd(8)-for-FreeBSD" id="launchd(8)-for-FreeBSD">launchd(8) for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/launchd" title="http://wiki.freebsd.org/moin.cgi/launchd">Wiki Project Page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/launchd" title="Wiki Project Page">http://wiki.freebsd.org/moin.cgi/launchd</a></td></tr><tr><td><a href="http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/launchd.8.html" title="http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/launchd.8.html">Apple's launchd(8) man page</a></td><td>
-	    URL: <a href="http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/launchd.8.html" title="Apple's launchd(8) man page">http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/launchd.8.html</a></td></tr></table><p>
-	Contact:
-          R. Tyler
-
-          Ballance
-         &lt;<a href="mailto:tyler@tamu.edu">tyler@tamu.edu</a>&gt;
-	</p>
-      <p>So far progress has been slow, the autoconf build system has
-      been removed from all of the launchd(8) code, and launchctl(1) is
-      building and semi-functional on FreeBSD-CURRENT (i.e.
-      CoreFoundation hooks have been removed).</p>
-
-      <p>I'm currently working on porting "liblaunch" which is the core
-      backend to both launchd(8) (the actual daemon) and launchctl(1),
-      there are some mach/xnu specific hooks and calls that need to be
-      remove and either reimplemented or worked around.</p>
-
-      <p>We're also waiting on a response from Apple on a possible
-      BSD-licensed version of the code (it's currently under the APSL)
-      Progress is slow, but steady.</p>
-    <hr /><h2><a name="Network-Interface-API-Cleanup" href="#Network-Interface-API-Cleanup" id="Network-Interface-API-Cleanup">Network Interface API Cleanup</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkIterfaceApis" title="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkIterfaceApis"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkIterfaceApis" title="">http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkIterfaceApis</a></td></tr></table><p>
-	Contact:
-          Anders
-
-          Persson
-         &lt;<a href="mailto:soc-anders@freebsd.org">soc-anders@freebsd.org</a>&gt;
-	</p>
-      <p>The goal of this project is to review the network interface API
-      and try to remove references to kernel-only data structures by
-      removing the use of libkvm and instead rely on other interfaces to
-      provide information. If there are no adequate interfaces, they
-      would be created.</p>
-
-      <p>Currently netstat is being reviewed and parts of it have been
-      modified to use sysctl rather than libkvm to provide the
-      information.</p>
-
-      <p>A big thank you to Brooks Davis for mentoring :-)</p>
-    <hr /><h2><a name="Nsswitch-/-Caching-daemon" href="#Nsswitch-/-Caching-daemon" id="Nsswitch-/-Caching-daemon">Nsswitch / Caching daemon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingTechnicalDetails" title="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingTechnicalDetails"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingTechnicalDetails" title="">http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingTechnicalDetails</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/MichaelBushkov" title="http://wiki.freebsd.org/moin.cgi/MichaelBushkov"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/MichaelBushkov" title="">http://wiki.freebsd.org/moin.cgi/MichaelBushkov</a></td></tr></table><p>
-	Contact:
-          Michael
-
-          Bushkov
-         &lt;<a href="mailto:soc-bushman@rsu.ru">soc-bushman@rsu.ru</a>&gt;
-	</p>
-      <p>The
-      <strong>nsswitch / caching daemon</strong>
-
-      project is being developed within the Google's Summer Of Code
-      program. The first goal of this project is to implement a set of
-      patches to extend the use of nsswitch subsystem. The second goal is
-      the development of the caching library and daemon to add the
-      caching ability to the nsswitch.</p>
-
-      <p>Currently services, protocols, rpc and openssh patches are
-      finished. Support for services, services_compat, rpc, protocols,
-      and ssh_host_keys databases is added with 'files', 'nis' and
-      'compat' (for services) sources possible. The nsswitch-friendly
-      openssh port is almost completed.</p>
-    <h3>Open tasks:</h3><ol><li>Implement set of patches to make nsswitch support
-      <strong>globus grid security files</strong>
-
-      ,
-      <strong>MAC and audit related configuration files</strong>
-
-      databases.</li><li>Implement the caching library and the caching daemon and
-      patch nsdispatch function to support caching.</li></ol><hr /><h2><a name="SEBSD" href="#SEBSD" id="SEBSD">SEBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/YanjunWu" title="http://wiki.freebsd.org/moin.cgi/YanjunWu">Show status in wiki, update more frequently.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/YanjunWu" title="Show status in wiki, update more frequently.">http://wiki.freebsd.org/moin.cgi/YanjunWu</a></td></tr></table><p>
-	Contact:
-          Yanjun
-
-          Wu
-         &lt;<a href="mailto:yanjun03@ios.cn">yanjun03@ios.cn</a>&gt;
-	</p>
-      <ol>
-        <li>Setup a local P4 workspace of SEBSD source and Setup lxr for
-        TrustedBSD source for studying source code.</li>
-
-        <li>Test a simple policy configuration for vsftpd.</li>
-
-        <li>Writing a HOWTO document
-        <em>Getting Started with SEBSD HOWTO</em>
-
-        by deriving the existing
-        <em>Getting Started with SELinux HOWTO</em>.</li>
-      </ol>
-
-      <p>Thanks Robert Watson and Scott Long for their kind help.</p>
-    <h3>Open tasks:</h3><ol><li>When writing the document, try to figure out the sebsd
-      userland utils that need to be ported.</li><li>Test and edit more policies for BSD environment.</li></ol><hr /><h2><a name="UFSJ----Journaling-for-UFS" href="#UFSJ----Journaling-for-UFS" id="UFSJ----Journaling-for-UFS">UFSJ -- Journaling for UFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brian
-
-          Wilson
-         &lt;<a href="mailto:polytopes@gmail.com">polytopes@gmail.com</a>&gt;
-	<br />
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>filesystem. Journaling helps ensure the filesystem's integrity
-      should the system crash. Journaling eliminates the need for
-      fsck'ing a filesystem, as the filesystem is never in an
-      inconsistent state (barring hardware failure). This implementation
-      is inspired by Darwin's HFS+ filesystem and the SGI XFS filesystem.
-      This is a Summer of Code project, with Scott Long as the mentor and
-      Brian Wilson as the developer/mentee. Currently this project is
-      still in the early stages, but will be in a usable state by
-      September 1 (the Google Summer of Code completion date).</p>
-    <h3>Open tasks:</h3><ol><li>Finish making the file system log metadata updates.</li><li>Add facilities to replay the log on dirty file
-      systems.</li><li>Make snapshots work with journaling.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Fundraising---TCP-&amp;-IP-Routing-Optimization" href="#Fundraising---TCP-&amp;-IP-Routing-Optimization" id="Fundraising---TCP-&amp;-IP-Routing-Optimization">Fundraising - TCP &amp; IP Routing Optimization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="http://people.freebsd.org/~andre/tcpoptimization.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="">http://people.freebsd.org/~andre/tcpoptimization.html</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>The TCP code in FreeBSD has evolved significantly since the fork
-      from 4.4BSD-Lite2 in 1994 primarily due to new features and
-      refinements of the TCP specifications.</p>
-
-      <p>The TCP code now needs a general overhaul, streamlining and
-      cleanup to make it easily comprehensible, maintainable and
-      extensible again. In addition there are many little optimizations
-      that can be done during such an operation, propelling FreeBSD back
-      at the top of the best performing TCP/IP stacks again, a position
-      it has held for the longest time in the 90's.</p>
-
-      <p>This overhaul is a very involved and delicate matter and needs
-      extensive formal and actual testing to ensure no regressions
-      compared to the current code. The effort needed for this work is
-      about three man-month of fully focused and dedicated time. To get
-      it done I need funding to take time off my day job and to dedicate
-      me to FreeBSD work much the way PHK did with his buffer cache and
-      vnode rework projects.</p>
-
-      <p>I've got the opportunity to work up to three man-month
-      exclusively full-time on FreeBSD during the second half of 2005.
-      That means up to 720 hours of full-steam coding (at 60 hours/week)!
-      I will work as much time as the fundraise provides.</p>
-
-      <p>I need to raise enough money for each month from donations from
-      the FreeBSD community to cover my fixed cost of living, office and
-      associated overhead. These fixed cost amount to US$6,300/month
-      (EUR5,200 or CHF8,000). Yes, Switzerland is not the cheapest place
-      to live. :)</p>
-
-      <p>A detailed description of the tasks involved and the code I will
-      write is on my FreeBSD website; Follow the link above.</p>
-    <h3>Open tasks:</h3><ol><li>Raise enough money to get all the almost finished TCP and IP
-      code into the tree.</li></ol><hr /><h2><a name="GEOM-Gate-rewrite" href="#GEOM-Gate-rewrite" id="GEOM-Gate-rewrite">GEOM Gate rewrite</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://cvsweb.freebsd.org/src/sys/geom/gate/" title="http://cvsweb.freebsd.org/src/sys/geom/gate/"></a></td><td>
-	    URL: <a href="http://cvsweb.freebsd.org/src/sys/geom/gate/" title="">http://cvsweb.freebsd.org/src/sys/geom/gate/</a></td></tr><tr><td><a href="http://cvsweb.freebsd.org/src/sbin/ggate/" title="http://cvsweb.freebsd.org/src/sbin/ggate/"></a></td><td>
-	    URL: <a href="http://cvsweb.freebsd.org/src/sbin/ggate/" title="">http://cvsweb.freebsd.org/src/sbin/ggate/</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>GGATE is a mechanism for exporting storage devices over the
-      network. It was reimplemented to be much faster and to handle
-      network failures better. The ggatec uses two threads now: sendtd,
-      which takes I/O request from the kernel and sends it to ggated;
-      recvtd, which receives finished requests and forwards them to the
-      kernel. The ggated uses three threads: recvtd, which receives I/O
-      requests from ggatec; disktd, which executes I/O requests (reads or
-      writes data); sendtd, which sends finished requests to ggatec. The
-      new ggate has been committed to 6.x.</p>
-
-      <p>The work was sponsored by
-      <a href="http://www.wheel.pl" shape="rect">Wheel Sp. z o.o.</a>
-      </p>
-    <hr /><h2><a name="TODO-list-for-volunteers" href="#TODO-list-for-volunteers" id="TODO-list-for-volunteers">TODO list for volunteers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since Google's "Summer of Code" resulted in a lot of interest in
-      open projects, I'm in the process of compiling a list of nice
-      projects for volunteers. Unlike Google's SoC those projects aren't
-      backed with money (but this doesn't means nobody is allowed to
-      sponsor one of those projects), so we can only guarantee the social
-      aspects (some "Thank you!" and "That's great!" messages). So far
-      the list has several entries where the difficulty ranges from
-      "someone just has to sit down and spend some time on it" up to "we
-      need a guru for this".</p>
-    <h3>Open tasks:</h3><ol><li>Merging untaken entries from the SoC list as soon as the
-      official participants/tasks in the SoC are announced.</li><li>Sending the document to some doc people for review.</li><li>Commit the list.</li></ol><hr /><h2><a name="VFS-SMP" href="#VFS-SMP" id="VFS-SMP">VFS SMP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Jeff
-
-          Roberson
-         &lt;<a href="mailto:jeff@freebsd.org">jeff@freebsd.org</a>&gt;
-	</p>
-      <p>FreeBSD's VFS layer has been fine grain locked along with the
-      FFS filesystem for the FreeBSD 6.0 release. The locking has been
-      underway for several years, with the project really picking up over
-      the last 6 months thanks largely to sponsorship provided by Isilon
-      Systems, Inc. a leading vendor of clustered storage systems. The
-      project has entered a stabilization phase, with a few bugs being
-      reported in extreme circumstances while the majority of users have
-      seen no problems. Tests on a 8 and 16 way machines yield reasonable
-      parallelization, however, it will be beneficial to do lock
-      contention analysis once things are fully stable.</p>
-
-      <p>For those interested in technical details, there have been a few
-      relatively significant changes with vnode life-cycle management.
-      Vnode reference counting and recycling is now no longer an ad-hoc
-      process involving a variety of flags, a use count and the hold
-      count. A single hold count is used to track all vnode references
-      and a destroyed vnode is freed in the context of the caller when
-      the last ref is lost. The old system would never reclaim memory
-      used by vnodes and also had pathlogical behavior with unreferenced
-      vnode caching under pressure. The new system is much simpler than
-      the old one, however, callers are now required to vhold a vnode
-      that they lock directly without going through vget to prevent it
-      from being recycled while they are waiting on a lock. Relying on
-      'location stable storage', which is a more strict version of 'type
-      stable storage' is no longer a valid approach.</p>
-
-      <p>Some other side effects include a much simpler and faster nullfs
-      implementation, an improved buf daemon flushing algorithm which
-      eliminated high latency that caused audio skipping, and a lots of
-      minor cleanups and debugging aids.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/doc/nl/books/handbook" title="http://www.freebsd.org/doc/nl/books/handbook">The Dutch Handbook</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/nl/books/handbook" title="The Dutch Handbook">http://www.freebsd.org/doc/nl/books/handbook</a></td></tr><tr><td><a href="http://www.evilcoder.org/content/section/6/39/" title="http://www.evilcoder.org/content/section/6/39/">The Dutch Project Site</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/content/section/6/39/" title="The Dutch Project Site">http://www.evilcoder.org/content/section/6/39/</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd_html/" title="http://www.evilcoder.org/freebsd_html/">The Dutch Preview Documentation</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd_html/" title="The Dutch Preview Documentation">http://www.evilcoder.org/freebsd_html/</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd/flyer.pdf" title="http://www.evilcoder.org/freebsd/flyer.pdf">The Dutch FreeBSD Flyer</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd/flyer.pdf" title="The Dutch FreeBSD Flyer">http://www.evilcoder.org/freebsd/flyer.pdf</a></td></tr></table><p>
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Siebrand
-
-          Mazeland
-         &lt;<a href="mailto:siebrand.mazeland@xs4all.nl">siebrand.mazeland@xs4all.nl</a>&gt;
-	<br />
-	Contact:
-          Rene
-
-          Ladan
-         &lt;<a href="mailto:r.c.ladan@student.tue.nl">r.c.ladan@student.tue.nl</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation Project is a ongoing project in
-      translating the english documentation to the Dutch language.
-      Currently we are almost done with the FreeBSD Handbook. Finishing
-      the Handbook is our first priority, and we could use your help.
-      Please contact Siebrand or myself if you want to helpout. After the
-      handbook we will focus on other documents as well, so feel free to
-      help us there as well</p>
-    <h3>Open tasks:</h3><ol><li>FreeBSD Handbook translation. Finish the translation from
-      English to Dutch</li><li>FreeBSD Handbook review. Finish the review of the translated
-      documents</li><li>FreeBSD Articles. Start translating the articles from English
-      to the Dutch Language</li><li>FreeBSD www. Start translating the website from English to
-      the Dutch Language</li><li>The rest of the FreeBSD Documents. Start translating them
-      from English to the Dutch Language.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Autotuning-of-the-page-queue-coloring-algorithm" href="#Autotuning-of-the-page-queue-coloring-algorithm" id="Autotuning-of-the-page-queue-coloring-algorithm">Autotuning of the page queue coloring algorithm</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.Leidinger.net/FreeBSD/current-patches/pq.diff" title="http://www.Leidinger.net/FreeBSD/current-patches/pq.diff">Patch</a></td><td>
-	    URL: <a href="http://www.Leidinger.net/FreeBSD/current-patches/pq.diff" title="Patch">http://www.Leidinger.net/FreeBSD/current-patches/pq.diff</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The VM subsystem has code to reduce the amount of cache
-      collisions of VM pages. Currently this code needs to be tuned with
-      a kernel option. I have a patch which changes this to auto-tuning
-      at boot time. The auto-tuning is MI, the cache size detection is
-      MD. Cache size detection is currently available for x86/amd64 (on
-      other systems it uses default values).</p>
-    <h3>Open tasks:</h3><ol><li>Add cache-detection code for other arches too (Marius told me
-      how to do this for sparc64).</li><li>Analyze why the cache detection on Athlons doesn't work (no
-      problems on a P4, but it uses a different code-path).</li></ol><hr /><h2><a name="CPU-Cache-Prefetching" href="#CPU-Cache-Prefetching" id="CPU-Cache-Prefetching">CPU Cache Prefetching</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="http://people.freebsd.org/~andre/tcpoptimization.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="">http://people.freebsd.org/~andre/tcpoptimization.html</a></td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" title="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch"></a></td><td>
-	    URL: <a href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" title="">http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>Modern CPU's can only perform to their maximum if their working
-      code is in fast L1-3 cache memory instead of the bulk main memory.
-      All of today's CPU's support certain L1-3 cache prefetching
-      instructions which cause data to be retrieved from main memory to
-      the cache ahead of the time that it is already in place when it is
-      eventually accessed by the CPU.</p>
-
-      <p>CPU Cache Prefetching however is not a silver bullet and has to
-      be used with extreme care and only in very specific places to be
-      beneficial. Incorrect usage can lead to massive cache pollution and
-      a drop in effective performance. Correct and very carefully usage
-      on the other can lead to drastic performance increases in common
-      operations.</p>
-
-      <p>In the linked patch CPU cache prefetching has been used to
-      prefetch the packet header (OSI layer 2 to 4) into the CPU caches
-      right after entering into the network stack. This avoids a complete
-      CPU stall on the first access to the packet header because packets
-      get DMA'd into main memory and thus never are already pre-cache in
-      the CPU caches. A second use in the patch is in the TCP input code
-      to prefetch the entire struct tcpcb which is very large and used
-      with a very high probability. Use in both of these places show a
-      very significant performance gain but not yet fully quantified.</p>
-
-      <p>The final patch will include documentation and a guide to
-      evaluate and assess the use of CPU cache prefetch instructions in
-      the kernel.</p>
-    <h3>Open tasks:</h3><ol><li>Need funding, see "Fundraising - TCP &amp; IP Routing
-      Optimization".</li></ol><hr /><h2><a name="libmemstat(3),-UMA(9)-and-malloc(9)-statistics" href="#libmemstat(3),-UMA(9)-and-malloc(9)-statistics" id="libmemstat(3),-UMA(9)-and-malloc(9)-statistics">libmemstat(3), UMA(9) and malloc(9) statistics</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.watson.org/~robert/freebsd/libmemstat/" title="http://www.watson.org/~robert/freebsd/libmemstat/">libmemstat(3)-derived tools</a></td><td>
-	    URL: <a href="http://www.watson.org/~robert/freebsd/libmemstat/" title="libmemstat(3)-derived tools">http://www.watson.org/~robert/freebsd/libmemstat/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>libmemstat(3) provides a user space library API to monitor
-      kernel memory allocators, currently uma(9) and malloc(9), with the
-      following benefits:</p>
-
-      <ul>
-        <li>ABI-robust interface making use of accessor functions, in
-        order to divorce monitoring applications from kernel/user ABI
-        changes.</li>
-
-        <li>Allocator-independent interfaces, allowing monitoring of
-        multiple allocators using the same interface.</li>
-
-        <li>CPU-cache awareness, allowing tracking of memory use across
-        multiple CPUs for allocators aware of caches. Unlike previous
-        interfaces, libmemstat(3) coalesces per-CPU stats in user space
-        rather than kernel, and exposes per-CPU stats to interested
-        applications.</li>
-
-        <li>Ability to track memory types over multiple queries, and
-        update existing structures, allowing easy tracking of statistics
-        over time.</li>
-      </ul>
-
-      <p>libmemstat(3) and the appropriate allocator changes for
-      uma(9) and malloc(9) are currently in HEAD (7-CURRENT), and MFC has
-      been approved to RELENG_6 for inclusion in 6.0-RELEASE. These
-      changes may also be backported to 5.x.</p>
-
-      <p>Sample applications include memstat(8), an allocator-independent
-      statistics viewing tool, memtop(8), which provides a top(1)-like
-      interface for monitoring kernel memory use and active memory types.
-      None of these are "pretty".</p>
-
-      <p>netstat -mb has also been updated to use libmemstat(3) to track
-      network memory use using uma(9), rather than the less reliable mbuf
-      allocator statistics interface. As a result, the statistics are now
-      more reliable on SMP systems (this corrects the bug in which mbuf
-      statistics sometimes "leaked", even though memory didn't), and more
-      informative (cache information is now displayed, as well as mbuf
-      tag information).</p>
-    <h3>Open tasks:</h3><ol><li>Teach libmemstat(3) to speak libkvm(3) in order to allow
-      tools linked -lmemstat to interogate kernel core dumps.</li><li>Teach libmemstat(3) to interface with user space malloc and
-      track malloc allocations for user space applications.</li><li>Update vmstat(8) -m and -z implementations to use
-      libmemstat(3) instead of the old monitoring interfaces. Code to do
-      this exists in the sample libmemstat(3) applications.</li><li>Identify how to make streams or the library endian-aware so
-      that streams dumped from a kernel of alternative endian could be
-      processed using libmemstat(3) on another system.</li><li>Identify any remaining caching allocators in the kernel, such
-      as the sfbuf allocator, and teach libmemstat(3) how to interface
-      with them.</li></ol><hr /><h2><a name="Low-overhead-performance-monitoring-for-FreeBSD" href="#Low-overhead-performance-monitoring-for-FreeBSD" id="Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement">Project home page</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="Project home page">http://people.freebsd.org/~jkoshy/projects/perf-measurement</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Modern CPUs have on-chip performance monitoring counters (PMCs)
-      that may be used to count low-level hardware events like
-      instruction retirals, branch mispredictions, and cache misses. PMC
-      architectures and capabilities vary between CPU vendors and between
-      CPU generations from the same vendor, making the creation of
-      portable applications difficult. This project implements a
-      cross-platform PMC management API for applications, and implements
-      the infrastructure to "virtualize" and manage these PMCs. The
-      creation of performance analysis tools that use this infrastructure
-      is also part of the project's goals.</p>
-
-      <p>Work since the last status report:</p>
-
-      <ul>
-        <li>Sampling mode support for P4 and AMD64 PMCs has been
-        implemented.</li>
-
-        <li>A pmclog(3) API for parsing hwpmc(4) log files has been
-        added.</li>
-
-        <li>A number of bugs in libpmc(3), hwpmc(4) and pmcstat(8) have
-        been fixed.</li>
-      </ul>
-
-      <p>Future work:</p>
-
-      <ul>
-        <li>Creating user documentation showing a few real-world uses of
-        the currently available tools.</li>
-
-        <li>Testing, improving the stability of the code, and
-        characterizing its overheads.</li>
-
-        <li>Implementing P5 PMC support.</li>
-      </ul>
-    <hr /><h2><a name="Removable-interface-improvements" href="#Removable-interface-improvements" id="Removable-interface-improvements">Removable interface improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" title="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" title="">http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/</a></td></tr><tr><td><a href="http://www.freebsd.org/projects/dingo/" title="http://www.freebsd.org/projects/dingo/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/dingo/" title="">http://www.freebsd.org/projects/dingo/</a></td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is an attempt to clean up handling of network
-      interfaces in order to allow interfaces to be removed reliably.
-      Current problems include panics if Dummynet is delaying packets to
-      an interface when it is removed.</p>
-
-      <p>I have removed struct ifnet's and layer two common structures
-      from device driver structures. This will eventually allow them to
-      be managed properly upon device removal. This code has been
-      committed and will appear in 6.0. Popular drivers have generally
-      been fixed, but more testing is needed.</p>
-    <hr /><h2><a name="SMP-Network-Stack" href="#SMP-Network-Stack" id="SMP-Network-Stack">SMP Network Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/netperf/" title="http://www.FreeBSD.org/projects/netperf/">Netperf home page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/netperf/" title="Netperf home page">http://www.FreeBSD.org/projects/netperf/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Significant work has occurred over the last few months relating
-      to the SMP network stack work. A few of the highlights are covered
-      here at a high level:</p>
-
-      <ul>
-        <li>The UMA(9) per-CPU caches have been modified to use critical
-        sections instead of mutexes. Recent critical section
-        optimizations make this a performance win for both UP and SMP
-        systems. This results in a several percent improvement in a
-        number of user space benchmarks, and larger improvement for
-        kernel-only network forwarding and processing benchmarks.</li>
-
-        <li>The malloc(9) allocator has been modified to store statistics
-        per-CPU instead of using a cross-CPU statistics pool, with each
-        per-CPU pool now using critical sections to synchronize access.
-        This results in a measurable performance win, especially on SMP
-        systems</li>
-
-        <li>The netnatm ATM code is now MPSAFE.</li>
-
-        <li>netipx MPSAFEty has been merged to RELENG_5.</li>
-
-        <li>The netperf cluster has now been expanded to include two
-        additional quad-CPU systems (one dual dual-core AMD system, one
-        quad-CPU PIII system).</li>
-
-        <li>libmemsetat(3) (see separate report) now corrects SMP-related
-        races in the measuring of mbuf allocator statistics, as well as
-        substantially improving kernel memory monitoring capabilities and
-        tools.</li>
-
-        <li>A range of locking bug fixes, and general network stack bug
-        fixes.</li>
-
-        <li>Significant updates to the SMPng web page (still more to
-        do!).</li>
-
-        <li>Identification of all non-MPSAFE network device drivers, with
-        ultimatum issued, on freebsd-arch. Quite a bit of new driver
-        locking work as a result (if_ed, if_de, ...).</li>
-
-        <li>Lots of other stuff.</li>
-      </ul>
-
-      <p>In most cases, these changes will appear in FreeBSD 6.0-RELEASE;
-      some have been, or will be, merged to FreeBSD 5.x.</p>
-
-      <p>On-going tasks include:</p>
-
-      <ul>
-        <li>Review and improvement of ifnet locking, such as address
-        lists and flags.</li>
-
-        <li>Optimization of interface start hand-off.</li>
-
-        <li>Prototyping of queue-oriented packet hand-off in the
-        stack.</li>
-
-        <li>Performance measurement and analysis.</li>
-
-        <li>Prototype rewrite and simplification of socket locking.</li>
-      </ul>
-    <hr /><h2><a name="Transparent-support-for-superpages-in-the-FreeBSD-Kernel" href="#Transparent-support-for-superpages-in-the-FreeBSD-Kernel" id="Transparent-support-for-superpages-in-the-FreeBSD-Kernel">Transparent support for superpages in the FreeBSD
-    Kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Alan L.
-
-          Cox
-         &lt;<a href="mailto:alc@cs.rice.edu">alc@cs.rice.edu</a>&gt;
-	<br />
-	Contact:
-          Olivier
-
-          Crameri
-         &lt;<a href="mailto:olivier.crameri@epfl.ch">olivier.crameri@epfl.ch</a>&gt;
-	</p>
-      <p>We are currently working on an updated implementation of
-      <a href="http://www.cs.rice.edu/~jnavarro/papers/osdi02.ps" shape="rect">Juan
-      Navarro's transparent support for superpages in FreeBSD.</a>
-      </p>
-
-      <p>The idea is to take advantage of the architectural support for
-      big memory pages (superpages) by using a reservation mechanism
-      allowing us to transparently promote groups of base pages into
-      superpages and demote superpages into several smaller superpages or
-      base pages.</p>
-
-      <p>The advantage of using superpages vs. base pages is to
-      significantly improve the TLB coverage of the physical memory, thus
-      improving the peformance by reducing the number of TLB misses.</p>
-
-      <p>The modification of the FreeBSD kernel that we are working on
-      involves the replacement of the current list based page allocation
-      mechanism with a system using a buddy allocator to reserve groups
-      of pages for a memory object. The promotion and demotion of the
-      pages occur directly within the pmap module.</p>
-
-      <p>The former implementation was supporting the alpha and IA64
-      architectures. We are adding the support for amd64. We currently
-      have an almost complete implementation. Once completed we will make
-      a performance study with a particular emphasis on TLB and cache
-      misses.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.trustedbsd.org/components.html#audit" title="http://www.trustedbsd.org/components.html#audit"></a></td><td>
-	    URL: <a href="http://www.trustedbsd.org/components.html#audit" title="">http://www.trustedbsd.org/components.html#audit</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Wayne
-
-          Salamon
-         &lt;<a href="mailto:wsalmon@FreeBSD.org">wsalmon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>In the past few months, significant work has been done relating
-      to the TrustedBSD audit implementation, including preparatory work
-      to merge audit into the FreeBSD CVS repository for FreeBSD 6.x. In
-      particular:</p>
-
-      <ul>
-        <li>The user space components, such as libbsm, include files, and
-        command line utilities have been broken out into an OpenBSM
-        distribution in Perforce. Improvements in OpenBSM will be made
-        available separately for use by projects such as Darwin, and
-        imported into the contrib area of FreeBSD.</li>
-
-        <li>The system call table format has been updated to include an
-        audit event identifier for each system call across all hardware
-        platforms and ABIs (merged), and all system calls have been
-        assigned event identifiers (not yet merged).</li>
-
-        <li>The audit management daemon has been rewritten to run on
-        FreeBSD (originally derived from Darwin) using /dev/audit to
-        track kernel events.</li>
-
-        <li>Many system calls now properly audit their arguments.</li>
-
-        <li>The TrustedBSD audit3 branch has been updated to a recent
-        6.x-CURRENT.</li>
-
-        <li>Significant work has gone into synchronizing the audit event
-        tables between FreeBSD, Darwin, and OpenSolaris to make sure file
-        formats and events are portable.</li>
-
-        <li>OpenBSM has been adapted to consume and generate
-        endian-independent event streams.</li>
-
-        <li>OpenBSM documentation has been created.</li>
-      </ul>
-
-      <p>The hope is still to provide audit as "experimental" in 6.0; the
-      primary blocking factor is our awaiting relicensing of the last
-      remaining audit files from Apple's APSL license to BSDL so that
-      they can be included in the FreeBSD kernel. This is anticipated to
-      complete in the near future. Once this is done, the changes can be
-      merged to CVS, and then MFC'd to RELENG_6. If this is not complete
-      by 6.0-RELEASE, the work will be merged shortly after the release,
-      as all ABI-sensitive data structures have been updated as
-      needed.</p>
-    <hr /><br /><h1><a name="Network-infrastructure" href="#Network-infrastructure" id="Network-infrastructure">Network infrastructure</a></h1><br /><h2><a name="Dingo" href="#Dingo" id="Dingo">Dingo</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/projects/dingo/" title="http://www.freebsd.org/projects/dingo/">somewhat out of date</a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/dingo/" title="somewhat out of date">http://www.freebsd.org/projects/dingo/</a></td></tr></table><p>
-	Contact:
-          Several
-         &lt;<a href="mailto:"></a>&gt;
-	</p>
-      <p>Currently trying to restart bits of the project. Cleaning up the
-      p4 branch. Recently more people have volunteered to help as well.
-      Brooks Davis has completed removing the ifnet from the softc.</p>
-    <h3>Open tasks:</h3><ol><li>See the web page.</li></ol><hr /><h2><a name="if_bridge" href="#if_bridge" id="if_bridge">if_bridge</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@freebsd.org">thompsa@freebsd.org</a>&gt;
-	</p>
-      <p>This was committed to current on 5 Jun 2005 and will first
-      appear in the 6.0 release, thanks to everyone who tested. Recent
-      improvements include:</p>
-
-      <ul>
-        <li>IPFW layer2 filtering</li>
-
-        <li>DUMMYNET support</li>
-
-        <li>IP header alignment checking</li>
-      </ul>
-
-      <p>There is ongoing work to bring in some of the advanced features
-      from OpenBSD such as IPSec bridging. People are encouraged to use
-      if_bridge and report any problems to the mailing lists.</p>
-    <hr /><h2><a name="IPv6-Support-for-IPFW" href="#IPv6-Support-for-IPFW" id="IPv6-Support-for-IPFW">IPv6 Support for IPFW</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@freebsd.org">mlaier@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@freebsd.org">brooks@freebsd.org</a>&gt;
-	</p>
-      <p>At the developer summit before BSDCan it was decided to remove
-      IP6FW from the tree as it has a couple of problems. The most
-      pressing one is the lack of synchronization and thus the need for
-      debug.mpsafenet=0. As a replacement Brooks Davis has imported
-      patches to teach the existing and well-locked IPFW2 code about
-      IPv6.</p>
-
-      <p>Since the initial import I have added some features required to
-      manage IPv4 and IPv6 in a single ruleset. I have also extended
-      existing opcodes to work with IPv6. There are, however, still some
-      opcodes that do not work with IPv6 and most of the more exotic ones
-      haven't been tested. As long as IPFW2+v6 does not provide enough
-      functionality and stability to work as a drop-in replacement for
-      IP6FW, we won't remove IP6FW.</p>
-
-      <p>In order to get the new code to that point we
-      <b>really</b>
-
-      need more testers with real world IPv6 deployment and interest in
-      IPFW+v6. The lack thereof (I haven't received a single answer on my
-      requests to various FreeBSD mailing lists) has made it hard to
-      progress.</p>
-    <h3>Open tasks:</h3><ol><li>Properly implement O_REJECT for IPv6</li><li>Maybe implement O_LOG</li><li>Test new(er) IPFW2 opcodes with IPv6</li><li>Test</li><li>Test</li><li>Test</li></ol><hr /><h2><a name="Move-ARP-out-of-routing-table" href="#Move-ARP-out-of-routing-table" id="Move-ARP-out-of-routing-table">Move ARP out of routing table</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~qingli/" title="http://people.freebsd.org/~qingli/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~qingli/" title="">http://people.freebsd.org/~qingli/</a></td></tr></table><p>
-	Contact:
-          Qing
-
-          Li
-         &lt;<a href="mailto:qingli@freebsd.org">qingli@freebsd.org</a>&gt;
-	</p>
-      <p>I've sent the patch to jinmei@isl.rdc.toshiba.co.jp @KAME for
-      review. I'm still waiting for feedback from Andre. There hasn't
-      been any major change since the last report. I've kept the code in
-      sync with CURRENT. Gleb has created a separate P4 branch and has
-      been helping out on the locking side. Gleb is also helping out on
-      the testing front.</p>
-    <h3>Open tasks:</h3><ol><li>I'm waiting for review feedback from my mentor Andre on the
-      overall design and code. I'm waiting for feedback from Andre on
-      Gleb's suggested modification.</li></ol><hr /><h2><a name="TCP-Reassembly-Rewrite-and-Optimization" href="#TCP-Reassembly-Rewrite-and-Optimization" id="TCP-Reassembly-Rewrite-and-Optimization">TCP Reassembly Rewrite and Optimization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="http://people.freebsd.org/~andre/tcpoptimization.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="">http://people.freebsd.org/~andre/tcpoptimization.html</a></td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" title="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch"></a></td><td>
-	    URL: <a href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" title="">http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" title="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" title="">http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>Currently TCP segment reassembly is implemented as a linked list
-      of segments. With today's high bandwidth links and large
-      bandwidth*delay products this doesn't scale and perform well.</p>
-
-      <p>The rewrite optimizes a large number of operational aspects of
-      the segments reassembly process. For example it is very likely that
-      the just arrived segment attaches to the end of the reassembly
-      queue, so we check that first. Second we check if it is the missing
-      segment or alternatively attaches to the start of the reassembly
-      queue. Third consecutive segments are merged together (logically)
-      and are skipped over in one jump for linear searches instead of
-      each segment at a time.</p>
-
-      <p>Further optimizations prototyped merge consecutive segments on
-      the mbuf level instead of only logically. This is expected to give
-      another significant performance gain. The new reassembly queue is
-      tracking all holes in the queue and it may be beneficial to
-      integrate this with the scratch pad of SACK in the future.</p>
-
-      <p>Andrew Gallatin was able to get 3.7Gb/sec TCP performance on
-      dual-2Gbit Myrinet cards with severe packet reordering (due to a
-      firmware bug) with the new TCP reassembly code. See second
-      link.</p>
-    <h3>Open tasks:</h3><ol><li>Need funding, see "Fundraising - TCP &amp; IP Routing
-      Optimization".</li></ol><hr /><h2><a name="TTCPv2:-Transactional-TCP-version-2" href="#TTCPv2:-Transactional-TCP-version-2" id="TTCPv2:-Transactional-TCP-version-2">TTCPv2: Transactional TCP version 2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="http://people.freebsd.org/~andre/tcpoptimization.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="">http://people.freebsd.org/~andre/tcpoptimization.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" title="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" title="">http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>The old TTCP according to RFC1644 was insecure, intrusive,
-      complicated and has been removed from FreeBSD &gt;= 5.3. Although
-      the idea and semantics behind it are still sound and valid.</p>
-
-      <p>The rewrite uses a much easier and more secure system with 24bit
-      long client and server cookies which are transported in the TCP
-      options. Client cookies protect against various kinds of blind
-      injection attacks and can be used as well to generally secure TCP
-      sessions (for BGP for example). Server cookies are only exchanged
-      during the SYN-SYN/ACK phase and allow a server to ensure that it
-      has communicated with this particular client before. The first
-      connection is always performing a 3WHS and assigning a server
-      cookie to a client. Subsequent connections can send the cookie back
-      to the server and short-cut the 3WHS to SYN-&gt;OPEN on the
-      server.</p>
-
-      <p>TTCPv2 is fully configurable per-socket via the setsockopt()
-      system call. Clients and server not capable of TTCPv2 remain fully
-      compatible and just continue using the normal 3WHS without any
-      delay or other complications.</p>
-
-      <p>Work on implementing TTCPv2 is done to 90% and expected to be
-      available by early February 2005. Writing the implementation
-      specification (RFC Draft) has just started.</p>
-    <h3>Open tasks:</h3><ol><li>Need funding, see "Fundraising - TCP &amp; IP Routing
-      Optimization".</li></ol><hr /><h2><a name="Wireless-Networking-Support" href="#Wireless-Networking-Support" id="Wireless-Networking-Support">Wireless Networking Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@freebsd.org">sam@freebsd.org</a>&gt;
-	</p>
-      <p>A lot of bugs were fixed in preparation for the 6.0 release. 6.0
-      will be the first release to include full WPA support (both
-      supplicant and authenticator).</p>
-
-      <p>A presentation on the forthcoming multi-bss support was given at
-      BSDCan 2005. The slides from the talk are available at
-      <a href="http://www.freebsd.org/~sam/BSDCan2005.pdf" shape="rect">
-      http://www.freebsd.org/~sam/BSDCan2005.pdf</a>.
-
-      The plan is to commit this work to HEAD after 6.0 is released
-      which means the first release that will have it is 7.0.</p>
-    <h3>Open tasks:</h3><ol><li>hostapd needs work to support the IAPP and 802.11i
-      preauthentication protocols (these are simple conversions of
-      existing Linux code).</li></ol><hr /><br /><h1><a name="Userland-programs" href="#Userland-programs" id="Userland-programs">Userland programs</a></h1><br /><h2><a name="OpenBSD-dhclient-import." href="#OpenBSD-dhclient-import." id="OpenBSD-dhclient-import.">OpenBSD dhclient import.</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>The OpenBSD rewrite of dhclient has been imported, replacing the
-      ISC dhclient. The OpenBSD client provides better support for
-      roaming on wireless networks and a simpler model of operation.
-      Instead of a single dhclient process per system, there is one per
-      network interface. This instance automatically goes away in the
-      even of link loss and is restarted via devd when link is
-      reacquired. To support this change, many aspects of the network
-      interface configuration process were overhauled.</p>
-
-      <p>The current code works well in most circumstances, but more
-      testing and polishing is needed.</p>
-    <hr /><h2><a name="Removing-of-old-basesystem-files-and-directories" href="#Removing-of-old-basesystem-files-and-directories" id="Removing-of-old-basesystem-files-and-directories">Removing of old basesystem files and directories</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.Leidinger.net/FreeBSD/current-patches/obsolete_removal.diff" title="http://www.Leidinger.net/FreeBSD/current-patches/obsolete_removal.diff">Patch</a></td><td>
-	    URL: <a href="http://www.Leidinger.net/FreeBSD/current-patches/obsolete_removal.diff" title="Patch">http://www.Leidinger.net/FreeBSD/current-patches/obsolete_removal.diff</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD lacks a way to remove old/outdated files and directories
-      in the basesystem. I have a patch which removes obsolete files in a
-      safe way (interactively, since only the administrator really knows
-      if there's a need to keep an old file or not; there's a switch for
-      batch-processing). This feature may or may not be available for
-      6.0-RELEASE, depending on the decision from the Release
-      Engineering team.</p>
-    <h3>Open tasks:</h3><ol><li>Respect the NO_* switches and remove those files too. This is
-      easy to do with the current implementation, but isn't needed to
-      commit the removal of obsolete files feature.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/platforms/ppc.html" title="http://www.freebsd.org/platforms/ppc.html">FreeBSD/PPC Platform page.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/platforms/ppc.html" title="FreeBSD/PPC Platform page.">http://www.freebsd.org/platforms/ppc.html</a></td></tr></table><p>
-	Contact:
-          Peter
-
-          Grehan
-         &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>Florent Thoumie has updated the massively out-of-date platform
-      page. Work continues to creating a 6.0 release of the PowerPC
-      port.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freshports.org/" title="http://www.freshports.org/"></a></td><td>
-	    URL: <a href="http://www.freshports.org/" title="">http://www.freshports.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>The following new features have been added to FreshPorts:</p>
-
-      <ul>
-        <li>
-          <a href="http://www.freshports.org/ports- deprecated.php" shape="rect">
-          Deprecated Ports</a>
-        </li>
-
-        <li>
-          <a href="http://www.freshports.org/ports- expired.php" shape="rect">Expired
-          Ports</a>
-        </li>
-
-        <li>
-          <a href="http://www.freshports.org/ports-expiration- date.php" shape="rect">
-          Ports Set To Expire</a>
-        </li>
-
-        <li>
-          <a href="http://www.freshports.org/phorum/read.php?f=1&amp;i=1021&amp;t=1021#repl y_1021" shape="rect">
-          Display relevant entries from ports/UPDATING on your watch
-          list</a>
-        </li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>I've noticed that FreshPorts is incorrectly reporting
-      vulnerabilities under a
-      <a href="http://www.freshports.org/phorum/read.php?f=1&amp;i=1025&amp;t=1025" shape="rect">
-      very specific situation</a>
-
-      . The fix is sitting in BETA, waiting to be moved to
-      production.</li><li>I've been working on added Last-Modified to the headers. At
-      present, there are none. Most of the pages on the BETA website have
-      been completed. I need to move this to production soon.</li><li>Customized news feeds are in the works. You'll be able to
-      create a news feed for each of your watch lists. This work is
-      contingent upon finishing the Last-Modified headers.</li></ol><hr /><h2><a name="Porting-v9-of-Intels-C/C++-Compiler" href="#Porting-v9-of-Intels-C/C++-Compiler" id="Porting-v9-of-Intels-C/C++-Compiler">Porting v9 of Intels C/C++ Compiler</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>Intel released version 9 of its C/C++ compiler. Work to port the
-      x86 version to FreeBSD is in progress as time permits. Porting the
-      EM64T (amd64) version is on the TODO list too, but is subject to
-      enough free time and access to appropriate hardware.</p>
-    <hr /><h2><a name="Update-of-the-Linux-userland-infrastructure" href="#Update-of-the-Linux-userland-infrastructure" id="Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Emulation
-
-          Mailinglist
-         &lt;<a href="mailto:emulation@FreeBSD.org">emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>The cleanup/streamlining and the possibility of overriding the
-      default Linux base as reported in the last report happened without
-      major problems. Work on the open tasks hasn't started yet, but is
-      scheduled to start "soon". If a volunteer wants to spend some hours
-      on one of the open tasks, he should tell it on the emulation
-      mailinglist.</p>
-    <h3>Open tasks:</h3><ol><li>Refactoring the common RPM code in
-      x11-toolkits/linux-gtk/Makefile into bsd.rpm.mk.</li><li>Determining which up-to-date Linux distribution to use as the
-      next default Linux base. Important criteria:
-      <ul>
-        <li>RPM based (to be able to use the existing
-        infrastructure)</li>
-
-        <li>good track record regarding availability of security
-        fixes</li>
-
-        <li>packages available from several mirror sites</li>
-
-        <li>available for several hardware architectures (e.g. i386,
-        amd64, sparc64; Note: not all architectures have a working
-        linuxolator for their native bit with, but as long as there are
-        no userland bits available, no motivation regarding writing the
-        kernel bits will arise)</li>
-      </ul>
-      </li><li>Moving the linuxolator userland to an up-to-date version (see
-      above).</li></ol><hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="OpenBSD-packet-filter---pf" href="#OpenBSD-packet-filter---pf" id="OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@freebsd.org">mlaier@freebsd.org</a>&gt;
-	</p>
-      <p>We will have pf as of OpenBSD 3.7 for RELENG_6. Import has been
-      completed in early May and FreeBSD release 6.0 will ship with
-      it.</p>
-
-      <p>A few serious issues with pfsync on SMP have been discovered
-      since CARP is around and more and more people use it on big iron.
-      Everything that has been discovered is fixed in HEAD and (if
-      applicable) MFCed back to RELENG_5. Some functional changes are
-      undergoing testing right now and will be MFCed in the coming
-      days.</p>
-
-      <p>With the import of if_bridge from Net/OpenBSD we finally have a
-      bridge implementation that allows for stateful filtering as well as
-      IPv6 filtering. Please see the respective report.</p>
-    <h3>Open tasks:</h3><ol><li>Shared lock implementation?</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan" href="#BSDCan" id="BSDCan">BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/2005/" title="http://www.bsdcan.org/2005/"></a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2005/" title="">http://www.bsdcan.org/2005/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>The second annual
-      <a href="http://www.bsdcan.org" shape="rect">BSDCan</a>
-
-      conference was well presented, well attended, and everyone went
-      away with good stories to tell. If you know anything that attended,
-      get them to tell you what they did, who they met with, and talks
-      they listened to.</p>
-
-      <p>We had 197 people from 15 different countries. That's a strong
-      turnout by any definition.</p>
-
-      <p>We'll be adding more people to the program committee for BSDCan
-      2006. This job involves prodding and poking people from your
-      respective projects. You get them to submit papers. There are a lot
-      of very interesting projects out there and not all of them submit a
-      paper.</p>
-
-      <p>If you know someone doing interesting work, please let me know
-      and urge them to start thinking about BSDCan 2006.</p>
-    <hr /><h2><a name="EuroBSDCon-2005---Basel" href="#EuroBSDCon-2005---Basel" id="EuroBSDCon-2005---Basel">EuroBSDCon 2005 - Basel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon.org/" title="http://www.eurobsdcon.org/">Homepage</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org/" title="Homepage">http://www.eurobsdcon.org/</a></td></tr><tr><td><a href="http://www.eurobsdcon.org/cfp.php" title="http://www.eurobsdcon.org/cfp.php">Call for papers</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org/cfp.php" title="Call for papers">http://www.eurobsdcon.org/cfp.php</a></td></tr></table><p>
-	Contact:
-          Information
-         &lt;<a href="mailto:info@eurobsdcon.org">info@eurobsdcon.org</a>&gt;
-	</p>
-      <p>The fourth European BSD conference in Basel, Switzerland is a
-      great opportunity to present new ideas to the community and to meet
-      some of the developers behind the different BSDs.</p>
-
-      <p>The two day conference program (Nov 26 and 27) will be
-      complemented by a tutorial day preceding the conference (Nov
-      25).</p>
-
-      <p>The program committee is looking for tutorial and paper
-      submissions. For details, please see: The
-      <a href="http://www.eurobsdcon.org/cfp.php" shape="rect">call for papers</a>
-
-      online.</p>
-    <hr /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In May 2005, Remko Lodder joined the FreeBSD Security Team,
-      followed by Christian S.J. Peron in July 2005. In the same time
-      period, Gregory Shapiro and Josef El-Rayes resigned from the team
-      in order to devote their time to other projects. The current
-      Security Team membership is published on the web site.</p>
-
-      <p>In the time since the last FreeBSD status report, twelve
-      security advisories have been issued concerning problems in the
-      base system of FreeBSD; of these, six problems were in
-      "contributed" code, while five problems were in code maintained
-      within FreeBSD. The Vulnerabilities and Exposures Markup Language
-      (VuXML) document has continued to be updated by the Security Team
-      and the Ports Committers documenting new vulnerabilities in the
-      FreeBSD Ports Collection; since the last status report, 97 new
-      entries have been added, bringing the total up to 519.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 4.10, FreeBSD 4.11, FreeBSD 5.3, and FreeBSD
-      5.4. Their respective End of Life dates are listed on the web
-      site.</p>
-    <hr /><h2><a name="TrustedBSD-SEBSD" href="#TrustedBSD-SEBSD" id="TrustedBSD-SEBSD">TrustedBSD SEBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/sebsd.html" title="http://www.TrustedBSD.org/sebsd.html">TrustedBSD/SEBSD web page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/sebsd.html" title="TrustedBSD/SEBSD web page">http://www.TrustedBSD.org/sebsd.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project has released a new snapshot of "SEBSD", a
-      port of NSA's SELinux FLASK and Type Enforcement implementation to
-      FreeBSD based on a late 2005 FreeBSD 6.x snapshot. The SEBSD
-      distribution has now been updated in Perforce to a recent 6.x
-      snapshot, and a new distribution will be made available in the near
-      future.</p>
-
-      <p>Work has been performed to merge additional dependencies for
-      SEBSD back into the base FreeBSD tree, including most recently,
-      changes to devfs, and System V and POSIX IPC.</p>
-    <h3>Open tasks:</h3><ol><li>Update to new NSA FLASK implementation, which has improved
-      MLS support.</li><li>Merge remaining kernel changes to support SEBSD back to the
-      base FreeBSD CVS repository, including file descriptor labeling and
-      access control (in contrast to file labeling and access control),
-      and categorization of kernel privileges.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2005-07-2005-10.html b/website/content/en/status/report-2005-07-2005-10.html
deleted file mode 100644
index 2b6edd3cf3..0000000000
--- a/website/content/en/status/report-2005-07-2005-10.html
+++ /dev/null
@@ -1,1384 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>After a long, exhausting, yet very productive third quarter of 2005
-    FreeBSD 6.0 has been released. Many activities were put into the
-    background in order to make this release the success it has
-    become.</p><p>Nonetheless, we received a tremendous amount of reports covering
-    various projects that either found their way into FreeBSD 6.0 already
-    or have started to develop in, what is now known as 7-CURRENT. The
-    EuroBSDCon and the Developer Summit in Basel next week will be a good
-    opportunity to help some of the ideas herein to take off.</p><p>Last round we had the pleasure to introduce our accepted Google
-    Summer of Code projects. Now, that the summer is over, we are even
-    more pleased to include reports about the outcome of these projects.
-    Some already found their way into the tree or the general public
-    otherwise - most ocularly the new webdesign.</p><p>Unfortunately, this publication has been delayed for various
-    reasons - the before mentioned release of 6.0 being one of them.
-    Thus, some of the reports might no longer be as up to date as they
-    were when we received them and we encourage you - even more this time
-    - to also visit the weblinks to get more recent information.</p><p>Thanks again to everyone who submitted reports, and our sincere
-    apologies for running late this time.</p><hr /><h3><a href="#Google-summer-of-code">Google summer of code</a></h3><ul><li><a href="#BSD-Installer">BSD Installer</a></li><li><a href="#csup:-cvs-mode-support">csup: cvs mode support</a></li><li><a href="#FreeBSD-Web-Site-Redesign">FreeBSD Web Site Redesign</a></li><li><a href="#Fuse-for-FreeBSD">Fuse for FreeBSD</a></li><li><a href="#gjournal">gjournal</a></li><li><a href="#gvinum-'move',-'rename'-support">gvinum 'move', 'rename' support</a></li><li><a href="#Improve-Libalias">Improve Libalias</a></li><li><a href="#Integrated-SNMP-monitoring">Integrated SNMP monitoring</a></li><li><a href="#Interface-Cleanup">Interface Cleanup</a></li><li><a href="#launchd(8)-for-FreeBSD">launchd(8) for FreeBSD</a></li><li><a href="#Nsswitch-/-Caching-daemon">Nsswitch / Caching daemon</a></li><li><a href="#SNMP-Monitoring">SNMP Monitoring</a></li><li><a href="#UFS-Journaling">UFS Journaling</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#ggtrace">ggtrace</a></li><li><a href="#iSCSI-Initiator">iSCSI Initiator</a></li><li><a href="#pfSense">pfSense</a></li><li><a href="#Realtime-POSIX-signal">Realtime POSIX signal</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#bridge.c-retired">bridge.c retired</a></li><li><a href="#TODO-list-for-volunteers">TODO list for volunteers</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></li><li><a href="#NEWCARD">NEWCARD</a></li><li><a href="#Sound-subsystem-improvements">Sound subsystem improvements</a></li><li><a href="#The-Kernel-Stress-Test-Suite">The Kernel Stress Test Suite</a></li></ul><h3><a href="#Network-infrastructure">Network infrastructure</a></h3><ul><li><a href="#OpenBSD-dhclient-import">OpenBSD dhclient import</a></li><li><a href="#Removable-interface-improvements">Removable interface improvements</a></li><li><a href="#TCP-&amp;-IP-Routing-Optimization-Fundraise">TCP &amp; IP Routing Optimization Fundraise</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Porting-FreeBSD-to-the-Xbox">Porting FreeBSD to the Xbox</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></li><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Ports-Tinderbox">Ports Tinderbox</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#Cronyx/Asterisk">Cronyx/Asterisk</a></li><li><a href="#OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan">BSDCan</a></li><li><a href="#EuroBSDCon-2005---Basel">EuroBSDCon 2005 - Basel</a></li></ul><ul><li><a href="#Problem-Report-Database">Problem Report Database</a></li></ul><hr /><br /><h1><a name="Google-summer-of-code" href="#Google-summer-of-code" id="Google-summer-of-code">Google summer of code</a></h1><br /><h2><a name="BSD-Installer" href="#BSD-Installer" id="BSD-Installer">BSD Installer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdinstaller.org/" title="http://www.bsdinstaller.org/"></a></td><td>
-	    URL: <a href="http://www.bsdinstaller.org/" title="">http://www.bsdinstaller.org/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="http://wiki.freebsd.org/moin.cgi/BSDInstaller"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="">http://wiki.freebsd.org/moin.cgi/BSDInstaller</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Turner
-         &lt;<a href="mailto:soc-andrew@FreeBSD.org">soc-andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>By the end of August I managed to modify the release building
-      process to build a live CD that loads the front and backends. It
-      could install all the distfiles, install the ports tree and had
-      minimal support to install and uninstall packages.</p>
-
-      <p>Since the end of the Summer of Code I have worked to integrate
-      the new Lua backend. This has been successful, with it now past the
-      point of the BSDINSTALLER-BETA-1 release. It can install the
-      distfiles but not the ports tree or packages yet.</p>
-    <hr /><h2><a name="csup:-cvs-mode-support" href="#csup:-cvs-mode-support" id="csup:-cvs-mode-support">csup: cvs mode support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/ChristophMathys" title="http://wiki.freebsd.org/moin.cgi/ChristophMathys">The wikipage with details about my SoC-project</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/ChristophMathys" title="The wikipage with details about my SoC-project">http://wiki.freebsd.org/moin.cgi/ChristophMathys</a></td></tr><tr><td><a href="http://mu.org/~mux/csup.html" title="http://mu.org/~mux/csup.html">csup project page</a></td><td>
-	    URL: <a href="http://mu.org/~mux/csup.html" title="csup project page">http://mu.org/~mux/csup.html</a></td></tr></table><p>
-	Contact:
-          Christoph
-
-          Mathys
-         &lt;<a href="mailto:cmathys@bluewin.ch">cmathys@bluewin.ch</a>&gt;
-	</p>
-      <p>During the "Summer of Code" I worked on csup (a rewrite of CVSup
-      in C). It already supported checkout-mode, so my task was to
-      implement support for cvs-mode. The biggest part of the project was
-      to implement support for rcs-files. As "byproducts" I also wrote
-      the necessary code to create nodes/hardlinks and to update files
-      using the rsync-algorithm. For what I know, the code works fine,
-      but errorhandling is practically inexistent.</p>
-    <h3>Open tasks:</h3><ol><li>Errors should be properly handled</li><li>Support to get fixups</li><li>The hard part to support rcs file updates is done, but there
-      is no checksum, some options are not honored and the performance
-      could be improved</li></ol><hr /><h2><a name="FreeBSD-Web-Site-Redesign" href="#FreeBSD-Web-Site-Redesign" id="FreeBSD-Web-Site-Redesign">FreeBSD Web Site Redesign</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org" title="http://www.FreeBSD.org"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org" title="">http://www.FreeBSD.org</a></td></tr><tr><td><a href="http://www.FreeBSD.org/old" title="http://www.FreeBSD.org/old">Archived copy of old site.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/old" title="Archived copy of old site.">http://www.FreeBSD.org/old</a></td></tr></table><p>
-	Contact:
-          Emily
-
-          Boyd
-         &lt;<a href="mailto:soc-emily@FreeBSD.org">soc-emily@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Web
-
-          Team
-         &lt;<a href="mailto:freebsd-www@FreeBSD.org">freebsd-www@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new website has gone live! Thanks to Emily Boyd for all her
-      hard work. We still have a lot of work to do to integrate
-      suggestions that have been made by users since we went live. The
-      new CSS design makes it much easier to rapidly change the look and
-      feel of the site, so it is easy to experiment. We're still looking
-      for more HTML/CSS designers to help us improve the site.</p>
-    <hr /><h2><a name="Fuse-for-FreeBSD" href="#Fuse-for-FreeBSD" id="Fuse-for-FreeBSD">Fuse for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://fuse4bsd.creo.hu/" title="http://fuse4bsd.creo.hu/">New home page</a></td><td>
-	    URL: <a href="http://fuse4bsd.creo.hu/" title="New home page">http://fuse4bsd.creo.hu/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/FuseFilesystem" title="http://wiki.freebsd.org/moin.cgi/FuseFilesystem">FreeBSD wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/FuseFilesystem" title="FreeBSD wiki page">http://wiki.freebsd.org/moin.cgi/FuseFilesystem</a></td></tr><tr><td><a href="http://creo.hu/~csaba/projects/fuse4bsd/downloads/" title="http://creo.hu/~csaba/projects/fuse4bsd/downloads/">Download location</a></td><td>
-	    URL: <a href="http://creo.hu/~csaba/projects/fuse4bsd/downloads/" title="Download location">http://creo.hu/~csaba/projects/fuse4bsd/downloads/</a></td></tr></table><p>
-	Contact:
-          Csaba
-
-          Henk
-         &lt;<a href="mailto:soc-chenk@freebsd.org">soc-chenk@freebsd.org</a>&gt;
-	</p>
-      <p>Fuse for FreeBSD is the outcome of my "ssh based networking
-      filesystem for FreeBSD" SoC project.</p>
-
-      <p>The kernel interface for the comprehensive userspace filesystem
-      API provided by the (
-      <a href="http://fuse.sourceforge.net" shape="rect">Fuse project</a>
-
-      ) has been implemented for FreeBSD (6.x and 7.x), under the BSD
-      license. This has the benefit of opening up the possibility of
-      porting the rich collection of Fuse based filesystems to
-      FreeBSD.</p>
-
-      <p>Now it's ready for consumption by a broader audience. The
-      <tt>sysutils/fusefs-kmod</tt>
-
-      ,
-      <tt>sysutils/fusefs-libs</tt>
-
-      ,
-      <tt>sysutils/fusefs-sshfs</tt>
-
-      ports can be expected to be integrated into the FreeBSD ports tree
-      in the next few days (the ports were created and are maintained by
-      Anish Mistry, and Simon Barner's careful review also helps a
-      lot).</p>
-    <h3>Open tasks:</h3><ol><li>Implement missing features like extended attributes and
-      attribute/name caching (with timeout).</li><li>Resolve problems with autotools and integrate userspace
-      modifications into the Fuse codebase.</li><li>Port Fuse based filesystems and language bindings to
-      FreeBSD.</li><li>Create sysfs (Fuse based filesystem interface to
-      sysctl).</li><li>Test, test, test among a broad variety of
-      circumstances.</li></ol><hr /><h2><a name="gjournal" href="#gjournal" id="gjournal">gjournal</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/gjournal" title="http://wiki.freebsd.org/moin.cgi/gjournal">gjournal wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/gjournal" title="gjournal wiki page">http://wiki.freebsd.org/moin.cgi/gjournal</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@yahoo.com">ivoras@yahoo.com</a>&gt;
-	</p>
-      <p>Gjournal provides GEOM-level journaling and COW capabilities to
-      storage devices. Unfortunately, it cannot be used as a substitute
-      for filesystem journaling (fsck is still needed when gjournal
-      device is used to host filesystems). Development has slowed down,
-      and the existing code needs much more testing. If there is
-      continued interest in it, I'll probably split the functionalities
-      into two projects, one handling COW and one handling the
-      journaling, in order to make the code cleaner.</p>
-    <h3>Open tasks:</h3><ol><li>More testing is needed.</li></ol><hr /><h2><a name="gvinum-'move',-'rename'-support" href="#gvinum-'move',-'rename'-support" id="gvinum-'move',-'rename'-support">gvinum 'move', 'rename' support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename" title="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename">gvinum 'move', 'rename' wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/GvinumMoveRename" title="gvinum 'move', 'rename' wiki">http://wiki.freebsd.org/moin.cgi/GvinumMoveRename</a></td></tr></table><p>
-	Contact:
-          Chris
-
-          Jones
-         &lt;<a href="mailto:soc-cjones@freebsd.org">soc-cjones@freebsd.org</a>&gt;
-	</p>
-      <p>Support for moving and renaming objects in gvinum was completed
-      at the end of August 2005. All gvinum objects (drives, subdisks,
-      plexes, and volumes) can be renamed, and subdisks can be moved from
-      drive to drive. Also, a man page for gvinum was created.</p>
-    <h3>Open tasks:</h3><ol><li>Update FreeBSD Handbook chapter on vinum to reflect gvinum.
-      Slowly in progress, but hopefully done by the end of the year,
-      workload permitting.</li></ol><hr /><h2><a name="Improve-Libalias" href="#Improve-Libalias" id="Improve-Libalias">Improve Libalias</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/PaoloPisati" title="http://wiki.freebsd.org/moin.cgi/PaoloPisati">Wiki/Official project site</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/PaoloPisati" title="Wiki/Official project site">http://wiki.freebsd.org/moin.cgi/PaoloPisati</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/PaoloPisati" title="http://wiki.freebsd.org/moin.cgi/PaoloPisati"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/PaoloPisati" title="">http://wiki.freebsd.org/moin.cgi/PaoloPisati</a></td></tr></table><p>
-	Contact:
-          Paolo
-
-          Pisati
-         &lt;<a href="mailto:p.pisati@oltrelinux.com">p.pisati@oltrelinux.com</a>&gt;
-	</p>
-      <p>The project met all the scheduled goals, and following are the
-      new features implemented in libalias:
-      <ul>
-        <li>integration with IPFW in kernel land</li>
-
-        <li>support for 4.x and 5.x as kld</li>
-
-        <li>converted from a monolithic to a modular architecture, added
-        the ability to load/unload at runtime support for new protocols
-        (modules work both in kernel and user land)</li>
-
-        <li>added logging support in kernel land</li>
-      </ul>
-
-      <br clear="none" />
-
-      Fell free to suggest other improvements.</p>
-    <h3>Open tasks:</h3><ol><li>Test and feedback are welcome</li></ol><hr /><h2><a name="Integrated-SNMP-monitoring" href="#Integrated-SNMP-monitoring" id="Integrated-SNMP-monitoring">Integrated SNMP monitoring</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~harti/bsnmp/index.html" title="http://people.freebsd.org/~harti/bsnmp/index.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~harti/bsnmp/index.html" title="">http://people.freebsd.org/~harti/bsnmp/index.html</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/ShteryanaShopova" title="http://wiki.freebsd.org/moin.cgi/ShteryanaShopova"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/ShteryanaShopova" title="">http://wiki.freebsd.org/moin.cgi/ShteryanaShopova</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/SnmpMonitoringModulesStatus" title="http://wiki.freebsd.org/moin.cgi/SnmpMonitoringModulesStatus"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/SnmpMonitoringModulesStatus" title="">http://wiki.freebsd.org/moin.cgi/SnmpMonitoringModulesStatus</a></td></tr></table><p>
-	Contact:
-          Philip
-
-          Paeps
-         &lt;<a href="mailto:philip@FreeBSD.org">philip@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:soc-shteryana@FreeBSD.org">soc-shteryana@FreeBSD.org</a>&gt;
-	</p>
-      <p>This summer, we've had the pleasure of having two Google Summer
-      of Code students hacking on our SNMP monitoring machinery. Victor
-      worked on implementing the Host Resources, TCP and UDP MIBs in
-      bsnmpd while Shteryana started on client-side SNMP tools.</p>
-
-      <p>With these modules and tools, a FreeBSD installation can be
-      monitored without having to install any (heavy!) third-party
-      tools.</p>
-    <h3>Open tasks:</h3><ol><li>
-        <p>While the modules and the tools currently in Perforce are
-        generally functional, they still need some tidying up (style(9))
-        and testing before they can be committed to CVS.</p>
-
-        <p>At the time of this writing, the Hostres MIB is pretty much
-        commit-ready in Perforce (//depot/user/philip/bsnmp/...), the
-        other modules and tools live in
-        //depot/projects/soc2005/bsnmp/... They'll be branched for
-        tidying up and committing "Real Soon Now"[tm]</p>
-      </li><li>Testers are very welcome. :-) Please let us know about any
-      bugs!</li></ol><hr /><h2><a name="Interface-Cleanup" href="#Interface-Cleanup" id="Interface-Cleanup">Interface Cleanup</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkInterfaceApisProposal" title="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkInterfaceApisProposal">SoC Proposal</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkInterfaceApisProposal" title="SoC Proposal">http://wiki.freebsd.org/moin.cgi/CleanupOfNetworkInterfaceApisProposal</a></td></tr></table><p>
-	Contact:
-          Anders
-
-          Persson
-         &lt;<a href="mailto:soc-anders@freebsd.org">soc-anders@freebsd.org</a>&gt;
-	</p>
-      <p>The dependencies to kernel-only datastructures in netstat
-      (ifnet, etc.) have been removed almost completely (AppleTalk and
-      IPX still needs work). In order to remove the dependencies, the
-      debugging features of netstat had to be removed. However, a project
-      to create a generic, modular 'data structure' examination tool is
-      ongoing, and the debugging features factor out of netstat have been
-      migrated to this tool.</p>
-    <h3>Open tasks:</h3><ol><li>Refactoring of the netstat code, create a modular version in
-      the spirit of ifconfig.</li><li>Data structure examination tool needs to be completed,
-      current state is more that of a prototype.</li></ol><hr /><h2><a name="launchd(8)-for-FreeBSD" href="#launchd(8)-for-FreeBSD" id="launchd(8)-for-FreeBSD">launchd(8) for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/launchd" title="http://wiki.freebsd.org/moin.cgi/launchd">Project Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/launchd" title="Project Wiki">http://wiki.freebsd.org/moin.cgi/launchd</a></td></tr></table><p>
-	Contact:
-          R. Tyler
-
-          Ballance
-         &lt;<a href="mailto:tyler@tamu.edu">tyler@tamu.edu</a>&gt;
-	</p>
-      <p>In short, launchd can run perfectly fine on FreeBSD, and
-      combined with launchctl, it can be used to manage daemons through
-      the launchctl(1) interface. Jobs can be added and managed two ways
-      as of yet from launchctl(1). Using zarzycki@'s experimental
-      "submit" command within launchctl(1) or by using my
-      lame/rudimentary/etc "launcher" format (launchd/launchers/*.launch)
-      which uses property(3) to parse out three simple, and important
-      details. The program label, path, and any program flags. Using the
-      "load" command, one can load the data into launchctl(1) and then
-      start the processes with the..."start" command. Jobs can be
-      removed/stopped with the "remove" command. The "limit" command
-      still throws launchctl(1) into an infinite loop, and yes, I plan on
-      fixing this.</p>
-
-      <p>There are some things that need to be fixed, first off, some
-      sort of boot time integration, whether as an init-replacement (i.e.
-      PID 1, a la Mac OS X) or as the first thing started from init, that
-      kicks all rcng things off. Along with, more importantly, a plist
-      parser, so we can have full compatibility with Mac OS X's launchd
-      via Core Foundation.</p>
-
-      <p>I'm also trying to get launchd(8) relicensed with the BSD
-      license, as opposed to the APSL, anybody with tips, or methods for
-      achieving this goal, contact me at tyler@tamu.edu</p>
-    <h3>Open tasks:</h3><ol><li>Writing a light-weight plist (non-XML) parser with lex and
-      yacc.</li></ol><hr /><h2><a name="Nsswitch-/-Caching-daemon" href="#Nsswitch-/-Caching-daemon" id="Nsswitch-/-Caching-daemon">Nsswitch / Caching daemon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingFinalReport" title="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingFinalReport"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingFinalReport" title="">http://wiki.freebsd.org/moin.cgi/NsswitchAndCachingFinalReport</a></td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/MichaelBushkov" title="http://wiki.freebsd.org/moin.cgi/MichaelBushkov"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/MichaelBushkov" title="">http://wiki.freebsd.org/moin.cgi/MichaelBushkov</a></td></tr></table><p>
-	Contact:
-          Michael
-
-          Bushkov
-         &lt;<a href="mailto:"></a>&gt;
-	</p>
-      <p>The nsswitch / caching daemon project was developed within the
-      Google's Summer Of Code program. Almost all goals of the project
-      were achieved. Thanks to Brooks Davis and Jacques Vidrine, who were
-      my mentors and greatly helped me.</p>
-
-      <p>Nsswitch subsystem was extended to support new sources
-      (services, protocols, rpc, openssh and GT4). The testing of the
-      Globus Grid Toolkit 4 patch (which adds support for nsswitch to
-      GT4) is still to be done. For nsswitch to support caching, the
-      caching daemon was implemented on top of the caching library, which
-      was also developed during the SoC. The current version of the
-      daemon uses simple nscd-like configuration file and seems to be
-      stable. To complete the SoC project, the experimental version of
-      libc with in-process caching enabled was made. It's benchmarking
-      will be done in the nearest future.</p>
-
-      <p>There were some requests for caching daemon to be able to act
-      like NSCD (to perform the actual nsswitch lookups by itself), so it
-      was modified to support this feature. But current implementation
-      has some restrictions and requires a lot of testing. Right now the
-      final polishing is being made to the project's sources, so that
-      they could be added to the CURRENT</p>
-    <h3>Open tasks:</h3><ol><li>Extend caching daemon to support NSCD functionality</li><li>Test Globus Grid Toolkit 4 patch</li><li>Add support for MAC and audit related configuration files to
-      the nsswitch</li></ol><hr /><h2><a name="SNMP-Monitoring" href="#SNMP-Monitoring" id="SNMP-Monitoring">SNMP Monitoring</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/VictorCruceru" title="http://wiki.freebsd.org/moin.cgi/VictorCruceru">FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/VictorCruceru" title="FreeBSD wiki">http://wiki.freebsd.org/moin.cgi/VictorCruceru</a></td></tr></table><p>
-	Contact:
-          Harti
-
-          Brandt
-         &lt;<a href="mailto:harti@freebsd.org">harti@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Philip
-
-          Paeps
-         &lt;<a href="mailto:philip@freebsd.org">philip@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Victor
-
-          Cruceru
-         &lt;<a href="mailto:soc-victor@freebsd.org">soc-victor@freebsd.org</a>&gt;
-	</p>
-      <p>New MIBs are implmented for the BSNMP agent:</p>
-
-      <ol>
-        <li>
-        <strong>HOST-RESOURCES-MIB</strong>
-
-        (
-        <a href="http://www.ietf.org/rfc/rfc2790.txt" shape="rect">
-        http://www.ietf.org/rfc/rfc2790.txt</a>
-
-        ). Philip is going to submit the code into the CVS
-        repository.</li>
-
-        <li>
-        <strong>TCP-MIB with combined IPv4 &amp; IPv6 support</strong>
-
-        (
-        <a href="http://www.ietf.org/rfc/rfc4022.txt" shape="rect">
-        http://www.ietf.org/rfc/rfc4022.txt</a>
-
-        ). This new TCP-MIB is 100% backward compatible with the old one
-        (v4 only). It adds a clear distinction between active and passive
-        tcp endpoints and for each endpoint info about the process it
-        belongs to.</li>
-
-        <li>
-        <strong>UDP-MIB with combined IPv4 &amp; IPv6 support</strong>
-
-        (
-        <a href="http://www.ietf.org/rfc/rfc4113.txt" shape="rect">
-        http://www.ietf.org/rfc/rfc4113.txt</a>
-
-        ). This new UDP-MIB is 100% backward compatible with the old one
-        (v4 only) and it adds multiple instances support for the UDP
-        endpoints and for each endpoint info about the processes using
-        it.</li>
-      </ol>
-    <h3>Open tasks:</h3><ol><li>For HOST-RESOURCES-MIB we are going to add support for more
-      detailed memory stats based of libmemstat(3)</li><li>The rest of the IPv6 MIBs.</li><li>FreeBSD enterprise MIBs for supporting SNMP configuration
-      (via SNMP SETs) for FreeBSD.</li></ol><hr /><h2><a name="UFS-Journaling" href="#UFS-Journaling" id="UFS-Journaling">UFS Journaling</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brian
-
-          Wilson
-         &lt;<a href="mailto:polytopes@gmail.com">polytopes@gmail.com</a>&gt;
-	<br />
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Scott has been working on inserting journalling hooks into the
-      ufs and ffs filesystem code. Brian has been balancing school and
-      redesigning various things that were deemed necessary to update
-      during the end of the actual SoC project.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the redesign of the internal block management
-      code.</li><li>Integration and test of the ffs/ufs hooks and the journaling
-      code.</li><li>Updating userland tools to be aware of and use the
-      journal.</li><li>Journal buffer management wiring to VM subsystem a la
-      XFS.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="ggtrace" href="#ggtrace" id="ggtrace">ggtrace</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ivoras.sharanet.org/projects/ggtrace.html" title="http://ivoras.sharanet.org/projects/ggtrace.html"></a></td><td>
-	    URL: <a href="http://ivoras.sharanet.org/projects/ggtrace.html" title="">http://ivoras.sharanet.org/projects/ggtrace.html</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@yahoo.com">ivoras@yahoo.com</a>&gt;
-	</p>
-      <p>Ggtrace is "GEOM gate tracer", utility to track I/O requests on
-      a storage device on FreeBSD. It uses the ggate facility of FreeBSD
-      to attach to a file or device and produces a device that can be
-      used for any I/O, including hosting filesystems.</p>
-
-      <p>I/O requests are presented in the form of a moving histogram
-      that can be used to discern which parts of the storage device are
-      used most often. One use of ggtrace is to analyze how filesystems
-      arrange and access data on storage devices.</p>
-
-      <p>The project is working and usable only on the RELENG_6
-      branch.</p>
-    <hr /><h2><a name="iSCSI-Initiator" href="#iSCSI-Initiator" id="iSCSI-Initiator">iSCSI Initiator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-12.tar.bz2" title="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-12.tar.bz2"></a></td><td>
-	    URL: <a href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-12.tar.bz2" title="">ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-12.tar.bz2</a></td></tr></table><p>
-	Contact:
-          Daniel
-
-          Braniss
-         &lt;<a href="mailto:danny@cs.huji.ac.il">danny@cs.huji.ac.il</a>&gt;
-	</p>
-      <p>This iSCSI kernel module and its companion control program, are
-      still under development, but the main parts seem to be working. A
-      second round of public tests has started.</p>
-    <h3>Open tasks:</h3><ol><li>login chap authentication</li><li>digest</li><li>network disconnect recovery</li></ol><hr /><h2><a name="pfSense" href="#pfSense" id="pfSense">pfSense</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pfsense.com" title="http://www.pfsense.com"></a></td><td>
-	    URL: <a href="http://www.pfsense.com" title="">http://www.pfsense.com</a></td></tr></table><p>
-	Contact:
-          Scott
-
-          Ullrich
-         &lt;<a href="mailto:sullrich@gmail.com">sullrich@gmail.com</a>&gt;
-	</p>
-      <p>pfSense is a m0n0wall derived operating system platform with
-      radically different goals such as using Packet Filter, FreeBSD 6,
-      ALTQ for excellent packet queueing and finally an integrated
-      package management system for extending the environment with new
-      features.</p>
-
-      <p>Work continues to stabilize pfSense in preparation for the
-      FreeBSD 6 release. Once FreeBSD 6 is released pfSense will enter
-      the final beta and release candidate phases in preparation for the
-      1.0 release.</p>
-    <h3>Open tasks:</h3><ol><li>Stabilize installer (cannot load kernel errors after
-      install)</li><li>Finish outgoing load balancing monitoring</li><li>Fix last minute bugs that turn up</li></ol><hr /><h2><a name="Realtime-POSIX-signal" href="#Realtime-POSIX-signal" id="Realtime-POSIX-signal">Realtime POSIX signal</a></h2><p>
-	Contact:
-          David
-
-          Xu
-         &lt;<a href="mailto:davidxu@FreeBSD.org">davidxu@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD kernel is powerful, but it still lacks some realtime
-      POSIX facilities, for example, sigqueue. Most of the code is ready,
-      and I am testing it.</p>
-    <h3>Open tasks:</h3><ol><li>POSIX timer, timer_xxx syscalls</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="bridge.c-retired" href="#bridge.c-retired" id="bridge.c-retired">bridge.c retired</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@freebsd.org">mlaier@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@freebsd.org">thompsa@freebsd.org</a>&gt;
-	</p>
-      <p>As of September 27, the old bridge(4) implementation has been
-      removed from HEAD and will not be part of FreeBSD 7 and later.
-      FreeBSD 6 will serve as transition period. The full functional
-      replacement if_bridge(4) is now available in FreeBSD 5 (not yet
-      part of 5.4 however), FreeBSD 6 and -CURRENT. Any problems should
-      be reported to Andrew Thompson, who is maintaining if_bridge in
-      FreeBSD.</p>
-    <h3>Open tasks:</h3><ol><li>Document the change in the handbook and other reference
-      material.</li></ol><hr /><h2><a name="TODO-list-for-volunteers" href="#TODO-list-for-volunteers" id="TODO-list-for-volunteers">TODO list for volunteers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The TODO list for volunteers (see the last report for more) is
-      now under review by some doc@ people.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Low-overhead-performance-monitoring-for-FreeBSD" href="#Low-overhead-performance-monitoring-for-FreeBSD" id="Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement">Project home page</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="Project home page">http://people.freebsd.org/~jkoshy/projects/perf-measurement</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>This projects implements a kernel module (hwpmc(4)), an
-      application programming interface (pmc(3)) and a few simple
-      applications (pmcstat(8) and pmccontrol(8)) for measuring system
-      performance using event monitoring hardware in modern CPUs.</p>
-
-      <p>The last three months have been spent in bug fixing and in
-      tweaking the code. A few more minor features and loose ends remain
-      to be taken care of. Once these are done, I hope to get started on
-      a graphical performance analyser.</p>
-    <hr /><h2><a name="NEWCARD" href="#NEWCARD" id="NEWCARD">NEWCARD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@freebsd.org">imp@freebsd.org</a>&gt;
-	</p>
-      <p>Due to an email snafu, the June report was not submitted, so
-      this report covers since the last 6 months.</p>
-
-      <p>Summary: The 16-bit part of NEWCARD has been greatly enhanced.
-      In addition, power control has become interrupt driven. Some
-      drivers make use of the new functionality.</p>
-
-      <p>The pccard layer now exports the CIS for each device that is
-      present, even if there's no driver for the card or parts of the
-      card.</p>
-
-      <p>The power up and reset sequence is now interrupt driven. This
-      has eliminated many of the long pauses that the system used to
-      experience after a card insertion. We can not play glitch-free
-      audio while inserting or removing a card.</p>
-
-      <p>A number of additional cards are recognized by PC Card. In
-      addition, drivers now can read the CIS for more information about
-      the card. Drivers have been enhanced to read the CIS for MAC
-      addresses and the like where appropriate.</p>
-
-      <p>The ed driver now attaches the mii bus of the AX88190 and
-      AX88790 fast ethernet PC Card chips. This allows better status
-      reporting and increased functionality for PHY chips that need some
-      help. The ed driver also supports the Tamarack TC5299J chipset
-      (including attaching its MII bus) now, the only open source OS that
-      does so (TC5299J cards will work with other open source OS, but
-      they won't report their status or attach a mii bus).</p>
-
-      <p>A number of bugs have been fixed in the pccard or cardbus
-      drivers. Most of these changes have been merged into the
-      forthcoming 6.0. Others will be merged after the release.</p>
-    <h3>Open tasks:</h3><ol><li>ExpressCard laptops have arrived with ExpressCard/54 and
-      ExpressCard/34 slots. It is unknown the extent of the work
-      necessary to support them.</li><li>The ISA attachment of cbb needs work to make it fully
-      functional.</li><li>A CIS parser in userland needs to be written. The pccardc
-      based CIS parser is OK, but it doesn't handle MFC cards too well.
-      Ideally the parser would produce output that is compatible with the
-      linux tool.</li><li>A mechanism for CIS override is needed. We need a tool that
-      will take an ascii representation of the CIS and produce a binary.
-      We need a tool that will install the binary into the kernel and
-      kernel modifications to switch from the CIS that's in the card to
-      the faked up CIS.</li><li>We need a mechanism for creating pseudo multi-function cards.
-      Initially, it seems that all we really need is the ability for an
-      arbitrary driver to add a sio companion, since that covers all the
-      cases I'm aware of. Resources would need to be 'donated' from the
-      creating driver to the sio card.</li><li>It would be nice if we could move to a more common CIS
-      parsing and dispatch. The CardBus side is wide open at the moment
-      since none of the pci drivers use the CIS information outside of a
-      few that get their MAC address via a standard interface.</li><li>The ep driver needs work to make the newer ep cards that have
-      mii bus on them actually probe and attach it. It needs to gain
-      media support for the non-mii based cards. The 3C1 still needs
-      work.</li><li>The sn driver needs work to support many of the SMC91Cxxx PC
-      Card devices. These are typically combination cards that need
-      special, non-standard initialization.</li><li>Power savings for 16-bit cards can be realized if we power
-      them up at 3.3V rather than at 5.0V. Not all cards can support
-      this, but many can and indicate this support in the CIS. Windows
-      tries the 3.3V configuration entries before the 5.0V ones. We
-      should do the same.</li><li>Most of the changes that have been made to the pccard and
-      cardbus layers can be merged back into RELENG_5.</li></ol><hr /><h2><a name="Sound-subsystem-improvements" href="#Sound-subsystem-improvements" id="Sound-subsystem-improvements">Sound subsystem improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Multimedia
-
-          Mailinglist
-         &lt;<a href="mailto:multimedia@FreeBSD.org">multimedia@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Ariff
-
-          Abdullah
-         &lt;<a href="mailto:skywizard@MyBSD.org.my">skywizard@MyBSD.org.my</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>Recently a lot of fixes, specially in handling format / rate
-      conversion and general stability was committed to -current. This
-      include fixes for most LOR's and new features (software volume
-      handling for soundcards without volume handling in hardware and the
-      possibility to switch to spdif).</p>
-
-      <p>A lot of effort was expended by Ariff (and other people) to come up
-      with those improvements. For this reason Ariff was "punished" with a
-      commit bit, so he is able to commit further improvements on his
-      own.</p>
-
-      <p>This work is not integrated into 6.0-RELEASE because of some
-      lose ends (see 'sndctl' below).</p>
-
-      <p>You can help by looking at
-      <a href="http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&amp;severity=&amp;priority=&amp;class=&amp;state=&amp;sort=none&amp;text=sound&amp;responsible=&amp;multitext=&amp;originator=&amp;release=" shape="rect">
-      sound related PR's in GNATS</a>
-
-      and making follow-up's which tell us if a problem still persists or
-      if a PR can be closed because the bug is fixed. Also feel free to
-      submit patches for anything on the TODO list below.</p>
-    <h3>Open tasks:</h3><ol><li>Update manual pages to reflect new features.</li><li>Fix driver specific issues (via, t4dwave, maestro).</li><li>Make all drivers MPSAFE.</li><li>Rewrite some parts (e.g. a new mixer subsystem with OSS
-      compatibility).</li><li>sndctl(1): tool to control non-mixer parts of the sound
-      system (e.g. spdif switching, virtual-3D effects) by an user
-      (instead of the sysctl approach in -current); pcmplay(1),
-      pcmrec(1), pcmutil(1).</li><li>Plugable FEEDER infrastructure. For ease of debugging various
-      feeder stuff and/or as userland library and test suite.</li><li>Support for new hardware (envy24, Intel HDA).</li><li>Performance enhancement (via 'slave'-channels, changes are
-      under review)?</li><li>Closer compatibility with OSS, especially for the upcoming
-      OSS v4.</li><li>Close a lot of PR's.</li><li>Document the sound system in the
-      <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/index.html" shape="rect">
-      FreeBSD Architecture Handbook</a>
-
-      .</li></ol><hr /><h2><a name="The-Kernel-Stress-Test-Suite" href="#The-Kernel-Stress-Test-Suite" id="The-Kernel-Stress-Test-Suite">The Kernel Stress Test Suite</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~pho/stress/" title="http://people.freebsd.org/~pho/stress/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~pho/stress/" title="">http://people.freebsd.org/~pho/stress/</a></td></tr></table><p>
-	Contact:
-          Peter
-
-          Holm
-         &lt;<a href="mailto:pho@freebsd.org">pho@freebsd.org</a>&gt;
-	</p>
-      <p>The current version of the test suite took form in the beginning
-      of the year after discussions with Jeff Roberson, during a long
-      period of testing Jeff's VFS SMP work.</p>
-
-      <p>At that time, Daniel Seuffert donated a Thunder 7500
-      motherboard complete with CPUs, RAM and coolers.  This allowed me
-		to do some serious SMP testing.</p>
-
-      <p>Mid July Murray Stokely suggested adding a link from the 6.0
-      todo web page to the Stress Test Status Page. At that time there
-      were a few reoccurring panics that made it hard to test the kernel
-      for other problems. Numerous people put a lot of hard work in
-      fixing the panics and livelocks found during the next months. At
-      the same time others stepped in and ran the test suite on their own
-      hardware, thus increasing the focus on kernel stability.</p>
-
-      <p>As of 6.0, the kernel stress test suite cannot panic the
-      kernel.</p>
-    <hr /><br /><h1><a name="Network-infrastructure" href="#Network-infrastructure" id="Network-infrastructure">Network infrastructure</a></h1><br /><h2><a name="OpenBSD-dhclient-import" href="#OpenBSD-dhclient-import" id="OpenBSD-dhclient-import">OpenBSD dhclient import</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>The OpenBSD rewrite of dhclient has been imported, replacing the
-      ISC dhclient. The OpenBSD client provides better support for
-      roaming on wireless networks and a simpler model of operation.
-      Instead of a single dhclient process per system, there is one per
-      network interface. This instance automatically goes away in the
-      even of link loss and is restarted via devd when link is
-      reacquired. To support this change, many aspects of the network
-      interface configuration process were overhauled.</p>
-
-      <p>The current code works well in most circumstances, but more
-      testing and polishing is needed. A few bugs are being tracked, but
-      most of them are edge cases.</p>
-
-      <p>Work on further interface configuration enhancements is underway
-      for FreeBSD 7.0.</p>
-    <hr /><h2><a name="Removable-interface-improvements" href="#Removable-interface-improvements" id="Removable-interface-improvements">Removable interface improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" title="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/" title="">http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/</a></td></tr><tr><td><a href="http://www.freebsd.org/projects/dingo/" title="http://www.freebsd.org/projects/dingo/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/dingo/" title="">http://www.freebsd.org/projects/dingo/</a></td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is an attempt to clean up handling of network
-      interfaces in order to allow interfaces to be removed reliably.
-      Current problems include panics if Dummynet is delaying packets to
-      an interface when it is removed.</p>
-
-      <p>I have removed struct ifnet's and layer two common structures
-      from device driver structures. This will eventually allow them to
-      be managed properly upon device removal. This code has been
-      committed and will appear in 6.0. Popular drivers continue to
-      be fixed. jhb's locking work has identified and corrected many
-      issues. rwatson has also committed cleanups to the multicast code
-      which fixed some issues in this area.</p>
-    <hr /><h2><a name="TCP-&amp;-IP-Routing-Optimization-Fundraise" href="#TCP-&amp;-IP-Routing-Optimization-Fundraise" id="TCP-&amp;-IP-Routing-Optimization-Fundraise">TCP &amp; IP Routing Optimization Fundraise</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="http://people.freebsd.org/~andre/tcpoptimization.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="">http://people.freebsd.org/~andre/tcpoptimization.html</a></td></tr><tr><td><a href="http://www.freebsd.org/news/status/report-mar-2005-june-2005.html#Fundraising---TCP-&amp;-IP-Routing-Optimization" title="http://www.freebsd.org/news/status/report-mar-2005-june-2005.html#Fundraising---TCP-&amp;-IP-Routing-Optimization"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/news/status/report-mar-2005-june-2005.html#Fundraising---TCP-&amp;-IP-Routing-Optimization" title="">http://www.freebsd.org/news/status/report-mar-2005-june-2005.html#Fundraising---TCP-&amp;-IP-Routing-Optimization</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>The fundraise has been very successful and I want to thank
-      everyone who has pledged their support and tipped the jar. The full
-      amount plus a little bit more has been raised in a very short
-      timeframe. More information on the exact amounts and their sponsors
-      can be found at the first link.</p>
-
-      <p>Due to the extended (and unexpected long) code freeze for the
-      release process of FreeBSD 6.0 (which is very high quality btw.)
-      I've decided to push back on working full time until the freeze is
-      lifted. So far I've done some work in the mbuf handling area and
-      some other netinet cleanups in my local repository.</p>
-
-      <p>Once FreeBSD 6.0 is released I resume my work on this project
-      and many changes and optimizations, as described in the first and
-      second link, will go into into FreeBSD-current.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Porting-FreeBSD-to-the-Xbox" href="#Porting-FreeBSD-to-the-Xbox" id="Porting-FreeBSD-to-the-Xbox">Porting FreeBSD to the Xbox</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.xbox-bsd.nl" title="http://www.xbox-bsd.nl"></a></td><td>
-	    URL: <a href="http://www.xbox-bsd.nl" title="">http://www.xbox-bsd.nl</a></td></tr></table><p>
-	Contact:
-          Rink
-
-          Springer
-         &lt;<a href="mailto:rink@rink.nu">rink@rink.nu</a>&gt;
-	<br />
-	Contact:
-          Ed
-
-          Schouten
-         &lt;<a href="mailto:ed@fxq.nl">ed@fxq.nl</a>&gt;
-	</p>
-      <p>As of 26th July 2005, it is possible to run FreeBSD on your Xbox
-      with minor patching effort. The framebuffer has initial support;
-      The USB ports, IDE- and audio controllers are fully supported; the
-      only part severely lacking now is the lack of support for the
-      NForce Ethernet controller.</p>
-
-      <p>Currently, efforts are focussing on eliminating the XBOX kernel
-      option and make the port self-detecting; this means the x86 and
-      xbox kernels will be identical. The goal is to provide native xbox
-      support in 7-CURRENT.</p>
-
-      <p>Furthermore, a porting effort is planned from Linux' GPL-ed
-      forcedeth.c; not only the Xbox port will benefit from this but also
-      all NForce motherboard owners. The resulting driver could be
-      kldload-ed to keep the kernel GPL-free.</p>
-    <h3>Open tasks:</h3><ol><li>The xbox framebuffer driver should be merged in the VESA
-      framework, so it can use syscons(4). Assistance on this would be
-      very welcome!</li></ol><hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/platforms/ppc.html" title="http://www.freebsd.org/platforms/ppc.html">FreeBSD/PPC Platform page.</a></td><td>
-	    URL: <a href="http://www.freebsd.org/platforms/ppc.html" title="FreeBSD/PPC Platform page.">http://www.freebsd.org/platforms/ppc.html</a></td></tr></table><p>
-	Contact:
-          Peter
-
-          Grehan
-         &lt;<a href="mailto:grehan@freebsd.org">grehan@freebsd.org</a>&gt;
-	</p>
-      <p>The project has been following the 6.0 release schedule by
-      producing BETA-* builds and is now up to the RC1 build.</p>
-
-      <p>Dario Freni successfully built a FreeSBIE/ppc iso for his
-      Summer-of-code project.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-GNOME-Project" href="#FreeBSD-GNOME-Project" id="FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project Homepage</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project Homepage">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-          Joe Marcus
-
-          Clarke
-         &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeBSD GNOME
-
-          Team
-         &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since our last status report, we have added a new member to the
-      team: Jean-Yves Lefort (jylefort). We have even spiced up our
-      <a href="http://www.FreeBSD.org/gnome/contact.html" shape="rect">contact
-      page</a>
-
-      with pictures of ourselves and in some cases, a cute hippo. And our
-      very own Adam Weinberger (adamw) has been made a GNOME Project
-      committer heading up the Canadian English translation project.</p>
-
-      <p>We have finished the port GNOME 2.12 to FreeBSD. However, due to
-      the ports slush in preparation for 6.0-RELEASE, the update has not
-      been merged into the official ports tree. If people are eager to
-      try out GNOME 2.12 while waiting for the ports tree to fully thaw,
-      we have
-      <a href="http://www.FreeBSD.org/gnome/docs/develfaq.html" shape="rect">
-      instructions</a>
-
-      on our website. GNOME 2.12 will be the first FreeBSD GNOME release
-      <em>not</em>
-
-      to include support for FreeBSD 4.X. While 4.X is still a very
-      viable release for servers, it lacks many of the features needed
-      for a Desktop Environment such as GNOME. We do plan to continue
-      support of the GNOME development platform on 4.X, however. This
-      includes Glib, GTK+, libgnome, etc. A new porting component will be
-      introduced with GNOME 2.12 called, ``ltverhack''. This will help
-      with future upgrades by keeping shared library versions from
-      needlessly changing.</p>
-
-      <p>The FreeBSD GNOME Project is also committed to providing our
-      users with a solid package experience. To that end, we have
-      extended our
-      <a href="http://www.freebsd.org/gnome/docs/faq2.html#q21" shape="rect">
-      Tinderbox</a>
-
-      to build amd64 packages for all supported versions of FreeBSD for
-      both the production and development releases of the GNOME Desktop.
-      The development packages are even built with debugging symbols to
-      better help with reporting problems.</p>
-    <h3>Open tasks:</h3><ol><li>FreeBSD needs a
-      <a href="http://www.freedesktop.org/wiki/Software_2fhal" shape="rect">HAL</a>
-
-      port. HAL will be vital for both GNOME and KDE in providing FreeBSD
-      users with a smooth, elegant desktop experience. Once GNOME 2.12
-      has been merged into the ports tree, work will begin on making HAL
-      on FreeBSD a reality. Contact
-      <a href="mailto:gnome@FreeBSD.org" shape="rect">gnome@FreeBSD.org</a>
-
-      if you are interested in helping.</li><li>We need help with project documentation. In particular, we
-      need help auditing the
-      <a href="http://www.FreeBSD.org/gnome/docs/faq.html" shape="rect">FAQ</a>
-
-      to make sure the content is still relevant, and we are not missing
-      any key items. If you're interested, please contact
-      <a href="mailto:gnome@FreeBSD.org" shape="rect">gnome@FreeBSD.org</a>
-
-      .</li></ol><hr /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freshports.org/" title="http://www.freshports.org/">FreshPorts</a></td><td>
-	    URL: <a href="http://www.freshports.org/" title="FreshPorts">http://www.freshports.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>I'm in the process of adding personalized newsfeeds to the
-      website. For each of your Watch Lists, you will also have a news
-      feed just for that watch list. Any commit to any port in your watch
-      list will turn up on your newsfeed. This fantastic new feature is
-      available now for your RSS pleasure at
-      <a href="http://beta.freshports.org/" shape="rect">the BETA site</a>
-
-      . I've also been doing some work in the area of supporting multiple
-      platforms and architectures. This will allow FreshPorts to
-      correctly report that a port is broken, for example, on i386, but
-      not the other platforms. This feature will take note of BROKEN,
-      FORBIDDEN, and IGNORE for the following architectures:
-      <ul>
-        <li>alpha</li>
-
-        <li>amd64</li>
-
-        <li>i386</li>
-
-        <li>ia64</li>
-
-        <li>sparc64</li>
-      </ul>
-
-      And the following OSVERSIONS (subject to upgrade as new releases
-      come along):
-      <ul>
-        <li>492100</li>
-
-        <li>504102</li>
-
-        <li>600033</li>
-
-        <li>700001</li>
-      </ul>
-
-      Upcoming changes, in addition to the above, include:
-      <ol>
-        <li>NOT_FOR_ARCHS</li>
-
-        <li>ONLY_FOR_ARCHS</li>
-
-        <li>IS_INTERACTIVE</li>
-      </ol>
-
-      I've been getting useful help from those on IRC. Thanks.</p>
-    <h3>Open tasks:</h3><ol><li>Complete the above.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD ports collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD ports collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://edwin.adsl.barnet.com.au/~edwin/ports/" title="http://edwin.adsl.barnet.com.au/~edwin/ports/">FreeBSD ports updated distfile survey (Edwin Groothius' report)</a></td><td>
-	    URL: <a href="http://edwin.adsl.barnet.com.au/~edwin/ports/" title="FreeBSD ports updated distfile survey (Edwin Groothius' report)">http://edwin.adsl.barnet.com.au/~edwin/ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>A great deal of work has gone into the Ports Collection since
-      the last report in April, much of it behind-the-scenes.</p>
-
-      <p>As this report was being written, the 6.0 release was ongoing.
-      Due to the amount of time that it has taken to get 6.0 through the
-      beta process and into RC, we have been in ports freeze or slush for
-      more than two months. Unfortunately this has held back needed work
-      on the ports infrastructure.</p>
-
-      <p>The last major update to bsd.port.mk, in early May, was
-      coordinated by Kirill Ponomarew added a number of new features and
-      closed 15 PRs. Another similar set of changes has been tested and
-      is ready for commit after release.</p>
-
-      <p>portmgr welcomed two new members to its team: Erwin Lansing (who
-      had previously served as secretary, a role in which he is
-      continuing) and Clement Laforet. Clement is interested in speeding
-      up the adoption of new changes into the infrastructure, an item I'm
-      sure that that everyone can support. He promises to bring some
-      fresh ideas to bear on this, including the revitalization of
-      devel/portmk as a testing ground for new changes to bsd.port.mk in
-      which the larger community can help test changes.</p>
-
-      <p>The unfetchable distfile survey, which had been non-functional
-      for quite some time, was revitalized by Bill Fenner, with many new
-      pages of analysis added to it. Work is still ongoing. As a result
-      of this analysis, Bill and Mark Linimon eliminated nearly 100 lines
-      of bogus or outdated sites from bsd.sites.mk alone. They are
-      continuing to work through many other sites and ports as successive
-      iterations of the survey reveal more dimensions to the problem. We
-      still need more help from the larger community (see below).</p>
-
-      <p>Edwin Groothius has instituted a similar but slightly different
-      survey. His program attempts to visit each listed mastersite for
-      each distfile and determine whether or not a newer version might be
-      available. The results are stored in a database. This is helping to
-      automate a function that had been left up to individual maintainers
-      to look through numerous websites to try to find these updates. The
-      survey has been hugely (if not universally) popular. Already,
-      dozens of port updates have been committed as a direct result of
-      this service.</p>
-
-      <p>In addition, portsmon, which had been down due to a machine
-      change, was moved to portsmon.FreeBSD.org and updated during this
-      time. Many thanks to Erwin Lansing for providing the loan of this
-      machine, and Will Andrews for having provided the loan of the
-      previous incarnation.</p>
-
-      <p>Both of the above surveys are now generating periodic email to
-      ports maintainers advising them of problems. This is in addition to
-      recurring email from portsmon. The surveys allow individual
-      maintainers to ask to receive no further email. portsmon does not
-      currently have this but it needs to be added. Although we have no
-      doubt the mail can in some cases be annoying (especially given the
-      fact that there will inevitably be some false positives), the fact
-      is that these emails have had a direct impact on the quality on the
-      ports. We ask for patience from the community while each of us
-      continues to fine-tune the algorithms controlling what email is
-      generated. (Because of the number of emails these systems generate,
-      it is impossible to go over every one individually for a sanity
-      check).</p>
-
-      <p>As a result of bounces from the above email, we have also been
-      resetting maintainers who have become unreachable.</p>
-
-      <p>Pav Lucistnik has done a great deal of work on the Porter's
-      Handbook, including some much needed reshuffling and cleanup.
-      Expanded sections include Apache and PHP; Configure Scripts;
-      Dealing With Shared Libraries; Dealing With User Configuration
-      Files; Handling Empty Directories; Python; and Ruby. In addition,
-      Edwin Groothius has contributed a section on OPTIONS, and numerous
-      other sections have been improved by good suggestions from various
-      other contributors.</p>
-
-      <p>A new article, "Maintaining and contributing to the FreeBSD
-      Ports Collection", has been prepared by Sam Lawrance and has been
-      reviewed and is ready for commit. This document attempts to codify
-      the rights and responsibilities of ports maintainers, which until
-      now had merely been "community lore" as discussed on various
-      mailing lists.</p>
-
-      <p>We continue to add new committers regularly, 8 since the last
-      report.</p>
-
-      <p>The ports collection now contains over 13,500 ports. This is an
-      increase of over 750 since the last report in April.</p>
-    <h3>Open tasks:</h3><ol><li>portmgr would like to ask maintainers and committers alike to
-      go through the status of their ports on the two distfile surveys,
-      both the one that shows unfetchable current distfiles and the one
-      that shows possibly updated distfiles. This is an effective way to
-      quickly help improve our user's perception of the state of the
-      ports.</li><li>A great deal of progress has been made in cracking down on
-      ports that install files outside the approved directories and/or do
-      not deinstall cleanly (see "Extra files not listed in PLIST" on
-      <a href="http://pointyhat.freebsd.org/errorlogs/" shape="rect">pointyhat</a>
-
-      ). These ports are now a small minority thanks to the dedicated
-      efforts of a large number of individuals.</li><li>We still have a large number of PRs that have been assigned
-      to committers for some time (in fact, they constitute the
-      majority). portmgr members are now going through this list and
-      asking each committer to either commit them or release them to the
-      general pool so that someone else may work on them. In addition,
-      the existing policies for inactive maintainers (two weeks for
-      maintainer- timeout on PRs; three months for maintainer reset if no
-      activity) are going to be much more actively pursued than in the
-      past, where the policies were more honored in the breach than in
-      the observance. The goal is to try to bring the Ports Collection as
-      up-to-date as possible. (While there has been progress on many
-      fronts, there are still areas where ports are suffering from
-      bit-rot.)</li></ol><hr /><h2><a name="Ports-Tinderbox" href="#Ports-Tinderbox" id="Ports-Tinderbox">Ports Tinderbox</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">Tinderbox Homepage</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="Tinderbox Homepage">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Joe Marcus
-
-          Clarke
-         &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Tinderbox
-
-          List
-         &lt;<a href="mailto:tinderbox-list@marcuscom.com">tinderbox-list@marcuscom.com</a>&gt;
-	</p>
-      <p>The Ports Tinderbox is a packaged system for building FreeBSD
-      ports in a clean environment. It can be used to test new ports,
-      updates to existing ports, or simply as a package building engine.
-      Tinderbox uses the same underlying code that the official FreeBSD
-      package build cluster, pointyhat, uses. So if a port builds under
-      Tinderbox, it is guaranteed to build on pointyhat.</p>
-
-      <p>More and more FreeBSD committers and ports maintainers are
-      starting to use Tinderbox. We just released version 2.1.0 which
-      added much-requested PostgreSQL support as well as fixed many bugs.
-      We expect a 2.1.1 release soon with some additional bug fixes.</p>
-
-      <p>With the 2.1.0 release of Tinderbox, we have branched the code
-      base so that we can focus on larger features in our HEAD branch
-      while still producing stable releases on a more frequent basis. The
-      biggest new feature planned for Tinderbox 3.0 is clustering support
-      which is being spearheaded by Ade Lovett (ade).</p>
-    <h3>Open tasks:</h3><ol><li>At this point, we really need help with documentation. Work
-      has begun on creating man pages for the various Tinderbox commands,
-      but we need help to churn them out at as faster rate. If you have
-      strong mdoc fu, and interested in helping us out, please contact
-      <a href="mailto:marcus@marcuscom.com" shape="rect">marcus@marcuscom.com</a>
-
-      .</li></ol><hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="Cronyx/Asterisk" href="#Cronyx/Asterisk" id="Cronyx/Asterisk">Cronyx/Asterisk</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cronyx.ru/hardware/wan.html" title="http://www.cronyx.ru/hardware/wan.html">Cronyx WAN Adapters</a></td><td>
-	    URL: <a href="http://www.cronyx.ru/hardware/wan.html" title="Cronyx WAN Adapters">http://www.cronyx.ru/hardware/wan.html</a></td></tr><tr><td><a href="http://www.freebsd.org/~rik" title="http://www.freebsd.org/~rik">rik's Home Page</a></td><td>
-	    URL: <a href="http://www.freebsd.org/~rik" title="rik's Home Page">http://www.freebsd.org/~rik</a></td></tr></table><p>
-	Contact:
-          Roman
-
-          Kurakin
-         &lt;<a href="mailto:rik@FreeBSD.org">rik@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new netgraph-to-zaptel module that allows to use E1(ISDN PRI)
-      WAN adapters as an interface card for open source PBX - Asterisk.
-      All you need is an adapter that able to work in raw phone mode
-      (like Cronyx Tau-PCI/2E1), eq. without HDLC-like framing and that
-      has support of Netgraph.</p>
-    <hr /><h2><a name="OpenBSD-packet-filter---pf" href="#OpenBSD-packet-filter---pf" id="OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@freebsd.org">mlaier@freebsd.org</a>&gt;
-	</p>
-      <p>Further improvements have been made to pfsync to make it behave
-      well in SMP scenarios. All bug fixes have been MFCed to RELENG_5
-      where applicable. A couple of bugfixes and feature improvements
-      have been imported via OpenBSD (originally suggested by FreeBSD
-      users).</p>
-
-      <p>As described in the last report, FreeBSD 6.0 and future RELENG_6
-      releases will be based on OpenBSD 3.7. Newer code will be imported
-      as soon as 6.0 has settled down a bit.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan" href="#BSDCan" id="BSDCan">BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/" title="http://www.bsdcan.org/">BSDCan</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/" title="BSDCan">http://www.bsdcan.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>We are in the process of recruiting new members for the program
-      committee. If you would like to volunteer before you are recruited,
-      please contact me.</p>
-
-      <p>The dates for 2006 have been announced: May 12-13, 2006. The
-      venue will be the same as previous events: University of Ottawa.
-      The prices will not increase from 2005.</p>
-
-      <p>Please start thinking about your papers. The call for papers
-      will go out soon.</p>
-    <hr /><h2><a name="EuroBSDCon-2005---Basel" href="#EuroBSDCon-2005---Basel" id="EuroBSDCon-2005---Basel">EuroBSDCon 2005 - Basel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon.org/" title="http://www.eurobsdcon.org/"></a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org/" title="">http://www.eurobsdcon.org/</a></td></tr></table><p>
-	Contact:
-          Information
-         &lt;<a href="mailto:info@eurobsdcon.org">info@eurobsdcon.org</a>&gt;
-	</p>
-      <p>The fourth European BSD conference in Basel, Switzerland is a
-      great opportunity to present new ideas to the community and to meet
-      some of the developers behind the different BSDs.</p>
-
-      <p>The two day conference program (Nov 26 and 27) will be
-      complemented by a tutorial day preceding the conference (Nov
-      25).</p>
-
-      <p>The FreeBSD developers will hold a DevSummit on Nov 24 and 25,
-      so several developers will be at the conference.</p>
-
-      <p>The program is available for
-      <a href="http://www.eurobsdcon.org/conference-schedule-saturday.php" shape="rect">
-      Saturday</a>
-
-      and
-      <a href="http://www.eurobsdcon.org/conference-schedule-sunday.php" shape="rect">
-      Sunday</a>
-
-      providing very interesting FreeBSD talks and topics.</p>
-
-      <p>Today more than 160 people from 25 countries have registered for
-      the conference.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2005-10-2005-12.html b/website/content/en/status/report-2005-10-2005-12.html
deleted file mode 100644
index 9f90c4ab19..0000000000
--- a/website/content/en/status/report-2005-10-2005-12.html
+++ /dev/null
@@ -1,993 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report is about the rather quiet last quarter of 2005, with
-    the release of FreeBSD 6.0 and the holiday season things evolved in
-    the background. Nonetheless, most exciting projects hit the tree (or
-    are going to very soon).</p><p>Upcoming events, such as the release of FreeBSD 6.1/5.5 and the
-    third BSDCan conference with a big developer summit promise to
-    provide a busier start in 2006. The foundation for upcoming
-    development, however, are the projects that are described herein.</p><p>We hope that you find interesting projects to look at or work on.
-    The next status report collection will be April 7 2006. We are
-    looking forward to your report then.</p><p>Thanks again to everyone who submitted reports, and thanks to Brad
-    Davis who stepped up for an extensive spelling and grammar review.
-    Enjoy reading!</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeSBIE">FreeSBIE</a></li><li><a href="#jemalloc">jemalloc</a></li><li><a href="#variant-symlinks">variant symlinks</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-list-of-projects-and-ideas-for-volunteers-(TODO-list-for-volunteers)">FreeBSD list of projects and ideas for volunteers (TODO list
-    for volunteers)</a></li><li><a href="#Problem-Report-Database">Problem Report Database</a></li><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li></ul><h3><a href="#FreeBSD-team-reports">FreeBSD team reports</a></h3><ul><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Release-Engineering-Status-Report">Release Engineering Status Report</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite)">Bt878 Audio Driver (aka FusionHDTV 5 Lite)</a></li><li><a href="#E1000-driver-improvements">E1000 driver improvements</a></li><li><a href="#LSI-MegaRAID-improvements">LSI MegaRAID improvements</a></li><li><a href="#Sound-subsystem-improvements">Sound subsystem improvements</a></li></ul><h3><a href="#Network-infrastructure">Network infrastructure</a></h3><ul><li><a href="#Early-Binding-Updates-and-Credit-Based-Authorization-for-the-Kame-Shisa-Mobile-IPv6-Software">Early Binding Updates and Credit-Based Authorization for the
-    Kame-Shisa Mobile IPv6 Software</a></li><li><a href="#FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></li><li><a href="#KAME-Project-Status-Report">KAME Project Status Report</a></li><li><a href="#New-Networking-Features-in-FreeBSD-6.0">New Networking Features in FreeBSD 6.0</a></li><li><a href="#Optimizing-the-FreeBSD-IP-and-TCP-Stack">Optimizing the FreeBSD IP and TCP Stack</a></li></ul><h3><a href="#Userland-programs">Userland programs</a></h3><ul><li><a href="#OpenBSD-dhclient">OpenBSD dhclient</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Xen-3.0">FreeBSD on Xen 3.0</a></li><li><a href="#FreeBSD/xbox">FreeBSD/xbox</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreshPorts">FreshPorts</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#SysKonnect/Marvell-Yukon-device-driver">SysKonnect/Marvell Yukon device driver</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#A-Comprehensive-Delay-Analysis-for-Reactive-and-Proactive-Handoffs-with-Mobile-IPv6-Route-Optimization">A Comprehensive Delay Analysis for Reactive and Proactive
-    Handoffs with Mobile IPv6 Route Optimization</a></li><li><a href="#BSDCan-2006">BSDCan 2006</a></li><li><a href="#TCP/IP-Optimization-Fundraiser-Status">TCP/IP Optimization Fundraiser Status</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="FreeSBIE" href="#FreeSBIE" id="FreeSBIE">FreeSBIE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freesbie.org" title="http://www.freesbie.org"></a></td><td>
-	    URL: <a href="http://www.freesbie.org" title="">http://www.freesbie.org</a></td></tr><tr><td><a href="http://torrent.freesbie.org" title="http://torrent.freesbie.org"></a></td><td>
-	    URL: <a href="http://torrent.freesbie.org" title="">http://torrent.freesbie.org</a></td></tr><tr><td><a href="freesbie@gufi.org" title="freesbie@gufi.org"></a></td><td>
-	    URL: <a href="freesbie@gufi.org" title="">freesbie@gufi.org</a></td></tr></table><p>
-	Contact:
-          FreeSBIE
-
-          staff
-         &lt;<a href="mailto:staff@freesbie.org">staff@freesbie.org</a>&gt;
-	</p>
-      <p>Development is going on after the complete rewrite of the
-      toolkit. There are many plugins available and we're testing a new
-      implementation of unionfs for 6.x. Since it's a bit unstable, it
-      won't be included in the release anyway. Developers hope to enter
-      the BETA state on February 1st, to release an -RC image around
-      February 15th and the RELEASE around March 1st. We need more people
-      to test the images we provide. Torrents for them are available at
-      <a href="http://torrent.freesbie.org" shape="rect">torrent.freesbie.org</a>
-
-      .</p>
-    <h3>Open tasks:</h3><ol><li>A new BETA Release, based on 6-STABLE, is available for
-      testing.</li></ol><hr /><h2><a name="jemalloc" href="#jemalloc" id="jemalloc">jemalloc</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Jason
-
-          Evans
-         &lt;<a href="mailto:jasone@FreeBSD.org">jasone@FreeBSD.org</a>&gt;
-	</p>
-      <p>libc's malloc implementation has been replaced with an
-      implementation that is designed to scale well for multi-threaded
-      applications running on multi-processor systems. This is
-      accomplished by creating multiple allocation arenas that are
-      independent of each other, and permanently assigning threads to
-      these arenas. In the common case, threads do not access the same
-      allocator arena at the same time, which reduces contention and
-      cache sloshing.</p>
-
-      <p>Single-threaded application performance is approximately
-      equivalent to what it was with phkmalloc, but for multi-threaded
-      applications that make heavy use of malloc, the performance
-      difference can be huge (orders of magnitude).</p>
-
-      <p>As with phkmalloc, the new malloc implementation supports
-      runtime configuration via the MALLOC_OPTIONS environment variable.
-      See the malloc(3) manpage for details on supported options, as well
-      as more information about the allocator's architecture.</p>
-    <hr /><h2><a name="variant-symlinks" href="#variant-symlinks" id="variant-symlinks">variant symlinks</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://butcher.heavennet.ru/patches/kernel/varsym/" title="http://butcher.heavennet.ru/patches/kernel/varsym/"></a></td><td>
-	    URL: <a href="http://butcher.heavennet.ru/patches/kernel/varsym/" title="">http://butcher.heavennet.ru/patches/kernel/varsym/</a></td></tr></table><p>
-	Contact:
-          Andrey
-
-          Elsukov
-         &lt;<a href="mailto:bu7cher@yandex.ru">bu7cher@yandex.ru</a>&gt;
-	</p>
-      <p>The port of DragonFly's variant symlinks (
-      <a href="http://freebsd.org/projects/ideas/#p-magicsymlinks" shape="rect">
-      project ideas</a>
-
-      ) to FreeBSD. Variant symlinks is a dynamic symbolic link
-      implementation. Source file of a variant symlink may contain one or
-      more variable names. Each of these variable names is enclosed in
-      braces and preceded by a dollar sign in the style of variable
-      references in sh(1). Whenever a variant symlink is followed, each
-      variable found in source file is replaced by its associated value.
-      In this manner, a variant symlink may resolve to different paths
-      based on context.</p>
-    <h3>Open tasks:</h3><ol><li>Document a new system calls.</li><li>More testing.</li><li>Write the rc.d script for the variant symlinks
-      initialization.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="FreeBSD-list-of-projects-and-ideas-for-volunteers-(TODO-list-for-volunteers)" href="#FreeBSD-list-of-projects-and-ideas-for-volunteers-(TODO-list-for-volunteers)" id="FreeBSD-list-of-projects-and-ideas-for-volunteers-(TODO-list-for-volunteers)">FreeBSD list of projects and ideas for volunteers (TODO list
-    for volunteers)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/ideas/" title="http://www.FreeBSD.org/projects/ideas/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/ideas/" title="">http://www.FreeBSD.org/projects/ideas/</a></td></tr></table><p>
-	Contact:
-          Joel
-
-          Dahl
-         &lt;<a href="mailto:joel@FreeBSD.org">joel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The "TODO list for volunteers" is now committed as the "FreeBSD
-      list of projects and ideas for volunteers". So far the interest in
-      the list is high and some volunteers already took the opportunity
-      to start tackling some of the entries.</p>
-
-      <p>Unfortunately the FreeBSD project does not have enough human
-      resources to provide a technical contact for every entry.
-      Interested volunteers should not be afraid to try to come up with a
-      solution for an entry without a technical contact. The people on
-      the hackers and current mailing list are typically very helpful
-      regarding answering specific questions (as long as they know the
-      answer...).</p>
-
-      <p>We are looking forward to hear about new ideas, people willing
-      to be technical contacts for generic topics (e.g. USB) or specific
-      entries (already existing or newly created), suggestions for
-      existing entries or completion reports for (parts of) an entry.</p>
-    <h3>Open tasks:</h3><ol><li>Add more ideas.</li><li>Find more technical contacts.</li></ol><hr /><h2><a name="Problem-Report-Database" href="#Problem-Report-Database" id="Problem-Report-Database">Problem Report Database</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/support.html#gnats" title="http://www.freebsd.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.freebsd.org/support.html#gnats" title="GNATS">http://www.freebsd.org/support.html#gnats</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister_at_freebsd_dot_org">bugmeister_at_freebsd_dot_org</a>&gt;
-	</p>
-      <p>The experiment to add 'tags' to many of the kern and related
-      PRs, including such things as '[nfs]', '[fxp]', and so forth,
-      continues. In addition, PRs with patches have been more
-      consistently tagged with '[patch]'. Two new periodic reports based
-      on both functional tags and PRs with patches have been added, with
-      the goal of making these PRs more visible.</p>
-    <hr /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/doc/nl/books/handbook" title="http://www.freebsd.org/doc/nl/books/handbook">FreeBSD released handbook</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/nl/books/handbook" title="FreeBSD released handbook">http://www.freebsd.org/doc/nl/books/handbook</a></td></tr><tr><td><a href="http://www.freebsd-nl.org/doc/nl" title="http://www.freebsd-nl.org/doc/nl">Preview documentation</a></td><td>
-	    URL: <a href="http://www.freebsd-nl.org/doc/nl" title="Preview documentation">http://www.freebsd-nl.org/doc/nl</a></td></tr><tr><td><a href="http://www.freebsd-nl.org/www/nl/" title="http://www.freebsd-nl.org/www/nl/">Preview website</a></td><td>
-	    URL: <a href="http://www.freebsd-nl.org/www/nl/" title="Preview website">http://www.freebsd-nl.org/www/nl/</a></td></tr></table><p>
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Siebrand
-
-          Mazeland
-         &lt;<a href="mailto:s.mazeland@xs4all.nl">s.mazeland@xs4all.nl</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation Project is an ongoing project,
-      focussed on translating the English documentation and website to
-      the Dutch language. Currently we are almost done with the FreeBSD
-      Handbook and started the initial translation of the FreeBSD
-      Website. We are always looking for people to help out, if you can
-      help, please contact Siebrand or me so that we can divide the work
-      amongst us.</p>
-
-      <p>Recent publications:
-      <br clear="none" />
-
-      Recently the Printing and the Serial Communications chapters were
-      added to the FreeBSD Dutch Handbook.</p>
-
-      <p>Recently started items:
-      <br clear="none" />
-
-      We started with the translation of the PPP and SLIP chapter and the
-      translation of the website.</p>
-    <h3>Open tasks:</h3><ol><li>Translate the final parts of the FreeBSD handbook.</li><li>Translate the FreeBSD Website</li></ol><hr /><br /><h1><a name="FreeBSD-team-reports" href="#FreeBSD-team-reports" id="FreeBSD-team-reports">FreeBSD team reports</a></h1><br /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>This report covers the period July 2005 - January 2006, since
-      the FreeBSD Security Team did not submit a status report for July -
-      October 2005.</p>
-
-      <p>In August 2005, the long-time Security Officer, Jacques Vidrine,
-      stepped down and was replaced by Colin Percival. Jacques remains
-      with the team as Security Officer Emeritus, and the team thanks him
-      for all his work over the past four years.</p>
-
-      <p>Also in August 2005, Dag-Erling C. Sm�rgrav was replaced by
-      Simon L. Nielsen as Deputy Security Officer. In addition, Tom
-      Rhodes and Guido van Rooij retired from the team in September 2005
-      and January 2006 respectively in order to devote their time to
-      other parts of the FreeBSD project. The current Security Team
-      membership is published on the web site.</p>
-
-      <p>In the time since the last status report, ten security
-      advisories have been issued (five in 2005, five in 2006) concerning
-      problems in the base system of FreeBSD; of these, four problems
-      were in "contributed" code, while six were in code maintained
-      within FreeBSD. The Vulnerabilities and Exposures Markup Language
-      (VuXML) document has continued to be updated by the Security Team
-      and the Ports Committers documenting new vulnerabilities in the
-      FreeBSD Ports Collection; since the last status report, 117 new
-      entries have been added, bringing the total up to 636.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 4.10, FreeBSD 4.11, FreeBSD 5.3, FreeBSD
-      5.4, and FreeBSD 6.0. Their respective End of Life dates are listed
-      on the web site.</p>
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD ports collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD ports collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://edwin.adsl.barnet.com.au/~edwin/ports/" title="http://edwin.adsl.barnet.com.au/~edwin/ports/">FreeBSD ports updated distfile survey (Edwin Groothius' report)</a></td><td>
-	    URL: <a href="http://edwin.adsl.barnet.com.au/~edwin/ports/" title="FreeBSD ports updated distfile survey (Edwin Groothius' report)">http://edwin.adsl.barnet.com.au/~edwin/ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>During this time, the number of ports PRs briefly dipped below
-      500 -- a number not seen since late 2000, when there were 4000
-      ports instead of our new total of over 14,000 ports. This is due to
-      the hard work of a large number of individuals, including pav,
-      edwin, mnag, garga, and many others. Congratulations folks! Some of
-      this was due to more aggressively committing PRs where the
-      maintainer had not responded within the timeout period. Although
-      controversial, this new policy seems to be succeeding in its goal
-      of improving the Ports Collection.</p>
-
-      <p>A new file, ports/KNOBS, was added by ahze to help bring some
-      order in the chaos that had been the OPTIONS namespace.</p>
-
-      <p>dougb has changed the way that rc.d works in -HEAD to work more
-      like the base rc.d scripts. We are hoping that this change will
-      make ports maintenance easier in the future. However, in the
-      meantime a few bugs have been introduced (which we intend to have
-      fixed by the time 6.1 is released). While this regression is
-      unfortunate, it was decided that now was the best time to try to
-      make this change rather than waiting for 7.0. We hope our users can
-      be patient with us in the interim.</p>
-
-      <p>Work continues to improve the marcuscom ports tinderbox, with
-      new features added by marcus, aDe, and edwin in particular. Several
-      ports committers are now running their own copies to test ports
-      changes.</p>
-
-      <p>The www.FreeBSD.org/ports page, and the portmgr web pages, were
-      reworked as well.</p>
-
-      <p>We have added 4 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>Progress has been made in cracking down on ports that do not
-      correctly install when LOCALBASE is not /usr/local, but some ports
-      remain.</li><li>portmgr would like to remind committers that PRs for their
-      ports should be handled (either committed or marked 'suspended' or
-      'analyzed') within the two week timeout period. In this way other
-      committers do not have to invoke the maintainer timeout and things
-      will work more smoothly.</li></ol><hr /><h2><a name="Release-Engineering-Status-Report" href="#Release-Engineering-Status-Report" id="Release-Engineering-Status-Report">Release Engineering Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/releng" title="http://www.freebsd.org/releng"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releng" title="">http://www.freebsd.org/releng</a></td></tr><tr><td><a href="http://www.freebsd.org/releases" title="http://www.freebsd.org/releases"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releases" title="">http://www.freebsd.org/releases</a></td></tr></table><p>
-	Contact:
-          RE
-
-          Team
-         &lt;<a href="mailto:re@freebsd.org">re@freebsd.org</a>&gt;
-	</p>
-      <p>Another very busy year for the FreeBSD Release Engineering Team.
-      Recognizing the problems, both technical and emotional, surrounding
-      the FreeBSD 5.x releases, our primary focus was in getting the bugs
-      out of FreeBSD 6.0 and getting it released. We succeeded at that
-      quite well, and the 6.0 release on Nov 18 was a huge success for
-      the project. Many thanks to all of the developers who put in
-      countless hours fixing bugs and improving performance, and to the
-      users who helped find, fix, and verify bugs.</p>
-
-      <p>Moving forward to 2006, we plan on doing a joint release of
-      FreeBSD 5.5 and 6.1 in late March. The 5.5 release will mark the
-      end of active FreeBSD 5.x development and releases, and is intended
-      to help users who have not yet switched to FreeBSD 6. It consists
-      primarily of bug fixes and minor improvements. FreeBSD 6.1 will be
-      an upgrade to 6.0 and will include new drivers, better performance
-      in certain areas, as well as bug fixes. We expect to release
-      FreeBSD 6.2 and 6.3 later in 2006.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite)" href="#Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite)" id="Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite)">Bt878 Audio Driver (aka FusionHDTV 5 Lite)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21" title="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21">Perforce source repository</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21" title="Perforce source repository">http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21</a></td></tr></table><p>
-	Contact:
-          John-Mark
-
-          Gurney
-         &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>Basic audio capture is working. All of the parameters are set by
-      userland, while the RISC program generation is by kernel. No real
-      audio has been captured as there are no drivers for the tuner yet.
-      Someone with a real Bt878 NTSC card that is supported by bktr(4)
-      could use this to capture audio w/o using the sound card.</p>
-
-      <p>The real goal of this driver is to make HD capture possible with
-      the DViCO FusionHDTV5 Lite card that I have. I have some of the
-      documentation that I need, but I'm still missing two key docs. The
-      docs for the LGDT3303 ATSC/8VSB/QAM demodulator chip and a block
-      diagram of the board showing which GPIO lines go where and how the
-      chips are interconnected. DViCO has been responsive in
-      acknowledging my emails, but they have yet to produced any data
-      besides pointing me to the Linux driver (which is difficult to
-      figure out stuff by).</p>
-    <h3>Open tasks:</h3><ol><li>Complete basic capture driver.</li><li>Make the bktr(4) drive cleanly attach to the card, and
-      possibly add support for analog capture.</li></ol><hr /><h2><a name="E1000-driver-improvements" href="#E1000-driver-improvements" id="E1000-driver-improvements">E1000 driver improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@freebsd.org">scottl@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Andre
-
-          Opperman
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>In an effort to solve the 'interrupt aliasing' problem that
-      plagues many motherboards under FreeBSD, I modified the Intel e1000
-      network driver (if_em) to use a combination of fast interrupts and
-      taskqueues. This technique avoids interrupt threads entirely, which
-      in turn avoids triggering the aliasing problem in the Intel APIC.
-      The result is that the driver now handles and masks interrupts
-      immediately, and a private taskqueue is then scheduled to run to
-      process the link events and rx/tx events. A side effect of this
-      asynchronous processing is that it acts much as traditional polling
-      does, in that the amount of work done in the taskqueue can be
-      controlled, and the taskqueue rescheduled to process work at a
-      later time. This leads to the driver having the low-latency
-      benefits of interrupts and the workload segmentation of polling,
-      all without complicated heuristics. Several users have reported
-      that the driver can handle higher loads than traditional polling
-      without deadlocks.</p>
-
-      <p>Along with this work, I modified the SMPng locking in the driver
-      so that no lock is required for the RX path. Since this path is
-      already implicitly serialized by the interrupt and/or taskqueue
-      and/or polling handler (all of which are exclusive to each other),
-      there was no need for extra synchronization. This has two benefits.
-      The first is reduction in processing overhead to unlock and lock
-      the driver for every RX packet, and significant reduction in
-      contention of the driver lock when transmitting and receiving
-      packets at the same time. I believe that it is further possible to
-      run the TX-complete path without a lock, further reducing overhead
-      and contention for high transmit loads. The reduced contention also
-      greatly benefited the fast-forward bridging code in FreeBSD, with
-      up to 25% performance improvement seen, as well as lower CPU
-      utilization.</p>
-
-      <p>The work can be found in FreeBSD 7-CURRENT for now. There are
-      still some rough edges relating to falling back to traditional
-      ithread and polling behavior, and I do not intend to merge the
-      changes back to FreeBSD 6.x until these are resolved. I also hope
-      to extend the INTR_FAST+taskqueue model into a general framework
-      for doing Mac OSX style filter interrupts. The work in the if_em
-      driver can also be extended to other high-performance network
-      drivers such as if_bge and if_ti. Any help with investigating these
-      topics is welcomed.</p>
-    <hr /><h2><a name="LSI-MegaRAID-improvements" href="#LSI-MegaRAID-improvements" id="LSI-MegaRAID-improvements">LSI MegaRAID improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@freebsd.org">scottl@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Doug
-
-          Ambrisko
-         &lt;<a href="mailto:ambrisko@freebsd.org">ambrisko@freebsd.org</a>&gt;
-	</p>
-      <p>Major work has gone into improving both the performance of the
-      LSI MegaRAID (amr) driver, and in adding Linux compatibility
-      support. SMPng locking was added in Oct 2005 as well as a number of
-      performance improvements. The result is 138% performance
-      improvement in some local transaction tests.</p>
-
-      <p>Throughout 2005 a lot of work has gone into adding Linux
-      compatibility to the driver. It is now possible to run many of the
-      LSI-provided management apps for Linux under FreeBSD. Both this
-      feature and the performance improvements are in the 7-CURRENT
-      development branch of FreeBSD and are scheduled to be backported in
-      time for the FreeBSD 6.1 release.</p>
-    <hr /><h2><a name="Sound-subsystem-improvements" href="#Sound-subsystem-improvements" id="Sound-subsystem-improvements">Sound subsystem improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~ariff/" title="http://people.FreeBSD.org/~ariff/">Patches for RELENG_5.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~ariff/" title="Patches for RELENG_5.">http://people.FreeBSD.org/~ariff/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/projects/ideas/" title="http://www.FreeBSD.org/projects/ideas/">The FreeBSD Project Ideas List.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/ideas/" title="The FreeBSD Project Ideas List.">http://www.FreeBSD.org/projects/ideas/</a></td></tr></table><p>
-	Contact:
-          Ariff
-
-          Abdullah
-         &lt;<a href="mailto:ariff@FreeBSD.org">ariff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Multimedia
-
-          Mailinglist
-         &lt;<a href="mailto:multimedia@FreeBSD.org">multimedia@FreeBSD.org</a>&gt;
-	</p>
-      <p>A lot of changes have taken place in the sound system since the
-      last status report. They range from less hiccups and distortion by
-      disk accesses and/or driver bugs to new and improved features
-      (software volume control implemented for soundcards which do not
-      have hardware volume control). Additionally a new driver
-      (snd_atiixp) has seen the light and a lot of problem reports were
-      fixed.</p>
-
-      <p>Most of those changes and the changes mentioned in the previous
-      status report are already merged to RELENG_6 and will be part of
-      6.1-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>Have a look at the sound related entries on the ideas
-      list.</li><li>Rewrite some parts (e.g. a new mixer subsystem with OSS
-      compatibility).</li><li>sndctl(1): tool to control non-mixer parts of the sound
-      system (e.g. spdif switching, virtual-3D effects) by an user
-      (instead of the sysctl approach in -current); pcmplay(1),
-      pcmrec(1), pcmutil(1).</li><li>Plugable FEEDER infrastructure. For ease of debugging various
-      feeder stuff and/or as userland library and test suite.</li><li>Support for new hardware (envy24, Intel HDA).</li><li>Performance enhancement (via 'slave'-channels).</li><li>Closer compatibility with OSS, especially for the upcoming
-      OSS v4.</li></ol><hr /><br /><h1><a name="Network-infrastructure" href="#Network-infrastructure" id="Network-infrastructure">Network infrastructure</a></h1><br /><h2><a name="Early-Binding-Updates-and-Credit-Based-Authorization-for-the-Kame-Shisa-Mobile-IPv6-Software" href="#Early-Binding-Updates-and-Credit-Based-Authorization-for-the-Kame-Shisa-Mobile-IPv6-Software" id="Early-Binding-Updates-and-Credit-Based-Authorization-for-the-Kame-Shisa-Mobile-IPv6-Software">Early Binding Updates and Credit-Based Authorization for the
-    Kame-Shisa Mobile IPv6 Software</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.tm.uka.de/~chvogt/ebucba/" title="http://www.tm.uka.de/~chvogt/ebucba/">Download patch here.</a></td><td>
-	    URL: <a href="http://www.tm.uka.de/~chvogt/ebucba/" title="Download patch here.">http://www.tm.uka.de/~chvogt/ebucba/</a></td></tr><tr><td><a href="http://doc.tm.uka.de/2005/draft-vogt-mobopts-early-binding-updates-00.txt" title="http://doc.tm.uka.de/2005/draft-vogt-mobopts-early-binding-updates-00.txt">[1]</a></td><td>
-	    URL: <a href="http://doc.tm.uka.de/2005/draft-vogt-mobopts-early-binding-updates-00.txt" title="[1]">http://doc.tm.uka.de/2005/draft-vogt-mobopts-early-binding-updates-00.txt</a></td></tr><tr><td><a href="http://doc.tm.uka.de/2005/draft-vogt-mobopts-credit-based-authorization-00.txt" title="http://doc.tm.uka.de/2005/draft-vogt-mobopts-credit-based-authorization-00.txt">[2]</a></td><td>
-	    URL: <a href="http://doc.tm.uka.de/2005/draft-vogt-mobopts-credit-based-authorization-00.txt" title="[2]">http://doc.tm.uka.de/2005/draft-vogt-mobopts-credit-based-authorization-00.txt</a></td></tr></table><p>
-	Contact:
-          Christian
-
-          Vogt
-         &lt;<a href="mailto:chvogt@tm.uka.de">chvogt@tm.uka.de</a>&gt;
-	</p>
-      <p>Based on the Kame-Shisa Mobile IPv6 Software for FreeBSD 5.4, we
-      implemented the performance optimization "Early Binding Updates"
-      and "Credit-Based Authorization". The combined optimizations
-      facilitate significant reductions in handoff delay without
-      compromising protocol security [1][2].</p>
-    <hr /><h2><a name="FAST_IPSEC-Upgrade" href="#FAST_IPSEC-Upgrade" id="FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>&gt;
-	</p>
-      <p>Currently splitting out the rest of the PF_KEY data-structures
-      from the key database. This will mean the user level applications
-      and the kernel will not share datastructures and that they can,
-      hopefully, advance on their own without being in lockstep.</p>
-    <h3>Open tasks:</h3><ol><li>Calculate diffs between Kame IPv4 version of IPSec and
-      FAST_IPSEC and upgrade FAST to the latest standards.</li><li>Add IPv6 support to FAST_IPSEC.</li></ol><hr /><h2><a name="KAME-Project-Status-Report" href="#KAME-Project-Status-Report" id="KAME-Project-Status-Report">KAME Project Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.kame.net/" title="http://www.kame.net/">KAME Project Homepage</a></td><td>
-	    URL: <a href="http://www.kame.net/" title="KAME Project Homepage">http://www.kame.net/</a></td></tr><tr><td><a href="http://www.kame.net/newsletter/20051107/" title="http://www.kame.net/newsletter/20051107/"></a></td><td>
-	    URL: <a href="http://www.kame.net/newsletter/20051107/" title="">http://www.kame.net/newsletter/20051107/</a></td></tr><tr><td><a href="http://www.wide.ad.jp/news/press/20051107-KAME-e.html" title="http://www.wide.ad.jp/news/press/20051107-KAME-e.html"></a></td><td>
-	    URL: <a href="http://www.wide.ad.jp/news/press/20051107-KAME-e.html" title="">http://www.wide.ad.jp/news/press/20051107-KAME-e.html</a></td></tr><tr><td><a href="http://ipv6style.jp/en/special/kame/20051205/index.shtml" title="http://ipv6style.jp/en/special/kame/20051205/index.shtml"></a></td><td>
-	    URL: <a href="http://ipv6style.jp/en/special/kame/20051205/index.shtml" title="">http://ipv6style.jp/en/special/kame/20051205/index.shtml</a></td></tr></table><p>
-	Contact:
-          SUZUKI
-
-          Shinsuke
-         &lt;<a href="mailto:suz@FreeBSD.org">suz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most of the latest KAME code has been merged to 7-current and
-      6-stable, to prepare for the project conclusion in March 2006. For
-      the same reason, we moved some ports applications (security/racoon,
-      net/pim6sd, net/pim6dd, net/dhcp6) from KAME to
-      sourceforge.net.</p>
-
-      <p>Some of the items (e.g. IGMPv3/MLDv2, Mobile-IPv6/NEMO, SCTP,
-      DCCP, ISATAP) are not merged yet from the latest KAME code for
-      several reasons. Other projects will continue to merge their
-      work.</p>
-    <h3>Open tasks:</h3><ol><li>remove __P() macros</li><li>set net.inet6.ip6.kame_version to a more appropriate date
-      :-)</li><li>update src/sys/netinet6/README</li></ol><hr /><h2><a name="New-Networking-Features-in-FreeBSD-6.0" href="#New-Networking-Features-in-FreeBSD-6.0" id="New-Networking-Features-in-FreeBSD-6.0">New Networking Features in FreeBSD 6.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Presentation.pdf" title="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Presentation.pdf">Presentation</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Presentation.pdf" title="Presentation">http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Presentation.pdf</a></td></tr><tr><td><a href="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Paper.pdf" title="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Paper.pdf">Paper</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Paper.pdf" title="Paper">http://people.freebsd.org/~andre/New%20Networking%20Features%20in%20FreeBSD%206%20-%20Paper.pdf</a></td></tr><tr><td><a href="http://www.eurobsdcon.org" title="http://www.eurobsdcon.org">EuroBSDCon 05</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org" title="EuroBSDCon 05">http://www.eurobsdcon.org</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>FreeBSD 6 has evolved drastically in the development branch
-      since FreeBSD 5.3 and especially so in the network area. The
-      presentation and paper give an in-depth overview of all network
-      stack related enhancements, changes and new code with a narrative
-      on their rationale.</p>
-    <hr /><h2><a name="Optimizing-the-FreeBSD-IP-and-TCP-Stack" href="#Optimizing-the-FreeBSD-IP-and-TCP-Stack" id="Optimizing-the-FreeBSD-IP-and-TCP-Stack">Optimizing the FreeBSD IP and TCP Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Presentation.pdf" title="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Presentation.pdf">Presentation</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Presentation.pdf" title="Presentation">http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Presentation.pdf</a></td></tr><tr><td><a href="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Paper.pdf" title="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Paper.pdf">Paper</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Paper.pdf" title="Paper">http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TCP%20Stack%20-%20Paper.pdf</a></td></tr><tr><td><a href="http://www.eurobsdcon.org" title="http://www.eurobsdcon.org">EuroBSDCon 05</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org" title="EuroBSDCon 05">http://www.eurobsdcon.org</a></td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="http://people.freebsd.org/~andre/tcpoptimization.html">TCP/IP Optimization Fundraiser 2005</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="TCP/IP Optimization Fundraiser 2005">http://people.freebsd.org/~andre/tcpoptimization.html</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>FreeBSD has gained fine grained locking in the network stack
-      throughout the 5.x-RELEASE series cumulating in 6.0-RELEASE.
-      Hardware architecture and performance characteristics have evolved
-      significantly since various BSD networking subsystems have been
-      designed and implemented. This paper gives a detailed look into the
-      implementation and design changes in FreeBSD 7-CURRENT to extract
-      the maximum network performance from the underlying hardware.</p>
-
-      <p>Sponsored by: TCP/IP Optimization Fundraiser 2005</p>
-    <hr /><br /><h1><a name="Userland-programs" href="#Userland-programs" id="Userland-programs">Userland programs</a></h1><br /><h2><a name="OpenBSD-dhclient" href="#OpenBSD-dhclient" id="OpenBSD-dhclient">OpenBSD dhclient</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>The OpenBSD rewrite of dhclient has been imported, replacing the
-      ISC dhclient. The OpenBSD client provides better support for
-      roaming on wireless networks and a simpler model of operation.
-      Instead of a single dhclient process per system, there is one per
-      network interface. This instance automatically goes away in the
-      even of link loss and is restarted via devd when link is
-      reacquired. To support this change, many aspects of the network
-      interface configuration process were overhauled.</p>
-
-      <p>Support for adding aliases to DHCP configured interfaces has
-      been committed to CURRENT and will be merged before 6.1-RELEASE.
-      Soon work will begin to merge changes from OpenBSD that have taken
-      place since the initial import.</p>
-
-      <p>Work on further interface configuration enhancements is underway
-      for FreeBSD 7.0.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Xen-3.0" href="#FreeBSD-on-Xen-3.0" id="FreeBSD-on-Xen-3.0">FreeBSD on Xen 3.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fsmware.com/xenofreebsd/7.0/STATUS" title="http://www.fsmware.com/xenofreebsd/7.0/STATUS">current status</a></td><td>
-	    URL: <a href="http://www.fsmware.com/xenofreebsd/7.0/STATUS" title="current status">http://www.fsmware.com/xenofreebsd/7.0/STATUS</a></td></tr></table><p>
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kip.macy@gmail.com">kip.macy@gmail.com</a>&gt;
-	</p>
-      <p>Full domU support in p4 branch of -CURRENT, except suspend /
-      restore. Dom0 work is in progress. Scott Long is working on xenbus
-      integration with newbus. After newbus integration it will go into
-      CVS. I hope to see it MFCed to RELENG_6 so it will be available for
-      6.1.</p>
-    <h3>Open tasks:</h3><ol><li>Port the backend drivers from Linux.</li><li>Port the domain management tools from Linux.</li><li>Add multiboot support to loader(8) to support it booting
-      xen.</li><li>SMP, x86_64, and PAE support.</li></ol><hr /><h2><a name="FreeBSD/xbox" href="#FreeBSD/xbox" id="FreeBSD/xbox">FreeBSD/xbox</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://xbox-bsd.nl" title="http://xbox-bsd.nl">FreeBSD/xbox project page.</a></td><td>
-	    URL: <a href="http://xbox-bsd.nl" title="FreeBSD/xbox project page.">http://xbox-bsd.nl</a></td></tr></table><p>
-	Contact:
-          Rink
-
-          Springer
-         &lt;<a href="mailto:rink@FreeBSD.org">rink@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD/xbox support is nearing completion. Patches are
-      available for nve(4) ethernet support, as well as a
-      syscons(4)-capable console. I am working to integrate these in
-      CURRENT, a backport to 6.x is planned too.</p>
-
-      <p>Work is under way to support X.Org as well; people with more
-      detailed knowledge of X.Org are welcome to assist.</p>
-    <h3>Open tasks:</h3><ol><li>Enable framebuffer support in X.Org</li><li>Figure out a way to use mfsroots without using
-      loader(8)</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freshports.org/" title="http://www.freshports.org/"></a></td><td>
-	    URL: <a href="http://www.freshports.org/" title="">http://www.freshports.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>
-      <a href="http://www.freshports.org/" shape="rect">FreshPorts</a>
-
-      recently moved to a new webserver. This should speed things up
-      considerably.</p>
-
-      <p>You can read all about the new hardware on the recently
-      introduced
-      <a href="http://news.freshports.org/" shape="rect">FreshPorts Blog</a>
-
-      . This blog will include technical discussions about ports and the
-      problems they present with respect to FreshPorts. Site
-      announcements will be posted there. As bugs are found, they will be
-      listed, as well as their fixes.</p>
-
-      <p>Supporting multiple platforms and architectures is still in the
-      development stage. Lack of time is affecting progress.</p>
-
-      <p>A fix for virtual ports is in the works. I'm also going to
-      implement more caching to speed things up. If interested in
-      discussing the options there, please get involved in the blog.</p>
-    <hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="SysKonnect/Marvell-Yukon-device-driver" href="#SysKonnect/Marvell-Yukon-device-driver" id="SysKonnect/Marvell-Yukon-device-driver">SysKonnect/Marvell Yukon device driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.marvell.com" title="http://www.marvell.com"></a></td><td>
-	    URL: <a href="http://www.marvell.com" title="">http://www.marvell.com</a></td></tr><tr><td><a href="http://www.syskonnect.de" title="http://www.syskonnect.de"></a></td><td>
-	    URL: <a href="http://www.syskonnect.de" title="">http://www.syskonnect.de</a></td></tr></table><p>
-	Contact:
-          Karim
-
-          Jamal
-         &lt;<a href="mailto:support@syskonnect.de">support@syskonnect.de</a>&gt;
-	</p>
-      <p>This project provides support for SysKonnect's SK-98xx,
-      SK-95xx,SK-9Exx and SK-9Sxx PCI/PCI-Express Gigabit Ethernet
-      adapters via the yk(4) driver, as well as Marvell's Yukon LOM
-      Gigabit Ethernet controllers via the myk(4) driver. Driver source
-      has been made available to selected members of the FreeBSD
-      project.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="A-Comprehensive-Delay-Analysis-for-Reactive-and-Proactive-Handoffs-with-Mobile-IPv6-Route-Optimization" href="#A-Comprehensive-Delay-Analysis-for-Reactive-and-Proactive-Handoffs-with-Mobile-IPv6-Route-Optimization" id="A-Comprehensive-Delay-Analysis-for-Reactive-and-Proactive-Handoffs-with-Mobile-IPv6-Route-Optimization">A Comprehensive Delay Analysis for Reactive and Proactive
-    Handoffs with Mobile IPv6 Route Optimization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.tm.uka.de/2006/vogt-2006-delay-analysis-for-reactive-and-proactive-handoffs.pdf" title="http://doc.tm.uka.de/2006/vogt-2006-delay-analysis-for-reactive-and-proactive-handoffs.pdf">Download document here.</a></td><td>
-	    URL: <a href="http://doc.tm.uka.de/2006/vogt-2006-delay-analysis-for-reactive-and-proactive-handoffs.pdf" title="Download document here.">http://doc.tm.uka.de/2006/vogt-2006-delay-analysis-for-reactive-and-proactive-handoffs.pdf</a></td></tr></table><p>
-	Contact:
-          Christian
-
-          Vogt
-         &lt;<a href="mailto:chvogt@tm.uka.de">chvogt@tm.uka.de</a>&gt;
-	</p>
-      <p>Optimizations to reduce handoff delays inherent in Mobile IPv6
-      Route Optimization as well as IPv6 router discovery, address
-      configuration, and movement detection have so far been mostly
-      considered on an individual basis. This document evaluates three
-      integrated solutions for improved handoff experience in
-      surroundings with different preconditions: reactive handoffs with
-      unmodified routers, reactive handoffs with router support, and
-      movement anticipation and proactive handoff management.</p>
-    <hr /><h2><a name="BSDCan-2006" href="#BSDCan-2006" id="BSDCan-2006">BSDCan 2006</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/" title="http://www.bsdcan.org/"></a></td><td>
-	    URL: <a href="http://www.bsdcan.org/" title="">http://www.bsdcan.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>We are well into the process of selecting the talks for BSDCan
-      2006. Our new
-      <a href="http://www.bsdcan.org/2006/committee.php" shape="rect">program
-      committee</a>
-
-      has a hard selection task over the new few weeks. The deadline for
-      the
-      <a href="http://www.bsdcan.org/2006/papers.php" shape="rect">Call For Papers</a>
-
-      has passed, but it's not too late to submit a talk. Please see the
-      above URL for details. After the success of the
-      <a href="http://www.bsdcan.org/2005/activity.php?id=72" shape="rect">Work in
-      Progress last year</a>
-
-      , we are going to do it again this year. If you are working on
-      something you'd like to tell the world about, considering giving a
-      5 minute talk at BSDCan. The
-      <a href="http://www.bsdcan.org/2006/registration.php" shape="rect">registration
-      prices for BSDCan 2006</a>
-
-      will be the same as they were for
-      <a href="http://www.bsdcan.org/2005/registration.php" shape="rect">2005</a>
-
-      . We will be again in the SITE building at University of Ottawa and
-      you'll have lots of opportunity to meet with people from all over
-      the world. Be sure to make your travel plans now and don't miss out
-      on the biggest BSD event this year: BSDCan 2006.</p>
-    <h3>Open tasks:</h3><ol><li>We're looking for volunteers to help out just before and
-      during the conference. Contact Dan at the above address.</li><li>If you have a talk you'd like to present, contact Dan at the
-      above address.</li></ol><hr /><h2><a name="TCP/IP-Optimization-Fundraiser-Status" href="#TCP/IP-Optimization-Fundraiser-Status" id="TCP/IP-Optimization-Fundraiser-Status">TCP/IP Optimization Fundraiser Status</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="http://people.freebsd.org/~andre/tcpoptimization.html">TCP/IP Optimization Fundraiser 2005</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/tcpoptimization.html" title="TCP/IP Optimization Fundraiser 2005">http://people.freebsd.org/~andre/tcpoptimization.html</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/em/if_em.c?rev=1.98&amp;content-type=text/x-cvsweb-markup" title="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/em/if_em.c?rev=1.98&amp;content-type=text/x-cvsweb-markup">em(4) driver commit</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/em/if_em.c?rev=1.98&amp;content-type=text/x-cvsweb-markup" title="em(4) driver commit">http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/em/if_em.c?rev=1.98&amp;content-type=text/x-cvsweb-markup</a></td></tr><tr><td><a href="http://www.freebsd.org/news/status/report-july-2005-oct-2005.html#TCP-&amp;-IP-Routing-Optimization-Fundraise" title="http://www.freebsd.org/news/status/report-july-2005-oct-2005.html#TCP-&amp;-IP-Routing-Optimization-Fundraise">Previous Status Report</a></td><td>
-	    URL: <a href="http://www.freebsd.org/news/status/report-july-2005-oct-2005.html#TCP-&amp;-IP-Routing-Optimization-Fundraise" title="Previous Status Report">http://www.freebsd.org/news/status/report-july-2005-oct-2005.html#TCP-&amp;-IP-Routing-Optimization-Fundraise</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>The fundraiser has been very successful and I want to thank
-      everyone who has pledged their support and tipped the jar. The full
-      amount plus a little bit more has been raised in a very short
-      timeframe. More information on the exact amounts and their sponsors
-      can be found at the first link.</p>
-
-      <p>After the delays on this project caused by the FreeBSD 6.0
-      Release cycle code freeze work has picked up and a paper was
-      written and a presentation held on "Optimizing the FreeBSD IP and
-      TCP Stack" for EuroBSDCon 05 on November 27th. See related status
-      report under that title.</p>
-
-      <p>From December 21st to January 11th I received access to a
-      calibrated Agilent N2X gigabit tester and traffic generator. Stock
-      FreeBSD 7-current was tested and profiled extensively in this
-      timeframe. A first proof of concept optimization was developed in
-      cooperation with Scott Long. It involved converting the Intel
-      Gigabit ethernet em(4) driver to make use of fast interrupt
-      handlers, taskqueues and lockless RX ring handling. This improved
-      the performance from 570kpps to 750kpps, a 25% improvement, with IP
-      fastforwarding enabled.</p>
-    <h3>Open tasks:</h3><ol><li>A large number of profiles and measurements was taken and a
-      detailed report on the performance characteristics and remaining
-      bottlenecks is under preparation.</li><li>Further optimizations and new features described on the
-      Optimization Fundraiser page.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2006-01-2006-03.html b/website/content/en/status/report-2006-01-2006-03.html
deleted file mode 100644
index b033bea25b..0000000000
--- a/website/content/en/status/report-2006-01-2006-03.html
+++ /dev/null
@@ -1,1012 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The highlights of this quarters report certainly include the
-    availability of native Java binaries thanks to the
-    <a href="http://www.freebsdfoundation.org/" shape="rect">FreeBSD Foundation</a>
-
-    , as well as progress has been made with Xen support and Sun's
-    Ultrasparc T1. Furthermore we are looking forward to FreeBSD 6.1 and
-    TrustedBSD audit support has been imported into FreeBSD 7-CURRENT.
-    All in all, a very exiting start to 2006.</p><p>In just under a month the developers will be gathering at
-    <a href="http://www.bsdcan.org/2006/" shape="rect">BSDCan 2006</a>
-
-    for, FreeBSD Dev Summit, a two day meeting of FreeBSD developers.
-    Once again the
-    <a href="http://www.bsdcan.org/2006/schedule.php" shape="rect">BSDCan schedule</a>
-
-    is filled with many interesting talks.</p><p>We hope you enjoy reading and look forward to hear from you for
-    the next round. Consult the list of
-    <a href="http://www.freebsd.org/projects/ideas/" shape="rect">projects and
-    ideas</a>
-
-    for ways to get involved. The submission date for the second quarter
-    reports will be July, 7th 2006.</p><p>Thanks to everybody who submitted a report and to Brad Davis, who
-    joined the Status Report team, for proof reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BSDInstaller">BSDInstaller</a></li><li><a href="#FreeSBIE">FreeSBIE</a></li><li><a href="#pfSense">pfSense</a></li><li><a href="#Symbol-Versioning">Symbol Versioning</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-OpenBSM">TrustedBSD OpenBSM</a></li></ul><h3><a href="#Network-infrastructure">Network infrastructure</a></h3><ul><li><a href="#Bridge-STP-Improvements">Bridge STP Improvements</a></li><li><a href="#FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></li><li><a href="#FreeBSD-NFS-Status-Report">FreeBSD NFS Status Report</a></li><li><a href="#SMPng-Network-Stack">SMPng Network Stack</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></li><li><a href="#Sound-subsystem-improvements">Sound subsystem improvements</a></li><li><a href="#Status-Report-ATA-project">Status Report ATA project</a></li><li><a href="#TMPFS-(Filesystem)-for-FreeBSD">TMPFS (Filesystem) for FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-list-of-projects-and-ideas-for-volunteers">FreeBSD list of projects and ideas for volunteers</a></li></ul><h3><a href="#Userland-programs">Userland programs</a></h3><ul><li><a href="#Mouse-Driver-Framework">Mouse Driver Framework</a></li><li><a href="#OpenBSD-dhclient">OpenBSD dhclient</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#ARM-Support-for-TS-7200">ARM Support for TS-7200</a></li><li><a href="#FreeBSD-on-Xen-3.0">FreeBSD on Xen 3.0</a></li><li><a href="#Ultrasparc-T1-support">Ultrasparc T1 support</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#libpkg---Package-management-library">libpkg - Package management library</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Update-of-the-linux-infrastructure-in-the-Ports-Collection">Update of the linux infrastructure in the Ports
-    Collection</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#HPLIP-(Full-HP-Printer-and-MFD-support)">HPLIP (Full HP Printer and MFD support)</a></li><li><a href="#Java-Binaries">Java Binaries</a></li><li><a href="#OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan">BSDCan</a></li><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#Fundraising-for-FreeBSD-security-development">Fundraising for FreeBSD security development</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BSDInstaller" href="#BSDInstaller" id="BSDInstaller">BSDInstaller</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="http://wiki.freebsd.org/moin.cgi/BSDInstaller"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="">http://wiki.freebsd.org/moin.cgi/BSDInstaller</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Turner
-         &lt;<a href="mailto:soc-andrew@FreeBSD.org">soc-andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>The BSDInstaller integration work has progressed since the
-      previous report. The backend has been changed to the new Lua
-      version. This is to ensure the version we use will be maintained.
-      The release Makefile now uses the Lua package rather the local copy
-      in Perforce. Ports are also being created for the required modules
-      to remove the need to bring Lua into the base.</p>
-    <h3>Open tasks:</h3><ol><li>Create a port for all the Lua modules required</li></ol><hr /><h2><a name="FreeSBIE" href="#FreeSBIE" id="FreeSBIE">FreeSBIE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freesbie.org" title="http://www.freesbie.org">Website</a></td><td>
-	    URL: <a href="http://www.freesbie.org" title="Website">http://www.freesbie.org</a></td></tr><tr><td><a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="http://liste.gufi.org/mailman/listinfo/freesbie">ML Subscribe Page</a></td><td>
-	    URL: <a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="ML Subscribe Page">http://liste.gufi.org/mailman/listinfo/freesbie</a></td></tr></table><p>
-	Contact:
-          FreeSBIE
-
-          Staff
-         &lt;<a href="mailto:staff@FreeSBIE.org">staff@FreeSBIE.org</a>&gt;
-	<br />
-	Contact:
-          FreeSBIE
-
-          Mailing List
-         &lt;<a href="mailto:freesbie@gufi.org">freesbie@gufi.org</a>&gt;
-	</p>
-      <p>The project is alive and plans to release an ISO image of
-      FreeSBIE 2.0 based on FreeBSD 6.1-RELEASE few day after the same
-      has been release. FreeSBIE 2.0 will be available for i386 and amd64
-      archs. Tests images can be download via BitTorrent from
-      <a href="http://torrent.freesbie.org" shape="rect">torrent.freesbie.org</a>
-
-      .</p>
-    <h3>Open tasks:</h3><ol><li>Test "test ISO images" for both amd64 and i386</li><li>Suggest packages to be added to the ISO image.</li><li>Suggestions needed for Xfce and fluxbox look.</li><li>Suggestions needed for applications' configuration
-      files.</li></ol><hr /><h2><a name="pfSense" href="#pfSense" id="pfSense">pfSense</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pfsense.com" title="http://www.pfsense.com">pfSense website</a></td><td>
-	    URL: <a href="http://www.pfsense.com" title="pfSense website">http://www.pfsense.com</a></td></tr></table><p>
-	Contact:
-          Scott
-
-          Ullrich
-         &lt;<a href="mailto:sullrich@gmail.com">sullrich@gmail.com</a>&gt;
-	</p>
-      <p>pfSense continues to grow and fix bugs. Since the last report we
-      have grown to 14 developers working part and full time on bringing
-      pfSense to 1.0. Beta 3 is scheduled for release on 4/15/2006.</p>
-    <h3>Open tasks:</h3><ol><li>Fix remaining bugs listed in CVSTrac</li><li>Fine tune existing code</li></ol><hr /><h2><a name="Symbol-Versioning" href="#Symbol-Versioning" id="Symbol-Versioning">Symbol Versioning</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~deischen/symver/library_versioning.html" title="http://people.freebsd.org/~deischen/symver/library_versioning.html">Symbol Versioning in FreeBSD.</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~deischen/symver/library_versioning.html" title="Symbol Versioning in FreeBSD.">http://people.freebsd.org/~deischen/symver/library_versioning.html</a></td></tr><tr><td><a href="http://docs.sun.com/app/docs/doc/817-1984" title="http://docs.sun.com/app/docs/doc/817-1984">Symbol Versioning in Solaris.</a></td><td>
-	    URL: <a href="http://docs.sun.com/app/docs/doc/817-1984" title="Symbol Versioning in Solaris.">http://docs.sun.com/app/docs/doc/817-1984</a></td></tr><tr><td><a href="http://people.redhat.com/~drepper/symbol-versioning" title="http://people.redhat.com/~drepper/symbol-versioning">Symbol Versioning in Linux</a></td><td>
-	    URL: <a href="http://people.redhat.com/~drepper/symbol-versioning" title="Symbol Versioning in Linux">http://people.redhat.com/~drepper/symbol-versioning</a></td></tr></table><p>
-	Contact:
-          Daniel
-
-          Eischen
-         &lt;<a href="mailto:deischen@FreeBSD.org">deischen@FreeBSD.org</a>&gt;
-	</p>
-      <p>Symbol versioning libraries allows us to maintain binary
-      compatibility without bumping library version numbers. Recently,
-      symbol versioning for libc, libpthread, libthread_db, and libm was
-      committed to -current. It is disabled by default, and can be
-      enabled by adding "SYMVER_ENABLED=true" to/etc/make.conf. A final
-      version bump for libc and other affected libraries (perhaps all)
-      should be done before enabling this by default.</p>
-    <h3>Open tasks:</h3><ol><li>Determining the impact on ports - portmgr (Kris) is running a
-      portbuild to identify any problems. I am working to resolve the few
-      problems that were found.</li><li>Making our linker link to libc and libpthread (when using
-      (-pthread)) when building shared libraries. This is needed so that
-      symbol version dependencies are recorded in the shared library. I
-      think kan@ is working on this.???</li><li>Identify and symbol version any other libraries that should
-      be symbol versioned. If anyone has any suggestions, I'm all
-      ears.</li></ol><hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/audit.html" title="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit Web Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/audit.html" title="TrustedBSD Audit Web Page">http://www.TrustedBSD.org/audit.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <p>In the past three months, the TrustedBSD CAPP audit
-      implementation has been merged to the FreeBSD 7-CURRENT development
-      tree in CVS, and the groundwork has been laid for a merge to 6.X.
-      OpenBSM, a BSD-licensed implementation of Sun's Basic Security
-      Module (BSM) API and file format, as well as extensions to support
-      intrusion detect applications. New features included support for
-      audit pipes, a pseudo-device that provides a live audit record
-      trail interface for intrusion detection applications, and an audit
-      filter daemon that allows plug-in modules to monitor live
-      events.</p>
-    <h3>Open tasks:</h3><ol><li>Complete audit coverage of non-native system call ABIs, some
-      more recent base system calls.</li><li>Integrate OpenBSM 1.0 alpha 6, which includes auditfilterd
-      and the audit filter API.</li></ol><hr /><h2><a name="TrustedBSD-OpenBSM" href="#TrustedBSD-OpenBSM" id="TrustedBSD-OpenBSM">TrustedBSD OpenBSM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.OpenBSM.org/" title="http://www.OpenBSM.org/">TrustedBSD OpenBSM Web Page</a></td><td>
-	    URL: <a href="http://www.OpenBSM.org/" title="TrustedBSD OpenBSM Web Page">http://www.OpenBSM.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <p>OpenBSM is a BSD-licensed implementation of Sun's Basic Security
-      Module (BSM) API and file format, based on Apple's Darwin
-      implementation. OpenBSM 1.0 alpha 5 is now available, and includes
-      significant bugfixes, documentation, and feature enhancements over
-      previous releases, including 64-bit token support,
-      endian-independent operation, improved memory management, and bug
-      fixes resulting from the static analysis tools provided by Coverity
-      and FlexeLint. Recent versions are now built and configured using
-      autoconf and automake, and have been built and tested with FreeBSD,
-      Mac OS X, and Linux.</p>
-    <h3>Open tasks:</h3><ol><li>Complete OpenBSM file format validation test suite.</li><li>Finalize audit filter API.</li><li>Complete file format documentation; record documentation for
-      new record types associated with Mac OS X, FreeBSD, and Linux
-      specific events not present in documented Solaris record
-      format.</li></ol><hr /><br /><h1><a name="Network-infrastructure" href="#Network-infrastructure" id="Network-infrastructure">Network infrastructure</a></h1><br /><h2><a name="Bridge-STP-Improvements" href="#Bridge-STP-Improvements" id="Bridge-STP-Improvements">Bridge STP Improvements</a></h2><p>
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has been started to implement the Rapid Spanning Tree
-      Protocol which supersedes STP. RSTP has a much faster link failover
-      time of around one second compared to 30-60 seconds for STP, this
-      is very important on modern networks. Some progress has been made
-      but a RSTP capable switch will be needed soon to proceed, see
-      <a href="http://www.freebsd.org/donations/wantlist.html" shape="rect">
-      http://www.freebsd.org/donations/wantlist.html</a>
-
-      .</p>
-    <h3>Open tasks:</h3><ol><li>Donation of a RSTP switch</li></ol><hr /><h2><a name="FAST_IPSEC-Upgrade" href="#FAST_IPSEC-Upgrade" id="FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html" title="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html"></a></td><td>
-	    URL: <a href="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html" title="">http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Split out of PF_KEY code between the kernel and user space has
-      been completed and committed to CVS.</p>
-
-      <p>The diff between Kame IPv4 based IPSec and FAST_IPSEC IPv4 did
-      not show any glaring issues.</p>
-
-      <p>Moving on to making IPv6 work in FAST_IPSEC including being able
-      to run the kernel with the following variations:
-      <ul>
-        <li>FAST_IPSEC in v4 only</li>
-
-        <li>KAME IPv6 and IPSec</li>
-
-        <li>KAME IPv6 and FAST_IPSEC</li>
-      </ul>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Any patches for FAST_IPSEC, KAME IPsec of either variant (v4
-      or v6) should be forwarded to bz@ and gnn@.</li><li>Build a better TAHI. TAHI, the test framework, will not be
-      maintained and is not the easiest system to use and understand. A
-      better test harness is possible and is necessary for other
-      networking projects as well. Contact gnn@ if you have time to work
-      on this as he has some code and ideas to start from.</li></ol><hr /><h2><a name="FreeBSD-NFS-Status-Report" href="#FreeBSD-NFS-Status-Report" id="FreeBSD-NFS-Status-Report">FreeBSD NFS Status Report</a></h2><p>
-	Contact:
-          Chuck
-
-          Lever
-         &lt;<a href="mailto:cel@FreeBSD.org">cel@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for NFS in FreeBSD received a boost this quarter as a
-      kernel developer from Network Appliance has volunteered to help
-      with the clients. Chuck Lever is now a src committer, mentored by
-      Mike Silbersack. Mohan Srinivasan and Jim Rees have ended their
-      apprenticeships and are now full committers. Mohan continues his
-      effort to make the NFSv2/3 client SMP safe. He expects to make the
-      changes available for review soon.</p>
-
-      <p>FreeBSD gained presence at the annual NFS interoperability event
-      known as Connectathon. Rick Macklem's FreeBSD NFSv4 server is
-      pretty stable now and available via anonymous ftp. NFSv4.1 features
-      are not a part of it yet and are not likely to happen until at
-      least the end of 2006. Contact rick@snowhite.cis.uoguelph.ca for
-      details.</p>
-    <hr /><h2><a name="SMPng-Network-Stack" href="#SMPng-Network-Stack" id="SMPng-Network-Stack">SMPng Network Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/netperf/" title="http://www.FreeBSD.org/projects/netperf/">FreeBSD Netperf Project</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/netperf/" title="FreeBSD Netperf Project">http://www.FreeBSD.org/projects/netperf/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD netperf project has recently focused on revising the
-      socket and protocol control block reference counts to define and
-      enforce reference and memory management invariants, allowing the
-      removal of unnecessary checks, error handling, and locking. Use of
-      global pcbinfo locks has now been eliminated from the socket send
-      and receive paths into all network protocols, including netipx,
-      netnatm, netatalk, netinet, netinet6, netgraph, and others. Checks
-      have generally been replaced with assertions; so_pcb is now
-      guaranteed to be non-NULL. This should improve performance by
-      reducing lock contention and unnecessary checks, as well as
-      facilitate future work to eliminate long holding of pcbinfo locks
-      in the TCP input path through proper reference counting for pcbs.
-      These changes have been committed to FreeBSD 7-CURRENT, and will be
-      merged in a few months once they have stabilized.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Low-overhead-performance-monitoring-for-FreeBSD" href="#Low-overhead-performance-monitoring-for-FreeBSD" id="Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement">Project home page</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement" title="Project home page">http://people.freebsd.org/~jkoshy/projects/perf-measurement</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>This projects implements a kernel module (hwpmc(4)), an
-      application programming interface (pmc(3)) and a few simple
-      applications (pmcstat(8) and pmccontrol(8)) for measuring system
-      performance using event monitoring hardware in modern CPUs.</p>
-
-      <p>New features since the last status report:</p>
-
-      <ul>
-        <li>Support for profiling dynamically loaded kernel and user
-        objects has been added.</li>
-
-        <li>pmcstat(8) now supports command-line syntax for logging to a
-        network socket.</li>
-      </ul>
-    <hr /><h2><a name="Sound-subsystem-improvements" href="#Sound-subsystem-improvements" id="Sound-subsystem-improvements">Sound subsystem improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.leidinger.net/FreeBSD/hdac-20060313.tbz" title="http://www.leidinger.net/FreeBSD/hdac-20060313.tbz">Start of Intel HDA support.</a></td><td>
-	    URL: <a href="http://www.leidinger.net/FreeBSD/hdac-20060313.tbz" title="Start of Intel HDA support.">http://www.leidinger.net/FreeBSD/hdac-20060313.tbz</a></td></tr></table><p>
-	Contact:
-          Multimedia
-
-          Mailinglist
-         &lt;<a href="mailto:freebsd-multimedia@FreeBSD.org">freebsd-multimedia@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Ariff
-
-          Abdullah
-         &lt;<a href="mailto:ariff@FreeBSD.org">ariff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>A lot of fixes (bugs, LORs, panics) and improvements
-      (performance, compatibility, a new driver, 24/32bit samples
-      support, ...) have been merged to RELENG_6. FreeBSD 6.1 is the
-      first release which ships with the much improved sound system.
-      Additionally there's work underway:
-      <ul>
-        <li>To make the sound system API endianess clean. This should
-        make it easier (for a developer) to make the sound drivers usable
-        on all architectures.</li>
-
-        <li>To rework character device allocation. This way someone can
-        choose a specific channel, e.g. /dev/dsp0.r0 or /dev/dsp0.p0 to
-        access the first recording or play channel respectively). With
-        the "current" sound system (as in FreeBSD 6.1) this is not
-        possible (accessing /dev/dsp0.0 and /dev/dsp0.1 may give you the
-        first or the second channel, the number is just an enumeration,
-        not a channel-chooser).</li>
-
-        <li>To add multi-channel support/processing.</li>
-
-        <li>To add Intel HDA support. There's already some code to look
-        at (see URL referenced above), but is far from usable for an
-        enduser (we need some programmers, but no testers ATM, since
-        there are no user testable parts yet). Interested volunteers
-        should contact the multimedia mailinglist.</li>
-      </ul>
-
-      Parts of this work may be already in 6.1, but there's still a good
-      portion which isn't even in -current as of this writing.</p>
-    <h3>Open tasks:</h3><ol><li>Style(9) cleanup, survive against WARNS=2 (at least).</li><li>Have a look at the sound related entries on the ideas
-      list.</li><li>Rewrite some parts (e.g. a new mixer subsystem with OSS
-      compatibility).</li><li>sndctl(1): tool to control non-mixer parts of the sound
-      system (e.g. spdif switching, virtual-3D effects) by an user
-      (instead of the sysctl approach in -current); pcmplay(1),
-      pcmrec(1), pcmutil(1).</li><li>Plugable FEEDER infrastructure. For ease of debugging various
-      feeder stuff and/or as userland library and test suite.</li><li>Closer compatibility with OSS, especially for the upcoming
-      OSS v4.</li></ol><hr /><h2><a name="Status-Report-ATA-project" href="#Status-Report-ATA-project" id="Status-Report-ATA-project">Status Report ATA project</a></h2><p>
-	Contact:
-          S�ren
-
-          Schmidt
-         &lt;<a href="mailto:sos@FreeBSD.org">sos@FreeBSD.org</a>&gt;
-	</p>
-      <p>The last months has mostly been about stabilizing ATA for
-      6.1-RELEASE, and adding support for new chipsets. On that front
-      JMicron has raised the bar for vendors as they have provided not
-      only hardware but documentation on both their hardware and their
-      software RAID implementation, making it a breeze to add support for
-      their, by the way excellent, products. Other vendors can join in
-      here. :) Otherwise I'm always in the need for any amount of time or
-      means to get it if nothing else.</p>
-
-      <p>ATA has grown a USB backend so that fx. flash keys and external
-      HD/CD/DVD drives can be used directly without atapicam/CAM etc.
-      This is very handy on small (embedded) systems where resources are
-      limited and kernel space at a premium. burncd(8) is in the process
-      of being updated so it will support this along with SATA ATAPI
-      devices, and if time permits adding DVD support.</p>
-
-      <p>The next months will be used to (hopefully) work on getting ATA
-      to work properly on systems with &gt; 4G of memory and utilize the
-      64bit addressing of controllers that support it. RAID5 support for
-      ataraid is on the list together with hardening of the RAID
-      subsystem to help keep data alive and well.</p>
-    <hr /><h2><a name="TMPFS-(Filesystem)-for-FreeBSD" href="#TMPFS-(Filesystem)-for-FreeBSD" id="TMPFS-(Filesystem)-for-FreeBSD">TMPFS (Filesystem) for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://download.purpe.com/tmpfs" title="http://download.purpe.com/tmpfs">Project Home</a></td><td>
-	    URL: <a href="http://download.purpe.com/tmpfs" title="Project Home">http://download.purpe.com/tmpfs</a></td></tr><tr><td><a href="http://download.purpe.com/tmpfs/bmark.html" title="http://download.purpe.com/tmpfs/bmark.html">I/O Benchmarks</a></td><td>
-	    URL: <a href="http://download.purpe.com/tmpfs/bmark.html" title="I/O Benchmarks">http://download.purpe.com/tmpfs/bmark.html</a></td></tr></table><p>
-	Contact:
-          Rohit
-
-          Jalan
-         &lt;<a href="mailto:rohitj@purpe.com">rohitj@purpe.com</a>&gt;
-	</p>
-      <p>Three betas have been released so far. The code is operational
-      and seems to be stable but it is not MPSAFE yet.</p>
-
-      <p>The second and third betas used different mechanisms for data
-      I/O. (sfbuf vs. kernel_map+vacache) and at present I am in the
-      process on selecting one mechanism over the other. Your opinion is
-      solicited.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="FreeBSD-list-of-projects-and-ideas-for-volunteers" href="#FreeBSD-list-of-projects-and-ideas-for-volunteers" id="FreeBSD-list-of-projects-and-ideas-for-volunteers">FreeBSD list of projects and ideas for volunteers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/ideas/" title="http://www.FreeBSD.org/projects/ideas/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/ideas/" title="">http://www.FreeBSD.org/projects/ideas/</a></td></tr></table><p>
-	Contact:
-          Joel
-
-          Dahl
-         &lt;<a href="mailto:joel@FreeBSD.org">joel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD list of projects and ideas for volunteers is doing
-      well. Several items were picked up by volunteers and have found
-      their way into the tree. Others are under review or in
-      progress.</p>
-
-      <p>We are looking forward to hear about new ideas, people willing
-      to be technical contacts for generic topics (e.g. USB) or specific
-      entries (already existing or newly created), suggestions for
-      existing entries or completion reports for (parts of) an entry.</p>
-    <h3>Open tasks:</h3><ol><li>Add more ideas.</li><li>Find more technical contacts.</li><li>Find people willing to review/test implementations of
-      (somewhat) finished items.</li></ol><hr /><br /><h1><a name="Userland-programs" href="#Userland-programs" id="Userland-programs">Userland programs</a></h1><br /><h2><a name="Mouse-Driver-Framework" href="#Mouse-Driver-Framework" id="Mouse-Driver-Framework">Mouse Driver Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.semicomplete.com/projects/newpsm" title="http://www.semicomplete.com/projects/newpsm">mouse framework project</a></td><td>
-	    URL: <a href="http://www.semicomplete.com/projects/newpsm" title="mouse framework project">http://www.semicomplete.com/projects/newpsm</a></td></tr></table><p>
-	Contact:
-          Jordan
-
-          Sissel
-         &lt;<a href="mailto:jls@csh.rit.edu">jls@csh.rit.edu</a>&gt;
-	</p>
-      <p>The current mouse system is a mess with moused, psm, ums, and
-      mse supporting, individually, multiple kinds of mice. This project
-      aims to move all driver support into moused modules in userland. In
-      addition, many features lacking in the existing mouse
-      infrastructure are being added. It is my hope that this new system
-      will make both using mice and writing drivers easier down the
-      road.</p>
-    <h3>Open tasks:</h3><ol><li>Testing. Contact if interested.</li></ol><hr /><h2><a name="OpenBSD-dhclient" href="#OpenBSD-dhclient" id="OpenBSD-dhclient">OpenBSD dhclient</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>All dhclient changes in HEAD have been merged to 6-STABLE for
-      6.1-RELEASE. New patches currently in testing include startup
-      script support for fully asynchronous starting of dhclient which
-      eliminates the wait for link during startup and support for sending
-      the system hostname to the server when non is specified.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="ARM-Support-for-TS-7200" href="#ARM-Support-for-TS-7200" id="ARM-Support-for-TS-7200">ARM Support for TS-7200</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.embeddedarm.com/epc/ts7200-spec-h.html" title="http://www.embeddedarm.com/epc/ts7200-spec-h.html">TS-7200 Board</a></td><td>
-	    URL: <a href="http://www.embeddedarm.com/epc/ts7200-spec-h.html" title="TS-7200 Board">http://www.embeddedarm.com/epc/ts7200-spec-h.html</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO">Perforce Code Location</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO" title="Perforce Code Location">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg/arm&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://people.freebsd.org/~jmg/dmesg.ts7200" title="http://people.freebsd.org/~jmg/dmesg.ts7200">FreeBSD/arm TS-7200 dmesg output</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jmg/dmesg.ts7200" title="FreeBSD/arm TS-7200 dmesg output">http://people.freebsd.org/~jmg/dmesg.ts7200</a></td></tr></table><p>
-	Contact:
-          John-Mark
-
-          Gurney
-         &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>This is just an update to note that TS-7200 is building and
-      running with a recent -current.</p>
-
-      <p>I have been working on getting FreeBSD/arm running on the
-      TS-7200. So far the board boots, and has somewhat working ethernet
-      (some unexplained packet loss). I can netboot from a FreeBSD/i386
-      machine, and I can also mount msdosfs's on CF.</p>
-    <h3>Open tasks:</h3><ol><li>Figuring out why some small packets transmit with error (if
-      someone can get Technologic Systems to pay attention to me and this
-      issue, that'd be great!)</li><li>EP93xx identification information to properly attach various
-      onboard devices</li></ol><hr /><h2><a name="FreeBSD-on-Xen-3.0" href="#FreeBSD-on-Xen-3.0" id="FreeBSD-on-Xen-3.0">FreeBSD on Xen 3.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@FreeBSD.org">kmacy@FreeBSD.org</a>&gt;
-	</p>
-      <p>We had hoped to finish a prototype of Xen DomU and possible Dom0
-      in time for FreeBSD 6.1. The primary work was focused on bringing
-      Xen into the FreeBSD 'newbus' framework. Unfortunately, an
-      architectural problem in FreeBSD has stopped us. Xen relies on
-      message passing between to child and parent domains to communicate
-      device configuration, and this message passing requires that tsleep
-      and wakeup work early in boot. That doesn't seem to be the case,
-      and it's unclear what it would take to make it work. Without the
-      newbus work, it's hard to complete the Dom0 code, and impossible to
-      support Xen 3.0 features like domain suspension.</p>
-    <h3>Open tasks:</h3><ol><li>Make tsleep and wakeup work during early boot</li><li>Continue DomU newbus work</li><li>Continue Dom0 work</li></ol><hr /><h2><a name="Ultrasparc-T1-support" href="#Ultrasparc-T1-support" id="Ultrasparc-T1-support">Ultrasparc T1 support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://opensparc-t1.sunsource.net/index.html" title="http://opensparc-t1.sunsource.net/index.html">T1 processor and hypervisor documentation.</a></td><td>
-	    URL: <a href="http://opensparc-t1.sunsource.net/index.html" title="T1 processor and hypervisor documentation.">http://opensparc-t1.sunsource.net/index.html</a></td></tr><tr><td><a href="http://www.fsmware.com/sun4v/todo.txt" title="http://www.fsmware.com/sun4v/todo.txt">TODO list</a></td><td>
-	    URL: <a href="http://www.fsmware.com/sun4v/todo.txt" title="TODO list">http://www.fsmware.com/sun4v/todo.txt</a></td></tr></table><p>
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@FreeBSD.org">kmacy@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          John
-
-          Gurney
-         &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD has been ported the T1, Sun's newest processor. FreeBSD
-      currently runs multi-user SMP. JMG is actively working on improving
-      device support.</p>
-
-      <p>The port has taken several weeks longer than initially
-      anticipated as the majority of the current sparc64 port could not
-      be re-used.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="libpkg---Package-management-library" href="#libpkg---Package-management-library" id="libpkg---Package-management-library">libpkg - Package management library</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://libpkg.berlios.de/" title="http://libpkg.berlios.de/"></a></td><td>
-	    URL: <a href="http://libpkg.berlios.de/" title="">http://libpkg.berlios.de/</a></td></tr><tr><td><a href="http://developer.berlios.de/projects/libpkg/" title="http://developer.berlios.de/projects/libpkg/"></a></td><td>
-	    URL: <a href="http://developer.berlios.de/projects/libpkg/" title="">http://developer.berlios.de/projects/libpkg/</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Turner
-         &lt;<a href="mailto:andrew@fubar.geek.nz">andrew@fubar.geek.nz</a>&gt;
-	</p>
-      <p>Libpkg is a package management library using libarchive to
-      extract the package files. It is able to download, install and get
-      a list of installed packages. Work has also been started on
-      implementing the package tools from the base system. Most of
-      pkg_info has been implemented and pkg_add has been started.</p>
-    <h3>Open tasks:</h3><ol><li>Support for more command line options in pkg_info and
-      pkg_add</li><li>Creating a package</li><li>Test pkg_add works as expected for all implemented command
-      line options</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://edwin.adsl.barnet.com.au/~edwin/ports/" title="http://edwin.adsl.barnet.com.au/~edwin/ports/">FreeBSD ports updated distfile survey (Edwin Groothius' report)</a></td><td>
-	    URL: <a href="http://edwin.adsl.barnet.com.au/~edwin/ports/" title="FreeBSD ports updated distfile survey (Edwin Groothius' report)">http://edwin.adsl.barnet.com.au/~edwin/ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>During this time, the number of ports PRs rose dramatically from
-      its impressive low number seen late last quarter. This was due to
-      the holidays, the freeze for the 5.5/6.1 release cycle, and the
-      aggressive work several submitters have been doing to correct
-      long-standing problems with stale distfiles, stale WWW sites, port
-      that only work on i386, and so forth. Over 200 new ports have also
-      been added. The statistics do not truly reflect the state of the
-      Ports Collection, which continues to improve despite the increased
-      number of ports.</p>
-
-      <p>We now have 3 people who are qualified to run the 5-exp
-      regression tests. Due to this, we were able to run several cycles,
-      resulting in a series of commits that retired more than 3 dozen
-      portmgr PRs. There were a few snags during one commit due to some
-      unintended consequences, but the breakage was fixed in less than
-      one day. Notable changes include the addition of physical category
-      net-p2p and virtual categories hamradio and rubygems. Once 5.5 and
-      6.1 are released, portmgr hopes to be able to run regression tests
-      more often.</p>
-
-      <p>We have added 5 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>We need help getting back to our modern low of 500
-      PRs.</li><li>We have over 4,000 unmaintained ports (see, for instance,
-      <url href="http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports@FreeBSD.org">
-      the list on portsmon</url>
-
-      ). We are always looking for dedicated volunteers to adopt at least
-      a few ports.</li></ol><hr /><h2><a name="Update-of-the-linux-infrastructure-in-the-Ports-Collection" href="#Update-of-the-linux-infrastructure-in-the-Ports-Collection" id="Update-of-the-linux-infrastructure-in-the-Ports-Collection">Update of the linux infrastructure in the Ports
-    Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Emulation
-
-          Mailinglist
-         &lt;<a href="mailto:freebsd-emulation@FreeBSD.org">freebsd-emulation@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Boris
-
-          Samorodov
-         &lt;<a href="mailto:bsam@ipt.ru">bsam@ipt.ru</a>&gt;
-	</p>
-      <p>Work is underway to use the new linux_base-fc3 as the new
-      default linux base. Since there's some infrastructure work to do
-      before it can be made the new default, this will not happen before
-      the release of FreeBSD 5.5 and 6.1. At the same time a new X.org
-      based linux port will replace the outdated XFree86 based linux X11
-      port.</p>
-
-      <p>The use of fc3 instead of fc4 or fc5 is to make sure we have a
-      smooth transition with as less as possible breakage. We already use
-      several fc3 RPM's with the current default of linux_base-8, so
-      there should be not much problems to solve.</p>
-    <h3>Open tasks:</h3><ol><li>Mark all old linux_base ports as DEPRECATED (after making fc3
-      the default linux_base port).</li><li>Have a look at a linux-dri version which works with the
-      update to X.org.</li><li>When everything is switched to fc3 and everything works at
-      least as good as before, have a look at porting fc4 or fc5.</li></ol><hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="HPLIP-(Full-HP-Printer-and-MFD-support)" href="#HPLIP-(Full-HP-Printer-and-MFD-support)" id="HPLIP-(Full-HP-Printer-and-MFD-support)">HPLIP (Full HP Printer and MFD support)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://am-productions.biz/docs/hplip.php" title="http://am-productions.biz/docs/hplip.php">HPLIP FreeBSD Information</a></td><td>
-	    URL: <a href="http://am-productions.biz/docs/hplip.php" title="HPLIP FreeBSD Information">http://am-productions.biz/docs/hplip.php</a></td></tr><tr><td><a href="http://hplip.sourceforge.net/" title="http://hplip.sourceforge.net/">Official Site</a></td><td>
-	    URL: <a href="http://hplip.sourceforge.net/" title="Official Site">http://hplip.sourceforge.net/</a></td></tr></table><p>
-	Contact:
-          Anish
-
-          Mistry
-         &lt;<a href="mailto:amistry@am-productions.biz">amistry@am-productions.biz</a>&gt;
-	</p>
-      <p>A preliminary version of HP's hplip software for their printers
-      and multi-function devices has been ported. This allows viewing of
-      the status informantion from the printer. Such as ink levels, error
-      messages, and queue information. If you have an Officejet you can
-      also fax and scan. Photocard and Copies functionality is
-      untested.</p>
-    <h3>Open tasks:</h3><ol><li>General Testing</li><li>Photocard Testing</li><li>Various ugen fixes</li><li>Fix Officejet Panel Display</li><li>Run hpiod and hpssd as unprivileged users</li><li>Banish the Linuxisms in the Makefile</li><li>Fix "Make Copies"</li><li>Automatically Setup Scanner</li></ol><hr /><h2><a name="Java-Binaries" href="#Java-Binaries" id="Java-Binaries">Java Binaries</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org/downloads/java.shtml" title="http://www.freebsdfoundation.org/downloads/java.shtml">FreeBSD Foundation Java Homepage</a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org/downloads/java.shtml" title="FreeBSD Foundation Java Homepage">http://www.freebsdfoundation.org/downloads/java.shtml</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@freebsd.org">deb@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation released official certified JDK and JRE
-      1.5 binaries for the official FreeBSD 5.4 and FreeBSD 6.0 releases
-      on the i386 platform.
-      <br clear="none" />
-
-      We were able to accomplish this by hiring a contractor to run the
-      Sun certification tests and fixing the problems found. This could
-      not have been completed without the support from the BSD Java
-      Team.</p>
-
-      <p>We provided financial support for Java development and funded
-      the certification process. We spent a significant amount of time
-      and money on legal issues from contract and NDA creation for our
-      contractor to license agreements from Sun and creating our own for
-      the binaries. We worked with OEMs who would like to use the
-      binaries, but needed to understand what they need to do legally to
-      be able to redistribute the binaries. This is an area we are still
-      working on at our end. We are waiting for a letter from Sun to put
-      on our website to OEMs. We are also in the process of updating our
-      OEM license agreement. This should be available by mid-April.</p>
-
-      <p>We have received a positive response from the FreeBSD community
-      regarding the release of the binaries. We received a few requests
-      to support the FreeBSD 6.1/amd64 platform. We have decided to move
-      forward and support this too. We currently are working with a
-      contractor to provide Java support on 5.5/i386, 6.1/i386, and
-      6.1/amd64. Once 5.5 and 6.1 are released, we'll update the FreeBSD
-      Foundation website with the Java status. Regular updates to the
-      website will continue.</p>
-    <hr /><h2><a name="OpenBSD-packet-filter---pf" href="#OpenBSD-packet-filter---pf" id="OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work towards importing the upcoming OpenBSD 3.9 version of pf is
-      starting slowly. There are a couple of infrastructural changes
-      (e.g. interface groups) that need to be imported beforehand. This
-      work is in the final stage of progress.</p>
-
-      <p>A couple of bugfixes have happened since the last report and will
-      be available in FreeBSD 6.1/5.5. pf users are strongly encouraged
-      to upgrade to RELENG_6 as the version present in RELENG_5 is
-      collecting dust.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan" href="#BSDCan" id="BSDCan">BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/2006/" title="http://www.bsdcan.org/2006/"></a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2006/" title="">http://www.bsdcan.org/2006/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>The
-      <a href="http://www.bsdcan.org/2006/schedule.php" shape="rect">schedule</a>
-
-      for BSDCan 2006 demonstrates just how strong and popular BSDCan has
-      become in a very short time. Three concurrent streams of talks make
-      sure that there is something for everyone. We provide high quality
-      talks at very affordable
-      <a href="http://www.bsdcan.org/2006/registration.php" shape="rect">prices</a>
-
-      .</p>
-
-      <p>BSDCan is the biggest BSD event of 2006. Ask others who attended
-      in past years how much they enjoyed their time in Ottawa. Ask them
-      who they met, who they talked to, the contacts they made, the
-      information they learned.</p>
-
-      <p>Remember to bring your wife/husband/spouse/etc because we will
-      have things for them to do while you are attending the conference.
-      Ottawa is a fantastic tourist destination.</p>
-
-      <p>See you at BSDCan 2006!</p>
-    <h3>Open tasks:</h3><ol><li>
-      <a href="http://www.bsdcan.org/2006/activity.php?id=110" shape="rect">Works in
-      Progress</a>
-
-      - if you want to talk about your project for 5 minutes, this is
-      your chance. Get in touch with us ASAP to reserve your spot.</li><li>We're looking for volunteers to help out just before and
-      during the conference. Contact Dan at the above address.</li></ol><hr /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In March 2006, Marcus Alves Grando, George Neville-Neil, and
-      Philip Paeps joined the FreeBSD Security Team. The current Security
-      Team membership is published on the web site.</p>
-
-      <p>In the time since the last status report, eight security
-      advisories have been issued concerning problems in the base system
-      of FreeBSD; of these, three problems were in "contributed" code,
-      while five were in code maintained within FreeBSD. The
-      Vulnerabilities and Exposures Markup Language (VuXML) document has
-      continued to be updated by the Security Team and the Ports
-      Committers documenting new vulnerabilities in the FreeBSD Ports
-      Collection; since the last status report, 50 new entries have been
-      added, bringing the total up to 686.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 4.10, FreeBSD 4.11, FreeBSD 5.3, FreeBSD
-      5.4, and FreeBSD 6.0. Upon their release, FreeBSD 5.5 and FreeBSD
-      6.1 will also be supported. The respective End of Life dates of
-      supported releases are listed on the web site; of particular note,
-      FreeBSD 4.10 and FreeBSD 5.4 will cease to be supported at the end
-      of May 2006.</p>
-    <hr /><h2><a name="Fundraising-for-FreeBSD-security-development" href="#Fundraising-for-FreeBSD-security-development" id="Fundraising-for-FreeBSD-security-development">Fundraising for FreeBSD security development</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~cperciva/funding.html" title="http://people.freebsd.org/~cperciva/funding.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~cperciva/funding.html" title="">http://people.freebsd.org/~cperciva/funding.html</a></td></tr></table><p>
-	Contact:
-          Colin
-
-          Percival
-         &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since 2003, I have introduced the (now quite widely used)
-      FreeBSD Update and Portsnap tools, but rarely had time to make
-      improvements or add requested features. Consequently, on March
-      30th, I sent email to the freebsd-hackers, freebsd-security,
-      and freebsd-announce lists announcing that I was seeking funding to
-      allow me to spend the summer working full-time on these and my role
-      as FreeBSD Security Officer. Assuming that some cheques arrive as
-      expected, I have reached my donation target and will start work at
-      the beginning of May.</p>
-    <h3>Open tasks:</h3><ol><li>The work which I'm aiming to do is listed at the URL
-      above.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2006-04-2006-06.html b/website/content/en/status/report-2006-04-2006-06.html
deleted file mode 100644
index 74949aa934..0000000000
--- a/website/content/en/status/report-2006-04-2006-06.html
+++ /dev/null
@@ -1,1433 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>With the release of FreeBSD 5.5 and FreeBSD 6.1, the second
-    quarter of 2006 has been productive. Google is sponsoring 14 students
-    to work on FreeBSD as part of their Summer of Code Program (most of
-    which already submitted a report for elaboration on their
-    projects).</p><p>Sun's open-source software is starting to make its way into
-    FreeBSD as a port of DTrace is nearing completion and a port to the
-    UltraSparc T1 processor (which gives a great push to the ongoing SMP
-    efforts). Having a powerful debugging tool combined with a CPU that
-    can run up to 32 concurrent threads helps to identify scalability
-    issues.</p><p>BSDCan 2006 was yet again a smashing success and much was covered
-    in the 2-day developer summit. As a product of the conference, a new
-    focus on FreeBSD for the embedded sector has started. Various ARM
-    boards are targeted, a MIPS32 port is gearing up and people are
-    looking for other interesting platforms to port FreeBSD to.
-    Preparation for the EuroBSDCon (in Milan, Italy) on November has
-    already issued a call for papers.</p><p>In addition, a lot of spring cleaning is taking place in the
-    network stack. After conclusion of the KAME project, IPv6 code
-    integration has been refocused and a fully locked port of SCTP is in
-    the final stage of integration. Of course, all this goes without
-    noting all the progress made with the other network projects.</p><p>Please read below for more detailed news on the projects that
-    happened in FreeBSD during the last three months. If you are
-    interested in helping, consider the "Open Tasks lists" provided with
-    some reports. In addition we would like to point you at the
-    <a href="http://www.freebsd.org/projects/ideas/" shape="rect">list of projects and
-    ideas for volunteers</a>
-
-    and hope to receive a status report from you next time.</p><p>Thanks to all reporters for your excellent work and timing! Enjoy
-    reading.</p><hr /><h3><a href="#Google-summer-of-code">Google summer of code</a></h3><ul><li><a href="#BSNMP-Bridge-module">BSNMP Bridge module</a></li><li><a href="#gvirstor">gvirstor</a></li><li><a href="#Improving-Ports-Collection">Improving Ports Collection</a></li><li><a href="#Interrupt-handling">Interrupt handling</a></li><li><a href="#IPv6-Vulnerabilities">IPv6 Vulnerabilities</a></li><li><a href="#Jail-Resource-Limits">Jail Resource Limits</a></li><li><a href="#K-Kernel-Meta-Language">K Kernel Meta-Language</a></li><li><a href="#Linuxolator-kernel-update-to-match-functionality-of-2.6.x">Linuxolator kernel update to match functionality of
-    2.6.x</a></li><li><a href="#Nss-LDAP-importing-and-nsswitch-subsystem-improvement">Nss-LDAP importing and nsswitch subsystem improvement</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#DTrace">DTrace</a></li><li><a href="#Embedded-FreeBSD">Embedded FreeBSD</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li></ul><h3><a href="#Network-infrastructure">Network infrastructure</a></h3><ul><li><a href="#FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></li><li><a href="#FreeBSD-NFS-Status-Report">FreeBSD NFS Status Report</a></li><li><a href="#IPv6-cleanup">IPv6 cleanup</a></li><li><a href="#Multi-IP-v4/v6-jails">Multi-IP v4/v6 jails</a></li><li><a href="#SCTP-Integration">SCTP Integration</a></li><li><a href="#Wireless-Networking">Wireless Networking</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Giant-Less-UFS-with-Quotas">Giant-Less UFS with Quotas</a></li><li><a href="#Giant-Less-USB-framework">Giant-Less USB framework</a></li><li><a href="#GJournal">GJournal</a></li><li><a href="#Gvinum-improvements">Gvinum improvements</a></li><li><a href="#Sound-subsystem-improvements">Sound subsystem improvements</a></li><li><a href="#SSE2-Kernel-support">SSE2 Kernel support</a></li><li><a href="#XFS-for-FreeBSD">XFS for FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-list-of-projects-and-ideas-for-volunteers">FreeBSD list of projects and ideas for volunteers</a></li><li><a href="#Hungarian-translation-of-the-webpages">Hungarian translation of the webpages</a></li></ul><h3><a href="#Userland-programs">Userland programs</a></h3><ul><li><a href="#Low-overhead-performance-monitoring-tools">Low-overhead performance monitoring tools</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#PowerPC-Port">PowerPC Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Update-of-the-Linux-userland-infrastructure-in-the-Ports-Collection">Update of the Linux userland infrastructure in the Ports
-    Collection</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#BSDInstaller">BSDInstaller</a></li><li><a href="#pfSense">pfSense</a></li><li><a href="#xscale-board-buy">xscale board buy</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan">BSDCan</a></li><li><a href="#EuroBSDCon-2006---November-10th---12th,-Milan,-Italy">EuroBSDCon 2006 - November 10th - 12th, Milan, Italy</a></li><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#Release-Engineering">Release Engineering</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-summer-of-code" href="#Google-summer-of-code" id="Google-summer-of-code">Google summer of code</a></h1><br /><h2><a name="BSNMP-Bridge-module" href="#BSNMP-Bridge-module" id="BSNMP-Bridge-module">BSNMP Bridge module</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp/usr.sbin/bsnmpd/modules/snmp%5fbridge" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp/usr.sbin/bsnmpd/modules/snmp%5fbridge">P4 workspace</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp/usr.sbin/bsnmpd/modules/snmp%5fbridge" title="P4 workspace">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp/usr.sbin/bsnmpd/modules/snmp%5fbridge</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SnmpBridgeModule" title="http://wiki.freebsd.org/SnmpBridgeModule">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SnmpBridgeModule" title="Wiki page">http://wiki.freebsd.org/SnmpBridgeModule</a></td></tr></table><p>
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:shteryana@FreeBSD.org">shteryana@FreeBSD.org</a>&gt;
-	</p>
-      <p>As part of my SoC 2006 project I am working on implementing a
-      BRIDGE monitoring module for FreeBSD's BSNMP daemon. Initial
-      prototyping is done and some kernel changes are coming to be able
-      to access all needed data. In addition to IETF RFC 4188, which was
-      designed for monitoring a single bridge, this snmp module will
-      support monitoring of multiple bridge devices as supported by
-      FreeBSD.</p>
-    <h3>Open tasks:</h3><ol><li>Finish kernel changes and the code for the snmp
-      module.</li><li>Testing.</li></ol><hr /><h2><a name="gvirstor" href="#gvirstor" id="gvirstor">gvirstor</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/gvirstor" title="http://wiki.freebsd.org/gvirstor"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/gvirstor" title="">http://wiki.freebsd.org/gvirstor</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@freebsd.org">ivoras@freebsd.org</a>&gt;
-	</p>
-      <p>The purpose of
-      <em>gvirstor</em>
-
-      module is to provide the ability to create a virtual storage device
-      of arbitrarily large size (typically several terabytes) which
-      consists of an arbitrary number of physical storage devices
-      (actually any lower-level GEOM providers, including RAID devices)
-      of arbitrary size (typically 50 GB - 400 GB hard drives). Storage
-      space from these components is carved into small chunks (for
-      example 4 MB) and allocated (committed) to the virtual device on
-      as-needed basis.</p>
-
-      <p>Development has started and is progressing as planned (though a
-      little bit slow). Metadata format and virtual storage allocation
-      formats have been defined and more serious coding is in
-      progress.</p>
-    <h3>Open tasks:</h3><ol><li>Much user testing will be needed (though not
-      currently)</li></ol><hr /><h2><a name="Improving-Ports-Collection" href="#Improving-Ports-Collection" id="Improving-Ports-Collection">Improving Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n" title="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n">Wiki page about the project</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n" title="Wiki page about the project">http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n</a></td></tr><tr><td><a href="http://wiki.freebsd.org/DESTDIR" title="http://wiki.freebsd.org/DESTDIR">Explaining DESTDIR</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/DESTDIR" title="Explaining DESTDIR">http://wiki.freebsd.org/DESTDIR</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/98105" title="http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/98105">ports/98105</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/98105" title="ports/98105">http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/98105</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The improved support for the i386 binaries are ready for -exp
-      run. It only allows installing such ports on amd64 and ia64 when
-      there's a compatibility layer compiled into the kernel and the
-      32-bit libraries are installed under /usr/lib32.</p>
-
-      <p>The DESTDIR support are in progress. It works for the simplest
-      ports without USE_* that don't have a [pre|do|post]-install target.
-      There are more complicated issues with e.g. conflict checking in
-      DESTDIR, deinstalling from DESTDIR, those have to be fixed as
-      well.</p>
-    <h3>Open tasks:</h3><ol><li>DESTDIR issues should be fixed.</li><li>All ports should be examined whether they respect CC/CFLAGS,
-      and the erroneous ones should be fixed.</li><li>Fetch scripts should be taken out of bsd.port.mk to be
-      separate scripts.</li><li>A tool should be written that makes possible to cross-compile
-      ports.</li><li>A good plist generator tool should be written for porters or
-      the old one in ports/Tools/scripts should be updated.</li></ol><hr /><h2><a name="Interrupt-handling" href="#Interrupt-handling" id="Interrupt-handling">Interrupt handling</a></h2><p>
-	Contact:
-          Paolo
-
-          Pisati
-         &lt;<a href="mailto:piso@FreeBSD.org">piso@FreeBSD.org</a>&gt;
-	</p>
-      <p>With the introduction of fine grained locking in the SMPng
-      project, the FreeBSD kernel went under a major redesign, and many
-      subsystem changed significantly with it. In particular, device
-      driver's interrupt context ("the bottom half") had the necessity to
-      synchronise with process context ("the top half") and share data in
-      a consistent manner without using spl*(). To overcome this problem,
-      a new interrupt model based around interrupt threads was employed,
-      together with a fast interrupt model dedicated to particular driver
-      handlers that don't block on locks (i.e. serial port, clock,
-      etcetc). Unfortunately, even if the interrupt thread model proved
-      to be a reliable solution, its performance was not on par with
-      the pre SMPng era (4.x), and thus others solutions were
-      investigated, with interrupt filtering being one of that.</p>
-
-      <p>As part of my Summer of Code 2006 work, I'm implementing
-      interrupt filtering for FreeBSD, and when the framework will be in
-      place I'll compare the performance of filters, against all the
-      previous models: pre-SMPng(4.x), ithread and polling.</p>
-
-      <p>The most important modifications to the src tree so far were:
-      <ul>
-        <li>made PPC accept more than one FAST handler per irq line
-        (previously INTR_FAST implied INTR_EXCL)</li>
-
-        <li>converted all the INTR_FAST handlers to be filters: return an
-        error code to note what they did (FILTER_HANDLED/FILTER_STRAY)
-        and if they need more work to do (FILTER_SCHEDULE_THREAD)</li>
-
-        <li>moved part of the interrupt execution code from MD code to
-        kern_intr.c::intr_filter_loop()</li>
-
-        <li>broke newbus API: bus_setup_intr() grew a new filter
-        parameter of type "int driver_filter_t(void*)".</li>
-
-        <li>converted all the buses that override bus_setup_intr() to
-        handle filters</li>
-
-        <li>converted all the normal ithread drivers to provide a NULL
-        filter funcion</li>
-      </ul>
-
-      <br clear="none" />
-
-      The next milestone is to have all the different models (filters
-      only, ithread only and filter + ithread) work together
-      reliably.</p>
-    <h3>Open tasks:</h3><ol><li>Arm is largely untested</li><li>Sparc64 needs more work on low level (.s) interrupt
-      routine</li></ol><hr /><h2><a name="IPv6-Vulnerabilities" href="#IPv6-Vulnerabilities" id="IPv6-Vulnerabilities">IPv6 Vulnerabilities</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/ClementLecigne" title="http://wiki.freebsd.org/ClementLecigne"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/ClementLecigne" title="">http://wiki.freebsd.org/ClementLecigne</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Cl�ment
-
-          Lecigne
-         &lt;<a href="mailto:clemun@GMAIL.COM">clemun@GMAIL.COM</a>&gt;
-	</p>
-      <p>Clement has been working both with libnet and gnn's Python based
-      packet library (PCS) to produce code to test for vulnerabilities in
-      IPv6. To Clement has found some issues, all of which have been
-      reported to his mentor and to Security Officer at FreeBSD.org
-      Vulnerabilities will not be reported here.</p>
-    <h3>Open tasks:</h3><ol><li>Get 0.1 of PCS on to SourceForge for wider use.</li></ol><hr /><h2><a name="Jail-Resource-Limits" href="#Jail-Resource-Limits" id="Jail-Resource-Limits">Jail Resource Limits</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Chris
-
-          Jones
-         &lt;<a href="mailto:cdjones@freebsd.org">cdjones@freebsd.org</a>&gt;
-	</p>
-      <p>Project is in development with initial working software expected
-      mid-July 2006. CPU limits will be implemented with a hierarchical
-      scheduler: (initially) using a round-robin scheduler to select
-      which jail to run a task in and then delegating which task in the
-      jail to be run to a per-jail scheduler.</p>
-    <h3>Open tasks:</h3><ol><li>Complete round-robin inter-jail scheduler (with existing 4BSD
-      schedulers implemented per jail).</li><li>Add hooks for memory tracking.</li></ol><hr /><h2><a name="K-Kernel-Meta-Language" href="#K-Kernel-Meta-Language" id="K-Kernel-Meta-Language">K Kernel Meta-Language</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/SpencerWhitman" title="http://wiki.freebsd.org/SpencerWhitman"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SpencerWhitman" title="">http://wiki.freebsd.org/SpencerWhitman</a></td></tr></table><p>
-	Contact:
-          Spencer
-
-          Whitman
-         &lt;<a href="mailto:joecat@cmu.edu">joecat@cmu.edu</a>&gt;
-	<br />
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.ORG">phk@FreeBSD.ORG</a>&gt;
-	</p>
-      <p>A simple lexer and parser have almost been completed. Also
-      significant planing for future additions to K have been thought
-      up.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the lexer and parser</li><li>Implement the #! preprocessor function</li><li>Add lint like functionality to the preprocessor</li><li>Add style(9) checking to the preprocessor</li><li>Allow for detection of unused #includes</li></ol><hr /><h2><a name="Linuxolator-kernel-update-to-match-functionality-of-2.6.x" href="#Linuxolator-kernel-update-to-match-functionality-of-2.6.x" id="Linuxolator-kernel-update-to-match-functionality-of-2.6.x">Linuxolator kernel update to match functionality of
-    2.6.x</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/RomanDivacky" title="http://wiki.freebsd.org/RomanDivacky">Summer of Code proposal</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/RomanDivacky" title="Summer of Code proposal">http://wiki.freebsd.org/RomanDivacky</a></td></tr></table><p>
-	Contact:
-          Roman
-
-          Divacky
-         &lt;<a href="mailto:rdivacky@freebsd.org">rdivacky@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@freebsd.org">netchild@freebsd.org</a>&gt;
-	</p>
-      <p>FreeBSD linux emulation layer (linuxolator) currently implements
-      most of the functionality necessary to emulate 2.4.2 linux kernel,
-      but linux world has moved forward and current linux world requires
-      2.6.x features. The aim of this SoC task is to make Fedora Core 4
-      linux-base to be able to run with 2.6.x kernel. Currently this
-      means extending clone() syscall and implement pthread related
-      things. This involves TLS implementation (sys_set_thread_area
-      syscall) and possibly tid manipulation (used for pthread_join etc.)
-      and finally futexes (linux fast user-space mutexes implementation).
-      This should enable pthread-linked programs to work. After this is
-      done there may be other things necessary to implement however, only
-      time will tell. I am funded by google.com in their SoC to do this
-      work and I'll continue to work on this after the summer hopefully
-      as a part of my MSc. thesis.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the TLS thing + other thread related things (tid comes
-      to mind and looks necessary for pthread to work)</li><li>Futexes also look necessary for pthread to work</li><li>maybe other things to be able to run basic programs under
-      2.6.16 linuxolator</li></ol><hr /><h2><a name="Nss-LDAP-importing-and-nsswitch-subsystem-improvement" href="#Nss-LDAP-importing-and-nsswitch-subsystem-improvement" id="Nss-LDAP-importing-and-nsswitch-subsystem-improvement">Nss-LDAP importing and nsswitch subsystem improvement</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/LdapCachedDetailedDescription" title="http://wiki.freebsd.org/LdapCachedDetailedDescription">Wiki-pages containing an up-to-date information about project implementation details.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/LdapCachedDetailedDescription" title="Wiki-pages containing an up-to-date information about project implementation details.">http://wiki.freebsd.org/LdapCachedDetailedDescription</a></td></tr><tr><td><a href="http://wiki.freebsd.org/MichaelBushkov" title="http://wiki.freebsd.org/MichaelBushkov"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/MichaelBushkov" title="">http://wiki.freebsd.org/MichaelBushkov</a></td></tr></table><p>
-	Contact:
-          Michael
-
-          Bushkov
-         &lt;<a href="mailto:bushman@FreeBSD.org">bushman@FreeBSD.org</a>&gt;
-	</p>
-      <p>The basic goals of this SoC 2006 project are moving
-      nsswitch-modules out of the libc, extending the caching daemon and
-      importing nss_ldap into the base source tree. 2 milestones of the
-      project are currently completed.</p>
-
-      <p>1. Nss-modules were successfully moved out of the libc into the
-      separate dynamic libraries. In order for static binaries to work
-      properly (they can't use dynamic nss-modules), nss-modules are
-      linked statically into the libc.a. As the side-effect of
-      nss-modules separation, getipnodeby***() functions were rewritten
-      to use gethostby***() functions and not the nsdispatch(3) call.
-      Caching daemon's "perform-actual-lookups" option was extended to
-      support all implemented nsswitch databases.</p>
-
-      <p>2. A set of regressions tests was made to test nsswitch-related
-      functions. These tests are also capable of testing the stability of
-      these functions' behaviour after the system upgrade.</p>
-    <h3>Open tasks:</h3><ol><li>Import nss_ldap into the sources tree.</li><li>Improve the caching daemon's performance.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="DTrace" href="#DTrace" id="DTrace">DTrace</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jb/dtrace/index.html" title="http://people.freebsd.org/~jb/dtrace/index.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jb/dtrace/index.html" title="">http://people.freebsd.org/~jb/dtrace/index.html</a></td></tr></table><p>
-	Contact:
-          John
-
-          Birrell
-         &lt;<a href="mailto:jb@freebsd.org">jb@freebsd.org</a>&gt;
-	</p>
-      <p>Anonymous enablings now work. There is a new option in the boot
-      loader menu to load the DTrace modules and trace the kernel boot
-      process.</p>
-
-      <p>Sun Microsystems has been very supportive of the FreeBSD port
-      and has generously provided a Sun Fire T2000 server to allow Kip
-      Macy's sun4v port to be merged into the DTrace project tree.</p>
-
-      <p>The DTrace project tree sources are now exported to
-      cvsup10.freebsd.org</p>
-
-      <p>Refer to the project page for more details.</p>
-    <h3>Open tasks:</h3><ol><li>Current effort centres around making DTrace useful for the
-      sun4v porting effort which has shown up scalability issues with the
-      current FreeBSD SMP implementation. DTrace should be ideal for
-      analysing those issues.</li></ol><hr /><h2><a name="Embedded-FreeBSD" href="#Embedded-FreeBSD" id="Embedded-FreeBSD">Embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.embeddedfreebsd.org/" title="http://www.embeddedfreebsd.org/">Main Site</a></td><td>
-	    URL: <a href="http://www.embeddedfreebsd.org/" title="Main Site">http://www.embeddedfreebsd.org/</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	</p>
-      <p>There are several projects moving forward in the embedded area.
-      For now the main location for new information is
-      www.embeddedfreebsd.org. We have also created a new mailing list,
-      <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-embedded" shape="rect">
-      freebsd-embedded@freebsd.org</a>
-
-      , which is meant to eventually replace the freebsd-small. A call
-      was put out on small for people to move to embedded.</p>
-    <h3>Open tasks:</h3><ol><li>Update Developers Handbook with information on building
-      embedded versions of FreeBSD</li><li>Help with the MIPS port</li><li>Help with the ARM port</li><li>Investigate an SH port (requested by folks in Japan where the
-      Hitachi SH processor is quite popular in embedded)</li></ol><hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/audit.html" title="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit Web Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/audit.html" title="TrustedBSD Audit Web Page">http://www.TrustedBSD.org/audit.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Wayne
-
-          Salamon
-         &lt;<a href="mailto:wsalamon@FreeBSD.org">wsalamon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Christian
-
-          Peron
-         &lt;<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>&gt;
-	</p>
-      <p>TrustedBSD Audit provides fine-grained security event auditing
-      in FreeBSD 7.x, with a planned merge to 6.x for FreeBSD 6.2. Work
-      performed in the last three months:
-      <ul>
-        <li>Per audit pipe preselection allows IDS applications to
-        configure audit record selection per-pipe, new auditpipe.4
-        document.</li>
-
-        <li>audit_submit library call to reduce complexity of adding
-        audit support to applications.</li>
-
-        <li>Significant cleanup, bug fixing, locking improvements, token
-        parsing and generation improvements.</li>
-
-        <li>Solaris subject token compatibility, extended address
-        support.</li>
-
-        <li>Auditing of extended attributes calls, ACL support a work in
-        progress.</li>
-
-        <li>OpenBSM 1.0 alpha 7 integrated into CVS.</li>
-
-        <li>OpenBSM test tools in progress.</li>
-
-        <li>Experimental auditeventd which allows shared object plug-ins
-        to subscribe to live audit events via a shared pipe in order to
-        support the easy authoring of simple intrusion detection and
-        monitoring components.</li>
-      </ul>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Bring audit event daemon API and implementation to maturity.
-      Currently these are not installed by default in the CVS-merged
-      version.</li><li>Complete system call coverage.</li><li>Allow finer-grained configuration of what is audited:
-      implement control flags regarding paths, execve arguments,
-      environmental variables.</li><li>Support for auditing MAC policy data.</li><li>Additional user space application coverage, such as
-      application layer audit events from adduser, rmuser, pw,
-      etc.</li></ol><hr /><br /><h1><a name="Network-infrastructure" href="#Network-infrastructure" id="Network-infrastructure">Network infrastructure</a></h1><br /><h2><a name="FAST_IPSEC-Upgrade" href="#FAST_IPSEC-Upgrade" id="FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html" title="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html"></a></td><td>
-	    URL: <a href="http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html" title="">http://sources.zabbadoz.net/freebsd/ipv6/fast-ipsec.html</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>&gt;
-	</p>
-      <p>Continuing to add IPv6 support to FAST_IPSEC. Test environment
-      is now stable. Can build and run kernels with FAST_IPSEC and INET6
-      enabled but IPSec in IPv6 is now broken and being worked on.</p>
-    <h3>Open tasks:</h3><ol><li>Complete move to FAST_IPSEC type processing for IPv6. This is
-      complicated by the structure of the IPv6 code itself which, unlike
-      IPv4 splits transport and tunnel mode processing across the output
-      routine.</li></ol><hr /><h2><a name="FreeBSD-NFS-Status-Report" href="#FreeBSD-NFS-Status-Report" id="FreeBSD-NFS-Status-Report">FreeBSD NFS Status Report</a></h2><p>
-	Contact:
-          Chuck
-
-          Lever
-         &lt;<a href="mailto:cel@FreeBSD.org">cel@FreeBSD.org</a>&gt;
-	</p>
-      <p>Mohan Srinivasan committed his changes to make the NFSv2/3 client
-      MP safe to HEAD this quarter. Changes may be back-ported to 6.x
-      soon.</p>
-
-      <p>Robert Watson and Chuck Lever held a discussion about the future
-      of the in-kernel NFSv4 client during BSDCan 2006. The current NFSv4
-      client is unmaintained. Chuck also pointed out the long series of
-      unfixed PRs against the legacy client (NFSv2/3). These are at the
-      top of his priority list. Robert is also interested in making
-      NFSv4-style ACLs the lingua franca for FreeBSD file systems. There
-      was some discussion about integrating Rick MacKlem's NFSv4 server
-      into 7.x.</p>
-
-      <p>Chuck Lever became a full source committer during this
-      quarter.</p>
-    <hr /><h2><a name="IPv6-cleanup" href="#IPv6-cleanup" id="IPv6-cleanup">IPv6 cleanup</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sources.zabbadoz.net/freebsd/ipv6/" title="http://sources.zabbadoz.net/freebsd/ipv6/">Project summary</a></td><td>
-	    URL: <a href="http://sources.zabbadoz.net/freebsd/ipv6/" title="Project summary">http://sources.zabbadoz.net/freebsd/ipv6/</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ipv6" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ipv6">P4 workspace for future changes</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ipv6" title="P4 workspace for future changes">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ipv6</a></td></tr></table><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>&gt;
-	</p>
-      <p>Initial changes include:
-      <ul>
-        <li>Changed ip6_sprintf to no longer return a static buffer.</li>
-
-        <li>Started to adopt in6_pcb* code to what we have for legacy
-        IP.</li>
-      </ul>
-
-      <br clear="none" />
-
-      Next steps will be to reduce the number of global variables and
-      caches.</p>
-    <h3>Open tasks:</h3><ol><li>Cleanup code.</li><li>Make everything MPSafe.</li><li>Enhance things and add new features.</li></ol><hr /><h2><a name="Multi-IP-v4/v6-jails" href="#Multi-IP-v4/v6-jails" id="Multi-IP-v4/v6-jails">Multi-IP v4/v6 jails</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/jail" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/jail">P4 workspace</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/jail" title="P4 workspace">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/jail</a></td></tr></table><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>&gt;
-	</p>
-      <p>As an intermediate step until FreeBSD will have full network
-      stack virtualisation this work shall provide support for multi-IP
-      IPv4/v6 jails.</p>
-
-      <p>These changes are based on Pawel Jakub Dawidek's work for
-      multi-IPv4 jails and some initial work from Olivier Houchard for
-      single-IPv6 jails.</p>
-
-      <p>The changes need some more testing but basically things
-      work.</p>
-
-      <p>This is not considered to be the right thing todo so do
-      <b>not</b>
-
-      ask for official support or if this will be committed to the
-      FreeBSD source repository.
-      <br clear="none" />
-
-      After some more cleanup of non-jail related IPv6 changes I will
-      publish a patch for HEAD and perhaps RELENG_6 for everyone who
-      wants to give it a try anyway.</p>
-    <h3>Open tasks:</h3><ol><li>(IPv6) related security checks.</li><li>Write some tests. Especially IPv6 changes need more
-      testing.</li><li>Check what general changes might need merging to HEAD.</li></ol><hr /><h2><a name="SCTP-Integration" href="#SCTP-Integration" id="SCTP-Integration">SCTP Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.sctp.org/" title="http://www.sctp.org/">Stream Transmission Control Protocol</a></td><td>
-	    URL: <a href="http://www.sctp.org/" title="Stream Transmission Control Protocol">http://www.sctp.org/</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Randall
-
-          Stewart
-         &lt;<a href="mailto:rrs@cisco.com">rrs@cisco.com</a>&gt;
-	</p>
-      <p>For the last several months Randall Stewart has been working in
-      HEAD and STABLE to get us ready to integrate the SCTP protocol
-      (Stream Transmission Control Protocol) into FreeBSD. He is
-      currently working on a patch to share with a wider audience but
-      needs to do some integration work first. Randall has a provisional
-      commit bit and will be working with gnn on getting code committed
-      to the HEAD of the tree.</p>
-    <h3>Open tasks:</h3><ol><li>When this gets integrated it needs lots of testers.</li></ol><hr /><h2><a name="Wireless-Networking" href="#Wireless-Networking" id="Wireless-Networking">Wireless Networking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@errno.com">sam@errno.com</a>&gt;
-	</p>
-      <p>The wireless support has been stable for a while so most work has
-      focused on bug fixing and improving legacy drivers.</p>
-
-      <p>Max Laier and I worked on improving support for Intel wireless
-      cards. The results of this work included significant improvements
-      to the iwi(4) driver (for 2195/2200 parts) and the firmware(9)
-      facility for managing loadable device firmware. There is also an
-      updated ipw(4) that has improvements similar to those done for iwi
-      that is in early test. Support for the latest Intel devices, the
-      3945 pci-express cards, is planned for later this summer.</p>
-
-      <p>Atheros support was updated with a new hal that fixes a few
-      minor issues and provides known working builds for SPARC, PPC, and
-      ARM platforms. There is also working MIPS support that will be used
-      when the MIPS port is ready to test. Otherwise one useful bug was
-      fixed that affected AP operation with associated stations operating
-      in power save mode.</p>
-
-      <p>wpa_supplicant and hostapd were updated to the latest stable
-      build releases from Jouni Malinen.</p>
-
-      <p>Experimental changes to support injection of raw 802.11 frames
-      using bpf were posted for comment. This work was done in
-      collaboration with Andrea Bittau.</p>
-    <h3>Open tasks:</h3><ol><li>Legacy drivers such as wi are languishing and need
-      maintainers. This is prerequisite to bringing in new 802.11
-      features such as improved scanning and virtual ap.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Giant-Less-UFS-with-Quotas" href="#Giant-Less-UFS-with-Quotas" id="Giant-Less-UFS-with-Quotas">Giant-Less UFS with Quotas</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~kib/quotagiant" title="http://people.freebsd.org/~kib/quotagiant"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~kib/quotagiant" title="">http://people.freebsd.org/~kib/quotagiant</a></td></tr></table><p>
-	Contact:
-          Konstantin
-
-          Belousov
-         &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The patches to allow UFS operate with quotas in Giant-less mode
-      are brewed for long now. Since recent huge pile of fixes into
-      snapshots code, I think the problems you could encounter are caused
-      solely by the patch.</p>
-
-      <p>Aside performance benefits, patch has another one, much more
-      valuable. It makes UFS operating in one locking regime whatever
-      options are compiled into kernel. I think, in long term, that would
-      lead to better stability of the system.</p>
-    <h3>Open tasks:</h3><ol><li>I need testers feedback. Both stability reports and
-      performance measurements are welcomed !</li></ol><hr /><h2><a name="Giant-Less-USB-framework" href="#Giant-Less-USB-framework" id="Giant-Less-USB-framework">Giant-Less USB framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO">Current files</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="Current files">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://www.turbocat.net/~hselasky/usb4bsd" title="http://www.turbocat.net/~hselasky/usb4bsd">Easy to install tarballs</a></td><td>
-	    URL: <a href="http://www.turbocat.net/~hselasky/usb4bsd" title="Easy to install tarballs">http://www.turbocat.net/~hselasky/usb4bsd</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@c2i.net">hselasky@c2i.net</a>&gt;
-	</p>
-      <p>For some time now I have been working on converting the existing
-      USB device drivers to my new and mutex enabled USB API. I have
-      converted "ulpt", "ums", "uhid", "ukbd", "ugen", "uaudio", and a
-      few others. Around 10 USB device drivers are left to convert. Most
-      of these are network device drivers.</p>
-
-      <p>At the present moment I am working on getting scatter and
-      gathering support working for all USB host controllers. Scatter and
-      gathering means that one allocates PAGE_SIZE bytes of memory at a
-      time, and then fills these memory blocks up as much as possible
-      with USB host controller structures and buffers. This should solve
-      problems allocating DMA-able memory when the system memory becomes
-      fragmented.</p>
-    <h3>Open tasks:</h3><ol><li>If anyone wants to help convert the remaining USB device
-      drivers, please drop me an e-mail.</li></ol><hr /><h2><a name="GJournal" href="#GJournal" id="GJournal">GJournal</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html" title="http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html">Announce.</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html" title="Announce.">http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~pjd/patches/gjournal.patch" title="http://people.freebsd.org/~pjd/patches/gjournal.patch">Patches for HEAD.</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~pjd/patches/gjournal.patch" title="Patches for HEAD.">http://people.freebsd.org/~pjd/patches/gjournal.patch</a></td></tr><tr><td><a href="http://people.freebsd.org/~pjd/patches/gjournal6.patch" title="http://people.freebsd.org/~pjd/patches/gjournal6.patch">Patches for RELENG_6.</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~pjd/patches/gjournal6.patch" title="Patches for RELENG_6.">http://people.freebsd.org/~pjd/patches/gjournal6.patch</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>GJournal is a GEOM class which provides journaling for GEOM
-      providers. It can also be used to journal various file systems with
-      just a minimal filesystem-specific portion of code. Currently only
-      UFS journaling is implemented on top of gjournal. Being
-      filesystem-independent and operating below the file system level,
-      gjournal has no way to distinguish data from metadata, thus it
-      journals both. One of the nice things about gjournal is that it
-      works reliable even on disks with enabled write cache, which is
-      often not the case for journalled file systems. And remember... fsck
-      no more.</p>
-    <h3>Open tasks:</h3><ol><li>I'm looking for feedback from users who can test gjournal in
-      various workloads.</li></ol><hr /><h2><a name="Gvinum-improvements" href="#Gvinum-improvements" id="Gvinum-improvements">Gvinum improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Ulf
-
-          Lilleengen
-         &lt;<a href="mailto:lulf@stud.ntnu.no">lulf@stud.ntnu.no</a>&gt;
-	</p>
-      <p>I have been working on porting missing features in gvinum from
-      vinum, as well as adding new features.</p>
-
-      <p>So far the resetconfig, detach, dumpconfig, setstate (on plexes
-      and volumes) and stop commands have been implemented, as well as
-      some other minor fixes. The attach command is currently being
-      implemented, and started on disk-grouping. Currently most of this
-      is in p4, but patches will be submitted as soon as possible.</p>
-    <hr /><h2><a name="Sound-subsystem-improvements" href="#Sound-subsystem-improvements" id="Sound-subsystem-improvements">Sound subsystem improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~ariff/" title="http://people.FreeBSD.org/~ariff/">Some patches.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~ariff/" title="Some patches.">http://people.FreeBSD.org/~ariff/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/projects/ideas/" title="http://www.FreeBSD.org/projects/ideas/">The FreeBSD Project Ideas List.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/ideas/" title="The FreeBSD Project Ideas List.">http://www.FreeBSD.org/projects/ideas/</a></td></tr><tr><td><a href="http://www.leidinger.net/FreeBSD/hdac_20060525.tbz" title="http://www.leidinger.net/FreeBSD/hdac_20060525.tbz">Rudimentary HDA support.</a></td><td>
-	    URL: <a href="http://www.leidinger.net/FreeBSD/hdac_20060525.tbz" title="Rudimentary HDA support.">http://www.leidinger.net/FreeBSD/hdac_20060525.tbz</a></td></tr></table><p>
-	Contact:
-          Ariff
-
-          Abdullah
-         &lt;<a href="mailto:ariff@FreeBSD.org">ariff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Multimedia
-
-          Mailinglist
-         &lt;<a href="mailto:multimedia@FreeBSD.org">multimedia@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report we fixed some more bugs, added
-      basic support for envy24 chips and cleaned up the source for the
-      emu10kx driver in the ports to make it ready for import into the
-      base system.</p>
-
-      <p>We also got some patches with a little bit of infrastructure for
-      Intel HDA support. It's not finished and also not usable by end
-      users yet.</p>
-    <h3>Open tasks:</h3><ol><li>Have a look at the sound related entries on the ideas
-      list.</li><li>sndctl(1): tool to control non-mixer parts of the sound
-      system (e.g. spdif switching, virtual-3D effects) by an user
-      (instead of the sysctl approach in -current); pcmplay(1),
-      pcmrec(1), pcmutil(1).</li><li>Plugable FEEDER infrastructure. For ease of debugging various
-      feeder stuff and/or as userland library and test suite.</li><li>Support for new hardware (envy24, Intel HDA).</li></ol><hr /><h2><a name="SSE2-Kernel-support" href="#SSE2-Kernel-support" id="SSE2-Kernel-support">SSE2 Kernel support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/projects/ideas/#p-memcpy" title="http://www.freebsd.org/projects/ideas/#p-memcpy">Project details</a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/ideas/#p-memcpy" title="Project details">http://www.freebsd.org/projects/ideas/#p-memcpy</a></td></tr><tr><td><a href="http://unix.derkeiler.com/Mailing-Lists/FreeBSD/arch/2006-05/msg00109.html" title="http://unix.derkeiler.com/Mailing-Lists/FreeBSD/arch/2006-05/msg00109.html">Ongoing development</a></td><td>
-	    URL: <a href="http://unix.derkeiler.com/Mailing-Lists/FreeBSD/arch/2006-05/msg00109.html" title="Ongoing development">http://unix.derkeiler.com/Mailing-Lists/FreeBSD/arch/2006-05/msg00109.html</a></td></tr></table><p>
-	Contact:
-          Attilio
-
-          Rao
-         &lt;<a href="mailto:attilio@freebsd.org">attilio@freebsd.org</a>&gt;
-	</p>
-      <p>Some
-      <strong>FPU system</strong>
-
-      and
-      <strong>kernel memcpy/copyin/copyout</strong>
-
-      changes have been performed. In particular, a per-CPU save area has
-      been introduced (protected with an interlock) in order to assure a
-      stable saving mechanism.
-      <strong>copyout/copyin</strong>
-
-      have changed in order to use vectorised version of
-      <strong>memcpy</strong>
-
-      and an xmm version of memcpy has been provided.</p>
-    <h3>Open tasks:</h3><ol><li>Benchmarks on different versions of xmm copy, in particular
-      showing differences between UP and SMP architectures (evaluating
-      possibility to add block prefetch, non-temporal hints usage,
-      etc.)</li><li>Modifying npxdna trap handler in order to recognise xmm
-      environment usage and replace fxsave with 8-movdqa</li></ol><hr /><h2><a name="XFS-for-FreeBSD" href="#XFS-for-FreeBSD" id="XFS-for-FreeBSD">XFS for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~rodrigc/xfs/" title="http://people.freebsd.org/~rodrigc/xfs/">XFS for FreeBSD</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~rodrigc/xfs/" title="XFS for FreeBSD">http://people.freebsd.org/~rodrigc/xfs/</a></td></tr></table><p>
-	Contact:
-          Russell
-
-          Cattelan
-         &lt;<a href="mailto:cattelan@xfs.org">cattelan@xfs.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Kabaev
-         &lt;<a href="mailto:kan@freebsd.org">kan@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Craig
-
-          Rodrigues
-         &lt;<a href="mailto:rodrigc@freebsd.org">rodrigc@freebsd.org</a>&gt;
-	</p>
-      <p>The XFS for FreeBSD project is an effort to port the publicly
-      available GPL'd sources to SGI's XFS filesystem to FreeBSD.</p>
-
-      <p>In December, we imported a version of XFS into FreeBSD-CURRENT
-      which allows FreeBSD to mount an XFS filesystem as read-only.</p>
-
-      <p>As a side effort, we have been continuing on the work that PHK
-      started to clean up the mount code in FreeBSD. We can use the
-      existing FreeBSD mount(8) utility to mount an XFS partition,
-      without introducing a new mount_xfs utility.</p>
-    <h3>Open tasks:</h3><ol><li>We need to implement support for writing to XFS
-      partitions</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="FreeBSD-list-of-projects-and-ideas-for-volunteers" href="#FreeBSD-list-of-projects-and-ideas-for-volunteers" id="FreeBSD-list-of-projects-and-ideas-for-volunteers">FreeBSD list of projects and ideas for volunteers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/ideas/" title="http://www.FreeBSD.org/projects/ideas/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/ideas/" title="">http://www.FreeBSD.org/projects/ideas/</a></td></tr></table><p>
-	Contact:
-          Joel
-
-          Dahl
-         &lt;<a href="mailto:joel@FreeBSD.org">joel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD list of projects and ideas for volunteers is doing
-      well. Several items were picked up by volunteers and have found
-      their way into the tree. Others are under review or in progress. We
-      are looking forward to hear about new ideas, people willing to act
-      as technical contacts for generic topics such as USB or specific
-      entries (already existing or newly created) and suggestions for
-      existing entries or completion reports for (parts of) an entry.</p>
-    <h3>Open tasks:</h3><ol><li>Add more ideas.</li><li>Find more technical contacts.</li><li>Find people willing to review/test implementations of
-      (somewhat) finished items.</li></ol><hr /><h2><a name="Hungarian-translation-of-the-webpages" href="#Hungarian-translation-of-the-webpages" id="Hungarian-translation-of-the-webpages">Hungarian translation of the webpages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://gabor.t-hosting.hu/data/hu/" title="http://gabor.t-hosting.hu/data/hu/">Current status</a></td><td>
-	    URL: <a href="http://gabor.t-hosting.hu/data/hu/" title="Current status">http://gabor.t-hosting.hu/data/hu/</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The translated webpage is almost ready now. This Hungarian
-      translation is a "lite" version of the original English webpages,
-      since there are parts that are irrelevant for the Hungarian
-      community, or has pieces of data that change quickly, so it's no
-      use to translate these pages now, maybe later, if we have more
-      Hungarian contributors, but this webpage would be a good starting
-      point in translating the documentations, and we need a good place
-      to put translated documentations anyway.</p>
-
-      <p>I'm going to be very busy with SoC this summer, but I'll try to
-      find people that can help me out in this project. Any help
-      appreciated.</p>
-    <h3>Open tasks:</h3><ol><li>The remaining important pages should be translated.</li><li>The press/media/news sections should be restructured somehow
-      to being fed from the English webapges, since we don't have too
-      much Hungarian resource to make these up to date.</li><li>There's a rendering issue when browsing the pages with
-      JavaScript enabled, but this can be server-side for me, this should
-      be investigated as well.</li></ol><hr /><br /><h1><a name="Userland-programs" href="#Userland-programs" id="Userland-programs">Userland programs</a></h1><br /><h2><a name="Low-overhead-performance-monitoring-tools" href="#Low-overhead-performance-monitoring-tools" id="Low-overhead-performance-monitoring-tools">Low-overhead performance monitoring tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/LibElf" title="http://wiki.freebsd.org/LibElf">Wiki page tracking LibELF</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/LibElf" title="Wiki page tracking LibELF">http://wiki.freebsd.org/LibElf</a></td></tr><tr><td><a href="http://wiki.freebsd.org/PmcTools" title="http://wiki.freebsd.org/PmcTools">Wiki page for PmcTools</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/PmcTools" title="Wiki page for PmcTools">http://wiki.freebsd.org/PmcTools</a></td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement/">PMC Tools Project</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="PMC Tools Project">http://people.freebsd.org/~jkoshy/projects/perf-measurement/</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>As an intermediate step towards implementing support for
-      callgraphs and cross-architecture performance measurements, I am
-      creating a BSD-licensed library for ELF parsing &amp; manipulation.
-      This library will implement the SysV/SVR4 (g)ELF[3] API.</p>
-
-      <p>Current status: Implementation of the library is in progress. A
-      TET-based test suite for the API and manual pages documenting the
-      library's interfaces are being concurrently created.</p>
-
-      <p>Work is being done in FreeBSD's Perforce repository. I hope to
-      be ready for general review by the end of July '06.</p>
-    <h3>Open tasks:</h3><ol><li>Reviewers are needed for the code and the test suite. If you
-      have extensions to the stock SysV/SVR4 ELF(3) API that you would
-      like to see in -lelf, please send mail.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/platforms/ppc.html" title="http://www.freebsd.org/platforms/ppc.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/platforms/ppc.html" title="">http://www.freebsd.org/platforms/ppc.html</a></td></tr></table><p>
-	Contact:
-          Peter
-
-          Grehan
-         &lt;<a href="mailto:grehan@freebsd.org">grehan@freebsd.org</a>&gt;
-	</p>
-      <p>The project is slowly starting to ramp up after a long
-      move-induced hiatus.</p>
-
-      <p>Alan Cox has almost completed making the pmap module
-      Giant-free.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freshports.org/" title="http://www.freshports.org/">FreshPorts</a></td><td>
-	    URL: <a href="http://www.freshports.org/" title="FreshPorts">http://www.freshports.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>FreshPorts has seen several new features recently:
-      <ul>
-        <li>caching implemented at web application level to reduce load
-        on the database server and to serve pages faster</li>
-
-        <li>searching expanded to find all the ports that this maintainer
-        maintains, and all the commits by a particular committer</li>
-      </ul>
-
-      <br clear="none" />
-
-      Most of the work lately has been optimisation, either at the
-      database level or at the web application level.</p>
-
-      <p>A 2U server was recently donated to the
-      <a href="http://www.freshports.org" shape="rect">FreshPorts</a>
-
-      /
-      <a href="http://www.freshsource.org" shape="rect">FreshSource</a>
-
-      /
-      <a href="http://www.freebsddiary.org/" shape="rect">FreeBSD Diary</a>
-
-      /
-      <a href="http://www.bsdcan.org/" shape="rect">BSDCan</a>
-
-      group. We have also received a RAID card. Now we're looking for
-      some hard drives.</p>
-
-      <p>Over the past few weeks, work has concentrated on benchmarking
-      the new server and getting it ready for production. Eventually it
-      will need a new home as I don't really want it running in my
-      basement all the time (it's really loud!).</p>
-
-      <p>Thanks to
-      <a href="http://www.ixsystems.com" shape="rect">iXsystems</a>
-
-      and
-      <a href="http://www.3ware.com" shape="rect">3Ware</a>
-
-      for their contributions to this project.</p>
-    <h3>Open tasks:</h3><ol><li>We would like some more hardware (CPUs and HDD). Details
-      <a href="http://www.freebsddiary.org/sponsors-wanted.php" shape="rect">here</a>
-      </li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://beta.inerd.com/portscout/" title="http://beta.inerd.com/portscout/">portscout</a></td><td>
-	    URL: <a href="http://beta.inerd.com/portscout/" title="portscout">http://beta.inerd.com/portscout/</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Erwin
-
-          Lansing
-         &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>During this time, a huge number of ports PRs were committed,
-      bringing us back down below 800 for the first time since the
-      5.5/6.1 release cycle. This is due to a great deal of work,
-      especially from some of our newest committers.</p>
-
-      <p>This is all the more notable given the fact that we have been
-      adding new ports at a rapidly accelerating rate. We have now
-      exceeded the 15,000 port mark!</p>
-
-      <p>Three sets of changes have been added to the infrastructure,
-      including updates of default versions of MySQL, PHP, LDAP, and
-      linux_base, and numerous bugfixes and improvements. About 2 dozen
-      portmgr PRs were closed due to this.</p>
-
-      <p>In addition, a large-impact commit was made that attempts to
-      move us to a single libtool that is as unmodified from 'stock'
-      libtool as we can. Plans are also in place to do this for the
-      autotools.</p>
-
-      <p>Several people are at work on implementing the modularised xorg
-      ports. Most of the work is done but several key pieces remain. Once
-      this is finished, an -exp regression test will be needed (most
-      likely, more than one :-) ) It is possible that before this we will
-      need to do a regression test that moves X11BASE back into
-      LOCALBASE. This is still under study.</p>
-
-      <p>G�bor K�vesd�n started a Google Summer of Code
-      project on some highly needed improvements on the ports infrastructure
-      (see elsewhere in this report). As this is a long term project, gtetlow
-      kindly imported the most important ports infrastructure files into
-      perforce to ease development. Other developers are encouraged to
-      use perforce for ports development, especially as it can help
-      keeping patches up-to-date while going stale in GNATS. Even though
-      linimon has been pushing hard on running experimental builds on the
-      test cluster, it will take some time to work through the
-      backlog.</p>
-
-      <p>erwin added a ports section to the list of projects and ideas
-      for volunteers at the FreeBSD website. Have a look if you want to
-      work on the ports system. Don't hesitate to send additional ideas,
-      and committers are encouraged to add themselves as technical
-      contacts.</p>
-
-      <p>sem adopted portupgrade after it had been neglected for some
-      time and has been very active on upgrades and bugfixing.</p>
-
-      <p>dougb has continued to enhance his portmaster script and people
-      are finding success with it; although not designed to be as
-      full-featured as portupgrade, it does seem to be easier to
-      understand and use.</p>
-
-      <p>shaun has contributed portscout, a scanner for updated
-      distfiles, to the ports collection.</p>
-
-      <p>marcus upgraded GNOME to 2.14.1.</p>
-
-      <p>As well, there have been new releases of the ports tinderbox
-      code.</p>
-
-      <p>edwin has been hard at work on a PR-autoassigner for ports PRs,
-      which has saved a lot of time and been well-received. It has now
-      been installed on a freebsd.org machine (hub).</p>
-
-      <p>linimon has been more active in pursuing maintainer-timeouts,
-      and has reset a number of inactive maintainers, with more in the
-      pipeline. The intent is to try to reduce the number of PRs that sit
-      around unanswered for two weeks. In almost all cases the resets are
-      due to no response at all; maintainers who are merely "busy" are
-      not the source of most of these problems, and deserve the benefit
-      of the doubt. Some of the maintainers that have been reset haven't
-      contributed in months or even years.</p>
-
-      <p>We have added 10 (!) new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>We need help getting back to our modern low of 500
-      PRs.</li><li>We have over 4,000 unmaintained ports (see, for instance,
-      <a href="http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports@FreeBSD.org" shape="rect">
-      the list on portsmon</a>
-
-      ). We are always looking for dedicated volunteers to adopt at least
-      a few ports.</li><li>We can always use help with infrastructural enhancements. See
-      the ports section of
-      <a href="http://www.freebsd.org/projects/ideas/" shape="rect">the list of
-      projects and ideas</a>
-
-      .</li></ol><hr /><h2><a name="Update-of-the-Linux-userland-infrastructure-in-the-Ports-Collection" href="#Update-of-the-Linux-userland-infrastructure-in-the-Ports-Collection" id="Update-of-the-Linux-userland-infrastructure-in-the-Ports-Collection">Update of the Linux userland infrastructure in the Ports
-    Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Boris
-
-          Samorodov
-         &lt;<a href="mailto:bsam@FreeBSD.org">bsam@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Emulation
-
-          Mailinglist
-         &lt;<a href="mailto:emulation@FreeBSD.org">emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>We updated the default linux base port to Fedora Core 4 and the
-      default linux X11 libs port to the X.org RPM in FC4.</p>
-
-      <p>An update to FC5 or FC6 has to wait until the kernel got support
-      for syscalls of a newer linux kernel. See the corresponding SoC
-      project report for more.</p>
-    <hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="BSDInstaller" href="#BSDInstaller" id="BSDInstaller">BSDInstaller</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="http://wiki.freebsd.org/moin.cgi/BSDInstaller"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/moin.cgi/BSDInstaller" title="">http://wiki.freebsd.org/moin.cgi/BSDInstaller</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Turner
-         &lt;<a href="mailto:soc-andrew@FreeBSD.org">soc-andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report ports have been created for all
-      parts of the BSDInstaller except the backend.</p>
-
-      <p>A snapshot of the BSDInstaller was released during this quarter.
-      This has shown a number of bugs with the installation process. Most
-      have now been fixed.</p>
-    <hr /><h2><a name="pfSense" href="#pfSense" id="pfSense">pfSense</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pfsense.com" title="http://www.pfsense.com"></a></td><td>
-	    URL: <a href="http://www.pfsense.com" title="">http://www.pfsense.com</a></td></tr></table><p>
-	Contact:
-          Scott
-
-          Ullrich
-         &lt;<a href="mailto:sullrich@gmail.com">sullrich@gmail.com</a>&gt;
-	</p>
-      <p>pfSense is rapidly approaching release. We are down to a
-      handfull of bugs that should be fixed in the coming weeks. We
-      should have a release around the time of our 2nd annual hackathon
-      which is taking place on July 21st - July 28th. Many exciting
-      sub-projects are taking place within pfSense and the project is
-      gaining new developers monthly.</p>
-    <h3>Open tasks:</h3><ol><li>
-      <a href="http://cvstrac.pfsense.com/rptview?rn=6" shape="rect">
-      http://cvstrac.pfsense.com/rptview?rn=6</a>
-
-      lists the remaining open bugs.</li></ol><hr /><h2><a name="xscale-board-buy" href="#xscale-board-buy" id="xscale-board-buy">xscale board buy</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.gateworks.com/avila_gw2348_4.htm" title="http://www.gateworks.com/avila_gw2348_4.htm"></a></td><td>
-	    URL: <a href="http://www.gateworks.com/avila_gw2348_4.htm" title="">http://www.gateworks.com/avila_gw2348_4.htm</a></td></tr><tr><td><a href="http://www.netgate.com" title="http://www.netgate.com"></a></td><td>
-	    URL: <a href="http://www.netgate.com" title="">http://www.netgate.com</a></td></tr></table><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@errno.com">sam@errno.com</a>&gt;
-	</p>
-      <p>With the help of Jim Thompson of Netgate (
-      <a href="http://www.netgate.com/" shape="rect">http://www.netgate.com/</a>
-
-      ) the FreeBSD Foundation arranged a purchase of xscale-based boards
-      for folks interested in ARM support. Developers were able to
-      purchase boards at a reduced cost. The goals were to accelerate
-      and/or improve support for the ARM platform and to set forth at
-      least one board as a reference platform for the ARM support.
-      Netgate will be stocking lower-cost models of the board later in
-      the year (a special order was made for boards with only 2 mini-pci
-      slots).</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan" href="#BSDCan" id="BSDCan">BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/" title="http://www.bsdcan.org/">BSDCan</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/" title="BSDCan">http://www.bsdcan.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>
-      <a href="http://www.bsdcan.org/" shape="rect">BSDCan 2006</a>
-
-      continues to impress. Again this year, we had a good collection of
-      talks from a wide range of speakers. In all, we had over 200 people
-      from 14 different countries.</p>
-
-      <p>Our sponsorship pool continues to grow. This year we had
-      sponsorship from:
-      <ul>
-        <li>
-          <a href="http://www.usenix.org/" shape="rect">USENIX</a>
-        </li>
-
-        <li>
-          <a href="http://www.freebsdfoundation.org/" shape="rect">The FreeBSD
-          Foundation</a>
-        </li>
-
-        <li>
-          <a href="http://www.parse.com/" shape="rect">PARSE</a>
-        </li>
-
-        <li>
-          <a href="http://www.ixsystems.com/" shape="rect">iXsystems</a>
-        </li>
-
-        <li>
-          <a href="http://www.oreilly.com/" shape="rect">O'Reilly</a>
-        </li>
-
-        <li>
-          <a href="http://www.stevens-tech.edu/" shape="rect">Stevens Institute of
-          Technology</a>
-        </li>
-
-        <li>
-          <a href="http://www.ncircle.com/" shape="rect">nCircle</a>
-        </li>
-      </ul>
-
-      <br clear="none" />
-
-      The
-      <a href="http://www.bsdcan.org/2006/images/t-shirt.jpg" shape="rect">
-      t-shirts</a>
-
-      were very popular, with all of them going in very short time. Of
-      course, it helped that this year they were free, courtesy of
-      PARSE.</p>
-
-      <p>The 2007 planning has already begun and we look forward to
-      another popular and successful event.</p>
-
-      <p>My thanks to the 2006 program committee, the speakers, the
-      volunteers, the sponsors, and, of course, the attendees.</p>
-
-      <p>See you at BSDCan 2007.</p>
-    <hr /><h2><a name="EuroBSDCon-2006---November-10th---12th,-Milan,-Italy" href="#EuroBSDCon-2006---November-10th---12th,-Milan,-Italy" id="EuroBSDCon-2006---November-10th---12th,-Milan,-Italy">EuroBSDCon 2006 - November 10th - 12th, Milan, Italy</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon.org" title="http://www.eurobsdcon.org">Official Website</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org" title="Official Website">http://www.eurobsdcon.org</a></td></tr></table><p>
-	Contact:
-          Massimiliano
-
-          Stucchi
-         &lt;<a href="mailto:stucchi@eurobsdcon.org">stucchi@eurobsdcon.org</a>&gt;
-	</p>
-      <p>This year's EuroBSDCon will be held in Milan, Italy, on November
-      10th through 12th.</p>
-
-      <p>Hosted in the foggy northern Italy, the fifth EuroBSDCon aims at
-      being a new successful chapter in the itinerant series of European
-      BSD conferences.</p>
-
-      <p>EuroBSDCon represents the biggest gathering for BSD developers
-      from the old continent, as well as users and passionates from
-      around the World. It is also a chance to share experiences,
-      know-how, and cultures.</p>
-
-      <p>For the first time, parallel to the main event, an event for
-      wives/girlfriends/friends will be organised. It will consist of
-      guided tours of the city of Milan, a probable trip to Como and
-      visits to various museums. We're also working towards offering a
-      show at the Teatro alla Scala.</p>
-
-      <p>The FreeBSD developer summit will be also held on November
-      10th.</p>
-    <h3>Open tasks:</h3><ol><li>The Call For Papers is out, so everybody is invited to send
-      in papers or tutorials that might be of interest to the
-      community</li><li>The Conference Organisers are also looking for sponsors. Feel
-      free to contact oc@eurobsdcon.org in order to discover the
-      different sponsoring opportunities.</li></ol><hr /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the time since the last status report, four security
-      advisories have been issued concerning problems in the base system
-      of FreeBSD; of these, one problem was "contributed" code, while
-      three were in code maintained within FreeBSD. The Vulnerabilities
-      and Exposures Markup Language (VuXML) document has continued to be
-      updated by the Security Team and Ports Committers documenting new
-      vulnerabilities in the FreeBSD Ports Collection; since the last
-      status report, 71 new entries have been added, bringing the total
-      up to 757.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 4.11, FreeBSD 5.3, FreeBSD 5.4, FreeBSD 5.5,
-      FreeBSD 6.0, and FreeBSD 6.1. The respective End of Life dates of
-      supported releases are listed on the web site; of particular note,
-      FreeBSD 5.3 and FreeBSD 5.4 will cease to be supported at the end
-      of October 2006, while FreeBSD 6.0 will cease to be supported at
-      the end of November 2006.</p>
-    <hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/releng/" title="http://www.freebsd.org/releng/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releng/" title="">http://www.freebsd.org/releng/</a></td></tr><tr><td><a href="http://www.freebsd.org/releases/" title="http://www.freebsd.org/releases/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releases/" title="">http://www.freebsd.org/releases/</a></td></tr><tr><td><a href="http://www.freebsd.org/snapshots/" title="http://www.freebsd.org/snapshots/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/snapshots/" title="">http://www.freebsd.org/snapshots/</a></td></tr></table><p>
-	Contact:
-          Release Engineering Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The release engineering (RE) team announced the availability of
-      FreeBSD 5.5 and 6.1, both in May 2006. FreeBSD 5.5 is the last
-      planned release from the RELENG_5 branch in CVS. For the most part,
-      its main features consist of bugfixes, security patches, and minor
-      updates. We encourage users to move towards the 6.x series of
-      releases whenever practical. FreeBSD 6.1 is the latest of the
-      releases to come from the RELENG_6 branch in CVS. It includes
-      (among many other things) improved support for WiFi devices,
-      additional network and disk controller drivers, and a number of
-      fixes for filesystem stability. The next release to be issued from
-      this branch will be FreeBSD 6.2, which is currently scheduled for
-      September 2006.</p>
-
-      <p>The RE team is currently in a ``between releases'' mode. Current
-      activities include working with security-team@ on some errata fixes
-      for the RELENG_6_1 branch and producing snapshots of HEAD and
-      RELENG_6 at the start of each month.</p>
-
-      <p>Several personnel changes have taken place recently. Scott Long
-      has stepped down from his position on the RE team; we thank him for
-      his considerable efforts over the past four years. In his place,
-      Ken Smith has taken over the role of lead release engineer. Bruce
-      A. Mah has rejoined the RE team after a two-year sabbatical.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2006-06-2006-10.html b/website/content/en/status/report-2006-06-2006-10.html
deleted file mode 100644
index 3c7795975b..0000000000
--- a/website/content/en/status/report-2006-06-2006-10.html
+++ /dev/null
@@ -1,1715 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between June and
-    October 2006. This includes the conclusion of this year's Google
-    Summer of Code with 13 successful students. Some of last year's and
-    the current SoC participants have meanwhile joined the committer
-    ranks, kept working on their projects, and improving FreeBSD in
-    general.</p><p>This year's
-    <a href="http://www.eurobsdcon.org/" shape="rect">EuroBSDCon</a>
-
-    in Milan, Italy has meanwhile published an exciting program. Many
-    developers will be there to discuss these current and future projects
-    at the Developer Summit prior the conference. Next year's
-    conference calendar has a new entry - in addition to the now well
-    established
-    <a href="http://www.bsdcan.org/" shape="rect">BSDCan</a>
-
-    in Ottawa -
-    <a href="http://www.asiabsdcon.org/" shape="rect">AsiaBSDCon</a>
-
-    will take place in Tokyo at the beginning of March.</p><p>As we are closing in on FreeBSD 6.2 release many bugs are being
-    fixed and new features have been MFCed. On the other hand a lot of
-    the projects below already are focusing on FreeBSD 7.0 and promise
-    a lot of exciting news and features to come.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Summer-of-Code-Summary">Summer of Code Summary</a></li><li><a href="#Analyze-and-Improve-the-Interrupt-Handling-Infrastructure">Analyze and Improve the Interrupt Handling
-    Infrastructure</a></li><li><a href="#Bundled-PXE-Installer">Bundled PXE Installer</a></li><li><a href="#Gvirstor">Gvirstor</a></li><li><a href="#IPv6-Stack-Vulnerabilities">IPv6 Stack Vulnerabilities</a></li><li><a href="#Jail-Resource-Limits">Jail Resource Limits</a></li><li><a href="#Nss-LDAP-importing-and-nsswitch-subsystem-improvement">Nss-LDAP importing and nsswitch subsystem improvement</a></li><li><a href="#Porting-the-seref-policy-and-setools-to-SEBSD">Porting the seref policy and setools to SEBSD</a></li><li><a href="#Porting-Xen-to-FreeBSD">Porting Xen to FreeBSD</a></li><li><a href="#SNMP-monitoring-(BSNMP)">SNMP monitoring (BSNMP)</a></li><li><a href="#Update-of-the-Linux-compatibility-environment-in-the-kernel">Update of the Linux compatibility environment in the
-    kernel</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#CScout-on-the-FreeBSD-Source-Code-Base">CScout on the FreeBSD Source Code Base</a></li><li><a href="#DTrace">DTrace</a></li><li><a href="#Embedded-FreeBSD">Embedded FreeBSD</a></li><li><a href="#FreeSBIE">FreeSBIE</a></li><li><a href="#GJournal">GJournal</a></li><li><a href="#iSCSI-Initiator">iSCSI Initiator</a></li><li><a href="#Porting-ZFS-to-FreeBSD">Porting ZFS to FreeBSD</a></li><li><a href="#Summer-of-FreeBSD-security-development">Summer of FreeBSD security development</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#USB">USB</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Bridge-Spanning-Tree-Protocol-Improvements">Bridge Spanning Tree Protocol Improvements</a></li><li><a href="#FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></li><li><a href="#Highly-improved-implementations-of-sendfile(2),-sosend_*()-and-soreceive_stream()">Highly improved implementations of sendfile(2), sosend_*() and
-    soreceive_stream()</a></li><li><a href="#SCTP-Integration">SCTP Integration</a></li><li><a href="#TSO---TCP-Segmentation-Offload-committed">TSO - TCP Segmentation Offload committed</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Gvinum-improvements">Gvinum improvements</a></li><li><a href="#MMC/SD-Support">MMC/SD Support</a></li><li><a href="#Sound-Subsystem-Improvements">Sound Subsystem Improvements</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Chinese-(Simplified)-Project">Chinese (Simplified) Project</a></li><li><a href="#Hungarian-translation-of-the-webpages">Hungarian translation of the webpages</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Libelf">Libelf</a></li><li><a href="#OpenBSD-dhclient">OpenBSD dhclient</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#CPU-Microcode-Update-Software">CPU Microcode Update Software</a></li><li><a href="#FreeBSD/arm-on-Atmel-AT91RM9200">FreeBSD/arm on Atmel AT91RM9200</a></li><li><a href="#Sun-Niagara-port">Sun Niagara port</a></li><li><a href="#Xen-Port">Xen Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Enlightenment-DR17-support-in-the-ports-tree">Enlightenment DR17 support in the ports tree</a></li><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#Improving-FreeBSD-Ports-Collection-Infrastructure">Improving FreeBSD Ports Collection Infrastructure</a></li><li><a href="#OCaml-language-support-in-ports">OCaml language support in ports</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#AsiaBSDCon-2007">AsiaBSDCon 2007</a></li><li><a href="#BSDCan-2007">BSDCan 2007</a></li><li><a href="#EuroBSDCon-2006">EuroBSDCon 2006</a></li><li><a href="#FreeBSD-Multimedia-Resources-List">FreeBSD Multimedia Resources List</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Analyze-and-Improve-the-Interrupt-Handling-Infrastructure" href="#Analyze-and-Improve-the-Interrupt-Handling-Infrastructure" id="Analyze-and-Improve-the-Interrupt-Handling-Infrastructure">Analyze and Improve the Interrupt Handling
-    Infrastructure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Interrupts" title="http://wiki.freebsd.org/Interrupts">SoC Student Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Interrupts" title="SoC Student Wiki">http://wiki.freebsd.org/Interrupts</a></td></tr></table><p>
-	Contact:
-          Paolo
-
-          Pisati
-         &lt;<a href="mailto:pisati@FreeBSD.org">pisati@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project consisted in the improvement of the Interrupt
-      Handling System in FreeBSD: while retaining backward compatibility
-      with the previous models (FAST and ITHREAD), a new method called
-      'Interrupt filtering' was added. With interrupt filtering, the
-      interrupt handler is divided into 2 parts: the filter (that checks
-      if the actual interrupt belong to this device) and the ithread
-      (that is scheduled in case some blocking work has to be done). The
-      main benefits of interrupt filtering are:</p>
-
-      <ul>
-        <li>Feedback from filters (the system finally knows if any
-        handler has serviced an interrupt or not, and can react
-        consequently).</li>
-
-        <li>Lower latency/overhead for shared interrupt line.</li>
-
-        <li>Previous experiments with interrupt filtering showed an
-        increase in performance against the plain ithread model</li>
-      </ul>
-
-      <p>Moreover, during the development of interrupt filtering, some MD
-      dependent code was converted into MI code, PPC was fixed to support
-      multiple FAST handlers per line and an interrupt stray storm
-      detection logic was added. While the framework is done, there are
-      still machine dependent bits to be written (the support for ppc,
-      sparc64, arm and itanium has to be written/reviewed) and a serious
-      analysis of the performance of this model against the previous one
-      is a work-in-progress</p>
-    <hr /><h2><a name="Bundled-PXE-Installer" href="#Bundled-PXE-Installer" id="Bundled-PXE-Installer">Bundled PXE Installer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/MarkusBoelter" title="http://wiki.freebsd.org/MarkusBoelter">SoC Student Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/MarkusBoelter" title="SoC Student Wiki">http://wiki.freebsd.org/MarkusBoelter</a></td></tr></table><p>
-	Contact:
-          Markus
-
-          Boelter
-         &lt;<a href="mailto:m@FreeBSD.org">m@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Paul
-
-          Saab
-         &lt;<a href="mailto:ps@FreeBSD.org">ps@FreeBSD.org</a>&gt;
-	</p>
-      <p>For me, the Google Summer of Code was a new and very exciting
-      experience. I got actively involved in doing Open Source Software
-      and giving something back to the community. Facing some
-      challenges within the project forced me to look behind the scenery
-      of FreeBSD. The result was a better understanding of the overall
-      project. Working with a lot of developers directly also
-      gave a very special spirit to the Google Summer of Code.</p>
-
-      <p>I really enjoyed the time and will continue to work on the
-      project after the deadline. For me, it was a great chance to get
-      involved in active development and not just some scripts and hacks
-      at home. Getting paid for the work was just a small part of the
-      overall feeling.</p>
-
-      <p>Thanks to the people at the FreeBSD Project and Google for the
-      really, really great time!</p>
-    <hr /><h2><a name="Gvirstor" href="#Gvirstor" id="Gvirstor">Gvirstor</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/gvirstor" title="http://wiki.freebsd.org/gvirstor">gvirstor home page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/gvirstor" title="gvirstor home page">http://wiki.freebsd.org/gvirstor</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@freebsd.org">ivoras@freebsd.org</a>&gt;
-	</p>
-      <p>Gvirstor is a GEOM class providing virtual ("overcommit")
-      storage devices larger than physical available storage, with
-      possibility to add physical storage on-line when the need arises.
-      Current status is that it's done and waiting commit to HEAD,
-      scheduled for some time after 6.2 is released.</p>
-    <h3>Open tasks:</h3><ol><li>The project is in need of testing! If you have the equipment
-      and time, please give it a try so possible bugs can be fixed before
-      it goes into -CURRENT.</li></ol><hr /><h2><a name="IPv6-Stack-Vulnerabilities" href="#IPv6-Stack-Vulnerabilities" id="IPv6-Stack-Vulnerabilities">IPv6 Stack Vulnerabilities</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/ClementLecigne" title="http://wiki.freebsd.org/ClementLecigne">SoC Student Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/ClementLecigne" title="SoC Student Wiki">http://wiki.freebsd.org/ClementLecigne</a></td></tr><tr><td><a href="http://pcs.sf.net" title="http://pcs.sf.net">PCS Library</a></td><td>
-	    URL: <a href="http://pcs.sf.net" title="PCS Library">http://pcs.sf.net</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Clement
-
-          Lecigne
-         &lt;<a href="mailto:clem1@FreeBSD.org">clem1@FreeBSD.org</a>&gt;
-	</p>
-      <p>The focus of this project was to review past vulnerabilities,
-      create vulnerability testing tools and to discover new
-      vulnerabilities in the FreeBSD IPv6 stack which is derived from the
-      KAME project code. During the summer Clement took two libraries,
-      the popular libnet, and his mentor's Packet Construction Set (PCS)
-      and created tools to find security problems in the IPv6 code.
-      Several issues were found, bugs filed, and patches created. At the
-      moment Clement and George are editing a 50 page paper that
-      describes the project which will be submitted for conference
-      publication.</p>
-
-      <p>All of the code from the project, including the tools, is
-      online and is described in the paper.</p>
-
-      <p>By all measures, this was a successful project. Both student and
-      mentor gained valuable insight into a previously externally
-      maintained set of code. In addition to the new tools development in
-      this effort, the FreeBSD Project has gained a new developer to help
-      work on the code.</p>
-    <hr /><h2><a name="Jail-Resource-Limits" href="#Jail-Resource-Limits" id="Jail-Resource-Limits">Jail Resource Limits</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/JailResourceLimits" title="http://wiki.freebsd.org/JailResourceLimits">SoC Student Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/JailResourceLimits" title="SoC Student Wiki">http://wiki.freebsd.org/JailResourceLimits</a></td></tr></table><p>
-	Contact:
-          Chris
-
-          Jones
-         &lt;<a href="mailto:cdjones@freebsd.org">cdjones@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@freebsd.org">kmacy@freebsd.org</a>&gt;
-	</p>
-      <p>We now have support for limiting CPU and memory use in jails.
-      This allows fairer sharing of a systems' resources between divergent
-      uses by preventing one jail from monopolizing the available memory
-      and CPU time, if other users and jails have processes to run.</p>
-
-      <p>The code is currently available as patches against RELENG_6, and
-      Chris is in the process of applying it to -CURRENT. More details
-      can be found at JailResourceLimits on the wiki.</p>
-    <h3>Open tasks:</h3><ol><li>Port patches against -CURRENT.</li></ol><hr /><h2><a name="Nss-LDAP-importing-and-nsswitch-subsystem-improvement" href="#Nss-LDAP-importing-and-nsswitch-subsystem-improvement" id="Nss-LDAP-importing-and-nsswitch-subsystem-improvement">Nss-LDAP importing and nsswitch subsystem improvement</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/MichaelBushkov" title="http://wiki.freebsd.org/MichaelBushkov">SoC Student Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/MichaelBushkov" title="SoC Student Wiki">http://wiki.freebsd.org/MichaelBushkov</a></td></tr><tr><td><a href="http://wiki.freebsd.org/LdapCachedOriginalProposal" title="http://wiki.freebsd.org/LdapCachedOriginalProposal">Original Project Proposal</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/LdapCachedOriginalProposal" title="Original Project Proposal">http://wiki.freebsd.org/LdapCachedOriginalProposal</a></td></tr><tr><td><a href="http://wiki.freebsd.org/LdapCachedDetailedDescription" title="http://wiki.freebsd.org/LdapCachedDetailedDescription">Detailed Description of the Completed Project</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/LdapCachedDetailedDescription" title="Detailed Description of the Completed Project">http://wiki.freebsd.org/LdapCachedDetailedDescription</a></td></tr></table><p>
-	Contact:
-          Michael
-
-          Bushkov
-         &lt;<a href="mailto:bushman@FreeBSD.org">bushman@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Hajimu
-
-          UMEMOTO
-         &lt;<a href="mailto:ume@FreeBSD.org">ume@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Project consisted of five parts:</p>
-
-      <ol>
-        <li>Nsswitch modules and libc separation. The idea was to move
-        the source code for different nsswitch sources (such as "files",
-        "dns", "nis") out of the libc into the separate shared libraries.
-        This task was successfully finished and the patch is
-        available.</li>
-
-        <li>Regression tests for nsswitch. A set of regression tests to
-        test the correctness of all nsswitch-related functions and the
-        invariance of their behavior between system upgrades. The task
-        can be considered successfully completed, the patch is
-        available.</li>
-
-        <li>Rewriting nss_ldap. Though, this task was not clearly
-        mentioned in the original proposal, during the SoC we found
-        it would be easier, not to simply import PADL's nss_ldap, but
-	to rewrite it from scratch (licensing issues were among the
-	basic reasons for this). The resulting module behaves similarly
-	to PADL's module, but has a different architecture that is more
-	flexible.  Though it's basically finished, several useful
-	features from the PADL's nss_ldap still need to be implemented.
-	Despite the lack of some features, this task can be considered
-	successfully completed. Missing features will be implemented as
-	soon as possible, hopefully during September.</li>
-
-        <li>Importing nss_ldap into the Base System. The task was to
-        prepare a patch, that will allow users to use nss_ldap from the
-        base system. The task was successfully completed (the patch is
-        available), but required importing OpenLDAP into the base in
-        order for nss_ldap to work properly, and it had led to a long
-        discussion in the mailing list. This discussion, however, have
-        concluded with mostly positive opinions about nss_ldap and
-        OpenLDAP importing.</li>
-
-        <li>Cached performance optimization. The caching daemon
-        performance needs to be as high as possible in order for cached
-        to be as close (in terms of speed) to "files" nsswitch source as
-        possible. Cached's performance analysis was made and nsswitch
-        database pre-caching was introduced as the optimization. This
-        task was completed (the patch is available). However there is
-        room for improvement. More precise and extensive performance
-        analysis should be made and more optimizations need to be
-        introduces. This will be done in the near future.</li>
-      </ol>
-
-      <p>Though none of the code was committed yet into the official
-      FreeBSD tree, my experience from the previous year makes me think
-      that this situation is normal. I hope, that the code will be
-      reviewed and committed in the coming months.</p>
-    <hr /><h2><a name="Porting-the-seref-policy-and-setools-to-SEBSD" href="#Porting-the-seref-policy-and-setools-to-SEBSD" id="Porting-the-seref-policy-and-setools-to-SEBSD">Porting the seref policy and setools to SEBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/DongmeiLiu" title="http://wiki.freebsd.org/DongmeiLiu">SoC Student Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/DongmeiLiu" title="SoC Student Wiki">http://wiki.freebsd.org/DongmeiLiu</a></td></tr></table><p>
-	Contact:
-          Dongmei
-
-          Liu
-         &lt;<a href="mailto:dongmei@freebsd.org">dongmei@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Christian
-
-          Peron
-         &lt;<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Dongmei Liu spent the summer working on the basic footwork
-      required to port the SEREF policy to SEBSD. This work has been
-      submitted and can be viewed in the soc2006/dongmei_sebsd Perforce
-      branch. This work was originated from the SEBSD branch:
-      //depot/projects/trustedbsd/sebsd. Additionally setools-2.3 was
-      ported from Linux and can be found in contrib/sebsd/setools
-      directory. It is hoped that this work will be merged into the main
-      SEBSD development branch.</p>
-    <hr /><h2><a name="Porting-Xen-to-FreeBSD" href="#Porting-Xen-to-FreeBSD" id="Porting-Xen-to-FreeBSD">Porting Xen to FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.yuanjue.net/xen/howto.html" title="http://www.yuanjue.net/xen/howto.html">Step-by-step tutorial for installing and using FreeBSD as domU</a></td><td>
-	    URL: <a href="http://www.yuanjue.net/xen/howto.html" title="Step-by-step tutorial for installing and using FreeBSD as domU">http://www.yuanjue.net/xen/howto.html</a></td></tr><tr><td><a href="http://wiki.freebsd.org/YuanJue" title="http://wiki.freebsd.org/YuanJue">Wiki page for this project</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/YuanJue" title="Wiki page for this project">http://wiki.freebsd.org/YuanJue</a></td></tr></table><p>
-	Contact:
-          Jue
-
-          Yuan
-         &lt;<a href="mailto:yuanjue@FreeBSD.org">yuanjue@FreeBSD.org</a>&gt;
-	</p>
-      <p>As a participant of Google's Summer of Code 2006, I am focusing
-      on porting
-      <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" target="_blank" shape="rect">Xen</a>
-
-      to FreeBSD these months. The result of this summer's work include a
-      domU kernel that could be used for installation, a
-      <a href="http://www.yuanjue.net/xen/howto.html" target="_blank" shape="rect">
-      guide</a>
-
-      for getting started with FreeBSD on Xen, and some other trivial
-      improvements. But there are still a lot of work needing to be done
-      in this area, e.g, the long-expeted dom0 support. So I will
-      continue my work here and try to keep up with the update of Xen
-      itself.</p>
-    <h3>Open tasks:</h3><ol><li>dom0 support is the most urgent</li></ol><hr /><h2><a name="SNMP-monitoring-(BSNMP)" href="#SNMP-monitoring-(BSNMP)" id="SNMP-monitoring-(BSNMP)">SNMP monitoring (BSNMP)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp&amp;HIDEDEL=NOe" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp&amp;HIDEDEL=NOe">P4 workspace</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp&amp;HIDEDEL=NOe" title="P4 workspace">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/soc%2dshteryana/bsnmp&amp;HIDEDEL=NOe</a></td></tr><tr><td><a href="http://wiki.freebsd.org/CategorySNMP" title="http://wiki.freebsd.org/CategorySNMP">SNMP-related pages on FreeBSD Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/CategorySNMP" title="SNMP-related pages on FreeBSD Wiki">http://wiki.freebsd.org/CategorySNMP</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SnmpBridgeModule" title="http://wiki.freebsd.org/SnmpBridgeModule">A wiki page on if_bridge(4) monitoring module</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SnmpBridgeModule" title="A wiki page on if_bridge(4) monitoring module">http://wiki.freebsd.org/SnmpBridgeModule</a></td></tr><tr><td><a href="http://www.freshports.org/net-mgmt/bsnmptools/" title="http://www.freshports.org/net-mgmt/bsnmptools/">bsnmptools port</a></td><td>
-	    URL: <a href="http://www.freshports.org/net-mgmt/bsnmptools/" title="bsnmptools port">http://www.freshports.org/net-mgmt/bsnmptools/</a></td></tr></table><p>
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:shteryana@FreeBSD.org">shteryana@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>A BRIDGE monitoring module for FreeBSD's BSNMP daemon has been
-      implemented. In addition to RFC 4188 single bridge support and
-      extending the kernel to get access to all the information, a
-      private MIB was designed in order to be able to monitor multiple
-      bridges supported by FreeBSD. The kernel part has already been
-      committed to -CURRENT (thanks to thompsa@), for -STABLE a patch is
-      available (see the wiki), code has already been reviewed.</p>
-
-      <p>SoC 2005 work on SNMP client tools is now available too via port
-      (net-mgmt/bsnmptools), thanks to Andrew Pantyukhin for the port.</p>
-    <h3>Open tasks:</h3><ol><li>More testing is very welcome.</li><li>if_vlan(4) monitoring module.</li><li>jail(8) monitoring module.</li></ol><hr /><h2><a name="Summer-of-Code-Summary" href="#Summer-of-Code-Summary" id="Summer-of-Code-Summary">Summer of Code Summary</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/summerofcode-2006.html" title="http://www.FreeBSD.org/projects/summerofcode-2006.html">FreeBSD Summer of Code 2006</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/summerofcode-2006.html" title="FreeBSD Summer of Code 2006">http://www.FreeBSD.org/projects/summerofcode-2006.html</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SummerOfCode2006" title="http://wiki.freebsd.org/SummerOfCode2006">SoC 2006 Student wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SummerOfCode2006" title="SoC 2006 Student wiki">http://wiki.freebsd.org/SummerOfCode2006</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2006/" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2006/">SoC 2006 Perforce trees</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2006/" title="SoC 2006 Perforce trees">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2006/</a></td></tr></table><p>
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	</p>
-      <p>We had another successful summer taking part in the Google
-      Summer of Code. By all accounts, the FreeBSD participation in this
-      program was an unqualified success. We received over 150
-      applications for student projects, amongst which 13 were selected
-      for funding. All successful students received the full $4,500.</p>
-
-      <p>These student projects included security research, improved
-      installation tools, new utilities, and more. Many of the students
-      have continued working on their FreeBSD projects even after the
-      official close of the program. At least 2 of our FreeBSD mentors
-      will be meeting with Google organizers in Mountain View this month
-      to discuss the program at the Mentor Summit.</p>
-    <hr /><h2><a name="Update-of-the-Linux-compatibility-environment-in-the-kernel" href="#Update-of-the-Linux-compatibility-environment-in-the-kernel" id="Update-of-the-Linux-compatibility-environment-in-the-kernel">Update of the Linux compatibility environment in the
-    kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/linux-kernel" title="http://wiki.FreeBSD.org/linux-kernel">Wiki page about the linux compatibility environment.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/linux-kernel" title="Wiki page about the linux compatibility environment.">http://wiki.FreeBSD.org/linux-kernel</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Roman
-
-          Divacky
-         &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Emulation
-
-          Mailinglist
-         &lt;<a href="mailto:emulation@FreeBSD.org">emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>Roman Divacky participated in the Google Summer of Code 2006 and
-      implemented a major part of the syscall compatibility to the 2.6.16
-      Linux kernel. The work has been committed to -CURRENT (the default
-      compatibility still being a 2.4.2 Linux kernel) and we are working
-      on fixing the remaining bugs as time permits.</p>
-
-      <p>"Intron" submitted an implementation for the linux aio syscalls.
-      His work has been committed to the Perforce repository.</p>
-
-      <p>We also started to consolidate a list of known bugs, open issues
-      and helpful stuff (e.g. regression tests and their status) in
-      -CURRENT on a page in the FreeBSD wiki (see the links-section). It
-      also contains a link to a more or less up-to-date patch with stuff
-      we have in the Perforce repository so that interested people can
-      help with testing. Thanks to the help of Marcin Cieslak we already
-      fixed some bugs (some of the fixes are already MFCed to
-      -STABLE).</p>
-
-      <p>Thanks to the nice regression tests of the Linux Test Project
-      (LTP) we have a list of small (and not so small) things which need
-      to be looked at. This list makes up for a quick start into kernel
-      hacking. So if you have a little bit of knowledge about C
-      programming, and if you want to help us a little bit in improving
-      FreeBSD, feel free to have a look at the list and to try to fix a
-      problem or two. Sometimes it is as easy as "if (error condition)
-      return Esomething;" (but you should coordinate with the emulation
-      mailinglist, so that nobody does some work someone else just did
-      too). Even if you do not know how to program, you can help. Have a
-      look at the wiki page and tell us about things which should get
-      mentioned there too. Or download the patch and test it.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="CScout-on-the-FreeBSD-Source-Code-Base" href="#CScout-on-the-FreeBSD-Source-Code-Base" id="CScout-on-the-FreeBSD-Source-Code-Base">CScout on the FreeBSD Source Code Base</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/CScout" title="http://wiki.freebsd.org/CScout">The CScout project page on the FreeBSD wiki.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/CScout" title="The CScout project page on the FreeBSD wiki.">http://wiki.freebsd.org/CScout</a></td></tr></table><p>
-	Contact:
-          Diomidis
-
-          Spinellis
-         &lt;<a href="mailto:dds@FreeBSD.org">dds@FreeBSD.org</a>&gt;
-	</p>
-      <p>CScout is a refactoring editor and source code browser for
-      collections of C code. The aim of the project is to make it easy
-      for FreeBSD developers to use CScout and to improve the FreeBSD
-      source code quality through CScout-based queries and
-      refactorings.</p>
-
-      <p>CScout was first applied to the FreeBSD kernel in 2003. Its
-      application at that point involved substantial tinkering with the
-      build system. The version released in October 2006 makes the
-      running of CScout on the three Tier-1 architectures a fairly
-      straightforward procedure. The current version can also draw a
-      number of call graphs; this might help developers better understand
-      foreign code.</p>
-    <h3>Open tasks:</h3><ol><li>Use CScout to locate problematic code areas (for example
-      unused or too liberaly visible objects).</li><li>Use CScout to globaly rename identifiers in a more consistent
-      fashion.</li><li>Apply CScout to the userland code.</li><li>Identify CScout extensions that would help us improve the
-      quality of our code.</li><li>Arrange for the continuous availability of a live CScout
-      kernel session on the current version of the source code.</li></ol><hr /><h2><a name="DTrace" href="#DTrace" id="DTrace">DTrace</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          John
-
-          Birrell
-         &lt;<a href="mailto:jb@freebsd.org">jb@freebsd.org</a>&gt;
-	</p>
-      <p>Progress this month has been limited due to my sea-change,
-      moving house to the country.</p>
-
-      <p>Sun's OpenSolaris developers have followed through and released
-      the DTrace test suite as part of the OpenSolaris distribution.</p>
-
-      <p>jkoshy@'s work on libbsdelf is nearing feature completion for
-      DTrace and will make life easier in FreeBSD for DTrace, given that
-      we have more architectures to support than Sun has.</p>
-
-      <p>The FreeBSD project has made available a dual processor AMD64
-      machine for DTrace porting.</p>
-
-      <p>I am currently working through the diffs between the DTrace
-      project in P4 and -current, committing files to -current if they
-      are ready.</p>
-    <hr /><h2><a name="Embedded-FreeBSD" href="#Embedded-FreeBSD" id="Embedded-FreeBSD">Embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.embeddedfreebsd.org/" title="http://www.embeddedfreebsd.org/"></a></td><td>
-	    URL: <a href="http://www.embeddedfreebsd.org/" title="">http://www.embeddedfreebsd.org/</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	</p>
-      <p>Moved the HTML pages into the project CVS tree.</p>
-    <h3>Open tasks:</h3><ol><li>Setup the web site to be served from projects CVS so that it
-      can be updated by others.</li><li>Complete the ARM port.</li><li>Work on the MIPS port.</li><li>Update the documentation to include common tasks for embedded
-      engineers.</li></ol><hr /><h2><a name="FreeSBIE" href="#FreeSBIE" id="FreeSBIE">FreeSBIE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeSBIE.org" title="http://www.FreeSBIE.org">FreeSBIE Website</a></td><td>
-	    URL: <a href="http://www.FreeSBIE.org" title="FreeSBIE Website">http://www.FreeSBIE.org</a></td></tr><tr><td><a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="http://liste.gufi.org/mailman/listinfo/freesbie">FreeSBIE ML Subscription Form</a></td><td>
-	    URL: <a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="FreeSBIE ML Subscription Form">http://liste.gufi.org/mailman/listinfo/freesbie</a></td></tr><tr><td><a href="http://people.freebsd.org/~matteo/GMV/GMVAnnounce.txt" title="http://people.freebsd.org/~matteo/GMV/GMVAnnounce.txt">FreeSBIE GMV Announcement</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~matteo/GMV/GMVAnnounce.txt" title="FreeSBIE GMV Announcement">http://people.freebsd.org/~matteo/GMV/GMVAnnounce.txt</a></td></tr></table><p>
-	Contact:
-          FreeSBIE
-
-          Staff
-         &lt;<a href="mailto:staff@FreeSBIE.org">staff@FreeSBIE.org</a>&gt;
-	<br />
-	Contact:
-          Matteo
-
-          Riondato
-         &lt;<a href="mailto:matteo@FreeBSD.org">matteo@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeSBIE is a FreeBSD based LiveCD.</p>
-
-      <p>On August 19th, Matteo Riondato, a member of the FreeSBIE staff,
-      released an unofficial ISO, codename FreeSBIE GMV, based on FreeBSD
-      -CURRENT (read the Announcement to download it). This is supposed
-      to be the first in a series of four ISOs that will end up with the
-      release of FreeSBIE 2.0. Matteo is now working on another ISO,
-      codename FreeSBIE LVC, which is scheduled to be released October 12th.</p>
-
-      <p>FreeSBIE 2.0 will be based on FreeBSD 6.2-RELEASE and will
-      hopefully be released at EuroBSDCon 2006 in Milan. It will be
-      available for the i386 and AMD64 platforms.</p>
-    <h3>Open tasks:</h3><ol><li>Test the released ISO in preparation for the release.</li><li>Suggest software to include in the ISO.</li><li>Submit a simple and clear but complete fluxbox
-      configuration.</li></ol><hr /><h2><a name="GJournal" href="#GJournal" id="GJournal">GJournal</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~pjd/patches/gjournal_20060930.patch" title="http://people.freebsd.org/~pjd/patches/gjournal_20060930.patch">Patches against HEAD.</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~pjd/patches/gjournal_20060930.patch" title="Patches against HEAD.">http://people.freebsd.org/~pjd/patches/gjournal_20060930.patch</a></td></tr><tr><td><a href="http://people.freebsd.org/~pjd/patches/gjournal6_20060930.patch" title="http://people.freebsd.org/~pjd/patches/gjournal6_20060930.patch">Patches against RELENG_6.</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~pjd/patches/gjournal6_20060930.patch" title="Patches against RELENG_6.">http://people.freebsd.org/~pjd/patches/gjournal6_20060930.patch</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>GJournal seems to be finished. I fixed the last serious bug and
-      it is now stable and reliable in our tests. I'm planning to commit
-      it really soon now.</p>
-
-      <p>The work was sponsored by home.pl</p>
-    <hr /><h2><a name="iSCSI-Initiator" href="#iSCSI-Initiator" id="iSCSI-Initiator">iSCSI Initiator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 " title="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 "></a></td><td>
-	    URL: <a href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 " title="">ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 </a></td></tr></table><p>
-	Contact:
-          Damiel
-
-          Braniss
-         &lt;<a href="mailto:danny@cs.huji.ac.il">danny@cs.huji.ac.il</a>&gt;
-	</p>
-      <p>This iSCSI initiator kernel module and its companion control
-      program are still under development, but the main parts are
-      working.</p>
-    <h3>Open tasks:</h3><ol><li>Network Disconnect Recovery.</li><li>Sysctl Interface and Instrumentation.</li><li>Rewrite the userland side of iscontrol.</li></ol><hr /><h2><a name="Porting-ZFS-to-FreeBSD" href="#Porting-ZFS-to-FreeBSD" id="Porting-ZFS-to-FreeBSD">Porting ZFS to FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs">Source code.</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="Source code.">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs</a></td></tr><tr><td><a href="http://www.opensolaris.org/os/community/zfs/porting/" title="http://www.opensolaris.org/os/community/zfs/porting/">ZFS porting site.</a></td><td>
-	    URL: <a href="http://www.opensolaris.org/os/community/zfs/porting/" title="ZFS porting site.">http://www.opensolaris.org/os/community/zfs/porting/</a></td></tr><tr><td><a href="http://docs.freebsd.org/cgi/mid.cgi?20060822104516.GB16033" title="http://docs.freebsd.org/cgi/mid.cgi?20060822104516.GB16033">ZFS port announce.</a></td><td>
-	    URL: <a href="http://docs.freebsd.org/cgi/mid.cgi?20060822104516.GB16033" title="ZFS port announce.">http://docs.freebsd.org/cgi/mid.cgi?20060822104516.GB16033</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>My work is moving slowly forward. ZVOL is, I believe, fully
-      functional (I recently fixed snapshots and clones on zvols), which
-      means you can put UFS on top of RAID-Z volume, take a snapshot of
-      the volume, clone it if needed, etc. Very cool. The hardest part is
-      the ZPL layer, I'm still working on it. Most file system methods
-      work, but probably need detailed review and many fixes. Most of the
-      time these days I'm spending on implementing mmap(2) correctly. It
-      works more or less in simple tests but fails under fsx program. On
-      the other hand, 'fsx -RW' works very stable and reliable. Other
-      test programs (those that don't use mmap(2)) also work quite well.
-      There is still a lot of work to do, mostly in ZPL area, many
-      clean-ups, etc. Some functionality (like ACLs) I haven't even tried
-      to touch yet.</p>
-    <hr /><h2><a name="Summer-of-FreeBSD-security-development" href="#Summer-of-FreeBSD-security-development" id="Summer-of-FreeBSD-security-development">Summer of FreeBSD security development</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~cperciva/funding.html" title="http://people.freebsd.org/~cperciva/funding.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~cperciva/funding.html" title="">http://people.freebsd.org/~cperciva/funding.html</a></td></tr><tr><td><a href="http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/" title="http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/"></a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/" title="">http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/</a></td></tr></table><p>
-	Contact:
-          Colin
-
-          Percival
-         &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>I spent the months of May through August working on improving
-      Portsnap, FreeBSD Update, and devoting more time to my (continuing)
-      role as Security Officer. FreeBSD Update is now part of the FreeBSD
-      base system and is fully supported by the FreeBSD Security Team;
-      updates are currently only being built for the i386 architecture,
-      but AMD64 updates will become available soon.</p>
-
-      <p>In an attempt to reduce the number of people running out of date
-      (and unsupported) FreeBSD releases, I wrote an automatic binary
-      upgrade script for upgrading systems from FreeBSD 6.0 to FreeBSD
-      6.1; I will be releasing a new script for upgrading to FreeBSD
-      6.2-(RC*|RELEASE) soon (possibly before this status report is
-      published).</p>
-
-      <p>Further improvements to Portsnap are still ongoing.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/audit.html" title="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/audit.html" title="TrustedBSD Audit Page">http://www.TrustedBSD.org/audit.html</a></td></tr><tr><td><a href="http://www.OpenBSM.org/" title="http://www.OpenBSM.org/">OpenBSM Page</a></td><td>
-	    URL: <a href="http://www.OpenBSM.org/" title="OpenBSM Page">http://www.OpenBSM.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Christian
-
-          Peron
-         &lt;<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Wayne
-
-          Salamon
-         &lt;<a href="mailto:wsalamon@FreeBSD.org">wsalamon@FreeBSD.org</a>&gt;
-	</p>
-      <p>
-        <p>The TrustedBSD audit implementation provides fine-grained
-        security event logging throughout the FreeBSD operating system.
-        The big news for the last quarter is that the TrustedBSD audit
-        implementation has been merged into RELENG_6 branch, and appeared
-        in 6.2-BETA2. Over the past few months, work has also occurred in
-        the following areas:</p>
-
-        <ul>
-          <li>OpenBSM 1.0 alpha 8 through alpha 12 have been released and
-          merged into FreeBSD CVS. Changes include significant numbers of
-          bug fixes, documentation improvements, and feature
-          enhancements. These include regular expression based matching
-          for auditreduce, auditd management of kernel audit policy (such
-          as maximum trail file size), improvements in printing support
-          for a variety of tokens including execve argument support.</li>
-
-          <li>Significant enhancements to the FreeBSD Handbook chapter on
-          Audit.</li>
-
-          <li>Full audit support for execve events, including optional
-          auditing of command line arguments and environmental variables,
-          as well as audit support for a broad range of other additional
-          kernel events.</li>
-
-          <li>Kqueue support for audit pipes.</li>
-
-          <li>Robustness improvements in the presence of low disk space
-          conditions.</li>
-
-          <li>Support for system call capture on additional platforms,
-          such as ppc and ia64.</li>
-
-          <li>Improved support for very large audit record sizes (as
-          required for extensive execve support).</li>
-
-          <li>id(1) now supports a -A argument to query audit state for
-          the process.</li>
-
-          <li>An audit_warn(5) event for trail rotation, which can be
-          used for archiving, reduction, and other administrative
-          activities.</li>
-        </ul>
-
-        <p>Lots of testing as part of the 6.2-BETA cycle would be much
-        appreciated. Audit support will be considered an experimental
-        feature in FreeBSD 6.2-RELEASE, but we hope that it will be a
-        production feature in 6.3-RELEASE.</p>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Continue expanding auditing of syscall arguments.</li><li>Continue expanding auditing of administrative tools.</li><li>More testing!</li><li>Continue to explore improvements of the administrative model
-      for audit trails, etc.</li></ol><hr /><h2><a name="USB" href="#USB" id="USB">USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO">Current USB files</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="Current USB files">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://www.turbocat.net/~hselasky/usb4bsd" title="http://www.turbocat.net/~hselasky/usb4bsd">My USB homepage</a></td><td>
-	    URL: <a href="http://www.turbocat.net/~hselasky/usb4bsd" title="My USB homepage">http://www.turbocat.net/~hselasky/usb4bsd</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>&gt;
-	</p>
-      <p>During the last three months I have finished reworking nearly
-      all USB device drivers found in FreeBSD-7-CURRENT. Only two USB
-      drivers are left and that is ubser(4) and slhci. Some still use
-      Giant, but most have been brought out of Giant. At the moment I am
-      looking for testers that can test the various USB device drivers.
-      Some have already been tested, and confirmed to work, while others
-      have problems which need to be fixed. If you want to test, checkout
-      the USB perforce tree or download the SVN version of the USB driver
-      that is available on my homepage. At the moment the tarballs are a
-      little out of date.</p>
-
-      <p>Ideas and comments with regard to the new USB API are welcome
-      at:
-
-      <a href="mailto:freebsd-usb@freebsd.org" shape="rect">
-      freebsd-usb@freebsd.org</a>.</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the time since the last status report, six security
-      advisories have been issued concerning problems in the base system
-      of FreeBSD; of these, five problems were in "contributed" code,
-      while one was in code maintained within FreeBSD. The
-      Vulnerabilities and Exposures Markup Language (VuXML) document has
-      continued to be updated by the Security Team and Ports Committers
-      documenting new vulnerabilities in the FreeBSD Ports Collection;
-      since the last status report, 57 new entries have been added,
-      bringing the total up to 814.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 4.11, FreeBSD 5.3, FreeBSD 5.4, FreeBSD 5.5,
-      FreeBSD 6.0, and FreeBSD 6.1. The respective End of Life dates of
-      supported releases are listed on the web site; of particular note,
-      FreeBSD 5.3 and FreeBSD 5.4 will cease to be supported at the end
-      of October 2006, while FreeBSD 6.0 will cease to be supported at
-      the end of November 2006 (or possibly a short time thereafter in
-      order to allow time for upgrades to the upcoming FreeBSD 6.2).</p>
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/">marcuscom tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com/" title="marcuscom tinderbox">http://tinderbox.marcuscom.com/</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports PRs surged (especially due to a large number of new
-      port submissions), but with some hard work we have been able to get
-      back down to around 900. We are rapidly approaching 16,000
-      ports.</p>
-
-      <p>Due to this acceleration in adding new ports, portmgr is now
-      very concerned that we are outstripping the capacity of both the
-      build infrastructure and our volunteers to keep up with build
-      errors and port updates. Accordingly, we've added a guideline (not
-      a rule) that ports should be of more than just theoretical use to
-      be added to the Ports Collection (e.g. we can't support all of CPAN
-      + all of Sourceforge + everything else). Basically, use common
-      sense as a guideline; certainly no one wants to see any kind of
-      "gateway" procedure to get incoming ports approved.</p>
-
-      <p>Seven sets of changes have been added to the infrastructure,
-      mostly refactoring and bugfixing.</p>
-
-      <p>As part of a Summer of Code project, we have also incorporated
-      some of gabor@'s changes to incorporate better DESTDIR support.
-      However, due to some unanticipated side-effects, more work is going
-      to be needed in this area. gabor@ is continuing to work on the
-      changes.</p>
-
-      <p>netchild@ and bsam@ have been doing a great deal of work to
-      bring the linux emulator ports closer to sanity, including bringing
-      up a regression-test suite.</p>
-
-      <p>The long-anticipated import of X.Org 7 has stalled due to
-      developer time, mostly to deal with documentation and upgrade
-      instructions. Hopefully this can get done in the early 6.3
-      development cycle. See the wiki for more information.</p>
-
-      <p>As a part of that work, the decision has been made to move away
-      from using X11BASE and just put everything into LOCALBASE;
-      /usr/X11R6 is simply an artifact at this point. A plan for a
-      transition process is underway; a great deal of testing will need
-      to be done, but in the end the ports tree will be much cleaner. The
-      GNOME team has already done the work to move all of their ports
-      over, and it will be incorporated after the 6.2 release is
-      shipped.</p>
-
-      <p>tmclaugh@ is looking for someone to take over the C# ports. He
-      has maintained them for over a year and wants more time to be able
-      to work on other projects.</p>
-
-      <p>Some work has been done to get rid of FreeBSD 2.X cruft in
-      ports. Further work is needed to get the 3.X cruft removed.</p>
-
-      <p>linimon@ did another pass through resetting inactive
-      maintainers. Another list is waiting in the wings.</p>
-
-      <p>linimon@ is also working on adding the ability for portsmon to
-      analyze successful packages (not just failed ones), so that queries
-      such as "show me packages that build on i386 but not amd64" and
-      "show me why dependent package foo was not built on bar". This is
-      currently in alpha testing.</p>
-
-      <p>We have added 4 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>We still need help getting back to our modern low of 500
-      PRs.</li><li>We have nearly 4400 unmaintained ports (see, for instance,
-      <url href="http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports@FreeBSD.org">
-      the list on portsmon</url>
-
-      ). Although there has been a welcome upsurge in new maintainers
-      recently which has dropped the percentage down below 28%, we still
-      need much more help.</li><li>A test run of gcc4.1 on the ports tree showed around 1000 new
-      build errors. Kris@ has posted some results so that people can
-      start working on the problems now. In particular, it seems that
-      certain older versions of GCC cannot be built with GCC 4.1, so
-      ports that depend on those older versions are going to have to be
-      fixed as well. Although the import of GCC 4.1 to -CURRENT is not
-      imminent, the time to start planning is now.</li><li>The state of the packages on AMD64 and sparc64 significantly
-      lags that of i386. In many of these cases, packages are not
-      attempted because NOT_FOR_ARCH is used instead of more accurately
-      only setting BROKEN based on ARCH. (pointyhat can be forced to
-      build packages that are marked BROKEN, but not NOT_FOR_ARCH).
-      NOT_FOR_ARCH is supposed to denote only "will never work on this
-      ARCH". Although we have volunteers who have expressed interest in
-      sparc64 (and ia64), we need more people who are running amd64
-      (especially as a desktop) to help us get more packages
-      working.</li></ol><hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/releases/" title="http://www.FreeBSD.org/releases/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/" title="">http://www.FreeBSD.org/releases/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/snapshots/" title="http://www.FreeBSD.org/snapshots/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/snapshots/" title="">http://www.FreeBSD.org/snapshots/</a></td></tr></table><p>
-	Contact:
-          Release Engineering Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering team is currently working on
-      FreeBSD 6.2-RELEASE, which is scheduled for release in early
-      November 2006. Some notable features of this release include the
-      debut of security event auditing as an experimental feature, Xbox
-      support, the FreeBSD Update binary updating utility, and of course
-      many fixes and updates for existing programs. Pre-release images
-      for all Tier-1 architectures are available for testing now;
-      feedback on these builds is greatly appreciated. More information
-      about release engineering activities can be found at the links
-      above.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org" title="http://www.freebsdfoundation.org"></a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org" title="">http://www.freebsdfoundation.org</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@FreeBSD.org">deb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation continued to support the FreeBSD project
-      and community through various activities. These activities include
-      creating strategies for fund development and actively seeking
-      funding for the FreeBSD community, coordinating a new IBM
-      Bladeserver project, and protecting the image and integrity of
-      FreeBSD by governing the use of the trademarks. We are pleased to
-      be a sponsor of EuroBSDCon and will be sponsoring a few developers
-      to attend the conference through our travel grant program. And
-      finally, we have secured funds for a major project that will be
-      announced later this month.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Bridge-Spanning-Tree-Protocol-Improvements" href="#Bridge-Spanning-Tree-Protocol-Improvements" id="Bridge-Spanning-Tree-Protocol-Improvements">Bridge Spanning Tree Protocol Improvements</a></h2><p>
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is almost finished to implement the Rapid Spanning Tree
-      Protocol (RSTP) which supersedes Spanning Tree Protocol (STP).
-      RSTP has a much faster link failover time of around one second
-      compared to 30-60 seconds for STP, this is very important on
-      modern networks. The code will be posted shortly for testing and
-      feedback.</p>
-    <hr /><h2><a name="FAST_IPSEC-Upgrade" href="#FAST_IPSEC-Upgrade" id="FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="www.freebsd.org/~gnn/fast_ipv6.patch" title="www.freebsd.org/~gnn/fast_ipv6.patch">CURRENT patch to enable FAST_IPSEC and IPv6</a></td><td>
-	    URL: <a href="www.freebsd.org/~gnn/fast_ipv6.patch" title="CURRENT patch to enable FAST_IPSEC and IPv6">www.freebsd.org/~gnn/fast_ipv6.patch</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern
-
-          Zeeb
-         &lt;<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>&gt;
-	</p>
-      <p>First working version of code. Does not pass all TAHI tests, but
-      does pass packets correctly and does not panic.</p>
-    <h3>Open tasks:</h3><ol><li>More testing of the patch needed.</li></ol><hr /><h2><a name="Highly-improved-implementations-of-sendfile(2),-sosend_*()-and-soreceive_stream()" href="#Highly-improved-implementations-of-sendfile(2),-sosend_*()-and-soreceive_stream()" id="Highly-improved-implementations-of-sendfile(2),-sosend_*()-and-soreceive_stream()">Highly improved implementations of sendfile(2), sosend_*() and
-    soreceive_stream()</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065997.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065997.html">sendfile(2) patch with detailed performance figures</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065997.html" title="sendfile(2) patch with detailed performance figures">http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065997.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/066199.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/066199.html">sosend_*() patch with detailed performance figures</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2006-September/066199.html" title="sosend_*() patch with detailed performance figures">http://lists.freebsd.org/pipermail/freebsd-current/2006-September/066199.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~andre/sendfile+sosend+soreceive-20061006.diff" title="http://people.freebsd.org/~andre/sendfile+sosend+soreceive-20061006.diff">Combined sendfile(2), sosend_*() and soreceive_stream() patch</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/sendfile+sosend+soreceive-20061006.diff" title="Combined sendfile(2), sosend_*() and soreceive_stream() patch">http://people.freebsd.org/~andre/sendfile+sosend+soreceive-20061006.diff</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>The addition of TSO (TCP Segmentation Offload) has highlighted
-      some shortcomings in the sendfile(2) and sosend_*() kernel
-      implementations.</p>
-
-      <p>The current sendfile(2) code simply loops over the file, turns
-      each 4K page into an mbuf and sends it off. This has the effect
-      that TSO can only generate 2 packets per send instead of up to 44
-      at its maximum of 64K. kern_sendfile() has been rewritten to work
-      in two loops, the inner which turns as many pages into mbufs as it
-      can -- up to the free send socket buffer space. The outer loop then
-      drops the whole mbuf chain into the send socket buffer, calls
-      tcp_output() on it and then waits until 50% of the socket buffer
-      are free again to repeat the cycle. This way tcp_output() gets the
-      full amount of data to work with and can issue up to 64K sends for
-      TSO to chop up in the network adapter without using any CPU cycles.
-      Thus it gets very efficient especially with the readahead the VM
-      and I/O system do.</p>
-
-      <p>Looking at the benchmarks we see some very nice improvements:
-      181% faster with new sendfile vs. old sendfile (non-TSO), 570%
-      faster with new sendfile vs. old sendfile (TSO).</p>
-
-      <p>The current sosend_*() code uses a sosend_copyin() function that
-      loops over the supplied struct uio and does interleaved mbuf
-      allocations and uiomove() calls. m_getm() has been rewritten to be
-      simpler and to allocate PAGE_SIZE sized jumbo mbuf clusters (4k on
-      most architectures). m_uiotombuf() has been rewritten to use the
-      new m_getm() to obtain all mbuf space in one go. It then loops over
-      it and copies the data into the mbufs by using uiomove().
-      sosend_dgram() and sosend_generic() have been changed to use
-      m_uiotombuf() instead of sosend_copyin().</p>
-
-      <p>Looking at the benchmarks we see some very nice improvements:
-      290% faster with new sosend vs. old sosend (non-TSO), 280% faster
-      with new sosend vs. old sosend (TSO).</p>
-
-      <p>Newly written is a specific soreceive_stream() function for
-      stream protocols (primarily TCP) that does only one socket buffer
-      lock per socket read instead of one per data mbuf copied to
-      userland. When doing netperf tests with WITNESS (full lock tracking
-      and validation enabled) the receive performance increases from
-      ~360Mbit/s to ~520Mbit/s. Without WITNESS I could not measure any
-      statistically significant improvement on a otherwise unloaded
-      machine. The reason is two-fold: 1) per packet we do a wakeup and
-      readv() is pretty much as many times as packets come it, thus the
-      general overhead dominates; 2) the packet input path has a pretty
-      high overhead too. On heavily loaded machines which do a lot of
-      high speed receives a performance increase should be
-      measureable.</p>
-
-      <p>The patches are scheduled to be committed to FreeBSD-current at
-      end of October or early November 2006.</p>
-
-      <p>This work was sponsored by the TCP/IP Optimization Fundraiser
-      2005.</p>
-    <hr /><h2><a name="SCTP-Integration" href="#SCTP-Integration" id="SCTP-Integration">SCTP Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.sctp.org/" title="http://www.sctp.org/"></a></td><td>
-	    URL: <a href="http://www.sctp.org/" title="">http://www.sctp.org/</a></td></tr></table><p>
-	Contact:
-          Randall
-
-          Stewart
-         &lt;<a href="mailto:randall@freebsd.org">randall@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	</p>
-      <p>There are currently patches available for testing. A planned
-      integration to HEAD is set to happen in October.</p>
-    <h3>Open tasks:</h3><ol><li>The code still needs plenty of testing. See patches on
-      <a href="http://www.sctp.org/" shape="rect">sctp.org</a>
-
-      and in -CURRENT soon.</li></ol><hr /><h2><a name="TSO---TCP-Segmentation-Offload-committed" href="#TSO---TCP-Segmentation-Offload-committed" id="TSO---TCP-Segmentation-Offload-committed">TSO - TCP Segmentation Offload committed</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068524.html" title="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068524.html">TSO commit to tcp_output.c</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068524.html" title="TSO commit to tcp_output.c">http://lists.freebsd.org/pipermail/cvs-src/2006-September/068524.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068610.html" title="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068610.html">TSO em(4) hardware support</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/068610.html" title="TSO em(4) hardware support">http://lists.freebsd.org/pipermail/cvs-src/2006-September/068610.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/069493.html" title="http://lists.freebsd.org/pipermail/cvs-src/2006-September/069493.html">Enhanced em(4) TSO hw setup for IPv6 and future protocols</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/cvs-src/2006-September/069493.html" title="Enhanced em(4) TSO hw setup for IPv6 and future protocols">http://lists.freebsd.org/pipermail/cvs-src/2006-September/069493.html</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@freebsd.org">andre@freebsd.org</a>&gt;
-	</p>
-      <p>TSO - TCP Segmentation Offload support has been committed to the
-      network stack of FreeBSD-current in September 2006. With TSO, TCP
-      can send data in the send socket buffer in bulk down to the network
-      card which then does the splitting into MTU sized packets. On bulk
-      high speed sending the performance is increased by 25% (normal
-      writes) to 108% (sendfile). Jack Vogel and Prafulla Deuskar of
-      Intel committed the driver changes for TSO hardware support of
-      em(4) based network cards.</p>
-
-      <p>These changes are scheduled to be backported to FreeBSD 6-STABLE
-      shortly after FreeBSD 6.2-RELEASE is published to appear in
-      upcoming FreeBSD 6.3 early next year.</p>
-
-      <p>This work was sponsored by the TCP/IP Optimization Fundraiser
-      2005.</p>
-    <h3>Open tasks:</h3><ol></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Gvinum-improvements" href="#Gvinum-improvements" id="Gvinum-improvements">Gvinum improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff" title="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff"></a></td><td>
-	    URL: <a href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff" title="">http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff</a></td></tr></table><p>
-	Contact:
-          Ulf
-
-          Lilleengen
-         &lt;<a href="mailto:lulf@pvv.ntnu.no">lulf@pvv.ntnu.no</a>&gt;
-	</p>
-      <p>I thought that since I sent a status report the last time, I
-      might as well send one now.</p>
-
-      <p>Since the last status report I have done work on several of the
-      remaining commands as attach, detach, and finally the concat
-      command to be able to create concatenated volumes with one easy
-      command. The mirror and stripe commands are the next step after
-      this.</p>
-
-      <p>The most important thing I've been working on is maybe the
-      implementation of drivegroups. I have posted a bit information on
-      this mailinglists, but basically, it's a way to group drives with
-      the same configuration. This way, you can make many commands
-      operate on groups instead of drives, and the group-abstraction will
-      handle how the underlying subdisks are created on the drives.
-      In the future one will be able to move groups to different
-      machines, etc.</p>
-
-      <p>I've created a patch of all my work that is not in HEAD yet here
-      (this is a snapshot of my development branch, so how thing's are
-      done might be changed quite fast):
-      <a href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff" shape="rect">
-      http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff</a>
-      </p>
-
-      <p>Be aware that a there will probably be bugs in the code,
-      so don't use it in production yet!</p>
-
-      <p>Thanks to Greg Lehey for offering to help me on getting this
-      into CVS, and all feedback on this has been good.</p>
-    <h3>Open tasks:</h3><ol><li>Remaining components, mirror, stripe and some info
-      commands.</li></ol><hr /><h2><a name="MMC/SD-Support" href="#MMC/SD-Support" id="MMC/SD-Support">MMC/SD Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@freebsd.org">imp@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Bernd
-
-          Walter
-         &lt;<a href="mailto:tisco@freebsd.org">tisco@freebsd.org</a>&gt;
-	</p>
-      <p>The MMC/SD stack got a significant boost this quarter. Warner
-      Losh and Bernd Walter have written a generic MMC/SD flash card
-      stack for FreeBSD, and have implemented a host controller for the
-      AT91RM9200 embedded ARM controller they are each using in separate
-      projects.</p>
-
-      <p>The stack is presently experimental in quality. It is being used
-      as the root file system for these embedded projects. There's been
-      no work done to support hot insertion and removal of cards (neither
-      board wires up the pins necessary, and besides, / disappearing is
-      very bad). There are still many rough edges.</p>
-
-      <p>This is a freshly written stack. It has been written using the
-      SD 1.0 (and recently 2.0) simplified specification, with the
-      SanDisk MMC application notes supplementing. The Linux stack looks
-      good, although not entirely standards conforming (there's work in
-      progress that I've not seen that is supposed to fix this) and it
-      is contaminated with the GPL. The OpenBSD stack also looks
-      interesting, but Warner's experience porting NEWCARD over from
-      NetBSD suggested that a fresh rewrite may be faster, at least for
-      the bus and driver level. Since MMC is fairly simple, a port of the
-      sdhci driver might be possible.</p>
-
-      <p>Please see the open tasks list.</p>
-    <h3>Open tasks:</h3><ol><li>Write sdhci driver, and integrate it into the current
-      stack.</li><li>Add support for hot plugging of cards.</li><li>Add support for MMC cards (SD cards were the first
-      target).</li><li>Expand SD support to include SDIO cards as well as the new
-      SDHC standard cards.</li><li>Export stats via sysctl for each of the cards that are found
-      as a debugging and usage monitoring aid.</li><li>Add support for reading/writing multiple blocks at a time to
-      improve performance.</li><li>Implement any other host controller.</li><li>Add proper support for timeouts.</li></ol><hr /><h2><a name="Sound-Subsystem-Improvements" href="#Sound-Subsystem-Improvements" id="Sound-Subsystem-Improvements">Sound Subsystem Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~ariff/" title="http://people.FreeBSD.org/~ariff/">Some patches.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~ariff/" title="Some patches.">http://people.FreeBSD.org/~ariff/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/projects/ideas/" title="http://www.FreeBSD.org/projects/ideas/">The FreeBSD Project Ideas List.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/ideas/" title="The FreeBSD Project Ideas List.">http://www.FreeBSD.org/projects/ideas/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/soundsystem" title="http://wiki.FreeBSD.org/soundsystem">Wiki page about the sound system.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/soundsystem" title="Wiki page about the sound system.">http://wiki.FreeBSD.org/soundsystem</a></td></tr></table><p>
-	Contact:
-          Ariff
-
-          Abdullah
-         &lt;<a href="mailto:ariff@FreeBSD.org">ariff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Ryan
-
-          Beasley
-         &lt;<a href="mailto:ryanb@FreeBSD.org">ryanb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Multimedia
-
-          Mailinglist
-         &lt;<a href="mailto:multimedia@FreeBSD.org">multimedia@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report we added basic support for envy24ht
-      chips, imported the emu10kx driver into the base system and added
-      support for High Definition Audio (HDA) compatible chips.</p>
-
-      <p>Additionally the work of Ryan Beasley as part of his Google
-      Summer of Code 2006 participation is committed. It adds
-      compatibility to the Open Sound System (OSS) v4 API as far as this
-      was possible. This allows for more sophisticated programs to be
-      written. For example it is now possible to synchronize the start of
-      multiple sound channels. It is also possible for a driver to
-      support more than the AC97 mixer devices, but so far no driver has
-      been extended to support this yet. More about it can be found in
-      the wiki and in the official OSS documentation.</p>
-
-      <p>The wiki page about the sound system was started to describe
-      the current status of the sound system and to provide some
-      information about where we are heading. But more work needs to be
-      done to reach this goal. So far we collected some information about
-      the status of the most recent work in the soundsystem. So if you
-      have a look at it and you think that something important is
-      missing, just tell us about it. While fully prepared content is
-      very welcome, we are even happy about some ideas what we should
-      list on the wiki page.</p>
-    <h3>Open tasks:</h3><ol><li>Have a look at the sound related entries on the ideas
-      list.</li><li>sndctl(1): tool to control non-mixer parts of the sound
-      system (e.g. spdif switching, virtual-3D effects) by an user
-      (instead of the sysctl approach in -current); pcmplay(1),
-      pcmrec(1), pcmutil(1).</li><li>Plugable FEEDER infrastructure. For ease of debugging various
-      feeder stuff and/or as userland library and test suite.</li><li>Extend the wiki page.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Chinese-(Simplified)-Project" href="#Chinese-(Simplified)-Project" id="Chinese-(Simplified)-Project">Chinese (Simplified) Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://cnsnap.cn.FreeBSD.org/zh_CN/" title="http://cnsnap.cn.FreeBSD.org/zh_CN/">Latest snapshot for translated website</a></td><td>
-	    URL: <a href="http://cnsnap.cn.FreeBSD.org/zh_CN/" title="Latest snapshot for translated website">http://cnsnap.cn.FreeBSD.org/zh_CN/</a></td></tr><tr><td><a href="http://cnsnap.cn.FreeBSD.org/doc/zh_CN.GB2312/" title="http://cnsnap.cn.FreeBSD.org/doc/zh_CN.GB2312/">Latest snapshot for translated documentation</a></td><td>
-	    URL: <a href="http://cnsnap.cn.FreeBSD.org/doc/zh_CN.GB2312/" title="Latest snapshot for translated documentation">http://cnsnap.cn.FreeBSD.org/doc/zh_CN.GB2312/</a></td></tr></table><p>
-	Contact:
-          Xin
-
-          LI
-         &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;
-	</p>
-      <p>
-        <p>In the previous quarter we primarily focused on overall
-        quality of the translation rather than just increasing the number
-        of translations, and we have strived to make sure that these
-        translated stuff are up-to-date with their English revisions.
-        Also, we have merged the translated website into the central
-        repository.</p>
-
-        <p>In the next quarter we will focus on developing
-        documentation that will help to attract more developers.</p>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Translate more development related documentation.</li><li>Review more of the currently translated documentation.</li></ol><hr /><h2><a name="Hungarian-translation-of-the-webpages" href="#Hungarian-translation-of-the-webpages" id="Hungarian-translation-of-the-webpages">Hungarian translation of the webpages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://gabor.t-hosting.hu/data/hu/" title="http://gabor.t-hosting.hu/data/hu/">Snapshot</a></td><td>
-	    URL: <a href="http://gabor.t-hosting.hu/data/hu/" title="Snapshot">http://gabor.t-hosting.hu/data/hu/</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report, there has been a lot of progress.
-      I investigated a lot of charset issues and found out that HTML tidy
-      breaks some entities when using iso-8859-2, so HTML tidy had to be
-      disabled for Hungarian pages.</p>
-    <h3>Open tasks:</h3><ol><li>Translate 4 pages.</li><li>Review, fix typos and improve the wording where
-      necessary.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="Libelf" href="#Libelf" id="Libelf">Libelf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/LibElf" title="http://wiki.freebsd.org/LibElf">Wiki page tracking LibELF</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/LibElf" title="Wiki page tracking LibELF">http://wiki.freebsd.org/LibElf</a></td></tr><tr><td><a href="http://wiki.freebsd.org/PmcTools" title="http://wiki.freebsd.org/PmcTools">Wiki page for PmcTools</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/PmcTools" title="Wiki page for PmcTools">http://wiki.freebsd.org/PmcTools</a></td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement/">PMC Tools Project</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="PMC Tools Project">http://people.freebsd.org/~jkoshy/projects/perf-measurement/</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Libelf is a BSD-licensed library for ELF parsing &amp;
-      manipulation implementing the SysV/SVR4 (g)ELF[3] API.</p>
-
-      <p>Current status: Implementation of the library is nearly
-      complete. A TET-based test suite for the API is being worked
-      on.</p>
-    <h3>Open tasks:</h3><ol><li>Reviewers are needed for the code and the test suite. If you
-      have extensions to the stock SysV/SVR4 ELF(3) API that you would
-      like to see in -lelf, please send Joseph an email.</li></ol><hr /><h2><a name="OpenBSD-dhclient" href="#OpenBSD-dhclient" id="OpenBSD-dhclient">OpenBSD dhclient</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most dhclient changes in HEAD have been merged to 6-STABLE for
-      6.2-RELEASE. The highlight of these changes is a fix for runaway
-      dhclient processes when packets are not 4 byte aligned. Further
-      changes including always sending client identifiers are scheduled
-      for merge before the release. Work is ongoing to improve dhclient's
-      interaction with alternate methods of setting interface
-      addresses.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="CPU-Microcode-Update-Software" href="#CPU-Microcode-Update-Software" id="CPU-Microcode-Update-Software">CPU Microcode Update Software</a></h2><p>
-	Contact:
-          Stanislav
-
-          Sedov
-         &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	</p>
-      <p>Last month I was working on a driver/module to update the
-      microcode of Intel or AMD CPUs that support having their
-      microcode updated. As you might know these processors are
-      microcode-driven and this firmware can be updated. Intel(R)
-      often releases microcode updates, and AMD(R) updates can be
-      found in BIOS programs. The work is almost finished now, I just
-      need to find a bit of time to test it on AMD64 systems and
-      perform some code cleanup. The driver also provide a way for
-      userland programs to access the Machine Specific Registers (MSR)
-      and CPUID info for a certain cpu. This will allow some programs
-      like x86info to provide more accurate information about cpus in
-      SMP systems and make assumptions based on the contents of the
-      MSR.</p>
-
-      <p>Thanks to John Baldwin, Kostik Belousov, John-Mark Gurney and
-      Divacky Roman for helping during development.</p>
-    <h3>Open tasks:</h3><ol><li>Perform testing on the AMD64-based systems.</li><li>Write manpage.</li><li>Code cleanup/checks.</li></ol><hr /><h2><a name="FreeBSD/arm-on-Atmel-AT91RM9200" href="#FreeBSD/arm-on-Atmel-AT91RM9200" id="FreeBSD/arm-on-Atmel-AT91RM9200">FreeBSD/arm on Atmel AT91RM9200</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@freebsd.org">imp@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Olivier
-
-          Houchard
-         &lt;<a href="mailto:cognet@freebsd.org">cognet@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD/arm port has grown support for the Atmel AT91RM9200.
-      Boards based on this machine are booting to multiuser off either
-      NFS or an SD card. The onboard serial ports, PIO, ethernet and
-      SD/MMC card controllers are well supported. Support for the SSC,
-      IIC and SPI flash parts in the kernel will be forthcoming
-      shortly.</p>
-
-      <p>In addition to normal kernel support, the port includes a boot
-      loader that can initialize memory and boot off IIC eeprom, SPI
-      DataFlash, BOOTP/TFTP and SD memory cards.</p>
-
-      <p>The port will be included in forthcoming commercial
-      products.</p>
-    <h3>Open tasks:</h3><ol><li>Add support for other members of the AT91 family of arm9
-      processors.</li><li>Finish support for AT45D* flash parts.</li><li>Finish support for USB ports</li><li>Write support for USB Device functionality</li></ol><hr /><h2><a name="Sun-Niagara-port" href="#Sun-Niagara-port" id="Sun-Niagara-port">Sun Niagara port</a></h2><p>
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@FreeBSD.org">kmacy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for the UltraSparc T1 (Niagara) continues to improve.
-      The code has recently been checked into public CVS under
-      sys/sun4v.</p>
-
-      <p>It isn't clear whether or not I will have time to implement full
-      logical domaining support before the APIs become publicly
-      available. Testing indicates that substantial work will be needed
-      before FreeBSD can take full advantage of all 32 threads.</p>
-    <h3>Open tasks:</h3><ol><li>Random testing and bug fixes.</li><li>Import and extend improved mutex profiling support.</li><li>Virtual network and virtual disk device drivers for logical
-      domains.</li></ol><hr /><h2><a name="Xen-Port" href="#Xen-Port" id="Xen-Port">Xen Port</a></h2><p>
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@FreeBSD.org">kmacy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on Xen support has slowly been continuing in perforce. The
-      SOC student fixed several bugs and is continuing to work on it.
-      Someone is needed who has the time to complete dom0 support and
-      shepherd it production level stability.</p>
-
-      <p>Sufficient interest has been expressed in it that it probably
-      makes sense to check it in to public CVS so that more people can
-      try it out. Time permitting, I will bring it up to date and check
-      it in the next month.</p>
-    <h3>Open tasks:</h3><ol><li>dom0 support.</li><li>General testing and bug fixing.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Enlightenment-DR17-support-in-the-ports-tree" href="#Enlightenment-DR17-support-in-the-ports-tree" id="Enlightenment-DR17-support-in-the-ports-tree">Enlightenment DR17 support in the ports tree</a></h2><p>
-	Contact:
-          Stanislav
-
-          Sedov
-         &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	</p>
-      <p>Integration of the new innovative e17 window manager into the
-      ports tree is almost completed. A lot of new e17-related
-      applications was ported, all old ports were updated to the latest
-      stable cvs snapshot. The special framework (bsd.efl.mk) was created
-      to support the whole thing and simplify the creation of dependent
-      ports. I'll commit the changes in the days before the ports
-      freeze.</p>
-
-      <p>Thanks to Sergey Matveychuk (sem@) for providing a machine to
-      place CVS snapshots on. Without his help it will be impossible.</p>
-    <h3>Open tasks:</h3><ol><li>Port Entrance (xdm-like app, but very appealing).</li><li>Port Net and Wlan e17 module.</li><li>Develop FreeBSD-specific e17 apps/modules to use The
-      Ports Collection, system configs, etc.</li></ol><hr /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freshports.org/" title="http://www.freshports.org/">FreshPorts - The Place For Ports</a></td><td>
-	    URL: <a href="http://www.freshports.org/" title="FreshPorts - The Place For Ports">http://www.freshports.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>The new 2U server mentioned in the last report now has a
-      collection of Raptor drives in a RAID-10 configuration. Thanks to
-      very generous donations from the community, I purchased eight of
-      these drives at very good prices. The server will be deployed in
-      the next few weeks.</p>
-
-      <p>There has been quite a bit of work since the last report in
-      June. Some highlights include:</p>
-
-      <ul>
-        <li>New news feed
-        <a href="http://www.freshports.org/backend/" shape="rect">formats</a>,
-
-        including newsfeeds for your watch list.</li>
-
-        <li>Better pages caching for faster response.</li>
-
-        <li>Sanity Test Failures now available
-        <a href="http://news.freshports.org/2006/10/11/sanity-test-failures/" shape="rect">
-        online.</a>
-        </li>
-
-        <li>Ability to
-        <a href="http://news.freshports.org/2006/10/15/all-commits-under-a-point- in-the-tree/" shape="rect">
-        search for all commits</a>
-
-        (ports, doc, src, etc) under a given point in the tree.</li>
-      </ul>
-
-      <p>For more detail, please review the
-      <a href="http://news.freshports.org/" shape="rect">FreshPorts Blog</a>
-
-      .</p>
-    <hr /><h2><a name="Improving-FreeBSD-Ports-Collection-Infrastructure" href="#Improving-FreeBSD-Ports-Collection-Infrastructure" id="Improving-FreeBSD-Ports-Collection-Infrastructure">Improving FreeBSD Ports Collection Infrastructure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n" title="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n">G�bors wiki page.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n" title="G�bors wiki page.">http://wiki.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-          Erwin
-
-          Lansing
-         &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the Google Summer of Code 2006, G�bor worked on several
-      ideas to improve the ports infrastructure:</p>
-
-      <ol>
-        <li>New handling for i386 binary ports.</li>
-
-        <li>Cleanup: use ECHO_CMD and ECHO_MSG in bsd.port.mk
-        properly.</li>
-
-        <li>Add basic infrastructure support for debugging.</li>
-
-        <li>Installing ports with different destination (DESTDIR
-        macro).</li>
-
-        <li>Cleanup: Move fetch shell scripts out of bsd.port.mk.</li>
-
-        <li>Make ports respect CC and CFLAGS.</li>
-
-        <li>Cross-compiling Ports.</li>
-
-        <li>Plist generator tool.</li>
-      </ol>
-
-      <p>The first three items have been completed and the next two
-      items are being worked on. The DESTDIR support was more
-      complicated than presumed and took more time than expected to
-      complete.  G�bor will continue working to finish these tasks and
-      other ports related tasks. FreeBSD is happy to have interested
-      him to keep working on ports and ports infrastructure.</p>
-    <hr /><h2><a name="OCaml-language-support-in-ports" href="#OCaml-language-support-in-ports" id="OCaml-language-support-in-ports">OCaml language support in ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/lang/ocaml/bsd.ocaml.mk?rev=1.3&amp;content-type=text/plain" title="http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/lang/ocaml/bsd.ocaml.mk?rev=1.3&amp;content-type=text/plain">Framework include file</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/lang/ocaml/bsd.ocaml.mk?rev=1.3&amp;content-type=text/plain" title="Framework include file">http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/lang/ocaml/bsd.ocaml.mk?rev=1.3&amp;content-type=text/plain</a></td></tr></table><p>
-	Contact:
-          Stanislav
-
-          Sedov
-         &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	</p>
-      <p>There were a number of OCaml ports in our tree, and each of them
-      was doing the same work by maintaining OCaml ld.conf in the correct
-      state, installing/removing their files/entries etc. To simplify the
-      task of OCaml-language ports creation, the special framework
-      (bsd.ocamk.mk) was developed and most of the ports were converted to
-      use this framework. This allowed a lot of duplicate code to be
-      removed. This new framework handles all the things required to
-      install an OCaml-language library and properly register it.
-      bsd.ocaml.mk also contains knobs to deal with findlib-powered
-      libraries, modify ld.conf in the proper way, etc. Also, a lot of
-      new Ocaml-related ports were added.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="AsiaBSDCon-2007" href="#AsiaBSDCon-2007" id="AsiaBSDCon-2007">AsiaBSDCon 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.asiabsdcon.org/" title="http://www.asiabsdcon.org/">Conference Web Site</a></td><td>
-	    URL: <a href="http://www.asiabsdcon.org/" title="Conference Web Site">http://www.asiabsdcon.org/</a></td></tr></table><p>
-	Contact:
-          Hiroki
-
-          Sato
-         &lt;<a href="mailto:hrs@freebsd.org">hrs@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:secretary@asiabsdcon.org">secretary@asiabsdcon.org</a>&gt;
-	</p>
-      <p>Web site is up and we're soliciting papers and presentations.
-      Some tutorials are already scheduled. Email
-      <a href="mailto:secretary@asiabsdcon.org" shape="rect">
-      secretary@asiabsdcon.org</a>
-
-      if you have questions or submissions.</p>
-    <h3>Open tasks:</h3><ol><li>Send in more papers!</li></ol><hr /><h2><a name="BSDCan-2007" href="#BSDCan-2007" id="BSDCan-2007">BSDCan 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/" title="http://www.bsdcan.org/"></a></td><td>
-	    URL: <a href="http://www.bsdcan.org/" title="">http://www.bsdcan.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>The dates for
-      <a href="http://www.bsdcan.org/2007/" shape="rect">BSDCan 2007</a>
-      have been set: 11-12 May 2007. As is usual, BSDCan will be held at
-      University of Ottawa, with two days of tutorials prior to the
-      conference starting.</p>
-
-      <p>The
-      <a href="http://www.bsdcan.org/2007/papers.php" shape="rect">call for papers</a>
-
-      will go out in mid December. Start thinking about your submissions
-      now!</p>
-    <hr /><h2><a name="EuroBSDCon-2006" href="#EuroBSDCon-2006" id="EuroBSDCon-2006">EuroBSDCon 2006</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon.org/" title="http://www.eurobsdcon.org/">EuroBSDCon Home Page</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org/" title="EuroBSDCon Home Page">http://www.eurobsdcon.org/</a></td></tr><tr><td><a href="http://www.eurobsdcon.org/register/" title="http://www.eurobsdcon.org/register/">Registration Page</a></td><td>
-	    URL: <a href="http://www.eurobsdcon.org/register/" title="Registration Page">http://www.eurobsdcon.org/register/</a></td></tr></table><p>
-	Contact:
-          EuroBSDCon Organizing Committee
-
-
-
-         &lt;<a href="mailto:info@eurobsdcon.org">info@eurobsdcon.org</a>&gt;
-	</p>
-      <p>EuroBSDCon 2006 is taking place in Milan (Italy), from the 10th
-      to the 12th of November.</p>
-
-      <p>EuroBSDCon represents the biggest gathering for BSD developers
-      from the old continent, as well as users and passionates from
-      around the World. It is also a chance to share experiences,
-      know-how, and cultures.</p>
-
-      <p>The program is rich in talks about FreeBSD, with topics ranging
-      from "How the FreeBSD ports collection works" to "Interrupt
-      Filtering in FreeBSD". This means that both the novice and the
-      hacker can enjoy the conference.</p>
-
-      <p>Registration is open. The EuroBSDCon Organizing Committee hopes
-      to see you in Milan.</p>
-    <hr /><h2><a name="FreeBSD-Multimedia-Resources-List" href="#FreeBSD-Multimedia-Resources-List" id="FreeBSD-Multimedia-Resources-List">FreeBSD Multimedia Resources List</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mavetju.org/unix/multimedia.php" title="http://www.mavetju.org/unix/multimedia.php"></a></td><td>
-	    URL: <a href="http://www.mavetju.org/unix/multimedia.php" title="">http://www.mavetju.org/unix/multimedia.php</a></td></tr><tr><td><a href="http://www.mavetju.org/unix/multimedia-rss.php" title="http://www.mavetju.org/unix/multimedia-rss.php">RSS version</a></td><td>
-	    URL: <a href="http://www.mavetju.org/unix/multimedia-rss.php" title="RSS version">http://www.mavetju.org/unix/multimedia-rss.php</a></td></tr></table><p>
-	Contact:
-          Edwin
-
-          Groothuis
-         &lt;<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have setup the FreeBSD Multimedia Resources List, a
-      one-stop-shop for FreeBSD related podcasts, vodcasts and
-      audio/video resources. Hopefully this list will make it easier for
-      people to find and keep up to date with these recordings. The
-      overview is available as a normal HTML page and as an XML/RSS
-      feed.</p>
-
-      <p>The ultimate goal is to have this list to reside under the
-      www.FreeBSD.org umbrella.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2006-10-2006-12.html b/website/content/en/status/report-2006-10-2006-12.html
deleted file mode 100644
index 5ac6e1d617..0000000000
--- a/website/content/en/status/report-2006-10-2006-12.html
+++ /dev/null
@@ -1,1777 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Happy New Year. This Report covers the last quarter of a exciting
-    year 2006 for FreeBSD development. FreeBSD 6.2 is finally out of the
-    door and work towards FreeBSD 7.0 is gearing up. Some of the projects
-    in this report will be part of that effort, others are already in the
-    tree. Many projects need your help with testing and otherwise. Please
-    see the "Open tasks" sections for more information.</p><p>The BSD crowd will meet at
-    <a href="http://www.asiabsdcon.org/" shape="rect">AsiaBSDCon</a>
-    March 8-10th in Tokyo and a two day FreeBSD developer summit will be
-    held at
-    <a href="http://www.bsdcan.org/" shape="rect">BSDCan</a>
-
-    May 16-19th in Ottawa. Finally,
-    <a href="http://2007.eurobsdcon.org/" shape="rect">EuroBSDCon</a>
-
-    September 14-15th in Copenhagen is already looking for papers.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeSBIE">FreeSBIE</a></li><li><a href="#iSCSI-Initiator">iSCSI Initiator</a></li><li><a href="#Network-Stack-Virtualization">Network Stack Virtualization</a></li><li><a href="#New-USB-Stack">New USB Stack</a></li><li><a href="#Past-and-Future-PR-Closing-Events">Past and Future PR Closing Events</a></li><li><a href="#Porting-ZFS-to-FreeBSD">Porting ZFS to FreeBSD</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-MAC-Framework">TrustedBSD MAC Framework</a></li><li><a href="#TrustedBSD-priv(9)">TrustedBSD priv(9)</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Automatic-TCP-Send-and-Receive-Socket-Buffer-Sizing">Automatic TCP Send and Receive Socket Buffer Sizing</a></li><li><a href="#FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></li><li><a href="#ipfw-NAT-and-libalias">ipfw NAT and libalias</a></li><li><a href="#Multi-link-PPP-daemon-(MPD)">Multi-link PPP daemon (MPD)</a></li><li><a href="#Wireless-Networking">Wireless Networking</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Cryptographic-Subsystem">Cryptographic Subsystem</a></li><li><a href="#GEOM-Multipath">GEOM Multipath</a></li><li><a href="#Interrupt-Filtering">Interrupt Filtering</a></li><li><a href="#Sound-Subsystem-Improvements">Sound Subsystem Improvements</a></li><li><a href="#Update-of-the-Linux-Compatibility-Environment-in-the-Kernel">Update of the Linux Compatibility Environment in the
-    Kernel</a></li></ul><h3><a href="#Hardware-Drivers">Hardware Drivers</a></h3><ul><li><a href="#Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite-driver)">Bt878 Audio Driver (aka FusionHDTV 5 Lite driver)</a></li><li><a href="#Intel-3945ABG-Wireless-LAN-Driver:-wpi">Intel 3945ABG Wireless LAN Driver: wpi</a></li><li><a href="#MPT-LSI-Logic-Host-Adapters:-mpt">MPT LSI-Logic Host Adapters: mpt</a></li><li><a href="#QLogic-SCSI-and-Fibre-Channel:-isp">QLogic SCSI and Fibre Channel: isp</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Hungarian-Translation-of-the-Webpages">Hungarian Translation of the Webpages</a></li><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#BSNMP---More-Ongoing-and-Upcoming-Work">BSNMP - More Ongoing and Upcoming Work</a></li><li><a href="#BSNMP-Bridge-Module">BSNMP Bridge Module</a></li><li><a href="#BSNMP-Client-Tools">BSNMP Client Tools</a></li><li><a href="#Libelf">Libelf</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#ARM/XScale-Port">ARM/XScale Port</a></li><li><a href="#FreeBSD/powerpc-on-Freescale-MPC8555">FreeBSD/powerpc on Freescale MPC8555</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></li><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Updating-X.org-FreeBSD-Ports-to-7.2">Updating X.org FreeBSD Ports to 7.2</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan-2007">BSDCan 2007</a></li><li><a href="#EuroBSDCon-2007">EuroBSDCon 2007</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="FreeSBIE" href="#FreeSBIE" id="FreeSBIE">FreeSBIE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeSBIE.org" title="http://www.FreeSBIE.org"></a></td><td>
-	    URL: <a href="http://www.FreeSBIE.org" title="">http://www.FreeSBIE.org</a></td></tr><tr><td><a href="http://users.gufi.org/~rionda/20relnotes/" title="http://users.gufi.org/~rionda/20relnotes/">FreeSBIE 2.0 Release Notes Preview</a></td><td>
-	    URL: <a href="http://users.gufi.org/~rionda/20relnotes/" title="FreeSBIE 2.0 Release Notes Preview">http://users.gufi.org/~rionda/20relnotes/</a></td></tr><tr><td><a href="http://users.gufi.org/~rionda/20screen/" title="http://users.gufi.org/~rionda/20screen/">FreeSBIE 2.0 Screenshots Preview</a></td><td>
-	    URL: <a href="http://users.gufi.org/~rionda/20screen/" title="FreeSBIE 2.0 Screenshots Preview">http://users.gufi.org/~rionda/20screen/</a></td></tr></table><p>
-	Contact:
-          Matteo
-
-          Riondato
-         &lt;<a href="mailto:matteo@FreeBSD.org">matteo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeSBIE
-
-          Staff
-         &lt;<a href="mailto:staff@FreeSBIE.org">staff@FreeSBIE.org</a>&gt;
-	<br />
-	Contact:
-          FreeSBIE
-
-          Mailing List
-         &lt;<a href="mailto:freesbie@gufi.org">freesbie@gufi.org</a>&gt;
-	</p>
-      <p>FreeSBIE is approaching the 2.0-RELEASE. The first release
-      candidate proved to be good enough but a second one will probably
-      be released. An external developer is working on integrating
-      BSDInstaller in FreeSBIE 2.0 and this may cause a little delay of
-      the release date. Release Notes were written and need to be updated
-      with the current list of packages. A script which allows to switch
-      Tor+Privoxy on and off was added and its usage was documented. The
-      2.0-RELEASE is near, hopefully near the end of January but this
-      will also depend on when FreeBSD 6.2-RELEASE will be released.</p>
-    <hr /><h2><a name="iSCSI-Initiator" href="#iSCSI-Initiator" id="iSCSI-Initiator">iSCSI Initiator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.1.tar.bz2" title="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.1.tar.bz2"></a></td><td>
-	    URL: <a href="ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.1.tar.bz2" title="">ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.1.tar.bz2</a></td></tr></table><p>
-	Contact:
-          Daniel
-
-          Braniss
-         &lt;<a href="mailto:danny@cs.huji.ac.il">danny@cs.huji.ac.il</a>&gt;
-	</p>
-      <p>Though it is still a work in progress, it now supports more
-      targets, has login CHAP authentication and header/data digest. It
-      will also recover from a lost connection - most of the time.</p>
-    <h3>Open tasks:</h3><ol><li>instrumentation</li><li>task management support</li><li>improve the error recovery</li></ol><hr /><h2><a name="Network-Stack-Virtualization" href="#Network-Stack-Virtualization" id="Network-Stack-Virtualization">Network Stack Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://imunes.tel.fer.hr/virtnet/" title="http://imunes.tel.fer.hr/virtnet/"></a></td><td>
-	    URL: <a href="http://imunes.tel.fer.hr/virtnet/" title="">http://imunes.tel.fer.hr/virtnet/</a></td></tr></table><p>
-	Contact:
-          Marko
-
-          Zec
-         &lt;<a href="mailto:zec@fer.hr">zec@fer.hr</a>&gt;
-	</p>
-      <p>The network stack virtualization project aims at extending the
-      FreeBSD kernel to maintain multiple independent instances of
-      networking state. This will allow for complete networking
-      independence between jails on a system, including giving each jail
-      its own firewall, virtual network interfaces, rate limiting,
-      routing tables, and IPSEC configuration.</p>
-
-      <p>The prototype currently virtualizes the basic INET and INET6
-      kernel structures and subsystems, including the TCP machinery and
-      the IPFW firewall. The focus is currently being kept on resolving
-      bugs and sporadic lockups, and defining the internal and management
-      APIs. It is expected that within the next month the code will
-      become sufficiently complete and stable for testing by early
-      adopters.</p>
-    <hr /><h2><a name="New-USB-Stack" href="#New-USB-Stack" id="New-USB-Stack">New USB Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb">Current USB files</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb" title="Current USB files">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb</a></td></tr><tr><td><a href="http://www.turbocat.net/~hselasky/usb4bsd" title="http://www.turbocat.net/~hselasky/usb4bsd">My USB homepage</a></td><td>
-	    URL: <a href="http://www.turbocat.net/~hselasky/usb4bsd" title="My USB homepage">http://www.turbocat.net/~hselasky/usb4bsd</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last three months there has not been so much activity
-      in the USB project. Some regression issues have been reported and
-      fixed. Bernd Walter reports that he has got the new USB stack
-      working on ARM processors with some minor tweaks. Markus Brueffer
-      reports that he is working on the USB HID parser and support. A
-      current issue with the new USB stack is that the EHCI driver does
-      not work on the Sparc64 architecture. If someone has got a Sparc64
-      with FreeBSD 7-CURRENT on and can lend the USB project the root
-      password, a serial console and a USB test device, for example a USB
-      memory stick, that would be much appreciated. Another unresolved
-      issue is that the ural(4) USB device driver does not always work.
-      This is currently being worked on.</p>
-
-      <p>If you want to test the new USB stack, check out the USB
-      perforce tree or download the SVN version of the USB driver from my
-      USB homepage. At the moment the tarballs are a little out of
-      date.</p>
-
-      <p>Ideas and comments with regard to the new USB API are welcome at
-
-      <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-usb" shape="rect">
-      freebsd-usb@FreeBSD.org</a>
-
-      .</p>
-    <hr /><h2><a name="Past-and-Future-PR-Closing-Events" href="#Past-and-Future-PR-Closing-Events" id="Past-and-Future-PR-Closing-Events">Past and Future PR Closing Events</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Bugathons" title="http://wiki.freebsd.org/Bugathons"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Bugathons" title="">http://wiki.freebsd.org/Bugathons</a></td></tr></table><p>
-	Contact:
-          Florent
-
-          Thoumie
-         &lt;<a href="mailto:flz@FreeBSD.org">flz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Following the example of our NetBSD friends, we organized a
-      couple of Bugathons to help decreasing the open PR count. At first,
-      it was decided to make it a monthly event focused on both src,
-      ports and doc. Audience decreased with each Bugathon organized and
-      less non-ports committers attended the events. So from now on, we
-      will focus on ports (making it a Portathon) and organize a new
-      event after the end of each ports freeze (that should be twice a
-      year, at most).</p>
-    <hr /><h2><a name="Porting-ZFS-to-FreeBSD" href="#Porting-ZFS-to-FreeBSD" id="Porting-ZFS-to-FreeBSD">Porting ZFS to FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs">Source code.</a></td><td>
-	    URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="Source code.">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs</a></td></tr><tr><td><a href="http://www.opensolaris.org/os/community/zfs/porting/" title="http://www.opensolaris.org/os/community/zfs/porting/">ZFS porting site.</a></td><td>
-	    URL: <a href="http://www.opensolaris.org/os/community/zfs/porting/" title="ZFS porting site.">http://www.opensolaris.org/os/community/zfs/porting/</a></td></tr><tr><td><a href="http://docs.FreeBSD.org/cgi/mid.cgi?20060822104516.GB16033" title="http://docs.FreeBSD.org/cgi/mid.cgi?20060822104516.GB16033">ZFS port announce.</a></td><td>
-	    URL: <a href="http://docs.FreeBSD.org/cgi/mid.cgi?20060822104516.GB16033" title="ZFS port announce.">http://docs.FreeBSD.org/cgi/mid.cgi?20060822104516.GB16033</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ZFS file system works quite well on FreeBSD now. The first
-      patchset has already been published on the
-      <a herf="http://lists.freebsd.org/mailman/listinfo/freebsd-fs" shape="rect">
-      freebsd-fs@FreeBSD.org mailing list</a>
-
-      .</p>
-
-      <p>All file system methods are already implemented (except
-      ACL-related). Basically all stress tests I tried work, even under
-      very high load. There is still a problem with memory allocation,
-      which can get out of control, but from what I know the SUN guys
-      also work on this.</p>
-
-      <p>Recently I have been working on a file system regression test
-      suite. From what I found, there are no such test suites for free.
-      I've already more than 3000 tests and I'm testing correctness of
-      most file system related syscalls (chflags, chmod, chown, link,
-      mkdir, mkfifo, open, rename, rmdir, symlink, truncate, unlink). I'm
-      also working to make it usable on other operating systems (like
-      Solaris, where it already works and Linux).</p>
-
-      <p>Few days ago I also (almost) finished NFS support. You can't use
-      the 'zfs share' command yet, but you can export file systems via
-      /etc/exports and you can also access snapshots. It was quite hard,
-      because snapshots are separate file systems and after exporting the
-      main file system, we need to also serve data from snapshots under
-      it.</p>
-
-      <p>The one big thing which is missing is ACL support. This is not
-      an easy task, because we first have to make some decisions.
-      Currently we use POSIX ACLs in our UFS, but the market is moving
-      slowly to NTFS/NFSv4-type ACLs. In Solaris they use POSIX ACLs for
-      UFS and NFSv4-type ACLs for ZFS and we probably also want to use
-      NFSv4-type ACLs in our ZFS, which requires some work outside
-      ZFS.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/audit.html" title="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/audit.html" title="TrustedBSD Audit Page">http://www.TrustedBSD.org/audit.html</a></td></tr><tr><td><a href="http://www.OpenBSM.org/" title="http://www.OpenBSM.org/">OpenBSM Page</a></td><td>
-	    URL: <a href="http://www.OpenBSM.org/" title="OpenBSM Page">http://www.OpenBSM.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Christian
-
-          Peron
-         &lt;<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Wayne
-
-          Salamon
-         &lt;<a href="mailto:wsalamon@FreeBSD.org">wsalamon@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD 6.2-RELEASE, the first release of FreeBSD with
-      experimental audit support is now available. The plan is to make
-      audit a full production feature as of FreeBSD 6.3-RELEASE, with
-      "options AUDIT" compiled in by default. A TODO list has been posted
-      to trustedbsd-audit.</p>
-
-      <p>OpenBSM 1.0 alpha 13, which includes support for XML record
-      printing, additional 64-bit token types, additional audit events,
-      and more cross-platform build support, has been released. OpenBSM
-      1.0 alpha 14, which adds support for warnings clean building with
-      gcc 4.1, will be released shortly. The new OpenBSM release will be
-      merged to FreeBSD CVS in late January or early February.</p>
-    <h3>Open tasks:</h3><ol><li>Complete assignment of audit events to non-native and a few
-      remaining native system calls. Add additional system call argument
-      auditing.</li><li>Merge MAC Framework hooks allowing MAC modules to control
-      access to kernel audit services. Refine and merge MAC labeling
-      support in audit, including support for MAC annotations in the
-      audit trail.</li><li>Complete pass through user space services adding audit
-      support to system management tools (and ftpd). Work with third
-      party software maintainers to add audit support for applications
-      like xdm/kdm/gdm.</li><li>Merge latest OpenBSM, including XML output support.</li></ol><hr /><h2><a name="TrustedBSD-MAC-Framework" href="#TrustedBSD-MAC-Framework" id="TrustedBSD-MAC-Framework">TrustedBSD MAC Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/mac.html" title="http://www.TrustedBSD.org/mac.html">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/mac.html" title="TrustedBSD Project">http://www.TrustedBSD.org/mac.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>Most work on the MAC Framework during this period, other than as
-      relates to the priv(9) project described in a separate status
-      report, has been in refinement of the structure of the framework.
-      <ul>
-        <li>Add two new entry points allowing MAC Framework policy
-        modules to grant or limit fine-grained system privileges.</li>
-
-        <li>A sample mac_priv(4) policy module has been created
-        demonstrating how a MAC Framework policy module can grant
-        specific system privileges to specific users.</li>
-
-        <li>Commenting throughout the MAC Framework significantly
-        extended.</li>
-
-        <li>Correct a bug in which the original ifnet label was copied to
-        user space via ioctl, rather than the thread-local copy.</li>
-
-        <li>mac_enforce_subsystem debugging sysctls removed, as some
-        policies rely on access control checks being called even when
-        non-enforcing (specifically, information flow related
-        policies).</li>
-
-        <li>Break out mac.h include file into mac.h (user API, system
-        calls) and mac_framework.h (in-kernel interface to the MAC
-        Framework). Move non-user MAC include files from src/sys to
-        src/sys/security/mac. Move and break out kern_mac.c into
-        mac_framework.c and mac_syscalls.c. The MAC Framework is now
-        entirely located in src/sys/security/mac.</li>
-
-        <li>Export the MAC Framework version via a read-only sysctl and
-        provide a #define version usable by policies.</li>
-
-        <li>MAC Framework locking optimized to optimistically expect no
-        write lock contention during read locking.</li>
-      </ul>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Now that the MAC Framework has been fully moved to
-      src/sys/security/mac, embark on the 'mac2' interface cleanup, in
-      which many MAC Framework entry points are renamed for consistency.
-      This will require most MAC Framework policy modules to be modified
-      between FreeBSD 6.x and FreeBSD 7.x, although in a way that can be
-      largely done using sed.</li><li>Add accessor functions for policies retrieving per-policy
-      label data from labels, so that policy modules do not compile in
-      the binary layout of struct label. This will allow future
-      optimization of the label layout.</li><li>Complete integration of audit and MAC support, allowing MAC
-      policy modules to control access to audit interfaces, and allowing
-      them to annotate audit records.</li></ol><hr /><h2><a name="TrustedBSD-priv(9)" href="#TrustedBSD-priv(9)" id="TrustedBSD-priv(9)">TrustedBSD priv(9)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>TrustedBSD priv(9) replaces suser(9) as an in-kernel interface
-      for checking privilege in FreeBSD 7.x. Each privilege check now
-      takes a specific named privilege. This allows both centralization
-      of jail logic relating to privilege, which is currently distributed
-      around the kernel at the point of each call to suser(9), and allows
-      instrumentation of the privilege logic by the MAC Framework. Two
-      new MAC Framework entry points, one to grant and the other to limit
-      privilege, are now available, providing fine-grained control of
-      kernel privilege by policy modules. This lays the kernel
-      infrastructure groundwork for further refinement and extension of
-      the kernel privilege model. The priv(9) implementation has been
-      committed to FreeBSD 7-CURRENT.</p>
-
-      <p>This software was developed by Robert N. M. Watson for the
-      TrustedBSD Project under contract to nCircle Network Security,
-      Inc.</p>
-    <h3>Open tasks:</h3><ol><li>Complete review of kernel privilege checks, removal of
-      suser(9) jail flag now that checks are centralized.</li><li>Explore possible changes to kernel privilege model along
-      lines of POSIX.1e privileges, the Solaris privilege interface, etc.
-      This has been explored previously as part of the TrustedBSD
-      Capabilities project also.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en/articles/pr-guidelines/" title="http://www.FreeBSD.org/doc/en/articles/pr-guidelines/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en/articles/pr-guidelines/" title="">http://www.FreeBSD.org/doc/en/articles/pr-guidelines/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en/articles/problem-reports/" title="http://www.FreeBSD.org/doc/en/articles/problem-reports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en/articles/problem-reports/" title="">http://www.FreeBSD.org/doc/en/articles/problem-reports/</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Ceri
-
-          Davies
-         &lt;<a href="mailto:ceri@FreeBSD.org">ceri@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Bugbusting team is a team of volunteers keeping
-      track of various PR tickets in the GNATS application. Currently the
-      Bugbusting team is investigating old PR tickets, checking whether
-      they are still accurate, checking what needs to be done to fix the
-      issues reported and make sure that the developers team can focus on
-      the latest releases.</p>
-
-      <p>The team is always in need of volunteers willing to give a hand
-      to resolve the old tickets and get the best feedback that is needed
-      for the open tickets.</p>
-
-      <p>Please contact
-      <a href="mailto:FreeBSD-bugbusters@FreeBSD.org" shape="rect">
-      FreeBSD-bugbusters@FreeBSD.org</a>
-
-      if you want more information about the things that need to be
-      done.</p>
-    <h3>Open tasks:</h3><ol><li>Checkout old PR tickets, getting the proper feedback and
-      finally fix and/or resolve the tickets.</li></ol><hr /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/security/" title="http://www.FreeBSD.org/security/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/security/" title="">http://www.FreeBSD.org/security/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/administration.html#t-secteam" title="http://www.FreeBSD.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/administration.html#t-secteam" title="">http://www.FreeBSD.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.FreeBSD.org/" title="http://vuxml.FreeBSD.org/"></a></td><td>
-	    URL: <a href="http://vuxml.FreeBSD.org/" title="">http://vuxml.FreeBSD.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the time since the last status report, four security
-      advisories have been issued concerning problems in the base system
-      of FreeBSD (three in 2006 and one in 2007); of these, one problem
-      was in "contributed" code, while the remaining three were in code
-      maintained within FreeBSD. The Vulnerabilities and Exposures Markup
-      Language (VuXML) document has continued to be updated by the
-      Security Team and Ports Committers documenting new vulnerabilities
-      in the FreeBSD Ports Collection; since the last status report, 55
-      new entries have been added, bringing the total up to 869.</p>
-
-      <p>In order to streamline security team operations and ensure that
-      incoming emails are promptly acknowledged, Remko Lodder has been
-      appointed the security team secretary.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 4.11, FreeBSD 5.5, FreeBSD 6.0, FreeBSD 6.1,
-      and FreeBSD 6.2. The respective End of Life dates of supported
-      releases are listed on the web site; of particular note, FreeBSD
-      4.11 and FreeBSD 6.0 will cease to be supported at the end of
-      January 2007.</p>
-    <hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/releases/6.2R/announce.html" title="http://www.FreeBSD.org/releases/6.2R/announce.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/6.2R/announce.html" title="">http://www.FreeBSD.org/releases/6.2R/announce.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/snapshots/" title="http://www.FreeBSD.org/snapshots/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/snapshots/" title="">http://www.FreeBSD.org/snapshots/</a></td></tr></table><p>
-	Contact:
-          Release Engineering Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The recent activities of the Release Engineering team have
-      centered around FreeBSD 6.2-RELEASE, which is now available for
-      downloading. This is the latest release from the RELENG_6 branch,
-      and includes many new performance and stability improvements, bug
-      fixes, and new features. The release notes and errata notes for
-      FreeBSD 6.2 contain more specific information about what's new in
-      this version. We thank the FreeBSD developer and user community for
-      their efforts towards making this release possible.</p>
-
-      <p>The Release Engineering Team also produced snapshots of FreeBSD
-      CURRENT in November 2006 and January 2007. These snapshots have not
-      received extensive testing, and should not be used in production
-      environments. However, they can be used for testing or
-      experimentation, and show the kinds of functionality that can be
-      expected in future FreeBSD releases.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org" title="http://www.FreeBSDFoundation.org">The FreeBSD Foundation</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org" title="The FreeBSD Foundation">http://www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@FreeBSD.org">deb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation ended 2006 raising over $100,000. We
-      received commitments for another $55,000 in donations for the Fall
-      Fundraiser. We fell short of our goal of raising $200,000. But, we
-      are working hard to fill this gap, early in 2007, so we can
-      continue with the same level of support for the project and
-      community. Please go to
-      <a href="http://www.freebsdfoundation.org/donate/" shape="rect">
-      http://www.freebsdfoundation.org/donate/</a>
-
-      to find out how to make a donation to the foundation.</p>
-
-      <p>We added a donors page to our website to acknowledge our
-      generous donors. We negotiated and are now actively managing a
-      joint technology project with NLNet and the University of Zagreb to
-      develop virtualized network stack support for FreeBSD. We sponsored
-      AsiaBSDCon and are now accepting travel grant applications for this
-      conference.</p>
-
-      <p>We are working to upgrade the project's network testbed with
-      10Gigabit interconnects. Cisco has generously donated a 10Gigabit
-      switch and we have received network adapters from Myricom,
-      Neterion, Intel, and Chelsio. Adapters from other vendors are being
-      solicited so that we can do interoperability testing.</p>
-
-      <p>For more information on what we've been up to, check out our
-      end-of-year newsletter at
-      <a href="http://www.freebsdfoundation.org/press/2006Dec-newsletter.shtml" shape="rect">
-      http://www.freebsdfoundation.org/press/2006Dec-newsletter.shtml</a>
-
-      .</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Automatic-TCP-Send-and-Receive-Socket-Buffer-Sizing" href="#Automatic-TCP-Send-and-Receive-Socket-Buffer-Sizing" id="Automatic-TCP-Send-and-Receive-Socket-Buffer-Sizing">Automatic TCP Send and Receive Socket Buffer Sizing</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212.diff" title="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212.diff">Patch against 7-CURRENT</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212.diff" title="Patch against 7-CURRENT">http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212.diff</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212-RELENG_6.diff" title="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212-RELENG_6.diff">Patch against RELENG_6</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212-RELENG_6.diff" title="Patch against RELENG_6">http://people.FreeBSD.org/~andre/tcp_auto_buf-20061212-RELENG_6.diff</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>Normally the socket buffers are static (either derived from
-      global defaults or set with setsockopt) and do not adapt to real
-      network conditions. Two things happen: a) your socket buffers are
-      too small and you can't reach the full potential of the network
-      between both hosts; b) your socket buffers are too big and you
-      waste a lot of kernel memory for data just sitting around.</p>
-
-      <p>With automatic TCP send and receive socket buffers we can start
-      with a small buffer and quickly grow it in parallel with the TCP
-      congestion window to match real network conditions.</p>
-
-      <p>FreeBSD has a default 32K send socket buffer. This supports a
-      maximal transfer rate of only slightly more than 2Mbit/s on a 100ms
-      RTT trans-continental link. Or at 200ms just above 1Mbit/s. With
-      TCP send buffer auto scaling and the default values below it
-      supports 20Mbit/s at 100ms and 10Mbit/s at 200ms. That's an
-      improvement of factor 10, or 1000%. For the receive side it looks
-      slightly better with a default of 64K buffer size.</p>
-
-      <p>The automatic send buffer sizing patch is currently running on
-      one half of the FTP.FreeBSD.ORG cluster w/o any problems so far.
-      Against this machine with the automatic receive buffer sizing patch
-      I can download at 5.7 MBytes per second. Without patch it maxed out
-      at 1.6 MBytes per second as the delay bandwidth product became
-      equal to the static socket buffer size without hitting the limits
-      of the physical link between the machines. My test machine is about
-      35ms from that FTP.FreeBSD.ORG and connected through a moderately
-      loaded 100Mbit Internet link.</p>
-
-      <p>New sysctls are:
-      <ul>
-        <li>net.inet.tcp.sendbuf_auto=1 (enabled)</li>
-
-        <li>net.inet.tcp.sendbuf_inc=8192 (8K, step size)</li>
-
-        <li>net.inet.tcp.sendbuf_max=262144 (256K, growth limit)</li>
-
-        <li>net.inet.tcp.recvbuf_auto=1 (enabled)</li>
-
-        <li>net.inet.tcp.recvbuf_inc=16384 (16K, step size)</li>
-
-        <li>net.inet.tcp.recvbuf_max=262144 (256K, growth limit)</li>
-      </ul>
-      </p>
-    <hr /><h2><a name="FAST_IPSEC-Upgrade" href="#FAST_IPSEC-Upgrade" id="FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~gnn/fast_ipv6.patch" title="http://www.FreeBSD.org/~gnn/fast_ipv6.patch">Host only patch</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~gnn/fast_ipv6.patch" title="Host only patch">http://www.FreeBSD.org/~gnn/fast_ipv6.patch</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/gnn/" title="http://blogs.FreeBSDish.org/gnn/">gnn's networking blog</a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/gnn/" title="gnn's networking blog">http://blogs.FreeBSDish.org/gnn/</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Just this week I got routing working for the FAST_IPSEC and IPv6
-      code. Now there are memory smash problems, and then we need to
-      remove the old GIANT lock. I hope to produce another patch with the
-      routing code working in the next week.</p>
-    <h3>Open tasks:</h3><ol><li>Test the patch!!!!</li></ol><hr /><h2><a name="ipfw-NAT-and-libalias" href="#ipfw-NAT-and-libalias" id="ipfw-NAT-and-libalias">ipfw NAT and libalias</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Paolo
-
-          Pisati
-         &lt;<a href="mailto:piso@FreeBSD.org">piso@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for in-kernel NAT, redirect and LSNAT for ipfw was
-      committed to HEAD, and i encourage people to test it so we can
-      quickly discover/fix bugs.</p>
-
-      <p>To add these features to ipfw, compile a new kernel adding
-      "options IPFIREWALL_NAT" to your kernel config or, in case you use
-      modules, add "CFLAGS += -DIPFIREWALL_NAT" to your make.conf.</p>
-    <h3>Open tasks:</h3><ol><li>Teach libalias to handle mbufs (this will fix TSO-capable
-      NICs).</li><li>Add support for hardware checksum offloading.</li></ol><hr /><h2><a name="Multi-link-PPP-daemon-(MPD)" href="#Multi-link-PPP-daemon-(MPD)" id="Multi-link-PPP-daemon-(MPD)">Multi-link PPP daemon (MPD)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sourceforge.net/projects/mpd/" title="http://sourceforge.net/projects/mpd/">Project home</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/mpd/" title="Project home">http://sourceforge.net/projects/mpd/</a></td></tr><tr><td><a href="http://mpd.cvs.sourceforge.net/*checkout*/mpd/mpd/doc/changes.xml" title="http://mpd.cvs.sourceforge.net/*checkout*/mpd/mpd/doc/changes.xml">ChangeLog</a></td><td>
-	    URL: <a href="http://mpd.cvs.sourceforge.net/*checkout*/mpd/mpd/doc/changes.xml" title="ChangeLog">http://mpd.cvs.sourceforge.net/*checkout*/mpd/mpd/doc/changes.xml</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Motin
-         &lt;<a href="mailto:mav@alkar.net">mav@alkar.net</a>&gt;
-	<br />
-	Contact:
-          Archie
-
-          Cobbs
-         &lt;<a href="mailto:archie@FreeBSD.org">archie@FreeBSD.org</a>&gt;
-	</p>
-      <p>MPD is moving to the next major release - mpd4_0. At the end of
-      October one more beta version (4_0b5) was released and first RC is
-      planned soon.</p>
-
-      <p>Since 3_18 and 4_0b4 numerous bugs and cases of incorrect
-      internal handling have been fixed. Performance has been increased
-      and system requirements reduced.</p>
-
-      <p>Many new features have been implemented:
-      <ul>
-        <li>IPv6 support</li>
-
-        <li>NAT (using the ng_nat(4) node)</li>
-
-        <li>integrated web server</li>
-
-        <li>Deflate and Predictor-1 CCP compression</li>
-      </ul>
-      </p>
-
-      <p>Some historically broken features have been reimplemented:
-      <ul>
-        <li>TCP and UDP link types</li>
-
-        <li>CCP compression</li>
-
-        <li>ECP encryption</li>
-      </ul>
-      </p>
-
-      <p>To support compression, two new Netgraph nodes ng_deflate and
-      ng_pred1 have been created and the ng_ppp node has been
-      modified.</p>
-    <h3>Open tasks:</h3><ol><li>ng_ppp node refactoring.</li><li>Implement packet loss notification in related Netgraph nodes
-      (ng_ppp, ng_pptp, ng_async, ng_deflate, ng_pred1, ng_vjc, ...) to
-      reduce recovery time and probability of incorrect packet
-      decompression.</li><li>MPD auth subsystem refactoring.</li></ol><hr /><h2><a name="Wireless-Networking" href="#Wireless-Networking" id="Wireless-Networking">Wireless Networking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@errno.com">sam@errno.com</a>&gt;
-	</p>
-      <p>Work on wireless support has continued to evolve in the public
-      CVS tree while other work has been going on behind the scenes in
-      the developer's perforce repository.</p>
-
-      <p>Support was recently added to HEAD for half- and quarter-rate
-      channels as found in the 4.9 GHz FCC Public Safety Band. This work
-      was a prerequisite to adding similar support in the 900 MHz band as
-      found in Ubiquiti's SR9 cards. Adding this functionality was
-      straightforward due to the design of the net80211 layer, requiring
-      only some additions to handle the unusual mapping between
-      frequencies and IEEE channel numbers. The ath(4) driver currently
-      supports hardware capable of operating on half- and quarter-rate
-      channels.</p>
-
-      <p>Kip Macy recently made significant advances preparing legacy
-      drivers for the re-architected net80211 layer that has been
-      languishing in perforce. With his efforts this code is nearly ready
-      for public testing after which it can be merged into CVS. Our goal
-      is to complete this merge in time for the 7.x branch (otherwise it
-      will be forced to wait for 8.0 before it appears in a public
-      release). This revised net80211 layer includes advanced station
-      mode facilities such as background scanning and roaming and support
-      for Atheros' SuperG extensions. Getting the revised scanning work
-      into CVS will greatly simplify public distribution of the Virtual
-      AP (VAP) code as a patch as well as enable addition of 802.11n
-      support.</p>
-
-      <p>Benjamin Close is working on support for the Intel 3945 parts
-      commonly found in laptops. The work is going on in the perforce
-      repository with public code drops for testing.</p>
-
-      <p>Atheros PCI/Cardbus support was updated with a new HAL that
-      fixes a few minor issues and corrects a problem that kept AR2424
-      parts from working. The new HAL also enables more efficient use of
-      the hardware keycache for TKIP keys; on newer hardware you can now
-      support up to 57 stations without faulting keys into the cache.
-      Support for the latest 802.11n parts found in the new Lenovo and
-      Apple laptops (among others) is in development; initial release
-      will support only legacy operation.</p>
-
-      <p>Support for Atheros USB devices is coming. Atheros has agreed to
-      license their firmware with the same license applied to the HAL
-      which means it can be committed to the tree and distributed as part
-      of releases. The driver is still in development.</p>
-
-      <p>wpa_supplicant and hostapd were updated to the latest stable
-      build releases from Jouni Malinen. Shortly the in-tree code base
-      will switch to the 0.5.x tree which will bring in much new
-      functionality including dynamic VLAN tagging that will be
-      especially useful once the multi-bss support is available.</p>
-
-      <p>The support for injection of raw 802.11 frames was committed to
-      HEAD. This work was done in collaboration with Andrea Bittau. At
-      this point there are no plans to commit this to the STABLE branch
-      as it requires API changes.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Cryptographic-Subsystem" href="#Cryptographic-Subsystem" id="Cryptographic-Subsystem">Cryptographic Subsystem</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>Michael Richardson has been spearheading work to improve the
-      crypto subsystem used by various parts of the kernel including Fast
-      IPSec and geli. This work is sponsored by Hifn and has been
-      happening outside the CVS repository. A main focus of this work is
-      to add support for higher-level hardware operations that can
-      significantly improve the performance of IPSec and SSL
-      protocols.</p>
-
-      <p>Results of this work are now being readied for CVS. These
-      redesign the core/driver APIs to use the kobj facilities and recast
-      software crypto drivers as pseudo devices. The changes greatly
-      improve the system and permit new functionality such as specifying
-      which crypto device to use when multiple are available. The
-      redesign will also enable load balancing of crypto work across
-      multiple devices and the addition of virtual crypto sessions by
-      which small operations can be done in software when the overhead to
-      set up a hardware device is too costly.</p>
-
-      <p>In addition to the changes to the core crypto system several
-      crypto drivers have been updated to improve their operation. Top of
-      this list is the hifn(4) driver where many longstanding bugs have
-      been fixed for 7955/756 parts.</p>
-    <hr /><h2><a name="GEOM-Multipath" href="#GEOM-Multipath" id="GEOM-Multipath">GEOM Multipath</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>A toy implementation of GEOM based active/passive multipath is
-      now done and in a perforce repository. Seems to work.</p>
-    <hr /><h2><a name="Interrupt-Filtering" href="#Interrupt-Filtering" id="Interrupt-Filtering">Interrupt Filtering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Interrupts" title="http://wiki.FreeBSD.org/Interrupts"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Interrupts" title="">http://wiki.FreeBSD.org/Interrupts</a></td></tr></table><p>
-	Contact:
-          Paolo
-
-          Pisati
-         &lt;<a href="mailto:piso@FreeBSD.org">piso@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Interrupt filtering is a new method to handle interrupts in
-      FreeBSD that retains backward compatibility with the previous
-      models (FAST and ITHREAD), while improving over them in some
-      aspects. With interrupt filtering, the interrupt handler is divided
-      into 2 parts: the filter (that checks if the actual interrupt
-      belongs to a device) and a private per-handler ithread (that is
-      scheduled in case some blocking work has to be done). The main
-      benefits of this work are:
-      <ul>
-        <li>Feedback from filters (the operating system finally knows
-        what's the state of an event and can react consequently).</li>
-
-        <li>Lower latency/overhead for shared interrupt line.</li>
-
-        <li>Previous experiments with interrupt filtering showed an
-        increase in performance against the plain ithread model in some
-        cases.</li>
-
-        <li>General shrink of the machine dependent code - part of the
-        interrupting handling code was turned into machine independent
-        code.</li>
-      </ul>
-      </p>
-
-      <p>During the last quarter many improvements were made up to the
-      point where 3 archs (i386, amd64 and arm) are reported to work, and
-      the project can be considered feature complete.</p>
-
-      <p>I definitely want to make it part of the 7.0 release.</p>
-    <h3>Open tasks:</h3><ol><li>Define a road map to commit the code into the tree.</li><li>Rethink the interrupt stray handling (?!?!).</li><li>Finish off support for powerpc, sparc64 and ia64 (sun4v
-      support is known to be broken now).</li></ol><hr /><h2><a name="Sound-Subsystem-Improvements" href="#Sound-Subsystem-Improvements" id="Sound-Subsystem-Improvements">Sound Subsystem Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~ariff/" title="http://people.FreeBSD.org/~ariff/">Some patches / binary modules.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~ariff/" title="Some patches / binary modules.">http://people.FreeBSD.org/~ariff/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/projects/ideas/" title="http://www.FreeBSD.org/projects/ideas/">The FreeBSD Project Ideas List.</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/ideas/" title="The FreeBSD Project Ideas List.">http://www.FreeBSD.org/projects/ideas/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/soundsystem" title="http://wiki.FreeBSD.org/soundsystem">Wiki page about the sound system.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/soundsystem" title="Wiki page about the sound system.">http://wiki.FreeBSD.org/soundsystem</a></td></tr></table><p>
-	Contact:
-          Ariff
-
-          Abdullah
-         &lt;<a href="mailto:ariff@FreeBSD.org">ariff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Multimedia
-
-          Mailinglist
-         &lt;<a href="mailto:multimedia@FreeBSD.org">multimedia@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report there were improvements to the
-      emu10kx driver for High Definition Audio (HDA) compatible chips.
-      Some more chips are supported now and already supported chips
-      should provide a better zero-configuration experience.</p>
-
-      <p>The generic sound code got some very nice low latency changes,
-      and fixes which make it multichannel/endian/format safe. We do not
-      support multichannel operation yet, but this work is a prerequisite
-      to work on implementing multichannel operation. This work also
-      fixed some bugs which people may experience as clicks, hickups,
-      truncation or similar behavior in the sound-output.</p>
-
-      <p>So far there is no merge to 5.x or 6.x planned for this code,
-      especially because there are API/ABI changes, e.g., several sysctls
-      changed. People who do not care about this can download binary
-      sound modules from Ariff's download page for 6.x and 5.x.</p>
-
-      <p>We thank all people who tested the changes / submitted patches
-      and thus helped improving the sound system.</p>
-    <h3>Open tasks:</h3><ol><li>Have a look at the sound related entries on the ideas
-      list.</li><li>Add multichannel support.</li><li>sndctl(1): tool to control non-mixer parts of the sound
-      system (e.g. spdif switching, virtual-3D effects) by a user
-      (instead of the sysctl approach in -CURRENT); pcmplay(1),
-      pcmrec(1), pcmutil(1).</li><li>Plugable FEEDER infrastructure. For ease of debugging various
-      feeder stuff and/or as userland library and test suite.</li><li>Extend the wiki page.</li></ol><hr /><h2><a name="Update-of-the-Linux-Compatibility-Environment-in-the-Kernel" href="#Update-of-the-Linux-Compatibility-Environment-in-the-Kernel" id="Update-of-the-Linux-Compatibility-Environment-in-the-Kernel">Update of the Linux Compatibility Environment in the
-    Kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/linux-kernel" title="http://wiki.FreeBSD.org/linux-kernel">Wiki page about the Linux compatibility environment.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/linux-kernel" title="Wiki page about the Linux compatibility environment.">http://wiki.FreeBSD.org/linux-kernel</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Roman
-
-          Divacky
-         &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Emulation
-
-          Mailinglist
-         &lt;<a href="mailto:emulation@FreeBSD.org">emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report we made good progress in improving
-      the compatibility environment. We fixed more than 30 testcases on
-      i386 (130 testcases = 16% still failing) and more than 60 testcases
-      on amd64 (140 testcases = 17% still failing) in the Linux 2.4
-      compatibility. These numbers compare FreeBSD 6.2 with -CURRENT.
-      Some of those fixes are edge cases in the error handling, and some
-      of them fix real issues -- e.g. hangs -- and improve the stability
-      and correctness of the emulation.</p>
-
-      <p>Regarding the Linux 2.6 compatibility there are 140 testcases
-      (17%) on i386 and 150 testcases (18%) on amd64 still failing in
-      -CURRENT. After fixing some showstopper problems with real
-      applications, we should be able to give the 2.6 emulation a more
-      widespread exposure "soon" to find more bugs and to determine the
-      importance of those Linux syscalls which we did not implement
-      yet.</p>
-
-      <p>The severity of the broken testcases varies, and some of them
-      will never be fixed, e.g., we will never be able to load Linux
-      kernel modules into a FreeBSD kernel, being able to add swap with a
-      Linux command has very low priority, and fixing stuff which is used
-      by applications like IPC type 17 has high priority.</p>
-
-      <p>Some differences in the 2.6 compatibility are because not all
-      i386 changes are merged into the amd64 code, and some testcases are
-      already fixed in our perforce repository but need more review
-      before they can be committed to -CURRENT.</p>
-
-      <p>We need some more testers and bug reporters. So if you have a
-      little bit of time and a favorite Linux application, please play
-      around with it on -CURRENT. If there is a problem, have a look at
-      the wiki if we already know about it and report on
-      <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-emulation" shape="rect">
-      emulation@</a>
-
-      . We are especially interested in reports about the 2.6
-      compatibility (sysctl compat.linux.osversion=2.6.16), but only with
-      the most recent -CURRENT and maybe with some patches we have in the
-      perforce repository (mandatory on amd64).</p>
-
-      <p>We thank all people who tested the changes / submitted patches
-      and thus helped improving the Linux compatibility environment.</p>
-    <hr /><br /><h1><a name="Hardware-Drivers" href="#Hardware-Drivers" id="Hardware-Drivers">Hardware Drivers</a></h1><br /><h2><a name="Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite-driver)" href="#Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite-driver)" id="Bt878-Audio-Driver-(aka-FusionHDTV-5-Lite-driver)">Bt878 Audio Driver (aka FusionHDTV 5 Lite driver)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21" title="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21">Perforce source repository</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21" title="Perforce source repository">http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21</a></td></tr></table><p>
-	Contact:
-          John-Mark
-
-          Gurney
-         &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>Basic audio capture is working. All of the parameters are set by
-      userland, while the RISC program generation is by kernel. No real
-      audio has been captured as there are no drivers for the NTSC tuner
-      yet. Someone with a real Bt878 NTSC card that is supported by
-      bktr(4) could use this to capture audio without using the sound
-      card.</p>
-
-      <p>Due to lack of documentation from DViCO and LG, I have copied
-      magic values from the Linux driver and managed to get ATSC
-      capturing working. There was a bug in the capture driver that was
-      releasing buffers to userland early causing what appeared to be
-      reception issues. Now that we use the RISC status bits as buffer
-      completion bits, capture works cleanly. This does mean that even if
-      you provide more than 4 buffers to the driver, the buffers will be
-      divided into four segments, and returned in segments.</p>
-
-      <p>A Python module is available, along with a sample capture
-      application using it. The module is now known to work well with
-      threads so that tuning (expensive due to i2c ioctls) can happen in
-      another thread without causing program slow down. The module is
-      working well with a custom PVR backend.</p>
-
-      <p>Additional ioctls have been added to get sibling devices. This
-      allows one to open a bktrau device, and get the correct bktr(4)
-      device that is in the same slot. This is necessary so that when
-      adjusting GPIO pins or sending i2c commands, they are to the
-      correct device.</p>
-    <h3>Open tasks:</h3><ol><li>Provide support for NTSC and FM tuning.</li><li>Add support for other cards and tuners that use the Bt878
-      chip.</li></ol><hr /><h2><a name="Intel-3945ABG-Wireless-LAN-Driver:-wpi" href="#Intel-3945ABG-Wireless-LAN-Driver:-wpi" id="Intel-3945ABG-Wireless-LAN-Driver:-wpi">Intel 3945ABG Wireless LAN Driver: wpi</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi"></a></td><td>
-	    URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi" title="">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi</a></td></tr><tr><td><a href="http://www.clearchain.com/wiki/wpi" title="http://www.clearchain.com/wiki/wpi"></a></td><td>
-	    URL: <a href="http://www.clearchain.com/wiki/wpi" title="">http://www.clearchain.com/wiki/wpi</a></td></tr></table><p>
-	Contact:
-          Benjamin
-
-          Close
-         &lt;<a href="mailto:benjsc@FreeBSD.org">benjsc@FreeBSD.org</a>&gt;
-	</p>
-      <p>An initial port of the NetBSD wpi driver has been done and
-      development is happening fast to get this driver ready for the
-      tree. At present basic functionality works. The driver can
-      associate with a non encrypted peer and pass data in 11b and 11g
-      modes. There is still lots to do and testing is welcome.</p>
-
-      <p>Many thanks have to go to Sam, Max and Kip for helping the
-      driver reach this point.</p>
-    <h3>Open tasks:</h3><ol><li>Solve bus dma alignment issues</li><li>Support WEP and WPA</li><li>Testing and more testing</li></ol><hr /><h2><a name="MPT-LSI-Logic-Host-Adapters:-mpt" href="#MPT-LSI-Logic-Host-Adapters:-mpt" id="MPT-LSI-Logic-Host-Adapters:-mpt">MPT LSI-Logic Host Adapters: mpt</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>The 'mpt' project is support for the MPT LSI-Logic Host Adapters
-      (SCSI, Fibre Channel, SAS).</p>
-
-      <p>The last quarter saw a lot of change supported by Yahoo! and
-      LSI-Logic and many others as things settled out for better support
-      for U320. Some initial Big Endian support was offered by John
-      Birrel and Scott Long.</p>
-    <h3>Open tasks:</h3><ol><li>Finish SAS Integrated RAID support.</li><li>Try and get U320 RAID working better than it currently
-      does.</li><li>Finish Big Endian support, including that for target
-      mode.</li></ol><hr /><h2><a name="QLogic-SCSI-and-Fibre-Channel:-isp" href="#QLogic-SCSI-and-Fibre-Channel:-isp" id="QLogic-SCSI-and-Fibre-Channel:-isp">QLogic SCSI and Fibre Channel: isp</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Matthew
-
-          Jacob
-         &lt;<a href="mailto:mjacob@FreeBSD.org">mjacob@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is for support for QLogic SCSI and Fibre Channel
-      host adapters.</p>
-
-      <p>The last quarter saw the addition of 4Gb Fibre Channel support
-      and a complete rewrite of fabric management (which is still
-      settling out).</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Hungarian-Translation-of-the-Webpages" href="#Hungarian-Translation-of-the-Webpages" id="Hungarian-Translation-of-the-Webpages">Hungarian Translation of the Webpages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu/" title="http://www.FreeBSD.org/hu/">Hungarian webpages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu/" title="Hungarian webpages">http://www.FreeBSD.org/hu/</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Giorgos
-
-          Keramidas
-         &lt;<a href="mailto:keramida@FreeBSD.org">keramida@FreeBSD.org</a>&gt;
-	</p>
-      <p>G�bor K�vesd�n (gabor@) has submitted the Hungarian translation
-      of the webpages and Giorgos Keramidas (keramida@) has reviewed and
-      committed the pages. The initial rendering issues have also been
-      fixed and the webpage is in a pretty good shape now.</p>
-
-      <p>As usual, this translation does not contain every part of the
-      English version, but the most important and useful parts are there.
-      G�bor will maintain this translation and regularly sync the content
-      with the English version and add new translations if such become
-      available.</p>
-    <h3>Open tasks:</h3><ol><li>Fix typos and mistakes that will be revealed after a deeper
-      review by the public</li><li>Get more people involved</li></ol><hr /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/nl/books/handbook" title="http://www.FreeBSD.org/doc/nl/books/handbook"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/nl/books/handbook" title="">http://www.FreeBSD.org/doc/nl/books/handbook</a></td></tr><tr><td><a href="http://www.evilcoder.org/content/section/6/39/" title="http://www.evilcoder.org/content/section/6/39/"></a></td><td>
-	    URL: <a href="http://www.evilcoder.org/content/section/6/39/" title="">http://www.evilcoder.org/content/section/6/39/</a></td></tr><tr><td><a href="http://www.FreeBSD-nl.org/doc/nl/" title="http://www.FreeBSD-nl.org/doc/nl/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD-nl.org/doc/nl/" title="">http://www.FreeBSD-nl.org/doc/nl/</a></td></tr><tr><td><a href="http://www.FreeBSD-nl.org/www/" title="http://www.FreeBSD-nl.org/www/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD-nl.org/www/" title="">http://www.FreeBSD-nl.org/www/</a></td></tr></table><p>
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation Project is an ongoing project to
-      translate the FreeBSD Handbook to the Dutch Language.</p>
-
-      <p>Currently we almost translated the entire handbook, and we
-      translated parts of the website, sadly the project went into a
-      slush lately, so we seek out for fresh and new translators that are
-      willing to join the team to continue the effort.</p>
-    <h3>Open tasks:</h3><ol><li>Translate the rest of the handbook</li><li>Make the documentation up to date</li><li>Translate the rest of the website</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="BSNMP---More-Ongoing-and-Upcoming-Work" href="#BSNMP---More-Ongoing-and-Upcoming-Work" id="BSNMP---More-Ongoing-and-Upcoming-Work">BSNMP - More Ongoing and Upcoming Work</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BsnmpTODO" title="http://wiki.FreeBSD.org/BsnmpTODO">BSNMP TODO Wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BsnmpTODO" title="BSNMP TODO Wiki page">http://wiki.FreeBSD.org/BsnmpTODO</a></td></tr></table><p>
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:syrinx@FreeBSD.org">syrinx@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Harti
-
-          Brandt
-         &lt;<a href="mailto:harti@FreeBSD.org">harti@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>In addition to other more detailed reports this is intended to
-      give a summary about other ongoing or upcoming BSNMP related work.
-      To collect some ideas from users and coordinate work a BSNMP TODO
-      Wiki page was created. Feel free to add your ideas or let us know
-      about them.</p>
-
-      <p>
-        <ul>
-          <li>A contributor, Tsvetan Erenditsov, has volunteered to
-          implement a VLAN module for BSNMP. Shteryana is helping
-          him.</li>
-
-          <li>Sam Leffler has asked for a wireless networking monitoring
-          module, which will most likely be the next module to be
-          implemented.</li>
-
-          <li>Some major work is currently going on in the main BSNMP
-          tree:
-          <ul>
-            <li>SNMP transports have been factored out into loadable
-            modules. The old port tables are still there and will remain
-            at least for the next release. Later they will be removed.
-            The following modules and transports are already implemented
-            as loadable modules:
-            <ul>
-              <li>snmp_trans_udp: SNMP over UDP over IPv4, IPv6 and
-              scoped IPv6</li>
-
-              <li>snmp_trans_tcp: SNMP over TCP over IPv4, IPv6 and
-              scoped IPv6</li>
-
-              <li>snmp_trans_ldgram: SNMP over local datagram
-              sockets</li>
-
-              <li>snmp_trans_lstream: SNMP over local stream sockets</li>
-            </ul>
-            </li>
-
-            <li>Some I/O functions have been moved from the daemon to
-            libbsnmp.</li>
-
-            <li>libisa has been imported into the bsnmp tree. This
-            library aims at easy implementation of command line tools for
-            remote and local system administration with a special focus
-            on administration via SNMP. The library contains command line
-            parsing functions, a function for automatically handling help
-            text. Actual administration modules are implemented as
-            loadable modules. The atmconfig tool in the FreeBSD tree
-            contains some old parts of this library.</li>
-
-            <li>lisa_snmp is a module which implements SNMP functionality
-            for libisa.</li>
-
-            <li>lisa_snmpd is a module for remote administration of the
-            bsnmpd.</li>
-
-            <li>The config file parser of bsnmpd has been rewritten so
-            that each section of the file is handled as a transaction (in
-            contrast to the previous behavior where the entire file was
-            one transaction).</li>
-          </ul>
-          </li>
-        </ul>
-      </p>
-    <hr /><h2><a name="BSNMP-Bridge-Module" href="#BSNMP-Bridge-Module" id="BSNMP-Bridge-Module">BSNMP Bridge Module</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SnmpBridgeModule" title="http://wiki.FreeBSD.org/SnmpBridgeModule"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SnmpBridgeModule" title="">http://wiki.FreeBSD.org/SnmpBridgeModule</a></td></tr></table><p>
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:syrinx@FreeBSD.org">syrinx@FreeBSD.org</a>&gt;
-	</p>
-      <p>The BSNMP bridge module for FreeBSD's BSNMP daemon, which was
-      implemented during SoC 2006, was committed to HEAD. In addition to
-      RFC 4188 single bridge support it also supports monitoring multiple
-      bridges via a private MIB. Since SoC 2006 Rapid Spanning Tree
-      (RSTP) support (RSTP-MIB defined in RFC4318 and additions to the
-      private MIB) was added to the module as well.</p>
-
-      <p>A patch for RELENG_6 is available and will be merged to STABLE
-      the next weeks.</p>
-    <h3>Open tasks:</h3><ol><li>MFC to RELENG_6.</li><li>More feedback from users is always welcome.</li></ol><hr /><h2><a name="BSNMP-Client-Tools" href="#BSNMP-Client-Tools" id="BSNMP-Client-Tools">BSNMP Client Tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BsnmpTools" title="http://wiki.FreeBSD.org/BsnmpTools">Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BsnmpTools" title="Wiki Page">http://wiki.FreeBSD.org/BsnmpTools</a></td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/ bsnmp/contrib/bsnmp/snmptools" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/ bsnmp/contrib/bsnmp/snmptools">Shteryana's P4 tree</a></td><td>
-	    URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/ bsnmp/contrib/bsnmp/snmptools" title="Shteryana's P4 tree">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/ bsnmp/contrib/bsnmp/snmptools</a></td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ bsnmp%5fsyrinx/usr.sbin/bsnmpd/tools" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ bsnmp%5fsyrinx/usr.sbin/bsnmpd/tools">Bjoern's P4 tree (rewrite)</a></td><td>
-	    URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ bsnmp%5fsyrinx/usr.sbin/bsnmpd/tools" title="Bjoern's P4 tree (rewrite)">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/bz/ bsnmp%5fsyrinx/usr.sbin/bsnmpd/tools</a></td></tr></table><p>
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:syrinx@FreeBSD.org">syrinx@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>During SoC 2005 BSNMP client tools (bsnmptools) were implemented
-      and have since then been available via Shteryana's P4 tree or port
-      net-mgmt/bsnmptools.</p>
-
-      <p>In order to finally get the code committed some cleanup was
-      needed which ended in a partly rewrite to minimize duplicate code
-      and to reduce the size of the binaries. This ongoing work is
-      available via Bjoern's P4 tree and will be merged back to upstream
-      trees before it will be committed to HEAD.</p>
-    <h3>Open tasks:</h3><ol><li>Update Wiki Page to reflect latest work.</li><li>Finish cleanup and have it reviewed.</li><li>User feedback is always welcome.</li></ol><hr /><h2><a name="Libelf" href="#Libelf" id="Libelf">Libelf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/LibElf" title="http://wiki.FreeBSD.org/LibElf">Wiki page tracking LibELF</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/LibElf" title="Wiki page tracking LibELF">http://wiki.FreeBSD.org/LibElf</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/PmcTools" title="http://wiki.FreeBSD.org/PmcTools">Wiki page for PmcTools</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PmcTools" title="Wiki page for PmcTools">http://wiki.FreeBSD.org/PmcTools</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~jkoshy/projects/perf-measurement/" title="http://people.FreeBSD.org/~jkoshy/projects/perf-measurement/">PMC Tools Project</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~jkoshy/projects/perf-measurement/" title="PMC Tools Project">http://people.FreeBSD.org/~jkoshy/projects/perf-measurement/</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Libelf is a BSD-licensed library for ELF parsing &amp;
-      manipulation implementing the SysV/SVR4 (g)ELF[3] API.</p>
-
-      <p>Current status: The library is now in -CURRENT. Work continues
-      on its test suite and tutorial, and on deploying it in
-      PmcTools.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="ARM/XScale-Port" href="#ARM/XScale-Port" id="ARM/XScale-Port">ARM/XScale Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Olivier
-
-          Houchard
-         &lt;<a href="mailto:cognet@FreeBSD.org">cognet@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD is running multi-user on a variety of Gateworks Avila
-      boards with most of the on-board devices supported. These include
-      the compact flash/IDE slot, wired network interfaces, realtime
-      clock, and environmental sensors. Several different minipci cards
-      have been tested including those supported by the ath(4) and
-      hifn(4) drivers. Remaining devices that need support are the
-      onboard flash, optional 4-port network switch, and optional USB
-      interface. Crypto acceleration for IXP425 parts is planned but will
-      likely be done at a later time.</p>
-
-      <p>The Network Processor Engine (NPE) support is done with an
-      entirely new replacement for the Intel Access Layer (IAL). The most
-      important hardware facilities are supported (e.g. the hardware Q
-      manager) and the wired NIC driver was also done from scratch. The
-      resulting code is approximately 1/10th the number of lines of the
-      equivalent IAL code.</p>
-    <h3>Open tasks:</h3><ol><li>Bootstrap support needs work to enable booting from the
-      compact flash device.</li></ol><hr /><h2><a name="FreeBSD/powerpc-on-Freescale-MPC8555" href="#FreeBSD/powerpc-on-Freescale-MPC8555" id="FreeBSD/powerpc-on-Freescale-MPC8555">FreeBSD/powerpc on Freescale MPC8555</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Rafal
-
-          Jaworowski
-         &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	<br />
-	Contact:
-          Marcel
-
-          Moolenaar
-         &lt;<a href="mailto:xcllnt@mac.com">xcllnt@mac.com</a>&gt;
-	</p>
-      <p>Platform summary:
-      <ul>
-        <li>PowerQuiccIII integrated controller</li>
-
-        <li>e500 CPU core</li>
-
-        <li>compliant with PowerPC BookE specification (significantly
-        different from the 'traditional' PowerPC architecture the current
-        FreeBSD/powerpc supports, particularly in the areas of MMU
-        design, exceptions model, specific e500 machine instructions
-        etc.)</li>
-      </ul>
-      </p>
-
-      <p>Currently the machine is booting FreeBSD 6.1-RELEASE-p10 and
-      operating both single- and multi-user modes; below are highlights
-      of available functionality:
-      <ol>
-        <li>Low-level support</li>
-
-        <ul>
-          <li>booting from U-Boot bootloader</li>
-
-          <li>locore machine initialization</li>
-
-          <li>e500 exceptions</li>
-
-          <li>VM: a new pmap module developed</li>
-        </ul>
-
-        <li>On-chip peripherals</li>
-
-        <ul>
-          <li>introduced ocpbus hierarchy (nexus and descendants)</li>
-
-          <li>interrupt controller: using generic OpenPIC driver</li>
-
-          <li>serial console: using uart(4) driver</li>
-
-          <li>barebones serial support using the QUICC's SCC</li>
-
-          <li>host/PCI bridge: a new driver developed for the built-in
-          bridge</li>
-
-          <li>networking: a new driver developed for TSEC (3-speed
-          Ethernet)</li>
-        </ul>
-
-        <li>Booting</li>
-
-        <ul>
-          <li>from ATA disk and USB memory stick (both through a
-          secondary PCI VIA82C686B controller)</li>
-
-          <li>from network (NFS-mounted rootfs)</li>
-        </ul>
-
-        <li>Basic TCP/IP protocols and apps work (DHCP, NFS, SSH, FTP,
-        Telnet etc.)</li>
-
-        <li>Userland</li>
-
-        <ul>
-          <li>integrated SoftFloat emulation lib (required due to e500
-          not being equipped with the old-style PowerPC FPU)</li>
-
-          <li>almost all applications seem to work</li>
-        </ul>
-      </ol>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Work out extensible layout for sys/powerpc architecture
-      directory so we can easily add support for new core variations and
-      platforms to come in the future.</li><li>Integrate with FreeBSD source tree.</li><li>Release and tinderbox related options and settings.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-GNOME-Project" href="#FreeBSD-GNOME-Project" id="FreeBSD-GNOME-Project">FreeBSD GNOME Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-          FreeBSD
-
-          GNOME Project
-         &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>Where have we been?! Not doing status reports, that's for sure.
-      But the FreeBSD GNOME project has been very busy with regular GNOME
-      releases, and other side projects. We are currently shipping GNOME
-      2.16.2 in the ports tree, and we are testing GNOME 2.17.5 in the
-      <a href="http://www.FreeBSD.org/gnome/docs/develfaq.html" shape="rect">
-      MarcusCom</a>
-
-      tree.</p>
-
-      <p>Most recently, work has completed on a cleanup of the FreeBSD
-      backend to libgtop. This module has needed a lot of work, and
-      should now be reporting correct system statistics. The cleaned up
-      version is currently being tested in the MarcusCom tree, and will
-      make it into the FreeBSD ports tree along with GNOME 2.18.</p>
-
-      <p>The GStreamer framework has been taken out of direct
-      <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-gnome" shape="rect">
-      gnome@</a>
-
-      maintainership, and put under a new
-      <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia" shape="rect">
-      multimedia@</a>
-
-      umbrella. This will give multimedia-savvy developers a chance to
-      collaborate on this important piece of the GNOME Desktop along with
-      other important audio and video components.</p>
-
-      <p>The biggest accomplishment of 2006 for the FreeBSD GNOME team
-      had to have been the port of
-      <a href="http://www.freedesktop.org/wiki/Software_2fhal" shape="rect">HAL</a>
-
-      . This effort was started to give FreeBSD users a richer desktop
-      experience. Since the initial FreeBSD release of HAL with GNOME
-      2.16, it has been incorporated into the FreeBSD release of KDE
-      3.5.5 as well as PC-BSD 1.3. The FreeBSD backend has also made it
-      upstream into the HAL git repository so future releases of HAL will
-      have FreeBSD support out-of-the-box.</p>
-
-      <p>Finally, it is with sadness that we say good-bye to one of our
-      team members. Adam Weinberger stepped down from the FreeBSD GNOME
-      team to save lives instead (priorities, man!). His splash screens
-      and grammar nit-picking will be missed.</p>
-    <h3>Open tasks:</h3><ol><li>Now that HAL has been ported to FreeBSD, there is a strong
-      desire to see
-      <a href="http://www.gnome.org/projects/NetworkManager/" shape="rect">
-      NetworkManager</a>
-
-      ported. The big parts will be porting NM to use our 80211
-      framework, and extending some of the base utilities such as
-      ifconfig. Contact
-      <a href="mailto:marcus@FreeBSD.org" shape="rect">marcus@FreeBSD.org</a>
-
-      if you are interested in helping.</li><li>Our system-tools-backends module needs some attention. This
-      module is responsible for system configuration tasks in GNOME such
-      as user management, network shares administration, etc. A knowledge
-      of Perl is highly recommended. Contact
-      <a href="mailto:marcus@FreeBSD.org" shape="rect">marcus@FreeBSD.org</a>
-
-      if you are interested in helping.</li><li>We need good documentation writers to help update our
-      <a href="http://www.FreeBSD.org/gnome/docs/faq2.html" shape="rect">FAQ</a>
-
-      and other documentation. If you would like to take on the
-      responsibility full-time, or just contribute some pieces, please
-      notify
-      <a href="mailto:gnome@FreeBSD.org" shape="rect">gnome@FreeBSD.org</a>
-
-      .</li><li>We are always in need of GNOME development testers. See our
-      <a href="http://www.FreeBSD.org/gnome/docs/develfaq.html" shape="rect">
-      development branch FAQ</a>
-
-      for ways on how you can help make the next release of GNOME the
-      best release.</li></ol><hr /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freshports.org/" title="http://www.freshports.org/">FreshPorts</a></td><td>
-	    URL: <a href="http://www.freshports.org/" title="FreshPorts">http://www.freshports.org/</a></td></tr><tr><td><a href="http://news.freshports.org/" title="http://news.freshports.org/">FreshPorts News</a></td><td>
-	    URL: <a href="http://news.freshports.org/" title="FreshPorts News">http://news.freshports.org/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>There have been a number of improvements to FreshPorts over the
-      last quarter of 2006. The following are just a few of them. The
-      links take you to the relevant article within the
-      <a href="http://news.freshports.org" shape="rect">FreshPorts News website</a>
-
-      .
-      <ul>
-        <li>Better
-        <a href="http://news.freshports.org/index.php?s=pagination" shape="rect">
-        pagination</a>
-
-        of larger result sets</li>
-
-        <li>Listing of
-        <a href="http://news.freshports.org/2006/10/11/sanity-test-failures/" shape="rect">
-        sanity test failures</a>
-        </li>
-
-        <li>Inclusion of
-        <a href="http://news.freshports.org/2006/10/01/the-latest-and-greatest-vulnerabilities/" shape="rect">
-        latest vulnerabilities</a>
-
-        on the front page</li>
-
-        <li>Started working on adding tools to make
-        FreshSource/FreshPorts more useful as a
-        <a href="http://news.freshports.org/2006/11/29/freshsourcefreshports-as-a-developer-platform/" shape="rect">
-        developer tool</a>
-        </li>
-
-        <li>The new
-        <a href="http://www.freebsddiary.org/topics.php?aid=589#opteron" shape="rect">
-        dual opteron server</a>
-
-        has been
-        <a href="http://news.freshports.org/2006/11/09/opti-has-left-the-building/" shape="rect">
-        deployed!</a>
-        </li>
-      </ul>
-      </p>
-
-      <p>My thanks to the many people who have contributed suggestions,
-      ideas, and code over the years. Most of you are documented at the
-      above URLs.</p>
-    <h3>Open tasks:</h3><ol><li>FreshPorts/FreshSource as a developer tool</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="The FreeBSD Ports Collection">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~fenner/portsurvey/" title="http://people.FreeBSD.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.FreeBSD.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports count has jumped to 16347. The PR count, despite a
-      jump, has gone back down to around 700.</p>
-
-      <p>Not much work has been committed on the ports infrastructure due
-      to the long 6.2 release cycle. However, many test runs have been
-      done for several upcoming features, such as making sure that ports
-      will work with the new release of gcc (4.1), and do not have
-      /usr/X11R6 hard-coded into them. The intention of the latter is to
-      move all ports to $LOCALBASE, which can then be selected by the
-      user. This should help consistency going forwards, albeit at the
-      cost of a one-time conversion.</p>
-
-      <p>GNOME was updated to 2.16 during the release cycle.</p>
-
-      <p>In addition, we are in the process of moving the FORTRAN default
-      from f77 to gfortran. See the ports mailing list for details.</p>
-
-      <p>The new xorg ports are still being worked on as well; they are
-      intended to all live in $LOCALBASE. Hopefully this can get done in
-      the early 6.3 development cycle. See the wiki for more
-      information.</p>
-
-      <p>A new version of the ports Tinderbox code is available, which is
-      mostly a bugfix release.</p>
-
-      <p>We have also added Pav Lucistnik as a new portmgr member, who we
-      hope will help us work on the portmgr PR backlog. Welcome!</p>
-
-      <p>We have also added 8 new committers since the last report.</p>
-
-      <p>linimon continues to work on resetting committers who are no
-      longer interested in their ports; as well, several ports commit
-      bits have been stored for safekeeping. This is part of an attempt
-      to keep the best match between volunteers and work to be done.</p>
-    <h3>Open tasks:</h3><ol><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have many
-      unmaintained ports. As well, the packages on amd64 and sparc64 are
-      lagging behind.</li></ol><hr /><h2><a name="Updating-X.org-FreeBSD-Ports-to-7.2" href="#Updating-X.org-FreeBSD-Ports-to-7.2" id="Updating-X.org-FreeBSD-Ports-to-7.2">Updating X.org FreeBSD Ports to 7.2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://xorg.freedesktop.org/" title="http://xorg.freedesktop.org/">X.org Official Website</a></td><td>
-	    URL: <a href="http://xorg.freedesktop.org/" title="X.org Official Website">http://xorg.freedesktop.org/</a></td></tr><tr><td><a href="http://git.xbsd.org/?p=freebsd/ports.git;a=shortlog;h=xorg" title="http://git.xbsd.org/?p=freebsd/ports.git;a=shortlog;h=xorg">Experimental X.org Ports Tree</a></td><td>
-	    URL: <a href="http://git.xbsd.org/?p=freebsd/ports.git;a=shortlog;h=xorg" title="Experimental X.org Ports Tree">http://git.xbsd.org/?p=freebsd/ports.git;a=shortlog;h=xorg</a></td></tr><tr><td><a href="http://blog.xbsd.org/" title="http://blog.xbsd.org/">Latest news about FreeBSD X.org Porting Efforts</a></td><td>
-	    URL: <a href="http://blog.xbsd.org/" title="Latest news about FreeBSD X.org Porting Efforts">http://blog.xbsd.org/</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-x11/" title="http://lists.freebsd.org/pipermail/freebsd-x11/">FreeBSD-X11 Mailing List Archives</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-x11/" title="FreeBSD-X11 Mailing List Archives">http://lists.freebsd.org/pipermail/freebsd-x11/</a></td></tr></table><p>
-	Contact:
-          Florent
-
-          Thoumie
-         &lt;<a href="mailto:flz@FreeBSD.org">flz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Eric
-
-          Anholt
-         &lt;<a href="mailto:anholt@FreeBSD.org">anholt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Dejan
-
-          Lesjak
-         &lt;<a href="mailto:lesi@FreeBSD.org">lesi@FreeBSD.org</a>&gt;
-	</p>
-      <p>X.org 7.2 release has been delayed more than a month, which gave
-      us more time to fix build failures, to work on a few runtime issues
-      and to determine the easiest way to upgrade from 6.9 to 7.2 (mostly
-      with the help of people on the
-      <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-x11" shape="rect">
-      freebsd-x11@ mailing list</a>
-
-      ). Everything is in a rather good shape but there's still a little
-      amount of work to do. The merge of new ports is most likely to
-      happen before the end of January.</p>
-    <h3>Open tasks:</h3><ol><li>Do a global review of the diff between the original tree and
-      the experimental one (git-diff origin xorg for git users)</li><li>Fix the remaining (9 I think, 3 being lang/jdk's) build
-      errors</li><li>Continue testing</li><li>Do another experimental build on pointyhat</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan-2007" href="#BSDCan-2007" id="BSDCan-2007">BSDCan 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/2007/" title="http://www.bsdcan.org/2007/">BSDCan 2007</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2007/" title="BSDCan 2007">http://www.bsdcan.org/2007/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>Folks!
-      <br clear="none" />
-
-      It is that time of year. You may have missed the
-      <a href="http://www.bsdcan.org/2007/papers.php" shape="rect">call for papers</a>
-
-      , but please put in your proposal right away. This is often a busy
-      time of year, but please take the time to consider presenting at
-      BSDCan.</p>
-
-      <p>Please read the
-      <a href="http://www.bsdcan.org/2007/submissions.php" shape="rect">submission
-      instructions</a>
-
-      and send in your proposal today!</p>
-
-      <p>You may be interested in our sister conference: PGCon. If you
-      have an interest in
-      <a href="http://www.postgresql.org" shape="rect">PostgreSQL</a>
-
-      , a leading relational database, which just happens to be open
-      source, then we have the conference for you!
-      <a href="http://www.pgcon.org/2007/" shape="rect">PGCon 2007</a>
-
-      will be held immediately after BSDCan 2007, at the same venue, and
-      will follow a similar format.</p>
-    <h3>Open tasks:</h3><ol><li>Waiting for papers</li></ol><hr /><h2><a name="EuroBSDCon-2007" href="#EuroBSDCon-2007" id="EuroBSDCon-2007">EuroBSDCon 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2007.EuroBSDCon.org/" title="http://2007.EuroBSDCon.org/"></a></td><td>
-	    URL: <a href="http://2007.EuroBSDCon.org/" title="">http://2007.EuroBSDCon.org/</a></td></tr><tr><td><a href="http://www.EuroBSDCon.dk/" title="http://www.EuroBSDCon.dk/"></a></td><td>
-	    URL: <a href="http://www.EuroBSDCon.dk/" title="">http://www.EuroBSDCon.dk/</a></td></tr></table><p>
-	Contact:
-          Sidsel
-
-          Jensen
-         &lt;<a href="mailto:info@EuroBSDCon.dk">info@EuroBSDCon.dk</a>&gt;
-	</p>
-      <p>The sixth EuroBSDCon will take place in Copenhagen, Denmark on
-      <strong>Friday the 14th and Saturday 15th of September
-      2007</strong>
-
-      . The conference will be held at
-      <a href="http://www.symbion.dk/" shape="rect">Symbion Science Park</a>
-
-      . Sunday the 16th there will be an optional tour to LEGOland.</p>
-
-      <p>The
-      <a href="http://2007.eurobsdcon.org/cfp.html" shape="rect">call for papers</a>
-
-      was sent out right after EuroBSDCon 2006 in Milan in November and
-      abstracts are due February 1st! So hurry up and send in all your
-      fantastic and amazing papers to papers at eurobsdcon dot dk.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2007-01-2007-03.html b/website/content/en/status/report-2007-01-2007-03.html
deleted file mode 100644
index 146eaa4ef6..0000000000
--- a/website/content/en/status/report-2007-01-2007-03.html
+++ /dev/null
@@ -1,929 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between January and
-    March 2007. This quarter ended with a big bang as a port of Sun's
-    critically acclaimed ZFS was added to the tree and thus will be
-    available in the upcoming FreeBSD 7.0 release. Earlier this year
-    exciting benchmark results showed the fruits of our SMP work. Read
-    more on the details in the "SMP Scalability" report.</p><p>During the summer, FreeBSD will once again take part in Google's
-    Summer of Code initiative. Student selection is underway and we are
-    looking forward to a couple of exciting projects to come.</p><p>
-    <a href="http://www.bsdcan.org/" shape="rect">BSDCan</a>
-
-    is approaching rapidly, and will be held May 16-19th in Ottawa.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-and-ZFS">FreeBSD and ZFS</a></li><li><a href="#SMP-Scalability">SMP Scalability</a></li><li><a href="#USB">USB</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#Problem-Report-Database">Problem Report Database</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Building-Linux-Device-Drivers-on-FreeBSD">Building Linux Device Drivers on FreeBSD</a></li><li><a href="#Update-of-the-Linux-compatibility-environment-in-the-kernel">Update of the Linux compatibility environment in the
-    kernel</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></li><li><a href="#Importing-trunk(4)-from-OpenBSD">Importing trunk(4) from OpenBSD</a></li><li><a href="#Intel-3945ABG-Wireless-LAN-Driver:-wpi">Intel 3945ABG Wireless LAN Driver: wpi</a></li><li><a href="#Multi-link-PPP-daemon-(MPD)">Multi-link PPP daemon (MPD)</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#GCC-4.1-integration">GCC 4.1 integration</a></li><li><a href="#malloc(3)">malloc(3)</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#X.Org-7.2-integration">X.Org 7.2 integration</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan-2007">BSDCan 2007</a></li><li><a href="#EuroBSDCon-2007">EuroBSDCon 2007</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="FreeBSD-and-ZFS" href="#FreeBSD-and-ZFS" id="FreeBSD-and-ZFS">FreeBSD and ZFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs">Source code.</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="Source code.">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs</a></td></tr><tr><td><a href="http://www.opensolaris.org/os/community/zfs/" title="http://www.opensolaris.org/os/community/zfs/">OpenSolaris ZFS site.</a></td><td>
-	    URL: <a href="http://www.opensolaris.org/os/community/zfs/" title="OpenSolaris ZFS site.">http://www.opensolaris.org/os/community/zfs/</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070544.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070544.html">ZFS commit announce.</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070544.html" title="ZFS commit announce.">http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070544.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070616.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070616.html">ZFS - Quick Start.</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070616.html" title="ZFS - Quick Start.">http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070616.html</a></td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ZFS file system in now part of the FreeBSD operating system.
-      ZFS was ported from the OpenSolaris operating system and is under
-      CDDL license. As an experimental feature ZFS will be available in
-      FreeBSD 7.0-RELEASE.</p>
-    <hr /><h2><a name="SMP-Scalability" href="#SMP-Scalability" id="SMP-Scalability">SMP Scalability</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~kris/scaling/mysql.html" title="http://people.freebsd.org/~kris/scaling/mysql.html">MySQL scaling</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~kris/scaling/mysql.html" title="MySQL scaling">http://people.freebsd.org/~kris/scaling/mysql.html</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SMPTODO" title="http://wiki.freebsd.org/SMPTODO">Remaining Giant-locked code</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SMPTODO" title="Remaining Giant-locked code">http://wiki.freebsd.org/SMPTODO</a></td></tr></table><p>
-	Contact:
-          Kris
-
-          Kennaway
-         &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Jeff
-
-          Roberson
-         &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Attilio
-
-          Rao
-         &lt;<a href="mailto:attilio@FreeBSD.org">attilio@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Over the past few months there has been a substantially
-      increased focus on improving scalability of FreeBSD on large SMP
-      hardware. This has been driven in part by the new availability of
-      8-core hardware to the project, which allows easy profiling of
-      scalability bottlenecks and benchmarking of proposed changes.
-      Significant progress has been made on certain application workloads
-      such as MySQL and PostgreSQL, with the result that FreeBSD 7 now
-      has excellent scaling to at least 8-CPU systems with prospects for
-      further improvements. Progress with other application workloads has
-      been limited by the need to set up a suitable test case; please
-      contact me if you are interested in helping. As part of this
-      general effort, work is progressing steadily on removing the last
-      remaining Giant-locked code from the kernel. A complete list of
-      remaining Giant-locked code is found here:
-      <a href="http://wiki.freebsd.org/SMPTODO" shape="rect">
-      http://wiki.freebsd.org/SMPTODO</a>
-
-      Many of these sub-tasks have owners, but some do not. The major
-      remaining Giant-locked subsystem with no owner is the TTY
-      subsystem. In parallel, profiling of contention and bottlenecks in
-      other subsystems has lead to a number of experimental changes which
-      are being developed. Work is in progress by Jeff Roberson and
-      Attilio Rao to break up the global scheduler spinlock in favor of a
-      set of per-CPU scheduling locks, which is expected to improve
-      performance on systems with many CPUs. Experimental changes by
-      Robert Watson to allow for multiple netisr threads show good
-      promise for improving loopback IP performance on large SMP systems,
-      which can otherwise easily saturate a single netisr thread. A
-      variety of other changes are being profiled and evaluated to
-      improve SMP performance under various workloads. The majority of
-      these changes are collected in the //depot/user/kris/contention/
-      Perforce branch.</p>
-    <hr /><h2><a name="USB" href="#USB" id="USB">USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO">Current USB files</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="Current USB files">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://www.turbocat.net/~hselasky/usb4bsd" title="http://www.turbocat.net/~hselasky/usb4bsd">My USB Homepage</a></td><td>
-	    URL: <a href="http://www.turbocat.net/~hselasky/usb4bsd" title="My USB Homepage">http://www.turbocat.net/~hselasky/usb4bsd</a></td></tr><tr><td><a href="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf" title="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf">Code reference for the new USB stack and USB device drivers</a></td><td>
-	    URL: <a href="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf" title="Code reference for the new USB stack and USB device drivers">http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>&gt;
-	</p>
-      <p>During the last three months not too much has changed. Here is a
-      quick list of changes:</p>
-
-      <ol>
-        <li>There has been some cleanups in the UCOM layer, generally to
-        to create a context for all the callbacks so that they can call
-        sleeping functions. This is achieved using the USB config thread
-        system. The reason for this is that the code becomes simpler when
-        synchronous operation is applied versus asynchronous. But
-        asynchronous behavior is the most secure, hence then all USB
-        resources are preallocated for each transfer. After the change,
-        only data transfers are done asynchronously. All configuration is
-        now done synchronously. This makes the USB device drivers look
-        more like in the old USB stack.</li>
-
-        <li>moscom.c has been imported from OpenBSD. It is called
-        umoscom.c under FreeBSD.</li>
-
-        <li>ugensa.c has been imported from NetBSD.</li>
-
-        <li>f_axe.c has now has support for Ax88178 and Ax88772, which is
-        derived from OpenBSD.</li>
-      </ol>
-
-      <p>In my last status report I asked for access to Sparc64 boxes
-      with FreeBSD installed. Testing is ongoing and some problems remain
-      with EHCI PCI Cards. I am not exactly sure where the problem is,
-      but it appears that DMA-able memory does not get synced
-      properly.</p>
-
-      <p>Markus Brueffer is still working on the USB HID parser and
-      support. Nothing has been committed yet.</p>
-
-      <p>Several people have reported success with my new USB stack. Some
-      claim 2x improvements, others have seen more. But don't expect too
-      much.</p>
-
-      <p>If you want to test the new USB stack, checkout the USB perforce
-      tree or download the SVN version of the USB driver from my USB
-      homepage. At the moment the tarballs are a little out of date.</p>
-
-      <p>Ideas and comments with regard to the new USB API are welcome at
-      freebsd-usb@freebsd.org .</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the time since the last status report, one security advisory
-      has been issued concerning a problem in the base system of FreeBSD;
-      this problem was in "contributed" code maintained outside of
-      FreeBSD. In addition, several Errata Notices have been issued in
-      collaboration with the release engineering team, including one
-      concerning FreeBSD Update. The Vulnerabilities and Exposures Markup
-      Language (VuXML) document has continued to be updated by the
-      Security Team and Ports Committers documenting new vulnerabilities
-      in the FreeBSD Ports Collection; since the last status report, 21
-      new entries have been added, bringing the total up to 890.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2. Of
-      particular note, FreeBSD 4.11 and FreeBSD 6.0 are no longer
-      supported. The respective End of Life dates of supported releases
-      are listed on the web site.</p>
-    <hr /><h2><a name="Problem-Report-Database" href="#Problem-Report-Database" id="Problem-Report-Database">Problem Report Database</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/support.html#gnats" title="http://www.freebsd.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.freebsd.org/support.html#gnats" title="GNATS">http://www.freebsd.org/support.html#gnats</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister_at_freebsd_dot_org">bugmeister_at_freebsd_dot_org</a>&gt;
-	</p>
-      <p>We have added Remko Lodder to the bugmeister team. Remko has
-      been doing a great deal of work to go through antique PRs,
-      especially in the i386 category, and it was time to recognize that
-      hard work. As a result of his work the i386 count is at a
-      multi-year low.</p>
-
-      <p>Remko has also been instrumental in working with some new
-      volunteers who are interested in finding out how they can
-      contribute. Our current plans are to ask them to look through the
-      PR backlog and, firstly, ask for feedback from the submitters, and
-      secondly, identify PRs that need action by committers. We also have
-      some committers who have volunteered to review those PRs. If you
-      are interested in helping, please subscribe to
-      bugbusters@FreeBSD.org. Our thanks to our current helpers,
-      including Harrison Grundy.</p>
-
-      <p>The overall PR count has dropped to around 5100, a significant
-      reduction.</p>
-    <hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/snapshots/" title="http://www.FreeBSD.org/snapshots/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/snapshots/" title="">http://www.FreeBSD.org/snapshots/</a></td></tr></table><p>
-	Contact:
-          Release Engineering Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the past quarter, the Release Engineering team has begun
-      planning and preparing for FreeBSD 7.0, which is scheduled for
-      release later in 2007. The HEAD codeline has been placed in a
-      "slush" mode, meaning that large changes should be coordinated with
-      the Release Engineering team before being committed.</p>
-
-      <p>The RE team also produced snapshots of FreeBSD 6.2-STABLE and
-      7.0-CURRENT for February and March 2007, corresponding roughly to
-      the state of those development branches at the start of the
-      respective months. While they have not had the benefit of extensive
-      testing, and should not be used in production, they can be useful
-      for experimenting with or testing new features.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org" title="http://www.freebsdfoundation.org">The FreeBSD Foundation</a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org" title="The FreeBSD Foundation">http://www.freebsdfoundation.org</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@FreeBSD.org">deb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation ended Q1 raising over $65,000. We're a
-      quarter of the way to our goal of raising $250,000 this year. We
-      continued our mission of supporting developer communication by
-      helping FreeBSD developers attend AsiaBSDCon. We are a sponsor of
-      BSDCan and are currently accepting travel grant applications for
-      this conference.</p>
-
-      <p>The foundation provided support that helped the ZFS file system
-      development. We continued working to upgrade the project's network
-      testbed with 10Gigabit interconnects. We attended SCALE where we
-      received an offer from No Starch Press to include a foundation ad
-      in their BSD books. Our first ad will appear in the book "Designing
-      BSD Rootkits."</p>
-
-      <p>For more information on what we've been up to, check out our
-      website at
-      <a href="http://www.freebsdfoundation.org" shape="rect">
-      http://www.freebsdfoundation.org</a>
-
-      .</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Building-Linux-Device-Drivers-on-FreeBSD" href="#Building-Linux-Device-Drivers-on-FreeBSD" id="Building-Linux-Device-Drivers-on-FreeBSD">Building Linux Device Drivers on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html" title="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html"></a></td><td>
-	    URL: <a href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html" title="">http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html</a></td></tr></table><p>
-	Contact:
-          Luigi
-
-          Rizzo
-         &lt;<a href="mailto:rizzo@icir.org">rizzo@icir.org</a>&gt;
-	</p>
-      <p>The above URL documents some work done around January to build
-      an emulation layer for the Linux kernel API that would allow Linux
-      device driver to be built on FreeBSD with as little as possible
-      modifications. Initially the project focused on USB webcams, a
-      category of devices for which there was basically no support so
-      far. The emulation layer, available as a port (
-      <b>devel/linux-kmod-compat</b>
-
-      ) simulates enough of the Linux USB stack to let us build, from
-      unmodified Linux sources, two webcam drivers, also available as
-      ports (
-      <b>multimedia/linux-gspca-kmod</b>
-
-      and
-      <b>multimedia/linux-ov511-kmod</b>
-
-      ), with the former supporting over 200 different cameras.</p>
-
-      <p>While some of the functions map one-to-one, for others it was
-      necessary to build a full emulation (e.g. collecting input from
-      various function calls, and then mapping sets of Linux data
-      structures into functionally equivalent sets of FreeBSD data
-      structures). But overall, this project shows that the software
-      interfaces are reasonably orthogonal to each other so one does not
-      need to implement the full Linux kernel API to get something
-      working. More work is necessary to cover other aspects of the Linux
-      kernel API, e.g. memory mapping, PCI bus access, and the network
-      stack API, so we can extend support to other families of
-      peripherals.</p>
-    <h3>Open tasks:</h3><ol><li>Implement more subsystems (e.g. the network interface API;
-      the memory management/pci bus access API).</li><li>Address licensing issues. In the current port, the C code is
-      entirely new and under a FreeBSD license. Many of the headers have
-      been rewritten (and documented) from scratch (and so under a
-      FreeBSD license as well). Some of the other headers are still taken
-      from various Linux distributions and need to be rewritten to
-      generate BSD-licensed code that can be imported in the kernel
-      instead of being made available as a port. While this is not a
-      concern with GNU drivers, it may be an important feature for
-      drivers that are available under a dual license.</li></ol><hr /><h2><a name="Update-of-the-Linux-compatibility-environment-in-the-kernel" href="#Update-of-the-Linux-compatibility-environment-in-the-kernel" id="Update-of-the-Linux-compatibility-environment-in-the-kernel">Update of the Linux compatibility environment in the
-    kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/linux-kernel" title="http://wiki.FreeBSD.org/linux-kernel">Wiki page about the linux compatibility environment.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/linux-kernel" title="Wiki page about the linux compatibility environment.">http://wiki.FreeBSD.org/linux-kernel</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/linux-kernel/ltp" title="http://wiki.FreeBSD.org/linux-kernel/ltp">Wiki page about the linux test project testsuite success reports.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/linux-kernel/ltp" title="Wiki page about the linux test project testsuite success reports.">http://wiki.FreeBSD.org/linux-kernel/ltp</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Leidinger
-         &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Roman
-
-          Divacky
-         &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Emulation
-
-          Mailinglist
-         &lt;<a href="mailto:emulation@FreeBSD.org">emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report AMD64 was feature synced with i386.
-      Notably TLS and futexes are now available on AMD64. Many thanks to
-      Jung-Uk Kim for doing the TLS work.</p>
-
-      <p>Currently the focus is to implement the *at() family of linux
-      syscalls and to find and fix the remaining futex problems.</p>
-
-      <p>We need some more testers and bug reporters. So if you have a
-      little bit of time and a favorite linux application, please play
-      around with it on -CURRENT. If there is a problem, have a look at
-      the Wiki if we already know about it and report on emulation@. We
-      are specially interested in reports about the 2.6 compatibility
-      (sysctl compat.linux.osversion=2.6.16), but only with the most
-      recent -current and maybe with some patches we have in the perforce
-      repository (available from the wiki).</p>
-
-      <p>We would like to thank all the people which tested the changes /
-      submitted patches and thus helped improve the linux compatibility
-      environment.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="FAST_IPSEC-Upgrade" href="#FAST_IPSEC-Upgrade" id="FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~gnn/fast_ipv6.20070430.diff" title="http://people.freebsd.org/~gnn/fast_ipv6.20070430.diff">Latest patch against CURRENT</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~gnn/fast_ipv6.20070430.diff" title="Latest patch against CURRENT">http://people.freebsd.org/~gnn/fast_ipv6.20070430.diff</a></td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern
-
-          Zeeb
-         &lt;<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>&gt;
-	</p>
-      <p>There are currently two p4 branches being used for this work:
-      gnn_fast_ipsec: a dual stack branch which contains both Kame and
-      FAST_IPSEC with v6 enabled. gnn_radical_ipsec: a single stack
-      branch, still in progress, where Kame IPsec has been removed and
-      only FAST remains.</p>
-    <h3>Open tasks:</h3><ol><li>Test the patch!</li></ol><hr /><h2><a name="Importing-trunk(4)-from-OpenBSD" href="#Importing-trunk(4)-from-OpenBSD" id="Importing-trunk(4)-from-OpenBSD">Importing trunk(4) from OpenBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~thompsa/if_trunk-20070402.diff" title="http://people.freebsd.org/~thompsa/if_trunk-20070402.diff"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~thompsa/if_trunk-20070402.diff" title="">http://people.freebsd.org/~thompsa/if_trunk-20070402.diff</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has completed to port over trunk(4) from OpenBSD and this
-      also includes merging 802.3ad LACP from agr(4) in NetBSD. This
-      driver allows aggregation of multiple network interfaces as one
-      virtual interface using a number of different
-      protocols/algorithms.</p>
-
-      <ul>
-        <li>failover - Sends traffic through the secondary port if the
-        master becomes inactive.</li>
-
-        <li>fec - Supports Cisco Fast EtherChannel.</li>
-
-        <li>lacp - Supports the IEEE 802.3ad Link Aggregation Control
-        Protocol (LACP) and the Marker Protocol.</li>
-
-        <li>loadbalance - Static loadbalancing using an outgoing
-        hash.</li>
-
-        <li>roundrobin - Distributes outgoing traffic using a round-robin
-        scheduler through all active ports.</li>
-      </ul>
-
-      <p>This will be committed shortly, further testing is welcome.</p>
-    <hr /><h2><a name="Intel-3945ABG-Wireless-LAN-Driver:-wpi" href="#Intel-3945ABG-Wireless-LAN-Driver:-wpi" id="Intel-3945ABG-Wireless-LAN-Driver:-wpi">Intel 3945ABG Wireless LAN Driver: wpi</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi"></a></td><td>
-	    URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi" title="">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/benjsc/wpi</a></td></tr><tr><td><a href="http://www.clearchain.com/wiki/Wpi" title="http://www.clearchain.com/wiki/Wpi"></a></td><td>
-	    URL: <a href="http://www.clearchain.com/wiki/Wpi" title="">http://www.clearchain.com/wiki/Wpi</a></td></tr></table><p>
-	Contact:
-          Benjamin
-
-          Close
-         &lt;<a href="mailto:benjsc@freebsd.org">benjsc@freebsd.org</a>&gt;
-	</p>
-      <p>Work is slowly continuing on this driver, focusing mainly on
-      dealing with the newly released firmware for the card. The old
-      firmware was not redistributable, the new firmware can be
-      redistributed but has a completely different API. With the new
-      firmware changes almost complete, the driver is approaching a state
-      ready for -CURRENT.</p>
-    <h3>Open tasks:</h3><ol><li>Fix mbuf leakage (potential fix pending).</li><li>Integrate s/w control of radio transmitter.</li></ol><hr /><h2><a name="Multi-link-PPP-daemon-(MPD)" href="#Multi-link-PPP-daemon-(MPD)" id="Multi-link-PPP-daemon-(MPD)">Multi-link PPP daemon (MPD)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sourceforge.net/projects/mpd/" title="http://sourceforge.net/projects/mpd/">Project home</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/mpd/" title="Project home">http://sourceforge.net/projects/mpd/</a></td></tr><tr><td><a href="http://mpd.sourceforge.net/doc/mpd5.html" title="http://mpd.sourceforge.net/doc/mpd5.html">ChangeLog</a></td><td>
-	    URL: <a href="http://mpd.sourceforge.net/doc/mpd5.html" title="ChangeLog">http://mpd.sourceforge.net/doc/mpd5.html</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Motin
-         &lt;<a href="mailto:mav@alkar.net">mav@alkar.net</a>&gt;
-	</p>
-      <p>Stable release 4.1 of mpd4 branch was released in February
-      providing many new features and fixes. Mpd3 branch was declared
-      legacy.</p>
-
-      <p>Since the release several new features have been implemented in
-      CVS:</p>
-
-      <ul>
-        <li>Link repeater functionality (aka L2TP/PPTP Access
-        Concentrator),</li>
-
-        <li>Per-interface traffic filtering using ng_bpf,</li>
-
-        <li>Very fast traffic shaping/rate-limiting using ng_car.</li>
-      </ul>
-
-      <p>ng_car node has been updated, to support shaping and very fast
-      Cisco-like rate-limiting. ng_ppp node has been completely
-      re-factored to confirm to the protocol stack model.</p>
-    <h3>Open tasks:</h3><ol><li>LAC/PAC testing.</li><li>Traffic filtering/shaping/rate-limiting testing.</li><li>PPTP modification for multiple bindings support.</li><li>Dynamic link/bundle creation.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="GCC-4.1-integration" href="#GCC-4.1-integration" id="GCC-4.1-integration">GCC 4.1 integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Alexander
-
-          Kabaev
-         &lt;<a href="mailto:kan@FreeBSD.org">kan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Kris
-
-          Kennaway
-         &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-      <p>A version of GCC 4.1 is being prepared for inclusion into
-      FreeBSD 7.0-CURRENT. Work was started late in 2006 but progress on
-      certain technical points (e.g. correctly integrating and
-      bootstrapping a shared libgcc_s into the build) was slow due to
-      lack of developer time. The remaining outstanding issue is that
-      compiling with -O2 is shown to lead to runtime failures of certain
-      binaries (e.g. some port builds); it is not currently known whether
-      these are due to application errors or GCC miscompilations. It is
-      believed that the current snapshot is otherwise ready for
-      inclusion, and this will likely happen within a week or two.</p>
-    <hr /><h2><a name="malloc(3)" href="#malloc(3)" id="malloc(3)">malloc(3)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2007-March/070303.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2007-March/070303.html">malloc(3) (hopefully) set for 7.0</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2007-March/070303.html" title="malloc(3) (hopefully) set for 7.0">http://lists.freebsd.org/pipermail/freebsd-current/2007-March/070303.html</a></td></tr></table><p>
-	Contact:
-          Jason
-
-          Evans
-         &lt;<a href="mailto:jasone@freebsd.org">jasone@freebsd.org</a>&gt;
-	</p>
-      <p>malloc(3) has recently been enhanced to reduce memory overhead,
-      fragmentation, and mapped memory retention. As an added bonus, it
-      tends to be a bit faster. See the above URL for my email to the
-      -current mailing list for a more detailed description of the
-      enhancements.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports count is nearing 17,000. The PR count has been stable
-      at around 700. The 'new port' PR backlog is at a multi-year low. We
-      appreciate all the hard work of our ports committers.</p>
-
-      <p>Since the long 6.2 release cycle ended, portmgr has once again
-      been able to do experimental ports runs. As a result of six
-      run/commit cycles, the portmgr PR count is now the lowest in quite
-      some time. Please see the CHANGES and UPDATING files for details.
-      Many thanks to Pav among others for keeping the build cluster
-      busy.</p>
-
-      <p>We have received new hardware, resulting in a significant
-      speedup of our package building capability: the AMD64 package
-      builds now use 4 8-core machines (and one lonely UP system), which
-      means a full AMD64 build is about 5 times faster than it was. Also,
-      the i386 cluster gained an 8-core and roughly doubled its
-      performance too. Two of the sparc64 build machines have recently
-      brought back online, so package builds there have been restarted
-      there after a long period offline.</p>
-
-      <p>linimon continues to work on improvements to portsmon to allow
-      graphing of the dependent ports of ignored/failed ports. This work
-      will be presented at BSDCan. In addition, pages that show the state
-      of port uploads on ftp*.FreeBSD.org have been added, as well as
-      ports that have NO_PACKAGE set. Also, the individual port overview
-      page now shows the latest package that has been uploaded to the ftp
-      servers for each buildenv.</p>
-
-      <p>A number of absent maintainers have been replaced by some new
-      volunteers who had been sending PRs to update and/or fix their
-      ports. Welcome! This helps to spread the workload.</p>
-
-      <p>Since the last report, support for FreeBSD 4.X has been dropped
-      from the Ports Collection. Anyone still using RELENG_4 should have
-      stayed with the ports infrastructure as of the RELEASE_4_EOL tag, as
-      later commits remove that support. 4.X served us long and well but
-      the burden of trying to support 4 major branches finally became too
-      much to ask of our volunteers. Use of 4.X, even with the
-      RELEASE_4_EOL tag, is no longer recommended; we recommend either
-      6.2-RELEASE or RELENG_6, depending on your needs.</p>
-
-      <p>There have been new releases of the ports tinderbox code, the
-      portmaster update utility, and portupgrade. A new utility,
-      pkgupgrade, has been introduced by Michel Talon, which appears
-      interesting.</p>
-
-      <p>KDE was updated to 3.5.6.</p>
-
-      <p>GNOME was updated to 2.18.</p>
-
-      <p>XFree86 version 3 was removed as being years out of date.</p>
-
-      <p>We have added 3 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have many
-      unmaintained ports. The number of buildable packages on AMD64 lags
-      behind a bit; sparc64 requires even more work.</li></ol><hr /><h2><a name="X.Org-7.2-integration" href="#X.Org-7.2-integration" id="X.Org-7.2-integration">X.Org 7.2 integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/ModularXorg" title="http://wiki.freebsd.org/ModularXorg"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/ModularXorg" title="">http://wiki.freebsd.org/ModularXorg</a></td></tr></table><p>
-	Contact:
-          Florent
-
-          Thoumie
-         &lt;<a href="mailto:flz@FreeBSD.org">flz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Dejan
-
-          Lesjak
-         &lt;<a href="mailto:lesi@FreeBSD.org">lesi@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Kris
-
-          Kennaway
-         &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-      <p>X.Org 7.2 is now on final approach for landing into the ports
-      tree. Work had proceeded at a slow pace for the first few months of
-      the year due to reduced availability of flz@, the single developer
-      working on integration. Recently lesi@ was recruited back into the
-      task and readiness of the ports collection was pushed to completion
-      (i.e. there are no major regressions apparent on package builds).
-      The remaining tasks which need to be completed are a review of the
-      diff to make sure no unintentional changes or regressions slip in
-      to the CVS tree in the big merge, and completion of an upgrade
-      script to manage the migration from X.Org 6.9 (X.Org 7.2 is so
-      fundamentally different that it cannot be upgraded "automatically"
-      using the existing tools like portupgrade). We hope to have these
-      finished within a week or two, at which stage the ports collection
-      will be frozen for the integration, and we will likely remain in a
-      ``mini-freeze'' for a week or two in order to focus committer
-      attention on resolving the inevitable undetected problems which
-      will emerge from this major change.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan-2007" href="#BSDCan-2007" id="BSDCan-2007">BSDCan 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/2007/" title="http://www.bsdcan.org/2007/">BSDCan 2007</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2007/" title="BSDCan 2007">http://www.bsdcan.org/2007/</a></td></tr></table><p>
-	Contact:
-          Dan
-
-          Langille
-         &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-      <p>The
-      <a href="http://www.bsdcan.org/2007/schedule/" shape="rect">Schedule</a>
-
-      and the
-      <a href="http://www.bsdcan.org/2007/schedule/track/Tutorial/index.en.html" shape="rect">
-      Tutorials</a>
-
-      have been released. Once again, we have a very strong collection of
-
-      <a href="http://www.bsdcan.org/2007/schedule/speakers.en.html" shape="rect">
-      Speakers</a>
-
-      .</p>
-
-      <p>BSDCan: Low Cost. High Value. Something for Everyone.</p>
-
-      <p>Everyone is going to be there. Make your plans now.</p>
-    <hr /><h2><a name="EuroBSDCon-2007" href="#EuroBSDCon-2007" id="EuroBSDCon-2007">EuroBSDCon 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2007.EuroBSDCon.org/" title="http://2007.EuroBSDCon.org/"></a></td><td>
-	    URL: <a href="http://2007.EuroBSDCon.org/" title="">http://2007.EuroBSDCon.org/</a></td></tr></table><p>
-	Contact:
-          EuroBSDCon 2007 Organizing Committee
-         &lt;<a href="mailto:info@EuroBSDCon.dk">info@EuroBSDCon.dk</a>&gt;
-	</p>
-      <p>The sixth EuroBSDCon will take place at
-      <a href="http://uk.symbion.dk/" shape="rect">Symbion</a>
-
-      in Copenhagen, Denmark on Friday the 14th and Saturday 15th of
-      September 2007.</p>
-
-      <p>The
-      <strong>estimated</strong>
-
-      price for the two day conference is 200EUR, excluding
-      <a href="http://www.legoland.dk/" shape="rect">Legoland</a>
-
-      trip and social event. The whole-day trip to Legoland is expected
-      to cost around 130EUR including transportation, some food on the
-      way, and entry fee. Arrangements have been made with a newly
-      renovated
-      <a href="http://danhostel.dk/vandrerhjem.asp?lan=uk&amp;id=144" shape="rect">
-      Hostel</a>
-
-      which offers beds for 23EUR per night and 10EUR breakfast. A lounge
-      with sponsored Internet connection will be available at the Hostel.
-      Staying at the hostel is of course entirely optional and several
-      Hotels exists in the area. Reservation for the conference and exact
-      prices are expected to be ready no later than 1st of May.</p>
-
-      <p>As of this writing 10 presentations have been accepted and more
-      are in the process of being evaluated.</p>
-
-      <p>For FreeBSD Developers, a by invitation Developers summit will
-      be held in connection with the conference. Exactly when this will
-      take place has not yet been decided.</p>
-
-      <p>We are still looking for more sponsors.</p>
-
-      <p>A public IRC channel
-      <strong>#eurobsdcon</strong>
-
-      on EFnet has been created for discussion and questions about the
-      conference.</p>
-
-      <p>More details will follow on the
-      <a href="http://2007.EuroBSDCon.org/" shape="rect">EuroBSDCon 2007 web site</a>
-
-      as they become available.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2007-04-2007-06.html b/website/content/en/status/report-2007-04-2007-06.html
deleted file mode 100644
index 5928b362ac..0000000000
--- a/website/content/en/status/report-2007-04-2007-06.html
+++ /dev/null
@@ -1,1927 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between April and
-    June 2007. Again an exciting quarter for FreeBSD. In May we saw one
-    of the biggest developers summits to date at
-    <a href="http://www.bsdcan.org/2007/" shape="rect">BSDCan</a>
-
-    , our 25 Google Summer of Code students started working on
-    <a href="http://www.freebsd.org/projects/summerofcode-2007.html" shape="rect">
-    their projects</a>
-
-    - progress reports are available below, and finally the 7.0 release
-    cycle was started three weeks ago.</p><p>If your are curious about what's new in FreeBSD 7.0 we suggest
-    reading Ivan Voras' excellent summary at:
-    <a href="http://ivoras.sharanet.org/freebsd/freebsd7.html" shape="rect">
-    http://ivoras.sharanet.org/freebsd/freebsd7.html</a>
-
-    and of course these reports.</p><p>The next gathering of the BSD community will be at
-    <a href="http://2007.eurobsdcon.org/" shape="rect">EuroBSDCon in Copenhagen</a>
-
-    , September 14-15. More details about the conference and the
-    developer summit are available in the respective reports below.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Google-summer-of-code">Google summer of code</a></h3><ul><li><a href="#A-GUI-audit-analyzer-for-FreeBSD">A GUI audit analyzer for FreeBSD</a></li><li><a href="#Apple's-MacBook-on-FreeBSD">Apple's MacBook on FreeBSD</a></li><li><a href="#BSD-Bintools-project">BSD Bintools project</a></li><li><a href="#Distributed-Logging-Daemon">Distributed Logging Daemon</a></li><li><a href="#finstall">finstall</a></li><li><a href="#FreeBSD-update-front-end">FreeBSD-update front end</a></li><li><a href="#Gvinum-improvements">Gvinum improvements</a></li><li><a href="#http-support-for-PXE">http support for PXE</a></li><li><a href="#Linuxulator-update">Linuxulator update</a></li><li><a href="#lockmgr-rewriting">lockmgr rewriting</a></li><li><a href="#mtund---Magic-Tunnel-Daemon">mtund - Magic Tunnel Daemon</a></li><li><a href="#Multicast-DNS-and-Service-Discovery">Multicast DNS and Service Discovery</a></li><li><a href="#Porting-Linux-KVM-to-FreeBSD">Porting Linux KVM to FreeBSD</a></li><li><a href="#Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD">Porting OpenBSD's sysctl Hardware Sensors Framework to
-    FreeBSD</a></li><li><a href="#Ports-Collection-infrastructure-improvements">Ports Collection infrastructure improvements</a></li><li><a href="#Security-Regression-Test">Security Regression Test</a></li><li><a href="#tarfs:-A-tar-File-System">tarfs: A tar File System</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD/xen">FreeBSD/xen</a></li><li><a href="#HDTV-Drivers-(ATSC)">HDTV Drivers (ATSC)</a></li><li><a href="#Kernel-contention-reduction-using-mysql">Kernel contention reduction using mysql</a></li><li><a href="#Stack-trace-capture-in-PMCTools">Stack trace capture in PMCTools</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#TrustedBSD-MAC-Framework">TrustedBSD MAC Framework</a></li><li><a href="#USB">USB</a></li><li><a href="#USB-update">USB update</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Problem-Report-Database">Problem Report Database</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#Security-Officer-and-Security-Team">Security Officer and Security Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Fine-grain-thread-locking">Fine grain thread locking</a></li><li><a href="#gvirstor">gvirstor</a></li><li><a href="#SCHED_SMP-and-SCHED_ULE">SCHED_SMP and SCHED_ULE</a></li><li><a href="#TrustedBSD-priv(9)">TrustedBSD priv(9)</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#10Gigabit-Network-Support">10Gigabit Network Support</a></li><li><a href="#FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></li><li><a href="#FreeBSD-and-Wake-On-Lan">FreeBSD and Wake On Lan</a></li><li><a href="#Multi-link-PPP-daemon-(MPD)">Multi-link PPP daemon (MPD)</a></li><li><a href="#Multiprocessor-Network-Stack">Multiprocessor Network Stack</a></li><li><a href="#Network-Stack-Virtualization">Network Stack Virtualization</a></li><li><a href="#Wireless-Networking">Wireless Networking</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#FreeBSD-and-Coverity-Prevent">FreeBSD and Coverity Prevent</a></li><li><a href="#FreeSBIE">FreeSBIE</a></li><li><a href="#OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></li><li><a href="#PC-BSD">PC-BSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#EuroBSDcon-2007">EuroBSDcon 2007</a></li><li><a href="#EuroBSDCon-2007-Developer-Summit">EuroBSDCon 2007 Developer Summit</a></li><li><a href="#libarchive/bsdtar">libarchive/bsdtar</a></li><li><a href="#The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-summer-of-code" href="#Google-summer-of-code" id="Google-summer-of-code">Google summer of code</a></h1><br /><h2><a name="A-GUI-audit-analyzer-for-FreeBSD" href="#A-GUI-audit-analyzer-for-FreeBSD" id="A-GUI-audit-analyzer-for-FreeBSD">A GUI audit analyzer for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="" title=""></a></td><td>
-	    URL: <a href="" title=""></a></td></tr></table><p>
-	Contact:
-          Dongmei
-
-          Liu
-         &lt;<a href="mailto:ldm@ercist.iscas.ac.cn">ldm@ercist.iscas.ac.cn</a>&gt;
-	</p>
-      <p>This project is due to provide a GUI audit log analysis tool
-      for FreeBSD. Refer to ethereal/wireshark packet parsing engine
-      and its framework to view and parse audit logs.</p>
-    <h3>Open tasks:</h3><ol><li>Get a GUI framework using GTK2.0 include menu bar, toolbar,
-      list view and tree view.</li><li>Parse and display audit log in the trailer file in the list
-      view and tree view.</li><li>Online capture audit log and parse and display them in the
-      list view and tree view</li><li>Add the filter mechanism</li><li>Add the statistic mechanism</li><li>Remote audit log analysis mechanism</li></ol><hr /><h2><a name="Apple's-MacBook-on-FreeBSD" href="#Apple's-MacBook-on-FreeBSD" id="Apple's-MacBook-on-FreeBSD">Apple's MacBook on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/rpaulo%2dmacbook/" title="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/rpaulo%2dmacbook/">P4 repository</a></td><td>
-	    URL: <a href="http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/rpaulo%2dmacbook/" title="P4 repository">http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/rpaulo%2dmacbook/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/AppleMacbook" title="http://wiki.freebsd.org/AppleMacbook">wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/AppleMacbook" title="wiki page">http://wiki.freebsd.org/AppleMacbook</a></td></tr></table><p>
-	Contact:
-          Rui
-
-          Paulo
-         &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Apple's MacBook computers are nicely designed and have neat
-      features that other laptops don't. While Mac OS X is a nice
-      operating system, UNIX folks (like me) would prefer to run other
-      operating systems like FreeBSD. This project aims to bring bug
-      fixes and new drivers to FreeBSD that would help running this OS
-      on this platform.</p>
-    <h3>Open tasks:</h3><ol><li>Write drivers or fix issues for/with the touchpad,
-      keyboard, remote control IR receiver, Bluetooth.</li><li>Fix reboot, halt, suspend/resume issues.</li></ol><hr /><h2><a name="BSD-Bintools-project" href="#BSD-Bintools-project" id="BSD-Bintools-project">BSD Bintools project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/BSDBintools" title="http://wiki.freebsd.org/BSDBintools"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/BSDBintools" title="">http://wiki.freebsd.org/BSDBintools</a></td></tr></table><p>
-	Contact:
-          Kai
-
-          Wang
-         &lt;<a href="mailto:kaiw27@gmail.com">kaiw27@gmail.com</a>&gt;
-	</p>
-      <p>A basic implementation of ar(1) (include ranlib) was finished
-      and available in the perforce repository. Currently it provides
-      all the main functions an ar(1) should have and it is based on
-      the libarchive and libelf library thus is expected to have a
-      better and simpler structure than the GPL'ed version. The work
-      left in this part of the project is to perform a elaborate test
-      and add additional functions.</p>
-    <hr /><h2><a name="Distributed-Logging-Daemon" href="#Distributed-Logging-Daemon" id="Distributed-Logging-Daemon">Distributed Logging Daemon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=232192+0+/usr/local/www/db/text/2007/freebsd-hackers/20070527.freebsd-hackers" title="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=232192+0+/usr/local/www/db/text/2007/freebsd-hackers/20070527.freebsd-hackers">Description of the project design</a></td><td>
-	    URL: <a href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=232192+0+/usr/local/www/db/text/2007/freebsd-hackers/20070527.freebsd-hackers" title="Description of the project design">http://docs.freebsd.org/cgi/getmsg.cgi?fetch=232192+0+/usr/local/www/db/text/2007/freebsd-hackers/20070527.freebsd-hackers</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/karma%5faudit/dlog&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/karma%5faudit/dlog&amp;HIDEDEL=NO">Perforce repository for project hosting</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/karma%5faudit/dlog&amp;HIDEDEL=NO" title="Perforce repository for project hosting">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/karma%5faudit/dlog&amp;HIDEDEL=NO</a></td></tr></table><p>
-	Contact:
-          Alexey
-
-          Mikhailov
-         &lt;<a href="mailto:karma@FreeBSD.org">karma@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The basic idea behind this project is to implement secure and
-      reliable log file shipping to remote hosts. While the
-      implementation focuses on audit logs, the goal is to build tools
-      that will make it possible to perform distributed logging for any
-      application by using a simple API and linking with a shared
-      library.</p>
-    <h3>Open tasks:</h3><ol><li>Network protocol implementation</li><li>Spooling</li><li>SSL support</li></ol><hr /><h2><a name="finstall" href="#finstall" id="finstall">finstall</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/finstall" title="http://wiki.freebsd.org/finstall"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/finstall" title="">http://wiki.freebsd.org/finstall</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@FreeBSD.org">ivoras@FreeBSD.org</a>&gt;
-	</p>
-      <p>Project "finstall" aims to create a next-generation FreeBSD
-      installer that will make use of the newest features present in
-      the system. The project should yield something usable for
-      7.0-RELEASE, but the intention is to keep it as a "second"
-      installer system during 7.x, alongside sysinstall. In any case,
-      sysinstall will be kept for architectures not supported by
-      finstall (e.g. all except i386 and amd64).</p>
-    <h3>Open tasks:</h3><ol><li>The work is progressing well and on plan. There's a small
-      setback currently with X11 applications executing of a read-only
-      file system (at least that's the currently recognizable
-      symptom).</li><li>Any interested testers are very much welcome!</li></ol><hr /><h2><a name="FreeBSD-update-front-end" href="#FreeBSD-update-front-end" id="FreeBSD-update-front-end">FreeBSD-update front end</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/FreeBSDUpdateFrontend" title="http://wiki.freebsd.org/FreeBSDUpdateFrontend"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/FreeBSDUpdateFrontend" title="">http://wiki.freebsd.org/FreeBSDUpdateFrontend</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Turner
-         &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project is split up with a front end to interact with the
-      user and a back end to interact with freebsd-update. The back and
-      front ends are able to communicate with each other using an XML
-      protocol. The GUI is almost at the point it can take a command
-      from the user and send it to the back end. The back end is able
-      to detect when updates are ready.</p>
-    <hr /><h2><a name="Gvinum-improvements" href="#Gvinum-improvements" id="Gvinum-improvements">Gvinum improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/soc2007" title="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/soc2007">Patches of my SoC wo</a></td><td>
-	    URL: <a href="http://folk.ntnu.no/lulf/patches/freebsd/gvinum/soc2007" title="Patches of my SoC wo">http://folk.ntnu.no/lulf/patches/freebsd/gvinum/soc2007</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/lulf/" title="http://blogs.freebsdish.org/lulf/">Weblog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/lulf/" title="Weblog">http://blogs.freebsdish.org/lulf/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/UlfLilleengen/SOC" title="http://wiki.freebsd.org/UlfLilleengen/SOC">Wikipage</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/UlfLilleengen/SOC" title="Wikipage">http://wiki.freebsd.org/UlfLilleengen/SOC</a></td></tr></table><p>
-	Contact:
-          Ulf
-
-          Lilleengen
-         &lt;<a href="mailto:lulf@FreeBSD.org">lulf@FreeBSD.org</a>&gt;
-	</p>
-      <p>My previous status reports contained a lot of code that
-      updated gvinum with the old vinum features.</p>
-
-      <p>This year gvinum has been significantly rewritten. Lukas Ertl
-      began rewriting the way gvinum is organized from using a multi
-      consumer/provider model, to use a single consumer and provider,
-      and having an event-system that first handles user-requests, and
-      then runs normal I/O operations (Much like other GEOM classes).
-      This makes the code easier to read, and perhaps there will be
-      less bugs :)</p>
-
-      <ol>
-        <li>setstate on plexes and volumes.</li>
-
-        <li>attach/detach command now works.</li>
-
-        <li>concat/stripe/mirror commands. The previous code conflicted
-        more than I expected with the new gvinum system, but it should
-        work now.</li>
-
-        <li>(Mounted) rebuilds possible.</li>
-
-        <li>(Mounted) sync possible.</li>
-
-        <li>Some refactoring of old code (Basically updating old code
-        to use the new event system, and add some abstractions where
-        possible)</li>
-      </ol>
-
-      <p>And of course, some time has gone to work out how things
-      should be done, and to fix other bugs. I hope some of you are
-      interested in trying this out (all the work has been in perforce
-      so far), a patch can be found in the URL section. . This is a bit
-      experimental, and although I've done much testing to hunt down
-      bugs, there are most probably bugs left.</p>
-
-      <p>I have other goals this summer as well. However, since some
-      parts of gvinum was rewritten, I might not be able to do all of
-      these, but growing is already working for the concatenated
-      volumes (and also mirrored). I'd also like to implement growing
-      for Raid5 arrays as well. Logging plexes would also be cool to
-      have, but this is not really needed, since we have g_journal.
-      Both these features will be addressed after I've made sure gvinum
-      does all old vinum does, and also perhaps better. As I might have
-      some extra time on my hands this summer, so I gladly accept
-      suggestions on what else I might fix or implement "while I'm at
-      it".</p>
-    <h3>Open tasks:</h3><ol><li>Stability, stability, stability. I want gvinum to work
-      really well. To accomplish that I have several test-machines I'm
-      going to do different tests on. I sort of have a little test-plan
-      in the working that I'll be using.</li><li>A gvinumadmin tool that would make gvinum easier to use for
-      unexperienced users. Perhaps integrate this into the installer.
-      This is now probably something I'll do at the end, when hopefully
-      everything works :) I might poke Ivan Voras a bit on this.</li><li>Documenting gvinum and it's differences to vinum better. I
-      take notes on where I need to document, so this is in
-      progress.</li><li>Implementing growing and shrinking of volumes.</li><li>Implement logging plexes. Log all parity data being
-      written.</li></ol><hr /><h2><a name="http-support-for-PXE" href="#http-support-for-PXE" id="http-support-for-PXE">http support for PXE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/taleks-pxe_http" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/taleks-pxe_http">Project repository.</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/taleks-pxe_http" title="Project repository.">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/taleks-pxe_http</a></td></tr><tr><td><a href="http://wiki.freebsd.org/http_support_for_PXE" title="http://wiki.freebsd.org/http_support_for_PXE">Project related Wiki-page.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/http_support_for_PXE" title="Project related Wiki-page.">http://wiki.freebsd.org/http_support_for_PXE</a></td></tr></table><p>
-	Contact:
-          Alexey
-
-          Tarasov
-         &lt;<a href="mailto:taleks@FreeBSD.org">taleks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Main goal of project is to introduce code working in PXE
-      preboot environment, able to download from web server via direct
-      connection or http proxy and prepare booting of FreeBSD
-      kernel.</p>
-
-      <p>Already implemented, but haven't thoroughly tested: PXE
-      wrappers core code, ARP, ICMP echo request/reply, sockets code
-      similar to common sockets (UDP and TCP modules). On base of
-      sockets: simple DHCP client, DNS client.</p>
-
-      <p>Currently working on http client, TCP testing, kernel booting
-      and documenting main concepts of project modules.</p>
-    <h3>Open tasks:</h3><ol><li>Testing PXE API related code in different PXE
-      implementations.</li><li>Testing of implemented protocols.</li></ol><hr /><h2><a name="Linuxulator-update" href="#Linuxulator-update" id="Linuxulator-update">Linuxulator update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/linux-soc2007" title="http://wiki.freebsd.org/linux-soc2007">Linuxulator update 2007</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/linux-soc2007" title="Linuxulator update 2007">http://wiki.freebsd.org/linux-soc2007</a></td></tr></table><p>
-	Contact:
-          Roman
-
-          Divacky
-         &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Konstantin
-
-          Belousov
-         &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Just like last year I got the opportunity to work on updating
-      the Linuxulator to Linux version 2.6. This year I work on
-      finishing futexes, *at syscalls and epoll/inotify.</p>
-
-      <p>I, cooperating with Konstantin Belousov, have managed to fix
-      futexes to the state of passing the official futex testing
-      program. The fix was committed and 7.0R will ship with correct
-      futex implementation. Work is planned on removing Giant locking
-      from futexes. This only needs some careful review and
-      testing.</p>
-
-      <p>These days I mostly focus on *at syscalls, the patch is almost
-      finished for committing and I hope that it will make it into 7.0R.
-      As a part of this work I implemented native FreeBSD syscalls as
-      well. Watch arch mailing list as I post the patch there.</p>
-
-      <p>I also finished writing my master thesis describing how the
-      Linuxulator works and G�bor K�vesd�n is working
-      on integrating it into official FreeBSD articles.</p>
-
-      <p>No work has happened in the epoll/inotify area but I hope to
-      work on it right after I finish the *at syscalls.h</p>
-    <h3>Open tasks:</h3><ol><li>Finishing *at syscalls.</li><li>Start the epoll/inotify work.</li><li>Finish removal of Giant from futexes.</li></ol><hr /><h2><a name="lockmgr-rewriting" href="#lockmgr-rewriting" id="lockmgr-rewriting">lockmgr rewriting</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/AttilioRao" title="http://wiki.freebsd.org/AttilioRao">http://wiki.freebsd.org/AttilioRao</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/AttilioRao" title="http://wiki.freebsd.org/AttilioRao">http://wiki.freebsd.org/AttilioRao</a></td></tr></table><p>
-	Contact:
-          Attilio
-
-          Rao
-         &lt;<a href="mailto:attilio@FreeBSD.org">attilio@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Jeff
-
-          Roberson
-         &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project consists in a rewriting of the lockmgr(9)
-      interface on a lighter basis, using atomic instructions and
-      direct usage of the sleepqueue interface. This should lead to a
-      faster primitive, a saner interface and an higher maintainability
-      of the code.</p>
-
-      <p>So far, 3 newly files called kern/kern_lockng.c,
-      sys/_lockmgrng.h and sys/lockmgrng.h have been created for the
-      new primitive and an initial implementation has been committed
-      into the perforce branch:
-      //depot/user/attilio/attilio_lockmgr/...</p>
-
-      <p>The implementation contains a good set of code intended to
-      replace old lockmgr. Actually it only misses the support for lock
-      draining that will be committed after an initial phase of testing
-      and the inclusion of a better wake-up algorithm (which will
-      simplify draining a lot and will improve performance on
-      wakeup).</p>
-    <h3>Open tasks:</h3><ol><li>Need some testing</li></ol><hr /><h2><a name="mtund---Magic-Tunnel-Daemon" href="#mtund---Magic-Tunnel-Daemon" id="mtund---Magic-Tunnel-Daemon">mtund - Magic Tunnel Daemon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/SuperTunnelDaemon" title="http://wiki.freebsd.org/SuperTunnelDaemon">mtund wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SuperTunnelDaemon" title="mtund wiki page">http://wiki.freebsd.org/SuperTunnelDaemon</a></td></tr></table><p>
-	Contact:
-          Matus
-
-          Harvan
-         &lt;<a href="mailto:mharvan@FreeBSD.org">mharvan@FreeBSD.org</a>&gt;
-	</p>
-      <p>IP can easily be tunneled over a plethora of network protocols
-      at various layers, such as IP, ICMP, UDP, TCP, DNS, HTTP, SSH.
-      While a direct connection may not always be possible due to a
-      firewall, the IP packets could be encapsulated as payload in
-      other protocols, which would get through. However, each such
-      encapsulation requires the setup of a different program and the
-      user has to manually probe different encapsulations to find out
-      which of them works in a given environment.</p>
-
-      <p>mtund is a tunneling daemon using run-time loadable plugins
-      for the different encapsulations. It automagically selects the
-      best encapsulation in each environment and fails over to another
-      encapsulation in case the environment changes. There already is
-      running code available, capable of tunneling via TCP and UDP with
-      a working failover mechanism. As this is a Summer of Code
-      project, rapid changes and addition of new features can be
-      expected during the summer. Please see the wiki page for more
-      details and up-to-date information.</p>
-
-      <p>Note that the project originally started under the name of
-      Super Tunnel Daemon, but was later renamed to mtund for Magic
-      Tunnel Daemon.</p>
-    <h3>Open tasks:</h3><ol><li>I am always happy to hear from others trying out the code
-      and providing feedback, both positive and negative.</li></ol><hr /><h2><a name="Multicast-DNS-and-Service-Discovery" href="#Multicast-DNS-and-Service-Discovery" id="Multicast-DNS-and-Service-Discovery">Multicast DNS and Service Discovery</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/MulticastDNS" title="http://wiki.freebsd.org/MulticastDNS"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/MulticastDNS" title="">http://wiki.freebsd.org/MulticastDNS</a></td></tr></table><p>
-	Contact:
-          Fredrik
-
-          Lindberg
-         &lt;<a href="mailto:fli@FreeBSD.org">fli@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project aims to create a multicast DNS daemon and service
-      discovery utilities suitable for the base system. Multicast DNS
-      is a part of Zero Configuration Networking (Zeroconf) and
-      provides the ability to address hosts using DNS-like names
-      without the need of an existing (unicast), managed DNS server.
-      Work on the responder daemon is well underway and the only large
-      missing piece of the puzzle is a way for local clients to do
-      queries. The code can be found in the p4 branch
-      projects/soc2007/fli-mdns_sd if anyone would like to give it a
-      spin, even though it's incomplete. The project plan can be found
-      on the wiki.</p>
-    <hr /><h2><a name="Porting-Linux-KVM-to-FreeBSD" href="#Porting-Linux-KVM-to-FreeBSD" id="Porting-Linux-KVM-to-FreeBSD">Porting Linux KVM to FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/FabioChecconi/PortingLinuxKVMToFreeBSD" title="http://wiki.freebsd.org/FabioChecconi/PortingLinuxKVMToFreeBSD"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/FabioChecconi/PortingLinuxKVMToFreeBSD" title="">http://wiki.freebsd.org/FabioChecconi/PortingLinuxKVMToFreeBSD</a></td></tr></table><p>
-	Contact:
-          Fabio
-
-          Checconi
-         &lt;<a href="mailto:fabio@FreeBSD.org">fabio@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Luigi
-
-          Rizzo
-         &lt;<a href="mailto:luigi@FreeBSD.org">luigi@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Linux kernel-based Virtual Machine (KVM) is a mechanism to
-      exploit the virtualization extensions present in some modern CPUs
-      (e.g., Intel VT and AMD-V). Virtualization extensions let
-      ordinary processes execute a subset of privileged instructions in
-      a controlled way at near-native speed. This in turn may improve
-      the performance of system emulators such as qemu, xen, vmware,
-      vkernel, User Mode Linux (UML), etc.</p>
-
-      <p>This project consists in porting to FreeBSD the Linux KVM,
-      implemented as a loadable module, lkvm.ko. We use the approach in
-      ports/devel/linux-kmod-compat to reuse the original Linux source
-      code almost unmodified. We will also port a modified version of
-      qemu which exploits the facilities made available by the Linux
-      KVM to speed up emulation.</p>
-
-      <p>The URL above links to progress report detailing the exact
-      project goals, milestones reached, and commit log details.</p>
-
-      <p>As of end of June 2007, we have mainly extended
-      linux-kmod-compat to support the kernel API used by the Linux KVM
-      code. The required functions have been implemented at various
-      degrees, from simple stubs to fully functional ones. We have also
-      imported the modified qemu and the libraries that are used to
-      build the Linux KVM userspace client. In the second half of the
-      SoC work we plan to complete the implementation of the kernel API
-      and have a fully functional Linux KVM module, together with its
-      client (qemu).</p>
-    <hr /><h2><a name="Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD" href="#Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD" id="Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD">Porting OpenBSD's sysctl Hardware Sensors Framework to
-    FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mojo.ru/us/GSoC2007.FreeBSD.cnst-sensors.proposal.html" title="http://mojo.ru/us/GSoC2007.FreeBSD.cnst-sensors.proposal.html">Port OpenBSD's sysctl hw.sensors framework to FreeBSD, original proposal for GSoC2007</a></td><td>
-	    URL: <a href="http://mojo.ru/us/GSoC2007.FreeBSD.cnst-sensors.proposal.html" title="Port OpenBSD's sysctl hw.sensors framework to FreeBSD, original proposal for GSoC2007">http://mojo.ru/us/GSoC2007.FreeBSD.cnst-sensors.proposal.html</a></td></tr><tr><td><a href="http://cnst.livejournal.com/tag/GSoC2007" title="http://cnst.livejournal.com/tag/GSoC2007">cnst's GSoC2007 blog</a></td><td>
-	    URL: <a href="http://cnst.livejournal.com/tag/GSoC2007" title="cnst's GSoC2007 blog">http://cnst.livejournal.com/tag/GSoC2007</a></td></tr><tr><td><a href="http://cnst.livejournal.com/data/atom?tag=GSoC2007" title="http://cnst.livejournal.com/data/atom?tag=GSoC2007">cnst's GSoC2007 atom feed</a></td><td>
-	    URL: <a href="http://cnst.livejournal.com/data/atom?tag=GSoC2007" title="cnst's GSoC2007 atom feed">http://cnst.livejournal.com/data/atom?tag=GSoC2007</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/cnst-sensors/" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/cnst-sensors/">cnst-sensors in soc2007 in perforce</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/cnst-sensors/" title="cnst-sensors in soc2007 in perforce">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/cnst-sensors/</a></td></tr></table><p>
-	Contact:
-          Constantine A.
-
-          Murenin
-         &lt;<a href="mailto:cnst@FreeBSD.org">cnst@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:syrinx@FreeBSD.org">syrinx@FreeBSD.org</a>&gt;
-	</p>
-      <p>OpenBSD includes sysctl hw.sensors framework since 2003; since
-      2005 the frameworks supports raid drives and most known i2c
-      sensors; since 2006 the framework is redesigned with a sensor
-      device concept in mind to accommodate continued growth. Consists
-      of kernel api, sysctl(3)/sysctl(8), sensorsd(8), ntpd(8),
-      systat(1), ports/sysutils/symon and 51 drivers as of
-      2007-07-07.</p>
-
-      <p>This GSoC2007 project is to port the underpinnings of this
-      unified hardware monitoring interface to FreeBSD. Whilst it won't
-      be possible to port all of the drivers due to architecture
-      differences, we aim at porting all other parts of the framework
-      and accompanying userland utilities.</p>
-
-      <p>At this time, lm(4) at isa and some kernel api have already
-      been ported. The next big step is to complete sysctl(3) glue code
-      so that further work on porting userland utilities could be
-      accomplished. Details about sysctl are being discussed on
-      arch@.</p>
-    <h3>Open tasks:</h3><ol><li>sysctl(3) glue code</li></ol><hr /><h2><a name="Ports-Collection-infrastructure-improvements" href="#Ports-Collection-infrastructure-improvements" id="Ports-Collection-infrastructure-improvements">Ports Collection infrastructure improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borSoC2007" title="http://wiki.freebsd.org/G%C3%A1borSoC2007">G�bor's SoC 2007 wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/G%C3%A1borSoC2007" title="G�bor's SoC 2007 wiki page">http://wiki.freebsd.org/G%C3%A1borSoC2007</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Andrew
-
-          Pantyukhin
-         &lt;<a href="mailto:sat@FreeBSD.org">sat@FreeBSD.org</a>&gt;
-	</p>
-      <p>G�bor K�vesd�n is working on some
-      improvements for the Ports Collection infrastructure. This year,
-      he aimed to work on long-standing issues, which are tracked in
-      GNATS, but we have not had a volunteer for recently. With the
-      mentorship of Andrew Pantyukhin, he is also reimplementing the
-      DESTDIR support for Ports Collection in a more practical way. The
-      complete description and status of this project is available on
-      G�bor's SoC 2007 Wiki page.</p>
-    <h3>Open tasks:</h3><ol><li>Please see the Wiki page for the current status.</li></ol><hr /><h2><a name="Security-Regression-Test" href="#Security-Regression-Test" id="Security-Regression-Test">Security Regression Test</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/zhouzhouyi%5fmactest%5fsoc" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/zhouzhouyi%5fmactest%5fsoc">Perforce Repository.</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/zhouzhouyi%5fmactest%5fsoc" title="Perforce Repository.">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2007/zhouzhouyi%5fmactest%5fsoc</a></td></tr></table><p>
-	Contact:
-          Zhouyi
-
-          Zhou
-         &lt;<a href="mailto:zhouzhouyi@FreeBSD.org">zhouzhouyi@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Security Regression Test is supported by the project of Google
-      summer code 2007. The main objective of this stage is to test the
-      correctness of FreeBSD Mandatory Access Control Framework
-      including correctly passing the security label from userland to
-      kernel and non-bypassibility of Mandatory Access Control
-      Hooks.</p>
-
-      <p>Work performed in the last month:</p>
-
-      <ol>
-        <li>Constructed a pair of pseudo ethernet drivers used for
-        testing network related hooks. To avoid the packet go through
-        the lo interface, the IP address in the packet is twisted in
-        the driver.</li>
-
-        <li>Constructed a framework for logging Mandatory Access
-        Control hooks which is got called during a period of time.
-        <ul>
-          <li>In kernel, every non-null label is got externalized into
-          human readable string and recorded in a tail queue together
-          with the name of hook that got called and possible flags or
-          modes (etc. VREAD/VWRITE for mac_check_vnode_open hook).
-          There is a thread much like audit subsystem's audit_worker
-          logging the queue into a userspace file. The userland program
-          use open, ioctl and close the /dev/mactest node to trigger
-          and stop the logging. The logging file is truncated to zero
-          every time the logging mechanism is triggered.</li>
-
-          <li>In userland, a bison based parsing tool is used to parse
-          the logged file and reconstruct the record chain which will
-          be compared with testsuite supplied configuration file to
-          examine if expected hooks is got called and the
-          label/flags/modes are correct. c) The testsuite mainly
-          follows src/tools/regression/fstest, modified to adapt to
-          test Mandatory Access Control Framework and include tests for
-          signals</li>
-        </ul>
-        </li>
-      </ol>
-    <h3>Open tasks:</h3><ol><li>The code is quick and dirty. For example, a call to vn_open
-      without checking its return value which is not fault tolerance.
-      The coding style also needs modifications.</li><li>Although a test framework is completely constructed, the
-      detailed test cases still need to be written, the test cases
-      beside fstest and signal need to be add.</li><li>Testing of audit subsystem has not begin.</li><li>Other parts of Security Subsystem in FreeBSD also need
-      concern.</li></ol><hr /><h2><a name="tarfs:-A-tar-File-System" href="#tarfs:-A-tar-File-System" id="tarfs:-A-tar-File-System">tarfs: A tar File System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.googlebit.com/doku.php?id=tarfs" title="http://www.googlebit.com/doku.php?id=tarfs">TarFS Wiki</a></td><td>
-	    URL: <a href="http://www.googlebit.com/doku.php?id=tarfs" title="TarFS Wiki">http://www.googlebit.com/doku.php?id=tarfs</a></td></tr></table><p>
-	Contact:
-          Eric
-
-          Anderson
-         &lt;<a href="mailto:anderson@FreeBSD.org">anderson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Tarfs is a simple tar file system implementation for
-      FreeBSD.</p>
-
-      <p>The current goals are:</p>
-
-      <ul>
-        <li>Support all standard read-only operations</li>
-
-        <li>Support large tar files (several gb's)</li>
-
-        <li>Use minimal memory</li>
-
-        <li>Allow using tar file as a root file system</li>
-
-        <li>Fast enough to actually use</li>
-      </ul>
-
-      <p>Here's the current state of things:</p>
-
-      <ul>
-        <li>Can mount most tar files</li>
-
-        <li>Can do most operations (open,lookup,stat,readdir,etc)</li>
-
-        <li>Supports large tar files (tested up to 2GB)</li>
-
-        <li>Uses a relatively small amount of memory - proportional to
-        number of files/dirs</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>No `..' directory in root of mounted tar file system</li><li>Locking issues regarding `..' in subdirs off root of
-      fs</li><li>No block/char special device support. Needed?</li><li>Needs a directory hashing method</li><li>More testing needed.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="FreeBSD/xen" href="#FreeBSD/xen" id="FreeBSD/xen">FreeBSD/xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Rink
-
-          Springer
-         &lt;<a href="mailto:rink@FreeBSD.org">rink@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is well under way to finish Kip Macy's FreeBSD/xen port,
-      and get it into a shape which is suitable for inclusion in
-      7.0.</p>
-
-      <p>Generally, the port is stable and performs quite well. The
-      major bottleneck is the inability to work with GCC 4.2, this is
-      the last major TODO before the work can be committed.</p>
-    <h3>Open tasks:</h3><ol><li>Fix the port to correctly work with GCC 4.2.</li><li>Port the Xen drivers to newbus.</li><li>Test/fix PAE support.</li><li>Start on amd64 support.</li></ol><hr /><h2><a name="HDTV-Drivers-(ATSC)" href="#HDTV-Drivers-(ATSC)" id="HDTV-Drivers-(ATSC)">HDTV Drivers (ATSC)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21" title="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21">bktrau Perforce source repository</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21" title="bktrau Perforce source repository">http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fbktrau%2F...&amp;ignore=GO%21</a></td></tr><tr><td><a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fcxd%2F...&amp;ignore=GO%21" title="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fcxd%2F...&amp;ignore=GO%21">cxd Perforce source repository</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fcxd%2F...&amp;ignore=GO%21" title="cxd Perforce source repository">http://perforce.freebsd.org/fileSearch.cgi?FSPC=%2F%2Fdepot%2Fuser%2Fjmg%2Fcxd%2F...&amp;ignore=GO%21</a></td></tr></table><p>
-	Contact:
-          John-Mark
-
-          Gurney
-         &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>This entry was previously the Bt878 Audio Driver (aka
-      FusionHDTV 5 Lite driver) announcement, but as work expanded
-      slightly, it's a bit more generic now.</p>
-
-      <p>A few bugs in bktrau has been fixed since January. If you have
-      been running an earlier version, it is recommended to upgrade as
-      the driver could panic. The driver works with multiple cards in
-      the same machine (tested with two).</p>
-
-      <p>
-      <b>FusionHDTV 5 Lite</b>
-
-      -- Due to lack of documentation from DViCO and LG, I have copied
-      magic values from the Linux driver to get ATSC capturing
-      working.</p>
-
-      <p>
-      <b>ATI HDTV Wonder</b>
-
-      -- After years of trying to get into the ATI developer program,
-      they have finally suspended it, so no support from ATI. I have
-      started work on a driver, cxd, for the Conexant CX2388x based
-      cards. The ATI HDTV Wonder uses ATI's own demodulator, and I was
-      able to get it to tune, after cribbing from the Linux driver.
-      When capturing, I get some valid data, but not all the data. Due
-      to lack of support from ATI and linux-dvb the project has been
-      put on indefinite hold.</p>
-
-      <p>If someone has another CX2388x based card, it shouldn't be too
-      hard to take the driver and get it working with a different
-      tuner.</p>
-
-      <p>A Python module is available for both drivers/cards, along w/
-      a sample capture application using it. The module is now known to
-      work well with threads so that tuning (expensive due to i2c
-      ioctl's) can happen in another thread without causing program
-      slow down. The module is working well with a custom PVR
-      backend.</p>
-    <h3>Open tasks:</h3><ol><li>Provide support for NTSC and FM tuning.</li><li>Add support for other cards and tuners that use the Bt878
-      chip.</li><li>Add support for other cards and tuners that use the CX2388x
-      chip.</li></ol><hr /><h2><a name="Kernel-contention-reduction-using-mysql" href="#Kernel-contention-reduction-using-mysql" id="Kernel-contention-reduction-using-mysql">Kernel contention reduction using mysql</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeffr-tech.livejournal.com/" title="http://jeffr-tech.livejournal.com/">mysql benchmarks and discussion.</a></td><td>
-	    URL: <a href="http://jeffr-tech.livejournal.com/" title="mysql benchmarks and discussion.">http://jeffr-tech.livejournal.com/</a></td></tr></table><p>
-	Contact:
-          Jeff
-
-          Roberson
-         &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD developers have been using mysql as a testbed to find
-      kernel contention hotspots in the kernel. As a result of this we
-      have seen a 5x performance improvement over 6.0 on 8way machines.
-      Recent changes include finer locking in fcntl(), removing Giant
-      from flock and fcntl F_SETLK. These changes will be available in
-      7.0 and primarily improve write performance. Experimental changes
-      to select() have also been discussed on arch@ that solve
-      contention issues there however these will not be ready in the
-      7.0 timeframe.</p>
-    <hr /><h2><a name="Stack-trace-capture-in-PMCTools" href="#Stack-trace-capture-in-PMCTools" id="Stack-trace-capture-in-PMCTools">Stack trace capture in PMCTools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/PmcTools" title="http://wiki.freebsd.org/PmcTools">PMCTools Wiki page.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/PmcTools" title="PMCTools Wiki page.">http://wiki.freebsd.org/PmcTools</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>The kernel/hwpmc(4) bits of stack trace capture have been
-      implemented and are available in Perforce under path
-      '//depot/user/jkoshy/projects/pmc/...'. I'm currently enhancing
-      pmcstat(8) to extract and summarize this information. Support by
-      Google Inc. for this project is thankfully acknowledged.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/audit.html" title="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/audit.html" title="TrustedBSD Audit Page">http://www.TrustedBSD.org/audit.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Christian
-
-          Peron
-         &lt;<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <p>General cleanups in preparation for 7.0.</p>
-
-      <p>Process audit state moved to the credential to allow it to be
-      accessed lock-free in most cases, as well as allowing it to be
-      used in asynchronous contexts.</p>
-
-      <p>OpenBSM 1.0a14 has been imported, which: fixes IPv6 endian
-      issues, makes OpenBSM gcc41 warnings clean, teaches
-      audit_submit(3) about getaudit_addr(), adds zonename tokens;
-      other changes since the existing CVS 1.0a12 release previously
-      imported include man page improvements, XML printing support,
-      better audit.log.5 documentation, additional 64-bit token types,
-      and new audit event identifiers.</p>
-
-      <p>MAC checks have been added so that MAC policies can control
-      use of audit system calls.</p>
-
-      <p>Additional system call arguments are now audited.</p>
-
-      <p>Audit now provides a security.audit sysctl node in order to
-      determine if audit support is compiled in; boot-time console
-      printfs have been removed.</p>
-
-      <p>"options AUDIT" is now in the 7-CURRENT GENERIC kernel, so
-      AUDIT support will be available out of the box in 7.0 without a
-      kernel recompile. Manually enabling audit support in rc.conf will
-      still be required. With FreeBSD 7.0, AUDIT will be a fully
-      supported, rather than experimental, feature.</p>
-    <hr /><h2><a name="TrustedBSD-MAC-Framework" href="#TrustedBSD-MAC-Framework" id="TrustedBSD-MAC-Framework">TrustedBSD MAC Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/mac.html" title="http://www.TrustedBSD.org/mac.html">TrustedBSD MAC Page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/mac.html" title="TrustedBSD MAC Page">http://www.TrustedBSD.org/mac.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>Cleanup of MAC Framework API/KPI layers: mac.h is now just the
-      user and user&lt;-&gt;kernel API; mac_framework.h is the
-      kernel&lt;-&gt;MAC Framework KPI, and mac_policy.h is the MAC
-      Framework&lt;-&gt;MAC policy module KPI. Along similar lines,
-      mac_label_get() and mac_label_set() accessor functions now allow
-      policies to access label data without encoding struct label
-      binary layout into policy modules, opening the door to more
-      efficient layouts. struct label is now in mac_internal.h and used
-      only inside the MAC Framework.</p>
-
-      <p>General MAC policy cleanup, including removing no-op entry
-      points and sysctls for some sample policies. mac_test(4) has been
-      cleaned up significantly, and counters for all entry points
-      added.</p>
-
-      <p>A MAC check for UNIX domain socket connect has been added.</p>
-
-      <p>MAC checks have been added so that MAC policies can control
-      use of audit system calls.</p>
-
-      <p>MAC checks that duplicate existing privileges but add no
-      additional context have been removed (such as sysarch_ioperm,
-      kld_unload, settime, and system_nfsd) -- checks aligned with
-      privileges but that do provide additional context, such as
-      additional arguments, have been kept.</p>
-
-      <p>The Biba and LOMAC policies now implement priv(9) checks,
-      differentiating between privileges that may compromise system
-      integrity models, and those that don't.</p>
-
-      <p>The essentially unused mnt_fslabel / mnt_label distinction has
-      been eliminated by moving to a single mnt_label. No functional
-      change to any policy.</p>
-
-      <p>Several MAC-related interfaces have been modified to
-      synchronize with the naming conventions present in the version of
-      the MAC Framework adopted in Mac OS X Leopard; significant
-      further changes are in the pipeline to complete this
-      synchronization. While it will not be possible to reuse a policy
-      between the two platforms without careful thinking and
-      modification, this makes porting much easier.</p>
-    <hr /><h2><a name="USB" href="#USB" id="USB">USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO">Current USB files</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="Current USB files">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://www.turbocat.net/~hselasky/usb4bsd" title="http://www.turbocat.net/~hselasky/usb4bsd">My USB Homepage</a></td><td>
-	    URL: <a href="http://www.turbocat.net/~hselasky/usb4bsd" title="My USB Homepage">http://www.turbocat.net/~hselasky/usb4bsd</a></td></tr><tr><td><a href="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf" title="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf">Code reference for the new USB stack and USB device drivers</a></td><td>
-	    URL: <a href="http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf" title="Code reference for the new USB stack and USB device drivers">http://www.turbocat.net/~hselasky/usb4bsd/dev_new_usb.pdf</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last three months there has been several changes to
-      the USB stack. Here is a quick list of the most important
-      changes:</p>
-
-      <ol>
-        <li>FULL speed isochronous devices over HIGH speed USB Hubs are
-        now fully supported. Due to various reasons the maximum
-        isochronous bandwidth has been limited to 6MBit/s. This limit
-        is tunable.</li>
-
-        <li>There is now full support for Linux USB device drivers
-        through a Linux USB API emulation layer.</li>
-
-        <li>Various cleanups and fixes.</li>
-      </ol>
-
-      <p>Markus Brueffer is still working on the USB HID parser and
-      support. Nothing has been committed yet.</p>
-
-      <p>If you want to test the new USB stack, checkout the USB
-      perforce tree or download the SVN version of the USB driver from
-      my USB homepage. At the moment the tarballs are a little out of
-      date.</p>
-
-      <p>Ideas and comments with regard to the new USB API are welcome
-      at freebsd-usb@FreeBSD.org .</p>
-    <hr /><h2><a name="USB-update" href="#USB-update" id="USB-update">USB update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>About 18 months ago, I started to remove the compatibility
-      macros that we had in the USB stack. These macros made it very
-      hard to read the code and to diagnose problems. They represented
-      a barrier to entry for people reading and understanding the
-      stack. In addition, many of them effectively hid bugs from all
-      but the most intensive investigations of the code.</p>
-
-      <p>I've removed almost all of the macros in the client drivers,
-      and all instances of the macros in the core FreeBSD USB stack.
-      This makes the drivers more readable, and a little more robust.
-      During this process, I fixed a lot of little bugs that people had
-      been tripping over, and some that people hadn't reported. I've
-      added a boatload of new vendor and product ids to the drivers
-      from user PRs as well as from OpenBSD/NetBSD drivers.</p>
-
-      <p>I finished up this work so that the FreeBSD USB stack would be
-      more maintainable during the RELENG_7 period of time. I plan on
-      MFCing most of the changes I've made into RELENG_6 after they
-      have been shaken out in current. There was only one API changes
-      in this work, so this is doable, and makes sharing drivers
-      between 6.x and 7.x much easier. At this stage, it is unclear how
-      long RELENG_6 will be around, so I'm hoping this will make USB
-      much better in 6.3 if that's the release people choose to
-      run.</p>
-
-      <p>I've shied away from many of the more complicated changes to
-      the stack. There's work being done outside of the tree by Hans
-      Petter Selasky (hps) to make these sorts of changes. There is
-      much in his stack that's ready to be merged, and I hope to
-      integrate from that work useful bits that can be merged without
-      disruption to improve the FreeBSD USB stack.</p>
-
-      <p>I'm also looking for other FreeBSD developers that can jump in
-      and help. Nearly all of the improvements I've done by spending a
-      few hours a week sorting through the PRs for extremely low
-      hanging fruit. There's plenty of room for others to be involved
-      as well in improving FreeBSD's USB stack, as well as chances for
-      us to import the now-useful bits from the evolving hps USB stack,
-      hopefully reducing the diffs between it and the present FreeBSD
-      USB stack. In addition, I'm looking for someone to do similar
-      device ID merges from DragonFlyBSD.</p>
-
-      <p>Finally, I've embarked on a mission to try to merge all the
-      BSD's usbdevs files. There's no reason to have separate ones.
-      I've started to modify usbdevs(1) to read the
-      src/sys/dev/usb/usbdevs file and report more verbose information
-      that way. A merged usbdevs would be larger, and take up more
-      memory in a USBVERBOSE kernel, so to mitigate that effect, I'm
-      making changes to usbdevs(1).</p>
-    <h3>Open tasks:</h3><ol><li>The biggest area of concern before the 7.0 release is to
-      get the updated device lists into the manual pages. This task is
-      too big for me to take on in addition to the work I'm doing in
-      cleaning up.</li><li>We need more people that are willing to help out on the
-      'trivial' PRs that add IDs to the driver. In addition, we need
-      people to periodically sync our driver lists with DragonFlyBSD,
-      NetBSD, and OpenBSD drivers.</li><li>Merging the other BSD's usbdevs tables would be very
-      helpful.</li><li>Writing a usbdevs parser for usbdevs(1) to use.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports count is over 17,300. The PR count has been stable
-      at around 800; we have not quite cleared up the backlog that
-      showed up during the freeze to import xorg7.2.</p>
-
-      <p>There have been 4 experimental runs on the build cluster, most
-      notably resulting in some speedups for package registration. A
-      further experimental run to genericize autotools handling is in
-      progress.</p>
-
-      <p>One of the most sweeping ports commits to happen in years was
-      the upgrade of xorg from 6.9 to 7.2. This involved a complete
-      rework of the internals of the port, as X.org itself has
-      effectively pushed the responsibility for packaging to the OSes
-      that incorporate it. The idea was to be able for them to update
-      individual code (such as video drivers) without having to reroll
-      the entire distribution. This commit caused us to have the
-      longest period of preparation work, and actual tree lockdown,
-      that I am aware of. The commit continues to be controversial,
-      partly due to the fact that none of our port upgrade tools was up
-      to the task of doing the upgrade without manual intervention.</p>
-
-      <p>At the same time that xorg was upgraded, we moved the
-      installation directory from the obsolete /usr/X11R6 to our
-      default /usr/local. This further complicated the upgrade.</p>
-
-      <p>There have been new releases of the ports tinderbox code, the
-      portmaster update utility, and portupgrade.</p>
-
-      <p>GNOME was updated to 2.18.2.</p>
-
-      <p>We have added 7 new committers since the last report. We
-      appreciate all the new help. However, a few committers have
-      turned in their commit bits for safekeeping, due to lack of
-      time.</p>
-
-      <p>Unfortunately, Clement Laforet has also had to step down from
-      portmgr due to lack of time. We thank him for his help so
-      far.</p>
-
-      <p>Erwin, Kris and Mark met up at BSDCan and reviewed all the
-      portmgr-owned PRs. A large number were closed, or suspended
-      pending more work from the submitter. After closing the PRs that
-      were committed after the -exp builds, the number of portmgr owned
-      PRs came down to an all time low of 48 from around 70. We hope to
-      make further progress during the rest of the year.</p>
-    <h3>Open tasks:</h3><ol><li>gcc4.2 has been imported to the base for 7.0.
-      Unfortunately, this breaks a large number of ports. We need
-      committer and maintainer help to get these in good shape for the
-      release.</li><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have many
-      unmaintained ports. The packages on amd64 are lagging behind a
-      bit; those on sparc64 require even more work.</li></ol><hr /><h2><a name="Problem-Report-Database" href="#Problem-Report-Database" id="Problem-Report-Database">Problem Report Database</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/support.html#gnats" title="http://www.freebsd.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.freebsd.org/support.html#gnats" title="GNATS">http://www.freebsd.org/support.html#gnats</a></td></tr><tr><td><a href="http://people.freebsd.org/~bsd/prstats/" title="http://people.freebsd.org/~bsd/prstats/">PR statistics</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~bsd/prstats/" title="PR statistics">http://people.freebsd.org/~bsd/prstats/</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister_at_FreeBSD_dot_org">bugmeister_at_FreeBSD_dot_org</a>&gt;
-	</p>
-      <p>Gavin Atkinson has joined the bugbuster team via getting a
-      GNATS account on the FreeBSD cluster. He is following in the
-      footsteps of Matteo Riondato, who later graduated to a full src
-      commit bit. So far, he has helped close nearly 150 PRs, including
-      many that had become stale. Welcome!</p>
-
-      <p>Our short-term goal is to try to identify bugs that we might
-      be easily able to fix before the 6.3/7.0 simultaneous release. So
-      far, great progress has been made on ata- and usb-related
-      PRs.</p>
-
-      <p>The goal for the rest of this year is to generate more
-      developer interest in fixing bugs. To do this, we are, first,
-      trying to do more work on triaging PRs as they come in, to help
-      flag ones that seem to be valid problems (especially if they
-      include patches.) Secondly, we have started a new weekly periodic
-      posting to the freebsd-bugbusters@FreeBSD.org mailing list, which
-      is a short list of PRs that we feel are ready for committer
-      action. This posting is automatically generated from a text-file
-      list that we maintain.</p>
-
-      <p>We are continuing to try to manage our community's
-      expectations of what we can do with the incoming PRs. In
-      particular, we are trying to discourage submissions of the form
-      "I cannot get the XYZ function to work". In practice, these PRs
-      are not worked on. Instead, we are now encouraging these postings
-      to go to one of the mailing lists such as freebsd-questions@,
-      freebsd-x11@, and so forth. The idea is to emphasize GNATS as a
-      "Problem Report" method, rather than a "general FreeBSD support"
-      method. I feel that, otherwise, we were creating a false
-      expectation.</p>
-
-      <p>The overall PR count has dropped to below 5000, despite the
-      extra PRs still not cleared up from the ports freeze for the
-      xorg7.2 import. Significant progress has been made on the i386,
-      kern, and bin PRs, as well as PRs in the 'feedback' state. In
-      addition, Warner Losh has made progress on closing many of the
-      usb PRs.</p>
-    <h3>Open tasks:</h3><ol><li>Please join us on the freebsd-bugbusters@ mailing list, or
-      on #freebsd-bugbusters on EFNet, to help us triage PRs as they
-      come in and also help us to work through the backlog, and help us
-      to try to create a bugbusting "community".</li></ol><hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/snapshots/" title="http://www.FreeBSD.org/snapshots/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/snapshots/" title="">http://www.FreeBSD.org/snapshots/</a></td></tr></table><p>
-	Contact:
-          Release Engineering Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>Code freeze in preparation for FreeBSD 7.0 began on June 18th.
-      There are several large projects still being finished up as well
-      as some issues that resulted as "fallout" from the work done just
-      before the code freeze started (e.g. things resulting from the
-      GCC 4.2 import). A schedule for the 7.0 release has not been set
-      yet but the hope is that the first BETA build will be done near
-      the end of July with a "fairly normal" release cycle (a few BETA
-      builds followed by two or three RCs, each separated by around two
-      weeks).</p>
-
-      <p>We are planning to release FreeBSD 6.3 around the same time as
-      FreeBSD 7.0 is released so the release schedule for that will be
-      set at the same point we set the release cycle for 7.0, hopefully
-      late in July.</p>
-    <hr /><h2><a name="Security-Officer-and-Security-Team" href="#Security-Officer-and-Security-Team" id="Security-Officer-and-Security-Team">Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the time since the last status report, two security
-      advisories have been issued concerning problems in the base
-      system of FreeBSD; both of these problems were in "contributed"
-      code maintained outside of FreeBSD. The FreeBSD Vulnerabilities
-      and Exposures Markup Language (VuXML) document has continued to
-      be updated; since the last status report, 35 new entries have
-      been added, bringing the total up to 925.</p>
-
-      <p>In order to improve handling of security issues in the FreeBSD
-      Ports Collection a new "ports-security" team has been created to
-      include ports committers who periodically help with fixing ports
-      security issues and documenting them in the FreeBSD VuXML
-      document. Committers who wish to help with this effort can
-      contact simon@ for details.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2. The
-      respective End of Life dates of supported releases are listed on
-      the web site; it is expected that of the upcoming releases,
-      FreeBSD 6.3 will be supported for two years after release, while
-      FreeBSD 7.0 will be supported for one year after release.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org" title="http://www.freebsdfoundation.org">The FreeBSD Foundation</a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org" title="The FreeBSD Foundation">http://www.freebsdfoundation.org</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@FreeBSD.org">deb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation ended Q2 raising over $116,000. We're
-      almost half way to our goal of raising $250,000 this year! We
-      continued our mission of supporting developer communication by
-      helping FreeBSD developers attend BSDCan. We were also a sponsor
-      of BSDCan and the developer summit. We are a sponsor of
-      EuroBSDCon 2007 and are now accepting travel grant applications
-      for this conference. Foundation board members met with
-      representatives of companies that use or are thinking of using
-      FreeBSD both in the bay area and Ottawa.</p>
-
-      <p>The Foundation has negotiated a joint development agreement
-      with Google, Inc. to sponsor FreeBSD developer Joseph Koshy to
-      improve FreeBSD's HWPMC implementation, including adding
-      stacktrace support, and a donation of SMP hardware for future SMP
-      scalability work. We greatly appreciate Google's support for this
-      project, which will facilitate performance measurement and
-      optimization of both the FreeBSD operating system and
-      applications running on it.</p>
-
-      <p>To learn more about what we're doing, go to our website at
-      <a href="http://www.freebsdfoundation.org/" shape="rect">
-      http://www.FreeBSDFoundation.org/</a>
-
-      . Our July newsletter will be published soon to update you on how
-      we've been supporting the project and community worldwide.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Fine-grain-thread-locking" href="#Fine-grain-thread-locking" id="Fine-grain-thread-locking">Fine grain thread locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Jeff
-
-          Roberson
-         &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Attilio
-
-          Rao
-         &lt;<a href="mailto:attilio@FreeBSD.org">attilio@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Kris
-
-          Kennaway
-         &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-      <p>Over the past 6 months several developers undertook an effort
-      to replace the global scheduler lock with a finer-grain interface
-      modeled on the Solaris container lock approach. This
-      significantly reduces contention on higher-end multiprocessor
-      machines.</p>
-
-      <p>This patch went into 7.0-CURRENT and has proven to be very
-      stable. The last remaining bugs are in rusage and effect only
-      process time accounting statistics.</p>
-    <hr /><h2><a name="gvirstor" href="#gvirstor" id="gvirstor">gvirstor</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/gvirstor" title="http://wiki.freebsd.org/gvirstor"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/gvirstor" title="">http://wiki.freebsd.org/gvirstor</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@FreeBSD.org">ivoras@FreeBSD.org</a>&gt;
-	</p>
-      <p>Gvirstor is a GEOM class which provides virtual storage
-      capacity (something like virtual memory for storage devices).
-      It's ready to be committed to HEAD (the plan is for it to get
-      into 7.0-RELEASE).</p>
-    <h3>Open tasks:</h3><ol><li>Any interested testers are welcome!</li></ol><hr /><h2><a name="SCHED_SMP-and-SCHED_ULE" href="#SCHED_SMP-and-SCHED_ULE" id="SCHED_SMP-and-SCHED_ULE">SCHED_SMP and SCHED_ULE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeffr-tech.livejournal.com/" title="http://jeffr-tech.livejournal.com/">Benchmarks and SCHED_SMP discussion.</a></td><td>
-	    URL: <a href="http://jeffr-tech.livejournal.com/" title="Benchmarks and SCHED_SMP discussion.">http://jeffr-tech.livejournal.com/</a></td></tr></table><p>
-	Contact:
-          Jeff
-
-          Roberson
-         &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-      <p>SCHED_SMP is a fork of the ULE scheduler which makes use of
-      the new fine grain scheduler locking in 7.0-CURRENT to
-      significantly improve SMP performance on some workloads. It has
-      improved and stronger affinity, smarter CPU load balancing,
-      structural improvements and many sysctl tunables. This can be
-      considered ULE 3.0. Discussions are ongoing as to whether this
-      will go into 7.0 as SCHED_SMP or as SCHED_ULE in 7.0 or 7.1.</p>
-
-      <p>SCHED_ULE has had many bugfixes and performance improvements
-      over the 7.0 development cycle and should no longer be considered
-      unstable or experimental. On most workloads it significantly
-      outperforms SCHED_4BSD on SMP and even slightly outperforms it on
-      UP. There are some pathlogical workloads which exhibit as much as
-      a 5% performance penalty. Many thanks to Kris Kennaway and
-      current users for bug reports and performance testing.</p>
-    <hr /><h2><a name="TrustedBSD-priv(9)" href="#TrustedBSD-priv(9)" id="TrustedBSD-priv(9)">TrustedBSD priv(9)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/" title="http://www.TrustedBSD.org/">TrustedBSD Project</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/" title="TrustedBSD Project">http://www.TrustedBSD.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>Further reduction of suser(9) consumers in order to attempt to
-      remove the suser(9) KPI for 7.0. This includes resource limits,
-      System V IPC, PPP, netinet port reuse, the NFS server, and
-      netatalk. Remove unnecessary or redundant privilege checks were
-      possible. UFS-privileges that apply to other file systems have
-      been renamed to VFS privileges.</p>
-
-      <p>All suser_cred() flags and priv_check_cred() flags are no
-      longer required, as SUSER_ALLOWJAIL and SUSER_RUID use are
-      determined entirely inside kern_jail.c and kern_priv.c and
-      selected based on the privilege number, not a calling context
-      flag. All privileges are now consistently allowed or not allowed
-      in jail, and consistently use the ruid or euid. We will leave the
-      flags field there as it will likely be used for other things in
-      the future.</p>
-
-      <p>Documentation in suser(9) and priv(9) has been updated.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="10Gigabit-Network-Support" href="#10Gigabit-Network-Support" id="10Gigabit-Network-Support">10Gigabit Network Support</a></h2><p>
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@FreeBSD.org">kmacy@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Andrew
-
-          Gallatin
-         &lt;<a href="mailto:gallatin@FreeBSD.org">gallatin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Jack
-
-          Vogel
-         &lt;<a href="mailto:jfv@FreeBSD.org">jfv@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support was added for two more 10gigabit network drivers and
-      there were major advances on improving system performance over
-      10g media.</p>
-
-      <p>Kip Macy committed a new driver for the Chelsio adapters. The
-      cxgb driver supports all current 10g adapters, as well as the new
-      four-port gigabit model. The cxgb driver work was supported by
-      Chelsio.</p>
-
-      <p>Drew Gallatin made significant improvements to the Myricom 10g
-      driver mxge. With these updates the driver does line rate
-      transfers with less system overhead.</p>
-
-      <p>Neterion contributed the nxge driver to support all their
-      Xframe 10Gbe Server/Storage adapters. The initial driver import
-      was done by Sam Leffler; a switch over to vendor support will
-      happen soon.</p>
-
-      <p>Jack Vogel is preparing a driver to support the latest Intel
-      10g hardware devices. The new driver - ixgbe - will complement
-      the existing ixgb driver that supports older Intel 10g cards.</p>
-
-      <p>Kip and Drew worked with other folks on performance analysis
-      and tuning. This work improved cpu affinity and reduced overhead
-      for managing network resources. Work is also underway to define a
-      common Large Receive Offlaod (LRO) infrastructure. LRO is
-      analogous to TSO on the receive side enabling drivers to receive
-      at near line rate with normal sized frames. This common code base
-      will help replace driver-specific code.</p>
-    <hr /><h2><a name="FAST_IPSEC-Upgrade" href="#FAST_IPSEC-Upgrade" id="FAST_IPSEC-Upgrade">FAST_IPSEC Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Bjoern
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>FAST_IPSEC has now replaced Kame IPsec as the IPsec stack in
-      HEAD. This will be part of the 7.0 release. The merge happened in
-      early July with George handling the kernel bits and Bjoern
-      handling user space.</p>
-
-      <p>The kernel option IPSEC is now the ONLY option for IPsec
-      support in the FreeBSD kernel.</p>
-    <h3>Open tasks:</h3><ol><li>Test test test!!!!</li></ol><hr /><h2><a name="FreeBSD-and-Wake-On-Lan" href="#FreeBSD-and-Wake-On-Lan" id="FreeBSD-and-Wake-On-Lan">FreeBSD and Wake On Lan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://stsp.name/wol/" title="http://stsp.name/wol/"></a></td><td>
-	    URL: <a href="http://stsp.name/wol/" title="">http://stsp.name/wol/</a></td></tr><tr><td><a href="http://stsp.name/wol/README.txt" title="http://stsp.name/wol/README.txt"></a></td><td>
-	    URL: <a href="http://stsp.name/wol/README.txt" title="">http://stsp.name/wol/README.txt</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=83807&amp;cat=kern" title="http://www.freebsd.org/cgi/query-pr.cgi?pr=83807&amp;cat=kern"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=83807&amp;cat=kern" title="">http://www.freebsd.org/cgi/query-pr.cgi?pr=83807&amp;cat=kern</a></td></tr></table><p>
-	Contact:
-          Stefan
-
-          Sperling
-         &lt;<a href="mailto:stsp@stsp.name">stsp@stsp.name</a>&gt;
-	</p>
-      <p>I have been working on making wake on lan (WOL) work with
-      FreeBSD. Contrary to popular believe OS support is required for
-      WOL to work properly. In particular network card drivers need to
-      configure network cards for WOL during system shutdown, else the
-      cards won't wake up. WOL is _not_ just a BIOS issue.</p>
-
-      <p>This is work in progress. Currently the following
-      cards/chipsets are supported:</p>
-
-      <ul>
-        <li>NatSemi DP83815 (if_sis)</li>
-
-        <li>Via Rhine (if_vr, only VT6102 and up chips support
-        WOL)</li>
-
-        <li>Nvidia nForce (if_nve,
-        <b>needs testing</b>
-
-        )</li>
-
-        <li>3Com Etherlink XL and Fast Etherlink XL (if_xl,
-        <b>needs testing</b>
-
-        , only 3c905B type adapters support WOL)</li>
-      </ul>
-
-      <p>I would be glad to get more feedback on my patch. I can add
-      support for more chipsets but I need testers for hardware I don't
-      have. I would appreciate access to data sheets for any NIC
-      chipsets that are supported by FreeBSD and have WOL support.</p>
-
-      <p>I would especially appreciate technical feedback on the patch,
-      preferably by a committer who is willing to nitpick the patch to
-      make it ready for inclusion in -CURRENT. I currently maintain the
-      patch against RELENG_6_2 for my own use but I would port it to
-      -CURRENT for inclusion.</p>
-    <hr /><h2><a name="Multi-link-PPP-daemon-(MPD)" href="#Multi-link-PPP-daemon-(MPD)" id="Multi-link-PPP-daemon-(MPD)">Multi-link PPP daemon (MPD)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sourceforge.net/projects/mpd/" title="http://sourceforge.net/projects/mpd/">Project home</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/mpd/" title="Project home">http://sourceforge.net/projects/mpd/</a></td></tr><tr><td><a href="http://mpd.sourceforge.net/doc/mpd5.html" title="http://mpd.sourceforge.net/doc/mpd5.html">ChangeLog</a></td><td>
-	    URL: <a href="http://mpd.sourceforge.net/doc/mpd5.html" title="ChangeLog">http://mpd.sourceforge.net/doc/mpd5.html</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Motin
-         &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>Mpd-4.2 has been released. It includes many new features,
-      performance improvements and fixes.</p>
-
-      <p>The most significant and unique new feature is a link repeater
-      functionality. It allows mpd to accept incoming connection of any
-      supported type and forward it out as same or different type
-      outgoing connection. As example, this functionality allows mpd to
-      implement real LAC with accepting incoming PPPoE connection from
-      client and forwarding it using L2TP tunnel to LNS. All other
-      software L2TP implementations I know is only a LAC emulators
-      without real incoming calls forwarding abilities.</p>
-
-      <p>Also mpd-4.2 presents:</p>
-
-      <ul>
-        <li>PPTP listening on multiple different IPs,</li>
-
-        <li>L2TP tunnel authentication with shared secret,</li>
-
-        <li>fast traffic filtering, shaping and rate-limiting using
-        ng_bpf and ng_car,</li>
-
-        <li>new 'ext-auth' auth backend as full-featured local
-        alternative to 'radius-auth',</li>
-
-        <li>NetFlow generation for both incoming and outgoing packets
-        same time.</li>
-      </ul>
-
-      <p>Replacing external ifconfig and route calls with their
-      internal implementations and other optimizations in 4.2 gave
-      significant performance boost in session management. Newly
-      implemented overload protection mechanism partially drops
-      incoming connection requests for periods of critical load by
-      monitoring daemon's internal message queue. As result, simple
-      2GHz P4 system is now able to accept, authenticate and completely
-      process spike of 1000 concurrent PPPoE connections in just a 30
-      seconds.</p>
-    <h3>Open tasks:</h3><ol><li>Implement dynamic link/bundle creation.</li><li>Auth proxying support in repeater mode. It is required for
-      some LAC/PAC and Tunnel Switching Aggregator (TSA) setups.</li><li>Remove static phys - link - bundle and phys - repeater
-      relations. Implement ability to differentiate incoming
-      connections processing depending on user login, domain and/or
-      other parameters.</li></ol><hr /><h2><a name="Multiprocessor-Network-Stack" href="#Multiprocessor-Network-Stack" id="Multiprocessor-Network-Stack">Multiprocessor Network Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/netperf/" title="http://www.FreeBSD.org/projects/netperf/">Netperf Project Page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/netperf/" title="Netperf Project Page">http://www.FreeBSD.org/projects/netperf/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:net@FreeBSD.org">net@FreeBSD.org</a>&gt;
-	</p>
-      <p>The custom file descriptor array lock has been replaced with
-      an optimized sx lock, resulting in 2x-4x improvement in MySQL
-      transaction rates on 8-core MySQL benchmarks. This improvement is
-      due to moving to shared locking for frequent fd lookup
-      operations, as well as significant optimization of the case where
-      the filedesc lock is highly contended (as occurs in the threaded
-      MySQL server performing constant socket I/O).</p>
-
-      <p>The custom socket buffer I/O serialization lock (sblock),
-      previously created by interlocking SB_WANT and SB_LOCK flags with
-      the socket buffer mutex, has been replaced with an optimized sx
-      lock, leading to a 10% performance improvement in MySQL and
-      PostgreSQL benchmarks on 8-core systems. As part of this change,
-      sx locks now have interruptible sleep primitives to allow the
-      SB_NOINTR flag to work properly.</p>
-
-      <p>These changes also correct a long-standing bug in socket
-      buffer lock contention and SB_NOWAIT reported by Isilon; a
-      simpler patch has been merged to 6.x to fix this bug without
-      merging loocking changes.</p>
-
-      <p>TCP debugging is now properly synchronized using a new
-      tcp_debug_mtx.</p>
-
-      <p>UMA allocation counters are now used for pipes rather than
-      custom atomic counters, resulting in lowered overhead for pipe
-      allocation and free.</p>
-
-      <p>Significant code cleanup, commenting, and in some cases
-      MFC'ing, has taken place with respect to the network stack and
-      synchronization. Additional DDB debugging commands for sockets of
-      various sorts have been added, allowing listing of socket state
-      from DDB without the use of GDB.</p>
-
-      <p>Certain non-MPSAFE subsystems have been removed or will be
-      removed from FreeBSD 7.0, including IPX over IP tunneling (not
-      general IPX/SPX support, just the tunneling over IP), KAME IPSEC
-      (FAST_IPSEC is MPSAFE and now now supports IPv6), i4b, netatm
-      (two other ATM stacks are still present), and ng_h4. Some of
-      these features will be reintroduced in FreeBSD 7.1, but by
-      removing them now, we are able to remove the NET_NEEDS_GIANT
-      compatibility infrastructure that significant complicates and
-      obfuscates the socket and network stack code.</p>
-
-      <p>Other measurement and optimization projects continue; however,
-      the 7.0 locking/synchronization work for the network stack is
-      essentially complete.</p>
-    <h3>Open tasks:</h3><ol><li>New work to parallelize the netisr thread (netisr2) as well
-      as distribute UDP and TCP processing over multiple CPUs by
-      connection, rather than just by input source as in 7.0, was
-      presented at BSDCan. This work will be targeted at the 8-CURRENT
-      branch.</li><li>Complete netatm and NET_NEEDS_GIANT removal for 7.0.</li><li>Complete MPSAFE locking of mld6 and nd6 IPv6 subsystems,
-      which currently run under a global lock.</li></ol><hr /><h2><a name="Network-Stack-Virtualization" href="#Network-Stack-Virtualization" id="Network-Stack-Virtualization">Network Stack Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://imunes.tel.fer.hr/virtnet/" title="http://imunes.tel.fer.hr/virtnet/"></a></td><td>
-	    URL: <a href="http://imunes.tel.fer.hr/virtnet/" title="">http://imunes.tel.fer.hr/virtnet/</a></td></tr></table><p>
-	Contact:
-          Marko
-
-          Zec
-         &lt;<a href="mailto:zec@fer.hr">zec@fer.hr</a>&gt;
-	</p>
-      <p>The network stack virtualization project aims at extending the
-      FreeBSD kernel to maintain multiple independent instances of
-      networking state. This will allow for complete networking
-      independence between jails on a system, including giving each
-      jail its own firewall, virtual network interfaces, rate limiting,
-      routing tables, and IPSEC configuration.</p>
-
-      <p>I believe that the prototype, which is kept in sync with
-      FreeBSD -CURRENT, is now sufficiently stable for testing. It
-      virtualizes the basic INET and INET6 kernel structures and
-      subsystems, including IPFW and PF firewalls, and more. In the
-      next month I plan to have the IPSEC code fully virtualized, and
-      refine and document the management APIs. The short-term goal is
-      to deliver production-grade kernel support for virtualized
-      networking for FreeBSD 7.0-RELEASE (as a snap-in kernel
-      replacement), while continuing to keep the code in sync with
-      -CURRENT for possible merging at a later date.</p>
-    <hr /><h2><a name="Wireless-Networking" href="#Wireless-Networking" id="Wireless-Networking">Wireless Networking</a></h2><p>
-	Contact:
-          Sam
-
-          Leffler
-         &lt;<a href="mailto:sam@FreeBSD.org">sam@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
-	</p>
-      <p>A major update of the 802.11 wireless support was committed.
-      Changes include advanced station mode facilities such as
-      background scanning and roaming, and support for 802.11n devices.
-      In addition parts of the Atheros' SuperG protocol extensions were
-      added so that wireless clients that communicate with
-      Atheros-based access points can operate more effectively. The
-      changes to the infrastructure are also important because they
-      simplify future distribution of Virtual AP (VAP) support.</p>
-
-      <p>This work represents the effort of many people including Kip
-      Macy, Andrew Thompson, Sepherosa Ziehau, Max Laier, and Kevin Lo.
-      Getting these changes into the tree now ensures they will be
-      present for the lifetime of the 7.x branch.</p>
-
-      <p>The scanning and SuperG work were supported by Atheros. The
-      802.11n-related work was supported by Marvell.</p>
-    <h3>Open tasks:</h3><ol><li>Please test your wireless networking, especially during the
-      7.0 BETA and RC period.</li></ol><hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="FreeBSD-and-Coverity-Prevent" href="#FreeBSD-and-Coverity-Prevent" id="FreeBSD-and-Coverity-Prevent">FreeBSD and Coverity Prevent</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          David
-
-          Maxwell
-         &lt;<a href="mailto:dmaxwell@coverity.com">dmaxwell@coverity.com</a>&gt;
-	</p>
-      <p>FreeBSD's static analysis scans have been updated with a
-      recent version of Coverity Prevent. Coverity is providing
-      additional advice on configuration of the analysis to maximize
-      the benefit from the tools.</p>
-
-      <p>At BSDCan2007, Coverity provided FreeBSD with a license for an
-      additional analysis tool called Extend, which allows writing
-      custom FreeBSD specific code checkers. David Maxwell presented
-      training material for interested FreeBSD developers. Some
-      applications of custom checkers have been considered, and more
-      results will be forthcoming as they are implemented and
-      tested.</p>
-    <hr /><h2><a name="FreeSBIE" href="#FreeSBIE" id="FreeSBIE">FreeSBIE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freesbie.org" title="http://www.freesbie.org">FreeSBIE Website</a></td><td>
-	    URL: <a href="http://www.freesbie.org" title="FreeSBIE Website">http://www.freesbie.org</a></td></tr><tr><td><a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="http://liste.gufi.org/mailman/listinfo/freesbie">Freesbie ML Subscription</a></td><td>
-	    URL: <a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="Freesbie ML Subscription">http://liste.gufi.org/mailman/listinfo/freesbie</a></td></tr></table><p>
-	Contact:
-          Matteo
-
-          Riondato
-         &lt;<a href="mailto:matteo@FreeBSD.org">matteo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeSBIE
-
-          Staff
-         &lt;<a href="mailto:staff@freesbie.org">staff@freesbie.org</a>&gt;
-	<br />
-	Contact:
-          FreeSBIE
-
-          ML
-         &lt;<a href="mailto:freesbie@gufi.org">freesbie@gufi.org</a>&gt;
-	</p>
-      <p>After the success of FreeSBIE-2.0.1-RELEASE, development slew
-      down a bit, but we have a big task for the summer: enable unionfs
-      again and trying the new efficient memory filesystem, tmpfs.</p>
-
-      <p>For all new ISO images we will be following RELENG_7, with the
-      hope to release a stable image once 7.0-RELEASE have been
-      released.</p>
-    <h3>Open tasks:</h3><ol><li>Build and test an ISO image with
-      FreeSBIE+unionfs+tmpfs.</li></ol><hr /><h2><a name="OpenBSD-packet-filter---pf" href="#OpenBSD-packet-filter---pf" id="OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Max
-
-          Laier
-         &lt;<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>&gt;
-	</p>
-      <p>pf in HEAD (soon to be FreeBSD 7.0) has been updated to
-      OpenBSD 4.1 bringing in a couple of new features:</p>
-
-      <ul>
-        <li>ftp-proxy has been rewritten, and a tftp version,
-        tftp-proxy, has been added</li>
-
-        <li>pf(4) now supports Unicast Reverse Path Forwarding (uRPF)
-        checks for simplified ingress filtering</li>
-
-        <li>The pflog(4) interface is now clonable. pf(4) can log to
-        multiple pflog interfaces now, each rule can specify which
-        pflog interface to log to</li>
-
-        <li>pflogd(8) can now be told which pflog interface to work
-        with</li>
-
-        <li>pfctl(8) can now expire table entries</li>
-
-        <li>keep state is now the default for pf.conf(5) rules, as is
-        the flags S/SA option on TCP connections. no state and flags
-        any can be used to disable stateful filtering or TCP flags
-        checking</li>
-
-        <li>The pfctl(8) ruleset optimiser can be enabled in
-        pf.conf(5)</li>
-
-        <li>pf(4) anchors can now be loaded inline in the main
-        pf.conf(5) and can be printed recursively</li>
-
-        <li>Allow pf(4) rules inside anchors to have their counters
-        reset, and make counter read &amp; reset an atomic
-        operation</li>
-      </ul>
-
-      <p>Some patches that went into OpenBSD after 4.1 and improve
-      performance significantly will be merged later.</p>
-
-      <p>Work to support pf and netgraph interaction is underway and
-      will be imported after 7.0. As all required ABI changes have been
-      made during the update, we will be able to MFC this work for 7.1
-      later on.</p>
-    <hr /><h2><a name="PC-BSD" href="#PC-BSD" id="PC-BSD">PC-BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pcbsd.org/" title="http://www.pcbsd.org/">PC-BSD Homepage</a></td><td>
-	    URL: <a href="http://www.pcbsd.org/" title="PC-BSD Homepage">http://www.pcbsd.org/</a></td></tr></table><p>
-	Contact:
-          Kris
-
-          Moore
-         &lt;<a href="mailto:kris@pcbsd.com">kris@pcbsd.com</a>&gt;
-	</p>
-      <p>The last major updates are currently being made to PC-BSD 1.4,
-      which will include KDE 3.5.7, Beryl, Flash, Intel Wireless,
-      Nvidia Drivers and more! This release will also include new
-      utilities to make running PC-BSD on the desktop easier than ever,
-      including:</p>
-
-      <ul>
-        <li>Network Manager with WIFI Support</li>
-
-        <li>Add / Remove Components</li>
-
-        <li>Firewall Manager for PF</li>
-
-        <li>Xorg Display setup wizard</li>
-      </ul>
-
-      <p>Once any final major issues are resolved, we will be issuing a
-      public beta of PC-BSD 1.4 to ensure compatibility across a
-      variety of platforms.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="EuroBSDcon-2007" href="#EuroBSDcon-2007" id="EuroBSDcon-2007">EuroBSDcon 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2007.EuroBSDCon.org/" title="http://2007.EuroBSDCon.org/"></a></td><td>
-	    URL: <a href="http://2007.EuroBSDCon.org/" title="">http://2007.EuroBSDCon.org/</a></td></tr></table><p>
-	Contact:
-          EuroBSDCon 2007 Organizing Committee
-         &lt;<a href="mailto:info@EuroBSDCon.dk">info@EuroBSDCon.dk</a>&gt;
-	</p>
-      <p>The sixth EuroBSDCon will take place at Symbion in Copenhagen,
-      Denmark on Friday the 14th and Saturday 15th of September
-      2007.</p>
-
-      <p>The programme is ready and online at the webpage. Registration
-      is open. Details about tutorials and Legoland trip are ready too.
-
-      <br clear="none" />
-
-      The keynote will be John Hartman: Real men's pipes</p>
-
-      <p>If you share a room with friends at the hostel, then lodging
-      is really inexpensive, and the lounge has high speed Internet
-      access. Staying at the hostel is of course optional, and the area
-      has several hotels.</p>
-
-      <p>KD85.com and O'Reilly will each have a booth at the
-      conference.</p>
-
-      <p>We are still looking for more sponsors.</p>
-
-      <p>A public IRC channel #eurobsdcon on EFnet has been created for
-      discussion and questions about the conference.</p>
-    <hr /><h2><a name="EuroBSDCon-2007-Developer-Summit" href="#EuroBSDCon-2007-Developer-Summit" id="EuroBSDCon-2007-Developer-Summit">EuroBSDCon 2007 Developer Summit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/200709DevSummit" title="http://wiki.freebsd.org/200709DevSummit"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/200709DevSummit" title="">http://wiki.freebsd.org/200709DevSummit</a></td></tr></table><p>
-	Contact:
-          Poul-Henning
-
-          Kamp
-         &lt;<a href="mailto:phk@FreeBSD.org">phk@FreeBSD.org</a>&gt;
-	</p>
-      <p>The next developer summit will be different from the previous
-      ones.</p>
-
-      <p>Very different.</p>
-
-      <p>Gone are the auditorium style seating, beamers, endless
-      presentations and soggy sandwiches.</p>
-
-      <p>Instead we head out to an old village school in the
-      beautiful Danish countryside, we hang around all over the place,
-      sleep in the old science room, cook our own food and hack the
-      living daylights out of anything we care for.</p>
-
-      <p>September 17th and 18th, right after EuroBSDcon2007 in
-      Copenhagen. (Well, right after the optional trip to
-      legoland...)</p>
-
-      <p>Be there!</p>
-
-      <p>PS: Yes, it's not uncivilized, there is a full speed ADSL and
-      WLAN.</p>
-    <hr /><h2><a name="libarchive/bsdtar" href="#libarchive/bsdtar" id="libarchive/bsdtar">libarchive/bsdtar</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~kientzle/libarchive/" title="http://people.freebsd.org/~kientzle/libarchive/">Project page</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~kientzle/libarchive/" title="Project page">http://people.freebsd.org/~kientzle/libarchive/</a></td></tr></table><p>
-	Contact:
-          Tim
-
-          Kientzle
-         &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Colin
-
-          Percival
-         &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>Both libarchive 2 and bsdtar 2 are now in -CURRENT and will be
-      in 7.0. Libarchive 1.9 and bsdtar 1.9 should be in 6-STABLE in
-      time for 6.3.</p>
-
-      <p>libarchive 2 is much faster writing to disk than libarchive 1.
-      It also supports new formats, has several minor API/ABI
-      corrections, is more portable, and has many fewer bugs. Of
-      special note is "libarchive_test", a new program that exercises
-      much of the libarchive functionality; anyone interested in
-      working on libarchive should become familiar with this test
-      suite. bsdtar 2 is less ambitious, but does have a number of bug
-      fixes and takes advantage of several new features in libarchive
-      2.</p>
-
-      <p>libarchive 1.9 is identical to libarchive 2 except it
-      maintains the old API/ABI. Similarly, bsdtar 1.9 is nearly
-      identical to bsdtar 2, lacking only a few features that would
-      prevent it from being used with existing libarchive 1
-      libraries.</p>
-    <h3>Open tasks:</h3><ol><li>Tim Kientzle has started work on a libarchive-based cpio
-      implementation that should be ready for inclusion with FreeBSD
-      8.</li><li>Volunteer needed: We want a libarchive-based pax to replace
-      our out-of-date pax implementation.</li><li>Volunteer needed: pkg_add should use libarchive instead of
-      forking an external tar; this could eventually make it much
-      faster.</li><li>Volunteer(s) needed: libarchive should write more cpio
-      variants (easy); libarchive should read and write mtree format
-      (not difficult); libarchive should write GNUtar 1.0 format sparse
-      tar entries (tricky); bsdtar should support
-      --metadata=&lt;archive&gt; to read names and properties from one
-      archive, with data from disk, to create a new archive (mtree
-      support in libarchive would make this very useful); bsdtar should
-      preserve sparseness when creating archives.</li></ol><hr /><h2><a name="The-Hungarian-Documentation-Project" href="#The-Hungarian-Documentation-Project" id="The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/hu/docproj/hungarian.html" title="http://www.freebsd.org/hu/docproj/hungarian.html">Info for volunteers</a></td><td>
-	    URL: <a href="http://www.freebsd.org/hu/docproj/hungarian.html" title="Info for volunteers">http://www.freebsd.org/hu/docproj/hungarian.html</a></td></tr><tr><td><a href="http://www.freebsd.org/hu/" title="http://www.freebsd.org/hu/">Hungarian Webpages</a></td><td>
-	    URL: <a href="http://www.freebsd.org/hu/" title="Hungarian Webpages">http://www.freebsd.org/hu/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/linux-comparison/" title="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/linux-comparison/">Latest translation</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/linux-comparison/" title="Latest translation">http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/linux-comparison/</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have added one translated article since the last status
-      report about this project. The infrastructure is ready to support
-      localized articles and books as well, we just lack of human
-      resource. New volunteers are highly welcome! Please see the link
-      below and contact G�bor if you are interested.</p>
-    <h3>Open tasks:</h3><ol><li>Translate more articles and books.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2007-07-2007-10.html b/website/content/en/status/report-2007-07-2007-10.html
deleted file mode 100644
index dfff2bab56..0000000000
--- a/website/content/en/status/report-2007-07-2007-10.html
+++ /dev/null
@@ -1,809 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between July and
-    October 2007. The sixth EuroBSDCon was held in Denmark in September.
-    The Google Summer of Code project came to a close and lots of
-    participants are working getting their code merged back into
-    FreeBSD.</p><p>The bugs in the FreeBSD HEAD branch are being shaked out and it is
-    being prepared for the FreeBSD 7 branching. If your are curious about
-    what's new in FreeBSD 7.0 we suggest reading Ivan Voras' excellent
-    summary
-    <a href="http://ivoras.sharanet.org/freebsd/freebsd7.html" shape="rect">here</a>
-
-    .</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Summer-of-Code">Summer of Code</a></li><li><a href="#finstall">finstall</a></li><li><a href="#FreeBSD-update-Front-End">FreeBSD-update Front End</a></li><li><a href="#gvirstor">gvirstor</a></li><li><a href="#MTund---Magic-Tunnel-Daemon">MTund - Magic Tunnel Daemon</a></li><li><a href="#Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD">Porting OpenBSD's sysctl Hardware Sensors Framework to
-    FreeBSD</a></li><li><a href="#Ports-Collection-infrastructure-improvements">Ports Collection infrastructure improvements</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Apple's-MacBook-on-FreeBSD">Apple's MacBook on FreeBSD</a></li><li><a href="#Multi-link-PPP-daemon-(MPD)-5.x">Multi-link PPP daemon (MPD) 5.x</a></li><li><a href="#Multicast-DNS">Multicast DNS</a></li><li><a href="#Porting-Linux-KVM-to-FreeBSD">Porting Linux KVM to FreeBSD</a></li><li><a href="#USB">USB</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD.org-Admins-Report">FreeBSD.org Admins Report</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Network-Stack-Virtualization">Network Stack Virtualization</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#PC-BSD-Handbook">PC-BSD Handbook</a></li><li><a href="#The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></li><li><a href="#The-Spanish-Documentation-Project">The Spanish Documentation Project</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#EuroBSDcon-2007">EuroBSDcon 2007</a></li><li><a href="#GNATS-graphs">GNATS graphs</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="finstall" href="#finstall" id="finstall">finstall</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/finstall" title="http://wiki.freebsd.org/finstall"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/finstall" title="">http://wiki.freebsd.org/finstall</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@freebsd.org">ivoras@freebsd.org</a>&gt;
-	</p>
-      <p>The "finstall" project is about the new graphical installer for
-      FreeBSD. The basic frameworks (both client-side and server-side)
-      are done during the SoC 2007 and it's ready for major new features
-      to be implemented. This project should yield an usable installer
-      for 7.0-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>- There are several patches needed for finstall's operation
-      that are still waiting on re@'s approval (unionfs, pwd, kbdmap).
-      Finstall will be late or unusable until these patches are
-      committed.</li><li>- After the patches are committed, there are several exciting
-      features to be implemented, among others ZFS and GEOM RAID
-      support.</li></ol><hr /><h2><a name="FreeBSD-update-Front-End" href="#FreeBSD-update-Front-End" id="FreeBSD-update-Front-End">FreeBSD-update Front End</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://developer.berlios.de/projects/facund/" title="http://developer.berlios.de/projects/facund/"></a></td><td>
-	    URL: <a href="http://developer.berlios.de/projects/facund/" title="">http://developer.berlios.de/projects/facund/</a></td></tr></table><p>
-	Contact:
-          Andrew
-
-          Turner
-         &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>The freebsd-update front end is able to wait for freebsd-update
-      to download a new set of patches to apply. It can then install and
-      rollback the patches on either the local computer or over a SSH
-      tunnel.</p>
-
-      <p>Since the end of the Summer of Code work has moved to BerliOS.
-      The focus has been on writing tests for the front end, back end and
-      communication library. The library has had tests written for most
-      of it while the front and back ends have none.</p>
-    <h3>Open tasks:</h3><ol><li>Write more tests.</li></ol><hr /><h2><a name="gvirstor" href="#gvirstor" id="gvirstor">gvirstor</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/gvirstor" title="http://wiki.freebsd.org/gvirstor"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/gvirstor" title="">http://wiki.freebsd.org/gvirstor</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@freebsd.org">ivoras@freebsd.org</a>&gt;
-	</p>
-      <p>GEOM_VIRSTOR (virtual disk space / over-commit GEOM class) has
-      been committed to 7-CURRENT and will ship in 7.0-RELEASE. Thanks to
-      Pawel Jakub Dawidek and others who have made this possible.</p>
-    <h3>Open tasks:</h3><ol><li>It needs wider exposure and testing.</li></ol><hr /><h2><a name="MTund---Magic-Tunnel-Daemon" href="#MTund---Magic-Tunnel-Daemon" id="MTund---Magic-Tunnel-Daemon">MTund - Magic Tunnel Daemon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/MTund" title="http://wiki.freebsd.org/MTund">mtund Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/MTund" title="mtund Wiki Page">http://wiki.freebsd.org/MTund</a></td></tr><tr><td><a href="http://www.inf.ethz.ch/personal/mharvan/docs/eurobsdcon.pdf" title="http://www.inf.ethz.ch/personal/mharvan/docs/eurobsdcon.pdf">MTund Poster</a></td><td>
-	    URL: <a href="http://www.inf.ethz.ch/personal/mharvan/docs/eurobsdcon.pdf" title="MTund Poster">http://www.inf.ethz.ch/personal/mharvan/docs/eurobsdcon.pdf</a></td></tr></table><p>
-	Contact:
-          Matus
-
-          Harvan
-         &lt;<a href="mailto:mharvan@FreeBSD.org">mharvan@FreeBSD.org</a>&gt;
-	</p>
-      <p>IP can easily be tunneled over a plethora of network protocols
-      at various layers, such as IP, ICMP, UDP, TCP, DNS, HTTP, SSH.
-      While a direct connection may not always be possible due to a
-      firewall, the IP packets could be encapsulated as payload in other
-      protocols, which would get through. However, each such
-      encapsulation requires the setup of a different program and the
-      user has to manually probe different encapsulations to find out
-      which of them works in a given environment.</p>
-
-      <p>MTund is a tunneling daemon using run-time loadable plugins for
-      the different encapsulations. It automagically selects the best
-      encapsulation in each environment and can fail over to another
-      encapsulation. Several plugins have been implemented and the daemon
-      supports multiple concurrent clients.</p>
-
-      <p>Note that the project originally started under the name of Super
-      Tunnel Daemon, but was later renamed to Magic Tunnel Daemon
-      (MTund).</p>
-    <h3>Open tasks:</h3><ol><li>Config file format and parser.</li><li>More plugins (http, ssh, ...).</li></ol><hr /><h2><a name="Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD" href="#Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD" id="Porting-OpenBSD's-sysctl-Hardware-Sensors-Framework-to-FreeBSD">Porting OpenBSD's sysctl Hardware Sensors Framework to
-    FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/GSoC2007/cnst-sensors" title="http://wiki.freebsd.org/GSoC2007/cnst-sensors">Port OpenBSD's sysctl hw.sensors framework to FreeBSD, a Google Summer of Code 2007 project</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/GSoC2007/cnst-sensors" title="Port OpenBSD's sysctl hw.sensors framework to FreeBSD, a Google Summer of Code 2007 project">http://wiki.freebsd.org/GSoC2007/cnst-sensors</a></td></tr><tr><td><a href="http://cnst.livejournal.com/tag/GSoC2007" title="http://cnst.livejournal.com/tag/GSoC2007">cnst's GSoC2007 blog</a></td><td>
-	    URL: <a href="http://cnst.livejournal.com/tag/GSoC2007" title="cnst's GSoC2007 blog">http://cnst.livejournal.com/tag/GSoC2007</a></td></tr><tr><td><a href="http://cnst.livejournal.com/data/atom?tag=GSoC2007" title="http://cnst.livejournal.com/data/atom?tag=GSoC2007">cnst's GSoC2007 atom feed</a></td><td>
-	    URL: <a href="http://cnst.livejournal.com/data/atom?tag=GSoC2007" title="cnst's GSoC2007 atom feed">http://cnst.livejournal.com/data/atom?tag=GSoC2007</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/021722.html" title="http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/021722.html">Project completion announcement from 2007-09-13</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/021722.html" title="Project completion announcement from 2007-09-13">http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/021722.html</a></td></tr><tr><td><a href="http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/?ac=83" title="http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/?ac=83"></a></td><td>
-	    URL: <a href="http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/?ac=83" title="">http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/?ac=83</a></td></tr></table><p>
-	Contact:
-          Constantine A.
-
-          Murenin
-         &lt;<a href="mailto:cnst@FreeBSD.org">cnst@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Shteryana
-
-          Shopova
-         &lt;<a href="mailto:syrinx@FreeBSD.org">syrinx@FreeBSD.org</a>&gt;
-	</p>
-      <p>The
-      <strong>GSoC2007/cnst-sensors</strong>
-
-      project was about porting the
-      <em>sysctl hw.sensors</em>
-
-      framework from OpenBSD to FreeBSD. The project was
-      <a href="http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/021722.html" shape="rect">
-      successfully completed</a>,
-
-      <a href="http://leaf.dragonflybsd.org/mailarchive/commits/2007-10/msg00015.html" shape="rect">
-		committed into DragonFly BSD</a>, and is now pending final review and integration
-		into the FreeBSD's CVS tree (subject to the tree being unfrozen).</p>
-
-  <p>The <em>sensors framework</em> provides a unified interface for
-		storing, registering and accessing information about hardware
-		monitoring sensors. Sensor types include, but are not limited to,
-		temperature, voltage, fan RPM, time offset and logical drive
-		status. In the OpenBSD base system, the framework spans
-		<em>sensor_attach(9)</em>, <em>sysctl(3)</em>, <em>sysctl(8)</em>,
-		<em>systat(1)</em>, <em>sensorsd(8)</em>, <em>ntpd(8)</em> and
-		more than 50 drivers, ranging from I2C temperature sensors and
-      Super I/O hardware monitors to IPMI and RAID controllers. Several
-      third-party tools are also available, for example, a plug-in for
-      Nagios and ports/sysutils/symon.</p>
-
-      <p>As a part of this Google Summer of Code project, all core
-      components of the framework were ported, including sysctl, systat
-      and sensorsd. Some drivers for the most popular Super I/O Hardware
-		Monitors were ported, too: <em>it(4)</em>, supporting most
-		contemporary ITE Tech Super I/O, and <em>lm(4)</em>, supporting
-		most contemporary Winbond Super I/O. Moreover, some existing
-		FreeBSD drivers were converted to utilise the framework, for
-		example, <em>coretemp(4)</em>.</p>
-    <h3>Open tasks:</h3><ol><li>Final Review and Commit</li></ol><hr /><h2><a name="Ports-Collection-infrastructure-improvements" href="#Ports-Collection-infrastructure-improvements" id="Ports-Collection-infrastructure-improvements">Ports Collection infrastructure improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borSoC2007" title="http://wiki.freebsd.org/G%C3%A1borSoC2007">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/G%C3%A1borSoC2007" title="Wiki page">http://wiki.freebsd.org/G%C3%A1borSoC2007</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The two most important parts of this Summer of Code projects
-      have been accomplished.</p>
-
-      <p>The DESTDIR support for the Ports Collection has been rewritten
-      to use a chrooted install. Now it is much more lightweight and
-      easier to understand, but it works well for the most common cases,
-      where it is supposed to be useful.</p>
-
-      <p>The Perl parts of the Ports Collection infrastructure have been
-      extracted into an own module. At the same time, a new version
-      handling has been invented. You can find more info on the Wiki.</p>
-    <hr /><h2><a name="Summer-of-Code" href="#Summer-of-Code" id="Summer-of-Code">Summer of Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/summerofcode-2007.html" title="http://www.FreeBSD.org/projects/summerofcode-2007.html">Official FreeBSD Summer of Code 2007 Final Status Update</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/summerofcode-2007.html" title="Official FreeBSD Summer of Code 2007 Final Status Update">http://www.FreeBSD.org/projects/summerofcode-2007.html</a></td></tr><tr><td><a href="http://googlesummerofcode.blogspot.com/2007/09/updates-from-freebsd.html" title="http://googlesummerofcode.blogspot.com/2007/09/updates-from-freebsd.html">Google Blog Post About FreeBSD</a></td><td>
-	    URL: <a href="http://googlesummerofcode.blogspot.com/2007/09/updates-from-freebsd.html" title="Google Blog Post About FreeBSD">http://googlesummerofcode.blogspot.com/2007/09/updates-from-freebsd.html</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SummerOfCode2007" title="http://wiki.freebsd.org/SummerOfCode2007">FreeBSD Summer of Code Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SummerOfCode2007" title="FreeBSD Summer of Code Wiki">http://wiki.freebsd.org/SummerOfCode2007</a></td></tr></table><p>
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>We're happy to report the successful conclusion of our third
-      consecutive Google Summer of Code. By all accounts, the FreeBSD
-      participation in this program was an unqualified success. We
-      narrowed down the many impressive applications to 25 that were
-      selected for funding and 92% of these completed successfully and
-      were awarded the full $4,500 stipend. The FreeBSD Foundation was
-      also granted $500 per student from Google for a total of
-      $12,500.</p>
-
-      <p>These student projects included security research, improved
-      installation tools, new utilities, and more. Many of the students
-      have continued working on their FreeBSD projects even after the
-      official close of the program. Three students have already been
-      granted full src/ commit access to CVS and more are expected. At
-      least 2 of our FreeBSD mentors will be meeting with Google
-      organizers in Mountain View this month to discuss the program at
-      the Mentor Summit.</p>
-    <h3>Open tasks:</h3><ol><li>Integration of student projects into FreeBSD -CURRENT.
-      Several are currently blocked on the FreeBSD 7.0 code freeze, but
-      we hope to see these contributions included in a future
-      release.</li><li>Updating the ideas list. Many of the items listed there have
-      been completed and we could always use new projects for next year's
-      students and for others to work on throughout the year.
-      http://www.FreeBSD.org/projects/ideas</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Apple's-MacBook-on-FreeBSD" href="#Apple's-MacBook-on-FreeBSD" id="Apple's-MacBook-on-FreeBSD">Apple's MacBook on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/AppleMacbook" title="http://wiki.freebsd.org/AppleMacbook"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/AppleMacbook" title="">http://wiki.freebsd.org/AppleMacbook</a></td></tr></table><p>
-	Contact:
-          Rui
-
-          Paulo
-         &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Summer of Code project went well and we reached interesting
-      results. At least the Mac Mini should be fully supported by now.
-      Regarding the other Apple systems, we still need to polish some
-      edges.</p>
-    <h3>Open tasks:</h3><ol><li>Integrate rpaulo-macbook p4 branch into CVS.</li><li>Continue the work on the remaining issues.</li></ol><hr /><h2><a name="Multi-link-PPP-daemon-(MPD)-5.x" href="#Multi-link-PPP-daemon-(MPD)-5.x" id="Multi-link-PPP-daemon-(MPD)-5.x">Multi-link PPP daemon (MPD) 5.x</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sourceforge.net/projects/mpd/" title="http://sourceforge.net/projects/mpd/">Project home</a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/mpd/" title="Project home">http://sourceforge.net/projects/mpd/</a></td></tr><tr><td><a href="http://mpd.sourceforge.net/doc5/mpd5.html" title="http://mpd.sourceforge.net/doc5/mpd5.html">ChangeLog</a></td><td>
-	    URL: <a href="http://mpd.sourceforge.net/doc5/mpd5.html" title="ChangeLog">http://mpd.sourceforge.net/doc5/mpd5.html</a></td></tr></table><p>
-	Contact:
-          Alexander
-
-          Motin
-         &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>New mpd-5.x branch has been started and first public release is
-      planned soon. The main goal of the new branch is to implement new
-      operation principles based on dynamic on-demand links/bundles
-      creation. There are several benefits received from new design:</p>
-
-      <ul>
-        <li>Significantly simplified server configuration - no more tons
-        of predefined links/bundles,</li>
-
-        <li>New multilink implementation - no more predefined link-bundle
-        relations,</li>
-
-        <li>Call forwarding (LAC, PAC, TSA) like in Cisco VPDN setups can
-        now be enabled/configured depending on peer auth
-        name/domain.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>L2TP auth proxying support.</li></ol><hr /><h2><a name="Multicast-DNS" href="#Multicast-DNS" id="Multicast-DNS">Multicast DNS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/MulticastDNS" title="http://wiki.freebsd.org/MulticastDNS"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/MulticastDNS" title="">http://wiki.freebsd.org/MulticastDNS</a></td></tr></table><p>
-	Contact:
-          Fredrik
-
-          Lindberg
-         &lt;<a href="mailto:fli@FreeBSD.org">fli@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project (started out as a GSoC 2007 project) aims to provide
-      a complete Multicast DNS and Service Discovery suite. Much progress
-      have been made since the last status report and the project is
-      slowly reaching a usable state. Most features are complete and the
-      current focus is on fixing outstanding bugs, fine tuning and
-      testing. However, there are still a few open tasks (see below).
-      More information and snapshots can be found at the wiki page.</p>
-    <h3>Open tasks:</h3><ol><li>Avahi library wrapper.</li><li>dns_sd (Apple) library wrapper.</li><li>Testing (always welcome).</li></ol><hr /><h2><a name="Porting-Linux-KVM-to-FreeBSD" href="#Porting-Linux-KVM-to-FreeBSD" id="Porting-Linux-KVM-to-FreeBSD">Porting Linux KVM to FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://feanor.sssup.it/~fabio/freebsd/lkvm/" title="http://feanor.sssup.it/~fabio/freebsd/lkvm/"></a></td><td>
-	    URL: <a href="http://feanor.sssup.it/~fabio/freebsd/lkvm/" title="">http://feanor.sssup.it/~fabio/freebsd/lkvm/</a></td></tr></table><p>
-	Contact:
-          Fabio
-
-          Checconi
-         &lt;<a href="mailto:fabio@FreeBSD.org">fabio@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Luigi
-
-          Rizzo
-         &lt;<a href="mailto:luigi@FreeBSD.org">luigi@FreeBSD.org</a>&gt;
-	</p>
-      <p>
-        <p>Linux KVM (Kernel-based Virtual Machine) is a software package
-        that can be used to create virtual machines fully emulating x86
-        hardware on top of machines supporting Intel VT-x or AMD-V
-        virtualization extensions, available on newer AMD and Intel
-        processors, e.g., recent Athlon64, Core 2 Duo, Xeon and so
-        on.</p>
-
-        <p>Linux KVM has been ported to FreeBSD as a loadable kernel
-        module, using the linux-kmod-compat port (in /usr/ports/devel/)
-        to reuse as much as possible of the original source code, plus an
-        userspace client consisting in a modified version of qemu, that
-        uses KVM for the execution of its guests.</p>
-
-        <p>The porting has been completed, many of the limitations
-        present at the end of the Summer of Code have been removed and
-        the known bugs have been fixed. Some configurations have been
-        tested, FreeBSD-CURRENT i386 guests have been booted on Intel and
-        AMD processors, both in i386 and amd64 (host) installations. Only
-        one client at a time is supported by now and performance is not
-        that exciting, but the project seems to be ready to receive wider
-        testing.</p>
-      </p>
-    <hr /><h2><a name="USB" href="#USB" id="USB">USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO">Current USB files</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO" title="Current USB files">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://perforce.freebsd.org/fileLogView.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb/README" title="http://perforce.freebsd.org/fileLogView.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb/README">Current USB API README file</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/fileLogView.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb/README" title="Current USB API README file">http://perforce.freebsd.org/fileLogView.cgi?FSPC=//depot/projects/usb/src/sys/dev/usb/README</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>&gt;
-	</p>
-      <p>During the last three months there has been a flush of changes
-      going into the FreeBSD USB P4 project. The changes mainly concern
-      the ability to support the USB device side and multi frame USB
-      transfers. Up to date the FreeBSD USB stack has only supported the
-      USB Host Side. Before Christmas 2007 the P4 USB project will offer
-      USB device support and some simple USB device side implementations.
-      Technically an USB device side driver will look very similar to an
-      USB host side driver. Infact there will be very few differences.
-      Support for multi frame USB transfers opens up the possibility to
-      transfer multiple short-packet terminated USB frames to/from
-      different memory locations resulting in only one interrupt on the
-      USB Host Controller. More specific: I have implemented support for
-      the "alt_next" pointer in the EHCI Transfer Descriptor. This should
-      give a noticeable increase in the maximum number of short-packet
-      terminated BULK frames that can be transferred per second.</p>
-
-      <p>I regularly get questions from people asking about when the USB
-      P4 project will be merged into FreeBSD-current. The answer is not
-      simple, but probably something like another year. The reason is not
-      that the current code in the USB P4 project is not usable, but
-      rather that the quality needs to be raised in means of making
-      already good solutions more technically excellent, writing more
-      documentation and styling the code.</p>
-
-      <p>Ideas and comments with regard to the new USB API are welcome at
-      freebsd-usb@freebsd.org.</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD.org-Admins-Report" href="#FreeBSD.org-Admins-Report" id="FreeBSD.org-Admins-Report">FreeBSD.org Admins Report</a></h2><p>
-	Contact:
-          FreeBSD.org
-
-          Admins Team
-
-          admins@FreeBSD.org
-         &lt;<a href="mailto:"></a>&gt;
-	</p>
-      <p>Over the last couple of months several FreeBSD.org systems have
-      been experiencing hardware issues. This included the main
-      web-server www.FreeBSD.org which had a bad fan. The bad fan has
-      been replaced so it should hopefully be stable again. In general we
-      are working on replacing older hardware with newer systems and
-      consolidating machine functions in the process.</p>
-
-      <p>Since August most FreeBSD.org services have been available via
-      IPv6 with connectivity provided from ISC using a tunnel.</p>
-
-      <p>To honor the "Eat your own dog-food" principle the first two
-      FreeBSD.org infrastructure systems have been upgraded to FreeBSD 7
-      and more are being upgraded as time permit.</p>
-
-      <p>Due to heavy load on the project's Perforce and CVS server the
-      two services are being moved to separate systems to improve
-      performance of both CVS and Perforce.</p>
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">The Marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="The Marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr><tr><td><a href="http://wiki.freebsd.org/gcc4" title="http://wiki.freebsd.org/gcc4">GCC4 Status Page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/gcc4" title="GCC4 Status Page">http://wiki.freebsd.org/gcc4</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports count is over 17,700. The PR count has decreased a bit
-      to just over 700.</p>
-
-      <p>There have been 6 experimental runs on the build cluster. The
-      resulting commits include the fixup of last year's DESTDIR changes,
-      the refactoring of perl bits into bsd.perl.mk, the update of xorg
-      from 7.2 to 7.3, the upgrade of all of the autoconf dependencies to
-      the latest version (wherever possible), and the upgrade of Python
-      to 2.5. This effort has resulted in the fewest number of 'open'
-      portmgr PRs in quite some time. portmgr appreciates all the people
-      who worked with us on these patches, and people's patience as we
-      catch up.</p>
-
-      <p>As well, lofi@ committed the upgrade of QT to 4.3.1.</p>
-
-      <p>We have added 3 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>GCC4.2 has been imported to the base for 7.0. Unfortunately,
-      this broke a large number of ports. The ones that have not yet been
-      fixed have now been flagged as 'broken' for both i386 and amd64, as
-      appropriate. Please see the GCC4 status page (above) if you are
-      able to help.</li><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have many
-      unmaintained ports. The packages on amd64 are lagging behind a bit;
-      those on sparc64 require even more work.</li></ol><hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Network-Stack-Virtualization" href="#Network-Stack-Virtualization" id="Network-Stack-Virtualization">Network Stack Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://imunes.tel.fer.hr/virtnet/" title="http://imunes.tel.fer.hr/virtnet/"></a></td><td>
-	    URL: <a href="http://imunes.tel.fer.hr/virtnet/" title="">http://imunes.tel.fer.hr/virtnet/</a></td></tr></table><p>
-	Contact:
-          Marko
-
-          Zec
-         &lt;<a href="mailto:zec@fer.hr">zec@fer.hr</a>&gt;
-	</p>
-      <p>The network stack virtualization project aims at extending the
-      FreeBSD kernel to maintain multiple independent instances of
-      networking state. This allows for networking independence between
-      jail-like environmens, each maintaining its private network
-      interface set, IPv4 and IPv6 network and port address space,
-      routing tables, IPSec configuration, firewalls, and more.</p>
-
-      <p>The prototype, which is kept in sync with FreeBSD -CURRENT,
-      should be sufficiently stable for testing and experimental use. The
-      project's web page includes weekly code snapshots, as well as a
-      virtualized FreeBSD system installed on a VMWare disk image
-      available for download.</p>
-
-      <p>The short-term goal is to deliver production-grade kernel
-      support for virtualized networking for FreeBSD 7.0-RELEASE (as a
-      snap-in kernel replacement), while continuing to keep the code in
-      sync with -CURRENT for possible merging at a later date.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="PC-BSD-Handbook" href="#PC-BSD-Handbook" id="PC-BSD-Handbook">PC-BSD Handbook</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pcbsd.org" title="http://www.pcbsd.org">PC-BSD Web Page</a></td><td>
-	    URL: <a href="http://www.pcbsd.org" title="PC-BSD Web Page">http://www.pcbsd.org</a></td></tr><tr><td><a href="http://www.FreeBSD.org/handbook" title="http://www.FreeBSD.org/handbook">FreeBSD Handbook</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/handbook" title="FreeBSD Handbook">http://www.FreeBSD.org/handbook</a></td></tr></table><p>
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Matt
-
-          Olander
-         &lt;<a href="mailto:matt@FreeBSD.org">matt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Fukang
-
-          Chen
-         &lt;<a href="mailto:loader@FreeBSD.org">loader@FreeBSD.org</a>&gt;
-	</p>
-      <p>The PC-BSD derivative of FreeBSD is becoming increasingly
-      popular for new users of BSD. Much of the content in the existing
-      FreeBSD Handbook is directly applicable to PC-BSD. We are writing
-      PC-BSD specific installation and port/packages chapters (PBI).
-      These chapters will be checked into
-      docs/en_US.ISO8859-1/books/pcbsd-handbook and will include some of
-      the same chapters as the Handbook does, but with a different
-      &amp;os entity and possibly with some conditional changes in those
-      chapter files.</p>
-    <h3>Open tasks:</h3><ol><li>More work is needed on a PC-BSD ports/packages chapter.
-      Fukang may already have some work in this area so coordinate with
-      him first.</li><li>More text is needed for the PC-BSD installation chapter to
-      augment the screenshots that Fukang has collected. Contact him to
-      coordinate.</li></ol><hr /><h2><a name="The-Hungarian-Documentation-Project" href="#The-Hungarian-Documentation-Project" id="The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/hu/docproj/hungarian.html" title="http://www.freebsd.org/hu/docproj/hungarian.html">Info for volunteers</a></td><td>
-	    URL: <a href="http://www.freebsd.org/hu/docproj/hungarian.html" title="Info for volunteers">http://www.freebsd.org/hu/docproj/hungarian.html</a></td></tr><tr><td><a href="http://www.freebsd.org/hu/" title="http://www.freebsd.org/hu/">Hungarian website</a></td><td>
-	    URL: <a href="http://www.freebsd.org/hu/" title="Hungarian website">http://www.freebsd.org/hu/</a></td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/docproj%5fhu&amp;HIDEDEL=NO" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/docproj%5fhu&amp;HIDEDEL=NO">Perforce repository</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/docproj%5fhu&amp;HIDEDEL=NO" title="Perforce repository">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/docproj%5fhu&amp;HIDEDEL=NO</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have a new volunteer, G�bor P�li, who provided us
-      some high-quality contributions. As a result, we have been able to add 5
-      new articles since the last status report.</p>
-
-      <p>There is also an ongoing effort in the Perforce repository to
-      translate the FreeBSD Handbook to Hungarian. Any kind of support is
-      highly welcome.</p>
-    <h3>Open tasks:</h3><ol><li>Translate the Handbook.</li></ol><hr /><h2><a name="The-Spanish-Documentation-Project" href="#The-Spanish-Documentation-Project" id="The-Spanish-Documentation-Project">The Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/" title="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/">Info for volunteers</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/" title="Info for volunteers">http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/</a></td></tr></table><p>
-	Contact:
-          J. Vicente
-
-          Carrasco Vay�
-         &lt;<a href="mailto:carvay@FreeBSD.org">carvay@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>After a long break in this project, we started reviewing and
-      refreshing our translations. We have to update the content to
-      reflect the current state of the English version. There are a few
-      parts written in a poor style, another task is to improve these a
-      bit. Any kind of help is highly welcome.</p>
-    <h3>Open tasks:</h3><ol><li>Sync the website with the English version.</li><li>Sync the documentation with the English version.</li><li>Review the quality of poorly translated parts.</li><li>Add more translations.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="EuroBSDcon-2007" href="#EuroBSDcon-2007" id="EuroBSDcon-2007">EuroBSDcon 2007</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2007.EuroBSDCon.org/" title="http://2007.EuroBSDCon.org/"></a></td><td>
-	    URL: <a href="http://2007.EuroBSDCon.org/" title="">http://2007.EuroBSDCon.org/</a></td></tr></table><p>
-	Contact:
-          EuroBSDCon 2007 Organizing Committee
-         &lt;<a href="mailto:info@EuroBSDCon.dk">info@EuroBSDCon.dk</a>&gt;
-	</p>
-      <p>The sixth EuroBSDCon went well. 215 people attended the
-      conference. Feedback has been very positive.</p>
-
-      <p>At the conference we had a Best Talk contest. Steven Murdoch,
-      Isaac Levy and Pawel Jakub "zfs-man" Dawidek each received a prize
-      for their fantastic talks.</p>
-
-      <p>Also over 300 pictures from the conference has been uploaded to
-      Flickr with the tag
-      <a href="http://www.flickr.com/photos/tags/eurobsdcon2007/" shape="rect">
-      EuroBSDCon2007</a>
-      </p>
-
-      <p>Videos and slides from the talks are now online at the
-      conference website.</p>
-
-      <p>We thank our speakers for graciously having permitted recording
-      and publication of their talks</p>
-
-      <p>EuroBSDCon 2008 will take place in Strassbourg.</p>
-    <hr /><h2><a name="GNATS-graphs" href="#GNATS-graphs" id="GNATS-graphs">GNATS graphs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~edwin/gnats/" title="http://people.freebsd.org/~edwin/gnats/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~edwin/gnats/" title="">http://people.freebsd.org/~edwin/gnats/</a></td></tr></table><p>
-	Contact:
-          Edwin
-
-          Groothuis
-         &lt;<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>With the leaving of bsd@, we lost the GNATS statistics webpages.
-      On this URL I generate a new set of graphs, right now a subset of
-      what bsd@ had, hopefully a superset of that in the future.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2007-10-2007-12.html b/website/content/en/status/report-2007-10-2007-12.html
deleted file mode 100644
index d06df12d1f..0000000000
--- a/website/content/en/status/report-2007-10-2007-12.html
+++ /dev/null
@@ -1,1111 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between October and
-    December 2007.
-    <a href="http://2008.asiabsdcon.org/" shape="rect">AsiaBSDCon 2008</a>
-
-    is approaching and will be held at the Tokyo University of Science in
-    Tokyo, Japan on the 27th - 30th of March 2008. The FreeBSD Foundation
-    has released a
-    <a href="http://www.freebsdfoundation.org/press/2007Dec-newsletter.shtml" shape="rect">
-    Newsletter</a>
-
-    detailing their activities over the past few months.</p><p>FreeBSD 7.0 is nearing release and the 2nd Release Candidate is
-    ready for testing and is available for
-    <a href="http://www.freebsd.org/where.html#helptest" shape="rect">download now</a>.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#DTrace">DTrace</a></li><li><a href="#FreeBSD-Installer">FreeBSD Installer</a></li><li><a href="#Performance-Monitoring-Project">Performance Monitoring Project</a></li><li><a href="#TCP-ECN">TCP ECN</a></li><li><a href="#TrustedBSD-Audit">TrustedBSD Audit</a></li><li><a href="#Xen">Xen</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Security-Officer-and-Security-Team">Security Officer and Security Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Coda">Coda</a></li><li><a href="#DDB-scripting,-output-capture,-and-textdumps">DDB scripting, output capture, and textdumps</a></li><li><a href="#FreeBSD-SMP-network-stack-scalability">FreeBSD SMP network stack scalability</a></li><li><a href="#FreeBSD/mips">FreeBSD/mips</a></li><li><a href="#LVM-geom-class">LVM geom class</a></li><li><a href="#Major-TCP-Code-Cleanup-and-Rewrite">Major TCP Code Cleanup and Rewrite</a></li><li><a href="#Multi-IPv4/v6-jails">Multi-IPv4/v6 jails</a></li><li><a href="#TCP-Reassembly-Queue-Optimization">TCP Reassembly Queue Optimization</a></li><li><a href="#VM-Overcommit">VM Overcommit</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></li><li><a href="#The-Spanish-Documentation-Project">The Spanish Documentation Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#malloc(3)">malloc(3)</a></li><li><a href="#procstat(1)">procstat(1)</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Ports-2.0">Ports 2.0</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#Bug-Busting">Bug Busting</a></li><li><a href="#FreeBSD-Mirror-Site-Status">FreeBSD Mirror Site Status</a></li><li><a href="#Opensource-Solutions-'08">Opensource Solutions '08</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="DTrace" href="#DTrace" id="DTrace">DTrace</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jb/reasons/reasons.html" title="http://people.freebsd.org/~jb/reasons/reasons.html">Change summary</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~jb/reasons/reasons.html" title="Change summary">http://people.freebsd.org/~jb/reasons/reasons.html</a></td></tr></table><p>
-	Contact:
-          John
-
-          Birrell
-         &lt;<a href="mailto:jb@FreeBSD.org">jb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Thanks to support from Cisco Systems, Inc, the port of the
-      DTrace dynamic tracing framework from OpenSolaris to FreeBSD is
-      active again. A solution to the integration issues surrounding the
-      CDDL and BSD licenses has been found. There is an entirely BSD
-      licensed set of hooks/shims which are optionally compiled into the
-      kernel. This option can be included in the GENERIC kernel and
-      shipped without any CDDL patent encumberance. The CTF (Compact C
-      Type Format) tools now work across all architectures enabled in a
-      'make universe'. A BSD licensed DWARF library has been developed.
-      The kernel DTrace support is limited to amd64 and i386 at the
-      moment. It currently passes 822 of the tests in the DTrace Test
-      Suite. It is expected that the initial commit to FreeBSD-CURRENT
-      will occur within the next month after review. Refer to the change
-      summary page for details of the proposed changes.</p>
-    <hr /><h2><a name="FreeBSD-Installer" href="#FreeBSD-Installer" id="FreeBSD-Installer">FreeBSD Installer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~mtm/fin.tar.bz2" title="http://people.freebsd.org/~mtm/fin.tar.bz2"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mtm/fin.tar.bz2" title="">http://people.freebsd.org/~mtm/fin.tar.bz2</a></td></tr></table><p>
-	Contact:
-          Mike
-
-          Makonnen
-         &lt;<a href="mailto:mtm@FreeBSD.Org">mtm@FreeBSD.Org</a>&gt;
-	</p>
-      <p>The FreeBSD Installer project (FIN) is yet another attempt to
-      replace the aging sysinstall(8). I am attempting to keep the best
-      parts of sysinstall(8) and combine them with the framework provided
-      by the BSDInstaller (bsdinstaller.org) to create an installation
-      program for FreeBSD that is multi-lingual, supports multiple
-      installation media, supports remote installation, and is easily
-      extensible to other installation types (gui, cgi, etc). The current
-      implementation will slice disks, install your choice of base
-      distributions, and set hostname and root password.</p>
-    <h3>Open tasks:</h3><ol><li>Setting date, time, and time zone information</li><li>Choosing and installing packages</li><li>Support for installation media other than IDE CD-Rom (HTTP,
-      FTP, etc)</li><li>Integration with devel/gettext</li></ol><hr /><h2><a name="Performance-Monitoring-Project" href="#Performance-Monitoring-Project" id="Performance-Monitoring-Project">Performance Monitoring Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://littlebit.dk:5000/" title="http://littlebit.dk:5000/">Temporary website location</a></td><td>
-	    URL: <a href="http://littlebit.dk:5000/" title="Temporary website location">http://littlebit.dk:5000/</a></td></tr></table><p>
-	Contact:
-          Erik
-
-          Cederstrand
-         &lt;<a href="mailto:erik@cederstrand.dk">erik@cederstrand.dk</a>&gt;
-	</p>
-      <p>As part of my thesis, I've been working on a framework to
-      monitor the performance of CURRENT over time. The project is now in
-      a state where a server and a slave are producing benchmark results
-      and publishing the results to a web page for testing. Already, the
-      setup has detected regressions. Lots of improvements can be made,
-      but it is already quite useful. Over the next month I'll be adding
-      a few features, fixing bugs and writing documentation.</p>
-    <h3>Open tasks:</h3><ol><li>Decide on a useful set of benchmarks</li><li>Find a more permanent home for the database and
-      webserver</li><li>Go live</li></ol><hr /><h2><a name="TCP-ECN" href="#TCP-ECN" id="TCP-ECN">TCP ECN</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=DN2@//depot/projects/tcpecn/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=DN2@//depot/projects/tcpecn/?ac=83">Perforce repository</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=DN2@//depot/projects/tcpecn/?ac=83" title="Perforce repository">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=DN2@//depot/projects/tcpecn/?ac=83</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-net/2007-November/016007.html" title="http://lists.freebsd.org/pipermail/freebsd-net/2007-November/016007.html">Mail discussion</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-net/2007-November/016007.html" title="Mail discussion">http://lists.freebsd.org/pipermail/freebsd-net/2007-November/016007.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~rpaulo/tcp_ecn.diff" title="http://people.freebsd.org/~rpaulo/tcp_ecn.diff">Patch</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~rpaulo/tcp_ecn.diff" title="Patch">http://people.freebsd.org/~rpaulo/tcp_ecn.diff</a></td></tr></table><p>
-	Contact:
-          Rui
-
-          Paulo
-         &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Completed and tested. Awaiting review from other committers.</p>
-    <hr /><h2><a name="TrustedBSD-Audit" href="#TrustedBSD-Audit" id="TrustedBSD-Audit">TrustedBSD Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.TrustedBSD.org/audit.html" title="http://www.TrustedBSD.org/audit.html">TrustedBSD Audit home page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/audit.html" title="TrustedBSD Audit home page">http://www.TrustedBSD.org/audit.html</a></td></tr><tr><td><a href="http://www.TrustedBSD.org/openbsm.html" title="http://www.TrustedBSD.org/openbsm.html">TrustedBSD OpenBSM home page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/openbsm.html" title="TrustedBSD OpenBSM home page">http://www.TrustedBSD.org/openbsm.html</a></td></tr><tr><td><a href="http://www.TrustedBSD.org/bsmtrace.html" title="http://www.TrustedBSD.org/bsmtrace.html">BSMtrace home page</a></td><td>
-	    URL: <a href="http://www.TrustedBSD.org/bsmtrace.html" title="BSMtrace home page">http://www.TrustedBSD.org/bsmtrace.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Christian
-
-          Peron
-         &lt;<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD Audit Mailing List
-         &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project was proud to release OpenBSM 1.0, the
-      first production release of OpenBSM, which is shipped with FreeBSD
-      6.3 and will ship with FreeBSD 7.0. This release represents largely
-      polishing, bug fixing, and cleanup over the previous alpha release,
-      but for FreeBSD 6.x introduced features such as XML audit trail
-      printing, new token types, and new event identifiers.</p>
-
-      <p>A variety of development work continues on audit, including
-      initial work on OpenBSM 1.1 alpha, work on improving the
-      performance and semantics of audit pipes, and the experimental
-      bsmtrace host intrusion detection package.</p>
-    <h3>Open tasks:</h3><ol><li>Improve performance for live intrusion detection by
-      introducing additional buffering and multi-record copying for audit
-      pipes.</li><li>Improve flexibility for live intrusion detection and
-      monitoring by adding finer-grained record matching support for
-      audit pipes, such as by-pid and by-pid-tree.</li><li>Introduce multi-host network support for experimental
-      bsmtrace intrusion detection package, allowing central monitoring
-      and alarms on live bsm traces from many hosts.</li><li>Continue analysis of CC audit requirements to flesh out
-      missing event sources, such as user admin tools that don't
-      currently generate audit records.</li></ol><hr /><h2><a name="Xen" href="#Xen" id="Xen">Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fsmware.com/xenofreebsd/7.0/download/" title="http://www.fsmware.com/xenofreebsd/7.0/download/">A small file-backed disk and some sample configuration files can be found</a></td><td>
-	    URL: <a href="http://www.fsmware.com/xenofreebsd/7.0/download/" title="A small file-backed disk and some sample configuration files can be found">http://www.fsmware.com/xenofreebsd/7.0/download/</a></td></tr></table><p>
-	Contact:
-          Kip
-
-          Macy
-         &lt;<a href="mailto:kmacy@FreeBSD.org">kmacy@FreeBSD.org</a>&gt;
-	</p>
-      <p>The port will only run as a guest (i.e. domU) right now, on
-      i386/PAE platforms. Status:</p>
-      <ul>
-        <li>domU is self-hosting on 8-CURRENT (can compile world + kernel
-          in a VM).</li>
-        <li>Xen 3.0.3 and earlier are not supported.</li>
-        <li>Device structure needs to be cleaned up, it's not conformant
-          to newbus.</li>
-        <li>SMP and amd64 are targeted for support by May for RELENG_6
-          and RELENG_7.</li>
-        <li>dom0 support is not currently on the roadmap.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Substantial cleanup needed, talk with Kip Macy or Scott Long
-      if you are interested in helping</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="Security-Officer-and-Security-Team" href="#Security-Officer-and-Security-Team" id="Security-Officer-and-Security-Team">Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the time since the last status report, four security
-      advisories have been issued concerning problems in the base system
-      of FreeBSD; one of these problems was in "contributed" code
-      maintained outside of FreeBSD. The FreeBSD Vulnerabilities and
-      Exposures Markup Language (VuXML) document has continued to be
-      updated; since the last status report, 61 new entries have been
-      added, bringing the total up to 1023. Many of these new VuXML
-      entries were made by members of the "ports-security" team.</p>
-
-      <p>The "ports-security" team is still looking for more committers
-      who can periodically help with fixing ports security issues and
-      documenting them in the FreeBSD VuXML document. Committers who wish
-      to help with this effort can contact simon@ for details.</p>
-
-      <p>The following FreeBSD releases are supported by the FreeBSD
-      Security Team: FreeBSD 5.5, FreeBSD 6.1, FreeBSD 6.2, and FreeBSD
-      6.3. The respective End of Life dates of supported releases are
-      listed on the web site; it is expected that the upcoming FreeBSD
-      7.0 release will be supported for one year after its release.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Coda" href="#Coda" id="Coda">Coda</a></h2><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>A large number of bugs have been fixed in the FreeBSD "coda"
-      kernel module over the past six months, and a man page has been
-      added to describe the module. Many of these bugs were the result of
-      the coda module failing to keep up with the many enhancements to
-      FreeBSD VFS over the last few years. As a result of these fixes, it
-      is now possible to use Coda with FreeBSD 7.x and 8.x without
-      immediate panics, and possibly for an extended period. The new man
-      page does clarify that Coda is an experimental distributed file
-      system and not yet appropriate for production use on FreeBSD, but
-      things are looking a lot better than they were.</p>
-    <hr /><h2><a name="DDB-scripting,-output-capture,-and-textdumps" href="#DDB-scripting,-output-capture,-and-textdumps" id="DDB-scripting,-output-capture,-and-textdumps">DDB scripting, output capture, and textdumps</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-        <p>The kernel DDB facility has been enhanced to add several new
-        features:</p>
-
-        <p>
-        <em>DDB scripting</em>
-        allows the user to define a set of simple scripts from within the
-        debugger or userspace using the new ddb(8) tool to automate
-        debugging steps. Scripts can be automatically executed when the
-        debugger is entered ("kdb.enter.panic", "kdb.enter.break", ...)
-        or manually using the DDB "run" command.</p>
-
-        <p>
-        <em>DDB output capture</em>
-        allows the user to request that the output of DDB be captured
-        into a buffer for access from user space or to be written out in
-        a textdump.</p>
-
-        <p>
-        <em>DDB textdumps</em>,
-        a new dump format that writes out a tarball of text-based
-        debugging information, such as the kernel message buffer, panic
-        message, kernel configuration, kernel version, and DDB capture
-        buffer to the swap partition, to be extracted via savecore(8).
-        This provides a compact, portable, and kernel compile independent
-        debugging package.</p>
-
-        <p>Various interesting formulas for use are described in ddb(4)
-        and textdump(4); the facilities are separable, so you can, for
-        example, run a few DDB commands and capture their output, then
-        write a regular dump and extract that output using kgdb, or you
-        can do the same and write it out as a textdump. Likewise, scripts
-        can be used to automate manual debugging, or implement textdumps
-        by enabling output capture, running a series of commands, and
-        forcing a textdump to be written before rebooting.</p>
-
-        <p>Support for these facilities has been merged into 8-CURRENT,
-        and will be merged to 7-STABLE after the release of FreeBSD
-        7.0.</p>
-    <h3>Open tasks:</h3><ol><li>Improve semantics of combining textdumps with
-      KDB_UNATTENDED.</li><li>Allow scripts to use the DDB "continue" command when the
-      script has been started automatically as a result of a KDB enter
-      event, such as "kdb.enter.sysctl" or "kdb.enter.break".</li></ol><hr /><h2><a name="FreeBSD-SMP-network-stack-scalability" href="#FreeBSD-SMP-network-stack-scalability" id="FreeBSD-SMP-network-stack-scalability">FreeBSD SMP network stack scalability</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Kris
-
-          Kennaway
-         &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are a variety of on-going projects relating to improving
-      SMP scalability of the FreeBSD network stack post-7.0. These
-      include:</p>
-
-      <p>
-        <em>Detailed profiling of application workloads such as BIND9,
-        MySQL, PgSQL and Apache have been used to identify performance
-        bottlenecks and to guide changes to the source code.</em>
-      </p>
-
-      <p>
-      <em>rwlock(9) use for pcbinfo and inpcb locking</em>
-
-      , allowing the acquisition of only read locks for pcbinfo and inpcb
-      during UDP receive and transmit--this is highly desirable in order
-      to improve BIND9 performance, which sends and receives from many
-      threads at a time on a single UDP socket.</p>
-
-      <p>
-      <em>Breaking out pcbinfo into a series of parallel data
-      structures</em>
-
-      , where the particular pcbinfo instance is selected using a hash of
-      the connection tuple (and where ambiguous cases are present in all
-      instances). This would allow greatly reducing pcbinfo contention
-      for parallel input cases, which are increasingly likely with
-      multiple input queue network devices, such as the Chelsio cxgb
-      10gbps driver.</p>
-
-      <p>
-      <em>Investigation of use opportunities for rmlock(9)</em>
-
-      -- rmlocks provide very lightweight acquisition for read, but
-      expensive acquisition for write, and may be an appropriate
-      replacement for rwlocks where significantly more reads than writes
-      take place -- such as for firewall rule list protection, pf hook
-      registration, address lists, etc.</p>
-
-      <p>
-      <em>Weak connection affinity</em>
-
-      , in which the effective affinity of a connection, determined by
-      its hash/rss work assignment to a particular input queue by the
-      network stack or network card, is tracked and exposed to user space
-      so that work associated with that connection can be performed on or
-      close to the CPU where the kernel will be processing input for the
-      connection. Software work placement has been done using the
-      <em>netisr2</em>
-
-      implementation, which creates per-CPU netisr threads and assigns
-      work based on connection properties.</p>
-
-      <p>There are also many other pieces of related work going on,
-      especially relating to 10gbps network drivers, and workloads of
-      particular interest include BIND9, MySQL, pgsql, Apache, and
-      general TCP parallelism.</p>
-    <hr /><h2><a name="FreeBSD/mips" href="#FreeBSD/mips" id="FreeBSD/mips">FreeBSD/mips</a></h2><p>
-	Contact:
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Oleksandr
-
-          Tymoshenko
-         &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Ollivier
-
-          Houchard
-         &lt;<a href="mailto:cognet@FreeBSD.org">cognet@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Randall
-
-          Stewart
-         &lt;<a href="mailto:rrs@FreeBSD.org">rrs@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD/mips boots to multiuser using gxemul on the MALTA board
-      with a 4Kc based CPU. The port is targeting MIPS32 and MIPS64
-      release 1 and release 2 based systems. Work is underway to support
-      multicore systems.</p>
-
-      <p>Preliminary ports to adm 5120, the IDT RC32434, the Sentry 5,
-      and a few other targets have started. These ports are in various
-      stages of stability.</p>
-
-      <p>Juniper Networks has donated a generic MIPS FreeBSD port. This
-      port doesn't run on any real hardware, but contains the necessary
-      parts to run on idealized MIPS hardware. The FreeBSD/mips workers
-      have been merging the current base and the Juniper code into a
-      unified base. In addition, Cavium Networks has donated code
-      supporting their multicore mips64r2 platform. This code is also
-      being merged into the tree and cleaned up as well. The merged code
-      base presently is making it to the first (or maybe second) call to
-      cpu_switch before dying. Active work is underway in this area.</p>
-    <hr /><h2><a name="LVM-geom-class" href="#LVM-geom-class" id="LVM-geom-class">LVM geom class</a></h2><p>
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
-	</p>
-      <p>glvm is a geom class which reads the metadata from a LVM2 (Linux
-      volume manager) disk and creates a geom provider for each logical
-      volume. An example is the logs lv on a volume group called vg0
-      appearing as /dev/lvm/vg0-logs, this can be mounted as a disk.</p>
-
-      <p>The code is working and will be posted for testing soon.</p>
-    <hr /><h2><a name="Major-TCP-Code-Cleanup-and-Rewrite" href="#Major-TCP-Code-Cleanup-and-Rewrite" id="Major-TCP-Code-Cleanup-and-Rewrite">Major TCP Code Cleanup and Rewrite</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_new/..." title="http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_new/...">Change log</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_new/..." title="Change log">http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_new/...</a></td></tr><tr><td><a href="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_new/netinet/tcp_input.c" title="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_new/netinet/tcp_input.c">TCP input source code</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_new/netinet/tcp_input.c" title="TCP input source code">http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_new/netinet/tcp_input.c</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD TCP code has evolved a lot over time and many new
-      features were added. However over time it got crufty, complex and
-      hard to read and track. In some places functionality was moved away
-      but the corresponding code in the main TCP functions was not or not
-      fully removed.</p>
-
-      <p>The main purpose of of the TCP code cleanup and rewrite is to
-      make the code:</p>
-
-      <ul>
-        <li>Easily readable again;</li>
-
-        <li>Easily trackable again;</li>
-
-        <li>A lot simpler to maintain;</li>
-
-        <li>Verifiably correct and RFC conforming;</li>
-
-        <li>Easily extendable for new congestion control algorithms;</li>
-
-        <li>Increase in performance.</li>
-      </ul>
-
-      <p>Quite a bit of code is already (re)written but a lot still
-      remains to be done.</p>
-    <h3>Open tasks:</h3><ol><li>Integration of code from private branch into public perforce
-      repository.</li><li>Completion of code and rewrite. Integration with pluggable
-      congestion control algorithms.</li><li>Full code behavior check against all TCP RFCs and drafts of
-      upcoming RFCs.</li><li>Extended testing and full code review by other TCP
-      developers.</li></ol><hr /><h2><a name="Multi-IPv4/v6-jails" href="#Multi-IPv4/v6-jails" id="Multi-IPv4/v6-jails">Multi-IPv4/v6 jails</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.ORG">bz@FreeBSD.ORG</a>&gt;
-	</p>
-      <p>The multi-IPv4/v6 jails project was resumed in early January
-      after previous work had been abandoned in 2006.</p>
-
-      <p>As an alternate solution to full network stack virtualization,
-      this work shall provide a lightweight solution for multi-IP
-      virtualization. The changes are even more important because of the
-      emerging demand for IPv6.</p>
-
-      <p>The current status includes updated user space utilities. Kernel
-      side has grown support for multiple IP addresses for both address
-      families in jails, while the old kernel internal lookup/checking
-      functions were kept and can be compiled in during the transition
-      period limiting jails to one IP address. Additionally a show jails
-      DDB command was added to ease debugging.</p>
-
-      <p>As an auxiliary project the last suser(9) checks were replaced
-      in netinet6/ to support optional raw IPv6 sockets with jails. The
-      new priv(9) checks were committed to HEAD.</p>
-    <h3>Open tasks:</h3><ol><li>Check for proper v4-mapped v6 address handling.</li><li>Review/add SCTP jail checks.</li><li>Think of enhanced lookups for jails with lots of IP addresses
-      (preserving the "primary" IPv4 address).</li><li>Regression tests and review.</li></ol><hr /><h2><a name="TCP-Reassembly-Queue-Optimization" href="#TCP-Reassembly-Queue-Optimization" id="TCP-Reassembly-Queue-Optimization">TCP Reassembly Queue Optimization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_reass/..." title="http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_reass/...">Change log</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_reass/..." title="Change log">http://perforce.freebsd.org/changeList.cgi?CMD=changes&amp;FSPC=//depot/projects/tcp_reass/...</a></td></tr><tr><td><a href="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_reass/netinet/tcp_reass.c" title="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_reass/netinet/tcp_reass.c">TCP reassembly queue source file</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_reass/netinet/tcp_reass.c" title="TCP reassembly queue source file">http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/projects/tcp_reass/netinet/tcp_reass.c</a></td></tr></table><p>
-	Contact:
-          Andre
-
-          Oppermann
-         &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD TCP reassembly queue system has reached its limits
-      with today's high speed links over long distances and large socket
-      buffers. The old code is almost unchanged compared to 4.4BSD
-      and gets quite inefficient with large mbuf chains.</p>
-
-      <p>The new code aggregates consecutive segments into blocks and
-      inserts the blocks into a tail queue. The insertion points for a
-      newly arrived segment are checked in order of their probability.
-      This prevents full chain traversals and is very efficient.</p>
-
-      <p>To prevent easy resource exhaustion attacks the effective mbuf
-      usage is accounted for and limited by the size of socket buffer.
-      This way the reassembly queue can't be abused with many holes among
-      small segments.</p>
-
-      <p>A further addition is the combination of received SACK block
-      tracking with the reassembly queue. The reassembly queue now tracks
-      all blocks of segments. This makes tracking it again for SACK
-      unnecessary. Additionally the limitation to six SACK blocks is
-      lifted and the size of the inpcb structure is reduced quite a
-      bit.</p>
-
-      <p>The new code is stable and in testing correctly handles the
-      download of a full set of FreeBSD CDROM images and 180 ports
-      distfiles from widely distributed sites around the world at 2%
-      packet loss.</p>
-    <h3>Open tasks:</h3><ol><li>Additional small performance and space optimizations.</li><li>Extended testing with new ipfw tcptruncate option to chop up
-      TCP segments and feed them with full and partial loss into
-      reassembly.</li><li>Full code review by other TCP developers.</li></ol><hr /><h2><a name="VM-Overcommit" href="#VM-Overcommit" id="VM-Overcommit">VM Overcommit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~kib/overcommit" title="http://people.freebsd.org/~kib/overcommit">The project page</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~kib/overcommit" title="The project page">http://people.freebsd.org/~kib/overcommit</a></td></tr></table><p>
-	Contact:
-          Konstantin
-
-          Belousov
-         &lt;<a href="mailto:kostikbel@gmail.com">kostikbel@gmail.com</a>&gt;
-	<br />
-	Contact:
-          Peter
-
-          Holm
-         &lt;<a href="mailto:peter@holm.cc">peter@holm.cc</a>&gt;
-	</p>
-      <p>The patch to account the possibly required swap space and limit
-      it by total amount of configured swap or per-uid limit is revived,
-      ported to the 8-CURRENT. Now it is intensively tested by Peter
-      Holm. Please, give it a run in the diverse workloads. Your comments
-      are welcome!</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-Hungarian-Documentation-Project" href="#The-Hungarian-Documentation-Project" id="The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/hu/" title="http://www.freebsd.org/hu/">Hungarian webpage</a></td><td>
-	    URL: <a href="http://www.freebsd.org/hu/" title="Hungarian webpage">http://www.freebsd.org/hu/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/" title="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/">Hungarian articles</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/" title="Hungarian articles">http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/</a></td></tr><tr><td><a href="http://perforce.freebsd.org/changeList.cgi?FSPC=//depot/projects/docproj%5fhu/books/handbook/...%2b//depot/projects/docproj%5fhu/share/..." title="http://perforce.freebsd.org/changeList.cgi?FSPC=//depot/projects/docproj%5fhu/books/handbook/...%2b//depot/projects/docproj%5fhu/share/...">Perforce changelist</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/changeList.cgi?FSPC=//depot/projects/docproj%5fhu/books/handbook/...%2b//depot/projects/docproj%5fhu/share/..." title="Perforce changelist">http://perforce.freebsd.org/changeList.cgi?FSPC=//depot/projects/docproj%5fhu/books/handbook/...%2b//depot/projects/docproj%5fhu/share/...</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have added the translation of the FreeBSD Flyer and
-      maintained the existing translations. A huge progress is being made
-      to provide a Hungarian translation of the FreeBSD Handbook. Also,
-      there is an ongoing effort to provide Hungarian release notes for
-      the upcoming FreeBSD releases.</p>
-    <h3>Open tasks:</h3><ol><li>Translate Handbook</li><li>Add release notes for HEAD and RELENG_7</li></ol><hr /><h2><a name="The-Spanish-Documentation-Project" href="#The-Spanish-Documentation-Project" id="The-Spanish-Documentation-Project">The Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/" title="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/">Info for volunteers</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/" title="Info for volunteers">http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/</a></td></tr></table><p>
-	Contact:
-          Jos� Vicente
-
-          Carrasco Vay�
-         &lt;<a href="mailto:carvay@FreeBSD.org">carvay@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report we have made a nice progress about
-      the website translation. The structure of the translated sites is
-      polished and we have brought a significant set of pages up-to-date.
-      New pages with important content have also been translated. Apart
-      from the good progress, there is a still a lot to do. Some pages
-      are still seriously outdated and some important parts are
-      missing.</p>
-
-      <p>At the same time, we have added one new article translation and
-      one is still awaiting review before being committed.</p>
-    <h3>Open tasks:</h3><ol><li>Continue synchronizing the website with the English one and
-      translate further important parts</li><li>Synchronize the articles and the Handbook</li><li>Add new translations</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="malloc(3)" href="#malloc(3)" id="malloc(3)">malloc(3)</a></h2><p>
-	Contact:
-          Jason
-
-          Evans
-         &lt;<a href="mailto:jasone@FreeBSD.org">jasone@FreeBSD.org</a>&gt;
-	</p>
-      <p>malloc(3) has been enhanced in several ways to reduce lock
-      contention when multi-threaded programs concurrently use the
-      malloc(3) functions. The primary enhancements are lazy deallocation
-      and dynamic arena load balancing.</p>
-
-      <p>Lazy deallocation is designed to reduce contention for programs
-      that use the producer-consumer model, where a thread produces
-      (allocates) objects, and a pool of worker threads consumes
-      (deallocates) those objects. As a side benefit, lazy deallocation
-      also substantially reduces lock contention if multiple unrelated
-      threads are using the same arena.</p>
-
-      <p>Allocation activity patterns can change throughout the lifetime
-      of a program. Dynamic arena load balancing monitors arena lock
-      contention and re-assigns threads to other arenas as necessary,
-      thus smoothing out allocator performance.</p>
-
-      <p>In order to monitor lock contention in support of arena load
-      balancing, I had to switch to using pthreads mutexes. This all by
-      itself smoothed out allocator performance under high load, since
-      the internal libc "spinlocks" aren't really spinlocks, whereas
-      malloc now spins for a bit before blocking.</p>
-
-      <p>I plan to MFC these changes to RELENG_7, hopefully in time for
-      the FreeBSD 7.1 release.</p>
-    <hr /><h2><a name="procstat(1)" href="#procstat(1)" id="procstat(1)">procstat(1)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new command line tool, procstat(1), allows detailed inspection
-      and printing of process properties, including file descriptors,
-      threads, kernel thread stacks, credentials, and virtual memory
-      mappings of processes. Several new sysctls have been added to the
-      kernel in order to export this information cleanly, and the
-      stack(9) facility has been enhanced to allow the capture of kernel
-      stacks from threads other than curthread. None of these features
-      depends on procfs, continuing the effort to remove a requirement
-      for procfs in order to print process information, as well as adding
-      new types of information not available with procfs. Kernel stack
-      printing is particularly useful as it provides much more detailed
-      information on why a thread is blocked in kernel beyond the useful
-      but limited wmesg context provided to date. This is helpful in
-      debugging both user process problems and kernel problems. procstat
-      has been merged into FreeBSD 8-CURRENT, and will be merged to
-      7-STABLE after FreeBSD 7.0 is released.</p>
-    <h3>Open tasks:</h3><ol><li>Merge to RELENG_7.</li><li>Add a mode to print process signal disposition.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Ports-2.0" href="#Ports-2.0" id="Ports-2.0">Ports 2.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Aryeh
-
-          Friedman
-         &lt;<a href="mailto:aryeh.friedman@gmail.com">aryeh.friedman@gmail.com</a>&gt;
-	<br />
-	Contact:
-          Alejandro
-
-          Pulver
-         &lt;<a href="mailto:alepulver@FreeBSD.org">alepulver@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          David
-
-          Southwell
-         &lt;<a href="mailto:david@vizion2000.net">david@vizion2000.net</a>&gt;
-	</p>
-      <p>Completed initial requirements gathering. Selection of
-      development tools complete. General internal design complete.</p>
-
-      <p>Ports 2.0 goals are:</p>
-
-      <ul>
-        <li>Re-engineer/modernize the ports build process using graph
-        theory and more flexible depends calculations.</li>
-
-        <li>Better document ports 1.0 and 2.0</li>
-
-        <li>Maintain 100% user level compatibility with ports 1.0</li>
-
-        <li>After a long trial period replace ports 1.0 in the "base
-        system"</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Create engine</li><li>Combine ports 1.0 docs from porters guide and the handbook
-      into a single guide</li><li>Create a proof of concept by building xorg (including all
-      dependanicies) under the new system</li><li>Create mailing list and web site</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports count continues to accelerate and is now over 18,000.
-      The PR count, which had dipped to around 750 before the 6.3/7.0
-      freeze, is now back up to about 1000, due to the fact that we
-      remain in ports slush.</p>
-
-      <p>Because of the freeze/slush, no experimental ports runs have
-      been committed since the last report. Although 2 more -exp runs
-      have been completed, we are waiting for 7.0R to commit them.</p>
-
-      <p>Once 7.0R happens, a lot of chaos is going to happen in the
-      Ports Collection. This has built up during the long release cycle.
-      Get ready for the following changes, among others:</p>
-
-      <ul>
-        <li>upgrade of KDE to 4.0 (being tested)</li>
-
-        <li>upgrade to gettext</li>
-
-        <li>upgrade to libtool</li>
-
-        <li>introduction of perl 5.10</li>
-
-        <li>final removal of XFree86 (deprecated for quite some
-        time)</li>
-
-        <li>removal of other expired ports</li>
-      </ul>
-
-      <p>Most of the portmgr activity was related to the QA process for
-      the releases. In addition, linimon spent quite some time trying to
-      get the sparc64 ports into better shape, and sent out a request for
-      more people to help test sparc64 ports. Some people have responded
-      with offers for letting committers get accounts on their machines.</p>
-
-      <p>Unfortunately during this time period, we became unable to build
-      packages for ia64-7. As a result, we are not currently building
-      packages for ia64 any more. If any one wants to step up to work on
-      this architecture, let portmgr know.</p>
-
-      <p>We are currently building packages for amd64-5, amd64-6,
-      amd64-7, amd64-8, i386-5, i386-6, i386-7, i386-8, sparc64-6, and
-      sparc64-7. Note, however, that RELENG_5 will reach the end of its
-      supported life on May 31, and package builds for those 2 buildenvs will stop
-      as of that date. (8 buildenvs * 18,000 ports should be enough to
-      keep us busy.)</p>
-
-      <p>Other than that, the packages are in the best shape that they
-      have been in for some time. linimon continues to work on package
-      analysis tools for portsmon.</p>
-
-      <p>We have added 2 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have over
-      4,000 unmaintained ports (see, for instance, the list on portsmon).
-      We are always looking for dedicated volunteers to adopt at least a
-      few unmaintained ports. As well, the packages on amd64 and sparc64
-      lag behind i386, and we need more testers for those.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="Bug-Busting" href="#Bug-Busting" id="Bug-Busting">Bug Busting</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/support.html#gnats" title="http://www.freebsd.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.freebsd.org/support.html#gnats" title="GNATS">http://www.freebsd.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.freebsd.org/BugBusting/Resources" title="http://wiki.freebsd.org/BugBusting/Resources">BugBusting Resources</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/BugBusting/Resources" title="BugBusting Resources">http://wiki.freebsd.org/BugBusting/Resources</a></td></tr><tr><td><a href="http://wiki.freebsd.org/Bugathons/January2008" title="http://wiki.freebsd.org/Bugathons/January2008">January 2008 Bugathon</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Bugathons/January2008" title="January 2008 Bugathon">http://wiki.freebsd.org/Bugathons/January2008</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister_at_FreeBSD_dot_org">bugmeister_at_FreeBSD_dot_org</a>&gt;
-	</p>
-    <p>As a result of a posting on freebsd-current@ complaining about a
-    communication gap between users and developers, there has been a
-    great deal of new interest in working on bugbusting -- in particular,
-    we brainstormed on ideas on how non-committers can help. The two main
-    ideas that are being discussed are incoming bug triage (classifying,
-    rating, and so forth), and working with users (helping users to work
-    through problems that aren't classical Problem Reports.</p>
-
-    <p>As a result of this, we held our first Bugathon in quite some time
-    (on #freebsd-bugbusters on EFNet). Over 30 people participated. As a
-    result of this, over 120 PRs were closed, and dozens more were put
-    into the 'feedback' state. Most of these PRs were in the kern/ and
-    bin/ categories, which are the two that need the most work. (The new
-    arrival rate was over 40/day during this time, including ports, so
-    there was a significant net decrease.)</p>
-
-    <p>Several new wiki pages were created to support this effort, and
-    finally capture a lot of the previous discussions from both the
-    mailing list and the IRC channel. There are even more good ideas
-    which Mark Linimon has promised to work up and investigate,
-    including:</p>
-    <ul>
-      <li>a web page to show "last N days of PRs"</li>
-
-      <li>some way for committers to only view PRs that have been in some
-      way 'vetted' or 'confirmed'</li>
-
-      <li>more publicity for what we've already got in place, and for
-      what we intend to do next</li>
-
-      <li>new categories, classifications, and states for PRs, that will
-      better match our workflow</li>
-    </ul>
-
-    <p>Note: at this time we are not yet looking to replace GNATS. The
-    idea right now is to see what we can learn about how our workflow
-    does (and ought to) work, and experiment with some low-cost changes
-    to get various people's reactions. Linimon's feeling is that any of
-    these kinds of changes would carry over to a new system, if we were
-    to change over.</p>
-
-    <p>rwatson also created a wiki page to put down some thoughts about
-    how to work on the various kernel problems that are reported.
-    Although preliminary, this captures some expertise and puts it into a
-    place where prospective volunteers can more easily find it.</p>
-
-    <p>The overall PR count is back up to just under 5300. Although this
-    is net increase from the previous report, there were long periods of
-    src and ports freeze during this time, which creates a spike in the
-    overall count. (src and ports both remain in slush during that time).
-    The peak number was approaching 5500.</p>
-
-    <p>Overall, we seem to have some momentum and new volunteers
-    interested in working on user-reported problems. bugmeister is
-    hopeful that we can capitalize on this and make some good progress in
-    the rest of 2008.</p>
-    <hr /><h2><a name="FreeBSD-Mirror-Site-Status" href="#FreeBSD-Mirror-Site-Status" id="FreeBSD-Mirror-Site-Status">FreeBSD Mirror Site Status</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mavetju.org/unix/ftp-stats.php" title="http://www.mavetju.org/unix/ftp-stats.php"></a></td><td>
-	    URL: <a href="http://www.mavetju.org/unix/ftp-stats.php" title="">http://www.mavetju.org/unix/ftp-stats.php</a></td></tr></table><p>
-	Contact:
-          Edwin
-
-          Groothuis
-         &lt;<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are several websites already with overview of the FreeBSD
-      FTP mirrror sites, but they all seem to have one problem: They are
-      not manually updated with the list of sites. For example,
-      http://mirrorlist.freebsd.org/FBSDsites.php, despite being hosted
-      by an Australia, doesn't have the Australian mirrors on it, while
-      http://people.freebsd.org/~kuriyama/mirrors/ doesn't tell you which
-      files are available from there. The data on my page shows the
-      availability of the ISO images on all FTP mirror sites. The list of
-      FTP mirror sites is obtained from DNS by either doing a
-      zone-transfer or by just trying the standard names. The first data
-      block shows a quick overview of the availability of the ISO image
-      directories per server, architecture and mirror site. The second
-      data block shows a verbose availability of the contents of the ISO
-      image directories per server.</p>
-    <h3>Open tasks:</h3><ol><li>The next addition will be the availability of the pre-build
-      packages.</li></ol><hr /><h2><a name="Opensource-Solutions-'08" href="#Opensource-Solutions-'08" id="Opensource-Solutions-'08">Opensource Solutions '08</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.solutionslinux.fr/en/" title="http://www.solutionslinux.fr/en/"></a></td><td>
-	    URL: <a href="http://www.solutionslinux.fr/en/" title="">http://www.solutionslinux.fr/en/</a></td></tr></table><p>
-	Contact:
-          Mathieu
-
-          Arnold
-         &lt;<a href="mailto:mat@FreeBSD.org">mat@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Ollivier
-
-          Robert
-         &lt;<a href="mailto:roberto@FreeBSD.org">roberto@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Thierry
-
-          Thomas
-         &lt;<a href="mailto:thierry@FreeBSD.org">thierry@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Rodrigo
-
-          Osorio
-         &lt;<a href="mailto:rodrigo@bebik.net">rodrigo@bebik.net</a>&gt;
-	</p>
-      <p>Like every year for the past few years is held what in France is
-      mostly called "Solutions Linux" in Paris La D�fense. The exhibition
-      will take place the 29, 30 and 31st of January in the CNIT.</p>
-
-      <p>The interesting thing about this event is that 80% of the floor
-      is taken by companies (IBM, Novell, Oracle), and the remaining 20%
-      is given freely to associations and non-profit organizations, where
-      you'll find many (if not most) french LUGs, *BSDs, most Linux
-      distributions, Mozilla, OOo...</p>
-
-      <p>This year, FreeBSD will once again have a booth, and we'll be
-      showing what FreeBSD is, why it's the damn best OS out there. We'll
-      also be distributing flyers and CD's for the whole three days</p>
-
-      <p>Admission to the exhibitions is free, so if you ever happen to
-      pass by, come and see us, we'll be at booth A39.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2008-01-2008-03.html b/website/content/en/status/report-2008-01-2008-03.html
deleted file mode 100644
index ec1c841207..0000000000
--- a/website/content/en/status/report-2008-01-2008-03.html
+++ /dev/null
@@ -1,760 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This Status Report covers FreeBSD related projects between January
-    and March 2008. During this time FreeBSD 7.0 was released.
-    <a href="http://www.bsdcan.org/" shape="rect">BSDCan</a>
-
-    is upon us with the Developer Summit starting the 14th and the
-    Conference starting the 16th.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#finstall---Graphical-installer-for-FreeBSD">finstall - Graphical installer for FreeBSD</a></li><li><a href="#Summer-of-Code">Summer of Code</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#ProPolice-support-for-FreeBSD">ProPolice support for FreeBSD</a></li><li><a href="#Rewriting-the-TTY-layer">Rewriting the TTY layer</a></li><li><a href="#USB">USB</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li><li><a href="#The-Ports-Collection">The Ports Collection</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Multi-IPv4/v6/no-IP-jails">Multi-IPv4/v6/no-IP jails</a></li><li><a href="#UnionFS-Improvements">UnionFS Improvements</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Ideas-Web-Application">Ideas Web Application</a></li><li><a href="#The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></li><li><a href="#The-Spanish-Documentation-Project">The Spanish Documentation Project</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="finstall---Graphical-installer-for-FreeBSD" href="#finstall---Graphical-installer-for-FreeBSD" id="finstall---Graphical-installer-for-FreeBSD">finstall - Graphical installer for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/finstall" title="http://wiki.freebsd.org/finstall"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/finstall" title="">http://wiki.freebsd.org/finstall</a></td></tr><tr><td><a href="http://sourceforge.net/projects/finstall" title="http://sourceforge.net/projects/finstall"></a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/finstall" title="">http://sourceforge.net/projects/finstall</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@freebsd.org">ivoras@freebsd.org</a>&gt;
-	</p>
-      <p>"finstall" is a graphical installer project for FreeBSD,
-      sponsored by Google during the 2007 Summer of Code. Its goal is to
-      create a modern installer, usable by both novice users and experts.
-      Because it is divided into front end and back end, it can
-      potentially be used for advanced purposes as system configuration,
-      remote and custom installs, etc. The project has resulted in a
-      simple installer ISO image for i386 that can be used for new
-      installations on empty hard drives. Development has continued
-      post-SoC but somewhat slowly; recently implemented features include
-      ZFS support and BSDStats support. To attract more potential
-      developers (especially those without an account on FreeBSD's
-      official development systems), the project has moved to
-      SourceForge. Future development plans include support for headless
-      / remote installs, partitioning, etc. Talks about finstall will be
-      given at BSDCan 2008.</p>
-    <h3>Open tasks:</h3><ol><li>Remote / headless install support.</li><li>Better partitioning support in the front end.</li><li>GPT boot support.</li><li>Fine grained package selection support.</li></ol><hr /><h2><a name="Summer-of-Code" href="#Summer-of-Code" id="Summer-of-Code">Summer of Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/summerofcode.html" title="http://www.FreeBSD.org/projects/summerofcode.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/summerofcode.html" title="">http://www.FreeBSD.org/projects/summerofcode.html</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SummerOfCode" title="http://wiki.freebsd.org/SummerOfCode"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SummerOfCode" title="">http://wiki.freebsd.org/SummerOfCode</a></td></tr></table><p>
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The student application period for the Summer of Code is over
-      and the mentors and administrators are carefully reviewing the
-      applications, clarifying the project parameters, and deciding which
-      students to recommend for funding from Google.</p>
-
-      <p>This year we received over 100 student applications from
-      students in 26 different countries. We also have over 60 potential
-      mentors that we are currently matching up with students. We will
-      soon announce the winning students on the summer of code website
-      and the process of bringing these students into our development
-      community will begin.</p>
-
-      <p>Each student will again be given Perforce and wiki access and
-      all developers are encouraged to contact any students working in
-      related areas, as we don't want the students to have access to our
-      community only through their formal assigned mentor.</p>
-    <h3>Open tasks:</h3><ol><li>Help introduce our new summer of code students to FreeBSD
-      development. Some students are very experienced at developing on
-      FreeBSD and others are new to our environment and could use more
-      assistance.</li><li>Update the ideas database with new project ideas that you'd
-      like to see for next year's Summer of Code.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="ProPolice-support-for-FreeBSD" href="#ProPolice-support-for-FreeBSD" id="ProPolice-support-for-FreeBSD">ProPolice support for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://tataz.chchile.org/~tataz/FreeBSD/SSP/" title="http://tataz.chchile.org/~tataz/FreeBSD/SSP/">FreeBSD/SSP</a></td><td>
-	    URL: <a href="http://tataz.chchile.org/~tataz/FreeBSD/SSP/" title="FreeBSD/SSP">http://tataz.chchile.org/~tataz/FreeBSD/SSP/</a></td></tr></table><p>
-	Contact:
-          J�r�mie
-
-          Le Hen
-         &lt;<a href="mailto:jeremie@le-hen.org">jeremie@le-hen.org</a>&gt;
-	</p>
-      <p>This patch modifies the build infrastructure in order to use
-      GCC's stack-smashing protection (SSP, aka ProPolice) when building
-      world, kernel and ports. Don't forget to see the website and
-      especially the FAQ for a list of ports that fail to build with
-      ProPolice. The patch extends the meaning of src.conf(5) WITHOUT_SSP
-      so as to prevent both building libssp and using ProPolice when
-      compiling. An interesting thing to note is that libssp is GNU
-      licensed (it is provided with GCC 4.2.1) but since libc includes
-      the mandatory symbols, programs won't be linked against GNU libssp.
-      A new knob USE_SSP has been also added for the ports
-      infrastructure, you can set it to "yes" in make.conf(5) and use
-      <tt>USE_SSP=</tt>
-
-      on command-line to disable ProPolice for some ports. The patch has
-      been reviewed and should hopefully be committed soon. The port part
-      hasn't been reviewed yet, though.</p>
-    <hr /><h2><a name="Rewriting-the-TTY-layer" href="#Rewriting-the-TTY-layer" id="Rewriting-the-TTY-layer">Rewriting the TTY layer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=7ru@//depot/user/ed/mpsafetty/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=7ru@//depot/user/ed/mpsafetty/?ac=83">Perforce branch</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=7ru@//depot/user/ed/mpsafetty/?ac=83" title="Perforce branch">http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=7ru@//depot/user/ed/mpsafetty/?ac=83</a></td></tr></table><p>
-	Contact:
-          Ed
-
-          Schouten
-         &lt;<a href="mailto:ed@80386.nl">ed@80386.nl</a>&gt;
-	</p>
-      <p>About 10 weeks ago I started rewriting the TTY layer. The
-      existing TTY code is about 20-25 years old and has been extended
-      over and over, without really improving its design.</p>
-
-      <p>The new TTY layer will allow us to remove usage of the Giant
-      from drivers. It also includes an improved buffering mechanism,
-      which has more constant-time operations and prevents copying data
-      multiple times when moving data to userspace.</p>
-
-      <p>Right now the code should work quite well for most users. The
-      code in Perforce includes a new pseudo-TTY driver, which is finally
-      capable of destroying TTY's and their associated buffers when
-      needed. The syscons, uart and ucom drivers have also been ported to
-      the new TTY layer.</p>
-
-      <p>The code is quite complete, but it still misses driver
-      interaction for carrier/connection detection and sending breaks.
-      Many drivers still need to be ported.</p>
-    <h3>Open tasks:</h3><ol><li>People who are willing to test. Contact me if you cannot
-      perform Perforce checkouts.</li><li>Not all drivers have been ported. Patches or hardware are
-      welcome.</li><li>Some changes could already be backported.</li></ol><hr /><h2><a name="USB" href="#USB" id="USB">USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;c=A2y@//depot/projects/usb/src/sys/dev/usb/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;c=A2y@//depot/projects/usb/src/sys/dev/usb/?ac=83">Current USB files</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;c=A2y@//depot/projects/usb/src/sys/dev/usb/?ac=83" title="Current USB files">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;c=A2y@//depot/projects/usb/src/sys/dev/usb/?ac=83</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;cdf=//depot/projects/usb/src/sys/dev/usb/README&amp;sr=136513&amp;c=2Ro@//depot/projects/usb/src/sys/dev/usb/README" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;cdf=//depot/projects/usb/src/sys/dev/usb/README&amp;sr=136513&amp;c=2Ro@//depot/projects/usb/src/sys/dev/usb/README">Current USB API README file</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;cdf=//depot/projects/usb/src/sys/dev/usb/README&amp;sr=136513&amp;c=2Ro@//depot/projects/usb/src/sys/dev/usb/README" title="Current USB API README file">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb/&amp;cdf=//depot/projects/usb/src/sys/dev/usb/README&amp;sr=136513&amp;c=2Ro@//depot/projects/usb/src/sys/dev/usb/README</a></td></tr><tr><td><a href="http://www.selasky.org/hans_petter/usb4bsd" title="http://www.selasky.org/hans_petter/usb4bsd">Install instructions</a></td><td>
-	    URL: <a href="http://www.selasky.org/hans_petter/usb4bsd" title="Install instructions">http://www.selasky.org/hans_petter/usb4bsd</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>&gt;
-	</p>
-      <p>During the last three months there has mostly been bugfix and
-      documentation commits. The code is currently in a stable and full
-      featured state. The FreeBSD P4 USB project now has a fully
-      symmetric USB stack at API level and has been tested to work with
-      AT91RM9200 ARM based boards and USS820 based devices. There are
-      currently two USB device side drivers implemented, namely CDC
-      Ethernet and Mass Storage (SCSI+BBB) so that you can now make your
-      custom USB Flash Disk using FreeBSD. Don't confuse USB device side
-      drivers with USB host side drivers.</p>
-
-      <p>Currently the USB P4 project is under review.</p>
-
-      <p>Ideas and comments with regard to the new USB API are welcome on
-      the FreeBSD
-      <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-usb" shape="rect">USB
-      Mailing List</a>
-
-      .</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/support.html#gnats" title="http://www.freebsd.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.freebsd.org/support.html#gnats" title="GNATS">http://www.freebsd.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.freebsd.org/BugBusting/Resources" title="http://wiki.freebsd.org/BugBusting/Resources">BugBusting Resources</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/BugBusting/Resources" title="BugBusting Resources">http://wiki.freebsd.org/BugBusting/Resources</a></td></tr><tr><td><a href="http://wiki.freebsd.org/Bugathons/February2008" title="http://wiki.freebsd.org/Bugathons/February2008">February 2008 Bugathon</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Bugathons/February2008" title="February 2008 Bugathon">http://wiki.freebsd.org/Bugathons/February2008</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/recentprs.txt" title="http://people.freebsd.org/~linimon/studies/prs/recentprs.txt">new PRs in the last 7 days</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/recentprs.txt" title="new PRs in the last 7 days">http://people.freebsd.org/~linimon/studies/prs/recentprs.txt</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.txt" title="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.txt">PRs recommended for committer evaluation</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.txt" title="PRs recommended for committer evaluation">http://people.freebsd.org/~linimon/studies/prs/recommended_prs.txt</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/stalefeedback.txt" title="http://people.freebsd.org/~linimon/studies/prs/stalefeedback.txt">feedback PRs with no change in 2 months</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/stalefeedback.txt" title="feedback PRs with no change in 2 months">http://people.freebsd.org/~linimon/studies/prs/stalefeedback.txt</a></td></tr></table><p>
-	Contact:
-          Ceri
-
-          Davies
-         &lt;<a href="mailto:bugmeister_at_freebsd_dot_org">bugmeister_at_freebsd_dot_org</a>&gt;
-	<br />
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:bugmeister_at_freebsd_dot_org">bugmeister_at_freebsd_dot_org</a>&gt;
-	<br />
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister_at_freebsd_dot_org">bugmeister_at_freebsd_dot_org</a>&gt;
-	</p>
-      <p>As one of the results of our January and February bugathons, we
-      have granted Volker Werth (vwe@) direct access to GNATS. During the
-      past few months he has been instrumental in working on several
-      hundred PRs (mainly src-related), and either closing them or
-      helping users work through issues they are having. There have been
-      several commits to the src tree that directly resulted from this.
-      Welcome Volker!</p>
-
-      <p>As well, several new people are assisting us in classifying
-      incoming PRs, working with users, and reviewing patches. Among the
-      most active are Bruce Cran, Dylan Cochran, and Harrison Grundy. We
-      appreciate everyone's efforts.</p>
-
-      <p>As a direct result of the above, we have been able to hold the
-      overall PR count down to around 5300 (the peak was around 5500).
-      despite the facts that PR submissions have jumped recently, and the
-      ports PR backlog is a little higher than recent trends (due to the
-      long freeze/slush cycle). What is most encouraging, however, is not
-      the absolute number, as much as that we are handling incoming PRs
-      much more quickly and completely. While we are still not where we
-      need to be, this trend is very encouraging.</p>
-
-      <p>As well, The Bugbusting Team has learned some lessons about how
-      we can best involve new people in bugbusting, e.g., how to best
-      leverage people who have varying levels of experience and areas of
-      interest. Our old response of "just look through the bug reports
-      and let us know if you see anything that needs doing" tends to
-      discourage all but the most highly-motivated. Some of these ideas
-      are being studied to figure how to change our process flow.</p>
-
-      <p>There are still a number of good technical suggestions from the
-      two Bugathons that need to be written up and discussed. The first
-      few have resulted in the following: there are a few new web pages
-      that include: new PRs in the last 7 days; the web representation of
-      the "recommended by bugbusting team" list; and "PRs in feedback
-      with no change for 2 months". (See above). Many more need to be
-      added.</p>
-
-      <p>Much of the work of the second Bugathon was in identifying and
-      closing PRs for which fixes had already been committed. Others were
-      identified and relabled as 'patched' to move them along.</p>
-    <h3>Open tasks:</h3><ol><li>Think of some way for committers to only view PRs that have
-      been in some way 'vetted' or 'confirmed.'</li><li>Generate more publicity for what we've already got in place,
-      and for what we intend to do next.</li><li>Define new categories, classifications, and states for PRs,
-      that will better match our workflow.</li></ol><hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org" title="http://www.freebsdfoundation.org">The FreeBSD Foundation Website</a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org" title="The FreeBSD Foundation Website">http://www.freebsdfoundation.org</a></td></tr><tr><td><a href="http://www.freebsdfoundation.org/subscribe.shtml" title="http://www.freebsdfoundation.org/subscribe.shtml">FreeBSD Foundation Mailing List</a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org/subscribe.shtml" title="FreeBSD Foundation Mailing List">http://www.freebsdfoundation.org/subscribe.shtml</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@FreeBSD.org">deb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The foundation provided legal counsel for the project to
-      understand the impact of GPLv3 on the project and to create a
-      policy on software licenses. We approved a budget of $250,000 for
-      2008. We were a sponsor for AsiaBSDCon and provided travel grants
-      to three people to attend the conference. We are a sponsor for
-      BSDCan and the BSDCan Developer Summit. We have approved travel
-      grants for 10 people to attend BSDCan. We are supporting projects
-      that will provide Java 1.6 binaries for FreeBSD 6.3 and 7.0. Join
-      our mailing list to receive monthly updates. See you at BSDCan!</p>
-    <hr /><h2><a name="The-Ports-Collection" href="#The-Ports-Collection" id="The-Ports-Collection">The Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>portmgr is pleased to announce that Florent Thoumie (flz) has
-      joined us. We immediately put him to work on cleaning up the pkg_*
-      tools.</p>
-
-      <p>After the extended freeze and then slush for 7.0R, we have
-      finally been able to start catching up on the backlog that built up
-      during that time.</p>
-
-      <p>The ports count is now over 18,200. The PR count has only
-      dropped to around 1000. We are still turning around PRs fairly
-      quickly, but are not making progress on the backlog.</p>
-
-      <p>We have only been able to do 2 -exp runs recently. Although a
-      number of PRs have been closed, we are still at 57 portmgr PRs.</p>
-
-      <p>During this period, GNOME has been updated to 2.22.0. Also, a
-      new port for linux emulation (emulators/linux_base-f8) has been
-      introduced for general testing.</p>
-
-      <p>XFree86 has been removed. (It had been deprecated for quite some
-      time; modern development seems to be happening in X.Org.) This
-      simplifies the infrastructure. A few other stale ports have been
-      reaped.</p>
-
-      <p>The following large changes are in the pipeline:</p>
-
-      <ul>
-        <li>Upgrade of KDE to 4.0 (being tested)</li>
-
-        <li>Upgrade of automake to 1.10.1</li>
-
-        <li>Upgrade of gettext to 0.17</li>
-
-        <li>Upgrade of libtool to 1.5.26 (not 2.x at this time)</li>
-
-        <li>Upgrade of m4 to 1.14.11</li>
-
-        <li>Introduction of Perl 5.10</li>
-      </ul>
-
-      <p>We are currently building packages for amd64-5, amd64-6,
-      amd64-7, amd64-8, i386-5, i386-6, i386-7, i386-8, sparc64-6, and
-      sparc64-7. Note, however, that RELENG_5 will reach end of its
-      supported life May 31, 2008, and package builds for those 2
-      buildenvs will stop as of that date.</p>
-
-      <p>We have been able to use some new machines to speed up the
-      package builds (in particular, amd64) -- in fact, to the point that
-      we are now outrunning the capacity of some of the mirrors to stay
-      current. A solution for the problem is being investigated.</p>
-
-      <p>We have added 4 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have over
-      4,000 unmaintained ports (see, for instance, the list on portsmon).
-      We are always looking for dedicated volunteers to adopt at least a
-      few unmaintained ports. As well, the packages on amd64 and sparc64
-      lag behind i386, and we need more testers for those.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Multi-IPv4/v6/no-IP-jails" href="#Multi-IPv4/v6/no-IP-jails" id="Multi-IPv4/v6/no-IP-jails">Multi-IPv4/v6/no-IP jails</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sources.zabbadoz.net/freebsd/jail.html" title="http://sources.zabbadoz.net/freebsd/jail.html">Webpage for regularly updates and patches</a></td><td>
-	    URL: <a href="http://sources.zabbadoz.net/freebsd/jail.html" title="Webpage for regularly updates and patches">http://sources.zabbadoz.net/freebsd/jail.html</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50">Perforce tree</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50" title="Perforce tree">http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50</a></td></tr></table><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The multi-IPv4/v6 jails project was resumed in early January
-      after previous work had been abandoned in 2006.</p>
-
-      <p>As an alternate solution to full network stack virtualization,
-      this work shall provide a lightweight solution for multi-IP
-      virtualization. The changes are even more important because of the
-      emerging demand for IPv6.</p>
-
-      <p>The current status includes updated user space utilities. Kernel
-      side has grown support for multiple IP addresses for both address
-      families in jails, as well as no IP addresses at all. 32bit and
-      jail version 1 backward compatibility support were implemented.</p>
-
-      <p>The development was moved to perforce and patches for early
-      adopters are available.</p>
-    <h3>Open tasks:</h3><ol><li>The TODO list can be found in the TODO file in
-      perforce.</li><li>Regression tests and review.</li></ol><hr /><h2><a name="UnionFS-Improvements" href="#UnionFS-Improvements" id="UnionFS-Improvements">UnionFS Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~daichi/unionfs/" title="http://people.freebsd.org/~daichi/unionfs/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~daichi/unionfs/" title="">http://people.freebsd.org/~daichi/unionfs/</a></td></tr></table><p>
-	Contact:
-          Daichi
-
-          GOTO
-         &lt;<a href="mailto:daichi@freebsd.org">daichi@freebsd.org</a>&gt;
-	<br />
-	Contact:
-          Masanori
-
-          OZAWA
-         &lt;<a href="mailto:ozawa@ongs.co.jp">ozawa@ongs.co.jp</a>&gt;
-	</p>
-      <p>Our implementation of UnionFS has been merged into HEAD,
-      7-stable and 6-stable already. Now we are working on UnionFS
-      stability improvement. We have developed the following 5 patches.
-      If you are interested, please try them and report your results.</p>
-      <ul>
-        <li>
-          <a href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-1.diff" shape="rect">
-          unionfs-p20-1.diff</a>
-        </li>
-
-        <li>
-          <a href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-2.diff" shape="rect">
-          unionfs-p20-2.diff</a>
-        </li>
-
-        <li>
-          <a href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-3.diff" shape="rect">
-          unionfs-p20-3.diff</a>
-        </li>
-
-        <li>
-          <a href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-4.diff" shape="rect">
-          unionfs-p20-4.diff</a>
-        </li>
-
-        <li>
-          <a href="http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-5.diff" shape="rect">
-          unionfs-p20-5.diff</a>
-        </li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Robert Watson has pointed out that unionfs-p20-5.diff has
-      some problems around how it treats sockets. We are researching
-      those.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Ideas-Web-Application" href="#Ideas-Web-Application" id="Ideas-Web-Application">Ideas Web Application</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://apps.stokely.org/ideas/" title="http://apps.stokely.org/ideas/">Idea Database</a></td><td>
-	    URL: <a href="http://apps.stokely.org/ideas/" title="Idea Database">http://apps.stokely.org/ideas/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/IdeasWebApp" title="http://wiki.freebsd.org/IdeasWebApp">Design Document</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/IdeasWebApp" title="Design Document">http://wiki.freebsd.org/IdeasWebApp</a></td></tr></table><p>
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	</p>
-      <p>A prototype web application has been written for the
-      http://www.FreeBSD.org website which allows authenticated users to
-      add new development ideas or comment and vote on ideas added by
-      others. This application is a proposed replacement for the static
-      webpage that is currently maintained with project ideas for summer
-      of code students and others looking to get involved with
-      FreeBSD.</p>
-
-      <p>Some of the features currently available include:</p>
-
-      <ul>
-        <li>Allows anyone to propose a new idea.</li>
-
-        <li>Allows anyone to comment and vote on previously proposed
-        ideas.</li>
-
-        <li>Provides an RSS feed of the newest ideas.</li>
-
-        <li>Provides an RSS feed of the comments/votes for any specific
-        idea.</li>
-
-        <li>Allows one to sort and search the ideas list by category,
-        proposer, votes, summary title, or full text, and subscribe to
-        RSS feed of search results.</li>
-
-        <li>Anonymous ideas/comments are hidden by default until cleared
-        by a moderator.</li>
-
-        <li>Moderator bits to be set for certain users so that they can
-        moderate the above (can subscribe to an rss file for unmoderated
-        ideas and comments needing their attention).</li>
-
-        <li>Import functionality to import the current ideas.xml
-        file.</li>
-
-        <li>Graphs and statistics about the ideas in the database are
-        provided.</li>
-      </ul>
-
-      <p>The code is checked into perforce under
-      <strong>//depot/user/murray/www/apps/django/ideas/...</strong>
-
-      and I would eventually like to see this hosted on FreeBSD.org
-      hardware, linked from the main website, and checked into
-      <strong>www/apps/django/ideas</strong>.</p>
-    <h3>Open tasks:</h3><ol><li>A thorough security review of the code is needed. If you have
-      experience with reviewing web applications for sql injection,
-      cross-site scripting, and other vulnerabilities please contact me.
-      The application uses the Django framework.</li><li>Better import/export tools to get the data from our current
-      ideas.xml web app into the database and back out again.</li><li>More usability review and suggestions needed to make this a
-      compelling replacement to the current static XML system.</li></ol><hr /><h2><a name="The-Hungarian-Documentation-Project" href="#The-Hungarian-Documentation-Project" id="The-Hungarian-Documentation-Project">The Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.org/hu" title="http://FreeBSD.org/hu">Hungarian website</a></td><td>
-	    URL: <a href="http://FreeBSD.org/hu" title="Hungarian website">http://FreeBSD.org/hu</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/" title="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/">Hungarian articles</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/" title="Hungarian articles">http://www.freebsd.org/doc/hu_HU.ISO8859-2/articles/</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are pleased to welcome G�bor P�li as a doc committer. He has
-      successfully completed the translation of the
-      FreeBSD�Handbook. The final review of his work is pending now
-      and we will import it soon to the repository. We consider the
-      translation of the release notes the next important milestone of
-      this translation project.</p>
-    <h3>Open tasks:</h3><ol><li>Review the translated Handbook.</li><li>Translate release notes for -CURRENT and 7.X.</li></ol><hr /><h2><a name="The-Spanish-Documentation-Project" href="#The-Spanish-Documentation-Project" id="The-Spanish-Documentation-Project">The Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.org/es" title="http://FreeBSD.org/es">FreeBSD Spanish Website</a></td><td>
-	    URL: <a href="http://FreeBSD.org/es" title="FreeBSD Spanish Website">http://FreeBSD.org/es</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/es_ES.ISO8859-1/" title="http://www.freebsd.org/doc/es_ES.ISO8859-1/">Spanish Translations</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/es_ES.ISO8859-1/" title="Spanish Translations">http://www.freebsd.org/doc/es_ES.ISO8859-1/</a></td></tr></table><p>
-	Contact:
-          Jos� Vicente
-
-          Carrasco Vay�
-         &lt;<a href="mailto:carvay@FreeBSD.org">carvay@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are progressing better these days again. We have made some
-      updates to the website and to the Handbook, including the complete
-      translation of the jails chapter. We have also added a new
-      translation of an article and an another one is under review.</p>
-    <h3>Open tasks:</h3><ol><li>Complete updating of the website.</li><li>Update the Handbook and translate new chapters.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2008-04-2008-06.html b/website/content/en/status/report-2008-04-2008-06.html
deleted file mode 100644
index bfd728f0a4..0000000000
--- a/website/content/en/status/report-2008-04-2008-06.html
+++ /dev/null
@@ -1,780 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This Status Report covers FreeBSD related projects between April
-    and June 2008. During this period The FreeBSD Foundation has
-    released their <a href="http://www.freebsdfoundation.org/press/2008Jul-newsletter.shtml" shape="rect">July
-    Newsletter</a>.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Layer2-filtering">Layer2 filtering</a></li><li><a href="#Porting-BSD-licensed-text-processing-tools-from-OpenBSD">Porting BSD-licensed text-processing tools from
-    OpenBSD</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Build-cluster">Build cluster</a></li><li><a href="#finstall">finstall</a></li><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#Graphics-support-for-the-boot-loader">Graphics support for the boot loader</a></li><li><a href="#USB">USB</a></li></ul><h3><a href="#FreeBSD-Architecture">FreeBSD Architecture</a></h3><ul><li><a href="#ARM/Marvell-port">ARM/Marvell port</a></li></ul><h3><a href="#The-Ports-Collection">The Ports Collection</a></h3><ul><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Qt/KDE4-Status-Report">Qt/KDE4 Status Report</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-FAQ-Renovation">FreeBSD FAQ Renovation</a></li><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li><li><a href="#The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Layer2-filtering" href="#Layer2-filtering" id="Layer2-filtering">Layer2 filtering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/GlebKurtsov/Improving_layer2_filtering" title="http://wiki.freebsd.org/GlebKurtsov/Improving_layer2_filtering"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/GlebKurtsov/Improving_layer2_filtering" title="">http://wiki.freebsd.org/GlebKurtsov/Improving_layer2_filtering</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/gleb/" title="http://blogs.freebsdish.org/gleb/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/gleb/" title="">http://blogs.freebsdish.org/gleb/</a></td></tr></table><p>
-	Contact:
-          Gleb
-
-          Kurtsou
-         &lt;<a href="mailto:gk@FreeBSD.org">gk@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
-	</p>
-      <p>Project aims to improve layer2 filtering in ipfw and pf. So far
-      following project goals are achieved: pfil framework is extended to
-      handle ethernet packets, ipfw layer2 filtering is greatly
-      simplified, added l2filter and l2tag per interface flags. Both ipfw
-      and pf firewalls support filtering by ethernet addresses, support
-      stateful filtering with ethernet addresses and firewall's lookup
-      tables are extended to contain ethernet addresses.</p>
-    <h3>Open tasks:</h3><ol><li>Implement ARP filtering options in IPFW.</li></ol><hr /><h2><a name="Porting-BSD-licensed-text-processing-tools-from-OpenBSD" href="#Porting-BSD-licensed-text-processing-tools-from-OpenBSD" id="Porting-BSD-licensed-text-processing-tools-from-OpenBSD">Porting BSD-licensed text-processing tools from
-    OpenBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borSoC2008" title="http://wiki.freebsd.org/G%C3%A1borSoC2008">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/G%C3%A1borSoC2008" title="Wiki page">http://wiki.freebsd.org/G%C3%A1borSoC2008</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=Kqj@//depot/projects/soc2008/gabor_textproc/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=Kqj@//depot/projects/soc2008/gabor_textproc/?ac=83">Perforce depot</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=Kqj@//depot/projects/soc2008/gabor_textproc/?ac=83" title="Perforce depot">http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=Kqj@//depot/projects/soc2008/gabor_textproc/?ac=83</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The grep utility is ready for a thorough test on the portbuild
-      cluster. It is almost compatible with GNU grep, but there are
-      differences in the regex handling at the level of the regex
-      libraries of GNU and the base system one, thus a better
-      compatibility is very hard to implement.</p>
-
-      <p>Some progress has been made on diff, but some important options
-      are still missing. The sort utility seems to be very problematic in
-      the aspect of the wide character support by design, thus it was
-      given a lower priority.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the incomplete options of diff and optimize it.</li><li>Investigate about the opportunities to fix sort.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Build-cluster" href="#Build-cluster" id="Build-cluster">Build cluster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Kris
-
-          Kennaway
-         &lt;<a href="mailto:kris@FreeBSD.org">kris@FreeBSD.org</a>&gt;
-	</p>
-      <p>For the past couple of months I have been working on
-      generalizing the package build cluster to allow it to host other
-      batch and interactive jobs. Currently we make an inefficient use of
-      build machines because various projects have dedicated machines
-      that are either underloaded or overloaded for their particular
-      tasks. The goal is to provide a framework for combining all of
-      these machine resources into a single cluster that can be shared by
-      many users, reducing dead time and allowing distributed build tasks
-      to take advantage of extra build resources when available.
-      Developers will be able to obtain on-demand interactive access to a
-      jail running on any of the available architectures, with root
-      access. Similarly, batch jobs will specify their resource
-      requirements and be dispatched to run on a suitable machine in the
-      cluster. Current status: The job queue manager is working and is
-      now being used to map package builds to machines. Various package
-      build scripts have been rewritten to use it instead of the previous
-      build scheduler. The generic job dispatcher is being prototyped and
-      will be validated with several existing services such as INDEX
-      builds. Various support services like ZFS snapshot replication have
-      been written.</p>
-    <hr /><h2><a name="finstall" href="#finstall" id="finstall">finstall</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/finstall" title="http://wiki.freebsd.org/finstall"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/finstall" title="">http://wiki.freebsd.org/finstall</a></td></tr><tr><td><a href="http://www.sf.net/projects/finstall" title="http://www.sf.net/projects/finstall"></a></td><td>
-	    URL: <a href="http://www.sf.net/projects/finstall" title="">http://www.sf.net/projects/finstall</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@freebsd.org">ivoras@freebsd.org</a>&gt;
-	</p>
-      <p>Between the last report and this one, the project has yielded a
-      LiveCD installer for i386 containing FreeBSD 7.0-RELEASE. The
-      project was presented at BSDCan 2008. The development is
-      progressing slowly due to the lack of free time. I'm looking for
-      funding that will allow me more involvement in the project. The big
-      item currently in development is documentation and description of
-      the protocol used between the front-end and the back-end, which
-      will result in more robustness in the implementation and could
-      support third-party clients. This sub-project is near completion.
-      The project is currently hosted at SourceForge to allow
-      contribution from non-FreeBSD developers.</p>
-    <h3>Open tasks:</h3><ol><li>Partition editor.</li><li>Package selection.</li></ol><hr /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/support.html#gnats" title="http://www.freebsd.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.freebsd.org/support.html#gnats" title="GNATS">http://www.freebsd.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.freebsd.org/BugBusting" title="http://wiki.freebsd.org/BugBusting">BugBusting</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/BugBusting" title="BugBusting">http://wiki.freebsd.org/BugBusting</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html" title="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html">PRs indexed by manpage</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html" title="PRs indexed by manpage">http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html" title="http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html">PRs indexed by tag</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html" title="PRs indexed by tag">http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/prs_possibly_committed.html" title="http://people.freebsd.org/~linimon/studies/prs/prs_possibly_committed.html">PRs which may have already been committed</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/prs_possibly_committed.html" title="PRs which may have already been committed">http://people.freebsd.org/~linimon/studies/prs/prs_possibly_committed.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html" title="http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html">Well-Known PRs as determined by the bugbusting team</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html" title="Well-Known PRs as determined by the bugbusting team">http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html</a></td></tr><tr><td><a href="http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues" title="http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues">Commonly Reported Issues</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues" title="Commonly Reported Issues">http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues</a></td></tr></table><p>
-	Contact:
-          Ceri
-
-          Davies
-         &lt;<a href="mailto:bugmeister@">bugmeister@</a>&gt;
-	<br />
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:bugmeister@">bugmeister@</a>&gt;
-	<br />
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister@">bugmeister@</a>&gt;
-	</p>
-      <p>We have granted Bruce Cran (bruce@) direct access to GNATS and
-      Volker Werth (vwe@) has been released from mentorship. We
-      appreciate their help!</p>
-
-      <p>We had a third bugathon in June, which resulted in the closing
-      of a number of bugs and the investigation/classification of several
-      others. We are still trying to find ways to get more committers
-      helping us with closing PRs that the team has already analyzed.</p>
-
-      <p>We continue to make good progress in categorizing PRs as they
-      arrive with 'tags' that correspond to manpages. (Special thanks go
-      to Dylan Cochran for the help.) As a result, we now have created
-      some prototype reports that allow browsing the database
-      <url href="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html">
-      by manpage</url>.</p>
-
-      <p>In addition, another new report, oriented towards PR submitters,
-      summarizes the
-      <url href="http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html">
-      most commonly reported issues</url>.
-      Many of these issues persist because they are difficult to fix.
-      Before filing a PR, you may want to check through this list.</p>
-
-      <p>Mark Linimon summarized the good technical suggestions from the
-      bugathons so far this year to the wiki. As a part of this, he
-      rearranged the wiki pages, so if you have not seen them for a
-      while, please see
-      <url href="http://wiki.freebsd.org/BugBusting">BugBusting</url>.
-      In particular, the Resources page is much more complete.</p>
-
-      <p>Jeremy Chadwick (koitsu@) is now maintaining a
-      <url href="http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues">
-      page</url>
-
-      that summarizes some of the commonly reported issues. This
-      complements some of the reports, above, but includes a great deal
-      more information, including how-tos.</p>
-
-      <p>The overall PR count has been holding at around 5300 since the
-      last release.</p>
-    <h3>Open tasks:</h3><ol><li>Think of some way for committers to only view PRs that have
-      been in some way 'vetted' or 'confirmed'.</li><li>Generate more publicity for what we've already got in place,
-      and for what we intend to do next.</li><li>Define new categories, classifications, and states for PRs,
-      that will better match our workflow.</li></ol><hr /><h2><a name="Graphics-support-for-the-boot-loader" href="#Graphics-support-for-the-boot-loader" id="Graphics-support-for-the-boot-loader">Graphics support for the boot loader</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/OliverFromme/BootLoader" title="http://wiki.freebsd.org/OliverFromme/BootLoader"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/OliverFromme/BootLoader" title="">http://wiki.freebsd.org/OliverFromme/BootLoader</a></td></tr></table><p>
-	Contact:
-          Oliver
-
-          Fromme
-         &lt;<a href="mailto:olli@freebsd.org">olli@freebsd.org</a>&gt;
-	</p>
-      <p>This project aims to implement graphics support for FreeBSD's
-      boot loader. It will replace the existing ASCII menu. (Note that
-      the ASCII menu will still be available when graphics mode cannot be
-      used, such as on serial console or on unsupported hardware.)</p>
-
-      <p>For a more detailed description and screen shots please refer to
-      the project's Wiki URL above.</p>
-
-      <p>Progress is slow (due to lack of time) but steady. The code
-      currently lives in the Perforce repository. I'll try to prepare a
-      first public CFT as soon as possible.</p>
-    <h3>Open tasks:</h3><ol><li>Implement a platform switch.</li><li>Implement "themes" support (in FORTH).</li><li>Documentation.</li></ol><hr /><h2><a name="USB" href="#USB" id="USB">USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=oDu@//depot/projects/usb/src/sys/dev/usb2/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=oDu@//depot/projects/usb/src/sys/dev/usb2/?ac=83">Current USB files</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=oDu@//depot/projects/usb/src/sys/dev/usb2/?ac=83" title="Current USB files">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=oDu@//depot/projects/usb/src/sys/dev/usb2/?ac=83</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;cdf=//depot/projects/usb/src/sys/dev/usb2/core/README.TXT&amp;c=Vfw@//depot/projects/usb/src/sys/dev/usb2/core/README.TXT?ac=64&amp;rev1=2" title="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;cdf=//depot/projects/usb/src/sys/dev/usb2/core/README.TXT&amp;c=Vfw@//depot/projects/usb/src/sys/dev/usb2/core/README.TXT?ac=64&amp;rev1=2">Current USB API README file</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;cdf=//depot/projects/usb/src/sys/dev/usb2/core/README.TXT&amp;c=Vfw@//depot/projects/usb/src/sys/dev/usb2/core/README.TXT?ac=64&amp;rev1=2" title="Current USB API README file">http://p4web.freebsd.org/@md=d&amp;cd=//&amp;cdf=//depot/projects/usb/src/sys/dev/usb2/core/README.TXT&amp;c=Vfw@//depot/projects/usb/src/sys/dev/usb2/core/README.TXT?ac=64&amp;rev1=2</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>&gt;
-	</p>
-      <p>During the last three months there has been a number of changes.
-      Most notably all global USB symbols have been renamed to "usb2_" to
-      allow for co-existence with the old USB stack. Also there is now a
-      completely new and reworked UGEN driver which allows multiple
-      drivers to hook onto the same USB device. No more need to unload
-      any kernel drivers. For example it is now possible to have a
-      userland Mouse driver stealing half of the mouse events at the same
-      time "ums" is loaded. The only disadvantage is that your mouse
-      cursor will move slower on the screen. This is maybe not the most
-      common use-case, but it illustrates that kernel USB drivers are no
-      longer locking out other USB userland drivers. A new userland
-      libusb is in the works for FreeBSD. The USB stack now also has
-      support for independent USB BUS, USB Device, and USB Interface
-      permissions. That means you can more easily give USB permissions to
-      USB device drivers at either USB BUS, USB Device or USB Interface
-      level. All USB modules have now been grouped into functional
-      categories: usb2_bluetooth, usb2_ndis, usb2_controller, usb2_quirk,
-      usb2_core, usb2_serial, usb2_ethernet, usb2_sound, usb2_image,
-      usb2_storage, usb2_input, usb2_template, usb2_misc, and
-      usb2_wlan.</p>
-
-      <p>Ideas and comments with regard to the new USB API are welcome
-      on the <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-usb" shape="rect">
-      FreeBSD-USB Mailing List</a>.</p>
-    <hr /><br /><h1><a name="FreeBSD-Architecture" href="#FreeBSD-Architecture" id="FreeBSD-Architecture">FreeBSD Architecture</a></h1><br /><h2><a name="ARM/Marvell-port" href="#ARM/Marvell-port" id="ARM/Marvell-port">ARM/Marvell port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/arm/src/sys/arm/orion/&amp;c=0h4@//depot/projects/arm/src/sys/arm/orion/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/arm/src/sys/arm/orion/&amp;c=0h4@//depot/projects/arm/src/sys/arm/orion/?ac=83">Orion in Perforce</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/arm/src/sys/arm/orion/&amp;c=0h4@//depot/projects/arm/src/sys/arm/orion/?ac=83" title="Orion in Perforce">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/arm/src/sys/arm/orion/&amp;c=0h4@//depot/projects/arm/src/sys/arm/orion/?ac=83</a></td></tr></table><p>
-	Contact:
-          Rafal
-
-          Jaworowski
-         &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	<br />
-	Contact:
-          Bartlomiej
-
-          Sieka
-         &lt;<a href="mailto:tur@semihalf.com">tur@semihalf.com</a>&gt;
-	</p>
-      <p>After the last couple of months of intensive development going
-      on towards FreeBSD support for Marvell System-on-Chip devices, we
-      have FreeBSD 8.0-CURRENT running on the following systems:</p>
-      <ul>
-        <li>Orion (already available in Perforce):</li>
-	<ul>
-	  <li>88F5281</li>
-	  <li>88F5181</li>
-	  <li>88F5182</li>
-        </ul>
-	<li>Kirkwood - 88F6281</li>
-	<li>Discovery - MV78100</li>
-      </ul>
-      <p>The above families of SOCs are built around CPU
-      cores compliant with ARMv5TE instruction set architecture
-      definition. They share a number of integrated peripherals, for most
-      of which we already have operational and stable drivers:</p>
-      <ul>
-        <li>UART</li>
-	<li>EHCI USB 2.0</li>
-	<li>Ethernet</li>
-	<li>IDMA (general purpose DMA engine)</li>
-	<li>XOR</li>
-	<li>TWSI (I2C)</li>
-	<li>Timers, watchdog, RTC</li>
-	<li>GPIO</li>
-	<li>Interrupt controller</li>
-	<li>L1, L2 cache</li>
-      </ul>
-      <p>High level functional summary:</p>
-      <ul>
-        <li>Production Quality</li>
-	<li>Error-free Operation</li>
-	<li>Multiuser</li>
-	<li>Self-hosted kernel/world builds</li>
-	<li>NFS- or USB-mounted root filesystem</li>
-      </ul>
-      <p>The code is partially available (Orion in Perforce), other
-        variants will also be integrated with Perforce/SVN soon.</p>
-    <h3>Open tasks:</h3><ol><li>Drivers that are In-progress: PCI and PCIE.</li></ol><hr /><br /><h1><a name="The-Ports-Collection" href="#The-Ports-Collection" id="The-Ports-Collection">The Ports Collection</a></h1><br /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://people.freebsd.org/~fenner/portsurvey/" title="http://people.freebsd.org/~fenner/portsurvey/">FreeBSD ports unfetchable distfile survey (Bill Fenner's report)</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~fenner/portsurvey/" title="FreeBSD ports unfetchable distfile survey (Bill Fenner's report)">http://people.freebsd.org/~fenner/portsurvey/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports count has jumped to over 19,000. The PR count has been
-      holding steady at around 900.</p>
-
-      <p>KDE has been updated to 4.1. Special thanks go to Martin Wilke
-      for a great deal of pre-testing.</p>
-
-      <p>GNOME has been updated three times, first to 2.22.1 and then to
-      2.22.2 and 2.22.3.</p>
-
-      <p>Other notable updates are automake, gettext, libtool, and
-      m4.</p>
-
-      <p>Florent Thoumie has been working on some updates to the pkg_*
-      tools.</p>
-
-      <p>Ion-Mihai Tetcu has set up a tinderbox with several purposes:
-      first, to quickly try to build packages as changes are committed;
-      secondly, to build them with a non-standard set of environment
-      variables; and thirdly, to build older packages with the non-
-      standard set of environment variables. As a result of all this
-      work, and work by various committers, we are much closer to
-      building packages corrected in the NOPORTDOCS case.</p>
-
-      <p>Kris Kennaway has done a substantial rewrite of the package
-      building tools, including moving as a default to ZFS, which allows
-      quick cloning of src and ports directories. It is now much easier
-      to manage and monitor the builds. Work on this is continuing. See
-      the commits to
-      <url href="http://www.freebsd.org/cgi/cvsweb.cgi/ports/Tools/portbuild/scripts/">
-      Tools/portbuild/scripts</url>
-
-      for more information. (Work is ongoing to update the Package
-      Building article.) Related work has involved cleaning up some of
-      the ports infrastructure; in particular, the INDEX builds are now
-      much faster.</p>
-
-      <p>We have been able to do many -exp runs since the last report,
-      including those for bsd.cmake.mk, autotools update, CC environment
-      passing, the KDE 4.1 pre-integration and post-integration checks,
-      lockmgr changes, tty changes, and others.</p>
-
-      <p>Although a number of PRs have been closed, we are still at 57
-      portmgr PRs, the same as the last report.</p>
-
-      <p>The following large changes are in the pipeline:
-      <ul>
-        <li>Introduction of Perl 5.10</li>
-      </ul>
-      </p>
-
-      <p>We are currently building packages for amd64-6, amd64-7,
-      amd64-8, i386-6, i386-7, i386-8, sparc64-6, and sparc64-7. RELENG_5
-      has reached the end of its supported life.</p>
-
-      <p>We have added 4 new committers since the last report.</p>
-    <h3>Open tasks:</h3><ol><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have over
-      4,000 unmaintained ports (see, for instance, the list on portsmon).
-      We are always looking for dedicated volunteers to adopt at least a
-      few unmaintained ports. As well, the packages on amd64 and sparc64
-      lag behind i386, and we need more testers for those.</li></ol><hr /><h2><a name="Qt/KDE4-Status-Report" href="#Qt/KDE4-Status-Report" id="Qt/KDE4-Status-Report">Qt/KDE4 Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freebsd.kde.org" title="http://freebsd.kde.org"></a></td><td>
-	    URL: <a href="http://freebsd.kde.org" title="">http://freebsd.kde.org</a></td></tr></table><p>
-	Contact:
-          Martin
-
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          FreeBSD KDE Team
-         &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>Qt4 has been updated to 4.4.1 in our test repository. We ran
-      into some runtime problems with Qt 4.4.0, so it was never committed
-      it to the ports tree. Most of the problems have been fixed in 4.4.1
-      and we plan to commit it in a few days.</p>
-
-      <p>At the moment, the KDE 4.1 ports are ready for testing before
-      they are committed to the FreeBSD ports tree. We have already had
-      the first Call for Public Testing on July 17th, 2008 with KDE 4.1
-      beta2. The feedback has been positive so far. If you want to help
-      to test them to speed up the process, please visit the
-      <a href="http://wiki.freebsd.org/KDE4/install" shape="rect">Wiki page</a>
-
-      and provide feedback.</p>
-
-      <p>We plan to have it all committed by the middle of August.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="FreeBSD-FAQ-Renovation" href="#FreeBSD-FAQ-Renovation" id="FreeBSD-FAQ-Renovation">FreeBSD FAQ Renovation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en/books/faq/" title="http://www.FreeBSD.org/doc/en/books/faq/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en/books/faq/" title="">http://www.FreeBSD.org/doc/en/books/faq/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/faq-renewal" title="http://wiki.freebsd.org/faq-renewal">FreeBSD FAQ Renewal Proposal</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/faq-renewal" title="FreeBSD FAQ Renewal Proposal">http://wiki.freebsd.org/faq-renewal</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Manolis
-
-          Kiagias
-         &lt;<a href="mailto:manolis@FreeBSD.org">manolis@FreeBSD.org</a>&gt;
-	</p>
-      <p>An extensive work on renovating the FreeBSD FAQ has been started
-      to support its Greek and Hungarian translations. Further
-      improvements and content changes are still possible, we hope other
-      committers will help us to keep the FAQ updated and tuned
-      further.</p>
-
-      <p>We have launched a renewal proposal to collect and organize the
-      ideas around a more interactive, accurate, open for comments,
-      consistent across several views etc. FAQ document. We would like to
-      experiment with methods to implement the goals mentioned before,
-      and help is more than welcome.</p>
-    <h3>Open tasks:</h3><ol><li>Review the renovated FAQ.</li><li>Add more question and answers to the FAQ.</li><li>Refine the FAQ renewal proposal.</li></ol><hr /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd-nl.org" title="http://www.freebsd-nl.org">Main documentation site</a></td><td>
-	    URL: <a href="http://www.freebsd-nl.org" title="Main documentation site">http://www.freebsd-nl.org</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd_nl/" title="http://www.evilcoder.org/freebsd_nl/">Project site</a></td><td>
-	    URL: <a href="http://www.evilcoder.org/freebsd_nl/" title="Project site">http://www.evilcoder.org/freebsd_nl/</a></td></tr></table><p>
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Rene
-
-          Ladan
-         &lt;<a href="mailto:r.c.ladan@gmail.com">r.c.ladan@gmail.com</a>&gt;
-	</p>
-      <p>
-        <p>The FreeBSD Dutch Documentation Project is an ongoing project
-        to translate the FreeBSD Documentation resources to the Dutch
-        language.</p>
-
-        <p>The project is currently progressing very well in translating
-        the FreeBSD Handbook to the Dutch language, the last chapter is
-        being translated by the project members.</p>
-
-        <p>Recent achievements include the translation of the Jails
-        chapter, and the Virtualization chapter, as well as progression
-        on the Advanced Networking chapter. Rene Ladan is a keyplayer in
-        that region.</p>
-
-        <p>We also started with the FAQ translation, which is another
-        major target which we should be reaching at some point.</p>
-
-        <p>If you care to helpout with the translation(s) and/or want to
-        know something about it, please do not hesitate to contact us, we
-        are glad to help where possible.</p>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Finish the Handbook translation.</li><li>Finish the FAQ translation.</li><li>Finish the Website translation.</li><li>Keep the projects in sync with the English version(s).</li></ol><hr /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.org/hu" title="http://FreeBSD.org/hu">Hungarian Web Site for FreeBSD</a></td><td>
-	    URL: <a href="http://FreeBSD.org/hu" title="Hungarian Web Site for FreeBSD">http://FreeBSD.org/hu</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu_HU.ISO8859-2/" title="http://www.FreeBSD.org/doc/hu_HU.ISO8859-2/">Hungarian Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu_HU.ISO8859-2/" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu_HU.ISO8859-2/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for The FreeBSD Hungarian Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for The FreeBSD Hungarian Documentation Project">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>Hungarian translation of the
-      <a href="http://www.freebsd.org/doc/hu/books/handbook" shape="rect">
-      FreeBSD�Handbook</a>
-
-      has been finally committed to the doc repository. The translation
-      of the
-      <em>FreeBSD�FAQ</em>
-
-      has also been started, however, the original document needed to be
-      brought up to date first. Two other article translations has been
-      added,
-      <a href="http://www.freebsd.org/doc/hu/articles/compiz-fusion" shape="rect">
-      compiz-fusion</a>
-
-      and
-      <a href="http://www.freebsd.org/doc/hu/articles/linux-users" shape="rect">
-      linux-users</a>.</p>
-
-      <p>Our Perforce depot was reorganized for the better layout, giving
-      newcomers more space to play. The
-      <a href="http://www.freebsd.org/cgi/cvsweb.cgi/doc/el_GR.ISO8859-7/share/tools/checkupdate/checkupdate.py" shape="rect">
-      checkupdate</a>
-
-      script written by Giorgos�Keramidas, a new tool for checking
-      translations has been adopted to help the project's work.</p>
-    <h3>Open tasks:</h3><ol><li>Translate release notes for -CURRENT and 7.X.</li><li>Translate more articles.</li><li>Translate books/fdp-primer.</li></ol><hr /><h2><a name="The-FreeBSD-Spanish-Documentation-Project" href="#The-FreeBSD-Spanish-Documentation-Project" id="The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.org/es" title="http://FreeBSD.org/es">Spanish Web Site for FreeBSD</a></td><td>
-	    URL: <a href="http://FreeBSD.org/es" title="Spanish Web Site for FreeBSD">http://FreeBSD.org/es</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/es_ES.ISO8859-1/" title="http://www.FreeBSD.org/doc/es_ES.ISO8859-1/">Spanish Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/es_ES.ISO8859-1/" title="Spanish Documentation for FreeBSD">http://www.FreeBSD.org/doc/es_ES.ISO8859-1/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/SpanishDocumentationProject" title="http://wiki.FreeBSD.org/SpanishDocumentationProject">The FreeBSD Spanish Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SpanishDocumentationProject" title="The FreeBSD Spanish Documentation Project's Wiki Page">http://wiki.FreeBSD.org/SpanishDocumentationProject</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_es/&amp;c=S1s@//depot/projects/docproj_es/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_es/&amp;c=S1s@//depot/projects/docproj_es/?ac=83">Perforce Depot for The FreeBSD Spanish Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_es/&amp;c=S1s@//depot/projects/docproj_es/?ac=83" title="Perforce Depot for The FreeBSD Spanish Documentation Project">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_es/&amp;c=S1s@//depot/projects/docproj_es/?ac=83</a></td></tr></table><p>
-	Contact:
-          Jos� Vicente
-
-          Carrasco Vay�
-         &lt;<a href="mailto:carvay@FreeBSD.org">carvay@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have not made any significant progress in this period. We
-      definitely need more active translators to progress with the
-      translation project.</p>
-    <h3>Open tasks:</h3><ol><li>Complete renovation of the Spanish web site.</li><li>Update Handbook translation.</li><li>Translate release notes for -CURRENT and 7.X.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2008-07-2008-09.html b/website/content/en/status/report-2008-07-2008-09.html
deleted file mode 100644
index 0a8cb7dcdc..0000000000
--- a/website/content/en/status/report-2008-07-2008-09.html
+++ /dev/null
@@ -1,700 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>In this Quarter work has been progressing in quite a few areas of
-    FreeBSD. FreeBSD 7.1-BETA2 and 6.4-RC2 have been released for
-    pre-release testing. EuroBSDCon 2008 took place in Strasbourg, France
-    and quite a few developers got together for the Developer Summit
-    before the Conference. The USB2 stack has been imported into the
-    -HEAD branch.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#CVSMode-for-csup">CVSMode for csup</a></li><li><a href="#FreeBSD-for-ASUS-EeePC">FreeBSD for ASUS EeePC</a></li><li><a href="#pkg_trans">pkg_trans</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li><li><a href="#USB2">USB2</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#Release-Engineering-Team">Release Engineering Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Multi-IPv4/v6/no-IP-jails">Multi-IPv4/v6/no-IP jails</a></li><li><a href="#Synaptics-touchpads-support-improvements-in-psm(4)">Synaptics touchpads support improvements in psm(4)</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/powerpc-for-Freescale-MPC8572">FreeBSD/powerpc for Freescale MPC8572</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-mirror-statistics">FreeBSD mirror statistics</a></li><li><a href="#FreeBSD-Multimedia-Resources-List">FreeBSD Multimedia Resources List</a></li><li><a href="#MavEtJu's-FreeBSD-Mailing-List-Browser">MavEtJu's FreeBSD Mailing List Browser</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="CVSMode-for-csup" href="#CVSMode-for-csup" id="CVSMode-for-csup">CVSMode for csup</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;po=h&amp;c=gCY@//depot/user/lulf/csup/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;po=h&amp;c=gCY@//depot/user/lulf/csup/?ac=83">Perforce repository</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;po=h&amp;c=gCY@//depot/user/lulf/csup/?ac=83" title="Perforce repository">http://p4web.freebsd.org/@md=d&amp;cd=//&amp;po=h&amp;c=gCY@//depot/user/lulf/csup/?ac=83</a></td></tr></table><p>
-	Contact:
-          Ulf
-
-          Lilleengen
-         &lt;<a href="mailto:lulf@FreeBSD.org">lulf@FreeBSD.org</a>&gt;
-	</p>
-      <p>The implementation of cvsmode for csup has become more mature,
-      and has been tested by a few people so far. All parts directly
-      related to CVSMode have been implemented, and it seems to work
-      quite well. Testers are still needed, so any users of cvsup
-      using it to mirror or fetch the CVS repository (cvsmode/mirror
-      mode) are encouraged to try it.</p>
-    <h3>Open tasks:</h3><ol><li>Implement support for the rsync protocol (not needed for proper
-      working, but it will probably speed up csup in some cases)</li><li>Implement complete support for using the status file in
-      cvsmode</li></ol><hr /><h2><a name="FreeBSD-for-ASUS-EeePC" href="#FreeBSD-for-ASUS-EeePC" id="FreeBSD-for-ASUS-EeePC">FreeBSD for ASUS EeePC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/AsusEee" title="http://wiki.freebsd.org/AsusEee">ASUS Eee Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/AsusEee" title="ASUS Eee Wiki">http://wiki.freebsd.org/AsusEee</a></td></tr></table><p>
-	Contact:
-          Stanislav
-
-          Sedov
-         &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Rui
-
-          Paulo
-         &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Lars
-
-          Engels
-         &lt;<a href="mailto:lme@FreeBSD.org">lme@FreeBSD.org</a>&gt;
-	</p>
-      <p>
-      <em>ASUS Eee</em>
-
-      is a line of cheap subnotebooks. These come with Linux or Windows
-      preinstalled. The hardware is a bit inconventional, so it required
-      some efforts to make FreeBSD run properly on this hardware. Also,
-      these machines contain some hardware that was not supported by
-      FreeBSD.</p>
-
-      <p>Currently FreeBSD should run on all Eee models out of the box,
-      and most hardware should just work. At least, 700, 701, 901 and
-      1000 was tested successfully. The hardware supported includes
-      Atheros wireless backed by ath(4) in HEAD (you still need a patch
-      for RELENG_7), Attansic L2 FastEthernet controller (ae(4)),
-      High Definition audio controller (snd_hda), Synaptics touchpad and
-      so on. Suspend/resume also works fine with some exceptions.</p>
-
-      <p>There is also a hardware monitoring module, that allows user to
-      control FAN speed and voltage, as well as monitor current CPU
-      temperature. Wiki page contains information on how to obtain this
-      module and use it. There are also a lot of useful tips and tricks
-      for using FreeBSD on ASUS EeePC on that page.</p>
-    <h3>Open tasks:</h3><ol><li>Attansic L1 Gigabit Ethernet support (for ASUS Eee
-      901)</li><li>Wireless driver for ASUS Eee 901 (ral(4))</li><li>Fix Synaptics resume path.</li></ol><hr /><h2><a name="pkg_trans" href="#pkg_trans" id="pkg_trans">pkg_trans</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/IvanVoras/PkgTransProposal" title="http://wiki.freebsd.org/IvanVoras/PkgTransProposal"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/IvanVoras/PkgTransProposal" title="">http://wiki.freebsd.org/IvanVoras/PkgTransProposal</a></td></tr></table><p>
-	Contact:
-          Ivan
-
-          Voras
-         &lt;<a href="mailto:ivoras@freebsd.org">ivoras@freebsd.org</a>&gt;
-	</p>
-      <p>The "pkg_trans" project is a work in progress aiming to add
-      package transactions / grouping to common package manipulation
-      utilities (pkg_add, pkg_delete). The intention is to have all
-      packages pulled in by a particular command like "pkg_add" or "make
-      install" grouped in a single transaction, which can be later rolled
-      back. This will allow users to, for example, install a big tree of
-      dependent packages (like kde4), try it, and later delete it.</p>
-
-      <p>Currently the pkg_trans and the patched utilities are available
-      for testing. There are some open issues but it's generally
-      stable.</p>
-    <h3>Open tasks:</h3><ol><li>I cannot modify the "make install" infrastructure for ports
-      and 3rd party utilities such as portupgrade. People who know these
-      utilities are very welcome to help.</li><li>More testing is needed.</li></ol><hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org" title="http://www.freebsdfoundation.org"></a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org" title="">http://www.freebsdfoundation.org</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@FreeBSD.org">deb@FreeBSD.org</a>&gt;
-	</p>
-      <p>For the first time we sent out a request for project proposals.
-      We were very excited about the proposals we received. We accepted
-      four projects and will be announcing them soon. We were proud to
-      sponsor NYCBSDCon and EuroBSDCon. We are also a sponsor of
-      MeetBSDCon. We provided travel grants for the Cambridge FreeBSD
-      Developer Summit in August. We are continuing to provide updated
-      Java binaries for FreeBSD 7.0. We continued to provide legal
-      support for the project.</p>
-    <hr /><h2><a name="USB2" href="#USB2" id="USB2">USB2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=OPj@//depot/projects/usb/src/sys/dev/usb2/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=OPj@//depot/projects/usb/src/sys/dev/usb2/?ac=83">Current USB files</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=OPj@//depot/projects/usb/src/sys/dev/usb2/?ac=83" title="Current USB files">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/usb/src/sys/dev/usb2/&amp;c=OPj@//depot/projects/usb/src/sys/dev/usb2/?ac=83</a></td></tr></table><p>
-	Contact:
-          Hans Petter
-
-          Sirevaag Selasky
-         &lt;<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>&gt;
-	</p>
-      <p>The new USB stack has been imported to FreeBSD-CURRENT. There is
-      an ongoing review process at the freebsd-usb mailing list and the
-      freebsd-current mailing list. A couple of minor issues remain.</p>
-
-      <p>Ideas and comments with regard to the new USB stack are welcome
-      at freebsd-usb@freebsd.org .</p>
-    <h3>Open tasks:</h3><ol></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Security-Officer-and-Security-Team" href="#FreeBSD-Security-Officer-and-Security-Team" id="FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/security/" title="http://www.freebsd.org/security/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/security/" title="">http://www.freebsd.org/security/</a></td></tr><tr><td><a href="http://www.freebsd.org/administration.html#t-secteam" title="http://www.freebsd.org/administration.html#t-secteam"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/"></a></td><td>
-	    URL: <a href="http://vuxml.freebsd.org/" title="">http://vuxml.freebsd.org/</a></td></tr></table><p>
-	Contact:
-          Security
-
-          Officer
-         &lt;<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Security
-
-          Team
-         &lt;<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Security Team has recently had some membership
-      changes. George V. Neville-Neil, Dag-Erling Smorgrav, and Marcus
-      Alves Grando have retired from the team. We thank them for their
-      work while they were on the security team. Xin Li, Martin Wilke,
-      Qing Li, and Stanislav Sedov have joined the team.</p>
-    <hr /><h2><a name="Release-Engineering-Team" href="#Release-Engineering-Team" id="Release-Engineering-Team">Release Engineering Team</a></h2><p>
-	Contact:
-          Ken
-
-          Smith
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team continues to work on getting
-      6.4-RELEASE and 7.1-RELEASE ready. 6.4-RC2 builds are coming up
-      shortly, with 6.4-RELEASE expected about two weeks later. There are
-      still a few issues being worked on for 7.1-RELEASE though hopefully
-      we will be ready to proceed with 7.1-RC1 within the next week. Both
-      6.4-RELEASE and 7.1-RELEASE will include DVD image ISOs for the
-      amd64 and i386 architectures which has been requested by quite a
-      few end-users.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Multi-IPv4/v6/no-IP-jails" href="#Multi-IPv4/v6/no-IP-jails" id="Multi-IPv4/v6/no-IP-jails">Multi-IPv4/v6/no-IP jails</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sources.zabbadoz.net/freebsd/jail.html" title="http://sources.zabbadoz.net/freebsd/jail.html">Web page for regularly updates and patches</a></td><td>
-	    URL: <a href="http://sources.zabbadoz.net/freebsd/jail.html" title="Web page for regularly updates and patches">http://sources.zabbadoz.net/freebsd/jail.html</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50">Perforce tree</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50" title="Perforce tree">http://p4web.freebsd.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50</a></td></tr></table><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.ORG">bz@FreeBSD.ORG</a>&gt;
-	</p>
-      <p>The multi-IPv4/v6/no-IP jails project was resumed beginning of
-      this year and is in the final stage now. A commit is imminent
-      waiting for final review to be finished.</p>
-
-      <p>As an alternative solution to full network stack virtualization,
-      this work shall provide a lightweight solution for multi-IP
-      virtualization. The changes are even more important because of the
-      emerging demand for IPv6.</p>
-
-      <p>Ideally this will be merged to FreeBSD 7 before 7.2-RELEASE and
-      stay in FreeBSD 8 for the transitional period to full network stack
-      virtualization.</p>
-    <h3>Open tasks:</h3><ol><li>Finish review.</li><li>Management (rc framework, ..) for 7-STABLE.</li><li>Identify ports that need to be updated.</li></ol><hr /><h2><a name="Synaptics-touchpads-support-improvements-in-psm(4)" href="#Synaptics-touchpads-support-improvements-in-psm(4)" id="Synaptics-touchpads-support-improvements-in-psm(4)">Synaptics touchpads support improvements in psm(4)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/SynapticsTouchpad" title="http://wiki.freebsd.org/SynapticsTouchpad"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SynapticsTouchpad" title="">http://wiki.freebsd.org/SynapticsTouchpad</a></td></tr></table><p>
-	Contact:
-          Jean-Sébastien
-
-          Pédron
-         &lt;<a href="mailto:dumbbell@FreeBSD.org">dumbbell@FreeBSD.org</a>&gt;
-	</p>
-      <p>psm(4) provides basic support for Synaptics Touchpad but doesn't
-      allow one to take advantage of many features like multi-finger tap
-      and tap-hold, or virtual scrolling. A driver for X.Org is available
-      but the movements are not very precise and the setup is not easy if
-      you want to use your touchpad in the console.</p>
-
-      <p>The goal of this project is to first provide a better movement
-      filtering and smoothing, then bring the more advanced features.</p>
-
-      <p>Right now, movement filtering, multi-finger tap, tap-hold and
-      virtual scrolling (using a dedicated area) is implemented.</p>
-
-      <p>Virtual scrolling with two fingers (as seen on Apple MacBook)
-      will be brought back soon.</p>
-
-      <p>But before that, the new driver needs testing! It's currently
-      tested on an ASUS V6V only and feedback on other laptops would be
-      greatly appreciated.</p>
-    <h3>Open tasks:</h3><ol><li>Test and send feedback.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/powerpc-for-Freescale-MPC8572" href="#FreeBSD/powerpc-for-Freescale-MPC8572" id="FreeBSD/powerpc-for-Freescale-MPC8572">FreeBSD/powerpc for Freescale MPC8572</a></h2><p>
-	Contact:
-          Rafal
-
-          Jaworowski
-         &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	<br />
-	Contact:
-          Bartlomiej
-
-          Sieka
-         &lt;<a href="mailto:tur@semihalf.com">tur@semihalf.com</a>&gt;
-	</p>
-      <p>The MPC8572 system-on-chip device is a high-end member of
-      Freescale PowerQUICC III family, which features a rich set of
-      integrated peripherals. It is a dual e500v2 core system, compliant
-      with Book-E definition of the Power Architecture. For detailed
-      specification see:
-      http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC8572E
-      This work is extending our (single core) MPC85XX port already
-      available in the SVN tree. Currently the MPC8572 support covers:
-      <ul>
-        <li>all existing functionality of FreeBSD/MPC85XX (console, e500
-        interrupts/exceptions, networking, etc.)</li>
-
-        <li>SMP</li>
-
-        <ul>
-          <li>dual-e500 cores running at 1.5GHz each</li>
-
-          <li>ULE</li>
-        </ul>
-
-        <li>Security engine (SEC)</li>
-
-        <li>General purpose DMA controller</li>
-
-        <li>Pattern matching engine (PME)</li>
-
-        <li>Ethernet controller (eTSEC) advanced features</li>
-
-        <ul>
-          <li>multicast</li>
-
-          <li>jumbo frames</li>
-
-          <li>TCP/IP h/w checksumming</li>
-
-          <li>VLAN tagging</li>
-
-          <li>polling</li>
-
-          <li>interrupt coalescing</li>
-        </ul>
-
-        <li>PCI-Express bridge</li>
-
-        <li>I2C controller</li>
-      </ul>
-
-      High level functional summary:
-      <ul>
-        <li>stable multiuser SMP operation</li>
-
-        <li>NFS-mounted root filesystem</li>
-      </ul>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Remaining built-in peripherals drivers</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu" title="http://www.FreeBSD.org/hu">Hungarian Web Page for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu" title="Hungarian Web Page for FreeBSD">http://www.FreeBSD.org/hu</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu" title="http://www.FreeBSD.org/doc/hu">Hungarian Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>In July,
-      <em>pgj</em>
-
-      gave a
-      <a href="http://people.freebsd.org/~pgj/fhdp/fhdp-slides.20080704.pdf.gz" shape="rect">
-      presentation</a>
-
-      (in Hungarian) about the FreeBSD Hungarian Documentation Project in
-      Debrecen, Hungary.</p>
-
-      <p>Based on the checkupdate script mentioned in our previous status
-      report, we launched our
-      <a href="http://lists.freebsd.org/pipermail/cvs-doc/2008-July/018608.html" shape="rect">
-      Translation Checking Service</a>
-
-      to help to schedule periodic updates for Hungarian doc/www
-      translations. Moreover, a small bug in EPS images blocking
-      automatic generation of the Handbook PDF version
-      <a href="http://lists.freebsd.org/pipermail/cvs-doc/2008-August/018785.html" shape="rect">
-      was corrected</a>
-
-      , therefore it is now available for
-      <a href="ftp://ftp.freebsd.org/pub/FreeBSD/doc/hu/books/handbook" shape="rect">
-      download</a>
-
-      .</p>
-
-      <p>Shortly after the renovation of its source, translation of the
-      FAQ has also become part of Hungarian documentations. Both
-      <a href="http://www.freebsd.org/doc/hu/books/faq" shape="rect">online</a>
-
-      and
-      <a href="ftp://ftp.freebsd.org/pub/FreeBSD/doc/hu/books/faq" shape="rect">
-      offline</a>
-
-      versions are available. A recently translated article
-      (<a href="http://www.freebsd.org/doc/hu/articles/gjournal-desktop" shape="rect">
-      gjournal-desktop</a>) has also been added.</p>
-
-      <p>Hungarian translation of the
-      <em>FreeBSD Documentation Project Primer for New Contributors</em>
-
-      has been
-      <a href="http://wiki.freebsd.org/TheHungarianFDPPrimer" shape="rect">started</a>
-
-      . We hope this will encourage others to help our work. There is
-      always place in our team, every submitted translation or feedback
-      is appreciated and very welcome.</p>
-    <h3>Open tasks:</h3><ol><li>Translate release notes for -CURRENT and 7.X</li><li>Translate articles</li><li>Translate the FDP Primer</li><li>Read the translations, send feedback</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="FreeBSD-mirror-statistics" href="#FreeBSD-mirror-statistics" id="FreeBSD-mirror-statistics">FreeBSD mirror statistics</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mavetju.org/unix/freebsd-mirrors/" title="http://www.mavetju.org/unix/freebsd-mirrors/">Website</a></td><td>
-	    URL: <a href="http://www.mavetju.org/unix/freebsd-mirrors/" title="Website">http://www.mavetju.org/unix/freebsd-mirrors/</a></td></tr><tr><td><a href="http://www.mavetju.org/unix/freebsd-mirrors/score.php" title="http://www.mavetju.org/unix/freebsd-mirrors/score.php">10 Day Score overview</a></td><td>
-	    URL: <a href="http://www.mavetju.org/unix/freebsd-mirrors/score.php" title="10 Day Score overview">http://www.mavetju.org/unix/freebsd-mirrors/score.php</a></td></tr></table><p>
-	Contact:
-          Edwin
-
-          Groothuis
-         &lt;<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are many FreeBSD mirrors, either FTP or WWW or CVSup or
-      RSync, but are they really all up-to-date? Some are, some aren't.
-      The ones who aren't, how out to date are they? Or do they only
-      carry a subset of the data? And how does it go over time?</p>
-
-      <p>This project checks once per day the contents of the sites which
-      are advertised in DNS, with the rsync*, www*, cvsup* and ftp*
-      prefixes. The lists of hosts are based on the contents of the DNS
-      zonefile for the country domains, so it will be automatically
-      adjusted whenever a mirror is added.</p>
-
-      <p>The statuses can be compared on country base and between two
-      dates and the 10 day score overview shows the general health of the
-      FreeBSD Mirroring network.</p>
-    <h3>Open tasks:</h3><ol><li>Create a list of contact details per mirror.</li><li>Chase mirror maintainers with regarding to the status of
-      their servers.</li></ol><hr /><h2><a name="FreeBSD-Multimedia-Resources-List" href="#FreeBSD-Multimedia-Resources-List" id="FreeBSD-Multimedia-Resources-List">FreeBSD Multimedia Resources List</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.html" title="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.html">Website</a></td><td>
-	    URL: <a href="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.html" title="Website">http://www.mavetju.org/unix/multimedia/freebsd/multimedia.html</a></td></tr><tr><td><a href="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.xml" title="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.xml">RSS feed</a></td><td>
-	    URL: <a href="http://www.mavetju.org/unix/multimedia/freebsd/multimedia.xml" title="RSS feed">http://www.mavetju.org/unix/multimedia/freebsd/multimedia.xml</a></td></tr></table><p>
-	Contact:
-          Edwin
-
-          Groothuis
-         &lt;<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>Please note that the FreeBSD Multimedia Resources List is still
-      alive and kicking. It is a one-stop-shop for FreeBSD related
-      podcasts, vodcasts and audio/video resources. It has talks, videos
-      and papers of the New York City BSD Con 2008, FreeBSD Developer
-      Summit, BSDCan 2008, AsiaBSDCon 2008, OpenFest and has recordings
-      with regular talks like the NYCBUG user group and regular podcast
-      of BSDTalk.</p>
-    <h3>Open tasks:</h3><ol></ol><hr /><h2><a name="MavEtJu's-FreeBSD-Mailing-List-Browser" href="#MavEtJu's-FreeBSD-Mailing-List-Browser" id="MavEtJu's-FreeBSD-Mailing-List-Browser">MavEtJu's FreeBSD Mailing List Browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mavetju.org/mail/" title="http://www.mavetju.org/mail/">Website</a></td><td>
-	    URL: <a href="http://www.mavetju.org/mail/" title="Website">http://www.mavetju.org/mail/</a></td></tr></table><p>
-	Contact:
-          Edwin
-
-          Groothuis
-         &lt;<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>Earlier this year I put efforts into the creation of a new layout
-      for the FreeBSD mailinglists. The following issues were tackled:
-      <ul>
-        <li>Display which mailinglists are active and are visited
-        often.</li>
-
-        <li>A clean weekly/monthly overview per list.</li>
-
-        <li>In the weekly/monthly overview, be able to go forward and
-        backward in time.</li>
-
-        <li>Browsing through threads goes by the Replies/Replies
-        To/Referenced By/References To fields of the emails, but visible
-        who the email is from.</li>
-
-        <li>An overview of the thread with quick links to the
-        articles.</li>
-
-        <li>Text attachments are normally shown, other attachment are
-        normally not shown.</li>
-
-        <li>Tag messages, see your browsing history, reply to emails and
-        an "wrap long lines" feature.</li>
-
-        <li>Filtering out of svn-, cvs-, freebsd-, and p4- groups.</li>
-
-        <li>Show date and time in the format you want.</li>
-
-        <li>Storing of preferences managed via OpenID
-        identification.</li>
-      </ul>
-
-      The mailinglist website is updated once per hour with the
-      mailinglists via cvsup.</p>
-    <h3>Open tasks:</h3><ol><li>Addition of RSS feeds per mailinglist and for the "last day"
-      feature.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2008-10-2008-12.html b/website/content/en/status/report-2008-10-2008-12.html
deleted file mode 100644
index 42ebc1858c..0000000000
--- a/website/content/en/status/report-2008-10-2008-12.html
+++ /dev/null
@@ -1,939 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This quarter included some very exciting work including the
-    release of FreeBSD 6.4 and the much anticipated release of
-    FreeBSD 7.1. We also launched our own official <a href="http://forums.FreeBSD.org" shape="rect">FreeBSD Forums</a>.
-    The first Bugathon of the year will be held this weekend, see
-    below for more information and how to participate.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BSD#-Project">BSD# Project</a></li><li><a href="#FreeBSD-Bugathons">FreeBSD Bugathons</a></li><li><a href="#FreeBSD-BugBusting-Team">FreeBSD BugBusting Team</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li><li><a href="#VuXML-generator">VuXML generator</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Release-Engineering">Release Engineering</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#HDA-sound-driver-(snd_hda)">HDA sound driver (snd_hda)</a></li><li><a href="#Multi-IPv4/v6/no-IP-jails">Multi-IPv4/v6/no-IP jails</a></li><li><a href="#Network-Stack-Virtualization">Network Stack Virtualization</a></li><li><a href="#PmcTools">PmcTools</a></li><li><a href="#SD/MMC-subsystem">SD/MMC subsystem</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/powerpc-for-AMCC/IBM-PPC440/460">FreeBSD/powerpc for AMCC/IBM PPC440/460</a></li><li><a href="#FreeBSD/sparc64-UltraSPARC-III-support">FreeBSD/sparc64 UltraSPARC III support</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Greek-Documentation-Project">The FreeBSD Greek Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSD-licensed-grep">BSD-licensed grep</a></li><li><a href="#The-FreeBSD-Forums">The FreeBSD Forums</a></li><li><a href="#YouTube-Channel-for-BSD">YouTube Channel for BSD</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BSD#-Project" href="#BSD#-Project" id="BSD#-Project">BSD# Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/bsd-sharp/" title="http://code.google.com/p/bsd-sharp/">The BSD# project on Google-code</a></td><td>
-	    URL: <a href="http://code.google.com/p/bsd-sharp/" title="The BSD# project on Google-code">http://code.google.com/p/bsd-sharp/</a></td></tr><tr><td><a href="http://www.mono-project.org/" title="http://www.mono-project.org/">Mono (Open source .Net Development Framework)</a></td><td>
-	    URL: <a href="http://www.mono-project.org/" title="Mono (Open source .Net Development Framework)">http://www.mono-project.org/</a></td></tr></table><p>
-	Contact:
-          Phillip
-
-          Neumann
-         &lt;<a href="mailto:pneumann@gmail.com">pneumann@gmail.com</a>&gt;
-	<br />
-	Contact:
-          Romain
-
-          Tarti�re
-         &lt;<a href="mailto:romain@blogreen.org">romain@blogreen.org</a>&gt;
-	</p>
-      <p>The BSD# Project is devoted to porting the Mono .NET framework
-      and applications to the FreeBSD operating system.</p>
-
-      <p>Because of a lack of time, Mono stalled at version 1.2.5 for
-      more than one year in the FreeBSD ports tree. However, things have
-      moved and the BSD# Team is proud to announce that the Mono ports are
-      about to be updated to 2.0.1. Ports depending on Mono will also be
-      updated to the latest available version at the same occasion.</p>
-
-      <p>While the ports will be updated really soon now that FreeBSD 7.1
-      has been released, impatient people can download and merge the BSD# ports
-      in their FreeBSD tree right now following the instructions provided
-      on the BSD# Project's page.</p>
-    <h3>Open tasks:</h3><ol><li>Test and send feedback.</li><li>Port Mono applications to FreeBSD.</li><li>Build a debug live-image of FreeBSD so that Mono hackers
-      without a FreeBSD box can help us fixing bugs more
-      efficiency.</li></ol><hr /><h2><a name="FreeBSD-Bugathons" href="#FreeBSD-Bugathons" id="FreeBSD-Bugathons">FreeBSD Bugathons</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting/Resources" title="http://wiki.FreeBSD.org/BugBusting/Resources"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting/Resources" title="">http://wiki.FreeBSD.org/BugBusting/Resources</a></td></tr><tr><td><a href="http://bugs.FreeBSD.org" title="http://bugs.FreeBSD.org"></a></td><td>
-	    URL: <a href="http://bugs.FreeBSD.org" title="">http://bugs.FreeBSD.org</a></td></tr><tr><td><a href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?responsible=freebsd-net" title="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?responsible=freebsd-net"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?responsible=freebsd-net" title="">http://www.FreeBSD.org/cgi/query-pr-summary.cgi?responsible=freebsd-net</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:bugbusters@FreeBSD.org">bugbusters@FreeBSD.org</a>&gt;
-	</p>
-      <p>Last year, we didn't have many Bugathons - this year is planned
-      to be different!</p>
-
-      <p>The BugBusting team is trying to improve bug handling and thus
-      we'll start a new experiment. In the past our Bugathons were
-      general Bugathons with no special topic set. Instead, starting in
-      2009 we'll try to hold a series of Bugathons that concentrate on
-      special interest areas.</p>
-
-      <p>Our next Bugathon will be held from 2009-01-30 to 2009-02-01
-      (Fri-Sun). We'll try to handle as many network related bugs as we
-      can. Our plan is to try to work through all network related PRs
-      still open in GNATS.</p>
-
-      <p>We need a number of maintainers in the area of networking
-      (drivers, chipsets, protocols, userland processes) to attend and
-      committers willing to commit fixes and improvements. Of course, we
-      also need users and administrators with special interest in network
-      related items to be with us to sort out things. Every helping hand,
-      everyone able to debug and analyze things is welcome.</p>
-
-      <p>If you're interested in getting networking stuff improved, join
-      us to make the upcoming releases of 7.2 and 8.0 the best ever
-      FreeBSD releases.</p>
-
-      <p>Join us on IRC: EFnet #FreeBSD-bugbusters from Friday 2009-01-30
-      to Sunday 2009-02-01. Don't miss this event!</p>
-
-      <p>The next Bugathon (TBA) will have topics in different special
-      interest areas.</p>
-    <h3>Open tasks:</h3><ol><li>Feel free to ask questions! You can reach the BugBusting team
-      at bugbusters@FreeBSD.org. Be there! Work with us! Join the team -
-      be a part!</li></ol><hr /><h2><a name="FreeBSD-BugBusting-Team" href="#FreeBSD-BugBusting-Team" id="FreeBSD-BugBusting-Team">FreeBSD BugBusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="GNATS">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting">BugBusting</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="BugBusting">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/">experimental report pages</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="experimental report pages">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr></table><p>
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:bugmeister@">bugmeister@</a>&gt;
-	<br />
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister@">bugmeister@</a>&gt;
-	</p>
-      <p>We will be having our next Bugathon on 2009-01-30 to 2009-02-01
-      (see <a href="#FreeBSD-Bugathons" shape="rect">this</a> entry).</p>
-
-      <p>At the recent DevSummit in Strasbourg, the participants spent
-      half a day working through the current "recommended PRs" list. The
-      list was divided up into sections by date, and each table was
-      assigned one section to work through. Not only were a good number
-      of fixes committed and their PRs closed, but the src developers
-      were brought up to speed on the triage work that the BugBusting
-      team has been doing (see below). We hope to build on this momentum
-      in the future. In addition, many new ideas for improved report
-      pages were discussed.</p>
-
-      <p>We continue to make good progress in categorizing PRs as they
-      arrive with 'tags' that correspond to manpages. As a result, we now
-      have created some prototype reports that allow browsing the
-      database
-      <a href="http://people.FreeBSD.org/~linimon/studies/prs/pr_manpage_index.html" shape="rect">
-      by manpage</a>.</p>
-
-      <p>In addition, another new report, oriented towards PR submitters,
-      summarizes the
-      <a href="http://people.FreeBSD.org/~linimon/studies/prs/well_known_prs.html" shape="rect">
-      most commonly reported issues</a>. Many of these issues persist
-      because they are difficult to fix. Before filing a PR, you may
-      want to check through this list.</p>
-
-      <p>As well, we now have a more active set of volunteers who are
-      willing to help users with reported problems of the form "xyz does
-      not seem to work". These types of reports are now being handled
-      much better than in the past.</p>
-
-      <p>One of those volunteers, Bruce Cran (brucec@), has now been
-      released from mentorship.</p>
-
-      <p>Mark Linimon (linimon@) continues to work on more new prototype
-      reports, including:</p>
-
-      <ul>
-        <li><a href="http://people.FreeBSD.org/~linimon/studies/prs/recentprs_day.html" shape="rect">
-        New PRs in the past day</a>, <a href="http://people.FreeBSD.org/~linimon/studies/prs/recentprs_week.html" shape="rect">
-        week</a>, <a href="http://people.FreeBSD.org/~linimon/studies/prs/recentprs_month.html" shape="rect">
-        month</a>.</li>
-
-        <li><a href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_tag_regression.html" shape="rect">
-        PRs with regressions</a>.</li>
-
-        <li>A way for developers to <a href="http://people.FreeBSD.org/~linimon/annotated_prs.sample.html" shape="rect">
-        create their own customized reports</a>.</li>
-      </ul>
-
-      <p>The <a href="http://wiki.FreeBSD.org/BugBusting/Commonly_reported_issues" shape="rect">
-      commonly reported issues</a> summary page, previously maintained
-      by Jeremy Chadwick, has been moved to a new location.</p>
-
-      <p>The overall PR count jumped to over 5600 during the 6.4/7.1
-      release cycle, but has come down a bit.</p>
-    <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with
-      closing PRs that the team has already analyzed.</li><li>Think of some way for committers to only view PRs that have
-      been in some way 'vetted' or 'confirmed'.</li><li>Generate more publicity for what we've already got in place,
-      and for what we intend to do next.</li><li>Define new categories, classifications, and states for PRs,
-      that will better match our workflow.</li></ol><hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDfoundation.org" title="http://www.FreeBSDfoundation.org"></a></td><td>
-	    URL: <a href="http://www.FreeBSDfoundation.org" title="">http://www.FreeBSDfoundation.org</a></td></tr></table><p>
-	Contact:
-          Deb
-
-          Goodkin
-         &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We ended the year raising over $282,000! We received 173
-      donations just in December. We are very grateful to all the people
-      who helped us come very close to our 2008 goal.</p>
-
-      <p>Three projects were started that are being funded by the
-      foundation. They are Safe Removal of Active Disk Devices,
-      Improvements to the FreeBSD TCP Stack, and Network Stack
-      Virtualization Projects.
-      <a href="http://www.FreeBSDfoundation.org/project%20announcements.shtml" shape="rect">
-      Click here</a>
-
-      to find out more about the projects.</p>
-
-      <p>We were a sponsor for meetBSD. We provided a travel grant for a
-      developer to attend this conference. We also handed out a few
-      limited edition foundation vests for developer recognition.</p>
-
-      <p>Read our
-      <a href="http://www.FreeBSDfoundation.org/press/2008Dec-newsletter.shtml" shape="rect">
-      end-of-year newsletter</a>, to find out what else we've done to
-      help The FreeBSD Project and community.</p>
-    <hr /><h2><a name="VuXML-generator" href="#VuXML-generator" id="VuXML-generator">VuXML generator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.credentia.cc/services/vuxml/" title="http://www.credentia.cc/services/vuxml/"></a></td><td>
-	    URL: <a href="http://www.credentia.cc/services/vuxml/" title="">http://www.credentia.cc/services/vuxml/</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Foster
-         &lt;<a href="mailto:mark@foster.cc">mark@foster.cc</a>&gt;
-	</p>
-      <p>VuXML generator ("wizard") is intended for end-users who want to
-      generate VuXML (XML) definitions. Users can just fill out an HTML
-      form &amp; this removes some of the guesswork and the learning
-      curve. The resulting VuXML can be submitted via send-pr as-is for
-      inclusion into the portaudit database.</p>
-    <h3>Open tasks:</h3><ol><li>Option to submit generated XML into a "review" queue
-      somewhere (thus eliminate the need for users to run send-pr at
-      all)</li><li>Option to generate OVAL definition in addition to
-      VuXML</li><li>Option to generate ready-to-run pr (e.g send-pr -f
-      &lt;outputfile&gt;)</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="The FreeBSD Ports Collection">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most of the effort in the last quarter has been QA effort for
-      6.4-RELEASE and 7.1-RELEASE. Since that time, we have once again
-      begun work on experimental package runs.</p>
-
-      <p>The ports count has jumped to over 19,600. The PR count had
-      jumped during the freeze/slush cycle for release, but has now
-      dropped back to its usual count of around 900.</p>
-
-      <p>GNOME has been updated to 2.24.3.</p>
-
-      <p>KDE has been updated to 4.1.4.</p>
-
-      <p>X.Org has been updated to 7.4.</p>
-
-      <p>The following large changes are in the pipeline:</p>
-
-      <ul>
-        <li>Introduction of Perl 5.10.</li>
-      </ul>
-
-      <p>We are currently building packages for amd64-6, amd64-7,
-      amd64-8, i386-6, i386-7, i386-8, sparc64-6, and sparc64-7. Several
-      new i386 and sparc64 machines have been added, which has helped
-      speed up the builds. We especially appreciate the loan of a number
-      of sparc64 machines by Gavin Atkinson.</p>
-
-      <p>We have added 5 new committers since the last report, and 2
-      older ones have rejoined.</p>
-    <h3>Open tasks:</h3><ol><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have over
-      4,700 unmaintained ports (see, for instance, the list on portsmon).
-      (The percentage hovers around 24%.) We are always looking for
-      dedicated volunteers to adopt at least a few unmaintained ports. As
-      well, the packages on amd64 and sparc64 lag behind i386, and we
-      need more testers for those.</li></ol><hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Release Engineering
-         &lt;<a href="mailto:re@">re@</a>&gt;
-	</p>
-        <p>Since the last status report both 7.1-RELEASE (5 January 2009)
-	and 6.4-RELEASE (28 November 2008) have been released. Starting
-	with 6.4-RELEASE, a new DVD ISO image called "dvd1" is provided
-	for amd64/i386. This image contains everything that is on the
-	CDROM discs. So "dvd1" can be used to do a full installation that
-        includes a basic set of packages, it has all of the documentation
-        for all supported languages, and it can be used for booting into
-        a "live CD-based filesystem" and system rescue mode. 6.4-RELEASE
-        was the last release of the 6.X branch, we have currently no plan
-        for any other 6.X release since most of the developers are
-        focused on 8-CURRENT and 7.X.</p>
-
-        <p>The long awaited 7.1-RELEASE is out since 5th of January. This
-        release process was far too long from everyone's point of view.
-        Working on another release (6.4-RELEASE) at the same time was not
-        helping the things, but we are aware of many problems that need
-        to be worked on to ease the whole release process. As a
-        consequence, we are currently working on a new plan for future
-        7.X (or 8.0) release. We plan to:</p>
-
-        <ul>
-          <li>Reduce the freeze period of ports tree, the freeze should
-          occur near the end of the release process during RC cycle</li>
-
-          <li>Change the way showstoppers are handled and do not stop a
-          release process for non-important issues or lack of
-          features.</li>
-        </ul>
-
-        <p>Some work has also been done on the documentation build, we
-        want to provide a more flexible way to install docs (Handbook,
-        FAQ, etc.) and detach the documentation build from the release build to use
-        instead ports (packages). This should make release building
-        easier on slow architectures. Hopefully this switch will be done
-        for 7.2-RELEASE or 8.0-RELEASE.</p>
-
-        <p>Regarding the time line, we still plan to release 8.0-RELEASE
-        in mid-June 2009. A time for the 7.2-RELEASE has not been set
-	yet.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="HDA-sound-driver-(snd_hda)" href="#HDA-sound-driver-(snd_hda)" id="HDA-sound-driver-(snd_hda)">HDA sound driver (snd_hda)</a></h2><p>
-	Contact:
-          Alexander
-
-          Motin
-         &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-        <p>snd_hda(4) audio driver was significantly improved to provide
-        better functionality according to High Definition Audio (HDA) and
-        Universal Audio Architecture (UAA) specifications.</p>
-
-        <p>According to HDA specification, driver now supports multiple
-        codecs per HDA bus and multiple audio functional groups per
-        codec.</p>
-
-        <p>According to UAA specification, driver now implements idea of
-        multiple logical audio devices per audio functional group. It
-        means, that depending on specific system needs, single audio
-        codec may provide several independent functions. For example,
-        main multichannel output, headset input/output and digital
-        SPDIF/HDMI audio input/output. Each of these functions are
-	provided as separate pcm devices and can be used independently.</p>
-
-        <p>Comparing to ALSA and OSS HDA drivers which are heavily tuned
-        to support each specific codec in every specific system, this
-        driver uses advanced codec tracing logic which allows it to
-        support most of existing HDA codecs and systems without any
-        special tuning, using only information provided by system and
-        codec itself. This also allows user to widely reconfigure logical
-        audio devices in his system for his own needs, just by specifying
-        wanted audio connectors usage in device.hints.</p>
-
-        <p>Also new driver implements SPDIF/HDMI digital audio,
-        suspend/resume and initial parts of multichannel support.</p>
-    <h3>Open tasks:</h3><ol><li>Implement input-to-output audio bypass tracing for codecs
-      where bypass signal is not taken from main input mixer.</li><li>Improve amplifiers control logic for cases where one signal
-      can be controlled in several points.</li><li>Implement multichannel playback, that required significant
-      sound(4) modifications.</li></ol><hr /><h2><a name="Multi-IPv4/v6/no-IP-jails" href="#Multi-IPv4/v6/no-IP-jails" id="Multi-IPv4/v6/no-IP-jails">Multi-IPv4/v6/no-IP jails</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sources.zabbadoz.net/FreeBSD/jail.html" title="http://sources.zabbadoz.net/FreeBSD/jail.html">Web page for regularly updates and patches</a></td><td>
-	    URL: <a href="http://sources.zabbadoz.net/FreeBSD/jail.html" title="Web page for regularly updates and patches">http://sources.zabbadoz.net/FreeBSD/jail.html</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50">Perforce tree</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50" title="Perforce tree">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/bz/jail/&amp;rc=s&amp;c=kmz@//depot/user/bz/jail/?ac=43&amp;mx=50</a></td></tr></table><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The multi-IPv4/v6/no-IP jails project patch has finally been
-      committed to FreeBSD-CURRENT at the end of November.</p>
-
-      <p>As an alternate solution to full network stack virtualization,
-      this work shall provide a lightweight solution for multi-IP
-      virtualization. The changes are even more important because of the
-      emerging demand for IPv6. Ideally this will be merged to FreeBSD 7
-      before 7.2-RELEASE and stay in FreeBSD 8 for the transitional
-      period to full network stack virtualization.</p>
-
-      <p>Since the commit a few minor things have been fixed and work to
-      address most of the remaining old jails PRs has almost been
-      finished. The fallout from ports breakage has been handled with
-      help from Erwin Lansing from the PortMgr Team.</p>
-    <hr /><h2><a name="Network-Stack-Virtualization" href="#Network-Stack-Virtualization" id="Network-Stack-Virtualization">Network Stack Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Image" title="http://wiki.FreeBSD.org/Image">Wiki VImage overview page.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Image" title="Wiki VImage overview page.">http://wiki.FreeBSD.org/Image</a></td></tr><tr><td><a href="http://www.FreeBSDfoundation.org/project%20announcements.shtml#Bjoern" title="http://www.FreeBSDfoundation.org/project%20announcements.shtml#Bjoern">FreeBSD Foundation funding.</a></td><td>
-	    URL: <a href="http://www.FreeBSDfoundation.org/project%20announcements.shtml#Bjoern" title="FreeBSD Foundation funding.">http://www.FreeBSDfoundation.org/project%20announcements.shtml#Bjoern</a></td></tr></table><p>
-	Contact:
-          Bjoern A.
-
-          Zeeb
-         &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Marko
-
-          Zec
-         &lt;<a href="mailto:zec@FreeBSD.org">zec@FreeBSD.org</a>&gt;
-	</p>
-      <p>The network stack virtualization project aims at extending the
-      FreeBSD kernel to maintain multiple independent instances of
-      networking state. This allows for networking independence between
-      jail-like environments, each maintaining its own private network
-      interfaces, IPv4 and IPv6 network and port address space, routing
-      tables, IPSec configuration, firewalls, and more.</p>
-
-      <p>During BSDCan 2007 an initial commit plan had been worked out.
-      The Developer Summit at Cambridge in August brought the first parts
-      of VImage into the kernel. Marko gave a summary and outlook at
-      EuroBSDCon in Strasbourg. From autumn until December all but the
-      last step had been committed by Marko.</p>
-
-      <p>Druing December Bjoern was able to work full time on VImage
-      because of FreeBSD Foundation funding. In addition to helping with
-      reviews, summarizing things on the Wiki, a virtual cross-over
-      Ethernet-like interface pair was developed to be able to bring
-      networking to an instances without the mandatory need of
-      netgraph.</p>
-
-      <p>The next steps will be to bring in the most important last step
-      giving us multiple network stacks. After that all developers will
-      be able to help to find (and fix) bugs. Further subsystems not yet
-      addressed will need to be virtualized then. In addition to this
-      Jamie Gritton's management interface will be imported.</p>
-    <hr /><h2><a name="PmcTools" href="#PmcTools" id="PmcTools">PmcTools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/PmcTools" title="http://wiki.FreeBSD.org/PmcTools">Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PmcTools" title="Wiki Page">http://wiki.FreeBSD.org/PmcTools</a></td></tr><tr><td><a href="http://code.google.com/p/pmctools/issues" title="http://code.google.com/p/pmctools/issues">Bug List</a></td><td>
-	    URL: <a href="http://code.google.com/p/pmctools/issues" title="Bug List">http://code.google.com/p/pmctools/issues</a></td></tr></table><p>
-	Contact:
-          Joseph
-
-          Koshy
-         &lt;<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for Intel (TM) Atom/Core/Core2 family PMCs was added to
-      PmcTools. Bugs in the toolset were tracked down and fixed, and the
-      ABI between libpmc(3) and hwpmc(4) was reworked to hopefully be
-      more future proof.</p>
-    <hr /><h2><a name="SD/MMC-subsystem" href="#SD/MMC-subsystem" id="SD/MMC-subsystem">SD/MMC subsystem</a></h2><p>
-	Contact:
-          Alexander
-
-          Motin
-         &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          M. Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-        <p>FreeBSD mmc(4)/mmcsd(4) stack was improved to support all
-        MMC/SD card types existing now. Support was added for SD High
-        Capacity (SDHC) cards and MultiMediaCards (MMC) memory cards of
-        normal (up to 2GB) and high capacity. Support was also added
-	for 4/8bits wide buses, High Speed timings and multi-block
-	transfers allows to reach speeds up to 25MB/s (SD) and 52MB/s
-	(MMC) depending on which card and controller was used.</p>
-
-        <p>Added SD Host Controller driver, sdhci(4), that implements
-        support for SD specification compatible PCI SD/MMC card readers
-        to be used with mmc(4)/mmcsd(4) stack. Driver supports PIO and
-        DMA transfers, 1/4bits buses, high speed timings, card
-        insert/remove detection and write protection.</p>
-    <h3>Open tasks:</h3><ol><li>Many of the existing SD Host Controllers have undocumented
-      registers beyond SD specification. Some of them are unable to
-      detect the card without some additional initialization
-      implemented.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/powerpc-for-AMCC/IBM-PPC440/460" href="#FreeBSD/powerpc-for-AMCC/IBM-PPC440/460" id="FreeBSD/powerpc-for-AMCC/IBM-PPC440/460">FreeBSD/powerpc for AMCC/IBM PPC440/460</a></h2><p>
-	Contact:
-          Rafal
-
-          Jaworowski
-         &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>This work is bringing support for another Book-E style PowerPC
-      implementation (PPC440/460 core) embedded in a wide range of
-      system-on-chip devices. Current state highlights:</p>
-
-      <ul>
-        <li>Locore kernel initialisation</li>
-
-        <li>TLB handling</li>
-
-        <li>Console (UART)</li>
-
-        <li>Interrupts controller (UIC)</li>
-
-        <li>USB controller (OHCI, EHCI)</li>
-
-        <li>Multi user operation</li>
-      </ul>
-
-      <p>The CPU layer (kernel start-up, TLB handling) is derived from
-      existing E500 support. Eventually the code will be re-factored so
-      that the common logic is shared between processor variations and
-      only the lowest-level routines are provided separately. A number of
-      drivers for peripherals integrated on the chip needs to be written
-      (Ethernet, PCI/PCI-Express, crypto engines, SATA, I2C, SPI, GPIO
-      and others).</p>
-    <hr /><h2><a name="FreeBSD/sparc64-UltraSPARC-III-support" href="#FreeBSD/sparc64-UltraSPARC-III-support" id="FreeBSD/sparc64-UltraSPARC-III-support">FreeBSD/sparc64 UltraSPARC III support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~marius/8.0-20090111-SNAP-sparc64-disc1.iso.gz" title="http://people.FreeBSD.org/~marius/8.0-20090111-SNAP-sparc64-disc1.iso.gz"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~marius/8.0-20090111-SNAP-sparc64-disc1.iso.gz" title="">http://people.FreeBSD.org/~marius/8.0-20090111-SNAP-sparc64-disc1.iso.gz</a></td></tr></table><p>
-	Contact:
-          Marius
-
-          Strobl
-         &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD 8.0-CURRENT now has basic support for sun4u-machines
-      based on UltraSPARC III and beyond. This is still a work in
-      progress though due to the diversity of these machines, hardware
-      errata and bugs in machine independent parts of FreeBSD showing up.
-      A install image with the latest code which in comparison to the
-      official snapshot 200812 contains more dcons(4) fixes, an isp(4)
-      working with 10160 and 12160 on sparc64, an endian-clean mpt(4) as
-      needed for the on-board controller found in Fire V440, workarounds
-      needed for Fire V880 and a fix for machines with more than 8GB of
-      RAM (tested with 16GB) are available at the above URL. Known working
-      machines so far are:</p>
-
-      <ul>
-        <li>Blade 1000</li>
-        <li>Blade 1500</li>
-        <li>Blade 2000</li>
-        <li>Fire 280R</li>
-        <li>Fire V210</li>
-        <li>Fire V440 (except for the on-board NICs)</li>
-        <li>Fire V880</li>
-        <li>Netra 20/Netra T4</li>
-      </ul>
-
-      <p>The stability of FreeBSD on these machines is en par with that
-      on pre-USIII-based sun4u-machines. Machines similar to the ones
-      above like for example Fire V240 should also just work with all
-      essential on-board devices, i.e. serial console, ATA/SCSI
-      controller and NIC, being supported. So far the intention is to MFC
-      this code in time for FreeBSD 7.2.</p>
-    <h3>Open tasks:</h3><ol><li>Apart from serial devices, only cards supported by creator(4)
-      are currently usable as console, i.e. not even machfb(4) works in
-      sun4u-machines based on UltraSPARC III or beyond at this point (it
-      will trigger a RED state exception, which should not be that hard
-      to fix though), let alone XVR graphics cards.</li><li>A driver for the Sun Cassini/Cassini+ as well as National
-      Semiconductor DP83065 Saturn Gigabit NICs found on-board for
-      example in Fire V440 and as add-on cards is under development but
-      still needs some work.</li><li>There is no driver for controlling the fans in machines based
-      on the Excalibur board, yet. This means that Blade 1000/2000 are
-      not very usable as workstations so far due to the noise caused by
-      the fans permanently running at full speed.</li><li>There is no support for host-to-PCI-Express or host-to-PCI-X
-      bridges so far, at least for the latter due to lack of access to
-      such machines. Adding support for the XMITS PCI-X bridges to the
-      existing schizo(4) should be rather straightforward, PCI-Express
-      will require a new driver and probably some additional tweaking
-      though.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Greek-Documentation-Project" href="#The-FreeBSD-Greek-Documentation-Project" id="The-FreeBSD-Greek-Documentation-Project">The FreeBSD Greek Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDgr.org" title="http://www.FreeBSDgr.org">Greek Documentation Project Wiki and test builds</a></td><td>
-	    URL: <a href="http://www.FreeBSDgr.org" title="Greek Documentation Project Wiki and test builds">http://www.FreeBSDgr.org</a></td></tr></table><p>
-	Contact:
-          Giorgos
-
-          Keramidas
-         &lt;<a href="mailto:keramida@FreeBSD.org">keramida@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Manolis
-
-          Kiagias
-         &lt;<a href="mailto:manolis@FreeBSD.org">manolis@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Greek Documentation Project managed to complete a
-      significant amount of work during 2008. The first ten chapters of
-      the Handbook are now completely translated and kept in sync with
-      the English text. Work is also progressing nicely in the second
-      part of The Handbook, with many new translated chapters. At this
-      pace, we hope to have a complete Greek Handbook by 8.0-RELEASE.</p>
-
-      <p>More volunteers are always welcome of course, as there is still
-      plenty of work to be done.</p>
-    <h3>Open tasks:</h3><ol><li>Complete the Greek translation of the Handbook (about ten
-      chapters remaining)</li><li>Complete the Greek translation of the FAQ (currently at
-      around 40%)</li><li>Translate more documentation (articles) to Greek</li><li>Begin a Greek website on FreeBSD.org (volunteers
-      needed)</li></ol><hr /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu" title="http://www.FreeBSD.org/hu">Hungarian Web Page for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu" title="Hungarian Web Page for FreeBSD">http://www.FreeBSD.org/hu</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu" title="http://www.FreeBSD.org/doc/hu">Hungarian Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>Hungarian translation of the
-      <em>FreeBSD Documentation Project Primer for New Contributors</em>
-
-      has been finished and now it is available both
-      <a href="http://www.FreeBSD.org/doc/hu/books/fdp-primer" shape="rect">online</a>
-
-      and
-      <a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/hu/books/fdp-primer" shape="rect">
-      for download</a>.</p>
-
-      <p>We hope that having the FDP Primer translated will encourage
-      people to help our work. There is always place in our team, every
-      submitted translation or feedback is appreciated and very
-      welcome.</p>
-
-      <p>Beside the continuous maintenance of the Hungarian documentation
-      and web pages, a new article translation has been added to the
-      Hungarian Documentation Set,
-      <a href="http://www.FreeBSD.org/doc/hu/articles/cups" shape="rect">CUPS</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Read the translations, send feedback</li><li>Translate web pages</li><li>Translate articles</li><li>Translate release notes for -CURRENT and 7.X</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSD-licensed-grep" href="#BSD-licensed-grep" id="BSD-licensed-grep">BSD-licensed grep</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2008/gabor_textproc/&amp;c=vqZ@//depot/projects/soc2008/gabor_textproc/grep/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2008/gabor_textproc/&amp;c=vqZ@//depot/projects/soc2008/gabor_textproc/grep/?ac=83">Project repository</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2008/gabor_textproc/&amp;c=vqZ@//depot/projects/soc2008/gabor_textproc/grep/?ac=83" title="Project repository">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2008/gabor_textproc/&amp;c=vqZ@//depot/projects/soc2008/gabor_textproc/grep/?ac=83</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Some bugs have been fixed in the buffering and binary file
-      detection parts of grep. Due to the differences between the GNU
-      regexp library and our libc regexp implementation, I switched to the
-      GNU library so that we can maintain an acceptable level of
-      compatibility. The desired option would be to drop both GNU grep
-      and the GNU regexp library, but unfortunately we cannot just do that
-      because of these incompatibilities. Accordingly, the first step
-      should be replacing grep and then we should review and optimize our
-      regexp library. With this decision, BSD grep has acquired a higher
-      level of compatibility and now seems to be much more useful.</p>
-    <h3>Open tasks:</h3><ol><li>Make a portbuild run with BSD grep and fix possible
-      bugs.</li></ol><hr /><h2><a name="The-FreeBSD-Forums" href="#The-FreeBSD-Forums" id="The-FreeBSD-Forums">The FreeBSD Forums</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.FreeBSD.org/" title="http://forums.FreeBSD.org/"></a></td><td>
-	    URL: <a href="http://forums.FreeBSD.org/" title="">http://forums.FreeBSD.org/</a></td></tr></table><p>
-	Contact:
-          FreeBSD Forums
-
-          Admins
-         &lt;<a href="mailto:forum-admins@">forum-admins@</a>&gt;
-	<br />
-	Contact:
-          FreeBSD Forums
-
-          Moderators
-         &lt;<a href="mailto:forum-moderators@">forum-moderators@</a>&gt;
-	</p>
-      <p>The FreeBSD forums were publicly launched on November 16th, 2008
-      as a complementary support channel to our great mailing lists.</p>
-
-      <p>There were almost 2000 new users registered in the first three
-      days and each day we receive about 20 new user registrations. After
-      less than three months after going public, we are now serving
-      around 10,000 posts in 1,500 threads. We have received very
-      positive feedback from our users, which we take as a good
-      compensation for our efforts put into this project.</p>
-    <hr /><h2><a name="YouTube-Channel-for-BSD" href="#YouTube-Channel-for-BSD" id="YouTube-Channel-for-BSD">YouTube Channel for BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.youtube.com/bsdconferences" title="http://www.youtube.com/bsdconferences">BSD Conferences YouTube Channel</a></td><td>
-	    URL: <a href="http://www.youtube.com/bsdconferences" title="BSD Conferences YouTube Channel">http://www.youtube.com/bsdconferences</a></td></tr><tr><td><a href="http://murrayFreeBSD.blogspot.com/2008/12/new-channel-on-youtube-for-bsd.html" title="http://murrayFreeBSD.blogspot.com/2008/12/new-channel-on-youtube-for-bsd.html">Channel Announcement</a></td><td>
-	    URL: <a href="http://murrayFreeBSD.blogspot.com/2008/12/new-channel-on-youtube-for-bsd.html" title="Channel Announcement">http://murrayFreeBSD.blogspot.com/2008/12/new-channel-on-youtube-for-bsd.html</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/VideoProductionAndPublishing" title="http://wiki.FreeBSD.org/VideoProductionAndPublishing">Video Production and Publishing Wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/VideoProductionAndPublishing" title="Video Production and Publishing Wiki">http://wiki.FreeBSD.org/VideoProductionAndPublishing</a></td></tr></table><p>
-	Contact:
-          Murray
-
-          Stokely
-         &lt;<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new <a href="http://www.youtube.com/bsdconferences" shape="rect">channel</a>
-      has been setup on <a href="http://www.youtube.com" shape="rect">YouTube</a>
-      explicitly for BSD conference recordings. This channel does not
-      have the normal 10 minute limit so full high quality presentations
-      from 30 minutes to nearly 2 hours have been uploaded. So far over
-      23 videos are available from MeetBSD and NYCBSDCon, with more from
-      BSDCan and AsiaBSDCon coming soon.</p>
-
-      <p>We are currently looking for more videos from
-      <a href="http://www.bsdcan.org" shape="rect">BSDCan</a>,
-      <a href="http://www.eurobsdcon.org" shape="rect">EuroBSDCon</a>,
-      <a href="http://www.asiabsdcon.org" shape="rect">AsiaBSDCon</a>,
-      etc to upload to the channel. We also need help in creating
-      subtitles for each video in various languages. If you would like to
-      help out in generating subtitles for your language or if you have
-      old video content from one of the above BSD conferences please let
-      us know.</p>
-    <h3>Open tasks:</h3><ol><li>Adding subtitles in various languages to all of the technical
-      talks.</li><li>Finding more videos from previous conferences to
-      upload.</li><li>Audio post-processing. If anyone has experience removing
-      audio artifacts from a video recording we would love to talk to you
-      about working some magic on raw footage we have before uploading it
-      to YouTube.</li><li>We could use additional tips for improved video recording and
-      post-processing added to our video production and publishing
-      wiki.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2009-01-2009-03.html b/website/content/en/status/report-2009-01-2009-03.html
deleted file mode 100644
index 461fd12665..0000000000
--- a/website/content/en/status/report-2009-01-2009-03.html
+++ /dev/null
@@ -1,806 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Since the last Status Reports there has been interesting progress
-    in FreeBSD Development. FreeBSD 7.2 was released just a few days ago.
-    Some of the highlights include: Support for superpages in the FreeBSD
-    Virtual Memory subsystem. The FreeBSD Kernel Virtual Address space
-    has been increased to 6GB on amd64. An updated jail(8) subsystem that
-    supports multi-IPv4/IPv6/noIP and much more. Lots of FreeBSD
-    Developers are in Ottawa, Canada attending the FreeBSD Developer
-    Summit that is before BSDCan. BSDCan officially starts tomorrow and
-    should cover lots of interesting topics, see the
-    <a href="http://www.bsdcan.org/2009/" shape="rect">BSDCan Website</a>
-
-    for more information.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#Device-mmap()-Extensions">Device mmap() Extensions</a></li><li><a href="#OpenBSM">OpenBSM</a></li><li><a href="#Release-Engineering">Release Engineering</a></li><li><a href="#Sysinfo---a-set-of-scripts-which-document-your-system">Sysinfo - a set of scripts which document your system</a></li><li><a href="#TrustedBSD-MAC-Framework-in-GENERIC">TrustedBSD MAC Framework in GENERIC</a></li><li><a href="#VFS/NFS-DTrace-Probes">VFS/NFS DTrace Probes</a></li><li><a href="#VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-BugBusting-Team">FreeBSD BugBusting Team</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/powerpc-G5-Support">FreeBSD/powerpc G5 Support</a></li><li><a href="#FreeBSD/sparc64-UltraSPARC-III-support">FreeBSD/sparc64 UltraSPARC III support</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Dutch-Documentation-Project">Dutch Documentation Project</a></li><li><a href="#German-Documentation-Project">German Documentation Project</a></li><li><a href="#Hungarian-Documentation-Project">Hungarian Documentation Project</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#BSD-licensed-text-processing-tools">BSD-licensed text-processing tools</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang" title="http://wiki.freebsd.org/BuildingFreeBSDWithClang">Building FreeBSD with Clang</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang" title="Building FreeBSD with Clang">http://wiki.freebsd.org/BuildingFreeBSDWithClang</a></td></tr><tr><td><a href="http://git.hoeg.nl/?p=llvm-bmake" title="http://git.hoeg.nl/?p=llvm-bmake">Clang patchset</a></td><td>
-	    URL: <a href="http://git.hoeg.nl/?p=llvm-bmake" title="Clang patchset">http://git.hoeg.nl/?p=llvm-bmake</a></td></tr><tr><td><a href="http://clang.llvm.org/" title="http://clang.llvm.org/">Clang website</a></td><td>
-	    URL: <a href="http://clang.llvm.org/" title="Clang website">http://clang.llvm.org/</a></td></tr></table><p>
-	Contact:
-          Ed
-
-          Schouten
-         &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Roman
-
-          Divacky
-         &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Pawel
-
-          Worach
-         &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	</p>
-      <p>The last 3-4 months we've been working together with the LLVM
-      developers to discuss any bugs and issues we are experiencing with
-      their Clang compiler frontend. The FreeBSD project is looking at
-      the possibility to replace GCC with Clang as a system compiler. It
-      can compile 99% of the FreeBSD world and can compile booting kernel
-      on i386/amd64 but it still contains bugs and its C++ support is
-      still immature.</p>
-
-      <p>Ed is maintaining a patchset for the FreeBSD sources to replace
-      cc(1) by a Clang binary and bootstrap almost all sources with the
-      Clang compiler.</p>
-
-      <p>The LLVM developers are very helpful fixing most of the bugs
-      we've reported (over 100). Unfortunately we are currently blocked
-      on some bug reports that prevent us from building libc, libm,
-      libcrypto and various CDDL libraries with Clang but the FreeBSD
-      kernel itself compiles and boots.</p>
-    <h3>Open tasks:</h3><ol><li>Testing Clang with compilation of various applications and
-      reporting bugs.</li><li>Testing the llvm-bmake branch to find more bugs.</li><li>Arranging an experimental ports build.</li></ol><hr /><h2><a name="Device-mmap()-Extensions" href="#Device-mmap()-Extensions" id="Device-mmap()-Extensions">Device mmap() Extensions</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/~jhb/pat/" title="http://www.FreeBSD.org/~jhb/pat/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/~jhb/pat/" title="">http://www.FreeBSD.org/~jhb/pat/</a></td></tr></table><p>
-	Contact:
-          John
-
-          Baldwin
-         &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>GPU device drivers are increasingly requiring more sophisticated
-      support for mapping objects into both userland and the kernel. For
-      example, memory used for textures often needs to be mapped
-      Write-Combining rather than Write-Back. I have recently created
-      three patches to provide several extensions.</p>
-
-      <p>The first patch allows device drivers to use a different VM
-      object to back specific mmap() calls instead of always using the
-      device pager. The second patch introduces a new VM object type that
-      can map an arbitrary set of physical address ranges. This can be
-      used to let userland mmap PCI BARs, etc. The third patch allows
-      memory mappings to use different caching modes (e.g.
-      Write-Combining or Uncacheable).</p>
-
-      <p>Together I believe these patches provide the remaining pieces
-      needed for an Nvidia amd64 driver. They will also be useful for
-      future Xorg DRM support as well. The current set of patches can be
-      safely merged back to 7.x as well.</p>
-
-      <p>Currently I am waiting for review and feedback from several
-      folks. I am hopeful that these patches will be in HEAD soon, prior
-      to the 8.0 freeze.</p>
-    <hr /><h2><a name="OpenBSM" href="#OpenBSM" id="OpenBSM">OpenBSM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openbsm.org/" title="http://www.openbsm.org/">OpenBSM web page</a></td><td>
-	    URL: <a href="http://www.openbsm.org/" title="OpenBSM web page">http://www.openbsm.org/</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD audit mailing list
-         &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project has now released OpenBSM 1.1, the second
-      production release of the OpenBSM code base. OpenBSM 1.1 has been
-      merged to FreeBSD 8-CURRENT, and will be merged to 7-STABLE before
-      FreeBSD 7.3. Major changes since OpenBSM 1.0 include:
-      <ul>
-        <li>Trail files now include the host where the trail is
-        generated. Crash recovery has been improved. Trail expiration
-        based on size and date is now supported; by default trail files
-        will be expired after 10MB of trails. The default individual
-        trail limit is now 2MB.</li>
-
-        <li>Mac OS X Snow Leopard is now a fully supported platform;
-        launchd(8) can now be used to launchd auditd(8). Command line
-        tools and libraries are now supported on Mac OS X Leopard.</li>
-
-        <li>Extended header tokens are now supported, allowing audit
-        trails to be tagged with a host identifier. IPv6 addresses are
-        now supported in subject tokens. BSM token and record types have
-        been further synchronized to OpenSolaris; support for many new
-        system calls has been added. Local errors and socket types are
-        mapped to and from BSM values.</li>
-      </ul>
-
-      Since the last test release, OpenBSM 1.1 beta 1, 32/64-bit
-      compatibility has been fixed for the auditon(2) system call. A
-      default "expire-after" of 10MB is now set in audit_control(5).
-      Local fcntl(2) arguments are now mapped to wire BSM versions using
-      new APIs. The audit_submit(3) man page has been fixed. A new audit
-      event class has been added for post-login authentication and access
-      control events.</p>
-    <h3>Open tasks:</h3><ol><li>Migrate to sbufs in token-encoding.</li><li>Support for auditing NFS RPCs.</li></ol><hr /><h2><a name="Release-Engineering" href="#Release-Engineering" id="Release-Engineering">Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-          Release Engineering Team
-         &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team (with lots of help from lots of
-      other people) released FreeBSD 7.2 on May 4th, 2009. During this
-      period we have also begun reminding developers of the upcoming
-      FreeBSD 8.0 release cycle which is scheduled to begin in early June
-      2009 with release targeted at early September 2009.</p>
-    <hr /><h2><a name="Sysinfo---a-set-of-scripts-which-document-your-system" href="#Sysinfo---a-set-of-scripts-which-document-your-system" id="Sysinfo---a-set-of-scripts-which-document-your-system">Sysinfo - a set of scripts which document your system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://danger.rulez.sk/index.php/2009/04/14/sysinfo-a-set-of-scripts-which-document-your-freebsd-system/" title="http://danger.rulez.sk/index.php/2009/04/14/sysinfo-a-set-of-scripts-which-document-your-freebsd-system/">Public release announcement</a></td><td>
-	    URL: <a href="http://danger.rulez.sk/index.php/2009/04/14/sysinfo-a-set-of-scripts-which-document-your-freebsd-system/" title="Public release announcement">http://danger.rulez.sk/index.php/2009/04/14/sysinfo-a-set-of-scripts-which-document-your-freebsd-system/</a></td></tr><tr><td><a href="https://forums.freebsd.org/showthread.php?p=19321" title="https://forums.freebsd.org/showthread.php?p=19321">The FreeBSD Forums thread</a></td><td>
-	    URL: <a href="https://forums.freebsd.org/showthread.php?p=19321" title="The FreeBSD Forums thread">https://forums.freebsd.org/showthread.php?p=19321</a></td></tr></table><p>
-	Contact:
-          Daniel
-
-          Gerzo
-         &lt;<a href="mailto:danger@FreeBSD.org">danger@FreeBSD.org</a>&gt;
-	</p>
-      <p>
-      <em>Sysinfo</em>
-
-      is a shell script, the purpose of which is to automatically gather system
-      information and document the hardware and software configuration of the
-      given host system. The goal is to provide a system operator with
-      descriptive information about an unknown FreeBSD installation.</p>
-
-      <p>It consists of several modules (also shell scripts), thus is
-      easily extensible and provides an easy way to inspect overall
-      system configuration.</p>
-
-      <p>It has been written as part of my Bachelor thesis and its
-      development is a work in progress. Therefore, I would appreciate if
-      you could provide me with some feedback as I will defend my thesis
-      soon. Your feedback is welcome at the
-      <a href="https://forums.freebsd.org/showthread.php?p=19321" shape="rect">
-      forums</a>
-
-      , or alternatively you can send me a private email.</p>
-
-      <p>The tool itself can now be installed using the Ports tree from
-      the
-      <a href="http://www.freshports.org/sysutils/sysinfo" shape="rect">
-      sysutils/sysinfo</a>
-
-      port.</p>
-    <h3>Open tasks:</h3><ol><li>Receive additional feedback.</li><li>Perform more testing.</li><li>Extend and improve the tool.</li></ol><hr /><h2><a name="TrustedBSD-MAC-Framework-in-GENERIC" href="#TrustedBSD-MAC-Framework-in-GENERIC" id="TrustedBSD-MAC-Framework-in-GENERIC">TrustedBSD MAC Framework in GENERIC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.trustedBSD.org/mac.html" title="http://www.trustedBSD.org/mac.html">TrustedBSD MAC home page</a></td><td>
-	    URL: <a href="http://www.trustedBSD.org/mac.html" title="TrustedBSD MAC home page">http://www.trustedBSD.org/mac.html</a></td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          TrustedBSD discussion mailing list
-         &lt;<a href="mailto:trustedbsd-discuss@TrustedBSD.org">trustedbsd-discuss@TrustedBSD.org</a>&gt;
-	</p>
-      <p>There is on-going work to allow "options MAC" to be included in
-      the GENERIC kernel for 8.0. This primarily consists of performance
-      work to reduce overhead when policies are used, and eliminate when
-      none are configured. Work to date includes:
-      <ul>
-        <li>The MAC Framework now detects which object types are labeled
-        by policies, and MAC label storage is not allocated when it won't
-        be used.</li>
-
-        <li>Add MAC Framework DTrace probes so allow more easy analysis
-        of MAC Framework and policy interactions.</li>
-
-        <li>Eliminate mutex-protected reference count used to prevent
-        module unload during entry point invocation, and replace with an
-        sx lock and an rwlock, respectively for long-sleepable and
-        short-sleepable entry points, significantly lowering the overhead
-        of entering the MAC Framework. If no dynamic policies are loaded,
-        no locking overhead is taken.</li>
-      </ul>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Move to rmlocks for non-sleepable entry points to reduce
-      cache line thrashing under load.</li><li>Macroize invocation of MAC Framework entry points from the
-      kernel, and perform caller-side determination of whether MAC is
-      enabled in order to avoid additional function call overhead in the
-      caller path if MAC is disabled.</li></ol><hr /><h2><a name="VFS/NFS-DTrace-Probes" href="#VFS/NFS-DTrace-Probes" id="VFS/NFS-DTrace-Probes">VFS/NFS DTrace Probes</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new DTrace provider, dtnfsclient, has been added to the
-      FreeBSD 8.x kernel, and will be merged to 7.x before 7.3. The
-      following probes are available:
-      <ul>
-        <li>nfsclient:{nfs2,nfs3}:{procname}:start - NFSv2 and NFSv3 RPC
-        start probes</li>
-
-        <li>nfsclient:{nfs2,nfs3}:{procname}:done - NFSv2 and NFSv3 RPC
-        done probes</li>
-
-        <li>nfsclient:accesscache:: - NFS access cache
-        flush/hit/miss/load probes</li>
-
-        <li>nfsclient:attrcache:: - NFS attribute cache
-        flush/hit/miss/done</li>
-      </ul>
-
-      In addition, a number of VFS probes have been added:
-      <ul>
-        <li>vfs:vop:{vopname}:entry - VOP entry probe</li>
-
-        <li>vfs:vop:{vopname}:return - VOP return probe</li>
-
-        <li>vfs:namei:lookup:entry - VFS name lookup entry probe</li>
-
-        <li>vfs:namei:lookup:return - VFS name lookup return probe</li>
-
-        <li>vfs:namecache:*:* - VFS namecache
-        enter/enter_negative/fullpath_enter/fullpath_hit/fullpath_miss/fullpath_return/lookup_hit/lookup_hit_negative/lookup_miss/purge/purge_negative/purgevfs/zap/zap_negative
-        probes</li>
-      </ul>
-
-      These probes make it much easier to trace NFS and VFS events.</p>
-    <h3>Open tasks:</h3><ol><li>Add VFSOP tracing.</li><li>Add RPC-layer tracing, such as RPC retransmits.</li><li>Provide decoded NFS RPCs in order to expose transaction IDs
-      and file handles.</li></ol><hr /><h2><a name="VirtualBox-on-FreeBSD" href="#VirtualBox-on-FreeBSD" id="VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd/" title="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd/">Virtualbox on FreeBSD Announcement</a></td><td>
-	    URL: <a href="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd/" title="Virtualbox on FreeBSD Announcement">http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd/</a></td></tr><tr><td><a href="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd-first-screenshots/" title="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd-first-screenshots/">VirtualBox first Screenshots</a></td><td>
-	    URL: <a href="http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd-first-screenshots/" title="VirtualBox first Screenshots">http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd-first-screenshots/</a></td></tr><tr><td><a href="http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001369.html" title="http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001369.html">SUCCESS from Bernhard Froehlich</a></td><td>
-	    URL: <a href="http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001369.html" title="SUCCESS from Bernhard Froehlich">http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001369.html</a></td></tr></table><p>
-	Contact:
-          Beat
-
-          Gaetzi
-         &lt;<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Bernhard
-
-          Froehlich
-         &lt;<a href="mailto:decke@bluelife.at">decke@bluelife.at</a>&gt;
-	<br />
-	Contact:
-          Dennis
-
-          Herrmann
-         &lt;<a href="mailto:dhn@FreeBSD.org">dhn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Martin
-
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	</p>
-      <p>After the first mail from Alexander Eichner on the vbox-dev
-      mailinglist, we started the work on a VirtualBox port. 6 Days was
-      needed to get VirtualBox to start with over 20 patches. We'd like
-      to say thanks to Alexander Eichner, all the VirtualBox Developers,
-      Gustau Perez and Ulf Lilleengen. If you like to play with the
-      current port you can checkout the port <a href="http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/" shape="rect">
-      here</a>.
-
-      Please do not ping us about any problems, we know about a lot and
-      are still working to get them all solved before we do an official
-      call for testing.</p>
-    <h3>Open tasks:</h3><ol><li>Fix kernel crashes on 7.2-RELEASE.</li><li>Code cleanup.</li><li>Fix errors on AMD64.</li><li>Fix user/permission problems.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-BugBusting-Team" href="#FreeBSD-BugBusting-Team" id="FreeBSD-BugBusting-Team">FreeBSD BugBusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html" title="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html" title="">http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html</a></td></tr></table><p>
-	Contact:
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:bugmeister@">bugmeister@</a>&gt;
-	<br />
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:bugmeister@">bugmeister@</a>&gt;
-	</p>
-      <p>We continue to classify PRs as they arrive, with 'tags'
-      corresponding to the kernel subsystem, or man page references for
-      userland PRs. These tags, in turn, produce lists of PRs sorted both
-
-      <a href="http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html" shape="rect">
-      by tag</a>
-
-      and
-      <a href="http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html" shape="rect">
-      by manpage</a>
-      </p>
-
-      <p>Mark Linimon (linimon@) has created
-      <a href="http://people.freebsd.org/~linimon/annotated_prs.re.html" shape="rect">
-      special reports for the Release Engineering Team</a>
-
-      to help focus on regressions and other areas of interest relating
-      to the release of FreeBSD 7.2 in the coming weeks. This is a
-      refinement of the
-      <a href="http://people.freebsd.org/~linimon/annotated_prs.sample.html" shape="rect">
-      'customized reports for developers'</a>
-
-      announced in the last status report.</p>
-
-      <p>A full list of all the
-      <a href="http://people.freebsd.org/~linimon/studies/prs/" shape="rect">
-      automatically generated reports</a>
-
-      is also available. Any recommendations for reports which do not
-      currently exist but which would be beneficial are welcomed.</p>
-
-      <p>Mark Linimon also continues attempting to define the general
-      problem and investigating possible new work flow models, and will be
-      presenting on the subject at BSDCan.</p>
-
-      <p>The list of
-      <a href="http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html" shape="rect">
-      PRs recommended for committer evaluation</a>
-
-      by the BugBusting team continues to receive new additions. This
-      list contains PRs, mostly with patches, that the BugBusting team
-      feel are probably ready to be committed as-is, or are probably
-      trivially resolved in the hands of a committer with knowledge of
-      the particular subsystem. All committers are invited to take a look
-      at this list whenever they have a spare 5 minutes and wish to close
-      a PR.</p>
-
-      <p>Since the last status report, the number of open bugs
-      continued to hover around the 5600 mark, although has began to rise
-      with the 7.2 ports freeze.</p>
-
-      <p>As always, more help is appreciated, and committers and
-      non-committers alike are invited to join us on #freebsd-bugbusters
-      on EFnet and help close stale PRs or commit patches from valid
-      PRs.</p>
-    <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with
-      closing PRs that the team has already analyzed.</li><li>Think of some way for committers to only view PRs that have
-      been in some way 'vetted' or 'confirmed'.</li><li>Generate more publicity for what we've already got in place,
-      and for what we intend to do next.</li><li>Define new categories, classifications, and states for PRs,
-      that will better match our work flow (in progress).</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/powerpc-G5-Support" href="#FreeBSD/powerpc-G5-Support" id="FreeBSD/powerpc-G5-Support">FreeBSD/powerpc G5 Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-          Nathan
-
-          Whitehorn
-         &lt;<a href="mailto:nwhitehorn@freebsd.org">nwhitehorn@freebsd.org</a>&gt;
-	</p>
-      <p>FreeBSD 8.0-CURRENT now has support for PowerPC CPUs operating
-      in the 64-bit bridge mode. This includes the PowerPC 970 (G5) as
-      well as the POWER3 and POWER4. Currently only Apple systems are
-      known to work.</p>
-    <h3>Open tasks:</h3><ol><li>IBM systems currently are not supported due to missing
-      northbridge support.</li><li>Software fan control on SMU-based Apple G5 systems (G5 iMac,
-      later Powermac G5) is not available.</li></ol><hr /><h2><a name="FreeBSD/sparc64-UltraSPARC-III-support" href="#FreeBSD/sparc64-UltraSPARC-III-support" id="FreeBSD/sparc64-UltraSPARC-III-support">FreeBSD/sparc64 UltraSPARC III support</a></h2><p>
-	Contact:
-          Marius
-
-          Strobl
-         &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>Like announced in the previous status report, support for
-      sun4u-machines based on UltraSPARC III and beyond has been MFC'ed
-      to stable/7 (the last missing piece was r190297) and thus will be
-      present in the upcoming 7.2-RELEASE and can be already tested with
-      7.2-RC1. Additionally, as of r191076 machfb(4) has been fixed to
-      work with UltraSPARC III and beyond, that fix unfortunately did not
-      make it into 7.2-RC1 but will be in the final version. The X.Org
-      7.4 and Firefox ports as well as some other gecko-based ones like
-      Seamonkey once again have been fixed to also work and package on
-      sparc64, including on UltraSPARC III and UltraSPARC IIIi based
-      machines equipped with cards driven by creator(4) or machfb(4). The
-      driver for the Sun Cassini/Cassini+ as well as National
-      Semiconductor DP83065 Saturn Gigabit NICs found on-board for
-      example in Fire V440 and as add-on cards is coming along nicely,
-      the last thing which needs to be implemented before it can hit
-      CURRENT is support for jumbo frames.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Dutch-Documentation-Project" href="#Dutch-Documentation-Project" id="Dutch-Documentation-Project">Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/DutchDocumentationProject" title="http://wiki.freebsd.org/DutchDocumentationProject">Overview of the project and current status</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/DutchDocumentationProject" title="Overview of the project and current status">http://wiki.freebsd.org/DutchDocumentationProject</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/nl/" title="http://www.freebsd.org/doc/nl/">Released documentation</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/nl/" title="Released documentation">http://www.freebsd.org/doc/nl/</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=pFl@//depot/projects/docproj_nl/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=pFl@//depot/projects/docproj_nl/?ac=83">Perforce repository</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=pFl@//depot/projects/docproj_nl/?ac=83" title="Perforce repository">http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=pFl@//depot/projects/docproj_nl/?ac=83</a></td></tr></table><p>
-	Contact:
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Ren�
-
-          Ladan
-         &lt;<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Dutch Documentation Project is an ongoing project
-      to translate FreeBSD Documentation into the Dutch language.</p>
-
-      <p>The translation of the Handbook was completed last January. It
-      is kept up-to-date with the English version. Furthermore five
-      articles and the
-      <url href="http://www.evilcoder.org/freebsd-flyer.pdf">flyer</url>
-
-      have been translated.</p>
-
-      <p>Some initial work has been done to translate the website, but
-      most likely more translators are needed to fully realize it.</p>
-    <h3>Open tasks:</h3><ol><li>Recruit more translators.</li><li>Keep the translations up-to-date with the English
-      versions.</li><li>Finish the translation of the FAQ.</li><li>Translate more articles and maybe some books.</li></ol><hr /><h2><a name="German-Documentation-Project" href="#German-Documentation-Project" id="German-Documentation-Project">German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://doc.bsdgroup.de" title="https://doc.bsdgroup.de"></a></td><td>
-	    URL: <a href="https://doc.bsdgroup.de" title="">https://doc.bsdgroup.de</a></td></tr></table><p>
-	Contact:
-          Johann
-
-          Kois
-         &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Martin
-
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	</p>
-      <p>
-        <p>In February 2009 the German version of the FreeBSD Developer's
-        handbook went online. Additionally we managed to update large
-        areas of the FAQ thanks to the contributions of Benedict
-        Reuschling.</p>
-
-        <p>The website (at least the areas we see as relevant for a
-        translation) is translated and updated constantly.</p>
-
-        <p>More volunteers are always welcome of course, as there is
-        still plenty of work to be done.</p>
-      </p>
-    <h3>Open tasks:</h3><ol><li>Update the existing documentation set (especially the
-      handbook).</li><li>Read the translations. Check for problems/mistakes. Send
-      feedback.</li></ol><hr /><h2><a name="Hungarian-Documentation-Project" href="#Hungarian-Documentation-Project" id="Hungarian-Documentation-Project">Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu" title="http://www.FreeBSD.org/hu">Hungarian Web Page for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu" title="Hungarian Web Page for FreeBSD">http://www.FreeBSD.org/hu</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu" title="http://www.FreeBSD.org/doc/hu">Hungarian Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          G�bor
-
-          P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce that the FreeBSD Hungarian web pages
-      have been extended by the following items:</p>
-
-      <ul>
-        <li>Project news entries, staring from 2009 (HTML, RSS, RDF)</li>
-
-        <li>Press releases, starting from 2008 (HTML, RSS)</li>
-
-        <li>Events, starting from 2009 (HTML, RSS)</li>
-
-        <li>Security advisories (HTML, RSS)</li>
-      </ul>
-
-      <p>We are still hoping that having the
-      <a href="http://www.freebsd.org/doc/hu/books/fdp-primer/" shape="rect">FDP
-      Primer</a>
-
-      translated will encourage others to help our work. Feel free to
-      contribute, every submitted line of translation or feedback is
-      appreciated and is highly welcome. For more information on how to
-      contribute, please read the project's
-      <a href="http://www.freebsd.org/hu/docproj/hungarian.html" shape="rect">
-      introduction</a>
-
-      (in Hungarian).</p>
-    <h3>Open tasks:</h3><ol><li>Translate news entries, press releases.</li><li>Translate Release Notes for -CURRENT and 8.X.</li><li>Translate articles.</li><li>Translate web pages.</li><li>Read the translations, send feedback.</li></ol><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="BSD-licensed-text-processing-tools" href="#BSD-licensed-text-processing-tools" id="BSD-licensed-text-processing-tools">BSD-licensed text-processing tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc">Perforce repository</a></td><td>
-	    URL: <a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="Perforce repository">http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc</a></td></tr></table><p>
-	Contact:
-          G�bor
-
-          K�vesd�n
-         &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently, grep is finished and is only waiting for a portbuild
-      test. It is known to be more or less feature complete, while it is
-      much smaller than the GNU version.</p>
-
-      <p>As for sort, there has been some progress with the complete
-      rewrite and it is lacking few options. Performance is to be
-      measured, as well.</p>
-    <h3>Open tasks:</h3><ol><li>Test grep on pointyhat.</li><li>Complete sort with the missing features.</li><li>Do performance measurements for sort and look for possible
-      optimization opportunities.</li><li>Test sort on pointyhat.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2009-04-2009-09.html b/website/content/en/status/report-2009-04-2009-09.html
deleted file mode 100644
index cb69480c70..0000000000
--- a/website/content/en/status/report-2009-04-2009-09.html
+++ /dev/null
@@ -1,1563 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" src="../../layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between April and
-    September 2009.  During that time a lot of work has been done on
-    wide variety of projects, including the Google Summer of Code
-    projects.  The BSDCan conference was held in Ottawa, CA, in May.
-    The EuroBSDCon conference was held in Cambridge, UK, in September.
-    Both events were very successful.
-    A new major version of FreeBSD, 8.0 is to be released soon.
-    If you are wondering what's new in this long-awaited release, read
-    Ivan Voras' excellent <a href="http://ivoras.sharanet.org/freebsd/freebsd8.html" shape="rect">summary</a>.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy the reading.</p><p>Please note that the next deadline for submissions covering
-    reports between October and December 2009 is January 15th,
-    2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#About-Google-Summer-of-Code-2009">About Google Summer of Code 2009</a></li><li><a href="#BSD-licensed-iconv-(Summer-of-Code-2009)">BSD-licensed iconv (Summer of Code 2009)</a></li><li><a href="#BSD-licensed-text-processing-tools-(Summer-of-Code-2008)">BSD-licensed text-processing tools (Summer of Code 2008)</a></li><li><a href="#Ext2fs-Status-report-(Summer-of-Code-2009)">Ext2fs Status report (Summer of Code 2009)</a></li><li><a href="#libnetstat(3)---networking-statistics-(Summer-of-Code-2009)">libnetstat(3) - networking statistics (Summer of Code 2009)</a></li><li><a href="#pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)">pefs - stacked cryptographic filesystem (Summer of Code 2009)</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BSD#-Project">BSD# Project</a></li><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></li><li><a href="#Grand-Central-Dispatch---FreeBSD-port">Grand Central Dispatch - FreeBSD port</a></li><li><a href="#libprocstat(3)---process-statistics">libprocstat(3) - process statistics</a></li><li><a href="#New-BSD-licensed-debugger">New BSD licensed debugger</a></li><li><a href="#NFSv4-ACLs">NFSv4 ACLs</a></li><li><a href="#The-Newcons-project">The Newcons project</a></li><li><a href="#VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-KDE-Team">FreeBSD KDE Team</a></li><li><a href="#FreeBSD-Ports-Management-Team">FreeBSD Ports Management Team</a></li><li><a href="#Release-Engineering-Status-Report">Release Engineering Status Report</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></li><li><a href="#Modular-Congestion-Control">Modular Congestion Control</a></li><li><a href="#Network-Stack-Virtualization">Network Stack Virtualization</a></li><li><a href="#Stream-Control-Transmission-Protocol-(SCTP)">Stream Control Transmission Protocol (SCTP)</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD/ZFS">FreeBSD/ZFS</a></li><li><a href="#hwpmc-for-MIPS">hwpmc for MIPS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li><li><a href="#The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Gecko-Project">FreeBSD Gecko Project</a></li><li><a href="#Portmaster---utility-to-assist-users-with-managing-ports">Portmaster - utility to assist users with managing ports</a></li><li><a href="#Valgrind-suite-on-FreeBSD">Valgrind suite on FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#EuroBSDcon-2009">EuroBSDcon 2009</a></li><li><a href="#FreeBSD-Developer-Summit,-Cambridge-UK">FreeBSD Developer Summit, Cambridge UK</a></li><li><a href="#New-approach-to-the-locale-database">New approach to the locale database</a></li><li><a href="#The-FreeBSD-Forums">The FreeBSD Forums</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="About-Google-Summer-of-Code-2009" href="#About-Google-Summer-of-Code-2009" id="About-Google-Summer-of-Code-2009">About Google Summer of Code 2009</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd" title="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd">FreeBSD GSoC Homepage</a></td><td>
-	    URL: <a href="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd" title="FreeBSD GSoC Homepage">http://socghop.appspot.com/org/home/google/gsoc2009/freebsd</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SummerOfCode2009Projects" title="http://wiki.freebsd.org/SummerOfCode2009Projects">FreeBSD GSoC 2009 Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SummerOfCode2009Projects" title="FreeBSD GSoC 2009 Wiki">http://wiki.freebsd.org/SummerOfCode2009Projects</a></td></tr></table><p>
-	Contact: 
-	  Brooks
-
-	  Davis
-	 &lt;<a href="mailto:brooks@freebsd.org">brooks@freebsd.org</a>&gt;
-	<br />
-	Contact: 
-	  Tim
-
-	  Kientzle
-	 &lt;<a href="mailto:kientzle@freebsd.org">kientzle@freebsd.org</a>&gt;
-	<br />
-	Contact: 
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@freebsd.org">rwatson@freebsd.org</a>&gt;
-	</p>
-      <p>2009 was The FreeBSD Project's fifth year of participation
-	in the Google Summer of Code.  We had a total of 17 successful projects.
-	Some GSoC code will be shipping with FreeBSD 8.0-RELEASE and others
-	will be	integrated into future releases.</p>
-
-      <p>The FreeBSD GSoC admin team would like to thank Google and
-	our students and mentors of another great year!</p>
-    <hr /><h2><a name="BSD-licensed-iconv-(Summer-of-Code-2009)" href="#BSD-licensed-iconv-(Summer-of-Code-2009)" id="BSD-licensed-iconv-(Summer-of-Code-2009)">BSD-licensed iconv (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borSoC2009" title="http://wiki.freebsd.org/G%C3%A1borSoC2009">BSDL iconv on FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/G%C3%A1borSoC2009" title="BSDL iconv on FreeBSD wiki">http://wiki.freebsd.org/G%C3%A1borSoC2009</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The code has been extracted from NetBSD and has been transformed
-	into an independent shared library.  The basic encodings are
-	well supported.  Almost all forward conversions
-	(foo -&gt; UTF-32) are compatible with GNU but the reverse ones
-	are not so accurate because of GNU's advanced transliteration.
-	Some extra encodings have also been added.  There are two modules,
-	which segfault; they need some debugging.  I can keep working on this
-	project as part of my BSc thesis, so I hope to be able to solve
-	the remaining issues.  Improved GNU compatibility is also very
-	desired (extra command line options for iconv(1), iconvctl(),
-	private interfaces, etc.).</p>
-    <h3>Open tasks:</h3><ol><li>Fix segfaults in Big5 and HZ modules</li><li>Improve transliteration in reverse encodings</li><li>Improve GNU compatibility by implementing extra features</li><li>Verify POSIX compatibility</li><li>Verify GNU compatibility</li><li>Check performance</li></ol><hr /><h2><a name="BSD-licensed-text-processing-tools-(Summer-of-Code-2008)" href="#BSD-licensed-text-processing-tools-(Summer-of-Code-2008)" id="BSD-licensed-text-processing-tools-(Summer-of-Code-2008)">BSD-licensed text-processing tools (Summer of Code 2008)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borSoC2008" title="http://wiki.freebsd.org/G%C3%A1borSoC2008">Wiki page for the project</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/G%C3%A1borSoC2008" title="Wiki page for the project">http://wiki.freebsd.org/G%C3%A1borSoC2008</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project was started as part of Google Summer of Code 2008 but
-	there is still a bit of work to complete some missing parts.
-	The BSD-licensed grep implementation is feature-complete and
-	has a good level of GNU compatibility.  Our only current concern about
-	the BSD-licensed version is to improve its
-	performance.  The GNU variant is much more complex, has about
-	8 KSLOC, while BSD grep is tiny, has only 1.5 KSLOC.  GNU uses
-	some shortcuts and optimizations to speed-up calls to the regex library;
-	that is why it is significantly faster.  My point of view is that
-	such optimizations must be implemented in the regex library,
-	keeping the dependent utilities clean and easy to read.  BSD
-	grep is so tiny that there is hardly any optimization opportunity
-	by simplifying the code, so the regex library is the next important
-	TODO.  There is another issue with the current regex library.
-	It does not support some invalid regular expressions, which work
-	in GNU.  We need to maintain compatibility, so we cannot just drop
-	this feature.  Actually, BSD grep is linked to the GNU regex library
-	to maintain this feature but due to the lack of the mentioned
-	shortcuts, it is still slower than GNU.  Anyway, if we can live
-	with this little performance hit until we get a modern regex library,
-	I think grep is ready to enter HEAD.  As for the regex library,
-	NetBSD's result of the last SoC is worth taking a look.</p>
-
-      <p>The sort utility has been rewritten from scratch.  The existing
-	BSD-licensed implementation could not deal with wide characters
-	by design.  The new implementation is still lacking some features
-	but is quite complete.  There is a performance issue, though.
-	Sorting is a typical algorithmic subject but I am not an algorithmic
-	expert, so my implementation is not completely optimal.  Some help
-	would be welcome with this part.</p>
-
-      <p>The bc/dc utilities have been ported from OpenBSD.  They pass
-	OpenBSD's and GNU's regression tests but they arrived too late to
-	catch 8.X, so they will go to HEAD after the release.</p>
-    <h3>Open tasks:</h3><ol><li>Improve sort's sorting and file merging algorithms</li><li>Complete missing features for sort</li><li>Get a modern regex library for FreeBSD</li></ol><hr /><h2><a name="Ext2fs-Status-report-(Summer-of-Code-2009)" href="#Ext2fs-Status-report-(Summer-of-Code-2009)" id="Ext2fs-Status-report-(Summer-of-Code-2009)">Ext2fs Status report (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/SOC2009AdityaSarawgi" title="http://wiki.freebsd.org/SOC2009AdityaSarawgi">Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SOC2009AdityaSarawgi" title="Wiki Page">http://wiki.freebsd.org/SOC2009AdityaSarawgi</a></td></tr></table><p>
-	Contact: 
-	  Aditya
-
-	  Sarawgi
-	 &lt;<a href="mailto:sarawgi.aditya@gmail.com">sarawgi.aditya@gmail.com</a>&gt;
-	</p>
-      <p>FreeBSD's ext2fs had some parts under GPL.  The aim of my project was
-	to rewrite those parts and free ext2fs from GPL.  I have been
-	successful in rewriting the parts and NetBSD's ext2fs was a great
-	help in this.  Certain critical parts under GPL were also removed due
-	to which the write performance suffered.  I also implemented Orlov
-	Block Allocator for ext2fs.  Currently I am planning to make ext2fs
-	Multiprocessor Safe (MPSAFE).  My work resides in truncs_ext2fs
-	branch of Perforce.</p>
-    <h3>Open tasks:</h3><ol><li>Ext4 support for FreeBSD</li><li>Directory indexing for ext2fs</li><li>Journaling in ext2fs using gjournal</li></ol><hr /><h2><a name="libnetstat(3)---networking-statistics-(Summer-of-Code-2009)" href="#libnetstat(3)---networking-statistics-(Summer-of-Code-2009)" id="libnetstat(3)---networking-statistics-(Summer-of-Code-2009)">libnetstat(3) - networking statistics (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/PGJSoc2009" title="http://wiki.FreeBSD.org/PGJSoc2009">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PGJSoc2009" title="Wiki page">http://wiki.FreeBSD.org/PGJSoc2009</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83">Perforce depot</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83" title="Perforce depot">http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83</a></td></tr></table><p>
-	Contact: 
-	  G�bor
- 	  P�li
-         &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The libnetstat(3) project provides a user-space library API to monitor
-        networking functions with the following benefits:</p>
-
-      <ul>
-        <li>ABI-robust interface making use of accessor functions in
-  	  order to divorce monitoring applications from kernel or user ABI
-	  changes.</li>
-
-        <li>Supports running 32-bit monitoring tools on top of a 64-bit
-	  kernel.</li>
-
-        <li>Improved consistency for both kvm(3) and sysctl(3) when
-	  retrieving information.</li>
-      </ul>
-
-      <p>The supported abstractions are as follows:</p>
-
-      <ul>
-        <li>Active sockets and socket buffers</li>
-        <li>Network interfaces and multicast interfaces</li>
-        <li>mbuf(9) statistics</li>
-        <li>bpf(4) statistics</li>
-        <li>Routing statistics, routing tables, multicast routing</li>
-        <li>Protocol-dependent statistics</li>
-      </ul>
-
-      <p>There is a sample application, called nettop(8), which provides a
-        simple ncurses-based top(1)-like interface for monitoring active
-        connections and network buffer allocations via the library.  A
-        modified version of netstat(1) has also been created to use
-        libnetstat(3) as much as possible.</p>
-    <hr /><h2><a name="pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)" href="#pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)" id="pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)">pefs - stacked cryptographic filesystem (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://blogs.freebsdish.org/gleb/" title="http://blogs.freebsdish.org/gleb/">Gleb's Blog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/gleb/" title="Gleb's Blog">http://blogs.freebsdish.org/gleb/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SOC2009GlebKurtsov" title="http://wiki.freebsd.org/SOC2009GlebKurtsov">Project page in FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SOC2009GlebKurtsov" title="Project page in FreeBSD wiki">http://wiki.freebsd.org/SOC2009GlebKurtsov</a></td></tr></table><p>
-	Contact: 
-          Gleb
-
-          Kurtsou
-         &lt;<a href="mailto:gk@FreeBSD.org">gk@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Stanislav
-
-          Sedov
-         &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	</p>
-      <p>Pefs is a kernel level filesystem for transparently encrypting
-      files on top of other filesystems (like zfs or ufs).  It adds no
-      extra information into files (unlike others), doesn't require
-      cipher block sized io operations, supports per directory/file keys
-      and key chaining, uses unique per file tweak for encryption.
-      Supported algorithms: AES, Camellia, Salsa20.  The code is ready for
-      testing.</p>
-    <h3>Open tasks:</h3><ol><li>Implement encrypted name lookup/readir cache</li><li>Optimize sparse files handling and file resizing</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BSD#-Project" href="#BSD#-Project" id="BSD#-Project">BSD# Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/bsd-sharp/" title="http://code.google.com/p/bsd-sharp/">The BSD# project on Google code</a></td><td>
-	    URL: <a href="http://code.google.com/p/bsd-sharp/" title="The BSD# project on Google code">http://code.google.com/p/bsd-sharp/</a></td></tr><tr><td><a href="http://www.mono-project.org/" title="http://www.mono-project.org/">Mono (Open source .NET Development Framework)</a></td><td>
-	    URL: <a href="http://www.mono-project.org/" title="Mono (Open source .NET Development Framework)">http://www.mono-project.org/</a></td></tr></table><p>
-	Contact: 
-          Romain
-
-          Tarti�re
-         &lt;<a href="mailto:romain@blogreen.org">romain@blogreen.org</a>&gt;
-	</p>
-      <p>The BSD# Project is devoted to porting the Mono .NET framework
-      and applications to the FreeBSD operating system.</p>
-
-      <p>During the past year, the BSD# Team continued to track the Mono
-      development and the lang/mono port have almost always been
-      up-to-date (we however had to skip mono-2.2 because of some
-      regression issues in this release).  Most of our patches have been
-      merged in the mono trunk upstream, and should be included in the
-      upcoming mono-2.6 release.</p>
-
-      <p>In the meantime, a few more .NET related ports have been updated
-      or added to the FreeBSD ports tree.  These ports include:</p>
-
-      <ul>
-        <li>www/xsp and www/mod_mono that make it possible to use FreeBSD
-        for hosting ASP.NET application;</li>
-
-        <li>lang/boo, a CLI-targeted programming language similar to
-        Python;</li>
-
-        <li>lang/mono-basic, the Visual Basic .NET Framework for
-        Mono;</li>
-
-        <li>devel/monodevelop, an Integrated Development Environment for
-        .NET;</li>
-
-
-        <li>and much more...</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Test mono ports and send feedback (we are especially
-      interested in tests where NOPORTDOCS / WITH_DEBUG is
-      enabled).</li><li>Port the mono-debugger to FreeBSD.</li><li>Build a debug live-image of FreeBSD so that Mono hackers
-      without a FreeBSD box can help us fixing bugs more
-      efficiently.</li></ol><hr /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang" title="http://wiki.freebsd.org/BuildingFreeBSDWithClang"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang" title="">http://wiki.freebsd.org/BuildingFreeBSDWithClang</a></td></tr></table><p>
-	Contact: 
-          Ed
-
-          Schouten
-         &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Roman
-
-          Divacky
-         &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Pawel
-
-          Worach
-         &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	</p>
-      <p>The clang@FreeBSD team presents the status of clang/LLVM being
-      able to compile FreeBSD system.  The current status is:</p>
-
-      <ul>
-        <li>i386 - kernel boots, world needs little hacks but works</li>
-
-        <li>amd64 - kernel boots, world needs little hacks but works</li>
-
-        <li>ppc - broken because of unknown RTLD bug</li>
-
-        <li>other - unknown</li>
-      </ul>
-
-      <p>All other platforms are untested.</p>
-
-      <p>A lot has happened over the spring/summer: amd64 got proper
-      mcmodel=kernel support, compiler-rt has been introduced (paving the way
-      for libgcc replacement), we have run two experimental port builds to see
-      how clang does there.  The C++ support is able to parse devd.cc without
-      warnings.  We have got the kernel working with -O2.  FreeBSD has been promoted
-      to be an officially supported plaform in LLVM.  As a result of all this
-      work, many parts of FreeBSD that did not compile before now build
-      without problems.</p>
-    <h3>Open tasks:</h3><ol><li>The "ClangBSD" branch of FreeBSD got a little stale and has not
-      been updated for a while.</li><li>We also need to get some important fixes
-      into LLVM to get libc compiling and some other smaller issues.</li><li>We can still appreciate more testers on minor platforms (mostly on
-      ARM, PPC and MIPS, but testing on other platforms is also welcome).</li></ol><hr /><h2><a name="FreeBSD-TDM-Framework" href="#FreeBSD-TDM-Framework" id="FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></h2><p>
-	Contact: 
-	  Rafal
-
-	  Czubak
-       &lt;<a href="mailto:rcz@semihalf.com">rcz@semihalf.com</a>&gt;
-	<br />
-	Contact: 
-	  Michal
-
-	  Hajduk
-	 &lt;<a href="mailto:mih@semihalf.com">mih@semihalf.com</a>&gt;
-	</p>
-      <p>This work's purpose is a generic and flexible framework for systems
-	equipped with Time Division Multiplexing (TDM) units, often found on
-	embedded telecom chips.  The framework is designed to support various
-	controllers and many types of TDM channels e.g. voiceband, sound and
-	miscellaneous data channels.  Currently, voiceband infrastructure is
-	being developed on Marvell RD-88F6281 reference board.  It will serve
-	as an example of how to use the TDM framework for other channel types.
-	The direct objective of using TDM with voiceband channels is bringing
-	a FreeBSD based VoIP system, capable of bridging analog telephone world
-	with digital IP telephony.  Together with third party VoIP software
-	(e.g. Asterisk), the design can serve as VoIP Private Branch Exchange
-	(PBX).</p>
-
-      <p>Current state highlights:</p>
-
-      <ul>
-	<li>TDM controller interface</li>
-
-	<li>TDM channel interface</li>
-
-	<li>TDM channel API for kernel modules</li>
-
-	<li>codec interface</li>
-
-	<li>voiceband channel character device driver</li>
-
-	<li>TDM controller driver for Marvell Kirkwood and Discovery SoCs</li>
-
-	<li>Si3215 SLIC driver</li>
-
-	<li>Si3050 DAA driver</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Develop demo application showing example usage of voiceband
-	channel.</li><li>Integrate voiceband infrastructure with Zaptel/DAHDI telephony
-	hardware drivers.</li></ol><hr /><h2><a name="Grand-Central-Dispatch---FreeBSD-port" href="#Grand-Central-Dispatch---FreeBSD-port" id="Grand-Central-Dispatch---FreeBSD-port">Grand Central Dispatch - FreeBSD port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://libdispatch.macosforge.org/" title="http://libdispatch.macosforge.org/">GCD / libdispatch web page</a></td><td>
-	    URL: <a href="http://libdispatch.macosforge.org/" title="GCD / libdispatch web page">http://libdispatch.macosforge.org/</a></td></tr></table><p>
-	Contact: 
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Stacey
-	  Son
-	 &lt;<a href="mailto:sson@FreeBSD.org">sson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  libdispatch mailing list
-	 &lt;<a href="mailto:libdispatch-dev@lists.macosforge.org">libdispatch-dev@lists.macosforge.org</a>&gt;
-	</p>
-      <p>We have ported libdispatch, Apple's Grand Central Dispatch event
-	and concurrency framework to FreeBSD:</p>
-
-      <ul>
-	<li>Added new kqueue primitives required to support GCD, such
-	  as EVFILT_USER and EV_TRIGGER</li>
-	<li>Created autoconf and automake build framework for libdispatch</li>
-	<li>Modified libdispatch to use POSIX semaphores instead of
-	  Mach semaphores</li>
-	<li>Adapted libdispatch to use portable POSIX time routines</li>
-      </ul>
-
-      <p>Jordan Hubbard has also prepared a blocks-aware clang compiler
-	package for FreeBSD.  When compiled with clang, libdispatch
-	provides blocks-based, as well as function-based callbacks.</p>
-
-      <p>The port was presented at the FreeBSD Developer Summit in
-	Cambridge, UK in September, and slides are online on the devsummit
-	wiki page.  A FreeBSD port is now available in the Ports Collection.
-	After FreeBSD 8.0-RELEASE has shipped, the new kqueue primitives will be
-	MFC'd so that libdispatch works out of the box on FreeBSD 8.1-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>
-	Complete porting of libdispatch test suite to FreeBSD.
-      </li><li>
-	Investigate pthread work queue implementation for FreeBSD.
-      </li><li>
-	Evaluate performance impact of some machine-dependent and
-	OS-dependent optimizations present in the Mac OS X version of
-	libdispatch to decide if they should be done for other
-	platforms and OS's.
-      </li><li>
-	Explore whether FreeBSD base operating system tools would benefit
-	from being modified to use libdispatch.
-      </li></ol><hr /><h2><a name="libprocstat(3)---process-statistics" href="#libprocstat(3)---process-statistics" id="libprocstat(3)---process-statistics">libprocstat(3) - process statistics</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.freebsd.org/viewvc/base/projects/libprocstat/" title="http://svn.freebsd.org/viewvc/base/projects/libprocstat/">libprocstat repository</a></td><td>
-	    URL: <a href="http://svn.freebsd.org/viewvc/base/projects/libprocstat/" title="libprocstat repository">http://svn.freebsd.org/viewvc/base/projects/libprocstat/</a></td></tr></table><p>
-	Contact: 
-          Stanislav
-          Sedov
-         &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Ulf
-          Lilleengen
-         &lt;<a href="mailto:lulf@FreeBSD.org">lulf@FreeBSD.org</a>&gt;
-	</p>
-      <p>The libprocstat project is an ongoing effort to develop a library that can
-        be used to retrieve information about running processes and
-	open files in the uniform and platform-independent way both from
-	a running system or from core files.  This will facilitate the
-	implementation of file- or process-monitoring applications like
-	lsof(1), fstat(1), fuser, etc.  The libprocstat repository contains a
-	preliminary version of the library.  It also includes rewrites
-	of the fstat and the fuser
-	utilities ported to use this library instead of retrieving all
-	the required information via the kvm(3) interface; one of the
-	important advantages of the versions that use libprocstat is
-	that these utilities are ABI independent.</p>
-    <h3>Open tasks:</h3><ol><li>
-        Implement KVM-based namecache lookup to retrieve filesystem paths
-	associated with file descriptors and VM objects.
-      </li><li>
-        Analyze possible ways of exporting file and process information
-	from the kernel in an extensible and ABI-independent way.
-      </li></ol><hr /><h2><a name="New-BSD-licensed-debugger" href="#New-BSD-licensed-debugger" id="New-BSD-licensed-debugger">New BSD licensed debugger</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/TheBsdDebugger" title="http://wiki.freebsd.org/TheBsdDebugger">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/TheBsdDebugger" title="Wiki page">http://wiki.freebsd.org/TheBsdDebugger</a></td></tr><tr><td><a href="http://people.freebsd.org/~dfr/ngdb.git" title="http://people.freebsd.org/~dfr/ngdb.git">Repository</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~dfr/ngdb.git" title="Repository">http://people.freebsd.org/~dfr/ngdb.git</a></td></tr><tr><td><a href="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&amp;do=view&amp;target=NGDB-200909.pdf" title="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&amp;do=view&amp;target=NGDB-200909.pdf">Slides</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&amp;do=view&amp;target=NGDB-200909.pdf" title="Slides">http://wiki.freebsd.org/200909DevSummit?action=AttachFile&amp;do=view&amp;target=NGDB-200909.pdf</a></td></tr></table><p>
-	Contact: 
-	  Doug
-	  Rabson
-	 &lt;<a href="mailto:"></a>&gt;
-	</p>
-      <p>I have been working recently on writing a new debugger,
-	primarily for the FreeBSD platform.  For various reasons, I have
-	been writing it in a relatively obscure C-like language called
-	D.</p>
-
-      <p>So far, I have a pretty useful (if a little raw at the edges)
-	command line debugger which supports ELF, Dwarf debugging
-	information and (currently) 32 bit FreeBSD and Linux.  The
-	engine includes parsing and evaluation of arbitrary C expressions
-	along with the usual debugging tools such as breakpoints, source
-	code listing, single-step etc.  All the code is new and BSD
-	licensed.  Currently, the thing supports userland debugging of
-	i386 targets via ptrace and post-mortem core file debugging of
-	the same.  I will be adding amd64 support real soon (TM) and
-	maybe support for GDB's remote debugging protocol later.</p>
-    <hr /><h2><a name="NFSv4-ACLs" href="#NFSv4-ACLs" id="NFSv4-ACLs">NFSv4 ACLs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/NFSv4_ACLs" title="http://wiki.freebsd.org/NFSv4_ACLs"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/NFSv4_ACLs" title="">http://wiki.freebsd.org/NFSv4_ACLs</a></td></tr></table><p>
-	Contact: 
-	  Edward Tomasz
-
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>During Google Summer of Code 2008, I have implemented native support
-	for NFSv4 ACLs for both ZFS and UFS.  Most of the code has already been
-	merged to CURRENT.  NFSv4 ACLs are unconditionally enabled in ZFS and
-	the usual tools, like getfacl(1) and setfacl(1) can be used to view and
-	change them.  I plan to merge the remaining bits (UFS support) this month.
-	It should be possible to MFC it in order to ship in
-	FreeBSD 8.1-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>UFS changes review</li><li>Support for NFSv4 ACLs in tar(1)</li></ol><hr /><h2><a name="The-Newcons-project" href="#The-Newcons-project" id="The-Newcons-project">The Newcons project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Newcons" title="http://wiki.FreeBSD.org/Newcons">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Newcons" title="Wiki page">http://wiki.FreeBSD.org/Newcons</a></td></tr><tr><td><a href="http://people.freebsd.org/~ed/newcons/patches/" title="http://people.freebsd.org/~ed/newcons/patches/">Patchset</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~ed/newcons/patches/" title="Patchset">http://people.freebsd.org/~ed/newcons/patches/</a></td></tr></table><p>
-	Contact: 
-          Ed
-
-          Schouten
-         &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p>Some time ago I started writing a new driver for the FreeBSD
-      kernel called vt(4), which is basically a replacement of syscons.
-      There is still a lot of work that needs to be done but it is
-      probably useful to mention what it does (and what does not).</p>
-
-      <p>Right now there are just two graphics drivers for vt(4), namely
-      a VGA driver for i386 and amd64 and a Microsoft Xbox graphics
-      driver (because it was so easy to implement).  I still have to figure
-      out what I am going to do with VESA, because maybe it is better to
-      just ignore VESA and figure out how hard it is to extend DRM to
-      interact with vt(4).</p>
-
-      <p>Some random features: it already supports both Unicode (UTF-8)
-      input and output, it is MPSAFE and supports per-window graphical
-      fonts of variable dimensions, containing an almost infinite amount
-      of glyphs (both bold and regular).</p>
-    <h3>Open tasks:</h3><ol><li>Research needs to be done on DRM's codebase.</li><li>Syscons should already be migrated to TERM=xterm to make
-      switching between drivers a bit easier.</li></ol><hr /><h2><a name="VirtualBox-on-FreeBSD" href="#VirtualBox-on-FreeBSD" id="VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/VirtualBox" title="http://wiki.freebsd.org/VirtualBox"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/VirtualBox" title="">http://wiki.freebsd.org/VirtualBox</a></td></tr></table><p>
-	Contact: 
-           Beat
-           Gaetzi
-          &lt;<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Bernhard
-          Froehlich
-         &lt;<a href="mailto:decke@bluelife.at">decke@bluelife.at</a>&gt;
-	<br />
-	Contact: 
-          Dennis
-          Herrmann
-         &lt;<a href="mailto:dhn@FreeBSD.org">dhn@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Juergen
-          Lock
-         &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Martin
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	</p>
-      <p>VirtualBox has been committed to the Ports tree and synchronized
-        with the latest trunk version from Sun.  Several known
-        problems are already fixed and some new features have been
-        added:</p>
-
-      <ul>
-        <li>VT-x support</li>
-        <li>Bridging support (Big Thanks to Fredrik Lindberg)</li>
-        <li>Host Serial Support</li>
-        <li>ACPI Support</li>
-        <li>Host DVD/CD access</li>
-        <li>SMP Support</li>
-      </ul>
-
-      <p>We would like to say thanks to all the people who helped us by
-      reporting bugs and submitting fixes.  We also thank the VirtualBox
-      developers for their help with the ongoing effort to port
-      VirtualBox on FreeBSD.</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="">http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html</a></td></tr></table><p>
-	Contact: 
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Volker
-	  Werth
-	 &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
-	</p>
-      <p>We continue to classify PRs as they arrive, adding 'tags' to
-	the subject lines corresponding to the kernel subsystem
-	involved, or man page references for userland PRs.  These tags,
-	in turn, produce lists of PRs sorted both by tag and by
-	manpage.</p>
-
-      <p>The list of PRs recommended for committer evaluation by the
-	Bugbusting Team continues to receive new additions.  This list
-	contains PRs, mostly with patches, that the Bugbusting Team
-	feel are probably ready to be committed as-is, or are probably
-	trivially resolved in the hands of a committer with knowledge
-	of the particular subsystem.  All committers are invited to take
-	a look at this list whenever they have a spare 5 minutes and
-	wish to close a PR.</p>
-
-      <p>A full list of all the automatically generated reports is also
-	available at one of the cited URLs.  Any recommendations for
-	reports which not currently exist but which would be
-	beneficial are welcomed.</p>
-
-      <p>Gavin Atkinson gave a presentation on "The PR Collection
-	Status" at the EuroBSDCon 2009 DevSummit, and discussed with
-	other participants several other ideas to make the PR database
-	more useful and usable.  Several good ideas came from this, and
-	will hopefully lead to more useful tools in the near future.
-	Discussions also took place on how it may be possible to
-	automatically classify non-ports PRs with a view towards
-	notifying interested parties, although investigations into this
-	have not yet begun.</p>
-
-      <p>Mark Linimon also continues attempting to define the general
-	problem and investigating possible new workflow models, and
-	presented work on this at BSDCan 2009.</p>
-
-      <p>Since the last status report, the number of open bugs has
-	increased to around the 5900 mark, partially because of an
-	increased focus on getting more information into the existing
-	PRs, in an attempt to make sure all the information required is
-	now available.  As a result, although the number of open PRs has
-	increased, they are hopefully of better quality.</p>
-
-      <p>As always, more help is appreciated, and committers and
-	non-committers alike are always invited to join us on
-	#freebsd-bugbusters on EFnet and help close stale PRs or commit
-	patches from valid PRs.</p>
-    <h3>Open tasks:</h3><ol><li>
-	Work on suggestions from developers who were at the EuroBSDCon
-	DevSummit.
-      </li><li>
-	Try to find ways to get more committers helping us with closing
-	the PRs that the team has already analyzed.
-      </li></ol><hr /><h2><a name="FreeBSD-KDE-Team" href="#FreeBSD-KDE-Team" id="FreeBSD-KDE-Team">FreeBSD KDE Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freebsd.kde.org" title="http://freebsd.kde.org"></a></td><td>
-	    URL: <a href="http://freebsd.kde.org" title="">http://freebsd.kde.org</a></td></tr><tr><td><a href="http://miwi.bsdcrew.de/category/kde/" title="http://miwi.bsdcrew.de/category/kde/"></a></td><td>
-	    URL: <a href="http://miwi.bsdcrew.de/category/kde/" title="">http://miwi.bsdcrew.de/category/kde/</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/tabthorpe/category/kde" title="http://blogs.freebsdish.org/tabthorpe/category/kde"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/tabthorpe/category/kde" title="">http://blogs.freebsdish.org/tabthorpe/category/kde</a></td></tr></table><p>
-	Contact: 
-          Thomas
-
-          Abthorpe
-         &lt;<a href="mailto:tabthorpe@FreeBSD.org">tabthorpe@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Max
-
-          Brazhnikov
-         &lt;<a href="mailto:makc@FreeBSD.org">makc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Martin
-
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the spring, the FreeBSD KDE team has been busy upgrading
-      KDE from 4.2.0 up through to 4.3.1.  As part of the ongoing
-      maintenance of KDE, the team also updated Qt4 from 4.4.3 through to
-      4.5.2</p>
-
-      <p>We added two new committers/maintainers to the team, Kris Moore
-      (kmoore@) and Dima Panov (fluffy@).  We also granted enhanced area51
-      access to contributors Alberto Villa and Raphael Kubo da Costa.
-      Alberto has been our key contributor updating and testing Qt
-      4.6.0-tp1.  Raphael is a KDE developer, who has become our Gitorious
-      liaison, he has been responsible for getting FreeBSD Qt patches
-      merged in upstream.</p>
-
-      <p>Markus Br�ffer (markus@) spent a lot of time patching widgets
-      and system plugins so they would work under FreeBSD.  We would like
-      to thank him for all his effort!</p>
-    <h3>Open tasks:</h3><ol><li>Update to Qt 4.6.0</li><li>Update to KDE 4.4.0</li><li>Work with our userbase on fixing an EOL for KDE3 in the ports
-      tree</li></ol><hr /><h2><a name="FreeBSD-Ports-Management-Team" href="#FreeBSD-Ports-Management-Team" id="FreeBSD-Ports-Management-Team">FreeBSD Ports Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/ports/" title="http://www.freebsd.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/ports/" title="The FreeBSD Ports Collection">http://www.freebsd.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">The FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="The FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact: 
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports count has soared to over 20,700.  The PR count had
-	been driven below 800 by some extraordinary effort, but once
-	again is back to its usual count of around 900.</p>
-
-      <p>We are currently building packages for amd64-6, amd64-7,
-	amd64-8, i386-6, i386-7, i386-8, sparc64-7, and sparc64-8.
-	There have been preliminary runs of i386-9; however, to be able
-	to continue builds on -9, we will either need to find places to
-	host a number of new machines, or drop package building for -6.
-	The mailing list discussion of the latter proved quite
-	controversial.</p>
-
-      <p>We have added some new i386 machines to help speed up the
-	builds, but this only makes up for the disk failures on some
-	of our older, slower, i386 nodes.</p>
-
-      <p>We also appreciate the loan of more package build machines from
-	several committers, including pgollucci@, gahr@, erwin@, Boris
-	Kochergin, and Craig Butler.</p>
-
-      <p>The portmgr@ team has also welcomed new members Ion-Mihai Tetcu
-	(itetcu@) and Martin Wilke (miwi@).  We also thank departing
-	member Kirill Ponomarew (krion@) for his long service.</p>
-
-      <p>Ion-Mihai has spent much time working on a system that does
-	automatic Quality Assurance on new commits, called QAT.  A
-	second tinderbox called QATty has helped us to fix many problems,
-	especially those involving custom PREFIX and LOCALBASE settings,
-	and documentation inclusion options.  Ports conformance to
-	documented features / non-default configuration will follow.</p>
-
-      <p>Between pav and miwi, over 2 dozen experimental ports runs have
-	been completed and committed.</p>
-
-      <p>We have added 5 new committers since the last report, and 2
-	older ones have rejoined.</p>
-    <h3>Open tasks:</h3><ol><li>We are currently trying to set up ports tinderboxes that
-	can be made available to committers for pre-testing; those
-	who can loan machines for this should contact Ion-Mihai
-	(itetcu@) with details regarding the hardware and
-	bandwidth.</li><li>Most of the remaining ports PRs are "existing port/PR
-	assigned to committer".  Although the maintainer-timeout policy
-	is helping to keep the backlog down, we are going to need to do
-	more to get the ports in the shape they really need to be
-	in.</li><li>Although we have added many maintainers, we still have
-	almost 4,700 unmaintained ports (see, for instance, the list on
-	portsmon).  (The percentage is down to 22%.)  We are always
-	looking for dedicated volunteers to adopt at least a few
-	unmaintained ports.  As well, the packages on amd64 and sparc64
-	lag behind i386, and we need more testers for those.</li></ol><hr /><h2><a name="Release-Engineering-Status-Report" href="#Release-Engineering-Status-Report" id="Release-Engineering-Status-Report">Release Engineering Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact: 
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team continues to work on FreeBSD
-	8.0-RELEASE.  Public testing has turned up quite a few problems,
-	many related to the low-level network (routing/ARP table) changes
-	and their interactions with IPv6.</p>
-
-      <p>Progress continues to be made on fixing up the issues that have
-	been identified during the public testing.  At this point in time
-	we are shooting for two more public test builds (RC2 and RC3)
-	followed by the release late October or early November.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org" title="http://www.freebsdfoundation.org"></a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org" title="">http://www.freebsdfoundation.org</a></td></tr></table><p>
-	Contact: 
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>Kicking off our fall fund-raising campaign! Find out more at
-	<a href="http://www.freebsdfoundation.org/donate/" shape="rect">http://www.freebsdfoundation.org/donate/</a>.</p>
-
-      <p>We were a sponsor for EuroBSDCon 2009, and provided travel
-	grants to 8 FreeBSD developers and users.  We sponsored Kyiv BSD
-	2009, in Kiev Ukraine.  We were also a sponsor of BSDCan, and
-	sponsored 7 developers.  We funded three new projects, New Console
-	Driver by Ed Schouten, AVR32 Support by Arnar Mar Sig, and
-	Wireless Mesh Support by Rui Paulo, which has completed.
-	We continued funding a project that is making improvements to the
-	FreeBSD TCP Stack by Lawrence Stewart.  The project that made
-	removing disk devices with mounted filesystems on them safe, by
-	Edward Napierala, is now complete.</p>
-
-      <p>We recognized the following FreeBSD developers at EuroBSDCon
-	2009: Poul-Henning Kamp, Bjoern Zeeb, and Simon Nielsen.  These
-	developers received limited edition FreeBSD Foundation vests.</p>
-
-      <p>Follow us on <a href="https://twitter.com/freebsdfndation" shape="rect">Twitter</a> now!</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Enhancing-the-FreeBSD-TCP-Implementation" href="#Enhancing-the-FreeBSD-TCP-Implementation" id="Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/etcp09/" title="http://caia.swin.edu.au/freebsd/etcp09/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/etcp09/" title="">http://caia.swin.edu.au/freebsd/etcp09/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.freebsdfoundation.org/projects.shtml" title="http://www.freebsdfoundation.org/projects.shtml"></a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org/projects.shtml" title="">http://www.freebsdfoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/" title="http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/" title="">http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/</a></td></tr></table><p>
-	Contact: 
-          Lawrence
-          Stewart
-         &lt;<a href="mailto:lstewart@freebsd.org">lstewart@freebsd.org</a>&gt;
-	</p>
-      <p>TCP appropriate byte counting (RFC 3465) support has been merged
-        into the FreeBSD 8 branch and will ship in FreeBSD 8.0-RELEASE.</p>
-
-      <p>The reassembly queue auto-tuning and SIFTR work was not ready in
-        time to safely integrate for 8.0-RELEASE.  Padding has been added
-        to necessary TCP structs to facilitate MFCing features back to the
-	8-STABLE branch after 8.0 is released.</p>
-
-      <p>Candidate patches against FreeBSD-CURRENT will be ready for wider
-        testing in the coming weeks.  The <a href="mailto:freebsd-net@FreeBSD.org" shape="rect">freebsd-net</a> mailing list
-	will be solicited for testing/feedback when everything is ready.</p>
-    <h3>Open tasks:</h3><ol><li>
-	Solicit review/testing and integrate the ALQ kld and variable
-	length message support patch into FreeBSD-CURRENT.
-      </li><li>
-	Solicit review/testing and integrate the SIFTR tool into
-	FreeBSD-CURRENT.
-      </li><li>
-	Complete dynamic reassembly queue auto-tuning patch for FreeBSD-CURRENT.
-      </li><li>
-	Fix an identified bug in the SACK implementation's fast retransmit/fast
-	recovery behavior.
-      </li><li>
-	Profit!
-      </li></ol><hr /><h2><a name="Modular-Congestion-Control" href="#Modular-Congestion-Control" id="Modular-Congestion-Control">Modular Congestion Control</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/" title="http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/"></a></td><td>
-	    URL: <a href="http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/" title="">http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/</a></td></tr></table><p>
-	Contact: 
-          Lawrence
-          Stewart
-         &lt;<a href="mailto:lstewart@freebsd.org">lstewart@freebsd.org</a>&gt;
-	</p>
-      <p>The patch has received some significant rototilling in the past
-        few months to prepare it for merging to FreeBSD-CURRENT.
-	Additionally, I completed an implementation of the CUBIC congestion
-	control algorithm to complement the existing NewReno and H-TCP
-	algorithm implementations already available.</p>
-
-      <p>I have one further intrusive change to make, which will allow
-        congestion control modules to be shared between the TCP and SCTP
-	stacks.  Once this is complete, I will be soliciting for
-	review/testing in the hope of committing the patch to
-	FreeBSD-CURRENT in time to be able to backport it for 8.1-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>
-        Abstract the congestion control specific variables out of the TCP and
-	SCTP control blocks into a new struct that can be passed into the API
-	instead of the control block itself.
-      </li></ol><hr /><h2><a name="Network-Stack-Virtualization" href="#Network-Stack-Virtualization" id="Network-Stack-Virtualization">Network Stack Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Image" title="http://wiki.freebsd.org/Image">Wiki VImage overview page (incl. TODO).</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Image" title="Wiki VImage overview page (incl. TODO).">http://wiki.freebsd.org/Image</a></td></tr><tr><td><a href="http://wiki.freebsd.org/200909DevSummit" title="http://wiki.freebsd.org/200909DevSummit">FreeBSD Developer Summit, 2009, Cambridge, UK.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/200909DevSummit" title="FreeBSD Developer Summit, 2009, Cambridge, UK.">http://wiki.freebsd.org/200909DevSummit</a></td></tr></table><p>
-	Contact: 
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.ORG">bz@FreeBSD.ORG</a>&gt;
-	<br />
-	Contact: 
-	  Marko
-	  Zec
-	 &lt;<a href="mailto:zec@FreeBSD.ORG">zec@FreeBSD.ORG</a>&gt;
-	<br />
-	Contact: 
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.ORG">rwatson@FreeBSD.ORG</a>&gt;
-	</p>
-      <p>The network stack virtualization project aims at extending the
-	FreeBSD kernel to maintain multiple independent instances of
-	networking state.  This allows for networking independence
-	between jail environment, each maintaining its private network
-	interfaces, IPv4 and IPv6 network and port address space, routing
-	tables, IPSec configuration, firewalls, and more.</p>
-
-      <p>During the last months the remaining pieces of the VIMAGE work
-	were merged by Marko, Julian and Bjoern.  Robert Watson developed
-	a vnet allocator to overcome ABI issues.  Jamie Gritton merged
-	his hierarchical jail framework that now also is the management
-	interface for virtual network stacks.</p>
-
-      <p>During the FreeBSD Developer Summit that took place at
-	EuroBSDCon 2009 in Cambridge, UK, people virtualized more code.
-	As a result SCTP and another accept filter were virtualized and
-	more people became familiar with the design of VImage and the underlying concepts.
-	Finally getting more hands involved was a crucial first step for
-	the long term success of kernel virtualization.</p>
-
-      <p>The next steps will be to finish the network stack
-	virtualization, generalize the allocator framework before
-	thinking of virtualizing further subsystems and to update the related
-	documentation.  Along with that a proper jail management
-	framework will be worked on.  Long term goals, amongst others,
-	will be to virtualize more subsystems like SYS-V IPC, better
-	privilege handling, and resource limits.</p>
-
-      <p>In the upcoming FreeBSD 8.0 Release, vnets are treated as an
-	experimental feature.  As a result, they are not yet recommended for use in
-	production environments.  There was lots of time spent to
-	finalize the infrastructure for vnets though, so that further
-	changes can be merged and we are aiming to have things
-	production ready for 8.2.</p>
-
-      <p>In case you want to help to achieve this goal, feel free to
-	contact us and support or help virtualizing outstanding parts
-	like two firewalls, appletalk, netipx, ... as well as generating
-	regression tests.</p>
-    <hr /><h2><a name="Stream-Control-Transmission-Protocol-(SCTP)" href="#Stream-Control-Transmission-Protocol-(SCTP)" id="Stream-Control-Transmission-Protocol-(SCTP)">Stream Control Transmission Protocol (SCTP)</a></h2><p>
-	Contact: 
-	  Randall
-	  Stewart
-	 &lt;<a href="mailto:rrs@FreeBSD">rrs@FreeBSD</a>&gt;
-	</p>
-      <p>SCTP continues to have minor fixes added to it as well as some
-	new features.  First and foremost, we now have VIMAGE and SCTP
-  	working and playing together.  This goal was accomplished with
-	the help of bz@, my new mentee tuexen@ and myself working
-	together at the FreeBSD DevSummit in Cambridge, UK.  Also the
-	non-renegable SACK feature contributed by the university of
-	Delaware was fixed so that now its safe to turn on (its
-	sysctl).  If you are using SCTP with CMT (Conncurrent
-	Multipath Transfer) you will want to enable this option
-	(CMT is also a sysctl).  With CMT enabled you will be able to
-	send data to all the destinations of an SCTP peer.</p>
-
-      <p>We welcomed a new mentee (soon to be a commiter) to FreeBSD.
-	Michael Tuexen is now a mentee of rrs@.  Michael has been
-	contributing to the SCTP work for quite some time and also
-	moonlights as a Professor at the University of Muenster
-	in Germany (when not doing SCTP coding).</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="FreeBSD/ZFS" href="#FreeBSD/ZFS" id="FreeBSD/ZFS">FreeBSD/ZFS</a></h2><p>
-	Contact: 
-	  Pawel
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>We believe that the ZFS file system is now production-ready in
-	FreeBSD 8.0.  Most (if not all) reported bugs were fixed and ZFS
-	is no longer tagged as experimental.  There is also ongoing work
-	in Perforce to bring the latest ZFS version (v19) to FreeBSD.</p>
-    <h3>Open tasks:</h3><ol><li>
-	Download 8.0 release candidates and test, test, test and report
-	any problems to the
-	<a href="mailto:freebsd-fs@FreeBSD.org" shape="rect">freebsd-fs@FreeBSD.org</a>
-	mailing list.
-      </li></ol><hr /><h2><a name="hwpmc-for-MIPS" href="#hwpmc-for-MIPS" id="hwpmc-for-MIPS">hwpmc for MIPS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/FreeBSD/mips" title="http://wiki.freebsd.org/FreeBSD/mips">Main FreeBSD MIPS Page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/FreeBSD/mips" title="Main FreeBSD MIPS Page">http://wiki.freebsd.org/FreeBSD/mips</a></td></tr><tr><td><a href="http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro" title="http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro">Sub page for the board I am using.</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro" title="Sub page for the board I am using.">http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro</a></td></tr></table><p>
-	Contact: 
-          George
-          Neville-Neil
-         &lt;<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>&gt;
-	</p>
-      <p>Currently working on board bringup.  I have looked over the docs
-        for how MIPS provides performance counters and will begin adding
-	code soon.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/docproj/translations.html#dutch" title="http://www.freebsd.org/docproj/translations.html#dutch">Current status of the Dutch translation</a></td><td>
-	    URL: <a href="http://www.freebsd.org/docproj/translations.html#dutch" title="Current status of the Dutch translation">http://www.freebsd.org/docproj/translations.html#dutch</a></td></tr></table><p>
-	Contact: 
-          Ren�
-
-          Ladan
-         &lt;<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Remko
-
-          Lodder
-         &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	</p>
-      <p>The current translations (Handbook and some articles) are kept
-      up to date with the English versions.  Some parts of the website
-      have been
-      <url href="http://www.freebsd.org/nl">translated</url>, more work
-      is in progress.</p>
-    <h3>Open tasks:</h3><ol><li>Find more volunteers for translating the remaining parts of
-      the website and the FAQ.</li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://doc.bsdgroup.de" title="https://doc.bsdgroup.de"></a></td><td>
-	    URL: <a href="https://doc.bsdgroup.de" title="">https://doc.bsdgroup.de</a></td></tr><tr><td><a href="http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede" title="http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede"></a></td><td>
-	    URL: <a href="http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede" title="">http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede</a></td></tr></table><p>
-	Contact: 
-          Johann
-
-          Kois
-         &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Benedict
-
-          Reuschling
-         &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Martin
-
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	</p>
-      <p>In May 2009, Benedict Reuschling received his commit bit to the
-      www/de and doc/de_DE.ISO8859-1 trees under the mentorship of Johann
-      Kois.  Since then, he has been working primarily on the Handbook, updating
-      existing chapters and translating new ones.  Most notably, the
-      filesystems and DTrace chapters have been recently translated.  Bugs found
-      in the original documents along the way were reported back so that
-      the other translation teams could incorporate them, as well.</p>
-
-      <p>Christoph Sold has put his time in translating the wiki pages of
-      the BSD Certification Group into the German language.  This is very
-      helpful for all German people who want to take the exam and like to read
-      the information about it in their native language.  Daniel Seuffert
-      has sent valuable corrections and bugfixes.  Thanks to both of them for
-      their time and efforts!</p>
-
-      <p>The website is translated and updated constantly.  Missing parts
-      will be translated as time permits.</p>
-
-      <p>We appreciate any help from volunteers in proofreading
-      documents, translating new ones and keeping them up to date.  Even
-      small error reports are of great help for us.  You can find
-      contact information at the above URL.</p>
-    <h3>Open tasks:</h3><ol><li>Update the existing documentation set (especially the
-      Handbook).</li><li>Translate more articles to German.</li><li>Read the translations.  Check for problems and mistakes.  Send
-      feedback.</li></ol><hr /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu" title="http://www.FreeBSD.org/hu">Hungarian Web Page for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu" title="Hungarian Web Page for FreeBSD">http://www.FreeBSD.org/hu</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu" title="http://www.FreeBSD.org/doc/hu">Hungarian Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  G�bor
-
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the last months, we have not added new translations, although we
-	have been working on the existing ones to have them updated.  We need
-	more translators and volunteers to keep the amount of the translated
-	documentation growing, so feel free to contribute.  Every line of
-	submission or feedback is appreciated and highly welcome.</p>
-
-      <p>If you want to join our work, please read the <a href="http://www.freebsd.org/hu/docproj/hungarian.html" shape="rect">introduction</a>
-	to the project as well as the <a href="http://www.freebsd.org/doc/hu/books/fdp-primer/" shape="rect">FDP Primer</a>
-	(both of them are available in Hungarian).</p>
-    <h3>Open tasks:</h3><ol><li>Translate news entries, press releases</li><li>Translate Release Notes for -CURRENT and 8.X</li><li>Translate articles</li><li>Translate web pages</li><li>Read the translations, send feedback</li></ol><hr /><h2><a name="The-FreeBSD-Spanish-Documentation-Project" href="#The-FreeBSD-Spanish-Documentation-Project" id="The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/es" title="http://www.FreeBSD.org/es">Spanish Web Page for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/es" title="Spanish Web Page for FreeBSD">http://www.FreeBSD.org/es</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/es" title="http://www.FreeBSD.org/doc/es">Spanish Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/es" title="Spanish Documentation for FreeBSD">http://www.FreeBSD.org/doc/es</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/es/articles/fdp-es/" title="http://www.freebsd.org/doc/es/articles/fdp-es/">Introduction to the FreeBSD Spanish Documentation Project</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/es/articles/fdp-es/" title="Introduction to the FreeBSD Spanish Documentation Project">http://www.freebsd.org/doc/es/articles/fdp-es/</a></td></tr></table><p>
-	Contact: 
-	  Jos� Vicente
-
-	  Carrasco Vay�
-	 &lt;<a href="mailto:carvay@FreeBSD.org">carvay@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  G�bor
-
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Recently, we have added one new article translation.  The
-	existing translations have not been updated, though.  We need
-	more human resources to keep up with the work and keep the
-	translations up-to-date.</p>
-    <h3>Open tasks:</h3><ol><li>Update the Handbook translation</li><li>Update the web page translation</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact: 
-	  Marius
-
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>Noteworthy developments regarding FreeBSD/sparc64 since the last
-	Status Reports are:</p>
-
-       <ul>
-	<li>Cas(4), a driver for Sun Cassini/Cassini+, as well as
-	  National Semiconductor DP83065 Saturn Gigabit NICs has been
-	  committed and thus will be part of FreeBSD beginning with
-	  8.0-RELEASE and 7.3-RELEASE, respectively.  This means that
-	  the on-board NICs found in Fire V440, as well as the add-on
-	  cards based on these chips, are now supported, including on
-	  non-sparc64 machines.  Unfortunately, the cas(4) driver triggers what
-	  seem to be secondary problems with the on-board NICs found in
-	  B100 blades and Fire V480, which due to lack of access to such
-	  systems could not be fixed so far.</li>
-
-	<li>Initial support for sun4u machines based on the "Fire"
-	  Host-PCI-Express bridge like Fire V215, V245, etc. has been
-	  completed (including support for the on-board ATA controller,
-	  which caused several problems at first, and MSI/MSI-X).  Some
-	  code like the quirk handling for the ALi/ULi chips found in
-	  these machines needs to be revisited though and no stability
-	  tests have been conducted so far.  If all goes well, the code
-	  will hit HEAD some time after FreeBSD 8.0-RELEASE has been
-	  released.  In theory, machines based on the "Oberon"
-	  Host-PCI-Express bridge, at least for the most part, should
-	  also be supported with these changes, but due to lack of access
-	  to a Mx000 series machine the code could not be tested with
-	  these so far.</li>
-
-	<li>Some bugs in the snd_t4dwave(4) driver have been fixed, as
-	  well as some special handling for sparc64 has been added so
-	  it does 32-bit DMA and now generally works with the on-board
-	  ALi M5451 found for example in Blade 100 and Blade 1500.
-	  Unfortunately, it was only tested to work correctly in two out
-	  of three Blade 100.  Why it still does not work correctly in
-	  the remaining one is currently unknown but at least no longer
-	  causes IOMMU-panics so testing snd_t4dwave(4) on sparc64 is no
-	  longer harmful.  These changes will be part of
-	  FreeBSD 8.0-RELEASE and 7.3-RELEASE.</li>
-
-	<li>Ata-marvell(4) has been fixed to work on sparc64 (actually
-	  also on anything that is not x86 with less than 4GB of RAM).
-	  These fixes will be part of FreeBSD 8.0-RELEASE and
-	  7.3-RELEASE.</li>
-
-	<li>A proper and machine-independent fix for the old problem
-	  that the loader leaves the NIC opened by the firmware,
-	  which could lead to panics during boot when netbooting,
-	  has been developed but not committed yet.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Gecko-Project" href="#FreeBSD-Gecko-Project" id="FreeBSD-Gecko-Project">FreeBSD Gecko Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO" title="https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO">Gecko TODO</a></td><td>
-	    URL: <a href="https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO" title="Gecko TODO">https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO</a></td></tr></table><p>
-	Contact: 
-          Beat
-          Gaetzi
-         &lt;<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Martin
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Andreas
-          Tobler
-         &lt;<a href="mailto:andreast-list@fgznet.ch">andreast-list@fgznet.ch</a>&gt;
-	</p>
-      <p>Andreas Tobler made the classic mistake of sending us a lot of
-	powerpc and sparc64 related patches.  The usual punishment, of
-	giving him a commit bit to the Gecko repository, has been
-	applied.</p>
-
-      <p>We currently have some old ports in the ports tree:</p>
-
-      <ul>
-        <li>www/mozilla is 5 year old now, no longer supported upstream,
-          and has a lot of security vulnerabilities.  We can use
-	  www/seamonkey instead.</li>
-
-        <li>www/xulrunner is superseeded by www/libxul.</li>
-      </ul>
-
-      <p>A patch that includes the following changes has been tested on
-        pointyhat and is ready for commit:</p>
-
-      <ul>
-        <li>Remove references to www/mozilla/Makefile.common and
-	  www/mozilla/bsd.gecko.mk</li>
-        <li>Switch USE_GECKO= xulrunner firefox mozilla to
-	  USE_GECKO= libxul and remove www/xulrunner</li>
-      </ul>
-
-      <p>We are also working on Firefox 3.6 (Alpha 2), Thunderbird 3.0 (Beta 4),
-        new libxul 1.9.1.3 and Seamonkey 2.0 (Beta 2) ports.  All of them are
-	already committed to our Gecko repository.</p>
-
-      <p>A current status and todo list can be found at
-	<a href="http://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO" shape="rect">http://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Remove mozilla, xulrunner and firefox2 from the ports tree.</li><li>The www/firefox35 port should be moved to www/firefox.</li><li>The old (and somewhat stale) Gecko providers mozilla, nvu,
-        xulrunner, flock and firefox also need to be removed.</li></ol><hr /><h2><a name="Portmaster---utility-to-assist-users-with-managing-ports" href="#Portmaster---utility-to-assist-users-with-managing-ports" id="Portmaster---utility-to-assist-users-with-managing-ports">Portmaster - utility to assist users with managing ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster.html" title="http://dougbarton.us/portmaster.html"></a></td><td>
-	    URL: <a href="http://dougbarton.us/portmaster.html" title="">http://dougbarton.us/portmaster.html</a></td></tr></table><p>
-	Contact: 
-	  Doug
-	  Barton
-	 &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	</p>
-      <p>I am currently seeking funding for further development work on
-	portmaster.  There are several features that are regularly
-	requested by the community (such as support for installing
-	packages) that I would very much like to implement but that
-	will take more time than I can reasonably volunteer to implement
-	correctly.  There is information about the funding proposal
-	available at the link above.</p>
-
-      <p>Meanwhile I have recently completed another round of bug fixes
-	and feature enhancements.  The often-requested ability to specify
-	the -x (exclude) option more than once on the command line was
-	added in version 2.12.  Also in that version I added the
-	--list-origins option to make it easier to reinstall ports after
-	a major version upgrade, or install the same set of ports on
-	another system.</p>
-    <h3>Open tasks:</h3><ol><li>See the funding proposal.</li></ol><hr /><h2><a name="Valgrind-suite-on-FreeBSD" href="#Valgrind-suite-on-FreeBSD" id="Valgrind-suite-on-FreeBSD">Valgrind suite on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Valgrind" title="http://wiki.freebsd.org/Valgrind">Valgrind Wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Valgrind" title="Valgrind Wiki page">http://wiki.freebsd.org/Valgrind</a></td></tr></table><p>
-	Contact: 
-          Stanislav
-          Sedov
-         &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Valgrind suite in the FreeBSD ports collection has been updated to
-        version 3.5.0 (the latest available version).  Most of the issues of
-	the previous version should be resolved now: we expect memcheck,
-	callgrind and cachegrind to be fully functional on both i386 and
-	amd64 platforms as well as for i386 binaries running on amd64
-	system.  DRD/hellgrind should work too, though they generate
-	a lot of false-positives for now, so their output is a bit messy.</p>
-    <h3>Open tasks:</h3><ol><li>
-        Port exp-ptrcheck valgrind tool and fix outstanding issues
-        that show up in memcheck/helgrind/DRD in the Valgrind regression
-	tests suite.
-      </li><li>
-        More testing (please, help).
-      </li><li>
-        Integrate our patches upstream.
-      </li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="EuroBSDcon-2009" href="#EuroBSDcon-2009" id="EuroBSDcon-2009">EuroBSDcon 2009</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2009.eurobsdcon.org/" title="http://2009.eurobsdcon.org/">2009</a></td><td>
-	    URL: <a href="http://2009.eurobsdcon.org/" title="2009">http://2009.eurobsdcon.org/</a></td></tr><tr><td><a href="http://2010.eurobsdcon.org/" title="http://2010.eurobsdcon.org/">2010</a></td><td>
-	    URL: <a href="http://2010.eurobsdcon.org/" title="2010">http://2010.eurobsdcon.org/</a></td></tr></table><p>
-	Contact: 
-          Sam
-
-          Smith
-         &lt;<a href="mailto:eurobsdcon@ukuug.org">eurobsdcon@ukuug.org</a>&gt;
-	<br />
-	Contact: 
-          Robert
-
-          Watson
-         &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>EuroBSDcon 2009 happened in Cambridge, with over 160 users,
-      developers, friends and others.  Slides, papers and audio are now up
-      on the website for those who could not make it to Cambridge.  Next
-      year's event in 2010 will take place in Karlsruhe from 8 to 10 October
-      2010.  If you are interested in what you missed in 2009, or to join
-      the mailing list so you do not miss out next year, visit
-      <a href="http://2009.eurobsdcon.org/" shape="rect">http://2009.eurobsdcon.org</a>.
-
-      </p>
-    <hr /><h2><a name="FreeBSD-Developer-Summit,-Cambridge-UK" href="#FreeBSD-Developer-Summit,-Cambridge-UK" id="FreeBSD-Developer-Summit,-Cambridge-UK">FreeBSD Developer Summit, Cambridge UK</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/200909DevSummit" title="http://wiki.FreeBSD.org/200909DevSummit"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/200909DevSummit" title="">http://wiki.FreeBSD.org/200909DevSummit</a></td></tr></table><p>
-	Contact: 
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Around 70 FreeBSD developers and guests attended the FreeBSD
-	developer summit prior to EuroBSDCon 2009 in Cambridge, UK.
-	Hosted at the University of Cambridge Computer Laboratory, the
-	workshop-style event consisted of prepared presentations, as well
-	as group hacking and discussion sessions.  Talks covered topics
-	including 802.11 mesh networking, virtual network stacks and
-	kernels, a new BSD-licensed debugger, benchmarking, bugbusting,
-	NetFPGA, a port of Apple's GCD (Grand Central Dispatch) to
-	FreeBSD, security policy work, cryptographic signatures,
-	FreeBSD.org system administration, time geeks, a new console
-	driver, and the FreeBSD subversion migration.  Slides for many
-	talks are now available on the wiki page.  A good time was had by
-	all, including a punting outing on the River Cam!</p>
-    <hr /><h2><a name="New-approach-to-the-locale-database" href="#New-approach-to-the-locale-database" id="New-approach-to-the-locale-database">New approach to the locale database</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/LocaleNewApproach" title="http://wiki.freebsd.org/LocaleNewApproach">Documentation on FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/LocaleNewApproach" title="Documentation on FreeBSD wiki">http://wiki.freebsd.org/LocaleNewApproach</a></td></tr><tr><td><a href="svn://svn.freebsd.org/base/user/edwin/locale" title="svn://svn.freebsd.org/base/user/edwin/locale">Code</a></td><td>
-	    URL: <a href="svn://svn.freebsd.org/base/user/edwin/locale" title="Code">svn://svn.freebsd.org/base/user/edwin/locale</a></td></tr></table><p>
-	Contact: 
-          Edwin
-
-          Groothuis
-         &lt;<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          i18n
-
-          mailinglist
-         &lt;<a href="mailto:freebsd-i18n@FreeBSD.org">freebsd-i18n@FreeBSD.org</a>&gt;
-	</p>
-      <p>Problem: Over the years the FreeBSD locale database
-      (share/colldef, share/monetdef, share/msgdef, share/numericdef,
-      share/timedef) has accumulated a total of 165 definitions (language
-      - country-code - character-set triplets).  The contents of the files
-      for Western European languages are often low-ASCII but for Eastern
-      European and Asian languages partly or fully high-ASCII.  Without
-      knowing how to display or interpret the character-sets, it is
-      difficult to make sure by the general audience that the local
-      language (language - country-code) definitions are displayed
-      properly in various character-sets.</p>
-
-      <p>Suggested approach: With the
-      combination of the data in the Unicode project (whose goal is to
-      define all the possible written characters and symbols on this
-      planet) and the Common Locale Data Repository (whose goal is to
-      document all the different data and definitions needed for the
-      locale database), we can easily keep track of the data, without the
-      need of being able to display the data in the required
-      character sets or understand them fully when updates are submitted
-      by third parties.</p>
-
-      <p>Current status: Conversion of share/monetdef,
-      share/msgdef, share/numericdef, share/timedef to the new design is
-      completed.  The Makefile infrastructure is converted.  Regression
-      checks are done.  Most of the tools are in place, waiting on the
-      import of bsdiconv to the base system.</p>
-    <h3>Open tasks:</h3><ol><li>At this moment the system is not self-hosted yet, because of
-      the lack of an iconv-kind of program in the base operating system.
-      Gabor@ is working on bsdiconv as a GSoC project and once that has been
-      imported we will be able to perform a clean install from the definitions in
-      Unicode text format to the required formats and
-      character sets.</li></ol><hr /><h2><a name="The-FreeBSD-Forums" href="#The-FreeBSD-Forums" id="The-FreeBSD-Forums">The FreeBSD Forums</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.freebsd.org/" title="http://forums.freebsd.org/"></a></td><td>
-	    URL: <a href="http://forums.freebsd.org/" title="">http://forums.freebsd.org/</a></td></tr></table><p>
-	Contact: 
-          FreeBSD Forums
-
-          Admins
-         &lt;<a href="mailto:forum-admins@FreeBSD.org">forum-admins@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          FreeBSD Forums
-
-          Moderators
-         &lt;<a href="mailto:forum-moderators@FreeBSD.org">forum-moderators@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since their public launch in November 2008, the FreeBSD Forums
-      (the most recent addition to the user community and support
-      channels for the FreeBSD Operating System) have witnessed a
-      healthy and steady growth.</p>
-
-      <p>The user population is now at over 8,000 registered users, who
-      have participated in over 6,000 topics, containing over 40,000
-      posts in total.  The sign-up rate hovers between 50-100 each week.
-      The total number of visitors (including 'guests') is hard to gauge
-      but is likely to be a substantial multiple of the registered
-      userbase.</p>
-
-      <p>New topics and posts are actively 'pushed out' to search
-      engines.  This in turn makes the Forums show up in search results
-      more and more often, making it a valuable and very accessible
-      source of information for the FreeBSD community.</p>
-
-      <p>One of the contributing factors to the Forums' success is their
-      'BSD-style' approach when it comes to administration and
-      moderation.  The Forums have a strong and unified identity, they are
-      neatly divided into sub-forums (like 'Networking', 'Installing
-      &amp; Upgrading', etc.), very actively moderated, spam-free, and
-      with a core group of very active and helpful members, dispensing
-      many combined decades' worth of knowledge to starting, intermediate
-      and professional users of FreeBSD.</p>
-
-      <p>We expect the Forums to be, and to remain, a central hub in
-      FreeBSD's community and support efforts.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2009-10-2009-12.html b/website/content/en/status/report-2009-10-2009-12.html
deleted file mode 100644
index bf0b8e3905..0000000000
--- a/website/content/en/status/report-2009-10-2009-12.html
+++ /dev/null
@@ -1,1458 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" src="../../layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between October and
-    December 2009. This is the last of the four reports covering 2009,
-    which has shown to be a very important year for the FreeBSD Project. Besides
-    other notable things, a new major version of FreeBSD, 8.0-RELEASE, has been
-    released, while the release process for 7.3-RELEASE is soon to begin.</p><p>Thanks to all the reporters for the excellent work! We hope you
-    enjoy reading. Let us also take this opportunity to wish you all a
-    happy and successful new year for 2010.</p><p>Please note that the deadline for submissions covering the
-    period between January and March 2010 is April 15th, 2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#BSD-licensed-iconv">BSD-licensed iconv</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#3G-USB-support">3G USB support</a></li><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></li><li><a href="#HAST-&#8212;-Highly-Available-Storage">HAST &#8212; Highly Available Storage</a></li><li><a href="#Intel-XScale-hwpmc(9)-support">Intel XScale hwpmc(9) support</a></li><li><a href="#POSIX-utmpx-for-FreeBSD">POSIX utmpx for FreeBSD</a></li><li><a href="#SUJ-&#8212;-Journaled-SoftUpdates">SUJ &#8212; Journaled SoftUpdates</a></li><li><a href="#The-webcamd-deamon">The webcamd deamon</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#bwn(4)-&#8212;-Broadcom-Wireless-driver">bwn(4) &#8212; Broadcom Wireless driver</a></li><li><a href="#IP-Payload-Compression-Protocol-support">IP Payload Compression Protocol support</a></li><li><a href="#Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver">Ralink wireless RT2700U/2800U/3000U run(4) USB driver</a></li><li><a href="#Syncing-pf(4)-with-OpenBSD-4.5">Syncing pf(4) with OpenBSD 4.5</a></li><li><a href="#Wireless-mesh-networking">Wireless mesh networking</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#CAM-based-ATA-implementation">CAM-based ATA implementation</a></li><li><a href="#Group-Limit-Increase">Group Limit Increase</a></li><li><a href="#NFSv4-ACL-support">NFSv4 ACL support</a></li><li><a href="#V4L-support-in-Linux-emulator">V4L support in Linux emulator</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li><li><a href="#The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Flattened-Device-Tree-for-embedded-FreeBSD">Flattened Device Tree for embedded FreeBSD</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#FreeBSD/mips">FreeBSD/mips</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium-web-browser">Chromium web browser</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#DAHDI-(Zaptel)-support-for-FreeBSD">DAHDI (Zaptel) support for FreeBSD</a></li><li><a href="#NVIDIA-amd64-driver">NVIDIA amd64 driver</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#AsiaBSDCon-2010-&#8212;-The-BSD-Conference">AsiaBSDCon 2010 &#8212; The BSD Conference</a></li><li><a href="#BSDCan-2010-&#8212;-The-BSD-Conference">BSDCan 2010 &#8212; The BSD Conference</a></li><li><a href="#meetBSD-2010-&#8212;-The-BSD-Conference">meetBSD 2010 &#8212; The BSD Conference</a></li><li><a href="#The-FreeBSD-Forums">The FreeBSD Forums</a></li></ul><h3><a href="#Userland-utilities">Userland utilities</a></h3><ul><li><a href="#BSD-licensed-text-processing-tools">BSD-licensed text processing tools</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="BSD-licensed-iconv" href="#BSD-licensed-iconv" id="BSD-licensed-iconv">BSD-licensed iconv</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv">Sources in the Perforce repository</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv" title="Sources in the Perforce repository">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Good compatibility has been ensured and there are only few pending
-	items that have to be reviewed/enhanced.  Recently, an enhancement
-	has been completed, which makes it possible to accomplish better
-	transliteration, just like in the GNU version.  An initial testing
-	patch is expected at the beginning of February.</p>
-     <h3>Open tasks:</h3><ol><li>Enhance conversion tables to make use of enhanced
-	transliteration.</li><li>A performance optimization might be done later.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="3G-USB-support" href="#3G-USB-support" id="3G-USB-support">3G USB support</a></h2><p>
-	Contact: 
-          Andrew
-
-          Thompson
-         &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
-	</p>
-      <p>Recently, a bunch of new device IDs have been added for the
-	u3g(4) cellular wireless driver; the list should be comparable now with
-      other operating systems around. A lot of these devices have a
-      feature where the unit first attaches as a disk or CD-ROM that
-      contains the Win/Mac drivers. This state should be detected by the
-      u3g driver and the usb device is sent a command to switch to modem
-      mode. This has been working for quite some time but as it is
-      implemented differently for each vendor I am looking for feedback
-      on any units where the auto switchover is not working (or the init
-      is not recognized at all). Please ensure you are running an up to
-      date kernel, like r201681 or later from 9.0-CURRENT, or 8-STABLE
-      after the future merge of this revision.</p>
-    <hr /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr></table><p>
-	Contact: 
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Pawel
-	  Worach
-	 &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	</p>
-      <p>We are again able to build bootable i386/amd64 kernel.  Nathan
-	Whitehorn committed a fix to FreeBSD, which enabled LLVM/clang to
-	work mostly fine on PowerPC.  There is some preliminary testing
-	of LLVM/clang on ARM and MIPS being done.  We have some ideas
-	about sparc64 support which are currently being investigated.
-	You are welcome to contact us if you want to help.</p>
-
-      <p>Since the last report, a lot has happened mostly in the area of
-	C++; clang is currently able to build working groff, gperf and
-	devd, i.e. all of the C++ apps we have in base.  Unfortunately,
-	it still cannot build any of the C++ libraries &#8212; two of
-	them are missing builtins and libstdc++ is broken for other
-	reasons.</p>
-
-      <p>Not much happened in the clangbsd branch as we cannot
-	upgrade the clang/llvm there because we are blocked by a bug
-	that requires using newer assembler than we can ship.  This
-	might be solved by either fixing this (short term) or using
-	llvm-mc instead of GNU as for assembling (longer term).</p>
-    <h3>Open tasks:</h3><ol><li>Help with ARM/MIPS/sparc64.</li><li>More testing of clang on 3rd party apps (ports).</li><li>Discussion on integrating LLVM/clang into FreeBSD.</li></ol><hr /><h2><a name="FreeBSD-TDM-Framework" href="#FreeBSD-TDM-Framework" id="FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></h2><p>
-	Contact: 
-	  Rafal
-	  Czubak
-	 &lt;<a href="mailto:rcz@semihalf.com">rcz@semihalf.com</a>&gt;
-	<br />
-	Contact: 
-	  Michal
-	  Hajduk
-	 &lt;<a href="mailto:mih@semihalf.com">mih@semihalf.com</a>&gt;
-	</p>
-      <p>Important changes regarding FreeBSD TDM Framework since the last status
-	report:</p>
-
-      <ul>
-	<li>Fully functional TDM controller driver for Marvell Kirkwood and
-	  Discovery SoCs.</li>
-
-	<li>Working voiceband channel character device driver.</li>
-
-	<li>Working Si3215, Si3050 codec drivers on corresponding FXS, FXO
-	  ports.</li>
-
-	<li>Demo application, which is capable of manipulating voiceband
-	  channel and codec state, starting/stopping channel transfers and
-	  echoing on single channel.</li>
-
-	<li>Preliminary version of driver bridging the voiceband
-	  infrastructure with Zaptel/DAHDI.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Improve various issues regarding working drivers and demo
-	application.</li><li>Test Si3050 codec driver operation with PSTN.</li><li>Fully integrate voiceband infrastructure with Zaptel/DAHDI telephony
-	hardware drivers.</li></ol><hr /><h2><a name="HAST-&#8212;-Highly-Available-Storage" href="#HAST-&#8212;-Highly-Available-Storage" id="HAST-&#8212;-Highly-Available-Storage">HAST &#8212; Highly Available Storage</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html" title="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html">Announcement</a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html" title="Announcement">http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html</a></td></tr></table><p>
-	Contact: 
-          Pawel Jakub
-
-          Dawidek
-         &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>HAST software will provide synchronous replication of any GEOM
-      provider (eg. disk, partition, mirror, etc.) or file from one FreeBSD
-      machine (primary node) to another one (secondary node).</p>
-
-      <p>Because data is replicated at the block level neither applications, nor
-      file systems have to be modified to take advantage of this
-      functionality.</p>
-
-      <p>The functionality that HAST software will provide is very similar
-      to the functionality provided by the DRBD project for Linux.</p>
-
-      <p>The HAST project is sponsored by the FreeBSD Foundation.</p>
-
-      <p>Work is progressing well; first milestone was reached in December
-	2009 and the expected project completion date is January 31,
-	2010.</p>
-
-      <p>Check out FreeBSD mailing lists for patches to test in February and
-      wish me good luck!</p>
-
-      <p>And by the way, do not forget to donate to the FreeBSD Foundation, as your
-      donations make projects like this possible.</p>
-
-      <p>Thank you!</p>
-    <hr /><h2><a name="Intel-XScale-hwpmc(9)-support" href="#Intel-XScale-hwpmc(9)-support" id="Intel-XScale-hwpmc(9)-support">Intel XScale hwpmc(9) support</a></h2><p>
-	Contact: 
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Preliminary Hardware Performance Counter support for Intel
-	XScale ARM processors was committed to FreeBSD 9.0-CURRENT
-	in December.  This adds another supported architecture to hwpmc(9).
-	The system works for basic performance counter usage but more
-	advanced usage scenarios, namely callchain support, are not
-	yet implemented.</p>
-    <hr /><h2><a name="POSIX-utmpx-for-FreeBSD" href="#POSIX-utmpx-for-FreeBSD" id="POSIX-utmpx-for-FreeBSD">POSIX utmpx for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html" title="http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html">Announcement</a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html" title="Announcement">http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html</a></td></tr><tr><td><a href="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html" title="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html">POSIX specification</a></td><td>
-	    URL: <a href="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html" title="POSIX specification">http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html</a></td></tr><tr><td><a href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c" title="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c">NetBSD's implementation</a></td><td>
-	    URL: <a href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c" title="NetBSD's implementation">http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c</a></td></tr><tr><td><a href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c" title="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c">OpenSolaris' implementation</a></td><td>
-	    URL: <a href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c" title="OpenSolaris' implementation">http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c</a></td></tr></table><p>
-	Contact: 
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p>On January 13, I removed the utmp user accounting database and
-	replaced it with a new POSIX utmpx implementation. Unfortunately, the upgrade path is a bit
-	complex, because the utmp interface provided almost no library
-	interface to interact with the database files.</p>
-
-      <p>This change may have caused some regressions. Some ports may fail
-	to build, while there could also be bugs in the library
-	functions.</p>
-    <h3>Open tasks:</h3><ol><li>Get a list of broken ports.</li><li>Fix them to comply to standards.</li><li>Send patches upstream.</li></ol><hr /><h2><a name="SUJ-&#8212;-Journaled-SoftUpdates" href="#SUJ-&#8212;-Journaled-SoftUpdates" id="SUJ-&#8212;-Journaled-SoftUpdates">SUJ &#8212; Journaled SoftUpdates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeffr_tech.livejournal.com/" title="http://jeffr_tech.livejournal.com/"></a></td><td>
-	    URL: <a href="http://jeffr_tech.livejournal.com/" title="">http://jeffr_tech.livejournal.com/</a></td></tr></table><p>
-	Contact: 
-          Jeff
-
-          Roberson
-         &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have been adding a small intent log to SoftUpdates to
-      eliminate the requirement for fsck after an unclean shutdown. This
-      work has been funded by Yahoo!, iXsystems, and Juniper. Kirk
-      McKusick has been aiding me with design critiques and helping me
-      better understand SoftUpdates.</p>
-
-      <p>Extensive testing by myself and Peter Holm has yielded a stable
-      patch. Current users are encouraged to follow the instructions
-      posted to the current@FreeBSD.org mailing list to verify stability in your own workloads.
-      Updates are forthcoming and it is expected to be merged to
-      9.0-CURRENT before the end of January. Ports to older versions of FreeBSD
-      will be available in SVN under alternate branches. Official
-      backports will be decided by re@ when 9.0-CURRENT is stable.</p>
-
-      <p>The changes are fully backwards and forwards compatible as there
-      are very few metadata changes to the filesystem. The journal may be
-      enabled or disabled on existing FFS filesystems using tunefs(8).
-      The log consumes 64 MB of space at maximum and fsck time is
-      bounded by the size of the log rather than the size of the
-      filesystem. Other details are available in my technical
-      journal.</p>
-    <hr /><h2><a name="The-webcamd-deamon" href="#The-webcamd-deamon" id="The-webcamd-deamon">The webcamd deamon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.selasky.org/hans_petter/video4bsd/" title="http://www.selasky.org/hans_petter/video4bsd/"></a></td><td>
-	    URL: <a href="http://www.selasky.org/hans_petter/video4bsd/" title="">http://www.selasky.org/hans_petter/video4bsd/</a></td></tr></table><p>
-	Contact: 
-          Hans Petter
-
-          Selasky
-         &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>The webcamd daemon enables hundreds of different USB based
-      webcam devices to be used under the FreeBSD-8/9 operating system. The
-      webcam daemon is basically an application, which is a port of
-      Video4Linux USB webcam drivers into userspace on FreeBSD. The daemon
-      currently depends on libc, pthreads, libusb and the VIDEO4BSD
-      kernel module.</p>
-    <h3>Open tasks:</h3><ol><li>Add support for the remaining Video4Linux USB devices.</li><li>Make patches for increased buffer sizes, due to higher
-      latency in userspace. Especially for High Speed USB.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="GNATS">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting">BugBusting</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="BugBusting">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/">Experimental report pages</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="Experimental report pages">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html">PRs recommended for committer evaluation by the bugbusting team</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="PRs recommended for committer evaluation by the bugbusting team">http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt">Subscription list for the above report)</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="Subscription list for the above report)">http://people.FreeBSD.org/~linimon/recommended_subscribers.txt</a></td></tr></table><p>
-	Contact: 
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Volker
-	  Werth
-	 &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
-	</p>
-      <p>Bugmeister Gavin Atkinson has now been granted a src commit
-	bit, and is now starting to work through some of our
-	backlog.</p>
-
-      <p>The list of PRs recommended for committer evaluation by the
-	Bugbusting Team continues to receive new additions; however, it
-	has not yet achieved high visibility.  (This list contains PRs,
-	mostly with patches, that the Bugbusting Team consider potentially
-	ready to be committed as-is, or are probably trivially resolved
-	in the hands of a committer with knowledge of the particular
-	subsystem.)  One of the suggestions at the Cambridge devsummit
-	was to create a way for people to be emailed the weekly summary
-	that is posted to freebsd-bugs@, and this has now been implemented.
-	Please email linimon@FreeBSD.org to ask to be added to the
-	recommended_subscribers.txt file (see above).</p>
-
-      <p>We continue to classify PRs as they arrive, adding 'tags' to the
-	subject lines corresponding to the kernel subsystem involved, or
-	man page references for userland PRs.  These tags, in turn, produce
-	lists of PRs sorted both by tag and by manpage.  At this point
-	most of the PRs that refer to supported versions of FreeBSD have
-	been converted, and we are keeping up as new ones come in.  We
-	hope that this is making it easier to browse the PR database.</p>
-
-      <p>The overall PR count jumped to over 6,200 during the 8.0-RELEASE release
-	cycle but seems to have stabilized at around 6,100.  As in the
-	past, we have a fairly good clearance rate for ports PRs but
-	much less so for other PRs.  (Partly this is due to the concept
-	of individual ports having 'maintainers'.)</p>
-    <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with
-	closing PRs that the team has already analyzed.</li></ol><hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact: 
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team announced FreeBSD 8.0-RELEASE on
-	November 26th, 2009.  With 8.0-RELEASE completed planning has
-	begun for 7.3-RELEASE.  The schedule has been set with the
-	release date planned for early March 2010.</p>
-
-      <p>The Release Engineering Team would like to thank George
-	Neville-Neil (gnn@) for his service on the team.  George
-	continues to work with the FreeBSD Project but has stepped down
-	from the Release Engineering Team to focus on other
-	activities.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">The FreeBSD Foundation</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="The FreeBSD Foundation">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="https://twitter.com/freebsdfndation" title="https://twitter.com/freebsdfndation">Follow us on Twitter</a></td><td>
-	    URL: <a href="https://twitter.com/freebsdfndation" title="Follow us on Twitter">https://twitter.com/freebsdfndation</a></td></tr></table><p>
-	Contact: 
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>Despite a difficult economy, we more than doubled our number
-	of donors, we raised $269K towards our goal of $300K, and with
-	an improved economy hope to surpass that this year.</p>
-
-      <p>We have funded two new projects.  One is the Flattened Device Tree by
-	Rafal Jaworowski.  And, the second one is Highly Available Storage
-	by Pawel Jakub Dawidek.  We continued supporting the New Console
-	Driver by Ed Schouten and Improvements to the FreeBSD TCP Stack by
-	Lawrence Stewart.  We also purchased equipment for several
-	projects.</p>
-
-      <p>We have big plans for the new year!  We are going to significantly
-	increase our project development and equipment spending.  Stay
-	tuned for a project proposal submission announcement soon.  We
-	just announced that we are accepting travel grant applications
-	for AsiaBSDCon and will be accepting them soon for BSDCan.  And,
-	we are working on infrastructure projects to beef up hardware
-	for package-building, network-testing, etc.</p>
-
-      <p>Read more about how we supported the project and community by
-	reading our end-of-year newsletter available at <a href="http://www.FreeBSDFoundation.org/press/2009Dec-newsletter.shtml" shape="rect">http://www.FreeBSDFoundation.org/press/2009Dec-newsletter.shtml</a>.</p>
-
-      <p>We are fund-raising for 2010 now!  Find out more at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">http://www.FreeBSDFoundation.org/donate/</a>.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="bwn(4)-&#8212;-Broadcom-Wireless-driver" href="#bwn(4)-&#8212;-Broadcom-Wireless-driver" id="bwn(4)-&#8212;-Broadcom-Wireless-driver">bwn(4) &#8212; Broadcom Wireless driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO">bwn(4) sources in P4</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO" title="bwn(4) sources in P4">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO</a></td></tr></table><p>
-	Contact: 
-	  Weongyo
-	  Jeong
-	 &lt;<a href="mailto:weongyo@FreeBSD.org">weongyo@FreeBSD.org</a>&gt;
-	</p>
-      <p>bwn(4) is replacing bwi(4) driver for to the following
-	reasons:</p>
-
-      <ul>
-	<li>Uses latest v4 firmware image instead of using the much older v3
-	  firmware. In this way, we have some great benefits, such as
-	  support for N-PHYs and the fixes of various earlier firmware bugs.</li>
-
-	<li>Supports PIO mode. This is important because &#8212; as you might
-	  know &#8212; the Broadcom Wireless Driver is created by
-	  reverse-engineering so some pieces of hardware might not
-	  work with DMA operations.</li>
-
-	<li>Supports 64 bit DMA operations.</li>
-
-	<li>Separates bwi(4) driver into two parts; siba(4) driver and
-	  bwn(4) driver.  Many Broadcom wireless and NIC devices
-	  are based on Silicon Sonics Backplane, such as bwi(4), which
-	  implemented the SIBA operations internally. This resulted in
-	  code duplication as other drivers had to implement their
-	  own routines to deal with SIBA.  In the case of bwn(4),
-	  these two parts have been separated and implemented in their
-	  own kernel modules to avoid this problem and help further
-	  development by providing a standalone siba(4) driver.</li>
-      </ul>
-
-      <p>Currently, it is tested on big/little endian machines and 32/64-bit
-	DMA operation with STA mode.  A major patch for siba(4)
-	is being reviewed before committing into 9.0-CURRENT.</p>
-    <h3>Open tasks:</h3><ol><li>MESH/IBSS/HOSTAP mode is not supported.</li><li>LP/N PHYs are not supported.</li></ol><hr /><h2><a name="IP-Payload-Compression-Protocol-support" href="#IP-Payload-Compression-Protocol-support" id="IP-Payload-Compression-Protocol-support">IP Payload Compression Protocol support</a></h2><p>
-	Contact: 
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>One of the longer outstanding feature problems with the FreeBSD
-	IP security stack, broken IP Payload Compression Protocol
-	(IPcomp) support, has been fixed.</p>
-
-      <p>While working on the fix, various problems had been
-	identified:</p>
-
-      <ul>
-	<li>Problems with the IPcomp packet handling in IPsec.</li>
-
-	<li>opencrypto compression handling and deflate implementation
-	  limitations.  These were debugged using DTrace SDT
-	  probes.</li>
-
-	<li>Problems due to an outdated version of zlib used in some
-	  parts of the network stack and by the opencrypto
-	  framework.</li>
-      </ul>
-
-      <p>Patches for all but the zlib support have been committed to
-	9.0-RELEASE and merged to all supported stable branches including
-	6-STABLE.  Special thanks to Eugene Grosbein for helping with
-	testing.</p>
-    <h3>Open tasks:</h3><ol><li>Fix ng_deflate so that we can make use of Kip Macy's work
-	on an up-to-date unified zlib version in the kernel, which
-	would also fix the last occasional IPcomp hiccups.</li></ol><hr /><h2><a name="Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver" href="#Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver" id="Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver">Ralink wireless RT2700U/2800U/3000U run(4) USB driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.FreeBSD.org/showthread.php?t=7562" title="http://forums.FreeBSD.org/showthread.php?t=7562">Announcement on the FreeBSD Forums</a></td><td>
-	    URL: <a href="http://forums.FreeBSD.org/showthread.php?t=7562" title="Announcement on the FreeBSD Forums">http://forums.FreeBSD.org/showthread.php?t=7562</a></td></tr></table><p>
-	Contact: 
-          Akinori
-
-          Furukoshi
-         &lt;<a href="mailto:moonlightakkiy@yahoo.ca">moonlightakkiy@yahoo.ca</a>&gt;
-	</p>
-      <p>The run(4) driver brings support for Ralink RT2700U/2800U/3000U
-      USB wireless devices. For detailed information and list of all the
-      supported devices, please see the above mentioned URL. The source
-      code has been imported to the USB P4 repository on January 10, 2010
-      (172906).</p>
-    <h3>Open tasks:</h3><ol><li>Solve USB_TIMEOUT problem when sending beacons, and/or
-	confirm which chipsets supports AP mode if all of them do not
-      support it.</li><li>Read TX stats for AMRR on AP mode, and/or confirm which
-	chipsets supports AP mode if all of them do not support
-	it.</li><li>Maintain the code.</li></ol><hr /><h2><a name="Syncing-pf(4)-with-OpenBSD-4.5" href="#Syncing-pf(4)-with-OpenBSD-4.5" id="Syncing-pf(4)-with-OpenBSD-4.5">Syncing pf(4) with OpenBSD 4.5</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/">Viewing the changes.</a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="Viewing the changes.">http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="http://svn.FreeBSD.org/base/user/eri/pf45/head/">The actual repo to build from.</a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="The actual repo to build from.">http://svn.FreeBSD.org/base/user/eri/pf45/head/</a></td></tr></table><p>
-	Contact: 
-          Ermal
-
-          Luçi
-         &lt;<a href="mailto:eri@FreeBSD.org">eri@FreeBSD.org</a>&gt;
-	</p>
-      <p>This import is based on OpenBSD 4.5 state of pf(4). It includes
-      many improvements over the code currently present in FreeBSD. The
-      actual new feature present in pf45 repository is support for
-      divert(4), which should allow tools like snort_inline to work with
-      pf(4) too.</p>
-
-      <p>Currently, the pf(4) import is considered stable with normal
-      kernel, as well as VIMAGE enabled kernels.</p>
-    <h3>Open tasks:</h3><ol><li>pflow(4)/pflog(4)/pfsync(4) need to be made VIMAGE
-      aware.</li><li>More regression testing is needed.</li></ol><hr /><h2><a name="Wireless-mesh-networking" href="#Wireless-mesh-networking" id="Wireless-mesh-networking">Wireless mesh networking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/WifiMesh" title="http://wiki.FreeBSD.org/WifiMesh"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/WifiMesh" title="">http://wiki.FreeBSD.org/WifiMesh</a></td></tr></table><p>
-	Contact: 
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Development of the FreeBSD 802.11s stack continues.  The code in
-	FreeBSD HEAD has been updated to comply with draft 4.0.  Merge to
-	FreeBSD 8-STABLE will be done soon.</p>
-
-      <p>The developer is looking for funding to be able to implement mesh
-	link security algorithms and/or coordinated channel access
-	(performance improvement).</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="CAM-based-ATA-implementation" href="#CAM-based-ATA-implementation" id="CAM-based-ATA-implementation">CAM-based ATA implementation</a></h2><p>
-	Contact: 
-          Alexander
-
-          Motin
-         &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Scott
-
-          Long
-         &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Existing ata(4) infrastructure, which has been around many years,
-      has various problems and limitations when compared to modern
-      controllers/device support. Although the CAM subsystem (used for SCSI)
-      is almost as old as ata(4), it is more eligible to solve the current
-      problems. To reduce code duplication and better support border cases
-      such as ATAPI and SAS, we have started to develop a new CAM based
-      ATA implementation.</p>
-
-      <p>As such, CAM infrastructure has been extended to support different
-      transports. New transport has been implemented to support PATA/SATA
-	buses. To support ATA disks, a new CAM driver (ada) has been written. ATAPI
-      devices are supported by existing SCSI drivers cd, da, sa, etc. To
-	support SATA port-multipliers another new CAM driver (pmp) has been written. To
-      support most featured and widespread SATA controllers, new drivers
-      ahci(4) and siis(4) have been developed.</p>
-
-      <p>To support legacy ATA controllers, a kernel option ATA_CAM has been
-      added. When used, it makes all ata(4) controllers directly
-      available to CAM, deprecating ata(4) peripheral drivers and external
-      APIs. To make this possible, ata(4) code has been heavily refactored,
-      making controller driver API stricter.</p>
-
-      <p>Command queuing support gives new ATA implementation up to
-      double performance benefit on some workloads, with 20-30% improvement
-      quite usual.</p>
-
-      <p>SATA Port Multiplier support makes it easy to build fast and
-	cheap storage with huge capacities, by using dozens of SATA drives
-      in one system or external enclosures,</p>
-
-      <p>Some of that code has been presented in the recently released FreeBSD 8.0-RELEASE but
-	8-STABLE now includes a much improved version.</p>
-    <h3>Open tasks:</h3><ol><li>Improve timeout and transport error recovery.</li><li>Improve hot-plug support.</li><li>Find and fix any show stoppers for legacy ata(4)
-	deprecation.</li><li>Write a new, more featured driver for Marvell SATA controllers
-	(specifications desired).</li><li>Write SAS-specific transport and drivers for SAS HBAs (specifications
-        desired). SAS controllers can support SATA devices and
-        multipliers, so it should fit nicely into the new
-	infrastructure.</li></ol><hr /><h2><a name="Group-Limit-Increase" href="#Group-Limit-Increase" id="Group-Limit-Increase">Group Limit Increase</a></h2><p>
-	Contact: 
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Historically, FreeBSD has limited the number of supplemental
-	groups per process to 15 (NGROUPS_MAX was incorrectly declared to be
-	16).  In FreeBSD 8.0-RELEASE we raised the limit to 1023, which should be
-	sufficient for most users and will be acceptably efficient for
-	incorrectly written applications that statically allocate
-	NGROUPS_MAX + 1 entries.</p>
-
-      <p>Because some systems such as Linux 2.6 support a larger
-	group limit, we have further relaxed this restriction in 9.0-CURRENT and
-	made kern.ngroups a tunable value, which supports values between 1023
-	and INT_MAX - 1.  We plan to merge this to 8-STABLE before
-	8.1-RELEASE.</p>
-    <hr /><h2><a name="NFSv4-ACL-support" href="#NFSv4-ACL-support" id="NFSv4-ACL-support">NFSv4 ACL support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/NFSv4_ACLs" title="http://wiki.FreeBSD.org/NFSv4_ACLs"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/NFSv4_ACLs" title="">http://wiki.FreeBSD.org/NFSv4_ACLs</a></td></tr></table><p>
-	Contact: 
-          Edward Tomasz
-
-          Napierala
-         &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Native NFSv4 ACL support in ZFS and UFS has been committed into 9.0-CURRENT. It
-      is expected to be MFCed in order to make it into FreeBSD 8.1-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>Support for NFSv4 ACLs in tar(1).</li><li>MFC.</li></ol><hr /><h2><a name="V4L-support-in-Linux-emulator" href="#V4L-support-in-Linux-emulator" id="V4L-support-in-Linux-emulator">V4L support in Linux emulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://opal.com/freebsd/sys/compat/linux/" title="http://opal.com/freebsd/sys/compat/linux/"></a></td><td>
-	    URL: <a href="http://opal.com/freebsd/sys/compat/linux/" title="">http://opal.com/freebsd/sys/compat/linux/</a></td></tr></table><p>
-	Contact: 
-          J.R.
-
-          Oldroyd
-         &lt;<a href="mailto:fbsd@opal.com">fbsd@opal.com</a>&gt;
-	</p>
-      <p>V4L video support in the Linux emulator is now available.</p>
-
-      <p>This work allows Linux applications using V4L video calls to
-      work with existing FreeBSD video drivers that provide V4L interfaces.
-      It is tested and working with the net/skype port and also with
-      browser-based Flash applications that access webcams. An early version has been
-      committed to 9.0-CURRENT and work is in progress to commit the latest
-      version and then MFC. It is also tested on FreeBSD-8.0/amd64 and
-      FreeBSD-7.2/i386.</p>
-
-      <p>Note: to be clear, this does not add V4L support to all webcams.
-      The FreeBSD camera driver must already offer V4L support itself in
-      order for a Linux application to be able to use that camera. The
-      multimedia/pwcbsd port provides the pwc(4) driver that already has
-      V4L support. If your camera is supported by a different driver, you
-      will need to enhance that driver to add V4L support.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">German Documentation Project Homepage</a></td><td>
-	    URL: <a href="http://doc.bsdgroup.de" title="German Documentation Project Homepage">http://doc.bsdgroup.de</a></td></tr></table><p>
-	Contact: 
-          Johann
-
-          Kois
-         &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Benedict
-
-          Reuschling
-         &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Martin
-
-          Wilke
-         &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are happy to announce that Benedict Reuschling is now free
-      from mentorship and can commit to the documentation tree on his own.</p>
-
-      <p>Since the last status report, the German Documentation Team has
-      chased updates to various sections of the FreeBSD Handbook, FAQ and
-      the German website. Many handbook pages have been updated to the latest
-      version, including chapters about configuration, disks, kernel
-      configuration, printing, multimedia and virtualization.</p>
-
-      <p>We require help from volunteers that are willing to contribute
-      bug fixes or translations. The following documents need active
-      maintainership and are a good training ground for those willing to
-      join the translation team:</p>
-
-      <ul>
-        <li>arch-handbook/jail/</li>
-
-        <li>developers-handbook/I10n/</li>
-
-        <li>developers-handbook/policies/</li>
-
-        <li>developers-handbook/sockets/ (translation from scratch)</li>
-
-        <li>handbook/firewalls/ (translation from scratch)</li>
-
-        <li>handbook/security/</li>
-
-        <li>porters-handbook/</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Read the translations and report bugs to
-      de-bsd-translators@de.FreeBSD.org.</li><li>Translate articles or missing sections listed above.</li></ol><hr /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu/" title="http://www.FreeBSD.org/hu/">Hungarian Web Page for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu/" title="Hungarian Web Page for FreeBSD">http://www.FreeBSD.org/hu/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu/" title="http://www.FreeBSD.org/doc/hu/">Hungarian Documentation for FreeBSD</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu/" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the last months, no new translation has been added.
-	Lacking human resources, we can only manage to keep the existing
-	documentation and web page translations up to date.  If you are interested
-	in helping us, please contact us via the email addresses
-	noted above.</p>
-    <h3>Open tasks:</h3><ol><li>Translate release notes.</li><li>Add more article translations.</li></ol><hr /><h2><a name="The-FreeBSD-Spanish-Documentation-Project" href="#The-FreeBSD-Spanish-Documentation-Project" id="The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="http://www.FreeBSD.org/doc/es/articles/fdp-es/">Introduction to the Spanish Documentation Project</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="Introduction to the Spanish Documentation Project">http://www.FreeBSD.org/doc/es/articles/fdp-es/</a></td></tr><tr><td><a href="https://listas.es.FreeBSD.org/mailman/listinfo/doc" title="https://listas.es.FreeBSD.org/mailman/listinfo/doc">Translators' Mailing List</a></td><td>
-	    URL: <a href="https://listas.es.FreeBSD.org/mailman/listinfo/doc" title="Translators' Mailing List">https://listas.es.FreeBSD.org/mailman/listinfo/doc</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>There is one article translation pending review.  Apart from this,
-	neither translations nor maintenance work have been done.  We need
-	more volunteers, mostly translators but we are glad to have
-	more reviewers, as well.  One can join by simply subscribing to
-	the translators' mailing list where all the work is done.</p>
-    <h3>Open tasks:</h3><ol><li>Update Handbook translation.</li><li>Update webpage translation.</li><li>Add more article translations.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Flattened-Device-Tree-for-embedded-FreeBSD" href="#Flattened-Device-Tree-for-embedded-FreeBSD" id="Flattened-Device-Tree-for-embedded-FreeBSD">Flattened Device Tree for embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="http://wiki.FreeBSD.org/FlattenedDeviceTree">Project wiki pages</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="Project wiki pages">http://wiki.FreeBSD.org/FlattenedDeviceTree</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/..." title="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...">Project P4 branch</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/..." title="Project P4 branch">http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...</a></td></tr></table><p>
-	Contact: 
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The purpose of this project is to provide FreeBSD with support for the
-	Flattened Device Tree (FDT) technology, the mechanism for describing
-	computer hardware resources, which cannot be probed or self enumerated, in
-	a uniform and portable way. The primary consumers of this technology are
-	embedded FreeBSD platforms (ARM, AVR32, MIPS, PowerPC), where a lot of
-	designs are based on similar chips but have different assignment of pins,
-	memory layout, addresses bindings, interrupts routing and other resources.</p>
-
-      <p>Current state highlights:</p>
-
-      <ul>
-	<li>Environment, supported tools</li>
-
-	<ul>
-	  <li>Integrated device tree compiler (dtc) and libfdt into FreeBSD
-	    userspace, kernel and loader build</li>
-	</ul>
-
-	<li>loader(8)</li>
-
-	<ul>
-	  <li>Full support for device tree blob handling</li>
-
-	  <li>Load, traverse, modify (including add/remove) device tree
-	    nodes and properties</li>
-
-	  <li>Pass the device tree blob to the kernel</li>
-
-	  <li>Both ARM and PowerPC loader(8) supported</li>
-	</ul>
-
-	<li>Kernel side FDT support (common)</li>
-
-	<ul>
-	  <li>Developed OF interface for FDT-backed platforms</li>
-
-	  <li>ofw_bus I/F (and /dev/openfirm) available with FDT</li>
-
-	  <li>Integrated FDT resources representation with newbus (fdtbus
-	    and simplebus drivers)</li>
-	</ul>
-
-	<li>PowerPC kernel (Freescale MPC85XX SOC)</li>
-
-	<ul>
-	  <li>MPC8555CDS and MPC8572DS successfully converted to FDT
-	    conventions</li>
-	</ul>
-
-	<li>ARM kernel (Marvell Orion, Kirkwood and Discovery SOC)</li>
-
-	<ul>
-	  <li>Work in progress on integrating FDT infrastructure with ARM
-	    platform code</li>
-	</ul>
-      </ul>
-
-      <p>Work on this project has been sponsored by the FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Complete missing pieces for PowerPC (PCI bridge driver conversion to
-	FDT).</li><li>Complete ARM support.</li><li>Merge to SVN.</li></ol><hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><p>
-	Contact: 
-	  Marcel
-	  Moolenaar
-	 &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work continues on our ia64 port.  Many recent commits to
-	help improve stability have been made to 9.0-CURRENT and MFCed
-	to 8-STABLE.</p>
-
-      <p>Due to interest from a very motivated user, package builds
-	have been restarted for ia64-8.  This is primarily intended as
-	a QA step to discover and fix bugs on ia64, rather than to
-	create packages for upload.</p>
-
-      <p>Based on the above, Mark Linimon documented how to add more
-	architectures to the package cluster scheduler.  (This work will
-	also be of use in an upcoming effort to start powerpc package
-	builds.)</p>
-
-      <p>There are currently 3 ia64 machines online and building
-	packages.  The machines seem stable as long as multiple
-	simultaneous package builds are not attempted, in which case
-	they get machine checks.  This is puzzling, since other heavy
-	workloads seem stable on the same machines.</p>
-    <h3>Open tasks:</h3><ol><li>Continue to try to understand why multiple simultaneous
-	package builds bring the machines down.</li><li>Upgrade the firmware on the two machines at Yahoo! to
-	see if that helps the problem.</li><li>Configure a fourth machine that has been made available
-	to us.</li><li>Figure out the problems with the latest GCC port on
-	ia64.</li><li>We can use some help with reviewing the ia64 platform pages
-	and bringing them up-to-date.</li></ol><hr /><h2><a name="FreeBSD/mips" href="#FreeBSD/mips" id="FreeBSD/mips">FreeBSD/mips</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/mips/index.html" title="http://www.FreeBSD.org/projects/mips/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/projects/mips/index.html" title="">http://www.FreeBSD.org/projects/mips/index.html</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/FreeBSD/mips" title="http://wiki.FreeBSD.org/FreeBSD/mips"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/FreeBSD/mips" title="">http://wiki.FreeBSD.org/FreeBSD/mips</a></td></tr></table><p>
-	Contact: 
-          The FreeBSD/mips mailing list
-         &lt;<a href="mailto:mips@FreeBSD.org">mips@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          Warner
-
-          Losh
-         &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The base/projects/mips branch has been merged into 9.0-CURRENT.
-      The merge is complete and the sanity tests have passed. The code
-      has booted on both a Ubiquiti RouterStation (big endian) as well as
-      in gxemul (little endian).</p>
-
-      <p>The branch lived for one year, minus a day, and accumulated much
-      work:</p>
-
-      <ul>
-        <li>A new port to the Atheros AR71xx series of processors. This
-        port supports the RouterStation and RouterStation PRO boards from
-        Ubiquiti. Other boards should work with minimal tweaking. This
-        port should be considered as nearing production quality, and has
-        been used extensively by the developers. The primary author of
-        this port is Oleksandr Tymoshenko (gonzo@FreeBSD.org).</li>
-
-        <li>A new port to the SiByte BCM1250 SoC on the BCM91250
-        evaluation board (aka SWARM). This port is reported to be stable,
-        but this hardware is a little old and not widely available. The
-        primary author of this port is Neel Natu (neel@FreeBSD.org). Only
-        one core is presently supported.</li>
-
-        <li>A port, donated by Cavium, to their Octeon and Octeon plus
-        series of SoC (CN3xxx and CN5xxx). This code is preliminary,
-        supporting only a single core right now. It has been lightly
-        tested on the CN3860 evaluation board only in 32-bit mode. Warner
-        Losh (imp@FreeBSD.org) has been driving the efforts to get this
-        code into the tree.</li>
-
-        <li>A port, donated by RMI, to their XLR series of SoCs. This
-        port is single core only, as well. The code reaches multi-user but
-        should be considered beta quality for the moment. Randal Stewart
-        (rrs@FreeBSD.org) has been driving the efforts to integrate this
-        into the tree.</li>
-
-        <li>Preliminary support for building a mips64 kernel from this
-        source base. More work is needed here, but at least two kernels
-        successfully build in 64-bit mode (OCTEON1 and MALTA64).</li>
-
-        <li>Very early support for N32 and N64 ABIs</li>
-
-        <li>Support for booting compressed kernels has been added
-        (gonzo@).</li>
-
-        <li>Improved support for debugging</li>
-
-        <li>Improved busdma and bus_space support</li>
-
-        <li>Many bug fixes</li>
-
-        <li>More types of MIPS cores are recognized</li>
-
-        <li>Expanded cache handling for newer processors</li>
-
-        <li>Beginning of a port to the alchemy au1XXX cpus is present,
-        but experimental.</li>
-
-        <li>Work on SMP is underway to support multicore processors like
-        the SiByte, Octeon and XLR processors.</li>
-      </ul>
-
-      <p>The development branch had been updated incorrectly several times over the
-	past year, and the damage was too much to repair. We have retired the
-      branch and will do further mips development in 9.0-CURRENT for the time
-      being. If you have a checked out tree, the suggested way to update
-      the projects/mips tree you have is to do a "svn switch
-      svn://svn.FreeBSD.org/base/head" in that tree.</p>
-
-      <p>I would like to thank everybody that has contributed time, code
-      or hardware to make FreeBSD/mips better.</p>
-
-      <p>As development proceeds, I will keep posting updates. In
-      addition, I hope to have some mini "how-to" wiki pages done for
-      people that want to try it out.</p>
-    <h3>Open tasks:</h3><ol><li>We are still investigating how feasible merging all this work
-      into 8-STABLE will be, as it represents a huge leap forward in code
-      stability and quality.</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
-	Contact: 
-          Marius
-
-          Strobl
-         &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>The main thing that has taken place since the last Status Report
-      is that I have gotten to the bottom of the remaining PCI problems
-      with Sun Fire V215/V245 and support for these has been completed
-      and since r202023 now is part of 9.0-CURRENT. With some luck it will also
-      be part of the upcoming 7.3-RELEASE.</p>
-
-      <p>Some other news:</p>
-
-      <ul>
-        <li>Two bugs in the NFS server causing unaligned access and
-        thus panics on sparc64 and all other architectures with strict
-        alignment requirements (basically all Tier-2 ones) have been
-        fixed. There likely will be a 8.0-RELEASE Erratum Notice released
-        for these.</li>
-
-        <li>FreeBSD has been adopted to the changed firmware of newer Sun
-        Fire V480 (those equipped with version 7 Schizo bridges) and has been
-        reported to now run fine on these. The necessary change will be
-        part of 7.3-RELEASE. Unfortunately, using the on-board NICs in
-        older models of Sun Fire V480 (at least those equipped with
-        version 4 Schizo bridges) under FreeBSD still leads to the firmware
-        issuing a FATAL RESET due to what appears to be a CPU bug, which
-        needs to be worked around.</li>
-
-        <li>Work on supporting Sun Fire V1280 has been started but still
-        is in very early stages. Unfortunately, these are rather quirky
-        machines. After solving two firmware specialties the loader now
-        is able to boot the kernel but the latter currently still fails
-        in early cycles as trying to take the trap table over from the
-        firmware results in a solid hang.</li>
-      </ul>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium-web-browser" href="#Chromium-web-browser" id="Chromium-web-browser">Chromium web browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://chromium.jaggeri.com" title="http://chromium.jaggeri.com">test builds and port progress</a></td><td>
-	    URL: <a href="http://chromium.jaggeri.com" title="test builds and port progress">http://chromium.jaggeri.com</a></td></tr><tr><td><a href="http://www.links.org/?p=724" title="http://www.links.org/?p=724">first build information</a></td><td>
-	    URL: <a href="http://www.links.org/?p=724" title="first build information">http://www.links.org/?p=724</a></td></tr></table><p>
-	Contact: 
-          Ben
-
-          Laurie
-         &lt;<a href="mailto:ben@links.org">ben@links.org</a>&gt;
-	</p>
-      <p>Chromium is a Webkit-based web browser that is largely BSD
-      licensed. It has been ported from Linux to FreeBSD in October and we have been
-      posting patches and test builds periodically since then. Chromium
-      works well on FreeBSD &#8212; it is very fast and stable but there
-      are a handful of rough edges that need to be polished up. Two
-      remaining bugs should probably be fixed before releasing a
-      chromium-devel port. We are looking for volunteers to test and
-      maintain this port to make this BSD browser a viable option on
-      FreeBSD desktop systems.</p>
-    <h3>Open tasks:</h3><ol><li>Fix sporadic rendering freezes.</li><li>Fix JavaScript interpreter, v8, on i386 architecture.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">The FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="The FreeBSD Ports Collection">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
-	Contact: 
-          Mark
-
-          Linimon
-         &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most of the recent activity has been dealing with the 8.0-RELEASE
-      process. As an experiment, we have tried to decouple the ports QA
-      timeline as much as possible from the src QA timeline. Although
-      this meant that the impact on people actively maintaining and using
-      ports has been much less than in previous releases, it still has not
-      solved the problem of the release going out with a stale set of
-      packages. We are still trying to come up with a better solution for
-      the problem.</p>
-
-      <p>The ports count is over 21,000. The PR count jumped to over
-      1,000 but is now back to around 950.</p>
-
-      <p>We are currently building packages for amd64-6, amd64-7,
-      amd64-8, i386-6, i386-7, i386-8, i386-9, ia64-8, sparc64-7, and
-      sparc64-8. This represents the addition of i386-9 and ia64-8 since
-      the last report.</p>
-
-      <p>There has been some discussion of when to drop regular package
-      builds for 6.X but no decision has been made yet. The cluster and
-      the port managers are struggling to keep up with so many branches being
-      active all at the same time.</p>
-
-      <p>Mark Linimon continues to make progress on the cluster nodes.
-      Almost every node that does not have a hard disk failure is now
-      online. In addition, he continues to make progress debugging
-      problems that occasionally take nodes offline.</p>
-
-      <p>The next task is to characterize the overall performance of the
-      build cluster. The question has been asked of us, "what would it
-      take to speed up package builds?" There is no one simple answer. It
-      is not merely a matter of having a larger number of package
-      building machines, so before asking for funding we first need to
-      identify the current bottlenecks. While we are starting to
-      understand the problems on the nodes, the problems on the dispatch
-      machine itself are much harder. Complicating the matter is that
-      there are several periodic processes (ZFS backup, ZFS expiration,
-      and errorlog compression, among others) that can combine to slow
-      that machine significantly. The simultaneous interaction of all these
-      is proving difficult to quantify.</p>
-
-      <p>Between Pav Lucistnik and Martin Wilke, many more experimental ports runs have
-      been completed and committed.</p>
-
-      <p>We have added 3 new committers since the last report, and 1
-      older one has rejoined us.</p>
-    <h3>Open tasks:</h3><ol><li>We are still trying to set up ports tinderboxes that can be
-      made available to committers for pre-testing.</li><li>Most of the remaining ports PRs are "existing port/PR
-      assigned to committer". Although the maintainer-timeout policy is
-      helping to keep the backlog down, we are going to need to do more
-      to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have more
-      than 4,700 unmaintained ports. (See, for instance, the list on
-      portsmon. The percentage remains steady at just over 22%.) We are
-      always looking for dedicated volunteers to adopt at least a few
-      unmaintained ports. As well, the packages on amd64 and especially
-      sparc64 lag behind i386, and we need more testers for those.</li></ol><hr /><h2><a name="VirtualBox-on-FreeBSD" href="#VirtualBox-on-FreeBSD" id="VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/VirtualBox" title="http://wiki.FreeBSD.org/VirtualBox"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/VirtualBox" title="">http://wiki.FreeBSD.org/VirtualBox</a></td></tr></table><p>
-	Contact: 
-	  Beat
-	  Gaetzi
-	 &lt;<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Bernhard
-	  Froehlich
-	 &lt;<a href="mailto:decke@bluelife.at">decke@bluelife.at</a>&gt;
-	<br />
-	Contact: 
-	  Juergen
-	  Lock
-	 &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Martin
-	  Wilke
-	 &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	</p>
-      <p>VirtualBox 3.1.2 has been committed to the ports tree.</p>
-
-      <p>Several changes to the port have been performed with this
-	update including:</p>
-
-      <ul>
-	<li>Port has been renamed to virtualbox-ose to reflect that we
-	  are now using the OSE version.</li>
-
-	<li>A separate port for the kernel modules has been created
-	  &#8212; virtualbox-ose-kmod.</li>
-
-	<li>A separate port for guest additions for FreeBSD guests has
-	  been created &#8212; virtualbox-ose-additions.</li>
-
-	<li>Proper FreeBSD support for PulseAudio has been added.</li>
-
-	<li>Procfs is not required anymore because vbox uses sysctl(3)
-	  now.</li>
-
-	<li>Juergen Lock's FreeBSD host networking patches have been added.  They
-	  are now also in the upstream vbox SVN (modulo vbox variable
-	  naming style adjustments).</li>
-
-	<li>Allow direct tap networking again (for users that need the
-	  best network performance and/or need more complex network
-	  setups, like when they want to use routing instead of bridging
-	  to e.g. protect guests from messing with the lan's ARP tables;
-	  a tap + routing + proxy arp example is in the above
-	  freebsd-emulation@ posting.)</li>
-
-	<li>Enable vbox's shared MAC feature when using bridged mode on
-	  a Wifi interface, together with the virtualbox-ose-kmod
-	  change this should fix bridged mode for Wifi users.</li>
-      </ul>
-
-      <p>We would like to say thanks to all the people that helped us
-	by reporting bugs and submitting fixes.  We also thank the
-	VirtualBox developers for their help with the ongoing effort
-	to port VirtualBox to FreeBSD</p>
-    <hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="DAHDI-(Zaptel)-support-for-FreeBSD" href="#DAHDI-(Zaptel)-support-for-FreeBSD" id="DAHDI-(Zaptel)-support-for-FreeBSD">DAHDI (Zaptel) support for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html" title="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html">Official Announcement</a></td><td>
-	    URL: <a href="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html" title="Official Announcement">http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html</a></td></tr><tr><td><a href="http://svn.digium.com/svn/dahdi/freebsd/trunk/" title="http://svn.digium.com/svn/dahdi/freebsd/trunk/">SVN repository</a></td><td>
-	    URL: <a href="http://svn.digium.com/svn/dahdi/freebsd/trunk/" title="SVN repository">http://svn.digium.com/svn/dahdi/freebsd/trunk/</a></td></tr></table><p>
-	Contact: 
-          Max
-
-          Khon
-         &lt;<a href="mailto:fjoe@FreeBSD.org">fjoe@FreeBSD.org</a>&gt;
-	</p>
-      <p>A DAHDI support module for FreeBSD has been created in the
-      official Asterisk SVN repository.</p>
-
-      <p>The following drivers are currently ported:</p>
-
-      <ul>
-        <li>main DAHDI driver</li>
-
-        <li>all software echo cancellation drivers</li>
-
-        <li>dahdi_dynamic</li>
-
-        <li>dahdi_dynamic_loc</li>
-      </ul>
-
-      <p>The following HW drivers are currently ported and tested:</p>
-
-      <ul>
-        <li>wct4xxp, including HW echo cancellation support
-        (Octasic)</li>
-
-        <ul>
-          <li>Digium TE205P/TE207P/TE210P/TE212P: PCI dual-port
-          T1/E1/J1</li>
-
-          <li>Digium TE405P/TE407P/TE410P/TE412P: PCI quad-port
-          T1/E1/J1</li>
-
-          <li>Digium TE220: PCI-Express dual-port T1/E1/J1</li>
-
-          <li>Digium TE420: PCI-Express quad-port T1/E1/J1</li>
-        </ul>
-
-        <li>wcb4xxp</li>
-
-        <ul>
-          <li>Digium B410: PCI quad-port BRI</li>
-
-          <li>Junghanns.NET HFC-2S/4S/8S duo/quad/octoBRI</li>
-
-          <li>OpenVox B200P/B400P/B800P</li>
-
-          <li>BeroNet BN2S0/BN4S0/BN8S0</li>
-        </ul>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>The port for dahdi_dynamic_eth and dahdi_dynamic_ethmf is
-	underway.</li><li>More HW drivers need to be ported.</li><li>Please let me know if you can provide remote access with
-        serial console to any box with ISDN/T1/E1 HW not currently
-        supported by DAHDI for FreeBSD but supported by DAHDI for Linux. I
-        am also interested in porting drivers for FXO/FXS cards. Please
-        let me know if you can provide a remote access or donate a
-	card.</li></ol><hr /><h2><a name="NVIDIA-amd64-driver" href="#NVIDIA-amd64-driver" id="NVIDIA-amd64-driver">NVIDIA amd64 driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nvnews.net/vbulletin/showthread.php?t=142120" title="http://www.nvnews.net/vbulletin/showthread.php?t=142120">Release Announcement</a></td><td>
-	    URL: <a href="http://www.nvnews.net/vbulletin/showthread.php?t=142120" title="Release Announcement">http://www.nvnews.net/vbulletin/showthread.php?t=142120</a></td></tr></table><p>
-	Contact: 
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>NVIDIA has released the first BETA version of its graphics
-	drivers for FreeBSD/amd64.  Note that this driver will work on FreeBSD
-	versions 7.3-RELEASE or 8.0-RELEASE and later.  It also works on very recent
-	versions of 7.2-STABLE.  More details are provided in the
-	official release announcement.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="AsiaBSDCon-2010-&#8212;-The-BSD-Conference" href="#AsiaBSDCon-2010-&#8212;-The-BSD-Conference" id="AsiaBSDCon-2010-&#8212;-The-BSD-Conference">AsiaBSDCon 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2010.AsiaBSDCon.org/" title="http://2010.AsiaBSDCon.org/"></a></td><td>
-	    URL: <a href="http://2010.AsiaBSDCon.org/" title="">http://2010.AsiaBSDCon.org/</a></td></tr></table><p>
-	Contact: 
-	  AsiaBSDCon Information
-	 &lt;<a href="mailto:secretary@AsiaBSDCon.org">secretary@AsiaBSDCon.org</a>&gt;
-	</p>
-      <p>AsiaBSDCon is a conference for users and developers on BSD
-	based systems.  AsiaBSDCon is a technical conference and aims
-	to collect the best technical papers and presentations
-	available to ensure that the latest developments in our open
-	source community are shared with the widest possible audience.
-	The conference is for anyone developing, deploying and using
-	systems based on FreeBSD, NetBSD, OpenBSD, DragonFlyBSD, Darwin
-	and MacOS X.</p>
-
-      <p>The next conference will be held at the Tokyo University of
-	Science, Tokyo, Japan, on 11th to 14th March, 2010.</p>
-
-      <p>For more detailed information, please check the conference
-	web site.</p>
-    <hr /><h2><a name="BSDCan-2010-&#8212;-The-BSD-Conference" href="#BSDCan-2010-&#8212;-The-BSD-Conference" id="BSDCan-2010-&#8212;-The-BSD-Conference">BSDCan 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.BSDCan.org/2010/" title="http://www.BSDCan.org/2010/"></a></td><td>
-	    URL: <a href="http://www.BSDCan.org/2010/" title="">http://www.BSDCan.org/2010/</a></td></tr></table><p>
-	Contact: 
-	  BSDCan Information
-	 &lt;<a href="mailto:info@BSDCan.org">info@BSDCan.org</a>&gt;
-	</p>
-      <p>BSDCan, a BSD conference held in Ottawa, Canada, has quickly
-	established itself as the technical conference for people
-	working on and with 4.4BSD based operating systems and related
-	projects.  The organizers have found a fantastic formula that
-	appeals to a wide range of people from extreme novices to
-	advanced developers.</p>
-
-      <p>BSDCan 2010 will be held on 13-14 May 2010 at the University of
-	Ottawa, and will be preceded by two days of Tutorials on 11-12
-	May 2010.</p>
-
-      <p>There will be related events (of a social nature, for the most
-	part) on the day before and after the conference.</p>
-
-      <p>Please check the conference web site for more information.</p>
-    <hr /><h2><a name="meetBSD-2010-&#8212;-The-BSD-Conference" href="#meetBSD-2010-&#8212;-The-BSD-Conference" id="meetBSD-2010-&#8212;-The-BSD-Conference">meetBSD 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.meetBSD.org" title="http://www.meetBSD.org"></a></td><td>
-	    URL: <a href="http://www.meetBSD.org" title="">http://www.meetBSD.org</a></td></tr></table><p>
-	Contact: 
-	  meetBSD
-	  Information
-	 &lt;<a href="mailto:info@meetBSD.org">info@meetBSD.org</a>&gt;
-	</p>
-      <p>The meetBSD conference is an annual event gathering users and
-	developers of the BSD operating system family, mostly FreeBSD,
-	NetBSD and OpenBSD.  Afer the special California edition,
-	meetBSD Wintercamp in Livigno, this year we are back to
-	Krakow, Poland.</p>
-
-      <p>In 2010, meetBSD will be held on 2-3 July at the Jagiellonian
-	University.</p>
-
-      <p>See the conference main web site for more details.</p>
-    <hr /><h2><a name="The-FreeBSD-Forums" href="#The-FreeBSD-Forums" id="The-FreeBSD-Forums">The FreeBSD Forums</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.FreeBSD.org/" title="http://forums.FreeBSD.org/"></a></td><td>
-	    URL: <a href="http://forums.FreeBSD.org/" title="">http://forums.FreeBSD.org/</a></td></tr></table><p>
-	Contact: 
-          FreeBSD Forums
-
-          Admins
-         &lt;<a href="mailto:forum-admins@FreeBSD.org">forum-admins@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-          FreeBSD Forums
-
-          Moderators
-         &lt;<a href="mailto:forum-moderators@FreeBSD.org">forum-moderators@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last report we have seen a growth of 2,000 users on our
-      forums resulting in approximately 10,000 registered users at this time. The
-      posts count is about to reach 60,000 soon, which are contained in
-      almost 9,000 threads.</p>
-
-      <p>The sign-up rate still hovers between 50-100 each week. The
-      total number of visitors (including 'guests') is currently hard to
-      gauge, but is likely to be a substantial multiple of the registered
-      userbase.</p>
-
-      <p>New topics and posts are actively 'pushed out' to search
-      engines. This in turn makes the forums show up in search results
-      more and more often, making it a valuable and very accessible
-      source of information for the FreeBSD community.</p>
-
-      <p>One of the contributing factors to the forums' success is their
-      'BSD-style' approach when it comes to administration and
-      moderation. The forums have a strong and unified identity and are
-      very actively moderated, spam-free, and with a core group of very
-      active and helpful members, dispensing many combined decades' worth
-      of knowledge to starting, intermediate and professional users of
-      FreeBSD.</p>
-    <hr /><br /><h1><a name="Userland-utilities" href="#Userland-utilities" id="Userland-utilities">Userland utilities</a></h1><br /><h2><a name="BSD-licensed-text-processing-tools" href="#BSD-licensed-text-processing-tools" id="BSD-licensed-text-processing-tools">BSD-licensed text processing tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc">Perforce repository</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="Perforce repository">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>As 8.0-RELEASE is out, BSD bc/dc can be now committed to 9.0-CURRENT. We are
-	only waiting for an experimental package building to make sure there are no
-	regressions after this change.  BSD grep is complete but it cannot be integrated yet because of
-	some regex library issues.  We need first a fast and modern regex
-	library so that we can change to BSD grep.  BSD sort has few
-	incomplete features and needs some performance review.</p>
-    <h3>Open tasks:</h3><ol><li>Commit BSD bc/dc.</li><li>Implement remaining features for sort and optimize
-	performance.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2010-01-2010-03.html b/website/content/en/status/report-2010-01-2010-03.html
deleted file mode 100644
index b0c8d9d3d6..0000000000
--- a/website/content/en/status/report-2010-01-2010-03.html
+++ /dev/null
@@ -1,1554 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" src="../../layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between January and
-      March 2010.  Being the first of the four reports planned for 2010 with
-      46 entries, it shows a good progress of the FreeBSD Project and proves
-      that our committers are keeping up with the latest trends in the OS
-      development.  During this period, a new minor version of FreeBSD,
-      7.3-RELEASE, has been released, while the release process for
-      8.1-RELEASE is soon to begin and is planned to be released later this
-      summer.</p><p>Thanks to all the reporters for their excellent work!  We hope you
-      enjoy the reading.</p><p>Please note that the deadline for submissions covering the
-      period between April and June 2010 is July 15th, 2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Google-Summer-of-Code-2010">Google Summer of Code 2010</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Chromium-web-browser">Chromium web browser</a></li><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#EFI-support-for-FreeBSD/i386">EFI support for FreeBSD/i386</a></li><li><a href="#mfsBSD">mfsBSD</a></li><li><a href="#Modular-Congestion-Control">Modular Congestion Control</a></li><li><a href="#NAND-Flash-framework-for-embedded-FreeBSD">NAND Flash framework for embedded FreeBSD</a></li><li><a href="#Out-of-Tree-Toolchain">Out of Tree Toolchain</a></li><li><a href="#PC-BSD-PC-SysInstall-Backend">PC-BSD PC-SysInstall Backend</a></li><li><a href="#The-tbemd-branch">The tbemd branch</a></li><li><a href="#webcamd">webcamd</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#Release-Engineering-Team">Release Engineering Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#(Virtual)-Network-Stack-resource-cleanup">(Virtual) Network Stack resource cleanup</a></li><li><a href="#802.11n-support">802.11n support</a></li><li><a href="#Atheros-AR9285-support">Atheros AR9285 support</a></li><li><a href="#Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></li><li><a href="#Experimental-NFS-subsystem-(NFSv4)">Experimental NFS subsystem (NFSv4)</a></li><li><a href="#ipfw-and-dummynet-enhancements">ipfw and dummynet enhancements</a></li><li><a href="#net80211-rate-control-framework">net80211 rate control framework</a></li><li><a href="#TCP/UDP-connection-groups">TCP/UDP connection groups</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#CAM-based-ATA-implementation">CAM-based ATA implementation</a></li><li><a href="#Dynamic-Ticks-in-FreeBSD">Dynamic Ticks in FreeBSD</a></li><li><a href="#geom_sched">geom_sched</a></li><li><a href="#IPv6-without-legacy-IP-kernel">IPv6 without legacy IP kernel</a></li><li><a href="#Multichannel-playback-in-HDA-sound-driver-(snd_hda)">Multichannel playback in HDA sound driver (snd_hda)</a></li><li><a href="#Rewrite-of-FreeBSD-read/write-path-using-vnode-page">Rewrite of FreeBSD read/write path using vnode page</a></li><li><a href="#SUJ:-Journaled-Softupdates">SUJ: Journaled Softupdates</a></li><li><a href="#ZFS">ZFS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-port-for-libunwind">FreeBSD port for libunwind</a></li><li><a href="#LDAP-support-in-base-system">LDAP support in base system</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-port-for-TI-DaVinci">FreeBSD/arm port for TI DaVinci</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#FreeBSD/mips-on-D-Link-DIR-320">FreeBSD/mips on D-Link DIR-320</a></li><li><a href="#FreeBSD/powerpc">FreeBSD/powerpc</a></li><li><a href="#FreeBSD/powerpc64-port">FreeBSD/powerpc64 port</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Portmaster">Portmaster</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#QAT">QAT</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan-2010-&#8212;-The-BSD-Conference">BSDCan 2010 &#8212; The BSD Conference</a></li><li><a href="#meetBSD-2010----The-BSD-Conference">meetBSD 2010 -- The BSD Conference</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Google-Summer-of-Code-2010" href="#Google-Summer-of-Code-2010" id="Google-Summer-of-Code-2010">Google Summer of Code 2010</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://socghop.appspot.com/org/home/google/gsoc2010/freebsd" title="http://socghop.appspot.com/org/home/google/gsoc2010/freebsd">FreeBSD GSoC Homepage</a></td><td>
-	    URL: <a href="http://socghop.appspot.com/org/home/google/gsoc2010/freebsd" title="FreeBSD GSoC Homepage">http://socghop.appspot.com/org/home/google/gsoc2010/freebsd</a></td></tr><tr><td><a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline" title="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline">GSoC Timeline</a></td><td>
-	    URL: <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline" title="GSoC Timeline">http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline</a></td></tr></table><p>
-	Contact: 
-	  Brooks
-
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Robert
-
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are once again participating in the Google Summer of Code.  This
-	is our 6th year of participation and we hope to once again see great
-	results from our students.  Currently applications have all been
-	submitted and we are in the process of reviewing them.  Accepted
-	students will be announced April 26th and coding officially begins
-	May 24th.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Chromium-web-browser" href="#Chromium-web-browser" id="Chromium-web-browser">Chromium web browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://chromium.jaggeri.com" title="http://chromium.jaggeri.com">Main chromium site</a></td><td>
-	    URL: <a href="http://chromium.jaggeri.com" title="Main chromium site">http://chromium.jaggeri.com</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/Chromium" title="http://wiki.FreeBSD.org/Chromium">Build instructions for older patches</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Chromium" title="Build instructions for older patches">http://wiki.FreeBSD.org/Chromium</a></td></tr></table><p>
-	Contact: 
-	  sprewell
-	 &lt;<a href="mailto:chromium@jaggeri.com">chromium@jaggeri.com</a>&gt;
-	</p>
-      <p>Chromium is a Webkit-based web browser that is mostly BSD
-	licensed.  It works very well on FreeBSD and even supports new features
-	like HTML 5 video.  I have started offering subscriptions to fund the
-	porting effort to FreeBSD, funding which has already paid to fix
-	Chromium on BSD-i386.  I am using a new funding model where
-	subscriptions pay for development that is kept closed for at most 1
-	year, after which all patches used in a build are released to
-	subscribers under the same BSD license as Chromium.  Also, parts of
-	the closed patches are continually pushed upstream,
-	<a href="http://codereview.chromium.org/1543003" shape="rect">the BSD i386 fix has
-	already been committed upstream</a>.
-	The goal is to fund Chromium development on BSD while continually
-	pushing patches back to the BSD-licensed Chromium project.  I will
-	spin off a Chromium port for ports soon, for those who do not mind
-	using an older, stable build that does not have all the paid features
-	in the subscriber builds.  You can read about
-	<a href="http://chromium.jaggeri.com/issues" shape="rect">the issues that a
-	subscription would pay for, such as replacing the ALSA audio backend
-	with OSS</a>, and
-	<a href="http://chromium.jaggeri.com/subscriptions" shape="rect">find out more
-	about subscribing</a>.</p>
-    <hr /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html" title="http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html" title="">http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html</a></td></tr></table><p>
-	Contact: 
-	  Ed
-
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Roman
-
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Brooks
-
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Pawel
-
-	  Worach
-	 &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	</p>
-      <p>Since the last status report we got to the state where we are able
-	to build all of FreeBSD (the C and C++ bits) on i386/amd64 with clang.
-	The only exception is the bootloader which does not fit within the
-	given size constraint.  This is where the current efforts are going
-	on.  The C++ part got a big boost now being able to compile all C++
-	code in FreeBSD and itself.</p>
-
-      <p>We saw some movement on Mips and PowerPC.  Mips got its driver
-	definitions from Oleksander Tymoshenko and Nathan Whitehorn did the
-	same for PowerPC and tested the kernel.  Currently, the PPC kernel
-	seems to boot but due to lack of va_arg implementation for PowerPC
-	nothing is printed out.  Nathan is working on that.</p>
-
-      <p>Overall ClangBSD is selfhosting on i386/amd64 and some progress
-	has been made on PowerPC/PPC.  We also saw some contribution to the
-	Sparc64 but this seems to have stalled.</p>
-
-      <p>We need people to try out ClangBSD (see the wiki) and runtime test
-	it.  We also would appreciate help with other archs - namely ARM.</p>
-    <h3>Open tasks:</h3><ol><li>Runtime test ClangBSD on amd64/i386.</li><li>Help with ARM/Mips/Sparc64.</li><li>More testing of clang on 3rd party apps (ports).</li><li>Discussion on integrating LLVM/clang into FreeBSD.</li></ol><hr /><h2><a name="EFI-support-for-FreeBSD/i386" href="#EFI-support-for-FreeBSD/i386" id="EFI-support-for-FreeBSD/i386">EFI support for FreeBSD/i386</a></h2><p>
-	Contact: 
-	  Rui
-
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on supporting EFI booting on FreeBSD/i386 resumed.  The boot
-	loader can now read an ELF file from the EFI FAT partition.  We are
-	now working on trying to boot a kernel.</p>
-    <hr /><h2><a name="mfsBSD" href="#mfsBSD" id="mfsBSD">mfsBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mfsbsd.vx.sk" title="http://mfsbsd.vx.sk"></a></td><td>
-	    URL: <a href="http://mfsbsd.vx.sk" title="">http://mfsbsd.vx.sk</a></td></tr></table><p>
-	Contact: 
-	  Martin
-
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	</p>
-      <p>mfsBSD is a set of scripts that generate a bootable image (e.g. an
-	ISO file) that creates a working minimal installation of FreeBSD that is
-	completely loaded into memory (mfs).</p>
-
-      <p>The project has now reached a stable and well tested state. Images
-	can be created from 8.0-RELEASE or 7.3-RELEASE ISO image files or
-	from a custom makeworld.</p>
-
-      <p>A new feature is a script called "zfsinstall" that automates a
-	ZFS-only install of FreeBSD from a mfsbsd ISO (script works with
-	8-STABLE and 9-CURRENT, sample ISO images can be downloaded from the
-	project web site).</p>
-    <h3>Open tasks:</h3><ol><li>Bundle distribution installation files (target:
-	8.1-RELEASE).</li><li>Make zfsinstall 7.3 compatible (mostly gpart syntax).</li><li>Enable zfsinstall combination with sysinstall (zfsinstall
-	prepares drives, sysinstall installs distribution).</li><li>Integrate toolset into FreeBSD source (tools?).</li></ol><hr /><h2><a name="Modular-Congestion-Control" href="#Modular-Congestion-Control" id="Modular-Congestion-Control">Modular Congestion Control</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/" title="http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/"></a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/" title="">http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/</a></td></tr></table><p>
-	Contact: 
-	  Lawrence
-
-	  Stewart
-	 &lt;<a href="mailto:lstewart@FreeBSD.org">lstewart@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have just completed the last disruptive change to the KPI, which
-	laid the groundwork to allow different congestion aware transports to
-	share congestion control algorithms.  The import into the head branch
-	is a big job and my time is limited, so progress will be slow and I
-	will not have it done and ready to MFC by 8.1 as I had hoped.  I will
-	aim to have it in 8.2 though.</p>
-    <h3>Open tasks:</h3><ol><li>Solicit external testing.</li><li>Commit to head.</li></ol><hr /><h2><a name="NAND-Flash-framework-for-embedded-FreeBSD" href="#NAND-Flash-framework-for-embedded-FreeBSD" id="NAND-Flash-framework-for-embedded-FreeBSD">NAND Flash framework for embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153" title="http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153">Project wiki pages</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153" title="Project wiki pages">http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/..." title="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/...">Project P4 branch</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/..." title="Project P4 branch">http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/...</a></td></tr></table><p>
-	Contact: 
-	  Grzegorz
-
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact: 
-	  Rafal
-
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The purpose of this project is to provide embedded FreeBSD with a
-	generic and flexible scheme to support NAND Flash devices.  The
-	framework provides a set of KOBJ interfaces inside the kernel, which
-	allow for uniform and flexible management of the NAND devices:</p>
-
-      <ul>
-	<li>NAND Flash Controller (NFC) layer, into which back-end drivers
-	  for individual controllers plug in (implementing low-level routines
-	  specific to a given NAND controller)</li>
-
-	<li>Generic (common) NAND layer which provides means to perform
-	  operations on the flash devices in an abstract way (read, program,
-	  erase, get status etc.)</li>
-
-	<li>NAND character device, which exports chip device as a standard
-	  character device and allows to read/write directly to a device, as
-	  well as perform other specific operations by using ioctl.</li>
-
-	<li>GEOM NAND class for basic access through GEOM.</li>
-      </ul>
-
-      <p>Part of the infrastructure is a full system simulator of
-	ONFI-compliant devices (NANDsim), with a userland control application.
-	This allows for exercising of the framework on platforms without real
-	NAND chips.</p>
-
-      <p>Current state highlights:</p>
-
-      <ul>
-	<li>The framework is considered functionally complete (including
-	  NANDsim).</li>
-
-	<li>Framework compliant back-end drivers are available for the
-	  following NAND Flash controller (NFC) chips:</li>
-
-	<ul>
-	  <li>Freescale MPC8572 (PowerPC)</li>
-
-	  <li>Marvell MV-78100 (ARM)</li>
-
-	  <li>Samsung S3C24X0 (ARM)</li>
-	</ul>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Extend interface with features / options suggested by early
-	adopters of the code.</li><li>Complete, clean up, merge with HEAD.</li></ol><hr /><h2><a name="Out-of-Tree-Toolchain" href="#Out-of-Tree-Toolchain" id="Out-of-Tree-Toolchain">Out of Tree Toolchain</a></h2><p>
-	Contact: 
-	  Warner
-
-	  Losh
-	 &lt;<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt;
-	</p>
-      <p>Work is underway to allow the FreeBSD build system to use out of tree
-	compilers and binary utililies (loaders, linkers, etc), especially in
-	a cross compilation environment.  While it is possible to swap out the
-	compiler with a compatible compiler relatively easily, swapping out
-	the toolchain is more involved.  In addition, when using an external
-	compiler to build the system, certain parts of buildworld can be
-	omitted.</p>
-    <h3>Open tasks:</h3><ol><li>Create ports for latest binutils.  This work is nearly complete,
-	and is waiting for integration of two branches that are collapsing
-	soon (the 'tbemd' branch from Warner and the mips collapse from Juli
-	Mallet).</li><li>Create ports for gcc.  This work has been started.  Native builds
-	are straight forward, but cross builds have a buildworld dependency
-	at the moment.  These dependencies are being worked out, as well as
-	some gcc library dependencies.</li><li>Documentation needs to be written for how to use all of
-	this.</li></ol><hr /><h2><a name="PC-BSD-PC-SysInstall-Backend" href="#PC-BSD-PC-SysInstall-Backend" id="PC-BSD-PC-SysInstall-Backend">PC-BSD PC-SysInstall Backend</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pcbsd.org" title="http://www.pcbsd.org"></a></td><td>
-	    URL: <a href="http://www.pcbsd.org" title="">http://www.pcbsd.org</a></td></tr><tr><td><a href="http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall" title="http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall">pc-sysinstall in Trac</a></td><td>
-	    URL: <a href="http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall" title="pc-sysinstall in Trac">http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall</a></td></tr></table><p>
-	Contact: 
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are currently doing a lot of code cleanup in the new System
-	Installer backend for PC-BSD, pc-sysinstall, which can be used to
-	install regular FreeBSD as well.  Some new features have already been
-	implemented, such as:</p>
-
-      <ul>
-	<li>Improved ZFS support, raidz, mirroring, multiple mount-points
-	  per-pool, etc.</li>
-	<li>Support for GPT/EFI on "Full" installations, allowing us to go
-	  beyond the 2TB barrier.</li>
-	<li>MBR Slice/Partition manager.</li>
-	<li>geli passphrase support.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>We are mostly finished migrating to only using gpart instead of
-	fdisk, which gives us some new functionality for dealing with GPT/EFI
-	partitioning schemes.</li></ol><hr /><h2><a name="The-tbemd-branch" href="#The-tbemd-branch" id="The-tbemd-branch">The tbemd branch</a></h2><p>
-	Contact: 
-	  Warner
-
-	  Losh
-	 &lt;<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt;
-	</p>
-      <p>'tbemd' stands for Target Big Endian Must Die.  The current build
-	systems requires that one define TARGET_BIG_ENDIAN for either big
-	endian MIPS or big endian ARM processors.  There are many problems
-	with this approach.  The resulting system will not create the proper
-	binaries without TARGET_BIG_ENDIAN defined.  There is no easy way to
-	know what the endian is of the system you are running.  There are
-	many issues with ports, since they do not use bsd make, so do not
-	pick up the extra flags that are added if TARGET_BIG_ENDIAN is
-	defined.</p>
-
-      <p>The tbemd branch seeks to fix this.  We will move from
-	MACHINE_ARCH=mips for all mips platforms to MACHINE_ARCH=mipsel,
-	mipseb, mips64eb and mips64el to match NetBSD's conventions.  These
-	represent 32-bit mips little endian, 32-bit mips big endian, 64-bit
-	mips big endian and 64-bit mips little endian respectively.  ARM will
-	move to arm (little endian) and armeb (big endian), again following
-	the standards set elsewhere.  To facilitate a number of different
-	MACHINE_ARCHs all built from the same source, a new MACHINE_CPUARCH
-	is introduced and represents the sources needed to build CPU support
-	for a given MACHINE_ARCH.</p>
-
-      <p>In addition, MACHINE_ARCH is overused in the build system today.
-	Many of its uses are gratuitous and can be simplified.  Many of its
-	uses do not scale well and need to be refactored into a system that
-	will scale well.  A per MACHINE/MACHINE_ARCH/MACHINE_CPUARCH selection
-	mechanism for makefile snippets will be introduced to move much of
-	the current if spaghetti into more controlled lists.<br clear="none" />
-	The branch can build everything we currently support with the new
-	names.</p>
-    <h3>Open tasks:</h3><ol><li>Finish migrating to bsd.arch.inc.mk.</li><li>Reduce diffs between the branch and the mainline before the
-	collapse.</li><li>Documentation needs to be written for how to use all of
-	this.</li></ol><hr /><h2><a name="webcamd" href="#webcamd" id="webcamd">webcamd</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.selasky.org/hans_petter/video4bsd/" title="http://www.selasky.org/hans_petter/video4bsd/"></a></td><td>
-	    URL: <a href="http://www.selasky.org/hans_petter/video4bsd/" title="">http://www.selasky.org/hans_petter/video4bsd/</a></td></tr></table><p>
-	Contact: 
-	  Hans Petter
-
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p><B>Webcamd</B>
-	is a userland daemon that enables use of hundreds of different USB
-	based Linux device drivers under the FreeBSD-8/9 operating system.
-	Current focus has been on USB webcam and USB DVB-T/S/C devices.
-	It is also possible to use the webcamd framework to make other Linux
-	kernel USB devices work under the FreeBSD-8/9 operating system, without
-	violating the GPL license.  The daemon currently depends on libc,
-	pthreads, libusb and libcuse4bsd.  Cuse4BSD is a new character device
-	from userland implementation that fully supports open, read, write,
-	ioctl, mmap and close file operations.</p>
-
-      <p>If you like this project or want me to spend more time on it, you
-	can support it by transferring money to hselasky@c2i.net via
-	paypal.</p>
-    <h3>Open tasks:</h3><ol><li>Testing and bugfixes.</li><li>Add support for more device drivers.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats">GNATS</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="GNATS">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting">BugBusting</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="BugBusting">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/">experimental report pages</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="experimental report pages">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html">PRs recommended for committer evaluation by the bugbusting team</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="PRs recommended for committer evaluation by the bugbusting team">http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt">(subscription list for the above report)</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="(subscription list for the above report)">http://people.FreeBSD.org/~linimon/recommended_subscribers.txt</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html">PRs considered 'easy' by the bugbusting team (these are low-hanging fruit)</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html" title="PRs considered 'easy' by the bugbusting team (these are low-hanging fruit)">http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html" title="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html">summary chart of PRs with tags</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html" title="summary chart of PRs with tags">http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/AssigningPRs" title="http://wiki.FreeBSD.org/AssigningPRs">Assigning PRs</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/AssigningPRs" title="Assigning PRs">http://wiki.FreeBSD.org/AssigningPRs</a></td></tr></table><p>
-	Contact: 
-	  Gavin
-
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Mark
-
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Remko
-
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Volker
-
-	  Werth
-	 &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
-	</p>
-      <p>Bruce Cran (brucec) has graduated from GNATS-only access to having
-	a src commit bit.  He has been making commits to help us catch up with
-	the PR backlog.  Thanks!</p>
-
-      <p>We continue to classify PRs as they arrive, adding 'tags' to the
-	subject lines corresponding to the kernel subsystem involved, or man
-	page references for userland PRs.  These tags, in turn, produce lists
-	of PRs sorted both by tag and by manpage.  The most recent use of
-	these tags is the creating of a new report, Summary Chart of PRs With
-	Tags, which sorts tagged PRs into logical groups such as filesystem,
-	network drivers, libraries, and so forth.  The slice labels are
-	clickable.  The chart is updated once a day.  You can consider it as a
-	prototype for browsing "sub-categories" of kernel PRs.</p>
-
-      <p>The "recommended list" has been split up into "non-trivial PRs
-	which need committer evaluation" and the "easy list" of trivial PRs,
-	to try to focus some attention on the latter.</p>
-
-      <p>New reports were added for "PRs which are from FreeBSD vendors or
-	OEMs", "PRs containing code for new device drivers", and "PRs
-	referencing other BSDs".  These will primarily be of interest to
-	committers.</p>
-
-      <p>Some other bitrot on the "experimental PR reports" pages has been
-	fixed.</p>
-
-      <p>It is now possible for interested parties to be emailed a weekly,
-	customized, report along the lines of the above.  If you are
-	interested in setting one up, contact <a href="mailto:linimon@FreeBSD.org" shape="rect">linimon@FreeBSD.org</a>.</p>
-
-      <p>The overall PR count has recently jumped to around 6400.  This may
-	be due to increasing uptake of FreeBSD 8.</p>
-
-      <p>Our clearance rate of PRs, especially in kern and bin, seems to be
-	improving.</p>
-
-      <p>Mark Linimon polled various committers about their interest in
-	specific PRs. As a result, the AssigningPRs page on the wiki and the
-	src/MAINTAINERS file were updated based on feedback.</p>
-
-      <p>As always, anybody interested in helping out with the PR queue is
-	welcome to join us in #freebsd-bugbusters on EFnet.  We are always
-	looking for additional help, whether your interests lie in triaging
-	incoming PRs, generating patches to resolve existing problems, or
-	simply helping with the database housekeeping (identifying duplicate
-	PRs, ones that have already been resolved, etc).  This is a great way
-	of getting more involved with FreeBSD!</p>
-    <h3>Open tasks:</h3><ol><li>We will be having a bugbusting session at BSDCan.  If you are
-	developer who will be attending the conference, please stop
-	by.</li><li>try to find ways to get more committers helping us with closing
-	PRs that the team has already analyzed.</li></ol><hr /><h2><a name="Release-Engineering-Team" href="#Release-Engineering-Team" id="Release-Engineering-Team">Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact: 
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team announced FreeBSD-7.3 on March 23rd,
-	2010.  The schedule has been set for FreeBSD-8.1 with the release date
-	planned for mid July 2010.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org" title="http://www.FreeBSDFoundation.org"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org" title="">http://www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact: 
-	  Deb
-
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We were proud to be a sponsor for AsiaBSDCon in March.  We also
-	committed to sponsoring BSDCan 2010 and NYCBSDCon 2010.  We provided
-	travel grants for AsiaBSDCon.</p>
-
-      <p>We funded a project by Murray Stokely to provide Closed Captioning
-	of FreeBSD Technical Videos in the BSD Conferences YouTube Channel.  We
-	were very pleased that the foundation funded HAST project
-	completed.</p>
-
-      <p>We solicited project proposals and were very pleased with the
-	number of proposals we received.  With our project spending budget
-	increase, we will be able to fund more projects this year.</p>
-
-      <p>We grew our board of directors by adding Erwin Lansing.  This will
-	expand our representation in Europe.  Erwin brings ports knowledge and
-	expertise to the board.</p>
-
-      <p>We continued our work on infrastructure projects to beef up
-	hardware for package-building, network-testing, etc.</p>
-
-      <p>Follow us on
-	<a href="https://twitter.com/freebsdfndation" shape="rect">Twitter</a>
-
-      now!</p>
-
-      <p>We are fund-raising for 2010 now! Find out more at
-	<a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">
-	    http://www.FreeBSDFoundation.org/donate/</a>.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="(Virtual)-Network-Stack-resource-cleanup" href="#(Virtual)-Network-Stack-resource-cleanup" id="(Virtual)-Network-Stack-resource-cleanup">(Virtual) Network Stack resource cleanup</a></h2><p>
-	Contact: 
-	  Bjoern A.
-
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>In February work was done to address resource leaks in the
-	(virtual) network stack, especially on teardown.</p>
-
-      <p>During that time also multiple general run-time problems and leaks
-	were identified and fixed including leaked ipfw tables on module
-	unload, routing entries leaked, in case of interfaces going away, as
-	well as leaked link-layer entries in interaction with flowtable and
-	timers.</p>
-
-      <p>For virtual network stacks resources are are no longer allocated
-	multiple times or freed upon teardown for eventhandlers, IP and upper
-	level layers, like TCP syncache and host cache, flowtable, and
-	especially radix/routing table memory.<br clear="none" />
-	In addition epair(4) was enhanced and debugging was improved.</p>
-
-      <p>This work was sponsored by ISPsystem.</p>
-    <h3>Open tasks:</h3><ol><li>Merge the remaining patches.</li><li>Work on a better teardown model and get to the point where we
-	can free UMA zones without keeping pages for type stability and
-	timers around.</li></ol><hr /><h2><a name="802.11n-support" href="#802.11n-support" id="802.11n-support">802.11n support</a></h2><p>
-	Contact: 
-	  Rui
-
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>802.11n support in the Atheros driver is being worked on.  Right
-	now it can do AMPDU RX in software and we are working on TX AMPDU.
-	The code lives in a private Perforce branch, but some bits of it are
-	already committed to HEAD.</p>
-
-      <p>This work is being sponsored by iXsystems, inc.</p>
-    <hr /><h2><a name="Atheros-AR9285-support" href="#Atheros-AR9285-support" id="Atheros-AR9285-support">Atheros AR9285 support</a></h2><p>
-	Contact: 
-	  Rui
-
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Atheros AR9285 support was added to FreeBSD HEAD and 8-STABLE.  There
-	are still some issues but in general it works fine.</p>
-    <hr /><h2><a name="Enhancing-the-FreeBSD-TCP-Implementation" href="#Enhancing-the-FreeBSD-TCP-Implementation" id="Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/etcp09/" title="http://caia.swin.edu.au/freebsd/etcp09/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/etcp09/" title="">http://caia.swin.edu.au/freebsd/etcp09/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/projects.shtml" title="http://www.FreeBSDFoundation.org/projects.shtml"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/projects.shtml" title="">http://www.FreeBSDFoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="">http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/</a></td></tr></table><p>
-	Contact: 
-	  Lawrence
-
-	  Stewart
-	 &lt;<a href="mailto:lstewart@FreeBSD.org">lstewart@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ALQ(9) implementation and KPI has been rototilled and modified
-	(one more patch needs to be committed) to support variable length
-	messages.  In addition, it can now be compiled and loaded as a kernel
-	module.</p>
-
-      <p>With the ALQ changes in head, SIFTR can finally be imported.</p>
-
-      <p>Reassembly queue autotuning is in the project branch and needs to
-	be extracted as a patch people can easily test.</p>
-    <h3>Open tasks:</h3><ol><li>Solicit external testing for and commit SIFTR.</li><li>Solicit external testing for and commit reassembly queue
-	autotuning patch.</li></ol><hr /><h2><a name="Experimental-NFS-subsystem-(NFSv4)" href="#Experimental-NFS-subsystem-(NFSv4)" id="Experimental-NFS-subsystem-(NFSv4)">Experimental NFS subsystem (NFSv4)</a></h2><p>
-	Contact: 
-	  Rick
-
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@uoguelph.ca">rmacklem@uoguelph.ca</a>&gt;
-	</p>
-      <p>Although the bare bones of the NFS Version 4 support was released
-	in FreeBSD 8.0, the integration has been progressing slowly and support
-	should be functional for FreeBSD 8.1 for RFC3530 (NFS Version 4.0).</p>
-
-      <p>Post FreeBSD 8.1, I believe the focus will be on code cleanup and,
-	under a projects area of svn, some experimental work on aggressive
-	whole file caching to client disk.</p>
-    <h3>Open tasks:</h3><ol><li>Handling of delegations on the server w.r.t. local processes
-	running on the server.</li><li>Integration of recent changes to the regular NFS client, such
-	as Dtrace support.</li></ol><hr /><h2><a name="ipfw-and-dummynet-enhancements" href="#ipfw-and-dummynet-enhancements" id="ipfw-and-dummynet-enhancements">ipfw and dummynet enhancements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/dummynet/" title="http://info.iet.unipi.it/~luigi/dummynet/">main dummynet page</a></td><td>
-	    URL: <a href="http://info.iet.unipi.it/~luigi/dummynet/" title="main dummynet page">http://info.iet.unipi.it/~luigi/dummynet/</a></td></tr><tr><td><a href="http://www.youtube.com/watch?v=r8vBmybeKlE" title="http://www.youtube.com/watch?v=r8vBmybeKlE">youtube video on dummynet internals</a></td><td>
-	    URL: <a href="http://www.youtube.com/watch?v=r8vBmybeKlE" title="youtube video on dummynet internals">http://www.youtube.com/watch?v=r8vBmybeKlE</a></td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/qfq/" title="http://info.iet.unipi.it/~luigi/qfq/">Description of the qfq scheduler</a></td><td>
-	    URL: <a href="http://info.iet.unipi.it/~luigi/qfq/" title="Description of the qfq scheduler">http://info.iet.unipi.it/~luigi/qfq/</a></td></tr></table><p>
-	Contact: 
-	  Luigi
-
-	  Rizzo
-	 &lt;<a href="mailto:luigi@FreeBSD.org">luigi@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have recently completed a massive revision of ipfw and
-	dummynet, and the result has been committed to HEAD and stable/8.
-	The main features introduced with this work are:</p>
-
-      <ul>
-	<li>ipfw now has much faster skipto instructions, including
-	  table-based ones.  The complexity for rule lookups is now O(1) or
-	  O(log N) as opposed to the O(N) that we had before.  People using
-	  "skipto tablearg" or "pipe tablearg" with large numbers of rules or
-	  pipes should see a significant performance improvement;</li>
-
-	<li>Expensive operations in response to userland reconfigurations
-	  now do not interfere with kernel filtering for more than the time
-	  required to swap a pointer;</li>
-
-	<li>You can now use ports and the "tos" field as lookup argument
-	  for tables.  This might allow some simplifications in rulesets which
-	  in turn result in faster execution time;</li>
-
-	<li>ipfw can now send packets matching rules with a 'log' attribute
-	  to the "ipfw0" pseudo interface, where you can run tcpdump to
-	  implement additional filtering, logging etc.;</li>
-
-	<li>dummynet now supports many different scheduler types, to adapt
-	  to different needs people may have in terms of performance and
-	  service guarantees.  Existing schedulers now include FIFO, WF2Q+,
-	  Deficit Round Robin, Priority, and QFQ.  More schedulers can be
-	  implemented as loadable kernel modules.;</li>
-
-	<li>The kernel side has a backward-compatible interface so you can
-	  use a RELENG_7 or RELENG_8 version of /sbin/ipfw to configure the
-	  firewall and dummynet.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>There is ongoing work on optimizing the deletion of idle
-	entries in dummynet.  This should be completed shortly.</li><li>A longer term goal is to parallelize operation in presence of
-	ipfw dynamic rules, which currently require exclusive lock on a hash
-	table containing dynamic rules.</li></ol><hr /><h2><a name="net80211-rate-control-framework" href="#net80211-rate-control-framework" id="net80211-rate-control-framework">net80211 rate control framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~rpaulo/ratectl.diff" title="http://people.FreeBSD.org/~rpaulo/ratectl.diff"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~rpaulo/ratectl.diff" title="">http://people.FreeBSD.org/~rpaulo/ratectl.diff</a></td></tr></table><p>
-	Contact: 
-	  Rui
-
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The net80211 (wireless) stack will support a modular rate control
-	framework soon.  The idea is to reduce some code in the drivers and
-	add more rate control algorithms in the tree.  All drivers that do
-	rate control in software will automatically benefit from this
-	project.  On this stage, we are working on changing all the necessary
-	drivers to cope with the new framework and making sure it all works
-	as expected.  Later this year we will bring the necessary changes to
-	change the rate control algorithm with ifconfig(1).</p>
-
-      <p>If you are doing rate control algorithm or research on rate
-	control algorithms for wireless networks, FreeBSD is now an ideal
-	candidate for testing your project!</p>
-    <hr /><h2><a name="TCP/UDP-connection-groups" href="#TCP/UDP-connection-groups" id="TCP/UDP-connection-groups">TCP/UDP connection groups</a></h2><p>
-	Contact: 
-	   Robert
-	   Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	   FreeBSD network mailing list
-	 &lt;<a href="mailto:freebsd-net@FreeBSD.org">freebsd-net@FreeBSD.org</a>&gt;
-	</p>
-      <p>This on-going project is to reduce tcbinfo/udbinfo lock and cache
-	line contention; this global lock protects access to connection lists,
-	and while it is a read-write lock, it is acquired for every in-bound
-	packet (briefly) to look up the connection.  This project adds a new
-	connection group table, which assigns connections to groups, each of
-	which has CPU affinity and aligns with RSS-selected queues in high-end
-	1gbps and most 10gbps implementations. The following tasks have been
-	completed:</p>
-
-      <ul>
-	<li>Teach libkvm to handle dynamic per-cpu storage (DPCPU) to improve
-	  crashdump analysis of per-CPU data.</li>
-	<li>Teach netstat to monitor netisr DPCPU queues for live kernels and
-	  crashdumps.</li>
-	<li>Create a new inpcbgroup abstraction, used for UDP and TCP.</li>
-	<li>Distribute UDP and TCP connections (inpcbs) over groups based on
-	  4-tuple bindings.</li>
-	<li>Replicate membership across all groups for wildcard socket
-	  bindings.</li>
-	<li>Write new TCP/UDP connection and binding regression tests.</li>
-      </ul>
-
-      <p>The following tasks remain:</p>
-
-      <ul>
-	<li>Migrate from naive work assignment algorithm to RSS
-	  assignment.</li>
-	<li>Modify device driver KPI to allow consistent initialization and
-	  configuration between stack and hardware.</li>
-	<li>Complete migration to dynamic, per-CPU network statistics in TCP,
-	  UDP, and IP.</li>
-	<li>Add socket options to query effective CPU affinity of connections
-	  from userspace.</li>
-	<li>On supporting hardware, allow affinity for a specific connection
-	  to be explicitly migrated using a socket option.</li>
-	<li>Detailed performance evaluation and optimization.</li>
-      </ul>
-
-      <p>This work is being performed in the FreeBSD Perforce repository, and
-	is sponsored by Juniper Networks.  Connection groups and related
-	features are slated for inclusion in FreeBSD 9.0 (with possible
-	backports to 8-STABLE of some features).</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="CAM-based-ATA-implementation" href="#CAM-based-ATA-implementation" id="CAM-based-ATA-implementation">CAM-based ATA implementation</a></h2><p>
-	Contact: 
-	  Alexander
-
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on CAM-based ATA implementation continues.  Since last report
-	handling of heavy errors and timeouts was improved, Hot-plug now
-	works for both Host and Port Multiplier ports.  Series of changes were
-	made to CAM to fix some old issues and honor some new ATA
-	demands.</p>
-
-      <p>New drivers ahci(4) and siis(4) got some fixes and are quite
-	stable now.  "options ATA_CAM" kernel option shows good results in
-	supporting other controllers using existing ata(4) drivers, so it is
-	possible to start deprecating old ata(4) APIs now.</p>
-
-      <p>Started work on new Marvell SATA driver for both PCI-X/PCIe cards
-	and ARM System-on-Chip SATA controllers.  It is expected to support
-	NCQ, Port Multipliers with FIS-based switching and other new
-	features.</p>
-
-      <p>Most of the code is present in 8-STABLE.</p>
-    <h3>Open tasks:</h3><ol><li>Port ataraid(4) functionality to GEOM module.</li><li>Write SAS-specific transport and drivers for SAS HBAs (specs
-	wanted).  SAS controllers can support SATA devices and multipliers, so
-	it should fit nicely into new infrastructure.</li></ol><hr /><h2><a name="Dynamic-Ticks-in-FreeBSD" href="#Dynamic-Ticks-in-FreeBSD" id="Dynamic-Ticks-in-FreeBSD">Dynamic Ticks in FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://github.com/oza/FreeBSD-8.0-dyntick" title="http://github.com/oza/FreeBSD-8.0-dyntick">Project page (github).</a></td><td>
-	    URL: <a href="http://github.com/oza/FreeBSD-8.0-dyntick" title="Project page (github).">http://github.com/oza/FreeBSD-8.0-dyntick</a></td></tr><tr><td><a href="http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html" title="http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html">My weblog article which describes benchmark of dynamic ticks.</a></td><td>
-	    URL: <a href="http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html" title="My weblog article which describes benchmark of dynamic ticks.">http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html</a></td></tr></table><p>
-	Contact: 
-	  Tsuyoshi
-
-	  Ozawa
-	 &lt;<a href="mailto:ozawa@t-oza.net">ozawa@t-oza.net</a>&gt;
-	</p>
-      <p>I wrote experimental code (please see my project page) and threw
-	patch ( http://gist.github.com/350230 ) to freebsd-hackers.  A lot of
-	FreeBSD hackers gave me precious advice, so I am going to reflect it as
-	a next step.</p>
-    <h3>Open tasks:</h3><ol><li>Run hard/stat/prof-clocks irregularly (in progress).</li><li>Some timers which are added after the kernel's scheduling next
-	timer interrupt may be ignored (BUG).</li><li>Make callout queue have the tick when the next timer event rise
-	up.</li></ol><hr /><h2><a name="geom_sched" href="#geom_sched" id="geom_sched">geom_sched</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/geom_sched/" title="http://info.iet.unipi.it/~luigi/geom_sched/"></a></td><td>
-	    URL: <a href="http://info.iet.unipi.it/~luigi/geom_sched/" title="">http://info.iet.unipi.it/~luigi/geom_sched/</a></td></tr></table><p>
-	Contact: 
-	  Luigi
-
-	  Rizzo
-	 &lt;<a href="mailto:luigi@FreeBSD.org">luigi@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Fabio
-
-	  Checconi
-	 &lt;<a href="mailto:fabio@FreeBSD.org">fabio@FreeBSD.org</a>&gt;
-	</p>
-      <p><b>geom_sched</b> is a GEOM module that supports pluggable schedulers
-	for disk I/O requests.  The main algorithm supported at the moment is
-	an anticipatory Round Robin scheduler, which is especially effective
-	in presence of workloads with highly random disk accesses.  Other
-	schedulers are available on the <a href="http://info.iet.unipi.it/~luigi/geom_sched/" shape="rect">geom_sched</a>
-	page.</p>
-
-      <p>Developed in early 2009 and refined as a GSOC2009 project,
-	geom_sched has been recently introduced in HEAD and is going to be
-	soon merged to stable/8.  A version for stable/7 also exists, with
-	some restrictions.</p>
-
-      <p>To use the module, say on disk <b>ad4</b>, all you need to do
-	is:</p>
-
-<pre xml:space="preserve">
-kldload geom_sched
-geom sched insert ad4
-</pre>
-
-      <p>A number of sysctl variables under kern.geom.sched allow you to
-	tune the parameters of the algorithm, or bypass the scheduler
-	entirely so you can tell the difference of behaviour with and without
-	the scheduler.</p>
-    <hr /><h2><a name="IPv6-without-legacy-IP-kernel" href="#IPv6-without-legacy-IP-kernel" id="IPv6-without-legacy-IP-kernel">IPv6 without legacy IP kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=MNx@//depot/user/bz/noinet/src/sys/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=MNx@//depot/user/bz/noinet/src/sys/?ac=83">P4 workspace</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=MNx@//depot/user/bz/noinet/src/sys/?ac=83" title="P4 workspace">http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=MNx@//depot/user/bz/noinet/src/sys/?ac=83</a></td></tr></table><p>
-	Contact: 
-	  Bjoern A.
-
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>During 2009 work was done that allowed us to build a FreeBSD kernel
-	without INET and without INET6 (again).  This work was the foundation
-	for a prototype to get a kernel to compile and boot with only INET6
-	but no INET compiled in earlier this year.</p>
-
-      <p>The current focus is to identify general
-	architectural problems and dependencies we do have between these two
-	address families as well as with the upper layer protocols.  This will
-	at some point allow us to discuss the issues and seek solutions,
-	preparing for a future where we can remove either INET or INET6 from
-	the system.</p>
-
-      <p>Once we will have a stable, in-tree way to compile out either
-	address family, optimizations wrt. size, as well as user space
-	will need to be worked on.  In addition to this, the work is believed
-	to help should we further head in the direction of network stack
-	modularization.</p>
-    <hr /><h2><a name="Multichannel-playback-in-HDA-sound-driver-(snd_hda)" href="#Multichannel-playback-in-HDA-sound-driver-(snd_hda)" id="Multichannel-playback-in-HDA-sound-driver-(snd_hda)">Multichannel playback in HDA sound driver (snd_hda)</a></h2><p>
-	Contact: 
-	  Alexander
-
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>snd_hda(4) audio driver got real multichannel playback support.  It
-	now supports 4.0 (quadro), 5.1 and 7.1 analog speaker setups.  Digital
-	multichannel AC3/DTS passthrough was already implemented earlier.
-	Digital multichannel LPCM output via HDMI could also be possible now,
-	but is not tested.</p>
-
-      <p>To use multichannel playback you should have fresh 8-STABLE
-	kernel, instruct sound(4) vchans subsystem (if you are using it)
-	about your speaker setup using dev.pcm.X.play.vchanformat sysctls and
-	use your audio/video player application to play multichannel audio
-	content without down-mixing it to stereo.</p>
-    <h3>Open tasks:</h3><ol><li>HDMI/DisplayPort often require some audio support from X11
-	video drivers.  This area still should be investigated and tested,
-	especially relayed to multichannel LPCM playback.</li></ol><hr /><h2><a name="Rewrite-of-FreeBSD-read/write-path-using-vnode-page" href="#Rewrite-of-FreeBSD-read/write-path-using-vnode-page" id="Rewrite-of-FreeBSD-read/write-path-using-vnode-page">Rewrite of FreeBSD read/write path using vnode page</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.freebsd.org/viewvc/base/user/kib/vm6/" title="http://svn.freebsd.org/viewvc/base/user/kib/vm6/">Branch for the rewrite</a></td><td>
-	    URL: <a href="http://svn.freebsd.org/viewvc/base/user/kib/vm6/" title="Branch for the rewrite">http://svn.freebsd.org/viewvc/base/user/kib/vm6/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/VM6" title="http://wiki.FreeBSD.org/VM6"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/VM6" title="">http://wiki.FreeBSD.org/VM6</a></td></tr></table><p>
-	Contact: 
-	  Konstantin
-
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Peter
-
-	  Holm
-	 &lt;<a href="mailto:pho@FreeBSD.org">pho@FreeBSD.org</a>&gt;
-	</p>
-      <p>Based on the idea of Jeff Roberson, we reimplemented the path for
-	read(2)/write(2) syscalls using page cache (in wide sense) to
-	eliminate the issues with recursive vnode and buffer lock
-	acquisitions.  The usual reads and writes are no longer calls into
-	VOP_READ/VOP_WRITE; the operation is done by copying user buffers to
-	or from the pages of the vnode.  This fixes known deadlocks when reads
-	or writes are done over file-mmaped buffers.</p>
-
-      <p>The patch changes the performance characteristics of I/O, and we
-	observed both better and worse behaviour.  If filesystem implements
-	VOP_GETPAGES and VOP_PUTPAGES without referencing buffer cache,
-	buffers are completely eliminated from the i/o path (not true for UFS
-	or NFS).</p>
-    <h3>Open tasks:</h3><ol><li>We need wider testing and reviews.</li></ol><hr /><h2><a name="SUJ:-Journaled-Softupdates" href="#SUJ:-Journaled-Softupdates" id="SUJ:-Journaled-Softupdates">SUJ: Journaled Softupdates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeffr_tech.livejournal.com/" title="http://jeffr_tech.livejournal.com/"></a></td><td>
-	    URL: <a href="http://jeffr_tech.livejournal.com/" title="">http://jeffr_tech.livejournal.com/</a></td></tr></table><p>
-	Contact: 
-	  Jeff
-	  Roberson
-	 &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	</p>
-      <p>The soft-updates journaling project is nearing completion and will
-	be available in head by the time this status report is released.
-	Backports to other releases are maintained in <a href="svn://svn.FreeBSD.org/base/projects/suj" shape="rect">SVN</a>.  SUJ is
-	fully backwards compatible with non-journaled softupdates.  Existing
-	systems will not be affected.  Journaling may be enabled and disabled
-	by tunefs on unmounted filesystems.  Journaling provides near-instant
-	filesystem recovery after crash at the expense of some runtime
-	performance and extra disk I/O.</p>
-    <hr /><h2><a name="ZFS" href="#ZFS" id="ZFS">ZFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs">Perforce tree for latest ZFSv25 work</a></td><td>
-	    URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="Perforce tree for latest ZFSv25 work">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs</a></td></tr><tr><td><a href="http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome" title="http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome">OpenSolaris ZFS homepage</a></td><td>
-	    URL: <a href="http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome" title="OpenSolaris ZFS homepage">http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome</a></td></tr></table><p>
-	Contact: 
-	  Pawel Jakub
-
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Martin
-
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Xin
-
-	  LI
-	 &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ZFS file system has been updated to version 14 on both -HEAD
-	and 8-STABLE.  Ongoing work is undergoing to bring bug fixes and
-	performance improvements from upstream svn -HEAD to approximately ZFS
-	v15 in the near future, and a full upgrade of ZFS to version 24
-	including the de-duplication functionality, etc.  The de-duplication
-	functionality is currently partly supported, which is demonstrated
-	below:</p>
-
-<pre xml:space="preserve">
-# uname -sr
-FreeBSD 9.0-CURRENT
-# zpool create tank ad{4,6,8,10}
-# zpool get version tank
-NAME  PROPERTY  VALUE    SOURCE
-tank  version   24       default
-# zfs set dedup=on tank
-# dd if=/dev/random of=/tank/rand0 bs=1m count=1024
-# zpool get allocated,dedupratio tank
-NAME  PROPERTY    VALUE  SOURCE
-tank  allocated   1.00G  -
-tank  dedupratio  1.00x  -
-# dd if=/tank/rand0 of=/tank/rand1 bs=1m
-# dd if=/tank/rand0 of=/tank/rand2 bs=1m
-# dd if=/tank/rand0 of=/tank/rand3 bs=1m
-# zpool get allocated,dedupratio tank
-NAME  PROPERTY    VALUE  SOURCE
-tank  allocated   1.01G  -
-tank  dedupratio  4.00x  -
-</pre>
-    <h3>Open tasks:</h3><ol><li>Bring ZFS v15 changes to svn -HEAD and MFC.</li><li>Further polish the code in perforce and test for functionality,
-	etc.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de"></a></td><td>
-	    URL: <a href="http://doc.bsdgroup.de" title="">http://doc.bsdgroup.de</a></td></tr></table><p>
-	Contact: 
-	  Johann
-
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Benedict
-
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>Our last status report listed a number of documents that needed
-	help.  Thanks to the external contributions of Frank Boerner we were
-	able to update a substantial amount of documents.  This has resulted
-	in a great reduction of our backlog.  Subsequently, Benedict has
-	agreed to take Frank under mentorship for the German doc project.  We
-	are looking forward to his future contributions and thank him for his
-	past efforts.</p>
-
-      <p>Johann was busy keeping the German website in sync with updates to
-	FreeBSD.org.  However, there are still parts of the website that
-	remain untranslated.  We are looking for more support in maintaining
-	the German website.</p>
-
-      <p>FreeBSD users with German language skills are always welcome to join
-	our efforts in translating the documentation and/or fixing bugs.</p>
-    <h3>Open tasks:</h3><ol><li>Translate more parts of the documentation and the German
-	website.</li><li>Keep the current documentation up to date.</li><li>Report bugs to <a href="mailto:de-bsd-translators@de.FreeBSD.org" shape="rect">
-	  de-bsd-translators@de.FreeBSD.org</a>.</li></ol><hr /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu/" title="http://www.FreeBSD.org/hu/">Hungarian FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu/" title="Hungarian FreeBSD Web Pages">http://www.FreeBSD.org/hu/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu/" title="http://www.FreeBSD.org/doc/hu/">Hungarian FreeBSD Documentation</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu/" title="Hungarian FreeBSD Documentation">http://www.FreeBSD.org/doc/hu/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Web Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Web Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">The FreeBSD Hungarian Documentation Project's Perforce Repository</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="The FreeBSD Hungarian Documentation Project's Perforce Repository">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact: 
-	  G�bor
-
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  G�bor
-
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We restlessly keep the existing documentation and web page
-	translations up to date.  However, this will not last forever, and
-	help is always welcome, so if you feel yourself Hungarian with some
-	interests in translation, please contact our Documentation Project
-	via the email addresses noted above.</p>
-    <h3>Open tasks:</h3><ol><li>Translate release notes.</li><li>Translate articles.</li><li>Translate web pages.</li><li>Read translations, send feedback.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="FreeBSD-port-for-libunwind" href="#FreeBSD-port-for-libunwind" id="FreeBSD-port-for-libunwind">FreeBSD port for libunwind</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nongnu.org/libunwind/" title="http://www.nongnu.org/libunwind/"></a></td><td>
-	    URL: <a href="http://www.nongnu.org/libunwind/" title="">http://www.nongnu.org/libunwind/</a></td></tr></table><p>
-	Contact: 
-	  Konstantin
-
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The alpha version of libunwind library port for FreeBSD x86 and
-	x86_64 is completed and imported into the official libunwind git
-	repository.  Libunwind is the library to perform dynamic unwinding of
-	stacks, using dwarf call frame information.  The library features
-	remote unwinding using ptrace(2), very fast setjmp(3) implementation
-	and more interesting features.</p>
-    <hr /><h2><a name="LDAP-support-in-base-system" href="#LDAP-support-in-base-system" id="LDAP-support-in-base-system">LDAP support in base system</a></h2><p>
-	Contact: 
-	  Xin
-
-	  ZHAO
-	 &lt;<a href="mailto:quakelee@geekcn.org">quakelee@geekcn.org</a>&gt;
-	<br />
-	Contact: 
-	  Xin
-
-	  LI
-	 &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD is currently lacking support of LDAP based authentication and
-	user identity.</p>
-
-      <p>We have integrated a stripped down
-	<a href="http://www.openldap.org/" shape="rect">OpenLDAP</a>
-	library (renamed to avoid conflict with ports OpenLDAP libraries), as
-	well as some changes to OpenSSH as well as plugins for PAM, NSS and
-	can support.</p>
-
-      <p>We have used several existing works and updated them to use new
-	OpenLDAP API, fixed several bugs and integrated them together.  All
-	these works are under BSD or similar license and our new work would be
-	under 2-clause BSD license.  Currently, we support storing user
-	identity, password and SSH public keys in LDAP tree.</p>
-    <h3>Open tasks:</h3><ol><li>Further code review.</li><li>Make the changes less intrusive.</li><li>Fix issues found in production deployment.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm-port-for-TI-DaVinci" href="#FreeBSD/arm-port-for-TI-DaVinci" id="FreeBSD/arm-port-for-TI-DaVinci">FreeBSD/arm port for TI DaVinci</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&amp;familyId=1300&amp;tabId=1854" title="http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&amp;familyId=1300&amp;tabId=1854">DaVinci on TI's site</a></td><td>
-	    URL: <a href="http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&amp;familyId=1300&amp;tabId=1854" title="DaVinci on TI's site">http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&amp;familyId=1300&amp;tabId=1854</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/jceel/davinci/" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/jceel/davinci/">Project branch in P4</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/jceel/davinci/" title="Project branch in P4">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/user/jceel/davinci/</a></td></tr></table><p>
-	Contact: 
-	  Jakub
-
-	  Klama
-	 &lt;<a href="mailto:jceel@semihalf.com">jceel@semihalf.com</a>&gt;
-	</p>
-      <p>DaVinci (TMS320DM644x) is an ARM9-based system-on-chip family from
-	Texas Instruments with built-in DSP core and powerful
-	multimedia/video features.  This work is bringing support for FreeBSD on
-	these systems - it works in multiuser mode, using root filesystem
-	mounted either via NFS or from SD/MMC card.  The code is available in
-	P4 at //depot/user/jceel/davinci/.</p>
-
-      <p>Current DaVinci support includes:</p>
-
-      <ul>
-	<li>Booting from U-Boot bootloader</li>
-
-	<li>Serial console</li>
-
-	<li>Interrupt controller</li>
-
-	<li>Integrated timers</li>
-
-	<li>Power and sleep controller</li>
-
-	<li>10/100 Ethernet controller</li>
-
-	<li>SD/MMC controller</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Remaining built-in peripherals drivers (USB, ATA, NAND flash,
-	I2C, DMA engine, sound, video input/output).</li><li>Framework for communicating with DSP core.</li></ol><hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><p>
-	Contact: 
-	  Mark
-
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The stability of the machines under package build has been
-	improved by a number of recent commits.  Some rework is underway to
-	run with WITNESS.  However, we are still limited in the number of
-	simultaneous packages that can be built.</p>
-
-      <p>Based on this, we have completed the first full ia64-8 package
-	build.  17187 were built (as compared to 19885 on a recent i386-8.)
-	Mark Linimon has gone through the results to denote which packages do
-	not build.  A few fixes have already been committed based on this.</p>
-
-      <p>We currently have 3 available machines that are stable enough for
-	package builds.</p>
-
-      <p>Support for the SGI Altix 350 has made its start.  Porting is done
-	on 2 SGI Altix 350 machines connected with NUMAFlex, giving a total
-	of 4 CPUs and 24GB of DDR.  The kernel boots with code on the
-	projects/altix branch but since ACPI does not enumerate PCI busses,
-	no hardware devices are found.  SMP has been disabled because waking
-	up the APs result in a machine check.</p>
-    <h3>Open tasks:</h3><ol><li>Continue to try to understand why multiple simultaneous package
-	builds bring the machines down.</li><li>Upgrade the firmware on the two machines at Yahoo! to see if
-	that helps the problem.</li><li>Figure out why the fourth machine is not stable.</li><li>Configure a fifth machine that has been made available to
-	us.</li><li>Figure out the problems with the latest gcc port.</li><li>We need documentation about the SGI SAL implementation to speed
-	up porting to the SGI Altix 350.</li><li>The loader and kernel need to change to allow the kernel to be
-	loaded at a runtime-determined physical address as well as add
-	support for NUMA.</li></ol><hr /><h2><a name="FreeBSD/mips-on-D-Link-DIR-320" href="#FreeBSD/mips-on-D-Link-DIR-320" id="FreeBSD/mips-on-D-Link-DIR-320">FreeBSD/mips on D-Link DIR-320</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD" title="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD"></a></td><td>
-	    URL: <a href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD" title="">http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD</a></td></tr></table><p>
-	Contact: 
-	  Alexandr
-
-	  Rybalko
-	 &lt;<a href="mailto:ray@dlink.ua">ray@dlink.ua</a>&gt;
-	</p>
-      <p>FreeBSD/mips has been ported to D-Link DIR-320, wireless router based
-	on BCM5354 SoC.  Project aims to providing several working images
-	tailored for different purposes (profiles).  So far
-	<a href="http://ipsec-tools.sourceforge.net/" shape="rect">racoon</a>
-	based router-ipsec image is available.</p>
-    <h3>Open tasks:</h3><ol><li>bfeswitch configuration utility.</li><li>Add router profile.</li><li>Add wifi-router profile.</li><li>Add openvpn-router profile.</li></ol><hr /><h2><a name="FreeBSD/powerpc" href="#FreeBSD/powerpc" id="FreeBSD/powerpc">FreeBSD/powerpc</a></h2><p>
-	Contact: 
-	  Nathan
-
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>An Apple XServe G5 has been donated by Peter Grehan for package
-	building.  Based on the last two months' worth of testing, a large
-	number of commits have been made to increase stability.</p>
-
-      <p>We have completed the first full powerpc-8 package build.  Only
-	10918 were built (as compared to 19885 on a recent i386-8), primarily
-	due to a few high-impact packages failing (such as lang/python25).
-	Mark Linimon has gone through the results to denote which packages do
-	not build.  A few fixes have already been committed based on this; we
-	have patches that are being tested in the next run.</p>
-
-      <p>Mark Linimon is working on getting us more XServes.</p>
-    <h3>Open tasks:</h3><ol><li>Start the hard work of fixing individual packages.</li></ol><hr /><h2><a name="FreeBSD/powerpc64-port" href="#FreeBSD/powerpc64-port" id="FreeBSD/powerpc64-port">FreeBSD/powerpc64 port</a></h2><p>
-	Contact: 
-	  Nathan
-
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>A full 64-bit PowerPC port of FreeBSD is now complete, and should
-	shortly be merged to HEAD, likely first appearing in FreeBSD 9.0.  This
-	port supports SLB-based 64-bit server CPUs, such as the IBM POWER4-7,
-	PowerPC 970 (G5), and Cell Broadband Engine.  Current machine support
-	is limited to Apple single and dual processor G5 systems, with future
-	support planned for IBM Power Systems servers and the Sony
-	PlayStation 3.</p>
-    <hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
-	Contact: 
-	  Marius
-
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <ul>
-	<li>Yet another bug causing unaligned accesses in NFS server
-	  operation has been found and fixed in FreeBSD 7 and 8.  Unlike as
-	  announced in the last Status Report, no Erratum Notices regarding
-	  these problems have been issued as it quickly became obvious
-	  that dealing with so many of them is impractical, especially
-	  since the fixes unveiled secondary bugs.</li>
-
-	<li>Alexander Motin has fixed several bugs in netgraph(4) nodes in
-	  9.0-CURRENT which also caused unaligned accesses, so these should
-	  work now on sparc64.</li>
-
-	<li>Peter Jeremy has contributed several fixes for the sparc64 FPU
-	  emulation code, which now passes a test suite built around
-	  TestFloat.  These fixes were incorporated into FreeBSD 6, 7 and 8
-	  but unfortunately did not quite make it into 7.3-RELEASE but will
-	  be present in 8.1-RELEASE and 7.4-RELEASE.</li>
-
-	<li>Support for UltraSPARC-IV and -IV+ CPUs has been added and will
-	  be present in 8.1-RELEASE and 7.4-RELEASE.  Thus Sun Fire V890 is
-	  now supported and stable, though due to the lack of properly working
-	  test hardware, not with configurations consisting of a mix of US-IV
-	  and -IV+ CPUs.  However, performance is not yet where it should be,
-	  i.e. a buildworld on a 4x1.5GHz US-IV+ Sun Fire V890 takes nearly 3
-	  hours while on a Sun Fire V440 with (theoretically) less powerful
-	  4x1.5GHz US-IIIi CPUs it takes just over 1 hour.  So far it is
-	  unclear what is causing this, it might have to with what appears to
-	  be a silicon bug of US-IV+ CPUs encountered and worked around while
-	  adding support for these.</li>
-
-	<li>Work on getting Sun Fire V1280 supported has been continued.
-	  A third firmware bug has been worked around and a driver for
-	  the BootBus controller, which provides console and time-of-day
-	  services in these machines, has been written.  It is now possible to
-	  netboot Sun Fire V1280 into multi-user mode.  Unfortunately, they do
-	  not run stable as processes may hang when transitioning to another
-	  CPU, likely due to what the OpenSolaris code refers to as Cheetah+
-	  erratum 25, but which unfortunately is not part of the publicly
-	  available US-III+/++ errata document.  Efforts on understanding this
-	  problem are still ongoing.</li>
-
-	<li>Mark Linimon is trying to find volunteers interested in helping
-	  to fix packages on sparc64.</li>
-      </ul>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Portmaster" href="#Portmaster" id="Portmaster">Portmaster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster-proposal.html" title="http://dougbarton.us/portmaster-proposal.html"></a></td><td>
-	    URL: <a href="http://dougbarton.us/portmaster-proposal.html" title="">http://dougbarton.us/portmaster-proposal.html</a></td></tr></table><p>
-	Contact: 
-	  Doug
-
-	  Barton
-	 &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Portmaster version 2.22 is now in the ports tree and has full
-	support for the following new features:</p>
-
-      <ul>
-	<li>Using the INDEX file to show that an installed port needs
-	  updating.</li>
-
-	<li>Support for installation of packages in 'try packages first,'
-	  --packages-only, --packages-if-newer, and --packages-build
-	  modes.</li>
-
-	<li>A new --delete-build-only option to delete ports/packages that
-	  are not needed at run time.</li>
-
-	<li>Updating of the terminal title bar to show what is being worked
-	  on, and how much more is left to do.</li>
-
-	<li>Support for custom definitions of the packages repository and
-	  INDEX files.</li>
-
-	<li>The ability to operate without any local ports tree at all with
-	  the --index-only and --packages-only options.</li>
-
-	<li>A new dialog to confirm the list of ports to be installed.</li>
-      </ul>
-
-      <p>I am very excited about these new features, and owe a debt of
-	gratitude to the companies and especially the individuals who stepped
-	forward to support this work.  I literally could not have done it
-	without them.</p>
-    <h3>Open tasks:</h3><ol><li>There are still some interesting and oft-requested features
-	listed on the proposal web site that I would really like to
-	implement, including (but not limited to) downloading of all packages
-	before beginning the installation, and writing out a script that can
-	be re-run either on that machine, or on a set of identical
-	machines.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/"></a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com/" title="">http://tinderbox.marcuscom.com/</a></td></tr></table><p>
-	Contact: 
-	  Thomas
-
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Port
-
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most of quarter one was spent dealing with the 7.3-RELEASE
-	process.  With apparent success enforcing Feature Safe ports commits
-	during the 8.0-RELEASE, it was continued for the recent src/
-	freeze.</p>
-
-      <p>The ports count now exceeds 21,500 ports, and counting.  The open
-	PR count currently is over 1000.  With the release of FreeBSD 7.3, it is
-	hoped this count will drop drastically.</p>
-
-      <p>Since the last report, we added four new committers, and had an
-	old committer rejoin us.</p>
-
-      <p>With the donation of an Apple Xserve, powerpc builds have resumed.
-	Renewed interest in ia64 has brought about new ports builds.  A new
-	sparc64 machine hosted by skreuser will help us with this build.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how src code updates may affect the ports
-	tree, as well as providing QA runs for major ports updates.  Of note
-	-exp runs were done for; gabor's BSD licensed bc/dc in src/, mva's
-	OpenAL and SDL upgrades; brooks' removal of NGROUPS; ed's removal of
-	libcompat and regexp.h; dinoex's jpeg update; a test run for m4
-	update; jilles' update for sh(1); johans' update for bison; and
-	roam's curl update.</p>
-    <h3>Open tasks:</h3><ol><li>Looking for help fixing
-      <url link="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports broken
-	on CURRENT</url>.</li><li>Looking for help with
-	<url link="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures">
-	    Tier-2 architectures</url>.</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing and closing.</li><li>Major commits expected soon include the latest Xorg, KDE4, and
-	Gnome updates.</li></ol><hr /><h2><a name="QAT" href="#QAT" id="QAT">QAT</a></h2><p>
-	Contact: 
-	  Ion-Mihai
-
-	  Tetcu
-	 &lt;<a href="mailto:itetcu@FreeBSD.org">itetcu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Josh
-
-	  Paetzel
-	 &lt;<a href="mailto:jpaetzel@FreeBSD.org">jpaetzel@FreeBSD.org</a>&gt;
-	</p>
-      <p>QAT has been running on a single server for about two years now
-	and has proven very effective at catching problems with ports
-	commits.  Many of the problems it cannot catch are architecture or
-	branch related.  By moving QAT to a VMware box capable of running
-	arbitrary versions of FreeBSD on both amd64 and i386 this limitation
-	will be removed.</p>
-    <h3>Open tasks:</h3><ol><li>Bring VMware server online and provision VMs.</li><li>Refactor QAT code to handle concurrent builds.</li><li>Migrate the existing QAT to the new setup.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan-2010-&#8212;-The-BSD-Conference" href="#BSDCan-2010-&#8212;-The-BSD-Conference" id="BSDCan-2010-&#8212;-The-BSD-Conference">BSDCan 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.BSDCan.org/2010/" title="http://www.BSDCan.org/2010/"></a></td><td>
-	    URL: <a href="http://www.BSDCan.org/2010/" title="">http://www.BSDCan.org/2010/</a></td></tr><tr><td><a href="http://www.BSDCan.org/2010/schedule/" title="http://www.BSDCan.org/2010/schedule/">Tutorials and Talks Schedule</a></td><td>
-	    URL: <a href="http://www.BSDCan.org/2010/schedule/" title="Tutorials and Talks Schedule">http://www.BSDCan.org/2010/schedule/</a></td></tr></table><p>
-	Contact: 
-	  BSDCan Information
-	 &lt;<a href="mailto:info@BSDCan.org">info@BSDCan.org</a>&gt;
-	</p>
-      <p>BSDCan, a BSD conference held in Ottawa, Canada, has quickly
-	established itself as the technical conference for people
-	working on and with 4.4BSD based operating systems and related
-	projects.  The organizers have found a fantastic formula that
-	appeals to a wide range of people from extreme novices to
-	advanced developers.</p>
-
-      <p>BSDCan 2010 will be held on 13-14 May 2010 at the University of
-	Ottawa, and will be preceded by two days of Tutorials on 11-12
-	May 2010.</p>
-
-      <p>There will be related events (of a social nature, for the most
-	part) on the day before and after the conference.</p>
-
-      <p>Please check the conference web site for more information.</p>
-    <hr /><h2><a name="meetBSD-2010----The-BSD-Conference" href="#meetBSD-2010----The-BSD-Conference" id="meetBSD-2010----The-BSD-Conference">meetBSD 2010 -- The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.meetbsd.org" title="http://www.meetbsd.org"></a></td><td>
-	    URL: <a href="http://www.meetbsd.org" title="">http://www.meetbsd.org</a></td></tr></table><p>
-	Contact: 
-	  meetBSD
-
-	  Information
-	 &lt;<a href="mailto:info@meetbsd.org">info@meetbsd.org</a>&gt;
-	</p>
-      <p>meetBSD is an annual event gathering users and developers of the
-	BSD operating systems family, mostly FreeBSD, NetBSD and OpenBSD.  Afer
-	the special California edition, meetBSD Wintercamp in Livigno, this
-	year we are back to Krakow, Poland.</p>
-
-      <p>meetBSD 2010 will be held on 2-3 July at Jagiellonian
-	University.</p>
-
-      <p>See the conference main web site for more details.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2010-04-2010-06.html b/website/content/en/status/report-2010-04-2010-06.html
deleted file mode 100644
index b33bdda59a..0000000000
--- a/website/content/en/status/report-2010-04-2010-06.html
+++ /dev/null
@@ -1,1588 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between April and June
-      2010.  It is the second of the four reports planned for 2010, and
-      contains 47 entries.  During this period, a lot of work has
-      gone into the development of new minor version of FreeBSD, 8.1-RELEASE,
-      which should be released within days.</p><p>Thanks to all the reporters for the excellent work!  We hope you
-      enjoy reading.</p><p>Please note that the deadline for submissions covering the
-      period between July and September 2010 is October 15th, 2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch">Binary Package Patch Infrastructure &#8212; pkg_patch</a></li><li><a href="#Collective-Resource-Limits-(aka.-Jobs)">Collective Resource Limits (aka. Jobs)</a></li><li><a href="#ExtFS-Status-Report">ExtFS Status Report</a></li><li><a href="#File-System-Changes-Notification">File System Changes Notification</a></li><li><a href="#Google-Summer-of-Code-2010">Google Summer of Code 2010</a></li><li><a href="#Making-Ports-Work-with-Clang">Making Ports Work with Clang</a></li><li><a href="#Namecache-Improvements-&#8212;-dircache">Namecache Improvements &#8212; dircache</a></li><li><a href="#Package-Management-Library-&#8212;-libpkg">Package Management Library &#8212; libpkg</a></li><li><a href="#Packet-Capturing-Stack-&#8212;-ringmap">Packet-Capturing Stack &#8212; ringmap</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Clang-Replacing-GCC-in-the-Base-System">Clang Replacing GCC in the Base System</a></li><li><a href="#DAHDI/FreeBSD-Project">DAHDI/FreeBSD Project</a></li><li><a href="#Distributed-Audit">Distributed Audit</a></li><li><a href="#General-Purpose-DMA-Framework">General-Purpose DMA Framework</a></li><li><a href="#GEOM-Based-Pseudo-RAID-Implementation-&#8212;-geom_pseudoraid">GEOM-Based Pseudo-RAID Implementation &#8212;
-      geom_pseudoraid</a></li><li><a href="#GPIO-Framework">GPIO Framework</a></li><li><a href="#New-System-Installer-&#8212;-pc-sysinstall">New System Installer &#8212; pc-sysinstall</a></li><li><a href="#OpenAFS-Port">OpenAFS Port</a></li><li><a href="#Resource-Containers">Resource Containers</a></li><li><a href="#V4L-Support-in-Linux-Emulator">V4L Support in Linux Emulator</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-Core-Team-Election">FreeBSD Core Team Election</a></li><li><a href="#Release-Engineering-Team">Release Engineering Team</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></li><li><a href="#libnetstat(3)">libnetstat(3)</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Interrupt-Threads">Interrupt Threads</a></li><li><a href="#Jail-Based-Virtualization">Jail-Based Virtualization</a></li><li><a href="#Kernel-Event-Timers-Infrastructure">Kernel Event Timers Infrastructure</a></li><li><a href="#ZFS">ZFS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li><li><a href="#The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#BSD-Licensed-grep-in-Base-System">BSD-Licensed grep in Base System</a></li><li><a href="#BSD-Licensed-iconv-in-Base-System">BSD-Licensed iconv in Base System</a></li><li><a href="#FreeBSD-Services-Control-&#8212;-fsc">FreeBSD Services Control &#8212; fsc</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Flattened-Device-Tree-for-Embedded-FreeBSD">Flattened Device Tree for Embedded FreeBSD</a></li><li><a href="#FreeBSD-on-the-Sony-Playstation-3">FreeBSD on the Sony Playstation 3</a></li><li><a href="#FreeBSD/avr32">FreeBSD/avr32</a></li><li><a href="#FreeBSD/powerpc64">FreeBSD/powerpc64</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium-Web-Browser">Chromium Web Browser</a></li><li><a href="#FreeBSD-Haskell">FreeBSD Haskell</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSD-Day@2010">BSD-Day@2010</a></li><li><a href="#BSDCan">BSDCan</a></li><li><a href="#meetBSD-2010-&#8212;-The-BSD-Conference">meetBSD 2010 &#8212; The BSD Conference</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch" href="#Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch" id="Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch">Binary Package Patch Infrastructure &#8212; pkg_patch</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/IvanVoras/pkg_patch" title="http://wiki.FreeBSD.org/IvanVoras/pkg_patch">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/IvanVoras/pkg_patch" title="Wiki page">http://wiki.FreeBSD.org/IvanVoras/pkg_patch</a></td></tr></table><p>
-	Contact:
-	  Ivan
-	  Voras
-	 &lt;<a href="mailto:ivoras@FreeBSD.org">ivoras@FreeBSD.org</a>&gt;
-	</p>
-      <p>The pkg_patch project is about creating a binary package patch
-	infrastructure which would allow users to patch their live system's
-	packages in an easy and efficient way.  It is a C program written to
-	interface with libpkg (for things which are common to all pkg
-	utilities) meant to be included in the base system when it is done.
-	It comes with built-in mass patch creation and application
-	commands.  It is funded by Google Summer of Code 2010.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the project.</li><li>Get some testing for it.</li><li>Convince the Port Management Team it is actually a Good
-	Thing to have even as an experimental feature.</li><li>Agree upon the policy on which package patches will be
-	created (i.e. from which point in time to which point in time),
-	assuming the "stable" package tree idea has still not gotten
-	traction.</li></ol><hr /><h2><a name="Collective-Resource-Limits-(aka.-Jobs)" href="#Collective-Resource-Limits-(aka.-Jobs)" id="Collective-Resource-Limits-(aka.-Jobs)">Collective Resource Limits (aka. Jobs)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/G%C3%A1borSoC2010" title="http://wiki.FreeBSD.org/G%C3%A1borSoC2010">Project page on the wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/G%C3%A1borSoC2010" title="Project page on the wiki">http://wiki.FreeBSD.org/G%C3%A1borSoC2010</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2010/gabor_jobs/irix_jobs" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2010/gabor_jobs/irix_jobs">Sources in Perforce</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2010/gabor_jobs/irix_jobs" title="Sources in Perforce">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2010/gabor_jobs/irix_jobs</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The SGI IRIX operating system has a concept, called job, which
-	is used to group processes together and then apply resource limits
-	on them.  The purpose of this project is to implement this facility
-	on FreeBSD.</p>
-
-      <p>I spent most of the time familiarizing myself with how
-	things are done inside the kernel, how syscalls work, etc.  So far,
-	I have the basic understanding needed and I added the most
-	important syscalls to group processes together into jobs and
-	manipulate collective resource limits on them.</p>
-
-      <p>There is a bug, which I am tracking down at the moment, after
-	this I can start to implement actual resource limit enforcement.
-	For some of the limit types, it will be relatively easy but some
-	others will take more effort and studies.</p>
-    <h3>Open tasks:</h3><ol><li>Fix the showstopper bug, which prevent me working on actual
-	limit enforcement.</li><li>Implement limit enforcements for all of the limits supported
-	by IRIX.</li><li>Add support for userland facilities and make utilities
-	jobs-aware, like showing jobs in ps(1), etc.</li></ol><hr /><h2><a name="ExtFS-Status-Report" href="#ExtFS-Status-Report" id="ExtFS-Status-Report">ExtFS Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2010ZhengLiu" title="http://wiki.FreeBSD.org/SOC2010ZhengLiu"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2010ZhengLiu" title="">http://wiki.FreeBSD.org/SOC2010ZhengLiu</a></td></tr></table><p>
-	Contact:
-	  Zheng
-	  Liu
-	 &lt;<a href="mailto:gnehzuil@gmail.com">gnehzuil@gmail.com</a>&gt;
-	</p>
-      <p>This project has two goals: pre-allocation algorithm and ext4
-	read-only mode.</p>
-
-      <p>The aim of pre-allocation algorithm is to implement a reservation
-	window mechanism.  Now this mechanism has been introduced.  The
-	performance comparison can be found on the <a href="http://wiki.FreeBSD.org/SOC2010ZhengLiu" shape="rect">wiki</a>.</p>
-
-      <p>The aim of ext4 read-only mode is to make it possible to read ext4 file
-	system in read-only mode when the hard disk is formatted with default
-	features.  Currently it only supports a few features, such as extents,
-	huge_file.  Others features will be added, such as dir_index,
-	uninit_bg, dir_nlink, flex_bg and extra_isize.  My work resides in
-	extfs and ext4fs branch of Perforce.</p>
-    <hr /><h2><a name="File-System-Changes-Notification" href="#File-System-Changes-Notification" id="File-System-Changes-Notification">File System Changes Notification</a></h2><p>
-	Contact:
-	  Ilya
-	  Putsikau
-	 &lt;<a href="mailto:iputsikau@gmail.com">iputsikau@gmail.com</a>&gt;
-	</p>
-      <p>The aim of the project is to implement an inotify-compatible file system
-	change notification mechanism for FreeBSD and later, and add inotify
-	support to linuxulator.  The result, fsnotify is already functional
-	but not yet compatible with inotify in some details.</p>
-    <h3>Open tasks:</h3><ol><li>Add access permissions checks.</li><li>Port inotify test cases.</li><li>Fix compatibility issues.</li><li>Add linuxulator support.</li></ol><hr /><h2><a name="Google-Summer-of-Code-2010" href="#Google-Summer-of-Code-2010" id="Google-Summer-of-Code-2010">Google Summer of Code 2010</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SummerOfCode2010Projects" title="http://wiki.FreeBSD.org/SummerOfCode2010Projects">Summer of Code 2010 Projects</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SummerOfCode2010Projects" title="Summer of Code 2010 Projects">http://wiki.FreeBSD.org/SummerOfCode2010Projects</a></td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Tim
-	  Kientzle
-	 &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are once again participating in the Google Summer of Code.
-	This is our 6th year of participation and we hope to once again see
-	great results from our 18 students.  Coding officially began May
-	24th, and we are in the middle of the mid-term evaluation period.
-	You can see and comment on weekly status reports on the <a href="http://lists.freebsd.org/mailman/listinfo/soc-status" shape="rect">mailing
-	list</a> or on the <a href="http://wiki.freebsd.org/SummerOfCode2010" shape="rect">wiki</a>.</p>
-    <hr /><h2><a name="Making-Ports-Work-with-Clang" href="#Making-Ports-Work-with-Clang" id="Making-Ports-Work-with-Clang">Making Ports Work with Clang</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2010AndriusMorkunas" title="http://wiki.FreeBSD.org/SOC2010AndriusMorkunas"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2010AndriusMorkunas" title="">http://wiki.FreeBSD.org/SOC2010AndriusMorkunas</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/PortsAndClang" title="http://wiki.FreeBSD.org/PortsAndClang"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PortsAndClang" title="">http://wiki.FreeBSD.org/PortsAndClang</a></td></tr><tr><td><a href="http://rainbow-runner.nl/~andrius/soc/" title="http://rainbow-runner.nl/~andrius/soc/">GSoC2010 patches</a></td><td>
-	    URL: <a href="http://rainbow-runner.nl/~andrius/soc/" title="GSoC2010 patches">http://rainbow-runner.nl/~andrius/soc/</a></td></tr><tr><td><a href="http://rainbow-runner.nl/clang/patches/" title="http://rainbow-runner.nl/clang/patches/">All patches for ports</a></td><td>
-	    URL: <a href="http://rainbow-runner.nl/clang/patches/" title="All patches for ports">http://rainbow-runner.nl/clang/patches/</a></td></tr></table><p>
-	Contact:
-	  Andrius
-	  Morkunas
-	 &lt;<a href="mailto:hinokind@gmail.com">hinokind@gmail.com</a>&gt;
-	</p>
-      <p>First part of the project is mostly complete.  I added support
-	for new PORTS_CC variable which should be used in make.conf instead
-	of CC to change ports compiler.  This allows user to change ports
-	compiler easily, while still respecting USE_GCC.</p>
-
-      <p>Some patches were written to get ports to work with Clang, and
-	a lot of old patches written prior to the Google Summer of Code
-	project were updated.  There are still a lot of broken ports, and
-	some that cannot be built because of Clang/LLVM bugs, but at
-	this point, Clang can build most ports.</p>
-    <h3>Open tasks:</h3><ol><li>Fix broken ports that do not work with Clang.</li><li>Test patched ports with Clang, report Clang bugs.</li></ol><hr /><h2><a name="Namecache-Improvements-&#8212;-dircache" href="#Namecache-Improvements-&#8212;-dircache" id="Namecache-Improvements-&#8212;-dircache">Namecache Improvements &#8212; dircache</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2010GlebKurtsov" title="http://wiki.FreeBSD.org/SOC2010GlebKurtsov"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2010GlebKurtsov" title="">http://wiki.FreeBSD.org/SOC2010GlebKurtsov</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Kurtsou
-	 &lt;<a href="mailto:gk@FreeBSD.org">gk@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have been reimplementing VFS namecache to make it granularly
-	locked and supporting reliable full-path lookup without calling
-	underlying file system routines.  I have successfully implemented
-	directory cache that works in idealized environment with tmpfs.  I am
-	currently working on adding support for entries without associated
-	vnodes and for "weak" entries and incomplete cached path.</p>
-    <hr /><h2><a name="Package-Management-Library-&#8212;-libpkg" href="#Package-Management-Library-&#8212;-libpkg" id="Package-Management-Library-&#8212;-libpkg">Package Management Library &#8212; libpkg</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2010DavidForsythe" title="http://wiki.FreeBSD.org/SOC2010DavidForsythe">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2010DavidForsythe" title="Wiki page">http://wiki.FreeBSD.org/SOC2010DavidForsythe</a></td></tr><tr><td><a href="http://code.google.com/p/libpkg" title="http://code.google.com/p/libpkg">Main project page</a></td><td>
-	    URL: <a href="http://code.google.com/p/libpkg" title="Main project page">http://code.google.com/p/libpkg</a></td></tr></table><p>
-	Contact:
-	  David
-	  Forsythe
-	 &lt;<a href="mailto:dforsyth@FreeBSD.org">dforsyth@FreeBSD.org</a>&gt;
-	</p>
-      <p>The libpkg library will allow for fairly fine grained control
-	over package management.</p>
-
-      <p>Presently libpkg has complete read functionality.  Info and
-	delete tools that have most of the current package tool features
-	have already been implemented, and once they are completed they can
-	be considered replacements for their counterparts.</p>
-
-      <p>Once the write and logging aspects of the library are more
-	mature, add and create tools can be created quickly.  A new set of
-	more maintainable package tools that leverage libpkg will hopefully
-	be available soon after.</p>
-    <hr /><h2><a name="Packet-Capturing-Stack-&#8212;-ringmap" href="#Packet-Capturing-Stack-&#8212;-ringmap" id="Packet-Capturing-Stack-&#8212;-ringmap">Packet-Capturing Stack &#8212; ringmap</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/ringmap/" title="http://code.google.com/p/ringmap/">Project-Page on Google Code</a></td><td>
-	    URL: <a href="http://code.google.com/p/ringmap/" title="Project-Page on Google Code">http://code.google.com/p/ringmap/</a></td></tr><tr><td><a href="http://ringmap.googlecode.com/files/ringmap_slides.pdf" title="http://ringmap.googlecode.com/files/ringmap_slides.pdf">Slides</a></td><td>
-	    URL: <a href="http://ringmap.googlecode.com/files/ringmap_slides.pdf" title="Slides">http://ringmap.googlecode.com/files/ringmap_slides.pdf</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Fiveg
-	 &lt;<a href="mailto:afiveg@FreeBSD.org">afiveg@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ringmap stack is a complete FreeBSD packet-capturing
-	mplementation specialized for very high-speed networks.  Similar
-	to the "zero-copy BPF" implementation, the idea of ringmap is to
-	eliminate packet copy operations by using shared memory buffers.
-	However, unlike the "zero-copy BPF" model, ringmap eliminates
-	ALL packet copies during capturing: the network adapter's DMA
-	buffer is mapped directly into user-space.  The ringmap stack
-	also adapts libpcap accordingly to provide userspace
-	applications with access to the captured packets without any
-	additional overhead.</p>
-
-      <p>In the context of Google Summer of Code 2010:</p>
-
-      <ul>
-	<li>The ringmap software was ported to 9-CURRENT.</li>
-
-	<li>Ringmap was redesigned to make it easier to port to other
-	  adapters and to integrate it with other network drivers.</li>
-
-	<li>Also ringmap was extended to be multi-threaded.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Porting ringmap to 10GbE (integrating with ixgbe
-	driver).</li><li>Porting the entire ringmap code from 9-CURRENT to
-	-STABLE.</li><li>Evaluation tests.</li><li>Documentation.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Clang-Replacing-GCC-in-the-Base-System" href="#Clang-Replacing-GCC-in-the-Base-System" id="Clang-Replacing-GCC-in-the-Base-System">Clang Replacing GCC in the Base System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Pawel
-	  Worach
-	 &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	</p>
-      <p>In the past quarter we imported Clang into FreeBSD and it is being
-	built by default on i386/amd64/powerpc.  We have not yet committed
-	the necessary changes to let world compile with Clang.</p>
-
-      <p>Some bugs and warnings were fixed in HEAD as a result of the Clang
-	import and people are exploring more and more areas (DTrace, etc).
-	There are some bug fixes in Clang/LLVM as well that stem from the
-	import (unknown pragmas warnings, etc).</p>
-
-      <p>Roman Divacky and Matthew Fleming are working on ELF writer in
-	LLVM.  This is meant as a replacement for assembler (currently we
-	use an outdated GNU as(1)).  This work is progressing nice, currently it
-	is able to produce working variants of hello world in C and C++, and
-	some other small programs from "configure run".</p>
-    <h3>Open tasks:</h3><ol><li>Import of newer Clang/LLVM into HEAD.</li><li>Help with ARM/MIPS/SPARC64.</li><li>Start pushing src patches into HEAD.</li><li>More testing of Clang on third-party applications (ports).</li><li>More work on the ELF writer.</li></ol><hr /><h2><a name="DAHDI/FreeBSD-Project" href="#DAHDI/FreeBSD-Project" id="DAHDI/FreeBSD-Project">DAHDI/FreeBSD Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.asterisk.org/dahdi/" title="http://www.asterisk.org/dahdi/"></a></td><td>
-	    URL: <a href="http://www.asterisk.org/dahdi/" title="">http://www.asterisk.org/dahdi/</a></td></tr><tr><td><a href="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html" title="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html">Project Status</a></td><td>
-	    URL: <a href="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html" title="Project Status">https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html</a></td></tr></table><p>
-	Contact:
-	  Max
-	  Khon
-	 &lt;<a href="mailto:fjoe@samodelkin.net">fjoe@samodelkin.net</a>&gt;
-	</p>
-      <p>The purpose of DAHDI/FreeBSD project is to make it possible to use
-	FreeBSD as a base system for software PBX solutions.</p>
-
-      <p>DAHDI (Digium/Asterisk Hardware Device Interface) is an
-	open-source device driver framework and a set of hardware drivers for
-	E1/T1, ISDN digital, and FXO/FXS analog cards
-	[<a href="http://www.asterisk.org/dahdi/" shape="rect">1</a>].  Asterisk is one of the most
-	popular open-source software PBX solutions
-	[<a href="http://www.asterisk.org/" shape="rect">2</a>].</p>
-
-      <p>The project includes porting DAHDI framework and hardware drivers for
-	E1/T1, FXO/FXS analog, and ISDN digital cards to FreeBSD.  This also
-	includes TDMoE support, software and HW echo cancellation (Octasic,
-	VPMADT032), and hardware transcoding support (TC400B).  The work is ongoing
-	in the official DAHDI SVN repository with the close collaboration
-	with DAHDI folks at Digium.</p>
-
-      <p>The project is nearing completion.  The DAHDI framework and
-	hardware drivers telephony cards have been ported and tested.
-	There are a number of success stories from early adopters who
-	have been using E1/T1 and FXO/FXS cards on FreeBSD for several
-	months.</p>
-    <hr /><h2><a name="Distributed-Audit" href="#Distributed-Audit" id="Distributed-Audit">Distributed Audit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=wHa@//depot/projects/soc2010/disaudit/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=wHa@//depot/projects/soc2010/disaudit/?ac=83">Perforce repository</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=wHa@//depot/projects/soc2010/disaudit/?ac=83" title="Perforce repository">http://p4web.freebsd.org/@md=d&amp;cd=//&amp;c=wHa@//depot/projects/soc2010/disaudit/?ac=83</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2010SergioLigregni" title="http://wiki.FreeBSD.org/SOC2010SergioLigregni">Project Wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2010SergioLigregni" title="Project Wiki">http://wiki.FreeBSD.org/SOC2010SergioLigregni</a></td></tr></table><p>
-	Contact:
-	  Sergio
-	  Ligregni
-	 &lt;<a href="mailto:ligregni@FreeBSD.org">ligregni@FreeBSD.org</a>&gt;
-	</p>
-      <p>90% of the functionality is working, the daemons sync two
-	systems in a master-slave paradigm.</p>
-    <h3>Open tasks:</h3><ol><li>Standardize the code to meet FreeBSD requirements.</li><li>Implement SSL in network communication.</li><li>Perform security improvements and bug fixing, strlxxx() functions,
-	memcpy() instead of strcpy() when using non-char variables.</li><li>Integrate with the current Audit subsystem.</li></ol><hr /><h2><a name="General-Purpose-DMA-Framework" href="#General-Purpose-DMA-Framework" id="General-Purpose-DMA-Framework">General-Purpose DMA Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2010JakubKlama" title="http://wiki.FreeBSD.org/SOC2010JakubKlama">Project description on FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2010JakubKlama" title="Project description on FreeBSD wiki">http://wiki.FreeBSD.org/SOC2010JakubKlama</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=eCv@//depot/projects/soc2010/jceel_dma/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=eCv@//depot/projects/soc2010/jceel_dma/?ac=83">Project branch on Perforce</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=eCv@//depot/projects/soc2010/jceel_dma/?ac=83" title="Project branch on Perforce">http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=eCv@//depot/projects/soc2010/jceel_dma/?ac=83</a></td></tr></table><p>
-	Contact:
-	  Jakub
-	  Klama
-	 &lt;<a href="mailto:jceel@FreeBSD.org">jceel@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project purpose is adding support for general purpose DMA
-	engines found in most embedded devices.  GPDMA framework provides a
-	unified KOBJ interface to DMA engine drivers and unified
-	programming interface to use direct memory transfers in kernel and
-	userspace applications.</p>
-
-      <p>This project is a part of Google Summer of Code 2010 and it is a
-	work in progress.  Current status can be observed on the wiki
-	page.</p>
-    <h3>Open tasks:</h3><ol><li>Add support for more DMA engines.</li><li>Complete, clean up, and merge with HEAD.</li></ol><hr /><h2><a name="GEOM-Based-Pseudo-RAID-Implementation-&#8212;-geom_pseudoraid" href="#GEOM-Based-Pseudo-RAID-Implementation-&#8212;-geom_pseudoraid" id="GEOM-Based-Pseudo-RAID-Implementation-&#8212;-geom_pseudoraid">GEOM-Based Pseudo-RAID Implementation &#8212;
-      geom_pseudoraid</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://acm.poly.edu/~spawk/geom_pseudoraid-20100715.tbz" title="http://acm.poly.edu/~spawk/geom_pseudoraid-20100715.tbz">Code snapshot</a></td><td>
-	    URL: <a href="http://acm.poly.edu/~spawk/geom_pseudoraid-20100715.tbz" title="Code snapshot">http://acm.poly.edu/~spawk/geom_pseudoraid-20100715.tbz</a></td></tr></table><p>
-	Contact:
-	  Boris
-	  Kochergin
-	 &lt;<a href="mailto:spawk@acm.poly.edu">spawk@acm.poly.edu</a>&gt;
-	</p>
-      <p>The old ata(4) driver is believed to be going away sometime in
-	the future, to be replaced with ATA_CAM
-	[<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004106.html" shape="rect">1</a>].
-	However, ATA pseudo-RAID support in FreeBSD, ataraid(4), is
-	implemented as part of said ata(4) driver, which means that it,
-	too, will be going away.  It was decided that pseudo-RAID support is
-	desirable and that it should be reimplemented in GEOM
-	[<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004150.html" shape="rect">2</a>]
-	[<a href="http://www.FreeBSD.org/news/status/report-2010-01-2010-03.html#CAM-based-ATA-implementation" shape="rect">3</a>],
-	which this project aims to do.</p>
-
-      <p>Currently, RAID-1 arrays can be used on VIA Tech V-RAID and
-	Adaptec HostRAID controllers in a limited capacity.  There is no
-	support for writing metadata yet, so disks are not marked degraded,
-	there is no rebuild support, etc.  These features are planned, along
-	with support for more hardware and RAID-0 and SPAN arrays.</p>
-
-      <p>A major setback for the current code is that it uses the
-	device(9) family of functions to identify ATA pseudo-RAID
-	controllers and constructs arrays based on that information.
-	Unfortunately, ATA_CAM does not appear to add its devices to the
-	device tree, so that tactic cannot be used with ATA_CAM.  While this
-	is fine for development of the actual RAID parts of the code, the
-	project will be somewhat useless in the absence of the old ata(4)
-	driver.  There has been talk of exporting PCI information to GEOM
-	[<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004167.html" shape="rect">4</a>]
-	[<a href="http://lists.FreeBSD.org/pipermail/freebsd-geom/2010-April/004158.html" shape="rect">5</a>],
-	but the work does not appear to have been completed yet.</p>
-    <h3>Open tasks:</h3><ol><li>Obtain documentation for or reverse-engineer metadata formats
-	for which there is no write support in the ataraid(4) driver (for
-	example, Adaptec HostRAID).</li><li>Add CAM support for exporting PCI information to GEOM.</li></ol><hr /><h2><a name="GPIO-Framework" href="#GPIO-Framework" id="GPIO-Framework">GPIO Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/GPIO" title="http://wiki.FreeBSD.org/GPIO"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/GPIO" title="">http://wiki.FreeBSD.org/GPIO</a></td></tr></table><p>
-	Contact:
-	  Luiz Otavio O
-	  Souza
-	 &lt;<a href="mailto:loos.br@gmail.com">loos.br@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Implementation of General Purpose Input/Output interface for
-	FreeBSD.  Current GPIO bus implementation allows user to control pins
-	from userland and it could be expanded to support various type of
-	peripheral devices.  So far there are two drivers:</p>
-
-      <ul>
-	<li><b>gpioled</b> provides simple led(4) functionality.</li>
-
-	<li><b>gpioiic</b> implements I2C over GPIO.</li>
-      </ul>
-
-      <p>Framework is used in Alexandr Rybalko's port of FreeBSD to D-Link
-	DIR-320 and in Luis Otavio O Souza's work of bringing FreeBSD to
-	RouterBoard.</p>
-    <hr /><h2><a name="New-System-Installer-&#8212;-pc-sysinstall" href="#New-System-Installer-&#8212;-pc-sysinstall" id="New-System-Installer-&#8212;-pc-sysinstall">New System Installer &#8212; pc-sysinstall</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/svn-src-all/2010-June/025660.html" title="http://lists.FreeBSD.org/pipermail/svn-src-all/2010-June/025660.html">Initial commit message</a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/svn-src-all/2010-June/025660.html" title="Initial commit message">http://lists.FreeBSD.org/pipermail/svn-src-all/2010-June/025660.html</a></td></tr><tr><td><a href="http://www.BSDCan.org/2010/schedule/attachments/142_pc-sysinstall-kris-moore-2010.pdf" title="http://www.BSDCan.org/2010/schedule/attachments/142_pc-sysinstall-kris-moore-2010.pdf">BSDCan slides</a></td><td>
-	    URL: <a href="http://www.BSDCan.org/2010/schedule/attachments/142_pc-sysinstall-kris-moore-2010.pdf" title="BSDCan slides">http://www.BSDCan.org/2010/schedule/attachments/142_pc-sysinstall-kris-moore-2010.pdf</a></td></tr></table><p>
-	Contact:
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kris@pcbsd.org">kris@pcbsd.org</a>&gt;
-	<br />
-	Contact:
-	  M. Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new system installation backend, pc-sysinstall, was merged
-	into HEAD recently and work is already underway to make it more
-	functional and useful as a complete replacement to standard
-	"sysinstall".  It is written 100% in shell, not requiring any
-	additional tools from what is standard to FreeBSD.  The backend already
-	supports a number of exciting features such as:</p>
-
-      <ul>
-	<li>ZFS (Including support for raidz/mirror/multiple device pool
-	  setups).</li>
-
-	<li>Disk encryption via GELI(8).</li>
-
-	<li>Auto labeling of file systems with glabel(8).</li>
-
-	<li>Big disk support using GPT/EFI.</li>
-
-	<li>Full Installation Logging, which is saved to disk for
-	  post-install inspection.</li>
-      </ul>
-
-      <p>In addition to the features above, pc-sysinstall is unique, in
-	that every install ends up being a scripted install.  Front-ends, be
-	it GUI- or text-based, simply generate the appropriate system
-	configuration file, and pc-sysinstall does the grunt work of the
-	actual installation.  This is important for a couple of reasons.
-	First, it makes the task of front-end development much easier by
-	not needing to worry about a backend-driven program flow.  Second it
-	means that any front-end can be used to generate the installation
-	configuration file, which can then be copied or modified to perform
-	automated installs.</p>
-
-      <p>While pc-sysinstall is still relatively new, it is already in
-	use as the default backend for PC-BSD�8.0 and 8.1, and has been
-	getting a very good reception and any bugs found are fixed quickly.
-	A text-based front-end is already in the works which will allow
-	installation media to be created without X11 support.</p>
-    <hr /><h2><a name="OpenAFS-Port" href="#OpenAFS-Port" id="OpenAFS-Port">OpenAFS Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openafs.org" title="http://openafs.org">OpenAFS home page</a></td><td>
-	    URL: <a href="http://openafs.org" title="OpenAFS home page">http://openafs.org</a></td></tr><tr><td><a href="http://web.mit.edu/freebsd/openafs/openafs.shar" title="http://web.mit.edu/freebsd/openafs/openafs.shar">FreeBSD port for the OpenAFS 1.5.75 release</a></td><td>
-	    URL: <a href="http://web.mit.edu/freebsd/openafs/openafs.shar" title="FreeBSD port for the OpenAFS 1.5.75 release">http://web.mit.edu/freebsd/openafs/openafs.shar</a></td></tr></table><p>
-	Contact:
-	  Benjamin
-	  Kaduk
-	 &lt;<a href="mailto:kaduk@mit.edu">kaduk@mit.edu</a>&gt;
-	<br />
-	Contact:
-	  Derrick
-	  Brashear
-	 &lt;<a href="mailto:shadow@gmail.com">shadow@gmail.com</a>&gt;
-	</p>
-      <p>AFS is a distributed network filesystem that originated from the
-	Andrew Project at Carnegie-Mellon University; the OpenAFS client
-	implementation has not been particularly useful on FreeBSD since the
-	4.X releases.  Recent work on the OpenAFS codebase has updated
-	it to be consistent with current versions of FreeBSD, and the client,
-	though still considered experimental, is now relatively stable for
-	light (single-threaded) use on 9-CURRENT.  The auxiliary utilities
-	for managing and examining the filesystem are functional, and
-	reading and writing files works sufficiently well to copy /usr/src
-	into and out of AFS.  Compiling and running executables in AFS is
-	unsuccessful, though, as mmap() is not always reliable.</p>
-
-      <p>There are several known outstanding issues that are being
-	worked on, but detailed bug reports are welcome at <a href="mailto:port-freebsd@openafs.org" shape="rect">port-freebsd@openafs.org</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Fix the {get,put}pages vnode operations for more reliable
-	mmap() operation.</li><li>Update VFS locking to allow the use of disk-based client
-	caches as well as memory-based caches.</li><li>Track down races and deadlocks that appear under
-	load.</li><li>Integrate with the bsd.kmod.mk kernel-module build
-	infrastructure.</li></ol><hr /><h2><a name="Resource-Containers" href="#Resource-Containers" id="Resource-Containers">Resource Containers</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of now, FreeBSD only offers very rudimentary resource controls &#8212;
-	resource limits for many resources (e.g. SysV IPC) are missing, and
-	there is no way to set resource limits for jails.  As a result,
-	users who want to run many different workloads on a single physical
-	machine often have to replace jails with several FreeBSD instances
-	running in virtual machines.</p>
-
-      <p>The goal of this project is to implement resource containers
-	and a simple per-jail resource limits mechanism.  Resource
-	containers are also a prerequisite for other resource management
-	mechanisms, such as Hierarchical Resource Limits, for
-	"Collective Limits on Set of Processes (aka. Jobs)" Google
-	Summer of Code 2010 project, for implementing mechanism similar
-	to Linux cgroups, and might be also used to e.g. provide
-	precise resource usage accounting for administrative or billing
-	purposes.</p>
-
-      <p>This project is being sponsored by The FreeBSD Foundation.</p>
-    <hr /><h2><a name="V4L-Support-in-Linux-Emulator" href="#V4L-Support-in-Linux-Emulator" id="V4L-Support-in-Linux-Emulator">V4L Support in Linux Emulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://opal.com/freebsd/sys/compat/linux/" title="http://opal.com/freebsd/sys/compat/linux/"></a></td><td>
-	    URL: <a href="http://opal.com/freebsd/sys/compat/linux/" title="">http://opal.com/freebsd/sys/compat/linux/</a></td></tr></table><p>
-	Contact:
-	  J.R.
-	  Oldroyd
-	 &lt;<a href="mailto:fbsd@opal.com">fbsd@opal.com</a>&gt;
-	</p>
-      <p>Some bug fixes were applied, and the code was also tested and
-	made to work with the cuse4bsd webcam driver, which supports a
-	great many camera chipsets.</p>
-
-      <p>The code is still only in 9-CURRENT.  We were going to MFC it to
-	8.x but ran into the code freeze for 8.1, so missed that.  However,
-	the code does work on 8-STABLE.  We will try to get it MFC'd for
-	8.2.</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats">FreeBSD Support page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="FreeBSD Support page">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting">Resources and documentation available for Bugbusting</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="Resources and documentation available for Bugbusting">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/Bugathons" title="http://wiki.FreeBSD.org/Bugathons">Information on Bugathons</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Bugathons" title="Information on Bugathons">http://wiki.FreeBSD.org/Bugathons</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/">Links to all of the auto-generated PR reports</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="Links to all of the auto-generated PR reports">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html">PRs recommended for committer evaluation by the bugbusting team</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="PRs recommended for committer evaluation by the bugbusting team">http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html">PRs considered easy by the bugbusting team</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html" title="PRs considered easy by the bugbusting team">http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html" title="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html">Summary Chart of FreeBSD PRs</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html" title="Summary Chart of FreeBSD PRs">http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html</a></td></tr></table><p>
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Volker
-	  Werth
-	 &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
-	</p>
-      <p>After a long hiatus, we aim to hold a bugathon on the weekend of
-	the 6th�-�9th August.  Everybody is welcome to help resolve or
-	progress PRs from the database.  We appreciate the help of
-	committers and non-committers alike, please join us on IRC in
-	#freebsd-bugbusters on EFnet if you are free at any time over
-	that weekend and can help.  Please see the "Bugathon" URL for more
-	information.</p>
-
-      <p>Mark Linimon and Gavin Atkinson held a session on the State of
-	Bugbusting at BSDCan, which was well attended and led to some
-	interesting discussions.  Time was also found to sit down with
-	several committers to discuss long-standing PRs.</p>
-
-      <p>The bugbusting team continue work on trying to make the GNATS PR
-	database more accessible and easier for committers to find and
-	resolve PRs.</p>
-
-      <p>As a result, PRs continue to be classified as they arrive, by
-	adding 'tags' to the subject lines corresponding to the kernel
-	subsystem involved, or man page references for userland PRs.
-	Reports are generated from these nightly, grouping related PRs in
-	one place, sorted by tag or man page.  Mark Linimon continues work
-	on producing a new report, Summary Chart of PRs with Tags, which
-	sorts tagged PRs into logical groups such as file system, network
-	drivers, libraries, and so forth.  The slice labels are clickable
-	and may further subdivide the groups.  The chart is updated once
-	a day.  You can consider it as a prototype for browsing
-	"subcategories" of kernel PRs.</p>
-
-      <p>The "recommended list" has been split up into "non-trivial PRs
-	which need committer evaluation" and the "easy list" of trivial
-	PRs, to try to focus some attention on the latter.  Various new
-	reports exist, including "PRs containing code for new device
-	drivers", "PRs which are from FreeBSD vendors or OEMs", and
-	"PRs referencing other BSDs".</p>
-
-      <p>It is now possible for interested parties to be emailed a weekly,
-	customized, report similar in style to the above.  If you are
-	interested in setting one up, contact linimon@FreeBSD.org.</p>
-
-      <p>Our clearance rate of PRs, especially in kern and bin, seems to
-	be improving.  The number of non-ports PRs has stayed almost
-	constant since the last status report.</p>
-
-      <p>As always, anybody interested in helping out with the PR queue is
-	welcome to join us in #freebsd-bugbusters on EFnet.  We are always
-	looking for additional help, whether your interests lie in triaging
-	incoming PRs, generating patches to resolve existing problems, or
-	simply helping with the database housekeeping (identifying duplicate
-	PRs, ones that have already been resolved, etc).  This is a great way
-	of getting more involved with FreeBSD!</p>
-    <h3>Open tasks:</h3><ol><li>Plan and manage the bugathon in August, and get as many people
-	as possible interested in participating.</li><li>Try to find ways to get more committers helping us with closing
-	PRs that the team has already analyzed.</li></ol><hr /><h2><a name="FreeBSD-Core-Team-Election" href="#FreeBSD-Core-Team-Election" id="FreeBSD-Core-Team-Election">FreeBSD Core Team Election</a></h2><p>
-	Contact:
-	  Core
-	  Team
-	 &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The 2010 FreeBSD core team election was recently completed.  The
-	FreeBSD core team acts as the project's "board of directors" and is
-	responsible for approving new src committers, resolving disputes
-	between developers, appointing sub-committees for specific
-	purposes (security officer, release engineering, port managers,
-	webmaster, et cetera), and making any other administrative or
-	policy decisions as needed.  The core team has been elected by
-	FreeBSD developers every 2 years since 2000, and this marks our 6th
-	democratically elected core team.</p>
-
-      <p>The new core team would like to thank outgoing members Kris
-	Kennaway, Giorgos Keramidas, George V. Neville-Neil, Murray
-	Stokely, and Peter Wemm for their service over the past two
-	(and in some cases, many more) years.</p>
-
-      <p>The core team would also especially like to thank Dag-Erling
-	Sm�grav for running the election.</p>
-
-      <p>The newly elected core team members are:</p>
-
-      <ul>
-	<li>John Baldwin</li>
-	<li>Konstantin Belousov</li>
-	<li>Warner Losh</li>
-	<li>Pav Lucistnik</li>
-	<li>Colin Percival</li>
-      </ul>
-
-      <p>The returning core team members are:</p>
-
-      <ul>
-	<li>Wilko Bulte</li>
-	<li>Brooks Davis</li>
-	<li>Hiroki Sato</li>
-	<li>Robert Watson</li>
-      </ul>
-    <hr /><h2><a name="Release-Engineering-Team" href="#Release-Engineering-Team" id="Release-Engineering-Team">Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team has been working on the
-	FreeBSD�8.1-RELEASE.  At the time of this writing
-	the final builds have been completed and uploaded to
-	the master FTP site.  The release announcement should
-	be made within the next couple of days.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org" title="http://www.FreeBSDFoundation.org"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org" title="">http://www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We were proud to be a sponsor for BSDCan in May.  We also
-	committed to sponsoring MeetBSD 2010 Poland and California.  We
-	provided 12 travel grants for BSDCan.</p>
-
-      <p>The Foundation and Core Team held a summit on BSD-licensed
-	toolchains at BSDCan 2010.</p>
-
-      <p>We officially kicked off five new projects that we are funding.
-	They are BSNMP Improvements by Shteryana Shopova, Userland DTrace
-	by Rui Paulo, FreeBSD jail-based virtualization by Bjoern Zeeb, DAHDI
-	FreeBSD driver port by Max Khon, and Resource Containers project by
-	Edward Tomasz Napiera&#322;a.</p>
-
-      <p>We continued our work on infrastructure projects to beef up
-	hardware for package building, network testing, etc.  This includes
-	purchasing equipment as well as managing equipment donations.</p>
-
-      <p>We are half way through the year and we have raised around
-	$48,000 towards our goal of $350,000.  Find out how to make a
-	donation at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">
-	  http://www.FreeBSDFoundation.org/donate/</a>.</p>
-
-      <p>Our semi-annual newsletter will be published soon.  Check out our
-	<a href="http://www.FreeBSDFoundation.org/" shape="rect">website</a> to find
-	out more!</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Enhancing-the-FreeBSD-TCP-Implementation" href="#Enhancing-the-FreeBSD-TCP-Implementation" id="Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/etcp09/" title="http://caia.swin.edu.au/freebsd/etcp09/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/etcp09/" title="">http://caia.swin.edu.au/freebsd/etcp09/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDfoundation.org/projects.shtml" title="http://www.FreeBSDfoundation.org/projects.shtml"></a></td><td>
-	    URL: <a href="http://www.FreeBSDfoundation.org/projects.shtml" title="">http://www.FreeBSDfoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="">http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/</a></td></tr></table><p>
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lstewart@FreeBSD.org">lstewart@FreeBSD.org</a>&gt;
-	</p>
-      <p>SIFTR was recently imported into HEAD and will be backported to
-	8-STABLE in time to be included in 8.2-RELEASE.</p>
-
-      <p>TCP reassembly queue autotuning will be ready for public testing
-	within the next week and will be committed soon after.  It too will
-	be backported to 8-STABLE after an appropriate burn in period.</p>
-    <h3>Open tasks:</h3><ol><li>Try SIFTR out and let me know if you run into any
-	problems.</li><li>Solicit external testing for and commit the reassembly queue
-	autotuning patch.</li></ol><hr /><h2><a name="libnetstat(3)" href="#libnetstat(3)" id="libnetstat(3)">libnetstat(3)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/LibNetstat" title="http://wiki.FreeBSD.org/LibNetstat">Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/LibNetstat" title="Wiki Page">http://wiki.FreeBSD.org/LibNetstat</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~pgj/libnetstat/" title="http://people.FreeBSD.org/~pgj/libnetstat/">Patches</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~pgj/libnetstat/" title="Patches">http://people.FreeBSD.org/~pgj/libnetstat/</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/soc2009/&amp;c=mGl@//depot/projects/soc2009/pgj_libstat/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/soc2009/&amp;c=mGl@//depot/projects/soc2009/pgj_libstat/?ac=83">Perforce Depot (SoC 2009)</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/soc2009/&amp;c=mGl@//depot/projects/soc2009/pgj_libstat/?ac=83" title="Perforce Depot (SoC 2009)">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/soc2009/&amp;c=mGl@//depot/projects/soc2009/pgj_libstat/?ac=83</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Aman
-	  Jassal
-	 &lt;<a href="mailto:aman@FreeBSD.org">aman@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is about creating a wrapper library to support
-	monitoring and management of networking with avoiding direct use of
-	the FreeBSD kvm(3) and sysctl(3) interfaces.  This approach would allow
-	the kernel implementation to change and monitoring applications to
-	be extended without breaking applications and requiring them to be
-	recompiled.  We decided to merge the sources from the last year's
-	Summer of Code project back to the FreeBSD src/ repository piece by
-	piece, and we have defined several phases of integration.</p>
-
-      <ul>
-	<li>Standardize the in-kernel networking statistics
-	  structures.</li>
-
-	<li>Build a sysctl(3) interface, and add export routines.</li>
-
-	<li>Add a library, libnetstat(3) to work with the exported
-	  information, and to provide further functions in order to support
-	  extracting information via kvm(3).  This library implements
-	  abstractions over the gathered data.</li>
-
-	<li>Adapt sources of the existing applications, i.e. netstat(1)
-	  and bsnmpd(1) to use the abstractions offered by the library,
-	  resulting in a cleaner and simpler code.</li>
-
-	<li>Add new applications on the top of the library, e.g.
-	  nettop(1).</li>
-      </ul>
-
-      <p>The first phase has been already posted for review.  Note that we
-	are looking for a sponsor with an src commit bit and enough time to
-	represent the effort towards the Project.</p>
-    <h3>Open tasks:</h3><ol><li>Review the sources.</li><li>Pick a task from the list, and send patches.</li><li>Comment the patches, help them to improve.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Interrupt-Threads" href="#Interrupt-Threads" id="Interrupt-Threads">Interrupt Threads</a></h2><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>For a while I have wanted to rework interrupt threads to
-	address a few issues.  The new design uses per-CPU queues of
-	interrupt handlers.  Interrupt threads are allocated by a CPU from
-	a pool and bound to that CPU while draining that CPU's queue of
-	handlers.  Non-filter handlers can also reschedule themselves at
-	the back of the current CPU's queue while executing.  Filters with
-	handlers are now always enabled and should provide a full
-	replacement for the various uses of filters with "fast"
-	taskqueues.  A new class of "manual" handlers are also available
-	which are not automatically scheduled, but are only explicitly
-	scheduled from a filter.  Thus, a filter can potentially schedule
-	multiple handlers.</p>
-
-      <p>The code has been tested on amd64, but it needs wider review
-	and testing.  I hope to start soliciting review and feedback soon
-	with the goal of getting the code into 9.0.</p>
-    <hr /><h2><a name="Jail-Based-Virtualization" href="#Jail-Based-Virtualization" id="Jail-Based-Virtualization">Jail-Based Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern" title="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern">FreeBSD Foundation Announcement</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern" title="FreeBSD Foundation Announcement">http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=Z8Q@//depot/user/bz/vimage/src/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=Z8Q@//depot/user/bz/vimage/src/?ac=83">Perforce Workspace</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=Z8Q@//depot/user/bz/vimage/src/?ac=83" title="Perforce Workspace">http://p4web.FreeBSD.org/@md=d&amp;cd=//&amp;c=Z8Q@//depot/user/bz/vimage/src/?ac=83</a></td></tr></table><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project started with some cleanup on the network stack after
-	all the import work and adjustments for virtualization to minimize
-	changes to earlier branches.  These made it into the tree already
-	and to 8-STABLE, and it will be included in the upcoming 8.1
-	release.</p>
-
-      <p>The first major task was to generalize the virtualization
-	framework, so that virtualization of further subsystems would be
-	easier and could be achieved with less duplication.</p>
-
-      <p>In addition some documentation on the virtual network stack
-	programming was written to help developers virtualizing their code.
-	The interactive kernel debugger support was improved and libjail
-	along with jls and netstat can work on core dumps now and query
-	individual jails and attached virtual network stacks.</p>
-
-      <p>The second major task was network stack teardown, a concept
-	introduced with the network stack virtualization.  The primary goal
-	was to prototype a shutdown of the (virtual) network stacks from
-	top to bottom, which means letting interfaces go last rather than
-	first.  Work in this area is still in progress and will have to
-	continue to allow long term stability and a leak and panic free
-	shutdown.</p>
-
-      <p>The work on this project had been sponsored by the FreeBSD
-	Foundation and CK Software GmbH.  Special thanks also to John
-	Baldwin and Philip Paeps for helping with review and
-	suggestions.</p>
-    <h3>Open tasks:</h3><ol><li>Merge stabilised change sets.</li><li>Work further down the network stack freeing all resources for
-	a stable, safe teardown.</li></ol><hr /><h2><a name="Kernel-Event-Timers-Infrastructure" href="#Kernel-Event-Timers-Infrastructure" id="Kernel-Event-Timers-Infrastructure">Kernel Event Timers Infrastructure</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>Modern x86 systems include four different types of event timers:
-	i8254, RTC, LAPIC, and HPET.  First three are already supported by
-	FreeBSD.  Depending on hardware and loader tunables, periodic
-	interrupts from them are used to trigger all time-based events in
-	kernel.  That code has a long history, that made it tangled and
-	at the same time limited and hard-coded.</p>
-
-      <p>New kernel event timers infrastructure was started to allow
-	different event timer hardware to be operated in uniform way and to
-	allow more features to be supported.  Work consists of three main
-	parts: writing machine-independent timer driver API and management
-	code, updating existing drivers and improving HPET driver to
-	support event timers.</p>
-
-      <p>The new driver API provides unified support for both per-CPU
-	(independent for every CPU core) and global timers in periodic and
-	one-shot modes.  Management code at this moment uses only periodic
-	mode, while one-shot mode use is planned by later tickless kernel
-	work.</p>
-
-      <p>Different kinds of timers have different capabilities and could
-	be present in hardware in different combinations.  In every
-	situation the infrastructure automatically chooses two best event
-	timers to supply system with hardclock(), statclock(), and
-	profclock() events.  If some timer is not functioning &#8212; it will be
-	replaced.  If there is no second timer &#8212; it will be emulated.
-	The administrator may affect that choice using loader tunables during
-	boot and sysctl variables in run-time (kern.eventtimer.*, and so on).</p>
-
-      <p>Most of the code was recently committed to HEAD. Now it is used
-	by i386 and amd64 architectures.</p>
-    <h3>Open tasks:</h3><ol><li>Troubleshoot possible hardware and software issues.</li><li>Port other architectures to the new infrastructure.</li><li>Implement tickless kernel, utilizing new features, such as
-	per-CPU and one-shot timers.</li></ol><hr /><h2><a name="ZFS" href="#ZFS" id="ZFS">ZFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/ZFS" title="http://wiki.FreeBSD.org/ZFS">FreeBSD ZFS Wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/ZFS" title="FreeBSD ZFS Wiki">http://wiki.FreeBSD.org/ZFS</a></td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs">Latest FreeBSD ZFS development tree</a></td><td>
-	    URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="Latest FreeBSD ZFS development tree">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs</a></td></tr></table><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Xin
-	  Li
-	 &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ZFS file system has been updated to version 15 on HEAD and
-	it will be MFC'ed to 8-STABLE around September 13th, 2010.  Work
-	is in progress on porting the recent ZFS version 26 with
-	deduplication functionality.</p>
-    <h3>Open tasks:</h3><ol><li>Fix bugs, unresolved issues and to-dos in Perforce.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">Website of the FreeBSD German Documentation Project</a></td><td>
-	    URL: <a href="http://doc.bsdgroup.de" title="Website of the FreeBSD German Documentation Project">http://doc.bsdgroup.de</a></td></tr><tr><td><a href="http://www.FreeBSD.de/mailinglists.html" title="http://www.FreeBSD.de/mailinglists.html">Mailing lists for the coordination of our work and the place where you can report bugs back to us</a></td><td>
-	    URL: <a href="http://www.FreeBSD.de/mailinglists.html" title="Mailing lists for the coordination of our work and the place where you can report bugs back to us">http://www.FreeBSD.de/mailinglists.html</a></td></tr></table><p>
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>A number of updates to the documentation were made since the
-	last status report.  We are especially grateful for the
-	contributions from external people who sent the translations.  People
-	like Fabian Ruch, who updated the porters-handbook to the latest
-	version (which had been on his to-do list for quite some time), and
-	Benjamin Lukas, who did a great job with the from-scratch
-	translation of the MAC chapter of the German handbook.  We thank
-	them both for their contributions and hope they will continue their
-	efforts to enhance the German documentation.</p>
-
-      <p>Frank B�rner was released from Benedicts mentorship and is
-	now a full committer to the German Documentation Project.  We are
-	always looking for fresh blood that is willing to be mentored by us
-	as a first step in becoming committers for the documentation project
-	themselves.</p>
-
-      <p>Johann is keeping up the German website with the latest version.
-	But we could use more translators for sections that are not fully
-	translated yet.</p>
-    <h3>Open tasks:</h3><ol><li>Read the translations and report bugs that you have found (even
-	small ones).</li><li>Translate new parts of the documentation and the
-	website.</li></ol><hr /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu/" title="http://www.FreeBSD.org/hu/">Hungarian FreeBSD web pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/hu/" title="Hungarian FreeBSD web pages">http://www.FreeBSD.org/hu/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu/" title="http://www.FreeBSD.org/doc/hu/">Hungarian FreeBSD documentation</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/hu/" title="Hungarian FreeBSD documentation">http://www.FreeBSD.org/doc/hu/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Deport for the FreeBSD Hungarian Documentation Project</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Deport for the FreeBSD Hungarian Documentation Project">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>Thanks to Katalin Konkoly, the first few chapters of the FreeBSD
-	Handbook translation have been reviewed, therefore many typos and
-	mistranslations were spotted and fixed.  Apart from this, we are
-	still keeping the existing documentation and web page translations
-	up to date, currently without plans on further work.  If you are
-	interested in helping us, or you have any comments, or requests
-	regarding the translations, do not hesitate to contact the project
-	via the email addresses mentioned in the entry.</p>
-    <h3>Open tasks:</h3><ol><li>Review translations and send feedback.</li><li>Translate release notes.</li><li>Add more article translations.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project's Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project's Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project focuses on updating the www/ja and doc/ja_JP.eucJP/
-	trees.  Since last year www/ja tree has been mostly synchronized
-	with the English counterpart and doc/ja_JP.eucJP has also been
-	updated steadily.  We are now working on FreeBSD Handbook and Porter's
-	Handbook.</p>
-    <h3>Open tasks:</h3><ol><li>More Japanese translation of FreeBSD Handbook and contents of
-	www.FreeBSD.org.</li><li>Pre-/post-commit review of the translation.</li></ol><hr /><h2><a name="The-FreeBSD-Spanish-Documentation-Project" href="#The-FreeBSD-Spanish-Documentation-Project" id="The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="http://www.FreeBSD.org/doc/es/articles/fdp-es/">Primer for translators</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="Primer for translators">http://www.FreeBSD.org/doc/es/articles/fdp-es/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Vicente
-	  Carrasco Vay�
-	 &lt;<a href="mailto:carvay@FreeBSD.org">carvay@FreeBSD.org</a>&gt;
-	</p>
-      <p>We need manpower.  Existing documentation set has not been
-	updated for quite some time because of lack of volunteers.  Current
-	members are busy with other projects and real life at the moment
-	and we have not received anything from outside contributors.  It is
-	a shame because there are lots of users in Spain and Latin-America,
-	as well.  Besides, the world's first Free Software Street has been
-	recently inaugurated in Spain.  This obviously means that there is
-	interest in free software but unfortunately, this translation
-	project is not going very well nowadays.</p>
-    <h3>Open tasks:</h3><ol><li>Review and update existing translations.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="BSD-Licensed-grep-in-Base-System" href="#BSD-Licensed-grep-in-Base-System" id="BSD-Licensed-grep-in-Base-System">BSD-Licensed grep in Base System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc/grep" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc/grep">Sources in Perforce</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc/grep" title="Sources in Perforce">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc/grep</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>A portbuild test showed that grep is basically ready to enter
-	HEAD, but there were a few failures that seem to be
-	related.  These have to be investigated and fixed before
-	committing grep to 9-CURRENT.</p>
-    <h3>Open tasks:</h3><ol><li>Investigate and fix some minor issues.</li></ol><hr /><h2><a name="BSD-Licensed-iconv-in-Base-System" href="#BSD-Licensed-iconv-in-Base-System" id="BSD-Licensed-iconv-in-Base-System">BSD-Licensed iconv in Base System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://kovesdan.org/patches/iconv-20100708.diff" title="http://kovesdan.org/patches/iconv-20100708.diff">The latest patch for the base system</a></td><td>
-	    URL: <a href="http://kovesdan.org/patches/iconv-20100708.diff" title="The latest patch for the base system">http://kovesdan.org/patches/iconv-20100708.diff</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The work has been completed and the GNU compatibility levels
-	seems to be quite high.  One exception is the fallback support.  It
-	is difficult to implement that facility in this implementation
-	because the design is somewhat different.  Probably, it will not be
-	a big problem because that functionality is not even documented in
-	the GNU version so few applications might use it.</p>
-    <h3>Open tasks:</h3><ol><li>Run a portbuild test and solve possible problems that show
-	up.</li></ol><hr /><h2><a name="FreeBSD-Services-Control-&#8212;-fsc" href="#FreeBSD-Services-Control-&#8212;-fsc" id="FreeBSD-Services-Control-&#8212;-fsc">FreeBSD Services Control &#8212; fsc</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~trhodes/fsc/" title="http://people.FreeBSD.org/~trhodes/fsc/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~trhodes/fsc/" title="">http://people.FreeBSD.org/~trhodes/fsc/</a></td></tr></table><p>
-	Contact:
-	  Tom
-	  Rhodes
-	 &lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD Services Control is a mix of binaries which integrate into
-	the rc.d system and provide for service (daemon) monitoring.  It
-	knows about signals, pidfiles, and uses very few resources.</p>
-
-      <p>The fsc daemon (fscd) runs in the background once the system has
-	started.  Services are then added to this daemon via the fscadm
-	control utility, and from there they will be monitored.  When they
-	die, depending on the reason, they will be restarted.  Certain
-	signals may be ignored (list not decided) and fscd will remove that
-	service from monitoring.  Every action is logged to the system
-	logging daemon.  Additionally, the fscadm utility may be used to
-	inquire about what services are monitored, their pidfile location,
-	and current process ID.</p>
-
-      <p>FSC provides several advantages over the third-party
-	daemontools package.  For example, fscd uses push notifications
-	instead of polling; fscd is an internal, FreeBSD-maintained software
-	package accessible to all developers, where daemontools would have
-	to be a port and require us to maintain patches; fscd could be
-	easily integrated with the current rc.d infrastructure.</p>
-
-      <p>Partially based on the ideas of daemontools and Solaris Service
-	Service Mangement Facility (SMF), this could be an extremely
-	useful tool for FreeBSD systems.</p>
-    <h3>Open tasks:</h3><ol><li>Testing.  Get feedback on how it works in various
-	environments.</li><li>Code review.</li><li>Other ideas on the rc.d integration.</li><li>Update the manual pages.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Flattened-Device-Tree-for-Embedded-FreeBSD" href="#Flattened-Device-Tree-for-Embedded-FreeBSD" id="Flattened-Device-Tree-for-Embedded-FreeBSD">Flattened Device Tree for Embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="http://wiki.FreeBSD.org/FlattenedDeviceTree">Project wiki pages</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="Project wiki pages">http://wiki.FreeBSD.org/FlattenedDeviceTree</a></td></tr></table><p>
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The purpose of this project was to provide FreeBSD with support for
-	the Flattened Device Tree (FDT) technology.  A mechanism for
-	describing computer hardware resources, which cannot be probed or
-	self enumerated, in a uniform and portable way.  The primary
-	consumers of this technology are embedded FreeBSD platforms (ARM, MIPS,
-	PowerPC), where a lot of designs are based on similar chips, but
-	have different assignment of pins, memory layout, addresses ranges,
-	interrupts routing and other resources.</p>
-
-      <p>Current state highlights:</p>
-
-      <ul>
-	<li>All code and documentation developed during the course of
-	  this project was merged with HEAD, which covers FDT support for
-	  the following platforms and systems:</li>
-
-	<li>Marvell ARM</li>
-
-	<ul>
-	  <li>DB-88F5182</li>
-
-	  <li>DB-88F5281</li>
-
-	  <li>DB-88F6281</li>
-
-	  <li>DB-78100</li>
-
-	  <li>SheevaPlug</li>
-	</ul>
-
-	<li>Freescale PowerPC</li>
-
-	<ul>
-	  <li>MPC8555CDS</li>
-
-	  <li>MPC8572DS</li>
-	</ul>
-
-	<li>The FDT infrastructure (bus drivers, helper libraries, and
-	  routines shared across architectures and platforms) allows for
-	  easier porting to new platforms or variations.  The initially
-	  supported systems offer a working example of how to migrate
-	  towards FDT approach.</li>
-      </ul>
-
-      <p>Work on this project was sponsored by the FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Improve how-to and guidelines for new adopters (how to convert
-	to FDT and so on).</li><li>Migrate more existing embedded FreeBSD platforms (ARM, MIPS) to
-	FDT approach.</li></ol><hr /><h2><a name="FreeBSD-on-the-Sony-Playstation-3" href="#FreeBSD-on-the-Sony-Playstation-3" id="FreeBSD-on-the-Sony-Playstation-3">FreeBSD on the Sony Playstation 3</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/user/nwhitehorn/ps3/" title="http://svn.FreeBSD.org/viewvc/base/user/nwhitehorn/ps3/">Playstation 3 SVN repository</a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/viewvc/base/user/nwhitehorn/ps3/" title="Playstation 3 SVN repository">http://svn.FreeBSD.org/viewvc/base/user/nwhitehorn/ps3/</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has begun to port FreeBSD/powerpc64 to the IBM Cell-based Sony
-	Playstation 3, using the OtherOS feature present on some models of
-	the console.  As of July 14, the FreeBSD boot loader is ported, and it
-	is possible to netboot a kernel, which has support for the
-	framebuffer, MMU, and device discovery.  Once work on drivers for
-	the network interface and interrupt controller is complete, it will
-	be possible to boot the console multi-user.</p>
-    <hr /><h2><a name="FreeBSD/avr32" href="#FreeBSD/avr32" id="FreeBSD/avr32">FreeBSD/avr32</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/FreeBSD/avr32" title="http://wiki.FreeBSD.org/FreeBSD/avr32"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/FreeBSD/avr32" title="">http://wiki.FreeBSD.org/FreeBSD/avr32</a></td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD/avr32 project was started by Arnar Mar Sing, and actively
-	developed by him and Ulf Lilleengen.  It successfully reached
-	single-user stage but since then has not progressed much.  At the
-	moment I am trying to get it back into shape.  So far some problems
-	with toolchain on i386 host have been fixed, buildkernel succeeds,
-	buildworld succeeds with some exceptions.  Next step would be fixing
-	pmap and bringing port back to single-user stage.</p>
-    <hr /><h2><a name="FreeBSD/powerpc64" href="#FreeBSD/powerpc64" id="FreeBSD/powerpc64">FreeBSD/powerpc64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~nwhitehorn/FreeBSD-9.0-20100715-SNAP-powerpc64/" title="http://people.FreeBSD.org/~nwhitehorn/FreeBSD-9.0-20100715-SNAP-powerpc64/">Install CDs for powerpc64</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~nwhitehorn/FreeBSD-9.0-20100715-SNAP-powerpc64/" title="Install CDs for powerpc64">http://people.FreeBSD.org/~nwhitehorn/FreeBSD-9.0-20100715-SNAP-powerpc64/</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>On July 13, FreeBSD/powerpc64 was integrated into HEAD.  This
-	provides support for fully 64-bit operation on 64-bit PowerPC
-	machines conforming to the Book-S specification, including the
-	PowerPC 970, Cell, and POWER4-7.  Hardware support is currently
-	limited to Apple machines, although this should expand in the near
-	future.</p>
-
-      <p>Currently supported hardware:</p>
-
-      <ul>
-	<li>Apple Xserve G5</li>
-
-	<li>Apple Power Macintosh G5</li>
-
-	<li>Apple iMac G5</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report some issues with cas(4) have been
-	fixed, allowing it to work with Sun GigaSwift Ethernet 1.0 MMF
-	cards (Cassini Kuheen, part no. 501-5524) as well as the on-board
-	interfaces of Sun Fire B100s server blades (for the Sun Fire
-	B1600 platform).</p>
-
-      <p>Support for Fujitsu (Siemens) PRIMEPOWER 250 based on SPARC64
-	V CPUs has been added.  PRIMEPOWER 450, 650, and 850 likely also
-	work but have not been tested.  This also means that the building
-	blocks for support of machines based on SPARC64 VI and VII CPUs
-	like the Fujitsu/Sun SPARC Enterprise Mx000 series are now in
-	place, but they need testing as well.</p>
-
-      <p>The problems with Schizo version 7 bridges (actually the
-	firmware of these machines) triggering panics during boot finally
-	should be solved.</p>
-
-      <p>The work on getting Sun Fire V1280 supported has been stalled
-	due to access to such machines no longer being available.</p>
-
-      <p>The above mentioned improvements are/will be available in FreeBSD
-	8.1-RELEASE and 7.4-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>Access to machines based on SPARC64 VI and VII CPUs, like
-	the Fujitsu/Sun SPARC Enterprise Mx000 series would be
-	appreciated.</li><li>Someone adding support for 64-bit SPARC V9 to Clang/LLVM,
-	and getting it on par with GCC would be appreciated.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium-Web-Browser" href="#Chromium-Web-Browser" id="Chromium-Web-Browser">Chromium Web Browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://chromium.hybridsource.org" title="http://chromium.hybridsource.org">Main chromium site</a></td><td>
-	    URL: <a href="http://chromium.hybridsource.org" title="Main chromium site">http://chromium.hybridsource.org</a></td></tr><tr><td><a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=146302" title="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=146302">PR for chromium port</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=146302" title="PR for chromium port">http://www.FreeBSD.org/cgi/query-pr.cgi?pr=146302</a></td></tr></table><p>
-	Contact:
-	  Ruben
-	 &lt;<a href="mailto:chromium@hybridsource.org">chromium@hybridsource.org</a>&gt;
-	</p>
-      <p>Chromium is a Webkit-based web browser that is largely
-	BSD-licensed.  It works very well on FreeBSD and supports new features
-	like HTML 5 video.  This effort uses a new
-	hybrid-source model, where the FreeBSD patches are largely kept closed
-	for a limited time.  I submitted Chromium to ports a couple of
-	months ago and recently updated the submission to the stable 5.0.375
-	branch.  The port is ready to be committed pending final legal
-	approval by the FreeBSD Foundation.  Further work remains to port
-	Chromium to FreeBSD completely, such as porting the task manager fully
-	and making sure extensions work properly.</p>
-    <hr /><h2><a name="FreeBSD-Haskell" href="#FreeBSD-Haskell" id="FreeBSD-Haskell">FreeBSD Haskell</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Haskell" title="http://wiki.FreeBSD.org/Haskell">Wiki Page of the Project</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Haskell" title="Wiki Page of the Project">http://wiki.FreeBSD.org/Haskell</a></td></tr><tr><td><a href="http://www.FreeBSD.org/ports/haskell.html" title="http://www.FreeBSD.org/ports/haskell.html">FreeBSD Haskell Ports</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/haskell.html" title="FreeBSD Haskell Ports">http://www.FreeBSD.org/ports/haskell.html</a></td></tr><tr><td><a href="http://www.haskell.org/mailman/listinfo/freebsd-haskell" title="http://www.haskell.org/mailman/listinfo/freebsd-haskell">The freebsd-haskell Mailing List</a></td><td>
-	    URL: <a href="http://www.haskell.org/mailman/listinfo/freebsd-haskell" title="The freebsd-haskell Mailing List">http://www.haskell.org/mailman/listinfo/freebsd-haskell</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Giuseppe
-	  Pilichi
-	 &lt;<a href="mailto:jacula@FreeBSD.org">jacula@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  Shukla
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>Our efforts on porting the generalized, general-purpose purely
-	functional programming language, <a href="http://www.haskell.org/" shape="rect">Haskell</a> has rallied, since
-	two new committers, Giuseppe Pilichi and Ashish
-	Shukla joined recently, forming the FreeBSD Haskell Team.
-	Over the last months, FreeBSD/i386 and FreeBSD/amd64 have become Tier-1
-	platforms, featuring officially supported vanilla binary
-	distributions for the <a href="http://www.haskell.org/ghc/" shape="rect">Glasgow Haskell Compiler</a>
-	starting from version 6.12.1.  We introduced a unified ports
-	infrastructure for Haskell Cabal ports, which also makes possible
-	the <a href="http://code.haskell.org/~pgj/projects/hsporter" shape="rect">direct
-	  translation</a> of Cabal package descriptions to FreeBSD ports.
-	The number of Haskell package ports increases steadily.</p>
-    <h3>Open tasks:</h3><ol><li>Improve support for Haskell Cabal packages and their
-	translation.</li><li>Create a port for Haskell Platform.</li><li>Add more Haskell package ports.</li><li>Test and send feedback.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td>
-	    URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/"></a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com/" title="">http://tinderbox.marcuscom.com/</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>A significant part of quarter two was spent coordinating efforts
-	for inclusion of Xorg�7.5, KDE�4, GNOME�2, plus preparation of ports
-	for the 8.1 release process.  Due to the success of enforcing
-	Feature Safe ports commits during 7.3-RELEASE, it was continued
-	for the recent src/ freeze.</p>
-
-      <p>The port count is approaching 22,000 ports.  The open PR count
-	currently floats at about 1200 entries.</p>
-
-      <p>Since the last report, we added four new committers, and had two
-	old committers rejoin us.</p>
-
-      <p>The Ports Management Team is very grateful to the FreeBSD
-	Foundation for sponsoring two new head nodes for the ports building
-	cluster, pointyhat.  Each of the new head nodes has a larger
-	capacity, both with regard to performance but also in amount of
-	space available for the staging areas, allowing for faster, and
-	thus more, build cycles.  Additionally, having two head nodes will
-	allow us to dedicate one of them for building production-ready
-	binary packages, adding predicability for our users to when what
-	types of packages are available for installation, and dedicate the
-	other for regression testing of large port updates, ports
-	infrastructure improvements, the cluster scheduling code, and FreeBSD
-	itself.  Over the last few weeks, Mark Linimon has been working hard
-	to get the first of the two new nodes online and has already
-	completed its first package build.  This has involved a substantial
-	rework of our custom codebase.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports
-	updates.  Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>ale: Update of math/gmp.</li>
-	<li>delphij: Changes to Mk/bsd.ldap.mk.</li>
-	<li>gahr: Inclusion of USE_GL=glew.</li>
-	<li>pgollucci: Changes to Mk/bsd.*apache.mk plus updates to devel/apr
-	and www/apache*.</li>
-	<li>Testing of x11/xorg, x11/gnome2, x11/kde4, and
-	lang/mono</li>
-	<li>A test run make fetch run.</li>
-	<li>A test run for devel/gettext.</li>
-	<li>mm: Inclusion of USE_XZ.</li>
-	<li>ale: Request to switch default mysql from 5.0-EOL to
-	  5.1-GA.</li>
-      </ul>
-
-      <p>alepulver's Licensing Framework Summer of Code project has made
-	it into the tree and the Port Management Team is currently
-	assessing the fallout and it will come up with guidelines and
-	documentation in due time.</p>
-    <h3>Open tasks:</h3><ol><li>Looking for help fixing <a href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent" shape="rect">ports
-	  broken on 9-CURRENT</a>.</li><li>Looking for help with <a href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures" shape="rect">
-	  Tier-2 architectures</a>.</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing, and closing.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSD-Day@2010" href="#BSD-Day@2010" id="BSD-Day@2010">BSD-Day@2010</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/BSDDay_2010" title="http://wiki.freebsd.org/BSDDay_2010"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/BSDDay_2010" title="">http://wiki.freebsd.org/BSDDay_2010</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The purpose of this one-day event is to gather Central European
-	developers of today's open-source BSD systems to popularize
-	their work and their organization, and to provide an interface
-	for real-life communication.  There are no formalities, no
-	papers, and no registration or participation fee.  However the
-	invited developers are encouraged to give a talk on their
-	favorite BSD-related topic or join the live forum, then have a
-	beer with the other folks around.  The goal is to motivate
-	potential future developers and users, especially undergraduate
-	university students to work with BSD systems.</p>
-
-      <p>This year's BSD-Day will be held in Budapest, Hungary at
-	E�tv�s Lor�nd University, Faculty of Informatics
-	on November 20, 2010.</p>
-    <h3>Open tasks:</h3><ol><li>Apply as a developer, we are still looking for BSD people in
-	the area.</li></ol><hr /><h2><a name="BSDCan" href="#BSDCan" id="BSDCan">BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.BSDCan.org/2010/" title="http://www.BSDCan.org/2010/">BSDCan 2010</a></td><td>
-	    URL: <a href="http://www.BSDCan.org/2010/" title="BSDCan 2010">http://www.BSDCan.org/2010/</a></td></tr></table><p>
-	Contact:
-	  Dan
-	  Langille
-	 &lt;<a href="mailto:dvl@FreeBSD.org">dvl@FreeBSD.org</a>&gt;
-	</p>
-      <p>BSDCan 2010 was our 7th conference.  As has become the custom,
-	a FreeBSD developer summit was held in the two days before the
-	conference.  Record numbers attended the Dev Summit which carried
-	over into the conference proper.  It was great to see
-	representatives from so many more companies.  I saw many great
-	ideas take root and the start of cooperation on several
-	projects.</p>
-
-      <p>The talks during the Dev Summit are beginning to attract a wider
-	audience, and we have been talking about opening this up to the
-	general audience by creating a fourth track at BSDCan 2011.</p>
-
-      <p>As impossible as it sounds, each year has seen an increase in
-	the quality of talks and the number of proposals submitted.</p>
-    <h3>Open tasks:</h3><ol><li>I need people to help with various pre-conference tasks:
-	website updates, booking travel, etc.</li></ol><hr /><h2><a name="meetBSD-2010-&#8212;-The-BSD-Conference" href="#meetBSD-2010-&#8212;-The-BSD-Conference" id="meetBSD-2010-&#8212;-The-BSD-Conference">meetBSD 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.meetbsd.org" title="http://www.meetbsd.org"></a></td><td>
-	    URL: <a href="http://www.meetbsd.org" title="">http://www.meetbsd.org</a></td></tr><tr><td><a href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day1#" title="http://picasaweb.google.com/meetbsd/MeetBSD2010Day1#"></a></td><td>
-	    URL: <a href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day1#" title="">http://picasaweb.google.com/meetbsd/MeetBSD2010Day1#</a></td></tr><tr><td><a href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day2#" title="http://picasaweb.google.com/meetbsd/MeetBSD2010Day2#"></a></td><td>
-	    URL: <a href="http://picasaweb.google.com/meetbsd/MeetBSD2010Day2#" title="">http://picasaweb.google.com/meetbsd/MeetBSD2010Day2#</a></td></tr><tr><td><a href="http://picasaweb.google.com/meetbsd/MeetBSD2010SocialEvent#" title="http://picasaweb.google.com/meetbsd/MeetBSD2010SocialEvent#"></a></td><td>
-	    URL: <a href="http://picasaweb.google.com/meetbsd/MeetBSD2010SocialEvent#" title="">http://picasaweb.google.com/meetbsd/MeetBSD2010SocialEvent#</a></td></tr></table><p>
-	Contact:
-	  meetBSD
-	  Information
-	 &lt;<a href="mailto:info@meetbsd.org">info@meetbsd.org</a>&gt;
-	</p>
-      <p>meetBSD 2010 took place on July 2�-�3 in Krakow, Poland at the
-	Faculty of Mathematics and Computer Science building of the
-	Jagiellonian University.</p>
-
-      <p>The gathering was a much successful event which brought together
-	developers, contributors, and users of the BSD systems from around the
-	world.  We had many interesting presentations, of various character and
-	appeal for the diversified audience.</p>
-
-      <p>Attendees had a chance for taking the BSD Certification exam during
-	the conference, as well as the advantage of face to face side
-	conversations and discussions, which continued long during the social
-	event on Friday night!</p>
-
-      <p>The conference presentation slides are already available for
-	download.  Video recordings edition is being finalized, and their
-	publication is expected shortly.</p>
-
-      <p>We hope you enjoyed the event and had great time in Krakow.  See you
-	again soon!</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2010-07-2010-09.html b/website/content/en/status/report-2010-07-2010-09.html
deleted file mode 100644
index 1ce47a640e..0000000000
--- a/website/content/en/status/report-2010-07-2010-09.html
+++ /dev/null
@@ -1,1722 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between July and
-      September 2010.  It is the third of the four reports planned for
-      2010.  During this period, we were victims of one
-      of the biggest BSD events of the year &#8212; EuroBSDCon.
-      We hope that the ones of you who have been able to attend it
-      have enjoyed your stay.  Another good news is that work on the
-      new minor versions of FreeBSD, 7.4 and 8.2, is progressing well.</p><p>This report, with 55 entries, is the longest report in
-      the whole history and shows a good condition of the FreeBSD
-      community.</p><p>Thanks to all the reporters for the excellent work!  We hope you
-      enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between October and December 2010 is January 15th, 2011.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Atheros-AR913x-SoC-Support">Atheros AR913x SoC Support</a></li><li><a href="#Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch">Binary Package Patch Infrastructure &#8212; pkg_patch</a></li><li><a href="#ExtFS-Status-Report">ExtFS Status Report</a></li><li><a href="#Packet-Capturing-Stack-&#8212;-ringmap">Packet Capturing Stack &#8212; ringmap</a></li><li><a href="#Registration-of-Optional-Kernel-Subsystems-via-sysctl">Registration of Optional Kernel Subsystems via
-      sysctl</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BSD#-Project">BSD# Project</a></li><li><a href="#BSNMP-Enhancements">BSNMP Enhancements</a></li><li><a href="#Capsicum:-Practical-Capabilities-for-UNIX">Capsicum: Practical Capabilities for UNIX</a></li><li><a href="#Clang-Replacing-GCC-in-the-Base-System">Clang Replacing GCC in the Base System</a></li><li><a href="#DAHDI/FreeBSD-Project">DAHDI/FreeBSD Project</a></li><li><a href="#External-Toolchain-Support">External Toolchain Support</a></li><li><a href="#GELI-Additions">GELI Additions</a></li><li><a href="#gptboot-Improvements">gptboot Improvements</a></li><li><a href="#HAST-(Highly-Available-Storage)-Improvements">HAST (Highly Available Storage) Improvements</a></li><li><a href="#Kernel-level-Stacked-Cryptographic-File-System-&#8212;-PEFS">Kernel-level Stacked Cryptographic File System &#8212;
-      PEFS</a></li><li><a href="#pc-sysinstall">pc-sysinstall</a></li><li><a href="#Target-Big-Endian-Must-Die">Target Big Endian Must Die</a></li><li><a href="#Userland-DTrace">Userland DTrace</a></li><li><a href="#V4L-Support-in-Linux-Emulator">V4L Support in Linux Emulator</a></li><li><a href="#ZFSv28-is-Ready-for-Wider-Testing">ZFSv28 is Ready for Wider Testing</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-KDE-Team">FreeBSD KDE Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></li><li><a href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></li><li><a href="#Syncing-pf(4)-with-OpenBSD�4.5">Syncing pf(4) with OpenBSD�4.5</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Kernel-Event-Timers-Infrastructure">Kernel Event Timers Infrastructure</a></li><li><a href="#Netdump-Support">Netdump Support</a></li><li><a href="#Resource-Containers">Resource Containers</a></li><li><a href="#USB-Stack">USB Stack</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#mandoc/mdocml-&#8212;-groff-Replacement-for-Rendering-Manual-Pages-in-FreeBSD">mandoc/mdocml &#8212; groff Replacement for Rendering Manual
-      Pages in FreeBSD</a></li><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li><li><a href="#Web-Feeds-for-UPDATING-Files">Web Feeds for UPDATING Files</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></li><li><a href="#Updating-Base-Tools-to-Accommodate-Ports-Requirements">Updating Base Tools to Accommodate Ports
-      Requirements</a></li><li><a href="#xz-Compression-for-Packages-and-Log-Files">xz Compression for Packages and Log Files</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Bringing-up-ARM-to-FreeBSD-Tree">Bringing up ARM to FreeBSD Tree</a></li><li><a href="#FreeBSD-on-the-Playstation-3">FreeBSD on the Playstation 3</a></li><li><a href="#FreeBSD/mips-on-Octeon">FreeBSD/mips on Octeon</a></li><li><a href="#FreeBSD/mips-Ralink-RT3052F/Broadcom-BCM5354">FreeBSD/mips Ralink RT3052F/Broadcom BCM5354</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium-Web-Browser">Chromium Web Browser</a></li><li><a href="#OpenAFS-Port">OpenAFS Port</a></li><li><a href="#pkg_upgrade-(sysutils/bsdadminscripts)">pkg_upgrade (sysutils/bsdadminscripts)</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Ports-Distfile-and-WWW-Checker">Ports Distfile and WWW Checker</a></li><li><a href="#Valgrind-Port">Valgrind Port</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSD-Day@2010">BSD-Day@2010</a></li><li><a href="#EuroBSDCon-2010">EuroBSDCon 2010</a></li><li><a href="#EuroBSDCon-2011">EuroBSDCon 2011</a></li><li><a href="#FreeBSD-Developer-Summit,-Karlsruhe">FreeBSD Developer Summit, Karlsruhe</a></li><li><a href="#FreeBSD-Developer-Summit,-meetBSD-California-2010">FreeBSD Developer Summit, meetBSD California 2010</a></li><li><a href="#PC-BSD">PC-BSD</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Atheros-AR913x-SoC-Support" href="#Atheros-AR913x-SoC-Support" id="Atheros-AR913x-SoC-Support">Atheros AR913x SoC Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff" title="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff">(The Atheros hackery will eventually live here)</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff" title="(The Atheros hackery will eventually live here)">http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosHalStuff" title="http://wiki.FreeBSD.org/AdrianChadd/AtherosHalStuff">Atheros wireless device work</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosHalStuff" title="Atheros wireless device work">http://wiki.FreeBSD.org/AdrianChadd/AtherosHalStuff</a></td></tr></table><p>
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@FreeBSD.org">adrian@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD-CURRENT runs on the AR9132 SoC.  Minor platform-specific
-	tweaks are needed to use it on a given piece of hardware (eg.,
-	where in flash the Ethernet MAC address is stored.)  The AR910x
-	wireless MAC/PHY is supported.  The only available test platform
-	uses a 2.4GHz radio; 5GHz 11a mode has not been tested.  As with
-	other Atheros chipset support in FreeBSD, 11n support is not yet
-	finished.  The current development platform is the TP-Link
-	TP-WN1043ND 802.11n wireless bridge/router.  It is currently being
-	successfully used as a 11bg access point.</p>
-    <h3>Open tasks:</h3><ol><li>USB support is currently not functional.</li><li>There is currently no support for the Realtek Gigabit
-	switch/PHY chip.  This is being worked on.</li></ol><hr /><h2><a name="Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch" href="#Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch" id="Binary-Package-Patch-Infrastructure-&#8212;-pkg_patch">Binary Package Patch Infrastructure &#8212; pkg_patch</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/IvanVoras/pkg_patch" title="http://wiki.FreeBSD.org/IvanVoras/pkg_patch"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/IvanVoras/pkg_patch" title="">http://wiki.FreeBSD.org/IvanVoras/pkg_patch</a></td></tr></table><p>
-	Contact:
-	  Ivan
-	  Voras
-	 &lt;<a href="mailto:ivoras@FreeBSD.org">ivoras@FreeBSD.org</a>&gt;
-	</p>
-      <p>pkg_patch is a tool meant to be used with the rest of the
-	pkg_* utilities whose job is to create and apply binary patches
-	to FreeBSD package archives.  The SoC project was successfully
-	completed but there are some open issues about the integration of
-	the tool in the FreeBSD system.  Some changes are necessary to the
-	port/patch infrastructure to support the "update" mode instead of
-	"remove+add".</p>
-    <h3>Open tasks:</h3><ol><li>Solve pending issues about the ports install/upgrade
-	workflow, probably within the <a href="http://wiki.FreeBSD.org/Pkg_install2_specs" shape="rect">pkg_install2</a>
-	effort.</li></ol><hr /><h2><a name="ExtFS-Status-Report" href="#ExtFS-Status-Report" id="ExtFS-Status-Report">ExtFS Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2010ZhengLiu" title="http://wiki.FreeBSD.org/SOC2010ZhengLiu">Project wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2010ZhengLiu" title="Project wiki">http://wiki.FreeBSD.org/SOC2010ZhengLiu</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83">pre-allocation</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83" title="pre-allocation">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83">ext4 read-only mode</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83" title="ext4 read-only mode">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83</a></td></tr></table><p>
-	Contact:
-	  Zheng
-	  Liu
-	 &lt;<a href="mailto:gnehzuil@gmail.com">gnehzuil@gmail.com</a>&gt;
-	</p>
-      <p>This project has two goals: pre-allocation algorithm for ext2fs
-	and ext4 read-only mode.  Aim of the pre-allocation algorithm is
-	to implement a reservation window mechanism.  This mechanism has
-	been implemented and a patch have been submitted.  The aim of
-	ext4 read-only mode is to make it possible to read ext4 file
-	systems in read-only mode when the disk is formatted with
-	default features.  Until now it can read data from ext4 file
-	systems with default features in read-only mode.  A patch has
-	been submitted a patch to the freebsd-fs mailing list and there
-	is a new kernel module, called ext4fs, is under development for
-	it.</p>
-    <h3>Open tasks:</h3><ol><li>More testing of the pre-allocation algorithm.</li></ol><hr /><h2><a name="Packet-Capturing-Stack-&#8212;-ringmap" href="#Packet-Capturing-Stack-&#8212;-ringmap" id="Packet-Capturing-Stack-&#8212;-ringmap">Packet Capturing Stack &#8212; ringmap</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/ringmap/" title="http://code.google.com/p/ringmap/">Project-Page on Google Code</a></td><td>
-	    URL: <a href="http://code.google.com/p/ringmap/" title="Project-Page on Google Code">http://code.google.com/p/ringmap/</a></td></tr><tr><td><a href="http://ringmap.googlecode.com/files/ringmap_slides.pdf" title="http://ringmap.googlecode.com/files/ringmap_slides.pdf">Slides</a></td><td>
-	    URL: <a href="http://ringmap.googlecode.com/files/ringmap_slides.pdf" title="Slides">http://ringmap.googlecode.com/files/ringmap_slides.pdf</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/AlexandreFiveg" title="http://wiki.FreeBSD.org/AlexandreFiveg">Wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/AlexandreFiveg" title="Wiki">http://wiki.FreeBSD.org/AlexandreFiveg</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Fiveg
-	 &lt;<a href="mailto:afiveg@FreeBSD.org">afiveg@FreeBSD.org</a>&gt;
-	</p>
-      <p>Ringmap is a complete FreeBSD packet capturing stack specialized for
-	very high-speed networks.  The goal of this project is to develop the
-	software for efficient packet capturing and integrate it with the
-	generic network drivers and libpcap.</p>
-
-      <p>Current Status:</p>
-
-      <ul>
-	<li>Integrated with the lem driver.  Intel network controllers:
-	  8254X are supported.</li>
-
-	<li>Packet filtering using BPF in both kernel and user space.</li>
-
-	<li>Partly integrated with ixgbe driver for 10Gb capturing.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Support for hardware timestamping.</li><li>Writing packets to the disc from within the kernel.</li><li>Multiqueue support.</li><li>Extending the "ringmap" for packet transmission.</li></ol><hr /><h2><a name="Registration-of-Optional-Kernel-Subsystems-via-sysctl" href="#Registration-of-Optional-Kernel-Subsystems-via-sysctl" id="Registration-of-Optional-Kernel-Subsystems-via-sysctl">Registration of Optional Kernel Subsystems via
-      sysctl</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/freebsd/t127230759508" title="http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/freebsd/t127230759508">Project description on GSoC website</a></td><td>
-	    URL: <a href="http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/freebsd/t127230759508" title="Project description on GSoC website">http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/freebsd/t127230759508</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=view&amp;target=kibab_sysctlreg.pdf" title="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=view&amp;target=kibab_sysctlreg.pdf">Slides (from FreeBSD DevSummit in Karlsruhe)</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=view&amp;target=kibab_sysctlreg.pdf" title="Slides (from FreeBSD DevSummit in Karlsruhe)">http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=view&amp;target=kibab_sysctlreg.pdf</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:kibab@FreeBSD.org">kibab@FreeBSD.org</a>&gt;
-	</p>
-      <p>All work is now in Perforce.  Rich set of features is added to
-	the kernel, userland tools and libc modifications are ready,
-	documentation is ready.</p>
-    <h3>Open tasks:</h3><ol><li>Documentation review.</li><li>Presentation of feature set on the various mailing
-	lists.</li><li>Committing to -CURRENT, possibly merging to stable branches
-	(changes do not break ABI/KBI).</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BSD#-Project" href="#BSD#-Project" id="BSD#-Project">BSD# Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/bsd-sharp/" title="http://code.google.com/p/bsd-sharp/">The BSD# project on Google-code</a></td><td>
-	    URL: <a href="http://code.google.com/p/bsd-sharp/" title="The BSD# project on Google-code">http://code.google.com/p/bsd-sharp/</a></td></tr><tr><td><a href="http://www.mono-project.org/" title="http://www.mono-project.org/">Mono (Open source .Net Development Framework)</a></td><td>
-	    URL: <a href="http://www.mono-project.org/" title="Mono (Open source .Net Development Framework)">http://www.mono-project.org/</a></td></tr></table><p>
-	Contact:
-	  Romain
-	  Tarti�re
-	 &lt;<a href="mailto:romain@FreeBSD.org">romain@FreeBSD.org</a>&gt;
-	</p>
-      <p>The BSD# Project is devoted to porting the Mono .NET framework
-	and applications to the FreeBSD operating system.</p>
-
-      <p>Mono 2.8 has been released a few days ago and is already
-	available in the BSD# repository.  The update breaks a few ports
-	so the lang/mono update in the FreeBSD ports tree will be delayed
-	until those programs are fixed for a smoother update
-	experience.</p>
-
-      <p>Work is in progress to include some long-awaited ports such as
-	deskutils/gnome-do but they require a lot of testing and hacking
-	because they have clearly been designed to run on GNU/Linux and
-	portability has never been a priority (which is quite amusing if
-	you consider portability is the main reason to be for mono).</p>
-    <h3>Open tasks:</h3><ol><li>If you have some time, test mono ports and send
-	feedback.</li><li>If you have more time, join the BSD# Team! There are many
-	ways to help out!</li><li>Currently low priority, some mono hackers who do not use
-	FreeBSD would be interested in a debug live-image of FreeBSD to help us
-	diagnose and fix bugs more effectively.</li></ol><hr /><h2><a name="BSNMP-Enhancements" href="#BSNMP-Enhancements" id="BSNMP-Enhancements">BSNMP Enhancements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/CategorySNMP" title="http://wiki.FreeBSD.org/CategorySNMP">bsnmpd(1)-related pages on FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/CategorySNMP" title="bsnmpd(1)-related pages on FreeBSD wiki">http://wiki.FreeBSD.org/CategorySNMP</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/snmp_ieee80211&amp;HIDEDEL=NO" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/snmp_ieee80211&amp;HIDEDEL=NO">snmp_wlan(3) P4 code tree</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/snmp_ieee80211&amp;HIDEDEL=NO" title="snmp_wlan(3) P4 code tree">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/snmp_ieee80211&amp;HIDEDEL=NO</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/syrinx_bsnmpv3&amp;HIDEDEL=NO" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/syrinx_bsnmpv3&amp;HIDEDEL=NO">SNMPv3 for bnmspd(1) P4 code tree</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/syrinx_bsnmpv3&amp;HIDEDEL=NO" title="SNMPv3 for bnmspd(1) P4 code tree">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/syrinx/syrinx_bsnmpv3&amp;HIDEDEL=NO</a></td></tr></table><p>
-	Contact:
-	  Shteryana
-	  Shopova
-	 &lt;<a href="mailto:syrinx@FreeBSD.org">syrinx@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Philip
-	  Paeps
-	 &lt;<a href="mailto:philip@FreeBSD.org">philip@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the previous few months several additions were
-	developed to FreeBSD's built-in SNMP daemon &#8212; bsnmpd(1).</p>
-
-      <p>First a snmp_wlan(3) module was developed that allows
-	monitoring and configuration of wlan(4) interfaces operating in
-	various modes, including statistics, attached/neighboring
-	station information, MAC access control entries and mesh routing
-	information.  The module's code was submitted in SVN and is now
-	a part of the FreeBSD base system.</p>
-
-      <p>Next, SNMPv3 authentication and encryption support were added
-	to bsnmplib(3), bsnmpd(1) and bsnmptools (which are available
-	via the ports system currently).  The message digest and cipher
-	calculation calls use the implementation of the relevant
-	cryptographic algorithm implementation in OpenSSL's crypto(3)
-	library.  bsnmpd(1) may still optionally be compiled without the
-	crypto(3) library, in which case only unauthenticated plain-text
-	SNMPv3 PDUs may be processed.</p>
-
-      <p>In addition, a snmp_usm(3) module was developed that is used to
-	configure SNMPv3 users parameters (name, authentication &amp;
-	encryption algorithms used and relevant keys, etc.) into
-	bsnmpd(1) as per RFC 3414.</p>
-
-      <p>Finally, a snmp_vacm(3) module was developed that allows
-	configuration of view-based access control as per RFC 3415, and
-	relevant checks are made by bsnmpd(1) that allow or restrict
-	access to specific SNMPv1/SNMPv2 communities or SNMPv3 users to
-	certain MIB subtrees as per the configuration in the
-	snmp_vacm(3) module.  If none of the SNMPv3-related modules is
-	loaded, bsnmpd(1) preserves its current behavior with
-	SNMPv1/SNMPv2c PDUs.</p>
-
-      <p>This work is being funded by the FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Update Wiki Page to reflect latest work and document proper
-	use.</li><li>Finish cleanup and have it reviewed.</li><li>More extensive user testing.</li></ol><hr /><h2><a name="Capsicum:-Practical-Capabilities-for-UNIX" href="#Capsicum:-Practical-Capabilities-for-UNIX" id="Capsicum:-Practical-Capabilities-for-UNIX">Capsicum: Practical Capabilities for UNIX</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cl.cam.ac.uk/research/security/capsicum/" title="http://www.cl.cam.ac.uk/research/security/capsicum/">Capsicum: practical capabilities for UNIX</a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/research/security/capsicum/" title="Capsicum: practical capabilities for UNIX">http://www.cl.cam.ac.uk/research/security/capsicum/</a></td></tr><tr><td><a href="https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss" title="https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss">Capsicum project mailing list</a></td><td>
-	    URL: <a href="https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss" title="Capsicum project mailing list">https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss</a></td></tr><tr><td><a href="http://www.cl.cam.ac.uk/research/security/capsicum/papers/2010usenix-security-capsicum-website.pdf" title="http://www.cl.cam.ac.uk/research/security/capsicum/papers/2010usenix-security-capsicum-website.pdf">USENIX Security 2010 paper on Capsicum</a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/research/security/capsicum/papers/2010usenix-security-capsicum-website.pdf" title="USENIX Security 2010 paper on Capsicum">http://www.cl.cam.ac.uk/research/security/capsicum/papers/2010usenix-security-capsicum-website.pdf</a></td></tr></table><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jonathan
-	  Anderson
-	 &lt;<a href="mailto:anderson@FreeBSD.org">anderson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ben
-	  Laurie
-	 &lt;<a href="mailto:benl@google.com">benl@google.com</a>&gt;
-	<br />
-	Contact:
-	  Kris
-	   Kennaway
-	 &lt;<a href="mailto:kennaway@google.com">kennaway@google.com</a>&gt;
-	</p>
-      <p>Capsicum is a lightweight OS capability and sandbox framework
-	developed at the University of Cambridge Computer Laboratory,
-	supported by a grant from Google.  Capsicum extends the POSIX API,
-	providing several new OS primitives to support object-capability
-	security on UNIX-like operating systems: capabilities, a new
-	sandboxed capability mode for processes, anonymous shared memory
-	objects, process descriptors, and a modified C runtime able to
-	support distributed applications within sandboxes.  Capsicum
-	has been prototyped on FreeBSD -CURRENT, with a 8-STABLE
-	backport.</p>
-
-      <p>Capsicum is intended to supplement existing system-centric
-	mandatory access control protections by providing an
-	application-centric protection model, which better supports
-	compartmentalised user programs that set up one (or many)
-	sandboxes to process untrustworthy data in.  A number of
-	applications, from tcpdump to the Chromium web browser, have been
-	modified to use sandboxing to confine risky activities such as
-	the parsing of untrusted packets and HTML/JavaScript
-	rendering.</p>
-
-      <p>We plan to begin merging the core Capsicum kernel features
-	to FreeBSD -CURRENT in November/December 2010 once a number of
-	known problems have been resolved.  Following a KBI analysis, we
-	will consider merging our 8-STABLE backport to Subversion.  For
-	the time being, and while APIs stabilise, we plan to distribute
-	the Capsicum libraries via ports.  However, simply having the
-	kernel features in place is sufficient to support sandboxing in
-	tcpdump and Chromium.</p>
-
-      <p>The Capsicum paper by Robert Watson / Jonathan Anderson
-	(Cambridge) and Ben Laurie / Kris Kennaway (Google) won a best
-	paper award at the 2010 USENIX Security Symposium!</p>
-    <h3>Open tasks:</h3><ol><li>More aggressively test (and as needed, fix) possible UNIX
-	domain socket garbage collector interactions with Capsicum.</li><li>Using results of our recent model checking analysis of the
-	namei() sandboxing approach, make robustness improvements.</li><li>Merge to FreeBSD -CURRENT in November/December.</li><li>KBI analysis for possible 8-STABLE merge.</li><li>Convert more applications to use Capsicum sandboxing!</li></ol><hr /><h2><a name="Clang-Replacing-GCC-in-the-Base-System" href="#Clang-Replacing-GCC-in-the-Base-System" id="Clang-Replacing-GCC-in-the-Base-System">Clang Replacing GCC in the Base System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Pawel
-	  Worach
-	 &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Dimitry
-	  Andric
-	 &lt;<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>&gt;
-	</p>
-      <p>We recently imported the 2.8 release of Clang into -CURRENT.
-	This release contains many new features and improvements.  The
-	integrated assembler ships with this version, but it is not
-	ready for general use yet.</p>
-
-      <p>Since r212979, all necessary changes have been committed to be
-	able to build world with Clang, at least on amd64 and i386.  It
-	can also be installed and run, and we are now starting the
-	process of shaking out the inevitable bugs.</p>
-
-      <p>Because LLVM and Clang are still being improved continuously,
-	we want to import new versions regularly, approximately every two
-	months, to gain access to new features, bug fixes and performance
-	improvements.</p>
-
-      <p>There is also an effort on behalf of the ports people, to make
-	as many ports as possible compile and run properly with Clang.
-	Most of the time, this means fixing the incorrect assumption that
-	gcc is the only existing compiler, but sometimes more complicated
-	issues pop up.  Help in this area is greatly appreciated.</p>
-    <h3>Open tasks:</h3><ol><li>Importing new Clang snapshots fairly regularly
-	(approximately bi-monthly).</li><li>Seeing if Clang can be used to build world for ARM
-	(volunteers and ARM experts wanted).</li><li>Fixing as many ports as possible to build with Clang.</li><li>Running periodical ports exp builds with Clang (on amd64
-	and i386), for example once a month.</li></ol><hr /><h2><a name="DAHDI/FreeBSD-Project" href="#DAHDI/FreeBSD-Project" id="DAHDI/FreeBSD-Project">DAHDI/FreeBSD Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.asterisk.org/dahdi/" title="http://www.asterisk.org/dahdi/"></a></td><td>
-	    URL: <a href="http://www.asterisk.org/dahdi/" title="">http://www.asterisk.org/dahdi/</a></td></tr><tr><td><a href="http://svn.digium.com/svn/dahdi/freebsd/" title="http://svn.digium.com/svn/dahdi/freebsd/"></a></td><td>
-	    URL: <a href="http://svn.digium.com/svn/dahdi/freebsd/" title="">http://svn.digium.com/svn/dahdi/freebsd/</a></td></tr><tr><td><a href="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html" title="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html">Project Status</a></td><td>
-	    URL: <a href="https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html" title="Project Status">https://spreadsheets.google.com/pub?key=0Arw6eRL10yIwdGhLdGJWUHF4b3ExQzBsd3BGd2tublE&amp;hl=en&amp;single=true&amp;gid=0&amp;output=html</a></td></tr></table><p>
-	Contact:
-	  Max
-	  Khon
-	 &lt;<a href="mailto:fjoe@samodelkin.net">fjoe@samodelkin.net</a>&gt;
-	</p>
-      <p>The purpose of DAHDI/FreeBSD project is to make it possible to
-	use FreeBSD as a base system for software PBX solutions.</p>
-
-      <p>DAHDI (Digium/Asterisk Hardware Device Interface) is an
-	open-source device driver framework and a set of hardware drivers
-	for E1/T1, ISDN digital, and FXO/FXS analog cards [<a href="http://www.asterisk.org/dahdi/" shape="rect">1</a>].
-	Asterisk is one of the most popular open-source software PBX
-	solutions [<a href="http://www.asterisk.org/" shape="rect">2</a>].</p>
-
-      <p>The project includes porting DAHDI framework and hardware
-	drivers for E1/T1, FXO/FXS analog, and ISDN digital cards to
-	FreeBSD.  This also includes TDMoE support, software and hardware
-	echo cancellation (Octasic, VPMADT032), and hardware transcoding
-	support (TC400B).  The work is ongoing in the official DAHDI SVN
-	repository with the close collaboration with DAHDI folks at
-	Digium.</p>
-
-      <p>DAHDI/FreeBSD project is completed.  ports/misc/dahdi now contains
-	the most recent DAHDI/FreeBSD version and additional stuff that is
-	not available in DAHDI/FreeBSD SVN repository due to licensing and
-	copyright restrictions (OSLEC echo canceler, experimental zaphfc
-	driver).  Experimental sparc64 support is also implemented and is
-	currently being tested.</p>
-
-      <p>There is a pile of minor changes in queue that will be handled
-	soon:</p>
-
-      <ul>
-	<li>Add ability to run asterisk+dahdi under non-root user
-	  account.</li>
-
-	<li>Add support for bri_net_ptmp ISDN signalling to asterisk
-	  port and drop old and outdated zaptel+asterisk-bristuff
-	  ports.</li>
-      </ul>
-
-      <p>Periodic merges from DAHDI/Linux SVN will be continued on a
-	regular basis with rolling out new DAHDI/FreeBSD releases (most
-	likely synchronized with DAHDI/Linux releases).</p>
-    <hr /><h2><a name="External-Toolchain-Support" href="#External-Toolchain-Support" id="External-Toolchain-Support">External Toolchain Support</a></h2><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>One problem that the project has with its push towards
-	embedded platforms is with the toolchain.  The compilers and
-	linkers and such in the current FreeBSD support the architectures
-	generically, but often times silicon vendors produce specialized
-	toolchains to wring the most performance out of their silicon.
-	Right now, it is difficult to compile FreeBSD with these tools, as
-	many manual steps are required to make things 'just so'.</p>
-
-      <p>The external toolchain project will leverage some of the work
-	done by the Clang team to support Clang in the base system
-	(breaking the strict dependency on CC=cc (except for the broken
-	intel CC support)).  In addition, the orchestration of the build
-	(make buildworld) will change to avoid bootstrapping certain
-	tools, or compiling the compilers at all.  In addition, support
-	for using alternate assemblers, linkers, etc., will be added.
-	The work will be done in subversion in projects/xtc (for
-	eXternal Tool Chain).</p>
-    <hr /><h2><a name="GELI-Additions" href="#GELI-Additions" id="GELI-Additions">GELI Additions</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are three new GELI (a disk encryption GEOM class)
-	features available in -CURRENT:</p>
-
-      <ul>
-	<li>AES-XTS encryption.  XTS mode is a standard that is
-	  recommended these days for storage encryption.  This is the
-	  default now.  AES-XTS support was also added to opencrypto
-	  framework and aesni(4) driver.</li>
-
-	<li>Multiple encryption keys.  GELI will use one encryption key
-	  for at most 2^20 blocks (sectors), as it is not recommended to
-	  use the same encryption key for too much data.  It generates a key
-	  array from the master key on attach and uses it accordingly.  This
-	  is the default now.</li>
-
-	<li>Passphrase can now also be loaded from a file (-J and -j
-	  options).</li>
-      </ul>
-    <hr /><h2><a name="gptboot-Improvements" href="#gptboot-Improvements" id="gptboot-Improvements">gptboot Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/svn-src-head/2010-September/020957.html" title="http://lists.FreeBSD.org/pipermail/svn-src-head/2010-September/020957.html"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/svn-src-head/2010-September/020957.html" title="">http://lists.FreeBSD.org/pipermail/svn-src-head/2010-September/020957.html</a></td></tr></table><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>The gptboot now fully follows GPT specification (verifies
-	checksums and falls back to backup header and table if primary is
-	corrupted).</p>
-
-      <p>One can now use new attributes to configure partition that
-	gptboot will try to boot only once from and in case of a failure
-	it will fall back to the previous one.</p>
-
-      <p>For more information check out the commit message.</p>
-    <hr /><h2><a name="HAST-(Highly-Available-Storage)-Improvements" href="#HAST-(Highly-Available-Storage)-Improvements" id="HAST-(Highly-Available-Storage)-Improvements">HAST (Highly Available Storage) Improvements</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>HAST is now better than ever! Some recent improvements
-	include:</p>
-
-      <ul>
-	<li>Hooks supports &#8212; HAST will execute the given command
-	  on various events (connect, disconnect, synchronization start,
-	  synchronization completed, synchronization interrupted,
-	  split-brain condition, role change).</li>
-
-	<li>Configuration reload on SIGHUP, a very missing
-	  functionality.</li>
-
-	<li>Internal keepalive mechanism.</li>
-
-	<li>Many bug fixes, majority of them reported by Mikolaj
-	  Golub.</li>
-      </ul>
-    <hr /><h2><a name="Kernel-level-Stacked-Cryptographic-File-System-&#8212;-PEFS" href="#Kernel-level-Stacked-Cryptographic-File-System-&#8212;-PEFS" id="Kernel-level-Stacked-Cryptographic-File-System-&#8212;-PEFS">Kernel-level Stacked Cryptographic File System &#8212;
-      PEFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/PEFS" title="http://wiki.FreeBSD.org/PEFS"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PEFS" title="">http://wiki.FreeBSD.org/PEFS</a></td></tr><tr><td><a href="http://github.com/glk/pefs" title="http://github.com/glk/pefs"></a></td><td>
-	    URL: <a href="http://github.com/glk/pefs" title="">http://github.com/glk/pefs</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Kurtsou
-	 &lt;<a href="mailto:gk@FreeBSD.org">gk@FreeBSD.org</a>&gt;
-	</p>
-      <p>PEFS is a kernel level stacked cryptographic file system, i.e.
-	it stacks on top of existing mounted filesystems.  AES and
-	Camellia algorithms in XTS mode are supported.  The project has
-	matured since Summer of Code 2009, most important improvements
-	for last few months include: switch to use XTS encryption mode,
-	implementation of sparse file support, fixing rename bugs
-	including race and livelock conditions, addition of ext2 support.
-	PEFS suite contains pam module facilitating user authentication
-	with file system key and adding keys to mounted file system on
-	login.  PEFS passes fsx, pjdfstest, blogbench and dbench tests
-	running on top of UFS and ZFS.</p>
-    <hr /><h2><a name="pc-sysinstall" href="#pc-sysinstall" id="pc-sysinstall">pc-sysinstall</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://it.toolbox.com/blogs/bsd-guru/eurobsdcon-presentation-on-pcsysinstall-41831" title="http://it.toolbox.com/blogs/bsd-guru/eurobsdcon-presentation-on-pcsysinstall-41831"></a></td><td>
-	    URL: <a href="http://it.toolbox.com/blogs/bsd-guru/eurobsdcon-presentation-on-pcsysinstall-41831" title="">http://it.toolbox.com/blogs/bsd-guru/eurobsdcon-presentation-on-pcsysinstall-41831</a></td></tr></table><p>
-	Contact:
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  John
-	  Hixson
-	 &lt;<a href="mailto:john@ixsystems.com">john@ixsystems.com</a>&gt;
-	<br />
-	Contact:
-	  Josh
-	  Paetzel
-	 &lt;<a href="mailto:jpaetzel@FreeBSD.org">jpaetzel@FreeBSD.org</a>&gt;
-	</p>
-      <p>pc-sysinstall was imported into CURRENT recently.  For the moment
-	it is feature complete, although progress on the text front end
-	for it may expose additional functionality it needs.</p>
-    <h3>Open tasks:</h3><ol><li>The automated/scripted install features of pc-sysinstall
-	need wider testing and use to expose potential weaknesses, bugs,
-	and additional features it may require.</li><li>Related tasks include getting a text front-end to
-	pc-sysinstall working and hooking up pc-sysinstall to the build
-	so install media is generated that runs pc-sysinstall.</li></ol><hr /><h2><a name="Target-Big-Endian-Must-Die" href="#Target-Big-Endian-Must-Die" id="Target-Big-Endian-Must-Die">Target Big Endian Must Die</a></h2><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The "tbemd" or Target Big Endian Must Die effort is nearing
-	completion.  Most of the big sweeping changes to the tree have
-	been committed.  The last change, actually pulling the switch, is
-	stalled waiting for make universe improvements.  This work will
-	change the TARGET_ARCH from a plain 'mips' to 'mipsel' or
-	'mipseb' based on which endian the platform has.  It introduces
-	the concept of multiple architectures being implemented with one
-	set of files, and regularizes that design pattern into the FreeBSD
-	build process.  In the past, you had to set TARGET_BIG_ENDIAN=t to
-	compile for big endian, but that had a number of problems: can not
-	share /usr/obj between little and big endian targets, sometimes
-	the produced compilers will not work right unless TARGET_BIG_ENDIAN
-	is defined in the environment, etc.</p>
-    <h3>Open tasks:</h3><ol><li>Update make universe to cope with the new architectures
-	when building kernels.</li></ol><hr /><h2><a name="Userland-DTrace" href="#Userland-DTrace" id="Userland-DTrace">Userland DTrace</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/DTrace/userland" title="http://wiki.FreeBSD.org/DTrace/userland"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/DTrace/userland" title="">http://wiki.FreeBSD.org/DTrace/userland</a></td></tr></table><p>
-	Contact:
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Userland DTrace support was a FreeBSD Foundation sponsored
-	project that was developed during this summer.  The project aimed
-	to bring the userland DTracing functionality to FreeBSD as it is
-	available on OpenSolaris.  FreeBSD now supports the pid provider and
-	the usdt probes.  plockstat is available with a separate patch.
-	Dtruss, a DTrace script that works similarly to ktrace, but with
-	other advantages was imported into FreeBSD.  The mysql-server and
-	postgresql-server ports also have DTrace support.</p>
-    <hr /><h2><a name="V4L-Support-in-Linux-Emulator" href="#V4L-Support-in-Linux-Emulator" id="V4L-Support-in-Linux-Emulator">V4L Support in Linux Emulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://opal.com/freebsd/sys/compat/linux/" title="http://opal.com/freebsd/sys/compat/linux/"></a></td><td>
-	    URL: <a href="http://opal.com/freebsd/sys/compat/linux/" title="">http://opal.com/freebsd/sys/compat/linux/</a></td></tr></table><p>
-	Contact:
-	  J.R.
-	  Oldroyd
-	 &lt;<a href="mailto:fbsd@opal.com">fbsd@opal.com</a>&gt;
-	</p>
-      <p>The V4L support in the Linux emulator has been merged to
-	8-STABLE allowing use of video in Skype calls using a camera
-	supported by the pwcbsd or video4bsd drivers.  A known issue for
-	Skype is that your camera must support YUV420 mode which is what
-	Skype uses.  Note that V4L2 support is not included in the current
-	work, and remains as a project for anyone interested.</p>
-    <hr /><h2><a name="ZFSv28-is-Ready-for-Wider-Testing" href="#ZFSv28-is-Ready-for-Wider-Testing" id="ZFSv28-is-Ready-for-Wider-Testing">ZFSv28 is Ready for Wider Testing</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-fs/2010-August/009197.html" title="http://lists.FreeBSD.org/pipermail/freebsd-fs/2010-August/009197.html"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-fs/2010-August/009197.html" title="">http://lists.FreeBSD.org/pipermail/freebsd-fs/2010-August/009197.html</a></td></tr></table><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>ZFS v28 which includes data deduplication and plenty of other
-	shiny new features is ready for testing.  For more information
-	check out the announcement.</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr></table><p>
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Volker
-	  Werth
-	 &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
-	</p>
-      <p>The bugbusting team continue work on trying to make the contents
-	of the GNATS PR database cleaner, more accessible and easier for
-	committers to find and resolve PRs, by tagging PRs to indicate the
-	areas involved, and by ensuring that there is sufficient info
-	within each PR to resolve each issue.</p>
-
-      <p>July saw the addition of Alexander Best (arundel@) to this
-	bugbusting team, he is helping with the triaging PRs as they come
-	in, creating patches for problems and working with submitters to
-	get the solutions tested, and working through the PR backlog.</p>
-
-      <p>Also in July, Gavin Atkinson worked with Hans Petter Selasky on
-	the USB PRs, attempting to go through many of them and determine
-	the status of each of them.  As a result, nearly 10% of the USB
-	PRs were determined to be closeable, with many more either being
-	marked as patched already or able to be committed quickly.
-	Several PRs that only affect the old (pre-8.0) USB stack were
-	also identified and marked as such.  More work will take place
-	in this area in the future.</p>
-
-      <p>August saw us host another bugathon, with an aim of
-	investigating and getting into a committable state several of the
-	PRs with patches.  Turnout was not as great as in the past
-	&#8212; mainly believed to be due to the short notice, but still
-	several PRs were progressed, with several commits made and
-	several PRs closed.</p>
-
-      <p>The number of PRs has held steady over the last three months,
-	with improvements in numbers in some categories (especially usb
-	and bin) being offset by slight increases in others.</p>
-
-      <p>Reports continue to be produced from the PR database, all of
-	which can be found from the links above.  Committers interested
-	in custom reports are encouraged to discuss requirements with
-	bugmeister@ &#8212; we are happy to create new reports where
-	needs are identified.</p>
-
-      <p>As always, anybody interested in helping out with the PR queue is
-	welcome to join us in #freebsd-bugbusters on EFnet.  We are
-	always looking for additional help, whether your interests lie in
-	triaging incoming PRs, generating patches to resolve existing
-	problems, or simply helping with the database housekeeping
-	(identifying duplicate PRs, ones that have already been resolved,
-	etc).  This is a great way of getting more involved with
-	FreeBSD!</p>
-    <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with
-	closing PRs that the team has already analyzed.</li><li>Try to get more non-committers involved with the triaging
-	of PRs as they come in, and generating patches to fix reported
-	problems.</li></ol><hr /><h2><a name="FreeBSD-KDE-Team" href="#FreeBSD-KDE-Team" id="FreeBSD-KDE-Team">FreeBSD KDE Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org"></a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="">http://FreeBSD.kde.org</a></td></tr></table><p>
-	Contact:
-	  FreeBSD KDE
-	  Team
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:tabthorpe@FreeBSD.org">tabthorpe@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Max
-	  Brazhnikov
-	 &lt;<a href="mailto:makc@FreeBSD.org">makc@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Dima
-	  Panov
-	 &lt;<a href="mailto:fluffy@FreeBSD.org">fluffy@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Alberto
-	  Villa
-	 &lt;<a href="mailto:avilla@FreeBSD.org">avilla@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD KDE team has been actively keeping pace with <a href="http://techbase.kde.org/Schedules" shape="rect">development cycle</a>
-	as it is released by the KDE developers.  Often having KDE in the
-	ports tree within the same week it has been released.</p>
-
-      <p>An integral part of maintaining KDE exists in supporting the
-	Qt toolchain.  As Nokia releases <a href="http://qt.nokia.com/" shape="rect">Qt</a>,
-	our team is keeping pace making it available in our <a href="http://area51.pcbsd.org/" shape="rect">development repository</a>.</p>
-
-      <p>We are fortunate to have a strong contributor base that helps to
-	keep the process moving along.  Our heartfelt thanks go out to all
-	that have helped with patches, maintaining ports, and responding
-	with help on the mailing lists.</p>
-    <h3>Open tasks:</h3><ol><li>KDE 4.5.4 is due out at the end of November, with 4.6.0 to
-	be released early in 2011.</li><li>The FreeBSD KDE team is always looking for helpers, if you are
-	interested in assisting, please feel free to contact any of our
-	team members.</li></ol><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team has announced the schedule for the
-	upcoming joint release of FreeBSD 7.4 and 8.2.  The schedules
-	are available on the web site:</p>
-
-      <ul>
-	<li><a href="http://www.freebsd.org/releases/7.4R/schedule.html" shape="rect">
-	    7.4-RELEASE schedule</a></li>
-	<li><a href="http://www.freebsd.org/releases/8.2R/schedule.html" shape="rect">
-	    8.2-RELEASE schedule</a></li>
-      </ul>
-
-      <p>It is expected that 7.4 will be the last of the 7.X releases.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org" title="http://www.FreeBSDFoundation.org"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org" title="">http://www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We were proud to be a sponsor for MeetBSD�2010 Poland and
-	KyivBSD�2010 in Kiev, Ukraine.  We also committed to
-	sponsoring BSDDay Argentina 2010, MeetBSD California 2010, and
-	NYBSDCon�2010 all in November.  The Foundation was also
-	represented at MeetBSD Poland and Ohio LinuxFest.</p>
-
-      <p>Completed the Foundation funded projects: "FreeBSD Jail-Based
-	Virtualization" by Bjoern Zeeb and "DTrace Userland" by Rui
-	Paulo.</p>
-
-      <p>We kicked off a new project by Swinburne University called
-	"Five New TCP Congestion Control Algorithms for FreeBSD".</p>
-
-      <p>We continued our work on infrastructure projects to beef up
-	hardware for package-building, network-testing, etc.  This
-	includes purchasing equipment as well as managing equipment
-	donations.</p>
-
-      <p>We are three quarters of the way through the year and we have
-	raised around $160,000 towards our goal of $350,000.  Find out how
-	to make a donation at
-	<a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">
-	  http://www.FreeBSDFoundation.org/donate/</a>
-      </p>
-
-      <p>Stop by and visit with us at MeetBSD California (Nov 5-6),
-	LISA (Nov 10-11), and NYCBSDCon (Nov 12-14).</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Enhancing-the-FreeBSD-TCP-Implementation" href="#Enhancing-the-FreeBSD-TCP-Implementation" id="Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/etcp09/" title="http://caia.swin.edu.au/freebsd/etcp09/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/etcp09/" title="">http://caia.swin.edu.au/freebsd/etcp09/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/projects.shtml" title="http://www.FreeBSDFoundation.org/projects.shtml"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/projects.shtml" title="">http://www.FreeBSDFoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="">http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/</a></td></tr></table><p>
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lstewart@FreeBSD.org">lstewart@FreeBSD.org</a>&gt;
-	</p>
-      <p>All outstanding patches have been committed to -CURRENT after a
-	lengthy review process.  It is anticipated to merge all of the
-	project's SIFTR and reassembly queue-related patches from
-	-CURRENT to the stable branches in time for the upcoming 7.4 and
-	8.2 releases.</p>
-    <hr /><h2><a name="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" id="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/5cc/" title="http://caia.swin.edu.au/freebsd/5cc/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/5cc/" title="">http://caia.swin.edu.au/freebsd/5cc/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/projects.shtml" title="http://www.FreeBSDFoundation.org/projects.shtml"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/projects.shtml" title="">http://www.FreeBSDFoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="http://people.FreeBSD.org/~lstewart/patches/5cc/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="">http://people.FreeBSD.org/~lstewart/patches/5cc/</a></td></tr></table><p>
-	Contact:
-	  David
-	  Hayes
-	 &lt;<a href="mailto:dahayes@swin.edu.au">dahayes@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lstewart@FreeBSD.org">lstewart@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has commenced on a newly funded FreeBSD Foundation project
-	to bring six modular TCP congestion control (CC) algorithm
-	implementations (the existing NewReno and five new algorithms:
-	HTCP, CUBIC, Vegas, HD and CHD) to the FreeBSD kernel.  See the
-	CAIA 5cc and NewTCP websites for more details on the
-	algorithms.</p>
-
-      <p>To support the project's primary deliverable, we will also
-	be incorporating the CAIA modular CC and Khelp frameworks into
-	the FreeBSD kernel, along with the Enhanced Round Trip Time Khelp
-	module.</p>
-
-      <p>The project will make a sizable, state-of-the-art
-	contribution to FreeBSD and in certain areas, add completely novel
-	work unavailable in any other operating system known to us.</p>
-
-      <p>We anticipate a number of benefits, including vastly
-	improved researcher friendliness, reduced work for TCP oriented
-	vendors of FreeBSD-based appliances, and greater choice for system
-	administrators who operate FreeBSD systems in atypical network
-	scenarios.</p>
-
-      <p>Keep an eye on the freebsd-net mailing list for project-related
-	announcements.</p>
-    <hr /><h2><a name="Syncing-pf(4)-with-OpenBSD�4.5" href="#Syncing-pf(4)-with-OpenBSD�4.5" id="Syncing-pf(4)-with-OpenBSD�4.5">Syncing pf(4) with OpenBSD�4.5</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/">Viewing the changes.</a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="Viewing the changes.">http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="http://svn.FreeBSD.org/base/user/eri/pf45/head/">The actual repo to build from.</a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="The actual repo to build from.">http://svn.FreeBSD.org/base/user/eri/pf45/head/</a></td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-pf/2010-October/005842.html" title="http://lists.FreeBSD.org/pipermail/freebsd-pf/2010-October/005842.html">Public announcement.</a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-pf/2010-October/005842.html" title="Public announcement.">http://lists.FreeBSD.org/pipermail/freebsd-pf/2010-October/005842.html</a></td></tr></table><p>
-	Contact:
-	  Ermal
-	  Lu�i
-	 &lt;<a href="mailto:eri@FreeBSD.org">eri@FreeBSD.org</a>&gt;
-	</p>
-      <p>This work is based on OpenBSD�4.5 state of pf(4).  It includes
-	many improvements over the code currently present in FreeBSD.  The
-	actual new feature present in pf45 repository is support for
-	divert(4), which should allow tools like snort_inline to work
-	with pf(4) too.  This work also enables pfsync(4) to be loaded as
-	a module as well.</p>
-
-      <p>Currently, this work is considered stable and a patch against
-	-CURRENT has been released on freebsd-pf mailing list.</p>
-
-      <p>The reason why this work is based off of OpenBSD�4.5 is that
-	after this release they have changed the syntax which is not
-	backwards compatible.</p>
-
-      <p>After importing this one the work will go on the newest
-	version and decisions on it will then be done.</p>
-    <h3>Open tasks:</h3><ol><li>Make a decision whether we need pflow(4) in base.</li><li>More regression testing is needed.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Kernel-Event-Timers-Infrastructure" href="#Kernel-Event-Timers-Infrastructure" id="Kernel-Event-Timers-Infrastructure">Kernel Event Timers Infrastructure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=get&amp;target=timers.pdf" title="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=get&amp;target=timers.pdf">Slides from DevSummit in Karlsruhe.</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=get&amp;target=timers.pdf" title="Slides from DevSummit in Karlsruhe.">http://wiki.FreeBSD.org/201010DevSummit?action=AttachFile&amp;do=get&amp;target=timers.pdf</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~mav/tm6292_idle.patch" title="http://people.FreeBSD.org/~mav/tm6292_idle.patch">Proof of concept (dirty) patch, removing some timer events.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mav/tm6292_idle.patch" title="Proof of concept (dirty) patch, removing some timer events.">http://people.FreeBSD.org/~mav/tm6292_idle.patch</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on new event timers infrastructure continues.  In -CURRENT
-	amd64, arm (Marvell), i386, mips, pc98, powerpc, sparc64, sun4v
-	architectures were refactored to use new timers API.</p>
-
-      <p>New machine-independent timers management code was written.  It
-	can utilize both legacy periodic and new one-shot timer
-	operation modes.</p>
-
-      <p>Using one-shot mode allows to significantly reduce the number of
-	timer interrupts and respectively increase CPU sleep time
-	during idle periods.  Timer interrupts on idle CPUs are now
-	generated only when they are needed to handle registered
-	time-based events.  Busy CPUs unluckily still receive the full
-	interrupt rate for purposes of resource accounting, scheduling
-	and timekeeping.</p>
-
-      <p>With some additional tuning it is now possible to have an
-	8-core system, receiving only about 100 interrupts per second
-	and respectively have CPU idle periods up to 100ms.  This
-	allows to effectively use any supported CPU idle states
-	(C-states), that reduces power consumption and increases effect
-	of the Intel TurboBoost technology.</p>
-
-      <p>New manual pages were written to document this functionality:
-	eventtimers(7), attimer(4), atrtc(4), hpet(4).</p>
-    <h3>Open tasks:</h3><ol><li>Troubleshoot possible hardware issues.</li><li>Refactor remaining architectures (arm, ia64, XEN
-	PV).</li><li>Do some optimizations in different subsystems to reduce
-	number of time-based events.  Extend callout API with terms of
-	precision, allowing to group close events.</li><li>Make schedulers tickless, or at least less depending on
-	time events to make skipping timer interrupts possible when CPUs
-	are busy.</li><li>Merge code into 8-STABLE when it is considered ready.</li></ol><hr /><h2><a name="Netdump-Support" href="#Netdump-Support" id="Netdump-Support">Netdump Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Netdump" title="http://wiki.FreeBSD.org/Netdump"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Netdump" title="">http://wiki.FreeBSD.org/Netdump</a></td></tr><tr><td><a href="svn://svn.FreeBSD.org/base/project/sv/" title="svn://svn.FreeBSD.org/base/project/sv/"></a></td><td>
-	    URL: <a href="svn://svn.FreeBSD.org/base/project/sv/" title="">svn://svn.FreeBSD.org/base/project/sv/</a></td></tr></table><p>
-	Contact:
-	  Attilio
-	  Rao
-	 &lt;<a href="mailto:attilio@FreeBSD.org">attilio@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>Netdump provides kernel core dumping over the network, instead
-	of to a local disk.  It implements a very minimal TCP/IPv4 stack
-	and uses a custom UDP protocol to transmit the dump to the
-	netdump server running on another host.  Network interfaces
-	selected for dumping perform I/O in polling mode.</p>
-
-      <p>Netdump should find its use in diskless workstation clusters,
-	PXE-booted test machines, and perhaps when doing disk driver
-	development.</p>
-    <h3>Open tasks:</h3><ol><li>General FreeBSD dumping mechanism refinements.</li><li>Implement checksum on UDP packets.</li><li>Investigate the possibility to replace the custom protocol
-	with tftp.</li><li>Investigate the possibility to replace the custom TCP/IPv4
-	stack with Contiki.</li><li>Implement network console and gdb backend using a shared
-	debug context stack.</li><li>Add IPv6 support.</li></ol><hr /><h2><a name="Resource-Containers" href="#Resource-Containers" id="Resource-Containers">Resource Containers</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of this project is to implement resource containers
-	and a simple per-jail resource limits mechanism.  Resource
-	containers are also a prerequisite for other resource management
-	mechanisms, such as Hierarchical Resource Limits, for "Collective
-	Limits on Set of Processes (aka.  Jobs)" Google Summer of Code
-	2010 project, for implementing mechanism similar to Linux
-	cgroups, and might be also used to e.g. provide precise resource
-	usage accounting for administrative or billing purposes.  So far,
-	a generic resource usage framework has been developed, along with
-	limit enforcement for most resources.  Work is on-going on adding
-	limits for remaining resources, debugging and generally improving
-	the implementation.  This project is being sponsored by The FreeBSD
-	Foundation.</p>
-    <hr /><h2><a name="USB-Stack" href="#USB-Stack" id="USB-Stack">USB Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/head/sys/dev/usb/controller/xhci.c?view=log" title="http://svn.FreeBSD.org/viewvc/base/head/sys/dev/usb/controller/xhci.c?view=log">XHCI driver</a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/viewvc/base/head/sys/dev/usb/controller/xhci.c?view=log" title="XHCI driver">http://svn.FreeBSD.org/viewvc/base/head/sys/dev/usb/controller/xhci.c?view=log</a></td></tr></table><p>
-	Contact:
-	  Hans Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last two months the USB stack in -CURRENT has been
-	enhanced to support USB 3.0 and the XHCI USB 3.0 chipset from
-	Intel.  The XHCI chip will eventually replace the EHCI, OHCI and
-	UHCI chips.</p>
-    <h3>Open tasks:</h3><ol><li>FreeBSD testers which have access to USB 3.0 hardware are
-	wanted.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="mandoc/mdocml-&#8212;-groff-Replacement-for-Rendering-Manual-Pages-in-FreeBSD" href="#mandoc/mdocml-&#8212;-groff-Replacement-for-Rendering-Manual-Pages-in-FreeBSD" id="mandoc/mdocml-&#8212;-groff-Replacement-for-Rendering-Manual-Pages-in-FreeBSD">mandoc/mdocml &#8212; groff Replacement for Rendering Manual
-      Pages in FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mdocml.bsd.lv/" title="http://mdocml.bsd.lv/">Kristaps' mdocml project page.</a></td><td>
-	    URL: <a href="http://mdocml.bsd.lv/" title="Kristaps' mdocml project page.">http://mdocml.bsd.lv/</a></td></tr><tr><td><a href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml" title="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml">Git branch for FreeBSD mdocml related work.</a></td><td>
-	    URL: <a href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml" title="Git branch for FreeBSD mdocml related work.">https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml</a></td></tr></table><p>
-	Contact:
-	  Ulrich
-	  Sp�rlein
-	 &lt;<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>&gt;
-	</p>
-      <p>Kristaps' groff-replacement (only for rendering manual pages)
-	is already available in NetBSD and OpenBSD, and used to render the
-	base system manpages for the latter.  This project aims to do
-	similar things for FreeBSD.</p>
-
-      <p>mandoc(1) is more strict in what it accepts as input and is still
-	lacking some features that are used by some selected few manpages.</p>
-
-      <p>Getting manual page fixes accepted by upstream vendors has been
-	challenging.  Waiting for them to round-trip back into FreeBSD will
-	take even longer.  Future work will therefore result in direct
-	commits to our contrib/ and gnu/ repository areas, in the hope
-	this will not impact future vendor imports too much.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the Big Manpage Cleanup of 2010.</li><li>Write a textproc/groff port for the latest groff version.</li><li>Import mandoc(1), switch to catpages for base.</li><li>Supply necessary ports infrastructure to opt-in to
-	mandoc(1).</li><li>Discuss future of groff(1) in base wrt. share/doc.</li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">Website of the FreeBSD German Documentation Project.</a></td><td>
-	    URL: <a href="http://doc.bsdgroup.de" title="Website of the FreeBSD German Documentation Project.">http://doc.bsdgroup.de</a></td></tr></table><p>
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The committers to the German Documentation Project were mostly
-	trying to keep the documents and the website translations in sync
-	with the ones on FreeBSD.org.  Fabian Ruch was helpful in catching up
-	with the changes to the Porters Handbook.  Benedict translated the
-	Solid State article into German because this is becoming a good
-	addition to traditional hard drive storage.</p>
-
-      <p>We tried to re-activate committers who did not contribute for
-	some time but most of them are currently unable to free up enough
-	time.  We hope to gain fresh contributor blood as we are getting
-	occasional reports about bugs and grammar in the German
-	translation.</p>
-    <h3>Open tasks:</h3><ol><li>Submit grammar, spelling or other errors you find in the
-	German documents and the website.</li><li>Translate more articles and other open handbook
-	sections.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>The www/ja and doc/ja_JP.eucJP/ have been updated constantly
-	since the last status report.  We committed a big patch for
-	the "Installing FreeBSD" chapter of the FreeBSD Handbook which was
-	contributed by many people since a long time.  This chapter is
-	still outdated and needs more work.  Some progress was made in
-	the Porter's Handbook as well.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation of the FreeBSD Handbook and contents of
-	the <a href="http://www.FreeBSD.org" shape="rect">www.FreeBSD.org</a> site to
-	the Japanese language.</li><li>Pre-/post-commit review of the translation.</li></ol><hr /><h2><a name="Web-Feeds-for-UPDATING-Files" href="#Web-Feeds-for-UPDATING-Files" id="Web-Feeds-for-UPDATING-Files">Web Feeds for UPDATING Files</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://updating.versia.com/" title="http://updating.versia.com/"></a></td><td>
-	    URL: <a href="http://updating.versia.com/" title="">http://updating.versia.com/</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Kojevnikov
-	 &lt;<a href="mailto:alexander@kojevnikov.com">alexander@kojevnikov.com</a>&gt;
-	</p>
-      <p><a href="http://updating.versia.com/" shape="rect">updating.versia.com</a>
-	features web feeds for UPDATING files from ports, head, stable/7
-	and stable/8.  These feeds provide an easy way to track
-	important changes in the ports tree and the base system.</p>
-    <hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="FreeBSD-Services-Control-(fsc)" href="#FreeBSD-Services-Control-(fsc)" id="FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~trhodes/fsc/" title="http://people.FreeBSD.org/~trhodes/fsc/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~trhodes/fsc/" title="">http://people.FreeBSD.org/~trhodes/fsc/</a></td></tr></table><p>
-	Contact:
-	  Tom
-	  Rhodes
-	 &lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD Services Control is a mix of binaries which integrate
-	into the rc.d system and provide for service (daemon)
-	monitoring.  It knows about signals, pidfiles, and uses very
-	little resources.</p>
-
-      <p>The fsc daemon (fscd) runs in the background once the system
-	has started.  Services are then added to this daemon via the
-	fscadm control utility and from there they will be monitored.
-	When they die, depending on the reason, they will be restarted.
-	Certain signals may be ignored (list not decided), and fscd
-	will remove that service from monitoring.  Every action is
-	logged to the system logging daemon.  Additionally, the fscadm
-	utility may be used to inquire about what services are
-	monitored, their pidfile location, and current process id.</p>
-
-      <p>FSC provides several advantages over the third-party
-	daemontools package.  For example, fscd uses push notifications
-	instead of polling; fscd is an internal, FreeBSD-maintained
-	software package accessible to all developers where daemontools
-	would have to be a port and require us to maintain patches;
-	fscd could be easily integrated with the current rc.d
-	infrastructure.</p>
-
-      <p>Partially based on the ideas of daemontools and Solaris
-	Service Management Facility (SMF), this could be an extremely
-	useful tool for FreeBSD systems.</p>
-
-      <p>Since the last status report, two bugs have been fixed and
-	the documentation has been updated.  In the coming weeks we hope
-	to get more developer attention and review, perhaps even push
-	to commit the code into FreeBSD.</p>
-    <h3>Open tasks:</h3><ol><li>Testing and feedback would be really helpful.</li></ol><hr /><h2><a name="Updating-Base-Tools-to-Accommodate-Ports-Requirements" href="#Updating-Base-Tools-to-Accommodate-Ports-Requirements" id="Updating-Base-Tools-to-Accommodate-Ports-Requirements">Updating Base Tools to Accommodate Ports
-      Requirements</a></h2><p>
-	Contact:
-	  Gordon
-	  Tetlow
-	 &lt;<a href="mailto:gordon@FreeBSD.org">gordon@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of the project is to allow easier extension of base
-	system tools by the ports system.  Ideally, no files in /etc
-	should need to be modified by a port installation.</p>
-
-      <p>The man toolset was recently reimplemented as a BSDL version
-	instead of the old GPL version.  It is also a single shell script
-	instead of multiple C programs.  Ports can extend the man
-	functionality by dropping files into
-	/usr/local/etc/man.d/portname.conf.</p>
-
-      <p>Next up on the list is to finish the implementation for
-	newsyslog thereby allowing ports that need logs rotated to take
-	advantage of that tool.</p>
-    <hr /><h2><a name="xz-Compression-for-Packages-and-Log-Files" href="#xz-Compression-for-Packages-and-Log-Files" id="xz-Compression-for-Packages-and-Log-Files">xz Compression for Packages and Log Files</a></h2><p>
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for xz compression has been enabled in bsdtar (-CURRENT
-	8-STABLE) and added to pkg_create(1) and pkg_add(1) (-CURRRENT).
-	Packages with the .txz suffix can be created and installed.
-	Log file compression using xz in newsyslog(8) will be integrated
-	soon.  Benchmarks show 15-30% better compression ratios and up to
-	halved decompression times when compared to bzip2.  A switch from
-	the default package format from .tbz to .txz is to be
-	considered.</p>
-    <h3>Open tasks:</h3><ol><li>Test building all FreeBSD packages with xz compression.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Bringing-up-ARM-to-FreeBSD-Tree" href="#Bringing-up-ARM-to-FreeBSD-Tree" id="Bringing-up-ARM-to-FreeBSD-Tree">Bringing up ARM to FreeBSD Tree</a></h2><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt;
-	<br />
-	Contact:
-	  Mohammed
-	  Farrag
-	 &lt;<a href="mailto:mfarrag@FreeBSD.org">mfarrag@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are still in the beginning of the project since we started
-	it after the summer of code.</p>
-    <h3>Open tasks:</h3><ol><li>Reading ARM structure.</li><li>Reading MicroC OS.</li><li>Using Qemu to emulate the work.</li></ol><hr /><h2><a name="FreeBSD-on-the-Playstation-3" href="#FreeBSD-on-the-Playstation-3" id="FreeBSD-on-the-Playstation-3">FreeBSD on the Playstation 3</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="svn://svn.FreeBSD.org/base/user/nwhitehorn/ps3" title="svn://svn.FreeBSD.org/base/user/nwhitehorn/ps3">PS3 SVN Repository</a></td><td>
-	    URL: <a href="svn://svn.FreeBSD.org/base/user/nwhitehorn/ps3" title="PS3 SVN Repository">svn://svn.FreeBSD.org/base/user/nwhitehorn/ps3</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~nwhitehorn/ps3" title="http://people.FreeBSD.org/~nwhitehorn/ps3">Pre-built PS3 kernel</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~nwhitehorn/ps3" title="Pre-built PS3 kernel">http://people.FreeBSD.org/~nwhitehorn/ps3</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD/powerpc64 now boots multi-user SMP and is self-hosting on
-	the Playstation 3.  Booting requires a PS3 console with the
-	OtherOS capability (fat model console with firmware &lt; 3.21).
-	The only supported hardware at present is USB and the Ethernet
-	controller.</p>
-    <h3>Open tasks:</h3><ol><li>SATA support.</li><li>Boot loader enhancements to allow user input at the loader
-	prompt.</li><li>Support for the Cell SPU units.</li></ol><hr /><h2><a name="FreeBSD/mips-on-Octeon" href="#FreeBSD/mips-on-Octeon" id="FreeBSD/mips-on-Octeon">FreeBSD/mips on Octeon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/FreeBSD/mips/Octeon" title="http://wiki.FreeBSD.org/FreeBSD/mips/Octeon"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/FreeBSD/mips/Octeon" title="">http://wiki.FreeBSD.org/FreeBSD/mips/Octeon</a></td></tr></table><p>
-	Contact:
-	  Juli
-	  Mallett
-	 &lt;<a href="mailto:jmallett@FreeBSD.org">jmallett@FreeBSD.org</a>&gt;
-	</p>
-      <p>All Octeon development is now ongoing in -CURRENT and most
-	Octeon-specific and general MIPS changes from the old Octeon
-	branch have been checked in.  The Simple Executive from the Cavium
-	Octeon SDK has been checked into Subversion and most of the
-	Octeon port has been updated to use it where appropriate,
-	including moving to a port of the Linux Ethernet driver, octe.
-	SMP support is stable on 2-core systems and has seen some testing
-	on systems with up to 16 cores.</p>
-    <h3>Open tasks:</h3><ol><li>Some PCI devices still do not seem to work
-	completely.</li><li>Host-mode USB support is incomplete and needs further
-	testing and debugging.</li><li>Work on an ATA-based Compact Flash driver for boards that
-	support DMA has begun.</li><li>A GPIO driver should be trivial using the Simple
-	Executive.</li><li>Performance in the Linux-derived octe Ethernet driver could
-	be improved.  Support for some switch chipsets that are commonly
-	present in Octeon-based equipment is in progress.</li></ol><hr /><h2><a name="FreeBSD/mips-Ralink-RT3052F/Broadcom-BCM5354" href="#FreeBSD/mips-Ralink-RT3052F/Broadcom-BCM5354" id="FreeBSD/mips-Ralink-RT3052F/Broadcom-BCM5354">FreeBSD/mips Ralink RT3052F/Broadcom BCM5354</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD" title="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD">Description</a></td><td>
-	    URL: <a href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD" title="Description">http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD</a></td></tr><tr><td><a href="http://my.ddteam.net/hg/BASE/" title="http://my.ddteam.net/hg/BASE/">Mercurial repository</a></td><td>
-	    URL: <a href="http://my.ddteam.net/hg/BASE/" title="Mercurial repository">http://my.ddteam.net/hg/BASE/</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@dlink.ua">ray@dlink.ua</a>&gt;
-	</p>
-      <p>FreeBSD/mips has been ported to D-Link DAP-1350, wireless
-	AP/router based on Ralink RT3052F SoC.</p>
-
-      <p>Drivers status:</p>
-
-      <ul>
-	<li>rt2860: Ralink RT2860 802.11n &#8212; Worked, but RT3022
-	2.4G 2T2R radio tuning required.</li>
-
-	<li>rt: Ralink RT3052F onChip Ethernet MAC &#8212; Done.</li>
-
-	<li>rtsw: OnChip Ethernet switch &#8212; Not done (initialized
-	by UBoot).</li>
-
-	<li>usb-otg: DWC like USB OTG controller &#8212; Worked.</li>
-
-	<li>gpio: RT3052F onChip GPIO &#8212; Worked (LEDs,
-	Buttons).</li>
-
-	<li>cfi: CFI NOR Flash &#8212; Worked.</li>
-      </ul>
-
-      <p>FreeBSD/mips D-Link DIR-320 project(BCM5354 SoC).</p>
-
-      <p>New profile openvpn-router available for testing.</p>
-    <h3>Open tasks:</h3><ol><li>Debug/Fix USB OTG driver (RT3052F).</li><li>Debug/Fix 802.11n driver (RT3052F).</li><li>Write rtswitch driver (RT3052F).</li><li>Implement Timer unit driver (RT3052F).</li><li>Implement Hardware NAT/PPPoE/VLAN offload (RT3052F).</li><li>Implement I2C/I2S/PCM/SPI drivers (RT3052F).</li><li>switch configuration utility (BCM5354).</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>Apart from the constant bug fixing and adaptions to
-	machine-independent changes that pretty much always take place,
-	not much has happened in the area of sparc64 since the last
-	status report.  The only noteworthy exception are some performance
-	optimizations which take advantage of features of Fujitsu SPARC64
-	CPUs.  These were a bit too risky for putting them in shortly
-	before FreeBSD�8.1-RELEASE but will be part of 7.4-RELEASE and
-	8.2-RELEASE now that they have received the necessary
-	testing.</p>
-
-      <p>Part of reasons why not much has happened in this spot was some
-	lack of time on my side but also due to nobody showing up with a
-	not yet supported sun4u machine lately and me delving in the
-	network land instead, which yielded some things to report about
-	in the next status report.  On the other hand I recently got a
-	hold of a Sun Fire 3800, so these and other models from the same
-	family likely will be supported by FreeBSD at some point in the
-	future.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium-Web-Browser" href="#Chromium-Web-Browser" id="Chromium-Web-Browser">Chromium Web Browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://chromium.hybridsource.org" title="http://chromium.hybridsource.org">Main chromium site</a></td><td>
-	    URL: <a href="http://chromium.hybridsource.org" title="Main chromium site">http://chromium.hybridsource.org</a></td></tr><tr><td><a href="http://chromium.hybridsource.org/issues" title="http://chromium.hybridsource.org/issues">Porting summary</a></td><td>
-	    URL: <a href="http://chromium.hybridsource.org/issues" title="Porting summary">http://chromium.hybridsource.org/issues</a></td></tr></table><p>
-	Contact:
-	  Ruben
-	 &lt;<a href="mailto:chromium@hybridsource.org">chromium@hybridsource.org</a>&gt;
-	</p>
-      <p>Chromium is a Webkit-based web browser that is largely BSD
-	licensed and was recently committed to ports.  It has been working
-	well on FreeBSD and supports new features like HTML 5 video.  Newer
-	builds use the Clang compiler, Clang first compiled a non-debug
-	build of Chromium, a very large C++ project, on FreeBSD.  This
-	porting effort employs a new hybrid-source model: portions of the
-	latest FreeBSD patches are kept closed for a limited time and new
-	builds are made available only to paying subscribers, while older
-	builds are eventually spun off to ports.  Further work remains to
-	port all of Chromium to FreeBSD, I am now porting the task manager
-	to use FreeBSD's libkvm and the ALSA audio backend needs to be
-	ported to OSS.  There are other issues listed at the porting
-	summary, contact me if you would like to pitch in.</p>
-    <hr /><h2><a name="OpenAFS-Port" href="#OpenAFS-Port" id="OpenAFS-Port">OpenAFS Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openafs.org" title="http://openafs.org">OpenAFS home page</a></td><td>
-	    URL: <a href="http://openafs.org" title="OpenAFS home page">http://openafs.org</a></td></tr><tr><td><a href="http://web.mit.edu/freebsd/openafs/openafs.shar" title="http://web.mit.edu/freebsd/openafs/openafs.shar">FreeBSD port for the OpenAFS 1.5.77 release</a></td><td>
-	    URL: <a href="http://web.mit.edu/freebsd/openafs/openafs.shar" title="FreeBSD port for the OpenAFS 1.5.77 release">http://web.mit.edu/freebsd/openafs/openafs.shar</a></td></tr></table><p>
-	Contact:
-	  Benjamin
-	  Kaduk
-	 &lt;<a href="mailto:kaduk@mit.edu">kaduk@mit.edu</a>&gt;
-	<br />
-	Contact:
-	  Derrick
-	  Brashear
-	 &lt;<a href="mailto:shadow@gmail.com">shadow@gmail.com</a>&gt;
-	</p>
-      <p>AFS is a distributed network file system that originated from
-	the Andrew Project at Carnegie-Mellon University; the OpenAFS
-	client implementation has not been particularly useful on FreeBSD
-	since the FreeBSD�4.X releases.  The previous status report
-	brought the OpenAFS client to a useful form on -CURRENT,
-	though with many rough edges.  Only a couple of those edges have
-	been smoothed out during the past few months, as developer time
-	was scarce.  A mismatch between file size and vmobject size
-	tracking was resolved (allowing executables to be run from AFS),
-	and our system call entry has been updated on -CURRENT and 8-STABLE
-	to match reality.  Thanks to Kostik Belusov for both of those!
-	The code is useful enough that we plan to submit an
-	openafs-devel port to the Ports Collection in the coming
-	cycle.</p>
-
-      <p>There are several known outstanding issues that are being
-	worked on, but detailed bug reports are welcome at
-	port-freebsd@openafs.org.</p>
-    <h3>Open tasks:</h3><ol><li>Rework vnode locking for lookup operations to avoid an
-	easily-triggered deadlock between two threads when one is looking
-	up the parent directory.</li><li>Update VFS locking to allow the use of disk-based client
-	caches as well as memory-based caches.</li><li>Track down races and deadlocks that appear under
-	load.</li><li>Integrate with the bsd.kmod.mk kernel-module build
-	infrastructure.</li></ol><hr /><h2><a name="pkg_upgrade-(sysutils/bsdadminscripts)" href="#pkg_upgrade-(sysutils/bsdadminscripts)" id="pkg_upgrade-(sysutils/bsdadminscripts)">pkg_upgrade (sysutils/bsdadminscripts)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://sf.net/projects/bsdadminscripts" title="http://sf.net/projects/bsdadminscripts">bsdadminscripts SF project</a></td><td>
-	    URL: <a href="http://sf.net/projects/bsdadminscripts" title="bsdadminscripts SF project">http://sf.net/projects/bsdadminscripts</a></td></tr><tr><td><a href="http://sf.net/projects/bsdadminscripts/files/publications/2010-10-eurobsdcon/" title="http://sf.net/projects/bsdadminscripts/files/publications/2010-10-eurobsdcon/">EuroBSDCon�2010 slides and paper</a></td><td>
-	    URL: <a href="http://sf.net/projects/bsdadminscripts/files/publications/2010-10-eurobsdcon/" title="EuroBSDCon�2010 slides and paper">http://sf.net/projects/bsdadminscripts/files/publications/2010-10-eurobsdcon/</a></td></tr></table><p>
-	Contact:
-	  Dominic
-	  Fandrey
-	 &lt;<a href="mailto:kamikaze@bsdforen.de">kamikaze@bsdforen.de</a>&gt;
-	</p>
-      <p>pkg_upgrade was (to my knowledge) the first binary packages
-	only update tool for the FreeBSD ports.  Using it does not require a
-	copy of the ports tree.</p>
-
-      <p>Currently the tool is in the final stages of a recode, that
-	will greatly improve support for sharing packages over NFS or
-	nullfs mounts (e.g. for distributing packages into jails) and
-	also offers improved dependency tracking and performance, more in
-	line with how pointyhat and Tinderbox build packages.</p>
-
-      <p>I recently had the opportunity to present my work at the
-	EuroBSDCon�2010.</p>
-    <h3>Open tasks:</h3><ol><li>Complete session code.</li><li>Add INDEX generator script that harvests information
-	directly from packages and hence is always accurate.</li><li>Testing.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td>
-	    URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/"></a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com/" title="">http://tinderbox.marcuscom.com/</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree count now exceeds 22,000.  With the assistance
-	of many people, especially Philip Gollucci, the open PR count is
-	below 1000 for the first time in quite a while.  This is very
-	encouraging progress.</p>
-
-      <p>Since the last report, we added five new committers, and took
-	in two commit bits for safe keeping.</p>
-
-      <p>With onsite assistance from jhb@, gnn@, skreuzer@, and
-	pgollucci@, we now have 11 new servers at NYI.  The machines still
-	need testing for stability and will soon be assigned for package
-	building.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	on-going basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports updates.
-	Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>des: test libfetch</li>
-	<li>gabor: tests for BSD iconv and grep</li>
-	<li>mezz: switch www/neon28 to www/neon29</li>
-	<li>beat: update www/libxul</li>
-	<li>johans: update devel/bison and devel/m4</li>
-	<li>dinoex: update graphics/tiff</li>
-	<li>jpaetzel: update devel/popt</li>
-	<li>ade: multiple runs autotools upgrade</li>
-	<li>gerald: setting USE_GCC=4.5 as default</li>
-	<li>ashish: changes to Mk/bsd.license.mk</li>
-	<li>kwm: test of Clang in -CURRENT</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Looking for help fixing <a href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent" shape="rect">ports
-	  broken on -CURRENT</a>.</li><li>Looking for help with  <a href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures" shape="rect">
-	  Tier-2 architectures</a>.</li><li>Most ports PRs are assigned, we now need to focus on
-	testing, committing and closing.</li></ol><hr /><h2><a name="Ports-Distfile-and-WWW-Checker" href="#Ports-Distfile-and-WWW-Checker" id="Ports-Distfile-and-WWW-Checker">Ports Distfile and WWW Checker</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~ehaupt/distilator/" title="http://people.FreeBSD.org/~ehaupt/distilator/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~ehaupt/distilator/" title="">http://people.FreeBSD.org/~ehaupt/distilator/</a></td></tr></table><p>
-	Contact:
-	  Emanuel
-	  Haupt
-	 &lt;<a href="mailto:ehaupt@FreeBSD.org">ehaupt@FreeBSD.org</a>&gt;
-	</p>
-      <p>Given the current status of fenner's Distfiles Survey, a new
-	distfile checker was written in order to have an overview for the
-	state of each distfile in the ports tree.  The distfile checker is
-	also able to verify WWW entries in pkg-descr files.  This is an
-	attempt to weed out broken MASTER_SITES and outdated WWW
-	entries.</p>
-
-      <p>The current version uses a MySQL database backend and is able
-	to verify 432512 distfiles (30 concurrent threads) within 24
-	hours.</p>
-    <h3>Open tasks:</h3><ol><li>Provide JavaScript to sort/filter/search tables.</li></ol><hr /><h2><a name="Valgrind-Port" href="#Valgrind-Port" id="Valgrind-Port">Valgrind Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Valgrind" title="http://wiki.freebsd.org/Valgrind">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Valgrind" title="Wiki page">http://wiki.freebsd.org/Valgrind</a></td></tr><tr><td><a href="http://bitbucket.org/stass/valgrind-freebsd/overview" title="http://bitbucket.org/stass/valgrind-freebsd/overview">bibtbucket repository</a></td><td>
-	    URL: <a href="http://bitbucket.org/stass/valgrind-freebsd/overview" title="bibtbucket repository">http://bitbucket.org/stass/valgrind-freebsd/overview</a></td></tr><tr><td><a href="https://bugs.kde.org/show_bug.cgi?id=208531" title="https://bugs.kde.org/show_bug.cgi?id=208531">Bug tracker</a></td><td>
-	    URL: <a href="https://bugs.kde.org/show_bug.cgi?id=208531" title="Bug tracker">https://bugs.kde.org/show_bug.cgi?id=208531</a></td></tr></table><p>
-	Contact:
-	  Stanislav
-	  Sedov
-	 &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>Valgrind is a tool for detecting memory management and
-	threading bugs, and profiling.  Version 3.6.0 has recently been
-	released and the FreeBSD port has now been updated.</p>
-
-      <p>Development of the Valgrind port has moved from Perforce to
-	bitbucket.org, in order to make it easier for others to track
-	changes as we progress towards getting the port into shape to
-	commit upstream.  The repository's Bitbucket address is at the
-	beginning of the report.</p>
-
-      <p>A bugzilla entry has been submitted to track the FreeBSD Valgrind
-	port.  You can see the status and vote for the bug to express your
-	interest at <a href="https://bugs.kde.org/show_bug.cgi?id=208531" shape="rect">
-	  https://bugs.kde.org/show_bug.cgi?id=208531</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Port exp-ptrcheck valgrind tool and fix outstanding issues
-	that show up in memcheck/helgrind/DRD in the Valgrind regression
-	tests suite.</li><li>More testing (please, help).</li><li>Integrate our patches upstream.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSD-Day@2010" href="#BSD-Day@2010" id="BSD-Day@2010">BSD-Day@2010</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BSDDay_2010" title="http://wiki.FreeBSD.org/BSDDay_2010"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BSDDay_2010" title="">http://wiki.FreeBSD.org/BSDDay_2010</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The purpose of this one-day event is to gather Central
-	European developers of today's open-source BSD systems to
-	popularize their work and their organizations, and to meet each
-	other in the real life.  We would also like to motivate potential
-	future developers and users, especially undergraduate university
-	students to work with BSD systems.  This year's BSD-Day will be
-	held in Budapest, Hungary at E�tv�s Lor�nd
-	University, Faculty of Informatics on November 20, 2010.
-	Everybody is welcome!</p>
-    <hr /><h2><a name="EuroBSDCon-2010" href="#EuroBSDCon-2010" id="EuroBSDCon-2010">EuroBSDCon 2010</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2010.EuroBSDCon.org/" title="http://2010.EuroBSDCon.org/"></a></td><td>
-	    URL: <a href="http://2010.EuroBSDCon.org/" title="">http://2010.EuroBSDCon.org/</a></td></tr><tr><td><a href="http://2011.EuroBSDCon.org/" title="http://2011.EuroBSDCon.org/"></a></td><td>
-	    URL: <a href="http://2011.EuroBSDCon.org/" title="">http://2011.EuroBSDCon.org/</a></td></tr></table><p>
-	Contact:
-	  Wolfgang
-	  Zenker
-	 &lt;<a href="mailto:eurobsdcon2010@egeling.de">eurobsdcon2010@egeling.de</a>&gt;
-	<br />
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>EuroBSDCon�2010 happened in Karlsruhe, Germany, with many
-	users, developers, friends, and others.  We had many tutorials,
-	and 22 interesting presentations on various topics connected to
-	FreeBSD, OpenBSD, NetBSD, like the new USB stack, jail
-	improvements, Virtual Private Systems, SSH and PGP convergence,
-	ZFS, journaled Soft-Updates, BSD certification, porting to the
-	latest ARM processors, and pc-sysinstall.  The event was opened by
-	a keynote speech from Poul-Henning Kamp on software tools and
-	their future, and it was closed by short status reports on
-	different BSD flavors.</p>
-    <hr /><h2><a name="EuroBSDCon-2011" href="#EuroBSDCon-2011" id="EuroBSDCon-2011">EuroBSDCon 2011</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2011.eurobsdcon.org/" title="http://2011.eurobsdcon.org/">EuroBSDCon 2011 Placeholder</a></td><td>
-	    URL: <a href="http://2011.eurobsdcon.org/" title="EuroBSDCon 2011 Placeholder">http://2011.eurobsdcon.org/</a></td></tr><tr><td><a href="http://2011.eurobsdcon.org/CfP.html" title="http://2011.eurobsdcon.org/CfP.html">Call for Proposals</a></td><td>
-	    URL: <a href="http://2011.eurobsdcon.org/CfP.html" title="Call for Proposals">http://2011.eurobsdcon.org/CfP.html</a></td></tr></table><p>
-	Contact:
-	  Philip
-	  Paeps
-	 &lt;<a href="mailto:philip@FreeBSD.org">philip@FreeBSD.org</a>&gt;
-	</p>
-      <p>EuroBSDCon is the European technical conference for users and
-	developers on BSD based systems.  The EuroBSDCon 2011 conference
-	will be held in the Netherlands from Thursday 6 October 2011
-	to Sunday 9 October 2011, with tutorials on Thursday and Friday
-	and talks on Saturday and Sunday.</p>
-
-      <p>The EuroBSDCon conference is inviting developers and users of
-	BSD based systems to submit innovative and original papers not
-	submitted to other European conferences on BSD-related topics.</p>
-
-      <p>Please see the EuroBSDCon 2011 website for more details.</p>
-    <hr /><h2><a name="FreeBSD-Developer-Summit,-Karlsruhe" href="#FreeBSD-Developer-Summit,-Karlsruhe" id="FreeBSD-Developer-Summit,-Karlsruhe">FreeBSD Developer Summit, Karlsruhe</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/201010DevSummit" title="http://wiki.FreeBSD.org/201010DevSummit"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/201010DevSummit" title="">http://wiki.FreeBSD.org/201010DevSummit</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We were happy to have more than 40 FreeBSD developers and guests
-	attending the FreeBSD Developer Summit prior to EuroBSDCon�2010
-	in Karlsruhe, Germany.  This workshop-style event was hosted at
-	Karlsruhe Institute of Technology, and included prepared
-	presentations in the morning, as well as group hacking and
-	discussion sections in the afternoon.  We had various talks on
-	several topics, covering the USB subsystem, state of the
-	toolchain, the FreeBSD documentation, NanoBSD improvements, FreeBSD
-	port of PF, jails, Virtual Private Systems, cooperation with the
-	PC-BSD Project, FreeNAS, the new event timers subsystems,
-	bugbusting discussions and Ports Tinderbox presentations, and
-	many of this year's and last year's Google Summer of Code
-	projects.  Photos, videos, and slides for most of the talks are
-	available on the wiki page.</p>
-    <hr /><h2><a name="FreeBSD-Developer-Summit,-meetBSD-California-2010" href="#FreeBSD-Developer-Summit,-meetBSD-California-2010" id="FreeBSD-Developer-Summit,-meetBSD-California-2010">FreeBSD Developer Summit, meetBSD California 2010</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/201011DevSummit" title="http://wiki.FreeBSD.org/201011DevSummit">Information page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/201011DevSummit" title="Information page">http://wiki.FreeBSD.org/201011DevSummit</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@ixsystems.com">imp@ixsystems.com</a>&gt;
-	</p>
-      <p>We will be having a developers summit meeting at meetBSD
-	California 2010 on November 4th, the day before the conference.
-	Based on who is in attendance, we will be talking about the
-	status of pressing issues; working on pressing problems and
-	using the opportunity for face to face meetings to work out
-	issues that are difficult in email.  This is an invitation-only
-	event, but any developer can invite people they think would help
-	drive this meeting forward.  An agenda will be published closer
-	to the date.</p>
-    <hr /><h2><a name="PC-BSD" href="#PC-BSD" id="PC-BSD">PC-BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pcbsd.org" title="http://www.pcbsd.org">PC-BSD Website</a></td><td>
-	    URL: <a href="http://www.pcbsd.org" title="PC-BSD Website">http://www.pcbsd.org</a></td></tr><tr><td><a href="http://trac.pcbsd.org/browser/pcbsd/current/" title="http://trac.pcbsd.org/browser/pcbsd/current/">PC-BSD Current Repo</a></td><td>
-	    URL: <a href="http://trac.pcbsd.org/browser/pcbsd/current/" title="PC-BSD Current Repo">http://trac.pcbsd.org/browser/pcbsd/current/</a></td></tr></table><p>
-	Contact:
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is progressing quickly on a major re-factoring of PC-BSD
-	tools and the PBI format for 9.0.  Our GUI tools have been
-	converted to compile / run within native QT without KDE now,
-	allowing us to begin offering support for other desktop
-	environments for 9.0, such as Gnome, XFCE, LXDE, KDE, etc.  The
-	PBI format has undergone a complete evolution, and is now
-	entirely command-line based for all aspects of it, with only a
-	few dependencies upon curl &amp; xdg-utils.  This will allow us to
-	begin offering PBIs for traditional FreeBSD users starting with 9.0,
-	who will be able to install the pbi-manager from ports in the
-	near future.</p>
-    <h3>Open tasks:</h3><ol><li>We are still busy converting / fixing all our tools to play
-	nicely with various DE's, but making quick progress.</li><li>The new PBI format is still undergoing extensive testing,
-	and bugs are being isolated and fixed.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2010-10-2010-12.html b/website/content/en/status/report-2010-10-2010-12.html
deleted file mode 100644
index d05f131b43..0000000000
--- a/website/content/en/status/report-2010-10-2010-12.html
+++ /dev/null
@@ -1,1438 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between October and
-      December 2010.  It is the last of the four reports planned for 2010.
-      The work on the new minor versions of FreeBSD, 7.4 and 8.2, has been
-      progressing well and they should be released around the end of this
-      month.</p><p>Thanks to all the reporters for the excellent work!  This report
-      contains 37 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between January and March 2011 is April 15th, 2011.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BSDInstall">BSDInstall</a></li><li><a href="#Non-executable-Stacks">Non-executable Stacks</a></li><li><a href="#Webcamd">Webcamd</a></li><li><a href="#xz-Compression-for-Packages-and-Log-Files">xz Compression for Packages and Log Files</a></li><li><a href="#ZFS-pool-version-28">ZFS pool version 28</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team-Status-Report">FreeBSD Bugbusting Team Status Report</a></li><li><a href="#Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></li><li><a href="#Ethernet-Switch-Framework">Ethernet Switch Framework</a></li><li><a href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></li><li><a href="#FreeBSD-802.11n">FreeBSD 802.11n</a></li><li><a href="#FreeBSD-VirtIO-Network-Driver">FreeBSD VirtIO Network Driver</a></li><li><a href="#Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)">Generic IEEE 802.3 annex 31B full duplex flow control support
-      for Ethernet in mii(4)</a></li><li><a href="#IPv6-and-VIMAGE">IPv6 and VIMAGE</a></li><li><a href="#TCP-SMP-scalability-project">TCP SMP scalability project</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Resource-Containers">Resource Containers</a></li><li><a href="#SYSCTL-Type-Safety">SYSCTL Type Safety</a></li><li><a href="#TRIM-support-for-UFS">TRIM support for UFS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#mdocml-Replacing-groff-For-manpage-Rendering">mdocml Replacing groff For manpage Rendering</a></li><li><a href="#The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></li><li><a href="#GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid">GEOM-based ataraid(4) Replacement &#8212; geom_raid</a></li><li><a href="#gpart-Improvements">gpart Improvements</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Bringing-up-OMAP3">Bringing up OMAP3</a></li><li><a href="#FreeBSD-on-the-Playstation-3">FreeBSD on the Playstation 3</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium">Chromium</a></li><li><a href="#FreeBSD-as-Home-Theater-PC">FreeBSD as Home Theater PC</a></li><li><a href="#Port-Sandbox">Port-Sandbox</a></li><li><a href="#Portmaster">Portmaster</a></li><li><a href="#Ports-Additions">Ports Additions</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Robot-Operating-System">Robot Operating System</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FOSDEM-2011">FOSDEM 2011</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BSDInstall" href="#BSDInstall" id="BSDInstall">BSDInstall</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BSDInstall" title="http://wiki.FreeBSD.org/BSDInstall">BSDInstall Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BSDInstall" title="BSDInstall Wiki Page">http://wiki.FreeBSD.org/BSDInstall</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>BSDInstall is a replacement for the venerable sysinstall
-	installer.  It is designed to be modular and easily extensible,
-	while being fully scriptable and streamlining the installation
-	process.  It is mostly complete, and installs working systems on
-	i386, amd64, sparc64, powerpc, and powerpc64, with untested PC98
-	support.</p>
-
-      <p>New Features:</p>
-
-      <ul>
-	<li>Allows installation onto GPT disks on x86 systems</li>
-
-	<li>Can do installations spanning multiple disks</li>
-
-	<li>Allows installation into jails</li>
-
-	<li>Eases PXE installation</li>
-
-	<li>Virtualization friendly: can install from a live system onto
-	  disk images</li>
-
-	<li>Works on PowerPC</li>
-
-	<li>Streamlined system installation</li>
-
-	<li>More flexible scripting</li>
-
-	<li>Easily tweakable</li>
-
-	<li>All install CDs are live CDs</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Wireless networking configuration wizard.</li><li>ZFS installation support.</li><li>Itanium disk setup.</li></ol><hr /><h2><a name="Non-executable-Stacks" href="#Non-executable-Stacks" id="Non-executable-Stacks">Non-executable Stacks</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The support for non-executable stacks, using the approach
-	identical to one used by GNU toolchain and Linux'es, is implemented
-	for amd64 and PowerPC.  The support is already committed to HEAD.
-	For now, non-executable stacks are turned off by default.</p>
-
-      <p>I plan to provide a detailed information to ports@ and switch
-	the knob after port tree is unfrozed for 7.4/8.2 releases.</p>
-    <hr /><h2><a name="Webcamd" href="#Webcamd" id="Webcamd">Webcamd</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.selasky.org/hans_petter/video4bsd" title="http://www.selasky.org/hans_petter/video4bsd"></a></td><td>
-	    URL: <a href="http://www.selasky.org/hans_petter/video4bsd" title="">http://www.selasky.org/hans_petter/video4bsd</a></td></tr><tr><td><a href="http://www.freshports.org/multimedia/webcamd/" title="http://www.freshports.org/multimedia/webcamd/"></a></td><td>
-	    URL: <a href="http://www.freshports.org/multimedia/webcamd/" title="">http://www.freshports.org/multimedia/webcamd/</a></td></tr></table><p>
-	Contact:
-	  Hans Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>Webcamd is a small daemon that enables about 1500 different USB
-	based webcam, DVB and remote control USB devices under the
-	FreeBSD-8.0 and later operating system.  The webcam daemon is
-	basically an application which is a port of Video4Linux USB drivers
-	into userspace on FreeBSD.  The daemon currently depends on libc,
-	pthreads, libusb and libcuse4bsd.</p>
-
-      <p>During Q3 2010 webcamd got manpages thanks to Dru Lavigne.</p>
-    <h3>Open tasks:</h3><ol><li>I hope to get a Google summer of code project this year
-	building the default Linux Kernel 2.6.37+ and allowing use of
-	relevant Linux USB device drivers under FreeBSD.  Webcamd is not a
-	replacement for native FreeBSD kernel drivers and will only be used
-	when no existing FreeBSD drivers exist for a given device staying
-	clear of any GPLv2 issues.  If you are a student and/or is
-	interested in participating in such a project feel free to send an
-	e-mail to hselasky@FreeBSD.org.</li></ol><hr /><h2><a name="xz-Compression-for-Packages-and-Log-Files" href="#xz-Compression-for-Packages-and-Log-Files" id="xz-Compression-for-Packages-and-Log-Files">xz Compression for Packages and Log Files</a></h2><p>
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	</p>
-      <p>Creating and processing xz-compressed packages is now supported
-	by pkg_create(1), pkg_add(1) and bsdtar(1) in both 9-CURRENT and
-	8-STABLE.  Users can test working with .txz packages by adding
-	"PKG_SUFX=.txz" into /etc/make.conf.</p>
-
-      <p>The ports-mgmt/portupgrade utility supports .txz packages from
-	version 2.4.8 and a patch for ports-mgmt/portmaster has been
-	submitted but not yet accepted by the author.</p>
-
-      <p>A patch for newsyslog(8) with a rewrite of the use of
-	compression tools supporting xz compression is under maintainer
-	review.</p>
-    <h3>Open tasks:</h3><ol><li>Import xz(1) compression support into newsyslog(8).</li><li>Add .txz package support to ports-mgmt/portmaster.</li><li>Add .txz package support to the FreeBSD port building
-	cluster (pointyhat).</li><li>Test building all packages in .txz format and compare
-	results with .tbz.</li></ol><hr /><h2><a name="ZFS-pool-version-28" href="#ZFS-pool-version-28" id="ZFS-pool-version-28">ZFS pool version 28</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html" title="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html" title="">http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html" title="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html" title="">http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html</a></td></tr></table><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new version of the ZFS pool v28 patch was released for
-	testing, this time for 9-CURRENT and 8-STABLE.  Compared to
-	the previous patch it does include updated boot support,
-	improved sendfile(2) handling, a compatibility layer with
-	older ZFS and several other bugfixes.</p>
-
-      <p>If there are no major issues we can expect ZFS v28 imported
-	into the FreeBSD-CURRENT after 8.2 is released.</p>
-    <h3>Open tasks:</h3><ol><li>Import of ZFS v28 into FreeBSD-CURRENT.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team-Status-Report" href="#FreeBSD-Bugbusting-Team-Status-Report" id="FreeBSD-Bugbusting-Team-Status-Report">FreeBSD Bugbusting Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr></table><p>
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Volker
-	  Werth
-	 &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
-	</p>
-      <p>The number of non-ports PRs has held relatively steady over
-	the last three months, with a slightly improved resolution rate
-	being offset by a slightly increased rate of new arrivals.
-	Ports PRs have increased slightly in numbers, due in part to
-	the ports freeze in the lead up to the release of FreeBSD 7.4 and
-	FreeBSD 8.2.  The numbers traditionally drop quickly again once the
-	freeze is lifted.</p>
-
-      <p>In October, Gavin Atkinson and Mark Linimon held a session at
-	the FreeBSD Developers' Summit at EuroBSDCon, which led to some
-	productive discussions, and a number of people expressing
-	interest in becoming more involved with PR triaging and
-	resolution.</p>
-
-      <p>The bugbusting team continue work on trying to make the
-	contents of the GNATS PR database cleaner, more accessible and
-	easier for committers to find and resolve PRs, by tagging PRs
-	to indicate the areas involved, and by ensuring that there is
-	sufficient info within each PR to resolve each issue.</p>
-
-      <p>Reports continue to be produced from the PR database, all of
-	which can be found from the links above.  Committers interested
-	in custom reports are encouraged to discuss requirements with
-	bugmeister@ - we are happy to create new reports where needs are
-	identified.</p>
-
-      <p>As always, anybody interested in helping out with the PR queue
-	is encouraged to do so, the easiest way being to join us on IRC
-	in #freebsd-bugbusters on EFnet.  We are always looking for
-	additional help, whether your interests lie in triaging incoming
-	PRs, generating patches to resolve existing problems, or simply
-	helping with the database housekeeping (identifying duplicate
-	PRs, ones that have already been resolved, etc).  This is a
-	great way of getting more involved with FreeBSD!</p>
-    <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with
-	closing PRs that the team has already analyzed.</li><li>Try to get more non-committers involved with the triaging
-	of PRs as they come in, and generating patches to fix reported
-	problems.</li></ol><hr /><h2><a name="Release-Engineering-Team-Status-Report" href="#Release-Engineering-Team-Status-Report" id="Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team reports the joint release of
-	FreeBSD 7.4 and 8.2 has been delayed slightly but should be
-	completed within a week or two of the original schedule:
-	http://www.FreeBSD.org/releases/7.4R/schedule.html
-	http://www.FreeBSD.org/releases/8.2R/schedule.html</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org" title="http://www.FreeBSDFoundation.org"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org" title="">http://www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We raised $325,000 towards our goal of $350,000 for 2010! This
-	will allow us to increase our project development and equipment
-	spending for 2011.</p>
-
-      <p>We were proud to be a sponsor for EuroBSDCon 2010, BSDDay
-	Argentina 2010, MeetBSD California 2010, and NYBSDCon 2010.</p>
-
-      <p>Completed the Foundation funded projects: DAHDI Project by Max
-	Khon and BSNMP Improvements by Shteryana Sotirova.</p>
-
-      <p>We kicked off a new project by the University of Melbourne
-	called Feed-Forward Clock Synchronization Algorithms Project.  The
-	Five New TCP Congestion Control Algorithms for FreeBSD Project by
-	Swinburne University also officially started.</p>
-
-      <p>We continued our work on infrastructure projects to beef up
-	hardware for package-building, network-testing, etc.  This includes
-	purchasing equipment as well as managing equipment donations.</p>
-
-      <p>Stop by and visit with us at FOSDEM (Feb 5-6), SCALE (Feb 26),
-	AsiaBSDCon (March 17-20), and Indiana Linuxfest (March 26).</p>
-
-      <p>Read more about how we supported the project and community by
-	reading our end-of-year newsletter at: <a href="http://www.FreeBSDFoundation.org/press/2010Dec-newsletter.shtml" shape="rect">
-	  http://www.FreeBSDFoundation.org/press/2010Dec-newsletter.shtml</a>.</p>
-
-      <p>We are fund-raising for 2011 now! Find out more at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">
-	  http://www.FreeBSDFoundation.org/donate/</a>.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" id="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/" title="http://caia.swin.edu.au/urp/diffuse/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/" title="">http://caia.swin.edu.au/urp/diffuse/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="http://caia.swin.edu.au/urp/diffuse/downloads.html"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="">http://caia.swin.edu.au/urp/diffuse/downloads.html</a></td></tr></table><p>
-	Contact:
-	  Sebastian
-	  Zander
-	 &lt;<a href="mailto:szander@swin.edu.au">szander@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	</p>
-      <p>
-	<p>DIFFUSE is a system enabling FreeBSD's IPFW firewall subsystem
-	  to classify IP traffic based on statistical traffic
-	  properties.</p>
-
-	<p>With DIFFUSE, IPFW computes statistics (such as packet lengths
-	  or inter-packet time intervals) for observed flows, and uses ML
-	  (machine learning) techniques to assign flows into classes.  In
-	  addition to traditional packet inspection rules, IPFW rules may
-	  now also be expressed in terms of traffic statistics or classes
-	  identified by ML classification.  This can be helpful when direct
-	  packet inspection is problematic (perhaps for administrative
-	  reasons, or because port numbers do not reliably identify
-	  applications).</p>
-
-	<p>DIFFUSE also enables one instance of IPFW to send flow
-	  information and classes to other IPFW instances, which then can
-	  act on such traffic (e.g. prioritise, accept, deny, etc)
-	  according to its class.  This allows for distributed
-	  architectures, where classification at one location in your
-	  network is used to control fire-walling or rate-shaping actions
-	  at other locations.</p>
-
-	<p>In December 2010 we released DIFFUSE v0.1, a set of patches
-	  for FreeBSD-CURRENT.  It can be downloaded from the project's web
-	  site.  The web site also contains a more comprehensive
-	  introduction, including application examples, links to related
-	  work and documentation describing the software design.</p>
-
-	<p>We hope to release DIFFUSE v0.2 soon.  Keep an eye on the
-	  freebsd-ipfw and freebsd-net mailing lists for project-related
-	  announcements.</p>
-      </p>
-    <hr /><h2><a name="Ethernet-Switch-Framework" href="#Ethernet-Switch-Framework" id="Ethernet-Switch-Framework">Ethernet Switch Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://loos.no-ip.org/rspro/switch-1.diff" title="http://loos.no-ip.org/rspro/switch-1.diff"></a></td><td>
-	    URL: <a href="http://loos.no-ip.org/rspro/switch-1.diff" title="">http://loos.no-ip.org/rspro/switch-1.diff</a></td></tr></table><p>
-	Contact:
-	  Luiz
-	  Otavio O. Souza
-	 &lt;<a href="mailto:loos.br@gmail.com">loos.br@gmail.com</a>&gt;
-	</p>
-      <p>Implementation of a framework for ethernet switch control
-	(directly connected to the ethernet MAC controller) usually found
-	on embedded systems.  Currently based on ifconfig keywords, adds the
-	vlan control (filter/pass) on each switch port and adds the
-	possibility for the management of media state on interfaces with
-	multiple PHYs.</p>
-
-      <p>Currently, the code supports the IP175D (from some mikrotik
-      routerboards) and AR8316 (from Ubiquiti RSPRO) switches.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the IP175C driver (and maybe IP178x).</li><li>Better integration with miibus (rewrite of switchbus).</li><li>Fix (some) ifconfig keywords (better keywords, better usage
-	compatibility).</li><li>Export the ports statistics through SNMP (if available on
-	switch chip).</li><li>Add a swctl tool (?) for global settings management.</li><li>Write usage examples and the man page information about the
-	new ifconfig(8) keywords.</li></ol><hr /><h2><a name="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" id="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/5cc/" title="http://caia.swin.edu.au/freebsd/5cc/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/5cc/" title="">http://caia.swin.edu.au/freebsd/5cc/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/projects.shtml" title="http://www.FreeBSDFoundation.org/projects.shtml"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/projects.shtml" title="">http://www.FreeBSDFoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="http://people.FreeBSD.org/~lstewart/patches/5cc/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="">http://people.FreeBSD.org/~lstewart/patches/5cc/</a></td></tr></table><p>
-	Contact:
-	  David
-	  Hayes
-	 &lt;<a href="mailto:dahayes@swin.edu.au">dahayes@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lastewart@swin.edu.au">lastewart@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Bjoern
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project is nearing completion, with the following code
-	already available in the svn head branch:</p>
-
-      <ul>
-	<li>Modular congestion control framework.</li>
-
-	<li>Modularised implementations of NewReno, CUBIC and HTCP
-	  congestion control algorithms.</li>
-
-	<li>Khelp (Kernel Helper) and Hhook (Helper Hook)
-	  frameworks.</li>
-
-	<li>Basic Khelp/Hhook integration with the TCP stack.</li>
-      </ul>
-
-      <p>The ERTT (Enhanced Round Trip Time) Khelp module is days away
-	from being imported, which will then pave the way for the delay
-	based congestion control algorithms to follow.  Finally, a large
-	documentation dump will be committed in the form of new and
-	updated man pages.</p>
-
-      <p>We anticipate the project will conclude around the end of
-	January 2011.</p>
-    <h3>Open tasks:</h3><ol><li>Import the ERTT Khelp module.</li><li>Import the VEGAS, HD and CHD delay based congestion control
-	algorithm modules.</li><li>Import the documentation dump for all the code
-	contributed/developed as part of the project.</li></ol><hr /><h2><a name="FreeBSD-802.11n" href="#FreeBSD-802.11n" id="FreeBSD-802.11n">FreeBSD 802.11n</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff" title="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff" title="">http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff</a></td></tr></table><p>
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@FreeBSD.org">adrian@FreeBSD.org</a>&gt;
-	</p>
-      <ul>
-	<li>Net80211 station mode works in 2.4ghz HT/20 mode.  HT/40 and
-	  5ghz do not currently work.</li>
-
-	<li>Basic 802.11 TX and RX on the AR9160 works, from MCS0 to
-	  MCS15</li>
-
-	<li>TX A-MPDU and A-MSDU do not currently implemented - so no
-	  aggregate TX will happen</li>
-
-	<li>RX A-MPDU and A-MSDU is implemented and is supposed to work
-	  but does not &#8212; this needs to be debugged</li>
-
-	<li>802.11n RTS/CTS protection for legacy packets does not
-	  currently work.  There is some magic required to fix the TX packet
-	  length.  This is in progress.</li>
-
-	<li>WPA2 now works - a commit which enabled the hardware
-	  multicast broke AES-CCMP encryption on at least the AR9160.
-	  Further investigation is needed to fix this (and any other
-	  hardware encryption bugs that are lurking.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-VirtIO-Network-Driver" href="#FreeBSD-VirtIO-Network-Driver" id="FreeBSD-VirtIO-Network-Driver">FreeBSD VirtIO Network Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.linux-kvm.org/page/Virtio" title="http://www.linux-kvm.org/page/Virtio"></a></td><td>
-	    URL: <a href="http://www.linux-kvm.org/page/Virtio" title="">http://www.linux-kvm.org/page/Virtio</a></td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html" title="http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html" title="">http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html</a></td></tr></table><p>
-	Contact:
-	  Bryan
-	  V.
-	 &lt;<a href="mailto:deboomerang@gmail.com">deboomerang@gmail.com</a>&gt;
-	</p>
-      <p>VirtIO is a device framework offered by KVM/Qemu and Virtualbox
-	to allow guests to achieve better I/O performance.  A beta
-	network driver was made available earlier this month, and work
-	continues on completing the block device and refinements the
-	existing network driver.</p>
-    <hr /><h2><a name="Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)" href="#Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)" id="Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)">Generic IEEE 802.3 annex 31B full duplex flow control support
-      for Ethernet in mii(4)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://en.wikipedia.org/wiki/Ethernet_flow_control" title="http://en.wikipedia.org/wiki/Ethernet_flow_control"></a></td><td>
-	    URL: <a href="http://en.wikipedia.org/wiki/Ethernet_flow_control" title="">http://en.wikipedia.org/wiki/Ethernet_flow_control</a></td></tr></table><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>In r213878 a NetBSD-compatible mii_attach() was added to mii(4)
-	as an replacement for mii_phy_probe() and subsequently all Ethernet
-	device drivers in the tree which use this framework were converted
-	to take advantage of the former.  This allowed to considerably clean
-	up mii(4) as well as the converted MAC and PHY drivers and get rid
-	of quite a few hacks, amongst others the infamous "EVIL HACK".
-	However, the main motivation of this change was to allow the
-	addition of generic IEEE 802.3 annex 31B full duplex flow control
-	support to mii(4), which was ported from NetBSD but also enhanced
-	and fixed quite a bit and committed in r215297.  Along with this
-	bge(4), bce(4), msk(4), nfe(4) and stge(4) as well as brgphy(4),
-	e1000phy(4) and ip1000phy(4), which previously all implemented
-	their own flow control support based on mostly undocumented special
-	media flags separately, were converted to take advantage of the
-	generic support.  At least for CURRENT this means that these drivers
-	now no longer unconditionally advertise support for flow control
-	but only do so if flow control was selected as media option.  The
-	reason for implementing the generic flow control support that way
-	was to allow it to be switched on and off via ifconfig(8) with the
-	PHY specific default to typically being off in order to protect
-	from unwanted effects.  Subsequently support for flow control based
-	on the generic support was added to alc(4), fxp(4), cas(4), gem(4),
-	jme(4), re(4) and xl(4) as well as atphy(4), bmtphy(4), gentbi(4),
-	inphy(4), jmphy(4), nsgphy(4), nsphyter(4) and rgephy(4).  For
-	several of the remaining Ethernet drivers it also would only
-	require minor changes to enable flow control support if supported
-	by the respective MAC.  Due to the fact that each implementation
-	should be thoroughly tested and tuned this was only done for
-	drivers were hardware was available though.</p>
-
-      <p>An example for identifying support for flow control based on the
-	generic implementation in the dmesg-output for a certain
-	MAC-PHY-combination would be:</p>
-
-      <blockquote>bge0: &lt;Broadcom NetXtreme Gigabit Ethernet
-	Controller, ASIC rev. 0x002003&gt; mem 0
-	xfe010000-0xfe01ffff,0xfe000000-0xfe00ffff irq 25 at device 2.0 on
-	pci2
-	<br clear="none" />
-
-	bge0: CHIP ID 0x00002003; ASIC REV 0x02; CHIP REV 0x20; PCI-X
-	<br clear="none" />
-
-	miibus0: &lt;MII bus&gt; on bge0
-	<br clear="none" />
-
-	brgphy0: &lt;BCM5704 10/100/1000baseTX PHY&gt; PHY 1 on miibus0
-	<br clear="none" />
-
-	brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
-	1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto,
-	<strong>auto-flow</strong>
-      </blockquote>
-
-      <p>or in the output of <kbd>ifconfig -m</kbd> for a given device:</p>
-
-      <blockquote>supported media:
-	<blockquote>media autoselect
-	  <em>mediaopt flowcontrol</em>
-	</blockquote>
-      </blockquote>
-
-      <p>The latter also is what one would use to enable flow control for
-	such a device, i.e.:</p>
-
-      <blockquote>ifconfig bge0 media autoselect mediaopt
-	flowcontrol</blockquote>
-
-      <p>or in order to turn it off again:</p>
-
-      <blockquote>ifconfig bge0 media autoselect -mediaopt
-	flowcontrol</blockquote>
-
-      <p>Note that some PHY drivers, currently only rgephy(4) though, also
-	support enabling flow control support when using manual media
-	configuration like in the following example:</p>
-
-      <blockquote>ifconfig re0 media autoselect mediaopt
-	full-fuplex,flowcontrol</blockquote>
-
-      <p>In CURRENT this can also be further abbreviated (support for this
-	will eventually be merged back into the supported stable branch(es)
-	but not be present in 7.4-RELEASE or 8.2-RELEASE) as:</p>
-
-      <blockquote>ifconfig re0 media auto mediaopt fdx,flow</blockquote>
-
-      <p>For a device which has successfully negotiated flow control support
-	with its link partner will report it in the output of
-	<kbd>ifconfig</kbd> along with the available directions like in the
-	following example:</p>
-
-      <blockquote>media: Ethernet autoselect &lt;flowcontrol&gt;
-	(100baseTX &lt;full-duplex,
-	<em>flowcontrol,rxpause,txpause</em>&gt;)</blockquote>
-
-      <p>Another thing that was introduced with r215297 was generic support
-	for setting 1000baseT master mode via a media option when using
-	manual media configuration.  Consequently, brgphy(4), ciphy(4),
-	e1000phy(4) as well as ip1000phy(4) have been converted to take
-	advantage of this generic support.  At least for CURRENT this means
-	that these drivers now no longer take the link0 parameter for
-	selecting master mode but the master media option has to be used
-	instead like in the following example:</p>
-
-      <blockquote>ifconfig bge0 media 1000baseT mediaopt
-	full-duplex,master</blockquote>
-
-      <p>Selection of master mode now is also available with all other PHY
-	drivers supporting 1000baseT.</p>
-
-      <p>With the exception of the media option abbreviations all of the
-	above mentioned changes were merged into 7-STABLE in r215879 and
-	into 8-STABLE in r215881 respectively.  This means that they will be
-	part of 7.4-RELEASE and 8.2-RELEASE.  In order to no break POLA,
-	unlike as in CURRENT bge(4), bce(4), msk(4), nfe(4) and stge(4)
-	were changed to continue to always advertise support of flow
-	control to their link partners in these stable branches with no way
-	to turn that off as they also did before with their custom
-	implementations.  Additionally, brgphy(4), ciphy(4), e1000phy(4) as
-	well as ip1000phy(4) were changed to still also accept the link0
-	parameter in addition to the master media option for setting master
-	mode.</p>
-    <h3>Open tasks:</h3><ol><li>We actually miserably fail to properly document the available
-	media types and options in manual pages.  For example several of the
-	media lists in manual pages of MAC drivers like bge(4) already were
-	outdated and with the addition of generic flow control and
-	1000baseT master mode support these are now even more outdated.  Yet
-	worse is the fact that for MAC drivers which use the mii(4)
-	framework it is technically just plain wrong to include these lists
-	in their manual page as the PHY drivers actually are responsible
-	for handling the media types and options.  However, given that the
-	PHY drivers determine the available media types and options mostly
-	dynamically at run-time it generally makes no sense to have static
-	documentation of these in their manual pages (apart from the fact
-	that we currently have no manual pages for PHY drivers).  One good
-	way out of this should be to replace the media lists in MAC drivers
-	using mii(4) with just a note to check the output of
-	<kbd>ifconfig -m</kbd>
-	to get a list of the media types and options actually supported by
-	a given device and to add a generic ifmedia(4) manual page which
-	provides some general background information about media types and
-	options similar to what NetBSD and OpenBSD also have.</li></ol><hr /><h2><a name="IPv6-and-VIMAGE" href="#IPv6-and-VIMAGE" id="IPv6-and-VIMAGE">IPv6 and VIMAGE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ecdysis.viagenie.ca/" title="http://ecdysis.viagenie.ca/">NAT64 patches for pf</a></td><td>
-	    URL: <a href="http://ecdysis.viagenie.ca/" title="NAT64 patches for pf">http://ecdysis.viagenie.ca/</a></td></tr></table><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last quarter a lot of work was spent on quality time
-	hunting down and fixing open bugs and races in the network stack,
-	mostly IPv6, as well as testing and getting virtualized network
-	stack parts more stable.  Tests for the pf(4) firewall update were
-	started with VIMAGE.  In addition Viagenie's NAT64 patch was ported
-	over.</p>
-    <hr /><h2><a name="TCP-SMP-scalability-project" href="#TCP-SMP-scalability-project" id="TCP-SMP-scalability-project">TCP SMP scalability project</a></h2><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>A long-running TCP SMP scalability project is beginning to wrap
-	up, with the goal of committing a large outstanding patch to the
-	FreeBSD 9.x tree in the next month.  This work implements a
-	derivative of Willman, Rixner, and Cox's TCP connection group
-	model, blended with support for hardware load distribution
-	features in contemporary NICs (including RSS).  Additional
-	software distribution support can do work redistribution based
-	on new notions of CPU affinity for individual TCP
-	connections.</p>
-
-      <p>On-going work is refining performance on non-RSS supporting
-	configurations, and adding APIs to allow socket affinity to be
-	queried (and where supported) set by applications.  These
-	changes significantly improve network scalability by reducing
-	global lock contention, encouraging CPU affinity for
-	connections, and avoiding cache line contention.  The goal is
-	to allow steady-state TCP connections to use only CPU-local
-	cache lines, with work distributed to all CPUs.  Current
-	performance results are extremely promising.</p>
-
-      <p>This project has been sponsored by Juniper Networks.</p>
-    <h3>Open tasks:</h3><ol><li>Allow the hash model to be selected at boot-time or run-time
-	rather than compile-time; currently "options RSS" enables RSS
-	support unconditionally &#8212; for systems without RSS NICs,
-	this leads to a small one-time performance penalty at the
-	creation of each call to bind() or connect().</li><li>Add missing socket options to query (and override) default
-	CPU affinity for connections, which is derived from the active
-	software or hardware hash model.</li><li>Teach the network stack and appropriate NIC drivers to
-	propagate software-overridden connection affinity to hardware
-	using new device driver ioctls for managing TCAMs and hardware
-	hash tables.</li><li>Refine software redistribution of work in the event that
-	there are fewer hardware queues than available CPU threads in
-	which to process packets; the current prototype is able to do
-	this with significant performance benefits, but the model
-	requires refining.</li><li>Experiment with (and measure) software work redistribution
-	at run-time based on RSS bucket rearrangement.  This will
-	require a new event notification to device drivers so that
-	they can update hardware caches of the network stack's
-	authoritative table.</li><li>Commit.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Resource-Containers" href="#Resource-Containers" id="Resource-Containers">Resource Containers</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of this project is to implement resource containers and
-	a per-jail resource limits mechanism, so that system administrators
-	can partition resources like memory or CPU between jails and
-	prevent users from DoS-ing the whole system.  Project is close to
-	completion.  One big item that needs to be fixed before releasing a
-	patch for people to test is %CPU accounting; initial idea of just
-	using %CPU calculated by the scheduler turned out to be useless.
-	Implementing it cleanly will also make it easier to support other
-	similar resources (e.g. writes-per-second) in the future.</p>
-    <hr /><h2><a name="SYSCTL-Type-Safety" href="#SYSCTL-Type-Safety" id="SYSCTL-Type-Safety">SYSCTL Type Safety</a></h2><p>
-	Contact:
-	  Matthew
-	  Fleming
-	 &lt;<a href="mailto:mdf@FreeBSD.org">mdf@FreeBSD.org</a>&gt;
-	</p>
-      <p>I started upstreaming a patch from Isilon that adds
-	type-checking to the various SYSCTL_FOO and SYSCTL_ADD_FOO macros
-	for various scalar types, which has turned into quite the
-	discussion on the src mailing list.  The type-checking macros are
-	committed to sys/sysctl.h but under #if 0.</p>
-    <h3>Open tasks:</h3><ol><li>As of right now, it looks like I will be rolling a new sysctl
-	macro for the kernel that detects they type at compile time and
-	does the Right Thing.  Existing uses of the legacy SYSCTL_FOO and
-	SYSCTL_ADD_FOO for scalar types can be replaced, and will probably
-	turn into invocations of the new interface via preprocessor
-	macro.</li></ol><hr /><h2><a name="TRIM-support-for-UFS" href="#TRIM-support-for-UFS" id="TRIM-support-for-UFS">TRIM support for UFS</a></h2><p>
-	Contact:
-	  Kirk
-	  McKusick
-	 &lt;<a href="mailto:mckusick@FreeBSD.org">mckusick@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>TRIM support for UFS is implemented in HEAD.  Potentially, this
-	may increase the steady speed and longevity of SSDs.</p>
-
-      <p>Due to concerns with the speed of TRIM operations on many SSDs,
-	and not a lot of experience with the real-world behaviour, the
-	support is off by default, and should be enabled on the
-	per-filesystem basis.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="mdocml-Replacing-groff-For-manpage-Rendering" href="#mdocml-Replacing-groff-For-manpage-Rendering" id="mdocml-Replacing-groff-For-manpage-Rendering">mdocml Replacing groff For manpage Rendering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mdocml.bsd.lv/" title="http://mdocml.bsd.lv/"></a></td><td>
-	    URL: <a href="http://mdocml.bsd.lv/" title="">http://mdocml.bsd.lv/</a></td></tr><tr><td><a href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml" title="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml"></a></td><td>
-	    URL: <a href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml" title="">https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml</a></td></tr></table><p>
-	Contact:
-	  Ulrich
-	  Sp�rlein
-	 &lt;<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>&gt;
-	</p>
-      <p>Kristaps' groff-replacement (only for rendering manual pages) is
-	already available in NetBSD and OpenBSD, and used to render the
-	base system manpages for the latter.  This project aims to do
-	similar things for FreeBSD.  Since the last status report, mdocml
-	has grown rudimentary tbl(1) support and a whole lot of bugfixes
-	have gone in.  A groff port has been created and needs some more
-	testing before it can be committed to the tree.  Also the
-	WITHOUT_GROFF support in base has been fleshed out and is awaiting
-	review before commit.</p>
-    <h3>Open tasks:</h3><ol><li>Get ru@ to review WITHOUT_GROFF changes.</li><li>Get textproc/groff tested and committed.</li><li>Push more mdoc fixes into the tree.</li><li>Import mandoc(1), switch to catpages for base.  Discuss future
-	of groff in base wrt. share/doc.</li><li>Supply necessary ports infrastructure to opt-in to
-	mandoc(1).</li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project-Status-Report" href="#The-FreeBSD-German-Documentation-Project-Status-Report" id="The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">Website of the FreeBSD German Documentation Project.</a></td><td>
-	    URL: <a href="http://doc.bsdgroup.de" title="Website of the FreeBSD German Documentation Project.">http://doc.bsdgroup.de</a></td></tr></table><p>
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The committers to the German Documentation Project managed to
-	update the German documentation just in time to get the changes
-	included into the next FreeBSD releases.  The website translations
-	were also kept in sync with the ones on FreeBSD.org.</p>
-
-      <p>We tried to re-activate committers who did not contribute for
-	some time but most of them are currently unable to free up enough
-	time.  We hope to gain fresh contributor blood as we are getting
-	occasional reports about bugs and grammar in the german
-	translation.</p>
-    <h3>Open tasks:</h3><ol><li>Submit grammar, spelling or other errors you find in the
-	german documents and the website.</li><li>Translate more articles and other open handbook
-	sections.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>Although there is no radical change in this effort since the
-	last report, the www/ja and doc/ja_JP.eucJP/books/handbook have
-	constantly been updated.  During this period, generating translated
-	RSS feed for newsflash was started and links to the manual pages
-	were fixed in the Books and Articles documentation.  Some more
-	progress has been made in the Porter's Handbook and Contributing to
-	FreeBSD as well.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation of the FreeBSD <a href="http://www.FreeBSD.org/doc/ja_JP.eucJP/books/handbook/" shape="rect">
-	  Handbook</a> and contents of the
-	<a href="http://www.FreeBSD.org" shape="rect">www.FreeBSD.org</a>
-	website to the Japanese language.</li><li>Pre-/post-commit review of the translation.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="FreeBSD-Services-Control-(fsc)" href="#FreeBSD-Services-Control-(fsc)" id="FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Tom
-	  Rhodes
-	 &lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD Services Control is a mix of binaries which
-	integrate into the rc.d system and provide for service
-	(daemon) monitoring.  It knows about signals, pidfiles,
-	and uses very little resources.</p>
-
-      <p>The fscd utilities will be set up as a port and, hopefully,
-	dropped into the ports collection in the coming weeks.  This
-	will allow easier testing by everyone and it should make
-	migration into -CURRENT much easier.</p>
-    <hr /><h2><a name="GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid" href="#GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid" id="GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid">GEOM-based ataraid(4) Replacement &#8212; geom_raid</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mav/graid_design.h" title="http://people.FreeBSD.org/~mav/graid_design.h">General design description.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mav/graid_design.h" title="General design description.">http://people.FreeBSD.org/~mav/graid_design.h</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/projects/graid/" title="http://svn.FreeBSD.org/viewvc/base/projects/graid/">Project SVN branch.</a></td><td>
-	    URL: <a href="http://svn.FreeBSD.org/viewvc/base/projects/graid/" title="Project SVN branch.">http://svn.FreeBSD.org/viewvc/base/projects/graid/</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  M. Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>New project started to create GEOM-based replacement for
-	ataraid(4) &#8212; software RAID, that will be obsoleted by
-	migration to the new CAM-based ATA implementation.</p>
-
-      <p>This implementation planned with accent to modular design,
-	that includes common core and two sets of modules, handling data
-	transformations (RAID levels) and on-disk metadata formats
-	specifics.  Such design should make further extension easier.</p>
-
-      <p>At this moment work focused around RAID0/RAID1 transformations
-	and Intel metadata format.  Module is now able to read, write and
-	create Intel volumes.  Error recovery and rebuild work is now in
-	progress.  Support for other RAID levels and metadata formats,
-	supported by ataraid(4), planned later.</p>
-
-      <p>This project is sponsored by Cisco Systems, Inc.</p>
-    <h3>Open tasks:</h3><ol><li>Complete error recovery/rebuild work and stabilize modules
-	API.</li><li>Implement metadata modules for other formats.</li><li>Implement transformation modules for other RAID
-	levels.</li></ol><hr /><h2><a name="gpart-Improvements" href="#gpart-Improvements" id="gpart-Improvements">gpart Improvements</a></h2><p>
-	Contact:
-	  Andrey V.
-	  Elsukov
-	 &lt;<a href="mailto:ae@FreeBSD.org">ae@FreeBSD.org</a>&gt;
-	</p>
-      <p>GEOM class PART is the default disk partitioning class since
-	FreeBSD 8.0.  Compared to 8.1 now it does have several new features:
-	Partition resizing.  New "gpart resize" subcommand was implemented
-	for all partitioning schemes but EBR. GPT recovering.  Guid
-	Partition Table does have redundant metadata and it can be
-	recovered when some of them is damaged.  New "gpart recover"
-	subcommand was implemented for that purpose.  Ability to
-	backup/restore of partition table.  New "gpart backup" and "gpart
-	restore" subcommands were implemented.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Bringing-up-OMAP3" href="#Bringing-up-OMAP3" id="Bringing-up-OMAP3">Bringing up OMAP3</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff" title="http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff">an old patch for arm</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff" title="an old patch for arm">http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt;
-	<br />
-	Contact:
-	  Mohammed
-	  Farrag
-	 &lt;<a href="mailto:mfarrag@FreeBSD.org">mfarrag@FreeBSD.org</a>&gt;
-	</p>
-      <p>The attached file is an old patch for ARM.  We are developing new
-	patch and then we are going toward Porting OMAP3.</p>
-    <hr /><h2><a name="FreeBSD-on-the-Playstation-3" href="#FreeBSD-on-the-Playstation-3" id="FreeBSD-on-the-Playstation-3">FreeBSD on the Playstation 3</a></h2><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>On January 5, support for the Playstation 3 was imported into
-	FreeBSD 9.0-CURRENT.  This port is still somewhat raw (only
-	netbooting is supported, no access to the SPUs, etc.), but hardware
-	support should be more fleshed out by the time FreeBSD 9.0 is
-	released.  The port uses the OtherOS mechanism, and so requires a
-	"fat" console with firmware earlier than 3.21.</p>
-    <h3>Open tasks:</h3><ol><li>SATA driver.</li><li>Sound support.</li><li>SPU driver.</li></ol><hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-on-ec2/" title="http://www.daemonology.net/freebsd-on-ec2/">FreeBSD/EC2 status page</a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-on-ec2/" title="FreeBSD/EC2 status page">http://www.daemonology.net/freebsd-on-ec2/</a></td></tr></table><p>
-	Contact:
-	  Colin
-	  Percival
-	 &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD is now able to run on t1.micro instances in the Amazon
-	EC2 cloud.  FreeBSD 9.0 is not very stable, but it seems likely that
-	FreeBSD 8.2-RELEASE will approach the stability normally expected
-	of FreeBSD.</p>
-
-      <p>A list of available FreeBSD AMIs (EC2 machine images) appears on
-	the FreeBSD/EC2 status page.</p>
-    <h3>Open tasks:</h3><ol><li>Bring FreeBSD to a wider range of EC2 instance types.</li><li>Completely rework the locking in head/sys/i386/xen/pmap.c to
-	eliminate races and make 9.0-CURRENT stable under
-	paravirtualization.</li><li>Track down several possibly-related problems with scheduling
-	and timekeeping.</li><li>Fix other issues shown on the FreeBSD/EC2 status page.</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>CPUTYPE support for sparc64 has been added to CURRENT in
-	r216820.  The three flavors currently supported are
-	"ultrasparc", "ultrasparc3" and "v9".  So it is now possible to
-	let the compiler produce code optimize for the family of
-	UltraSPARC-III CPUs by setting CPUTYPE to "ultrasparc3".
-	Setting it to "ultrasparc" as well as omitting it completely
-	optimizes for UltraSPARC-I/II family CPUs as before.  Support
-	for generating generic 64-bit V9 code was mainly added for
-	reference purposes.  As it turned out, at least for SPARC64-V
-	CPUs running code optimized for UltraSPARC-III CPUs does not
-	perform measurably better than UltraSPARC-I/II one though so
-	the default is just fine for these.  This change was merged into
-	7-STABLE in r217005 and into 8-STABLE in r217004 respectively,
-	neither 7.4-RELEASE nor 8.2-RELEASE will include it
-	though.</p>
-
-      <p>Support for a certain feature available with
-	UltraSPARC-III+ and greater, i.e. with all sun4u CPUs following
-	the original UltraSPARC-III, has been added to CURRENT in
-	r216803.  The net effect of this change is that we now can use a
-	kernel TSB and thus a kernel address space of virtually any
-	size up to the full 64-bit address space on machines equipped
-	with these CPUs, apart from the fact that 1GB of address space
-	still takes up 4MB worth of data structures.  Before, the
-	theoretical limit was 16GB due to the fact that the MMUs of
-	these UltraSPARC CPUs only have 16 lockable TLB slots
-	(UltraSPARC-I/II have 64 and SPARC64 CPUs again have at least
-	32), with the actual limit being several GB below that because
-	we need some of these slots also for mapping the PROM, the
-	kernel itself and in MP-systems the per-CPU page.  Currently,
-	the kernel TSB and thus the kernel virtual address space is now
-	always sized one time the physical memory present in these
-	machines with the plan being to actually allow to it extend
-	beyond the size of the RAM as this helps especially ZFS.  Most
-	of this is implemented by patching the instructions used to
-	access the kernel TSB based on the CPU present, so the run-time
-	overhead of this change is rather low.  Once it is also enabled
-	and successfully tested with SPARC64 CPUs this change will be
-	merged back into the supported stable branch(es).</p>
-
-      <p>Theoretically it should be also possible to use the same
-	approach for the user TSB, which already is not locked into the
-	TLB but can cause nested traps.  However, for reasons I do not
-	understand yet, OpenSolaris only does this with SPARC64 CPUs.
-	On the other hand I think that also using it for the user TSB
-	and thus avoiding nested traps would get us closer to running
-	the FreeBSD/sparc64 code on machines equipped with sun4v CPUs,
-	which only supports trap level 0 and 1, too, so eventually we
-	could have a single kernel which runs on both sun4u and sun4v
-	machines (as does Linux and OpenBSD).</p>
-
-      <p>Work on adding support for Sun Fire 3800 and similar models
-	has begun but still is in its early stages.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium" href="#Chromium" id="Chromium">Chromium</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.chromium.org/Home" title="http://www.chromium.org/Home">Chromium homepage</a></td><td>
-	    URL: <a href="http://www.chromium.org/Home" title="Chromium homepage">http://www.chromium.org/Home</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~bapt/chrome9-fbsd.png" title="http://people.FreeBSD.org/~bapt/chrome9-fbsd.png">Screenshot</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bapt/chrome9-fbsd.png" title="Screenshot">http://people.FreeBSD.org/~bapt/chrome9-fbsd.png</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:freebsd-chromium@FreeBSD.org">freebsd-chromium@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are working on updating the Chromium web browser in our ports
-	to stay up to date with the latest supported release.  We currently
-	have the Chromium 9 beta running, but not all features are fully
-	implemented and the port still needs some polish before it can be
-	committed to the Ports Collection.  We have also been making
-	arrangements with Google to merge our work with their upstream,
-	which should ease the number of features and fixes we have to
-	maintain for ourselves in the future.  Our first release should be
-	in a few weeks and coincide with the official release of Chromium
-	9.</p>
-    <hr /><h2><a name="FreeBSD-as-Home-Theater-PC" href="#FreeBSD-as-Home-Theater-PC" id="FreeBSD-as-Home-Theater-PC">FreeBSD as Home Theater PC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/HTPC" title="http://wiki.FreeBSD.org/HTPC"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HTPC" title="">http://wiki.FreeBSD.org/HTPC</a></td></tr></table><p>
-	Contact:
-	  Bernhard
-	  Froehlich
-	 &lt;<a href="mailto:decke@FreeBSD.org">decke@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Juergen
-	  Lock
-	 &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD could be a much better platform for a Home Theater PC
-	than it currently is.  We are focusing on improving support for
-	media center applications.  Extending the major ports (MythTV, VDR,
-	XBMC) and create some documentation to guide interested people.</p>
-    <h3>Open tasks:</h3><ol><li>Improve remote control support in webcamd and with
-	lirc.</li><li>Port more Media Center applications (Enna, me-tv, ...).</li><li>Create a small guide on how to build a great FreeBSD Home
-	Theater PC.</li></ol><hr /><h2><a name="Port-Sandbox" href="#Port-Sandbox" id="Port-Sandbox">Port-Sandbox</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html" title="http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html">A little bit about</a></td><td>
-	    URL: <a href="http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html" title="A little bit about">http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html</a></td></tr><tr><td><a href="http://gitorious.org/port-sandbox/port-sandbox/trees/master" title="http://gitorious.org/port-sandbox/port-sandbox/trees/master">Source</a></td><td>
-	    URL: <a href="http://gitorious.org/port-sandbox/port-sandbox/trees/master" title="Source">http://gitorious.org/port-sandbox/port-sandbox/trees/master</a></td></tr><tr><td><a href="http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html" title="http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html">Screenshots</a></td><td>
-	    URL: <a href="http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html" title="Screenshots">http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html</a></td></tr></table><p>
-	Contact:
-	  Marcelo
-	  Araujo
-	 &lt;<a href="mailto:araujo@FreeBSD.org">araujo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Port-Sandbox now works properly and it is able to run by itself
-	through an embedded web server and bring a lot of information about
-	the port build process and all dependencies related.  Currently
-	Port-Sandbox is in the final stage and needs only only a few code
-	changes, more tests and should also be included in the ports
-	tree.</p>
-    <h3>Open tasks:</h3><ol><li>Change the way how it connects to database, fix it to maintain
-	a persistent connection.</li><li>Remove any kind of internal configuration from source code to
-	an external file configuration.</li><li>Create a Port-Sandbox port with all dependencies related to
-	it and test it in a clean system.</li><li>Create some documentation to let other people to keep
-	helping Port-Sandbox to grow up.</li><li>Finally, release it.</li></ol><hr /><h2><a name="Portmaster" href="#Portmaster" id="Portmaster">Portmaster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster-proposal.html" title="http://dougbarton.us/portmaster-proposal.html"></a></td><td>
-	    URL: <a href="http://dougbarton.us/portmaster-proposal.html" title="">http://dougbarton.us/portmaster-proposal.html</a></td></tr></table><p>
-	Contact:
-	  Doug
-	  Barton
-	 &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Portmaster version 3.6.1 is now in the ports tree, and the
-	emphasis in the last year has been on improving the stability and
-	performance of existing features, with a few new features sprinkled
-	in.  A lot of work has gone into error handling, both for unexpected
-	states in the ports system and for user input.  For example, all
-	prompts are now wrapped in code to verify that what was entered was
-	one of the valid options.</p>
-
-      <p>Perhaps the most interesting new element is that for the
-	features -e, -s, --clean-distfiles, --clean-packages,
-	--check-depends and --check-port-dbdir you can now specify either
-	-y or -n to automatically provide the corresponding answer to the
-	yes/no questions.  The -o, -r, and --index-only options have
-	received major overhauls, and now either work better or at least as
-	advertised.</p>
-
-      <p>There has also been a lot of work put into reducing the memory
-	footprint, especially in the environment variables that are shared
-	between the parent and child processes.  And for those operating
-	without a local ports tree (--index-only/--packages-only) all of
-	the features that <em>can</em>
-	work without the ports tree now do.</p>
-
-      <p>Significant support for the upgrading of operating without a
-	ports tree was provided by GridFury, LLC.  Their support, as well as
-	the support received from other members of the community continues
-	to be greatly appreciated.</p>
-    <h3>Open tasks:</h3><ol><li>There are still interesting features that have been suggested
-	by users listed on the page above that I have not been able to work
-	on, but would like to be able to.</li></ol><hr /><h2><a name="Ports-Additions" href="#Ports-Additions" id="Ports-Additions">Ports Additions</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bigbluebutton.org" title="http://bigbluebutton.org"></a></td><td>
-	    URL: <a href="http://bigbluebutton.org" title="">http://bigbluebutton.org</a></td></tr><tr><td><a href="http://smb4k.berlios.de/" title="http://smb4k.berlios.de/"></a></td><td>
-	    URL: <a href="http://smb4k.berlios.de/" title="">http://smb4k.berlios.de/</a></td></tr><tr><td><a href="http://www.freeswitch.org/" title="http://www.freeswitch.org/"></a></td><td>
-	    URL: <a href="http://www.freeswitch.org/" title="">http://www.freeswitch.org/</a></td></tr></table><p>
-	Contact:
-	  Josh
-	  Paetzel
-	 &lt;<a href="mailto:jpaetzel@FreeBSD.org">jpaetzel@FreeBSD.org</a>&gt;
-	</p>
-      <p>Bigbluebutton has joined the list of ready to run applications
-	in the ports tree.  Dru Lavigne has been instrumental on getting it
-	to run, as well as offering suggestions for improvements to the
-	port.</p>
-
-      <p>smb4k was updated to the latest release version, which requires
-	kde4.  This was enough of a change that a new port was created,
-	net/smb4k-kde4.  the initial port went through a number of quick
-	changes, including a patch to the source code to fix a FreeBSD
-	source code submitted by PC-BSD's Kris Moore.  This application
-	greatly eases the task of working with samba shares in a FreeBSD
-	environment.</p>
-
-      <p>Freeswitch is the result of 3 Asterisk developers working on a
-	VoIP package that fulfills their goals.  They have switched away from
-	a release model to a "just run latest SVN checkout" model.  With
-	the help of Richard Neese and Eric Crist, static snapshots of their
-	SVN repo have been taken, the port has been modified to use the
-	newer version, and extensive build and run testing has been
-	done.</p>
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td>
-	    URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/"></a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com/" title="">http://tinderbox.marcuscom.com/</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree slowly moves up closer to 23,000.  The PR count
-	still remains at about 1000.</p>
-
-      <p>In Q4 we added 2 new committers, took in 2 commit bit for safe
-	keeping, and welcomed back 4 returning committers.</p>
-
-      <p>The Ports Management team bid farewell to Kris Kennaway in
-	November 2010.  Kris was the root of krismail, the mail we all got
-	from time to time when ports broke on pointyhat.  Kris did a lot
-	of work benchmarking and testing FreeBSD for stability, scalability
-	and usability.</p>
-
-      <p>Mark Linimon has put a lot of effort into refactoring and
-	refining the code that runs the 'pointyhat' package build
-	dispatch system.  In 2010, the FreeBSD Foundation purchased for
-	portmgr a pair of new machines, pointyhat-west and
-	pointyhat-east, to take over from the existing machine.  (The
-	new machines have much greater RAM, CPU, and disk capacity.)
-	However, to properly utilize them, the existing code needed
-	to be generalized.</p>
-
-      <p>Persistent bugs, and some hardware troubles, have delayed the
-	rollout far beyond what was originally planned, but there
-	appears to be light at the end of the tunnel. (And, this time,
-	it does not appear to be an oncoming train.)</p>
-
-      <p>A document entitled "Mentoring Guidelines" as been circulated
-	among ports developers, and has been greeted with a lot of positive
-	feedback, and updates have been included.  In the short term,
-	updated copies will be maintained at
-	http://people.FreeBSD.org/~portmgr/mentor_guidelines.txt.asc.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports updates.
-	Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>ade: multiple runs for autotools refactoring</li>
-
-	<li>ed: test to replace libgcc.a with libcompiler_rt.a</li>
-
-	<li>jiles: test sh(1) against r212508</li>
-
-	<li>kde: Qt 4.7.0 update</li>
-
-	<li>kde: KDE 4.5.4 updte</li>
-
-	<li>kwm: Gnome 2.32 update</li>
-
-	<li>ports/144164: ensure package-noinstall target include rc.d
-	  scripts</li>
-
-	<li>ports/145598: include etc/devd in mtree</li>
-
-	<li>ports/145955: silence make fetch-required-list</li>
-
-	<li>ports/147701: perform DESKTOP_ENTRIES sanity check</li>
-
-	<li>ports/149657: removal of MD5 checksums</li>
-
-	<li>ports/149670: remove checks in _OPTIONSFILE</li>
-
-	<li>ports/150303: for INSTALL_LIBS</li>
-
-	<li>ports/150337: for PLIST_DIRSTRY</li>
-
-	<li>ports/151047: pass CPP to CONFIGURE/MAKE_ENV</li>
-
-	<li>ports/151799: fix PLIST_DIRSTRY</li>
-
-	<li>ports/151806: remove 2004 legacy hack</li>
-
-	<li>ports/152055 and ports/152059: for pear infrastructure</li>
-
-	<li>ports/152558: boost update</li>
-
-	<li>ports/152626: fix pkg-message display if installed from
-	  package</li>
-
-	<li>ports/152964: embed LICENSE name for STDOUT</li>
-
-	<li>ports/153018: implement variables in Mozilla
-	  dependencies</li>
-
-	<li>ports/153033: fix un-escaped shell metacharacters</li>
-
-	<li>ports/153041: clean up ruby plists</li>
-
-	<li>ports/153132: autotools cleanup</li>
-
-	<li>ports/153318: set PGSQL default to 8.4</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Looking for help fixing <url link="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports
-	broken on CURRENT</url>.</li><li>Looking for help with <url link="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures">
-	Tier-2 architectures</url>.</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing and closing.</li></ol><hr /><h2><a name="Robot-Operating-System" href="#Robot-Operating-System" id="Robot-Operating-System">Robot Operating System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.ros.org/wiki/" title="http://www.ros.org/wiki/">ROS website</a></td><td>
-	    URL: <a href="http://www.ros.org/wiki/" title="ROS website">http://www.ros.org/wiki/</a></td></tr><tr><td><a href="ftp://rene-ladan.nl/pub/ros-freebsd.pdf" title="ftp://rene-ladan.nl/pub/ros-freebsd.pdf">Presentation</a></td><td>
-	    URL: <a href="ftp://rene-ladan.nl/pub/ros-freebsd.pdf" title="Presentation">ftp://rene-ladan.nl/pub/ros-freebsd.pdf</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>&gt;
-	</p>
-      <p>Porting ROS to FreeBSD started in March 2010.  In May 2010, it
-	was possible to build  <filename role="package">devel/ros</filename>
-	without needing to apply patches, but some more changes were
-	necessary to be able to write a port for it.  Currently this and
-	several other ports related to ROS are available, most notably
-	<filename role="package">devel/ros-tutorials</filename>
-	to get up and running with ROS and
-	<filename role="package">devel/ros-nxt</filename>
-	to use LEGO Mindstorms NXT robots with ROS and FreeBSD.</p>
-    <h3>Open tasks:</h3><ol><li>Port the software required for nxt-rviz-plugin, which is part
-	of devel/ros-nxt but currently excluded from the build.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="FOSDEM-2011" href="#FOSDEM-2011" id="FOSDEM-2011">FOSDEM 2011</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FOSDEM.org" title="http://www.FOSDEM.org"></a></td><td>
-	    URL: <a href="http://www.FOSDEM.org" title="">http://www.FOSDEM.org</a></td></tr></table><p>
-	Contact:
-	  Marius
-	  Nuennerich
-	 &lt;<a href="mailto:marius@nuenneri.ch">marius@nuenneri.ch</a>&gt;
-	<br />
-	Contact:
-	  Daniel
-	  Seuffert
-	 &lt;<a href="mailto:ds@FreeBSD.org">ds@FreeBSD.org</a>&gt;
-	</p>
-      <p>FOSDEM 2011 will be held from Saturday, February 5th to
-	Sunday February 6th in Brussels, Belgium.  We will have a FreeBSD
-	booth and a developers room.  At the booth there will be
-	friendly supporters and a FreeBSD Foundation member answering
-	questions.  The devroom will have 6 1-hour long talks about
-	different topics, technical and social.  FOSDEM is one of the
-	biggest open-source events in Europe. It is completly free and
-	no registration is required.</p>
-    <h3>Open tasks:</h3><ol><li>Get more people involved as helpers for the booth and the
-	devroom are still needed.  Please contact Daniel or Marius if
-	you want to help out.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2011-01-2011-03.html b/website/content/en/status/report-2011-01-2011-03.html
deleted file mode 100644
index d9b86baa4a..0000000000
--- a/website/content/en/status/report-2011-01-2011-03.html
+++ /dev/null
@@ -1,1326 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between January and March
-      2011.  It is the first of the four reports planned for 2011.  During
-      this quarter, the work was focused on releasing the new minor
-      versions of FreeBSD, 7.4 and 8.2, which were released in February 2011.
-      Currently, the project is starting to work on the next major version,
-      9.0.</p><p>Thanks to all the reporters for the excellent work! This report
-      contains 34 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between April and June 2011 is July 15th, 2011.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Bringing-up-OMAP3">Bringing up OMAP3</a></li><li><a href="#GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid.">GEOM-based ataraid(4) Replacement &#8212; geom_raid.</a></li><li><a href="#HAST-(Highly-Available-Storage)">HAST (Highly Available Storage)</a></li><li><a href="#New-FreeBSD-Installer">New FreeBSD Installer</a></li><li><a href="#OpenAFS-Port">OpenAFS Port</a></li><li><a href="#pfSense">pfSense</a></li><li><a href="#RCTL,-aka-Resource-Containers">RCTL, aka Resource Containers</a></li><li><a href="#ZFSv28-available-in-FreeBSD-9-CURRENT">ZFSv28 available in FreeBSD 9-CURRENT</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-NYI-Admins-Status-Report">FreeBSD NYI Admins Status Report</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></li><li><a href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Journaled-Soft-Updates">Journaled Soft Updates</a></li><li><a href="#Linux-Compatibility-Layer---DVB-and-V4L2-Support">Linux Compatibility Layer - DVB and V4L2 Support</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#New-FreeBSD-Handbook-Section-Covering-HAST">New FreeBSD Handbook Section Covering HAST</a></li><li><a href="#The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li><li><a href="#Webcam-and-DVB-Compatibility-List">Webcam and DVB Compatibility List</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-on-Marvell-Raid-on-Chip">FreeBSD/arm on Marvell Raid-on-Chip</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/powerpc-on-Freescale-QorIQ">FreeBSD/powerpc on Freescale QorIQ</a></li><li><a href="#MIPS/Octeon-Support-and-bootinfo">MIPS/Octeon Support and bootinfo</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-as-Home-Theater-PC">FreeBSD as Home Theater PC</a></li><li><a href="#FreeBSD-Chromium">FreeBSD Chromium</a></li><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#KDE-FreeBSD">KDE-FreeBSD</a></li><li><a href="#Linux-Emulation-Ports">Linux Emulation Ports</a></li><li><a href="#Portmaster">Portmaster</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#www/apache22-Default">www/apache22 Default</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan">BSDCan</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Extfs-Status-Report">Extfs Status Report</a></li><li><a href="#Google-Summer-of-Code-2011">Google Summer of Code 2011</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Bringing-up-OMAP3" href="#Bringing-up-OMAP3" id="Bringing-up-OMAP3">Bringing up OMAP3</a></h2><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt;
-	<br />
-	Contact:
-	  Mohammed
-	  Farrag
-	 &lt;<a href="mailto:mfarrag@FreeBSD.org">mfarrag@FreeBSD.org</a>&gt;
-	</p>
-      <p>OMAP3 Emulation:</p>
-
-      <ul>
-	<li>Step #1: qemu-omap3 isn't ported to FreeBSD yet.  So,</li>
-	<li>Step #2: Use qemu-omap3 on Gentoo Host ..</li>
-	<li>Step #3: Is the end reached ?! No, bcz qemu-omap3 is not
-	  full.  So, go to step #4.</li>
-	<li>Step #4: Use Meego &gt;&gt; Download Ubuntu 10.10 &gt;&gt;
-	  Install it, and</li>
-	<li>Step #5: Compile FreeBSD kernel, Create root file system,
-	  mkimage, Emulate using Meego.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Device Drivers for OMAP3 Processors.</li></ol><hr /><h2><a name="GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid." href="#GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid." id="GEOM-based-ataraid(4)-Replacement-&#8212;-geom_raid.">GEOM-based ataraid(4) Replacement &#8212; geom_raid.</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  M. Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new RAID GEOM class (geom_raid) was added to FreeBSD 9-CURRENT, to
-	replace ataraid(4) in supporting various BIOS-based software RAIDs.
-	Unlike ataraid(4) this implementation does not depend on legacy
-	ata(4) subsystem and can be used with any disk drivers, including
-	new CAM-based ones (ahci(4), siis(4), mvs(4) and ata(4) with
-	`options ATA_CAM`).  To make code more readable and extensible, this
-	implementation follows modular design, including a core part and two
-	sets of modules, implementing support for different metadata
-	formats and RAID levels.</p>
-
-      <p>Support for such popular metadata formats is now implemented:
-	Intel, JMicron, NVIDIA, Promise (also used by AMD/ATI) and
-	SiliconImage.</p>
-
-      <p>Such RAID levels are now supported: RAID0, RAID1, RAID1E,
-	RAID10, SINGLE, CONCAT.</p>
-
-      <p>For any all of these RAID levels and metadata formats this class
-	supports full cycle of volume operations: reading, writing,
-	creation, deletion, disk removal and insertion, rebuilding, dirty
-	shutdown detection and resynchronization, bad sector recovery,
-	faulty disks tracking, hot-spare disks.  For Intel and Promise
-	formats there is support for multiple volumes per disk set.</p>
-
-      <p>See the graid(8) manual page for additional details.</p>
-
-      <p>Sponsored by: Cisco Systems, Inc. and iXsystems, Inc.</p>
-    <h3>Open tasks:</h3><ol><li>Implement metadata modules for other formats (DDF, Highpoint,
-	VIA, ...).</li><li>Implement transformation modules for other RAID levels
-	(RAID5, ...).</li></ol><hr /><h2><a name="HAST-(Highly-Available-Storage)" href="#HAST-(Highly-Available-Storage)" id="HAST-(Highly-Available-Storage)">HAST (Highly Available Storage)</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-	  Mikolaj
-	  Golub
-	 &lt;<a href="mailto:trociny@FreeBSD.org">trociny@FreeBSD.org</a>&gt;
-	</p>
-      <p>HAST development is progressing nicely.  Mikolaj Golub who contributes
-	to HAST is now a FreeBSD src committer.  Some changes worth noting since
-	the last report:</p>
-
-      <ul>
-	<li>Compression of the data being sent over the network. This can
-	  speed up especially synchronization process.</li>
-	<li>Optional checksuming for the data being send over the
-	  network.</li>
-	<li>Capsicum sandboxing for secondary node and hastctl.</li>
-	<li>Chroot+setuid+setgid sandboxing for primary node.</li>
-	<li>Allow administrators to specify source IP address for
-	  connections.</li>
-	<li>When changing role wait for a while for the other node to
-	  switch from primary to secondary to avoid split-brain.</li>
-	<li>Many bug fixes.</li>
-      </ul>
-    <hr /><h2><a name="New-FreeBSD-Installer" href="#New-FreeBSD-Installer" id="New-FreeBSD-Installer">New FreeBSD Installer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BSDInstall" title="http://wiki.FreeBSD.org/BSDInstall">BSDInstall Wiki Page (with test images)</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BSDInstall" title="BSDInstall Wiki Page (with test images)">http://wiki.FreeBSD.org/BSDInstall</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/PCBSDInstallMerge" title="http://wiki.FreeBSD.org/PCBSDInstallMerge">Wiki for Integration Plan with PC-BSD installer</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PCBSDInstallMerge" title="Wiki for Integration Plan with PC-BSD installer">http://wiki.FreeBSD.org/PCBSDInstallMerge</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>On March 14th, sysinstall was replaced on the 9.0 snapshot media
-	by a new, modular installer called BSDInstall.  This adds support
-	for a wide variety of new features while simplifying the
-	installation process.  Testing before the 9.0 release will be very
-	much appreciated -- CD and memory stick images for a variety of
-	platforms are linked from the BSDInstall wiki page.</p>
-
-      <p>Interesting features:</p>
-
-      <ul>
-	<li>Install CD media are always live CDs</li>
-	<li>Installations spanning multiple disks</li>
-	<li>Wireless setup</li>
-	<li>GPT disk formatting</li>
-	<li>Virtualization friendly: can install from a live system onto
-	  disk images</li>
-	<li>Easily hackable and more modular than sysinstall</li>
-	<li>Greater flexibility: shells available throughout the
-	  installation</li>
-      </ul>
-
-      <p>Work is presently ongoing to integrate this installer with the
-	backend provided by pc-sysinstall (second wiki link).</p>
-    <h3>Open tasks:</h3><ol><li>ZFS installation support.</li><li>IA64 disk setup.</li></ol><hr /><h2><a name="OpenAFS-Port" href="#OpenAFS-Port" id="OpenAFS-Port">OpenAFS Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openafs.org" title="http://openafs.org">OpenAFS home page</a></td><td>
-	    URL: <a href="http://openafs.org" title="OpenAFS home page">http://openafs.org</a></td></tr><tr><td><a href="http://web.mit.edu/freebsd/openafs/openafs.shar" title="http://web.mit.edu/freebsd/openafs/openafs.shar">FreeBSD port for OpenAFS 1.6.0 prerelease 4</a></td><td>
-	    URL: <a href="http://web.mit.edu/freebsd/openafs/openafs.shar" title="FreeBSD port for OpenAFS 1.6.0 prerelease 4">http://web.mit.edu/freebsd/openafs/openafs.shar</a></td></tr></table><p>
-	Contact:
-	  Benjamin
-	  Kaduk
-	 &lt;<a href="mailto:kaduk@mit.edu">kaduk@mit.edu</a>&gt;
-	<br />
-	Contact:
-	  Derrick
-	  Brashear
-	 &lt;<a href="mailto:shadow@gmail.com">shadow@gmail.com</a>&gt;
-	</p>
-      <p>AFS is a distributed network filesystem that originated from the
-	Andrew Project at Carnegie-Mellon University.  The OpenAFS client
-	implementation has not been particularly useful on FreeBSD since the
-	FreeBSD 4.X releases.  Work covered in previous reports brought the
-	OpenAFS client to a useful form on 9.0-CURRENT, though with some
-	rough edges.  Since our last report, we have fixed several bugs that
-	were impacting usability, and we expect the upcoming 1.6.0 release
-	to be usable for regular client workloads (though not heavy load).
-	Accordingly, we have submitted packaging for inclusion in the Ports
-	Collection (PR ports/152467).</p>
-
-      <p>There are several known outstanding issues that are being worked
-	on, but detailed bug reports are welcome at
-	port-freebsd@openafs.org.</p>
-    <h3>Open tasks:</h3><ol><li>Update VFS locking to allow the use of disk-based client
-	caches as well as memory-based caches.</li><li>Track down races and deadlocks that may appear under
-	load.</li><li>Integrate with the bsd.kmod.mk kernel-module build
-	infrastructure.</li><li>Eliminate a moderate memory leak from the kernel
-	module.</li><li>PAG (Process Authentication Group) support is not
-	functional.</li></ol><hr /><h2><a name="pfSense" href="#pfSense" id="pfSense">pfSense</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pfsense.org" title="http://www.pfsense.org">pfSense home page</a></td><td>
-	    URL: <a href="http://www.pfsense.org" title="pfSense home page">http://www.pfsense.org</a></td></tr></table><p>
-	Contact:
-	  Scott
-	  Ullrich
-	 &lt;<a href="mailto:sullrich@FreeBSD.org">sullrich@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Chris
-	  Buechler
-	 &lt;<a href="mailto:cmb@pfsense.org">cmb@pfsense.org</a>&gt;
-	<br />
-	Contact:
-	  Ermal
-	  Luci
-	 &lt;<a href="mailto:eri@FreeBSD.org">eri@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on 2.0 is rapidly coming to an end.  We released RC1 around
-	Feb 25 2011 and so far it seems to be rather stable.  2.0 is our first
-	major release in 2 years and almost all limitations of the previous
-	version has been overcome.</p>
-    <h3>Open tasks:</h3><ol><li>Finish testing RC1 and certify for release.</li></ol><hr /><h2><a name="RCTL,-aka-Resource-Containers" href="#RCTL,-aka-Resource-Containers" id="RCTL,-aka-Resource-Containers">RCTL, aka Resource Containers</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most of the code has already been merged into CURRENT.  There are
-	two remaining problems I would like to solve before 9.0-RELEASE - see
-	below - but otherwise, the code is stable; please test and report
-	any problems.  You will need to rebuild the kernel with "options
-	RACCT" and "options RCTL".  The rctl(8) manual page should be a good
-	introduction on how to use it.</p>
-
-      <p>This project was sponsored by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Reimplementing %CPU accounting and CPU throttling.</li><li>Making jail rules persistent - right now, one cannot add jail
-	rule before that jail is created, which makes it impossible to put
-	them into /etc/rctl.conf; also, rules disappear when jail gets
-	destroyed.</li></ol><hr /><h2><a name="ZFSv28-available-in-FreeBSD-9-CURRENT" href="#ZFSv28-available-in-FreeBSD-9-CURRENT" id="ZFSv28-available-in-FreeBSD-9-CURRENT">ZFSv28 available in FreeBSD 9-CURRENT</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	</p>
-      <p>ZFS v28 is now in HEAD!  Test, test, test and test.  Pretty please.
-	New features include:</p>
-
-      <ul>
-	<li>Data deduplication.</li>
-	<li>Triple parity RAIDZ (RAIDZ3).</li>
-	<li>zfs diff.</li>
-	<li>zpool split.</li>
-	<li>Snapshot holds.</li>
-	<li>zpool import -F.  Allows to rewind corrupted pool to earlier
-	  transaction group.</li>
-	<li>Possibility to import pool in read-only mode.</li>
-      </ul>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats">FreeBSD Support page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="FreeBSD Support page">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting">Resources and documentation available for Bugbusting</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="Resources and documentation available for Bugbusting">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/">Links to all of the auto-generated PR reports</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="Links to all of the auto-generated PR reports">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr></table><p>
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Volker
-	  Werth
-	 &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
-	</p>
-      <p>The bugmeister team is happy to welcome Eitan Adler (eadler@) as
-	the newest GNATS-only contributor.  Eitan has been helping triage
-	new bugs as they come in, as well as making good progress on many
-	of the older bugs, closing duplicates and obsolete bugs and
-	contacting submitters for extra information where necessary.  For
-	the first time in a long time we managed to get below 6000 open
-	PRs, in no small part due to Eitan's efforts.  Welcome aboard!</p>
-
-      <p>PRs continue to be classified as they arrive, by adding 'tags'
-	to the subject lines corresponding to the kernel subsystem
-	involved, or man page references for userland PRs.  Reports are
-	generated from these nightly, grouping related PRs into one place,
-	sorted by tag or man page.  This allows an interested party working
-	in one area or on one subsystem to easily find related bugs and
-	issues in the same area, which has proven quite effective in
-	getting some of the older bug reports closed.  These reports can all
-	be found by following the third link above.</p>
-
-      <p>We continue to look for ideas for other reports that may help
-	improve the PR closure rate.  If you have any suggestions for
-	reports which would contribute positively to the way you work,
-	please email bugmeister@ and we shall try to produce such a
-	report.</p>
-
-      <p>Our clearance rate of PRs, especially in kern and bin, seems to
-	be improving.  The number of non-ports PRs has stayed almost
-	constant since the last status report.</p>
-
-      <p>As always, anybody interested in helping out with the PR queue
-	is welcome to join us in #freebsd-bugbusters on EFnet.  We are
-	always looking for additional help, whether your interests lie in
-	triaging incoming PRs, generating patches to resolve existing
-	problems, or simply helping with the database housekeeping
-	(identifying duplicate PRs, ones that have already been resolved,
-	etc).  This is a great way of getting more involved with FreeBSD!</p>
-    <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with
-	closing PRs that the team has already analyzed.</li></ol><hr /><h2><a name="FreeBSD-NYI-Admins-Status-Report" href="#FreeBSD-NYI-Admins-Status-Report" id="FreeBSD-NYI-Admins-Status-Report">FreeBSD NYI Admins Status Report</a></h2><p>
-	Contact:
-	  NYI Admins Team
-	 &lt;<a href="mailto:nyi-admin@FreeBSD.org">nyi-admin@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD.org site at New York Internet is progressing, though
-	more slowly than we had hoped.  Due to problems with the old power
-	controllers and serial console servers, new equipment has been
-	bought by the FreeBSD Foundation.  Installing the new equipment
-	required re-racking all the existing servers which was done by the
-	local FreeBSD team (Steven Kreuzer and John Baldwin).</p>
-
-      <p>For basic infrastructure at the site (such as DHCP, DNS, console
-	etc.) the FreeBSD Foundation bought some new servers which are in the
-	process of being configured.</p>
-
-      <p>The FreeBSD Ports team are currently using 9 of the NYI servers for
-	package building.</p>
-    <h3>Open tasks:</h3><ol><li>We are looking for a storage system (15TB+) for keeping
-	replicas of all the main FreeBSD.org systems, a full ftp-archive
-	mirror, site local files etc.</li></ol><hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDfoundation.org" title="http://www.FreeBSDfoundation.org"></a></td><td>
-	    URL: <a href="http://www.FreeBSDfoundation.org" title="">http://www.FreeBSDfoundation.org</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We created our <a href="http://www.FreeBSDfoundation.org/documents/Budget2011.pdf" shape="rect">
-	2011 budget</a>.  Some of our plans for 2011 include spending
-	$125,000 on project development and $75,000 on equipment to
-	build up FreeBSD facilities in three locations.</p>
-
-      <p>We were proud to be a sponsor for AsiaBSDCon 2011 in Tokyo.  We
-	also committed to sponsoring BSDCan 2011 in May, and EuroBSDCon
-	2011 in October.  The Foundation was also represented at SCALE in
-	Los Angeles, Indiana LinuxFest in Indianapolis, and Flourish in
-	Chicago.</p>
-
-      <p>Completed Foundation-funded projects: <a href="http://www.FreeBSDfoundation.org/announcements.shtml#Swinburne" shape="rect">
-	  Five New TCP Congestion Control Algorithms project</a> by
-	Swinburne University and Resource Containers project by
-	Edward Napierala.</p>
-
-      <p>In February we visited companies in the Bay Area that use FreeBSD.
-	Our goal was to promote FreeBSD, better understand their interests and
-	needs, and help facilitate stronger relationships between these
-	companies and the Project.  The presentations we gave included the
-	benefits of FreeBSD, Project road-map, potential areas of
-	collaboration, case studies, and how the Foundation supports the
-	project.  By visiting in person we were able to show our commitment
-	to the Project and respond directly to questions and concerns they
-	may have had.  We were pleased with the positive responses we
-	received and plan on visiting more companies in the future.</p>
-
-      <p>We are funding two new projects.  The first project is
-	Implementing Support of GEM, KMS, and DRI for Intel Drivers by
-	Konstantin Belousov.  The second is Improving the Maturity of IPv6
-	Support of FreeBSD and PC-BSD by Bjoern Zeeb.</p>
-
-      <p>We continued our work on infrastructure projects to beef up
-	hardware for package-building, network-testing, etc.  This includes
-	purchasing equipment as well as managing equipment donations.</p>
-
-      <p>Stop by and visit with us at BSDCan (May 13-14) and SouthEast
-	LinuxFest (June 10-12).</p>
-
-      <p>The work above as well as many other tasks we do for the
-	project, couldn't be done without donations.  Please help us by
-	making a donation or asking your company to make a donation.  We
-	would be happy to send marketing literature to you or your company.
-	Find out how to make a donation at <a href="http://www.FreeBSDfoundation.org/donate/" shape="rect">
-	  http://www.FreeBSDfoundation.org/donate/</a>.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" id="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/" title="http://caia.swin.edu.au/urp/diffuse/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/" title="">http://caia.swin.edu.au/urp/diffuse/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="http://caia.swin.edu.au/urp/diffuse/downloads.html"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="">http://caia.swin.edu.au/urp/diffuse/downloads.html</a></td></tr></table><p>
-	Contact:
-	  Sebastian
-	  Zander
-	 &lt;<a href="mailto:szander@swin.edu.au">szander@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	</p>
-      <p>DIFFUSE is a system enabling FreeBSD's IPFW firewall subsystem to
-	classify IP traffic based on statistical traffic properties.</p>
-
-      <p>With DIFFUSE, IPFW computes statistics (such as packet lengths
-	or inter-packet time intervals) for observed flows, and uses ML
-	(machine learning) to classify flows into classes.  In addition to
-	traditional packet inspection rules, IPFW rules may now also be
-	expressed in terms of traffic statistics or classes identified by
-	ML classification.  This can be helpful when direct packet
-	inspection is problematic (perhaps for administrative reasons, or
-	because port numbers do not reliably identify applications).</p>
-
-      <p>DIFFUSE also enables one instance of IPFW to send flow
-	information and classes to other IPFW instances, which then can act
-	on such traffic (e.g. prioritise, accept, deny, etc.) according to
-	its class.  This allows for distributed architectures, where
-	classification at one location in your network is used to control
-	fire-walling or rate-shaping actions at other locations.</p>
-
-      <p>DIFFUSE is a set of patches for FreeBSD-CURRENT.  It can be
-	downloaded from the project's web site.  The web site also contains
-	a more comprehensive introduction, including application examples,
-	links to related work and documentation.</p>
-
-      <p>In February 2011 we released DIFFUSE v0.2.2.  This release
-	contains a number of bug fixes and new features.  Most notably since
-	version 0.2 there is a tool to build classifier models, and there
-	is a feature module and classifier model to classify Skype
-	traffic.</p>
-
-      <p>We hope to release DIFFUSE v0.3 soon.  Keep an eye on the
-	freebsd-ipfw and freebsd-net mailing lists for project-related
-	announcements.</p>
-    <hr /><h2><a name="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" id="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/5cc/" title="http://caia.swin.edu.au/freebsd/5cc/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/5cc/" title="">http://caia.swin.edu.au/freebsd/5cc/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/projects.shtml" title="http://www.FreeBSDFoundation.org/projects.shtml"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/projects.shtml" title="">http://www.FreeBSDFoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://FreeBSDfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-congestion.html" title="http://FreeBSDfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-congestion.html"></a></td><td>
-	    URL: <a href="http://FreeBSDfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-congestion.html" title="">http://FreeBSDfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-congestion.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="http://people.FreeBSD.org/~lstewart/patches/5cc/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="">http://people.FreeBSD.org/~lstewart/patches/5cc/</a></td></tr></table><p>
-	Contact:
-	  David
-	  Hayes
-	 &lt;<a href="mailto:dahayes@swin.edu.au">dahayes@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lastewart@swin.edu.au">lastewart@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Bjoern
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project is now complete, with the following code available
-	in the svn head branch:</p>
-
-      <ul>
-	<li>Modular congestion control framework.</li>
-	<li>Khelp (Kernel Helper) and Hhook (Helper Hook)
-	frameworks.</li>
-	<li>Basic Khelp/Hhook integration with the TCP stack.</li>
-	<li>Enhanced Round Trip Time (ERTT) Khelp module.</li>
-	<li>Modularised implementations of NewReno, CUBIC, H-TCP, Vegas,
-	  Hamilton-Delay and CAIA-Hamilton-Delay congestion control
-	  algorithms.</li>
-      </ul>
-
-      <p>In addition to the code, a large set of documentation was
-	committed (see the following man pages: cc(4), cc_newreno(4),
-	cc_cubic(4), cc_htcp(4), cc_vegas(4), cc_hd(4), cc_chd(4),
-	h_ertt(4), cc(9), khelp(9), hhook(9)) and a <a href="http://caia.swin.edu.au/reports/110228A/CAIA-TR-110228A.pdf" shape="rect">
-	technical report</a> was released which evaluates the
-	computational overhead associated with TCP before and after
-	the project's changes.</p>
-
-      <p>A candidate patch to MFC the modular congestion control
-	framework to the 8-STABLE branch is ready for testing  <a href="http://people.FreeBSD.org/~lstewart/patches/5cc/modularcc_mfc_8.x.r219091.patch" shape="rect">
-	here</a>.  If you try the patch, please send a note detailing
-	your experience (positive or negative) to Lawrence
-	Stewart.</p>
-
-      <p>Thanks go to the FreeBSD Foundation for funding this work, to the
-	project's technical reviewers for providing detailed feedback, and
-	to all FreeBSD users who have provided testing feedback thus far.</p>
-    <h3>Open tasks:</h3><ol><li>Test <a href="http://people.FreeBSD.org/~lstewart/patches/5cc/modularcc_mfc_8.x.r219091.patch" shape="rect">
-	  8-STABLE MFC candidate patch</a> and do the merge in time
-	  for 8.3-RELEASE.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Journaled-Soft-Updates" href="#Journaled-Soft-Updates" id="Journaled-Soft-Updates">Journaled Soft Updates</a></h2><p>
-	Contact:
-	  Jeff
-	  Roberson
-	 &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kirk
-	  McKusick
-	 &lt;<a href="mailto:mckusick@mckusick.com">mckusick@mckusick.com</a>&gt;
-	</p>
-      <p>All known problems with journaled soft updates have been fixed
-	in head.  If you have any problems while running with journaled soft
-	updates, please report them to us.</p>
-
-      <p>We have addressed several performance issues that have been
-	brought to our attention.  If you have any performance problems
-	while running with journaled soft updates, please report them to
-	us.</p>
-
-      <p>We have improved the recovery of resources when running with
-	soft updates on small (root) filesystems.  We anticipate being able
-	to use soft updates for root filesystems in the 9.0 system.</p>
-
-      <p>We expect to have journaled soft updates default to enabled in
-	the 9.0 system.  We encourage users of -CURRENT to enable journaled
-	soft updates to help shake out any remaining performance problems
-	and bugs.</p>
-    <hr /><h2><a name="Linux-Compatibility-Layer---DVB-and-V4L2-Support" href="#Linux-Compatibility-Layer---DVB-and-V4L2-Support" id="Linux-Compatibility-Layer---DVB-and-V4L2-Support">Linux Compatibility Layer - DVB and V4L2 Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~nox/dvb/" title="http://people.FreeBSD.org/~nox/dvb/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~nox/dvb/" title="">http://people.FreeBSD.org/~nox/dvb/</a></td></tr></table><p>
-	Contact:
-	  Juergen
-	  Lock
-	 &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	</p>
-      <p>Following (separate) discussions on the mailing lists I have
-	made patches to add DVB and V4L2 ioctl translation support to the
-	Linux compatibility layer, allowing Linux apps like SageTV, Skype,
-	and Flash to use DVB/ATSC tuners and webcams that previously only
-	worked for native FreeBSD apps. (Most of this hardware uses Linux
-	drivers via the <a href="http://www.freshports.org/multimedia/webcamd" shape="rect">
-	  multimedia/webcamd</a> port.)</p>
-    <h3>Open tasks:</h3><ol><li>Handle the remaining ioctls that (I think) are not used by
-	DVB tuners/cameras supported by webcamd (it only supports USB
-	devices, the unhandled ioctls mostly have to do with video overlays
-	and hardware MPEG2 decoding on analog or DVB tuners, features that
-	AFAIK don't exist on USB hardware.)</li><li>Make the DVB support a port because there were concerns
-	putting it in base due to the LGPL in one of the header files even
-	though I already separated out the code into an extra kld.
-	(linux_dvbwrapper.ko)</li><li>Get the patches polished and committed. :) (Until they are
-	you can check my <a href="http://people.FreeBSD.org/~nox/dvb/" shape="rect">DVB page</a>
-	and the freebsd-emulation@ mailing list for updates.)</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="New-FreeBSD-Handbook-Section-Covering-HAST" href="#New-FreeBSD-Handbook-Section-Covering-HAST" id="New-FreeBSD-Handbook-Section-Covering-HAST">New FreeBSD Handbook Section Covering HAST</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/disks-hast.html" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/disks-hast.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/disks-hast.html" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/disks-hast.html</a></td></tr></table><p>
-	Contact:
-	  Daniel
-	  Gerzo
-	 &lt;<a href="mailto:danger@FreeBSD.org">danger@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new FreeBSD Handbook section covering the Highly Available
-	STorage, or HAST developed by Pawel Jakub Dawidek has been
-	recently added.  In this section, you will learn what HAST is,
-	how it works, which features it provides and how to set it up.
-	It also includes a working example on how it can be used
-	together with devd(8) and CARP.  Enjoy your reading.</p>
-    <hr /><h2><a name="The-FreeBSD-German-Documentation-Project-Status-Report" href="#The-FreeBSD-German-Documentation-Project-Status-Report" id="The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">Website of the FreeBSD German Documentation Project.</a></td><td>
-	    URL: <a href="http://doc.bsdgroup.de" title="Website of the FreeBSD German Documentation Project.">http://doc.bsdgroup.de</a></td></tr></table><p>
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>Benedict Reuschling contributed the translation of the new
-	handbook section about HAST, while Benjamin Lukas was working on
-	the first translation of the firewall chapter of the handbook.  The
-	committers to the German Documentation Project were busy with
-	keeping the existing German documentation up-to-date.  The website
-	translations were also kept in sync with the ones on FreeBSD.org.</p>
-
-      <p>We tried to re-activate committers who did not contribute for
-	some time but most of them are currently unable to free up enough
-	time.  We hope to gain fresh contributor blood as we are getting
-	occasional reports about bugs and grammar in the german
-	translation.</p>
-     <h3>Open tasks:</h3><ol><li>Submit grammar, spelling or other errors you find in the
-	german documents and the website.</li><li>Translate more articles and other open handbook
-	sections.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>The www/ja and doc/ja_JP.eucJP/books/handbook have constantly
-	been updated.  During this period, translation of the handbook
-	installation page was finished.  The following chapters are now
-	synchronized with the English version:</p>
-
-      <ul>
-	<li>introduction</li>
-	<li>install</li>
-	<li>ports</li>
-	<li>x11</li>
-	<li>desktop</li>
-	<li>multimedia</li>
-	<li>mirrors</li>
-	<li>pgpkeys</li>
-      </ul>
-
-      <p>Merging translation results from the www tree on a separate
-	repository for the translation work into the main tree was also
-	finished.  Since outdated and/or non-translated documents also
-	remain in both doc/ja_JP.eucJP and www, further translation work is
-	still needed.  Some progress has been made in the Porter's Handbook
-	as well in this period.</p>
-    <hr /><h2><a name="Webcam-and-DVB-Compatibility-List" href="#Webcam-and-DVB-Compatibility-List" id="Webcam-and-DVB-Compatibility-List">Webcam and DVB Compatibility List</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/WebcamCompat" title="http://wiki.FreeBSD.org/WebcamCompat"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/WebcamCompat" title="">http://wiki.FreeBSD.org/WebcamCompat</a></td></tr></table><p>
-	Contact:
-	  Matthias
-	  Apitz
-	 &lt;<a href="mailto:guru@unixarea.de">guru@unixarea.de</a>&gt;
-	</p>
-      <p><strong>Webcam and DVB Compatibility List</strong></p>
-
-      <p>This is the FreeBSD Webcam, DVB, and Remote Control Compatibility
-	List.  The main goal of this page is to give an exact answer about
-	which application works with a given cam or DVB.  Combinations of
-	the hardware and software mentioned in this table are known to
-	work.</p>
-
-      <p>Please add more lines to the table or ask me to do so by just
-	sending a mail with your Cam/DVB information.  Please note: you
-	should only add information you have seen working and not you may
-	think of or imagine that they could work.  The contact information
-	(name and/or email addr) is optional.</p>
-    <h3>Open tasks:</h3><ol><li>Move this to a real database in where FreeBSD enduser could self
-	insert their gadgets, like the FreeBSD Laptop Compat List.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm-on-Marvell-Raid-on-Chip" href="#FreeBSD/arm-on-Marvell-Raid-on-Chip" id="FreeBSD/arm-on-Marvell-Raid-on-Chip">FreeBSD/arm on Marvell Raid-on-Chip</a></h2><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>Marvell 88RC8180 is an integrated RAID-on-Chip controller, based
-	on the Feroceon 88FR331 CPU core (ARMv5TE).  The 88RC9580 is a next
-	generation version, based on the Sheeva 88SV581 CPU core (ARMv6) of
-	this system-on-chip devices family.</p>
-
-      <p>Current FreeBSD suppport for 88RC8180 and 88RC9580 includes:</p>
-
-      <ul>
-	<li>Booting via U-Boot bootloader</li>
-	<li>L1, L2 cache</li>
-	<li>Serial console support (UART)</li>
-	<li>Interrupt controller</li>
-	<li>Integrated timers</li>
-	<li>PCI Express (root complex and endpoint modes)</li>
-	<li>Doorbells and messages</li>
-	<li>Ethernet controller</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Complete, clean up, merge with HEAD.</li></ol><hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-on-ec2/" title="http://www.daemonology.net/freebsd-on-ec2/">FreeBSD/EC2 status page</a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-on-ec2/" title="FreeBSD/EC2 status page">http://www.daemonology.net/freebsd-on-ec2/</a></td></tr></table><p>
-	Contact:
-	  Colin
-	  Percival
-	 &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD is now able to run on t1.micro and cc1.4xlarge instances in
-	the Amazon EC2 cloud. FreeBSD 8.2-RELEASE is stable subject to the
-	limitations of the instance type (e.g., running ZFS on a micro
-	instance with only 600 MB of RAM doesn't work very well), but FreeBSD
-	9.0 has significant stability issues.</p>
-
-      <p>A list of available FreeBSD AMIs (EC2 machine images) appears on
-	the FreeBSD/EC2 status page.</p>
-    <h3>Open tasks:</h3><ol><li>Bring FreeBSD to a wider range of EC2 instance types.</li><li>Completely rework the locking in head/sys/i386/xen/pmap.c to
-	eliminate races and make 9.0-CURRENT stable under
-	paravirtualization.</li><li>Track down several possibly-related problems with scheduling
-	and timekeeping.</li><li>Fix other issues shown on the FreeBSD/EC2 status page.</li></ol><hr /><h2><a name="FreeBSD/powerpc-on-Freescale-QorIQ" href="#FreeBSD/powerpc-on-Freescale-QorIQ" id="FreeBSD/powerpc-on-Freescale-QorIQ">FreeBSD/powerpc on Freescale QorIQ</a></h2><p>
-	Contact:
-	  Michal
-	  Dubiel
-	 &lt;<a href="mailto:md@semihalf.com">md@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>QorIQ is a brand of Power Architecture-based communications
-	microprocessors from Freescale.  It is an evolutionary step from the
-	PowerQUICC platform (MPC85xx) and is built around one or more Power
-	Architecture e500/e500mc cores.  This work is bringing up FreeBSD on
-	these system-on-chip devices along with device drivers for
-	integrated peripherials.</p>
-
-      <p>Current FreeBSD QorIQ support includes:</p>
-
-      <ul>
-	<li>QorIQ P2020 support</li>
-	<li>Booting via U-Boot bootloader</li>
-	<li>L1, L2 cache</li>
-	<li>Serial console (UART)</li>
-	<li>Interrupt controller</li>
-	<li>Ethernet (TSEC, SGMII mode)</li>
-	<li>I2C</li>
-	<li>EHCI controller (no Transaction Translation Unit)</li>
-	<li>Security Engine (SEC) 3.1</li>
-	<li>PCI Express controller (host mode)</li>
-	<li>Enhanced SDHC (no MMC support)</li>
-	<li>Dual-core (SMP) support</li>
-      </ul>
-    <hr /><h2><a name="MIPS/Octeon-Support-and-bootinfo" href="#MIPS/Octeon-Support-and-bootinfo" id="MIPS/Octeon-Support-and-bootinfo">MIPS/Octeon Support and bootinfo</a></h2><p>
-	Contact:
-	  Andrew
-	  Duane
-	 &lt;<a href="mailto:aduane@juniper.net">aduane@juniper.net</a>&gt;
-	</p>
-      <p>Working on improving support for Octeon processors and
-	integrating with other MIPS processor families.  Currently working
-	on support for the standard MIPS bootinfo structure as a boot API
-	(to supplement/replace the Caviums-specific structure).  Other
-	Octeon improvements including cleanups to CF and USB drivers to
-	come.</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-as-Home-Theater-PC" href="#FreeBSD-as-Home-Theater-PC" id="FreeBSD-as-Home-Theater-PC">FreeBSD as Home Theater PC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/HTPC" title="http://wiki.FreeBSD.org/HTPC"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HTPC" title="">http://wiki.FreeBSD.org/HTPC</a></td></tr></table><p>
-	Contact:
-	  Bernhard
-	  Froehlich
-	 &lt;<a href="mailto:decke@FreeBSD.org">decke@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Juergen
-	  Lock
-	 &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD could be a much better platform for a Home Theater PC than
-	it currently is.  We are focusing on improving support for media
-	center applications by extending the major ports (MythTV, VDR, XBMC)
-	and creating some documentation to guide interested people.</p>
-
-      <p>In the last months we continued to work on HTPC relevant ports,
-	improved lirc and multimedia/webcamd remote control support.  The
-	last missing major HTPC application VDR (Video Disk Recorder) has
-	finally been committed to the portstree as multimedia/vdr including
-	17 vdr plugin ports.</p>
-    <h3>Open tasks:</h3><ol><li>Improve remote control support in webcamd and with
-	lirc.</li><li>Port more Media Center applications (Enna, me-tv, ...)</li><li>Create a small guide on how to build a great FreeBSD Home
-	Theater PC.</li></ol><hr /><h2><a name="FreeBSD-Chromium" href="#FreeBSD-Chromium" id="FreeBSD-Chromium">FreeBSD Chromium</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://trillian.chruetertee.ch/chromium" title="http://trillian.chruetertee.ch/chromium"></a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/chromium" title="">http://trillian.chruetertee.ch/chromium</a></td></tr><tr><td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-chromium" title="http://lists.FreeBSD.org/mailman/listinfo/freebsd-chromium"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-chromium" title="">http://lists.FreeBSD.org/mailman/listinfo/freebsd-chromium</a></td></tr><tr><td><a href="http://www.chromium.org/Home" title="http://www.chromium.org/Home"></a></td><td>
-	    URL: <a href="http://www.chromium.org/Home" title="">http://www.chromium.org/Home</a></td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  Chromium Team
-	 &lt;<a href="mailto:chromium@FreeBSD.org">chromium@FreeBSD.org</a>&gt;
-	</p>
-      <p>Thanks to a great collaborative effort from the FreeBSD community, the
-	OpenBSD community, and the Chromium developers, Chromium has been
-	updated in the Ports tree.</p>
-
-      <p>In the spirit of release early and release often, updates to
-	Chromium happen frequently.  The contributors of the FreeBSD Chromium
-	team have demonstrated great agility in keeping pace with updates
-	in the development repository hosted at <a href="http://trillian.chruetertee.ch/chromium" shape="rect">
-	  http://trillian.chruetertee.ch/chromium</a>.</p>
-    <h3>Open tasks:</h3><ol><li>A task that lies ahead is working with the Chromium
-	developers at integrating the FreeBSD patches into the codebase.
-	Volunteers are welcome.</li></ol><hr /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Haskell" title="http://wiki.FreeBSD.org/Haskell">FreeBSD Haskell Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Haskell" title="FreeBSD Haskell Wiki Page">http://wiki.FreeBSD.org/Haskell</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/freebsd-haskell" title="https://github.com/freebsd-haskell/freebsd-haskell">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/freebsd-haskell" title="FreeBSD Haskell ports repository">https://github.com/freebsd-haskell/freebsd-haskell</a></td></tr><tr><td><a href="http://haskell.org/mailman/listinfo/freebsd-haskell/" title="http://haskell.org/mailman/listinfo/freebsd-haskell/">FreeBSD Haskell mailing list</a></td><td>
-	    URL: <a href="http://haskell.org/mailman/listinfo/freebsd-haskell/" title="FreeBSD Haskell mailing list">http://haskell.org/mailman/listinfo/freebsd-haskell/</a></td></tr></table><p>
-	Contact:
-	  G�bor J�nos
-	  P�LI
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Giuseppe
-	  Pilichi
-	 &lt;<a href="mailto:jacula@FreeBSD.org">jacula@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce that the FreeBSD Haskell team has updated
-	GHC to 7.0.3, and all other existing Haskell ports to the latest
-	stable versions, as well as added new ports.  The total number of
-	Haskell ports in the FreeBSD repository is now more than 200.  These
-	ports are still waiting to be committed.  At the moment, they are
-	available from <a href="https://github.com/freebsd-haskell/freebsd-haskell" shape="rect">FreeBSD
-	  Haskell ports repository</a>.  Any users who would like to get
-	early access to them, please refer to the <a href="http://www.haskell.org/pipermail/freebsd-haskell/2011-April/000278.html" shape="rect">
-	  FreeBSD Haskell ports Call For Testing</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Create a metaport for Haskell Platform.</li><li>Create a port for Happstack.</li><li>Create a port for gitit.</li></ol><hr /><h2><a name="KDE-FreeBSD" href="#KDE-FreeBSD" id="KDE-FreeBSD">KDE-FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE-FreeBSD</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE-FreeBSD">http://FreeBSD.kde.org</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde-freebsd@kde.org">kde-freebsd@kde.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team have continued to improve the experience of
-	KDE and Qt under FreeBSD.  The latest round of improvements
-	include:</p>
-
-      <ul>
-	<li>Improved shared resources (i.e. pixmaps for KDE)</li>
-	<li>Improved file monitoring (using kevent)</li>
-	<li>Improved KSysGuard support (new and refined sensors)</li>
-      </ul>
-
-      <p>The team have also made many releases and upstreamed many fixes
-	and patches.  The latest round of releases include:</p>
-
-      <ul>
-	<li>Qt: 4.7.2</li>
-	<li>KDE: 4.5.5; 4.6.1; 4.6.2</li>
-	<li>KOffice: 2.3.3</li>
-	<li>KDevelop: 4.2.0; 4.2.2 (KDevPlatform: 1.2.0; 1.2.2)</li>
-	<li>many smaller ports</li>
-      </ul>
-
-      <p>The team needs more testers and porters so please visit us at
-	kde-freebsd@kde.org</p>
-    <h3>Open tasks:</h3><ol><li>Continue improvements of KSysGuard.</li><li>General maintenance.</li><li>General testing.</li><li><b>Porting</b>.</li></ol><hr /><h2><a name="Linux-Emulation-Ports" href="#Linux-Emulation-Ports" id="Linux-Emulation-Ports">Linux Emulation Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-updated-linux-rpm-for-the-freebsd-linuxulator/" title="http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-updated-linux-rpm-for-the-freebsd-linuxulator/">HOWTO: cre­at­ing your own updated linux RPM for the FreeBSD linuxulator</a></td><td>
-	    URL: <a href="http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-updated-linux-rpm-for-the-freebsd-linuxulator/" title="HOWTO: cre­at­ing your own updated linux RPM for the FreeBSD linuxulator">http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-updated-linux-rpm-for-the-freebsd-linuxulator/</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Leidinger
-	 &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Emulation
-	  Mailinglist
-	 &lt;<a href="mailto:freebsd-emulation@FreeBSD.org">freebsd-emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>Old linux_base ports (all which are not used by default in some
-	release) where marked as deprecated with a short expiration
-	period.  The reason is that all those ports are long past their end
-	of life and do not receive security updates anymore.  Unfortunately
-	this is also true for the linux_base ports which are still used by
-	default in the releases, but no replacement is available ATM (see
-	open tasks).</p>
-
-      <p>The linux-f10-pango port was updated to a more recent version
-	whoch does not have a security problem by generating a linux-RPM in
-	a VM with "FreeBSD" as the vendor (see the links section for a
-	HOWTO).</p>
-    <h3>Open tasks:</h3><ol><li>Decide which RPM based linux distribution+version to track
-	next for the linux_base ports, create ports for it and test for
-	compatibility with our kernel code.</li></ol><hr /><h2><a name="Portmaster" href="#Portmaster" id="Portmaster">Portmaster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster-proposal.html" title="http://dougbarton.us/portmaster-proposal.html"></a></td><td>
-	    URL: <a href="http://dougbarton.us/portmaster-proposal.html" title="">http://dougbarton.us/portmaster-proposal.html</a></td></tr></table><p>
-	Contact:
-	  Doug
-	  Barton
-	 &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The latest version of portmaster contains numerous improvements
-	aimed at large-scale enterprise users.  Particularly, support for
-	the --index-only/--packages-only code has been significantly
-	improved.  Some of the highlights include:</p>
-
-      <ul>
-	<li>New --update-if-newer option which takes a list of ports
-	  and/or a glob pattern on the command line and only updates those
-	  that are out of date.  This feature is very useful for ensuring
-	  that the packages needed for updating a system are all available
-	  and up to date on the package building system.</li>
-
-	<li>The portmaster.rc file can now be stored in the same
-	  directory as the script itself, which aids in shared access to
-	  the script (for example over an NFS mount)</li>
-
-	<li>More features now work (or work better) with --index-only,
-	  including --check-depends</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>I have received some support for items E.2 and E.3 on the web
-	page listed above so I will be putting some effort into those areas
-	in the coming months.  I also have in mind to split out the "fetch"
-	code to be its own script, in part to support goal E.2, and to
-	allow for more efficient parallelization when downloading multiple
-	distfiles (especially for multiple ports that download the same
-	distfile).  This will also allow me to set a global limit for the
-	number of parallel fetches which should aid users on slow
-	links.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td>
-	    URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/"></a></td><td>
-	    URL: <a href="http://tinderbox.marcuscom.com/" title="">http://tinderbox.marcuscom.com/</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree slowly moves up closer to 23,000.  The PR count
-	still remains at about 1000.</p>
-
-      <p>In Q1 we added 2 new committers, and took in 4 commit bits for
-	safe keeping.</p>
-
-      <p>After a year of serving as the team secretary, Thomas Abthorpe's
-	membership was upgraded to full voting status.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports updates.
-	Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>erwin did a clang -exp run, and sent results to interested
-	  parties</li>
-
-	<li>kde@ requested an -exp run for KDE 4.6.1 and Qt 4.7.2</li>
-
-	<li>linimon -exp for update of default zope version to 3.2</li>
-
-	<li>miwi performed the following -exp runs, make fetch-original,
-	  xorg, cmake, pear, kde4 / py-qt / sip, and python2.7</li>
-
-	<li>mm requested an -exp run to test the last GPLv2 version of
-	  gcc 4.2.2</li>
-
-	<li>pav completed open-motif and mono -exp runs for respective
-	  submitters</li>
-
-	<li>ports/127214, -exp run to make copy/paste of portaudit user
-	  friendly</li>
-
-	<li>ports/144482, -exp run to fix package depends</li>
-
-	<li>ports/152102, -exp run to make dirrmtry more friendly</li>
-
-	<li>ports/152268, -exp run to update binutils</li>
-
-	<li>ports/153539, -exp run to allow checking STRIP when
-	  WITH_DEBUG is defined</li>
-
-	<li>ports/153547, -exp run to remove NO_SIZE</li>
-
-	<li>ports/153625, -exp run to pass CPPFLAGS to
-	  MAKE/CONFIGURE_ENV</li>
-
-	<li>ports/153634, -exp run to remove redundant PKGNAMEPREFIX for
-	  localised ports</li>
-
-	<li>ports/154121, -exp run to use --title for new libdialog</li>
-
-	<li>ports/154122, -exp run to update libtool to 2.4</li>
-
-	<li>ports/154186, -exp to allow using linux 2.4 emulation on FreeBSD
-	  8+</li>
-
-	<li>ports/154390, -exp run to make fetching output copy/paste
-	  friendly</li>
-
-	<li>ports/154653, -exp run to remove superfluous slash</li>
-
-	<li>ports/154799, -exp run to update glib + gtk</li>
-
-	<li>ports/154994, -exp run for MASTER_SITE_PERL_CPAN
-	  enhancements</li>
-
-	<li>ports/155502, -exp run to remove sanity check for
-	  X_WINDOW_SYSTEM</li>
-
-	<li>ports/155504, -exp run to remove USE_XPM from b.p.m.</li>
-
-	<li>ports/155505, -exp run to update GNU m4</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Looking for help fixing <a href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent" shape="rect">ports
-	  broken on CURRENT</a>.</li><li>Looking for help with  <a href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures" shape="rect">
-	  Tier-2 architectures</a>.</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing and closing.</li></ol><hr /><h2><a name="www/apache22-Default" href="#www/apache22-Default" id="www/apache22-Default">www/apache22 Default</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/maintainers.html#apache" title="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/maintainers.html#apache">prs</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/maintainers.html#apache" title="prs">http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/maintainers.html#apache</a></td></tr><tr><td><a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/147009" title="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/147009">-exp request</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/147009" title="-exp request">http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/147009</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/Apache" title="http://wiki.FreeBSD.org/Apache"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Apache" title="">http://wiki.FreeBSD.org/Apache</a></td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-apache/2011-March/002174.html" title="http://lists.FreeBSD.org/pipermail/freebsd-apache/2011-March/002174.html"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-apache/2011-March/002174.html" title="">http://lists.FreeBSD.org/pipermail/freebsd-apache/2011-March/002174.html</a></td></tr></table><p>
-	Contact:
-	  Philip
-	  Gollucci
-	 &lt;<a href="mailto:pgollucci@FreeBSD.org">pgollucci@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Olli
-	  Hauer
-	 &lt;<a href="mailto:ohauer@FreeBSD.org">ohauer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Apache
-	  Apache
-	 &lt;<a href="mailto:apache@FreeBSD.org">apache@FreeBSD.org</a>&gt;
-	</p>
-      <p>95% done, pending final -exp run, and pulling the switch.  HEADS-UP
-	announcement already sent to relevant lists.  This will be for
-	8.3/9.0.</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan" href="#BSDCan" id="BSDCan">BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/2011/" title="http://www.bsdcan.org/2011/">BSDCan 2011</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2011/" title="BSDCan 2011">http://www.bsdcan.org/2011/</a></td></tr></table><p>
-	Contact:
-	  Dan
-	  Langille
-	 &lt;<a href="mailto:dvl@FreeBSD.org">dvl@FreeBSD.org</a>&gt;
-	</p>
-      <p>Our <a href="http://www.bsdcan.org/2011/schedule/events.en.html" shape="rect">list
-	  of talks</a> has been settled, and the <a href="http://www.bsdcan.org/2011/schedule/index.en.html" shape="rect">
-	  schedule</a> is pretty much finalized.  There is still time
-	  to get into the <a href="http://www.bsdcan.org/2011/schedule/events/259.en.html" shape="rect">
-	  Works In Progress</a> session.</p>
-
-      <p>Best to book your <a href="http://www.bsdcan.org/2011/campus.php" shape="rect">on-campus
-	  accommodation</a>  now.  Or stay at one of the <a href="http://www.bsdcan.org/2011/travel.php" shape="rect">nearby
-	  hotels</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Show up.  Enjoy.  Profit.</li></ol><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Extfs-Status-Report" href="#Extfs-Status-Report" id="Extfs-Status-Report">Extfs Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83">ext2fs</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83" title="ext2fs">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/extfs/src/sys/fs/&amp;c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83">ext4fs</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83" title="ext4fs">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2010/ext4fs/src/sys/fs/&amp;c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83</a></td></tr></table><p>
-	Contact:
-	  Zheng
-	  Liu
-	 &lt;<a href="mailto:lz@FreeBSD.org">lz@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have implemented a reallocblks in ext2fs, like in ffs,
-	and submitted a patch file to mailing list.  Next I will try to
-	implement htree directory index in ext2fs.</p>
-    <hr /><h2><a name="Google-Summer-of-Code-2011" href="#Google-Summer-of-Code-2011" id="Google-Summer-of-Code-2011">Google Summer of Code 2011</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd" title="http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd"></a></td><td>
-	    URL: <a href="http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd" title="">http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SummerOfCode2011" title="http://wiki.freebsd.org/SummerOfCode2011">GSoC Wiki Homepage</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/SummerOfCode2011" title="GSoC Wiki Homepage">http://wiki.freebsd.org/SummerOfCode2011</a></td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD is proud to be participating in our seventh year of Google
-	Summer of Code.  On Monday, April 25th we accepted 17
-	proposals from an overall excellent field.  A full list of <a href="http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd" shape="rect">accepted
-	  proposals</a> can be found on the <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2011" shape="rect">GSoC
-	  website</a>.  We look forward to working with these students
-	over the summer.</p>
-
-      <p>As we did last year we plan to ask students to submit weekly
-	status reports to the
-	<a href="http://lists.FreeBSD.org/mailman/listinfo/soc-status" shape="rect">
-	  soc-status</a> mailing list.  Those wishing to keep up with
-	the work in progress and offer review may wish to
-	subscribe.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2011-04-2011-06.html b/website/content/en/status/report-2011-04-2011-06.html
deleted file mode 100644
index 1228445902..0000000000
--- a/website/content/en/status/report-2011-04-2011-06.html
+++ /dev/null
@@ -1,1419 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between April and June
-      2011.  It is the second of the four reports planned for 2011.  Since
-      this quarter, the work is being focused on the next major version of
-      FreeBSD, 9.0, which is to be released in September.</p><p>Thanks to all the reporters for the excellent work!  This report
-      contains 36 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between July and September 2011 is October 15th, 2011.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#Fix-clang-warnings">Fix clang warnings</a></li><li><a href="#libarchive,-bsdtar,-bsdcpio">libarchive, bsdtar, bsdcpio</a></li><li><a href="#ZFS-pool-version-28">ZFS pool version 28</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#ArabBSD">ArabBSD</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></li><li><a href="#FreeBSD-IPv6-only-Support">FreeBSD IPv6-only Support</a></li><li><a href="#IPv6-RA-Handling-Improvements">IPv6 RA Handling Improvements</a></li><li><a href="#netmap">netmap</a></li><li><a href="#New-ipfw-features">New ipfw features</a></li><li><a href="#TCP-User-Timeout-Option-(UTO)">TCP User Timeout Option (UTO)</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Intel-GPU-Driver">Intel GPU Driver</a></li><li><a href="#OpenAFS-port">OpenAFS port</a></li><li><a href="#Overhaul-of-the-mii(4)-subsystem">Overhaul of the mii(4)-subsystem</a></li><li><a href="#Status-Report-for-NFS">Status Report for NFS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-June-6th,-2011-Doc-Sprint">FreeBSD June 6th, 2011 Doc Sprint</a></li><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-the-Sony-Playstation-3">FreeBSD on the Sony Playstation 3</a></li><li><a href="#FreeBSD/arm-on-Marvell-Armada-XP">FreeBSD/arm on Marvell Armada XP</a></li><li><a href="#FreeBSD/powerpc-on-AppliedMicro-APM86290">FreeBSD/powerpc on AppliedMicro APM86290</a></li><li><a href="#FreeBSD/powerpc64-on-IBM-pSeries-machines">FreeBSD/powerpc64 on IBM pSeries machines</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium">Chromium</a></li><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#KDE-FreeBSD">KDE-FreeBSD</a></li><li><a href="#libvirt-networking-port">libvirt networking port</a></li><li><a href="#Portbuilder">Portbuilder</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#bsd_day(2011)">bsd_day(2011)</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Capsicum-adaptation-and-core-libraries">Capsicum adaptation and core libraries</a></li><li><a href="#Disk-device-error-counters">Disk device error counters</a></li><li><a href="#Google-Summer-of-Code">Google Summer of Code</a></li><li><a href="#nvi-iconv">nvi-iconv</a></li><li><a href="#Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/PortsAndClang" title="http://wiki.FreeBSD.org/PortsAndClang"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PortsAndClang" title="">http://wiki.FreeBSD.org/PortsAndClang</a></td></tr></table><p>
-	Contact:
-	  Dimitry
-	  Andric
-	 &lt;<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Pawel
-	  Worach
-	 &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	</p>
-      <p>We imported newer snapshot of clang/llvm.  This features quite
-	a lot of goodies.  Most notably there's a new register
-	allocator that brings much better runtime performance.  If you
-	did a performance evaluation of clang/llvm in the past now
-	it's the time to rerun it with the new register allocator!</p>
-
-      <p>There was some progress on Mips and PowerPC in addition to
-	the usual influx of improvements on ARM, i386 and amd64.  We've
-	managed to get clang compiled arm kernel booting.  ARM world is
-	blocked by FreeBSD using old ARM ABI.</p>
-
-      <p>We got a buildbot that periodically builds clang/llvm on
-	FreeBSD and FreeBSD (amd64 and i386) using clang/llvm, including
-	booting the resulting image.</p>
-
-      <p>We ran a few ports exp runs and got many ports bugs fixed so
-	right now we're able to build more than 15000 ports with
-	clang.  We expect this number to grow rapidly as the problems
-	are mostly trivial.</p>
-    <h3>Open tasks:</h3><ol><li>Fix your ports.</li><li>Performance evaluate the new clang/llvm.</li><li>Fix clang warnings in src.</li><li>Implement proper support for cross compiling.</li></ol><hr /><h2><a name="Fix-clang-warnings" href="#Fix-clang-warnings" id="Fix-clang-warnings">Fix clang warnings</a></h2><p>
-	Contact:
-	  Ben
-	  Laurie
-	 &lt;<a href="mailto:benl@FreeBSD.org">benl@FreeBSD.org</a>&gt;
-	</p>
-      <p>In order to assist with the process of moving away from gcc,
-	while I learn the ropes of being a contributor, I am
-	systematically fixing clang warnings, so we can turn on -Werror
-	again.</p>
-
-      <p>Down from &gt; 42,000 warnings at the end of May to &lt; 9,000
-	warnings now.</p>
-    <h3>Open tasks:</h3><ol><li>Always happy if someone else finds and fixes a
-	warning!</li></ol><hr /><h2><a name="libarchive,-bsdtar,-bsdcpio" href="#libarchive,-bsdtar,-bsdcpio" id="libarchive,-bsdtar,-bsdcpio">libarchive, bsdtar, bsdcpio</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/libarchive" title="http://code.google.com/p/libarchive"></a></td><td>
-	    URL: <a href="http://code.google.com/p/libarchive" title="">http://code.google.com/p/libarchive</a></td></tr></table><p>
-	Contact:
-	  Tim
-	  Kientzle
-	 &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Michihiro
-	  Nakajima
-	 &lt;<a href="mailto:ggcueroad@gmail.com">ggcueroad@gmail.com</a>&gt;
-	</p>
-      <p>Libarchive, bsdtar and bsdcpio in 9-CURRENT have been updated to
-	version 2.8.4 (thanks to mm@FreeBSD.org) and bsdtar now supports
-	extracting XAR and RPM archive formats.</p>
-
-      <p>There is ongoing development in trunk with many improvements
-	including support for new formats both on the read (e.g. cab, lha,
-	rar) and write parts (e.g. iso9660, xar).</p>
-    <hr /><h2><a name="ZFS-pool-version-28" href="#ZFS-pool-version-28" id="ZFS-pool-version-28">ZFS pool version 28</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	</p>
-      <p>ZFS pool version 28 has been merged into 8-STABLE as of
-	June 6, 2011.  In addition, several bugfixes and improvements
-	from the Illumos project have been imported.</p>
-    <h3>Open tasks:</h3><ol><li>Investigation of ZFS problem reports.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="ArabBSD" href="#ArabBSD" id="ArabBSD">ArabBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://sites.google.com/site/arabbsd/" title="https://sites.google.com/site/arabbsd/">Official Website</a></td><td>
-	    URL: <a href="https://sites.google.com/site/arabbsd/" title="Official Website">https://sites.google.com/site/arabbsd/</a></td></tr></table><p>
-	Contact:
-	  Mohammed
-	  Farrag
-	 &lt;<a href="mailto:mfarrag@FreeBSD.org">mfarrag@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD Awareness, Handbook Translation and FreeBSD Kernel
-	Development Summer Course.</p>
-    <h3>Open tasks:</h3><ol><li>FreeBSD Kernel Development Summer Course.</li></ol><hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="www.FreeBSDFoundation.org" title="www.FreeBSDFoundation.org"></a></td><td>
-	    URL: <a href="www.FreeBSDFoundation.org" title="">www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We were a proud sponsor of BSDCan.  We also sponsored 6
-	developers to attend the conference.  And, we brought in over
-	$1,000 in donations! The Foundation was also represented at
-	FlourishConf in Chicago, IL and SouthEast LinuxFest in
-	Spartanburg, SC.</p>
-
-      <p>We acquired a non-exclusive copyright license to the <a href="http://www.FreeBSDFoundation.org/press/Pathscale-PRrelease.shtml" shape="rect">
-	libcxxrt C++ runtime</a> software from PathScale.</p>
-
-      <p>Sponsored a project to create an <a href="http://www.FreeBSDFoundation.org/press/IPv6%20Day-PRrelease.shtml" shape="rect">
-	IPv6-only version</a> of FreeBSD and PC-BSD.</p>
-
-      <p>We're pleased announce the addition of Ed Maste to our Board
-	of Directors.  Ed has been involved with FreeBSD since 2003.  And,
-	has been a committer since 2005.  Ed leads the OS team at Sandvine
-	and is responsible for a number of developers who bring
-	enhancements from FreeBSD into Sandvine's OS and contribute their
-	own changes back to FreeBSD.</p>
-
-      <p>We continued our work on infrastructure projects to beef up
-	hardware for package-building, network-testing, etc.  This
-	includes purchasing equipment as well as managing equipment
-	donations.  In fact we just placed an order for a 80-core server
-	for SMP performance work.</p>
-
-      <p>Stop by and visit with us at Ohio LinuxFest, Columbus, OH, on
-	September 10.</p>
-
-      <p>The work above, as well as many other tasks we do for the
-	project, couldn't be done without donations.  Please help us by
-	making a donation or asking your company to make a donation.  We
-	would be happy to send marketing literature to you or your
-	company.  Find out how to make a donation at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">
-	http://www.FreeBSDFoundation.org/donate/</a>.</p>
-
-      <p>Find out more up-to-date Foundation news by reading our
-	<a href="http://FreeBSDFoundation.blogspot.com/" shape="rect">blog</a>
-	and <a href="https://www.facebook.com/FreeBSDFoundation" shape="rect">Facebook
-	page</a>.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" id="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/" title="http://caia.swin.edu.au/urp/diffuse/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/" title="">http://caia.swin.edu.au/urp/diffuse/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="http://caia.swin.edu.au/urp/diffuse/downloads.html"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="">http://caia.swin.edu.au/urp/diffuse/downloads.html</a></td></tr></table><p>
-	Contact:
-	  Sebastian
-	  Zander
-	 &lt;<a href="mailto:szander@swin.edu.au">szander@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	</p>
-      <p>DIFFUSE is a system enabling FreeBSD's IPFW firewall subsystem
-	to classify IP traffic based on statistical traffic properties.</p>
-
-      <p>With DIFFUSE, IPFW computes statistics (such as packet lengths
-	or inter-packet time intervals) for observed flows, and uses ML
-	(machine learning) to classify flows into classes.  In addition to
-	traditional packet inspection rules, IPFW rules may now also be
-	expressed in terms of traffic statistics or classes identified by
-	ML classification.  This can be helpful when direct packet
-	inspection is problematic (perhaps for administrative reasons, or
-	because port numbers do not reliably identify applications).</p>
-
-      <p>DIFFUSE also enables one instance of IPFW to send flow
-	information and classes to other IPFW instances, which then can act
-	on such traffic (e.g. prioritise, accept, deny, etc.) according to
-	its class.  This allows for distributed architectures, where
-	classification at one location in your network is used to control
-	fire-walling or rate-shaping actions at other locations.</p>
-
-      <p>The DIFFUSE prototype is a set of patches for FreeBSD-CURRENT
-	that can be downloaded from the project's web site.  The web site
-	also contains a more comprehensive introduction, as well as links
-	to related work and documentation.</p>
-
-      <p>In July 2011, we released DIFFUSE v0.4.  This release contains a
-	number of bug fixes and new features.  Most notably we improved the
-	functionality of the tools used for training classification models,
-	and performing offline analysis.</p>
-
-      <p>DIFFUSE v0.4 is the last release, as the DIFFUSE project has
-	concluded.  However, we may release bug fixes in the future if
-	necessary.</p>
-    <hr /><h2><a name="FreeBSD-IPv6-only-Support" href="#FreeBSD-IPv6-only-Support" id="FreeBSD-IPv6-only-Support">FreeBSD IPv6-only Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern" title="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern">FreeBSD Foundation project announcement</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern" title="FreeBSD Foundation project announcement">http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern</a></td></tr><tr><td><a href="http://www.ixsystems.com/ix/media/freebsd-foundation-and-ixsystems-announce-ipv6-only-testing-versions-of-freebsd-and-pc-bsd" title="http://www.ixsystems.com/ix/media/freebsd-foundation-and-ixsystems-announce-ipv6-only-testing-versions-of-freebsd-and-pc-bsd">FreeBSD Foundation and iXsystems press release</a></td><td>
-	    URL: <a href="http://www.ixsystems.com/ix/media/freebsd-foundation-and-ixsystems-announce-ipv6-only-testing-versions-of-freebsd-and-pc-bsd" title="FreeBSD Foundation and iXsystems press release">http://www.ixsystems.com/ix/media/freebsd-foundation-and-ixsystems-announce-ipv6-only-testing-versions-of-freebsd-and-pc-bsd</a></td></tr><tr><td><a href="http://www.FreeBSD.org/ipv6/ipv6only.html" title="http://www.FreeBSD.org/ipv6/ipv6only.html">FreeBSD IPv6-only Support</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ipv6/ipv6only.html" title="FreeBSD IPv6-only Support">http://www.FreeBSD.org/ipv6/ipv6only.html</a></td></tr><tr><td><a href="http://www.pcbsd.org/IPv6" title="http://www.pcbsd.org/IPv6">PC-BSD IPv6</a></td><td>
-	    URL: <a href="http://www.pcbsd.org/IPv6" title="PC-BSD IPv6">http://www.pcbsd.org/IPv6</a></td></tr></table><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>As a follow-up work to the no-IP kernel, a FreeBSD IPv6-only
-	prototype kernel was build beginning of 2010.  This work was now
-	carried on and merged to mainstream FreeBSD and will be part of the
-	upcoming 9.0-RELEASE allowing for custom no-IPv4 kernels to be
-	built.  In addition IPv6 installation and configuration support for
-	FreeBSD and PC-BSD were improved.</p>
-
-      <p>An IPv6-only kernel and continued efforts to build world without
-	IPv4, like FreeBSD had supported compiling out IPv6 for a long
-	time, will allow easier IPv6 validation work to happen.  This will
-	not only help FreeBSD or FreeBSD-derived commercial product
-	builders but we are also hoping to motivate other Open Source
-	projects to test their software for IPv6-readiness on FreeBSD or
-	PC-BSD.</p>
-
-      <p>We have provided and will continue to provide IPv6-only
-	snapshots for FreeBSD.  In IPv6-only PC-BSD snapshots have been
-	released to provide a great Open Source desktop environment to test
-	GUI applications for IPv6-readiness as well.</p>
-
-      <p>I would like to thank the FreeBSD Foundation and iXsystems for their
-	support of the project, as well as George Neville-Neil for
-	providing review and Kris Moore for helping on the PC-BSD
-	integration and building and providing the PC-BSD snapshots.</p>
-    <hr /><h2><a name="IPv6-RA-Handling-Improvements" href="#IPv6-RA-Handling-Improvements" id="IPv6-RA-Handling-Improvements">IPv6 RA Handling Improvements</a></h2><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	</p>
-      <p>ICMPv6 Router Advertisement (RA) message is a part of IPv6
-	Neighbor Discovery Protocol in RFC 4861 and takes an important role
-	in IPv6 basic functionality.  FreeBSD supports it in the kernel, and
-	the rtadvd(8) and rtsold(8) programs derived from KAME project
-	handle it in userland.</p>
-
-      <p>This small project aims to improve the current RA handling by
-	removing limitations and adding new functionality found in the
-	latest RFCs.  Changes committed are as follows:</p>
-
-      <ul>
-	<li>FreeBSD now supports RA receiving even if
-	  net.inet6.ip6.forwarding=1 and enabling/disabling the receiving
-	  in a per-interface basis.  The traditional "host" and "router"
-	  node model in IPv6 RFCs is translated into a concept of
-	  "RA-receiving interfaces" and "RA-sending interfaces" in
-	  FreeBSD�9.0 or later, not depending only on system-wide IP
-	  forwarding capability.  This is useful for a system with
-	  multiple IPv6-capable interfaces (such as a customer-edge
-	  router) which require SLAAC (Stateless Address
-	  Autoconfiguration) feature described in RFC 4862.</li>
-
-	<li>The rtadvd(8) and rtsold(8) programs now support IPv6 Router
-	  Advertisement Options for DNS Configuration in RFC 6106.  This
-	  enables updating /etc/resolv.conf by using RAs.</li>
-
-	<li>The rtadvd(8) daemon now supports dynamically-added/removed
-	  interfaces.  Although it was needed that all of RA-sending
-	  interfaces exist before the daemon was invoked, the new version
-	  no longer requires it.  When a new interface arrived, it will be
-	  configured on the fly.</li>
-
-	<li>The rtadvctl(8) utility has been added.  This displays
-	  RA-sending status on each interface and provides a way to
-	  control the daemon.  This utility makes system administration
-	  much easier.</li>
-      </ul>
-
-      <p>All of the changes described above have already been committed
-	to 9-CURRENT and a part of them will be merged to 8-STABLE.</p>
-    <hr /><h2><a name="netmap" href="#netmap" id="netmap">netmap</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/netmap/" title="http://info.iet.unipi.it/~luigi/netmap/"></a></td><td>
-	    URL: <a href="http://info.iet.unipi.it/~luigi/netmap/" title="">http://info.iet.unipi.it/~luigi/netmap/</a></td></tr></table><p>
-	Contact:
-	  Luigi
-	  Rizzo
-	 &lt;<a href="mailto:rizzo@iet.unipi.it">rizzo@iet.unipi.it</a>&gt;
-	</p>
-      <p>netmap is a novel framework to achieve wire-speed packet
-	processing in FreeBSD, while retaining the safety and richness of
-	features provided by the user space environment, and using only
-	standard system calls.  With netmap, it takes as little as 70 clock
-	cycles to move one packet between the user program and the wire.  As
-	an example, a single core running at 900MHz can generate the
-	14.8Mpps that saturate a 10GigE interface.  This is a 5-10x
-	improvement over the use of a standard device driver.  netmap is
-	implemented with a relatively small kernel device driver (less than
-	2000 lines of code), plus individual network card patches (300-500
-	lines each; currently supported are Intel 1 and 10 Gbit cards, and
-	RealTek 1 Gbit cards).  No special user libraries are needed,
-	although we have a small libpcap-over-netmap which enables the use
-	of existing applications on top of the new API with no source or
-	binary modifications.  The netmap home page contains a more detailed
-	description of the project, source code, papers and slides.</p>
-    <hr /><h2><a name="New-ipfw-features" href="#New-ipfw-features" id="New-ipfw-features">New ipfw features</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base?view=revision&amp;revision=223666" title="http://svnweb.FreeBSD.org/base?view=revision&amp;revision=223666"></a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base?view=revision&amp;revision=223666" title="">http://svnweb.FreeBSD.org/base?view=revision&amp;revision=223666</a></td></tr></table><p>
-	Contact:
-	  Vadim
-	  Goncharov
-	 &lt;<a href="mailto:vadim_nuclight@mail.ru">vadim_nuclight@mail.ru</a>&gt;
-	</p>
-      <p>The <a href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=4&amp;manpath=FreeBSD+9.0-RELEASE" shape="rect">
-	ipfw(4)</a> packet filter now supports <tt>call</tt>
-	and <tt>return</tt> rule actions.  When a packet matches a rule
-	with the <tt>call</tt> action, the rule number is saved in the
-	internal stack and rules processing continues from the first
-	rule with specified number (similar to <tt>skipto</tt> action,
-	but backward jumps are allowed).  If later a rule with
-	<tt>return</tt> action is encountered, the processing returns to
-	the first rule with number greater than the number saved in the
-	internal stack.  This makes it possible to organize "subroutines"
-	with rules, e.g. to call one subroutine several times from
-	different places in the ruleset.  For more details, see <a href="http://www.FreeBSD.org/cgi/man.cgi?query=ipfw&amp;sektion=8&amp;manpath=FreeBSD+9.0-RELEASE&amp;format=html" shape="rect">
-	ipfw(8)</a>.</p>
-    <hr /><h2><a name="TCP-User-Timeout-Option-(UTO)" href="#TCP-User-Timeout-Option-(UTO)" id="TCP-User-Timeout-Option-(UTO)">TCP User Timeout Option (UTO)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/CatalinNicutar/TCPUTO" title="http://wiki.FreeBSD.org/CatalinNicutar/TCPUTO">Project Wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/CatalinNicutar/TCPUTO" title="Project Wiki">http://wiki.FreeBSD.org/CatalinNicutar/TCPUTO</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2011/&amp;dw=u&amp;c=kml@//depot/projects/soc2011/cnicutar_tcputo_8/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2011/&amp;dw=u&amp;c=kml@//depot/projects/soc2011/cnicutar_tcputo_8/?ac=83">Repository</a></td><td>
-	    URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2011/&amp;dw=u&amp;c=kml@//depot/projects/soc2011/cnicutar_tcputo_8/?ac=83" title="Repository">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/soc2011/&amp;dw=u&amp;c=kml@//depot/projects/soc2011/cnicutar_tcputo_8/?ac=83</a></td></tr></table><p>
-	Contact:
-	  Catalin
-	  Nicutar
-	 &lt;<a href="mailto:cnicutar@FreeBSD.org">cnicutar@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Bjoern
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of the User Timeout option is to allow an application
-	to tweak the time TCP waits for acknowledgements.  Using UTO, an
-	application can choose the exact time it is willing to wait for
-	data to be acknowledged.  Also, an application can suggest to its
-	peer the time it should wait before dropping the connection (the
-	peer may or may not allow this).</p>
-
-      <p>As an example, a SSH client can request a large timeout (4
-	hours) for a connection.  After some time the client is
-	disconnected, reconnecting 2 hours later (with the same IP).  Due
-	to UTO, the connection should still be alive and any lost data
-	should be retransmitted.</p>
-
-      <p>Current testing is done on TCP over IPv4.  Timeouts can be
-	limited by global sysctls and an application can choose how to
-	send or accept timeout values via socket options.  In addition to
-	regression tests, support has been added to telnet, ssh and
-	netcat.</p>
-    <h3>Open tasks:</h3><ol><li>Regression tests for TCP over IPv6.</li><li>Add support to more userland applications.</li><li>Implement strategies and regression tests to handle and
-	simulate DoS scenarios.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Intel-GPU-Driver" href="#Intel-GPU-Driver" id="Intel-GPU-Driver">Intel GPU Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Intel_GPU" title="http://wiki.FreeBSD.org/Intel_GPU"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Intel_GPU" title="">http://wiki.FreeBSD.org/Intel_GPU</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation sponsored project to port the Linux
-	kernel-mode driver for Intel GPU progressed to the point where some
-	machines can use Xorg with ddx driver from the git head and latest
-	Mesa.  On my test machine I was able to run uhexen2 and
-	ioquake3.</p>
-
-      <p>Nonetheless, the driver is still in the early stages of
-	debugging.  Read the wiki page for more details, guidelines on
-	installation and initial bug analysis.</p>
-
-      <p>Main efforts right now are directed on getting the required VM
-	changes into the base system, ideally before 9.0 is released.</p>
-    <hr /><h2><a name="OpenAFS-port" href="#OpenAFS-port" id="OpenAFS-port">OpenAFS port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openafs.org" title="http://openafs.org">OpenAFS home page</a></td><td>
-	    URL: <a href="http://openafs.org" title="OpenAFS home page">http://openafs.org</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/afs" title="http://wiki.FreeBSD.org/afs">FreeBSD Wiki on AFS</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/afs" title="FreeBSD Wiki on AFS">http://wiki.FreeBSD.org/afs</a></td></tr></table><p>
-	Contact:
-	  Benjamin
-	  Kaduk
-	 &lt;<a href="mailto:kaduk@mit.edu">kaduk@mit.edu</a>&gt;
-	<br />
-	Contact:
-	  Derrick
-	  Brashear
-	 &lt;<a href="mailto:shadow@gmail.com">shadow@gmail.com</a>&gt;
-	</p>
-      <p>AFS is a distributed network filesystem that originated from the
-	Andrew Project at Carnegie-Mellon University.  Since our last
-	report, upstream OpenAFS has updated to a 1.6.0pre6 release
-	candidate, which is available in the FreeBSD Ports Collection.  We
-	still expect the upcoming 1.6.0 release to be usable for regular
-	client workloads (though not heavy load).  We have also made
-	progress on integration with the bsd.kmod.mk kernel-module-building
-	infrastructure, with a working prototype implementation.  Further
-	cleanup and testing is needed before it is ready to be
-	committed.</p>
-
-      <p>There are several known outstanding issues that are being worked
-	on, but detailed bug reports are welcome at
-	port-freebsd@openafs.org.</p>
-    <h3>Open tasks:</h3><ol><li>Update VFS locking to allow the use of disk-based client
-	caches as well as memory-based caches.</li><li>Track down races and deadlocks that may appear under
-	load.</li><li>Integrate with the bsd.kmod.mk kernel-module build
-	infrastructure.</li><li>Eliminate a moderate memory leak from the kernel
-	module.</li><li>PAG (Process Authentication Group) support is not
-	functional.</li></ol><hr /><h2><a name="Overhaul-of-the-mii(4)-subsystem" href="#Overhaul-of-the-mii(4)-subsystem" id="Overhaul-of-the-mii(4)-subsystem">Overhaul of the mii(4)-subsystem</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>The mii(4)-subsystem has been overhauled and fixes and
-	enhancements from NetBSD/OpenBSD since mii(4) originally has been
-	ported over have been merged.  As a result a lot of code duplication
-	and hacks have been removed from the PHY drivers and we are now
-	able again to share the miidevs file with NetBSD.  Due to KPI
-	breakages the majority of this work will not be merged back into
-	8-STABLE and earlier.</p>
-
-      <p>Additionally shorthand aliases for common media+option combinations
-	as announced by mii(4) have been added to the ifmedia code so that
-	now one can actually supply the media strings found in the dmesg
-	output to ifconfig(8).  Support for this will be merged back to
-	8-STABLE prior to 8.3-RELEASE.</p>
-    <hr /><h2><a name="Status-Report-for-NFS" href="#Status-Report-for-NFS" id="Status-Report-for-NFS">Status Report for NFS</a></h2><p>
-	Contact:
-	  Rick
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new NFS client and server are no longer considered
-	experimental and will most likely be the default for FreeBSD�9.0.
-	Included is support for NFSv4.0 as well as NFSv3 and NFSv2.  The
-	NFSv4.0 support was tested at a recent NFSv4 Interoperability
-	Bakeathon held at CITI of the University of Michigan.  Also tested
-	at the Bakeathon was a basic client implementation of NFSv4.1 which
-	will soon be available as a test patch against the FreeBSD�9.0
-	kernel sources.  If you are interested in testing NFSv4.1, stay
-	tuned to the freebsd-fs@FreeBSD.org mailing list.
-	zkirsch@FreeBSD.org and friends will be taking on a majority of the
-	NFSv4 server work while I concentrate on the client, with hopes
-	that the NFSv4.1 support will mature over the next year or so.</p>
-
-      <p>I will also be making a patch for an experimental aggressive
-	client side on-disk caching mechanism for NFSv4 I call Packrats
-	available.  An announcement about this will be made on
-	freebsd-fs@FreeBSD.org as well.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="FreeBSD-June-6th,-2011-Doc-Sprint" href="#FreeBSD-June-6th,-2011-Doc-Sprint" id="FreeBSD-June-6th,-2011-Doc-Sprint">FreeBSD June 6th, 2011 Doc Sprint</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/DocSprints" title="http://wiki.FreeBSD.org/DocSprints">The DocSprints page in the FreeBSD wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/DocSprints" title="The DocSprints page in the FreeBSD wiki">http://wiki.FreeBSD.org/DocSprints</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~bcr/doc/sprints/20110606-final.html" title="http://people.FreeBSD.org/~bcr/doc/sprints/20110606-final.html">Results of the June 6 Doc Sprint</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bcr/doc/sprints/20110606-final.html" title="Results of the June 6 Doc Sprint">http://people.FreeBSD.org/~bcr/doc/sprints/20110606-final.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/annotated_prs.docsprint.html" title="http://people.FreeBSD.org/~linimon/annotated_prs.docsprint.html">Closed PRs during the doc sprint</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~linimon/annotated_prs.docsprint.html" title="Closed PRs during the doc sprint">http://people.FreeBSD.org/~linimon/annotated_prs.docsprint.html</a></td></tr><tr><td><a href="http://openhelpconference.com/" title="http://openhelpconference.com/">Website of the Open Help conference</a></td><td>
-	    URL: <a href="http://openhelpconference.com/" title="Website of the Open Help conference">http://openhelpconference.com/</a></td></tr></table><p>
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Dru
-	  Lavigne
-	 &lt;<a href="mailto:dru@FreeBSD.org">dru@FreeBSD.org</a>&gt;
-	</p>
-      <p>On June 6, the FreeBSD documentation project held a doc sprint
-	where a number of documentation issues were discussed.  The sprint
-	took place primarily in IRC channel #bsddocs on EFNet.  Notes were
-	taken in an Etherpad document where all participants could
-	concurrently edit them in an easy to use interface.  Parallel to the
-	discussion, a number of doc problem reports have been closed.  There
-	are still some doc PRs that have been identified that could also be
-	closed, because their original issue was already committed but the
-	PR is still open.  This needs to be investigated on a case by case
-	basis.</p>
-
-      <p>Dru Lavigne brought in her experiences from the Open Help
-	conference that she was attending during the sprint.  It would be
-	good to have some FreeBSD documentation people at a future Open
-	Help conference to exchange ideas with other open source
-	documentation projects and how they go about doing their work.</p>
-
-      <p>The primary discussion focused on the issues that have been
-	talked about at the documentation working group at BSDCan's
-	DevSummit in May.  Subjects like converting the documentation
-	repository from CVS to SVN, the move from DocBook SGML to XML-based
-	documentation as well as other formats like RST (re-restructured
-	text), and publication efforts of the handbook in electronic and
-	dead-tree form were thoroughly debated.</p>
-
-      <p>Overall participation was good, but we would like to have more
-	documentation folks to participate in future sprints.  The next
-	sprint is planned before EuroBSDCon 2011 and will be announced in
-	time so that interested people can set aside some time for it.  We
-	also plan to include different time zones so that we can have more
-	input from various areas.  We hope to establish these kind of
-	sprints on a regular basis to deal with documentation issues that
-	affect the whole community.</p>
-
-      <p>Thanks to everyone who participated and helped bring some of the
-	issues we talked about forward.</p>
-    <h3>Open tasks:</h3><ol><li>Schedule the next documentation sprint before the next
-	EuroBSDCon and include different timezones.</li><li>Work on the todo items identified during the sprint.</li><li>Resolve open documentation problem reports identified to be
-	fixed, but still open for some reason.</li></ol><hr /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/DutchDocumentationProject" title="http://wiki.FreeBSD.org/DutchDocumentationProject">Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/DutchDocumentationProject" title="Wiki Page">http://wiki.FreeBSD.org/DutchDocumentationProject</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=Hid@//depot/projects/docproj_nl/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=Hid@//depot/projects/docproj_nl/?ac=83">Perforce repository</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=Hid@//depot/projects/docproj_nl/?ac=83" title="Perforce repository">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=Hid@//depot/projects/docproj_nl/?ac=83</a></td></tr></table><p>
-	Contact:
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last period most work went into keeping the Handbook
-	up to date; it is currently up-to-date except for a section on
-	network servers.  Other areas being worked on are the FAQ and the
-	web site.  The latter two are still a work-in-progress.</p>
-    <h3>Open tasks:</h3><ol><li>Volunteers! The best part is that you do not need to be an
-	expert on FreeBSD nor the Dutch language to join, just some
-	enthusiasm and spare time.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>The www/ja and doc/ja_JP.eucJP/books/handbook subtrees have
-	constantly been updated.  During this period, many part of out-dated
-	contents in the www/ja subtree were updated to the latest versions
-	in the English counterpart.  Thus most of the files in the subtree
-	are already synchronized with www/en at this moment, and this
-	updating work will be finished within this year.</p>
-
-      <p>For FreeBSD Handbook, translation work for the kernelconfig section
-	was just started.  In addition, we are planning to translate the
-	upcoming release announcement because it is also important for
-	Japanese people.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work for outdated and/or non-translated
-	documents in both doc/ja_JP.eucJP and www/ja.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-the-Sony-Playstation-3" href="#FreeBSD-on-the-Sony-Playstation-3" id="FreeBSD-on-the-Sony-Playstation-3">FreeBSD on the Sony Playstation 3</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~nwhitehorn/ps3/" title="http://people.freebsd.org/~nwhitehorn/ps3/"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~nwhitehorn/ps3/" title="">http://people.freebsd.org/~nwhitehorn/ps3/</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@freebsd.org">nwhitehorn@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD Playstation 3 port is now fairly mature and will be
-	included in the 9.0 release, starting with BETA2.  Most internal
-	devices, including the USB ports, bluetooth, ethernet, and SATA
-	devices are now supported, and the operating system can be
-	installed to and boot from the internal hard disk.</p>
-
-      <p>There are several remaining pieces to the port (Wireless,
-	Sound, X11, and the SPUs), which may be interesting
-	projects for those interested in non-PC architectures.</p>
-    <h3>Open tasks:</h3><ol><li>Built-in wireless.  The 802.11 wireless interface on the
-	Playstation 3 is multiplexed through the wired ethernet MAC and
-	is currently unsupported.</li><li>The sound hardware is not currently supported.</li><li>The framebuffer driver does not currently support X11.
-	This would involve writing a simple X11 framebuffer driver to
-	connect to syscons.</li><li>The synergistic processing units (SPUs) on the Cell
-	processor are not supported yet.  They present an interesting
-	model of heterogeneous computing, more suited for full treatment
-	by a UNIX-type kernel than GPGPU computing: each SPU has a
-	concept of user and supervisor mode, as well as interrupts, and
-	can share MMU context with the main CPU cores. As such, they in
-	principle can support a full UNIX process model.</li></ol><hr /><h2><a name="FreeBSD/arm-on-Marvell-Armada-XP" href="#FreeBSD/arm-on-Marvell-Armada-XP" id="FreeBSD/arm-on-Marvell-Armada-XP">FreeBSD/arm on Marvell Armada XP</a></h2><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>Marvell Armada XP is a complete system-on-chip solution based on
-	Sheeva embedded CPU.  These devices integrate up to four ARMv6/v7
-	compliant Sheeva CPU cores with shared L2 cache.  This work is
-	extending FreeBSD/arm infrastructure towards support for recent ARM
-	architecture variations along with a basic set of device drivers
-	for integrated peripherials.  Current FreeBSD suppport for Armada XP
-	includes:</p>
-
-      <ul>
-	<li>Booting via U-Boot bootloader</li>
-	<li>ARMv6/v7 support</li>
-	<ul>
-	  <li>Reworked CPU indentification scheme</li>
-	  <li>New cache identification scheme</li>
-	  <li>Support for PIPT caches</li>
-	  <li>Reworked PMAP for ARMv6/v7 features</li>
-	</ul>
-	<li>Serial console support (UART)</li>
-	<li>Interrupt controller</li>
-	<li>Integrated timers</li>
-	<li>USB driver attachment</li>
-	<li>Ethernet controller driver</li>
-      </ul>
-
-      <p>Next steps:</p>
-      <ul>
-	<li>L2 cache support</li>
-	<li>SMP support</li>
-	<li>PCI-Express and SATA drivers</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD/powerpc-on-AppliedMicro-APM86290" href="#FreeBSD/powerpc-on-AppliedMicro-APM86290" id="FreeBSD/powerpc-on-AppliedMicro-APM86290">FreeBSD/powerpc on AppliedMicro APM86290</a></h2><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The APM86290 system-on-chip device is a member of AppliedMicro's
-	PACKETpro family of embedded processors.  The chip includes two
-	Power Architecture PPC465 processor cores, which are compliant with
-	Book-E specification of the architecture, and a number of
-	integrated peripherals.  This work is extending current Book-E
-	support in FreeBSD towards PPC4xx processors variation along with
-	device drivers for integrated peripherials.  Current FreeBSD
-	APM86290 support includes:</p>
-
-      <ul>
-	<li>Booting via U-Boot bootloader</li>
-	<li>Support for PPC465 core</li>
-	<li>L1 cache</li>
-	<li>Serial console (UART)</li>
-      </ul>
-
-      <p>Next steps:</p>
-      <ul>
-	<li>Interrupt controller</li>
-	<li>EHCI USB driver attachment</li>
-	<li>Ethernet controller</li>
-	<li>Queue Manager/Traffic Manager</li>
-	<li>L2 cache support</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD/powerpc64-on-IBM-pSeries-machines" href="#FreeBSD/powerpc64-on-IBM-pSeries-machines" id="FreeBSD/powerpc64-on-IBM-pSeries-machines">FreeBSD/powerpc64 on IBM pSeries machines</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="svn://svn.FreeBSD.org/base/projects/pseries/" title="svn://svn.FreeBSD.org/base/projects/pseries/">Development Branch</a></td><td>
-	    URL: <a href="svn://svn.FreeBSD.org/base/projects/pseries/" title="Development Branch">svn://svn.FreeBSD.org/base/projects/pseries/</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Andreas
-	  Tobler
-	 &lt;<a href="mailto:andreast@FreeBSD.org">andreast@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of this project is to make FreeBSD running on PAPR
-	compliant machines like the IBM pSeries family.</p>
-
-      <p>Currently we can boot a POWER7 emulation under a recent qemu
-	snapshot.</p>
-
-      <p>The boot process stops when trying to find a PIC.</p>
-
-      <p>The same applies for an IntelliStation-285. (POWER5+).</p>
-    <h3>Open tasks:</h3><ol><li>Implement interrupt controller.</li><li>PCI bus scanning.</li><li>Drivers, drivers, drivers.</li><li>Improve memory management.</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <ul>
-	<li>The iommu(4) driver has been changed to take advantage of
-	  the streaming buffers of the host-PCI and host-SBus bridges if
-	  present, which in at least some configurations results in a
-	  modest performance improvement due to the caching of DMA
-	  transactions.  As a prerequisite, the bus_dma(9) usage of all
-	  drivers compiled as part of the sparc64 GENERIC kernel has been
-	  reviewed and fixed and in case of sound(4) and sym(4) at least
-	  worked around as necessary in order to be able to use the
-	  streaming buffers.
-	  <br clear="none" />
-
-	  Support for this will be merged back to 8-STABLE prior to
-	  8.3-RELEASE.</li>
-
-	<li>Following the update of the in-tree binutils to 2.17.50,
-	  which now for the first time include support for GNUTLS on
-	  sparc64 in the base, support for TLS relocations on sparc64 was
-	  added to rtld(1) and enabled in the base GCC and
-	  malloc(3).</li>
-
-	<li>Support and a workaround necessary for Sun Fire V890
-	  equipped with UltraSPARC-IV was added.
-	  <br clear="none" />
-
-	  Support for these will be merged back to 8-STABLE prior to
-	  8.3-RELEASE.</li>
-
-	<li>The schizo(4) driver has been updated to also support the
-	  XMITS Fireplane/Safari to PCI-X bridges and a workaround for
-	  Casinni/Skyhawk combinations has been added.  Chances are that
-	  the latter solves the crashes seen when using the on-board
-	  Casinni NICs of Sun Fire V480 equipped with centerplanes other
-	  than 501-6780 or 501-6790.
-	  <br clear="none" />
-
-	  These changes have been merged back to 8-STABLE and will be
-	  part of 8.3-RELEASE.</li>
-
-	<li>As part of the largeSMP project which had the goal of
-	  supporting more than 32 CPU cores in FreeBSD several parts of
-	  the sparc64 specific code had to be adapted mainly in the
-	  assembler bits but as a result now also supports more than 32
-	  CPU cores.</li>
-
-	<li>On machines where we do not need to lock the kernel TSB
-	  into the dTLB and thus may basically use the entire 64-bit
-	  kernel address space, i.e. on machines equipped with
-	  UltraSPARC-III+ and greater CPUs, the kernel virtual memory was
-	  increased to not be limited by VM_KMEM_SIZE_MAX and
-	  VM_KMEM_SIZE_SCALE decreased to 1 allowing kernel to use more
-	  memory as for example useful for ZFS.
-	  <br clear="none" />
-
-	  These changes will be merged back to 8-STABLE prior to
-	  8.3-RELEASE.</li>
-
-	<li>The shortcut taken in the code responsible for flushing
-	  user mappings from the TLBs of UltraSPARC-III and greater CPUs
-	  turned out to not scale well on MP-systems with more than 8 CPU
-	  cores and thus was re-written.  As a result it now scales up to
-	  at least 16-way machines.
-	  <br clear="none" />
-
-	  These changes will be merged back to 8-STABLE prior to
-	  8.3-RELEASE.</li>
-      </ul>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium" href="#Chromium" id="Chromium">Chromium</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.chromium.org/Home" title="http://www.chromium.org/Home">Main project site</a></td><td>
-	    URL: <a href="http://www.chromium.org/Home" title="Main project site">http://www.chromium.org/Home</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/chromium" title="http://trillian.chruetertee.ch/chromium">FreeBSD porting site</a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/chromium" title="FreeBSD porting site">http://trillian.chruetertee.ch/chromium</a></td></tr></table><p>
-	Contact:
-	  Chromium on FreeBSD Team
-	 &lt;<a href="mailto:chromium@FreeBSD.org">chromium@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last quarter we have been keeping the Chromium
-	browser up to date, with new major releases being imported into the
-	Ports Collection the same day as the upstream release.  As time
-	passes by, more patches are incorporated or otherwise became
-	obsolete by virtue of upstream code cleanups.  Version 13 is already
-	available from the Chruetertee repository, with 70 patches
-	less than version 12.</p>
-    <hr /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Haskell" title="http://wiki.FreeBSD.org/Haskell">FreeBSD Haskell wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Haskell" title="FreeBSD Haskell wiki page">http://wiki.FreeBSD.org/Haskell</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="https://github.com/freebsd-haskell/freebsd-haskell/">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="FreeBSD Haskell ports repository">https://github.com/freebsd-haskell/freebsd-haskell/</a></td></tr><tr><td><a href="http://haskell.org/mailman/listinfo/freebsd-haskell/" title="http://haskell.org/mailman/listinfo/freebsd-haskell/">FreeBSD Haskell mailing list</a></td><td>
-	    URL: <a href="http://haskell.org/mailman/listinfo/freebsd-haskell/" title="FreeBSD Haskell mailing list">http://haskell.org/mailman/listinfo/freebsd-haskell/</a></td></tr></table><p>
-	Contact:
-	  G�bor J�nos
-	  P�LI
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Giuseppe
-	  Pilichi
-	 &lt;<a href="mailto:jacula@FreeBSD.org">jacula@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce that the FreeBSD Haskell Team has
-	committed Haskell Platform 2011.2.0.1 to the FreeBSD Ports Collection,
-	as well as updated existing ports to their latest stable versions.
-	Apart from the ports officially available there, many ports (Snap
-	web framework, Leksah, and their dependencies) are still waiting to
-	be added.  Any users who like to get early access to them, please
-	refer to the instructions at <a href="https://github.com/freebsd-haskell/freebsd-haskell/" shape="rect">our
-	development repository</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Update Haskell Platform (along with GHC) to 2011.4.0.0 as
-	soon as it gets out.</li><li>Add more ports to the Ports Collection.</li><li>Create a port for Happstack.</li><li>Create a port for gitit.</li></ol><hr /><h2><a name="KDE-FreeBSD" href="#KDE-FreeBSD" id="KDE-FreeBSD">KDE-FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE-FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE-FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-switzerland" title="http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-switzerland">Dot article on the KDE sprints in Switzerland</a></td><td>
-	    URL: <a href="http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-switzerland" title="Dot article on the KDE sprints in Switzerland">http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-switzerland</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/avilla/2011/06/14/call-for-tests-kde-pim-4-6-0" title="http://blogs.FreeBSDish.org/avilla/2011/06/14/call-for-tests-kde-pim-4-6-0">Call for test of KDE PIM 4.6.0</a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/avilla/2011/06/14/call-for-tests-kde-pim-4-6-0" title="Call for test of KDE PIM 4.6.0">http://blogs.FreeBSDish.org/avilla/2011/06/14/call-for-tests-kde-pim-4-6-0</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51 Switzerland</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51 Switzerland">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde-freebsd@kde.org">kde-freebsd@kde.org</a>&gt;
-	</p>
-      <p>Alberto Villa and Raphael Kubo da Costa went to Randa,
-	Switzerland, to attend, respectively, the KDE Multimedia/Kdenlive
-	sprint and the Platform 11 sprint.  The sprints afforded them the
-	opportunity to form closer bonds with the upstream KDE community,
-	to learn about the future of Qt and KDE and make sure FreeBSD's
-	needs are taken into account.  For more information see the article
-	"From Platform to Frameworks -- KDE hackers meet in Switzerland" at
-	dot.kde.org.</p>
-
-      <p>The KDE on FreeBSD team have continued to improve the experience
-	of KDE and Qt under FreeBSD.  The latest round of improvements
-	include:</p>
-
-      <ul>
-	<li>Qt supports Clang as a compiler</li>
-      </ul>
-
-      <p>The team has also made many releases and upstreamed many fixes
-	and patches.  The latest round of releases include:</p>
-
-      <ul>
-	<li>Qt: 4.7.3</li>
-	<li>KDE: 4.6.3; 4.6.4; 4.6.5</li>
-	<li>Amarok: 2.4.1</li>
-	<li>Digikam (and KIPI-plugins): 1.9.0</li>
-      </ul>
-
-      <p>Further testing is requested for KDE PIM 4.6.0 and Calligra
-	2.3.72 before the ports are committed.  To test the ports please
-	visit Alberto Villa's call for test and area51.</p>
-
-      <p>The team is always looking for more testers and porters so
-	please visit us at kde-freebsd@kde.org and our homepage.</p>
-    <h3>Open tasks:</h3><ol><li>Testing KDE PIM 4.6.0.</li></ol><hr /><h2><a name="libvirt-networking-port" href="#libvirt-networking-port" id="libvirt-networking-port">libvirt networking port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.libvirt.org/" title="http://www.libvirt.org/"></a></td><td>
-	    URL: <a href="http://www.libvirt.org/" title="">http://www.libvirt.org/</a></td></tr></table><p>
-	Contact:
-	  Jason
-	  Helfman
-	 &lt;<a href="mailto:jhelfman@experts-exchange.com">jhelfman@experts-exchange.com</a>&gt;
-	<br />
-	Contact:
-	  Daniel P.
-	  Berrange
-	 &lt;<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>&gt;
-	</p>
-      <p>Libvirt, a Toolkit to interact with virtualization
-	capabilities, has been ported to FreeBSD, however the networking
-	capabilities have been disabled as they are incompatible with
-	FreeBSD.  Libvirt currently supports connecting to many types of
-	hypervisors, however it can be a far more useful tool if the
-	networking capabilities were ported to FreeBSD.</p>
-
-      <p>In contacting Daniel P. Berrange, he was kind enough to
-	advise on what is required to port networking of libvirt to
-	FreeBSD.  His response is paraphrased below:</p>
-
-      <p>There are two aspects to networking in libvirt:</p>
-
-      <ul>
-	<li>The virtual network driver (in
-	  src/network/bridge_driver.c) uses the Linux kernel's
-	  native 'bridge' functionality to provide an isolated, or
-	  routed, or NATed network connection to guests.  There is a
-	  bridge device on the host created, and guest TAP devices are
-	  added to it.  There is no physical ethernet device added to the
-	  bridge, and iptables is used to control whether the host OS
-	  routes traffic to/from the bridge &amp; physical LAN.<br clear="none" />
-	  Porting bridge and bridge control functionality to FreeBSD
-	  would need to be done, and how to nat/routed/isolated guest
-	  configs and write a compatible version of bridge_driver.c
-	  for FreeBSD.</li>
-
-	<li>The host interface driver (in src/inteface/netcf_driver.c)
-	  uses the netcf library to manage configuration of host network
-	  interfaces to do things like bonding, vlans, bridging and controlling
-	  the interfaces availability.  The core job is to port netcf to work
-	  with FreeBSD.  A netcf backend that understands FreeBSD's networking
-	  configuration files and calls appropriate tools to bring
-	  interfaces online/offline would need to be created.</li>
-      </ul>
-
-      <p>Both these jobs are pretty much independent, so can easily be
-	done in parallel.</p>
-    <h3>Open tasks:</h3><ol><li>Port bridge network driver for libvirt.</li><li>Port netcf driver for libvirt.</li></ol><hr /><h2><a name="Portbuilder" href="#Portbuilder" id="Portbuilder">Portbuilder</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/DragonSA/portbuilder" title="https://github.com/DragonSA/portbuilder">GIT Repository</a></td><td>
-	    URL: <a href="https://github.com/DragonSA/portbuilder" title="GIT Repository">https://github.com/DragonSA/portbuilder</a></td></tr><tr><td><a href="https://github.com/DragonSA/portbuilder/blob/0.1.3/README" title="https://github.com/DragonSA/portbuilder/blob/0.1.3/README">README</a></td><td>
-	    URL: <a href="https://github.com/DragonSA/portbuilder/blob/0.1.3/README" title="README">https://github.com/DragonSA/portbuilder/blob/0.1.3/README</a></td></tr><tr><td><a href="https://github.com/DragonSA/portbuilder/blob/0.1.3/TODO" title="https://github.com/DragonSA/portbuilder/blob/0.1.3/TODO">TODO</a></td><td>
-	    URL: <a href="https://github.com/DragonSA/portbuilder/blob/0.1.3/TODO" title="TODO">https://github.com/DragonSA/portbuilder/blob/0.1.3/TODO</a></td></tr></table><p>
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:naylor.b.david@gmail.com">naylor.b.david@gmail.com</a>&gt;
-	</p>
-      <p>I would like to introduce a project that has been in the works
-	for the last 3 years.  From the projects README:</p>
-
-      <p>A concurrent ports building tool.  Although FreeBSD ports
-	supports building a single port using multiple jobs (via
-	MAKE_JOBS), it cannot build multiple ports concurrently.  This tool
-	accomplishes just that.</p>
-
-      <p>Some of its key features:</p>
-
-      <ul>
-	<li>Concurrent port building</li>
-	<li>Load control</li>
-	<li>Top like UI</li>
-	<li>Persistent builds (by default)</li>
-      </ul>
-
-      <p>Portbuilder originally used threads to control each port at each
-	stage of the build however the required locks resulting in
-	deadlocks, and some ports would not build correctly.  To resolve
-	those issues a rewrite was done to use only a single thread, making
-	all locking code redundant.  Thanks to the use of kqueue(2) the
-	overhead of managing concurrent port builds is minimal.  Further
-	work to reduce that overhead is underway.</p>
-
-      <p>Portbuilder is installable from ports under
-	ports-mgmt/portbuilder, see the README for usage details.  Please
-	note that this is considered BETA quality, that the feature set and
-	API are expected to change, and that portbuilder may crash or fail
-	to behave properly.</p>
-    <h3>Open tasks:</h3><ol><li>Wiki page.</li><li>Testing.</li><li>See TODO.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td>
-	    URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr><tr><td><a href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-baptiste-daroussin.html" title="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-baptiste-daroussin.html"></a></td><td>
-	    URL: <a href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-baptiste-daroussin.html" title="">http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-baptiste-daroussin.html</a></td></tr><tr><td><a href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-julien-laffaye.html" title="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-julien-laffaye.html"></a></td><td>
-	    URL: <a href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-julien-laffaye.html" title="">http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-julien-laffaye.html</a></td></tr><tr><td><a href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-thomas-abthorpe.html" title="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-thomas-abthorpe.html"></a></td><td>
-	    URL: <a href="http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-thomas-abthorpe.html" title="">http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-thomas-abthorpe.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/2011/05/26/thankyoufoundation/" title="http://blogs.FreeBSDish.org/portmgr/2011/05/26/thankyoufoundation/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/2011/05/26/thankyoufoundation/" title="">http://blogs.FreeBSDish.org/portmgr/2011/05/26/thankyoufoundation/</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree slowly moves up closer to 23,000.  The PR count
-	still remains at about 1100.</p>
-
-      <p>In Q2 we added 3 new committers, took in 2 commit bits for safe
-	keeping, and added a new member to portmgr.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports updates.
-	Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>ports/154044, -exp run to update x11-toolkits/open-motif</li>
-
-	<li>ports/155269, -exp run to fix problem with base/ports
-	  ncurses</li>
-
-	<li>ports/155215, -exp run to update gmake, completed by
-	  linimon</li>
-
-	<li>ports/156575, -exp run to generate a subset of ports in
-	  INDEX</li>
-
-	<li>ports/155983, -exp run to reroot md5 in /sbin</li>
-
-	<li>ports/139116, -exp run to call target "install-rc-script"
-	  before "post-install"</li>
-
-	<li>ports/155510, -exp run to remove support for pre 7.X</li>
-
-	<li>ports/156533, -exp run to patch bsd.apache.mk</li>
-
-	<li>ports/152498, -exp run to improve USERS/GROUPS handling</li>
-
-	<li>flz has been performing clang -exp runs</li>
-
-	<li>erwin performed -exp run for perl 5.12.4 update</li>
-
-	<li>pav performed multiple -exp runs for gtk3</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Looking for help getting
-	<a href="http://wiki.FreeBSD.org/PortsAndClang" shape="rect">ports to build with
-	clang</a>.</li><li>Looking for help fixing <a href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent" shape="rect">ports broken
-	on CURRENT</a>.  (List needs updating, too)</li><li>Looking for help with <a href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures" shape="rect">
-	Tier-2 architectures</a>.  (List needs updating, too)</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing, and closing.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="bsd_day(2011)" href="#bsd_day(2011)" id="bsd_day(2011)">bsd_day(2011)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bsdday.eu/2011" title="http://bsdday.eu/2011"></a></td><td>
-	    URL: <a href="http://bsdday.eu/2011" title="">http://bsdday.eu/2011</a></td></tr></table><p>
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The purpose of this one-day event is to gather Central European
-	developers of today's open-source BSD systems to popularize their
-	work and their organizations, and to meet each other in the real
-	life.  We would also like to motivate potential future developers
-	and users, especially undergraduate university students to work
-	with BSD systems.</p>
-
-      <p>This year's BSD-Day will be held in Bratislava, Slovakia at
-	Slovak University of Technology, Faculty of Electrical
-	Engineering and Information Technology on November 5, 2011.</p>
-
-      <p>Everybody is welcome!</p>
-    <h3>Open tasks:</h3><ol><li>Apply.  We are looking for you!</li></ol><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Capsicum-adaptation-and-core-libraries" href="#Capsicum-adaptation-and-core-libraries" id="Capsicum-adaptation-and-core-libraries">Capsicum adaptation and core libraries</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cl.cam.ac.uk/research/security/capsicum" title="http://www.cl.cam.ac.uk/research/security/capsicum"></a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/research/security/capsicum" title="">http://www.cl.cam.ac.uk/research/security/capsicum</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/SOC2011IlyaBakulin" title="http://wiki.FreeBSD.org/SOC2011IlyaBakulin"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SOC2011IlyaBakulin" title="">http://wiki.FreeBSD.org/SOC2011IlyaBakulin</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:kibab@FreeBSD.org">kibab@FreeBSD.org</a>&gt;
-	</p>
-      <p>Some applications from the base system received sandboxing
-	support, current task is to adapt lightweight resolver daemon for
-	using it in sandboxes &#8212; this fixes problems with applications that
-	need to convert IP addresses into domain names while in
-	sandbox.</p>
-    <h3>Open tasks:</h3><ol><li>Add sandboxing to even more applications in the base
-	system.</li><li>Help Jonathan Anderson and Robert Watson to merge
-	FreeBSD-Capsicum into FreeBSD-HEAD.</li></ol><hr /><h2><a name="Disk-device-error-counters" href="#Disk-device-error-counters" id="Disk-device-error-counters">Disk device error counters</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Disk%20device%20error%20counters" title="http://wiki.FreeBSD.org/Disk%20device%20error%20counters">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Disk%20device%20error%20counters" title="Wiki page">http://wiki.FreeBSD.org/Disk%20device%20error%20counters</a></td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Dudinskyi
-	 &lt;<a href="mailto:dudinskyj@gmail.com">dudinskyj@gmail.com</a>&gt;
-	</p>
-      <p>Currently, I work on schedule, I printed the information of
-	disk error in utility iostat option -E.  While only displays five
-	types of errors.  Further analysis will give me the opportunity to
-	identify other types of disk errors.</p>
-    <h3>Open tasks:</h3><ol><li>Search other type of error and the place of their
-	registration.</li><li>Maybe find a better place registration of errors than
-	xpt_done().</li></ol><hr /><h2><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/SummerOfCode2011" title="http://wiki.FreeBSD.org/SummerOfCode2011">Summer of Code 2011 Project Wiki Pages</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/SummerOfCode2011" title="Summer of Code 2011 Project Wiki Pages">http://wiki.FreeBSD.org/SummerOfCode2011</a></td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are happy to be participating in our 7th Google Summer of
-	Code.  After the mid-term evaluation we have 15 projects working
-	towards the final evaluation.  You can see the latest status on
-	student's individual wiki pages or by subscribing to the soc-status
-	mailing list.</p>
-    <hr /><h2><a name="nvi-iconv" href="#nvi-iconv" id="nvi-iconv">nvi-iconv</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1" title="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1">Project proposal</a></td><td>
-	    URL: <a href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1" title="Project proposal">http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1</a></td></tr><tr><td><a href="https://github.com/lichray/nvi2" title="https://github.com/lichray/nvi2">GitHub page</a></td><td>
-	    URL: <a href="https://github.com/lichray/nvi2" title="GitHub page">https://github.com/lichray/nvi2</a></td></tr></table><p>
-	Contact:
-	  Zhihao
-	  Yuan
-	 &lt;<a href="mailto:lichray@gmail.com">lichray@gmail.com</a>&gt;
-	</p>
-      <p>This project creates a multibyte aware nvi fork.  While most of
-	the userland tools in the FreeBSD base system support multibyte
-	encodings, there is no pure-licensed nvi fork comes with
-	sufficient multibyte encoding (both Unicode and non-Unicode)
-	support prior to this.</p>
-
-      <p>Currently, functionally, the new nvi is ready for testing.  The
-	description is at https://github.com/lichray/nvi2/wiki (the patch
-	is deprecated).  I will commit a new one latter.</p>
-
-      <p>The features dropped from nvi-1.79 are:</p>
-
-      <ul>
-	<li>Perl and Tcl interpreter supports;</li>
-
-	<li>The whole Perl/Tcl/Tk scripting framework;</li>
-
-	<li>A third-party gtags support.</li>
-      </ul>
-
-      <p>and the features adopted from nvi-1.81.6 includes:</p>
-
-      <ul>
-	<li>Multibyte encoding supports (wchar_t + libiconv +
-	  libncursesw);</li>
-
-	<li>fileencoding and inputencoding options;</li>
-
-	<li>Undocumented :vsplit command, which vertically splits the
-	  screen.</li>
-      </ul>
-
-      <p>Many known bugs, incomplete code from nvi-devel are fixed.
-	However, I find a serious memory leaking (via valgrind) in the
-	nvi-devel iconv framework.  This requires a careful review.</p>
-    <h3>Open tasks:</h3><ol><li>Reviews the iconv part and fixes the memory leak.</li><li>Ex scripts for testing.  But it seems that I have no
-	experience on that...</li><li>File encoding detection.  My plan it to detect UTF-16 BOM
-	first, then UTF-8.  If all fails, uses locale.  UTF-8 BOM is not
-	supported by iconv, and we need to discuss whether we should
-	support it in the editor.</li></ol><hr /><h2><a name="Replacing-the-Regular-Expression-Code" href="#Replacing-the-Regular-Expression-Code" id="Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/G%C3%A1borSoC2011" title="http://wiki.FreeBSD.org/G%C3%A1borSoC2011">Wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/G%C3%A1borSoC2011" title="Wiki page">http://wiki.FreeBSD.org/G%C3%A1borSoC2011</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The current regular expression code in libc is quite outdated
-	and does not support wide characters.  There are various open
-	source regular expression libraries but replacing the code is
-	not a simple task because there are quite many considerations
-	and requirements.  The best candidate is TRE, which is a
-	BSD-licensed, supports wide and multibyte characters, conforms
-	to POSIX and it performs well compared to another available
-	alternatives, so the work has been started with TRE.  Apart
-	from the replacement, the plan is to implement heuristical
-	matching, which will speed up the pattern matching
-	significantly.  Besides, grep and diff in the base system have
-	been using the GNU regex code, which has a more permissive
-	syntax.  It is desired to have a single regex engine in the
-	base system, so the GNU syntax has to be implemented (as an
-	optional feature), as well.</p>
-
-      <p>So far, a fast string matching algorithm has been added,
-	which is a variant of the Turbo Boyer-Moore algorithm.  It has
-	been slightly tuned to support not only literal patterns but
-	patterns containing $^. symbols.  This algorithm is used
-	automatically when the pattern makes it possible.</p>
-
-      <p>Besides, heuristic matching has also been implemented.  If
-	the fast matcher cannot be applied directly, it parses the
-	pattern and separates the fixed-length prefix and suffix of
-	the pattern.  Then it can be used to locate the possibly
-	matching regions of the text, using a more efficient algorithm
-	than the full regex NFA and the latter only has to be applied
-	to the narrow context that has been located.</p>
-    <h3>Open tasks:</h3><ol><li>Implement GNU regex syntax.</li><li>Add test suite GNU-specific behavior and also add some
-	tests for locale-specific behavior.</li><li>Test and review the code.  Contact the author and check if
-	these improvements can be added to the upstream code so that
-	more people can benefit from this.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2011-07-2011-09.html b/website/content/en/status/report-2011-07-2011-09.html
deleted file mode 100644
index 6f6841e34e..0000000000
--- a/website/content/en/status/report-2011-07-2011-09.html
+++ /dev/null
@@ -1,1144 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between July and
-      September 2011.  It is the third of the four reports planned for 2011.
-      This quarter was mainly devoted to polishing the bits for the next
-      major version of FreeBSD, 9.0, which is to be released by then end
-      of this year.</p><p>Thanks to all the reporters for the excellent work! This report
-      contains 28 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between October and December 2011 is January 15th, 2012.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#GELI-status-update">GELI status update</a></li><li><a href="#HAST-(Highly-Available-Storage)-status-update">HAST (Highly Available Storage) status update</a></li><li><a href="#pfSense">pfSense</a></li><li><a href="#Tool-for-providing-FreeBSD-VM-Images">Tool for providing FreeBSD VM Images</a></li><li><a href="#ZFSguru">ZFSguru</a></li><li><a href="#ZRouter.org-project-&#8212;-a-FreeBSD-based-firmware-for-embedded-devices">ZRouter.org project &#8212; a FreeBSD-based firmware for embedded
-      devices</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li><li><a href="#The-FreeBSD-Release-Engineering-Team">The FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#802.11n-/-atheros">802.11n / atheros</a></li><li><a href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></li><li><a href="#Ethernet-Switch-Framework">Ethernet Switch Framework</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#The-new-CARP">The new CARP</a></li><li><a href="#VM-layer-for-allocations-larger-than-a-page">VM layer for allocations larger than a page</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Doc-sprint-on-IRC,-September-5,-2011">Doc sprint on IRC, September 5, 2011</a></li><li><a href="#The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></li><li><a href="#The-FreeBSD-Greek-Documentation-Project">The FreeBSD Greek Documentation Project</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-on-Marvell-Armada-XP">FreeBSD/arm on Marvell Armada XP</a></li><li><a href="#FreeBSD/powerpc-on-AppliedMicro-APM86290">FreeBSD/powerpc on AppliedMicro APM86290</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#OpenAFS-port">OpenAFS port</a></li><li><a href="#Portmaster">Portmaster</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#bsd_day(2011)">bsd_day(2011)</a></li><li><a href="#EuroBSDcon-2011">EuroBSDcon 2011</a></li><li><a href="#FreeBSD-Developer-Summit,-Maarssen">FreeBSD Developer Summit, Maarssen</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Multibyte-Encoding-Support-in-Nvi">Multibyte Encoding Support in Nvi</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="GELI-status-update" href="#GELI-status-update" id="GELI-status-update">GELI status update</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Selected GELI (disk encryption GEOM class) changes since 2010/Q3
-	report:</p>
-
-      <ul>
-	<li>Implementation of suspend/resume functionality.</li>
-	<li>New version subcommand to check GELI providers version.</li>
-	<li>New -V option for init subcommand, which allows to create
-	  GELI providers for older FreeBSD versions.</li>
-	<li>Significant aesni(4) performance improvements for AES-XTS
-	  algorithm.</li>
-      </ul>
-    <hr /><h2><a name="HAST-(Highly-Available-Storage)-status-update" href="#HAST-(Highly-Available-Storage)-status-update" id="HAST-(Highly-Available-Storage)-status-update">HAST (Highly Available Storage) status update</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mikolaj
-	  Golub
-	 &lt;<a href="mailto:trociny@FreeBSD.org">trociny@FreeBSD.org</a>&gt;
-	</p>
-      <p>HAST is under active development.  Some changes since Q1
-	report:</p>
-
-      <ul>
-	<li>Async replication mode.  Unfortunately it will not make it into
-	  9.0-RELEASE (pjd@).</li>
-	<li>IPv6 support (pjd@).</li>
-	<li>Activemap fix that significantly reduces number of metadata
-	  updates (trociny@).</li>
-	<li>Provider's write cache flush after metadata updates
-	  (pjd@).</li>
-	<li>Possibility to specify pidfile in configuration file
-	  (pjd@).</li>
-	<li>Many bug fixes and other improvments.</li>
-      </ul>
-    <hr /><h2><a name="pfSense" href="#pfSense" id="pfSense">pfSense</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pfsense.org/" title="http://www.pfsense.org/">pfSense Home</a></td><td>
-	    URL: <a href="http://www.pfsense.org/" title="pfSense Home">http://www.pfsense.org/</a></td></tr></table><p>
-	Contact:
-	  Scott
-	  Ullrich
-	 &lt;<a href="mailto:sullrich@gmail.com">sullrich@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Chris
-	  Buechler
-	 &lt;<a href="mailto:cbuechler@gmail.com">cbuechler@gmail.com</a>&gt;
-	</p>
-      <p>pfSense 2.0 has been released to the world.  This brings the past
-	three years of new feature additions, with significant enhancements
-	to almost every portion of the system.  The changes and new features
-	are <a href="http://doc.pfsense.org/index.php/2.0_New_Features_and_Changes" shape="rect">
-	summarized here</a>.  This is by far the most widely deployed
-	release we have put out, thanks to the efforts of thousands of
-	members of the community.</p>
-    <h3>Open tasks:</h3><ol><li>Work on 2.1 is underway with the biggest changes being IPV6
-	support and PBI packaged binaries for the package system.</li></ol><hr /><h2><a name="Tool-for-providing-FreeBSD-VM-Images" href="#Tool-for-providing-FreeBSD-VM-Images" id="Tool-for-providing-FreeBSD-VM-Images">Tool for providing FreeBSD VM Images</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/yerenkow/freebsd-vm-image" title="https://github.com/yerenkow/freebsd-vm-image">Main github repo</a></td><td>
-	    URL: <a href="https://github.com/yerenkow/freebsd-vm-image" title="Main github repo">https://github.com/yerenkow/freebsd-vm-image</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Yerenkow
-	 &lt;<a href="mailto:yerenkow@gmail.com">yerenkow@gmail.com</a>&gt;
-	</p>
-      <p>A set of scripts to make building FreeBSD VM images easy.</p>
-
-      <p>Providing a way to make regular build images of the latest version
-	from SVN.  Images currently can be copied with `dd` to USB
-	flash (for testing on real hardware) and VirtualBox
-	(.vdi).</p>
-    <h3>Open tasks:</h3><ol><li>Build images with ports-set from main port-tree</li><li>Build images with ports-set from main port-tree plus
-	overrides from area51 (like experimental images)</li><li>Build images with special development branches included (like
-	for testing drivers)</li></ol><hr /><h2><a name="ZFSguru" href="#ZFSguru" id="ZFSguru">ZFSguru</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zfsguru.com" title="http://zfsguru.com">ZFSguru main website</a></td><td>
-	    URL: <a href="http://zfsguru.com" title="ZFSguru main website">http://zfsguru.com</a></td></tr><tr><td><a href="http://zfsguru.com" title="http://zfsguru.com"></a></td><td>
-	    URL: <a href="http://zfsguru.com" title="">http://zfsguru.com</a></td></tr></table><p>
-	Contact:
-	  Jason
-	  Edwards
-	 &lt;<a href="mailto:guru@ZFSguru.com">guru@ZFSguru.com</a>&gt;
-	</p>
-      <p>ZFSguru is a newly designed Network Attached Storage operating
-	system, much like FreeNAS.  The difference is that ZFSguru
-	focuses heavily on ZFS and user friendly operation, and uses a full
-	FreeBSD distribution with no elements stripped down.  This allows
-	people new to FreeBSD and UNIX in general to access the power
-	of ZFS, while still allowing more advanced users to tweak their NAS
-	with additional functionality and use it as a normal FreeBSD
-	distribution.</p>
-
-      <p>Started a little over a year ago, the ZFSguru project is making
-	good progress.  It should already be one of the most user friendly
-	distributions focused on ZFS, and sports some very unique features.
-	The advanced ZFS benchmarking and convenient Root-on-ZFS
-	installation are good examples.  Priority is given to finishing the
-	missing core functionality, and extending the number of available
-	service addons which currently are limited to iSCSI-target and
-	VirtualBox extensions.</p>
-    <h3>Open tasks:</h3><ol><li>Finish ZFS and network related functionality in the
-	web-interface.</li><li>Introduce new service addons, adding optional functionality
-	to ZFSguru.</li><li>Extend the documentation.</li></ol><hr /><h2><a name="ZRouter.org-project-&#8212;-a-FreeBSD-based-firmware-for-embedded-devices" href="#ZRouter.org-project-&#8212;-a-FreeBSD-based-firmware-for-embedded-devices" id="ZRouter.org-project-&#8212;-a-FreeBSD-based-firmware-for-embedded-devices">ZRouter.org project &#8212; a FreeBSD-based firmware for embedded
-      devices</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zrouter.org" title="http://zrouter.org">Redmine project interface</a></td><td>
-	    URL: <a href="http://zrouter.org" title="Redmine project interface">http://zrouter.org</a></td></tr><tr><td><a href="http://lists.zrouter.org" title="http://lists.zrouter.org">Mailing lists</a></td><td>
-	    URL: <a href="http://lists.zrouter.org" title="Mailing lists">http://lists.zrouter.org</a></td></tr><tr><td><a href="http://zrouter.org/hg/zrouter/" title="http://zrouter.org/hg/zrouter/">Main ZRouter.org mercurial repository</a></td><td>
-	    URL: <a href="http://zrouter.org/hg/zrouter/" title="Main ZRouter.org mercurial repository">http://zrouter.org/hg/zrouter/</a></td></tr><tr><td><a href="http://zrouter.org/hg/FreeBSD/head/" title="http://zrouter.org/hg/FreeBSD/head/">FreeBSD HEAD copy with our modifications</a></td><td>
-	    URL: <a href="http://zrouter.org/hg/FreeBSD/head/" title="FreeBSD HEAD copy with our modifications">http://zrouter.org/hg/FreeBSD/head/</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	</p>
-      <p>ZRouter.org is a young project that aims to produce
-	FreeBSD-based firmware for small boxes such as SOHO router, APs, etc.
-	At the present time ZRouter.org is able to build working firmware
-	for:</p>
-
-      <ul>
-	<li>D-Link DAP-1350</li>
-	<li>D-Link DIR-320</li>
-	<li>D-Link DIR-320-NRU</li>
-	<li>D-Link DIR-330</li>
-	<li>D-Link DIR-615-E4</li>
-	<li>D-Link DIR-620</li>
-	<li>D-Link DIR-632</li>
-	<li>D-Link DSA-3110-A1</li>
-	<li>D-Link DSR-1000N</li>
-	<li>NorthQ NQ-900</li>
-	<li>TPLink TL-WR941ND-v3_2</li>
-	<li>Ubiquiti RSPRO</li>
-      </ul>
-
-      <p>Currently we are working on most parts of the core system but we
-	are also in the planning phase for implementing a simple web-based
-	GUI which we hope will have taken form before the next FreeBSD status
-	report.</p>
-
-      <p>We still have many items not done, so devices in that list
-	cannot be called "Production Ready" yet.  But we work on that.</p>
-
-      <p>It is easy to add new devices, because we have separate
-	definition of board and SoC(System on Chip), so if you have "Asus
-	WL-500g Premium v2" for example, you can copy D-Link/DIR-320
-	directory and tweak to work for your device.  We already have basic
-	support for:</p>
-
-      <ul>
-	<li>Broadcom BCM5354</li>
-	<li>Broadcom BCM5836</li>
-	<li>Ralink RT3052F</li>
-	<li>Ralink RT3050F</li>
-	<li>Ralink RT5350F</li>
-	<li>Atheros AR7161</li>
-	<li>Atheros AR7242</li>
-	<li>Atheros AR7241</li>
-	<li>Atheros AR7240</li>
-	<li>Atheros AR9132</li>
-	<li>Intel ixp435</li>
-	<li>Cavium CN5010</li>
-      </ul>
-
-      <p>If you have ability and time, please join us at http://zrouter.org
-	(Redmine interface and mailing lists)</p>
-    <h3>Open tasks:</h3><ol><li>Device drivers</li><li>Web UI</li><li>Control scripts</li><li>Watchdog</li><li>etc.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td>
-	    URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree slowly moves up closer to the 23,000 mark.  The PR count
-	still remains at about 1000.</p>
-
-      <p>In Q2 we added 4 new committers, but took in 6 commit bits for safe
-	keeping.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports updates.
-	Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>Python update</li>
-	<li>Boost updates</li>
-	<li>Gtk3 updates</li>
-	<li>clang testing</li>
-	<li>pkgng testing</li>
-	<li>testing ruby19</li>
-	<li>setting the default fortran to lang/gcc46</li>
-	<li>setting apache22 as default</li>
-	<li>setting the default LDFLAGS in CONFIGURE_ENV</li>
-      </ul>
-
-      <p>Work continues to refine the new build master pointyhat-west.  An
-	upgrade to -current done in September has proven problematic.  We
-	have enlisted ISC and Josh Paetzel to try to determine a fix.  In
-	the meantime, the source will be downgraded to RELENG_9.</p>
-
-      <p>The portsmon instance is being re-homed at Yahoo.  Users should
-	not see any changes.  The new instance is currently visible at
-	portsmonj.FreeBSD.org but will soon take on the
-	portsmon.FreeBSD.org name.  The team would like to express its
-	appreciation to TDC A/S for the loan of the existing machine for
-	several years.</p>
-
-      <p>Work is underway to create a new QAT instance at NYI/NJ.</p>
-
-      <p>portmgr also assisted in setting up a sparc64 machine for
-	general develop access at Yahoo.</p>
-
-      <p>Thanks to on-site work by Sean Bruno and Ben Haga, we once again
-	have access to the powerpc build machine at ISC, and powerpc builds
-	have been restarted.  They also helped us get one more i386 machine
-	back online.</p>
-
-      <p>linimon is working on a set of scripts to more quickly produce
-	pre-configured PXEboot images for package build nodes.</p>
-
-      <p>The update of __FreeBSD_version in param.h to 1000000 proved very
-	disruptive to the ports tree, triggering lots of bad assumption in
-	code that interpreted it as FreeBSD 1.  A great deal of work has
-	gone into identifying the instances of broken code and fixing and
-	upstreaming them.  While this is taking place, one recommended
-	workaround is to set your version to 999999.</p>
-    <h3>Open tasks:</h3><ol><li>Looking for help getting <a href="http://wiki.FreeBSD.org/PortsAndClang" shape="rect">ports to build with
-	clang</a>.</li><li>Looking for help fixing <a href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent" shape="rect">ports broken
-	on CURRENT</a>. (List needs updating, too)</li><li>Looking for help with <a href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures" shape="rect">
-	Tier-2 architectures</a>. (List needs updating, too)</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing and closing.</li></ol><hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The Foundation sponsored KyivBSD 2011 which was held in Kiev,
-	Ukraine on September 24.  We were represented at Ohio LinuxFest in
-	Columbus, Ohio.  And, we approved six travel grants for EuroBSDCon.
-	Stop by and visit us at the FreeBSD booth during LISA '11, December
-	7-8, in Boston, MA.</p>
-
-      <p>Three Foundation funded projects were completed during this
-	period: implementing xlocale APIs to enable porting libc++ by David
-	Chisnall, implementing DIFFUSE for FreeBSD by Swinburne University,
-	and adding GEM, KMS, and DRI support for Intel drivers by
-	Konstantin Belousov.</p>
-
-      <p>We published our <a href="http://www.FreeBSDFoundation.org/press/2011Aug-newsletter.shtml" shape="rect">
-	semi-annual newsletter</a>.  We purchased servers and other
-	hardware for the FreeBSD co-location centers at Sentex and
-	NYI.</p>
-
-      <p>The work above, as well as many other tasks which we do for the
-	FreeBSD Project, could not be done without donations.  Please help us
-	by making a donation or asking your company to make a donation.  We
-	would be happy to send marketing literature to you or your company.
-	Find out how to make a donation at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">our donate
-	page</a>.</p>
-
-      <p>Find out more up-to-date Foundation news by reading our <a href="http://FreeBSDFoundation.blogspot.com/" shape="rect">blog</a> and
-	<a href="http://www.facebook.com/FreeBSDFoundation" shape="rect">Facebook</a>
-	page.</p>
-    <hr /><h2><a name="The-FreeBSD-Release-Engineering-Team" href="#The-FreeBSD-Release-Engineering-Team" id="The-FreeBSD-Release-Engineering-Team">The FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team has been coordinating the upcoming
-	FreeBSD 9.0-RELEASE.  Thanks to work done by many of the
-	developers. The release, though delayed, is taking the shape
-	nicely.  We have reached the stage of doing the second
-	Release Candidate.  At this time we expect to have one more
-	Release Candidate, to be followed by the final release itself.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="802.11n-/-atheros" href="#802.11n-/-atheros" id="802.11n-/-atheros">802.11n / atheros</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg" title="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg" title="">http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg</a></td></tr></table><p>
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@FreeBSD.org">adrian@FreeBSD.org</a>&gt;
-	</p>
-      <p>AR5416, AR9160, and AR9280 functions in both station and hostap
-	mode.  Performance is good.</p>
-
-      <p>Software retry of frames is implemented.  Aggregation is
-	implemented.</p>
-
-      <p>BAR TX is not yet handled.  HT protection is not implemented; neither
-	is MIMO powersave.</p>
-    <h3>Open tasks:</h3><ol><li>BAR TX</li><li>MIMO powersave</li><li>Correct handling of flushing TX queues during interface
-	reset/reconfigure</li><li>Correct handling of 20&lt;-&gt;20/40mhz transitions (without
-	dropping frames)</li><li>More intelligent rate control</li></ol><hr /><h2><a name="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" id="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical
-      Evidence (DIFFUSE)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/diffused/" title="http://caia.swin.edu.au/freebsd/diffused/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/freebsd/diffused/" title="">http://caia.swin.edu.au/freebsd/diffused/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#diffuse" title="http://www.FreeBSDFoundation.org/project%20announcements.shtml#diffuse"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/project%20announcements.shtml#diffuse" title="">http://www.FreeBSDFoundation.org/project%20announcements.shtml#diffuse</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/" title="http://caia.swin.edu.au/urp/diffuse/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/" title="">http://caia.swin.edu.au/urp/diffuse/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="http://caia.swin.edu.au/urp/diffuse/downloads.html"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="">http://caia.swin.edu.au/urp/diffuse/downloads.html</a></td></tr></table><p>
-	Contact:
-	  Sebastian
-	  Zander
-	 &lt;<a href="mailto:szander@swin.edu.au">szander@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lastewart@swin.edu.au">lastewart@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	</p>
-      <p>DIFFUSE enables FreeBSD's IPFW firewall subsystem to classify IP
-	traffic based on statistical traffic properties.</p>
-
-      <p>With DIFFUSE, IPFW computes statistics (such as packet lengths
-	or inter-packet time intervals) for observed flows, and uses ML
-	(machine learning) to classify flows into classes.  In addition to
-	traditional packet inspection rules, IPFW rules may now also be
-	expressed in terms of traffic statistics or classes identified by
-	ML classification.  This can be helpful when direct packet
-	inspection is problematic (perhaps for administrative reasons, or
-	because port numbers do not reliably identify applications).</p>
-
-      <p>DIFFUSE also enables one instance of IPFW to send flow
-	information and classes to other IPFW instances, which then can act
-	on such traffic (e.g. prioritise, accept, deny, etc.) according to
-	its class.  This allows for distributed architectures, where
-	classification at one location in your network is used to control
-	fire-walling or rate-shaping actions at other locations.</p>
-
-      <p>The FreeBSD Foundation has funded the Centre for Advanced
-	Internet Architectures at Swinburne University of Technology to
-	undertake the DIFFUSED (DIFFUSE for freebsD) project, which aims to
-	refine our publicly released DIFFUSE prototype and integrate all
-	components of the architecture into FreeBSD.</p>
-
-      <p>The project is progressing well in the diffused_head project
-	branch of the FreeBSD Subversion repository, and is due to be
-	completed by the end of October 2011.  Once the project is
-	completed, the code will be merged from the project branch into the
-	head branch.  An MFC of the code to 8.x and 9.x should be possible
-	after an appropriate amount of soak time has elapsed.</p>
-    <hr /><h2><a name="Ethernet-Switch-Framework" href="#Ethernet-Switch-Framework" id="Ethernet-Switch-Framework">Ethernet Switch Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zrouter.org/hg/FreeBSD/head/file/default/head/sys/dev/switch" title="http://zrouter.org/hg/FreeBSD/head/file/default/head/sys/dev/switch">Code here.</a></td><td>
-	    URL: <a href="http://zrouter.org/hg/FreeBSD/head/file/default/head/sys/dev/switch" title="Code here.">http://zrouter.org/hg/FreeBSD/head/file/default/head/sys/dev/switch</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	</p>
-      <p>Many embedded devices have an Ethernet switch on board; such
-	switches are even embedded on some multiport NICs.  This
-	embedded switch framework is designed to give users the
-	ability to easily control basic features present in managed
-	switches, such as VLANs, QoS, port mirroring, etc.  Currently
-	we are able to control only VLANs on:</p>
-
-      <ul>
-	<li>Atheros AR8216/AR8316 (standalone and embedded in
-	  AR724X)</li>
-	<li>Broadcom BCM5325 switch family (also embedded in BCM5354
-	  SoC)</li>
-	<li>Ralink RT3050F/RT3052F internal switch</li>
-	<li>Realtek RTL8309</li>
-	<li>IP175X</li>
-	<li>IP178X</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Fix AR8216/AR8316 driver</li><li>Fix BCM5325 driver, not all ports pass data</li><li>Add tick handler for RTL8309 to automatically unisolate ports</li><li>Unify MIB statistic counters access</li><li>Add mii read/write bus methods</li><li>Implement pseudo interfaces for switch PHYs</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="The-new-CARP" href="#The-new-CARP" id="The-new-CARP">The new CARP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~glebius/newcarp/" title="http://people.FreeBSD.org/~glebius/newcarp/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~glebius/newcarp/" title="">http://people.FreeBSD.org/~glebius/newcarp/</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Smirnoff
-	 &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>I am now working on significant rewrite of CARP in FreeBSD.</p>
-
-      <p>The reason for this work is that the CARP protocol actually does
-	not bring a new interface, but is a property of interface address.
-	Rewriting it in this way helps to remove several hacks from
-	incoming packet processing, simplifies some code, makes CARP
-	addresses more sane from the viewpoint of routing daemons such as
-	quagga/zebra and closes many CARP-related PRs in GNATS.  It also
-	brings support for a single redundant address on the subnet, the
-	thing that is called "carpdev feature" in OpenBSD, long awaited in
-	FreeBSD.</p>
-
-      <p>For this moment I have a patch against head/ that compiles and
-	works in my test environment that I am going to deploy soon on some
-	of servers under my control.</p>
-
-      <p>The patch has been reviewed by Bjoern Zeeb (bz@).</p>
-    <h3>Open tasks:</h3><ol><li>More testing requested!</li><li>Implement arpbalance and ipbalance features.  This requires a
-	next step of rewriting, probably borrowing some ideas from
-	OpenBSD.</li><li>Update documentation.</li></ol><hr /><h2><a name="VM-layer-for-allocations-larger-than-a-page" href="#VM-layer-for-allocations-larger-than-a-page" id="VM-layer-for-allocations-larger-than-a-page">VM layer for allocations larger than a page</a></h2><p>
-	Contact:
-	  Alan
-	  Cox
-	 &lt;<a href="mailto:alc@FreeBSD.org">alc@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Davide
-	  Italiano
-	 &lt;<a href="mailto:davide.italiano@gmail.com">davide.italiano@gmail.com</a>&gt;
-	</p>
-      <p>The aim of this project is to create a new layer that sits
-	between UMA and the virtual memory system managing chunks of kernel
-	virtual memory on the order of 2 to 4 MB in size.  At the end of the
-	work, UMA page_alloc() would no longer call directly into the VM
-	system.  It would instead call into this new layer.  Thus,
-	uma_large_malloc() and uma_large_free() would no longer be
-	immediately allocating and deallocating kernel virtual memory.  This
-	results in a gain in terms of performances (there is a relatively
-	high cost in the approach adopted until now), and also in terms of
-	reduction of fragmentation (the VM system uses a first-fit policy of
-	allocation so there is room for improvements).</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Doc-sprint-on-IRC,-September-5,-2011" href="#Doc-sprint-on-IRC,-September-5,-2011" id="Doc-sprint-on-IRC,-September-5,-2011">Doc sprint on IRC, September 5, 2011</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bcr/doc/sprints/20110905-final.html" title="http://people.FreeBSD.org/~bcr/doc/sprints/20110905-final.html">Results and Notes written down during the sprint</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bcr/doc/sprints/20110905-final.html" title="Results and Notes written down during the sprint">http://people.FreeBSD.org/~bcr/doc/sprints/20110905-final.html</a></td></tr></table><p>
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Dru
-	  Lavigne
-	 &lt;<a href="mailto:dru@FreeBSD.org">dru@FreeBSD.org</a>&gt;
-	</p>
-      <p>On September 5, we held another documentation sprint on IRC
-	channel #bsddocs to discuss various issues that are important for
-	the whole FreeBSD documentation community.  We talked about the
-	status of the planned documentation repository conversion to SVN
-	and the status of the XML docbook conversion.  At that point in
-	time, we did not have any documentation regarding the new
-	bsdinstaller in the upcoming release, which would have been very
-	bad for users that were trying to install the release.  Luckily, a
-	small team formed quickly to start working on a new bsdinstall
-	chapter from scratch using a separate Google code repository that
-	gjb@ had set up.</p>
-
-      <p>Some of the topics we discussed were moved forward and their
-	status was revisited at EuroBSDcon's devsummit documentation
-	session.  Before the end of the conference, we had a new bsdinstall
-	chapter committed into the official documentation tree, thanks to
-	the efforts put into the new chapter by Gavin Atkinson, Warren
-	Block, and Glen Barber.  Garrett Cooper provided valuable
-	instructions on the various installation methods that are possible
-	with the new bsdinstaller.  Thanks to all who helped make this a
-	reality.</p>
-
-      <p>It is nice to see that the things we talked about at the
-	documentation sprint developed further, which is why we are trying
-	to do these sprints in regular intervals.</p>
-    <h3>Open tasks:</h3><ol><li>Plan the next documentation sprint</li><li>Continue working on the issues that are still open like the
-	conversion of the repository to SVN</li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project-Status-Report" href="#The-FreeBSD-German-Documentation-Project-Status-Report" id="The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://doc.bsdgroup.de" title="https://doc.bsdgroup.de">Website of the FreeBSD German Documentation Project.</a></td><td>
-	    URL: <a href="https://doc.bsdgroup.de" title="Website of the FreeBSD German Documentation Project.">https://doc.bsdgroup.de</a></td></tr></table><p>
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>We managed to update the German version of the documentation
-	just in time to get it included in the upcoming 9.0-RELEASE.  The
-	website translations were also kept in sync with the ones on
-	FreeBSD.org.</p>
-
-      <p>We tried to re-activate committers who did not contribute for
-	some time but most of them are currently unable to free up enough
-	time.  We hope to gain fresh contributor blood as we are getting
-	occasional reports about bugs and grammar in the German
-	translation.</p>
-    <h3>Open tasks:</h3><ol><li>Submit grammar, spelling or other errors you find in the
-	German documents and the website</li><li>Translate more articles and other open handbook sections
-	(especially the new chapter about the new FreeBSD
-	installer).</li></ol><hr /><h2><a name="The-FreeBSD-Greek-Documentation-Project" href="#The-FreeBSD-Greek-Documentation-Project" id="The-FreeBSD-Greek-Documentation-Project">The FreeBSD Greek Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDgr.org" title="http://www.FreeBSDgr.org">The FreeBSD Greek Documentation Project</a></td><td>
-	    URL: <a href="http://www.FreeBSDgr.org" title="The FreeBSD Greek Documentation Project">http://www.FreeBSDgr.org</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/el/books/handbook" title="http://www.FreeBSD.org/doc/el/books/handbook">The FreeBSD Greek Handbook</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/el/books/handbook" title="The FreeBSD Greek Handbook">http://www.FreeBSD.org/doc/el/books/handbook</a></td></tr></table><p>
-	Contact:
-	  Manolis
-	  Kiagias
-	 &lt;<a href="mailto:manolis@FreeBSD.org">manolis@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Giorgos
-	  Keramidas
-	 &lt;<a href="mailto:keramida@FreeBSD.org">keramida@FreeBSD.org</a>&gt;
-	</p>
-      <p>After a few rather quiet months, the FreeBSD Greek Documentation
-	Project is back on track, translating and improving the Handbook,
-	FAQ and FreeBSD articles.  The new bsdinstall chapter has been
-	translated and is now present in the Handbook.  Our  <a href="http://www.FreeBSDgr.org/handbook" shape="rect">experimental Handbook
-	builds</a> are also available at the project's hub.  Three new
-	status pages have been added:</p>
-
-      <ul>
-	<li><a href="http://www.FreeBSDgr.org/versions.html" shape="rect">Merge Status for
-	  the en_US tree</a> shows whether the local en_US repo is in
-	  sync with the official CVS</li>
-
-	<li><a href="http://www.FreeBSDgr.org/versionsel.html" shape="rect">Merge Status
-	  for the el_GR tree</a> - as above but for the Greek
-	  tree</li>
-
-	<li><a href="http://www.FreeBSDgr.org/pending.html" shape="rect">Pending
-	  Commits</a> shows newer yet to be committed versions of the
-	  Greek docs</li>
-      </ul>
-
-      <p>For more information, please visit <a href="http://www.FreeBSDgr.org" shape="rect">http://www.freebsdgr.org</a>.
-	Patches, fixes and contributions are always welcome.</p>
-    <h3>Open tasks:</h3><ol><li>Translate the remaining chapters of the Handbook to
-	Greek.</li><li>Complete the translation of the FreeBSD FAQ.</li><li>Keep the currently translated docs in sync with the English
-	versions.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>The www/ja and doc/ja_JP.eucJP/books/handbook subtrees have
-	constantly been updated since the last report.</p>
-
-      <p>www/ja: During this period, many areas of outdated content in
-	the www/ja subtree were updated to the latest versions of the
-	English counterparts.  The Japanese version of the 8.2R release
-	announcement was added and the upcoming 9.0R announcement will be
-	translated in a timely manner.</p>
-
-      <p>Handbook: The Japanese "kernelconfig" section finally caught up with
-	the original English version.  The next targets are "cutting-edge"
-	and the new installer section.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work for outdated documents in both
-	doc/ja_JP.eucJP and www/ja.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm-on-Marvell-Armada-XP" href="#FreeBSD/arm-on-Marvell-Armada-XP" id="FreeBSD/arm-on-Marvell-Armada-XP">FreeBSD/arm on Marvell Armada XP</a></h2><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>Marvell Armada XP is a complete system-on-chip solution based on
-	the Sheeva embedded CPUs.  These devices integrate up to four ARMv6/v7
-	compliant Sheeva CPU cores with shared L2 cache.</p>
-
-      <p>This work is extending FreeBSD/arm infrastructure towards
-	support for recent ARM architecture variations along with a basic
-	set of device drivers for integrated peripherals.</p>
-
-      <p>The following code has been implemented since the last status
-	report:</p>
-
-      <ul>
-	<li>PCI-Express support</li>
-	<li>SMP support</li>
-	<ul>
-	  <li>Created framework for ARM platform dependent code.</li>
-	  <li>Initialization and starting of Application Processor.</li>
-	  <li>Implementation of sending/handling IPI</li>
-	</ul>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>Finalize SMP support (TLB/cache operation broadcast,
-	  etc.)</li>
-	<li>L2 cache support</li>
-	<li>SATA driver</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD/powerpc-on-AppliedMicro-APM86290" href="#FreeBSD/powerpc-on-AppliedMicro-APM86290" id="FreeBSD/powerpc-on-AppliedMicro-APM86290">FreeBSD/powerpc on AppliedMicro APM86290</a></h2><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The APM86290 system-on-chip device is a member of AppliedMicro's
-	PACKETpro family of embedded processors.</p>
-
-      <p>The chip includes two Power Architecture PPC465 processor cores,
-	which are compliant with the Book-E specification of the architecture,
-	and a number of integrated peripherals.</p>
-
-      <p>This work is extending current Book-E support in FreeBSD towards
-	PPC4xx processor variants along with device drivers for
-	integrated peripherials.</p>
-
-      <p>The following drivers have been created since the last report:</p>
-
-      <ul>
-	<li>Interrupt controller</li>
-	<li>EHCI USB driver attachment</li>
-	<li>Queue Manager/Traffic Manager support</li>
-	<li>Initial support of Ethernet controller</li>
-	<li>GPIO, I2C</li>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>Finalize Ethernet controller driver</li>
-	<li>L2 cache support</li>
-      </ul>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><p>
-	Contact:
-	  Gabor Janos
-	  PaLI
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>We updated existing ports to their latest versions and hunted down
-	a bug in the 9-CURRENT rtld which was causing GHC to crash
-	intermittently.  We also started work on Haskell Platform 2011.3.0.0
-	(development version) in a <a href="https://github.com/freebsd-haskell/freebsd-haskell/tree/haskell-platform-2011.3.0.0" shape="rect">
-	separate git branch in our development repository</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Test GHC to work with clang/LLVM.</li><li>Add an option to the GHC port to be able to build it with already
-	installed GHC instead of requiring a separate GHC boostrap
-	tarball.</li><li>Update Haskell Platform (along with GHC) to 2011.4.0.0 as
-	soon as it gets out.</li><li>Add more ports to the Ports collection.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.KDE.org" title="http://FreeBSD.KDE.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.KDE.org" title="KDE/FreeBSD home page">http://FreeBSD.KDE.org</a></td></tr><tr><td><a href="http://FreeBSD.KDE.org/area51.php" title="http://FreeBSD.KDE.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.KDE.org/area51.php" title="area51">http://FreeBSD.KDE.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde-freebsd@KDE.org">kde-freebsd@KDE.org</a>&gt;
-	</p>
-      <p>The KDE/FreeBSD team has continued to improve the experience
-	of KDE software and Qt under FreeBSD.  The latest round of
-	improvements include:</p>
-
-      <ul>
-	<li>Splitting some of the KDE modules into smaller ports</li>
-	<li>Reduced startup time by ~15 seconds</li>
-	<li>Allowed auto-login out-of-the-box</li>
-	<li>Kopete supports GoogleTalk</li>
-	<li>Kalzium installs with its molecular editor</li>
-	<li>Zeitgeist support added</li>
-	<li>Porting Calligra to FreeBSD (work-in-progress)</li>
-      </ul>
-
-      <p>The team has also made many releases and upstreamed many fixes
-	and patches.  The latest round of releases include:</p>
-
-      <ul>
-	<li>Qt: 4.7.4</li>
-	<li>PyQt: 4.8.5 (SIP: 4.12.4)</li>
-	<li>KDE SC: 4.7.2</li>
-	<li>Amarok: 2.4.3</li>
-	<li>KDevelop: 4.2.3 (KDevPlatform: 1.2.3)</li>
-      </ul>
-
-      <p>The team is always looking for more testers and porters so
-	please contact us at kde-freebsd@KDE.org and visit our home page at
-	<a href="http://FreeBSD.KDE.org/" shape="rect">http://FreeBSD.KDE.org</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Testing KDE PIM 4.7.2</li><li>Testing phonon-gstreamer and phonon-vlc as the phonon-xine
-	backend was deprecated (and will remain in ports)</li></ol><hr /><h2><a name="OpenAFS-port" href="#OpenAFS-port" id="OpenAFS-port">OpenAFS port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openafs.org" title="http://openafs.org">OpenAFS home page</a></td><td>
-	    URL: <a href="http://openafs.org" title="OpenAFS home page">http://openafs.org</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/afs" title="http://wiki.FreeBSD.org/afs">FreeBSD Wiki on AFS</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/afs" title="FreeBSD Wiki on AFS">http://wiki.FreeBSD.org/afs</a></td></tr></table><p>
-	Contact:
-	  Benjamin
-	  Kaduk
-	 &lt;<a href="mailto:kaduk@mit.edu">kaduk@mit.edu</a>&gt;
-	<br />
-	Contact:
-	  Derrick
-	  Brashear
-	 &lt;<a href="mailto:shadow@gmail.com">shadow@gmail.com</a>&gt;
-	</p>
-      <p>AFS is a distributed network filesystem that originated from the
-	Andrew Project at Carnegie-Mellon University.  OpenAFS 1.6.0 has
-	been released, and is available in the FreeBSD Ports Collection; it is
-	usable under light load, but heavy usage reveals some issues that
-	remain unresolved.  The OpenAFS kernel module is now built using the
-	bsd.kmod.mk infrastructure on the git master branch; unfortunately
-	this change required a minor change in the OS-independent Makefiles
-	and could not be merged in time for 1.6.0.  Some attention has been
-	given to memory leaks, but only one small leak has been patched so
-	far.</p>
-
-      <p>There are several known outstanding issues that are being worked
-	on, but detailed bug reports are welcome at
-	port-freebsd@openafs.org.</p>
-    <h3>Open tasks:</h3><ol><li>Update VFS locking to allow the use of disk-based client
-	caches as well as memory-based caches.</li><li>Track down races and deadlocks that may appear under
-	load.</li><li>Eliminate a moderate memory leak from the kernel
-	module.</li><li>PAG (Process Authentication Group) support is not
-	functional.</li></ol><hr /><h2><a name="Portmaster" href="#Portmaster" id="Portmaster">Portmaster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster-proposal.html" title="http://dougbarton.us/portmaster-proposal.html"></a></td><td>
-	    URL: <a href="http://dougbarton.us/portmaster-proposal.html" title="">http://dougbarton.us/portmaster-proposal.html</a></td></tr></table><p>
-	Contact:
-	  Doug
-	  Barton
-	 &lt;<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Portmaster offers several new features since the last quarterly
-	update; some bug fixes for the package installation code, and
-	various internal optimizations.  The most exciting new feature is
-	probably the ability to specify the -r option more than once for
-	the same portmaster run.  This greatly increases efficiency when
-	several "branch" and/or "trunk" ports need updates at the same
-	time, especially for package-building systems.</p>
-    <h3>Open tasks:</h3><ol><li>Splitting out the fetch code is still "on the list" of work
-	to be done, but it was sidetracked by other priorities in the past
-	months.  I hope to complete it in the quarter to come.</li><li>Another new feature in the works is support for a list of
-	files for portmaster to preserve and restore during upgrades of a
-	port.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="bsd_day(2011)" href="#bsd_day(2011)" id="bsd_day(2011)">bsd_day(2011)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bsdday.eu/2011" title="http://bsdday.eu/2011">Home page of bsd_day(2011)</a></td><td>
-	    URL: <a href="http://bsdday.eu/2011" title="Home page of bsd_day(2011)">http://bsdday.eu/2011</a></td></tr></table><p>
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Gabor
-	  Pali
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The purpose of this one-day event was to gather Central European
-	developers of today's open-source BSD systems to popularize their
-	work and their organizations, and to meet each other in the real
-	life.  We wanted to motivate potential future developers
-	and users, especially undergraduate university students, to work
-	with BSD systems.</p>
-
-      <p>This year's BSD-Day was held in Bratislava, Slovakia at the
-	Slovak University of Technology, Faculty of Electrical Engineering
-	and Information Technology on November 5, 2011.</p>
-    <hr /><h2><a name="EuroBSDcon-2011" href="#EuroBSDcon-2011" id="EuroBSDcon-2011">EuroBSDcon 2011</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2011.eurobsdcon.org/" title="http://2011.eurobsdcon.org/">EuroBSDcon 2011 web site</a></td><td>
-	    URL: <a href="http://2011.eurobsdcon.org/" title="EuroBSDcon 2011 web site">http://2011.eurobsdcon.org/</a></td></tr></table><p>
-	Contact:
-	  EuroBSDcon
-	  Organizers
-	 &lt;<a href="mailto:oc-2011@eurobsdcon.org">oc-2011@eurobsdcon.org</a>&gt;
-	<br />
-	Contact:
-	  Gabor
-	  Pali
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The 10th anniversary European BSD Conference was organized in
-	Maarssen, The Netherlands with more than 250 registered visitors.
-	There were many interesting tutorials, including introductions to
-	DTrace and working with Netgraph.  It featured 26 high-quality talks
-	and 2 keynote speakers on various topics related to FreeBSD,
-	OpenBSD, NetBSD, or even MINIX: OpenBSD PF, NetBSD NPF, IPv6
-	support in FreeBSD, virtualization in the BSD domain, recent
-	developments in OpenSSH, exploration of the recent FreeNAS, system
-	management with ZFS, practical capabilities for UNIX known as
-	Capsicum.</p>
-
-      <p>It also had a dedicated track for the attendees of the FreeBSD
-	developer summit, where one could learn more about what is
-	happening currently in the Project.  We had presentations on the new
-	package management solution, Google Summer of Code 2011, a stacked
-	cryptographic file system, conversion of documents of different
-	formats, and status reports on the sparc64 port and the NAND flash
-	support.</p>
-    <hr /><h2><a name="FreeBSD-Developer-Summit,-Maarssen" href="#FreeBSD-Developer-Summit,-Maarssen" id="FreeBSD-Developer-Summit,-Maarssen">FreeBSD Developer Summit, Maarssen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/201110DevSummit" title="http://wiki.FreeBSD.org/201110DevSummit">Home page of the summit</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/201110DevSummit" title="Home page of the summit">http://wiki.FreeBSD.org/201110DevSummit</a></td></tr></table><p>
-	Contact:
-	  Gabor
-	  Pali
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We had 60 FreeBSD developers and invited guests attending the
-	FreeBSD Developer Summit organized as part of EuroBSDcon 2011 in
-	Maarssen, The Netherlands.  This year EuroBSDcon organizers offered
-	us their generous support in handling the details, like
-	registrations, renting the venue, and providing food for keeping
-	attendees happy.</p>
-
-      <p>The Maarssen developer summit spanned over 3 days.  It is
-	generally a workshop-style event that has now adopted the layout of
-	the developer summit organized successfully in Canada earlier in
-	May.  On the first day, there were working groups on various topics,
-	e.g. Capsicum, toolchain issues, ports, and documentation.  On the
-	second day, there were various plenary discussions, like how
-	FreeBSD relates to virtualization or how vendors relate to FreeBSD.
-	Finally, on the third day, there were many interesting
-	work-in-progress reports given in a dedicated developer summit
-	track at the main conference.</p>
-
-      <p>Photos and slides for the most of the talks are available on the
-	home page of the summit.</p>
-    <hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Multibyte-Encoding-Support-in-Nvi" href="#Multibyte-Encoding-Support-in-Nvi" id="Multibyte-Encoding-Support-in-Nvi">Multibyte Encoding Support in Nvi</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/ZhihaoSoC2011" title="http://wiki.FreeBSD.org/ZhihaoSoC2011">FreeBSD Wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/ZhihaoSoC2011" title="FreeBSD Wiki">http://wiki.FreeBSD.org/ZhihaoSoC2011</a></td></tr><tr><td><a href="https://github.com/lichray/nvi2" title="https://github.com/lichray/nvi2">Github page</a></td><td>
-	    URL: <a href="https://github.com/lichray/nvi2" title="Github page">https://github.com/lichray/nvi2</a></td></tr></table><p>
-	Contact:
-	  Zhihao
-	  Yuan
-	 &lt;<a href="mailto:lichray@gmail.com">lichray@gmail.com</a>&gt;
-	</p>
-      <p>nvi-iconv keeps the behaviors and the license of nvi-1.79 in the
-	base system and adopts the multibyte encoding support from
-	nvi-1.8x.</p>
-
-      <p>Status:</p>
-
-      <ul>
-	<li>Known memory leaks, bugs are fixed.  make buildworld clear,
-	  under WARNS=1 (the old one was WARNS=0).</li>
-	<li>UTF-16 is supported with less hacks.</li>
-	<li>The 'windowname' option now restores the xterm title through
-	  xprop.</li>
-	<li>The file encoding detection modified from file(1) is finished
-	  and considered stable.  The detection is always on as nvi-iconv
-	  never changes the actual encoding, and the detection falls back to
-	  locale.</li>
-	<li>Pavel Timofeev provided a full Russian translation of the
-	  catalog.  Thanks to him.</li>
-	<li>Now nvi-iconv is able to be compiled with widechar only and
-	  without iconv (inspired by a user on FreeBSDChina.org).  In
-	  that case, it only supports your locale.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>The wide character support in nvi's message (feedback over
-	the last line) system.</li><li>Collect more testing results and get code review.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2011-10-2011-12.html b/website/content/en/status/report-2011-10-2011-12.html
deleted file mode 100644
index 1f0a979f5b..0000000000
--- a/website/content/en/status/report-2011-10-2011-12.html
+++ /dev/null
@@ -1,1431 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between October and
-      December 2011.  It is the last of the four reports planned for 2011.
-      This quarter was mainly devoted to polishing the bits for the next
-      major version of FreeBSD, 9.0, which was already successfully released in
-      the beginning of January 2012.</p><p>Thanks to all the reporters for the excellent work! This report
-      contains 32 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between January and March 2012 is April 15th, 2012.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Auditdistd-Project">Auditdistd Project</a></li><li><a href="#BSD-Licensed-C++-Stack">BSD-Licensed C++ Stack</a></li><li><a href="#pfSense">pfSense</a></li></ul><h3><a href="#User-land-Programs">User-land Programs</a></h3><ul><li><a href="#Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></li><li><a href="#System-Configuration-Utilities">System Configuration Utilities</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Ports-Management-Team-Status-Report">FreeBSD Ports Management Team Status Report</a></li><li><a href="#Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#CAM-Target-Layer-(CTL)">CAM Target Layer (CTL)</a></li><li><a href="#FreeBSD-No-IPv4-(&quot;IPv6-Only&quot;)-Support">FreeBSD No-IPv4 ("IPv6-Only") Support</a></li><li><a href="#GEOM-MULTIPATH-Rewrite">GEOM MULTIPATH Rewrite</a></li><li><a href="#HDA-Sound-Driver-(snd_hda)-Improvements">HDA Sound Driver (snd_hda) Improvements</a></li><li><a href="#LSI-Supported-mps(4)-SAS-driver">LSI Supported mps(4) SAS driver</a></li><li><a href="#SCSI-Direct-Access-Driver-(da)-Improvements">SCSI Direct Access Driver (da) Improvements</a></li><li><a href="#Status-Report-for-NFS">Status Report for NFS</a></li><li><a href="#The-New-CARP">The New CARP</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#A-Tool-to-Check-for-Mistakes-in-Documentation-&#8212;-igor">A Tool to Check for Mistakes in Documentation &#8212; igor</a></li><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/390">FreeBSD/390</a></li><li><a href="#FreeBSD/arm-on-Marvell-Armada-XP">FreeBSD/arm on Marvell Armada XP</a></li><li><a href="#FreeBSD/powerpc-on-AppliedMicro-APM86290">FreeBSD/powerpc on AppliedMicro APM86290</a></li><li><a href="#FreeBSD/powerpc-on-Freescale-QorIQ-DPAA">FreeBSD/powerpc on Freescale QorIQ DPAA</a></li><li><a href="#Improving-Support-for-New-Features-in-the-Intel-SandyBridge-CPUs">Improving Support for New Features in the Intel SandyBridge CPUs</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#FreeBSD-Ruby-Ports">FreeBSD Ruby Ports</a></li><li><a href="#FreeBSD/GNOME">FreeBSD/GNOME</a></li><li><a href="#FreeBSD/KDE">FreeBSD/KDE</a></li><li><a href="#Multimedia-&#8212;-Watching/Recording-Digital-TV">Multimedia &#8212; Watching/Recording Digital TV</a></li><li><a href="#Perl-Ports-Testing">Perl Ports Testing</a></li><li><a href="#Public-FreeBSD-Ports-Development-Infrastructure-&#8212;-redports.org">Public FreeBSD Ports Development Infrastructure &#8212;
-      redports.org</a></li><li><a href="#Up-to-Date-X.Org-Server">Up to Date X.Org Server</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Auditdistd-Project" href="#Auditdistd-Project" id="Auditdistd-Project">Auditdistd Project</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Current weakness of FreeBSD's Security Event Audit facility is that
-	audit records are stored locally and can be modified or removed by
-	an attacker after a system compromise.</p>
-
-      <p>The auditdistd will allow to reliably and securely distribute
-	audit trail files over TCP/IP network to remote system.  In case of
-	system compromise it will enable administrators to analyze audit
-	records in trusted environment.</p>
-
-      <p>This project is sponsored by the FreeBSD Foundation and should be
-	completed by the end of February 2012.</p>
-    <hr /><h2><a name="BSD-Licensed-C++-Stack" href="#BSD-Licensed-C++-Stack" id="BSD-Licensed-C++-Stack">BSD-Licensed C++ Stack</a></h2><p>
-	Contact:
-	  David
-	  Chisnall
-	 &lt;<a href="mailto:theraven@FreeBSD.org">theraven@FreeBSD.org</a>&gt;
-	</p>
-      <p>Two new libraries, libc++ (providing a C++11 STL implementation)
-	and libcxxrt (providing an implementation of the C++ ABI
-	specification) have been added.  This is enabled by adding
-	WITH_LIBCPLUSPLUS=yes to src.conf.  It is not enabled by default
-	because libc++ does not build with the version of gcc in the base
-	system and requires you to build with clang.</p>
-
-      <p>Once it is built, you can select between using GNU libstdc++ and
-	libc++ by adding -stdlib=libc++ or -stdlib=libstdc++ to your
-	compile and link flags (when building with clang).</p>
-
-      <p>If you are running head (or have a spare [virtual] machine you
-	can try it on) then please try building your C++ code with libc++
-	and let me know of any failures, ideally with reduced test
-	cases.</p>
-    <h3>Open tasks:</h3><ol><li>Test ports with libc++.  Hopefully most will Just Work., but
-	others may need patches or have a hard dependency on
-	libstdc++.</li><li>Make libstdc++ dynamically link to libsupc++.  This will allow
-	us to use libmap.conf to switch between libsupc++ and
-	libcxxrt.</li><li>Enable building libc++ by default (hopefully in the 9.1
-	time-frame, when clang becomes the default system compiler) and
-	switch to using libcxxrt instead of libsupc++ by default.</li><li>Lots more testing.  Followed by even more testing.</li><li>Removing libstdc++ from the base system and making it
-	available through ports for backwards compatibility.</li></ol><hr /><h2><a name="pfSense" href="#pfSense" id="pfSense">pfSense</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pfsense.org/" title="http://www.pfsense.org/">pfSense homepage</a></td><td>
-	    URL: <a href="http://www.pfsense.org/" title="pfSense homepage">http://www.pfsense.org/</a></td></tr></table><p>
-	Contact:
-	  Scott
-	  Ullrich
-	 &lt;<a href="mailto:sullrich@gmail.com">sullrich@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Chris
-	  Buechler
-	 &lt;<a href="mailto:cbuechler@gmail.com">cbuechler@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Ermal
-	  Lu�i
-	 &lt;<a href="mailto:ermal.luci@gmail.com">ermal.luci@gmail.com</a>&gt;
-	</p>
-      <p>pfSense is a free and open source customized distribution of
-	FreeBSD tailored for use as a firewall and router.</p>
-
-      <p>2.0.1 was just released which corrected a number of issues
-	<a href="http://blog.pfsense.org/?p=633" shape="rect">
-	  http://blog.pfsense.org/?p=633</a>.</p>
-    <h3>Open tasks:</h3><ol><li>6 month release cycle.</li><li>Moving builds to FreeBSD 9.</li><li>Full IPV6 support.</li><li>PBI Package binaries.</li><li>Unbound integration.</li><li>Multi-instance Captive Portal.</li><li>Replacing Prototype with jQuery.</li></ol><hr /><br /><h1><a name="User-land-Programs" href="#User-land-Programs" id="User-land-Programs">User-land Programs</a></h1><br /><h2><a name="Replacing-the-Regular-Expression-Code" href="#Replacing-the-Regular-Expression-Code" id="Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/" title="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/">Project repo</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/" title="Project repo">http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/</a></td></tr><tr><td><a href="http://laurikari.net/tre/" title="http://laurikari.net/tre/">TRE homepage</a></td><td>
-	    URL: <a href="http://laurikari.net/tre/" title="TRE homepage">http://laurikari.net/tre/</a></td></tr><tr><td><a href="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf" title="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf">A paper on the topic</a></td><td>
-	    URL: <a href="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf" title="A paper on the topic">http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The current regular expression code in libc has to be replaced
-	because it is old, unmaintained and does not support wide
-	characters.  As it has been elaborated, TRE is the most suitable
-	replacement outside that has an acceptable license.  However, the
-	development of BSD grep also brought some relevant observations.  In
-	short, there are some possibilities to optimize pattern matching
-	but it is not possible with the POSIX API, because:</p>
-
-      <ul>
-	<li>It uses NUL-terminated strings that requires processing each
-	  character and makes longer jumps impossible.</li>
-
-	<li>It matches for one pattern at a time.  If more patterns are
-	  searched, there are more efficient ways for pattern matching but
-	  we have to know all of them and process them together.</li>
-      </ul>
-
-      <p>This project intends to implement these shortcut and provide
-	efficient pattern matching for all programs that use regex
-	matching.  It will also help avoiding the custom tricks that are
-	hardcoded into some programs, like GNU grep, to work around the
-	limiting POSIX API.  Besides, GNU grep has some extensions over the
-	POSIX regular expression, which are necessary if we want to get rid
-	of GNU code in the end.</p>
-    <h3>Open tasks:</h3><ol><li>Implement multi-pattern heuristic regex matching.</li><li>Implement GNU-specific regex extensions.</li><li>Adapt BSD grep to use the multi-pattern interface.</li><li>Test standard-compliance and correct behavior.</li></ol><hr /><h2><a name="System-Configuration-Utilities" href="#System-Configuration-Utilities" id="System-Configuration-Utilities">System Configuration Utilities</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://druidbsd.sourceforge.net/" title="http://druidbsd.sourceforge.net/">The DruidBSD Project</a></td><td>
-	    URL: <a href="http://druidbsd.sourceforge.net/" title="The DruidBSD Project">http://druidbsd.sourceforge.net/</a></td></tr></table><p>
-	Contact:
-	  Devin
-	  Teske
-	 &lt;<a href="mailto:dteske@vicor.com">dteske@vicor.com</a>&gt;
-	</p>
-      <p>On December 31st, 2011 sysutils/sysrc was added to the
-	ports-tree.  On January 6th, 2012 sysutils/host-setup was added to
-	the ports-tree.  Still pending is the addition of
-	sysutils/tzdialog.</p>
-
-      <p>Together or separately, these utilities try to make configuring
-	the system easier and more efficient.</p>
-
-      <p>sysrc(8) allows you to safely modify rc.conf(5) without fear or
-	trepidation; making remote-management and scripted changes a simple
-	transaction.  Also useful in managing puppet installations.</p>
-
-      <p>host-setup(8) allows you to configure your time zone, hostname,
-	network interfaces, default router/gateway, DNS nameservers in
-	resolv.conf(5) all via dialog(1) (or Xdialog(1)) interface.
-	Designed to replace sysinstall(8), host-setup is written entirely
-	in sh(1) and is completely stand-alone.</p>
-
-      <p>tzdialog(8) is an ISO-3166 compatible sh(1) rewrite of
-	tzsetup(8).  It is designed to be a drop-in replacement for tzsetup.
-	The major difference between the two is tzdialog(8) adds supports
-	for graphical user interface via Xdialog(1) (by passing the `-X'
-	argument), whereas tzsetup(8) only supports console-based
-	interaction.</p>
-    <h3>Open tasks:</h3><ol><li>Write a man-page for tzdialog(8).</li><li>Submit current tzdialog(8) version (1.1) and yet-to-be
-	completed man-page to ports-tree as sysutils/tzdialog.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Ports-Management-Team-Status-Report" href="#FreeBSD-Ports-Management-Team-Status-Report" id="FreeBSD-Ports-Management-Team-Status-Report">FreeBSD Ports Management Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td>
-	    URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree finally surpassed 23,000 ports.  The PR count
-	still remains at about 1100.</p>
-
-      <p>In Q4 we added 4 new committers, took in 4 commit bit for safe
-	keeping, and had one committer return to ports work.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports updates.
-	Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>KDE4 and cmake updates</li>
-
-	<li>Multiple runs to test and fix breakages induced by the bump
-	in digits for FreeBSD 10</li>
-
-	<li>Verify the removal of X11BASE from ports</li>
-
-	<li>Test ports after import of flex and m4 into src base</li>
-
-	<li>Optimizations to bsd.ports.mk</li>
-
-	<li>Test xcb update and split into multiple ports</li>
-
-	<li>Estimate number of ports utilizing old interface ioctls</li>
-
-	<li>Ongoing validation of infrastructure with pkgng</li>
-
-	<li>testing ports with clang as default compiler</li>
-      </ul>
-
-      <p>pkgng now has real safe binary upgrade, as well as real
-	integrity checking, work has been started to have the ports tree
-	be able to bootstrap pkgng.  More info on the <a href="http://lists.FreeBSD.org/pipermail/freebsd-ports/2011-November/071631.html" shape="rect">
-	  CFT email.</a>.</p>
-
-      <p>The pointyhat-west build machine continues toward production
-	use, code updates have made it more versatile such as swapping out
-	information in make.conf for build slaves, assist in testing of
-	pkgng -exp runs and to properly build linux_base ports.</p>
-
-      <p>It has been decided that the ports tree will be migrated from
-	CVS to Subversion, beat@ will be in charge of the project.  More
-	information on the <a href="http://wiki.FreeBSD.org/PortsSVN" shape="rect">wiki</a>.</p>
-
-      <p>A moderated mailing list has been created for ports related
-	announcements, <a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports-announce" shape="rect">
-	  http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports-announce</a>,
-	it is intended, but not limited, to be a means of communicating
-	portmgr@ announcements, Calls for Testing, plus other relevant
-	information to be used by our committers and ports maintainer
-	community.</p>
-    <h3>Open tasks:</h3><ol><li>Looking for help getting <a href="http://wiki.FreeBSD.org/PortsAndClang" shape="rect">ports to build
-	  with clang</a>.</li><li>Looking for help fixing <a href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent" shape="rect">ports broken
-	  on CURRENT</a>.  (List needs updating, too)</li><li>Looking for help with <a href="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures" shape="rect">
-	  Tier-2 architectures</a>.</li><li><a href="http://wiki.FreeBSD.org/PortsBrokenBySrcChanges" shape="rect">ports
-	  broken by src changes</a>.</li><li><a href="http://wiki.FreeBSD.org/PortsFailingOnPointyhat" shape="rect">ports
-	  failing on pointyhat</a>.</li><li><a href="http://wiki.FreeBSD.org/PortsFailingOnPointyhatWest" shape="rect">ports
-	  failing on pointyhat-west</a>.</li><li><a href="http://wiki.FreeBSD.org/Trybroken" shape="rect">ports that are marked
-	  as BROKEN</a>.</li><li><a href="http://wiki.FreeBSD.org/WhenDidThatPortBreak" shape="rect">When did
-	  that port break</a>.</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing and closing.</li></ol><hr /><h2><a name="Release-Engineering-Team-Status-Report" href="#Release-Engineering-Team-Status-Report" id="Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Release Engineering Team was pleased to announce the release
-	of FreeBSD-9.0 on January 12th, 2012.  To acknowledge his incredible
-	contributions to the world of computing and in particular the FreeBSD
-	Project's corner of that world FreeBSD-9.0 was dedicated to Dennis
-	Ritchie.  May he rest in peace.  The Release Engineering Team also
-	wishes to thank the FreeBSD Developers and Community for all the work
-	they put into the release.</p>
-
-      <p>With the FreeBSD-9.0 release cycle completed our focus shifts to
-	preparing for the FreeBSD-8.3 release.  A schedule has not been set but
-	we expect to be shooting for release some time in March 2012.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="www.FreeBSDFoundation.org" title="www.FreeBSDFoundation.org"></a></td><td>
-	    URL: <a href="www.FreeBSDFoundation.org" title="">www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The most exciting news to report is that we raised $426,000
-	through our fundraising efforts.  We were overwhelmed by the
-	generosity of the FreeBSD community.  We would like to thank everyone
-	who made a contribution to FreeBSD by either making a financial
-	donation to the foundation or volunteering on the Project.</p>
-
-      <p>We published our <a href="http://www.FreeBSDFoundation.org/press/2011Dec-newsletter.shtml" shape="rect">
-	  semi-annual newsletter</a> in December.  If you have not
-	already done so, please take a moment to read this publication
-	to find out how we supported the FreeBSD Project and community
-	during the second half of 2011.  There are also two great
-	testimonials in the newsletter from TaxiMagic and the Apache
-	Software Foundation.</p>
-
-      <p>The Foundation sponsored EuroBSDCon 2011 which was held in The
-	Netherlands, October 6-9.  And, we sponsored six developers to
-	attend the conference.  We sponsored the Bay Area Vendor Summit in
-	November.  We were represented at LISA '11, Dec 7-8 in Boston
-	MA.</p>
-
-      <p>We are a proud sponsor of AsiaBSDCon 2012, which will be held in
-	Tokyo, Japan, March 22-25.</p>
-
-      <p>The Foundation funded project Feed-Forward Clock Synchronization
-	Algorithms Project by the University of Melbourne completed.  We
-	approved two new projects for 2012, they are analyzing the
-	performance of FreeBSD's IPv6 stack by Bjoern Zeeb, and implementing
-	auditdistd daemon by Pawel Jakub Dawidek</p>
-
-      <p>We purchased more servers and other hardware for the FreeBSD
-	co-location centers at Sentex, NYI, and ISC.</p>
-
-      <p>The work above, as well as many other tasks which we do for the
-	FreeBSD Project, could not be done without donations.  Please help us by
-	making a donation or asking your company to make a donation.  We
-	would be happy to send marketing literature to you or your company.
-	Find out how to make a donation at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">our donate
-	  page</a>.</p>
-
-      <p>Find out more up-to-date Foundation news by reading our <a href="http://FreeBSDFoundation.blogspot.com/" shape="rect">blog</a> and
-	<a href="http://www.facebook.com/FreeBSDFoundation" shape="rect">Facebook</a>
-	page.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="CAM-Target-Layer-(CTL)" href="#CAM-Target-Layer-(CTL)" id="CAM-Target-Layer-(CTL)">CAM Target Layer (CTL)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031007.html" title="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031007.html"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031007.html" title="">http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031007.html</a></td></tr></table><p>
-	Contact:
-	  Ken
-	  Merry
-	 &lt;<a href="mailto:ken@FreeBSD.org">ken@FreeBSD.org</a>&gt;
-	</p>
-      <p>The CAM Target Layer (CTL) is now in FreeBSD/head.</p>
-
-      <p>CTL is a disk and processor device emulation subsystem originally
-	written for Copan Systems under Linux starting in 2003.  It
-	has been shipping in Copan (now SGI) products since 2005.</p>
-
-      <p>It was ported to FreeBSD in 2008, and thanks to an agreement
-	between SGI (who acquired Copan's assets in 2010) and Spectra
-	Logic in 2010, CTL is available under a BSD-style license.  The
-	intent behind the agreement was that Spectra would work to get
-	CTL into the FreeBSD tree.</p>
-
-      <p>It will likely be merged into the stable/9 tree in
-	mid-February.</p>
-
-      <p>Some CTL features:</p>
-
-      <ul>
-	<li>Disk and processor device emulation</li>
-	<li>Tagged queueing</li>
-	<li>SCSI task attribute support (ordered, head of queue,
-	  simple tags)</li>
-	<li>SCSI implicit command ordering support.  (e.g. if a read
-	  follows a mode select, the read will be blocked until the
-	  mode select completes.)</li>
-	<li>Full task management support (abort, LUN reset, target
-	  reset, etc.)</li>
-	<li>Support for multiple ports</li>
-	<li>Support for multiple simultaneous initiators</li>
-	<li>Support for multiple simultaneous backing stores</li>
-	<li>Persistent reservation support</li>
-	<li>Mode sense/select support</li>
-	<li>Error injection support</li>
-	<li>High Availability support (1)</li>
-	<li>All I/O handled in-kernel, no userland context switch
-	  overhead.</li>
-      </ul>
-
-      <p>(1) HA Support is just an API stub, and needs much more to be fully
-	functional.</p>
-
-      <p>For the basics on configuring and running CTL, see
-	src/sys/cam/ctl/README.ctl.txt in the FreeBSD/head source
-	tree.</p>
-    <hr /><h2><a name="FreeBSD-No-IPv4-(&quot;IPv6-Only&quot;)-Support" href="#FreeBSD-No-IPv4-(&quot;IPv6-Only&quot;)-Support" id="FreeBSD-No-IPv4-(&quot;IPv6-Only&quot;)-Support">FreeBSD No-IPv4 ("IPv6-Only") Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ipv6/ipv6only.html" title="http://www.FreeBSD.org/ipv6/ipv6only.html">FreeBSD No-IPv4 Support</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ipv6/ipv6only.html" title="FreeBSD No-IPv4 Support">http://www.FreeBSD.org/ipv6/ipv6only.html</a></td></tr></table><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The No-IPv4 (fka. "IPv6-Only") project initially
-	prototyped in p4 and merged into mainstream FreeBSD with support from
-	the FreeBSD Foundation and iXsystems earlier in 2011 for World IPv6
-	Day continued as a free time project.  Thanks to the help of an
-	anonymous source, dedicated i386 and amd64 build machines and a
-	distribution node were setup to allow continuous building of
-	snapshots and we hope to extend the support for the snapshots in
-	the future providing more services.</p>
-
-      <p>During the 9.0 release cycle a BETA and an RC snapshot were
-	built and released. FreeBSD 9.0-RELEASE will be the first official
-	release supporting a kernel to compile out IPv4 support.  We will
-	provide (and given 9.0 is out at time of writing do provide) a
-	no-IPv4 snapshot accompanying the official release and hope for
-	your feedback.</p>
-
-      <p>I would like to thank Hiroki Sato/allbsd.org for providing a mirror
-	in Japan for the Asian community in addition to mine in Europe.</p>
-    <h3>Open tasks:</h3><ol><li>Commit/Submit upstream a few user space fixes.</li><li>More user space cleanup and testing.</li><li>Get rid of <tt>gethostby*()</tt> calls.</li></ol><hr /><h2><a name="GEOM-MULTIPATH-Rewrite" href="#GEOM-MULTIPATH-Rewrite" id="GEOM-MULTIPATH-Rewrite">GEOM MULTIPATH Rewrite</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mav/gmultipath5.patch" title="http://people.FreeBSD.org/~mav/gmultipath5.patch">Patch committed into the HEAD.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mav/gmultipath5.patch" title="Patch committed into the HEAD.">http://people.FreeBSD.org/~mav/gmultipath5.patch</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>The GEOM MULTIPATH class underwent a major rewrite to fix many
-	problems and improve functionality, including:</p>
-
-      <ul>
-	<li>Improved locking and destruction process to fix crashes.</li>
-
-	<li>"Automatic" configuration method improved to make it safe by
-	  reading metadata back from all specified paths after writing to
-	  one.</li>
-
-	<li>"Manual" configuration method added to work without using
-	  on-disk metadata.  New "add" and "remove" commands allow to manage
-	  paths manually.</li>
-
-	<li>Failed paths are no longer dropped from GEOM, but only marked
-	  as failed and excluded from I/O operations.  Failed paths can be
-	  automatically restored when all other paths are lost or marked as
-	  failed, for example, because of device-caused (not transport)
-	  errors. "Fail" and "restore" commands added to manually control
-	  failure status.</li>
-
-	<li>Added Active/Active mode support.  Unlike the default
-	  Active/Passive mode, the load is evenly distributed between all
-	  working paths.  If supported by the device, it allows to
-	  significantly improve performance, utilizing bandwidth of all
-	  paths.  It is controlled by the -A option during creation.</li>
-
-	<li>Provider size check added to reduce chance of conflict with
-	  other GEOM classes.</li>
-
-	<li>GEOM is now destroyed on last provider disconnection.</li>
-
-	<li>`status` and `list` commands output was improved.</li>
-      </ul>
-
-      <p>These changes are now committed into the FreeBSD HEAD branch.  Merge
-	to 9-STABLE and 8-STABLE is planned after 9.0 release.</p>
-
-      <p>Project sponsored by iXsystems, Inc.</p>
-    <h3>Open tasks:</h3><ol><li>Implement some additional request ordering mechanism for the
-	Active/Active mode.  Some consumers in theory may not wait for
-	previous requests completion before submitting new overlapping or
-	dependent requests.  Those requests may be reordered on device if
-	run via different paths simultaneously.</li></ol><hr /><h2><a name="HDA-Sound-Driver-(snd_hda)-Improvements" href="#HDA-Sound-Driver-(snd_hda)-Improvements" id="HDA-Sound-Driver-(snd_hda)-Improvements">HDA Sound Driver (snd_hda) Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mav/hda.rewrite2.patch" title="http://people.FreeBSD.org/~mav/hda.rewrite2.patch">Latest patch</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~mav/hda.rewrite2.patch" title="Latest patch">http://people.FreeBSD.org/~mav/hda.rewrite2.patch</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>snd_hda(4) driver took major rewrite:</p>
-
-      <ul>
-	<li>Big old hdac driver was split into three independent pieces:
-	  HDA controller driver (hdac), HDA CODEC driver (hdacc) and HDA
-	  audio function driver (hdaa).  All drivers are completely
-	  independent and talk to each other only via NewBus interfaces.
-	  Using more NewBus bells and whistles allows to properly see HDA
-	  structure with standard system instruments, such as `devinfo -v`.
-	  Biggest driver file size now is 150K, instead of 240K before, and
-	  the code is much cleaner.</li>
-
-	<li>Support for multichannel recording was added.  While I have
-	  never seen it configured by default, UAA specification tells that
-	  it is possible.  Now, as specification defines, driver checks
-	  input associations for pins with sequence numbers 14 and 15, and
-	  if found (usually) &#8212; works as before, mixing signals together.
-	  If it does not, it configures input association as multichannel.
-	  I have found some CODECs doing strange things when configured for
-	  multichannel recording, but I have also found successfully working
-	  examples.</li>
-
-	<li>Signal tracer was improved to look for cases where several
-	  DACs/ADCs in CODEC can work with the same audio signal.  If such a
-	  case is found, the driver registers additional playback/record stream
-	  (channel) for the pcm device.  Having more than one stream allows
-	  to avoid vchans use and so avoid extra conversion to vchan's
-	  pre-configured sample rate and format.  Not many CODECs allow
-	  this, especially on playback, but some do.</li>
-
-	<li>New controller streams reservation mechanism was implemented.
-	  That allows to have more pcm devices than streams supported by
-	  the controller (usually 4 in each direction).  Now it limits only
-	  number of simultaneously transferred audio streams, that is
-	  rarely reachable and properly reported if happens.</li>
-
-	<li>Codec pins and GPIO signals configuration was exported via
-	  set of writable sysctls.  Another sysctl dev.hdaa.X.reconfig
-	  allows to trigger driver reconfiguration in run-time.  The only
-	  requirement is that all pcm devices should be closed at the
-	  moment, as they will be destroyed and recreated.  This should
-	  significantly simplify process of fixing CODEC configuration.  It
-	  should be possible now even to write GUI to do it with few mouse
-	  clicks.</li>
-
-	<li>Driver now decodes pins location and connector type names.  In
-	  some cases it gives a hint to the user where the connectors of
-	  the pcm device are located on the system case.  The number of
-	  channels supported by pcm device, reported now (if it is not 2),
-	  should also make finding them easier.</li>
-      </ul>
-
-      <p>The code is in testing now and should be soon committed to the
-	HEAD branch.</p>
-
-      <p>Project sponsored by iXsystems, Inc.</p>
-    <h3>Open tasks:</h3><ol><li>Closer inspection of HDMI/DisplayPort audio is
-	planned.</li><li>A number of hardware, mostly laptops, need workarounds to work
-	properly.  Some statistics should be collected to implement some of
-	them avoiding excessive code bloat.</li></ol><hr /><h2><a name="LSI-Supported-mps(4)-SAS-driver" href="#LSI-Supported-mps(4)-SAS-driver" id="LSI-Supported-mps(4)-SAS-driver">LSI Supported mps(4) SAS driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031358.html" title="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031358.html"></a></td><td>
-	    URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031358.html" title="">http://lists.FreeBSD.org/pipermail/freebsd-current/2012-January/031358.html</a></td></tr></table><p>
-	Contact:
-	  Ken
-	  Merry
-	 &lt;<a href="mailto:ken@FreeBSD.org">ken@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kashyap
-	  Desai
-	 &lt;<a href="mailto:Kashyap.Desai@lsi.com">Kashyap.Desai@lsi.com</a>&gt;
-	</p>
-      <p>The LSI-supported version of the mps(4) driver, that supports
-	their 6Gb SAS controllers and WarpDrive solid state drives, is
-	available in FreeBSD/head.</p>
-
-      <p>In addition to WarpDrive support, the driver also has several
-	other new features:</p>
-
-      <ul>
-	<li>Integrated RAID (IR) support</li>
-	<li>Improved error recovery code</li>
-	<li>Support for SCSI protection information (EEDP)</li>
-	<li>Support for TLR (Transport Level Retries), needed for tape
-	  drives</li>
-	<li>ioctl interface compatible with LSI utilities</li>
-      </ul>
-
-      <p>Thanks to LSI for doing the work on this driver, and the
-	testing.</p>
-
-      <p>I plan to merge it into stable/9 and stable/8 in early
-	February.</p>
-    <hr /><h2><a name="SCSI-Direct-Access-Driver-(da)-Improvements" href="#SCSI-Direct-Access-Driver-(da)-Improvements" id="SCSI-Direct-Access-Driver-(da)-Improvements">SCSI Direct Access Driver (da) Improvements</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>BIO_DELETE support (aka TRIM) was added to the CAM SCSI Direct
-	Access device driver (da).</p>
-
-      <p>Depending on device capabilities different methods are used to
-	implement it.  Currently used method can be read/set via
-	kern.cam.da.X.delete_method sysctls.  Possible values are:</p>
-
-      <ul>
-	<li>NONE - no provisioning support reported by the device;</li>
-
-	<li>DISABLE - provisioning support was disabled because of
-	  errors;</li>
-
-	<li>ZERO - use WRITE SAME (10) command to write zeroes;</li>
-
-	<li>WS10 - use WRITE SAME (10) command with UNMAP bit set;</li>
-
-	<li>WS16 - use WRITE SAME (16) command with UNMAP bit set;</li>
-
-	<li>UNMAP - use UNMAP command (equivalent of the ATA DSM TRIM
-	  command).</li>
-      </ul>
-
-      <p>The last two methods (UNMAP and WS16) are defined by SBC
-	specification and the UNMAP method is the most advanced one.  The
-	rest of the methods I have found supported in Linux, and as they
-	were trivial to implement, then why not? I hope they will be useful
-	in some cases.</p>
-
-      <p>As side product of fetching logical block provisioning support
-	flag, da driver also got support for reporting device physical
-	sector size (aka Advanced Format) via stripesize/stripeoffset GEOM
-	fields.  Some quirks were added for known 4K sector disks not
-	reporting it properly.</p>
-
-      <p>The code was committed to the HEAD branch and is going to be merged
-	to 8/9-STABLE after some time.</p>
-
-      <p>Project sponsored by iXsystems, Inc.</p>
-    <h3>Open tasks:</h3><ol><li>To implement more effective selection of the best delete
-	method some more parameters need to be obtained from the device.
-	Unluckily none of devices I have report them.</li></ol><hr /><h2><a name="Status-Report-for-NFS" href="#Status-Report-for-NFS" id="Status-Report-for-NFS">Status Report for NFS</a></h2><p>
-	Contact:
-	  Rick
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new NFS client and server are no longer considered
-	experimental and are the default for FreeBSD 9.0.  Included is fairly
-	complete support for NFSv4.0, as well as NFSv3 and NFSv2.  NFSv4.0
-	delegations are not enabled by default for the server, since there
-	is no handling of them for local system calls done on the server,
-	as yet.  So far, the transition seems to have gone alright, with only
-	a couple of obscure issues identified that did not get fixed
-	for FreeBSD 9.0.  Patches for these can be found at
-	<a href="http://people.FreeBSD.org/~rmacklem" shape="rect">
-	  http://people.FreeBSD.org/~rmacklem</a>
-      </p>
-
-      <p>Work is ongoing with respect to NFSv4.1 client support.  The
-	current code includes functioning support for the required
-	components, in particular, sessions for both fore and back
-	channels.  Development for the big optional component pNFS is in
-	progress and will hopefully be functional for the Files layout in a
-	few months.  The modified sources can be found at <a href="http://svn.FreeBSD.org/viewvc/base/projects/nfsv4.1-client" shape="rect">
-	  http://svn.FreeBSD.org/viewvc/base/projects/nfsv4.1-client</a>.</p>
-
-      <p>There is also a patch for what I call packrats, where threads
-	perform aggressive on-disk caching of delegated file in the NFSv4.0
-	client.  It currently seems to function OK, but does not yet have
-	client reboot recovery implemented, so it can only be used
-	experimentally at this time.  This patch can be found at <a href="http://people.FreeBSD.org/~rmacklem/packrat-patches" shape="rect">
-	  http://people.FreeBSD.org/~rmacklem/packrat-patches</a>.</p>
-    <hr /><h2><a name="The-New-CARP" href="#The-New-CARP" id="The-New-CARP">The New CARP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base?view=revision&amp;revision=228571" title="http://svnweb.FreeBSD.org/base?view=revision&amp;revision=228571">The main commit</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base?view=revision&amp;revision=228571" title="The main commit">http://svnweb.FreeBSD.org/base?view=revision&amp;revision=228571</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Smirnoff
-	 &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Bjoern
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  George
-	  Neville-Neil
-	 &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	</p>
-      <p>Significantly updated CARP protocol has been committed to head/.
-	I expect the new code to be easier to maintain and less buggy,
-	since it uses less hacks in the networking stack.</p>
-
-      <p>The new CARP does not bring a lot of new features, however here
-	is a couple:</p>
-
-      <ul>
-	<li>One can put a single redundant address on an interface.</li>
-
-	<li>Master/backup state can be switched via ifconfig.</li>
-
-	<li>Feature that demotes carp(4) during pfsync(4) update has been
-	  restored (it was lost in 7.0).</li>
-
-	<li>The overall ifconfig(8) output is now more readable, since
-	  addresses are exactly on the interfaces they are running.  Yes,
-	  this is feature, too :)</li>
-      </ul>
-
-      <p>The code has been developed by glebius@ with lots of help from
-	bz@.</p>
-    <h3>Open tasks:</h3><ol><li>Work on arpbalance/ipbalance features.  Since I do not utilize
-	them at all, first I need to find somebody eager to see these
-	features and willing to test patches.  Sponsoring work is also
-	appreciated.  glebius@ to handle.</li><li>Estimate whether we need to catch up with OpenBSD on putting
-	demotion counter into datagrams.  glebius@ to handle.</li><li>Update tcpdump(8) to enable nice printing of CARP packets.
-	gnn@ to handle.</li><li>Work with IANA to get an official protocol number.  gnn@ to
-	handle.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="A-Tool-to-Check-for-Mistakes-in-Documentation-&#8212;-igor" href="#A-Tool-to-Check-for-Mistakes-in-Documentation-&#8212;-igor" id="A-Tool-to-Check-for-Mistakes-in-Documentation-&#8212;-igor">A Tool to Check for Mistakes in Documentation &#8212; igor</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.wonkity.com/~wblock/igor/" title="http://www.wonkity.com/~wblock/igor/"></a></td><td>
-	    URL: <a href="http://www.wonkity.com/~wblock/igor/" title="">http://www.wonkity.com/~wblock/igor/</a></td></tr></table><p>
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>igor is a program that proofreads man pages, DocBook SGML
-	source, and other text files for many common mistakes.</p>
-
-      <p>Files are tested for spelling mistakes, repeated words, and
-	white-space problems.  Man pages are also checked for minimal
-	structure, and DocBook SGML source files are checked for formatting
-	and tag problems.</p>
-
-      <p>If you write or edit FreeBSD documentation, let igor help you check
-	it for correctness.</p>
-    <h3>Open tasks:</h3><ol><li>Find a testing or parsing framework that can do a faster or
-	better job, or that can understand the state of DocBook
-	tags.</li><li>Add more tests.</li><li>Improve speed.</li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://doc.bsdgroup.de/" title="https://doc.bsdgroup.de/">Homepage of the FreeBSD German Documentation Project</a></td><td>
-	    URL: <a href="https://doc.bsdgroup.de/" title="Homepage of the FreeBSD German Documentation Project">https://doc.bsdgroup.de/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/de_DE.ISO8859-1/books/handbook/bsdinstall.html" title="http://www.FreeBSD.org/doc/de_DE.ISO8859-1/books/handbook/bsdinstall.html">The German translation of the bsdinstall handbook chapter</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/de_DE.ISO8859-1/books/handbook/bsdinstall.html" title="The German translation of the bsdinstall handbook chapter">http://www.FreeBSD.org/doc/de_DE.ISO8859-1/books/handbook/bsdinstall.html</a></td></tr></table><p>
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	</p>
-      <p>The German Documentation Project is happy to report that two big
-	chapters have been translated in the past quarter.  The first update
-	is in the firewall chapter and covering the complete IPFW section.
-	It was contributed by Christopher J. Ruwe.  There were style and
-	language fixes to be done, but the biggest amount of work, the
-	actual translation, was done by him.  We thank Christopher very
-	much.</p>
-
-      <p>The other chapter that was translated is the new bsdinstall
-	chapter.  Benedict Reuschling did the work on this chapter.  He tried
-	to keep the same titles for sections that are mostly describing the
-	same things as in the sysinstall chapter (at least where this was
-	possible).</p>
-
-      <p>German speaking users are encouraged to read both chapters and
-	report typos or grammar errors back to us so we can fix them.</p>
-
-      <p>The German website is being updated on a regular basis.</p>
-    <h3>Open tasks:</h3><ol><li>Catch up with the latest changes made to the
-	documentation.</li><li>Translate more www pages into German.</li><li>Find bugs in the German documentation and fix them.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>During this period, many part of the outdated contents in the
-	www/ja subtree were updated to the latest versions in the English
-	counterpart.  The "bsdinstall" section in Handbook was newly
-	translated and the "cutting-edge" section is now
-	work-in-progress.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work for outdated documents in both
-	doc/ja_JP.eucJP and www/ja.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/390" href="#FreeBSD/390" id="FreeBSD/390">FreeBSD/390</a></h2><p>
-	Contact:
-	  Pau
-	  Amma
-	 &lt;<a href="mailto:fduuvrzv@yahoo.com">fduuvrzv@yahoo.com</a>&gt;
-	<br />
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>I wandered in and started working on FreeBSD/390 about 1 month ago
-	based on source Bjoern provided.  My short term goals are to sync it
-	with the current HEAD and write a minimal IPLabel loader, so we do
-	not have to depend on Hercules-only commands to test the kernel
-	boot process.</p>
-
-      <p>Then it will be time to make the crossbuild work again and get
-	the kernel booting.</p>
-    <hr /><h2><a name="FreeBSD/arm-on-Marvell-Armada-XP" href="#FreeBSD/arm-on-Marvell-Armada-XP" id="FreeBSD/arm-on-Marvell-Armada-XP">FreeBSD/arm on Marvell Armada XP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/projects/armv6/" title="http://svnweb.FreeBSD.org/base/projects/armv6/">ARMv6 branch</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/projects/armv6/" title="ARMv6 branch">http://svnweb.FreeBSD.org/base/projects/armv6/</a></td></tr></table><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>Marvell Armada XP is a complete system-on-chip solution based on
-	Sheeva embedded CPU.  These devices integrate up to four ARMv6/v7
-	compliant Sheeva CPU cores with shared L2 cache.</p>
-
-      <p>This work is extending the FreeBSD/arm infrastructure towards support
-	for recent ARM architecture variations along with a basic set of
-	device drivers for integrated peripherals.</p>
-
-      <p>The following code has been implemented since the last status
-	report:</p>
-
-      <ul>
-	<li>SMP support</li>
-
-	<ul>
-	  <li>Implemented TLB broadcast and RFO</li>
-
-	  <li>Tested 2 and 4 cores setup in WT cache mode</li>
-	</ul>
-
-	<li>SATA driver integrated and tested</li>
-
-	<li>CESA driver integrated and tested</li>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>L2 cache support</li>
-
-	<li>Full support for WB/WBA cache</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD/powerpc-on-AppliedMicro-APM86290" href="#FreeBSD/powerpc-on-AppliedMicro-APM86290" id="FreeBSD/powerpc-on-AppliedMicro-APM86290">FreeBSD/powerpc on AppliedMicro APM86290</a></h2><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The APM86290 system-on-chip device is a member of AppliedMicro's
-	PACKETpro family of embedded processors.</p>
-
-      <p>The chip includes two Power Architecture PPC465 processor cores,
-	which are compliant with Book-E specification of the architecture,
-	and a number of integrated peripherals.</p>
-
-      <p>This work is extending current Book-E support in FreeBSD towards
-	PPC4xx processors variation along with device drivers for
-	integrated peripherals.</p>
-
-      <p>The following drivers have been created since the last
-	report:</p>
-
-      <ul>
-	<li>Ethernet controller driver</li>
-
-	<li>Classifier driver</li>
-
-	<li>Finished Queue Manager/Traffic Manager</li>
-
-	<li>Improved performance and stability</li>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>L2 cache support</li>
-
-	<li>Merge APM86290 support to -CURRENT</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD/powerpc-on-Freescale-QorIQ-DPAA" href="#FreeBSD/powerpc-on-Freescale-QorIQ-DPAA" id="FreeBSD/powerpc-on-Freescale-QorIQ-DPAA">FreeBSD/powerpc on Freescale QorIQ DPAA</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040">P2041 product page</a></td><td>
-	    URL: <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040" title="P2041 product page">http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040</a></td></tr><tr><td><a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041">P3041 product page</a></td><td>
-	    URL: <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041" title="P3041 product page">http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041</a></td></tr><tr><td><a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020">P5020 product page</a></td><td>
-	    URL: <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020" title="P5020 product page">http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020</a></td></tr></table><p>
-	Contact:
-	  Michal
-	  Dubiel
-	 &lt;<a href="mailto:md@semihalf.com">md@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Piotr
-	  Ziecik
-	 &lt;<a href="mailto:kosmo@semihalf.com">kosmo@semihalf.com</a>&gt;
-	</p>
-      <p>The QorIQ Data Path Acceleration Architecture (DPAA) from
-	Freescale is a comprehensive architecture, which integrates all
-	aspects of packet processing in the SoC, addressing issues and
-	requirements resulting from the nature of QorIQ multicore SoCs.  It
-	includes:</p>
-
-      <ul>
-	<li>Cores</li>
-
-	<li>Network and packet I/O</li>
-
-	<li>Hardware offload accelerators</li>
-
-	<li>The infrastructure required to facilitate the flow of packets
-	  between the above</li>
-      </ul>
-
-      <p>The DPAA also addresses various performance related
-	requirements, especially those created by the high speed network
-	I/O found on multicore SoCs such as P2041, P3041, P5020, etc.  This
-	work is bringing up FreeBSD on these system-on-chip devices along with
-	device drivers for integrated peripherals.</p>
-
-      <p>Current FreeBSD QorIQ DPAA support includes:</p>
-
-      <ul>
-	<li>QorIQ P2041 and P3041 devices</li>
-
-	<li>E500mc core complex</li>
-
-	<li>Adaptation of toolchain for the new core</li>
-
-	<li>Booting via U-Boot bootloader</li>
-
-	<li>CoreNet interconnect fabric</li>
-
-	<li>L1, L2, L3 cache</li>
-
-	<li>Serial console (UART)</li>
-
-	<li>Interrupt controller</li>
-
-	<li>DPAA infrastructure (BMAN, FMAN, QMAN)</li>
-
-	<li>Ethernet (basic network functionality using Independent Mode
-	  of DPAA infrastructure)</li>
-
-	<li>EHCI controller</li>
-
-	<li>PCI Express controller (host mode)</li>
-
-	<li>SMP support (up to quad-core)</li>
-
-	<li>I2C</li>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>QorIQ P5020 (32-bit mode) support</li>
-
-	<li>Ethernet (full network functionality using Regular Mode of
-	  DPAA infrastructure)</li>
-
-	<li>Enhanced SDHC</li>
-      </ul>
-    <hr /><h2><a name="Improving-Support-for-New-Features-in-the-Intel-SandyBridge-CPUs" href="#Improving-Support-for-New-Features-in-the-Intel-SandyBridge-CPUs" id="Improving-Support-for-New-Features-in-the-Intel-SandyBridge-CPUs">Improving Support for New Features in the Intel SandyBridge CPUs</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for new features in the Intel SandyBridge CPUs is
-	progressing.</p>
-
-      <p>The patch to query and allow extended FPU states was committed,
-	which enabled the YMM registers and AVX instruction set on the
-	capable processors.  Todo items include get wider testing of the
-	change before planned merge to stable/9 in a month, and start
-	using XSAVEOPT instruction to optimize context switch times.</p>
-
-      <p>Patch to enable and use per-process TLB was developed.  Latest
-	version is available at <a href="http://people.freebsd.org/~kib/misc/pcid.2.patch" shape="rect">
-	  http://people.freebsd.org/~kib/misc/pcid.2.patch</a>.  The facility,
-	referred in the documentation as PCID, allows to avoid TLB flush
-	on context switches by applying PID tag to each non-global TLB
-	entry.  On SandyBridge, measurements did not prove any difference
-	between context switch latencies on patched and stock kernels.</p>
-
-      <p>Forthcoming IvyBridge CPUs promised to provide optimizations in
-	the form of INVPCID instructions that allow to optimize TLB
-	shootdown handlers. The patch above uses the instruction on the
-	capable CPU.  Todo items are to get access to IvyBridge and do the
-	benchmarks.</p>
-
-      <p>Future work might provide SEP support, use hardware random
-	generator from IvyBridge for random(4), considering using faster
-	instructions to access %fs and %gs bases, and use improved AES-NI
-	instruction set for aesni(4).</p>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Haskell" title="http://wiki.FreeBSD.org/Haskell">FreeBSD Haskell wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Haskell" title="FreeBSD Haskell wiki page">http://wiki.FreeBSD.org/Haskell</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="https://github.com/freebsd-haskell/freebsd-haskell/">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="FreeBSD Haskell ports repository">https://github.com/freebsd-haskell/freebsd-haskell/</a></td></tr><tr><td><a href="http://haskell.org/mailman/listinfo/freebsd-haskell/" title="http://haskell.org/mailman/listinfo/freebsd-haskell/">FreeBSD Haskell mailing list</a></td><td>
-	    URL: <a href="http://haskell.org/mailman/listinfo/freebsd-haskell/" title="FreeBSD Haskell mailing list">http://haskell.org/mailman/listinfo/freebsd-haskell/</a></td></tr></table><p>
-	Contact:
-	  G�bor J�nos
-	  P�LI
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce that the FreeBSD Haskell Team has updated
-	the Haskell Platform to 2011.4.0.0, as well as updated GHC to 7.0.4
-	in FreeBSD Haskell ports repository.  We also added a number of new
-	Haskell ports, and their count is now more than 300.  Some of the
-	new ports include Yesod, Happstack (popular web development
-	frameworks in Haskell), ThreadScope (a graphical profiler tool for
-	parallel Haskell programs).</p>
-
-      <p>Due to ports repository freeze for 9.0-RELEASE, these updates
-	are not in official ports tree yet.  They will be committed to the
-	ports repository after it is unfrozen again, in the meantime
-	they can be accessed through FreeBSD Haskell ports repository.</p>
-    <h3>Open tasks:</h3><ol><li>Commit pending Haskell ports to FreeBSD ports repository.</li><li>Test GHC to work with clang/LLVM.</li><li>Add an option to the <tt>lang/ghc</tt> port to be able to
-	build it with already installed GHC instead of requiring a
-	separate GHC bootstrap tarball.</li></ol><hr /><h2><a name="FreeBSD-Ruby-Ports" href="#FreeBSD-Ruby-Ports" id="FreeBSD-Ruby-Ports">FreeBSD Ruby Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Ruby" title="http://wiki.FreeBSD.org/Ruby">Wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Ruby" title="Wiki">http://wiki.FreeBSD.org/Ruby</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#ruby-" title="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#ruby-">PRs</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#ruby-" title="PRs">http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#ruby-</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#rubygem-" title="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#rubygem-">PRs</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#rubygem-" title="PRs">http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/prefixes.html#rubygem-</a></td></tr></table><p>
-	Contact:
-	  Philip
-	  Gollucci
-	 &lt;<a href="mailto:pgollucci@FreeBSD.org">pgollucci@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Steve
-	  Wills
-	 &lt;<a href="mailto:swills@FreeBSD.org">swills@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is underway to convert the remaining ruby- ports to
-	rubygem-* ports in order to keep up with the gem community.</p>
-
-      <p>A second attempt will be made to change the default ruby from
-	1.8 to 1.9.  There will be some unavoidable casualties of this
-	transition.  The sysutils/rubygem-chef-server port was contributed by
-	RideCharge Inc / Taxi Magic who is now using it exclusively.</p>
-    <h3>Open tasks:</h3><ol><li>Need some fresh -exp runs to check the new status especially with
-	ruby 1.9.3-p0.</li></ol><hr /><h2><a name="FreeBSD/GNOME" href="#FreeBSD/GNOME" id="FreeBSD/GNOME">FreeBSD/GNOME</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome" title="http://www.FreeBSD.org/gnome"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome" title="">http://www.FreeBSD.org/gnome</a></td></tr><tr><td><a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/" title="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/"></a></td><td>
-	    URL: <a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/" title="">http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/</a></td></tr></table><p>
-	Contact:
-	  GNOME FreeBSD mailing list
-	 &lt;<a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>It has been a while since we did a status report.</p>
-
-      <p>This year we started work on GNOME 3.0.  Due to time constrains
-	and lack of man power, this version did not make it into the ports.
-	Currently we have 3.2 in our development repo.  See the development
-	FAQ on our website for details.  The MC-UPDATING file contains
-	upgrade instructions.</p>
-
-      <p>Currently the GNOME team is understaffed, help is welcome!</p>
-    <h3>Open tasks:</h3><ol><li>Update the FreeBSD gnome website with GNOME 3.x information, and
-	still supply the 2.32.x info.</li></ol><hr /><h2><a name="FreeBSD/KDE" href="#FreeBSD/KDE" id="FreeBSD/KDE">FreeBSD/KDE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">FreeBSD/KDE home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="FreeBSD/KDE home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  KDE
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE/FreeBSD team have continued to improve the experience of
-	KDE software and Qt under FreeBSD.  The latest round of improvements
-	include:</p>
-
-      <ul>
-	<li>Many fixes upstream to make KDE and Qt build with Clang</li>
-
-	<li>Making automoc not freeze with parallel builds</li>
-      </ul>
-
-      <p>The team has also made many releases and upstreamed many fixes
-	and patches.  The latest round of releases include:</p>
-
-      <ul>
-	<li>KDE SC: 4.7.3, 4.7.4 (in the area51 experimental
-	  repository)</li>
-
-	<li>Qt: 4.8.0 (in the area51 experimental repository)</li>
-
-	<li>CMake: 2.8.6, 2.8.7</li>
-      </ul>
-
-      <p>The team is always looking for more testers and porters so
-	please contact us at kde@FreeBSD.org and visit our home page at
-	<a href="http://FreeBSD.kde.org" shape="rect">http://FreeBSD.kde.org</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Testing KDE SC 4.8.0.</li><li>Testing KDE PIM 4.7.4.</li><li>Testing phonon-gstreamer and phonon-vlc as the phonon-xine
-	backend was deprecated (but will remain in the ports for
-	now).</li><li>Testing the Calligra beta releases (in the area51
-	repository).</li></ol><hr /><h2><a name="Multimedia-&#8212;-Watching/Recording-Digital-TV" href="#Multimedia-&#8212;-Watching/Recording-Digital-TV" id="Multimedia-&#8212;-Watching/Recording-Digital-TV">Multimedia &#8212; Watching/Recording Digital TV</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/WebcamCompat" title="http://wiki.FreeBSD.org/WebcamCompat">Tested DVB and other hardware</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/WebcamCompat" title="Tested DVB and other hardware">http://wiki.FreeBSD.org/WebcamCompat</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HTPC" title="http://wiki.FreeBSD.org/HTPC"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/HTPC" title="">http://wiki.FreeBSD.org/HTPC</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/VDR" title="http://wiki.FreeBSD.org/VDR"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/VDR" title="">http://wiki.FreeBSD.org/VDR</a></td></tr></table><p>
-	Contact:
-	  Hans Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jason
-	  Harmening
-	 &lt;<a href="mailto:jason.harmening@gmail.com">jason.harmening@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Juergen
-	  Lock
-	 &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	</p>
-      <p>Progress has been made when watching/recording live digital TV
-	using FreeBSD:</p>
-
-      <ul>
-	<li><a href="http://freshports.org/multimedia/webcamd" shape="rect">
-	    multimedia/webcamd</a> is continuously adding support for
-	  more and more USB tuners using the Linux V4L/DVB drivers
-	  (also including remotes via webcamd and <a href="http://freshports.org/comms/lirc" shape="rect">comms/lirc</a>.)</li>
-
-	<li><a href="http://freshports.org/multimedia/cx88" shape="rect">
-	    multimedia/cx88</a> recently added Linux DVB API support
-	  for CX88-based PCI(-e) DVB-T tuners so "common" apps can now
-	  also be used with that hardware.</li>
-
-	<li><a href="http://freshports.org/multimedia/xbmc-pvr" shape="rect">
-	    multimedia/xbmc-pvr</a> was committed recently and the <a href="http://wiki.FreeBSD.org/VDR" shape="rect">multimedia/vdr</a>
-	  ports are working too for watching/recording live digital TV, and
-	  also other apps like kaffeine, or mplayer, or vlc.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Continue updating the VDR ports to the latest versions and
-	fix remaining bugs.</li><li>Update <a href="http://freshports.org/multimedia/libxine" shape="rect">
-	  multimedia/libxine</a> to 1.2.0 that recently was released
-	(which VDR uses.)</li><li>Test more hardware?</li></ol><hr /><h2><a name="Perl-Ports-Testing" href="#Perl-Ports-Testing" id="Perl-Ports-Testing">Perl Ports Testing</a></h2><p>
-	Contact:
-	  Steve
-	  Wills
-	 &lt;<a href="mailto:swills@FreeBSD.org">swills@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Sunpoet Po-Chuan
-	  Hsieh
-	 &lt;<a href="mailto:sunpoet@FreeBSD.org">sunpoet@FreeBSD.org</a>&gt;
-	</p>
-      <p>Many Perl modules in ports come with test cases included with
-	their source.  This project's goal is to ensure that all these tests
-	pass.  Patches have been added to the ports tinderbox to allow test
-	related dependencies to be installed and many ports have
-	TEST_DEPENDS now.  A patch is available to enable testing for those
-	who wish to help out.  All p5- ports have been built and tests
-	attempted.  Approximately 61% of the Perl ports pass currently.  Many
-	ports have been updated to include missing dependencies or make
-	other changes which allow tests to pass.  Long term goals include a
-	more generic framework for testing ports and automated tests
-	executed when ports are updated.</p>
-    <h3>Open tasks:</h3><ol><li>Many Perl ports which do not pass tests remain.</li><li>Need to figure out how to move testing out of
-	tinderbox.</li><li>A patch to build Perl with -pthread (but not enable
-	useithreads in Perl) is pending.  It will fix many currently broken
-	tests</li></ol><hr /><h2><a name="Public-FreeBSD-Ports-Development-Infrastructure-&#8212;-redports.org" href="#Public-FreeBSD-Ports-Development-Infrastructure-&#8212;-redports.org" id="Public-FreeBSD-Ports-Development-Infrastructure-&#8212;-redports.org">Public FreeBSD Ports Development Infrastructure &#8212;
-      redports.org</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://redports.org/" title="http://redports.org/"></a></td><td>
-	    URL: <a href="http://redports.org/" title="">http://redports.org/</a></td></tr><tr><td><a href="irc://irc.freenode.net#redports" title="irc://irc.freenode.net#redports">IRC: #redports on Freenode</a></td><td>
-	    URL: <a href="irc://irc.freenode.net#redports" title="IRC: #redports on Freenode">irc://irc.freenode.net#redports</a></td></tr><tr><td><a href="https://groups.google.com/group/redports" title="https://groups.google.com/group/redports">redports mailing list</a></td><td>
-	    URL: <a href="https://groups.google.com/group/redports" title="redports mailing list">https://groups.google.com/group/redports</a></td></tr><tr><td><a href="http://redports.org/wiki/UserGuide" title="http://redports.org/wiki/UserGuide">Userguide (with Screenshots)</a></td><td>
-	    URL: <a href="http://redports.org/wiki/UserGuide" title="Userguide (with Screenshots)">http://redports.org/wiki/UserGuide</a></td></tr></table><p>
-	Contact:
-	  Bernhard
-	  Froehlich
-	 &lt;<a href="mailto:decke@FreeBSD.org">decke@FreeBSD.org</a>&gt;
-	</p>
-      <p>Redports is a free service for FreeBSD port maintainers and port
-	committers to automatically buildtest ports on various FreeBSD
-	versions and architectures.  The motivation to do that was because
-	there are many people that do not have access to Ports Tinderboxes
-	and the existing Tinderboxes are usually dedicated to a single
-	team.</p>
-
-      <p>The platform was designed with scalability in mind but building
-	capacity is currently very limited until more hardware is
-	available.  I am already in contact with the usual suspects to
-	improve that.</p>
-    <h3>Open tasks:</h3><ol><li>Get more Hardware for building.</li><li>Port options support.</li><li>ports-mgmt/portlint support.</li></ol><hr /><h2><a name="Up-to-Date-X.Org-Server" href="#Up-to-Date-X.Org-Server" id="Up-to-Date-X.Org-Server">Up to Date X.Org Server</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Xorg" title="http://wiki.FreeBSD.org/Xorg"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Xorg" title="">http://wiki.FreeBSD.org/Xorg</a></td></tr></table><p>
-	Contact:
-	  X11 FreeBSD mailing list
-	 &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>The X11 team has started work on the next major update for the
-	X.Org ports.  You might have noticed libraries and proto ports being
-	updated that belong to the X.Org stack.  Currently in our development
-	repository we have the latest versions of many ports including mesa
-	and xf86-video-intel.</p>
-
-      <p>We support versions 1.7.7 and 1.10.4 of the X.Org tree for users
-	with the appropriate hardware and patches.</p>
-
-      <p>We need more testers for both the standard version from
-	xorg-devel and the WITH_NEW_XORG version.  We also need testers for
-	updated input/video drivers, especially for the less mainstream
-	ones.</p>
-
-      <p>In order to test check out our svn repository from <a href="http://trillian.chruetertee.ch/ports/browser/branches/xorg-dev" shape="rect">
-	  http://trillian.chruetertee.ch/ports/browser/branches/xorg-dev</a> and
-	the merge script from <a href="http://people.FreeBSD.org/~miwi/xorg/xorgmerge" shape="rect">
-	  http://people.FreeBSD.org/~miwi/xorg/xorgmerge</a>.  See the wiki for
-	more details.</p>
-    <h3>Open tasks:</h3><ol><li>Investigate xorg-server 1.12 which brings xinput 2.2.</li><li>Merge development repository into the main repository, after
-	more testing.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2012-01-2012-03.html b/website/content/en/status/report-2012-01-2012-03.html
deleted file mode 100644
index 1036ab47c1..0000000000
--- a/website/content/en/status/report-2012-01-2012-03.html
+++ /dev/null
@@ -1,1129 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between January and March
-      2012.  It is the first of the four reports planned for 2012.  This
-      quarter was highlighted by releasing the next major version of FreeBSD,
-      9.0, which was finally released in the beginning of January
-      2012.  The FreeBSD Project dedicates the FreeBSD 9.0-RELEASE to
-      the memory of Dennis M. Ritchie, one of the founding fathers of
-      the UNIX� operating system.  Our release engineering team has
-      been also busy with preparation of the 8.3-RELEASE, which was
-      publicly announced in April.</p><p>Thanks to all the reporters for the excellent work! This report
-      contains 27 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between April and June 2012 is July 15th, 2012.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-Services-Control">FreeBSD Services Control</a></li><li><a href="#GNU-Free-C++11-Stack">GNU-Free C++11 Stack</a></li><li><a href="#Growing-filesystems-online">Growing filesystems online</a></li><li><a href="#The-FreeNAS-Project">The FreeNAS Project</a></li></ul><h3><a href="#User-land-Programs">User-land Programs</a></h3><ul><li><a href="#Clang-Replacing-GCC-in-the-Base-System">Clang Replacing GCC in the Base System</a></li><li><a href="#Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></li><li><a href="#The-bsdconfig(8)-utility">The bsdconfig(8) utility</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></li><li><a href="#The-FreeBSD-Foundation-Team-Report">The FreeBSD Foundation Team Report</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#DTrace-Probes-for-the-linuxulator">DTrace Probes for the linuxulator</a></li><li><a href="#HDMI/DisplayPort-Audio-Support-in-HDA-Sound-Driver-(snd_hda)">HDMI/DisplayPort Audio Support in HDA Sound Driver
-      (snd_hda)</a></li><li><a href="#Improved-hwpmc(9)-Support-for-MIPS">Improved hwpmc(9) Support for MIPS</a></li><li><a href="#isci(4)-SAS-Driver">isci(4) SAS Driver</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Atheros-802.11n-Support">Atheros 802.11n Support</a></li><li><a href="#IPv6-Performance-Analysis">IPv6 Performance Analysis</a></li><li><a href="#Multi-FIB:-IPv6-Support-and-Other-Enhancements">Multi-FIB: IPv6 Support and Other Enhancements</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-on-Various-TI-Boards">FreeBSD/arm on Various TI Boards</a></li><li><a href="#FreeBSD/powerpc-on-Freescale-QorIQ-DPAA">FreeBSD/powerpc on Freescale QorIQ DPAA</a></li><li><a href="#NAND-File-System,-NAND-Flash-Framework,-NAND-Simulator">NAND File System, NAND Flash Framework, NAND Simulator</a></li><li><a href="#Porting-DTrace-to-MIPS-and-ARM">Porting DTrace to MIPS and ARM</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#A-New-linux_base-Port-Based-Upon-CentOS">A New linux_base Port Based Upon CentOS</a></li><li><a href="#BSD-licensed-sort-Utility-(GNU-sort-Replacement)">BSD-licensed sort Utility (GNU sort Replacement)</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Perl-Ports-Testing">Perl Ports Testing</a></li><li><a href="#The-FreeBSD-Haskell-Ports">The FreeBSD Haskell Ports</a></li><li><a href="#The-FreeBSD-Ports-Collection">The FreeBSD Ports Collection</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="FreeBSD-Services-Control" href="#FreeBSD-Services-Control" id="FreeBSD-Services-Control">FreeBSD Services Control</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~trhodes/fsc/" title="http://people.FreeBSD.org/~trhodes/fsc/"></a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~trhodes/fsc/" title="">http://people.FreeBSD.org/~trhodes/fsc/</a></td></tr></table><p>
-	Contact:
-	  Tom
-	  Rhodes
-	 &lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;
-	</p>
-      <p>After a while of moving and getting a new job, I finally got
-	back to this project (also thanks to several submissions by
-	Julian Fagir), a new version has been uploaded along with a short
-	description page.  The current version supports more options, a
-	configuration file, and updated rc.d script.  It also includes
-	manual page updates and an optional debugging mode.</p>
-    <hr /><h2><a name="GNU-Free-C++11-Stack" href="#GNU-Free-C++11-Stack" id="GNU-Free-C++11-Stack">GNU-Free C++11 Stack</a></h2><p>
-	Contact:
-	  David
-	  Chisnall
-	 &lt;<a href="mailto:theraven@FreeBSD.org">theraven@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report, the combination of libc++ and
-	libcxxrt has received some additional testing and gained some new
-	features including support for ARM EABI.  With clang 3.1, we now
-	pass all of the C++11 atomics tests.</p>
-
-      <p>The xlocale implementation (required for libc++) has been tested
-	with a variety of ports that were originally written for the Darwin
-	implementation, and bugs that this testing uncovered have been
-	fixed.  This should be released in 9.1.</p>
-
-      <p>In -CURRENT, we are now building libsupc++ as a shared library.
-	This provides the ABI layer and building it as a shared library
-	means that we can replace it with libcxxrt easily.  If you are
-	running -CURRENT, please try using libmap.conf to enable libcxxrt
-	instead of libsupc++.</p>
-
-      <p>If libstdc++ is using libcxxrt, you can now link against both
-	libraries that are using libstdc++ and libc++, making the migration
-	slightly easier, although you cannot pass STL objects between
-	libraries using different STL versions.</p>
-
-      <p>We still need a replacement for some parts of libgcc_s and for
-	the linker, but we're on track for a BSD licensed C++ stack in
-	10.0.</p>
-    <h3>Open tasks:</h3><ol><li>Test ports with libc++.  Hopefully most will Just Work, but
-	others may need patches or have a hard dependency on
-	libstdc++.</li><li>Enable building libc++ by default.  This is dependent upon
-	building with clang, because the version of gcc in the base system
-	does not support C++11 and so can not be used to build
-	libc++.</li><li>Removing libstdc++ from the base system and making it
-	available through ports for backwards compatibility.</li></ol><hr /><h2><a name="Growing-filesystems-online" href="#Growing-filesystems-online" id="Growing-filesystems-online">Growing filesystems online</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of this project is to make it possible to grow a
-	filesystem, both UFS and ZFS, while it's mounted read-write.  This
-	includes changes to both filesystems, GEOM infrastructure, and the
-	da(4) driver.  For testing purposes, I've also added resizing to
-	mdconfig(8) and implemented LUN resizing in CAM Target Layer.</p>
-
-      <p>From the system administrator point of view, this makes it
-	possible to resize mounted partition using gpart(8) and then resize
-	the filesystem on it using growfs(8) - all without unmounting it
-	first; especially useful if it's a root filesystem.</p>
-
-      <p>All the functionality works and is in the process of being
-	refined, reviewed and merged to HEAD.</p>
-
-      <p>This project is sponsored by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>The write suspension infrastructure (/dev/ufssuspend)
-	implemented to make resizing possible makes it also possible to
-	implement online tunefs(8) and fsck(8).</li><li>Right now, there is no way for a GEOM class to veto resizing
-	&#8212; classes are notified about resize and they can either adapt,
-	or wither.  Many classes store their metadata in the last sector,
-	though, so resizing a partition containing e.g. gmirror will make
-	it inoperable.  It would be nice if geom_mirror(4) could veto
-	resizing, so the administrator attempting to shoot himself in the
-	foot would get a warning.</li></ol><hr /><h2><a name="The-FreeNAS-Project" href="#The-FreeNAS-Project" id="The-FreeNAS-Project">The FreeNAS Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeNAS.org" title="http://www.FreeNAS.org"></a></td><td>
-	    URL: <a href="http://www.FreeNAS.org" title="">http://www.FreeNAS.org</a></td></tr></table><p>
-	Contact:
-	  Josh
-	  Paetzel
-	 &lt;<a href="mailto:jpaetzel@FreeBSD.org">jpaetzel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Xin
-	  Li
-	 &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeNAS 8.0.4 was released last month, which marks the end of
-	the 8.0.x branch in FreeNAS.</p>
-
-      <p>FreeNAS 8.2.0 is in BETA currently, and will hopefully be
-	released by the end of April.</p>
-
-      <p>It features a number of improvements over the 8.0.x line,
-	including plugin support, (the ability to run arbitrary software in
-	jails), as well as better integration between command line ZFS and
-	the GUI.</p>
-
-      <p>Once 8.2.0 is out it will be quickly followed up with 8.3.0,
-	which will include a number of driver updates as well as the long
-	awaited ZFS v28.</p>
-    <hr /><br /><h1><a name="User-land-Programs" href="#User-land-Programs" id="User-land-Programs">User-land Programs</a></h1><br /><h2><a name="Clang-Replacing-GCC-in-the-Base-System" href="#Clang-Replacing-GCC-in-the-Base-System" id="Clang-Replacing-GCC-in-the-Base-System">Clang Replacing GCC in the Base System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang">Building FreeBSD with Clang</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="Building FreeBSD with Clang">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Chisnall
-	 &lt;<a href="mailto:theraven@FreeBSD.org">theraven@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Dimitry
-	  Andric
-	 &lt;<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Pawel
-	  Worach
-	 &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	</p>
-      <p>Both FreeBSD 10.0-CURRENT and 9.0-STABLE now have Clang 3.0 release
-	installed by default.  At least on 10.0-CURRENT, both world and the
-	GENERIC kernel can be completely built without any -Werror
-	warnings.  This may not be the case for all custom kernel
-	configurations yet.</p>
-
-      <p>As of r231057, there is a WITH_CLANG_EXTRAS option for
-	src.conf(5), which will enable a number of additional LLVM and
-	Clang tools, such as 'llc' and 'opt'.  These tools are mainly useful
-	for people that want to manipulate LLVM bitcode (.bc) and LLVM
-	assembly language (.ll) files, or want to tinker with LLVM and
-	Clang themselves.</p>
-
-      <p>Also, as of r232322, there is a WITH_CLANG_IS_CC option for
-	src.conf(5), which will install Clang as /usr/bin/cc, /usr/bin/c++
-	and /usr/bin/cpp, making it the default system compiler.  Unless you
-	also use the WITHOUT_GCC option, gcc will still be available as
-	/usr/bin/gcc, /usr/bin/g++ and /usr/bin/gcpp.</p>
-
-      <p>The intent is to switch on this option by default rather sooner
-	than later, so we can start preparing for shipping 10.0-RELEASE
-	with Clang as as the default system compiler, and deprecating
-	gcc.</p>
-
-      <p>In other news, we will import a newer snapshot of Clang soon,
-	since upstream LLVM/Clang has already announced their 3.1 release
-	will be branched April 16, 2012.  Most likely, the actual 3.1
-	release will be follow a few weeks later, after which we will do
-	another import.</p>
-
-      <p>Last but not least, there are many ports people working on
-	making our ports compile properly with Clang.  Fixes are checked in
-	on a very regular basis now, and full exp-runs with Clang are also
-	done fairly regularly.  Of course, there are always a few difficult
-	cases, especially with very old software that will not even compile
-	with newer versions of gcc, let alone clang.</p>
-    <h3>Open tasks:</h3><ol><li>One of the most important tasks at the moment is to actually
-	build and run your entire FreeBSD system with Clang, as much as
-	possible.  Any compile-time or run-time problems should be reported
-	to the appropriate mailing list, or filed as a PR.  If you have
-	patches and/or workarounds, that would be even better.</li><li>Clang should have gotten better support for cross-compiling
-	after 3.0, so as soon as a 3.1 version is imported, we will need to
-	look at ways to get the FreeBSD world and kernels to cross-compile.
-	This is mainly of use for ARM and MIPS, which are architectures you
-	usually do not want to build natively on.</li><li>Help to make unwilling ports build with Clang is always
-	needed, and greatly appreciated.  Please mail the maintainer of your
-	favorite port with patches, or file PRs.</li></ol><hr /><h2><a name="Replacing-the-Regular-Expression-Code" href="#Replacing-the-Regular-Expression-Code" id="Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/" title="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/">Project repo</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/" title="Project repo">http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/</a></td></tr><tr><td><a href="http://laurikari.net/tre/" title="http://laurikari.net/tre/">TRE homepage</a></td><td>
-	    URL: <a href="http://laurikari.net/tre/" title="TRE homepage">http://laurikari.net/tre/</a></td></tr><tr><td><a href="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf" title="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf">A paper on the topic</a></td><td>
-	    URL: <a href="http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf" title="A paper on the topic">http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pdf</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report, there has been a significant
-	progress in optimizing TRE.  The multiple pattern heuristic code is
-	mostly finished and it distinguishes several different cases to
-	speed up pattern matching.  It extracts literal fragments from the
-	original patterns and uses a multiple pattern matching algorithm to
-	find any occurrence.  GNU grep uses the Commentz-Walter algorithm,
-	which is an automaton-based algorithm, while in this project, it
-	has been decided to use a Wu-Manber algorithm, which is more
-	efficient and also easier to implement.  In the current state, it
-	does not work entirely yet and some cases, like the REG_ICASE flag
-	are not yet covered.  This is the next major step to complete this
-	multiple pattern interface.  In the development branch, BSD grep is
-	already modified to use this new interface so it can be used for
-	testing and debugging purposes.</p>
-    <h3>Open tasks:</h3><ol><li>Finish multiple pattern heuristic regex matching.</li><li>Implement GNU-specific regex extensions.</li><li>Test standard-compliance and correct behavior.</li></ol><hr /><h2><a name="The-bsdconfig(8)-utility" href="#The-bsdconfig(8)-utility" id="The-bsdconfig(8)-utility">The bsdconfig(8) utility</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdconfig/" title="http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdconfig/">OpenSource Development Tree</a></td><td>
-	    URL: <a href="http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdconfig/" title="OpenSource Development Tree">http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdconfig/</a></td></tr><tr><td><a href="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1.svg" title="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1.svg">Menu Map w/ Includes</a></td><td>
-	    URL: <a href="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1.svg" title="Menu Map w/ Includes">http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1.svg</a></td></tr><tr><td><a href="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1i.svg" title="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1i.svg">Menu Map w/o Includes</a></td><td>
-	    URL: <a href="http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1i.svg" title="Menu Map w/o Includes">http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1i.svg</a></td></tr></table><p>
-	Contact:
-          Devin
-          Teske
-         &lt;<a href="mailto:dteske@FreeBSD.org">dteske@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-         Ron
-         McDowell
-         &lt;<a href="mailto:rcm@fuzzwad.org">rcm@fuzzwad.org</a>&gt;
-	</p>
-      <p>Approaching 20,000 lines of sh(1) code, the bsdconfig(8) tool is
-	approximately 70% complete.  Upon completion of this project,
-	bsdconfig(8) will represent (in conjunction with
-	already-existing bsdinstall(8)) a complete set of utilities
-	capable of purposefully deprecating sysinstall(8) in FreeBSD 9 and
-	higher.  This project has been a labor of love for Ron McDowell
-	and I for over 90 days now and we are approaching the completion
-	of this wonderful tool.</p>
-    <h3>Open tasks:</h3><ol><li>
-	The "installer suite" modules for acquiring/installing binary
-	packages and additional distribution sets. Startup services module.
-      </li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="Release-Engineering-Team-Status-Report" href="#Release-Engineering-Team-Status-Report" id="Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
-	Contact:
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>On behalf of the FreeBSD Project the Release Engineering Team
-	was are pleased to announce the release of the FreeBSD
-	8.3-RELEASE on April 18th, 2012.</p>
-
-      <p>With the FreeBSD 8.3 release cycle completed our focus shifts to
-	preparing for the FreeBSD 9.1-RELEASE.  A schedule will be posted
-	shortly, with the release target date set for mid-July 2012.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation-Team-Report" href="#The-FreeBSD-Foundation-Team-Report" id="The-FreeBSD-Foundation-Team-Report">The FreeBSD Foundation Team Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="www.FreeBSDFoundation.org" title="www.FreeBSDFoundation.org"></a></td><td>
-	    URL: <a href="www.FreeBSDFoundation.org" title="">www.FreeBSDFoundation.org</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The Foundation sponsored AsiaBSDCon 2012 which was held in
-	Tokyo, Japan, March 22-25.  We were represented at SCALE on Jan 21
-	and NELF on March 17.  This quarter we plan on being at ILF (Indiana
-	LinuxFest) April 14th, BSDCan May 11-12, and SELF (Southeast
-	LinuxFest) June 9.</p>
-
-      <p>We are proud to be a gold sponsor of BSDCan 2012, which will be
-	held in Ottawa, Canada, May 11-12.  We are sponsoring 14 developers
-	to attend the conference.</p>
-
-      <p>We kicked off three foundation funded projects &#8212; Growing
-	Filesystems Online by Edward Tomasz Napierala, Implementing
-	auditdistd daemon by Pawel Jakub Dawidek, and NAND Flash Support by
-	Semihalf.</p>
-
-      <p>We are pleased to <a href="http://www.FreeBSDfoundation.org/announcements.shtml" shape="rect">
-	announce</a> the addition of George Neville-Neil to our
-	board of directors.  Deb Goodkin, our Director of
-	Operations, was <a href="http://bsdtalk.blogspot.com/" shape="rect">interviewed by
-	  bsdtalk</a>.</p>
-
-      <p>We announced a call for project proposals.  We will accept
-	proposals until April 30th.  Please read <a href="http://www.FreeBSDfoundation.org/documents /FreeBSD%20Foundation%20Proposals%20March%202012.pdf" shape="rect">
-	  Project Proposal Procedures</a> to find out more.</p>
-
-      <p>FreeBSD 9.0 was released and we are proud to say we funded 7 of the
-	new features!</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="DTrace-Probes-for-the-linuxulator" href="#DTrace-Probes-for-the-linuxulator" id="DTrace-Probes-for-the-linuxulator">DTrace Probes for the linuxulator</a></h2><p>
-	Contact:
-	  Alexander
-	  Leidinger
-	 &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>Recently DTrace in the kernel was improved to be able to load
-	kernel modules with static dtrace providers after the dtrace
-	modules.  This allows me to commit my linuxulator specific
-	static provider work to -CURRENT.</p>
-
-      <p>Together with the linuxulator DTrace probes I developed some D
-	scripts to check various code paths in the linuxulator.  Those
-	scripts check various error cases which may be interesting to
-	verify userland code, but also linuxulator internals like
-	locks.</p>
-
-      <p>As of this writing I'm in the process of updating a test machine
-	to a more recent -current to prepare the commit.</p>
-    <hr /><h2><a name="HDMI/DisplayPort-Audio-Support-in-HDA-Sound-Driver-(snd_hda)" href="#HDMI/DisplayPort-Audio-Support-in-HDA-Sound-Driver-(snd_hda)" id="HDMI/DisplayPort-Audio-Support-in-HDA-Sound-Driver-(snd_hda)">HDMI/DisplayPort Audio Support in HDA Sound Driver
-      (snd_hda)</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>snd_hda(4) driver got number of improvements to better support
-	HDMI/DisplayPort audio, such as:</p>
-
-      <ul>
-	<li>Added fetching EDID-Like Data from the CODEC and video
-	  driver, describing audio capabilities of the display device.</li>
-
-	<li>Added setting HDMI/DP-specific CODEC options, such as number
-	  of channels, speakers configuration and channels mapping.</li>
-
-	<li>Added support for more multichannel formats.  For HDMI and
-	  DisplayPort device now supported: 2.0, 2.1, 3.0, 3.1, 4.0, 4.1,
-	  5.0, 5.1, 6.0, 6.1, 7.0 and 7.1 channels.</li>
-
-	<li>Added support for compressed streams passthrough with data
-	  rate 6.144 - 24Mbps, such as DTS-HD Master Audio or Dolby
-	  TrueHD.</li>
-
-	<li>Added support for HDA bus multiplexing to handle higher data
-	  rates (up to 92, 184 or more Mbps, depending on hardware
-	  capabilities).  It allows to handle several 192/24/8 LPCM playback
-	  streams simultaneously.</li>
-      </ul>
-
-      <p>Above functionality was successfully tested on NVIDIA GT210 and
-	GT520 video cards with nvidia-driver-290.10 driver.  HDMI audio on
-	older NVIDIA ION and Geforce 8300 boards still does not work for
-	unknown reason.  There are also successful reports about Intel video
-	with latest KMS-based drivers.  Support for ATI cards is limited to
-	older cards, because video driver supporting newer cards does
-	not support HDMI audio.</p>
-
-      <p>The code was committed to HEAD and merged to 9-STABLE
-	branch.</p>
-
-      <p>Project sponsored by iXsystems, Inc.</p>
-    <h3>Open tasks:</h3><ol><li>Make better use of received EDID-Like Data.</li><li>Identify and fix problem with older NVIDIA cards.</li></ol><hr /><h2><a name="Improved-hwpmc(9)-Support-for-MIPS" href="#Improved-hwpmc(9)-Support-for-MIPS" id="Improved-hwpmc(9)-Support-for-MIPS">Improved hwpmc(9) Support for MIPS</a></h2><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>hwpmc(9) for MIPS has been reworked.  The changes include:</p>
-
-      <ul>
-	<li>msip24k code was split to CPU-specific and arch-specific
-	  parts to make adding support for new CPUs easier</li>
-
-	<li>Added support for Octeon PMC</li>
-
-	<li>Added sampling support for MIPS in general</li>
-      </ul>
-    <hr /><h2><a name="isci(4)-SAS-Driver" href="#isci(4)-SAS-Driver" id="isci(4)-SAS-Driver">isci(4) SAS Driver</a></h2><p>
-	Contact:
-	  Jim
-	  Harris
-	 &lt;<a href="mailto:jimharris@FreeBSD.org">jimharris@FreeBSD.org</a>&gt;
-	</p>
-      <p>An Intel-supported isci(4) driver, for the integrated SAS
-	controller in Intel's C600 chipsets, is now available in head,
-	stable/9, stable/8 and stable/7.</p>
-
-      <p>The isci(4) driver will also be part of the FreeBSD 8.3
-	release.</p>
-    <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Atheros-802.11n-Support" href="#Atheros-802.11n-Support" id="Atheros-802.11n-Support">Atheros 802.11n Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg" title="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg" title="">http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/dev/ath(4)" title="http://wiki.FreeBSD.org/dev/ath(4)"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/dev/ath(4)" title="">http://wiki.FreeBSD.org/dev/ath(4)</a></td></tr></table><p>
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@FreeBSD.org">adrian@FreeBSD.org</a>&gt;
-	</p>
-      <p>802.11n station and hostap support is now fully functional, sans
-	correct hostap side power saving.  TX aggregation and TX BAR
-	handling is implemented.</p>
-
-      <p>Station chip power saving is not implemented at all yet, it's not
-	in the scope of this work.</p>
-
-      <p>Testers should disable bgscan (-bgscan) as scan/bgscan will
-	simply drop any traffic in the TX/RX queues, causing potential
-	traffic stalls.</p>
-    <h3>Open tasks:</h3><ol><li>Fix up hostap side power save handling.</li><li>Implement filtered frames support in the driver.</li><li>Fix scan/bgscan to correctly buffer and retransmit frames
-	when going off channel, so frames are not just "dropped" - this
-	causes issues in the aggregation sessions and may cause traffic
-	stalls.</li><li>Test/fix any issues with adhoc 802.11n support.</li></ol><hr /><h2><a name="IPv6-Performance-Analysis" href="#IPv6-Performance-Analysis" id="IPv6-Performance-Analysis">IPv6 Performance Analysis</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~bz/bench/" title="http://people.FreeBSD.org/~bz/bench/">Benchmarking results</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~bz/bench/" title="Benchmarking results">http://people.FreeBSD.org/~bz/bench/</a></td></tr></table><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>IPv6 performance numbers were often seen (significantly) lower
-	on FreeBSD when compared to IPv4.  Continuing last years IPv6-only
-	kernel efforts this project looked at various reasons for this and
-	started fixing some.</p>
-
-      <p>As part of the project a benchmark framework was created that
-	could carry out various tests including reboots in between runs and
-	gather results reproducibly without user intervention.  It
-	allows regular benchmarking with minimal configuration and easy
-	future extension for more benchmarks.</p>
-
-      <p>As a result of the initial analysis, UDP locking and route
-	lookups were improved, and delayed checksumming, TSO6 and LRO
-	support for IPv6 were implemented.  Following this checksum
-	"offload" for IPv6 on loopback was enabled and various
-	further individual improvements, both locking and general code
-	changes, as well as a reduction of the cache size footprint were
-	carried out.  Some of the changes were equally applied to IPv4.</p>
-
-      <p>Performance numbers on physical and loopback interfaces are
-	on par with IPv4 when using offload support with
-	TCP/IPv6, which is a huge improvement.  UDP and non-offload numbers
-	on IPv6 have generally improved but are still lower than on IPv4
-	and will need future work to catch up with a decade of IPv4
-	benchmarking and code path optimizations.  UDP IPv6 minimal size
-	send path packets per second (pps) numbers however have increased
-	beating IPv4 when sending to a local discard device.</p>
-
-      <p>This gets us really close to being able to prefer IPv6 by default
-	without causing loopback performance regressions.  For physical
-	interfaces, cxgb(4) in HEAD already supports IPv6 TCP offload and
-	LRO/v6 support was added.  To be able to get more test results on
-	different hardware, both ixgbe(4) and cxgbe(4) were also updated to
-	support TSO6 and LRO with IPv6.</p>
-
-      <p>Some of the insights gained from this work will help upcoming
-	discussions on both the lower/link-layer overhaul as well as for
-	the mbuf changes to prepare our stack for more, future improvements
-	(ahead of time).</p>
-
-      <p>I once again want to thank the FreeBSD Foundation and iXsystems for
-	their support of the project, as well as George Neville-Neil for
-	providing review.</p>
-
-      <p>Having set the start to close one of the biggest feature parity
-	gaps left I will continue to improve IPv6 code paths and hope that
-	we will see more contributions and independent results from the
-	community as well soon.</p>
-    <h3>Open tasks:</h3><ol><li>Carefully merge code changes to SVN.</li></ol><hr /><h2><a name="Multi-FIB:-IPv6-Support-and-Other-Enhancements" href="#Multi-FIB:-IPv6-Support-and-Other-Enhancements" id="Multi-FIB:-IPv6-Support-and-Other-Enhancements">Multi-FIB: IPv6 Support and Other Enhancements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/projects/multi-fibv6/" title="http://svnweb.FreeBSD.org/base/projects/multi-fibv6/">SVN multi-FIB IPv6 project area</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/projects/multi-fibv6/" title="SVN multi-FIB IPv6 project area">http://svnweb.FreeBSD.org/base/projects/multi-fibv6/</a></td></tr></table><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Alexander V.
-	  Chernikov
-	 &lt;<a href="mailto:melifaro@FreeBSD.org">melifaro@FreeBSD.org</a>&gt;
-	</p>
-      <p>In 2008 the multiple forwarding information base (FIB) feature
-	was introduced for IPv4 allowing up to 16 distinct forwarding
-	("routing") tables in the kernel.  Thanks to the sponsorship from
-	Cisco Systems, Inc. this feature is now also available for IPv6 and
-	one of the bigger IPv6 feature-parity gaps is closed.  The changes
-	have been integrated to HEAD, were merged back to stable/9 and
-	stable/8 and will be part of future releases for these branches.  A
-	backport to stable/7 is also available in the project branch.  If
-	more than one FIB is requested, IPv6 FIBs will be added along the
-	extra IPv4 FIBs without any special configuration needed and
-	programs like netstat and setfib, as well as ipfw, etc. were
-	extended to seamlessly support the multi-FIB feature on both
-	address families.</p>
-
-      <p>Thanks to the help of Alexander V. Chernikov all usage of the
-	multi-FIB feature is now using the boot-time variable rather than
-	depending on the compile time option.  In HEAD this now allows us
-	you to use the multi-FIB feature with GENERIC kernels not needing
-	to recompile your own anymore.  The former kernel option can still
-	be used to set a default value if desired.  Otherwise the net.fibs
-	loader tunable can be used to request more than one IPv6 and IPv4
-	FIB at boot time.</p>
-
-      <p>Last, routing sockets are now aware of FIBs and will only show
-	the routing messages targeted at the FIB attached to.  This allows
-	route monitor or routing daemons to get selective updates for just
-	a specific FIB.</p>
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Page">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>The same as before, the outdated contents in the www/ja subtree
-	were updated to the latest versions in the English counterpart.  The
-	updating work of the outdated translations in the www/ja subtree is
-	almost complete. Only the translations of the release documents
-	for old releases may be outdated.</p>
-
-      <p>During this period, we translated the 9.0-RELEASE announcement and
-	published it in a timely manner.  It seems that the Japanese version
-	of the release announcement is important for Japanese people as
-	this page has frequently been referenced.</p>
-
-      <p>For FreeBSD Handbook, translation work of the "cutting-edge"
-	section is still on-going.  Some updates in the "printing" and the
-	"linuxemu" section were done.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work of outdated documents in both
-	doc/ja_JP.eucJP and www/ja.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm-on-Various-TI-Boards" href="#FreeBSD/arm-on-Various-TI-Boards" id="FreeBSD/arm-on-Various-TI-Boards">FreeBSD/arm on Various TI Boards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/projects/armv6/sys/arm/ti/" title="http://svnweb.FreeBSD.org/base/projects/armv6/sys/arm/ti/"></a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/projects/armv6/sys/arm/ti/" title="">http://svnweb.FreeBSD.org/base/projects/armv6/sys/arm/ti/</a></td></tr></table><p>
-	Contact:
-	  Ben
-	  Gray
-	 &lt;<a href="mailto:bgray@FreeBSD.org">bgray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Olivier
-	  Houchard
-	 &lt;<a href="mailto:cognet@FreeBSD.org">cognet@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Damjan
-	  Marion
-	 &lt;<a href="mailto:dmarion@FreeBSD.org">dmarion@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of this project is to get FreeBSD running on various
-	popular boards that use TI-based SoCs like OMAP3, OMAP4, AM335x.
-	Project covers some ARM generic Cortex-A components: GIC (Generic
-	Interrupt Controller), PL310 L2 Cache Controller and SCU.</p>
-
-      <p>PandaBoard (TI OMAP4430) and PandaBoard ES (OMAP4460) Dual core
-	ARM Cortex-A9 board support includes: USB, onboard Ethernet over
-	USB, GPIO, I2C and MMC/SD card drivers.  Board works in multiuser
-	mode over NFS root.</p>
-
-      <p>BeagleBone (TI AM3358/AM3359) single core ARM Cortex-A8 based
-	board support currently includes: Ethernet, L2 cache, GPIO, I2C.
-	Board works in multiuser mode over NFS root.</p>
-    <h3>Open tasks:</h3><ol><li>Completing missing peripherals: DMA, SPI, MMC/SD, Video,
-	Audio.</li><li>Completing SMP support and testing.</li><li>Importing BeagleBoard (OMAP3) code to SVN.</li><li>Improving overall stability and performance.</li></ol><hr /><h2><a name="FreeBSD/powerpc-on-Freescale-QorIQ-DPAA" href="#FreeBSD/powerpc-on-Freescale-QorIQ-DPAA" id="FreeBSD/powerpc-on-Freescale-QorIQ-DPAA">FreeBSD/powerpc on Freescale QorIQ DPAA</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040">P2041 product page</a></td><td>
-	    URL: <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040" title="P2041 product page">http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040</a></td></tr><tr><td><a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041">P3041 product page</a></td><td>
-	    URL: <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041" title="P3041 product page">http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041</a></td></tr><tr><td><a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020">P5020 product page</a></td><td>
-	    URL: <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020" title="P5020 product page">http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020</a></td></tr><tr><td><a href="http://www.freescale.com/webapp/sps/site/homepage.jsp?code=64BIT&amp;fsrch=1&amp;sr=1" title="http://www.freescale.com/webapp/sps/site/homepage.jsp?code=64BIT&amp;fsrch=1&amp;sr=1">e5500 core home page</a></td><td>
-	    URL: <a href="http://www.freescale.com/webapp/sps/site/homepage.jsp?code=64BIT&amp;fsrch=1&amp;sr=1" title="e5500 core home page">http://www.freescale.com/webapp/sps/site/homepage.jsp?code=64BIT&amp;fsrch=1&amp;sr=1</a></td></tr></table><p>
-	Contact:
-	  Michal
-	  Dubiel
-	 &lt;<a href="mailto:md@semihalf.com">md@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Piotr
-	  Ziecik
-	 &lt;<a href="mailto:kosmo@semihalf.com">kosmo@semihalf.com</a>&gt;
-	</p>
-      <p>This work is bringing up the FreeBSD on Freescale QorIQ Data Path
-	Acceleration Architecture (DPAA) system-on-chips along with device
-	drivers for integrated peripherals.  Since the last status report,
-	the following support has been added:</p>
-
-      <ul>
-	<li>Ethernet (full network functionality using Regular Mode of
-	  DPAA infrastructure)</li>
-
-	<li>QorIQ P5020 SoC (e5500 core in legacy 32-bit mode)</li>
-
-	<li>P5020 QorIQ Development System support</li>
-
-	<li>Initial support for Enhanced SDHC</li>
-      </ul>
-
-      <p>The next step is:</p>
-
-      <ul>
-	<li>e5500 core in native 64-bit mode</li>
-      </ul>
-
-      <p>Related publications:</p>
-
-      <ul>
-	<li>Michal Dubiel, Piotr Ziecik, "FreeBSD on Freescale QorIQ Data
-	  Path Acceleration Architecture Devices", AsiaBSDCon, March 2012,
-	  Tokyo, Japan.</li>
-      </ul>
-    <hr /><h2><a name="NAND-File-System,-NAND-Flash-Framework,-NAND-Simulator" href="#NAND-File-System,-NAND-Flash-Framework,-NAND-Simulator" id="NAND-File-System,-NAND-Flash-Framework,-NAND-Simulator">NAND File System, NAND Flash Framework, NAND Simulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/projects/nand/" title="http://svnweb.FreeBSD.org/base/projects/nand/">NAND branch</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/projects/nand/" title="NAND branch">http://svnweb.FreeBSD.org/base/projects/nand/</a></td></tr></table><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Mateusz
-	  Guzik
-	 &lt;<a href="mailto:mjg@semihalf.com">mjg@semihalf.com</a>&gt;
-	</p>
-      <p>The NAND Flash stack consists of a driver framework for NAND
-	controllers and memory chips, a NAND device simulator and a fault
-	tolerant, log-structured file system, accompanied by tools,
-	utilities and documentation.</p>
-
-      <ul>
-	<li>NAND FS support merged into "nand" project branch</li>
-
-	<ul>
-	  <li>NAND FS filesystem</li>
-
-	  <li>NAND FS userland tools</li>
-	</ul>
-
-	<li>NAND Framework and NAND simulator merged into "nand" project
-	  branch</li>
-
-	<ul>
-	  <li>NAND framework: nandbus, generic nand chips drivers</li>
-
-	  <li>NAND Flash controllers (NFC) drivers for NAND Simulator and
-	    Marvell MV-78100 (ARM)</li>
-
-	  <li>NAND tool (which allows to erase, write/read pages/oob,
-	    etc.</li>
-	</ul>
-      </ul>
-
-      <p>The next steps include:</p>
-
-      <ul>
-	<li>Fix bugs</li>
-	<li>Merge into HEAD</li>
-      </ul>
-
-      <p>Work on this project is supported by the FreeBSD Foundation and
-	Juniper Networks.</p>
-    <hr /><h2><a name="Porting-DTrace-to-MIPS-and-ARM" href="#Porting-DTrace-to-MIPS-and-ARM" id="Porting-DTrace-to-MIPS-and-ARM">Porting DTrace to MIPS and ARM</a></h2><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The major part of DTrace has been ported to MIPS platform.
-	Supported ABIs: o32 and n64.  n32 has not been tested yet.  MIPS
-	implementation passes 853 of 927 tests from DTrace test suite.</p>
-
-      <p>The fbt provider and userland DTrace are not supported yet.</p>
-
-      <p>The port to ARM is in progress.</p>
-    <h3>Open tasks:</h3><ol><li>Userland DTrace support for MIPS.</li><li>Investigate amount of effort required for getting fbt
-	provider work at least partially.</li><li>Find proper solution for cross-platform CTF data generation
-	(required for ARM).</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="A-New-linux_base-Port-Based-Upon-CentOS" href="#A-New-linux_base-Port-Based-Upon-CentOS" id="A-New-linux_base-Port-Based-Upon-CentOS">A New linux_base Port Based Upon CentOS</a></h2><p>
-	Contact:
-	  Alexander
-	  Leidinger
-	 &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>We got a PR with a linux_based port which is based upon CentOS
-	6.  Currently this can only be used as a test environment, as it
-	depends upon a more recent linux kernel version, than the
-	linuxulator provides.</p>
-
-      <p>As of this writing, I'm in the process of preparing a commit of
-	this port.</p>
-    <h3>Open tasks:</h3><ol><li>Repocopy by portmgr.</li><li>Add conflicts in other linux_base ports.</li><li>Commit the CentOS based one.</li><li>Some cleanup.</li></ol><hr /><h2><a name="BSD-licensed-sort-Utility-(GNU-sort-Replacement)" href="#BSD-licensed-sort-Utility-(GNU-sort-Replacement)" id="BSD-licensed-sort-Utility-(GNU-sort-Replacement)">BSD-licensed sort Utility (GNU sort Replacement)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/" title="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/">FreeBSD port of BSD sort</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/" title="FreeBSD port of BSD sort">http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/</a></td></tr><tr><td><a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html" title="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html">IEEE Std 1003.1-2008 sort specification</a></td><td>
-	    URL: <a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html" title="IEEE Std 1003.1-2008 sort specification">http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html</a></td></tr></table><p>
-	Contact:
-	  Oleg
-	  Moskalenko
-	 &lt;<a href="mailto:oleg.moskalenko@citrix.com">oleg.moskalenko@citrix.com</a>&gt;
-	<br />
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently the BSD sort reached usable stable stage.  It is
-	stable, it is as fast as the GNU sort, and it supports multi-byte
-	locales (this is something that GNU sort does not do correctly).
-	BSD sort has all features of GNU sort 5.3.0 (version included into
-	FreeBSD) with some extra features and bug fixes.</p>
-    <h3>Open tasks:</h3><ol><li>Add BSD sort into HEAD as an alternative, installed as
-	bsdsort.  If proven to work as expected, change it to the default
-	sort version and remove GNU sort.</li><li>Investigate the possibility of a multi-threaded sort
-	implementation and implement it, if it proves more
-	efficient.</li><li>Upgrade BSD sort features to include some obscure new
-	features in the latest GNU sort version 8.15.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The team has made many releases and upstreamed many fixes and
-	patches.  The latest round of releases include:</p>
-
-      <ul>
-	<li>KDE SC: 4.7.4 (in ports) and 4.8.0, 4.8.1, 4.8.2 (in
-	  area51)</li>
-	<li>Qt: 4.8.0, 4.8.1 (in area51)</li>
-	<li>PyQt: 4.9.1; SIP: 4.13.2 (in area51)</li>
-	<li>KDevelop: 2.3.0; KDevPlatform: 1.3.0 (in area51)</li>
-	<li>Calligra: 2.3.87 (in area51)</li>
-	<li>Amarok: 2.5.0</li>
-	<li>CMake: 2.8.7</li>
-      </ul>
-
-      <p>Due to the prolonged port freeze the KDE team has not been able
-	to update KDE in Ports as it is considered a intrusive change.</p>
-
-      <p>The team is always looking for more testers and porters so
-	please contact us at kde@FreeBSD.org and visit our home page at
-	<a href="http://FreeBSD.kde.org" shape="rect">http://FreeBSD.kde.org</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Testing KDE SC 4.8.2.</li><li>Testing KDE PIM 4.8.2.</li><li>Testing phonon-gstreamer and phonon-vlc as the phonon-xine
-	backend was deprecated (but will remain in the ports for
-	now).</li><li>Testing the Calligra beta releases (in the area51
-	repository).</li></ol><hr /><h2><a name="Perl-Ports-Testing" href="#Perl-Ports-Testing" id="Perl-Ports-Testing">Perl Ports Testing</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Perl#Test_Dependencies" title="http://wiki.FreeBSD.org/Perl#Test_Dependencies"></a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Perl#Test_Dependencies" title="">http://wiki.FreeBSD.org/Perl#Test_Dependencies</a></td></tr></table><p>
-	Contact:
-	  Steve
-	  Wills
-	 &lt;<a href="mailto:swills@FreeBSD.org">swills@FreeBSD.org</a>&gt;
-	</p>
-      <p>Many Perl modules in ports come with test cases included with
-	their source.  This project's goal is to ensure that all these tests
-	pass.  Significant progress has been made on this project.  The
-	change to build perl with -pthread was committed and no issues have
-	been reported.  Many ports have had missing dependencies added
-	and/or other changes and approximately 90% of p5- ports pass tests.
-	Work is being done on bringing testing support out of ports
-	tinderbox.</p>
-    <h3>Open tasks:</h3><ol><li>Finish work on patch to bring testing support to
-	ports.</li><li>Add additional support for testing other types of ports such
-	as python and ruby.</li></ol><hr /><h2><a name="The-FreeBSD-Haskell-Ports" href="#The-FreeBSD-Haskell-Ports" id="The-FreeBSD-Haskell-Ports">The FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Haskell" title="http://wiki.FreeBSD.org/Haskell">FreeBSD Haskell wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Haskell" title="FreeBSD Haskell wiki page">http://wiki.FreeBSD.org/Haskell</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="https://github.com/freebsd-haskell/freebsd-haskell/">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="FreeBSD Haskell ports repository">https://github.com/freebsd-haskell/freebsd-haskell/</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/hsporter/" title="https://github.com/freebsd-haskell/hsporter/">hsporter repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/hsporter/" title="hsporter repository">https://github.com/freebsd-haskell/hsporter/</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/hsmtk/" title="https://github.com/freebsd-haskell/hsmtk/">hsmtk repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/hsmtk/" title="hsmtk repository">https://github.com/freebsd-haskell/hsmtk/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�LI
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud announce that the FreeBSD Haskell Team has committed
-	the Haskell Platform 2011.4.0.0 update, GHC 7.0.4 update, existing
-	port updates, as well new port additions to FreeBSD ports repository,
-	which were pending due to freeze for 9.0-RELEASE.  Some of the new
-	ports which were committed include Yesod, Happstack, wxHaskell,
-	gitit, Threadscope, etc. and the count of Haskell ports in FreeBSD
-	Ports tree is now almost 300.  All of these updates will be
-	available as part of upcoming 8.3-RELEASE.</p>
-
-      <p>We started project hsporter to automate creation of new FreeBSD
-	Haskell ports from .cabal file, as well as update existing ports.
-	We also published scripts which we were using in the FreeBSD Haskell
-	project under the project hsmtk.</p>
-    <h3>Open tasks:</h3><ol><li>Test GHC to work with clang/LLVM.</li><li>Add an option to the <tt>lang/ghc</tt>
-	port to be able to build it with already installed GHC instead of
-	requiring a separate GHC boostrap tarball.</li><li>Add more ports to the Ports Collection.</li></ol><hr /><h2><a name="The-FreeBSD-Ports-Collection" href="#The-FreeBSD-Ports-Collection" id="The-FreeBSD-Ports-Collection">The FreeBSD Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree slowly climbs above 23,000 ports.  The PR count
-	still remains at about 1100.</p>
-
-      <p>In Q1 we added 2 new committers, took in 2 commit bits for safe
-	keeping, and had one committer return to ports work.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports updates.
-	Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>Ports validation in the FreeBSD 10 environment</li>
-	<li>Updates to bison, libtool and libiconv</li>
-	<li>Set java/opendjdk6 as default java</li>
-	<li>Tests with clang set as default</li>
-	<li>Update to devel/boost and friends</li>
-	<li>Update of audio/sdl and friends</li>
-	<li>Tests for changes in the ports licensing infrastructure</li>
-	<li>Update to devel/ruby1[8|9]</li>
-	<li>Update to postresql</li>
-	<li>Update to apr</li>
-	<li>Checks for new x11/xorg</li>
-	<li>Security update to security/gnutls</li>
-	<li>Ongoing validation of infrastructure with pkgng</li>
-      </ul>
-
-      <p>A lot of focus during this period was put into getting the ports
-	tree into a ready state for FreeBSD 8.3, including preparing packages
-	for the release.</p>
-
-      <p>Beat Gaetzi has been doing ongoing tests with the ports tree to
-       ensure a smooth transition from CVS to Subversion.</p>
-    <h3>Open tasks:</h3><ol><li>Looking for help getting <url link="http://wiki.FreeBSD.org/PortsAndClang">ports to build
-	with clang</url>.</li><li>Looking for help with <url link="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures">
-	  Tier-2 architectures</url>.</li><li><url link="http://wiki.FreeBSD.org/PortsBrokenBySrcChanges">ports
-	  broken by src changes</url>.</li><li><url link="http://wiki.FreeBSD.org/PortsFailingOnPointyhat">ports
-	  failing on pointyhat</url>.</li><li><url link="http://wiki.FreeBSD.org/PortsFailingOnPointyhatWest">
-	  ports failing on pointyhat-west</url>.</li><li><url link="http://wiki.FreeBSD.org/Trybroken">ports that are marked
-	  as BROKEN</url>.</li><li><url link="http://wiki.FreeBSD.org/WhenDidThatPortBreak">When did
-	  that port break</url>?</li><li>Most ports PRs are assigned, we now need to focus on testing,
-	committing and closing.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2012-04-2012-06.html b/website/content/en/status/report-2012-04-2012-06.html
deleted file mode 100644
index a71dd542d2..0000000000
--- a/website/content/en/status/report-2012-04-2012-06.html
+++ /dev/null
@@ -1,835 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between April and June
-      2012.  This quarter was highlighted by having a new Core Team
-      elected, which took office on July 11th to start its work with a
-      relatively high number of new members.  Note that this is the
-      second of the four reports planned for 2012.</p><p>Thanks to all the reporters for the excellent work! This report
-      contains 17 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period
-      between July and December 2012 is February 17th, 2013.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></li><li><a href="#Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Documentation-Project">FreeBSD Documentation Project</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Port-Management-Team">The FreeBSD Port Management Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD/at91-Improvements">FreeBSD/at91 Improvements</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Multipath-TCP-(MPTCP)-for-FreeBSD">Multipath TCP (MPTCP) for FreeBSD</a></li><li><a href="#SMP-Friendly-pf(4)">SMP-Friendly pf(4)</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-on-ARM-Fast-Models-Simulator-for-Cortex-A15-MPCore-Processor">FreeBSD/arm on ARM Fast Models Simulator for Cortex-A15 MPCore
-      Processor</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#BSD-licensed-Sort-Utility-(GNU-sort(1)-Replacement)">BSD-licensed Sort Utility (GNU sort(1) Replacement)</a></li><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Portbuilder">Portbuilder</a></li><li><a href="#Redports">Redports</a></li><li><a href="#Xorg-on-FreeBSD">Xorg on FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSD-Day-2012">BSD-Day 2012</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="FreeBSD-Services-Control-(fsc)" href="#FreeBSD-Services-Control-(fsc)" id="FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></h2><p>
-	Contact:
-	  Tom
-	  Rhodes
-	 &lt;<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>&gt;
-	</p>
-      <p>FSC has been moved into the ports system (see
-	<tt>sysutils/fsc</tt>) and continues to improve outside of the
-	ports tree.  Some interesting work is being done in the area of
-	services control, system boot, and a simplification of the
-	process.  Stay tuned for more information in status reports that
-	follow.</p>
-    <h3>Open tasks:</h3><ol><li>Test, test, test.  Feedback is really important to this
-	project.</li></ol><hr /><h2><a name="Replacing-the-Regular-Expression-Code" href="#Replacing-the-Regular-Expression-Code" id="Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://laurikari.net/tre/" title="http://laurikari.net/tre/">TRE home page</a></td><td>
-	    URL: <a href="http://laurikari.net/tre/" title="TRE home page">http://laurikari.net/tre/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>It has been decided to implement the optimizations and
-	extensions as a more isolated layer and not directly in TRE
-	itself.  Since the last report there has been some progress in
-	this direction and the code has been significantly refactored.
-	It does not work yet in this new form but it is close to a
-	working state.  Apart from this, the multiple pattern matching
-	needs some debugging and some minor features are missing.</p>
-    <h3>Open tasks:</h3><ol><li>Finish multiple pattern heuristic regex matching.</li><li>Implement GNU-specific regex extensions.</li><li>Test performance, standard-compliance and correct
-	behavior.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Documentation-Project" href="#FreeBSD-Documentation-Project" id="FreeBSD-Documentation-Project">FreeBSD Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/GoogleCodeIn/2011Status" title="http://wiki.freebsd.org/GoogleCodeIn/2011Status"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/GoogleCodeIn/2011Status" title="">http://wiki.freebsd.org/GoogleCodeIn/2011Status</a></td></tr><tr><td><a href="http://wiki.freebsd.org/201208DevSummit" title="http://wiki.freebsd.org/201208DevSummit"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/201208DevSummit" title="">http://wiki.freebsd.org/201208DevSummit</a></td></tr><tr><td><a href="http://wiki.freebsd.org/DocIdeaList" title="http://wiki.freebsd.org/DocIdeaList"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/DocIdeaList" title="">http://wiki.freebsd.org/DocIdeaList</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:freebsd-doc@FreeBSD.org">freebsd-doc@FreeBSD.org</a>&gt;
-	</p>
-      <p>We continue to make progress in committing the work produced as
-	part of Google Code-In 2011; an overview of the status is at <a href="http://wiki.freebsd.org/GoogleCodeIn/2011Status" shape="rect">http://wiki.freebsd.org/GoogleCodeIn/2011Status</a>.
-	Doc committers and GCIN mentors are encouraged to go through the
-	list and help shepherd outstanding tasks into the tree.</p>
-
-      <p>We are planning a full day of Documentation Summit on the day
-	preceding the August 2012 DevSummit in Cambridge, UK.  This
-	follows a successful DocSummit day held at BSDCan in May 2012.
-	Further details are available at: <a href="http://wiki.freebsd.org/201208DevSummit" shape="rect">http://wiki.freebsd.org/201208DevSummit</a>.</p>
-
-      <p>A doc sprint took place over IRC (<tt>#bsddocs on</tt> EFnet)
-	in early July, setting out plans for reviving the marketing team
-	and a strong desire for a new, more organized website.</p>
-
-      <p>A lot of progress and momentum has built up with creating and
-	updating documentation and website content over the last few
-	months.  Also read the doceng report for the recent
-	infrastructure improvements.</p>
-
-      <p>Anyone wishing to help with this effort is welcome to join us
-	and say hello either on the freebsd-doc mailing list, or
-	<tt>#bsddocs</tt> on EFnet IRC.</p>
-    <h3>Open tasks:</h3><ol><li>Review the website content and remove outdated parts or
-	update when applicable.</li><li>Go through the doc idea list on the wiki and start working
-	them out.</li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://docs.FreeBSD.org/cgi/mid.cgi?1342030291.6001.80.camel" title="http://docs.FreeBSD.org/cgi/mid.cgi?1342030291.6001.80.camel">Announcement</a></td><td>
-	    URL: <a href="http://docs.FreeBSD.org/cgi/mid.cgi?1342030291.6001.80.camel" title="Announcement">http://docs.FreeBSD.org/cgi/mid.cgi?1342030291.6001.80.camel</a></td></tr></table><p>
-	Contact:
-	  Core Team
-	 &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Project is pleased to announce the completion of the
-	2012 Core Team election.  The FreeBSD Core Team acts as the
-	project's "Board of Directors" and is responsible for approving
-	new src committers, resolving disputes between developers,
-	appointing sub-committees for specific purposes (security
-	officer, release engineering, port managers, webmaster, et
-	cetera), and making any other administrative or policy decisions
-	as needed.  The Core Team has been elected by FreeBSD developers
-	every 2 years since 2000.</p>
-
-      <p>Peter Wemm rejoins the Core Team after a two-year hiatus, with
-	new members Thomas Abthorpe, Gavin Atkinson, David Chisnall,
-	Attilio Rao and Martin Wilke joining incumbents John Baldwin,
-	Konstantin Belousov and Hiroki Sato.</p>
-
-      <p>The complete newly elected core team is:</p>
-
-      <ul>
-	<li>Thomas Abthorpe &lt;tabthorpe@FreeBSD.org&gt;</li>
-	<li>Gavin Atkinson &lt;gavin@FreeBSD.org&gt;</li>
-	<li>John Baldwin &lt;jhb@FreeBSD.org&gt;</li>
-	<li>Konstantin Belousov &lt;kib@FreeBSD.org&gt;</li>
-	<li>David Chisnall &lt;theraven@FreeBSD.org&gt;</li>
-	<li>Attilio Rao &lt;attilio@FreeBSD.org&gt;</li>
-	<li>Hiroki Sato &lt;hrs@FreeBSD.org&gt;</li>
-	<li>Peter Wemm &lt;peter@FreeBSD.org&gt;</li>
-	<li>Martin Wilke &lt;miwi@FreeBSD.org&gt;</li>
-      </ul>
-
-      <p>The new Core Team would like to thank outgoing members Wilko
-	Bulte, Brooks Davis, Warner Losh, Pav Lucistnik, Colin Percival
-	and Robert Watson for their service over the past two (and in
-	some cases, many more) years.</p>
-
-      <p>The Core Team would also especially like to thank Dag-Erling
-	Sm�rgrav for running the election.</p>
-   <hr /><h2><a name="The-FreeBSD-Port-Management-Team" href="#The-FreeBSD-Port-Management-Team" id="The-FreeBSD-Port-Management-Team">The FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree slowly approaches 24,000 ports.  The PR count
-	still is close to 1200.</p>
-
-      <p>In Q2 we added 7 new committers and took in one commit bit for
-	safe keeping.</p>
-
-      <p>The Ports Management team have been running -exp runs on an
-	ongoing basis, verifying how base system updates may affect the
-	ports tree, as well as providing QA runs for major ports
-	updates.  Of note, -exp runs were done for:</p>
-
-      <ul>
-	<li>automake update</li>
-	<li>cmake update</li>
-	<li>xorg update</li>
-	<li>png update</li>
-	<li>Fix make reinstall</li>
-	<li>Implement <tt>USE_QT4</tt> in <tt>bsd.ports.mk</tt></li>
-	<li>KDE4 update</li>
-	<li>XFCE4 update</li>
-	<li>bison update</li>
-	<li>perl5.14 as default</li>
-	<li>ruby1.9 as default</li>
-	<li>ruby1.8 update</li>
-	<li>bsdsort regression test</li>
-      </ul>
-
-      <p>A lot of focus during this period was put into getting the
-	ports tree into a ready state for FreeBSD�9.1.</p>
-
-      <p>A significant step forward was the implementation of
-	OptionsNG.</p>
-
-      <p>A record number of Port Managers attended BSDCan 2012, with
-	five being present to partake in the week of events, culminating
-	in a portmgr PR closing session that dealt with 18 PRs in one
-	day.  You can see a group photo at <a href="http://www.facebook.com/portmgr" shape="rect"></a>.  While you are
-	there, please click on the "Like" icon.</p>
-
-      <p>Beat Gaetzi has been doing ongoing tests with the ports tree to
-	ensure a smooth transition from CVS to Subversion.  The tree was
-	successfully migrated the weekend of June 14, 2012.</p>
-    <h3>Open tasks:</h3><ol><li>Looking for help getting <a href="http://wiki.freebsd.org/PortsAndClang" shape="rect">ports to build with
-	clang</a>.</li><li>Looking for help fixing <a href="http://wiki.freebsd.org/PortsFailingOnCurrent" shape="rect">ports
-	broken on CURRENT</a>.  (List needs updating, too.)</li><li>Looking for help with <a href="http://wiki.freebsd.org/PortsBrokenOnTier2Architectures" shape="rect">Tier-2
-	architectures</a>.</li><li><a href="http://wiki.freebsd.org/PortsBrokenBySrcChanges" shape="rect">ports
-	broken by src changes</a>.</li><li><a href="http://wiki.freebsd.org/PortsFailingOnPointyhat" shape="rect">ports
-	failing on pointyhat</a>.</li><li><a href="http://wiki.freebsd.org/PortsFailingOnPointyhatWest" shape="rect">ports
-	failing on pointyhat-west</a>.</li><li><a href="http://wiki.freebsd.org/Trybroken" shape="rect">ports that are
-	marked as <tt>BROKEN</tt></a>.</li><li><a href="http://wiki.freebsd.org/WhenDidThatPortBreak" shape="rect">When
-	did that port break</a>?</li><li>Most ports PRs are assigned, we now need to focus on
-	testing, committing and closing.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="FreeBSD/at91-Improvements" href="#FreeBSD/at91-Improvements" id="FreeBSD/at91-Improvements">FreeBSD/at91 Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/FreeBSDAtmel" title="http://wiki.freebsd.org/FreeBSDAtmel">FreeBSD on ATMEL AT91 Wiki</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/FreeBSDAtmel" title="FreeBSD on ATMEL AT91 Wiki">http://wiki.freebsd.org/FreeBSDAtmel</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD's Atmel support has languished for some time.  A number of
-	improvements were urgently needed as demand for newer SoCs has
-	materialized.  New SoC support is not hard, but it does wind up
-	copying a lot of code.  I have started down the path to make it
-	easier to do.  I had planned on making it table driven.  But
-	then I discovered with dts files that Atmel was producing.</p>
-
-      <p>So, I plan on moving to using Atmel's <tt>.dsti</tt> files, or
-	variations on them.  They have .dsti files for all the AT91SAM9
-	parts.  This should allow us to support new SoCs and boards
-	faster.</p>
-
-      <p>However, there are some challenges with this approach.  Pin
-	multiplexing seems undefined in Atmel's dts file.  Only a few of
-	the devices are well-defined at the present time.  And the
-	encoding seems to be immature.</p>
-
-      <p>So we have a target-rich port that is quite ripe for
-	refactoring.</p>
-    <h3>Open tasks:</h3><ol><li>Update the base system libfdt to a version that supports
-	include.</li><li>Write a <tt>.dtsi</tt> for Atmel AT91RM9200.</li><li>Write <tt>.dti</tt> files for all supported boards.</li><li>Help sort out the pin multiplexing issue.</li><li>Refactor existing board files to make new ones easier in the
-	interim.</li><li>Knock yourself out and implement board support for new
-	CPUs.</li></ol><hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="Multipath-TCP-(MPTCP)-for-FreeBSD" href="#Multipath-TCP-(MPTCP)-for-FreeBSD" id="Multipath-TCP-(MPTCP)-for-FreeBSD">Multipath TCP (MPTCP) for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/newtcp/mptcp/" title="http://caia.swin.edu.au/newtcp/mptcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/newtcp/mptcp/" title="">http://caia.swin.edu.au/newtcp/mptcp/</a></td></tr><tr><td><a href="http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed-09" title="http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed-09">TCP Extensions for Multipath Operation with Multiple Addresses (draft)</a></td><td>
-	    URL: <a href="http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed-09" title="TCP Extensions for Multipath Operation with Multiple Addresses (draft)">http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed-09</a></td></tr><tr><td><a href="http://mptcp.info.ucl.ac.be/" title="http://mptcp.info.ucl.ac.be/">"MultiPath TCP &#8212; Linux Kernel implementation" home page</a></td><td>
-	    URL: <a href="http://mptcp.info.ucl.ac.be/" title="&quot;MultiPath TCP &#8212; Linux Kernel implementation&quot; home page">http://mptcp.info.ucl.ac.be/</a></td></tr></table><p>
-	Contact:
-	  Nigel
-	  Williams
-	 &lt;<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lastewart@swin.edu.au">lastewart@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	</p>
-      <p>Work is underway to create an IETF draft-compatible Multipath
-	TCP implementation for the FreeBSD kernel.</p>
-
-      <p>A key goal of the project is to create a research platform to
-	investigate a range of multipath related transport issues
-	including congestion control, retransmission strategy and packet
-	scheduling policy.  We also aim to provide full interoperability
-	with the Linux kernel implementation being developed at
-	Universit� catholique de Louvain.</p>
-
-      <p>We expect to release code and results at the project's home
-	page as it progresses.</p>
-    <hr /><h2><a name="SMP-Friendly-pf(4)" href="#SMP-Friendly-pf(4)" id="SMP-Friendly-pf(4)">SMP-Friendly pf(4)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/pf/head/" title="http://svnweb.freebsd.org/base/projects/pf/head/">Project SVN branch</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/projects/pf/head/" title="Project SVN branch">http://svnweb.freebsd.org/base/projects/pf/head/</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-pf/2012-June/006643.html" title="http://lists.freebsd.org/pipermail/freebsd-pf/2012-June/006643.html">Alpha announcement email thread</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-pf/2012-June/006643.html" title="Alpha announcement email thread">http://lists.freebsd.org/pipermail/freebsd-pf/2012-June/006643.html</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Smirnoff
-	 &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project is aimed at moving the <tt>pf(4)</tt> packet filter
-	out of single mutex, as well as in general improving of its FreeBSD
-	port.</p>
-
-      <p>The project is near its finish, the code is planned to go into
-	head after more testing and benchmarking.  If you are interested
-	in details, please see the corresponding email thread on
-	freebsd-pf (see links).</p>
-    <h3>Open tasks:</h3><ol><li>Rewrite the <tt>pf(4)</tt> <tt>ioctl()</tt> interface so
-	that it does not utilize in-kernel structures.  That would make
-	ABI more stable and ease future development.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Page">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>Our translation work has slightly moved on to handbook from the
-	<tt>www/ja</tt> (CVS) or <tt>htdocs</tt> (SVN) subtree, since
-	almost translated web page contents were updated to the latest
-	English counterparts.</p>
-
-      <p>During this period, we translated the 8.3-RELEASE announcement
-	and published it in a timely manner.  Newsflash and some other
-	updates in the English version were also translated as soon as
-	possible.</p>
-
-      <p>For FreeBSD Handbook, translation work of the "cutting-edge" and
-	"printing" sections have been completed.  Some updates in the
-	"linuxemu" and "serialcomms" section were done.  At this moment,
-	"bsdinstall", "cutting-edge", "desktop", "install",
-	"introduction", "kernelconfig", "mirrors", "multimedia",
-	"pgpkeys", "ports", "printing", and "x11" chapters are
-	synchronized with the English versions.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work of outdated documents in
-	<tt>ja_JP.eucJP</tt> subtree.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm-on-ARM-Fast-Models-Simulator-for-Cortex-A15-MPCore-Processor" href="#FreeBSD/arm-on-ARM-Fast-Models-Simulator-for-Cortex-A15-MPCore-Processor" id="FreeBSD/arm-on-ARM-Fast-Models-Simulator-for-Cortex-A15-MPCore-Processor">FreeBSD/arm on ARM Fast Models Simulator for Cortex-A15 MPCore
-      Processor</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.arm.com/products/processors/cortex-a/cortex-a15.php" title="http://www.arm.com/products/processors/cortex-a/cortex-a15.php">Cortex-A15 product page</a></td><td>
-	    URL: <a href="http://www.arm.com/products/processors/cortex-a/cortex-a15.php" title="Cortex-A15 product page">http://www.arm.com/products/processors/cortex-a/cortex-a15.php</a></td></tr><tr><td><a href="http://www.arm.com/products/tools/models/fast-models.php" title="http://www.arm.com/products/tools/models/fast-models.php">Fast Models product page</a></td><td>
-	    URL: <a href="http://www.arm.com/products/tools/models/fast-models.php" title="Fast Models product page">http://www.arm.com/products/tools/models/fast-models.php</a></td></tr></table><p>
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Tomasz
-	  Nowicki
-	 &lt;<a href="mailto:tn@semihalf.com">tn@semihalf.com</a>&gt;
-	</p>
-      <p>ARM Fast Models is platform which helps software developers
-	debug systems in parallel with SoC design, speeding up and
-	improving system development.  This work is bringing up FreeBSD on
-	ARM Fast Models system based on ARM Cortex-A15 and peripheral
-	components.  It works in single user mode, using a compiled-in
-	kernel RAM disk minimal root file system.</p>
-
-      <p>Current FreeBSD support includes:</p>
-
-      <ul>
-	<li>L1, L2 cache, Branch Predictor</li>
-	<li>Dual-core (SMP) support setup in WB cache mode</li>
-	<li>Cortex-A15 integrated Generic Timer</li>
-	<li>Drivers for ARM peripheral components:
-	  <ul>
-	    <li>PL011 UART controller</li>
-	    <li>PL390 GIC - Generic Interrupt Controller</li>
-	    <li>SP804 Dual Timer</li>
-	  </ul>
-	</li>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>Quad-core (SMP) support</li>
-	<li>Multi-user mode</li>
-      </ul>
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="BSD-licensed-Sort-Utility-(GNU-sort(1)-Replacement)" href="#BSD-licensed-Sort-Utility-(GNU-sort(1)-Replacement)" id="BSD-licensed-Sort-Utility-(GNU-sort(1)-Replacement)">BSD-licensed Sort Utility (GNU sort(1) Replacement)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/" title="http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/">FreeBSD port of BSD sort(1)</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/" title="FreeBSD port of BSD sort(1)">http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/</a></td></tr><tr><td><a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html" title="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html">IEEE Std 1003.1-2008 sort(1) specification</a></td><td>
-	    URL: <a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html" title="IEEE Std 1003.1-2008 sort(1) specification">http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html</a></td></tr></table><p>
-	Contact:
-	  Oleg
-	  Moskalenko
-	 &lt;<a href="mailto:oleg.moskalenko@citrix.com">oleg.moskalenko@citrix.com</a>&gt;
-	<br />
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>BSD <tt>sort(1)</tt> has been made the default sort utility in
-	10-CURRENT.  It is compatible with the latest GNU
-	<tt>sort(1)</tt>, version 8.15, except that the multi-threaded
-	mode is not enabled by default.</p>
-    <h3>Open tasks:</h3><ol><li>When the track record of the BSD <tt>sort(1)</tt> allows,
-	remove GNU <tt>sort(1)</tt> from -CURRENT.</li><li>Improve reliability of the multi-threaded sort and
-	investigate the possibility of making it the default compilation
-	mode.</li><li>Investigate possibility of factoring out the sort
-	functionality into a standalone library so that other utilities
-	can also make use of it.</li></ol><hr /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Haskell" title="http://wiki.freebsd.org/Haskell">FreeBSD Haskell wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Haskell" title="FreeBSD Haskell wiki page">http://wiki.freebsd.org/Haskell</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="https://github.com/freebsd-haskell/freebsd-haskell/">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="FreeBSD Haskell ports repository">https://github.com/freebsd-haskell/freebsd-haskell/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�LI
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce that the FreeBSD Haskell Team has updated
-	the Haskell Platform to 2012.2.0.0, GHC to 7.4.1 as well as
-	updated existing ports to their latest stable versions.  We also
-	added a number of new Haskell ports, and their count in FreeBSD
-	Ports tree is now 336.</p>
-    <h3>Open tasks:</h3><ol><li>Test GHC to work with clang/LLVM.</li><li>Add an option to the <tt>lang/ghc</tt> port to be able to
-	build it with already installed GHC instead of requiring a
-	separate GHC bootstrap tarball.</li><li>Commit pending Haskell ports to the FreeBSD Ports tree.</li><li>Add more ports to the Ports Collection.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The team has made many releases and upstreamed many fixes and
-	patches.  The latest round of releases include:</p>
-
-      <ul>
-	<li>KDE SC: 4.8.3, 4.8.4 (in ports) and 4.8.95 (in area51)</li>
-	<li>Qt: 4.8.1, 4.8.2</li>
-	<li>PyQt: 4.9.1; SIP: 4.13.2; QScintilla 2.6.1</li>
-	<li>KDevelop: 2.3.1; KDevPlatform: 1.3.1</li>
-	<li>Calligra: 2.4.2, 2.4.3</li>
-	<li>Amarok: 2.5.90 (in area51)</li>
-	<li>CMake: 2.8.8</li>
-	<li>Digikam (and KIPI-plugins): 2.6.0</li>
-      </ul>
-
-      <p>As a result &#8212; according to PortScout &#8212; kde@ has 393
-	ports, of which 91% are up-to-date.</p>
-
-      <p>The team is always looking for more testers and porters so
-	please contact us and visit our home page.</p>
-    <h3>Open tasks:</h3><ol><li>Test KDE SC 4.8.95.</li><li>Test KDE PIM 4.8.95.</li><li>Update out-of-date ports, see <a href="http://portscout.FreeBSD.org/kde@freebsd.org.html" shape="rect">PortScout</a> for a
-	list.</li></ol><hr /><h2><a name="Portbuilder" href="#Portbuilder" id="Portbuilder">Portbuilder</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/DragonSA/portbuilder" title="https://github.com/DragonSA/portbuilder">Git Repository</a></td><td>
-	    URL: <a href="https://github.com/DragonSA/portbuilder" title="Git Repository">https://github.com/DragonSA/portbuilder</a></td></tr><tr><td><a href="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/README" title="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/README">README</a></td><td>
-	    URL: <a href="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/README" title="README">https://github.com/DragonSA/portbuilder/blob/0.1.5.2/README</a></td></tr><tr><td><a href="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/TODO" title="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/TODO">TODO</a></td><td>
-	    URL: <a href="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/TODO" title="TODO">https://github.com/DragonSA/portbuilder/blob/0.1.5.2/TODO</a></td></tr></table><p>
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:naylor.b.david@gmail.com">naylor.b.david@gmail.com</a>&gt;
-	</p>
-      <p>Since the last update there has been 2 feature releases and 4
-	bug-fix releases.  A highlight of the changes made:</p>
-
-      <ul>
-	<li>Support has been added for:</li>
-	  <ul>
-	    <li><tt>-j</tt>: controlling concurrency per stage</li>
-	    <li>pkgng: next generation package manager</li>
-	    <li>installing packages via repository</li>
-	    <li>dynamic defaults (loaded from
-	      <tt>/etc/make.conf</tt>)</li>
-	    <li>new options framework (aka OptionsNG)</li>
-	  </ul>
-
-	<li>Some of the fixes include:</li>
-	  <ul>
-	    <li>correct assertions</li>
-	    <li>correct build logic</li>
-	    <li>retry when kevent receives <tt>EINTR</tt></li>
-	    <li>correctly detecting installed ports</li>
-	    <li>many fixes in the build logic</li>
-	  </ul>
-      </ul>
-
-      <p>A benchmark was run timing portbuilder against a standard ports
-	build of KDE (<tt>x11/kde4</tt>) in a clean <tt>chroot(8)</tt>
-	environment.  Portbuilder achieved a build time of 2:21:16
-	compared to ports build time of 4:47:21 for an decreased build
-	time of 51% from using portbuilder.</p>
-    <hr /><h2><a name="Redports" href="#Redports" id="Redports">Redports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.redports.org/" title="http://www.redports.org/"></a></td><td>
-	    URL: <a href="http://www.redports.org/" title="">http://www.redports.org/</a></td></tr></table><p>
-	Contact:
-	  Bernhard
-	  Froehlich
-	 &lt;<a href="mailto:decke@FreeBSD.org">decke@FreeBSD.org</a>&gt;
-	</p>
-      <p>There was good progress in the last half a year and a lot of
-	support from different parties to make redports a stable and
-	fast service.</p>
-
-      <p>A long known security concern within tinderbox was raised at
-	the BSD-Day in Vienna which was addressed by beat.  That
-	improves security and isolation of the concurrent running jobs a
-	lot and gives me peace of mind.</p>
-
-      <p>We also recently got two beefy machines from the FreeBSD
-	Foundation which increases computing power a lot.  So no more
-	backlogs and your jobs finish much quicker.</p>
-
-      <p>But as usual now that we have enough power I was able to make
-	another promise come true and integrated Ports QAT functionality
-	into redports.  Ports QAT was an automated services that did a
-	buildtest after each commit to the official FreeBSD ports tree.  If
-	a build fails it sends out mails and logfiles to the committer.
-	That finds bad commits quickly and allows the committer to fix
-	it before the first user notices.  The former service stopped
-	about 2 years ago and we had no proper replacement for that task
-	at hand.  Now that this is fully integrated into redports it
-	also gives us all the nice benefits of a common platform.</p>
-    <h3>Open tasks:</h3><ol><li>Automatic build incoming patches from Ports PRs in redports
-	and send results to GNATS database.</li><li>People want an GCC testing environment on redports where all
-	ports are build with <tt>lang/gcc47</tt>.  To make that happen
-	we need to patch the ports framework to handle that and
-	correctly bootstrap with base GCC.  This also gives us the
-	possibility to build all our binary packages with a modern gcc
-	and is easy to use for regular users.  Contributors?</li></ol><hr /><h2><a name="Xorg-on-FreeBSD" href="#Xorg-on-FreeBSD" id="Xorg-on-FreeBSD">Xorg on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Xorg" title="http://wiki.freebsd.org/Xorg"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Xorg" title="">http://wiki.freebsd.org/Xorg</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk"></a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr></table><p>
-	Contact:
-	  Martin
-	  Wilke
-	 &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Koop
-	  Mast
-	 &lt;<a href="mailto:kwm@FreeBSD.org">kwm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Niclas
-	  Zeising
-	 &lt;<a href="mailto:zeising@FreeBSD.org">zeising@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Eitan
-	  Adler
-	 &lt;<a href="mailto:eadler@FreeBSD.org">eadler@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the beginning of this period, an update to the xorg
-	distribution for FreeBSD was made, dubbed xorg 7.5.2.  This update
-	included a new flag, <tt>WITH_NEW_XORG</tt>, to get a more
-	recent xorg distribution for those with modern hardware.  To get
-	KMS support for recent Intel graphics chipsets <tt>WITH_KMS</tt>
-	must also be set.  This requires a recent FreeBSD 10-CURRENT or
-	FreeBSD 9-STABLE.</p>
-    <h3>Open tasks:</h3><ol><li>Switch to use FreeGLUT instead of libGLUT, since the latter
-	is old and has there is no upstream support or releases any
-	more.  Work on this is mostly done.</li><li>Update the xorg distribution to what is in the development
-	repository.  The xorg project recently did a new release, and
-	the development repository contains this release.  It needs more
-	testing before it can be merged, and a CFT was sent out in the
-	beginning of June.  Work on this is ongoing.</li><li>Decide how to handle the new and old xorg distributions.  In
-	recent xorg, a lot of legacy driver support has been dropped,
-	therefore we need to maintain two xorg distributions to not
-	loose a lot of hardware drivers.  Currently, this is done by
-	setting the flag <tt>WITH_NEW_XORG</tt> in
-	<tt>/etc/make.conf</tt>, but a more practical solution is
-	needed.  This is especially important since the flag is not very
-	user friendly, and since there currently will be no official
-	packages for the new distribution.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSD-Day-2012" href="#BSD-Day-2012" id="BSD-Day-2012">BSD-Day 2012</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bsdday.eu/2012" title="http://bsdday.eu/2012">BSD-Day 2012 web site</a></td><td>
-	    URL: <a href="http://bsdday.eu/2012" title="BSD-Day 2012 web site">http://bsdday.eu/2012</a></td></tr><tr><td><a href="http://www.youtube.com/playlist?list=PL13D5471D8ECF08C9" title="http://www.youtube.com/playlist?list=PL13D5471D8ECF08C9">Video recordings of the talks at YouTube</a></td><td>
-	    URL: <a href="http://www.youtube.com/playlist?list=PL13D5471D8ECF08C9" title="Video recordings of the talks at YouTube">http://www.youtube.com/playlist?list=PL13D5471D8ECF08C9</a></td></tr><tr><td><a href="https://picasaweb.google.com/116452848880746560170/BSDDay2012?authkey=Gv1sRgCN3twLrxuaeongE" title="https://picasaweb.google.com/116452848880746560170/BSDDay2012?authkey=Gv1sRgCN3twLrxuaeongE">Event photo album</a></td><td>
-	    URL: <a href="https://picasaweb.google.com/116452848880746560170/BSDDay2012?authkey=Gv1sRgCN3twLrxuaeongE" title="Event photo album">https://picasaweb.google.com/116452848880746560170/BSDDay2012?authkey=Gv1sRgCN3twLrxuaeongE</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>For this year, we moved the time of the event earlier by six
-	months, so it was held on May 5, 2012 and it was co-located with
-	the Austrian Linuxweeks (Linuxwochen �sterreich) in Vienna.
-	We had many sponsors, like the freshly joined FreeBSD Foundation,
-	iXsystems, FreeBSDMall, BSD Magazine, allBSD.de Projekt, that
-	enabled us to continue our previously launched series of
-	multi-project BSD developer summits all around Central
-	Europe.</p>
-
-      <p>To kick off, there was a "stammtisch" (local beer meetup)
-	organized in the downtown of Vienna, at Kolar on the Friday
-	evening before the event &#8212; as usual.  Then it was followed
-	by the event on Saturday that brought many interesting topics
-	from the world of FreeBSD, OpenBSD and NetBSD: running NetBSD as an
-	embedded system for managing VOIP applications, introduction to
-	the Capsicum security framework, relayd(8), the load balancer
-	and proxy solution for OpenBSD, status update of the
-	developments around the FreeBSD ports tree, using DVCSs in clouds,
-	firewalling with pfSense, and mfsBSD.  Please consult the links
-	in the report for the details.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2012-07-2012-09.html b/website/content/en/status/report-2012-07-2012-09.html
deleted file mode 100644
index 9e763df51d..0000000000
--- a/website/content/en/status/report-2012-07-2012-09.html
+++ /dev/null
@@ -1,695 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between July and
-      September 2012. This is the third of the four reports planned for
-      2012.</p><p>Highlights from this quarter include successful participation in
-      Google Summer of Code, major work in areas of the source and
-      ports trees, and a Developer Summit attended by over 30
-      developers.</p><p>Thanks to all the reporters for the excellent work! This report
-      contains 12 entries and we hope you enjoy reading it.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-on-Altera-FPGAs">FreeBSD on Altera FPGAs</a></li><li><a href="#Native-iSCSI-Target">Native iSCSI Target</a></li><li><a href="#Parallel-rc.d-execution">Parallel rc.d execution</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD-on-ARMv6/ARMv7">FreeBSD on ARMv6/ARMv7</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-Developer-Summit,-Cambridge,-UK">FreeBSD Developer Summit, Cambridge, UK</a></li></ul><h3><a href="#FreeBSD-in-Google-Summer-of-Code">FreeBSD in Google Summer of Code</a></h3><ul><li><a href="#Google-Summer-of-Code-2012">Google Summer of Code 2012</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="FreeBSD-on-Altera-FPGAs" href="#FreeBSD-on-Altera-FPGAs" id="FreeBSD-on-Altera-FPGAs">FreeBSD on Altera FPGAs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cl.cam.ac.uk/research/security/ctsrd/" title="http://www.cl.cam.ac.uk/research/security/ctsrd/">CTSRD Project</a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/research/security/ctsrd/" title="CTSRD Project">http://www.cl.cam.ac.uk/research/security/ctsrd/</a></td></tr><tr><td><a href="http://www.cl.cam.ac.uk/research/security/ctsrd/cheri.html" title="http://www.cl.cam.ac.uk/research/security/ctsrd/cheri.html">CHERI</a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/research/security/ctsrd/cheri.html" title="CHERI">http://www.cl.cam.ac.uk/research/security/ctsrd/cheri.html</a></td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Bjoern
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the course of developing the <a href="http://www.cl.cam.ac.uk/research/security/ctsrd/cheri.html" shape="rect">
-	    CHERI processor</a> as part of the <a href="http://www.cl.cam.ac.uk/research/security/ctsrd/" shape="rect">CTSRD
-	    project</a> SRI International's Computer Science Laboratory and
-	the University of Cambridge Computer Laboratory have developed
-	support for a number of general purpose IP cores for Altera FPGAs
-	including the Altera Triple Speed Ethernet (ATSE) MAC core, the
-	Altera University Program SD Card core, and the Altera JTAG UART.
-	We have also added support for general access to memory mapped
-	devices on the Avalon bus via the avgen bus. We have implemented
-	both nexus and flattened device tree (FDT) attachments for these
-	devices.</p>
-
-      <p>In addition to these softcore we have developed support for
-	the Terasic multi-touch LCD and are working to provide support
-	for the Terasic HDMI Transmitter Daughter Card. Both of these
-	work with common development and/or reference boards for Altera
-	FPGAs. They do require additional IP cores which we plan to
-	release to the open source community in the near future.</p>
-
-      <p>With exception of the ATSE and HDMI drivers we have merged all
-	of these changes to FreeBSD-CURRENT. We anticipate that these
-	drivers will be useful for users who with to run FreeBSD on either
-	hard or soft core CPUs on Altera FPGAs.</p>
-
-      <p>This work has been sponsored by DARPA, AFRL, and Google.</p>
-    <hr /><h2><a name="Native-iSCSI-Target" href="#Native-iSCSI-Target" id="Native-iSCSI-Target">Native iSCSI Target</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the July-September time period, the Native iSCSI Target
-	project was officially started under sponsorship from the FreeBSD
-	Foundation. Before the end of September I've written ctld(8), the
-	userspace part of the target, responsible for handling
-	configuration, accepting incoming connections, performing
-	authentication and iSCSI parameter negotiation, and handing off
-	connections to the kernel. For the time being, I've reused some
-	parts of protocol-handling code from the istgt project; since
-	ctld(8) only handles the Login phase, the code can be rewritten
-	in a much simpler and shorter way in the future.</p>
-    <hr /><h2><a name="Parallel-rc.d-execution" href="#Parallel-rc.d-execution" id="Parallel-rc.d-execution">Parallel rc.d execution</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/buganini/rcexecr" title="https://github.com/buganini/rcexecr"></a></td><td>
-	    URL: <a href="https://github.com/buganini/rcexecr" title="">https://github.com/buganini/rcexecr</a></td></tr><tr><td><a href="https://github.com/kil/rcorder" title="https://github.com/kil/rcorder"></a></td><td>
-	    URL: <a href="https://github.com/kil/rcorder" title="">https://github.com/kil/rcorder</a></td></tr></table><p>
-	Contact:
-	  Kuan-Chung
-	  Chiu
-	 &lt;<a href="mailto:buganini@gmail.com">buganini@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Kilian
-	 &lt;<a href="mailto:kklimek@uos.de">kklimek@uos.de</a>&gt;
-	</p>
-      <p>There are two implementations to make rc.d execution parallel.
-	Compared to Kil's rcorder, rcexecr brings more concurrence and
-	provides more flexibility than older "early_late_divider"
-	mechanism but require more invasive /etc patch. Both
-	implementations have switch to toggle parallel execution. Further
-	modification/integration needs more discussion.</p>
-    <h3>Open tasks:</h3><ol><li>Refine /etc/rc.d/* to eliminate unnecessary waiting.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="https://wiki.freebsd.org/BugBusting" title="https://wiki.freebsd.org/BugBusting"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/BugBusting" title="">https://wiki.freebsd.org/BugBusting</a></td></tr></table><p>
-	Contact:
-	  Eitan
-	  Adler
-	 &lt;<a href="mailto:eadler@FreeBSD.org">eadler@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>In August, Eitan Adler (eadler@) and Oleksandr Tymoshenko
-	(gonzo@) joined the Bugmeister team. At the same time, Remko
-	Lodder and Volker Werth stepped down. We extend our thanks to
-	Volker and Remko for their work in the past, and welcome
-	Oleksandr and Eitan. Eitan and Oleksandr have been working hard
-	on migrating from GNATS, and have made significant progress on
-	evaluating new software, and creating scripts to export data
-	from GNATS.</p>
-
-      <p>The bugbusting team continue work on trying to make the
-	contents of the GNATS PR database cleaner, more accessible and
-	easier for committers to find and resolve PRs, by tagging PRs
-	to indicate the areas involved, and by ensuring that there is
-	sufficient info within each PR to resolve each issue.</p>
-
-      <p>As always, anybody interested in helping out with the PR
-	queue is welcome to join us in #freebsd-bugbusters on EFnet. We
-	are always looking for additional help, whether your interests
-	lie in triaging incoming PRs, generating patches to resolve
-	existing problems, or simply helping with the database
-	housekeeping (identifying duplicate PRs, ones that have already
-	been resolved, etc). This is a great way of getting more
-	involved with FreeBSD!</p>
-    <h3>Open tasks:</h3><ol><li>Further research into tools suitable to replace
-	GNATS.</li><li>Get more users involved with triaging PRs as they come
-	in.</li><li>Assist committers with closing PRs.</li></ol><hr /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org/press/2012Jul-newsletter.shtml" title="http://www.freebsdfoundation.org/press/2012Jul-newsletter.shtml">Semi-annual newsletter</a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org/press/2012Jul-newsletter.shtml" title="Semi-annual newsletter">http://www.freebsdfoundation.org/press/2012Jul-newsletter.shtml</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The Foundation hosted and sponsored the Cambridge FreeBSD
-	developer summit in August 2012.</p>
-
-      <p>We were represented at the following conferences: OSCON July
-	2012, Texas LinuxFest, and Ohio LinuxFest.</p>
-
-      <p>We negotiated/supervised Foundation funded projects:
-	Distributed Security Audit Logging, Capsicum Component
-	Framework, Native iSCSI Target Scoping, and Growing UFS
-	Filesystems Online.</p>
-
-      <p>We negotiated, supervised, and funded hardware needs for
-	FreeBSD co-location centers.</p>
-
-      <p>We welcomed Kirk McKusick to our board of directors. He took
-	over the responsibility of managing our investments.</p>
-
-      <p>We visited companies to discuss their FreeBSD use and to help
-	facilitate collaboration with the Project.</p>
-
-      <p>We managed FreeBSD vendor community mailing list and
-	meetings.</p>
-
-      <p>We created a high quality FreeBSD 9 brochure to help promote
-	FreeBSD.</p>
-
-      <p>Published our <a href="http://www.freebsdfoundation.org/press/2012Jul-newsletter.shtml" shape="rect">
-	    semi-annual newsletter</a> that highlighted Foundation
-	  funded projects, travel grants for
-	  developers, conferences sponsored and other ways the Foundation
-	  supported the FreeBSD Project.</p>
-
-      <p>We hired a technical writer to help with FreeBSD
-	marketing/promotional material.</p>
-
-      <p>We began work on redesigning our website.</p>
-    <hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact:
-	  Core Team
-	 &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>Along with the change in the Core Team membership, several
-	related roles changed hands. Gabor Pali assumed the role of core
-	secretary from Gavin Atkinson, and David Chisnall replaced Robert
-	Watson as liaison to the FreeBSD Foundation. The Core Team felt
-	there was no longer a need for a formal security team liaison, so
-	that role was retired.</p>
-
-      <p>In the third quarter, the Core Team granted access for 2 new
-	committers and took 2 commit bits into safekeeping.</p>
-
-      <p>The Core Team worked with the Port Management Team and Cluster
-	Administrators to set a date to stop providing CVS exports for
-	the ports repository, which is February 28, 2013. In the
-	meantime, the CVS export for 9.1-RELEASE was restored.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="FreeBSD-on-ARMv6/ARMv7" href="#FreeBSD-on-ARMv6/ARMv7" id="FreeBSD-on-ARMv6/ARMv7">FreeBSD on ARMv6/ARMv7</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  freebsd-arm mailing list
-	 &lt;<a href="mailto:freebsd-arm@FreeBSD.org">freebsd-arm@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for ARMv6 and ARMv7 architecture has been merged from
-	project branch to HEAD.  This code covers the following parts:
-	<ul>
-	  <li>General ARMv6/ARMv7 kernel bits (pmap, cache, assembler
-	    routines, etc...)</li>
-	  <li>ARM Generic Interrupt Controller driver</li>
-	  <li>Improved thread-local storage for cpus &gt;=ARMv6</li>
-	  <li>Driver for SMSC LAN95XX and LAN8710A ethernet controllers</li>
-	  <li>Marvell MV78x60 support (multiuser, ARMADA XP kernel config)</li>
-	  <li>TI OMAP4 and AM335x support (multiuser, no GPU or graphics
-	    support, kernel configs for Pandaboard and Beaglebone)</li>
-	  <li>LPC32x0 support (multiuser, frame buffer works with SSD1289
-	    LCD controller.  Embedded Artists EA3250 kernel config)</li>
-	</ul>
-      </p>
-
-      <p>This work was a result of a joint effort by many people,
-	including but not limited to: Grzegorz Bernacki (gber@),
-	Aleksander Dutkowski, Ben R. Gray (bgray@), Olivier Houchard
-	(cognet@), Rafal Jaworowski (raj@) and Semihalf team, Tim
-	Kientzle (kientzle@), Jakub Wojciech Klama (jceel@), Ian Lepore
-	(ian@), Warner Losh (imp@), Damjan Marion (dmarion@), Lukasz
-	Plachno, Stanislav Sedov (stas@), Mark Tinguely and Andrew
-	Turner (andrew@).  Thanks to all, who contributed by
-	submitting code, testing and giving valuable advice.</p>
-    <h3>Open tasks:</h3><ol><li>More hardware bring-ups and more drivers</li><li>Finish SMP support</li><li>VFP/NEON support</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Page">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>Web page (htdocs): Newsflash and some other updates in the
-	English version were translated to keep them up-to-date.
-	Especially "security incident on FreeBSD infrastructure" was
-	translated and published in a timely manner.</p>
-
-      <p>FreeBSD Handbook: Big update in the "advanced-networking". With
-	this update, merging translation results from the handbook in the
-	local repository of Japanese documentation project into the main
-	repository was completed. This chapter is still outdated and
-	needs more work. The other sections have also constantly been
-	updated. Especially, new subsection "Using pkgng for Binary
-	Package Management" was added to "ports" section and "Using
-	subversion" subsection was added to "mirrors" section.</p>
-
-      <p>Article: Some progress was made in "Writing FreeBSD Problem
-	Reports" and "Writing FreeBSD Problem Reports" articles.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work of outdated documents in the
-	<tt>ja_JP.eucJP</tt> subtree.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE/FreeBSD team have continued to improve the experience of
-	KDE software and Qt under FreeBSD. The latest round of improvements
-	include:
-	<ul>
-	  <li>Fixes for building Qt with libc++ and C++11</li>
-
-	  <li>Fixes for Solid-related crashes</li>
-
-	  <li>Fix battery detection in battery monitor plasmoid</li>
-	</ul>
-      </p>
-
-      <p>The team has also made many releases and upstreamed many fixes
-	and patches. The latest round of releases include:
-	<ul>
-	  <li>KDE SC: 4.9.1 (area51) and 4.8.4 (ports)</li>
-
-	  <li>Qt: 4.8.3 (area51)</li>
-
-	  <li>PyQt: 4.9.4 (area51); QScintilla 2.6.2 (area51); SIP:
-	    4.13.3 (area51)</li>
-
-	  <li>Calligra: 2.4.3, 2.5-RC2, 2.5.0. 2.5.1, 2.5.2 (area51) and
-	    2.4.3, 2.5.0, 2.5.1 (ports)</li>
-
-	  <li>Amarok: 2.6.0 (area51)</li>
-
-	  <li>CMake: 2.8.9 (ports)</li>
-
-	  <li>Digikam (and KIPI-plugins): 2.7.0, 2.8.0, 2.9.0 (area51)
-	    and 2.7.0, 2.9.0 (ports)</li>
-
-	  <li>QtCreator: 2.6.0-beta (area51)</li>
-
-	  <li>many smaller ports</li>
-	</ul>
-      </p>
-
-      <p>The team is always looking for more testers and porters so
-	please contact us at kde@FreeBSD.org and visit our home page at
-	<a href="http://FreeBSD.kde.org" shape="rect">http://FreeBSD.kde.org</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Please see 2012 Q4 Status Report</li><li>Updating out-of-date ports, see
-	<a href="http://portscout.FreeBSD.org/kde@freebsd.org.html" shape="rect">PortScout</a>
-	for a list</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree approaches 24,000 ports, while the PR count
-	still is above 1000.</p>
-
-      <p>In Q3 we added 2 new committers and took in two commits bit
-	for safe keeping.</p>
-
-      <p>The Ports Management team had performed multiple -exp runs,
-	verifying how base system updates may affect the ports tree,
-	as well as providing QA runs for major ports updates.</p>
-
-      <p>Beat Gaetzi took over the role of sending out fail mails, a
-	role that Pav Lucistnik had previously held. Beat also undertook
-	the task of converting the Ports tree from CVS to Subversion.</p>
-
-      <p>Florent Thoumie stepped down from his role on portmgr, he was
-	instrumental in maintaining the legacy pkg_* code.</p>
-    <h3>Open tasks:</h3><ol><li>Most ports PRs are assigned, we now need to focus on
-	testing, committing and closing.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="FreeBSD-Developer-Summit,-Cambridge,-UK" href="#FreeBSD-Developer-Summit,-Cambridge,-UK" id="FreeBSD-Developer-Summit,-Cambridge,-UK">FreeBSD Developer Summit, Cambridge, UK</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201208DevSummit" title="https://wiki.freebsd.org/201208DevSummit">Developer Summit Home Page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201208DevSummit" title="Developer Summit Home Page">https://wiki.freebsd.org/201208DevSummit</a></td></tr></table><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the end of August, there was an "off-season" Developer
-	Summit held in Cambridge, UK at the University of Cambridge
-	Computer Laboratory. This was a three-day event, with a
-	documentation summit scheduled for the day before.  The three
-	days of the main event were split into three sessions, with two
-	tracks in each.  Some of them even involved ARM developers from
-	the neighborhoods which proven to be productive, and led to
-	further engagement between the FreeBSD community and ARM.</p>
-
-      <p>The schedule was finalized on the first day, spawning a
-	plethora of topics to discuss, followed by splitting into groups.
-	A short summary from each of the groups was presented in the
-	final session and then published at the event's home page on the
-	FreeBSD wiki. This summit contributed greatly to arriving to a
-	tentative plan for throwing the switch to make clang the default
-	compiler on HEAD. This was further discussed on the mailing list,
-	and has now happened, bringing us one big step closer to a
-	GPL-free FreeBSD 10. As part of the program, an afternoon of short
-	talks from researchers in the Cambridge Computer Laboratory
-	involved either operating systems work in general or FreeBSD in
-	particular. Robert Watson showed off a tablet running FreeBSD on a
-	MIPS-compatible soft-core processor running on an Altera
-	FPGA.</p>
-
-      <p>In association with the event, a dinner was hosted by St. John's
-	college and co-sponsored by Google and the FreeBSD Foundation. The
-	day after the conference, a trip was organized to Bletchley Park,
-	which was celebrating Turing's centenary in 2012.</p>
-    <hr /><br /><h1><a name="FreeBSD-in-Google-Summer-of-Code" href="#FreeBSD-in-Google-Summer-of-Code" id="FreeBSD-in-Google-Summer-of-Code">FreeBSD in Google Summer of Code</a></h1><br /><h2><a name="Google-Summer-of-Code-2012" href="#Google-Summer-of-Code-2012" id="Google-Summer-of-Code-2012">Google Summer of Code 2012</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/projects/summerofcode.html" title="http://www.freebsd.org/projects/summerofcode.html">FreeBSD Summer of Code page</a></td><td>
-	    URL: <a href="http://www.freebsd.org/projects/summerofcode.html" title="FreeBSD Summer of Code page">http://www.freebsd.org/projects/summerofcode.html</a></td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2012" title="https://wiki.freebsd.org/SummerOfCode2012">Summer of Code 2012 projects</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2012" title="Summer of Code 2012 projects">https://wiki.freebsd.org/SummerOfCode2012</a></td></tr></table><p>
-	Contact:
-
-
-	  FreeBSD Summer of Code Administrators
-	 &lt;<a href="mailto:soc-admins@FreeBSD.org">soc-admins@FreeBSD.org</a>&gt;
-	</p>
-      <p>Over the Summer of 2012, FreeBSD were once again granted a
-	place to participate in the Google Summer of Code program. We
-	received a total of 32 project proposals, and were ultimately
-	given 15 slots for university students to work on open source
-	projects mentored by existing FreeBSD developers.</p>
-
-      <p>We were able to accept a wide spread of proposals, covering
-	both the base system and the ports infrastructure. We had
-	students working on file systems, file integrity checking, and
-	parallelization in the ports collection. Students worked on
-	kernel infrastructure, including one project to support CPU
-	resource limits on users, processes and jails, and one student
-	improving the BSD callout(9) and timer facilities. Two students
-	worked on the ARM platform, widely used in embedded systems and
-	smart phones; one student worked on a significant cleanup and
-	improvements to the Flattened Device Tree implementation code,
-	while the other ported FreeBSD to the OMAP3-based BeagleBoard-xM
-	device. One student worked on improving IPv6 support in
-	userland tools, whilst another worked on BIOS emulation for the
-	BHyVE BSD-licensed hypervisor, new in FreeBSD 10. Other students
-	worked on EFI boot support, userland lock profiling and an
-	automated kernel crash reporting system.</p>
-
-      <p>Overall, a significant proportion of the code produced has
-	or will be integrated into FreeBSD in one form or another. All of
-	the work is available in our Summer Of Code Subversion
-	repository, and some of the work has already been merged back
-	into the main repositories.</p>
-
-      <p>FreeBSD is once again grateful to Google for being selected to
-	participate in Summer of Code 2012.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2012-10-2012-12.html b/website/content/en/status/report-2012-10-2012-12.html
deleted file mode 100644
index 759d4ddcc9..0000000000
--- a/website/content/en/status/report-2012-10-2012-12.html
+++ /dev/null
@@ -1,1045 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between October and
-      December 2012. This is the last of four reports planned for 2012.</p><p>Highlights from this status report include a very successful
-      EuroBSDCon 2012 conference and associated FreeBSD Developer Summit,
-      both held in Warsaw, Poland. Other highlights are several projects
-      related to the FreeBSD port to the ARM architecture, extending
-      support for platforms, boards and CPUs, improvements to the
-      performance of the pf(4) firewall, and a new native iSCSI target.</p><p>Thanks to all the reporters for the excellent work! This report
-      contains 27 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering the period between January
-      and March 2013 is April 21st, 2013.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BHyVe">BHyVe</a></li><li><a href="#Native-iSCSI-Target">Native iSCSI Target</a></li><li><a href="#NFS-Version-4">NFS Version 4</a></li><li><a href="#pxe_http----booting-FreeBSD-from-apache">pxe_http -- booting FreeBSD from apache</a></li><li><a href="#UEFI">UEFI</a></li><li><a href="#Unprivileged-install-and-image-creation">Unprivileged install and image creation</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#BSD-licenced-patch(1)">BSD-licenced patch(1)</a></li><li><a href="#bsdconfig(8)">bsdconfig(8)</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Documentation-Engineering">FreeBSD Documentation Engineering</a></li><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#Postmaster">Postmaster</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#AMD-GPUs-kernel-modesetting-support">AMD GPUs kernel-modesetting support</a></li><li><a href="#Common-Flash-Interface-(CFI)-driver-improvements">Common Flash Interface (CFI) driver improvements</a></li><li><a href="#SMP-Friendly-pf(4)">SMP-Friendly pf(4)</a></li><li><a href="#Unmapped-I/O">Unmapped I/O</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Compiler-improvements-for-FreeBSD/ARMv6">Compiler improvements for FreeBSD/ARMv6</a></li><li><a href="#FreeBSD-on-AARCH64">FreeBSD on AARCH64</a></li><li><a href="#FreeBSD-on-BeagleBone">FreeBSD on BeagleBone</a></li><li><a href="#FreeBSD-on-Raspberry-Pi">FreeBSD on Raspberry Pi</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Xfce">Xfce</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#EuroBSDcon-2012">EuroBSDcon 2012</a></li><li><a href="#FreeBSD-Developer-Summit,-Warsaw">FreeBSD Developer Summit, Warsaw</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BHyVe" href="#BHyVe" id="BHyVe">BHyVe</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/BHyVe" title="https://wiki.FreeBSD.org/BHyVe"></a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/BHyVe" title="">https://wiki.FreeBSD.org/BHyVe</a></td></tr><tr><td><a href="http://www.bhyve.org/" title="http://www.bhyve.org/"></a></td><td>
-	    URL: <a href="http://www.bhyve.org/" title="">http://www.bhyve.org/</a></td></tr></table><p>
-	Contact:
-	  Neel
-	  Natu
-	 &lt;<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>BHyVe is a type-2 hypervisor for FreeBSD/amd64 hosts with Intel
-	VT-x and EPT CPU support. The bhyve project branch was merged
-	into CURRENT on Jan 18. Work is progressing on performance, ease
-	of use, AMD SVM support, and being able to run non-FreeBSD operating
-	systems.</p>
-    <h3>Open tasks:</h3><ol><li>1. Booting Linux/*BSD/Windows</li><li>2. Moving the codebase to a more modular design consisting
-	of a small base and loadable modules</li><li>3. Various hypervisor features such as suspend/resume/live
-	migration/sparse disk support</li></ol><hr /><h2><a name="Native-iSCSI-Target" href="#Native-iSCSI-Target" id="Native-iSCSI-Target">Native iSCSI Target</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the October-December time period, the Native iSCSI
-	Target project progressed to the working prototype stage. Most of
-	this time was spent writing kernel-based part, an iSCSI frontend
-	to the CAM Target Layer. The frontend handles iSCSI Full Feature
-	phase after ctld(8) hands off the connection. The istgt-derived
-	code in ctld(8) was rewritten from scratch; now it's much shorter
-	and more readable. The ctladm(8) utility gained iSCSI-specific
-	subcommands to handle tasks such as listing iSCSI sessions or
-	forcing disconnection. The target works correctly with the FreeBSD
-	initiator.</p>
-    <hr /><h2><a name="NFS-Version-4" href="#NFS-Version-4" id="NFS-Version-4">NFS Version 4</a></h2><p>
-	Contact:
-	  Rick
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>&gt;
-	</p>
-      <p>The NFSv4.1 client, including support for pNFS for the Files
-	Layout only, has now been committed to head/current. Work on
-	NFSv4.1 server support has just been started and will hopefully
-	be ready for head/current this summer. The client side disk
-	caching of delegated files is progressing and the code is under
-	projects/nfsv4-packrats in the subversion repository. Someone is
-	working on server side referrals and, as such, I hope this might
-	make it into 10.0 as well.</p>
-    <hr /><h2><a name="pxe_http----booting-FreeBSD-from-apache" href="#pxe_http----booting-FreeBSD-from-apache" id="pxe_http----booting-FreeBSD-from-apache">pxe_http -- booting FreeBSD from apache</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/user/sbruno/pxe_http_head/" title="http://svnweb.FreeBSD.org/base/user/sbruno/pxe_http_head/">svn repo of project</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/user/sbruno/pxe_http_head/" title="svn repo of project">http://svnweb.FreeBSD.org/base/user/sbruno/pxe_http_head/</a></td></tr></table><p>
-	Contact:
-	  Sean
-	  Bruno
-	 &lt;<a href="mailto:sbruno@FreeBSD.org">sbruno@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently works with VirtualBox VMs and Apache 2.2 port.</p>
-    <h3>Open tasks:</h3><ol><li>Lots and lots of compile warnings exist with clang and gcc.
-	This really needs to be investigated.</li><li>Better support for other webservers. Currently needs Apache
-	to work.</li><li>Needs another pass at basic documentation. Current
-	documentation is actually quite good from the original</li><li>Network stack needs audit. I'm not sure if the
-	HTTP/TCP/UDP/IP code is original or based on something
-	else.</li></ol><hr /><h2><a name="UEFI" href="#UEFI" id="UEFI">UEFI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/UEFI" title="https://wiki.FreeBSD.org/UEFI"></a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/UEFI" title="">https://wiki.FreeBSD.org/UEFI</a></td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/projects/uefi/" title="http://svnweb.FreeBSD.org/base/projects/uefi/"></a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/projects/uefi/" title="">http://svnweb.FreeBSD.org/base/projects/uefi/</a></td></tr></table><p>
-	Contact:
-	  Benno
-	  Rice
-	 &lt;<a href="mailto:benno@FreeBSD.org">benno@FreeBSD.org</a>&gt;
-	</p>
-      <p>There is code in the projects/uefi branch that can build a
-	working 64-bit loader for UEFI. This loader can load a kernel and
-	boot to a mountroot prompt on a serial console on a system with
-	&#8804; 1GB of RAM. Full multiuser has not yet been tested. Work is
-	progressing towards having a working syscons. The issue
-	preventing boot on systems with &gt; 1GB of RAM has not yet been
-	found. UEFI-compatible boot media can be generated using in-tree
-	tools, however there are issues with detecting the CD filesystem
-	and using it as the load default. The 64-bit UEFI loader can load
-	a 32-bit kernel but currently cannot hand over to it due to a
-	lack of code to switch to 32-bit mode. Further research is
-	required into Secure Boot.</p>
-    <hr /><h2><a name="Unprivileged-install-and-image-creation" href="#Unprivileged-install-and-image-creation" id="Unprivileged-install-and-image-creation">Unprivileged install and image creation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>In order to make it easier to build releases and embedded
-	system disk images I have been adding infrastructure to allow
-	the install and packaging stages to the FreeBSD build progress to
-	run without root privilege. To this end I have added two
-	options to the toplevel build system: The
-	<tt>-DDB_FROM_SRC</tt> option allows the install to proceed
-	when the required set of passwd and group entires does not
-	match the host system. The <tt>-DNO_ROOT</tt> option causes
-	files to be installed as the running user and for metadata such
-	as owner, group, suid bits, and file flags to be logged in a
-	<tt>${DESTDIR}/METALOG</tt> file.</p>
-
-      <p>This work required the import of NetBSD's <tt>mtree</tt> and
-	the addition of a number of features from NetBSD to
-	<tt>install</tt>. I have added all FreeBSD features to NetBSD's
-	<tt>mtree</tt> and imported it as <tt>nmtree</tt>. Before FreeBSD
-	10.0 is released I will replace our version. I have also added
-	all required features to <tt>install</tt>. Changes to
-	<tt>makefs</tt> were required to parse the contents of the
-	<tt>METALOG</tt> file.</p>
-
-      <p>These new features required importing new versions of the
-	pwcache(3) and vis(3) APIs from NetBSD so those portions of
-	libc.</p>
-
-      <p>In addition to modifying build infrastructure to use the new
-	features of <tt>mtree</tt> and <tt>install</tt>. I corrected a
-	number of cases of files being installed by programs other than
-	<tt>install</tt> or being installed more than once. A few known
-	instances of duplicate directories in the output exist, but the
-	results are usable in some contexts.</p>
-
-      <p>I plan to MFC these changes as far back as the stable/8
-	branch to make it possible to build all supported releases
-	without root privilege.</p>
-
-      <p>This work was sponsored by DARPA and AFRL.</p>
-    <h3>Open tasks:</h3><ol><li>Add support for <tt>-DNO_ROOT</tt> to
-	<tt>src/release/Makefile</tt> so that releases can be built
-	without root privilege.</li><li>Create a tool to install partition tables and file system
-	images in disk image files without the use of <tt>mdctl</tt>,
-	<tt>gpart</tt>, and <tt>dd</tt>.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="BSD-licenced-patch(1)" href="#BSD-licenced-patch(1)" id="BSD-licenced-patch(1)">BSD-licenced patch(1)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/bsd-patch/" title="http://code.google.com/p/bsd-patch/">Home for BSD patch (deprecated)</a></td><td>
-	    URL: <a href="http://code.google.com/p/bsd-patch/" title="Home for BSD patch (deprecated)">http://code.google.com/p/bsd-patch/</a></td></tr></table><p>
-	Contact:
-	  Pedro
-	  Giffuni
-	 &lt;<a href="mailto:pfg@FreeBSD.org">pfg@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Gabor
-	  Kovesdan
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Xin
-	  Li
-	 &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD has been using for a while a very old version of GNU
-	patch that is partially under the GPLv2. The original GNU patch
-	utility is based on an initial implementation by Larry Wall that
-	was not actually copyleft. OpenBSD did many enhancements to an
-	older non-copyleft version of patch, this version was later
-	adopted and further refined by DragonFlyBSD and NetBSD but there
-	was no centralized development of the tool and FreeBSD kept working
-	independently. In less than a week we took the version in
-	DragonFlyBSD and adapted the FreeBSD enhancements to make it behave
-	nearer to the version used natively in FreeBSD. Most of the work was
-	done by Pedro Giffuni, adapting patches from sepotvin@ and ed@,
-	and additional contributions were done by Christoph Mallon, Gabor
-	Kovesdan and Xin Li. As a result of this we now have a new
-	version of patch committed in head/usr.bin/patch that you can try
-	by using WITH_BSD_PATCH in your builds. The new patch(1) doesn't
-	support the FreeBSD-specific -I and -S options which don't seem
-	necessary. In GNU patch -I actually means 'ignore whitespaces'
-	and we now support it too.</p>
-    <h3>Open tasks:</h3><ol><li>Testing.  A lot more testing.</li></ol><hr /><h2><a name="bsdconfig(8)" href="#bsdconfig(8)" id="bsdconfig(8)">bsdconfig(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.FreeBSD.org/base/head/usr.sbin/bsdconfig/" title="http://svnweb.FreeBSD.org/base/head/usr.sbin/bsdconfig/">Dev Tree</a></td><td>
-	    URL: <a href="http://svnweb.FreeBSD.org/base/head/usr.sbin/bsdconfig/" title="Dev Tree">http://svnweb.FreeBSD.org/base/head/usr.sbin/bsdconfig/</a></td></tr><tr><td><a href="http://freshports.org/sysutils/bsdconfig/" title="http://freshports.org/sysutils/bsdconfig/">Ports Tree</a></td><td>
-	    URL: <a href="http://freshports.org/sysutils/bsdconfig/" title="Ports Tree">http://freshports.org/sysutils/bsdconfig/</a></td></tr><tr><td><a href="http://druidbsd.sf.net/download/bsdconfig/" title="http://druidbsd.sf.net/download/bsdconfig/">Dev Depot</a></td><td>
-	    URL: <a href="http://druidbsd.sf.net/download/bsdconfig/" title="Dev Depot">http://druidbsd.sf.net/download/bsdconfig/</a></td></tr></table><p>
-	Contact:
-	  Devin
-	  Teske
-	 &lt;<a href="mailto:dteske@FreeBSD.org">dteske@FreeBSD.org</a>&gt;
-	</p>
-      <p>bsdconfig(8) is actively being developed in HEAD under the
-	WITH_BSDCONFIG build-requirement. Snapshots are occasionally
-	taken and made available through the ports system to make testing
-	on 9.0-RELEASE or higher easier on the testers. Currently HEAD is
-	far beyond the version 0.7.3 sitting in ports. Upcoming changes
-	will push this to version 0.8 bringing in the necessary
-	frameworks required for in-depth package management and
-	distribution maintenance (read: one step closer to full 1.0
-	release).</p>
-    <hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact:
-	  Core Team
-	 &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the fourth quarter, the Core Team granted access for 7 new
-	committers, and took 1 commit bit in for safekeeping.</p>
-
-      <p>The Core Team oversaw the response to the security incident in
-	November in cooperation with the security team, port managers,
-	and cluster administrators. For more information on the fallouts
-	and response see the
-	<a href="http://www.FreeBSD.org/news/2012-compromise.html" shape="rect">
-	  official announcement</a>. As a result, 9.1-RELEASE was delayed
-	until late December and was released with a limited set of binary
-	packages. The Core Team continues to work with developers to
-	rebuild, review, and restore the package building infrastructure
-	along with redports/QAT.</p>
-    <hr /><h2><a name="FreeBSD-Documentation-Engineering" href="#FreeBSD-Documentation-Engineering" id="FreeBSD-Documentation-Engineering">FreeBSD Documentation Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/internal/doceng.html" title="http://www.FreeBSD.org/internal/doceng.html">Documentation Engineering Team Charter</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/internal/doceng.html" title="Documentation Engineering Team Charter">http://www.FreeBSD.org/internal/doceng.html</a></td></tr></table><p>
-	Contact:
-	  Glen
-	  Barber
-	 &lt;<a href="mailto:gjb@FreeBSD.org">gjb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Marc
-	  Fonvieille
-	 &lt;<a href="mailto:blackend@FreeBSD.org">blackend@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	</p>
-      <p>The translations/, projects/ and user/ directories of the doc
-	repository have been opened with the announced policies in
-	effect. These branches are now actively used for translations
-	work, editing the upcoming printed version of the Handbook,
-	and some doc infrastructure improvements.</p>
-
-      <p>The next phase of the infrastructure improvements is in
-	progress. It will migrate to real XML tools (with the exception
-	of Jade) for validation and rendering. At the same time, the
-	DocBook schema will be updated to 4.5.</p>
-
-      <p>After long discussions, Google Analytics has been enabled on
-	FreeBSD.org webpages but access to statistical data has to be
-	solicited from the Documentation Engineering Team on an
-	individual and one time basis.</p>
-
-      <p>Since July, we have added two doc committers and one
-	translator.</p>
-    <h3>Open tasks:</h3><ol><li>Help the ongoing work on printed edition of the
-	Handbook.</li><li>Finish the migration to XML tools.</li></ol><hr /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>A strong year-end <a href="http://www.FreeBSDFoundation.org/announcements.shtml#fundraising" shape="rect">
-	  fundraising campaign</a> led to the raising $770,000 in 2012.
-	Thank you to everyone who made a donation to support FreeBSD!</p>
-
-      <p>We published our <a href="http://www.FreeBSDFoundation.org/press/2012Dec-newsletter.shtml" shape="rect">
-	  year-end newsletter</a> that highlighted everything we did to
-	support the FreeBSD Project and community during the second half of
-	the year.</p>
-
-      <p>We were a Gold Sponsor for EuroBSDCon. We also attended the
-	conference and developer summit. Erwin Lansing organized and
-	chaired the Ports and Package Summit and Vendor Summit at
-	EuroBSDCon 2012. We attended MeetBSD developer summit
-	November 2012.</p>
-
-      <p>George Neville-Neil organized and the Foundation sponsored the
-	Bay Area Vendor Summit November 2012. We were represented at
-	LISA.</p>
-
-      <p>Kirk McKusick taught a tutorial and gave a keynote at EuroBSDCon
-	2012, and Justin Gibbs gave a talk at ZFS Day, October 2012.</p>
-
-      <p>We talked to DNS server software vendors and participated in
-	discussions on our DNS implementation, specifically with regard
-	to DNSSEC validation, at CENTR Tech September 2012 (Amsterdam,
-	the Netherlands) and EuroBSDCon.</p>
-
-      <p>We visited companies to discuss their FreeBSD use and to help
-	facilitate collaboration with the Project.</p>
-
-      <p>Robert Watson published <a href="http://queue.acm.org/detail.cfm?id=2430732" shape="rect">
-	  ACM Queue and Communications of the ACM: A decade of OS
-	  access-control extensibility</a> and Kirk McKusick
-	published <a href="http://queue.acm.org/detail.cfm?id=2367378" shape="rect">
-	  ACM Queue and Communications of the ACM: Disks from the
-	  Perspective of a File System</a>.</p>
-
-      <p>We negotiated/supervised Foundation funded projects: porting
-	FreeBSD to the Efika ARM platform, Capsicum Component Framework,
-	Native iSCSI Target implementation, and EUFI.</p>
-
-      <p>We negotiated/supervised/funded hardware needs in FreeBSD
-	co-location centers.</p>
-
-      <p>Many board members provided support for recovery efforts
-	following the security compromise of FreeBSD.org systems in late
-	2012.</p>
-
-      <p>We completed negotiation and provided legal counsel for the
-	new website privacy policy for the FreeBSD Project.</p>
-
-      <p>We are now an industrial partner in the
-	Cambridge/Imperial/Edinburgh EPSRC REMS project on the Rigorous
-	Engineering of Mainstream Systems.</p>
-
-      <p>We coordinated the Foundation's discussion of Jira/Java;
-	conclusion, will continue to be supportive of OpenJDK and not
-	restart proprietary JDK support.</p>
-
-      <p>We implemented a donor management database to help with our
-	fundraising efforts. We also began working on automating the
-	donation process.</p>
-
-      <p>We started the Faces of FreeBSD Series where we share the story of
-	a Foundation grant recipient periodically. This allows us to
-	spotlight people who received Foundation funding to work on
-	development projects, run conferences, travel to conferences,
-	and advocate for FreeBSD.</p>
-
-      <p>We hired two technical staff members.</p>
-    <hr /><h2><a name="Postmaster" href="#Postmaster" id="Postmaster">Postmaster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  David
-	  Wolfskill
-	 &lt;<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</a>&gt;
-	</p>
-	<p>The postmaster team has expanded, with the addition of
-	  Florian Smeets (flo@FreeBSD.org).</p>
-
-	<p>We have implemented a Mailman "handler" to drop duplicate
-	  messages when both copies are sent to the same list (under
-	  both the "long" (e.g., "freebsd-current") and "short"
-	  (e.g., "current") names).</p>
-
-	<p>We have created several new mailing lists:</p>
-	<ul>
-	  <li>freebsd-course: educational course on FreeBSD</li>
-	  <li>freebsd-numerics: Discussions of high quality
-	    implementation of libm functions.</li>
-	  <li>freebsd-snapshots: FreeBSD Development Snapshot
-	    Announcements</li>
-	  <li>freebsd-tcltk: FreeBSD-specific Tcl/Tk discussions</li>
-	</ul>
-
-	<p>We have also removed old mailing lists:</p>
-	<ul>
-	  <li>freebsd-binup</li>
-	  <li>freebsd-www (merged into freebsd-doc)</li>
-	</ul>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="AMD-GPUs-kernel-modesetting-support" href="#AMD-GPUs-kernel-modesetting-support" id="AMD-GPUs-kernel-modesetting-support">AMD GPUs kernel-modesetting support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/AMD_GPU" title="https://wiki.FreeBSD.org/AMD_GPU">Project status on the wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/AMD_GPU" title="Project status on the wiki">https://wiki.FreeBSD.org/AMD_GPU</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~kib/misc/ttm.1.patch" title="http://people.FreeBSD.org/~kib/misc/ttm.1.patch">Initial TTM port</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~kib/misc/ttm.1.patch" title="Initial TTM port">http://people.FreeBSD.org/~kib/misc/ttm.1.patch</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Kabaev
-	 &lt;<a href="mailto:kan@FreeBSD.org">kan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jean-S�bastien
-	  P�dron
-	 &lt;<a href="mailto:dumbbell@FreeBSD.org">dumbbell@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Jean-S�bastien P�dron started to port the AMD GPUs driver
-	from Linux to FreeBSD 10-CURRENT in January 2013. This work is based
-	on a previous effort by Alexander Kabaev. Konstantin Belousov
-	provided the initial port of the TTM memory manager.</p>
-
-      <p>As of this writing, the driver is building but the tested
-	device fails to attach.</p>
-
-      <p>Status updates will be posted to the FreeBSD wiki.</p>
-    <hr /><h2><a name="Common-Flash-Interface-(CFI)-driver-improvements" href="#Common-Flash-Interface-(CFI)-driver-improvements" id="Common-Flash-Interface-(CFI)-driver-improvements">Common Flash Interface (CFI) driver improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Common Flash Interface provides a common programming
-	interface for a wide range of NOR flash devices commonly found in
-	embedded systems. I have developed a number of improvements to
-	the cfi(4) device when used on Intel StrataFlash parts.
-	Unnecessary erase cycles are now avoided, devices that require
-	single word writes only write changed words, and multi-word
-	writes are supported for Intel and Sharp devices. Additionally
-	the timeout code has been reworked and no longer imposes unneeded
-	latency on operations taking less than 100us. With all of these
-	changes streaming write speed has improved by more than an order
-	of magnitude. Once these changes are reviewed they will be
-	committed to HEAD.</p>
-
-      <p>This work was sponsored by DARPA and AFRL.</p>
-    <hr /><h2><a name="SMP-Friendly-pf(4)" href="#SMP-Friendly-pf(4)" id="SMP-Friendly-pf(4)">SMP-Friendly pf(4)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Gleb
-	  Smirnoff
-	 &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project is aimed at moving the pf(4) packet filter out of
-	a single mutex, as well as in general improving of the FreeBSD port.
-	The project has reached its main goal. The pf(4) is no longer
-	covered by single mutex and contention on network stack on pf(4)
-	is now very low. The code is production ready. The projects/pf
-	branch had been merged to the head branch and will be available
-	in 10.0-RELEASE.</p>
-    <hr /><h2><a name="Unmapped-I/O" href="#Unmapped-I/O" id="Unmapped-I/O">Unmapped I/O</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~kib/misc/unmapped.13.patch" title="http://people.FreeBSD.org/~kib/misc/unmapped.13.patch">The patch.</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~kib/misc/unmapped.13.patch" title="The patch.">http://people.FreeBSD.org/~kib/misc/unmapped.13.patch</a></td></tr></table><p>
-	Contact:
-	  Jeff
-	  Roberson
-	 &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>A well-known performance problem of FreeBSD on large SMP
-	hardware is the need to invalidate TLB for all CPUs when
-	instantiating and destroying the VMIO buffers. Invalidation is
-	performed by sending inter-processor interrupt broadcast, which
-	disrupts the execution path of each CPU, and induces latency
-	on the request itself. Since most I/O requests processing require
-	creation of the buffers to hold the data in the kernel, TLB
-	invalidation becomes an obstacle for I/O scalability on
-	many-CPU machines.</p>
-
-      <p>The work done for flushing the TLBs is especially meaningless
-	since most mappings created are not used for anything but copying
-	the data from the usermode to the kernel page cache forth and
-	back. Most architectures have already established facilities to
-	perform such copies using much faster techniques, for instance,
-	the direct map on amd64, or specially reserved per-CPU page
-	frames or TLB entries on other architectures.</p>
-
-      <p>Jeff Roberson unified the machine-specific parts of the
-	busdma(9), making a common set of low-level functions available
-	on each architecture. This was committed as r246713. The end
-	result is that the new types of the load functions can be added
-	in the single, machine-independent place. In particular, it is
-	easy to modify the drivers to accept the 'unmapped' bio requests,
-	which lists the vm pages for the device dma engine, instead of
-	the virtual address of the kernel buffer.</p>
-
-      <p>Konstantin Belousov developed the changes for buffer cache
-	which allow the VMIO buffers to not map the referenced pages, and
-	used the feature for UFS. Per-architecture pmap_copy_pages(9)
-	methods were added to facilitate fast copying between user I/O
-	buffers and pages of unmapped buffers. The unmapped buffers
-	create the unmapped bio requests for the drivers, support for
-	which was made possible by Jeff's patch.</p>
-
-      <p>Tests show that even on a small 4-core machine, the system
-	time for reading files on UFS is reduced by 30%.</p>
-    <h3>Open tasks:</h3><ol><li>Test the patch, in particular, on non-x86
-	architectures.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Page">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ja_JP.eucJP subtree has constantly been updated since the
-	last status report.</p>
-
-      <p>In FreeBSD Handbook, translation work of the "users" section has
-	been completed. "linuxemu" and "serialcomms" were updated and
-	subsection "Subversion mirror site" was newly added to "mirrors"
-	section.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work of outdated documents in the
-	<tt>ja_JP.eucJP</tt> subtree.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Compiler-improvements-for-FreeBSD/ARMv6" href="#Compiler-improvements-for-FreeBSD/ARMv6" id="Compiler-improvements-for-FreeBSD/ARMv6">Compiler improvements for FreeBSD/ARMv6</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD/ARM architecture is now supported by the in-tree clang
-	compiler. ARM EABI support is now available for both clang and
-	gcc along with the older and less documented OABI. There are
-	several outstanding issues, once they are fixed EABI will be
-	made default.</p>
-    <h3>Open tasks:</h3><ol><li>Test EABI builds</li><li>Fix exception handling for EABI</li><li>Test clang builds</li><li>Get clang to work natively on EABI-based ARM system.
-	Currently it works only as cross-compiler for ARM EABI.</li></ol><hr /><h2><a name="FreeBSD-on-AARCH64" href="#FreeBSD-on-AARCH64" id="FreeBSD-on-AARCH64">FreeBSD on AARCH64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/zxombie/aarch64-freebsd-sandbox" title="https://github.com/zxombie/aarch64-freebsd-sandbox"></a></td><td>
-	    URL: <a href="https://github.com/zxombie/aarch64-freebsd-sandbox" title="">https://github.com/zxombie/aarch64-freebsd-sandbox</a></td></tr><tr><td><a href="http://www.arm.com/products/tools/models/fast-models/foundation-model.php" title="http://www.arm.com/products/tools/models/fast-models/foundation-model.php"></a></td><td>
-	    URL: <a href="http://www.arm.com/products/tools/models/fast-models/foundation-model.php" title="">http://www.arm.com/products/tools/models/fast-models/foundation-model.php</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has started on porting FreeBSD to AARCH64, ARM's new 64-bit
-	architecture, using the ARMv8 Foundation Model software. GCC and
-	binutils have been ported to FreeBSD and work started on kernel
-	initialization, including MMU setup.</p>
-    <h3>Open tasks:</h3><ol><li>Get the MMU working</li><li>Get system register documentation from ARM</li><li>Port clang AArch64 to FreeBSD</li><li>Bring the code into a FreeBSD project branch</li></ol><hr /><h2><a name="FreeBSD-on-BeagleBone" href="#FreeBSD-on-BeagleBone" id="FreeBSD-on-BeagleBone">FreeBSD on BeagleBone</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Tim
-	  Kientzle
-	 &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Damjan
-	  Marion
-	 &lt;<a href="mailto:dmarion@FreeBSD.org">dmarion@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Brett
-	  Wynkoop
-	 &lt;<a href="mailto:wynkoop@wynn.com">wynkoop@wynn.com</a>&gt;
-	</p>
-      <p>FreeBSD on BeagleBone is benefiting from the general work on ARM
-	stability being done by many people, and is proving to be a nice
-	testbed for our ARMv7 support. All ongoing work is happening now
-	directly in -CURRENT and we expect it to be in pretty good shape
-	by the time 10.0 ships.</p>
-
-      <p>The network driver is now pretty stable; the system should be
-	useful as a small network device.</p>
-
-      <p>Occasional system snapshots are being built and advertised for
-	people to test. Ask on freebsd-arm@ if you'd like to try the
-	newest one.</p>
-    <h3>Open tasks:</h3><ol><li>We need someone to finish the USB driver. Ask if you'd like
-	to take this over.</li><li>MMCSD performance is still rather poor.</li><li>There's been discussion of how to improve the GPIO
-	configuration and pinmux handling to simplify hardware
-	experimentation. If we had more people to help build drivers, we
-	could start supporting some of the BeagleBone capes.</li><li>Mostly we just need people to use it and report any issues
-	they encounter.</li></ol><hr /><h2><a name="FreeBSD-on-Raspberry-Pi" href="#FreeBSD-on-Raspberry-Pi" id="FreeBSD-on-Raspberry-Pi">FreeBSD on Raspberry Pi</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD is running on Raspberry Pi and supports the following
-	peripherals:</p>
-      <ul>
-	<li>USB controller</li>
-	<li>SDHC controller</li>
-	<li>Network</li>
-	<li>Framebuffer (HDMI and composite)</li>
-	<li>GPIO</li>
-	<li>VCHI interface</li>
-      </ul>
-      <p>Videocore tests (OpenGL, video decoding, audio, display access)
-	work with current VCHI driver implementation.</p>
-    <h3>Open tasks:</h3><ol><li>Add DMA mode support to USB driver. Some proof-of-concept
-	code is done but more work required to finish it.</li><li>Re-implement VCHI driver with more FreeBSD-friendly
-	locking.</li><li>Implement more drivers: SPI, PWM, audio.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Haskell" title="http://wiki.FreeBSD.org/Haskell">FreeBSD Haskell wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Haskell" title="FreeBSD Haskell wiki page">http://wiki.FreeBSD.org/Haskell</a></td></tr><tr><td><a href="https://github.com/FreeBSD-haskell/FreeBSD-haskell/" title="https://github.com/FreeBSD-haskell/FreeBSD-haskell/">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-haskell/FreeBSD-haskell/" title="FreeBSD Haskell ports repository">https://github.com/FreeBSD-haskell/FreeBSD-haskell/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�LI
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce that the FreeBSD Haskell Team has
-	updated the Haskell Platform to 2012.4.0.0, GHC to 7.4.2 as well
-	as updated existing ports to their latest stable versions. All
-	Haskell ports are also updated to use new OPTIONS framework, and
-	now, building with dynamic libraries (DYNAMIC) is on by default.
-	GHC also uses GCC 4.6 and binutils 2.22 from ports. We also added
-	a number of new Haskell ports, and their count in FreeBSD Ports tree
-	is now 368.</p>
-    <h3>Open tasks:</h3><ol><li>Test GHC to work with clang/LLVM.</li><li>Commit pending Haskell ports to the FreeBSD Ports tree.</li><li>Add more ports to the Ports Collection.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE/FreeBSD team have continued to improve the experience of
-	KDE software and Qt under FreeBSD. The latest round of improvements
-	include:</p>
-      <ul>
-	<li>Fix handling of Removable property in solid engine</li>
-
-	<li>Fix management of backlight with UPower (requires
-	  acpi_video(4))</li>
-
-	<li>Installing spell-checking dictionaries with a dependency of
-	  KDE-locale ports</li>
-      </ul>
-
-      <p>The team has also made many releases and upstreamed many fixes
-	and patches. The latest round of releases include:</p>
-      <ul>
-	<li>KDE SC: 4.9.2 (area51)</li>
-
-	<li>PyQt: 4.9.5 (area51); SIP: 4.14 (area51)</li>
-
-	<li>KDevelop: 4.4.0, 4.4.1 (area51); KDevPlatform: 1.4.0, 1.4.1
-	  (area51)</li>
-
-	<li>Calligra: 2.5.3, 2.5.4 (area51)</li>
-
-	<li>CMake: 2.8.10.1</li>
-
-	<li>Many smaller ports</li>
-      </ul>
-
-      <p>The team is always looking for more testers and porters so
-	please contact us at kde@FreeBSD.org and visit our home page at
-	<a href="http://FreeBSD.kde.org" shape="rect">http://FreeBSD.kde.org</a>.</p>
-    <h3>Open tasks:</h3><ol><li>Updating out-of-date ports, see
-	<a href="http://portscout.FreeBSD.org/kde@freebsd.org.html" shape="rect">PortScout</a>
-	for a list</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree crossed the threshold of 24,000 ports, while the
-	PR count still is close to 1600.</p>
-
-      <p>In Q4 we added five new committers and took in two commit bits
-	for safe keeping.</p>
-
-      <p>In the tradition of recruiting new portmgr@ at conferences, we
-	added Bernhard Froehlich to our ranks. He is the one responsible
-	for redports.org</p>
-
-      <p>Pav Lucistnik stepped down from his role on portmgr, he was
-	one of our principles doing -exp runs and well known for sending
-	failmails.</p>
-
-      <p>In the well publicised compromise, the pointyhat machines were
-	broken into and subsequently taken down, isolated and sanitised.
-	As a pre-emptive move redports/QAT were also taken down. Work is
-	under way to restore the services.</p>
-
-      <p>Mark Linimon began a from-scratch test install on one of his
-	own spare machines with the purpose of documenting all the
-	missing steps from the portbuild article. While doing so, he
-	further overhauled the codebase to both make it easier to
-	install, and to further refactor it in light of a security review
-	(still ongoing at time of this writing). Once this is complete,
-	the next task will be to reinstall all existing machines from
-	scratch.</p>
-    <h3>Open tasks:</h3><ol><li>Most ports PRs are assigned, we now need to focus on
-	testing, committing and closing.</li></ol><hr /><h2><a name="Xfce" href="#Xfce" id="Xfce">Xfce</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Xfce" title="https://wiki.FreeBSD.org/Xfce"></a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Xfce" title="">https://wiki.FreeBSD.org/Xfce</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>A major update has been made to
-	<strong>Thunar</strong> (file manager for the Xfce Desktop
-	Environment).</p>
-
-      <p><em>1.6.x</em> series introduce lots of improvements, most
-	noticeably is <strong>tabs support</strong>, and the performance
-	has been improved.</p>
-    <h3>Open tasks:</h3><ol><li>Try to fix HSTS (HTTP Strict Transport Security) feature in
-	Midori with Vala 0.12.1 (works fine with Vala &#8805; 0.14.x)</li><li>Replace libxfce4gui (deprecated and not maintained by
-	upstream) by libxfce4ui in order to enhance support for Xfce &#8805;
-	4.10.</li><li>Test core and plugins (panel, Thunar) with GLib &#8805; 4.32
-	(to replace deprecated and removed functions introduced since
-	GLib 2.30).</li><li>Fix gtk-xfce-engine with Gtk+ &#8805; 3.6.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="EuroBSDcon-2012" href="#EuroBSDcon-2012" id="EuroBSDcon-2012">EuroBSDcon 2012</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2012.eurobsdcon.org/" title="http://2012.eurobsdcon.org/">EuroBSDcon 2012 web site</a></td><td>
-	    URL: <a href="http://2012.eurobsdcon.org/" title="EuroBSDcon 2012 web site">http://2012.eurobsdcon.org/</a></td></tr><tr><td><a href="http://www.youtube.com/user/eurobsdcon" title="http://www.youtube.com/user/eurobsdcon">EuroBSDcon YouTube channel</a></td><td>
-	    URL: <a href="http://www.youtube.com/user/eurobsdcon" title="EuroBSDcon YouTube channel">http://www.youtube.com/user/eurobsdcon</a></td></tr></table><p>
-	Contact:
-	  EuroBSDcon
-	  Organizers
-	 &lt;<a href="mailto:oc-2012@eurobsdcon.org">oc-2012@eurobsdcon.org</a>&gt;
-	<br />
-	Contact:
-	  Gabor
-	  Pali
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The 11th European BSD Conference took place in Warsaw, Poland
-	at the Warsaw University of Technology with a large number of
-	visitors. It started up with two tracks of tutorials, featuring
-	FreeNAS, pfSense, DTrace, PF, development of NetBSD drivers, and
-	an overall introduction to the FreeBSD operating system given by
-	Kirk McKusick. There we also had opening and closing keynotes,
-	supplemented with 22 talks on different topics related to FreeBSD,
-	OpenBSD, NetBSD, FreeNAS and PC-BSD: BHyVe, configuration
-	management with puppet, improvements in the OpenBSD cryptographic
-	framework, tuning ZFS, server load balancing in DNS, running FreeBSD
-	on embedded systems, e.g MIPS and ARM, and challenges in identity
-	management and authentication.</p>
-
-      <p>The conference also had a dedicated track presented by the
-	attendees of the FreeBSD developer summit and open to all, where one
-	could learn more about what is happening currently in the
-	Project: results of Google Summer of Code 2012, architectural
-	changes in the FreeBSD documentation tree, ILNP, advancements in
-	package building and development of pkg(8), and a status report
-	on the USB stack.</p>
-    <hr /><h2><a name="FreeBSD-Developer-Summit,-Warsaw" href="#FreeBSD-Developer-Summit,-Warsaw" id="FreeBSD-Developer-Summit,-Warsaw">FreeBSD Developer Summit, Warsaw</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/201210DevSummit" title="http://wiki.FreeBSD.org/201210DevSummit">Home page of the summit</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/201210DevSummit" title="Home page of the summit">http://wiki.FreeBSD.org/201210DevSummit</a></td></tr></table><p>
-	Contact:
-	  Gabor
-	  Pali
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>We had 53 FreeBSD developers and invited guests attending the
-	FreeBSD Developer Summit organized as part of EuroBSDcon 2012 in
-	Warsaw, Poland at the Warsaw University of Technology. This year
-	EuroBSDcon organizers again offered us their generous support in
-	helping with keeping the event running smooth, helping with
-	registrations, renting the venue, and providing food for keeping
-	attendees satisfied and happy.</p>
-
-      <p>The Warsaw developer summit spanned over 3 days and had 9
-	working groups on various topics. We improved last year's layout
-	inherited from the Canadian summits because it has worked well
-	earlier but could use some further refinements. On both the first
-	and second days, we ran the working groups, ranging from the
-	standard matters, discussing issues with the USB stack, the
-	compiler toolchain, the Ports Collection, or the documentation to
-	some experimental ones, e.g. arranging an operating systems
-	course focusing on FreeBSD. In addition to this, similarly to last
-	year, one of the working groups was about gathering vendors to
-	present their ideas and engage in discussion with the developers
-	on their needs from the Project. Finally, on the third day, there
-	were a number of exciting work-in-progress reports given in a
-	dedicated Developer Summit track at the main conference.</p>
-
-      <p>Photos and slides for the most of the talks are available on
-	the home page of the summit.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2013-01-2013-03.html b/website/content/en/status/report-2013-01-2013-03.html
deleted file mode 100644
index c398eb525f..0000000000
--- a/website/content/en/status/report-2013-01-2013-03.html
+++ /dev/null
@@ -1,1272 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between January and
-      March 2013. This is the first of four reports planned for 2013.</p><p>Highlights from this status report include the busy preparations
-      of 8.4-RELEASE, restoration of binary package building, steady
-      progress of several porting efforts, like work on the FreeBSD ports
-      of xorg, GNOME, KDE, and Xfce, bringing FreeBSD to Cubieboard and
-      Hackberry boards, development of ARM and AMD GPU support,
-      improving performance of UFS/FFS and callouts, and introducing a
-      multipath TCP implementation for the network stack.</p><p>Thanks to all the reporters for the excellent work!  This report
-      contains 31 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering the period between April
-      and June 2013 is July 7th, 2013.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeNAS">FreeNAS</a></li><li><a href="#Kernel-Information-in-Process-Core-Dumps">Kernel Information in Process Core Dumps</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugmeister-Team">FreeBSD Bugmeister Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Managers">FreeBSD Port Managers</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#AMD-GPU-Kernel-Mode-Setting-(KMS)-Support">AMD GPU Kernel Mode-Setting (KMS) Support</a></li><li><a href="#Atomic-&quot;close-on-exec&quot;">Atomic "close-on-exec"</a></li><li><a href="#callout(9)-Improvements">callout(9) Improvements</a></li><li><a href="#Multipath-TCP-(MPTCP)-for-FreeBSD">Multipath TCP (MPTCP) for FreeBSD</a></li><li><a href="#racct:-Block-IO-Accounting">racct: Block IO Accounting</a></li><li><a href="#Read-only-Port-of-NetBSD's-UDF-File-System">Read-only Port of NetBSD's UDF File System</a></li><li><a href="#TCP-AO-Authentication-Option">TCP-AO Authentication Option</a></li><li><a href="#UFS/FFS-Performance-Work">UFS/FFS Performance Work</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Improving-the-Documentation-Project-Infrastructre">Improving the Documentation Project Infrastructre</a></li><li><a href="#The-entities-Documentation-Branch">The entities Documentation Branch</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Cubieboard">FreeBSD on Cubieboard</a></li><li><a href="#FreeBSD/arm-Superpages-for-ARMv7">FreeBSD/arm Superpages for ARMv7</a></li><li><a href="#FreeBSD/ARM-Toolchain-Improvements">FreeBSD/ARM Toolchain Improvements</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#PyPy">PyPy</a></li><li><a href="#Wine32-on-FreeBSD/amd64">Wine32 on FreeBSD/amd64</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li><li><a href="#xorg-on-FreeBSD">xorg on FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BXR.SU-&#8212;-Super-User's-BSD-Cross-Reference">BXR.SU &#8212; Super User's BSD Cross Reference</a></li><li><a href="#mdoc.su-&#8212;-Short-Manual-Page-URLs">mdoc.su &#8212; Short Manual Page URLs</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="FreeNAS" href="#FreeNAS" id="FreeNAS">FreeNAS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeNAS.org/" title="http://www.FreeNAS.org/"></a></td><td>
-	    URL: <a href="http://www.FreeNAS.org/" title="">http://www.FreeNAS.org/</a></td></tr></table><p>
-	Contact:
-	  Alfred
-	  Perlstein
-	 &lt;<a href="mailto:alfred@FreeBSD.org">alfred@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Josh
-	  Paetzel
-	 &lt;<a href="mailto:jpaetzel@FreeBSD.org">jpaetzel@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeNAS 8.3.1-RELEASE-p2 will hit Sourceforge the second week
-	of April, and should end up as the last FreeNAS release based on
-	FreeBSD�8.X.  It is currently the only Free Open Source NAS
-	product available with any form of ZFS encryption (provided by
-	GELI).</p>
-    <h3>Open tasks:</h3><ol><li>The team is hard at work on getting a FreeBSD�9.X-based
-	release of FreeNAS ready.  Currently there are several nightly
-	snapshots available.</li><li>Add HAST to the webinterface.</li><li>Migrate to NFSv4.</li><li>Integrate foundation sponsored kernel iSCSI target.</li></ol><hr /><h2><a name="Kernel-Information-in-Process-Core-Dumps" href="#Kernel-Information-in-Process-Core-Dumps" id="Kernel-Information-in-Process-Core-Dumps">Kernel Information in Process Core Dumps</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Mikolaj
-	  Golub
-	 &lt;<a href="mailto:trociny@freebsd.org">trociny@freebsd.org</a>&gt;
-	</p>
-      <p>When doing postmortem analysis of a crashed process it is
-	sometimes very useful to have kernel information about the process
-	at the moment of the crash, like open file descriptors or resource
-	limits.  For a live process this information can be obtained via
-	<tt>sysctl(3)</tt> interface e.g. using <tt>procstat(1)</tt>.</p>
-
-      <p>The aim of the project is to add additional notes to a process
-	core dump, which include process information from the kernel at
-	the moment of the process crash, teach <tt>libprocstat(3)</tt>
-	to extract this information and make <tt>procstat(1)</tt> use
-	this functionality.</p>
-
-      <p>At the moment all necessary code changes are committed to HEAD
-	and are going to be merge to stable/9 in 1 month.</p>
-    <hr /><h2><a name="Native-iSCSI-Stack" href="#Native-iSCSI-Stack" id="Native-iSCSI-Stack">Native iSCSI Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="https://wiki.freebsd.org/Native%20iSCSI%20target"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="">https://wiki.freebsd.org/Native%20iSCSI%20target</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Focus of the project was extended to also include a new iSCSI
-	initiator.  Compared to the old one, it is more reliable, much
-	more user-friendly, and somewhat faster.  It uses exactly the
-	same configuration file format as the old one to make migration
-	easier.</p>
-
-      <p>As for the target side, it was verified to work properly
-	against major initiators (FreeBSD, Linux, Solaris, Windows and VMWare
-	ESX).</p>
-
-      <p>This project is being sponsored by FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>RDMA support, for both the target and the initiator.</li><li>Performance optimization.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugmeister-Team" href="#FreeBSD-Bugmeister-Team" id="FreeBSD-Bugmeister-Team">FreeBSD Bugmeister Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Eitan
-	  Adler
-	 &lt;<a href="mailto:eadler@FreeBSD.org">eadler@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-    <p>The FreeBSD Bugmeister Team are continuing to evaluate options for
-	alternate bug trackers and have narrowed their choices to two
-	possibilities: Bugzilla and roundup.</p>
-
-    <p>The number of non-ports PRs have remained relatively static over
-	the last three months, with as many coming in as being closed.
-	The number of ports PRs have increased recently, largely due to
-	the ports freeze for the upcoming 8.4-RELEASE.</p>
-
-    <p>The Bugmeister team continue work on trying to make the contents
-	of the GNATS PR database cleaner, more accessible and easier for
-	committers to find and resolve PRs, by tagging PRs to indicate
-	the areas involved, and by ensuring that there is sufficient
-	info within each PR to resolve each issue.</p>
-
-    <p>As always, anybody interested in helping out with the PR queue is
-	welcome to join us in <tt>#freebsd-bugbusters</tt> on EFnet.  We
-	are always looking for additional help, whether your interests
-	lie in triaging incoming PRs, generating patches to resolve
-	existing problems, or simply helping with the database
-	housekeeping (identifying duplicate PRs, ones that have already
-	been resolved, etc).  This is a great way of getting more
-	involved with FreeBSD!</p>
-    <h3>Open tasks:</h3><ol><li>Finalize the decision of which new bug tracker to
-	use.</li><li>Get more users involved with triaging PRs as they come
-	in.</li><li>Assist committers with closing PRs.</li></ol><hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Core Team
-	 &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>At the end of 2012, the Core Team approved using Google
-	Analytics on the Project web site to enable the Documentation
-	Engineering Team to collect statistics on its usage for better
-	profiling.  In the first quarter of 2013, the Core Team worked
-	with the Documentation Engineering Team to finalize the
-	associated policies.</p>
-
-      <p>Due to some debates around the political correctness of quotes
-	added for the fortune(6) utility, the corresponding data file
-	has been removed from the base system in -CURRENT.</p>
-
-      <p>In light of the security incident, the liaison role between the
-	Core Team and the Security Team has been restored, with Gavin
-	Atkinson assuming this role.  The Core Team work hard on
-	resolving the current situation of the binary package building
-	cluster and the associated security problems in tight
-	cooperation with the Ports Management Team, Cluster
-	Administators, and the FreeBSD Foundation Board.  The <a href="http://www.FreeBSD.org/news/2012-compromise.html" shape="rect">compromise page</a>
-	is kept updated on the results.</p>
-
-      <p>The FreeBSD Project submitted an application for Google Summer of
-	Code this year again.</p>
-
-      <p>There was access granted for 2 new committers and 1 commit bit
-	was taken for safekeeping in this quarter.</p>
-    <hr /><h2><a name="FreeBSD-Port-Managers" href="#FreeBSD-Port-Managers" id="FreeBSD-Port-Managers">FreeBSD Port Managers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="http://www.freebsd.org/doc/en/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/" title="http://portsmon.freebsd.org/"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/" title="">http://portsmon.freebsd.org/</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/" title="http://www.freebsd.org/portmgr/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/" title="">http://www.freebsd.org/portmgr/</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree contains approximately 24,300 ports, while the
-	PR count still is close to 1600.</p>
-
-      <p>In the first quarter we added 4 new committers, took in 1
-	commit bit for safe keeping, and re-instated 1 commit bit.</p>
-
-      <p>In February, Mark Linimon (linimon) stepped down from his
-	duties in the team.  Mark had been the second longest serving member of
-	the team.  Mark had spent many long hours refactoring and
-	documenting the portbuild software to ensure that pointyhat
-	services could be restored.</p>
-
-      <p>After a security review, redports.org was turned back on,
-	restoring Tinderbox services to contributors, along with post
-	commit QATs.  In addition, pointyhat infrastructure had also
-	undergone a review and work begain on restoring the package
-	build system.</p>
-
-      <p>Erwin Lansing (erwin) and Martin Wilke (miwi) took on the
-	principle roles of getting the portbuild software installed and
-	running on pointyhat.  As a result of all their hard work,
-	portmgr@ was finally able to resume doing -exp runs, preparing
-	packages for the upcoming 8.4 release, as well as getting a set
-	of 9.1 packages retroactively prepared.</p>
-
-      <p>After many long years of being the defacto standard for the
-	Project, CVS support for the ports tree officially ended on
-	February 28.</p>
-
-      <p>The ports tree was tagged with <tt>RELEASE_7_EOL</tt>, to
-	coincide with the end of life for FreeBSD�7.X.</p>
-
-      <p>Beat Gaetzi (beat) stepped down from his duties on portmgr@ in
-	March.  Among his notable contributions was the task of migrating
-	the Ports Tree from the old CVS repo to Subversion.</p>
-
-      <p>Bryan Drewery (bdrewery) joined the Ports Management team in
-	March, bringing with him his wealth of knowledge and skill from
-	maintaining portupgrade, portmaster, assisting with pkgng, as
-	well as co-developing poudriere.</p>
-    <h3>Open tasks:</h3><ol><li>Most ports PRs are assigned, we now need to focus on
-	testing, committing and closing.</li></ol><hr /><h2><a name="FreeBSD-Postmaster-Team" href="#FreeBSD-Postmaster-Team" id="FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  David
-	  Wolfskill
-	 &lt;<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the first quarter of 2013, the FreeBSD Postmaster Team has
-	implemented the following items that may be interest of the
-	general public:</p>
-
-      <ul>
-	<li>Changes in configuration of Mailman-managed lists: allow to
-	  accept the <tt>application/pkcs7-signature</tt> MIME type (in
-	  addition to the <tt>application/x-pkcs7-signature</tt> MIME
-	  type), thus permitting S/MIME signatures on list mail.</li>
-
-	<li>New lists: <tt>freebsd-ops-announce</tt> &#8212;
-	  announcements of infrastructure issues, and <tt>freebsd-pkg</tt>
-	  &#8212; discussion of binary package management and package
-	  tools.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/releases/8.4R/schedule.html" title="http://www.freebsd.org/releases/8.4R/schedule.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releases/8.4R/schedule.html" title="">http://www.freebsd.org/releases/8.4R/schedule.html</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD 8.4-RC1 just got out the door and we are planning RC2.  A
-	couple of critical fixes have come in that will be included in
-	RC2.  The schedule has slipped about 10 days so far.  We are
-	expecting the final release by the end of April.  Packages for 8.4
-	have been provided by a fully operational package building
-	cluster.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="AMD-GPU-Kernel-Mode-Setting-(KMS)-Support" href="#AMD-GPU-Kernel-Mode-Setting-(KMS)-Support" id="AMD-GPU-Kernel-Mode-Setting-(KMS)-Support">AMD GPU Kernel Mode-Setting (KMS) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/AMD_GPU" title="https://wiki.freebsd.org/AMD_GPU">Project status on the wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/AMD_GPU" title="Project status on the wiki">https://wiki.freebsd.org/AMD_GPU</a></td></tr></table><p>
-	Contact:
-	  Jean-S�bastien
-	  P�dron
-	 &lt;<a href="mailto:dumbbell@FreeBSD.org">dumbbell@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  J.R.
-	  Oldroyd
-	 &lt;<a href="mailto:jr@opal.com">jr@opal.com</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project progressed well since February:</p>
-
-      <ul>
-	<li>Konstantin committed his TTM port to 10-CURRENT.</li>
-
-	<li>With the help of John Baldwin (jhb) and Andriy Gapon (avg),
-	  the Video BIOS situation greatly improved: the
-	  <tt>radeonkms</tt> driver reads the BIOS shadow copy if the
-	  video card is the primary one, or query the PCI expansion ROM
-	  otherwise.  In the end, this code will be probably committed
-	  to the PCI driver so that other video drivers benefit from
-	  it.</li>
-
-	<li>Andriy also reported several problems with the I2C code.
-	  Now that they are fixed, the monitors plugged into DVI and
-	  HDMI connectors are detected and their EDID is read correctly.
-	  VGA connector is not tested so far.</li>
-
-	<li>There is a locking problem in either TTM or the Radeon
-	  driver which prevents OpenGL from working properly.
-	  Jean-S�bastien is currently tracking this down.</li>
-
-	<li>J.R. Oldroyd started to work on a 9-STABLE backport of the
-	 driver which is now working quite well.  He had to backport
-	 some features from the VM which may need further refinement by
-	 the VM folks.</li>
-      </ul>
-
-      <p><a href="http://www.yakaz.com/" shape="rect">Yakaz</a> loaned
-	Jean-S�bastien a computer which allows him to test a
-	RV630-based discrete card and, in the future, other PCIe cards.
-	Several users already kindly tested the driver.  Big thanks to
-	all those contributors!</p>
-
-      <p>In its current state, the driver allows a simple X
-	session (no OpenGL), run common applications, watch movies,
-	change the resolution and enable additional monitors with
-	<tt>xrandr(1)</tt>.  The most blocking issue now is the OpenGL
-	deadlock which prevents running modern compositors/desktop
-	environment, games and WebGL demos.  We are not ready for a
-	"Call For Testers" yet.</p>
-    <h3>Open tasks:</h3><ol><li>Test multiple cards configurations for Video BIOS issues,
-	especially Intel integrated card + Radeon discrete card, and AMD
-	integrated card (IGP) + Radeon discrete card.  No need to check
-	configurations with one shared connector though, it is not
-	supported right now.</li></ol><hr /><h2><a name="Atomic-&quot;close-on-exec&quot;" href="#Atomic-&quot;close-on-exec&quot;" id="Atomic-&quot;close-on-exec&quot;">Atomic "close-on-exec"</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/AtomicCloseOnExec" title="https://wiki.freebsd.org/AtomicCloseOnExec"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/AtomicCloseOnExec" title="">https://wiki.freebsd.org/AtomicCloseOnExec</a></td></tr></table><p>
-	Contact:
-	  Jilles
-	  Tjoelker
-	 &lt;<a href="mailto:jilles@FreeBSD.org">jilles@FreeBSD.org</a>&gt;
-	</p>
-      <p>If threads or signal handlers call <tt>fork()</tt> and
-	<tt>exec()</tt>, file descriptors may be passed undesirably to
-	child processes, which may lead to hangs (if a pipe is not
-	closed), exceeding the file descriptor limit and security
-	problems (if the child process has lower privilege).  One
-	solution is various new APIs that set the <q>close-on-exec</q>
-	flag atomically with allocating a file descriptor.  Some
-	existing software will use the new features if present or will
-	even refuse to compile without them.</p>
-
-      <p>Various parts have been present for some time.</p>
-
-      <p>In first quarter of 2013, extensions to <tt>recvmsg()</tt>,
-	<tt>socket()</tt>, <tt>socketpair()</tt> and
-	<tt>posix_openpt()</tt> have been added.</p>
-    <hr /><h2><a name="callout(9)-Improvements" href="#callout(9)-Improvements" id="callout(9)-Improvements">callout(9) Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~davide/asia/callout_paper.pdf" title="http://people.freebsd.org/~davide/asia/callout_paper.pdf"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~davide/asia/callout_paper.pdf" title="">http://people.freebsd.org/~davide/asia/callout_paper.pdf</a></td></tr><tr><td><a href="http://people.freebsd.org/~davide/asia/calloutng.pdf" title="http://people.freebsd.org/~davide/asia/calloutng.pdf"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~davide/asia/calloutng.pdf" title="">http://people.freebsd.org/~davide/asia/calloutng.pdf</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/base?view=revision&amp;revision=247777" title="http://svnweb.freebsd.org/base?view=revision&amp;revision=247777"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base?view=revision&amp;revision=247777" title="">http://svnweb.freebsd.org/base?view=revision&amp;revision=247777</a></td></tr></table><p>
-	Contact:
-	  Davide
-	  Italiano
-	 &lt;<a href="mailto:davide@FreeBSD.org">davide@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>In FreeBSD, timers are provided by the callout facility, which
-	allows to register a function with an argument to be called at
-	specified future time.  The subsystem suffered of some problems,
-	such as the impossibility of handling high-resolution events or
-	its inherent periodic structure, which may lead to spurious
-	wakeups and higher power consumption.  Some consumers, such as
-	high-speed networking, VoIP and other real-time applications
-	need a better precision than the one currently allowed.  Also,
-	especially with the ubiquity of laptops in the last years, the
-	energy wasted by interrupts waking CPUs from sleep may be a
-	sensitive factor.  Recent changes in the subsystem addressed
-	those long-standing issues as well as introduced a new
-	programming interface to take advantage of the new features.</p>
-    <h3>Open tasks:</h3><ol><li>Evaluating if it is worthwhile to migrate any of the other
-	callout(9) consumers to the new interface.</li><li>Move callout consumers still using the legacy
-	timeout()/untimeout() interface to callout_*() in order to get
-	rid of redundant code and clean up KPI.</li></ol><hr /><h2><a name="Multipath-TCP-(MPTCP)-for-FreeBSD" href="#Multipath-TCP-(MPTCP)-for-FreeBSD" id="Multipath-TCP-(MPTCP)-for-FreeBSD">Multipath TCP (MPTCP) for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html" title="http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html" title="">http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html</a></td></tr><tr><td><a href="http://caia.swin.edu.au/newtcp/mptcp/" title="http://caia.swin.edu.au/newtcp/mptcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/newtcp/mptcp/" title="">http://caia.swin.edu.au/newtcp/mptcp/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/reports/130424A/CAIA-TR-130424A.pdf" title="http://caia.swin.edu.au/reports/130424A/CAIA-TR-130424A.pdf"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/reports/130424A/CAIA-TR-130424A.pdf" title="">http://caia.swin.edu.au/reports/130424A/CAIA-TR-130424A.pdf</a></td></tr><tr><td><a href="https://pub.allbsd.org/FreeBSD-snapshots/" title="https://pub.allbsd.org/FreeBSD-snapshots/"></a></td><td>
-	    URL: <a href="https://pub.allbsd.org/FreeBSD-snapshots/" title="">https://pub.allbsd.org/FreeBSD-snapshots/</a></td></tr></table><p>
-	Contact:
-	  Nigel
-	  Williams
-	 &lt;<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lastewart@swin.edu.au">lastewart@swin.edu.au</a>&gt;
-	<br />
-	Contact:
-	  Grenville
-	  Armitage
-	 &lt;<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>&gt;
-	</p>
-      <p>We have been working to create a BSD-licensed implementation of
-	Multipath TCP &#8212; a set of TCP extensions that allow for
-	transparent multipath operation with multiple IP addresses as
-	specified in experimental RFC6824.</p>
-
-      <p>We made our first v0.1 public release on 2013-03-11 and
-	recently released v0.3 on 2013-04-16.  The code is currently
-	considered to be of alpha quality.  We are working towards
-	pushing the code into a FreeBSD Subversion repository project
-	branch to continue the on-going development effort in a more
-	publicly accessible location.  As part of this move, we hope to
-	begin releasing regular snapshot installer ISOs of the MPTCP
-	project branch courtesy of Hiroki Sato and the allbsd.org daily
-	snapshot infrastructure.</p>
-
-      <p>We are about to release a CAIA technical report 130424A
-	entitled <q>Design Overview of Multipath TCP version 0.3 for
-	FreeBSD�10</q> on 2013-04-24 which provides a high-level
-	design and architecture overview of the v0.3 code release.</p>
-
-      <p>Going forward, we expect to continue development and release
-	additional technical reports and academic papers covering topics
-	such as performance analysis and multipath congestion
-	control/scheduling.</p>
-    <h3>Open tasks:</h3><ol><li>The code is currently of alpha quality so we welcome all
-	testing feedback, but please familiarize yourself with the README
-	file and "Known Limitations" section in particular before
-	jumping in.</li></ol><hr /><h2><a name="racct:-Block-IO-Accounting" href="#racct:-Block-IO-Accounting" id="racct:-Block-IO-Accounting">racct: Block IO Accounting</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/RudolfTomori/IOLimits" title="https://wiki.freebsd.org/RudolfTomori/IOLimits"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/RudolfTomori/IOLimits" title="">https://wiki.freebsd.org/RudolfTomori/IOLimits</a></td></tr></table><p>
-	Contact:
-	  Rudolf
-	  Tomori
-	 &lt;<a href="mailto:rudot@FreeBSD.org">rudot@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project adds the block IO access accounting to the
-	racct/rctl resource limiting framework; a working prototype
-	implementation is available.</p>
-    <hr /><h2><a name="Read-only-Port-of-NetBSD's-UDF-File-System" href="#Read-only-Port-of-NetBSD's-UDF-File-System" id="Read-only-Port-of-NetBSD's-UDF-File-System">Read-only Port of NetBSD's UDF File System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/williamdevries/UDF" title="https://github.com/williamdevries/UDF">Github Repository</a></td><td>
-	    URL: <a href="https://github.com/williamdevries/UDF" title="Github Repository">https://github.com/williamdevries/UDF</a></td></tr></table><p>
-	Contact:
-	  Will
-	  DeVries
-	 &lt;<a href="mailto:william.devries@gmail.com">william.devries@gmail.com</a>&gt;
-	</p>
-      <p>An initial read-only port of NetBSD's UDF file system has been
-	largely completed.  (The UDF file system is often used on CD, DVD
-	and Blu-Ray discs.) This port provides a number of advantages
-	over FreeBSD's current UDF implementation, which include:</p>
-
-      <ul>
-	<li>Support for version 2.60 of the UDF file system
-	  specification.  FreeBSD's current implementation only partially
-	  supports version 1.5 of the standard, which was released in
-	  1997.  Since Windows and other systems support newer version
-	  of this file system, our users are left without the ability to
-	  read some media written by these systems.  In addition,
-	  Blu-Ray discs are commonly written using version 2.50 or
-	  2.60.</li>
-
-	<li>The ability to override the owner and group for all the
-	  files and directories on a UDF volume using mount options.</li>
-
-	<li>The ability to set the owner and group for files and
-	  directories that lack defined owner or group information using
-	  mount options.  (The UDF specification allows for files and
-	  directories without owners or groups.)</li>
-
-	<li>The ability to override the mode for all directories and
-	  files on a volume using mount options.</li>
-
-	<li>Support for mounting previous versions of incrementally
-	  recorded media, like CD-Rs.</li>
-      </ul>
-    <hr /><h2><a name="TCP-AO-Authentication-Option" href="#TCP-AO-Authentication-Option" id="TCP-AO-Authentication-Option">TCP-AO Authentication Option</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/base/user/andre/tcp-ao/" title="http://svnweb.freebsd.org/base/user/andre/tcp-ao/">SVN branch</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/user/andre/tcp-ao/" title="SVN branch">http://svnweb.freebsd.org/base/user/andre/tcp-ao/</a></td></tr></table><p>
-	Contact:
-	  Andr�
-	  Oppermann
-	 &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work is under way to implement TCP-AO (TCP Authentication
-	Option) according to RFC5925 and RFC5926.  TCP-AO is an
-	extension to TCP-MD5 signatures commonly used in routers to
-	secure BGP routing protocol sessions against spoofing attacks.
-	The work is under contract and sponsored by Juniper
-	Networks.</p>
-    <hr /><h2><a name="UFS/FFS-Performance-Work" href="#UFS/FFS-Performance-Work" id="UFS/FFS-Performance-Work">UFS/FFS Performance Work</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mckusick.com/publications/faster_fsck.pdf" title="http://www.mckusick.com/publications/faster_fsck.pdf">Paper describing this work</a></td><td>
-	    URL: <a href="http://www.mckusick.com/publications/faster_fsck.pdf" title="Paper describing this work">http://www.mckusick.com/publications/faster_fsck.pdf</a></td></tr></table><p>
-	Contact:
-	  Kirk
-	  McKusick
-	 &lt;<a href="mailto:mckusick@mckusick.com">mckusick@mckusick.com</a>&gt;
-	</p>
-      <p>Some work on the performance of UFS/FFS has been recently
-	committed to HEAD.  The purpose of the corresponding change to
-	the FFS layout policy is to reduce the running time for a full
-	file system check.  It also reduces the random access time for
-	large files and speeds up the traversal time for directory tree
-	walks.</p>
-
-      <p>The key idea is to reserve a small area in each cylinder group
-	immediately following the inode blocks for the use of metadata,
-	specifically indirect blocks and directory contents.  The new
-	policy is to preferentially place metadata in the metadata area
-	and everything else in the blocks that follow the metadata
-	area.</p>
-
-      <p>The size of this area can be set when creating a filesystem
-	using <tt>newfs(8)</tt> or changed in an existing filesystem using
-	<tt>tunefs(8)</tt>.  Both utilities use the <tt>-k
-	held-for-metadata-blocks</tt> option to specify the amount of
-	space to be held for metadata blocks in each cylinder group.  By
-	default, <tt>newfs(8)</tt> sets this area to half of minfree
-	(typically 4% of the data area).</p>
-
-      <p>As with all layout policies, it only affects layouts of things
-	allocated after it is put in place.  So these changes will
-	primarily be noticable on newly created file systems.</p>
-
-      <p>File system checks have been sped up by caching the cylinder
-	group maps in pass1 so that they do not need to be read again in
-	pass5.  As this nearly doubles the memory requirement for
-	<tt>fsck(8)</tt>, the cache is thrown away if other memory needs
-	in <tt>fsck(8)</tt> would otherwise fail.  Thus, the memory
-	footprint of <tt>fsck(8)</tt> remains unchanged in memory
-	constrained environments.  This optimization will be evident on
-	all UFS/FFS filesystems.</p>
-
-      <p>This work was inspired by a <a href="http://www.usenix.org/conference/fast13/ffsck-fast-file-system-checker" shape="rect">paper</a>
-	presented at Usenix's FAST '13.</p>
-    <h3>Open tasks:</h3><ol><li>MFC to 9-STABLE and possibly 8-STABLE should happen by May
-	unless problems arise with these changes in HEAD.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Improving-the-Documentation-Project-Infrastructre" href="#Improving-the-Documentation-Project-Infrastructre" id="Improving-the-Documentation-Project-Infrastructre">Improving the Documentation Project Infrastructre</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/doc/projects/xml-tools/" title="http://svnweb.freebsd.org/doc/projects/xml-tools/">The xml-tools branch</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/doc/projects/xml-tools/" title="The xml-tools branch">http://svnweb.freebsd.org/doc/projects/xml-tools/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>There is an on-going work to improve the documentation
-	infrastructure and modernize our documentation toolchain.  The
-	work can be found in the <tt>xml-tools</tt> branch and is very
-	near to completion.  The improvements include the following:</p>
-
-      <ul>
-	<li>Upgrade to DocBook 4.5.</li>
-	<li>Use XSLT instead of DSSSL to render XHTML-based output.</li>
-	<li>Generate PDF from PS and simplify image processing.</li>
-	<li>Fix <tt>make lint</tt> and validate the whole documentation
-	  set.</li>
-	<li>Fix rendering of TOC elements.</li>
-	<li>Fix misused link elements that resulted in a corrupt
-	  rendering.</li>
-	<li>Use more human-friendly publication data and release info
-	  rendering.</li>
-	<li>Add support for XInclude in DocBook documents.</li>
-	<li>Add support for profiling with attributes.</li>
-	<li>Add support for Schematron constraints.</li>
-	<li>Add experimental epub support.</li>
-	<li>Add experimental support for XSL-FO-based printed
-	  output.</li>
-	<li>Clean up obsolete SGML constructs.</li>
-	<li>Clean up catalogs.</li>
-	<li>Drop HTML Tidy since it is not needed any more.</li>
-      </ul>
-
-      <p>The changes eliminate some dependencies and switch the doc
-	repository to a real XML toolchain with proper validation and
-	more advanced rendering tools.  The only exceptions are Jade and
-	the DSSSL stylesheets, which are still needed for printed
-	output.</p>
-    <h3>Open tasks:</h3><ol><li>Fix rendering problems with images in printed
-	formats.</li><li>Update the Documentation Primer to reflect changes.</li></ol><hr /><h2><a name="The-entities-Documentation-Branch" href="#The-entities-Documentation-Branch" id="The-entities-Documentation-Branch">The entities Documentation Branch</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/doc/projects/entities/" title="http://svnweb.freebsd.org/doc/projects/entities/">Subversion repository link</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/doc/projects/entities/" title="Subversion repository link">http://svnweb.freebsd.org/doc/projects/entities/</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>&gt;
-	</p>
-      <p>The entities branch was created to reduce duplication of
-	committer entities.  Currently there is one in
-	<tt>authors.ent</tt> (with email addresses) and another one in
-	developers.ent (without email addresses).  This seems to be a
-	leftover from the doc/www split in earlier times.  To remedy
-	this, <tt>developers.ent</tt> is merged into
-	<tt>authors.ent</tt> and entities with email addresses are
-	postfixed as such.  Apart from the instructions for the initial
-	commit, there should be little user-visible changes.  Some
-	related cleanups, like cleaning up team definitions, replacing
-	literal names by entities from <tt>authors.ent</tt>, and adding
-	missing names to <tt>authors.ent</tt> are also made.</p>
-    <h3>Open tasks:</h3><ol><li>Finish processing of the &lt;email&gt; tag.</li><li>Send out a CFT.</li><li>Merge back into head branch.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Page">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td>
-	    URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p>
-	Contact:
-	  Hiroki
-	  Sato
-	 &lt;<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryusuke
-	  Suzuki
-	 &lt;<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>&gt;
-	</p>
-      <p>Web page (<tt>htdocs</tt>): Newsflash and some other updates in
-	the English version have been translated to keep them up-to-date.
-	Specifically, the release related contents were updated in this
-	period.</p>
-
-      <p>Books: FreeBSD Handbook has constantly been updated since the last
-	report; particularly, "ports", "desktop" section were largely
-	updated.  Some progress has been made in the
-	"advanced-networking" section, contributed by a new
-	translator.</p>
-
-      <p><q>Writing FreeBSD Problem Reports</q> article is now in sync with
-	the English version.</p>
-    <h3>Open tasks:</h3><ol><li>Further translation work of outdated documents in
-	ja_JP.eucJP subtree.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Cubieboard" href="#FreeBSD-on-Cubieboard" id="FreeBSD-on-Cubieboard">FreeBSD on Cubieboard</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Ganbold
-	  Tsagaankhuu
-	 &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Initial support of Allwinner A10 SoC is committed to -CURRENT.
-	FreeBSD is now running on boards such as Cubieboard, Hackberry and
-	it supports following peripherals:</p>
-
-      <ul>
-	<li>USB EHCI</li>
-	<li>GPIO</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Get EMAC Ethernet driver working.  Need more help from
-	network driver experts.</li><li>Implement more drivers.</li></ol><hr /><h2><a name="FreeBSD/arm-Superpages-for-ARMv7" href="#FreeBSD/arm-Superpages-for-ARMv7" id="FreeBSD/arm-Superpages-for-ARMv7">FreeBSD/arm Superpages for ARMv7</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf" title="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf">Paper</a></td><td>
-	    URL: <a href="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf" title="Paper">http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/ARMSuperpages" title="https://wiki.freebsd.org/ARMSuperpages">Wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/ARMSuperpages" title="Wiki page">https://wiki.freebsd.org/ARMSuperpages</a></td></tr><tr><td><a href="https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git" title="https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git">Project's GitHub repository</a></td><td>
-	    URL: <a href="https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git" title="Project's GitHub repository">https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git</a></td></tr></table><p>
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafa&#322;
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>ARM architecture is more and more prevalent, not only in the
-	mobile and embedded space.  Among the more interesting industry
-	trends emerging in the recent months has been the "ARM server"
-	concept.  Some top-tier companies have started developing systems
-	like this already (Dell, HP).</p>
-
-      <p>Key to FreeBSD success in these new areas are sophisticated
-	features, among them are superpages.</p>
-
-      <p>The objective of this project is to provide FreeBSD/arm with the
-	superpages support, which will allow for efficient use of TLB
-	translations (enlarge TLB coverage), leading to improved
-	performance in many applications and scalability.  Indicated
-	functionality is intended to work on ARMv7-based processors,
-	however compatibility with ARMv6 will be preserved.</p>
-
-      <p>Current support status:</p>
-
-      <ul>
-	<li>Port of the pv_entry allocator.</li>
-	<li>Switch to "AP[2:1]" access permissions model.</li>
-	<li>PTE-based, page-referenced/modified emulation.</li>
-	<li>Fixes regarding page replacement strategy.</li>
-	<li>Code optimizations and bug fixes.</li>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>Dirty pages management.</li>
-	<li>Gradual integration to FreeBSD -CURRENT.</li>
-	<li>Further pmap optimizations.</li>
-	<li>Fragmentation control management.</li>
-	<li>Testing and benchmarking.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Support for multiple page sizes.</li><li>Implementation of page promotion, demotion and eviction
-	mechanisms.</li></ol><hr /><h2><a name="FreeBSD/ARM-Toolchain-Improvements" href="#FreeBSD/ARM-Toolchain-Improvements" id="FreeBSD/ARM-Toolchain-Improvements">FreeBSD/ARM Toolchain Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Clang has been made the default compiler on ARM.  A number of
-	issues with LLVM and clang have been found, reported, and fixed
-	upstream.</p>
-
-      <p>An issue where some ARM EABI applications compiled with clang
-	crash has been reported upstream with a patch and will be
-	brought into the FreeBSD tree when it is accepted.  The only other
-	issue blocking moving to the ARM EABI is C++ exceptions fail to
-	work correctly with shared objects.  This will need us to either
-	import libunwind or implement the functions libgcc_s requires to
-	find the correct unwind table.</p>
-    <h3>Open tasks:</h3><ol><li>Fix exception handling for EABI.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Haskell" title="http://wiki.freebsd.org/Haskell">FreeBSD Haskell wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Haskell" title="FreeBSD Haskell wiki page">http://wiki.freebsd.org/Haskell</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="https://github.com/freebsd-haskell/freebsd-haskell/">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/freebsd-haskell/" title="FreeBSD Haskell ports repository">https://github.com/freebsd-haskell/freebsd-haskell/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  Shukla
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce FreeBSD Haskell Team has updated existing
-	ports to their latest stable versions.  We also added number of
-	new ports, which brings the count of Haskell ports in FreeBSD ports
-	tree to more than 400, featuring many popular software, e.g.
-	<tt>xmonad</tt>, <tt>git-annex</tt>, <tt>pandoc</tt> or various
-	web framework implementations.  All of these updates will be
-	available as part of the upcoming 8.4-RELEASE.  We also came to
-	know that Haskell ports are also being used successfully on
-	DragonFlyBSD's dports tree.</p>
-
-      <p>In our development repository, there was some optional support
-	added for LLVM-based code generation using the GHC LLVM backend.
-	This works mostly on FreeBSD too, though some of the ports would
-	need fixing so it is still considered experimental.</p>
-    <h3>Open tasks:</h3><ol><li>Try to build GHC with clang (as system compiler).</li><li>Commit pending Haskell ports to the FreeBSD ports tree.</li><li>Add more ports to the Ports Collection.</li></ol><hr /><h2><a name="GNOME/FreeBSD" href="#GNOME/FreeBSD" id="GNOME/FreeBSD">GNOME/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/gnome" title="http://www.freebsd.org/gnome"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/gnome" title="">http://www.freebsd.org/gnome</a></td></tr><tr><td><a href="http://www.freebsd.org/gnome/docs/develfaq.html" title="http://www.freebsd.org/gnome/docs/develfaq.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/gnome/docs/develfaq.html" title="">http://www.freebsd.org/gnome/docs/develfaq.html</a></td></tr><tr><td><a href="http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom" title="http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom"></a></td><td>
-	    URL: <a href="http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom" title="">http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom</a></td></tr><tr><td><a href="https://github.com/jlmess77/mate-ports" title="https://github.com/jlmess77/mate-ports"></a></td><td>
-	    URL: <a href="https://github.com/jlmess77/mate-ports" title="">https://github.com/jlmess77/mate-ports</a></td></tr></table><p>
-	Contact:
-	  FreeBSD GNOME team
-	 &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The GNOME/FreeBSD Team has recently merged Glib 2.34, Gtk+ 2.24.17
-	and Gtk+ 3.6.4 into ports, the C++ bindings also have got
-	updates.  In additional "low-level" GNOME ports received
-	updates, like libsoup, gobject-introspection, atk and vala for
-	example.  The telepathy stack and empathy where also
-	updated.</p>
-
-      <p>The <tt>USE_GNOME</tt> macro has received support for
-	<tt>:run</tt> and <tt>:build</tt> targets thanks to Jeremy
-	Messenger (mezz).  Currently only libxml2 and libxslt support
-	these targets.</p>
-
-      <p><tt>USE_GNOME=pkgconfig</tt> is being deprecated in favor of
-	<tt>USE_PKGCONFIG=build</tt>.  The former also adds a run
-	dependency on pkg-config, which is not required.  A first pass
-	was done to get rid of this in the Glib update to 2.34.  In
-	cooperation with the X11 Team, the usage of
-	<tt>USE_GNOME=pkgconfig</tt> in X components will be removed.
-	After the fallout from this is handled and stragglers are
-	converted, the <tt>USE_GNOME</tt> option will be removed.</p>
-
-      <p>In addition <tt>USE_GNOME=gnomehack</tt> is deprecated and
-	should not be used.  Please replace it with
-	<tt>USES=pathfix</tt>.</p>
-
-      <p>The GNOME development repository has switched from CVS to SVN.
-	CVS will not get any more updates.  Uses can get a new version
-	of the <a href="http://marcuscom.com/downloads/marcusmerge" shape="rect">marcusmerge</a>
-	script that supports SVN from its home page, and should remove
-	the old CVS checkout "ports" dir.</p>
-
-      <ul>
-	<li>SVN anonymous root: <a href="svn://creme-brulee.marcuscom.com/" shape="rect">svn://creme-brulee.marcuscom.com/</a>
-	  or <a href="svn://sushi.marcuscom.com/" shape="rect">svn://sushi.marcuscom.com/</a> (IPv6)</li>
-	<li>ViewVC: <a href="http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom" shape="rect">http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom</a></li>
-      </ul>
-
-      <p>Ongoing efforts:</p>
-
-      <ul>
-	<li><tt>glib</tt> 2.36, <tt>pango</tt> 1.34.0, <tt>gtk</tt>
-	  3.8.0 and <tt>gobject-introspection</tt> 1.36.0 where updated in
-	  the GNOME development repository.</li>
-
-	<li>Gustau Perez i Querol stepped up and started work on
-	  updating the old GNOME 3.4 ports to 3.6.  At the moment of
-	  writing these are not available in the GNOME development
-	  repository just yet.  For his efforts, he was awarded a FreeBSD
-	  GNOME team membership.</li>
-
-	<li>Jeremy Messenger (mezz) has completed Mate 1.6 which will be arriving in
-	  ports near you when deemed stable enough.</li>
-      </ul>
-
-      <p>If you want to help with keeping the documentation updated or
-	helping out in other ways, even if it only parts for the
-	Glib/Gtk/GNOME stack you are interested in, please contact
-	us!</p>
-    <h3>Open tasks:</h3><ol><li>Update the FreeBSD.org/gnome website, in particular the
-	developer information about USE_GNOME, maybe put that section in
-	the Porter's Handbook instead.</li><li>Merge more updated ports from MC to ports.</li><li>Testing latest Glib/Gtk releases with existing ports, and import
-	it into ports when it is ready.</li><li>After porting GNOME 3.6 run tests and fix bugs.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	KDE
-	FreeBSD
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE/FreeBSD Team is very proud to have Schaich Alonso (aschai)
-	joining the team.  Welcome!</p>
-
-      <p>The KDE/FreeBSD Team have continued to improve the experience of
-	KDE software and Qt under FreeBSD.  The latest round of improvements
-	include:</p>
-
-      <ul>
-	<li>Fix problems establishing UDP connections.</li>
-      </ul>
-
-      <p>The Team have also made many releases and upstreamed many fixes
-	and patches.  The latest round of releases include:</p>
-
-      <ul>
-	<li>KDE SC: 4.9.5, 4.10.1 (ports)</li>
-	<li>Qt: 5.0.0 (area51) and 4.8.4 (ports)</li>
-	<li>PyQt: 4.9.6 (ports); QScintilla 2.7 (ports); SIP: 4.14.2 (area51) and 4.14.3 (ports)</li>
-	<li>KDevelop: 4.4.1 (ports); KDevPlatform: 1.4.1 (ports)</li>
-	<li>Calligra: 2.5.5, 2.6.2 (ports)</li>
-	<li>Amarok: 2.7.0</li>
-	<li>CMake: 2.8.10.2</li>
-	<li>Digikam (and KIPI-plugins): 3.1.0 (area51)</li>
-	<li>QtCreator: 4.6.1 (ports)</li>
-	<li>KDE Telepathy 0.6.0 (area51)</li>
-	<li>many smaller ports</li>
-      </ul>
-
-      <p>As a result &#8212; according to PortScout &#8212; we have 431
-	ports, of which 93.5% (from 91%) are up-to-date.</p>
-
-      <p>The Team are always looking for more testers and porters so
-	please contact us and visit our home page.</p>
-    <h3>Open tasks:</h3><ol><li>Updating out-of-date ports, see PortScout for a list.</li></ol><hr /><h2><a name="PyPy" href="#PyPy" id="PyPy">PyPy</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/PyPy" title="http://wiki.FreeBSD.org/PyPy">FreeBSD-PyPy Project page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/PyPy" title="FreeBSD-PyPy Project page">http://wiki.FreeBSD.org/PyPy</a></td></tr></table><p>
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	</p>
-      <p>PyPy has been successfully updated to 2.0-beta1 with 2.0-beta2
-	finishing translating and other tests.  Many major changes were
-	made to the PyPy port from the 2.0-beta1 release, these
-	include:</p>
-
-      <ul>
-	<li>Reworking the build script.</li>
-	<li>Optionally use <tt>pypy</tt> (when available) for self-translating.</li>
-	<li>Refine memory checks.</li>
-	<li>Fix the test target.</li>
-      </ul>
-
-      <p>Although the port is in a healthy state, PyPy on FreeBSD has some
-	rough edges (see <tt>make test</tt> for examples of
-	roughness).</p>
-    <h3>Open tasks:</h3><ol><li>Fix failed unit tests.</li><li>Integrate PyPy into bsd.python.mk.</li><li>See the project page for more items.</li></ol><hr /><h2><a name="Wine32-on-FreeBSD/amd64" href="#Wine32-on-FreeBSD/amd64" id="Wine32-on-FreeBSD/amd64">Wine32 on FreeBSD/amd64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/i386-Wine" title="http://wiki.freebsd.org/i386-Wine">Wine32 on FreeBSD/amd64 Project page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/i386-Wine" title="Wine32 on FreeBSD/amd64 Project page">http://wiki.freebsd.org/i386-Wine</a></td></tr></table><p>
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	</p>
-      <p>The i386-wine port (formally wine-fbsd64) has been added to the
-	ports collection (as emulators/i386-wine-devel).  Although the
-	port can only be compiled under a x86 32-bit system the
-	resulting package can be installed on a x86 64-bit system and
-	enable running of 32-bit Microsoft Windows programs.</p>
-
-      <p>Packages for the port are in development and should be
-	announced shortly on the freebsd-questions and freebsd-emulation
-	mailing lists.</p>
-
-      <p>There are some issues with Wine32 on FreeBSD/amd64 &#8212;
-	possibly related to <tt>FREEBSD32_COMPAT</tt>, or other general
-	32/64-bit issues &#8212; that could do with some focus.</p>
-    <h3>Open tasks:</h3><ol><li>Port wine64 to FreeBSD.</li><li>Port WoW64 (wine32 and wine64 together) to FreeBSD.</li><li>Fix 32- and 64-bit issues (such as Intel graphics not
-	accelerating).</li></ol><hr /><h2><a name="Xfce/FreeBSD" href="#Xfce/FreeBSD" id="Xfce/FreeBSD">Xfce/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Xfce" title="https://wiki.FreeBSD.org/Xfce"></a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Xfce" title="">https://wiki.FreeBSD.org/Xfce</a></td></tr><tr><td><a href="http://people.freebsd.org/~olivierd/patches/midori-0.4.9_0.5.0.diff" title="http://people.freebsd.org/~olivierd/patches/midori-0.4.9_0.5.0.diff">Midori 0.5 patches</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~olivierd/patches/midori-0.4.9_0.5.0.diff" title="Midori 0.5 patches">http://people.freebsd.org/~olivierd/patches/midori-0.4.9_0.5.0.diff</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Xfce FreeBSD Team has updated many ports, especially:</p>
-
-      <ul>
-	<li>tumbler: 0.1.27 (add new option, COVER)</li>
-	<li>Parole: 0.5.0</li>
-	<li>xfdesktop: 4.10.2</li>
-	<li>Midori: 0.4.9 (fully compatible with Vala 0.18), 0.5.0 is available
-	  (see links)</li>
-	<li>Orage: 4.8.4</li>
-	<li>xfce4-terminal: 0.6.1 (renamed by upstream, previous name
-	 was Terminal)</li>
-      </ul>
-
-      <p>This last application contains drop-down functionality: new
-	window slides down from the top of the screen when key (we can
-	define keyboard shortcut) is pressed.</p>
-    <h3>Open tasks:</h3><ol><li>Replace libxfce4gui (deprecated and not maintained by
-	upstream) by libxfce4ui in order to enhance support panel plugins
-	for Xfce &gt;= 4.10.</li><li>Work on Midori Gtk3 port.</li><li>Fix gtk-xfce-engine with Gtk+ &gt;=3.6.</li></ol><hr /><h2><a name="xorg-on-FreeBSD" href="#xorg-on-FreeBSD" id="xorg-on-FreeBSD">xorg on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Xorg" title="http://wiki.freebsd.org/Xorg"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Xorg" title="">http://wiki.freebsd.org/Xorg</a></td></tr><tr><td><a href="http://people.freebsd.org/~zeising/xorg-7.7.diff" title="http://people.freebsd.org/~zeising/xorg-7.7.diff"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~zeising/xorg-7.7.diff" title="">http://people.freebsd.org/~zeising/xorg-7.7.diff</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk"></a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/branches/xorg-7.7" title="http://trillian.chruetertee.ch/ports/browser/branches/xorg-7.7"></a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/branches/xorg-7.7" title="">http://trillian.chruetertee.ch/ports/browser/branches/xorg-7.7</a></td></tr></table><p>
-	Contact: FreeBSD X11 Team &lt;<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Niclas
-	  Zeising
-	 &lt;<a href="mailto:zeising@FreeBSD.org">zeising@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Koop
-	  Mast
-	 &lt;<a href="mailto:kwm@FreeBSD.org">kwm@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most of the work during this period has been in updating,
-	testing and stabilizing the development repository.  A number of
-	xorg applications and various other leaf ports has been
-	committed as part of this effort.  After this a CFT was sent out
-	asking for help in testing the remaining bits in development,
-	including updates to all major libraries and xorg-server.</p>
-
-      <p>Currently, the CFT patch has been submitted for an exp-run to
-	iron out any final bugs.  The plan is to merge it sometime after
-	FreeBSD 8.4 is released and the ports tree is reopened for
-	commits.</p>
-
-      <p>Work is also ongoing to port new versions of MESA and OpenGL,
-	as well as a new version of xorg-server, and perhaps in the
-	future, Wayland.  These are considered more long-term goals and
-	are not targeted for the current update.</p>
-    <h3>Open tasks:</h3><ol><li>Decide how to handle the new and old xorg distributions.  In
-	recent xorg, a lot of legacy driver support has been dropped,
-	therefore we need to maintain two xorg distributions to not
-	lose a lot of hardware drivers.  Currently, this is done by
-	setting the flag WITH_NEW_XORG in /etc/make.conf, but a more
-	practical solution is needed.  This is especially important
-	since the flag is not very user-friendly, and since there
-	currently will be no official packages for the new
-	distribution.</li><li>Continue to test and update xorg related ports.  There are
-	new versions of xserver, as well as MESA and related OpenGL
-	libraries which needs to be ported and eventually integrated
-	into the ports tree.</li><li>Port Wayland.  The future of graphical environments in open
-	source operating systems seems to be Wayland.  This needs to be
-	ported to FreeBSD so that a wider audience can test it, and so that
-	it eventually can be integrated into the ports tree, perhaps as
-	a replacement for the current xorg.</li><li>Look into replacements for HAL.  HAL is used for
-	hot-plugging of devices, but it has been long abandoned by Linux.
-	A replacement, perhaps built on top of devd would be nice to
-	have.  This work should be coordinated with the FreeBSD GNOME and
-	KDE teams.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BXR.SU-&#8212;-Super-User's-BSD-Cross-Reference" href="#BXR.SU-&#8212;-Super-User's-BSD-Cross-Reference" id="BXR.SU-&#8212;-Super-User's-BSD-Cross-Reference">BXR.SU &#8212; Super User's BSD Cross Reference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bxr.su/" title="http://bxr.su/">BXR.SU &#8212; Super User's BSD Cross Reference</a></td><td>
-	    URL: <a href="http://bxr.su/" title="BXR.SU &#8212; Super User's BSD Cross Reference">http://bxr.su/</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042334.html" title="http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042334.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042334.html" title="">http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042334.html</a></td></tr></table><p>
-	Contact:
-	  Constantine A.
-	  Murenin
-	 &lt;<a href="mailto:cnst++@FreeBSD.org">cnst++@FreeBSD.org</a>&gt;
-	</p>
-      <p>Super User's BSD Cross Reference (BXR.SU) is a new source-code
-	search engine that covers the complete kernel and non-GNU
-	userland source trees of FreeBSD, NetBSD, OpenBSD, and DragonFly
-	BSD.</p>
-
-      <p>BXR.SU is optimised to be very fast, has daily updates of all
-	the trees, and also acts as a deterministic URL shortener.</p>
-
-      <p>BXR.SU is based on an OpenGrok fork, but it is more than just
-	OpenGrok.  We have fixed a number of annoyances, eliminated
-	features that just never worked right from the outright, and
-	provided integration with tools like CVSweb (including great
-	mirrors like allbsd.org), FreeBSD's ViewVC (SVN), as well as GitHub
-	and Gitweb from <tt>git.freebsd.your.org</tt>, plus a tad of
-	other improvements, including a complete rewrite of an mdoc
-	parser.  Last, but definitely not least, is an extensive set of
-	nginx rewrite rules that makes it a breeze to use BXR.SU as a
-	deterministic URL compactor for referencing BSD source code.
-	For example, the <tt>http://bxr.su/f/kern/sched_ule.c</tt> URL
-	will automatically redirect to
-	<tt>http://bxr.su/FreeBSD/sys/kern/sched_ule.c</tt> through
-	nginx.</p>
-
-      <p>Note that according to the release schedule of BXR.SU, there is
-	no IPv4 glue until 2013-04-24; otherwise, the service is available
-	via both IPv4 and IPv6.  See the 2013-04-01 announcement on the
-	freebsd-hackers mailing list for more details.</p>
-    <h3>Open tasks:</h3><ol><li>Find up-to-date git repositories (served with Gitweb) of
-	NetBSD and OpenBSD.</li><li>Find a Gitweb mirror of FreeBSD that is faster than GitHub and
-	Gitorious.</li></ol><hr /><h2><a name="mdoc.su-&#8212;-Short-Manual-Page-URLs" href="#mdoc.su-&#8212;-Short-Manual-Page-URLs" id="mdoc.su-&#8212;-Short-Manual-Page-URLs">mdoc.su &#8212; Short Manual Page URLs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mdoc.su/" title="http://mdoc.su/">mdoc.su &#8212; Short Manual Page URLs for FreeBSD, NetBSD, OpenBSD and DragonFly BSD</a></td><td>
-	    URL: <a href="http://mdoc.su/" title="mdoc.su &#8212; Short Manual Page URLs for FreeBSD, NetBSD, OpenBSD and DragonFly BSD">http://mdoc.su/</a></td></tr><tr><td><a href="http://nginx.conf.mdoc.su/mdoc.su.nginx.conf" title="http://nginx.conf.mdoc.su/mdoc.su.nginx.conf">nginx.conf for mdoc.su</a></td><td>
-	    URL: <a href="http://nginx.conf.mdoc.su/mdoc.su.nginx.conf" title="nginx.conf for mdoc.su">http://nginx.conf.mdoc.su/mdoc.su.nginx.conf</a></td></tr><tr><td><a href="https://github.com/cnst/mdoc.su" title="https://github.com/cnst/mdoc.su"></a></td><td>
-	    URL: <a href="https://github.com/cnst/mdoc.su" title="">https://github.com/cnst/mdoc.su</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-doc/2013-February/021465.html" title="http://lists.freebsd.org/pipermail/freebsd-doc/2013-February/021465.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-doc/2013-February/021465.html" title="">http://lists.freebsd.org/pipermail/freebsd-doc/2013-February/021465.html</a></td></tr></table><p>
-	Contact:
-	  Constantine A.
-	  Murenin
-	 &lt;<a href="mailto:cnst++@FreeBSD.org">cnst++@FreeBSD.org</a>&gt;
-	</p>
-      <p><a href="http://mdoc.su/" shape="rect">mdoc.su</a> is a deterministic URL
-	shortener for BSD manual pages, written entirely in
-	<tt>nginx.conf</tt>.</p>
-
-      <p>Since the original announcement, OS version support has been
-	added (e.g. <tt>/f91/</tt> and <tt>/FreeBSD-9.1/</tt> etc.), as
-	well as dynamic multi-flavour web-pages with multiple links
-	(e.g. <tt>http://mdoc.su/f,d/ifnet.9</tt> and
-	<tt>http://mdoc.su/-/mdoc</tt>), which even let you specify the
-	versions too (e.g. <tt>http://mdoc.su/f91,n60,o52,d/mdoc</tt>).</p>
-
-      <p>The source code for the whole site is available under a BSD
-	licence.</p>
-    <h3>Open tasks:</h3><ol><li>Fork it on GitHub (see links)!</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2013-04-2013-06.html b/website/content/en/status/report-2013-04-2013-06.html
deleted file mode 100644
index d0792bc419..0000000000
--- a/website/content/en/status/report-2013-04-2013-06.html
+++ /dev/null
@@ -1,1491 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between April and June
-      2013.  This is the second of four reports planned for 2013.</p><p>The last three months have been very active for the FreeBSD
-      developer community, including events such as BSDCan and the FreeBSD
-      Developer Summit collocated with it (covered in a separate report,
-      see the <a href="report-2013-05-devsummit.html" shape="rect">BSDCan Developer Summit Special</a>)
-      and BSD-Day 2013.  It has also seen improvements from the top to
-      the bottom of the FreeBSD system.  Desktop users will be pleased to
-      note work on improving the state of AMD GPUs and making the
-      console interaction with kernel mode setting &#8212; required for
-      recent <tt>xorg</tt> drivers &#8212; cleaner and from continued
-      work to make binary packages easier to use.  Developers will note
-      continued improvements to our toolchain, with a new debugger being
-      prepared for integration.  Server users will benefit from various
-      improvements to virtualization support and scalability in the
-      kernel.  Of course, the FreeBSD system is nothing without
-      applications to run atop it, and this quarter has seen some
-      tireless work by members of the ports team to ensure that users
-      have a wide choice of desktop and development environments, with
-      highlights from the GNOME, KDE, Xfce, and Haskell teams in this
-      report.</p><p>Thanks to all the reporters for the excellent work!  This report
-      contains 33 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between July and September
-      2013 is October 7th, 2013.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#FreeBSD-Security-Team">FreeBSD Security Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#PC-BSD">PC-BSD</a></li><li><a href="#Virtual-Private-Systems">Virtual Private Systems</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#AMD-GPU-Kernel-Mode-setting-Support">AMD GPU Kernel Mode-setting Support</a></li><li><a href="#Improved-TCP-SYN-Cookies">Improved TCP SYN Cookies</a></li><li><a href="#Multi-threaded-Pagedaemon">Multi-threaded Pagedaemon</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#Newcons-Reboot">Newcons Reboot</a></li><li><a href="#Realtek-RTL8188CU/RTL8192CU-USB-Wireless-Driver">Realtek RTL8188CU/RTL8192CU USB Wireless Driver</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#V4L2-Update-in-the-Linuxulator">V4L2 Update in the Linuxulator</a></li><li><a href="#Wireless-Networking-Improvements">Wireless Networking Improvements</a></li><li><a href="#Xen-Support-Improvements">Xen Support Improvements</a></li><li><a href="#ZFS-TRIM-and-Enhanced-BIO_DELETE-Support">ZFS TRIM and Enhanced BIO_DELETE Support</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></li><li><a href="#Superpages-for-ARMv7">Superpages for ARMv7</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#bsdconfig(8)-and-sysrc(8)">bsdconfig(8) and sysrc(8)</a></li><li><a href="#bsnmpd(1)-Support-in-hastd(8)">bsnmpd(1) Support in hastd(8)</a></li><li><a href="#Capsicum">Capsicum</a></li><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li><li><a href="#xorg-on-FreeBSD">xorg on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Upgrading-the-Documentation-Set-to-DocBook-5.0">Upgrading the Documentation Set to DocBook 5.0</a></li></ul><h3><a href="#Events">Events</a></h3><ul><li><a href="#BSD-Day-2013">BSD-Day 2013</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#New-Capsicum-Features">New Capsicum Features</a></li><li><a href="#Qt-and-GTK+-Frontends-for-pkg(8)">Qt and GTK+ Frontends for pkg(8)</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact:
-	  FreeBSD
-	  Core Team
-	 &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the second quarter of 2013, the Core Team approved a new
-	Security Officer, Dag-Erling Sm�rgrav and his deputy, Xin
-	Li.  The Core Team acknowledges Simon Nielsen, the outgoing
-	Security Officer, for his work in the role.  Peter Wemm took the
-	lead on the reorganization and administration of the FreeBSD
-	cluster, and with the Core Team's approval, Glen Barber and Ryan
-	Steinmetz were welcomed to the cluster administration team.</p>
-
-      <p>Based on the recommendation and experiences of Martin Wilke,
-	the Core Team also supported establishing a liaison role between
-	port managers and release engineers in order to improve their
-	communication, especially for preparing releases.  The Core Team
-	welcomes Bryan Drewery to this role.</p>
-
-      <p>Following up on the request from Eitan Adler, the Core Team
-	agreed to remove CVS from the base system, which was soon followed
-	by importing a lightweight version of Subversion tools,
-	implemented by Peter Wemm.</p>
-
-      <p>There were src commit bits issued for 3 new developers and 1
-	existing committer received extension in this quarter.</p>
-    <hr /><h2><a name="FreeBSD-Postmaster-Team" href="#FreeBSD-Postmaster-Team" id="FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  Postmaster Team
-	 &lt;<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the second quarter of 2013, the FreeBSD Postmaster Team has
-	implemented the following items that may be interest of the
-	general public:</p>
-
-      <ul>
-	<li>With help from <tt>clusteradm</tt>, found that
-	  <tt>unbound</tt> (the resolver used on <tt>mx1</tt> and
-	  <tt>mx2</tt>) is configured to perform DNSSEC validation which
-	  implies that if a signed zone fails validation,
-	  <tt>unbound</tt> refuses to use the information.  This had
-	  caused one person to be unable to exchange email with
-	  <tt>FreeBSD.org</tt> until the zone signatures were
-	  refreshed.</li>
-
-	<li>Created the <tt>freebsd-dtrace</tt> mailing list, requested
-	  by George Neville-Neil.</li>
-
-	<li>Resurrected the <tt>freebsd-testing</tt> mailing list,
-	  requested by Garrett Cooper.</li>
-
-	<li>Created the <tt>freebsd-tex</tt> mailing list, requested by
-	  Hiroki Sato.</li>
-
-	<li>In response to another comment that our message rejection
-	  message was unclear in the case that greylisting was the
-	  reason, re-worded that message.</li>
-
-	<li>Augmented the allowable MIME types for <tt>secteam</tt> with
-	  the following to permit sending encrypted messages:
-
-	  <ul>
-	    <li><tt>application/pgp-encrypted</tt></li>
-	    <li><tt>application/pkcs7-encrypted</tt></li>
-	    <li><tt>application/x-pkcs7-encrypted</tt></li>
-	    <li><tt>multipart/encrypted</tt></li>
-	  </ul>
-	</li>
-
-	<li>Began replacing <tt>freebsd-mozilla</tt> with
-	  <tt>freebsd-gecko</tt>.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/releases/8.4R/errata.html" title="http://www.freebsd.org/releases/8.4R/errata.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releases/8.4R/errata.html" title="">http://www.freebsd.org/releases/8.4R/errata.html</a></td></tr><tr><td><a href="http://www.freebsd.org/releases/9.2R/schedule.html" title="http://www.freebsd.org/releases/9.2R/schedule.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/releases/9.2R/schedule.html" title="">http://www.freebsd.org/releases/9.2R/schedule.html</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD�8.4-RELEASE cycle completed on June 7, 2013,
-	approximately two months behind the original schedule.  Please
-	be sure to read the Errata Notices for any post-release issues
-	discovered after 8.4-RELEASE.</p>
-
-      <p>The FreeBSD�9.2-RELEASE process will begin July 6, 2013.
-	Unless any critical issues arise, FreeBSD�9.2-RELEASE is
-	expected to be available late August or early September.</p>
-
-      <p>Users tracking the FreeBSD�9.<i>X</i> branch are encouraged
-	to test the -BETA and -RC builds whenever possible, and provide
-	feedback and report issues to the <a href="http://lists.freebsd.org/pipermail/freebsd-stable" shape="rect">freebsd-stable
-	  mailing list</a>.</p>
-    <hr /><h2><a name="FreeBSD-Security-Team" href="#FreeBSD-Security-Team" id="FreeBSD-Security-Team">FreeBSD Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  FreeBSD Security Team
-	 &lt;<a href="mailto:secteam@FreeBSD.org">secteam@FreeBSD.org</a>&gt;
-	</p>
-      <p>On April 15th Dag-Erling Sm�rgrav and Xin Li took over
-	as security officers for the FreeBSD Project, and the team welcomed
-	Qing Li back to the team in June.  This report briefly
-	summarizes the work of the Security Team from April until the
-	end of June.</p>
-
-      <p>The Security Team has released the following advisories:</p>
-
-      <ul>
-	<li><tt>FreeBSD-SA-13:05.nfsserver</tt>: Insufficient input
-	  validation in the NFS server (<tt>nfsd(8)</tt>), reported by
-	  Adam Nowacki.</li>
-
-	<li><tt>FreeBSD-SA-13:06.mmap</tt>: Privilege escalation via
-	  <tt>mmap()</tt>, reported by Konstantin Belousov.</li>
-      </ul>
-
-      <p>The Security Team has contributed to the following errata
-	notices:</p>
-
-      <ul>
-	<li><tt>FreeBSD-EN-13:02.vtnet</tt>: Frames are not properly
-	  forwarded to <tt>vtnet(4)</tt> when two or more MAC addresses
-	  are configured on QEMU 1.4.0 and later in 8.4-RELEASE,
-	  reported by Julian Stecklina.</li>
-
-	<li><tt>FreeBSD-EN-13:01.fxp</tt>: Initialization of
-	  <tt>fxp(4)</tt> network interfaces results in an infinite loop
-	  with <tt>dhclient(8)</tt> in 8.4-RELEASE, reported by Michael
-	  L. Squires.</li>
-      </ul>
-
-      <p>Per the request of Baptiste Daroussin, the Security Team has
-	also reviewed the source code of Poudriere, the port build and
-	test system which is planned to be used for producing
-	<tt>pkg(8)</tt> ("new-style") packages on the FreeBSD cluster.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="PC-BSD" href="#PC-BSD" id="PC-BSD">PC-BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pcbsd.org" title="http://www.pcbsd.org">PC-BSD Home Page</a></td><td>
-	    URL: <a href="http://www.pcbsd.org" title="PC-BSD Home Page">http://www.pcbsd.org</a></td></tr></table><p>
-	Contact:
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	</p>
-      <p>Progress on moving PC-BSD &amp; TrueOS to a "rolling release"
-	is happening quickly.  We have implemented our own package
-	repository, fully based on <tt>pkg(8)</tt>, which is updated twice
-	monthly, and are now hosting dedicated
-	<tt>freebsd-update(8)</tt> systems.  In addition to the
-	<tt>9.1-RELEASE</tt> ISO images, we have begun to create a
-	<tt>9-STABLE</tt> branch as well, using
-	<tt>freebsd-update(8)</tt> to push out the latest world and
-	kernel binaries on a monthly basis.</p>
-
-      <p>We are currently working on an implementation of ZFS Boot
-	Environments for desktops and servers.  These users to install
-	updates or experimental versions in separate ZFS clones and
-	select the one to run at boot time, providing an easy way of
-	testing upgrades before deployment.</p>
-    <hr /><h2><a name="Virtual-Private-Systems" href="#Virtual-Private-Systems" id="Virtual-Private-Systems">Virtual Private Systems</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.7he.at/freebsd/vps/" title="http://www.7he.at/freebsd/vps/"></a></td><td>
-	    URL: <a href="http://www.7he.at/freebsd/vps/" title="">http://www.7he.at/freebsd/vps/</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/vps/" title="http://svnweb.freebsd.org/base/projects/vps/"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/projects/vps/" title="">http://svnweb.freebsd.org/base/projects/vps/</a></td></tr></table><p>
-	Contact:
-	  Klaus
-	  Ohrhallinger
-	 &lt;<a href="mailto:k@7he.at">k@7he.at</a>&gt;
-	</p>
-      <p>VPS for FreeBSD is an OS-level based virtualization implementation
-	that supports advanced features like live migration.  It has
-	been recently imported into the Project's Subversion repository
-	as a project branch.  The code is currently of alpha
-	quality.</p>
-    <h3>Open tasks:</h3><ol><li>Test with many different guest setups/applications.  All
-	feedback is highly appreciated.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="AMD-GPU-Kernel-Mode-setting-Support" href="#AMD-GPU-Kernel-Mode-setting-Support" id="AMD-GPU-Kernel-Mode-setting-Support">AMD GPU Kernel Mode-setting Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/AMD_GPU" title="https://wiki.freebsd.org/AMD_GPU">Project status on the wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/AMD_GPU" title="Project status on the wiki">https://wiki.freebsd.org/AMD_GPU</a></td></tr></table><p>
-	Contact:
-	  Jean-S�bastien
-	  P�dron
-	 &lt;<a href="mailto:dumbbell@FreeBSD.org">dumbbell@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Due to non-FreeBSD-related activities from April to end of June,
-	the project progressed slowly:</p>
-
-      <ul>
-	<li>Some important problems in TTM were fixed and several others
-	  are being worked out.  Applications affected by these bugs are
-	  non-linear video editing software (which do not use Xv to
-	  preview the video) or "screen" of VirtualBox, for
-	  instance.</li>
-
-	<li>Regarding the locking issue with OpenGL, no work has been
-	  done yet.  <tt>glxgears</tt> works but some modern desktop
-	  environments or WebGL demos hang.  Once TTM bugs described
-	  above are fixed, this is the next target.</li>
-
-	<li>Patches to Mesa to make it build out-of-the-box were
-	  submitted upstream.  As of writing, some were committed but
-	  not all of them.  Additionally, as result of a joint work with
-	  Jonathan Gray (of OpenBSD), Mesa should work on FreeBSD, OpenBSD,
-	  and hopefully on other BSD flavors without additional
-	  patches.</li>
-      </ul>
-
-	<p>Several users tested the driver.  Andriy Gapon, Jonathan
-	  Gray, and Mark Kettenis (of OpenBSD) submitted patches.  kyzh
-	  kindly donated several discrete cards from different series.
-	  A big thanks to all those contributors!</p>
-
-	<p>The driver is still not stable enough for a wider call for
-	  testers.</p>
-    <h3>Open tasks:</h3><ol><li>Write instructions for the wiki to explain how to test the
-	driver.</li></ol><hr /><h2><a name="Improved-TCP-SYN-Cookies" href="#Improved-TCP-SYN-Cookies" id="Improved-TCP-SYN-Cookies">Improved TCP SYN Cookies</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=28838+0+current/freebsd-net" title="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=28838+0+current/freebsd-net">Description</a></td><td>
-	    URL: <a href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=28838+0+current/freebsd-net" title="Description">http://docs.freebsd.org/cgi/getmsg.cgi?fetch=28838+0+current/freebsd-net</a></td></tr><tr><td><a href="http://people.freebsd.org/~andre/syncookie-20130708.diff" title="http://people.freebsd.org/~andre/syncookie-20130708.diff">Patch</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~andre/syncookie-20130708.diff" title="Patch">http://people.freebsd.org/~andre/syncookie-20130708.diff</a></td></tr></table><p>
-	Contact:
-	  Andre
-	  Oppermann
-	 &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have had a SYN cookie implementation for quite some time now
-	but it has some limitations with current realities for window
-	scaling and SACK encoding the in the few available bits.</p>
-
-      <p>This patch updates and improves SYN cookies mainly by:</p>
-
-      <ol>
-	<li>Encoding of MSS, WSCALE (window scaling) and SACK into the
-	  ISN (initial sequence number) without the use of timestamp
-	  bits.</li>
-
-	<li>Switching to the very fast and cryptographically strong
-	  SipHash-2-4 hash MAC algorithm to protect the SYN cookie
-	  against forgery.</li>
-      </ol>
-
-      <p>The common parameters used on TCP sessions have changed quite a
-	bit since SYN cookies were invented some 17 years ago.  Today we
-	have a lot more bandwidth which makes use of window scaling
-	almost mandatory.  Also SACK has become standard as it makes
-	recovering from packet loss much more efficient.</p>
-
-      <p>The original SYN cookies method only stored an indexed MSS
-	value in the cookie.  This obviously is not sufficient any more
-	and breaks in the presence of WSCALE.  WSCALE information is
-	only exchanged during SYN and SYN-ACK.  If we cannot keep track
-	of it then we severely underestimate the available send or
-	receive window, compounded with the fact that with large window
-	scaling the window size information on the TCP segment header
-	would be even lower numerically.</p>
-
-      <p>A number of years back, SYN cookies were extended to store the
-	additional state in the TCP timestamp fields, if available on a
-	connection.  It has been adopted by Linux as well.  While
-	timestamps are common among the BSD, Linux and other Unix
-	systems, Windows never enabled them by default, thus they are
-	not present for the vast majority of clients seen on the
-	Internet.</p>
-
-      <p>The new improvement in this patch moves all necessary
-	information into the ISN again, removing the need for
-	timestamps.  Both the MSS and send WSCALE are stored in 3 bit
-	indexed form together with a single bit for SACK.  While we
-	cannot represent all possible MSS and WSCALE values in only 3
-	bits each (both are 16-bit fields in the TCP header), it turns
-	out that is not actually necessary.</p>
-
-      <p>These improvements allow one to run with SYN cookies only on
-	Internet-facing servers.  However while SYN cookies are
-	calculated and sent all the time, they are only used when the
-	syn cache overflows due to attacks or overload.  In that case
-	though, you can rest assured that no significant degradation in
-	TCP connection setup happens any more and that even Windows
-	clients can make use of window scaling and SACK.</p>
-    <h3>Open tasks:</h3><ol><li>Additional testing on busy servers.</li></ol><hr /><h2><a name="Multi-threaded-Pagedaemon" href="#Multi-threaded-Pagedaemon" id="Multi-threaded-Pagedaemon">Multi-threaded Pagedaemon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~kib/misc/pagedaemon-numa.1.patch" title="http://people.freebsd.org/~kib/misc/pagedaemon-numa.1.patch"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~kib/misc/pagedaemon-numa.1.patch" title="">http://people.freebsd.org/~kib/misc/pagedaemon-numa.1.patch</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project aims to improve scalability of the virtual memory
-	subsystem.  Based on a prototype change from Jeff Roberson,
-	per-domain page queues and per-domain pagedaemon working threads
-	have been implemented to enable this.  At the moment, the
-	domains coincide with the NUMA proximity domains, but this is
-	not neccessary and could be improved with further separation to
-	allow more parallelism in the pagedaemon.</p>
-
-      <p>The patch is relatively simple, with the most delicate parts
-	being the page laundry and OOM logic, which requires coordination
-	between all pagedaemon threads to prevent false triggering.</p>
-
-      <p>Testing on diverse workloads and on real multi-socket machines
-	is required.</p>
-
-      <p>This project is sponsored by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Debug on multi-domain NUMA machine.</li><li>Test, get review and commit.</li></ol><hr /><h2><a name="Native-iSCSI-Stack" href="#Native-iSCSI-Stack" id="Native-iSCSI-Stack">Native iSCSI Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="https://wiki.freebsd.org/Native%20iSCSI%20target"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="">https://wiki.freebsd.org/Native%20iSCSI%20target</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The native kernel iSCSI target and initiator project progressed
-	well over the April to June period.  The primary focus was to
-	introduce support for iSER (iSCSI over RDMA) in both the
-	initiator and the target.  Prerequisite for this was merging
-	some common parts together and implementing a workaround for the
-	lack of iSER support in userspace.  Apart from that, there were
-	a myriad of smaller improvements.  Such as creating more
-	user-friendly administration utilities, for example
-	<tt>iscsictl(8)</tt> which displays SCSI device nodes for each
-	iSCSI session.  This frees the user from getting the same
-	information through <tt>camcontrol(8)</tt>.  There are also
-	improvements in logging and manual pages.</p>
-
-      <p>Once the iSER support becomes stable, the work will focus on
-	performance optimizations.  The plan is to commit both the new
-	initiator and target in August to allow shipping them in 10.0.
-	The project will continue with implementing support for software
-	iWARP stack (useful mostly for testing and development), SCSI
-	passthrough and various other improvements.</p>
-
-	<p>This project is being sponsored by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Performance optimization.</li><li>Merge to FreeBSD <tt>head</tt>.</li></ol><hr /><h2><a name="Newcons-Reboot" href="#Newcons-Reboot" id="Newcons-Reboot">Newcons Reboot</a></h2><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	</p>
-      <p>The purpose of the Newcons project is to provide a new
-	interface for console and video output to graphic devices.  This
-	will allow simple drivers access the console and terminal mode
-	early, and framebuffer access for <tt>xorg</tt>.  Drivers will
-	not need embedded font bitmaps, color maps, or mouse cursor
-	bitmaps, as the whole infrastructure will be provided by the
-	<tt>vt(4)</tt> Newcons driver.</p>
-
-      <p>As the project includes Kernel Mode Setting (KMS) integration,
-	one of the goals is support for modern Xorg releases, allowing
-	the kernel to switch back to virtual terminal mode after
-	graphics mode or resolution used with <tt>xorg</tt> changes.</p>
-
-      <p>There are a lot of changes involved in the project.  Main tasks
-	include:</p>
-
-      <ul>
-	<li>Core functionality (almost done).</li>
-	<li>Mouse support.</li>
-	<li>KMS (kernel mode setting) support.</li>
-	<li>USB keyboard support.</li>
-	<li>Splash screen support (partially working).</li>
-	<li>Driver support.</li>
-	<li><tt>vidcontrol(1)</tt> support.</li>
-      </ul>
-
-      <p>The first deliverables of the project, including
-	<tt>moused(8)</tt>, <tt>ukbd(4)</tt>, and KMS support are expected
-	to arrive around the middle or end of August 2013.  The whole
-	project is expected to complete in November 2013.</p>
-
-      <p>This project is being sponsored by The FreeBSD Foundation.</p>
-
-      <p>Many thanks to Ed Schouten who started Newcons project and did
-	most of the work.</p>
-    <h3>Open tasks:</h3><ol><li>Provide different flavors of hardware for testing the
-	implementation.  Do not hesitate to volunteer when a call for
-	testing is announced.</li></ol><hr /><h2><a name="Realtek-RTL8188CU/RTL8192CU-USB-Wireless-Driver" href="#Realtek-RTL8188CU/RTL8192CU-USB-Wireless-Driver" id="Realtek-RTL8188CU/RTL8192CU-USB-Wireless-Driver">Realtek RTL8188CU/RTL8192CU USB Wireless Driver</a></h2><p>
-	Contact:
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kevin
-	  Lo
-	 &lt;<a href="mailto:kevlo@FreeBSD.org">kevlo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>urtwn(4)</tt> driver was imported from OpenBSD.  This
-	is a driver for very small Realtek USB WiFi cards which are pretty
-	inexpensive and can do 802.11n at the maximum theoretical speed
-	of 150 Mbps.  They make a good addition to embedded systems such
-	as the Raspberry Pi and the BeagleBone.  The driver requires
-	firmware that is available in the FreeBSD Ports Collection
-	(<tt>net/urtwn-firmware-kmod</tt>).  Note that 802.11n is not
-	yet supported.</p>
-    <hr /><h2><a name="SDIO-Driver" href="#SDIO-Driver" id="SDIO-Driver">SDIO Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SDIO" title="https://wiki.freebsd.org/SDIO">SDIO project page on the FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SDIO" title="SDIO project page on the FreeBSD wiki">https://wiki.freebsd.org/SDIO</a></td></tr><tr><td><a href="https://github.com/kibab/freebsd/tree/kibab-dplug" title="https://github.com/kibab/freebsd/tree/kibab-dplug">Source code</a></td><td>
-	    URL: <a href="https://github.com/kibab/freebsd/tree/kibab-dplug" title="Source code">https://github.com/kibab/freebsd/tree/kibab-dplug</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>SDIO is an interface designed as an extension for the existing
-	SD card standard, to allow connecting different peripherals to the
-	host with the standard SD controller.  Peripherals currently
-	sold at the general market include WLAN/BT modules, cameras,
-	fingerprint readers, barcode scanners.  The driver is
-	implemented as an extension to the existing MMC bus, adding a
-	lot of new SDIO-specific bus methods.  Getting information about
-	the card works, including querying all the supported I/O
-	functions.  Simple byte transfers and multi-byte reads work.</p>
-
-      <p>A prototype of the driver for Marvell SDIO WLAN/BT module is
-	also being developed, using the existing Linux driver as a
-	reference.</p>
-    <h3>Open tasks:</h3><ol><li>Extend MMC bus interface with more SDIO-specific bus methods
-	to allow child drivers to perform multi-byte in/out
-	transfers.</li><li>Write firmware loading code for the prototype of the WLAN
-	driver.  Further work on the WLAN driver should probably be done
-	as a separate project.</li><li>Implement detach path.  It has not been tested yet because
-	the DreamPlug hardware available does not have an external
-	SDIO-capable slot.</li></ol><hr /><h2><a name="V4L2-Update-in-the-Linuxulator" href="#V4L2-Update-in-the-Linuxulator" id="V4L2-Update-in-the-Linuxulator">V4L2 Update in the Linuxulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Alexander
-	  Leidinger
-	 &lt;<a href="mailto:netchild@FreeBSD.org">netchild@FreeBSD.org</a>&gt;
-	</p>
-      <p>The V4L2 support in the linuxulator was updated in FreeBSD
-	<tt>head</tt>.  This lets Skype v4 display video.</p>
-    <h3>Open tasks:</h3><ol><li>Find out why audio in Skype v4 stops working after some
-	calls.</li></ol><hr /><h2><a name="Wireless-Networking-Improvements" href="#Wireless-Networking-Improvements" id="Wireless-Networking-Improvements">Wireless Networking Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@FreeBSD.org">adrian@FreeBSD.org</a>&gt;
-	</p>
-      <p>Recently the FreeBSD wireless networking stack has received
-	updates in the following areas:</p>
-
-      <ul>
-	<li>Improved transmit locking in <tt>net80211(4)</tt> to
-	  eliminate a whole class of subtle race conditions leading to
-	  out-of-order packets being handed to the driver.</li>
-
-	<li>Spectral scan (FFT) information is now available for the
-	  AR9280, AR9285, AR9287 series NICs.</li>
-
-	<li>Added support for AR93xx, AR94xx, AR95xx NICs &#8212;
-	  <tt>hostap</tt>, <tt>adhoc</tt> and <tt>station</tt> modes
-	  have been tested, including 3x3 stream support for the those
-	  NICs where appropriate.</li>
-
-	<li>Implemented ps-poll handling in <tt>hostap</tt> mode.  This
-	  was required for correct behaviour with stations that implement
-	  aggressive power save.</li>
-
-	<li>Added AR933x SoC support &#8212; including all on-board
-	  peripherals &#8212; the <tt>8devices.com</tt> Carambola-2
-	  board is now fully supported and will run FreeBSD from NOR
-	  flash.</li>
-      </ul>
-    <hr /><h2><a name="Xen-Support-Improvements" href="#Xen-Support-Improvements" id="Xen-Support-Improvements">Xen Support Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary" title="http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary">Git repository</a></td><td>
-	    URL: <a href="http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary" title="Git repository">http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary</a></td></tr></table><p>
-	Contact:
-	  Justin T.
-	  Gibbs
-	 &lt;<a href="mailto:gibbs@FreeBSD.org">gibbs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Will
-	  Andrews
-	 &lt;<a href="mailto:will@FreeBSD.org">will@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Andre
-	  Oppermann
-	 &lt;<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Roger
-	  Pau Monn�
-	 &lt;<a href="mailto:roger.pau@citrix.com">roger.pau@citrix.com</a>&gt;
-	</p>
-      <p>FreeBSD Xen HVM can be further improved by using more PV
-	interfaces inside a HVM guest.  So far the following items have
-	been completed:</p>
-
-      <ul>
-	<li>Update Xen interface files.  (Merged into
-	  <tt>head</tt>)</li>
-	<li>Add support for the vector callback injection mechanism.
-	  This replaces the PCI interrupt and provides a per-cpu
-	  callback, which was not possible when using the PCI
-	  interrupt.</li>
-	<li>Rework event channel implementation and use the same code
-	  paths for both PV and PVHVM.</li>
-	<li>Implement PV one-shot event timers and timecounters.</li>
-	<li>Implement PV IPIs.</li>
-	<li>Live migration support for PV timers and PV IPIs.</li>
-      </ul>
-
-      <p>With this changes, FreeBSD will have a complete PVHVM port, this
-	will also set the ground for a future PVH port (when PVH support
-	is merged into Xen).</p>
-
-      <p>PVHVM allows a virtual machine that boots as a native guest to
-	be able to take full advantage of paravirtualized drivers,
-	giving a performance improvement in most I/O related tasks.  PVH
-	allows a guest to take advantage of hardware assistance for
-	memory management, but uses fully paravirtualized events and
-	boot procedure, which brings two significant advantages beyond
-	performance.  The first is that domain 0 does not have to run a
-	QEMU instance for emulated boot for PVH guests, which is a
-	common reason for hosting providers to charge more for Windows
-	and other HVM guests.  The second is that PVH domains can be
-	used as domain 0, without requiring different pmap (memory
-	management) code from the conventional kernel.  This will allow
-	us to ship a single kernel binary supporting bare metal
-	hardware, running as a Xen unprivileged guest, and eventually as
-	Xen domain 0.</p>
-
-      <p>Further improvements on blkfront and netfront have also been
-	commited:</p>
-
-      <ul>
-	<li>Fix netfront crash when detaching an interface.</li>
-	<li>Enable netfront to specify a maximum TSO length limiting the
-	  segment chain to what the Xen host side can handle after
-	  defragmentation.</li>
-	<li>Add barriers and flush support to blkfront.</li>
-      </ul>
-
-      <p>Netfront changes have been merged to <tt>stable</tt> branches,
-	blkfront changes are only in <tt>head</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>Merge remaining changes into <tt>head</tt>.</li></ol><hr /><h2><a name="ZFS-TRIM-and-Enhanced-BIO_DELETE-Support" href="#ZFS-TRIM-and-Enhanced-BIO_DELETE-Support" id="ZFS-TRIM-and-Enhanced-BIO_DELETE-Support">ZFS TRIM and Enhanced BIO_DELETE Support</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Steven
-	  Hartland
-	 &lt;<a href="mailto:smh@FreeBSD.org">smh@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of June, FreeBSD's ZFS implementation now includes
-	TRIM support in <tt>head</tt>, <tt>stable/9</tt>, and
-	<tt>stable/8</tt> branches.  This allows ZFS to help maintain
-	high performance on flash-based devices such as SSD's even under
-	high-load conditions.</p>
-
-      <p>When creating new pools and adding new devices to existing
-	pools it first performs a full-device level TRIM to help ensure
-	optimum starting performance.  This behaviour can be overridden
-	by setting the <tt>vfs.zfs.vdev.trim_on_init</tt> sysctl
-	variable to <tt>0</tt> if for example the disks are new or have
-	already been secure erased, which can also now be done using
-	<tt>camcontrol(8)</tt> security actions.</p>
-
-      <p>In order to support TRIM, the kernel requires the underlying
-	device driver supports <tt>BIO_DELETE</tt>.  This is currently
-	mapped through to hardware methods such as ATA TRIM and SCSI
-	UNMAP, which are commonly supported by SSDs via CAM.</p>
-
-      <p>In order to increase the supported hardware base, CAM's SCSI
-	layer was also enhanced to allow ATA TRIM via SATL ATA
-	Passthrough to be used in addition to the existing UNMAP and WS
-	methods.  This allows SATA disks attached to SCSI controllers
-	with CAM based drivers such as <tt>mps(4)</tt> and
-	<tt>mpt(4)</tt> to provide delete support.</p>
-
-      <p>Stats for ZFS TRIM can be monitored by looking at the sysctl
-	variables under <tt>kstat.zfs.misc.zio_trim</tt> in addition to
-	live GEOM delete stats via the <tt>gstat -d</tt> command.</p>
-
-      <p>This project was sponsored by <a href="http://www.multiplay.com" shape="rect">Multiplay</a> and implemented by
-	Pawel Jakub Dawidek.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Intel-IOMMU-(VT-d,-DMAR)-Support" href="#Intel-IOMMU-(VT-d,-DMAR)-Support" id="Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html" title="http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html"></a></td><td>
-	    URL: <a href="http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html" title="">http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-arch/2013-May/014368.html" title="http://lists.freebsd.org/pipermail/freebsd-arch/2013-May/014368.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-arch/2013-May/014368.html" title="">http://lists.freebsd.org/pipermail/freebsd-arch/2013-May/014368.html</a></td></tr><tr><td><a href="http://people.freebsd.org/~kib/misc/dmar.1.patch" title="http://people.freebsd.org/~kib/misc/dmar.1.patch"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~kib/misc/dmar.1.patch" title="">http://people.freebsd.org/~kib/misc/dmar.1.patch</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Intel VT-d is a set of extensions that were originally designed
-	to allow virtualizing devices.  It allows safe access to physical
-	devices from virtual machines and can also be used for better
-	isolation and performance increases.  A VT-d driver was
-	developed that implements the <tt>busdma(9)</tt> interface using
-	the DMA Remap units (DMARs) found in current Intel chipsets.
-	The driver provides reliability and security improvements for
-	the system by facilitating restricted access to main memory from
-	busmastering devices.</p>
-
-      <p>It also eliminates bounce buffering (copying) by allocating
-	remapped regions that satisfy a device's access limitations.</p>
-
-      <p>With additional work to define a suitable interface the VT-d
-	driver will also provide PCI pass-through functionality for
-	hypervisors.</p>
-
-      <p>This project is sponsored by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Implement workarounds for chipset errata.</li><li>Commit to HEAD after additional testing.</li><li>Rebalance MSI/MSI-X using interrupt remapping unit, also
-	required for x2APIC use on big machines.</li><li>Integrate with the Intel GPU MMU and handle Ironlake and
-	SandyBridge errata for the GFXVTd unit.</li><li>Provide an interface for VMM (hypervisors).</li><li>Consider implementing a driver for AMD's IOMMU.</li></ol><hr /><h2><a name="Superpages-for-ARMv7" href="#Superpages-for-ARMv7" id="Superpages-for-ARMv7">Superpages for ARMv7</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf" title="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf"></a></td><td>
-	    URL: <a href="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf" title="">http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/ARMSuperpages" title="https://wiki.freebsd.org/ARMSuperpages"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/ARMSuperpages" title="">https://wiki.freebsd.org/ARMSuperpages</a></td></tr><tr><td><a href="https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git" title="https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git"></a></td><td>
-	    URL: <a href="https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git" title="">https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git</a></td></tr></table><p>
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The ARM architecture is becoming more and more prevalent, with
-	increasing usage beyond the mobile and embedded space.  Among
-	the more interesting industry trends emerging in the recent
-	months, there has been the concept of "ARM server".  Some
-	top-tier companies, e.g.  Dell and HP, have already started to
-	develop such systems.</p>
-
-      <p>Key to success of FreeBSD in these new areas is dealing with the
-	sophisticated features of the platform, for example adding
-	support for superpages.</p>
-
-      <p>The objective of this project is to enable FreeBSD/arm to utilize
-	superpages which would allow efficient use of TLB translations
-	(by enlarging TLB coverage), leading to improved performance in
-	many applications and scalability.  This is intended to work on
-	ARMv7-based processors, however compatibility with ARMv6 will be
-	preserved.</p>
-
-      <p>The following steps have been made since the last status
-	report:</p>
-
-      <ul>
-	<li>Implement <tt>pmap_copy()</tt> to support <tt>fork()</tt>
-	  system calls.</li>
-	<li>Support for multiple page sizes.</li>
-	<li>Implement superpage creation, promotion, demotion, and
-	  eviction mechanisms.</li>
-	<li>Implement PV entry management for superpages.</li>
-	<li>Partially integrate code to the <tt>head</tt> branch.</li>
-      </ul>
-
-      <p>Next steps:</p>
-
-      <ul>
-	<li>Test and benchmark.</li>
-	<li>Complete integration into FreeBSD <tt>head</tt>.</li>
-      </ul>
-
-      <p>This project is jointly sponsored by The FreeBSD Foundation and
-	Semihalf.</p>
-    <h3>Open tasks:</h3><ol><li>Start utilizing superpages on ARMv6/v7.</li><li>Find bugs and debug.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="bsdconfig(8)-and-sysrc(8)" href="#bsdconfig(8)-and-sysrc(8)" id="bsdconfig(8)-and-sysrc(8)">bsdconfig(8) and sysrc(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://druidbsd.sourceforge.net/" title="http://druidbsd.sourceforge.net/"></a></td><td>
-	    URL: <a href="http://druidbsd.sourceforge.net/" title="">http://druidbsd.sourceforge.net/</a></td></tr></table><p>
-	Contact:
-	  Devin
-	  Teske
-	 &lt;<a href="mailto:dteske@FreeBSD.org">dteske@FreeBSD.org</a>&gt;
-	</p>
-      <p>New utilities have been introduced in FreeBSD base system:
-	<tt>bsdconfig(8)</tt> and <tt>sysrc(8)</tt>.
-	<tt>bsdconfig(8)</tt> is a replacement for the post-install
-	abilities of deprecated <tt>sysinstall(8)</tt>, while
-	<tt>sysrc(8)</tt> is a robust utility for managing
-	<tt>rc.conf(5)</tt> from the command line without a text
-	editor.</p>
-    <hr /><h2><a name="bsnmpd(1)-Support-in-hastd(8)" href="#bsnmpd(1)-Support-in-hastd(8)" id="bsnmpd(1)-Support-in-hastd(8)">bsnmpd(1) Support in hastd(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Mikolaj
-	  Golub
-	 &lt;<a href="mailto:trociny@FreeBSD.org">trociny@FreeBSD.org</a>&gt;
-	</p>
-      <p>A <tt>hastd(8)</tt> module for <tt>bsnmpd(1)</tt> has been
-	committed to FreeBSD <tt>head</tt> and merged to the
-	<tt>stable/8</tt> and <tt>stable/9</tt> branches recently.  This
-	module makes it possible to monitor and manage <tt>hastd(8)</tt>
-	via the SNMP protocol.</p>
-    <hr /><h2><a name="Capsicum" href="#Capsicum" id="Capsicum">Capsicum</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cl.cam.ac.uk/research/security/capsicum/" title="http://www.cl.cam.ac.uk/research/security/capsicum/"></a></td><td>
-	    URL: <a href="http://www.cl.cam.ac.uk/research/security/capsicum/" title="">http://www.cl.cam.ac.uk/research/security/capsicum/</a></td></tr><tr><td><a href="https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss" title="https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss"></a></td><td>
-	    URL: <a href="https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss" title="">https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss</a></td></tr></table><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Capsicum
-	  Mailing List
-	 &lt;<a href="mailto:cl-capsicum-discuss@lists.cam.ac.uk">cl-capsicum-discuss@lists.cam.ac.uk</a>&gt;
-	</p>
-      <p>Capsicum, a lightweight OS capability and sandboxing framework,
-	is being actively worked on.  In the last few months the
-	following tasks have been completed:</p>
-
-      <ul>
-	<li>Committed Capsicum overhaul to FreeBSD <tt>head</tt> (r247602).
-	  This allows to use capability rights in more places, simplifies
-	  kernel code and implements ability to limit <tt>ioctl(2)</tt>
-	  and <tt>fcntl(2)</tt> system calls.</li>
-
-	<li><tt>hastd(8)</tt> is now using Capsicum for sandboxing, as
-	  whitelisting ioctls is possible (r248297).</li>
-
-	<li><tt>auditdistd(8)</tt> is now using Capsicum for sandboxing,
-	  as it is now possible to setup append-only restriction on file
-	  descriptor (available in Perforce).</li>
-
-	<li>Implemented <tt>connectat(2)</tt> and <tt>bindat(2)</tt>
-	  system calls for UNIX domain sockets that are allowed in
-	  capability mode (r247667).</li>
-
-	<li>Implemented <tt>chflagsat(2)</tt> system call
-	  (r248599).</li>
-
-	<li>Revised the Casper daemon for application capabilities.</li>
-
-	<li>Implemented <tt>libcapsicum</tt> for application
-	  capabilities.</li>
-
-	<li>Implemented various Casper services to be able to use more
-	  functionality within a sandbox: <tt>system.dns</tt>,
-	  <tt>system.pwd</tt>, <tt>system.grp</tt>,
-	  <tt>system.random</tt>, <tt>system.filesystem</tt>,
-	  <tt>system.socket</tt>, <tt>system.sysctl</tt>.</li>
-
-	<li>Implemented Capsicum sandboxing for <tt>kdump(1)</tt> (from
-	  r251073 to r251167).  The version in Perforce also supports
-	  sandboxing for the <tt>-r</tt> flag, using Casper
-	  services.</li>
-
-	<li>Implemented Capsicum sandboxing for <tt>dhclient(8)</tt>
-	  (from r252612 to r252697).</li>
-
-	<li>Implemented Capsicum sandboxing for <tt>tcpdump(8)</tt>
-	  (available in Perforce).</li>
-
-	<li>Implemented Capsicum sandboxing for <tt>libmagic(3)</tt>
-	  (available in Perforce).</li>
-
-	<li>Implemented the <tt>libnv</tt> library for name/value pairs
-	  handling in the hope of wider adaptation across FreeBSD.</li>
-      </ul>
-
-      <p>For Capsicum-based sandboxing in the FreeBSD base system, the
-	commits referenced above and the provided code aim to serve as
-	examples.  We would like to see more FreeBSD tools to be sandboxed
-	&#8212; every tool that can parse data from untrusted sources,
-	for example.  This requires deep understanding of how the tool
-	in question works, not necessarily only Capsicum.</p>
-
-      <p>This work is being sponsored by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Get involved, make the Internet finally(!) a secure place.
-	Contact us at the <tt>cl-capsicum-discuss</tt> mailing list,
-	where we can provide guidelines on how to do sandboxing
-	properly.  The fame is there, waiting.</li></ol><hr /><h2><a name="LLDB-Debugger-Port" href="#LLDB-Debugger-Port" id="LLDB-Debugger-Port">LLDB Debugger Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/lldb" title="https://wiki.freebsd.org/lldb"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/lldb" title="">https://wiki.freebsd.org/lldb</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLDB is the the debugger project in the LLVM family.  It
-	supports the Mac OS X, Linux, and FreeBSD platforms, but the latter
-	has recently suffered under a lack of maintenance.</p>
-
-      <p>After cleaning bit rot in LLDB's FreeBSD support, it again builds
-	and can be used for basic debugging of single-threaded
-	applications.  The test suite also runs to completion, although
-	it experiences a large number of failures.</p>
-
-      <p>Ed Maste has been granted an LLDB commit bit, and is now
-	committing ongoing bug fixes and development directly to the
-	upstream repository.  There is a significant amount of work
-	still to be done, with one goal being the incorporation of
-	<tt>lldb</tt> into the base system.</p>
-
-      <p>This project is sponsored by DARPA/AFRL in collaboration with
-	SRI International and the University of Cambridge.</p>
-    <h3>Open tasks:</h3><ol><li>Add support for multithreaded processes.</li><li>Fix watchpoints.</li><li>Add support for remote debuging (<tt>gdbserver</tt> /
-	<tt>debugserver</tt>).</li><li>Add support for core files.</li><li>Add support for kernel debugging.</li><li>Verify i386 and ARM architectures.</li><li>Implement MIPS target support.</li><li>Verify cross-debugging.</li><li>Investigate and fix test suite failures.</li><li>Prepare <tt>lldb</tt> for incorporation into the base
-	system.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Haskell-Ports" href="#FreeBSD-Haskell-Ports" id="FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Haskell" title="http://wiki.freebsd.org/Haskell">FreeBSD Haskell wiki page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Haskell" title="FreeBSD Haskell wiki page">http://wiki.freebsd.org/Haskell</a></td></tr><tr><td><a href="https://github.com/freebsd-haskell/ports/" title="https://github.com/freebsd-haskell/ports/">FreeBSD Haskell ports repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd-haskell/ports/" title="FreeBSD Haskell ports repository">https://github.com/freebsd-haskell/ports/</a></td></tr><tr><td><a href="http://haskell.inf.elte.hu/packages/" title="http://haskell.inf.elte.hu/packages/">Experimental pkg(8) package repositories</a></td><td>
-	    URL: <a href="http://haskell.inf.elte.hu/packages/" title="Experimental pkg(8) package repositories">http://haskell.inf.elte.hu/packages/</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ashish
-	  SHUKLA
-	 &lt;<a href="mailto:ashish@FreeBSD.org">ashish@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are proud to announce that the FreeBSD Haskell Team has updated
-	the Haskell Platform to 2013.2.0.0, GHC to 7.6.3, as well as
-	updated existing ports to their latest stable versions.  In this
-	update, we provided experimental support for LLVM-based code
-	generation (disabled by default) to Haskell ports.  We also
-	added a number of new ports, which brings their count in the
-	FreeBSD Ports Collection to 402, and now Haskell ports play nicer
-	with <tt>portmaster(8)</tt>-based upgrades.</p>
-
-      <p>In cooperation with Konstantin Belousov and Dimitry Andric, we
-	have managed to unbreak the build of GHC on 32-bit 10.x systems,
-	so we have packages for 10.x again.  However, it turned out that
-	this bug (in thread signal delivery) can also affect the
-	building process for other platforms as well, which explains
-	some of the strange build breakages our users experienced in the
-	past.</p>
-
-      <p>We have also learned that there is <a href="http://www.haskell.org/pipermail/ghc-devs/2013-June/001506.html" shape="rect">ongoing work</a>
-	in the GHC upstream which will allow us to provide support for
-	building with Clang natively once GHC�7.8 becomes part of
-	the Haskell Platform.</p>
-    <h3>Open tasks:</h3><ol><li>Test experimental Clang/LLVM code generation support to
-	enable it by default.</li><li>Commit pending Haskell ports to the ports tree.</li><li>Port more (popular) Cabal packages.</li></ol><hr /><h2><a name="GNOME/FreeBSD" href="#GNOME/FreeBSD" id="GNOME/FreeBSD">GNOME/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact:
-	  FreeBSD GNOME Team
-	 &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The GNOME�3.6 work is moving along slowly but steadily.
-	Almost all the GNOME�3 desktop ports were updated to their
-	corresponding 3.6 versions.</p>
-
-      <p>A big challenge was taken by getting the <tt>webkit-gtk3</tt>
-	port updated to 2.0.3.  Currently programs using
-	<tt>webkit-gtk3</tt> crash on launch.  It is hard to find the
-	causes as the debug build of <tt>webkit-gtk</tt> either runs out of
-	memory or disk space on the developement system used.</p>
-    <h3>Open tasks:</h3><ol><li>Update the FreeBSD GNOME website with recent changes in the
-	ports tree, add new items in preparation for GNOME�3 and
-	Mate, etc.</li><li>Merge Glib 2.36, GTK+ 3.8 and related ports back to the
-	Ports Collection.</li><li>Continue work on GNOME�3.6, fix bugs and write code for
-	missing features.</li><li>Complete the port of MATE.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact:
-	  KDE
-	  FreeBSD
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE/FreeBSD Team has continued to improve the experience of
-	KDE software and Qt under FreeBSD.  During this quarter, the team
-	has kept most of the KDE and Qt ports up-to-date, working on the
-	following releases:</p>
-
-      <ul>
-	<li>KDE SC: 4.10.2, 4.10.3, 4.10.4</li>
-	<li>Qt: 5.0.2 (area51)</li>
-	<li>PyQt: 4.10.2; QScintilla 2.7.2; SIP: 4.14.7</li>
-	<li>KDevelop: 4.5.1</li>
-	<li>Calligra: 2.6.2</li>
-	<li>CMake: 2.8.11.1</li>
-	<li>Digikam (and KIPI-plugins): 3.1.0, 3.2.0 </li>
-	<li>KDE Telepathy: 0.6.0, 0.6.1</li>
-      </ul>
-
-      <p>As a result &#8212; according to <a href="http://portscout.freebsd.org/kde@freebsd.org.html" shape="rect">PortScout</a>
-	&#8212; <tt>kde@</tt> has 473 ports (up from 431), of which
-	98.73% are up-to-date (up from 93.5%).  iXsystems Inc.
-	continues to provided a machine for the team to build packages
-	and to test updates.  iXsystems Inc. has been providing the
-	KDE/FreeBSD Team with support for quite a long time and we are very
-	grateful for that.  This quarter, we would also like to thank
-	Steve Wills (<tt>swills@</tt>) for providing access to another
-	machine so that we can do our work even faster.</p>
-
-      <p>While a great deal of the team's efforts are focused towards
-	packaging released code, we also take a proactive stand in
-	making sure future versions of the software we port is also
-	going to work well on FreeBSD.  This involves being in close
-	contact with upstream, raising awareness of FreeBSD as an active
-	project and also sending actual patches that most of the time
-	benefit many other operating systems besides FreeBSD itself.  In
-	this regard, we have been dedicating a lot of time making sure
-	both <tt>clang</tt> and <tt>libc++</tt> are fully supported in
-	KDE and Qt.  Not only has this resulted in many patches being
-	sent to these projects, but the exposure to these large code
-	bases have been beneficial to the Clang-on-FreeBSD project as well.
-	Dimitry Andric (<tt>dim@</tt>) has been of great help as a point
-	of contact for all the issues we have faced.</p>
-
-      <p>As usual, the team is always looking for more testers and
-	porters so please contact us and visit our home page.  It would
-	be especially useful to have more helping hands on tasks such as
-	getting rid of the dependency on the defunct HAL project and
-	providing integration with KDE's Bluedevil Bluetooth
-	interface.</p>
-    <h3>Open tasks:</h3><ol><li>Update out-of-date ports, see <a href="http://portscout.freebsd.org/kde@freebsd.org.html" shape="rect">PortScout</a>
-	for a list.</li><li>Work on KDE 4.11 and Qt 5.</li><li>Make sure the whole KDE stack (including Qt) builds and works
-	correctly with <tt>clang</tt> and <tt>libc++</tt>.</li><li>Remove the dependency on HAL.</li></ol><hr /><h2><a name="Xfce/FreeBSD" href="#Xfce/FreeBSD" id="Xfce/FreeBSD">Xfce/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xfce" title="">https://wiki.freebsd.org/Xfce</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Xfce Team
-	 &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Xfce Team has updated its ports to the latest stable
-	releases, especially:</p>
-
-      <ul>
-	<li>Core (mostly bugfixes and translation updates):</li>
-
-	<ul>
-	  <li><tt>deskutils/xfce4-tumbler</tt> (0.1.29)</li>
-	  <li><tt>x11-wm/xfce4-panel</tt> (4.10.1)</li>
-	  <li><tt>sysutils/xfce4-settings</tt> (4.10.1)</li>
-	  <li><tt>x11-wm/xfce4-session</tt> (4.10.1)</li>
-	  <li><tt>sysutils/garcon</tt> (0.2.1)</li>
-	  <li><tt>x11/libxfce4util</tt> (4.10.1)</li>
-	  <li><tt>x11-wm/xfce4-wm</tt> (4.10.1)</li>
-	</ul>
-
-	<li>Applications:</li>
-
-	<ul>
-	  <li><tt>multimedia/xfce4-parole</tt> (0.5.1)</li>
-	  <li><tt>www/midori</tt> (0.5.2)</li>
-	  <li><tt>deskutils/xfce4-notifyd</tt> (0.2.4)</li>
-	  <li><tt>misc/xfce4-appfinder</tt> (4.10.1)</li>
-	  <li><tt>x11/xfce4-terminal</tt> (0.6.2)</li>
-	  <li><tt>x11-fm/thunar</tt> (1.6.3)</li>
-	</ul>
-
-	<li>Panel plugins:</li>
-
-	<ul>
-	  <li><tt>deskutils/xfce4-xkb-plugin</tt> (0.5.6)</li>
-	  <li><tt>textproc/xfce4-dict-plugin</tt> (0.7.0)</li>
-	  <li><tt>x11-clocks/xfce4-timer-plugin</tt> (1.5.0)</li>
-	  <li><tt>x11/xfce4-embed-plugin</tt> (new)</li>
-	</ul>
-
-	<li>Thunar plugins:</li>
-
-	<ul>
-	  <li><tt>audio/thunar-media-tags-plugin</tt> (0.2.1)</li>
-	  <li><tt>archivers/thunar-archive-plugin</tt> (0.3.1)</li>
-	</ul>
-
-	<li><tt>x11/xfce4-embed-plugin</tt> can integrate any
-	  application window into the Xfce panel.</li>
-
-	<li>A new plugin is also available which monitors and displays earthquakes,
-	  it is called <a href="http://people.freebsd.org/~olivierd/xfce4-equake-plugin.shar" shape="rect">xfce4-equake-plugin</a>.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Fix CPU issue with <tt>textproc/xfce4-dict-plugin</tt> (<a href="https://bugzilla.xfce.org/show_bug.cgi?id=10103" shape="rect">bug #10103</a>).</li><li>Investigate why <tt>midori-gtk3</tt> crashes too often.
-	(The port is finished, but some libraries are not present by
-	default in ports tree).</li><li>Fix <tt>x11-themes/gtk-xfce-engine</tt> with Gtk+ &gt;=3.6.</li></ol><hr /><h2><a name="xorg-on-FreeBSD" href="#xorg-on-FreeBSD" id="xorg-on-FreeBSD">xorg on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Xorg" title="http://wiki.freebsd.org/Xorg"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/Xorg" title="">http://wiki.freebsd.org/Xorg</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk"></a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Niclas
-	  Zeising
-	 &lt;<a href="mailto:zeising@FreeBSD.org">zeising@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Koop
-	  Mast
-	 &lt;<a href="mailto:kwm@FreeBSD.org">kwm@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the beginning of this quarter, work focused on making
-	the <tt>xorg</tt> update as robust and stable as possible in
-	preparation for the merge to ports.  As a part of this, ports
-	exp-runs were performed to find and resolve regressions and
-	other issues.  Once this was completed, <tt>xorg</tt> was
-	updated to version 7.7 on May 25, after more than a year of hard
-	work.</p>
-
-      <p>After the update, work immediately shifted to focus on updating
-	and patching <tt>xorg</tt> client libraries, since numerous
-	security issues had been identified in those.  Unfortunately,
-	this took a little longer than anticipated, but all fixes were
-	comitted eventually.</p>
-
-      <p>There has also been work on making the new <tt>xorg</tt>
-	distribution the default for FreeBSD�9.1 and later.  A patch
-	was sent out and tested with good results, but this is currently
-	postponed because switching virtual terminals is not working
-	with the KMS driver.</p>
-
-      <p>Currently, work is focusing on keeping <tt>xorg</tt> drivers
-	and libraries up to date.  Instead of making big updates every
-	year or less, minor updates to some libraries, applications and
-	drivers happen fairly regularly.  Focus is also starting to
-	shift towards newer versions of MESA and <tt>xorg-server</tt>,
-	but this is still very experimental.</p>
-    <h3>Open tasks:</h3><ol><li>Continue the porting effort of recent versions of MESA.
-	This is ongoing work, but integrating this into the development
-	repo is hard work.  Once this is completed, and KMS support for
-	ATI is more mature, more testing can be done.</li><li>Port Wayland.  The future of graphical environments in open
-	source operating system seems to be Wayland.  This needs to be
-	ported to FreeBSD so that a wider audience can test it, and so that
-	it eventually can be integrated into the ports tree, perhaps as
-	a replacement for the current <tt>xorg</tt>.</li><li>Look into replacements for HAL.  HAL is used for
-	hot-plugging of devices, but it has been long abandoned by
-	Linux.  A replacement, perhaps built on top of <tt>devd(8)</tt>,
-	would be nice to have.  This work should be coordinated with the
-	FreeBSD GNOME and KDE teams.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Upgrading-the-Documentation-Set-to-DocBook-5.0" href="#Upgrading-the-Documentation-Set-to-DocBook-5.0" id="Upgrading-the-Documentation-Set-to-DocBook-5.0">Upgrading the Documentation Set to DocBook 5.0</a></h2><p>
-	Contact:
-	  G�bor
-	  K�vesd�n
-	 &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Documentation Project has been using old versions of markup
-	standards until recently when we switched to a real XML
-	toolchain and DocBook 4.5.  However, we still depend on obsolete
-	technologies &#8212; DSSSL and Jade.  DocBook 5.0 provides
-	cleaner markup and some nice new features.</p>
-
-      <p>The objective of this project is to upgrade the documentation
-	set to DocBook 5.0 and to find a way to properly render our
-	sources without using DSSSL, since the DSSSL stylesheets are
-	discontinued and cannot render DocBook 5.0.  The documentation
-	sources have already been successfully transformed to DocBook
-	5.0 and updates to the rendering process are under
-	development.  The common opinion among FreeBSD developers is that
-	Java is a heavy dependency that should be avoided.  This has
-	suggested the transformation of DocBook sources to TeX and use
-	TeX as a rendering backend.  There are two ways to do this; the
-	sources can be transformed either directly or through the XSL FO
-	output generated by the stylesheets provided for the DocBook Project.
-	The latter approach has been chosen as a preferred
-	way since it better fits the existing documentation
-	infrastructure and provides easier customization.</p>
-
-      <p>This project is generously funded by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the implementation of the rendering process.</li><li>Integrate the rendering solution into the
-	infrastructure.</li><li>Merge back changes to <tt>head</tt>.</li></ol><hr /><br /><h1><a name="Events" href="#Events" id="Events">Events</a></h1><br /><h2><a name="BSD-Day-2013" href="#BSD-Day-2013" id="BSD-Day-2013">BSD-Day 2013</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bsdday.eu/2013" title="http://bsdday.eu/2013">BSD-Day 2013 web site</a></td><td>
-	    URL: <a href="http://bsdday.eu/2013" title="BSD-Day 2013 web site">http://bsdday.eu/2013</a></td></tr><tr><td><a href="http://www.youtube.com/playlist?list=PLJJHfhjb5TOjB-sHRwJBGWd8XA7nc1gk_" title="http://www.youtube.com/playlist?list=PLJJHfhjb5TOjB-sHRwJBGWd8XA7nc1gk_">YouTube playlist of talks</a></td><td>
-	    URL: <a href="http://www.youtube.com/playlist?list=PLJJHfhjb5TOjB-sHRwJBGWd8XA7nc1gk_" title="YouTube playlist of talks">http://www.youtube.com/playlist?list=PLJJHfhjb5TOjB-sHRwJBGWd8XA7nc1gk_</a></td></tr><tr><td><a href="https://picasaweb.google.com/116452848880746560170/BSDDay2013?authkey=Gv1sRgCNvIoMWoxNTRYw" title="https://picasaweb.google.com/116452848880746560170/BSDDay2013?authkey=Gv1sRgCNvIoMWoxNTRYw">Event photo album</a></td><td>
-	    URL: <a href="https://picasaweb.google.com/116452848880746560170/BSDDay2013?authkey=Gv1sRgCNvIoMWoxNTRYw" title="Event photo album">https://picasaweb.google.com/116452848880746560170/BSDDay2013?authkey=Gv1sRgCNvIoMWoxNTRYw</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The BSD-Day is a now recurring excuse for BSD developers and
-	users to meet up in person, share some beers and talk about what
-	they are working on these days.  There was a detour this year to
-	visit the beautiful city of Naples of Italy, the home of pizza.
-	Fortunately, the event has again gained support from numerous
-	and generous sponsors, such as The FreeBSD Foundation, the EMC
-	Corporation, iXsystems, FreeBSDMall, BSD Magazine, and many
-	others which enabled us to cover the costs of travel and
-	accommodation for the speakers.  We are really grateful for
-	this.</p>
-
-      <p>Similarly to the previous years, the whole event started with a
-	dinner in the downtown (somewhere around the Irish Pub) on
-	Friday which suddenly turned into a do-it-yourself pizza-fest.
-	Then it was followed by the Saturday event at the Institute of
-	Biostructures and Bioimaging.  There we had a lot of attendees
-	for the associated BSDA exam in the morning &#8212; 8 persons.
-	The event itself had many interesting topics as well, for
-	example moving MCLinker into the BSD world, organization and
-	culture of the FreeBSD Project, the new <tt>callout(9)</tt>
-	framework, building and testing ports with Poudriere and
-	Tinderbox, FreeBSD in the embedded space, or building reliable VPN
-	networks with OpenBSD.  See the links in the report for
-	more.</p>
-    <hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="New-Capsicum-Features" href="#New-Capsicum-Features" id="New-Capsicum-Features">New Capsicum Features</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2013/CapsicumFeatures" title="https://wiki.freebsd.org/SummerOfCode2013/CapsicumFeatures"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2013/CapsicumFeatures" title="">https://wiki.freebsd.org/SummerOfCode2013/CapsicumFeatures</a></td></tr></table><p>
-	Contact:
-	  Mariusz
-	  Zaborski
-	 &lt;<a href="mailto:oshogbo@FreeBSD.org">oshogbo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Capsicum is a lightweight OS capability and sandboxing
-	framework implemented in FreeBSD.  This is still a new technology,
-	so there is a lot of space for improvements.  Thanks to the
-	Google Summer of Code program and Pawel Jakub Dawidek for
-	volunteering as mentor, Mariusz will have the chance to work on
-	this project in the summer.</p>
-
-      <p>The work on sandboxing the <tt>rwho(1)</tt> and
-	<tt>rwhod(8)</tt> utilities was completed recently.  There is
-	also a plan to implement two new modules for Casper.  Casper is
-	a daemon to provide services for applications using Capsicum's
-	capability mode.  Some experimentation with implementing two new
-	capability rights is in progress, so is porting one more program
-	to use the existing features of the Capsicum framework.</p>
-    <h3>Open tasks:</h3><ol><li><tt>system.unix</tt> &#8212; a Casper module provides
-	connect and listen on Unix domain socket.</li><li><tt>system.udp</tt> &#8212; a Casper module enabling
-	connect, listen, send, and receive of UDP packets.</li><li>Implementing sandboxing for <tt>fetch(1)</tt>.</li><li>Introduce new capability rights: <tt>CAP_SEND_RIGHTS</tt>
-	and <tt>CAP_RECV_RIGHTS</tt>.</li></ol><hr /><h2><a name="Qt-and-GTK+-Frontends-for-pkg(8)" href="#Qt-and-GTK+-Frontends-for-pkg(8)" id="Qt-and-GTK+-Frontends-for-pkg(8)">Qt and GTK+ Frontends for pkg(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2013/pkgQtGtk" title="https://wiki.freebsd.org/SummerOfCode2013/pkgQtGtk"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2013/pkgQtGtk" title="">https://wiki.freebsd.org/SummerOfCode2013/pkgQtGtk</a></td></tr></table><p>
-	Contact:
-	  Justin
-	  Muniz
-	 &lt;<a href="mailto:jmuniz@FreeBSD.org">jmuniz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Eitan
-	  Adler
-	 &lt;<a href="mailto:eadler@FreeBSD.org">eadler@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is part of Google Summer of Code.  Work has only
-just begun, and the code is in its infancy.  The Subversion repository
-holds experimental code that is actively being developed.  Development
-should be concluded before the end of September, and the project will
-enter the maintenance phase of its life cycle.</p>
-    <h3>Open tasks:</h3><ol><li>Work with Matt Windsor to create a <tt>pkg(8)</tt> backend
-	for PackageKit.</li><li>Extend PackageKit's Qt frontend to offer more functionality
-through <tt>pkg(8)</tt>.</li><li>Extend PackageKit's GKT+ frontend to offer more
-functionality through <tt>pkg(8)</tt>.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>We started the quarter with our "Raise a Million &#8212; Spend
-	a Million" Spring Fundraiser.  This was the first of three major
-	fundraisers scheduled for the year.  We were pleased to have
-	raised $365,291 by the end of the campaign &#8212; May 31.  Last
-	year, by the same time, we had raised only $56,196.  We have
-	started this year off with a much better fundraising strategy.
-	We want to send a big thank you to everyone out there that has
-	made a donation in 2013.  Your early donations have made a
-	significant impact on our fundraising endeavors so far this
-	year.</p>
-
-      <p>Some things we accomplished this last quarter are:</p>
-
-      <ul>
-	<li>Attended BSDCan in Ottawa, Texas LinuxFest in Austin,
-	  SouthEast LinuxFest in Charlotte, and ICANN 46 meeting in
-	  Beijing.</li>
-
-	<li>We were a Gold Sponsor for BSDCan 2013 and sponsored 7
-	  developers to attend the conference.</li>
-
-	<li>We signed up to be a Platinum Sponsor for EuroBSDCon
-	  2013.</li>
-
-	<li>We sponsored 1 developer to attend OpenHelp.</li>
-
-	<li>Recognized Mark Linimon, Simon L. B. Nielsen, Bjoern A.
-	  Zeeb, and Ken Smith, at BSDCan, for their significant
-	  contributions to FreeBSD.  We also recognized Dan Langille for
-	  his tireless effort of putting on BSDCan for 10 years.</li>
-
-	<li>We sponsored the developer and vendor summits at BSDCan,
-	  with 100 and 30 attendees respectively.</li>
-
-	<li>We sponsored BSD-Day 2013 that was held in Naples, Italy on
-	  April 6.</li>
-
-	<li>We held our annual board meeting in Ottawa.</li>
-
-	<li>We sponsored the following projects: Capsicum, ARM
-	  Superpages, iSCSI, Page Queue Locking, Input/Output Memory
-	  Management Unit, Documentation project infrastructure, and
-	  writing white papers.</li>
-
-	<li>We hired Edward Tomasz Napiera&#322;a as the second member
-	  of our technical staff to work on FreeBSD projects
-	  full-time.</li>
-
-	<li>We hired Ed Maste as Director of Project Development.</li>
-
-	<li>With our continued support of building out the FreeBSD
-	  infrastructure, we purchased high-end servers for the Sentex Lab
-	  to be used with the latest 40 Gbps Ethernet cards from Chelsio
-	  to do performance testing and analysis, smaller servers for
-	  firewalls for NYI and ISC, and cables to connect our Juniper
-	  switches together into a bigger Juniper switch we purchased
-	  for NYI.</li>
-      </ul>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2013-05-devsummit.html b/website/content/en/status/report-2013-05-devsummit.html
deleted file mode 100644
index d46602d409..0000000000
--- a/website/content/en/status/report-2013-05-devsummit.html
+++ /dev/null
@@ -1,532 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>BSDCan 2013 DevSummit Special Status Report</h1><p>This special status report contains a summary of the discussions
-      from the various working groups at the BSDCan 2013 DevSummit.  The
-      FreeBSD Project organizes DevSummits at various events, typically at
-      the major BSD conferences, so that developers can meet and discuss
-      matters in person.</p><hr /><ul><li><a href="#Beyond-Buildworld...">Beyond Buildworld...</a></li><li><a href="#Documentation">Documentation</a></li><li><a href="#Network-Receive-Performance">Network Receive Performance</a></li><li><a href="#Ports-and-Packages">Ports and Packages</a></li><li><a href="#UEFI">UEFI</a></li><li><a href="#Virtualization">Virtualization</a></li></ul><hr /><h2><a name="Beyond-Buildworld..." href="#Beyond-Buildworld..." id="Beyond-Buildworld...">Beyond Buildworld...</a></h2><p>
-	Contact:
-          Brooks
-
-          Davis
-         &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>Buildworld is the target for building the base system in the
-	venerable FreeBSD build system.  This session aimed to investigate
-	the current limitations, discuss recent improvements, and
-	propose future directions for this process.</p>
-
-      <p>Over recent years, FreeBSD has been used increasingly in embedded
-	systems and so cross development has become a lot more
-	important.  One of the changes recently committed by Brooks
-	Davis now permits building the entire base system and creating a
-	disk image without root privileges.  This makes embedded
-	development easier, as a number of users can now share an
-	expensive development box, capable of performing builds
-	quickly, without having to give all of them root.</p>
-
-      <p>This session also discussed the bmake import, which brings in
-	NetBSD's make along with some improvements from Juniper, which
-	should allow much more accurate dependency tracking and faster
-	parallel and incremental builds.  This should have some
-	additional benefits to the rest of the project, for example by
-	making our tinderbox infrastructure, which notifies developers if
-	the have broken the build, able to report failures much more
-	quickly.</p>
-
-      <p>One frequently requested capability, which is now being
-	investigated by Marcel Moolenar, is the ability to build FreeBSD
-	from other platforms.  Currently, developing a FreeBSD-based
-	embedded system requires a FreeBSD host system for building, which
-	is a barrier to entry that we would like to avoid.</p>
-
-      <p>There are a number of changes to our toolchain planned for the
-	10.x and 11.x timescales, including replacing GNU binutils with
-	LLVM-based tools and importing MCLinker.  These are unlikely to
-	be the default in 10.0, but we hope to be able to provide a
-	GPL-free base system as a functional option this year.</p>
-    <hr /><h2><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h2><p>
-	Contact:
-          Dru
-
-          Lavigne
-         &lt;<a href="mailto:dru@FreeBSD.org">dru@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-          Benedict
-
-          Reuschling
-         &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The documentation working group met during the main sessions
-	and also had several productive evenings improving the state of
-	FreeBSD documentation.</p>
-
-      <p>The FreeBSD Handbook has undergone some significant updates
-	recently and there is work underway to create a snapshot that
-	will be available as a professionally published print edition.
-	There are still some sections in need of updates before this can
-	happen and the documentation team is working on engaging the
-	relevant developers to review this content.</p>
-
-      <p>The FreeBSD web site redesign was discussed.  Currently, many of
-	the most commonly accessed pages are difficult to navigate to.
-	Its visual design is also somewhat dated.  The documentation
-	team is working to design an improved structure and has several
-	offers of assistance with the appearance.</p>
-
-      <p>The FreeBSD Project is international and many of the contributors
-	do not have English as their first language.  To encourage more
-	participation from the rest of the world, it is important to
-	have high-quality translations of the documentation.  PC-BSD
-	uses pootle (available from the FreeBSD ports tree) to assist with
-	keeping translations consistent and up to date and we are
-	evaluating doing the same for FreeBSD.</p>
-
-      <p>The documentation team plans to have a Docs Hackathon colocated
-	with the Cambridge DevSummit in August.</p>
-    <hr /><h2><a name="Network-Receive-Performance" href="#Network-Receive-Performance" id="Network-Receive-Performance">Network Receive Performance</a></h2><p>
-	Contact:
-          George
-
-          Neville-Neil
-         &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD has traditionally been a platform with support for very
-	high performance networking.  This is one of the main reasons
-	why it was selected for the Netflix streaming appliance, which
-	is currently responsible for over 20% of the Internet traffic in
-	the USA.  The goal of this session was to discuss current
-	bottlenecks at the receiving end of connections.</p>
-
-      <p>Modern network cards support multiple receive queues and can
-	deliver packets into them depending on various criteria.  The
-	design of a good API for accessing this functionality is very
-	important, as it shortens the path between a packet arriving in
-	the card and it being delivered into a userspace process.  In an
-	extreme case, for example with cluster applications or virtual
-	machines, the receive queue may be accessed directly from a
-	process bypassing the kernel.  In a more conventional setting,
-	the packets should be delivered to a kernel thread on the same
-	CPU as the receiving process, so that the copy to userspace is
-	cheap.</p>
-
-      <p>The group examined a number of different proposals, including
-	some patches, and discussed the requirements for a general API.
-	This work is ongoing.</p>
-    <hr /><h2><a name="Ports-and-Packages" href="#Ports-and-Packages" id="Ports-and-Packages">Ports and Packages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~bdrewery/poudriere-0515.pdf" title="http://people.freebsd.org/~bdrewery/poudriere-0515.pdf">Slides on the status of Poudriere</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~bdrewery/poudriere-0515.pdf" title="Slides on the status of Poudriere">http://people.freebsd.org/~bdrewery/poudriere-0515.pdf</a></td></tr><tr><td><a href="http://people.freebsd.org/~sson/imgact_binmisc/20130515-bsdcan-xbuild-ports.pdf" title="http://people.freebsd.org/~sson/imgact_binmisc/20130515-bsdcan-xbuild-ports.pdf">Slides on QEMU-based cross-building</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~sson/imgact_binmisc/20130515-bsdcan-xbuild-ports.pdf" title="Slides on QEMU-based cross-building">http://people.freebsd.org/~sson/imgact_binmisc/20130515-bsdcan-xbuild-ports.pdf</a></td></tr></table><p>
-	Contact:
-          Erwin
-
-          Lansing
-         &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>The working group on ports and packages discussed the fallout
-	from the security incident and the lessons learned.  Old-style
-	binary package building is now online and the infrastructure for
-	building them is in a much more maintainable state.  Building
-	<tt>pkg(8)</tt> (new-style) packages should be possible
-	soon.</p>
-
-      <p>Bryan Drewery presented a short talk on the status of
-	Poudriere, the new package builder.  This is usable for building
-	package sets for local deployment and for the official FreeBSD
-	packages.  When the original package building infrastructure was
-	designed, it took most of a day to build a large port like
-	Mozilla on a high-end machine.  Now, we have single machines in
-	the FreeBSD cluster that can build the entire ports tree in a day.
-	Poudriere is designed for this model and does not rely on ports
-	supporting parallel builds internally.  Instead, it builds each
-	port in a separate jail, with ports that do not depend on each
-	other being built in parallel when there are spare CPUs.</p>
-
-      <p>Moving forward, the project plans to decouple package releases
-	from base system releases.  Each base system release is intended
-	to be backwards compatible within that release series and so any
-	packages for N.x should work on N.x+1.  The project will build
-	weekly package sets for each branch that will be retained for
-	two weeks, with no QA, and monthly sets that will undergo QA and
-	will be available for 12 months.</p>
-
-      <p>Stacy Son and Brooks Davis talked about packages for less
-	common architectures.  Stacy has worked to bring QEMU usermode
-	support to FreeBSD.  This means that MIPS or ARM FreeBSD binaries can
-	run on an x86 FreeBSD system.  The kernel will detect the foreign
-	binary and launch it in the emulator.  Stacy has been using this
-	to create jails containing a cross compiler and shell for the
-	host architecture, but native libraries for the target.  This
-	allows ports that are not cross-build aware to run configure
-	scripts that do things like compile executables and run them,
-	but still has the most processor-intensive part of the build
-	(compiling and linking) running outside of emulation.  With this
-	approach, we are easily able to build weekly package sets for
-	MIPS and ARM on a single x86 box.  For installing onto embedded
-	systems, there are still some open problems.  The
-	<tt>pkg(8)</tt> infrastructure can install many packages onto a
-	disk image, but will not be able to run complex post-install
-	scripts without the target system booting.</p>
-    <hr /><h2><a name="UEFI" href="#UEFI" id="UEFI">UEFI</a></h2><p>
-	Contact:
-          Benno
-
-          Rice
-         &lt;<a href="mailto:benno@FreeBSD.org">benno@FreeBSD.org</a>&gt;
-	</p>
-      <p>UEFI is the new boot firmware standard pushed by Intel.  It
-	comes with a number of challenges, including the SecureBoot
-	restriction, that prevents the firmware from booting unsigned
-	kernels and bootloaders.  This is not currently a problem, as
-	most systems either do not enable this restriction by default,
-	or make it easy to disable, but it will be more important in the
-	future.</p>
-
-      <p>The goal for UEFI support in FreeBSD is to merge the bootloader
-	that is currently in the projects branch, which will perform
-	signature verification and then hand off to the more
-	conventional FreeBSD bootloader.  This loader will be very simple
-	and so will need changing (and re-signing) fairly infrequently.
-	The FreeBSD Foundation will be responsible for ensuring that the
-	bootloader is signed and so will work with SecureBoot.</p>
-
-      <p>There are a number of restructuring and refactoring tasks that
-	will need to be done over the next few months to ensure that the
-	FreeBSD boot process works cleanly with UEFI.  These include
-	removing some code duplication between various platforms that
-	use UEFI, removing some legacy support from the i386 kernel, and
-	restructuring how some of the bootloader code is built.
-	Interaction with UEFI will be simplified once clang supports the
-	MS Windows calling convention (used by UEFI) when generating
-	UNIX binaries.  Benno Rice has been working on this, with some
-	assistence from David Chisnall, and this support should appear
-	soon.</p>
-    <hr /><h2><a name="Virtualization" href="#Virtualization" id="Virtualization">Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~grehan/bsdcan13_virt_ext.pdf" title="http://people.freebsd.org/~grehan/bsdcan13_virt_ext.pdf">Overall status slides</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~grehan/bsdcan13_virt_ext.pdf" title="Overall status slides">http://people.freebsd.org/~grehan/bsdcan13_virt_ext.pdf</a></td></tr><tr><td><a href="http://people.freebsd.org/~gibbs/XenStatusBSDCan2013.pdf" title="http://people.freebsd.org/~gibbs/XenStatusBSDCan2013.pdf">Xen status slides</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~gibbs/XenStatusBSDCan2013.pdf" title="Xen status slides">http://people.freebsd.org/~gibbs/XenStatusBSDCan2013.pdf</a></td></tr><tr><td><a href="http://people.freebsd.org/~bryanv/pdfs/bsdcan2013_virtio.pdf" title="http://people.freebsd.org/~bryanv/pdfs/bsdcan2013_virtio.pdf">VirtIO status slides</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~bryanv/pdfs/bsdcan2013_virtio.pdf" title="VirtIO status slides">http://people.freebsd.org/~bryanv/pdfs/bsdcan2013_virtio.pdf</a></td></tr><tr><td><a href="http://people.freebsd.org/~grehan/bsdcan13_bhyve.pdf" title="http://people.freebsd.org/~grehan/bsdcan13_bhyve.pdf">Bhyve slides</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~grehan/bsdcan13_bhyve.pdf" title="Bhyve slides">http://people.freebsd.org/~grehan/bsdcan13_bhyve.pdf</a></td></tr></table><p>
-	Contact:
-          Peter
-
-          Grehan
-         &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>Virtualization is an increasingly important topic, with large
-	providers like Amazon deploying huge numbers of VMs and many
-	users deploying VMs on desktop systems for testing and backwards
-	compatibility.  Today, FreeBSD supports a wide variety of
-	virtualization options.  This working group discussed the
-	current status and future directions of several of them.</p>
-
-      <p>Xen is the de-facto standard for large-scale virtualization and
-	FreeBSD has supported running as a guest for some time.
-	SpectraLogic has funded recent work on improving this, with two
-	overlapping goals.  The first is to allow FreeBSD to run as the
-	Domain 0 operating system.  This is the operating system that
-	runs with elevated privilege and is allowed to talk directly to
-	the hardware and which must provide the virtualized devices to
-	the guests.  This requires full paravirtualization support.
-	Related to this is the ability to use more paravirtualized
-	hardware when booting as a hardware virtualized guest.  This
-	includes support for the new PVH mode, which uses hardware
-	support for memory operations but paravirtualized drivers for
-	everything else, giving the best performance possible with
-	Xen.</p>
-
-      <p>The FreeBSD VirtualBox port is progressing well, with preliminary
-	support for 3D accleration in guests.  The patches for
-	Microsoft's HyperV, provided by Microsoft, are currently being
-	tested with a view to incorporating them into FreeBSD 10.</p>
-
-      <p>FreeBSD also includes its own virtualization infrastructure, bhyve
-	(pronounced beehive), which is designed to support
-	hardware-assisted virtualization.  This has made significant
-	progress over the past year, including now supporting AMD's
-	virtualization extensions as well as those from Intel.  With so
-	many options, FreeBSD is now very well placed in terms of
-	virtualization, both as a host and a guest.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2013-07-2013-09.html b/website/content/en/status/report-2013-07-2013-09.html
deleted file mode 100644
index b939432207..0000000000
--- a/website/content/en/status/report-2013-07-2013-09.html
+++ /dev/null
@@ -1,1350 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between July and
-      September 2013.  This is the third of four reports planned for
-      2013.</p><p>We have had another very active three months in the FreeBSD world,
-      including two Developer Summits (BSDCam and EuroBSDcon) that will be
-      covered in separate status reports.  FreeBSD continues to push hard
-      on security, with improvements to both the performance and
-      reliability of the random number generation, and more
-      compartmentalisation in programs in the base system.  For
-      developers, there is work on a new modern debugger.  There is also
-      a significant amount of of modernization in the support for
-      Objective-C and Ada via ports, making FreeBSD a first-rate platform
-      for developing in either language, in addition to the existing
-      C++11 and C11 support already present in the base system.  Server
-      users will be pleased to see improvements in the iSCSI stack and
-      scalability allowing over a million I/O operations per second on
-      commodity hardware, while desktop users will see improvements in X
-      support for new GPUs and for possible X replacements.</p><p>Thanks to all the reporters for the excellent work!  This report
-      contains 30 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between October and
-      December 2013 is January 14th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Static-Code-Analysis">Static Code Analysis</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#AES-NI-Improvements-for-GELI">AES-NI Improvements for GELI</a></li><li><a href="#Atomic-&quot;close-on-exec&quot;">Atomic "close-on-exec"</a></li><li><a href="#Continuation-of-the-Newcons-Project">Continuation of the Newcons Project</a></li><li><a href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#Reworking-random(4)">Reworking random(4)</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#VirtIO-Network-Multiqueue">VirtIO Network Multiqueue</a></li><li><a href="#VMware-VMXNET3-Driver">VMware VMXNET3 Driver</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Cubieboard2">FreeBSD on Cubieboard2</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/pseries">FreeBSD/pseries</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li><li><a href="#Superpages-for-ARMv7">Superpages for ARMv7</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Capsicum">Capsicum</a></li><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></li><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#GNUstep-on-FreeBSD">GNUstep on FreeBSD</a></li><li><a href="#X.Org-on-FreeBSD">X.Org on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Documentation-Project-Primer-Edit">FreeBSD Documentation Project Primer Edit</a></li><li><a href="#The-entities-Documentation-Branch">The entities Documentation Branch</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Download-Manager-Service-for-the-Ports-Collection">Download Manager Service for the Ports Collection</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the third quarter of 2013, the Core Team focused on
-	officially launching <tt>pkg.freebsd.org</tt>, the Project's
-	official <tt>pkg(8)</tt> repository, in cooperation with the
-	Port Management Team, the Security Team, and the Cluster
-	Administration Team.  At the same time, there are plans to
-	gradually deprecate the use of the old <tt>pkg_add(1)</tt>,
-	allowing <tt>pkg(8)</tt> to be the default binary package
-	management solution for FreeBSD, arriving with 10.0-RELEASE.
-	Thomas Abthorpe has been appointed to the role of liaison
-	between the Core Team and the Ports Management Team, in order to
-	make the collaboration more effective.</p>
-
-      <p>David Chisnall has joined the group that publishes the
-	Quarterly Status reports and compiled a special status report on
-	the results of the BSDCan�2013 Developer Summit.  David
-	also took the lead role on the organization of an off-season
-	developer summit in Cambridge, UK, which was finally held at the
-	end of August.  For the items discussed in Cambridge,
-	preparation of a detailed report is still in progress.</p>
-
-      <p>There were src commit bits issued for 5 new developers and most
-	of the src commits being idle more than 12 months have been
-	taken into safekeeping as result of a major cleanup to the
-	repository access file in July, performed by Gavin Atkinson.</p>
-    <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="http://www.freebsd.org/doc/en/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout" title="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout" title="">http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout</a></td></tr></table><p>
-	Contact: FreeBSD Port Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree contains approximately 24,400 ports, while the
-	PR count exceeds 1,900.  In the third quarter, we added four new
-	committers and took in six commit bits for safekeeping.</p>
-
-      <p>A significant amount of effort has gone into tweaking and
-	manipulating the infrastructure to modernize and update it, in
-	preperation for <tt>pkg(8)</tt> replacing the old
-	<tt>pkg_add(1)</tt> infrastructure, as well as preparing for
-	FreeBSD�10.0 with Clang as default compiler, <tt>libc++</tt>
-	as the default C++ standard library, and <tt>iconv(1)</tt>
-	integrated into <tt>libc</tt>.</p>
-
-      <p>Automated procedures for quality assurance have been
-	implemented, notably <tt>pkg-fallout</tt>.  All porters are
-	encouraged to subscribe to the associated mailing list (see
-	links), and do their part to fix ports for <tt>pkg(8)</tt> and
-	Clang readiness.</p>
-
-      <p>Many iterations of tests were run to ensure that as many
-	packages as possible would be available for the 9.2 release.</p>
-    <h3>Open tasks:</h3><ol><li>Most ports PRs are assigned, we now need to focus on
-	testing, committing, and closing.</li></ol><hr /><h2><a name="FreeBSD-Postmaster-Team" href="#FreeBSD-Postmaster-Team" id="FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-fortran" title="http://lists.freebsd.org/mailman/listinfo/freebsd-fortran"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-fortran" title="">http://lists.freebsd.org/mailman/listinfo/freebsd-fortran</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout" title="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout" title="">http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-users-jp" title="http://lists.freebsd.org/mailman/listinfo/freebsd-users-jp"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-users-jp" title="">http://lists.freebsd.org/mailman/listinfo/freebsd-users-jp</a></td></tr></table><p>
-	Contact: FreeBSD Postmaster Team &lt;<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the third quarter of 2013, the FreeBSD Postmaster Team has
-	implemented the following items that may be interest of the
-	general public:</p>
-
-      <ul>
-	<li>Created the <tt>freebsd-fortran</tt> list, requested by Anton Shterenlikht.</li>
-
-	<li>Created the <tt>freebsd-pkg-fallout</tt> list, requested by
-	  Baptiste Daroussin.</li>
-
-	<li>Created the <tt>freebsd-users-jp</tt> list, requested by Hiroki
-	  Sato</li>
-
-	<li>Retired the <tt>freebsd-mozilla</tt> list, requested by Florian
-	  Smeets.</li>
-
-	<li>Worked with the FreeBSD Cluster Administrators to enable TLS
-	  support on incoming and outgoing mail servers.</li>
-
-	<li>Started discussions and exploration of current and possible
-	  future mail and spam filtering.</li>
-
-	<li>Started the process for retiring the <tt>aic7xxx</tt>
-	  mailing list.  Completion of this is scheduled for 12 October
-	  2013.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releases/9.2R/schedule.html" title="http://www.FreeBSD.org/releases/9.2R/schedule.html">FreeBSD�9.2-RELEASE schedule</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/9.2R/schedule.html" title="FreeBSD�9.2-RELEASE schedule">http://www.FreeBSD.org/releases/9.2R/schedule.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/releases/10.0R/schedule.html" title="http://www.FreeBSD.org/releases/10.0R/schedule.html">FreeBSD�10.0-RELEASE schedule</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/10.0R/schedule.html" title="FreeBSD�10.0-RELEASE schedule">http://www.FreeBSD.org/releases/10.0R/schedule.html</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/">FreeBSD�Virtual Machine Images</a></td><td>
-	    URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/" title="FreeBSD�Virtual Machine Images">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD�Development Snapshots</a></td><td>
-	    URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD�Development Snapshots">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team has completed the 9.2-RELEASE
-	process.  The release cycle changed with a last-minute addition
-	of 9.2-RC4.  The 9.2-RELEASE was announced September 30, four
-	weeks behind the original schedule.</p>
-
-      <p>The FreeBSD�10.0-RELEASE cycle has started, and testing is
-	strongly encouraged.  For testing purposes, both installation
-	images and virtual machine images exist on the FreeBSD�Project
-	FTP servers.</p>
-    <h3>Open tasks:</h3><ol><li>Test 10.0-CURRENT and report problems.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Static-Code-Analysis" href="#Static-Code-Analysis" id="Static-Code-Analysis">Static Code Analysis</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://scan.coverity.com/" title="http://scan.coverity.com/">Coverity Scan</a></td><td>
-	    URL: <a href="http://scan.coverity.com/" title="Coverity Scan">http://scan.coverity.com/</a></td></tr><tr><td><a href="http://scan.freebsd.your.org/" title="http://scan.freebsd.your.org/">Clang Static Analyzer Scan for FreeBSD</a></td><td>
-	    URL: <a href="http://scan.freebsd.your.org/" title="Clang Static Analyzer Scan for FreeBSD">http://scan.freebsd.your.org/</a></td></tr><tr><td><a href="http://clang-analyzer.llvm.org/" title="http://clang-analyzer.llvm.org/">Clang Static Analyzer Home Page</a></td><td>
-	    URL: <a href="http://clang-analyzer.llvm.org/" title="Clang Static Analyzer Home Page">http://clang-analyzer.llvm.org/</a></td></tr></table><p>
-	Contact:
-	  Ulrich
-	  Spoerlein
-	 &lt;<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>&gt;
-	</p>
-      <p>With our own (old and unstable) instance of Coverity Prevent
-	gone, we have now fully transitioned to the Scan project run by
-	Coverity (see links), which Open Source projects can use to
-	learn about possible defects in their source code.</p>
-
-      <p>We also continue to run our code base through the Static
-	Analyzer that is shipped with Clang/LLVM.  It cannot track the
-	state of the code over time, but has the benefit that everyone
-	can use it without any special setup.  See the home page at the
-	links section for more information on the Clang Static Analyzer
-	project in general, and head over to the FreeBSD Clang Static
-	Analyzer Scan page (see links) to see those possible defects (no
-	signup required).</p>
-
-      <p>We are looking for a co-admin for both of these projects to
-	increase the bus-factor and the chance of survival for these
-	services.  Fame and fortune await!</p>
-    <h3>Open tasks:</h3><ol><li>Maybe turn on email reports for new defects to the internal
-	list of FreeBSD developers.</li><li>Find co-admin.</li><li>Fix the defects reported by Coverity and Clang.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="AES-NI-Improvements-for-GELI" href="#AES-NI-Improvements-for-GELI" id="AES-NI-Improvements-for-GELI">AES-NI Improvements for GELI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/255187" title="http://svnweb.freebsd.org/changeset/base/255187"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/255187" title="">http://svnweb.freebsd.org/changeset/base/255187</a></td></tr></table><p>
-	Contact:
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>An enhancement to the AES-NI implementation for OpenCrypto, the
-	kernel's cryptography framework, has been committed that
-	significantly improves AES-XTS and AES-CBC decryption
-	performance.  This gives <tt>geli(8)</tt> around a three times
-	performance boost on <tt>gnop(8)</tt> using AES-XTS compared to
-	the old code.</p>
-
-      <p>These improvements are available to users of the OpenCrypto
-	framework and <tt>crypto(4)</tt>.</p>
-    <hr /><h2><a name="Atomic-&quot;close-on-exec&quot;" href="#Atomic-&quot;close-on-exec&quot;" id="Atomic-&quot;close-on-exec&quot;">Atomic "close-on-exec"</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/AtomicCloseOnExec" title="https://wiki.freebsd.org/AtomicCloseOnExec"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/AtomicCloseOnExec" title="">https://wiki.freebsd.org/AtomicCloseOnExec</a></td></tr></table><p>
-	Contact:
-	  Jilles
-	  Tjoelker
-	 &lt;<a href="mailto:jilles@FreeBSD.org">jilles@FreeBSD.org</a>&gt;
-	</p>
-      <p>If threads or signal handlers call <tt>fork()</tt> and
-	<tt>exec()</tt>, file descriptors may be passed undesirably to
-	child processes, which may lead to hangs (if a pipe is not
-	closed), exceeding the file descriptor limit, and security
-	problems (if the child process has lower privilege).  One
-	solution is various new APIs that set the "close-on-exec" flag
-	atomically with allocating a file descriptor.  Some existing
-	software will use the new features if present or will even
-	refuse to compile without them.</p>
-
-      <p>With <tt>mkostemp()</tt>, <tt>dup3()</tt>, and a change to
-	modes of <tt>fopen()</tt> and <tt>freopen()</tt>, everything
-	proposed in Austin Group issue #411 has now been implemented.
-	For all POSIX-specified functions that allocate file
-	descriptors, it is possible to request that the new descriptor
-	be set close-on-exec atomically.</p>
-
-      <p>Additionally, many file descriptors used internally by
-	<tt>libc</tt> and <tt>libutil</tt> now have the close-on-exec bit
-	set.</p>
-    <hr /><h2><a name="Continuation-of-the-Newcons-Project" href="#Continuation-of-the-Newcons-Project" id="Continuation-of-the-Newcons-Project">Continuation of the Newcons Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.freebsd.org/base/user/ed/newcons/" title="http://svn.freebsd.org/base/user/ed/newcons/">Newcons project branch</a></td><td>
-	    URL: <a href="http://svn.freebsd.org/base/user/ed/newcons/" title="Newcons project branch">http://svn.freebsd.org/base/user/ed/newcons/</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Newcons project is aimed to replace the old
-	<tt>syscons(4)</tt>-based virtual terminals.  The main
-	objectives are: support Unicode characters, and move away from
-	the dependency on fixed VGA and VESA graphics modes and built-in
-	BIOS services.</p>
-
-      <p>This project was originally started by Ed Schouten, and it
-	already featured the following features (among many others) in
-	2013:</p>
-
-      <ul>
-	<li>Unicode fonts with Latin, Cyrillic and some more simple
-	  character sets.</li>
-	<li>Unicode output support.</li>
-	<li>Graphics mode support.</li>
-	<li>Text mode support.</li>
-	<li><tt>sysmouse(4)</tt> support, without copy/paste.</li>
-      </ul>
-
-      <p>And these have been extended by the following items
-	recently:</p>
-
-      <ul>
-	<li>History, that is, the ability to scroll through the terminal
-	  history.  The old, separate history buffer has been
-	  removed.</li>
-
-	<li>The history is implemented by a circular buffer which has no
-	  risk of overflow, and scrolling appears "unlimited".</li>
-
-	<li><tt>VT_PROCESS</tt> mode, a way to hold the terminal and
-	  prevent terminal switching.  For example, X.Org uses this
-	  feature to prevent the user from switching to a non-X
-	  terminal.</li>
-
-	<li><tt>drm2/fb_helper</tt>, the KMS driver.  This binds Newcons
-	  to framebuffers created the DRM-enabled video drivers in the
-	  kernel (such as <tt>i915kms</tt> and <tt>radeonkms</tt>).</li>
-
-	<li>Dynamic attachment of VT drivers, <tt>vt_allocate()</tt> to
-	  allow attaching console video drivers at a later point where
-	  framebuffer owner can manage the initialization.  This is for
-	  KMS and devices without early graphics support.</li>
-      </ul>
-
-      <p>Supported startup modes for KMS:</p>
-
-      <ul>
-	<li>Start without VT graphics drivers, then load KMS.</li>
-	<li>Start with VGA, then load KMS.</li>
-	<li>Preload KMS, then the KMS driver will be attached to the
-	  output.</li>
-	<li>Preload KMS, start with VGA, then KMS driver will replace
-	  the VGA output.</li>
-      </ul>
-
-      <p>This project is being sponsored by The FreeBSD Foundation.  Many
-	thanks to Ed Schouten, who started the Newcons project and did
-	most of the work.</p>
-    <h3>Open tasks:</h3><ol><li>Implement a Generic Framebuffer interface, a simple
-	interface to offer direct access to the framebuffer from the
-	userland (via <tt>/dev/fb*</tt>) and automatic management of
-	virtual terminals by Newcons.</li><li>Mouse support, copy/paste using
-	<tt>sysmouse(4)</tt>.</li><li>Improve locking.</li><li>Bug fixes.</li><li>Integrate into FreeBSD <tt>head</tt>.</li><li>Integrate into FreeBSD�10.0.</li><li>Implement mapping non-ASCII characters to Unicode on
-	keyboard input.</li><li>Adapt existing screen savers.</li><li>Last but not least, testing is welcome!</li></ol><hr /><h2><a name="GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking" href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking" id="GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/camlock/" title="http://svnweb.freebsd.org/base/projects/camlock/">Project SVN branch</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/projects/camlock/" title="Project SVN branch">http://svnweb.freebsd.org/base/projects/camlock/</a></td></tr><tr><td><a href="http://people.freebsd.org/~mav/camlock_patches/" title="http://people.freebsd.org/~mav/camlock_patches/">Project patches</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mav/camlock_patches/" title="Project patches">http://people.freebsd.org/~mav/camlock_patches/</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>Last year's high-performance storage vendor summit reported a
-	performance bottleneck in the FreeBSD block storage subsystem,
-	limiting peak performance to around 300-500K IOPS.  While that
-	is still more than enough for average systems, detailed
-	investigation has shown a number of places that require radical
-	improvement.  The unmapped I/O support implemented early this
-	year has already improved I/O performance by about 30% and moved
-	more focus toward GEOM and CAM subsystems scalability.  Fixing
-	these issues was the goal of this project.</p>
-
-      <p>The existing GEOM design assumed most I/O handling was to be
-	done by only two kernel threads (<tt>g_up()</tt> and
-	<tt>g_down()</tt>).  That simplified locking in some cases, but
-	limited potential SMP scalability and created additional
-	scheduler overhead.  This project introduces the concept of
-	direct I/O dispatch into GEOM for cases where it is known to be
-	safe and efficient.  That implies marking some GEOM consumers
-	and providers with one or two new flags, declaring situations
-	when a direct function call can be used instead of normal
-	request queuing.  That permits avoiding any context switches
-	inside GEOM for the most widely used topologies, simultaneously
-	processing multiple I/Os from multiple calling threads.</p>
-
-      <p>Having GEOM pass through multiple concurrent calls down to the
-	underlying layers exposed major lock congestion in CAM.  In the
-	existing CAM design, all devices connected to the same ATA/SCSI
-	controller share a single lock, which can be quite busy due to
-	multiple controller hardware accesses and/or code logic.
-	Experiments have shown that applying only the above GEOM direct
-	dispatch changes burns up to 60% of system CPU time or even more
-	in attempts to obtain these locks by multiple callers, killing
-	any benefits of GEOM direct dispatch.</p>
-
-      <p>To overcome this scaling limitation, a new fine-grained CAM
-	locking design was implemented.  It implies splitting the big
-	per-SIM locks into several smaller ones: per-LUN locks, per-bus
-	locks, queue locks, etc.  After these changes, the remaining
-	per-SIM lock protects only the controller driver internals,
-	reducing lock congestion down to an acceptable level and keeping
-	compatibility with existing drivers.</p>
-
-      <p>Together, the GEOM and CAM changes double the peak I/O rate,
-	reaching up to 1,000,000 IOPS on contemporary hardware.</p>
-
-      <p>The changes were tested by a number of people and will be
-	committed into FreeBSD <tt>head</tt> and merged to
-	<tt>stable/10</tt> after the end of the FreeBSD 10.0 release
-	cycle.</p>
-
-      <p>The project is sponsored by iXsystems, Inc.</p>
-    <h3>Open tasks:</h3><ol><li>More reviews, more stability and performance tests.</li></ol><hr /><h2><a name="Native-iSCSI-Stack" href="#Native-iSCSI-Stack" id="Native-iSCSI-Stack">Native iSCSI Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="https://wiki.freebsd.org/Native%20iSCSI%20target"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="">https://wiki.freebsd.org/Native%20iSCSI%20target</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Due to the quickly approaching time of 10.0-RELEASE, the
-	priorities for the native iSCSI stack shifted somewhat, from
-	performance optimizations to making sure the new stack is
-	reliable, feature-complete, and is able to interoperate correctly
-	with various implementations.  Plenty of time was invested into
-	testing and debugging, mostly on the initiator side, to make
-	sure it works correctly with other targets, such as Solaris
-	COMSTAR, and behaves properly in edge conditions like connection
-	problems.  Nevertheless, some fundamental optimizations, such as
-	Immediate Data support, were implemented.  The documentation has
-	improved, and there will be a new section added to the FreeBSD
-	Handbook describing the use of the new stack.</p>
-
-      <p>The new stack was committed to <tt>head</tt> and will ship as
-	part of 10.0-RELEASE.  There is ongoing work on fixing issues
-	reported by early adopters.</p>
-
-      <p>This project is being sponsored by The FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Fix newly reported issues.</li><li>Improve performance.</li></ol><hr /><h2><a name="Reworking-random(4)" href="#Reworking-random(4)" id="Reworking-random(4)">Reworking random(4)</a></h2><p>
-	Contact:
-	  Mark
-	  Murray
-	 &lt;<a href="mailto:markm@freebsd.org">markm@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Arthur
-	  Mesh
-	 &lt;<a href="mailto:arthurmesh@gmail.com">arthurmesh@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Dag-Erling
-	  Sm�rgrav
-	 &lt;<a href="mailto:des@freebsd.org">des@freebsd.org</a>&gt;
-	</p>
-      <p>Random numbers require a lot more thought and preparation than
-	would naively appear to be the case.  For simulations, number
-	sequences that are repeatable but sufficiently disordered are
-	often needed to achieve required experimental duplication
-	ability, and many programmers are familiar with these.  For
-	cryptography, it is essential that an attacker not be able to
-	predict or guess the output sequence, thus giving a source of
-	security-critical secret material for uses such as passwords or
-	"key material".</p>
-
-      <p>FreeBSD's random number generator, available as the pseudo-file
-	<tt>/dev/random</tt> produces unpredictable numbers intended for
-	cryptographic use, and is thus a Cryptograpically-Secured
-	Pseudo-Random Number Generator, or CSPRNG.  The security is
-	given by careful design of the output generator (based on a
-	block cipher) and input entropy accumulation queues.  The latter
-	uses hashes to accumulate stochastic information harvested from
-	various places in the kernel to provide highly unpredictable
-	input to the generator.  The algorithm for doing this, Yarrow,
-	by Schneier et al, may be found by web search.</p>
-
-      <p>FreeBSD's CSPRNG also allowed for certain stochastic sources,
-	deemed to be "high-quality", to directly supply the
-	<tt>random(4)</tt> device without going through Yarrow.  With
-	recent revelations over possible government surveillance and
-	involvement in the selection of these "high-quality" sources, it
-	is felt that they can no longer be trusted, and must therefore
-	also be processed though Yarrow.</p>
-
-      <p>The matter was discussed at various levels of formality at the
-	Cambridge Developer Summit in August, and at EuroBSDcon 2013 in
-	September.</p>
-
-      <p>This work is now done, and the <tt>random(4)</tt> CSPRNG is now
-	brought to a more paranoid, modern standard of distrust with
-	regard to its entropy sources.  Infrastructure work was also
-	done to facilitate certain entropy-source choices for the
-	convenience of the system administrators.</p>
-
-      <p>Future work is now going ahead with the implementation of the
-	Fortuna algorithm by Ferguson and Schneier as an upgrade or
-	alternative to Yarrow.  Initially a choice will be presented,
-	and decisions on the future of the CSPRNG processing algorithms
-	in use will be made in the future as needs arise.</p>
-    <h3>Open tasks:</h3><ol><li>Implement FIPS 800-90b support.</li><li>A full, in-depth review of entropy.</li></ol><hr /><h2><a name="SDIO-Driver" href="#SDIO-Driver" id="SDIO-Driver">SDIO Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SDIO" title="https://wiki.freebsd.org/SDIO">SDIO Project Page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SDIO" title="SDIO Project Page">https://wiki.freebsd.org/SDIO</a></td></tr><tr><td><a href="https://github.com/kibab/freebsd/tree/kibab-dplug" title="https://github.com/kibab/freebsd/tree/kibab-dplug">Source Code</a></td><td>
-	    URL: <a href="https://github.com/kibab/freebsd/tree/kibab-dplug" title="Source Code">https://github.com/kibab/freebsd/tree/kibab-dplug</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>SDIO is an interface designed as an extension of the existing
-	SD card standard, to allow connecting different peripherals to
-	the host with the standard SD controller.  Peripherals currently
-	sold at the general market include WLAN/BT modules, cameras,
-	fingerprint readers, and barcode scanners.  The driver is
-	implemented as an extension to the existing MMC bus, adding a
-	lot of new SDIO-specific bus methods.  A prototype of the driver
-	for the Marvell SDIO WLAN/BT (Avastar 88W8787) module is also
-	being developed, using the existing Linux driver as the
-	reference.</p>
-
-      <p>SDIO card detection and initialization already work, most
-	needed bus methods are implemented and tested.  There is an
-	ongoing work to design a good locking model for the stack.  The
-	WiFi driver is able to load firmware onto the card and
-	initialize it.</p>
-    <h3>Open tasks:</h3><ol><li>SDIO stack: Design a locking model, define how the
-	interrupts should be processed (on SDIO controller level, MMC
-	stack level and by child drivers).</li><li>Marvell SDIO WiFi: connect to the FreeBSD network stack, write
-	the code to implement required functions (such as sending and
-	receiving data, network scanning, and so on).</li><li>Implement detach path.  It cannot be tested on the DreamPlug
-	used for development, because the DreamPlug does not have an
-	external SDIO-capable slot.</li></ol><hr /><h2><a name="VirtIO-Network-Multiqueue" href="#VirtIO-Network-Multiqueue" id="VirtIO-Network-Multiqueue">VirtIO Network Multiqueue</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/255112" title="http://svnweb.freebsd.org/changeset/base/255112"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/255112" title="">http://svnweb.freebsd.org/changeset/base/255112</a></td></tr></table><p>
-	Contact:
-	  Bryan
-	  Venteicher
-	 &lt;<a href="mailto:bryanv@freebsd.org">bryanv@freebsd.org</a>&gt;
-	</p>
-      <p>The VirtIO network driver, <tt>vtnet(4)</tt>, is used by FreeBSD
-	systems running on hypervisors including <tt>bhyve(4)</tt> and
-	Linux's KVM.  It recently gained support for multiple queues,
-	along with a significant cleanup and support for a few
-	additional features.</p>
-    <hr /><h2><a name="VMware-VMXNET3-Driver" href="#VMware-VMXNET3-Driver" id="VMware-VMXNET3-Driver">VMware VMXNET3 Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2013-August/043494.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2013-August/043494.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2013-August/043494.html" title="">http://lists.freebsd.org/pipermail/freebsd-current/2013-August/043494.html</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/base/head/sys/dev/vmware/vmxnet3/" title="http://svnweb.freebsd.org/base/head/sys/dev/vmware/vmxnet3/"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/head/sys/dev/vmware/vmxnet3/" title="">http://svnweb.freebsd.org/base/head/sys/dev/vmware/vmxnet3/</a></td></tr></table><p>
-	Contact:
-	  Bryan
-	  Venteicher
-	 &lt;<a href="mailto:bryanv@freebsd.org">bryanv@freebsd.org</a>&gt;
-	</p>
-      <p>A port of the OpenBSD <tt>vmx(4)</tt> ethernet driver for
-	VMware virtual machines has been committed.  The driver can be
-	used in place of the VMware Tools <tt>vmxnet3</tt> driver, which
-	currently does not support 10.0-RELEASE (or anything past
-	9.0-RELEASE).</p>
-    <h3>Open tasks:</h3><ol><li>Performance improvements, multiqueue support.</li><li>Merge to <tt>stable/9</tt>.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Cubieboard2" href="#FreeBSD-on-Cubieboard2" id="FreeBSD-on-Cubieboard2">FreeBSD on Cubieboard2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/254056" title="http://svnweb.freebsd.org/changeset/base/254056"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/254056" title="">http://svnweb.freebsd.org/changeset/base/254056</a></td></tr></table><p>
-	Contact:
-	  Ganbold
-	  Tsagaankhuu
-	 &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>Initial support of Allwinner A20 SoC is committed to
-	<tt>head</tt>.  The A20 SoC on Cubieboard2 is pin-to-pin
-	compatible with the A10 in Cubieboard1 and FreeBSD supports the
-	following peripherals:</p>
-
-      <ul>
-	<li>USB EHCI</li>
-	<li>GPIO</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Get the EMAC Ethernet driver working.  Need more help from
-	network driver experts.</li><li>Add more drivers.</li></ol><hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-on-ec2/" title="http://www.daemonology.net/freebsd-on-ec2/">FreeBSD/EC2 Status Page</a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-on-ec2/" title="FreeBSD/EC2 Status Page">http://www.daemonology.net/freebsd-on-ec2/</a></td></tr><tr><td><a href="https://aws.amazon.com/marketplace/pp/B00AA25MLK/" title="https://aws.amazon.com/marketplace/pp/B00AA25MLK/">AWS Marketplace Listing</a></td><td>
-	    URL: <a href="https://aws.amazon.com/marketplace/pp/B00AA25MLK/" title="AWS Marketplace Listing">https://aws.amazon.com/marketplace/pp/B00AA25MLK/</a></td></tr></table><p>
-	Contact:
-	  Colin
-	  Percival
-	 &lt;<a href="mailto:cperciva@freebsd.org">cperciva@freebsd.org</a>&gt;
-	</p>
-      <p>FreeBSD images are available for use in EC2 for 8.3-RELEASE,
-	8.4-RELEASE, 9.0-RELEASE, 9.1-RELEASE, and 9.2-RELEASE.  In
-	9.2-RELEASE, FreeBSD runs in EC2 using an unpatched source tree,
-	but it needs the <tt>XENHVM</tt> kernel configuration.</p>
-
-      <p>Starting from FreeBSD 10.0-ALPHA3, the <tt>GENERIC</tt> kernel
-	configuration now contains all the <tt>XENHVM</tt> bits needed
-	to allow FreeBSD to run in EC2 natively.  Consequently,
-	FreeBSD�10.0 will be the first release for which FreeBSD/EC2 is
-	purely "bits off the ISO".  This also means that starting with
-	10.0 it will be possible to use <tt>freebsd-update(8)</tt> for
-	all base system updates &#8212; in earlier releases it was
-	necessary to recompile the <tt>XENHVM</tt> kernel manually.</p>
-
-      <p>Due to FreeBSD's use of HVM virtualization, running on "old" EC2
-	instance types (m1, m2, c1, t1) requires that FreeBSD pretends to
-	be Windows, which unfortunately results in paying the higher
-	"windows" EC2 instance prices.  On "new" EC2 instances (cc1,
-	cc2, cg1, cr1, hi1, hs1, and m3) FreeBSD can run as a "unix" image
-	at the lower rate.</p>
-    <h3>Open tasks:</h3><ol><li>Test FreeBSD 10.0-ALPHAs/BETAs/RCs as they become available.
-	Plenty of new Xen code has been committed recently and there are
-	probably bugs to find before the release.</li><li>Keep nagging Amazon to provide more instance types which
-	FreeBSD can run on without paying a "Windows tax".</li><li>Provide some mechanism for instance configuration via EC2
-	<tt>user-data</tt>.  This might involve using
-	<tt>cloud-init</tt>, or it might be a new system.</li></ol><hr /><h2><a name="FreeBSD/pseries" href="#FreeBSD/pseries" id="FreeBSD/pseries">FreeBSD/pseries</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/255643" title="http://svnweb.freebsd.org/changeset/base/255643"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/255643" title="">http://svnweb.freebsd.org/changeset/base/255643</a></td></tr></table><p>
-	Contact:
-	  Andreas
-	  Tobler
-	 &lt;<a href="mailto:andreast@freebsd.org">andreast@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@freebsd.org">nwhitehorn@freebsd.org</a>&gt;
-	</p>
-      <p>Starting with FreeBSD 10.0-ALPHA4, the <tt>projects/pseries</tt>
-	branch has been merged into FreeBSD <tt>head</tt>.  This allows
-	FreeBSD/powerpc64 to run in an IBM POWER logical partition and on
-	certain classes of older IBM-type PowerPC hardware.</p>
-    <h3>Open tasks:</h3><ol><li>Test, possibly on real hardware.  Most testing and
-	development was conducted with the emulated LPAR target in QEMU.
-	Please send any testing reports to the <tt>freebsd-ppc</tt>
-	mailing list.</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are several things going on with the FreeBSD/sparc64
-	port.</p>
-
-      <p>After having fixed all remaining problems and starting with
-	9.2-RELEASE, releases for this architecture are cross-built on
-	the FreeBSD Project cluster.  As one might already have noticed,
-	this means that from now on, sparc64 install sets and images
-	including those for ALPHA, BETA, and RC builds, are available
-	alongside those for the other platforms supported by FreeBSD.
-	Since August 2013, automatically cross-built monthly
-	FreeBSD/sparc64 snapshots are distributed via the official project
-	mirrors.  Hopefully, this can soon be extended further with
-	<tt>freebsd-update(8)</tt> support for sparc64.</p>
-
-      <p>The X.Org ports have been fixed to work on sparc64 when built
-	with the <tt>WITH_NEW_XORG</tt> knob.  However, it still needs
-	to be evaluated whether the recently committed update to Mesa
-	9.1.6 has introduced any breakage.</p>
-    <hr /><h2><a name="Superpages-for-ARMv7" href="#Superpages-for-ARMv7" id="Superpages-for-ARMv7">Superpages for ARMv7</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf" title="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf"></a></td><td>
-	    URL: <a href="http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf" title="">http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf</a></td></tr><tr><td><a href="http://wiki.freebsd.org/ARMSuperpages" title="http://wiki.freebsd.org/ARMSuperpages"></a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/ARMSuperpages" title="">http://wiki.freebsd.org/ARMSuperpages</a></td></tr><tr><td><a href="http://blogs.arm.com/software-enablement/1079-transparent-superpages-for-freebsd-on-arm" title="http://blogs.arm.com/software-enablement/1079-transparent-superpages-for-freebsd-on-arm"></a></td><td>
-	    URL: <a href="http://blogs.arm.com/software-enablement/1079-transparent-superpages-for-freebsd-on-arm" title="">http://blogs.arm.com/software-enablement/1079-transparent-superpages-for-freebsd-on-arm</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=view&amp;target=semihalf-superpages_armv7.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=view&amp;target=semihalf-superpages_armv7.pdf"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=view&amp;target=semihalf-superpages_armv7.pdf" title="">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=view&amp;target=semihalf-superpages_armv7.pdf</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/254918" title="http://svnweb.freebsd.org/changeset/base/254918"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/254918" title="">http://svnweb.freebsd.org/changeset/base/254918</a></td></tr></table><p>
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafa&#322;
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>The ARM architecture is becoming more and more prevalent, with
-	increasing usage beyond the mobile and embedded space.  Among
-	the more interesting industry trends emerging in the recent
-	months, there has been the concept of "ARM server".  Top-tier
-	companies like Dell and HP have already started to develop such
-	systems.</p>
-
-      <p>Key to the success of FreeBSD in these new areas is dealing with
-	the sophisticated features of the platform, for example adding
-	support for superpages.</p>
-
-      <p>The objective of this project is to enable FreeBSD/arm to utilize
-	superpages, allowing efficient use of TLB translations (by
-	enlarging TLB coverage), leading to improved performance in many
-	applications and scalability.  This is intended to work on
-	ARMv7-based processors, however compatibility with ARMv6 will be
-	preserved.</p>
-
-      <p>The following steps have been made since the last status
-	report:</p>
-
-      <ul>
-	<li>The <tt>pmap(9)</tt> module has been adjusted to fully
-	  utilize superpages.</li>
-
-	<li>Found and fixed minor bugs in superpage management.</li>
-
-	<li>Implemented the <tt>pmap_advise()</tt> routine.</li>
-
-	<li>Performed extensive testing and benchmarking:
-
-	  <ul>
-	    <li>Giga Updates Per Second (GUPS) benchmark: 34% lower memory access
-	      latency and 34% higher updates ratio.</li>
-
-	    <li>LMbench: 38% lower memory latency.</li>
-
-	    <li>Self-hosted <tt>buildworld</tt>: 20% shorter, using GCC.</li>
-	  </ul></li>
-
-	<li>Final integration into FreeBSD <tt>head</tt>.</li>
-      </ul>
-
-      <p>This project is jointly sponsored by The FreeBSD Foundation and
-	Semihalf.</p>
-    <h3>Open tasks:</h3><ol><li>Adjust <tt>pmap</tt> to resolve the demotion issue caused by
-	the continuous active queue scanning in VM.</li><li>Support for 64KB page size.</li><li>Move <tt>pv_flags</tt> to page table entry descriptors.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="Capsicum" href="#Capsicum" id="Capsicum">Capsicum</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Capsicum is the FreeBSD sandboxing subsystem, which presents
-	programmers with a capability module allowing fine-grained
-	delegation of rights to less-privileged processes.  Casper is a
-	friendly daemon that provides services to sandboxed processes,
-	allowing policy-based access to privileged services such as DNS
-	resolution.</p>
-
-      <p>The work on Capsicum and related projects (such as Casper,
-	<tt>libnv</tt>, etc.) is progressing nicely.  An overhaul of the
-	<tt>cap_rights_t</tt> was committed to FreeBSD <tt>head</tt> and
-	will be included in 10.0.  This allows us to have more
-	capability rights on file descriptors than the previous limit of
-	64 rights, which was almost reached.  This change is not
-	backward compatible, so it was very important to get it into
-	10.0.</p>
-
-      <p><tt>libnv</tt>, used for communication between Casper services
-	and consumers, but which will hopefully be used more widely, is
-	finalized and comes with a nice set of regression tests.</p>
-
-      <p>The number of applications sandboxed using the Capsicum
-	framework is increasing.  We have around 10 of them already in
-	base and more that are not yet committed.</p>
-
-      <p>This project is being sponsored by the FreeBSD Foundation.</p>
-    <h3>Open tasks:</h3><ol><li>Finish documentation of Casper and its services.</li><li>Implement regression tests for Casper services.</li><li>Finish documentation for <tt>libnv</tt>.</li><li>Start making <tt>libc</tt> more sandbox-friendly, that is,
-	modifying functions such as <tt>strerror(3)</tt>,
-	<tt>strsignal(3)</tt>, <tt>localtime(3)</tt>,
-	<tt>login_get*()</tt>, <tt>getservent(3)</tt>,
-	<tt>getprotent(3)</tt>, and <tt>getrpcent(3)</tt> which
-	currently open files on first use, which might be too late if we
-	are already in a capability-mode sandbox.</li><li>Rethink the <tt>system.filesystem</tt> Casper service to
-	allow for easy compartmentalization of various command-line
-	tools that operate on multiple files.</li></ol><hr /><h2><a name="LLDB-Debugger-Port" href="#LLDB-Debugger-Port" id="LLDB-Debugger-Port">LLDB Debugger Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/lldb" title="https://wiki.freebsd.org/lldb"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/lldb" title="">https://wiki.freebsd.org/lldb</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	</p>
-      <p>LLDB is the debugger project in the LLVM family.  It supports
-	the Mac OS X, Linux, and FreeBSD platforms.</p>
-
-      <p>A number of improvements have been made to the port since the
-	previous status update.  Unit test failures have been triaged
-	and have defects entered in LLDB's bug tracker.  In combination
-	with the <tt>lldb</tt> buildbot this allows for the quick
-	identification of new failures introduced by other ongoing
-	development.  Core file support has also been added.</p>
-
-      <p>An LLDB snapshot has been imported into the FreeBSD base system
-	and is available as of SVN revision 255722.  It is not yet built
-	by default but may be enabled by adding <tt>WITH_LLDB=</tt> to
-	<tt>src.conf(5)</tt>.</p>
-
-      <p>This project is sponsored by DARPA/AFRL in collaboration with SRI
-	International and the University of Cambridge.</p>
-    <h3>Open tasks:</h3><ol><li>Support live debugging of multithreaded processes.</li><li>Fix amd64 watchpoints.</li><li>Add support for remote debugging (gdbserver,
-	debugserver).</li><li>Add support for kernel debugging.</li><li>Verify i386 and arm architectures.</li><li>Implement MIPS target support.</li><li>Verify cross-debugging.</li><li>Investigate and fix test suite failures.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Ada-Ports" href="#FreeBSD-Ada-Ports" id="FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.dragonlace.net" title="http://www.dragonlace.net"></a></td><td>
-	    URL: <a href="http://www.dragonlace.net" title="">http://www.dragonlace.net</a></td></tr></table><p>
-	Contact:
-	  John
-	  Marino
-	 &lt;<a href="mailto:marino@FreeBSD.org">marino@FreeBSD.org</a>&gt;
-	</p>
-      <p>A few years ago, Ada-based ports almost completely disappeared
-	from the Ports Collection.  This was not surprising, as
-	FSF�GNAT, the only open-source Ada compiler, ceased to
-	build correctly on any BSD flavor.  Previously-built bootstrap
-	compilers would not run on modern FreeBSD, and certainly not on
-	amd64.  The first step, see the link for details, was to patch
-	GCC in order to fix GNAT not only on FreeBSD, but DragonFly,
-	NetBSD, and OpenBSD as well.  New bootstraps for both i386 and
-	amd64 platforms were produced during this effort.  Ada compilers
-	on FreeBSD now pass 100% of the ACATS and GCC testsuites.</p>
-
-      <p>With the introduction of the first new Ada compiler port, the
-	GCC�4.6-based <tt>lang/gnat-aux</tt>, the GNAT Programming
-	Studio (a multilanguage integrated development environment),
-	XML/Ada, and GtkAda were among the first Ada ports
-	resurrected.</p>
-
-      <p>With the latest compiler, <tt>lang/gcc-aux</tt> based on GCC
-	4.7, a cohesive Ada framework was created with the new
-	<tt>USES=</tt> framework.  Currently around 20 ports are part of
-	this framework including Florist, ASIS, GPRbuild, QtAda,
-	AdaControl, AdaBrowse, PolyOrb, and AWS (Ada Web Server).</p>
-
-      <p>The GNAT AUX compiler is also still in use to serve as a basis
-	for the GNATDroid ports which are FreeBSD-to-Android Ada+C cross-compilers.
-	However, these will soon be integrated into the Ada Framework.</p>
-
-      <p>At this point, it looks like FreeBSD (shared with DragonFly via
-	DPorts) has taken the crown from Debian as the recognized best
-	Ada development platform.  The FreeBSD versions of the software are
-	more recent and the Ports Collection has ports not available on
-	Debian, such as LibSparkCrypto, the Matreshka library, and the
-	Ahven unit tester.</p>
-
-      <p>Future work potentially includes converting GCC AUX to
-	GCC�4.8 to acquire better Ada�2012 support, importing
-	Spark�2014 into ports when it arrives and to continue to
-	add new Ada ports to the framework.</p>
-    <hr /><h2><a name="FreeBSD-Python-Ports" href="#FreeBSD-Python-Ports" id="FreeBSD-Python-Ports">FreeBSD Python Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Python" title="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Python" title="The FreeBSD Python Team Page">https://wiki.FreeBSD.org/Python</a></td></tr><tr><td><a href="irc://freebsd-python@irc.freenode.net" title="irc://freebsd-python@irc.freenode.net">IRC channel</a></td><td>
-	    URL: <a href="irc://freebsd-python@irc.freenode.net" title="IRC channel">irc://freebsd-python@irc.freenode.net</a></td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  Python Team
-	 &lt;<a href="mailto:python@FreeBSD.org">python@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are currently working on cleaning up the
-	<tt>lang/python*</tt> ports to improve their compatibility with
-	the original upstream build behaviour and to reduce the need for
-	FreeBSD-specific build patches.  A first step was made in September
-	by reducing the flags injected into the different Python
-	interpreter versions.</p>
-
-      <p>The first tasks have been completed to support the installation
-	of packages for different Python ports.  A new metaport structure
-	has replaced the original Python port behaviour, and will be
-	enhanced over the next months to enable improved installation
-	support of packages for different Python versions at the same
-	time.</p>
-
-      <p>The Python ports framework was enhanced with automated
-	packaging list creation and replacement macros, which improve the
-	compatibility with multiple Python versions and reduce the
-	packaging list sizes.</p>
-
-      <p>PyPy was heavily enhanced over the last couple of months.
-	Major updates to the port solved integration issues and a new
-	<tt>pypy-devel</tt> port for snapshots and previews was added.
-	Since the PyPy�3 release, there is a new
-	<tt>pypy3-devel</tt> port available to provide not only
-	compatibility for Python�2.x specific scripts, but also for
-	those using the 3.x language specification.</p>
-
-      <p>IronPython found its way into the FreeBSD ports tree, providing an
-	implementation of the Python language based on .NET and
-	Mono.</p>
-    <h3>Open tasks:</h3><ol><li>Develop a high-level and lightweight Python Ports
-	Policy.</li><li>Chase the unification of Distribute
-	(<tt>devel/py-distribute</tt>) and Setuptools
-	(<tt>devel/py-setuptools*</tt>).</li><li>Add support for granular dependencies (for example
-	<tt>&gt;=1.0</tt> or <tt>&lt; 2.0</tt>).</li><li>Look at what adding <tt>pip</tt> (Python Package Index)
-	support looks like.</li><li>More tasks can be found on the Team's wiki page (see
-	links).</li></ol><hr /><h2><a name="GNOME/FreeBSD" href="#GNOME/FreeBSD" id="GNOME/FreeBSD">GNOME/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="">http://www.FreeBSD.org/gnome/</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>Glib�2.36 and Gtk�3.8 were imported into the ports
-	tree.  The GNOME Team is currently working on improving the
-	quality of GNOME�3.6.  The version of
-	<tt>multimedia/cheese</tt> shipped with GNOME�3 is now able
-	to use <tt>devd(8)</tt> to find the camera through
-	<tt>multimedia/webcamd</tt>.  Several build improvements have
-	been made to the <tt>www/webkit-gtk3</tt> port, however it still
-	is rather fragile.</p>
-
-      <p>MATE, a desktop environment forked from the now-unmaintained
-	codebase of GNOME�2, is about ready to go in.</p>
-
-      <p>GNOME�2 will be removed at some point in the near future.
-	How or when this will happen is not yet clear.</p>
-    <h3>Open tasks:</h3><ol><li>Test the update.  Contact the maintainers if it is suspected
-	that a port does not work with the newer version of
-	<tt>devel/glib20</tt>.</li><li>Update the FreeBSD GNOME website with recent changes in the
-	ports tree, add new items in preparation for GNOME�3 and Mate,
-	etc.</li><li>Continue working on GNOME�3.6, stability and missing
-	features.</li><li>Import MATE into the ports tree.</li></ol><hr /><h2><a name="GNUstep-on-FreeBSD" href="#GNUstep-on-FreeBSD" id="GNUstep-on-FreeBSD">GNUstep on FreeBSD</a></h2><p>
-	Contact:
-	  David
-	  Chisnall
-	 &lt;<a href="mailto:theraven@FreeBSD.org">theraven@FreeBSD.org</a>&gt;
-	</p>
-      <p>GNUstep is the open source implementation of the Objective-C
-	APIs based on the OpenStep specification that Apple brands as
-	Cocoa.  The similarities between the FreeBSD and OS�X
-	<tt>libc</tt> make FreeBSD an attractive target platform for
-	porting OS�X applications, with the addition of
-	GNUstep.</p>
-
-      <p>The GNUstep ports in FreeBSD have now been updated to the latest
-	releases and now build with the GNUstep Objective-C runtime and
-	Clang 3.3, with the non-fragile ABI by default.  This means that
-	all of the modern features of Objective-C are supported,
-	including Automatic Reference Counting (ARC) and recent syntax
-	improvements.</p>
-
-      <p>The <tt>devel/gnustep</tt> meta-port will install all of the
-	core GNUstep libraries, ready for development.  The
-	<tt>x11/gnustep-app</tt> meta-port will install all of the
-	GNUstep-based applications and libraries currently in the ports
-	tree.  Many of these are old and not well-tested with later
-	GNUstep release, so consider them experimental at present.
-	We are currently working on updating them, including moving from
-	some abandoned upstream locations to the GNUstep Applications
-	Project (GAP), which has taken over maintenance of a number of
-	older GNUstep programs.</p>
-    <hr /><h2><a name="X.Org-on-FreeBSD" href="#X.Org-on-FreeBSD" id="X.Org-on-FreeBSD">X.Org on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">X11 Team roadmap (WIP)</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="X11 Team roadmap (WIP)">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Xorg" title="https://wiki.freebsd.org/Xorg">Ports-related status</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xorg" title="Ports-related status">https://wiki.freebsd.org/Xorg</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related development repository</a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="Ports-related development repository">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr><tr><td><a href="https://wiki.freebsd.org/AMD_GPU" title="https://wiki.freebsd.org/AMD_GPU">AMD GPU status</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/AMD_GPU" title="AMD GPU status">https://wiki.freebsd.org/AMD_GPU</a></td></tr><tr><td><a href="https://github.com/dumbbell/freebsd/tree/kms-drm-update-38" title="https://github.com/dumbbell/freebsd/tree/kms-drm-update-38">DRM generic code update branch on GitHub</a></td><td>
-	    URL: <a href="https://github.com/dumbbell/freebsd/tree/kms-drm-update-38" title="DRM generic code update branch on GitHub">https://github.com/dumbbell/freebsd/tree/kms-drm-update-38</a></td></tr></table><p>
-	Contact: FreeBSDX11 Team &lt;<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>Mesa 9.1 (libGL and dri) was updated in ports.  This includes
-	experimental ports for libEGL and libgles2: they are
-	dependencies of the experimental ports for Wayland and
-	Weston.</p>
-
-      <p>The <tt>radeonkms</tt> driver was committed to FreeBSD
-	<tt>head</tt> in the end of August and will be part of
-	10.0-RELEASE.  It received several fixes since the initial
-	commit and now seems quite stable.  However, one missing major
-	feature is support for suspend/resume: the GPU almost always
-	locks up during resume on the test computer.</p>
-
-      <p>Thanks to the update of Mesa and the update of
-	<tt>x11-drivers/xf86-video-ati</tt> to 7.2.0
-	in the ports tree, every pieces are in place to allow users to use recent
-	AMD video cards (up to HD7000, maybe some HD8000).</p>
-
-      <p>The driver will now only receive bug fixes and focus will move
-	on the update of the DRM generic code and the <tt>i915</tt>
-	driver.</p>
-
-      <p>The generic DRM code, shared by the <tt>i915kms</tt> and
-	<tt>radeonkms</tt> video drivers is quite old now.  Work has
-	started to update and sync it with that of Linux�3.8.  This
-	code is available on GitHub.</p>
-
-      <p>The expected benefits are:</p>
-
-      <ul>
-	<li>Fixes in the framebuffer code, which would help the future
-	  deployment of Newcons.</li>
-
-	<li>Preliminary support for minor devices (that is, control
-	  versus render nodes).</li>
-
-	<li>Support for <tt>setmaster</tt> and <tt>dropmaster</tt>,
-	  which allows to run multiple X sessions.</li>
-      </ul>
-
-      <p>Fran�ois Tigeot from DragonFly is also working on updates to
-	their DRM code, and the X11 team is planning to share the
-	effort.</p>
-
-      <p>An experimental <tt>devd(8)</tt> backend was added to the
-	<tt>x11-servers/xorg-server</tt> port.  This allows X.Org to use
-	<tt>devd(8)</tt> to detect and configure input devices (for
-	example, keyboards and mices) dynamically.</p>
-
-      <p>Our current wiki articles are used to describe projects and
-	report status.  However, they lack some consistency and links
-	between them.  We started to think about reorganizing them
-	to:</p>
-
-      <ul>
-       <li>Improve the coordination between the ports and the kernel
-	efforts.</li>
-
-       <li>Make the information more accessible.</li>
-      </ul>
-
-      <p>Nothing is visible yet on the wiki.</p>
-    <h3>Open tasks:</h3><ol><li>Keep tracking Mesa 9.2 or later and <tt>xorg-server</tt>
-	1.14.  Both are currently blocked, but it is good to keep track of
-	what upstream is doing.</li><li>Test and report successes and failures for AMD GPUs.</li><li>Wayland builds now.  Work is being done on Weston to see if
-	there are any run-time issues.  Weston is the reference
-	compositor for Wayland.</li><li>Improve the <tt>devd(8)</tt> backend for
-	<tt>x11-servers/xorg-server</tt>, so the HAL option can be
-	removed completely.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="FreeBSD-Documentation-Project-Primer-Edit" href="#FreeBSD-Documentation-Project-Primer-Edit" id="FreeBSD-Documentation-Project-Primer-Edit">FreeBSD Documentation Project Primer Edit</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/doc/en/books/fdp-primer/book.html" title="http://www.freebsd.org/doc/en/books/fdp-primer/book.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en/books/fdp-primer/book.html" title="">http://www.freebsd.org/doc/en/books/fdp-primer/book.html</a></td></tr></table><p>
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Documentation Project Primer had not changed at the
-	same rate as the documents themselves.  Some sections were
-	outdated and others were verbose and confusing, while
-	information on new changes to the documentation were not
-	described at all.  In July, Warren gave the entire FDP Primer a
-	fairly intense edit for simplicity and clarity.  Chapters and
-	sections were moved into a more logical order, and information
-	was updated to be a better guide to the current state.  Markup
-	examples were added and revised.  Style guidelines were also
-	extended and updated.  The Primer is now far more consistent and
-	usable.  As always, there is still room for improvement, and
-	additions or corrections are encouraged.</p>
-    <h3>Open tasks:</h3><ol><li>An introductory chapter on writing manual pages with
-	<tt>mdoc(7)</tt> would be an excellent addition.</li></ol><hr /><h2><a name="The-entities-Documentation-Branch" href="#The-entities-Documentation-Branch" id="The-entities-Documentation-Branch">The entities Documentation Branch</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/doc/42226" title="http://svnweb.freebsd.org/changeset/doc/42226"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/doc/42226" title="">http://svnweb.freebsd.org/changeset/doc/42226</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>entities</tt> project branch has been successfully
-	merged into the main documentation branch per revision 42226 of
-	the <tt>doc</tt> repository (see link).  The purpose of this
-	branch was to remove the duplicated definitions of authors in
-	both <tt>authors.ent</tt> and <tt>developers.ent</tt>.  The
-	latter file has been removed after migrating its contents to the
-	former file.  While most changes are not visible to end users,
-	the Committer's Guide was changed to accomodate for changes
-	related to adding a new committer.  Translators were also
-	informed of the update.  The largest hurdle mentioned in the
-	last report, processing the <tt>&lt;email&gt;</tt> element, was
-	solved with the help of G�bor K�vesd�n.</p>
-    <hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Download-Manager-Service-for-the-Ports-Collection" href="#Download-Manager-Service-for-the-Ports-Collection" id="Download-Manager-Service-for-the-Ports-Collection">Download Manager Service for the Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2013/IntellegentDownloadManager" title="https://wiki.freebsd.org/SummerOfCode2013/IntellegentDownloadManager">Project wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2013/IntellegentDownloadManager" title="Project wiki page">https://wiki.freebsd.org/SummerOfCode2013/IntellegentDownloadManager</a></td></tr><tr><td><a href="https://wiki.freebsd.org/IdeasPage/IDMS" title="https://wiki.freebsd.org/IdeasPage/IDMS">More information on DMS</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/IdeasPage/IDMS" title="More information on DMS">https://wiki.freebsd.org/IdeasPage/IDMS</a></td></tr></table><p>
-	Contact:
-	  Ambarisha
-	  Bhatlapenumarthi
-	 &lt;<a href="mailto:ambarisha@freebsd.org">ambarisha@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Xin
-	  Li
-	 &lt;<a href="mailto:delphij@freebsd.org">delphij@freebsd.org</a>&gt;
-	</p>
-      <p>This is a Google Summer of Code 2013 project that aims to
-	replace the <tt>fetch(1)</tt>-based method for getting
-	distribution files, such as source tarballs, for the third-party
-	applications (ports) with an intelligent Download Manager
-	Service (see links for more information).</p>
-
-      <p>All the modules highlighted in the project wiki have been
-	completed (see links).  Specifically:</p>
-
-      <ul>
-	<li>A service that receives and serves download requests.  It
-	  samples download speeds from different mirrors and uses this
-	  information to pick the best mirror on the next request.  It
-	  can migrate jobs between mirrors if it realizes that a
-	  complete download from a different mirror would be faster than
-	  proceeding with the mirror it is currently using.</li>
-
-	<li>A status dump feature has also been added to the client
-	  (<tt>dmget</tt>) which dumps the information about active
-	  downloads, speeds from mirrors, etc.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>The implementation (especially job migration and dumping
-	status) has not been tested thoroughly.  Test the code, write more
-	unit and regression tests.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Most of our funding is used to support
-	FreeBSD development projects, conferences and developer summits,
-	purchase equipment to grow and improve the FreeBSD infrastructure,
-	and provide legal support for the Project.</p>
-
-      <p>We listened to our donors who asked us to have more fundraising
-	efforts throughout the year.  This quarter we had the second of
-	three fundraising campaigns planned for 2013.  We started the
-	quarter having raised $365,291.  By the end of the quarter, we
-	raised $410,000 for the year.  These early donations have made a
-	significant impact on our fundraising efforts this year.</p>
-
-      <p>Some of the highlights from this past quarter include:</p>
-
-      <ul>
-	<li>Projects completed last quarter:
-
-	  <ul>
-	    <li>ARM Superpages</li>
-	    <li>Documentation project infrastructure enhancements</li>
-	  </ul></li>
-
-	<li>Projects in progress:
-
-	  <ul>
-	    <li>Native iSCSI kernel stack</li>
-	    <li>Newcons console driver</li>
-	  </ul></li>
-
-	<li>Projects that started last quarter:
-
-	  <ul>
-	    <li>Capsicum Integration</li>
-	    <li>Network Stack Layer 2 Modernization</li>
-	  </ul></li>
-
-	<li>Platinum Sponsor for EuroBSDCon, had six Foundation
-	  representatives attend the conference and the Developer Summit,
-	  sponsored 7 developers to attend the conference, and sponsored
-	  the Developer Summit.</li>
-
-	<li>Sponsored the Cambridge Developer Summit, and sponsored 2
-	  developers to attend this event.</li>
-
-	<li>Attended Indianapolis LinuxFest July 27, FOSSCON in
-	  Philadelphia August 10, Ohio LinuxFest in Columbus September 14,
-	  and LinuxCon in New Orleans September 16-17, to promote
-	  FreeBSD.</li>
-
-	<li>Met with the FreeBSD Core Team to discuss their goals and to
-	  discuss areas that we can help.</li>
-
-	<li>Met with the Documentation Team to talk about helping them
-	  update their website as well as what other areas we can help
-	  them with.</li>
-
-	<li>Recognized Dag-Erling Sm�rgrav at EuroBSDCon for his
-	  contributions to FreeBSD.</li>
-
-	<li>Became a sponsor of vBSDCon, a new conference in Washington,
-	  DC.</li>
-
-	<li>Hired Glen Barber as a full-time employee to do system
-	  administration work and to help with release engineering.</li>
-
-	<li>Hired Cinthy Tanko as a part-time administrative assistant
-	  to help with day-to-day Foundation activities.</li>
-
-	<li>Purchased hardware to be placed in our NYI colo to support
-	  the building and distribution of new style packages in advance
-	  of FreeBSD�10.</li>
-
-	<li>Provided teleconferencing services to the Core Team to
-	  support their monthly conferences.</li>
-      </ul>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2013-09-devsummit.html b/website/content/en/status/report-2013-09-devsummit.html
deleted file mode 100644
index e1976c430c..0000000000
--- a/website/content/en/status/report-2013-09-devsummit.html
+++ /dev/null
@@ -1,1051 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>EuroBSDcon 2013 Developer Summit Special Status Report</h1><p>This special status report contains a summary of the discussions
-      from the various working groups at the EuroBSDcon 2013 Developer
-      Summit.  The FreeBSD Project organizes developer summits at various
-      events, typically at the major BSD conferences, so that developers
-      can meet and discuss matters in person.</p><hr /><ul><li><a href="#Desktop">Desktop</a></li><li><a href="#Developer-Summit-Track">Developer Summit Track</a></li><li><a href="#DNS">DNS</a></li><li><a href="#Documentation">Documentation</a></li><li><a href="#Embedded-Platforms">Embedded Platforms</a></li><li><a href="#Networking">Networking</a></li><li><a href="#Ports-and-Packages">Ports and Packages</a></li><li><a href="#Security">Security</a></li><li><a href="#Toolchain-and-Build-Systems">Toolchain and Build Systems</a></li><li><a href="#USB">USB</a></li><li><a href="#Vendor-Discussions">Vendor Discussions</a></li><li><a href="#Virtualization">Virtualization</a></li><li><a href="#ZFS">ZFS</a></li></ul><hr /><h2><a name="Desktop" href="#Desktop" id="Desktop">Desktop</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DesktopWG-Summary.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DesktopWG-Summary.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DesktopWG-Summary.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DesktopWG-Summary.pdf</a></td></tr></table><p>
-	Contact:
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the Desktop working group, Kris Moore summarized the changes
-	made over the last few months in the world of PC-BSD.  Builds
-	based on the freshly released <tt>9.2-RELEASE</tt> are in
-	progress, and future builds based on <tt>10-STABLE</tt> are
-	coming soon.  The plan there is to track the <tt>10-STABLE</tt>
-	branch until it becomes <tt>11-STABLE</tt>.  Kris also described
-	the <q>rolling release</q> model they have switched to.  This
-	approach leverages <tt>freebsd-update(8)</tt> to provide rolling
-	updates for the base system (that is, the kernel and the
-	userland utilities) and in parallel with that, <tt>pkg(8)</tt>
-	is employed for the packages, especially for the desktop
-	applications.  It was also reported that the PC-BSD staff has
-	improved the ZFS integration of their tools, including the
-	installer.  Another highlight of the upcoming PC-BSD releases is
-	that they will include Gleb Kurtsou's PEFS that provides user
-	encryption of user home directories with PAM-based
-	authentication.</p>
-
-      <p>Next, the current in-progress items were reported and
-	discussed.  The <tt>sysutils/pcbsd-utils</tt> and
-	<tt>sysutils/pcbsd-utils-qt4</tt> ports have been recently added
-	to the ports tree that contain all PC-BSD developed tools and
-	utilities, where the former features the command-line and the
-	latter features the GUI-enabled versions of the corresponding
-	programs.  The PC-BSD developers have also been working on a
-	<q>life-preserver</q> ZFS command-line and GUI utility, which is
-	still in heavy development.  The purpose of these tools to
-	leverage ZFS for snapshot and replication functionality as a
-	backup solution.</p>
-
-      <p>Finally, the plans for PC-BSD�10 were summarized.  The PBI
-	package format that PC-BSD employs in now under revision and
-	will be updated to use <tt>pkg(8)</tt> repository to build PBIs
-	and provide better integration for server PBIs.  As part of this
-	effort, it will also be investigated whether it is possible to
-	run PBIs without actual installation.  <tt>pc-sysinstall</tt>
-	will have a text-based front-end.  This is going to be basic at
-	first, but later it will provide a command-line interface to do
-	installation with the <tt>pc-sysinstall</tt> backend.</p>
-    <hr /><h2><a name="Developer-Summit-Track" href="#Developer-Summit-Track" id="Developer-Summit-Track">Developer Summit Track</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://goo.gl/2EF30C" title="http://goo.gl/2EF30C">Playlist of the talks</a></td><td>
-	    URL: <a href="http://goo.gl/2EF30C" title="Playlist of the talks">http://goo.gl/2EF30C</a></td></tr></table><p>
-	Contact:
-	  G�bor
-	  P�li
-	 &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since 2011, the FreeBSD Developer Summit Track has become an
-	essential part of BSDCan and EuroBSDcon conferences.  It
-	provides the developers and community members an opportunity to
-	tell about their latest projects, brainstorm on solutions to a
-	hard problem, train attendees to use a new tool, make
-	observations about a FreeBSD development process and how to improve
-	it, talk about how their company uses FreeBSD, or coordinate
-	activities.  One can also catch reports from the Google Summer
-	of Code students at the European instances.</p>
-
-      <p>At EuroBSDcon 2013 we had talks on the following topics:
-	superpages for ARM, an SDIO stack, porting GlusterFS, unattended
-	encrypted kernel crash dumps, adding Capsicum support for
-	compression services, an intelligent download management
-	service, LLDB, improvements in packet forwarding, multipath TCP
-	support, a FreeBSD-based network simulation environment, and
-	finally, porting Mirage, an operating system written in the
-	OCaml functional language, to FreeBSD.  The playlist of the talk
-	recordings (audio with slides and demonstrations) can be found
-	above at the entry's URL section.</p>
-    <hr /><h2><a name="DNS" href="#DNS" id="DNS">DNS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-dns-summary.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-dns-summary.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-dns-summary.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-dns-summary.pdf</a></td></tr></table><p>
-	Contact:
-	  Erwin
-	  Lansing
-	 &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD�10 is not going to have BIND any more, it is going to
-	be based on <tt>unbound(8)</tt> and LDNS, both have been
-	imported into the base system, along with a small
-	<tt>host(1)</tt> replacement.  LDNS also comes with
-	<tt>drill(1)</tt> that needs a simple wrapper to make it
-	compatible with the <tt>dig(1)</tt> command-line interface.
-	OpenSSH can use LDNS for checking SSH fingerprints which also
-	implies that DNSSEC validation is enabled by default.  Note that
-	<tt>unbound(8)</tt> will be hidden, it will be a local resolver
-	only.  For other purposes, one shall have to install its version
-	in the Ports Collection instead.</p>
-
-      <p>For the next major version, FreeBSD�11, there will be more
-	time to find an alternative to BIND, so it was also discussed in
-	the working group what the requirements would be for an ideal
-	DNS implementation.  Based on the results, what we want is a
-	caching, validating resolver library, which is compartmentalized
-	by Capsicum, supports per-user policies and integration with the
-	Casper daemon, BSD-licensed, has a low footprint, fast, and
-	thread-safe.  But the most important factor here is that we want
-	to standardize the API towards application level, so we can
-	actually report back to the user on what happens in relation
-	with DNSSEC operations in an informative way.  There have been
-	many proposals for that, like the get-api from Hoffman, or
-	draft-hayatnagarkar-dns-ext-validator-api for <tt>libval</tt>,
-	but it is currently being standardized by members of IETF.  What
-	we want to do is to contact those people and make sure that
-	FreeBSD�11 will become a standard reference
-	implementation.</p>
-    <hr /><h2><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DocWGSummaryReport.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DocWGSummaryReport.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DocWGSummaryReport.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DocWGSummaryReport.pdf</a></td></tr></table><p>
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>We wanted to try something new this year, so instead of doing a
-	lot of talk, we focused on doing actual work, and fixing PRs in
-	collaboration with the attendees who participated the working
-	group.  It turned out that it did not work so well, because we
-	had a lot of things to discuss, but some issues were fixed
-	eventually.</p>
-
-      <p>There was a huge demand for a new webpage: it has to be more
-	modern to catch up with the recent trends.  It should provide
-	dynamic content like blogrolls, twitter feeds, etc.  Currently,
-	the problem is that the web site lacks many basic
-	functionalities, such as the search option is not working
-	properly.  Isabelle Long has been working on integrating the
-	DuckDuckGo search engine into the web site, and she will
-	hopefully commit the necessary changes soon.  There are other
-	problems, for example, there is no link to the FreeBSD Forums,
-	while they have established themselves as another support option
-	for users.</p>
-
-      <p>Then the representatives of the FreeBSD Foundation joined our
-	group and showed us what they have been working on.  They showed
-	a design proposal for their website.  Their suggestion is to
-	make the FreeBSD Foundation website look similar to the FreeBSD
-	Project website, so these pages could be connected visually.
-	Judging from the fancy proposal they have shown us, it will
-	probably take a lot of infrastructural work to make our website
-	look closely to the Foundation's.  As a result, we agreed to
-	form a team for the new website, assembled from Project members
-	internally, to ensure that the new design satisfies expectations
-	from all sides, e.g., administration, functionality, security,
-	and so on.</p>
-
-      <p>Another thing that we have talked about was the on-going print
-	edition work of the FreeBSD Handbook.  We have promised to complete
-	the effort by BSDCan this year, but apparently we could not make
-	it in time.  Dru Lavigne went through the whole Handbook and
-	identified many problems to solve (outdated content, unrelated
-	sections, etc.) in order to have really good content ready for
-	the printed edition.  We need more content and reviewers, so if
-	you are looking through the Handbook and meet an outdated
-	section, please contact the Documentation Team.  You do not have
-	to send patches right away, it is enough to provide a few
-	sentences or a paragraph only to improve or add the description
-	for the given system functionality.  The Documentation Team will
-	then take care of putting them in the Handbook or the relevant
-	documents.</p>
-
-      <p>We also discussed the idea of having maintainers assigned to
-	specific sections and chapters of the Handbook, similarly to the
-	policy implemented in the Ports Collection, so users and related
-	PRs can be forwarded to them, and the maintainers take care of
-	keeping those areas in the documentation up-to-date.  The goal
-	is to reduce the overall workload on the Documentation Team.</p>
-
-      <p>Finally, it was mentioned at the vendor group that we want to
-	revamp our actual workflow for translating documents.  We are
-	currently doing the translation work by using a standard editor
-	translating sentence by sentence, which is tedious.  In addition
-	to that, most of the translator teams are really small, so it is
-	hard for them to catch up with the changes in the English
-	documents and they become outdated quickly.  We have briefly
-	talked with Gavin Atkinson about removing really outdated
-	documentation from the <tt>doc</tt> tree, like the ones who are
-	still reflecting FreeBSD�5.x or so.  In summary, the main
-	objective is to have a system that helps by keeping track of
-	translations, like the PC-BSD developers are doing: we are aware
-	that Kris Moore has written some scripts to extend the standard
-	tools like Pootle to improve their efficiency.  It would be a
-	huge win to see how many sentences are already translated, how
-	many are left to translate, how many of them could be reused
-	using such a system.  Another benefit of these systems is that
-	they can provide an interface for casual contributors to provide
-	translations which can be then checked and committed by the
-	documentation developers.</p>
-    <hr /><h2><a name="Embedded-Platforms" href="#Embedded-Platforms" id="Embedded-Platforms">Embedded Platforms</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=Embedded-devsummit-201309.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=Embedded-devsummit-201309.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=Embedded-devsummit-201309.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=Embedded-devsummit-201309.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit/Embedded" title="https://wiki.freebsd.org/201309DevSummit/Embedded">Notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit/Embedded" title="Notes">https://wiki.freebsd.org/201309DevSummit/Embedded</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201308DevSummit/Embedded" title="https://wiki.freebsd.org/201308DevSummit/Embedded">Cambridge notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201308DevSummit/Embedded" title="Cambridge notes">https://wiki.freebsd.org/201308DevSummit/Embedded</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>The discussion on embedded platforms was started in Cambridge a
-	month earlier, where it was kicked off with a presentation by
-	BrilliantService on their Viking operating system for a head
-	mount augmented reality display.  We then had a discussion of
-	board bringup and the related topic of kernel minimization.
-	This was followed by a long discussion of system image creation
-	and what is required to promote some embedded platforms to
-	Tier-1 status.  Finally, we discussed power management.</p>
-
-      <p>The discussion of Tier-1 status for embedded platforms,
-	particularly Raspberry-Pi, identified a number of things required
-	to make this possible.  In addition to some driver improvements
-	and stabilization efforts, we need to build images as part of,
-	or derived from the products of the current release build
-	process.  We also need to be building packages (Stacey Son is
-	working on making this happen for ARM and MIPS64).  We will also
-	need some form of binary updates.  Initially this will probably
-	be done via <tt>freebsd-update(8)</tt>, but in the long term this
-	will likely be too slow to be practical.  Further discussion of
-	this topic was a major thread at the EuroBSDCon developer
-	summit.</p>
-
-      <p>The power management discussion was wide ranging and concluded
-	that we do need better power management infrastructure and that we
-	are not entirely sure what that looks like.  We certainly do
-	need some way to represent the power management bus/device trees
-	that differ from the conventional models of attachment in our
-	device infrastructure.  We also need smarter scheduling to allow
-	us to do things like steer all interrupts away from certain
-	cores so they can be shut all the way down.</p>
-
-      <p>In Malta, the first thing we talked about was trying to get
-	better goals, use cases for the external toolchain support so that
-	we have the work done by FreeBSD�11, where any architecture
-	that supports can be built by using external toolchains.  We
-	talked about different ways for an architecture that does not
-	have support for a native toolchain to work in the QEMU-based
-	package building infrastructure.  By FreeBSD�11, we also want
-	to make sure that it was all well-documented so that users will
-	know what is and what is not supported on a given platform.</p>
-
-      <p>Next, we had a long discussion about the auto tuning changes
-	that Alfred Perlstein did recently.  They are great for machines
-	with a gigabyte or more memory, but they are bad for machines
-	that almost have no memory, so Adrian Chadd has volunteered to
-	fix this (see the slides for more details).</p>
-
-      <p>We talked a lot about what to do around the ARM port in
-	FreeBSD�11, and we have set some goals for 11 in this area.
-	Some of the highlights are as follows.  We want to have the
-	ability to boot one kernel on any <tt>armv6</tt> platform
-	&#8212; currently there are a number technical roadblocks to
-	that.  We want to keep the <tt>armv4</tt> and <tt>armv5</tt>
-	support in 11 until there is some particular reason not to do
-	that.  One of the biggest tasks probably, since we are moving to
-	Clang, would be the external toolchain item.  Besides that, the
-	<tt>armv6</tt> will grow hardware floating-point support, we are
-	hoping to have Symmetric Multi-Processing (SMP).  And we talked
-	rather extensively about some of the release engineering tasks
-	we will have to do: we need to have images for popular boards,
-	such as Raspberry Pi and BeagleBoard.  We would like to have
-	some work done in this area in the 10.1 timeframe.  We want to
-	get packages spun up for ARM and MIPS, as well as setting the
-	infrastructure up for <tt>freebsd-update(8)</tt>.  It was also
-	briefly mentioned that there is no good GPU support on ARM right
-	now, and that is on the FreeBSD side.  We need a strategy that has
-	the least disadvantages, which might be adopting the Android ABI
-	and let the Android blobs to be dropped in.  There are a number
-	of challenges in this case.</p>
-
-      <p>In addition to that, we talked about MIPS and various FDT
-	issues.  The key problems for the latter were that we need
-	better clock and power support and there are separate
-	<q>domains</q> from the device tree, and they need to be
-	treated as such.  Also, GPIO and pinmux are inconsistent
-	between the different releases, we need to fix that.  We also
-	talked about Arm64, where there are lot of things to do.  The key
-	though is find out (with the assistance of the FreeBSD Foundation)
-	who is interested in Arm64 among the vendors and how to
-	collaborate with them.  Since the Foundation has the contacts
-	and the related NDAs to the largest consumers, probably they are
-	in the best position to drive this effort.  Together with the
-	Semihalf people and the ARM representative at the summit, Andrew
-	Wafaa, we have conluded that Arm64 support is not far away from
-	the things we have now support for in the kernel.  It turned out
-	that it is mostly about how we organize the source tree and
-	similar minor issues.</p>
-    <hr /><h2><a name="Networking" href="#Networking" id="Networking">Networking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit/Networking" title="https://wiki.freebsd.org/201309DevSummit/Networking">Notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit/Networking" title="Notes">https://wiki.freebsd.org/201309DevSummit/Networking</a></td></tr></table><p>
-	Contact:
-	  Lawrence
-	  Stewart
-	 &lt;<a href="mailto:lstewart@FreeBSD.org">lstewart@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Gleb
-	  Smirnoff
-	 &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>Andr� Oppermann gave a status report on his current work on the
-	interface between the network stack and the drivers.  He is
-	planning to publish a formal documentation on the stack-driver
-	boundary and split the <tt>ifnet</tt> structure into separate,
-	stack- and driver-owned sections.  All drivers will be adjusted
-	to this new world order, and a call for feedback will be posted
-	to the respective mailing lists.  This change is being
-	implemented in the <tt>projects/ifq</tt> Subversion branch,
-	supervised by Ed Maste on behalf of the FreeBSD Foundation as
-	sponsor.  Andr� is close to completing his TCP-AO work, and
-	working on moving the IPsec code into a <tt>pfil(9)</tt>-based
-	kernel module.  Gleb Smirnoff came up with the problem of
-	implementing a lightweight reference counting to avoid dangling
-	pointers, and Alexander Chernikov started a discussion on the
-	routing performance.</p>
-
-      <p>Another highlight of the networking stack working group was the
-	discussion on testing, where everybody agreed that developers
-	should communicate with companies able to test the performance
-	with different workloads.  Olivier Cochard-Labb� (from Orange)
-	and Alexander Chernikov (from Yandex) have already shown
-	interest in this effort, while the Netflix staff (Lawrence
-	Stewart, Adrian Chadd, and Scott Long) confirmed that they have
-	access to a TCP-heavy production workload.  On a related note,
-	it was added that Netflix is looking to host developer summits
-	focused on networking in Los Gatos, California, on a
-	semi-regular basis.</p>
-    <hr /><h2><a name="Ports-and-Packages" href="#Ports-and-Packages" id="Ports-and-Packages">Ports and Packages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-ports-summary.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-ports-summary.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-ports-summary.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-ports-summary.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit/Ports" title="https://wiki.freebsd.org/201309DevSummit/Ports">Notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit/Ports" title="Notes">https://wiki.freebsd.org/201309DevSummit/Ports</a></td></tr></table><p>
-	Contact:
-	  Erwin
-	  Lansing
-	 &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>We had one full presentation by Allan Jude, a quick overview of
-	what they did for the PC-BSD CDN (Content Delivery Network).
-	For example, it uses the <tt>--delay-update</tt> flag for
-	<tt>rsync(1)</tt> to make it more atomic, uses a lot of ZFS
-	functions (e.g., replication, snapshot management) and
-	implements automatic mirror selection.  It was a quite
-	interesting talk, and featured some interesting ideas that we
-	could pick and use for the FreeBSD package distribution network.
-	This was then followed by a talk by Jeremy Le Hen, who talked
-	about stack protection (SSP).  It will be enabled by default in
-	FreeBSD�10.x on amd64 and i386 platforms, but can be turned
-	off by the <tt>SSP_UNSAFE</tt> knob.  Conversely, it is not
-	enabled by default on 9.x, but can be turned on by the other
-	knob, <tt>WITH_SSP_PORT</tt>.  This should work on amd64, and it
-	has no effect on i386.</p>
-
-      <p>Baptiste Daroussin talked about staged installs which was
-	committed recently.  Every other package system does that, now we
-	do it as well.  It brings a lot of improvements, such as we can
-	catch packaging list errors earlier, before the package is
-	actually installed on the file system.  There the
-	<tt>NEED_ROOT</tt> knob can be used if a port requires root
-	privileges for building and packaging.  It also simplifies most
-	of the logic employed at the build farms, because many of the
-	checks can be automated this way, catching broken plists and
-	helping to get rid of the special <tt>post-install</tt> scripts.
-	It lays the foundation for some new features we want to add in
-	the future, for example implementing sub-packages.  Having
-	sub-packages enables building packages once and putting files
-	into separate smaller packages which can be then installed
-	individually.  Compared to all the other options, it is turned
-	off by default, and ports are slowly converted to this format
-	one by one &#8212; however, at some point, we might say that
-	ports not converted to support staging will be removed.
-	Actually, this would help us find out which ports in the tree
-	are not used any more.</p>
-
-      <p>Then there was a discussion about what to do next.  We have
-	been talking about package sets for at least three years now, it
-	seems we are finally able to do it.  We are going to try to do a
-	security branch, together with reviving the ports security team,
-	in cooperation with the Security Officer, Dag-Erling Sm�rgrav.
-	We are aiming for quarterly releases and weekly security updates
-	for those releases in the security branch.  This has been an
-	ongoing plan for three years, because we needed many things to
-	happen before we could proceed, such as moving away from CVS,
-	introducing new-style binary packages, deploying new build
-	clusters.  We have finally got them all, and we can actually do
-	it now with the <tt>pkg-test</tt> setup.  So, we are hoping to
-	start with the first quarterly release in early November.</p>
-
-      <p>We had a long discussion about removing support for old-style binary
-	packages now that we have <tt>pkg(8)</tt>.  Staying compatible with
-	<tt>pkg_install(1)</tt> hinders the introduction of new features, e.g.,
-	sub-packages mentioned above.  We cannot really add those new features
-	as the old tools will not support them and we cannot expect ports to
-	work with two different package formats at the same time.  We
-	do not want to surprise our users too much, but it turns out there is
-	an easy migration path.  Among many others, an advantage of
-	<tt>pkg(8)</tt> that it can interoperate with various
-	third-party applications, e.g., puppet and chef.  It is still a POLA
-	violation, so we should be careful of how the actual transition is
-	made.  We should give a lot of warning to the users, specially in case
-	of large installations, where there are custom scripts to work with
-	ports and packages.  The date for throwing the switch has been
-	set for six months, that is, April 2014, which fits nicely with
-	the End-of-Life date of 8.3-RELEASE, the last release that does
-	not include <tt>pkg(8)</tt>.  So, at BSDCan next year, we can
-	hopefully celebrate the switch from <tt>pkg_install(1)</tt>.</p>
-
-      <p>Finally, we discussed issues related to package naming.  The
-	problem is that certain ports have the same name and they rely
-	on this, so currently we have <tt>LATEST_LINK</tt> to work
-	around this behavior.  We should educate people to make better
-	use of <tt>PKGNAMESUFFIX</tt> to make sure that all affected
-	ports have a unique name.  To encourage this, we should set up
-	automated checking to warn people about having packages of the
-	same name.  <tt>PKGNAME</tt> must be unique across categories,
-	so when one uses <tt>pkg-add(8)</tt>, the system has to know
-	which package to choose for install.  This will improve things
-	for better handling of options, adding package flavors and
-	implementing sub-packages.</p>
-    <hr /><h2><a name="Security" href="#Security" id="Security">Security</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=201309+DevSummit+Security+Report.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=201309+DevSummit+Security+Report.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=201309+DevSummit+Security+Report.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=201309+DevSummit+Security+Report.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit/Security" title="https://wiki.freebsd.org/201309DevSummit/Security">Notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit/Security" title="Notes">https://wiki.freebsd.org/201309DevSummit/Security</a></td></tr></table><p>
-	Contact:
-	  Dag-Erling
-	  Sm�rgrav
-	 &lt;<a href="mailto:des@FreeBSD.org">des@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the security working group, we had four items in the agenda.
-	First of all, we started with the current state of
-	<tt>/dev/random</tt>.  There were a number of known entropy
-	harvesting bugs that have been fixed, for example feeding a lot of
-	zeroes from the network stack.  We have a pluggable random
-	generator framework and we have a number of plugins for it,
-	Yarrow is one, and the RDRAND, Padlock are two others, we have
-	one that blocks and one that panics, and few coding examples and
-	so on.  For 10, we are going to backtrack and remove RDRAND and
-	Padlock backends and feed them into Yarrow instead of delivering
-	their output directly to <tt>/dev/random</tt>.  It will still be
-	possible to access hardware random number generators, that is,
-	RDRAND, Padlock etc., directly by inline assembly or by using
-	OpenSSL from userland, if required, but we cannot trust them any
-	more.  In addition to this, we want to collect more entropy
-	early in the boot process, because we want to get rid of the
-	<tt>initrandom</tt> script that feeds mostly static data into
-	<tt>/dev/random</tt> and pretends that is actually entropy,
-	when it is not.  Pawel Jakub Dawidek has a patch which has been
-	floating around and doing some analysis on this, we finally got
-	some numbers for it.  This patch feeds the amount of time it
-	takes to attach a device into <tt>/dev/random</tt> and it turns
-	out that one can get about 4 good bits of entropy from each
-	device.  Also, we should have the installer fill up the
-	<tt>/entropy</tt> file on the newly installed system, so we have
-	something when the system starts up for the first time.  And
-	there is also the matter of (especially with virtualization and
-	cloning, which is becoming more and more common) ensuring that
-	the clones diverge quickly enough.  As an example, we discussed
-	having the installer generate SSH keys.  But a problem is that if
-	you install a VM and it generates the SSH keys, and then it is
-	cloned, all the instances will have the same keys.  So when the
-	individual VMs are started and they do not have enough entropy
-	harvesting early in the boot process, then keys are generated
-	based on the entropy that the installer has dumped during the
-	installation process, which is as almost as bad.  The device
-	attach patch helps with that.</p>
-
-      <p>The next item was package signing.  We have a short-term
-	solution for 10 until a more professional one is developed.  In
-	this design, the package builders do not have the keys, instead
-	they submit hashes to a signing server after they are done, and
-	the signing server returns the signature.  We are simply going
-	to ship the fingerprints with the base system under
-	<tt>/etc/pkg/fingerprints</tt>.  If we need to revoke a key, or
-	distribute a new key, we will just issue a new FreeBSD Security
-	Advisory (which should be done anyway), and will have
-	<tt>freebsd-update(8)</tt> distribute an update that moves
-	the key from the <tt>trusted</tt> directory to the
-	<tt>revoked</tt> directory and adds the new key to the
-	<tt>trusted</tt> directory.  When launched, <tt>pkg(8)</tt>
-	looks into those directories, loads all the keys it finds, and
-	will accept a packages if it is signed by at least one good key
-	and no revoked keys.</p>
-
-      <p>Package signing was followed by mitigation by Sofian Brabez.
-	He has stackgap optimization and <tt>mmap()</tt> randomization
-	ready to be included in 10, but turned off by default.  Stackgap
-	randomization adds a random amount of empty space at the top of
-	the stack, so that an attacker cannot just make assumptions
-	about the actual stack layout of the applications in case of
-	buffer overflows.  The problem with stackgap randomization is
-	programs like Varnish, that have many threads and therefore very
-	small stacks in order to avoid running out of stack space, will
-	run out of stack space.  This is because stackgap randomization
-	will increase the size of the stacks.  <tt>mmap()</tt>
-	randomization inserts a random gap between consecutive mappings
-	for the same purpose.  Stack protection (SSP) can now be enabled
-	by default.  The problem is if it is turned on by default, a lot
-	of ports will break.  It is because GCC includes an additional
-	object file during linking for checking the canary words, and
-	this apparently interferences the way some ports build.
-	<tt>libc</tt> is now a linker script and not just a <tt>.so</tt>
-	file, therefore the linker will always know how to handle this.
-	<tt>ldbase</tt> randomization was also discussed, but it has not
-	been implemented.  It randomizes where the libraries are loaded
-	by the run-time linker.</p>
-
-      <p>The final item on the agenda was VuXML and <tt>portaudit</tt>.  We
-	have a number of shortcomings with VuXML.  One of them is that the
-	<tt>portaudit</tt> tool is based on string matching which is
-	unreliable, especially when we have ports that are renamed and
-	multiple ports, different versions of the same software.  In addition,
-	there are many errors in the actual data, especially a very
-	common error is to have <tt>&gt;</tt> instead of <tt>&gt;=</tt>.
-	Also, the auditing tools do not verify the base system version.
-	We have VuXML entries for Security Advisories but they are
-	unused because of this.  One of the reasons for that is that the kernel
-	patch level does not necessarily reflect the patch level of the
-	userland, because <tt>freebsd-update(8)</tt> does not update the
-	kernel patch level unless the actual update affects the kernel.  So
-	we are going to start including CPE information in ports.  That is the
-	Common Platform Enumeration, and that is a NIST standard for uniquely
-	identifying software packages, versions, variances, even port
-	revisions.  The point of using CPEs is that it is unique, not
-	tied to the name of the port so we can have multiple ports with
-	the same CPE without any trouble.  We will store it as
-	annotations for <tt>pkg(8)</tt> packages.  CPEs published by
-	NIST can be simply pushed directly to VuXML and we do not have
-	to do the matching ourselves any more.  The specification of CPE
-	includes a matching algorithm and is shipped with a reference
-	implementation.  FreeBSD�10 is going to install a script under
-	<tt>/libexec</tt> that prints the userland patch level, and
-	<tt>freebsd-update(8)</tt> will update that script so it will be
-	possible to verify the userland patch level as well.</p>
-    <hr /><h2><a name="Toolchain-and-Build-Systems" href="#Toolchain-and-Build-Systems" id="Toolchain-and-Build-Systems">Toolchain and Build Systems</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=toolchain-and-build-eurobsdcon2013.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=toolchain-and-build-eurobsdcon2013.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=toolchain-and-build-eurobsdcon2013.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=toolchain-and-build-eurobsdcon2013.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit/ToolchainAndBuild" title="https://wiki.freebsd.org/201309DevSummit/ToolchainAndBuild">Notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit/ToolchainAndBuild" title="Notes">https://wiki.freebsd.org/201309DevSummit/ToolchainAndBuild</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201308DevSummit/ToolchainAndBuild" title="https://wiki.freebsd.org/201308DevSummit/ToolchainAndBuild">Cambridge notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201308DevSummit/ToolchainAndBuild" title="Cambridge notes">https://wiki.freebsd.org/201308DevSummit/ToolchainAndBuild</a></td></tr><tr><td><a href="https://wiki.freebsd.org/GPLinBase" title="https://wiki.freebsd.org/GPLinBase">Roadmap</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/GPLinBase" title="Roadmap">https://wiki.freebsd.org/GPLinBase</a></td></tr></table><p>
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>The discussions on toolchains and build systems in Malta
-	started a month earlier in Cambridge.  There, the main themes
-	were source code analysis, the status of replacing GCC, and a
-	discussion of packaging the base system.  Notes on these and
-	other topics can be found on the session page on the wiki.</p>
-
-      <p>Source code analysis took several directions.  We discussed
-	adding annotations to the source tree to support various advanced
-	analysis tools.  There was general agreement that this has some
-	downsides if they get out of date, but that it is useful so long
-	as the annotations are verified.  Most proposed annotation
-	require some sort of LLVM support, so we discussed the process of
-	integrating LLVM analysis into the build framework.  We also
-	discussed the idea of running various analysis tools as part of
-	the tinderbox framework.</p>
-
-      <p>In the context of replacing GCC, we discussed David Chisnall's
-	plan to stop building GCC and <tt>libstdc++</tt> on systems where
-	Clang is the default compiler (this has happened).  Further, we
-	plan to migrate all existing platforms to Clang or an external
-	GCC by 11.  External toolchain support currently works with
-	Clang, but not GCC.</p>
-
-      <p>Finally, Baptiste Daroussin discussed his proposal to package
-	base with packages as a replacement for the current tarballed
-	distributions.  Once this is done, it is possible to do the tasks
-	<tt>freebsd-update(8)</tt> does including upgrades and detecting
-	changed files in a more operating-friendly way.  Using
-	<tt>pkg(8)</tt> as a replacement for <tt>freebsd-update(8)</tt>
-	is not a general solution yet, as package signing and delta
-	support is required to make it viable.</p>
-
-      <p>In Malta we covered two main topics: the overall status of
-	non-permissively licensed (GPL-licensed) software in the base
-	system, and a detailed discussion of the status of external
-	toolchain support.  We also decided that a future meeting should
-	discuss making incremental builds practical and that we should
-	run a working group specifically on the kernel build system at a
-	future conference.</p>
-
-      <p>About half the meeting was consumed by a detailed walkthrough
-	of the <tt>GPLinBase</tt> wiki page (see links).  A number of
-	areas need modest amounts of work and <tt>binutils</tt>
-	replacement needs quite a bit.  In practice, we believe we have
-	most of the required pieces in either the ELF Toolchain project
-	or LLVM, but the work of identifying pieces and testing them
-	with base and ports will take some time.</p>
-
-      <p>We then discussed the status of Warner Losh's work on adding
-	support for GCC to the external toolchain infrastructure and on
-	upstreaming patches to GCC.  Fortunately, the majority of our
-	changes to GCC in base are x86 modernization which is no longer
-	required in new releases.  In practice, we have about 2000 lines
-	of changes that should be merged and a few hundred more we
-	should add to cross toolchain ports.  In addition to creating a
-	modern cross GCC, the external toolchain support needs work due
-	to differences in support for <tt>-B</tt> and possibly
-	<tt>--sysroot</tt> between Clang and GCC.  Further discussions
-	of external toolchain support occurred in the Embedded
-	session.</p>
-    <hr /><h2><a name="USB" href="#USB" id="USB">USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013Status.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013Status.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013Status.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013Status.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013.pdf">Notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013.pdf" title="Notes">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=DevSummitUSB2013.pdf</a></td></tr></table><p>
-	Contact:
-	  Hans-Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the USB working group, Hans-Petter Selasky summarized what
-	happened to FreeBSD's USB stack during the last year.  He
-	mentioned that there were no serious issues, while the USB
-	driver support improved on both device and controller fronts.
-	He also noted that many systems have started to use the USB
-	stack itself outside the FreeBSD kernel, for example DragonFly BSD.
-	Hans-Petter briefly walked through the list of ideas on how to
-	improve USB support further: he wants to import more Linux USB
-	serial port and Ethernet device drivers into userspace, which
-	can be then accessed through his <tt>webcamd(8)</tt> daemon,
-	move the NDIS (Ethernet and wireless) USB wrapper to userspace,
-	and implement emulation of the Linux USB file system at
-	character device level via the Cuse4BSD-based daemon, also in
-	userspace.</p>
-
-      <p>The summary was followed by the discussion of how to fix the
-	detach issues experienced in case of USB wireless and Ethernet
-	devices, initiated by Adrian Chadd.  In addition to that, some
-	DWC OTG were discussed, such as the need for implementing DMA
-	support and expose it to more testing for all device speeds, not
-	only for Ethernet and memory sticks.</p>
-    <hr /><h2><a name="Vendor-Discussions" href="#Vendor-Discussions" id="Vendor-Discussions">Vendor Discussions</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-vendor-summary.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-vendor-summary.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-vendor-summary.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=20130928-eurobsdcon-vendor-summary.pdf</a></td></tr></table><p>
-	Contact:
-	  Erwin
-	  Lansing
-	 &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;
-	</p>
-      <p>First, Justin Gibbs, on behalf of the FreeBSD Foundation, gave a
-	status update.  A major change was that previously we had only a
-	single part-time employee, Deb Goodkin.  Now we have a two
-	full-time technical staff members involved in some of the
-	current projects, such as Kostik Belousov who is still working
-	on improving our X.org support.  They are also helping out with
-	improving continuity within different teams like the Release
-	Engineering Team and the Security Team.  We also employed Glen
-	Barber as a system administrator who is working with the FreeBSD
-	cluster administrators to supervise the Project's machines, and
-	he is also helping out with release engineering.  Ed Maste has
-	been employed part-time as a project manager to oversee the
-	progress of the Foundation-sponsored projects.  But we are
-	hoping to get more people involved, especially on the sides of
-	administration and marketing.</p>
-
-      <p>We had a presentation by Daichi Goto about his company in
-	Japan, called BSD Consulting, Inc.  He consulted for a company
-	where he wanted to solve problems using FreeBSD but the company did
-	not allow him to do that as they could not get commercial
-	support for FreeBSD.  So he started his own company solely for this
-	purpose, which for example, includes hardware certification.</p>
-
-      <p>There was a discussion revolving around that current status of
-	our documentation and web site, especially in Japan, where most
-	of the people do not speak English very well.  In the rest of
-	the time we had a long but fruitful discussion about smaller
-	projects, for example incorporating more bug fixes related to
-	Infiniband into releases.  In general, it would be useful to
-	backport not only security fixes but major fixes and release
-	backported erratas for the releases.  Then we talked about
-	nanobsd support, making it more visible and accessible to the
-	potential users.  Next, we talked about promoting ARM and MIPS
-	platforms to Tier-1, providing more translated documents and
-	testimonials, documentation to attract news users for FreeBSD and
-	reach out for them: how to write problem reports, debug the
-	kernel, etc.  In connection to that, PR triage was also
-	mentioned, where the goal is to provide an answer for every
-	incoming bug report in a couple of days.  As usual, Java was
-	also on the menu, where it seems they are swinging back to
-	OpenJDK being the default in 1.8.</p>
-    <hr /><h2><a name="Virtualization" href="#Virtualization" id="Virtualization">Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=eurobsdcon_summary.pdf" title="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=eurobsdcon_summary.pdf">Summary</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=eurobsdcon_summary.pdf" title="Summary">https://wiki.freebsd.org/201309DevSummit?action=AttachFile&amp;do=get&amp;target=eurobsdcon_summary.pdf</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201309DevSummit/Virtualization" title="https://wiki.freebsd.org/201309DevSummit/Virtualization">Notes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201309DevSummit/Virtualization" title="Notes">https://wiki.freebsd.org/201309DevSummit/Virtualization</a></td></tr></table><p>
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the virtualization working group, Peter Grehan gave a status
-	report.  In FreeBSD�10, a lot of pieces of work have been
-	going on for the last two years, so we are slowly getting the
-	guest support of Xen, PHVM, Hyper-V drivers, and
-	<tt>bhyve(4)</tt> into 10.0-RELEASE.  We talked a little bit
-	about the <tt>bhyve(4)</tt> <q>memory overcommit</q> work that
-	Neel has been doing for a quite long time, but we are hoping
-	that it will get into 10 as well.  It gives much better
-	integration with management of guest memory, with the FreeBSD
-	Virtual Memory subsystem, so we can actually page guest memory
-	to swap.  Some of the future directions for the
-	<tt>bhyve(4)</tt> work has also been discussed: we want to shift
-	away from the user-space boot loader, and use the BSD-licensed
-	UEFI code from Intel as a boot ROM, we want to have more Windows
-	guest support at some point, and getting the ability to suspend
-	and resume the guests, which eventually leads to adding support
-	for live migration.</p>
-    <hr /><h2><a name="ZFS" href="#ZFS" id="ZFS">ZFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Martin
-	  Matu&#353;ka
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Matthew
-	  Ahrens
-	 &lt;<a href="mailto:mahrens@delphix.com">mahrens@delphix.com</a>&gt;
-	</p>
-      <p>For starting up, Justin Gibbs gave an overview of shingled media
-	which is a new technology that is coming from the hardware
-	vendors.  We talked about some performance issues with that,
-	came up with some simple ideas of how to make sure that
-	everything can take advantage of this, or actually not to have
-	bad performance when not deleting, just overwriting the data.
-	We finally came to the conclusion that it is probably very hard
-	to do better than that.</p>
-
-      <p>Then a status report of ZFS on other platforms besides FreeBSD and
-	Illumos was given.  On Linux, it basically works, it is being
-	actively developed, it is in the kernel.  On Mac OS X, it is
-	quite immature, but there is a lot of work going on there.  On
-	Oracle Solaris, they are still working on ZFS but probably we
-	will never see source code from them.</p>
-
-      <p>We talked about creating a common, cross-platform code
-	repository for ZFS that all the platforms would pull code from.
-	The idea here is that all the platforms available would get the
-	platform-independent code from there verbatim, so getting
-	changes into all platforms is much easier.  This would not
-	include things like the ZPL, which need to interface with each
-	platform-specific VFS layer, but that would reduce the hackiness
-	of the Solaris Porting Layer that is in FreeBSD and Linux while
-	adding a little bit of porting layer to Illumos.  We talked
-	about how we should stage this work and we decided we definitely
-	want to try to include the Linux developers from the beginning
-	rather than doing just Illumos plus FreeBSD and then tacking on the
-	Linux layer.</p>
-
-      <p>Next, we talked about test coverage and what tests are
-	available.  Spectra Logic has finished porting the STF test suite
-	to FreeBSD, so we discussed how we can make them more widely
-	available, and potentially getting them into the main source
-	tree.  Eventually, it will become part of the independent code
-	repository but it may take a while to get there.</p>
-
-      <p>And then we also talked about <tt>zfsd</tt>, which is a
-	substitute for FMA.  This is a Solaris technology which deals
-	with hot spares and device replacement, etc.  So <tt>zfsd</tt>
-	is a replacement for this tool on FreeBSD, implemented by Spectra
-	Logic.  With regard to this, we discussed some of the issues
-	about getting it into the main tree, as they had done some
-	subtle physical pathing that was not a hundred percent
-	generic.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2013-10-2013-12.html b/website/content/en/status/report-2013-10-2013-12.html
deleted file mode 100644
index ab8b67c09f..0000000000
--- a/website/content/en/status/report-2013-10-2013-12.html
+++ /dev/null
@@ -1,1619 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between October and
-      December 2013.  This is the last of four reports planned for
-      2013.</p><p>The last quarter of 2013 was very active for the FreeBSD
-      community, much like the preceding quarters.  Many advances were
-      made in getting FreeBSD to run on ARM-based System-on-Chip boards
-      like Cubieboard, Rockchip, Snapdragon, S4, Freescale i.MX6, and
-      Vybrid VF6xx.  FreeBSD is also becoming a better platform for Xen
-      and the Amazon Elastic Compute Cloud.  There are plans for FreeBSD
-      to become a fully supported compute host for OpenStack.  The I/O
-      stack has again received some performance boosts on
-      multi-processor systems through work touching the CAM and GEOM
-      subsystems, and through better adaptation of UMA caches to
-      system memory constraints for ZFS.  The FreeBSD Foundation did an
-      excellent job in this quarter, and many of their sponsored
-      projects like VT-d and UEFI support, iSCSI stack, Capsicum, and
-      auditdistd are about to complete. At the same time, new projects
-      like Automounter and Intel GPU updates have just been launched.
-      The Newcons project has been merged into -CURRENT, which will
-      make it possible to finally move to the latest version of X.Org
-      in the Ports Collection. Efforts are also under way to improve
-      testing with Jenkins and Kyua.  It is an exciting time for users
-      and developers of FreeBSD!</p><p>Thanks to all the reporters for the excellent work!  This report
-      contains 37 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between January and
-      March 2014 is April 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#CBSD">CBSD</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></li><li><a href="#Intel-802.11n-NIC-(iwn(4))-Work">Intel 802.11n NIC (iwn(4)) Work</a></li><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#UMA/ZFS-and-RPC/NFS-Performance-Improvements">UMA/ZFS and RPC/NFS Performance Improvements</a></li><li><a href="#Updated-vt(9)-System-Console">Updated vt(9) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#FreeBSD-on-Cubieboard{1,2}">FreeBSD on Cubieboard{1,2}</a></li><li><a href="#FreeBSD-on-Freescale-i.MX6-processors">FreeBSD on Freescale i.MX6 processors</a></li><li><a href="#FreeBSD-on-Freescale-Vybrid-VF6xx">FreeBSD on Freescale Vybrid VF6xx</a></li><li><a href="#FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/Xen">FreeBSD/Xen</a></li><li><a href="#Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#auditdistd(8)">auditdistd(8)</a></li><li><a href="#Base-GCC-Updates">Base GCC Updates</a></li><li><a href="#BSDInstall-ZFSBoot">BSDInstall ZFSBoot</a></li><li><a href="#Capsicum-and-Casper">Capsicum and Casper</a></li><li><a href="#Centralized-Panic-Reporting">Centralized Panic Reporting</a></li><li><a href="#FreeBSD-Test-Suite">FreeBSD Test Suite</a></li><li><a href="#The-LLDB-Debugger">The LLDB Debugger</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#X.Org-on-FreeBSD">X.Org on FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p>
-	Contact: FreeBSD Cluster Administration Team &lt;<a href="mailto:admins@">admins@</a>&gt;
-	</p>
-      <p>The FreeBSD Cluster Administration Team consists of the people
-	responsible for administering the machines that the project
-	relies on for its distributed work and communications to be
-	synchronised.  In the last quarter of 2013, they continued
-	general maintenance of the FreeBSD cluster across all sites.</p>
-
-      <p>In addition to general upkeep tasks, additional
-	cluster-related items were addressed.  Some of these
-	items include:</p>
-
-      <ul>
-	<li>Added several machines for the Kyua testing framework.</li>
-	<li>Replaced failed hardware hosting various web services.</li>
-	<li>Coordinated with the FreeBSD Security Officer and Ports
-	  Management Teams to implement signed binary packages.</li>
-	<li>Added the <tt>redports.org</tt> machines to the list of
-	  machines managed by the Cluster Administration Team.</li>
-	<li>Began discussion with contacts at Yandex regarding the
-	  addition of a mirror site for binary packages and Subversion
-	  repositories.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team constitutes the project's <q>Board of
-	Directors</q>, responsible for deciding the project's overall
-	goals and direction as well as managing specific areas of the
-	FreeBSD project landscape.</p>
-
-      <p>In the fourth quarter of 2013, the Core Team finally reached
-	its previous goal of launching the official repositories for
-	<tt>pkg(8)</tt>-based binary packages.  The Core Team also
-	unified the commit bit expiration policies for all Project
-	repositories, allowing committers to idle for 18 months before
-	their commit bits are automatically taken into safekeeping.
-	This was then followed by an extension to suspension of cluster
-	accounts for the committers who lost all of their commit bits.
-	This helps to improve the security of the Project server cluster
-	by temporarily disabling inactive accounts.  In addition to the
-	above efforts, Thomas Abthorpe resurrected the <q>Grim
-	Reaper</q> service which helps to enforce the aforementioned
-	policy.</p>
-
-      <p>With the work of John Baldwin, Hiroki Sato, and others, many
-	licenses in the base system source code have been revisited and
-	cleaned up.  Furthermore, the Core Team is hoping that the
-	situation can be improved by introducing periodic automated
-	checks of the license agreements, and by providing developers
-	guidelines on questions of licensing.  John Baldwin and David
-	Chisnall have been guiding the work of the FreeBSD Graphics Team on
-	moving to the newer version of X.Org and related software in the
-	Ports Collection, in coordination with the switch to Newcons on
-	FreeBSD 10.x.</p>
-
-      <p>It was a busy quarter for the src repository as well.  The Core
-	Team was happy to welcome Jordan K. Hubbard (<tt>jkh</tt>) back,
-	who has recently returned to the FreeBSD business, and joined
-	iXsystems as project manager and release engineer of FreeNAS.
-	In addition to this, there were three commit bits offered for new
-	developers, two committers were upgraded, one commit bit was taken
-	for safekeeping, and one src bit was reactivated.</p>
-    <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="http://www.freebsd.org/doc/en/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact: FreeBSD Port Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Ports collection is a package management system for
-	the FreeBSD operating system, providing an easy and consistent way of
-	installing software packages.  The FreeBSD Ports Collection now
-	contains approximately 24,500 ports, while the PR count exceeds
-	1,900.</p>
-
-      <p>The FreeBSD Port Management Team ensures that the FreeBSD ports
-	developer community provides a Ports Collection that is
-	functional, stable, up-to-date, and full-featured.  Its secondary
-	responsibility is to coordinate among the committers and
-	developers who work on it.  As part of these efforts, we added three
-	new committers, took in three commit bits for safe keeping, and
-	reinstated one commit bit in the fourth quarter of 2013.</p>
-
-      <p>Ongoing effort went into testing larger changes, as many as eight a
-	week, including sweeping changes to the tree, moderization of
-	the infrastructure, and basic quality assurance (QA) runs.  Many
-	iterations of tests against <tt>10.0-RELEASE</tt> were run to
-	ensure that the maximum number of packages would be available
-	for the release.</p>
-
-      <p>We now have <tt>pkg(8)</tt> packages for the releases 8.3, 8.4,
-	9.1, 9.2, 10.0 and -CURRENT on <tt>pkg.FreeBSD.org</tt>.  During
-	this same time, further enhancements were put into
-	<tt>pkg(8)</tt>, including secure package signing.</p>
-
-      <p>Commencing November 1, the Port Management Team undertook a
-	<q>portmgr-lurkers</q> pilot project in which ports committers
-	could volunteer to assist the Port Management Team for a
-	four-month duration.  The first two candiates are Mathieu Arnold
-	(<tt>mat</tt>) and Antoine Brodin (<tt>antoine</tt>).</p>
-
-      <p>Ongoing maintenance goes into <tt>redports.org</tt>, including
-	QAT runs, ports and security updates.</p>
-    <h3>Open tasks:</h3><ol><li>As previously noted, many PRs continue to languish; we would
-	like to see some committers dedicate themselves to closing as many
-	as possible!</li></ol><hr /><h2><a name="FreeBSD-Postmaster-Team" href="#FreeBSD-Postmaster-Team" id="FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10" title="http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10" title="">http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10" title="http://lists.freebsd.org/mailman/listinfo/ctm-src-10"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10" title="">http://lists.freebsd.org/mailman/listinfo/ctm-src-10</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast" title="http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast" title="">http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html" title="http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html">OpenPGP Keys section in the Committer's Guide</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html" title="OpenPGP Keys section in the Committer's Guide">http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html</a></td></tr></table><p>
-	Contact: FreeBSD Postmaster Team &lt;<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the fourth quarter of 2013, the FreeBSD Postmaster Team has
-	implemented the following items that may be interest of the
-	general public:</p>
-
-      <ul>
-	<li>Retired the <tt>freebsd-aic7xxx</tt> mailing list.</li>
-
-	<li>Created a <tt>graphics-team</tt> alias, requested by Niclas
-	  Zeising.</li>
-
-	<li>Worked with the FreeBSD Port Management Team to set up
-	  <tt>portmgr-lurkers</tt> so port managers can move addresses
-	  between those two aliases at their discretion.</li>
-
-	<li>Created the lists associated with the new <tt>stable/10</tt>
-	  branch: <tt>svn-src-stable-10</tt>, <tt>ctm-src-10</tt>, and
-	  <tt>ctm-src-10-fast</tt>.</li>
-
-	<li>Redirected the <tt>vbox</tt> alias to the <tt>emulation</tt>
-	  list, requested by Bernhard Fr�hlich.</li>
-
-	<li>Continued a discussion on current and possible future mail
-	  and spam filtering.</li>
-
-	<li>Disbanded <tt>lua</tt> and transferred it to Baptiste
-	  Daroussin, requested by Matthias Andree and Baptiste
-	  Daroussin.</li>
-
-	<li>Modified the list moderators/administrators for
-	  <tt>ports-secteam</tt>, requested by Dag-Erling Sm�rgrav.</li>
-
-	<li>Assisted Warren Block with an update to the "OpenPGP Keys
-	  for FreeBSD" section of the Committer's Guide.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releases/10.0R/schedule.html" title="http://www.FreeBSD.org/releases/10.0R/schedule.html">FreeBSD�10.0-RELEASE schedule</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/10.0R/schedule.html" title="FreeBSD�10.0-RELEASE schedule">http://www.FreeBSD.org/releases/10.0R/schedule.html</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/">FreeBSD�Virtual Machine Images</a></td><td>
-	    URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/" title="FreeBSD�Virtual Machine Images">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD�Development Snapshots</a></td><td>
-	    URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD�Development Snapshots">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is finishing the
-	10.0-RELEASE cycle.  The release cycle changed with two
-	last-minute release candidate builds, each addressing
-	fixes critical to include in the final release.</p>
-
-      <p>The FreeBSD 10.0-RELEASE cycle is expected to be completed by
-	mid-January, approximately eight weeks behind the original
-	schedule.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="CBSD" href="#CBSD" id="CBSD">CBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdstore.ru" title="http://www.bsdstore.ru"></a></td><td>
-	    URL: <a href="http://www.bsdstore.ru" title="">http://www.bsdstore.ru</a></td></tr><tr><td><a href="https://github.com/olevole/cbsd" title="https://github.com/olevole/cbsd"></a></td><td>
-	    URL: <a href="https://github.com/olevole/cbsd" title="">https://github.com/olevole/cbsd</a></td></tr></table><p>
-	Contact:
-	  Oleg
-	  Ginzburg
-	 &lt;<a href="mailto:olevole@olevole.ru">olevole@olevole.ru</a>&gt;
-	</p>
-      <p>CBSD is another FreeBSD jail management solution, aimed at
-	combining various features, such as <tt>racct(8)</tt>,
-	<tt>vnet</tt>, <tt>zfs(8)</tt>, <tt>carp(4)</tt>, and
-	<tt>hastd(8)</tt>, into a single tool.  This provides a more
-	comprehensive way to build application servers using
-	pre-installed jails with a typical set of software, and requires
-	minimal effort to configure.</p>
-    <h3>Open tasks:</h3><ol><li>Proper English translation of the website and the
-	documentation.</li></ol><hr /><h2><a name="Jenkins-Continuous-Integration-for-FreeBSD" href="#Jenkins-Continuous-Integration-for-FreeBSD" id="Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/" title="http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/">Vendor Summit presentation</a></td><td>
-	    URL: <a href="http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/" title="Vendor Summit presentation">http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/</a></td></tr></table><p>
-	Contact:
-	  Craig
-	  Rodrigues
-	 &lt;<a href="mailto:rodrigc@FreeBSD.org">rodrigc@FreeBSD.org</a>&gt;
-	</p>
-      <p>At the November 2013 FreeBSD Vendor Summit, some work was
-	presented that Craig Rodrigues has been doing with Continuous
-	Integration and Testing at iXsystems.  Craig's presentation
-	described how iXsystems is using modern best practices for
-	building and testing the FreeNAS code.  Jenkins is a framework
-	for doing continuous builds and integration that is used by
-	hundreds of companies.  BHyve (BSD Hypvervisor) is the new
-	virtual machine system which will be part of FreeBSD�10.
-	Webdriver is a Python toolkit for testing web applications.  By
-	combining these technologies, iXsystems is developing a modern
-	and sophisticated workflow for testing and improving the quality
-	of FreeNAS.</p>
-
-      <p>Ed Maste from The FreeBSD Foundation was interested in this work,
-	and based on this interest, it is now being ported to FreeBSD.
-	Currently, a machine in the FreeBSD cluster has been allocated for
-	this purpose, where a <tt>bhyve(4)</tt>-based virtual machine
-	was set up and Jenkins was installed.  The remainder is still in
-	progress.</p>
-    <h3>Open tasks:</h3><ol><li>Finish setting up Jenkins.</li><li>Add more builds to Jenkins.</li><li>Integrate testing with Jenkins.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking" href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking" id="GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~mav/disk.pdf" title="http://people.freebsd.org/~mav/disk.pdf">Slides from EuroBSDCon 2013, also describing this project</a></td><td>
-	    URL: <a href="http://people.freebsd.org/~mav/disk.pdf" title="Slides from EuroBSDCon 2013, also describing this project">http://people.freebsd.org/~mav/disk.pdf</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/260387" title="http://svnweb.freebsd.org/changeset/base/260387">CAM improvements in the stable/10 branch</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/260387" title="CAM improvements in the stable/10 branch">http://svnweb.freebsd.org/changeset/base/260387</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/260385" title="http://svnweb.freebsd.org/changeset/base/260385">GEOM improvements in the stable/10 branch</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/260385" title="GEOM improvements in the stable/10 branch">http://svnweb.freebsd.org/changeset/base/260385</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>The CAM and GEOM multi-processor scalability improvement
-	project has completed.  The corresponding code has been committed
-	to FreeBSD <tt>head</tt> and recently merged to the
-	<tt>stable/10</tt> branch; it shall appear in
-	<tt>10.1-RELEASE</tt>.</p>
-
-      <p>As part of this project, <tt>cam(4)</tt> (the ATA/SCSI subsystem)
-	has received more fine-grained locking for better utilization of
-	multi-core systems.  In addition, the locking in <tt>geom(4)</tt>
-	(the block storage subsystem) has also been polished, and a new
-	direct dispatch functionality was implemented to spread the load
-	between multiple threads and processors, and reduce the number
-	of context switches.</p>
-
-      <p>Thanks to these <tt>cam(4)</tt> and <tt>geom(4)</tt> changes,
-	the peak I/O rate has doubled on contemporary hardware, reaching
-	up to 1,000,000�IOPS!</p>
-    <p>This project was sponsored by iXsystems, Inc.</p><h3>Open tasks:</h3><ol><li>Some CAM controller drivers (SIMs) could also be optimized
-	to get more benefits from this project, utilizing the new locking
-	models and direct command completions from multiple interrupt
-	threads.</li></ol><hr /><h2><a name="Intel-802.11n-NIC-(iwn(4))-Work" href="#Intel-802.11n-NIC-(iwn(4))-Work" id="Intel-802.11n-NIC-(iwn(4))-Work">Intel 802.11n NIC (iwn(4)) Work</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@freebsd.org">adrian@freebsd.org</a>&gt;
-	</p>
-      <p>There has been a large amount of work on <tt>iwn(4)</tt> over
-	the last six months:</p>
-
-      <ul>
-	<li>New hardware support: 2xxx, 6xxx, 1xx series hardware.</li>
-
-	<li>Many bugs were fixed, including scanning, association, EAPOL
-	  related fixes.</li>
-
-	<li><tt>iwn(4)</tt> now natively works with 802.11n rates from the
-	  net80211 rate control code, rather than mapping non-11n rates to 11n
-	  rates.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>There are still some scan hangs, due to how net80211 scans a
-	single channel at a time.  This needs to be resolved.</li><li>The transmit, receive, scan and calibration code needs to be
-	refactored out of <tt>if_iwn.c</tt> and into separate source
-	files.</li><li>There still seem to be some issues surrounding 2�GHz
-	versus 5�GHz association attempts leading to firmware
-	assertions, especially on the Intel 4965 NIC.</li></ol><hr /><h2><a name="Intel-GPU-Driver-Update" href="#Intel-GPU-Driver-Update" id="Intel-GPU-Driver-Update">Intel GPU Driver Update</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project will update the Intel graphics chipset driver,
-	<tt>i915kms</tt>, to a recent snapshot of the Linux upstream
-	code.  The update will provide at least 1.5 years of bugfixes
-	from the Intel team, and introduce support for the newest
-	hardware &#8212; in particular Haswell and ValleyView.  The
-	IvyBridge code will also be updated.  The addition of several
-	features which are required to update X.Org and Mesa
-	is also planned.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Native-iSCSI-Stack" href="#Native-iSCSI-Stack" id="Native-iSCSI-Stack">Native iSCSI Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="https://wiki.freebsd.org/Native%20iSCSI%20target"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="">https://wiki.freebsd.org/Native%20iSCSI%20target</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>iSCSI is a popular block storage protocol.  Under this project,
-	a new, fast, and reliable kernel-based iSCSI initiator (client)
-	and target (server) have been implemented.</p>
-
-      <p>During October to December, the work focused on performance and
-	scalability.  The target and the initiator now spread the load
-	over multiple kernel threads, and the locking is optimized to
-	reduce contention.  This makes better use of multiple processor
-	cores.</p>
-
-      <p>Work to finish iSER support is ongoing.  All those
-	optimizations will be gradually merged to <tt>head</tt> in
-	February, and are expected to merged back to <tt>stable/10</tt>
-	and finally arrive in <tt>10.1-RELEASE</tt>.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="New-Automounter" href="#New-Automounter" id="New-Automounter">New Automounter</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Research and prototyping has begun on a new project to
-	implement <tt>autofs(4)</tt> &#8212; an automounter filesystem
-	&#8212; and its userland counterpart, <tt>automountd(8)</tt>.
-	The idea is to provide a very similar user experience to the
-	automounters available on Linux, MacOS X, and Solaris, including
-	using the same map format.  The automounter will also integrate
-	with directory services, such as LDAP.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="UEFI-Boot" href="#UEFI-Boot" id="UEFI-Boot">UEFI Boot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/UEFI" title="https://wiki.freebsd.org/UEFI">UEFI wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/UEFI" title="UEFI wiki page">https://wiki.freebsd.org/UEFI</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/uefi/" title="http://svnweb.freebsd.org/base/projects/uefi/">UEFI project branch</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/projects/uefi/" title="UEFI project branch">http://svnweb.freebsd.org/base/projects/uefi/</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Unified Extensible Firmware Interface (UEFI) provides boot-
-	and run-time services for x86 computers, and is a replacement for
-	the legacy BIOS.  This project will adapt the FreeBSD loader and
-	kernel boot process for compatibility with UEFI firmware, found
-	on contemporary servers, desktops, and laptops.</p>
-
-      <p>In 2013, The FreeBSD Foundation sponsored Benno Rice for a short
-	project to improve the UEFI bootloader.  This resulted in a
-	working proof-of-concept in the UEFI project branch, but it was
-	not ready to be merged to FreeBSD <tt>head</tt>.</p>
-
-      <p>Ed Maste has taken that original work and, with review feedback
-	from Konstantin Belousov, been preparing it for integration into
-	FreeBSD <tt>head</tt>.  Some changes have been merged to
-	<tt>head</tt> already.  The rest will be merged as they are
-	refined.</p>
-
-      <p>Intel provided a motherboard and CPU for the project, which
-	proved invaluable for addressing bugs that did not appear while
-	testing with the QEMU emulator.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Resolve a 32- versus 64-bit <tt>libstand(3)</tt> build issue.</li><li>Merge kernel parsing of EFI memory map metadata.</li><li>Integrate the EFI framebuffer with <tt>vt(9)</tt> (also
-	known as Newcons).</li><li>Connect <tt>efiloader</tt> to the build.</li><li>Document manual installation for dual-boot configurations.</li><li>Integrate UEFI configuration with the FreeBSD installer.</li><li>Support secure boot.</li></ol><hr /><h2><a name="UMA/ZFS-and-RPC/NFS-Performance-Improvements" href="#UMA/ZFS-and-RPC/NFS-Performance-Improvements" id="UMA/ZFS-and-RPC/NFS-Performance-Improvements">UMA/ZFS and RPC/NFS Performance Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905" title="http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905">Discussion of the ZFS/UMA changes</a></td><td>
-	    URL: <a href="http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905" title="Discussion of the ZFS/UMA changes">http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>The performance of ZFS and NFS was suboptimal in FreeBSD, so we
-	have recently investigated some possible improvement paths.  The
-	<tt>uma(9)</tt> memory allocator caching code was improved to
-	adapt better to system memory constraints.  Combined with other
-	virtual memory subsystem improvements done in the previous
-	years, it should be safe to actively use <tt>uma(9)</tt> caches
-	now.  Their use in ZFS for ZIO/ARC may be enabled via the
-	<tt>vfs.zfs.zio.use_uma</tt> <tt>loader(8)</tt> tunable, which
-	is now the default for amd64, where it is recommended.  Use of
-	<tt>uma(9)</tt> caches for LZ4 compression buffers is
-	unconditionally enabled on all architectures as it is has no
-	serious drawbacks.  On systems with many CPUs, these changes
-	doubled the performance in the benchmarks.</p>
-
-      <p>Several areas of the NFS server stack (RPC, FHA, DRC) got a
-	number of fixes and performance optimizations that significantly
-	improve performance and reduce the CPU usage in a number of
-	tests.  Together with the ZFS memory allocator changes mentioned
-	above, it was possible to reach 200K NFS block read IOPS and 55K
-	SPEC NFS IOPS.</p>
-
-      <p>The code was committed to <tt>head</tt>.  The <tt>uma(9)</tt>
-	ZFS commits have been already merged to <tt>stable/10</tt>, and
-	the remainder will be done soon as well.</p>
-    <p>This project was sponsored by iXsystems, Inc.</p><h3>Open tasks:</h3><ol><li>The SPEC NFS test hits lock congestion on several global
-	locks in the file system layer when a quite intensive
-	<tt>READDIRPLUS</tt> NFS request is received.  Fixing this
-	problem could improve performance on large systems even
-	further.</li></ol><hr /><h2><a name="Updated-vt(9)-System-Console" href="#Updated-vt(9)-System-Console" id="Updated-vt(9)-System-Console">Updated vt(9) System Console</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Newcons" title="https://wiki.freebsd.org/Newcons">Project wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Newcons" title="Project wiki page">https://wiki.freebsd.org/Newcons</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p>Colloquially known as Newcons, <tt>vt(9)</tt> is a modern
-	replacement for the existing, quite old, virtual terminal
-	emulator called <tt>syscons(4)</tt>.  Initially motivated by the
-	lack of Unicode support in <tt>syscons(4)</tt>, the project was
-	later expanded to cover the new requirement of supporting Kernel
-	Mode Switching (KMS).</p>
-
-      <p>The project is now approaching completion and is ready for
-	wider testing, as the related code was already merged to FreeBSD
-	<tt>head</tt>.  Hence, <tt>vt(9)</tt> can be tested easily by
-	replacing the following two lines in the kernel config file:</p>
-
-      <pre xml:space="preserve">device sc
-device vga</pre>
-
-      <p>with the following ones:</p>
-
-      <pre xml:space="preserve">device vt
-device vt_vga</pre>
-
-      <p>Major highlights:</p>
-
-      <ul>
-	<li>Unicode support.</li>
-	<li>Double-width character support for CJK characters.</li>
-	<li><tt>xterm(1)</tt>-like terminal emulation.</li>
-	<li>Support for Kernel Mode Setting (KMS) drivers
-	  (<tt>i915kms</tt>, <tt>radeonkms</tt>).</li>
-	<li>Support for different fonts per terminal window.</li>
-	<li>Simplified drivers.</li>
-      </ul>
-
-      <p>Brief status of supported architectures and hardware:</p>
-
-      <ul>
-	<li>amd64 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) &#8212; works.</li>
-	<li>ARM framebuffer &#8212; works.</li>
-	<li>i386 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) &#8212; works.</li>
-	<li>IA64 &#8212; untested.</li>
-	<li>MIPS &#8212; untested.</li>
-	<li>PPC and PPC64 &#8212; works, but without X.Org yet.</li>
-	<li>SPARC &#8212; works on certain hardware (e.g., Ultra 5).</li>
-	<li><tt>vesa(4)</tt> &#8212; in progress.</li>
-	<li>i386/amd64 nVidia driver &#8212; need testing.</li>
-	<li>Xbox framebuffer driver &#8212; need testing.</li>
-      </ul>
-
-      <p>Known Issues:</p>
-
-      <ul>
-	<li>Switching to <tt>vty0</tt> from X.Org on Fatal events will not work.</li>
-	<li>Certain hardware (e.g., Lenovo X220) get a black screen when
-	  i915kms is preloaded.</li>
-	<li>Scrolling can be slow;</li>
-	<li>Screen borders are not cleared when changing fonts.</li>
-	<li><tt>vt(9)</tt> locks up with the <tt>gallant12x22</tt> font in VirtualBox.</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Create sub-directories for <tt>vt(9)</tt> under
-	  <tt>/usr/share/</tt> to store key maps and fonts.</li><li>Implement remaining features supported by
-	  <tt>vidcontrol(1)</tt>.</li><li>Write the <tt>vt(9)</tt> manual page.</li><li>Support keyboard handled directly by device <tt>kbd</tt>
-	  (without <tt>kbdmux(4)</tt>).</li><li>CJK fonts (in progress).</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" id="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openstack.org" title="http://www.openstack.org"></a></td><td>
-	    URL: <a href="http://www.openstack.org" title="">http://www.openstack.org</a></td></tr><tr><td><a href="http://www.opencontrail.org" title="http://www.opencontrail.org"></a></td><td>
-	    URL: <a href="http://www.opencontrail.org" title="">http://www.opencontrail.org</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-devstack" title="https://github.com/Semihalf/openstack-devstack"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/openstack-devstack" title="">https://github.com/Semihalf/openstack-devstack</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-nova" title="https://github.com/Semihalf/openstack-nova"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/openstack-nova" title="">https://github.com/Semihalf/openstack-nova</a></td></tr><tr><td><a href="https://github.com/Semihalf/contrail-vrouter" title="https://github.com/Semihalf/contrail-vrouter"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/contrail-vrouter" title="">https://github.com/Semihalf/contrail-vrouter</a></td></tr><tr><td><a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node"></a></td><td>
-	    URL: <a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="">https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node</a></td></tr></table><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Micha&#322;
-	  Dubiel
-	 &lt;<a href="mailto:md@semihalf.com">md@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafa&#322;
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>OpenStack is a cloud operating system that controls large pools
-	of compute, storage, and networking resources in a data center.
-	OpenContrail is a network virtualization (SDN) solution
-	comprising a network controller, a virtual router, and an
-	analytics engine, which can be integrated with cloud
-	orchestration systems like OpenStack or CloudStack.</p>
-
-      <p>The goal of this work is to enable FreeBSD as a fully supported
-	compute host for OpenStack, using OpenContrail virtualized
-	networking.  The main areas of development are the
-	following:</p>
-
-      <ul>
-	<li>OpenStack compute driver (<tt>nova-compute</tt>) for the
-	  FreeBSD <tt>bhyve(4)</tt> hypervisor.</li>
-
-	<li>OpenContrail vRouter (forwarding-plane kernel module) port
-	  to FreeBSD.</li>
-
-	<li>Integration and performance optimizations.</li>
-      </ul>
-
-      <p>The current state of development features a working demo of
-	OpenStack with compute node components running on a FreeBSD host:</p>
-
-      <ul>
-	<li>The native <tt>bhyve(4)</tt> hypervisor is driven by a
-	  <tt>nova-compute</tt> component for spawning guest instances
-	  and a <tt>nova-network</tt> component for providing simple
-	  networking between those guests.</li>
-
-	<li>The <tt>nova-network</tt> approach (based on local host
-	  bridging) is becoming an obsolete technology in OpenStack and
-	  was used here only for demonstration and proof-of-concept
-	  purposes, without exploring all the possible features.</li>
-
-	<li>The main objective is to move to OpenContrail-based
-	  networking, therefore becoming compliant with the modern
-	  OpenStack networking API ("neutron").</li>
-      </ul>
-    <p>This project was sponsored by Juniper Networks, Inc.</p><h3>Open tasks:</h3><ol><li>Decide how to integrate <tt>bhyve(4)</tt> with
-	<tt>nova-compute</tt>, either natively or via the
-	<tt>libvirt</tt> management layer.</li></ol><hr /><h2><a name="FreeBSD-on-Cubieboard{1,2}" href="#FreeBSD-on-Cubieboard{1,2}" id="FreeBSD-on-Cubieboard{1,2}">FreeBSD on Cubieboard{1,2}</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c" title="https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c">EMAC driver code</a></td><td>
-	    URL: <a href="https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c" title="EMAC driver code">https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c</a></td></tr></table><p>
-	Contact:
-	  Ganbold
-	  Tsagaankhuu
-	 &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>Cubieboard is a single-board computer based on the AllWinner
-	A10 SoC, popular on cheap tablets, phones and media PCs.  The
-	second version enhances the board mainly by replacing the
-	AllWinner A10 SoC with an AllWinner A20 which contains 2 ARM
-	Cortex-A7 MPCore CPUs and 2 Mali-400 GPUs (Mali-400MP2).  In the
-	last few months, work has continued on their FreeBSD port, and
-	some work was done on the EMAC 10/100 Ethernet driver (see
-	link).  The driver is now in a good shape, however the RX side
-	is very slow and there is need to have an external DMA driver that
-	can be used in this case.</p>
-    <hr /><h2><a name="FreeBSD-on-Freescale-i.MX6-processors" href="#FreeBSD-on-Freescale-i.MX6-processors" id="FreeBSD-on-Freescale-i.MX6-processors">FreeBSD on Freescale i.MX6 processors</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html" title="http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html">Announcement of Wanboard support</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html" title="Announcement of Wanboard support">http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html</a></td></tr></table><p>
-	Contact:
-	  Ian
-	  Lepore
-	 &lt;<a href="mailto:ian@freebsd.org">ian@freebsd.org</a>&gt;
-	</p>
-      <p>The i.MX range is a family of Freescale Semiconductor
-	proprietary microprocessors for multimedia applications based on
-	the ARM architecture and focused on low power consumption.  The
-	i.MX6x series is based on the ARM Cortex A9 solo, dual, or quad
-	cores.  Initial support for them has been committed to
-	<tt>head</tt>, and merged to <tt>stable/10</tt>.  All members of
-	the i.MX6 family (Solo, Dual, and Quad core) are supported, but
-	SMP support on the multi-core SoCs has not yet been enabled.</p>
-
-      <p>Initial driver support includes:</p>
-
-      <ul>
-	<li>USB (EHCI)</li>
-	<li>Ethernet (Gigabit)</li>
-	<li>SD Card</li>
-	<li>UART</li>
-      </ul>
-
-      <p>The initial hardware bringup was done on Wandboard hardware,
-	see the announcement on <tt>freebsd-arm</tt> in the links section
-	for more information.</p>
-    <h3>Open tasks:</h3><ol><li>Write drivers for additional on-chip hardware, including
-	I2C, SPI, AHCI, audio, and video.</li><li>Add support to FreeBSD-crochet script to generate Wandboard
-	images</li></ol><hr /><h2><a name="FreeBSD-on-Freescale-Vybrid-VF6xx" href="#FreeBSD-on-Freescale-Vybrid-VF6xx" id="FreeBSD-on-Freescale-Vybrid-VF6xx">FreeBSD on Freescale Vybrid VF6xx</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/258057" title="http://svnweb.freebsd.org/changeset/base/258057"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/258057" title="">http://svnweb.freebsd.org/changeset/base/258057</a></td></tr></table><p>
-	Contact:
-	  Ruslan
-	  Bukin
-	 &lt;<a href="mailto:br@freebsd.org">br@freebsd.org</a>&gt;
-	</p>
-      <p>Basic support for the Freescale Vybrid Family VF6xx
-	heterogeneous ARM Cortex-A5/M4 System-on-Chip (SoC) was added to
-	FreeBSD <tt>head</tt>.  The Vybrid VF6xx family is an
-	implementation of the new modern Cortex-A5-based low-power ARM
-	SoC boards.  Vybrid devices are ideal for applications including
-	simple HMI in appliances and industrial machines, secure control
-	of infrastructure and manufacturing equipment, energy conversion
-	applications such as motor drives and power inverters,
-	ruggedized wired and wireless connectivity, and control of
-	mobile battery-operated systems such as robots and industrial
-	vehicles.</p>
-
-      <p>Supported device drivers:</p>
-
-      <ul>
-	<li>NAND Flash Controller (NFC)</li>
-	<li>USB Enhanced Host Controller Interface (EHCI)</li>
-	<li>General-Purpose Input/Output (GPIO)</li>
-	<li>Universal Asynchronous Receiver/Transmitter (UART)</li>
-      </ul>
-
-      <p>Also supported:</p>
-
-      <ul>
-	<li>Generic Interrupt Controller (GIC)</li>
-	<li>MPCore timer</li>
-	<li><tt>ffec</tt> Ethernet driver</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Add support for a number of different VF5xx- and VF6xx-based
-	development boards.</li><li>Expand device driver support, including framebuffer and
-	other devices.</li></ol><hr /><h2><a name="FreeBSD-on-Newer-ARM-Boards" href="#FreeBSD-on-Newer-ARM-Boards" id="FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock" title="https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock">FreeBSD on Radxa Rock</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock" title="FreeBSD on Radxa Rock">https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/256949" title="http://svnweb.freebsd.org/changeset/base/256949"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/256949" title="">http://svnweb.freebsd.org/changeset/base/256949</a></td></tr><tr><td><a href="https://github.com/tsgan/qualcomm" title="https://github.com/tsgan/qualcomm">Some preliminary sources for Snapdragon board IFC6410</a></td><td>
-	    URL: <a href="https://github.com/tsgan/qualcomm" title="Some preliminary sources for Snapdragon board IFC6410">https://github.com/tsgan/qualcomm</a></td></tr></table><p>
-	Contact:
-	  Ganbold
-	  Tsagaankhuu
-	 &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>Rockchip is a series of SoC (System on Chip) integrated
-	circuits that are mainly for embedded systems applications in
-	mobile entertainment devices such as smartphones, tablets, e-books,
-	set-top boxes, media players, personal video, and MP3 players.
-	Due to their evolution from the MP3/MP4 player market, most
-	Rockchip ICs feature advanced media decoding logic but lack
-	integrated cellular radio basebands.  Initial support for the
-	Rockchip RK3188 (Quad core Cortex A9) SoC is committed to
-	<tt>head</tt>.  Now FreeBSD runs on Radxa Rock and it supports
-	the following peripherals:</p>
-
-      <ul>
-	<li>Existing DWC OTG driver in host mode</li>
-	<li>GPIO</li>
-      </ul>
-
-      <p>Some work was also done on initial support for the Qualcomm
-	Snapdragon S4 SoC, featuring the Krait CPU, which is considered
-	a "platform" for use in smartphones, tablets, and smartbook
-	devices.  Krait has many similarities with the ARM Cortex-A15
-	CPU and is also based on the ARMv7 instruction set.  A minimal
-	console driver was written, and FreeBSD's early boot messages can
-	be now seen on the serial console.  The timer driver works too,
-	and the boot now stops at the mountroot prompt.</p>
-    <hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-on-ec2/" title="http://www.daemonology.net/freebsd-on-ec2/">FreeBSD/EC2 status page</a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-on-ec2/" title="FreeBSD/EC2 status page">http://www.daemonology.net/freebsd-on-ec2/</a></td></tr><tr><td><a href="http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html" title="http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html">Configinit</a></td><td>
-	    URL: <a href="http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html" title="Configinit">http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html</a></td></tr></table><p>
-	Contact:
-	  Colin
-	  Percival
-	 &lt;<a href="mailto:cperciva@freebsd.org">cperciva@freebsd.org</a>&gt;
-	</p>
-      <p>An Amazon Machine Image (AMI) is a special type of virtual
-	appliance that is used to create a virtual machine within the
-	Amazon Elastic Compute Cloud ("EC2").  It serves as the basic
-	unit of deployment for services delivered using EC2.  Such AMIs
-	are available for <tt>8.3-RELEASE</tt> and later FreeBSD releases,
-	and every ALPHA, BETA, and RC of FreeBSD�10.0.  Starting from
-	FreeBSD�<tt>10.0-BETA1</tt>, FreeBSD/EC2 images are running
-	"fully supported" FreeBSD binaries, and starting from
-	FreeBSD�<tt>10.0-RC1</tt>, FreeBSD/EC2 images include a
-	<tt>"configinit"</tt> system for autoconfiguration using EC2
-	user-data.</p>
-
-      <p>Due to limitations of old (<tt>m1</tt>, <tt>m2</tt>,
-	<tt>c1</tt>, <tt>t1</tt>) instance types,
-	<tt>"Windows"</tt>-labelled images are required for those
-	instance types; however all of the recent instances types
-	&#8212; <tt>m3</tt> (general purpose), <tt>c3</tt> (high-CPU),
-	and <tt>i2</tt> (high-I/O) &#8212; support FreeBSD at the
-	<tt>"unix"</tt> pricing rates.</p>
-
-      <p>The maintainer of this platform considers it to be ready for
-	production use.</p>
-    <h3>Open tasks:</h3><ol><li>Hand over the task of building FreeBSD AMIs to the Release
-	Engineering Team.</li><li>Get Amazon to add <tt>"FreeBSD"</tt> to the list of platforms
-	supported by EC2, so that it can stop showing up as <tt>"Other
-	Linux"</tt>.</li></ol><hr /><h2><a name="FreeBSD/Xen" href="#FreeBSD/Xen" id="FreeBSD/Xen">FreeBSD/Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="http://wiki.xen.org/wiki/FreeBSD_PVH">FreeBSD PVH wiki page</a></td><td>
-	    URL: <a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="FreeBSD PVH wiki page">http://wiki.xen.org/wiki/FreeBSD_PVH</a></td></tr></table><p>
-	Contact:
-	  Roger
-	  Pau Monn�
-	 &lt;<a href="mailto:royger@FreeBSD.org">royger@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Justin T.
-	  Gibbs
-	 &lt;<a href="mailto:gibbs@FreeBSD.org">gibbs@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xen is a native (bare-metal) hypervisor providing services that
-	allow multiple computer operating systems to execute on the same
-	computer hardware concurrently.  Xen�4.4 will bring a
-	virtualization mode called PVH &#8212; PV (paravirtualization)
-	in an HVM (fully-virtual) container.  This is essentially a
-	paravirtualized guest using paravirtualized drivers for boot and
-	I/O.  Otherwise it uses hardware virtualization extensions,
-	without the need for emulation.</p>
-
-      <p>After merging the changes to improve Xen PVHVM
-	support, work has shifted on getting PVH DomU support on FreeBSD.
-	Patches have been posted, and after a couple of rounds of review,
-	the series looks almost ready for merging into <tt>head</tt>.
-	Also, very initial patches for FreeBSD PVH Dom0 support has been
-	posted.  So far the posted series only focuses on getting FreeBSD
-	booting as a Dom0 and being able to interact with the
-	hardware.</p>
-    <p>This project was sponsored by Citrix Systems R&amp;D, and Spectra Logic Corporation.</p><h3>Open tasks:</h3><ol><li>Finish reviewing and commit the PVH DomU support.</li><li>Work on PVH Dom0 support.</li></ol><hr /><h2><a name="Intel-IOMMU-(VT-d,-DMAR)-Support" href="#Intel-IOMMU-(VT-d,-DMAR)-Support" id="Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/257251" title="http://svnweb.freebsd.org/changeset/base/257251"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/257251" title="">http://svnweb.freebsd.org/changeset/base/257251</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/259512" title="http://svnweb.freebsd.org/changeset/base/259512"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/259512" title="">http://svnweb.freebsd.org/changeset/base/259512</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>An Input/Output Memory Management Unit (IOMMU) is a Memory
-	Management Unit (MMU) that connects a Direct Memory
-	Access-capable (DMA-capable) I/O bus to main memory; therefore,
-	I/O virtualization is performed by the chipset.  An example
-	IOMMU is the graphics address remapping table (GART) used by AGP
-	and PCI Express graphics cards.  Intel has published a
-	specification for IOMMU technology as Virtualization Technology
-	for Directed I/O, abbreviated VT-d.</p>
-
-      <p>A VT-d driver was committed to <tt>head</tt> and
-	<tt>stable/10</tt>, so <tt>busdma(9)</tt> is now able to utilize
-	VT-d.  The feature is disabled by default, but it may be enabled
-	via the <tt>hw.dmar.enable</tt> <tt>loader(8)</tt> tunable
-	&#8212; see the links for more information.  The immediate plans
-	include increasing the support for this kind of hardware by
-	testing and providing workarounds for specific issues, and
-	by adding features of the next generation of Intel IOMMU.
-	Hopefully, the existing and new consumers of VT-d will start to
-	use the driver soon.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="auditdistd(8)" href="#auditdistd(8)" id="auditdistd(8)">auditdistd(8)</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>auditdistd(8)</tt> daemon is responsible for
-	distributing audit trail files over TCP/IP networks securely and
-	reliably.  Currently, the daemon uses Transport Layer Security
-	(TLS) for communication, but only server-side certificates are
-	verified, based on the certificate's fingerprint.  The ongoing
-	work will make it possible to use client-side certificates and
-	will support more complete public-key infastructure, which
-	includes validation of the entire certificate chain, including
-	revocation checking against Certification Revocation Lists at
-	every level.  From now on, <tt>auditdistd(8)</tt> will support
-	TLSv1.2 and PFS modes only.  In addition, it will be possible to
-	send audit trail files to multiple receivers.</p>
-
-      <p>The work will be completed at the beginning of February
-	2014.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Base-GCC-Updates" href="#Base-GCC-Updates" id="Base-GCC-Updates">Base GCC Updates</a></h2><p>
-	Contact:
-	  Pedro
-	  Giffuni
-	 &lt;<a href="mailto:pfg@FreeBSD.org">pfg@FreeBSD.org</a>&gt;
-	</p>
-      <p>The GCC compiler in the FreeBSD base system is on its way to
-	deprecation and is only used by some Tier-2 platforms at this
-	time.  While Clang is much better in many aspects, we still
-	cannot use all the new features that it
-	brings in the base system until we can drop GCC completely.  As a stop-gap
-	solution, several bug fixes and features from Apple GCC and
-	other sources have been ported to our version of GCC�4.2.1
-	to make it more compatible with Clang.  FreeBSD's GCC has added
-	more warnings and some enhancements like <tt>-Wmost</tt> and
-	<tt>-Wnewline-eof</tt>.  An implementation for Apple's blocks
-	extension is now available, too, and it will be very useful to
-	enhance FreeBSD's support for Apple's Grand Central Dispatch
-	(GCD).</p>
-    <h3>Open tasks:</h3><ol><li>A merge from <tt>head</tt> to <tt>stable/9</tt> is being
-	considered but it disables nested functions by default, so the
-	impact on the Ports Collection needs to be evaluated.</li><li>No further development of GCC�4.2 in the base system is
-	planned.</li></ol><hr /><h2><a name="BSDInstall-ZFSBoot" href="#BSDInstall-ZFSBoot" id="BSDInstall-ZFSBoot">BSDInstall ZFSBoot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall" title="http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall" title="">http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall</a></td></tr><tr><td><a href="https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE" title="https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE">Original Root-on-ZFS instuctions on the FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE" title="Original Root-on-ZFS instuctions on the FreeBSD Wiki">https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE</a></td></tr></table><p>
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>&gt;
-	<br />
-	Contact:
-	  Devin
-	  Teske
-	 &lt;<a href="mailto:dteske@FreeBSD.org">dteske@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>BSDInstall has been the default installation program since
-	FreeBSD�<tt>9.0-RELEASE</tt>.  However, it could not utilize
-	one of the best features of FreeBSD, ZFS.</p>
-
-      <p>The ZFSBoot project started at EuroBSDCon�2013 and reached
-	stable status in December, just in time for
-	FreeBSD�<tt>10.0-RELEASE</tt>.  Currently, ZFSBoot implements
-	root-on-ZFS with 4k partition alignment, optional forced 4k
-	sectors, optional <tt>geli(8)</tt> full disk encryption, and
-	support for boot environments.</p>
-
-      <p>As part of ZFSBoot, BSDInstall itself also received a number of
-	updates, including enhanced debugging, more scriptability, a new
-	keymap selection menu, and a number of other small changes to
-	streamline the installation process.  The new keymap menu allows
-	the user to test the selected keymap before continuing, to
-	ensure it is the desired keymap.  Minor changes were made to the
-	network configuration dialogues to make the identification of
-	wireless interfaces easier.</p>
-
-      <p>A number of additional features are also planned.  The
-	user should be able to create additional datasets and adjust the properties on
-	all datasets in an interactive menu.  There should also be integration with BSDConfig
-	to allow users to install packages and the various other
-	functionality that was previously provided by
-	<tt>sysinstall</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>Interactive dataset editor.</li><li>Dataset property editor.</li><li>Consider using shell <tt>geom(4)</tt> parser.</li><li>BSDConfig integration.</li><li>UFS as a file system option, to allow users to create
-	encrypted UFS installs.</li><li>Optionally make the boot pool UFS or reside on USB
-	device(s).</li><li>Further streamline the installation process.</li></ol><hr /><h2><a name="Capsicum-and-Casper" href="#Capsicum-and-Casper" id="Capsicum-and-Casper">Capsicum and Casper</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html" title="http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html"></a></td><td>
-	    URL: <a href="http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html" title="">http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html</a></td></tr></table><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Capsicum is a lightweight OS capability and sandbox framework
-	implementing a hybrid capability system model.  The Casper
-	daemon enables sandboxed application to use functionality
-	normally unavailable in capability-mode sandboxes.</p>
-
-      <p>The Casper daemon, <tt>libcasper</tt>, <tt>libcapsicum(3)</tt>,
-	<tt>libnv(3)</tt> and Casper services (<tt>system.dns</tt>,
-	<tt>system.grp</tt>, <tt>system.pwd</tt>, <tt>system.random</tt>
-	and <tt>system.sysctl</tt>) have been committed to FreeBSD
-	<tt>head</tt>.  The <tt>tcpdump(8)</tt> utility in <tt>head</tt>
-	now uses the <tt>system.dns</tt> service to do DNS lookups.  The
-	<tt>kdump(1)</tt> utility in <tt>head</tt> now uses the
-	<tt>system.pwd</tt> and <tt>system.grp</tt> services to convert
-	user and group identifiers to user and group names.</p>
-
-      <p>There is ongoing work to sandbox more applications.  If you are
-	interested in helping to make FreeBSD more secure and would like to
-	learn about Capsicum and Casper, do not hesitate to contact
-	Pawel &#8212; he can provide candidate programs that could use
-	sandboxing.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Centralized-Panic-Reporting" href="#Centralized-Panic-Reporting" id="Centralized-Panic-Reporting">Centralized Panic Reporting</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html" title="http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html">Usage instructions</a></td><td>
-	    URL: <a href="http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html" title="Usage instructions">http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html</a></td></tr></table><p>
-	Contact:
-	  Colin
-	  Percival
-	 &lt;<a href="mailto:cperciva@freebsd.org">cperciva@freebsd.org</a>&gt;
-	</p>
-      <p>With the <tt>sysutils/panicmail</tt> port, a mechanism is now
-	in place for automated submission of
-	kernel panic reports to a central location.  It is hoped that
-	this will prove useful, as similar systems have for other
-	operating systems, in identifying common panics so that
-	developers can be alerted and they can be fixed faster.</p>
-
-      <p>In the first two months that this mechanism has been in place,
-	28 kernel panics have been reported.  This is nowhere near enough
-	to be useful, so readers are strongly encouraged to install the
-	<tt>sysutils/panicmail</tt> port and follow the instructions to
-	enable it.</p>
-    <h3>Open tasks:</h3><ol><li>Get more systems set up to automatically submit panic
-	reports!</li></ol><hr /><h2><a name="FreeBSD-Test-Suite" href="#FreeBSD-Test-Suite" id="FreeBSD-Test-Suite">FreeBSD Test Suite</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/TestSuite" title="http://wiki.FreeBSD.org/TestSuite">Project page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/TestSuite" title="Project page">http://wiki.FreeBSD.org/TestSuite</a></td></tr><tr><td><a href="http://kyua1.nyi.FreeBSD.org/" title="http://kyua1.nyi.FreeBSD.org/">Continuous testing infrastructure</a></td><td>
-	    URL: <a href="http://kyua1.nyi.FreeBSD.org/" title="Continuous testing infrastructure">http://kyua1.nyi.FreeBSD.org/</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html" title="http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html">Mailing list announcement</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html" title="Mailing list announcement">http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html</a></td></tr><tr><td><a href="http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html" title="http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html">Blog post</a></td><td>
-	    URL: <a href="http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html" title="Blog post">http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html</a></td></tr></table><p>
-	Contact:
-	  Julio
-	  Merino
-	 &lt;<a href="mailto:jmmv@FreeBSD.org">jmmv@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Test Suite project aims to equip FreeBSD with a
-	comprehensive test suite that is easy to run out of the box and
-	during the development of the system.  The test suite is
-	installed into <tt>/usr/tests/</tt> and the <tt>kyua(1)</tt>
-	command-line tool (<tt>devel/kyua</tt> in the Ports Collection)
-	is used to run them.</p>
-
-      <p>The benefits of having a test suite that is easy to use and
-	continuously run are obvious: regressions can be caught sooner
-	rather than later and the Release Engineering Team can better
-	assess the quality of the tree before deciding to cut a release.
-	Additionally, because we choose to install the tests, we allow
-	any end user to perform sanity checks on new installations of
-	the system on their particular hardware configuration &#8212; a
-	very attractive thing to do when deploying production
-	servers.</p>
-
-      <p>During the last few months, we have added the necessary pieces to
-	the build system to support building and installing test programs of
-	various kinds. To demonstrate the functionality of these, some test
-	programs were added and others were migrated from the old testing tree
-	in <tt>tools/regression/</tt> to the new layout for tests.</p>
-
-      <p>The current test suite should be seen as a proof of concept at this
-	point: it is only composed of a small set of test programs and the goal
-	is to get the infrastructure in place before mass-migrating existing
-	test code and/or importing external tests.</p>
-
-      <p>As part of this work, two new releases of Kyua were published.
-	Of special interest is the addition of a TAP-compliant backend so
-	that existing tests from <tt>tools/regression/</tt> can be
-	plugged into the test suite with minimum effort.</p>
-
-      <p>As of December 31st, the basic continuous testing
-	infrastructure is up and running, see the links section for the
-	home page.  For further information, please see the related
-	announcement and blog post on the subject (also in the links
-	section).</p>
-    <h3>Open tasks:</h3><ol><li>We have three machines for the test cluster.  At the
-	moment, only one of them is in use to continuously test amd64 on
-	both <tt>head</tt> and <tt>stable/10</tt>.  We need to figure
-	out the right level of parallelization to put other machines to
-	use &#8212; but a first easy cut may be to just test different
-	architectures (with the help of QEMU).</li><li>Related to the above, the Kyua reporting engine needs
-	significant tuning to make the reports nice and clean.  Ideally,
-	Kyua should be able to coalesce results from different runs into
-	a single location and generate cohesive reports out of them.
-	Fixing this is a high priority.</li><li>A tutorial on writing tests for FreeBSD has been proposed for
-	AsiaBSDCon�2014.  The outcome of the proposal is still
-	unknown, but stay tuned!</li><li>Port, port, and port more tests to the new test suite.  A
-	test suite is worthless if it does not validate stuff.  Stay tuned
-	for a request for help once we have put all basic pieces in
-	place and have streamlined the migration process.</li></ol><hr /><h2><a name="The-LLDB-Debugger" href="#The-LLDB-Debugger" id="The-LLDB-Debugger">The LLDB Debugger</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/lldb" title="https://wiki.freebsd.org/lldb"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/lldb" title="">https://wiki.freebsd.org/lldb</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLDB is the debugger in the LLVM family of projects.  It
-	supports Mac OS X, Linux, and FreeBSD, with ongoing work to support
-	Windows.</p>
-
-      <p>In the last quarter of 2013, LLDB gained support for live
-	(<tt>ptrace(2)</tt>-based) debugging of multithreaded processes
-	on FreeBSD.  Initial FreeBSD MIPS target support has also been
-	committed, along with a number of endianness fixes in the
-	general LLDB infrastructure.</p>
-
-      <p>The LLDB snapshot in the FreeBSD tree was updated to
-	<tt>r196322</tt>.  Currently disabled by default, it will be
-	enabled for <tt>amd64</tt> after the import of Clang�3.4.
-	In the interim, it may be enabled by adding <tt>WITH_LLDB=</tt>
-	to <tt>src.conf(5)</tt>.</p>
-    <p>This project was sponsored by DARPA/AFRL, SRI International, and University of Cambridge.</p><h3>Open tasks:</h3><ol><li>Update the in-tree snapshot to build after the Clang 3.4
-	import.</li><li>Fix <tt>amd64</tt> watchpoints.</li><li>Test and fix the <tt>i386</tt> port.</li><li>Implement FreeBSD ARM support.</li><li>Add support for kernel debugging (live local and remote
-	debugging, and core files).</li><li>Fix the remaining test suite failures.</li><li>Enable by default on the <tt>amd64</tt> architecture.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Python-Ports" href="#FreeBSD-Python-Ports" id="FreeBSD-Python-Ports">FreeBSD Python Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Python" title="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Python" title="The FreeBSD Python Team page">https://wiki.FreeBSD.org/Python</a></td></tr><tr><td><a href="irc://freebsd-python@irc.freenode.net" title="irc://freebsd-python@irc.freenode.net">IRC channel</a></td><td>
-	    URL: <a href="irc://freebsd-python@irc.freenode.net" title="IRC channel">irc://freebsd-python@irc.freenode.net</a></td></tr></table><p>
-	Contact: FreeBSD Python Team &lt;<a href="mailto:python@FreeBSD.org">python@FreeBSD.org</a>&gt;
-	</p>
-      <p>Python is a widely used general-purpose, high-level programming
-	language.  For many operating systems, Python is a standard
-	component; it ships with FreeBSD as well.  A lot of progress has
-	been made around the FreeBSD Python ports in the last quarter.</p>
-
-      <p>The <tt>devel/py-distribute</tt> port has been replaced by the
-	refreshed <tt>devel/py-setuptools</tt> port, which comes with a
-	lot of features that simplify the methods of installing Python
-	packages.  The change also led us to install everything through
-	Setuptools now, which resembles PyIP a bit and allows us to
-	perform some major cleanup on the distutils installation
-	behaviour.</p>
-
-      <p>The implicit <tt>lang/python</tt> build and run-time dependency
-	was removed from the ports infrastructure.  Every port now
-	depends on a specific Python version or on the
-	<tt>lang/python</tt> metaport.  This prevents compatibility
-	issues for ports that depend on Python�2.x OR
-	Python�3.x exclusively, but use the <tt>python</tt>
-	command, which might point to a version of incompatible user
-	choice.</p>
-
-      <p>The <tt>lang/python27</tt> port was updated to version 2.7.6,
-	and the <tt>lang/python33</tt> port was updated to version
-	3.3.3, and the <tt>lang/pypy</tt> port was updated to version
-	2.2.1.</p>
-
-      <p>We are currently working on the necessary infrastructure quirks
-	to support different Python versions for the same port.  Most of
-	the work has been done and needs to be tested before it can be
-	integrated.</p>
-    <h3>Open tasks:</h3><ol><li>Develop a high-level and lightweight Python Ports Policy.</li><li>Add support for granular dependencies (for example
-	<tt>&gt;=1.0</tt> or <tt>&lt;2.0</tt>).</li><li>Look at what adding <tt>pip</tt> support looks like.</li><li>Convert all <tt>USE_PYDISTUTILS=easy_install</tt> entries to
-	<tt>yes</tt> and remove the use of <tt>easy_install</tt> from
-	the ports infrastructure.</li><li>More tasks can be found on the team's wiki page (see
-	links).</li></ol><hr /><h2><a name="GNOME/FreeBSD" href="#GNOME/FreeBSD" id="GNOME/FreeBSD">GNOME/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome/" title="">http://www.FreeBSD.org/gnome/</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/ports/334661" title="http://svnweb.freebsd.org/changeset/ports/334661">Import of MATE</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/ports/334661" title="Import of MATE">http://svnweb.freebsd.org/changeset/ports/334661</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>GNOME is a desktop environment and graphical user interface
-	that runs on top of a computer operating system.  GNOME is part
-	of the GNU Project and can be used with various Unix-like
-	operating systems, including FreeBSD.</p>
-
-      <p>In this quarter, MATE�1.6 was finally imported into the
-	Ports Collection, thanks to the efforts of Jeremy Messenger.
-	MATE is a desktop environment forked from the now-unmaintained
-	code base of GNOME�2, therefore it is basically a
-	replacement for GNOME�2.  Users wanting
-	to keep GNOME�2 as their desktop are advised to switch to MATE since
-	GNOME�2 will be replaced by GNOME�3 in the near
-	future.  This switch will be announced in advance, so people
-	will have time to move to MATE if they have not already.  The
-	complete MATE-based desktop environment can be installed via the
-	<tt>x11/mate</tt> port, or, for a minimal install,
-	<tt>x11/mate-base</tt>.</p>
-
-      <p>Our home page is quite out of date.  An update for it for
-	GNOME�3.6 is underway.  Part of this update is rewriting
-	and updating the old GNOME porting guide as a chapter of the
-	Porter's Handbook.</p>
-
-      <p>Another major task required for getting a bleeding-edge GNOME
-	to build on FreeBSD mostly out-of-the box is moving to JHbuild with
-	some custom rules.  This is done to find and fix compile issues
-	on other BSDs more quickly.</p>
-    <h3>Open tasks:</h3><ol><li>GNOME�2 ports still need to be sorted out to evaluate
-	which GNOME�2 components will be gone or be replaced with
-	their newer GNOME�3 versions.  This task is currently halted
-	until we can get the documentation into a shape good enough to
-	gather the issues and document the migration, including how
-	to avoid the migration if the upgrade is not preferred.  (This
-	does not mean we do not want to know about issues with
-	upgrading, though).</li><li>Help the X11 Team with Cairo�1.12, since the next
-	version of GNOME�3 (3.12) will need an up-to-date version
-	of Pango and GTK�3.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr><tr><td><a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="http://portscout.freebsd.org/kde@freebsd.org.html">Out-of-date ports</a></td><td>
-	    URL: <a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="Out-of-date ports">http://portscout.freebsd.org/kde@freebsd.org.html</a></td></tr></table><p>
-	Contact: KDE FreeBSD Team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>KDE is an international free software community producing an
-	integrated set of cross-platform applications designed to run on
-	Linux, FreeBSD, Solaris, Microsoft Windows, and OS X systems.  The
-	KDE/FreeBSD Team have continued to improve the experience of KDE
-	software and Qt under FreeBSD.</p>
-
-      <p>During the last quarter, the team has kept most of the KDE and Qt
-	ports up-to-date, working on the following releases:</p>
-
-      <ul>
-	<li>KDE SC (area51): 4.11.2, 4.11.3, 4.11.4</li>
-	<li>Qt: 4.8.5 and 5.2 (area51)</li>
-	<li>PyQt: 4.10.3; SIP: 4.15.2; QScintilla2: 2.8</li>
-	<li>Qt Creator 2.8.0</li>
-	<li>KDevelop: 4.5.2</li>
-	<li>Calligra: 2.7.5</li>
-	<li>CMake: 2.8.12, 2.8.12.1</li>
-      </ul>
-
-      <p>As a result, according to PortScout, our team has 464 ports
-	(down from 473), of which 88.15% are up-to-date (down from
-	98.73%).  iXsystems Inc. continues to provide a machine for
-	the team to build packages and to test updates.  iXsystems Inc.
-	has been providing the KDE/FreeBSD Team with support for quite a
-	long time and we are very grateful for that.</p>
-
-      <p>As usual, the team is always looking for more testers and
-	porters, so please contact us or visit our home page (see links).
-	It would be especially useful to have more helping hands on
-	tasks such as getting rid of the dependency on the defunct HAL
-	project and providing integration with KDE's Bluedevil Bluetooth
-	interface.</p>
-    <h3>Open tasks:</h3><ol><li>Update out-of-date ports, see links for a list.</li><li>Worke on KDE�4.12 and Qt�5.</li><li>Make sure the whole KDE stack (including Qt) builds and
-	works correctly with Clang and <tt>libc++</tt>.</li><li>Remove the dependency on HAL.</li></ol><hr /><h2><a name="Wine/FreeBSD" href="#Wine/FreeBSD" id="Wine/FreeBSD">Wine/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Wine" title="http://wiki.FreeBSD.org/Wine">Wine wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Wine" title="Wine wiki page">http://wiki.FreeBSD.org/Wine</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/i386-Wine" title="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/i386-Wine" title="Wine on amd64 wiki page">http://wiki.FreeBSD.org/i386-Wine</a></td></tr><tr><td><a href="http://www.winehq.org/" title="http://www.winehq.org/">Wine homepage</a></td><td>
-	    URL: <a href="http://www.winehq.org/" title="Wine homepage">http://www.winehq.org/</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeiffer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	</p>
-      <p>Wine is a free and open source software application that aims
-	to allow applications designed for Microsoft Windows to run on
-	Unix-like operating systems, such as FreeBSD.  The Wine/FreeBSD Team
-	have continued to improve the experience of Wine under FreeBSD.</p>
-
-      <p>During the fourth quarter of 2013, the team has kept Wine
-	updated by porting:</p>
-
-      <ul>
-	<li>Stable releases: 1.6 and 1.6.1</li>
-	<li>Development releases: 1.7.4 through 1.7.8</li>
-      </ul>
-
-      <p>The ports have included packages built for <tt>amd64</tt>
-	(available through the Ports Collection).</p>
-
-      <p>The Wine ports have been kept up-to-date with the changes in
-	the Ports Collection, including some improvements:</p>
-
-      <ul>
-	<li>Building with Clang by default (via <tt>USES=compiler:c11</tt>).</li>
-	<li>Conditional X11 support (on by default; allowing for
-	  headless instances of Wine).</li>
-	<li>Staging support and other ports best practices.</li>
-      </ul>
-
-      <p>Support in improving the experience of Wine on FreeBSD is needed.
-	Key areas including fixing regressions, adding copy protection
-	scheme support, and fixing regressions when using Wine under
-	FreeBSD/<tt>amd64</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>Open Tasks and Known Problems (see links for the wiki
-	page).</li><li>FreeBSD/<tt>amd64</tt> integration (see links for the i386-Wine
-	wiki page).</li><li>Porting WoW64 and Wine64.</li></ol><hr /><h2><a name="X.Org-on-FreeBSD" href="#X.Org-on-FreeBSD" id="X.Org-on-FreeBSD">X.Org on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">X11 roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="X11 roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related development repository</a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="Ports-related development repository">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html" title="http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html">CFT for Cairo 1.12 and 8.x survey</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html" title="CFT for Cairo 1.12 and 8.x survey">http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html</a></td></tr></table><p>
-	Contact: FreeBSD X11 Team &lt;<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>The newer graphics stack (<tt>WITH_NEW_XORG</tt>) is now built
-	by default on <tt>head</tt> and is provided as binary packages
-	from the official FreeBSD <tt>pkg(8)</tt> repository for
-	<tt>11-CURRENT</tt>.  The major updates are:</p>
-
-      <ul>
-	<li>X.Org server 1.12.</li>
-	<li>Mesa 9.1.</li>
-	<li>Recent Intel and Radeon X.Org drivers, using exclusively
-	  the KMS kernel drivers available in FreeBSD�9.x (Intel) and FreeBSD�10.x
-	  (Radeon).</li>
-      </ul>
-
-      <p>This change makes X.Org on FreeBSD <tt>head</tt> work
-	out-of-the-box on workstations and laptops based on recent Intel
-	and Radeon GPUs.  FreeBSD�10.x will follow in a few weeks or
-	months.</p>
-
-      <p>Some software has started to require Cairo�1.12, for
-	example GTK+�3.10 and Pango.  Unfortunately, this version
-	of Cairo triggers a bug in the old Intel driver (2.7.1,
-	installed when <tt>WITH_NEW_XORG</tt> is not set), which causes
-	display artifacts.  A "Call For Testers" mail was posted on the
-	<tt>freebsd-x11</tt> mailing-list (see the links above) to
-	gather information about the behavior on other configurations
-	(new Intel driver and non-Intel drivers).  As of this writing,
-	the reports received talk about improvements or, at least, no
-	change noticed.</p>
-
-      <p>To better manage changes such as the <tt>WITH_NEW_XORG</tt> and
-	the Cairo�1.12 changes mentioned above, we asked on the
-	<tt>freebsd-x11</tt> mailing-list if people are using
-	FreeBSD�8.x on their desktop computers and why they do not
-	upgrade to FreeBSD�9.x or 10.x.  So far, we received very few
-	answers to this.</p>
-
-      <p>The Radeon KMS driver in FreeBSD�10.x is now considered
-	stable, especially now that integrated GPUs are properly
-	initialized.  One of the next steps will be to merge this to
-	<tt>stable/9</tt>.</p>
-
-      <p>A "Graphics" wiki article (see links) was created to centralize
-	and coordinate the work being done on both the ports and the
-	kernel.  It contains the following important information:</p>
-
-      <ul>
-	<li>A roadmap of the team.</li>
-	<li>A matrix of supported hardware.</li>
-	<li>Instructions on upgrading to KMS.</li>
-	<li>Project status and results.</li>
-      </ul>
-
-      <p>This starting page then points to project- and topic-specific
-	articles where more detailed information is available.</p>
-    <h3>Open tasks:</h3><ol><li>Report why FreeBSD�8.x is still used on your desktop and
-	why moving to FreeBSD�9.x or 10.x is not an option.</li><li>Report about the Cairo�1.12 update on your system.</li><li>See the "Graphics" wiki page for up-to-date information.</li></ol><hr /><h2><a name="Xfce/FreeBSD" href="#Xfce/FreeBSD" id="Xfce/FreeBSD">Xfce/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce">The FreeBSD Xfce Team's wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xfce" title="The FreeBSD Xfce Team's wiki page">https://wiki.freebsd.org/Xfce</a></td></tr><tr><td><a href="https://people.freebsd.org/~olivierd/xfce-core-unstable.html" title="https://people.freebsd.org/~olivierd/xfce-core-unstable.html">Core</a></td><td>
-	    URL: <a href="https://people.freebsd.org/~olivierd/xfce-core-unstable.html" title="Core">https://people.freebsd.org/~olivierd/xfce-core-unstable.html</a></td></tr><tr><td><a href="https://people.freebsd.org/~olivierd/parole-unstable.html" title="https://people.freebsd.org/~olivierd/parole-unstable.html">Parole</a></td><td>
-	    URL: <a href="https://people.freebsd.org/~olivierd/parole-unstable.html" title="Parole">https://people.freebsd.org/~olivierd/parole-unstable.html</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms, such as FreeBSD.  It aims to be fast and
-	lightweight, while still being visually appealing and easy to
-	use.  The FreeBSD Xfce Team has kept most of the Xfce ports
-	up-to-date, while fixing many issues along the way in this
-	quarter.</p>
-
-      <p>Currently, the following components with the following versions
-	are available:</p>
-
-      <ul>
-	<li>Applications:</li>
-
-	<ul>
-	  <li>Orage (4.10.0)</li>
-	  <li>Midori (0.5.6)</li>
-	  <li>xfce4-terminal (0.6.3)</li>
-	  <li>xfce4-parole (0.5.3, 0.5.4)</li>
-	</ul>
-
-	<li>Panel plugins:</li>
-
-	<ul>
-	  <li>xfce4-whiskermenu-plugin (1.2.0, 1.2.1, 1.2.2, 1.3.0)</li>
-	  <li>xfce4-mailwatch-plugin (1.2.0)</li>
-	  <li>xfce4-wmdock-plugin (0.6.0)</li>
-	</ul>
-      </ul>
-
-      <p>We helped Midori's upstream switch from Waf (Python script)
-	to CMake.  Xfce now also supports Gtk2, Gtk3, and the new
-	WebKitGtk API, available from the 2.x branch, not present in our
-	ports tree at the moment, though.  Most of the ports now use
-	stage directories, with only some plugins left to convert.</p>
-
-      <p>We also removed obsolete ports:</p>
-
-      <ul>
-	<li><tt>x11-themes/lila-xfwm4</tt> (Xfwm4 theme)</li>
-	<li><tt>multimedia/xfce4-media</tt> (multimedia player)</li>
-	<li><tt>net-im/xfce4-messenger-plugin</tt></li>
-      </ul>
-
-      <p>Besides, we followed the development of the Xfce core
-	components and Parole closely.  See the links for documentation
-	on how to upgrade those libraries.</p>
-    <h3>Open tasks:</h3><ol><li>Fix Midori's build on DragonFly, through DPorts.</li><li>Fix build of the Granite framework (it is an extension to
-	Gtk and Midori uses it) on FreeBSD�10 and <tt>head</tt>.
-	Those are mostly LLVM failures.</li><li>Add support for Berkeley DB 5 and higher to Orage.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://www.freebsdfoundation.org/press/2013Dec-newsletter" title="http://www.freebsdfoundation.org/press/2013Dec-newsletter">Semi-annual newsletter</a></td><td>
-	    URL: <a href="http://www.freebsdfoundation.org/press/2013Dec-newsletter" title="Semi-annual newsletter">http://www.freebsdfoundation.org/press/2013Dec-newsletter</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Most of the funding is used to support
-	FreeBSD development projects, conferences and developer summits,
-	purchase equipment to grow and improve the FreeBSD infrastructure,
-	and provide legal support for the Project.</p>
-
-      <p>We held our year-end fundraising campaign.  We are still
-	processing donations and will post the final numbers by
-	mid-January.  We are extremely grateful to all the individuals
-	and organizations that supported us and the Project by making a
-	donation in 2013.  We have already started our fundraising
-	efforts for 2014.</p>
-
-      <p>Some of the highlights from this past quarter include:</p>
-
-      <ul>
-	<li>We sponsored or are sponsoring the following projects:
-
-	  <ul>
-	    <li>Projects completed last quarter: Capsicum, Casper daemon, and
-	      Intel I/O Memory Management Unit driver.</li>
-	    <li>Projects in progress: Native in-kernel iSCSI stack,
-	      network stack layer 2 modernization, UEFI boot, updated
-	      <tt>vt(9)</tt> system console.</li>
-	    <li>Projects started last quarter: Automounter, Intel
-	      graphics driver update.</li>
-	  </ul>
-	</li>
-
-	<li>Continued work on the FreeBSD Journal, our new online FreeBSD magazine,
-	  which debuts on January 27th (see links).</li>
-
-	<li>Sponsored, organized, and ran the Bay Area Developer Summit.</li>
-
-	<li>Sponsored and attended the first ever vBSDCon, which had an
-	  impressive attendance.</li>
-
-	<li>Sponsored and attended the OpenZFS developer summit.</li>
-
-	<li>Represented the foundation at the following conferences: All
-	  Things Open in Raleigh, NC and LISA in Washington, DC.</li>
-
-	<li>Sponsored the FreeBSD 20th Birthday Party, held in San
-	  Francisco.</li>
-
-	<li>Attended the ICANN meeting in Buenos Aires in November and
-	  gave a short presentation on the change from BIND to unbound in
-	  FreeBSD�10.0 during the ccNSO Tech Day.</li>
-
-	<li>Met with a few companies to discuss their FreeBSD use, what
-	  they would like to see supported in FreeBSD, and assist with
-	  collaboration between them and the Project.</li>
-
-	<li>Purchased an 80-core server to reside at Sentex for the
-	  Project to use for stability, scalability, and performance
-	  improvements.  It is a big step forwards for the Foundation in
-	  providing this kind of hardware to the Project's developers.
-	  It will let us test our scaling to 80 simultaneous cores and
-	  1�TB of RAM.  It will also be used to do performance
-	  analysis on large workloads, such as large databases etc.</li>
-
-	<li>Acquired a second rack to use at Sentex.</li>
-
-	<li>We received a commitment from VMware, Inc. for BSD-licensed
-	  drivers.  They also committed to a yearly silver level
-	  donation.</li>
-
-	<li>Signed up as a Google Compute trusted tester for the
-	  Project.</li>
-
-	<li>Funded a project to produce a white paper titled <q>Managed
-	  Services Using FreeBSD at NYI</q>.</li>
-
-	<li>Finally, we published our semi-annual newsletter (see links)
-	  highlighting what we did to support the FreeBSD Project and
-	  Community in 2013.</li>
-      </ul>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2014-01-2014-03.html b/website/content/en/status/report-2014-01-2014-03.html
deleted file mode 100644
index 730c5a3833..0000000000
--- a/website/content/en/status/report-2014-01-2014-03.html
+++ /dev/null
@@ -1,2035 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between January and
-      March 2014.  This is the first of four reports planned for
-      2014.</p><p>The first quarter of 2014 was, again, a hectic and
-      productive time for FreeBSD.  The Ports team released their
-      landmark first quarterly <q>stable</q> branch.  FreeBSD continues
-      to grow on the ARM architecture, now running on an ARM-based
-      ChromeBook. SMP is now possible on multi-core ARM systems.
-      bhyve, the native FreeBSD hypervisor, continues to improve.  An
-      integral test suite is taking shape, and the Jenkins Continuous
-      Integration system has been implemented.  FreeBSD patches to GCC
-      are being <q>forward-ported</q>, and LLDB, the Clang/LLVM
-      debugger is being ported. Desktop use has also seen
-      improvements, with work on Gnome, KDE, Xfce, KMS video drivers,
-      X.org, and <tt>vt</tt>, the new console driver which supports
-      KMS and Unicode.  Linux and Wine binary compatibility layers
-      have been improved.  UEFI booting support has been merged to
-      head. The FreeBSD Foundation continues to assist in moving FreeBSD
-      forward, sponsoring conferences and meetings and numerous
-      development projects.  And these are only some of the things
-      that happened! Read on for even more.</p><p>Thanks to all the reporters for the excellent work!  This
-      report contains 41 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between April and
-      June 2014 is July 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Documentation-Engineering-Team">FreeBSD Documentation Engineering Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ASLR-and-PIE">ASLR and PIE</a></li><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#PCI-SR-IOV-Infrastructure">PCI SR-IOV Infrastructure</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#Updated-vt(4)-System-Console">Updated vt(4) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#bhyve">bhyve</a></li><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#FreeBSD-on-Chromebook">FreeBSD on Chromebook</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#FreeBSD/armv6hf">FreeBSD/armv6hf</a></li><li><a href="#SMP-on-Multi-Core-ARM-Systems">SMP on Multi-Core ARM Systems</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#auditdistd(8)">auditdistd(8)</a></li><li><a href="#External-Toolchain-Improvements">External Toolchain Improvements</a></li><li><a href="#Forward-Port-FreeBSD-GCC">Forward Port FreeBSD GCC</a></li><li><a href="#FreeBSD-Test-Suite">FreeBSD Test Suite</a></li><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium">Chromium</a></li><li><a href="#FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></li><li><a href="#GCC-in-the-Ports-Collection">GCC in the Ports Collection</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#libvirt/bhyve-Support">libvirt/bhyve Support</a></li><li><a href="#OpenAFS-on-FreeBSD">OpenAFS on FreeBSD</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#Using-CentOS-6.5-as-Linux-Base">Using CentOS 6.5 as Linux Base</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#ZFS-Chapter-of-the-Handbook">ZFS Chapter of the Handbook</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-Participating-in-Summer-of-Code-2014">FreeBSD Participating in Summer of Code 2014</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p>
-	Contact: FreeBSD Cluster Administration Team &lt;<a href="mailto:admins@">admins@</a>&gt;
-	</p>
-      <p>The FreeBSD Cluster Administration Team consists of the people
-	responsible for administering the machines that the project
-	relies on for its distributed work and communications to be
-	synchronised.  In this quarter, the team has worked on the
-	following:</p>
-
-      <ul>
-	<li>Assimilated master email configurations into a single
-	  source control repository.</li>
-
-	<li>Moved the FreeBSD web server CGI services to a new location
-	  (sponsored).</li>
-
-	<li>Further enhanced upon our internal monitoring
-	  utilities.</li>
-
-	<li>Added a Russian <tt>pkg(8)</tt> mirror, hosted by
-	  Yandex.</li>
-
-	<li>Moved the FreeBSD�Foundation web services to a new
-	  server (sponsored).</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team constitutes the project's <q>Board of
-	Directors</q>, responsible for deciding the project's overall
-	goals and direction as well as managing specific areas of the
-	FreeBSD project landscape.</p>
-
-      <p>The first quarter of 2014 was very active for the Core Team.
-	John Baldwin and David Chisnall kept coordinating the work required
-	for providing a newer version of X.Org for 9.x and 10.x
-	systems. Now that <tt>vt(4)</tt>, a successor to
-	<tt>syscons(4)</tt> that offers a KMS-enabled console, has
-	been merged to both <tt>stable/9</tt> and <tt>stable/10</tt>,
-	an alternative <tt>pkg(8)</tt> repository is in preparation
-	for wider testing of <tt>vt(4)</tt> and the new X.Org version.
-	In addition to that, John Baldwin published the
-	policy on licenses for new files and files with non-standard
-	licenses.  Thanks to the efforts of Gavin Atkinson, FreeBSD has again
-	made it into the Google Summer of Code program, for the tenth
-	time.  David Chisnall reported that both <tt>libc++</tt> and
-	<tt>libstdc++</tt> can now be built, as all of the
-	standards-compliant implementations of the required numerical
-	functions have been added.</p>
-
-      <p>The Core Team conducted an annual review among the Project
-	teams and hats, where team members had to declare whether they
-	wished to continue their service.  As a result, Florian Smeets
-	replaced David Wolfskill in the lead role of the Postmaster Team, and
-	Glen Barber assumed the head Release Engineer position from
-	Ken Smith.  The Core Team congratulates Florian and Glen,
-	and thanks David and Ken for their long-standing work.</p>
-
-      <p>The Core Team approved chartering the Ports Security Team,
-	which is established to maintain security updates for the
-	ported applications.  In coordination with the Port Management
-	Team, <tt>pkg_tools</tt> was eventually deprecated and tagged
-	with an End-of-Life date, in order to clear the way for
-	<tt>pkg(8)</tt>.  The Port Management Team also requested a
-	way to make it possible to track userland ABI and KBI changes
-	reliably for the Ports Collection.  Ideally this can be
-	achieved by increasing the value of <tt>__FreeBSD_version</tt>
-	on each fix, therefore the corresponding discussion concluded
-	in freezing the ABI note tag for releases in order to keep the
-	size of binary patches for <tt>freebsd-update(8)</tt> low.
-	A related Errata Notice is about to be published soon.</p>
-
-      <p>Only a single commit bit was taken for safekeeping.
-	We did not have new committers to the <tt>src/</tt> repository
-	in this quarter.</p>
-    <hr /><h2><a name="FreeBSD-Documentation-Engineering-Team" href="#FreeBSD-Documentation-Engineering-Team" id="FreeBSD-Documentation-Engineering-Team">FreeBSD Documentation Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-doc/2014-February/023265.html" title="http://lists.freebsd.org/pipermail/freebsd-doc/2014-February/023265.html">Announcement of Warren Block's addition</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-doc/2014-February/023265.html" title="Announcement of Warren Block's addition">http://lists.freebsd.org/pipermail/freebsd-doc/2014-February/023265.html</a></td></tr></table><p>
-	Contact: FreeBSD Documentation Engineering Team &lt;<a href="mailto:doceng@FreeBSD.org">doceng@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Documentation Engineering Team is responsible for
-	defining and following up on the documentation goals for the
-	committers in the Documentation project.  The team is pleased to
-	announce a new member &#8212; Warren Block.  In early March, the
-	FreeBSD Documentation Engineering Team members assumed
-	responsibility for the FreeBSD Webmaster Team.</p>
-    <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Thomas
-	  Abthorpe
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:culot@FreeBSD.org">culot@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Port Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The role of the FreeBSD Port Management Team is to ensure that the
-	FreeBSD Ports Developer community provides a ports collection that is
-	functional, stable, up-to-date and full-featured.  It is also to
-	coordinate among the committers and developers who work on
-	it.</p>
-
-      <p>The ports tree slowly approaches the 25,000 ports threshold,
-	while the PR count exceeds 1,800.  In the first quarter, we
-	added four new committers, took in three commit bits for safe
-	keeping, and reinstated one commit bit.</p>
-
-      <p>In January, the longest serving port manager, Joe Marcus Clarke,
-	stepped down from his active duties on the team.  At a similar
-	time Ion-Mihai Tetcu also stepped down from his duties.
-	Fortunately, as a result of the first <tt>portmgr-lurkers</tt>
-	intake, we were able to replace them with Mathieu Arnold and
-	Antoine Brodin.</p>
-
-      <p>Commencing March 1, the second intake of
-	<tt>portmgr-lurkers</tt> started active duty on <tt>portmgr</tt>
-	for a four month duration.  The next two candidates are
-	Alexey Dokuchaev and Frederic Culot.</p>
-
-      <p>This quarter also saw the release of the first quarterly
-	branch, namely <tt>2014Q1</tt>.  This branch is intended to
-	provide a stable and high-quality ports tree, with patches
-	related to security fixes as well as packaging and runtime fixes
-	being backported from <tt>head</tt>.</p>
-
-      <p>Ongoing maintenance goes into redports.org, including QAT runs
-	and ports and security updates.</p>
-    <h3>Open tasks:</h3><ol><li>As previously noted, many PRs continue to languish.  We
-	would like to see committers dedicate themselves to closing as
-	many as possible.</li></ol><hr /><h2><a name="FreeBSD-Postmaster-Team" href="#FreeBSD-Postmaster-Team" id="FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></h2><p>
-	Contact: FreeBSD Postmaster Team  &lt;<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Postmaster Team is responsible for mail being
-	correctly delivered to the committers' email addresses, ensuring
-	that the mailing lists work, and should take measures against
-	possible disruptions of project mail services, such as having
-	troll-, spam- and virus-filters.</p>
-
-      <p>In the first quarter of 2014, the team has implemented these
-	items that may be interest of the general public:</p>
-
-      <ul>
-	<li>Continued a discussion on current and possible future mail
-	  and spam filtering.</li>
-
-	<li>Discovered more of what needs to be done for a new year
-	  (with respect to email archives), did what we could, and
-	  recorded the steps for next time.</li>
-
-	<li>Added Kubilay Kocak to <tt>donations</tt>, requested by
-	  Pietro Cerutti.</li>
-
-	<li>Added Warren Block to <tt>doceng</tt>.</li>
-
-	<li>Made sure <tt>portmgr</tt> receives bounces for
-	  <tt>pkg-fallout</tt> messages.</li>
-
-	<li>Created a <tt>jenkins-admin</tt> mail alias.</li>
-
-	<li>Enabled Mailman password reminder emails again.</li>
-
-	<li>Discovered that all Mailman cron jobs were disabled in
-	  November during upgrades.  Enabled those again.  This caused
-	  problems like digests not being sent.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releases/9.3R/schedule.html" title="http://www.FreeBSD.org/releases/9.3R/schedule.html">FreeBSD�9.3-RELEASE schedule</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/9.3R/schedule.html" title="FreeBSD�9.3-RELEASE schedule">http://www.FreeBSD.org/releases/9.3R/schedule.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/releases/9.3R/todo.html" title="http://www.FreeBSD.org/releases/9.3R/todo.html">FreeBSD�9.3-RELEASE todo list</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/releases/9.3R/todo.html" title="FreeBSD�9.3-RELEASE todo list">http://www.FreeBSD.org/releases/9.3R/todo.html</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD�development snapshots</a></td><td>
-	    URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD�development snapshots">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>In early January, the team became aware of several
-	last-minute showstopper issues in FreeBSD�10.0, which led
-	to an extension in the final release builds.
-	FreeBSD�10.0-RELEASE was announced on January 20, two months
-	behind the original schedule.</p>
-
-      <p>The schedule for the FreeBSD�9.3-RELEASE cycle has been
-	written and posted to the website, and the release cycle will
-	begin early May.</p>
-
-      <p>There is ongoing work to integrate support for embedded
-	architectures as part of the release build process.  At this
-	time, support exists for a number of ARM kernels, in
-	particular the Raspberry Pi, BeagleBone, and WandBoard.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Jenkins-Continuous-Integration-for-FreeBSD" href="#Jenkins-Continuous-Integration-for-FreeBSD" id="Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://jenkins.FreeBSD.org" title="https://jenkins.FreeBSD.org">Jenkins CI server in FreeBSD cluster</a></td><td>
-	    URL: <a href="https://jenkins.FreeBSD.org" title="Jenkins CI server in FreeBSD cluster">https://jenkins.FreeBSD.org</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins#Jenkins_for_FreeBSD_status" title="https://wiki.freebsd.org/Jenkins#Jenkins_for_FreeBSD_status">Jenkins on FreeBSD project status</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins#Jenkins_for_FreeBSD_status" title="Jenkins on FreeBSD project status">https://wiki.freebsd.org/Jenkins#Jenkins_for_FreeBSD_status</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins#Presentations_and_Working_Groups" title="https://wiki.freebsd.org/Jenkins#Presentations_and_Working_Groups">Video and slides of March 13, 2014 presentation at Bay Area FreeBSD User Group (BAFUG)</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins#Presentations_and_Working_Groups" title="Video and slides of March 13, 2014 presentation at Bay Area FreeBSD User Group (BAFUG)">https://wiki.freebsd.org/Jenkins#Presentations_and_Working_Groups</a></td></tr><tr><td><a href="http://empt1e.blogspot.ru/2014/03/using-jenkins-libvirt-slave-plugin-with.html" title="http://empt1e.blogspot.ru/2014/03/using-jenkins-libvirt-slave-plugin-with.html">Jenkins, libvirt, and bhyve</a></td><td>
-	    URL: <a href="http://empt1e.blogspot.ru/2014/03/using-jenkins-libvirt-slave-plugin-with.html" title="Jenkins, libvirt, and bhyve">http://empt1e.blogspot.ru/2014/03/using-jenkins-libvirt-slave-plugin-with.html</a></td></tr><tr><td><a href="http://jenkins-ci.org" title="http://jenkins-ci.org">Jenkins Continuous Integration</a></td><td>
-	    URL: <a href="http://jenkins-ci.org" title="Jenkins Continuous Integration">http://jenkins-ci.org</a></td></tr><tr><td><a href="http://www.ansible.com" title="http://www.ansible.com">Ansible</a></td><td>
-	    URL: <a href="http://www.ansible.com" title="Ansible">http://www.ansible.com</a></td></tr></table><p>
-	Contact:
-	  Craig
-	  Rodrigues
-	 &lt;<a href="mailto:rodrigc@FreeBSD.org">rodrigc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jenkins Administrators &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Testing &lt;<a href="mailto:freebsd-testing@FreeBSD.org">freebsd-testing@FreeBSD.org</a>&gt;
-	</p>
-      <p>Jenkins is a framework used by many companies and open
-	source projects for Continuous Integration (CI).  CI allows
-	developers to commit code to a Source Code Management (SCM)
-	system such as Subversion, and then have automated programs
-	check out, build, and test the code.  Jenkins is implemented
-	in the Java language.</p>
-
-      <p>Ed Maste reviewed some CI work that Craig Rodrigues had done
-	for the FreeNAS project with Jenkins, and encouraged him to
-	set up something similar for the FreeBSD Project.  With the help
-	of the FreeBSD Cluster Administration Team, he set up a FreeBSD
-	machine running two bhyve virtual machines,
-	<tt>jenkins-9.FreeBSD.org</tt> and
-	<tt>jenkins-10.FreeBSD.org</tt>.  He set up software builds of
-	<tt>head</tt> and several <tt>stable</tt> branches on these
-	machines.  The status of these builds is visible on a web
-	interface accessible at <tt>jenkins.FreeBSD.org</tt>.  When
-	any of the builds fail, emails are sent to
-	<tt>freebsd-current</tt> or <tt>freebsd-stable</tt>.  Emails
-	are also sent directly to the list of people who recently
-	committed code to Subversion since the last successful
-	build.</p>
-
-      <p>As part of the Jenkins setup, Craig Rodrigues encountered
-	problems with running Java on FreeBSD�9.2 and
-	FreeBSD�10.0.  Both problems stemmed from changes to the
-	FreeBSD Virtual Memory (VM) subsystem.  On FreeBSD 9.2-RELEASE,
-	running Jenkins under Java would cause the kernel to panic.
-	This was a known problem, and fixed in 9.2.-RELEASE-p3.  On
-	FreeBSD 10.0-RELEASE, Java processes would randomly crash.
-	Disabling the <tt>vm.pmap.pcid_enabled</tt> <tt>sysctl(3)</tt>
-	variable seemed to fix the problem.  In <tt>kern/187238</tt>,
-	Henrik Gulbrandsen submitted fixes to the FreeBSD VM to address
-	this problem.  Konstantin Belousov committed the fixes to <tt>head</tt>,
-	where they are being tested now.</p>
-
-      <p>During the setup of the bhyve VMs which run Jenkins
-	processes, Craig Rodrigues wrote scripts to start bhyve VMs from
-	the <tt>rc.d</tt> bootup scripts, which were then published at
-	GitHub.</p>
-
-      <p>On February 19, 2014, Craig Rodrigues notified the FreeBSD
-	developers that Jenkins was running in the FreeBSD cluster, and
-	that they could look at the web interface to see the status of
-	builds.</p>
-
-      <p>On March 13, 2014, Craig Rodrigues gave a presentation of the
-	Jenkins work at the Bay Area FreeBSD User Group (BAFUG) in
-	Mountain View, California, USA.  Video of the presentation was
-	recorded and put online by iXsystems.</p>
-
-      <p>Craig Rodrigues assembled a team of volunteers,
-	<tt>jenkins-admin</tt>, to help maintain
-	<tt>jenkins.FreeBSD.org</tt> and expand the use of Jenkins CI
-	used in the FreeBSD cluster.  <tt>jenkins-admin</tt> consists of
-	the following people working in the following areas:</p>
-
-      <ul>
-	<li>R. Tyler Croy is both a FreeBSD developer and a Jenkins
-	  developer.  He will be working on fixing bugs in Jenkins
-	  specific to FreeBSD.  He is first looking at fixing the
-	  libpam4j library which is used by Jenkins to interface with
-	  the PAM system for user authentication.  The released
-	  version of libpam4j does not currently work on FreeBSD.</li>
-
-	<li>Li-Wen Hsu maintains the <tt>devel/jenkins</tt> port.  He
-	  set up a Jenkins build which runs the scan-build static
-	  analyzer which is part of LLVM.</li>
-
-	<li>Steven Kreuzer has experience administering Jenkins systems.
-	  He set up several builds on <tt>jenkins.FreeBSD.org</tt>,
-	  including a Jenkins build of the FreeBSD documentation.  He is
-	  looking into using Ansible for automatic provisioning of VMs
-	  running Jenkins in the FreeBSD cluster.</li>
-
-	<li>Craig Rodrigues will be running a Continuous Testing working
-	  group at the FreeBSD Devsummit in Ottawa on May 15, 2014.  He
-	  will also give a Jenkins presentation on May 17, 2014.  He
-	  is interested in working with Julio Merino to integrate Jenkins
-	  and Kyua.  They have exchanged some emails about this on the
-	  <tt>freebsd-testing</tt> list.</li>
-
-	<li>Steve Wills maintains the <tt>devel/jenkins-lts</tt> port.
-	  He has implemented several builds at
-	  <tt>jenkins.FreeBSD.org</tt> which detect commits to the
-	  FreeBSD ports repository, and then build the ports tree using
-	  Poudri�re.</li>
-      </ul>
-
-      <p>At the end of March, Roman Bogorodskiy reported to
-	<tt>jenkins-admin</tt> that he has successfully run the
-	Jenkins libvirt plugin with his libvirt modifications to
-	integrate with bhyve.  He provided a link to a blog posting
-	where he described his experience.</p>
-    <p>This project was sponsored by iXsystems, Inc.</p><h3>Open tasks:</h3><ol><li>Obtain certificates for LDAP and web servers, to replace
-	self-signed certificates.</li><li>Set up more Jenkins builds of the FreeBSD base repository on
-	different branches and with different configurations.</li><li>Set up more Jenkins builds of the FreeBSD ports repository on
-	different FreeBSD versions.</li><li>Integrate with Kyua, so that Jenkins can run Kyua tests
-	and report the results directly in the native Jenkins web UI
-	where test results are reported.</li><li>Write scripts which can take a Jenkins build of FreeBSD, and
-	boot the results in a bhyve VM or on real hardware.</li><li>Fix libpam4j on FreeBSD.</li><li>Continuous Testing working group at Devsummit on May 15,
-	2014</li><li>Jenkins presentation at BSDCan on May 17, 2014</li></ol><hr /><h2><a name="ZFSguru" href="#ZFSguru" id="ZFSguru">ZFSguru</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zfsguru.com/" title="http://zfsguru.com/">Home page</a></td><td>
-	    URL: <a href="http://zfsguru.com/" title="Home page">http://zfsguru.com/</a></td></tr></table><p>
-	Contact:
-	  Jason
-	  Edwards
-	 &lt;<a href="mailto:sub.mesa@gmail.com">sub.mesa@gmail.com</a>&gt;
-	</p>
-      <p>ZFSguru is a multifunctional server appliance with a strong
-	emphasis on storage.  It wants to deliver all the great BSD
-	and ZFS technology to a wider audience, while at the same time
-	pleasing more advanced users as well with unique features and
-	customization.</p>
-
-      <p>A <q>vanilla</q> ZFSguru installation comes with only Samba
-	and a web-interface setup, but can be extended easily by
-	installing addons called <q>services</q> to add functionality
-	as desired. This prevents users from running programs they do
-	not need and do not want.  Advanced users can still use
-	ZFSguru as they would a normal FreeBSD installation with a 100%
-	ZFS setup (<q>Root-on-ZFS</q>).  ZFSguru does not strip away
-	anything, and uses a <tt>GENERIC</tt>-like kernel with only
-	some additional settings added like InfiniBand networking,
-	Device Polling and AltQ.  This means you can use a ZFSguru
-	installation as you would use a FreeBSD installation.</p>
-
-      <p>In the first month of 2014, ZFSguru has released beta9
-	version of the web interface.  This release brings vastly
-	improved support for Samba and NFS configuration.  In
-	particular, it adds a convenient drag-and-drop interface for
-	Samba permissions.  This allows novice users to configure
-	access to shares in various configurations.  It allows both
-	control and usability, with no manual being necessary in order
-	to operate it.  This is the ZFSguru style.</p>
-
-      <p>New system versions have been released, based on FreeBSD 9.2,
-	10.0, and <tt>head</tt>.  The experimental <tt>head</tt>
-	version has <tt>vt(4)</tt> and X.org 7.12.4 and the
-	Intel/Radeon KMS graphics drivers.  That is, the latest and
-	greatest of FreeBSD graphics development.  The ZFSguru project
-	plans to release <tt>stable/10</tt> builds in the near future
-	which also have the MFCed patches for <tt>vt(4)</tt>, the
-	KMS-enabled system console with Unicode support.  Please see
-	the <tt>vt(4)</tt> entry for more information.</p>
-
-      <p>Support for ZFS version 5000 is now universal across 9.2,
-	10.0 and <tt>head</tt> builds.  LZ4 compression is the key
-	feature for ZFS version 5000.  Otherwise users are advised to
-	keep their pool versions as is, to be as compatible as you can
-	with as many ZFS platforms as possible.  Only upgrade the pool
-	as you desire its functionality, forfeiting the compatibility
-	with older storage platforms.</p>
-    <h3>Open tasks:</h3><ol><li>ZFSguru beta10 will increase the compatibility of newly added
-	Samba functionality with non-Gecko browsers.  It will also fix
-	some minor bugs as well as speed up some pages by having a
-	redesigned remote database system called GuruDB.</li><li>ZFSguru beta11 will add the one major feature still
-	missing in ZFSguru: the Migration Manager.  This allows users
-	to maintain a file with all the configuration of their ZFSguru
-	installation. It can be used like a firmware &#8212; restoring
-	the machine to the exact state and configuration of the
-	snapshot configuration. It allows users to maintain a backup
-	of their ZFSguru configuration and allows upgrading to a newer
-	ZFSguru system version without any hassle.</li><li>Automated system builds should bring more system image
-	releases.</li><li>New website with new forum and new login system.</li><li>Developer website with GitLab setup, allowing bug reports,
-	code contributions, wiki, and wall messages.  Note that GitLab
-	has also been provided as a ZFSguru service, for those
-	interested in trying GitLab.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="ASLR-and-PIE" href="#ASLR-and-PIE" id="ASLR-and-PIE">ASLR and PIE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://0xfeedface.org/blog/lattera/2014-04-03/awesome-freebsd-aslr-progress" title="http://0xfeedface.org/blog/lattera/2014-04-03/awesome-freebsd-aslr-progress">Blog post with latest status update</a></td><td>
-	    URL: <a href="http://0xfeedface.org/blog/lattera/2014-04-03/awesome-freebsd-aslr-progress" title="Blog post with latest status update">http://0xfeedface.org/blog/lattera/2014-04-03/awesome-freebsd-aslr-progress</a></td></tr><tr><td><a href="https://github.com/lattera/freebsd/tree/soldierx/lattera/aslr" title="https://github.com/lattera/freebsd/tree/soldierx/lattera/aslr">Shawn's ASLR branch</a></td><td>
-	    URL: <a href="https://github.com/lattera/freebsd/tree/soldierx/lattera/aslr" title="Shawn's ASLR branch">https://github.com/lattera/freebsd/tree/soldierx/lattera/aslr</a></td></tr><tr><td><a href="https://github.com/opntr/opBSD/tree/op/stable/10-aslr" title="https://github.com/opntr/opBSD/tree/op/stable/10-aslr">Oliv�r's ASLR branch</a></td><td>
-	    URL: <a href="https://github.com/opntr/opBSD/tree/op/stable/10-aslr" title="Oliv�r's ASLR branch">https://github.com/opntr/opBSD/tree/op/stable/10-aslr</a></td></tr></table><p>
-	Contact:
-	  Shawn
-	  Webb
-	 &lt;<a href="mailto:lattera@gmail.com">lattera@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Oliv�r
-	  Pint�r
-	 &lt;<a href="mailto:oliver.pntr@gmail.com">oliver.pntr@gmail.com</a>&gt;
-	</p>
-      <p>Address space layout randomization (ASLR) is a computer
-	security technique involved in protection from buffer overflow
-	attacks.  In order to prevent an attacker from reliably
-	jumping to a particular exploited function in memory, ASLR
-	involves randomly arranging the positions of key data areas of
-	a program, including the base of the executable and the
-	positions of the stack, heap, and libraries, in a process'
-	address space.</p>
-
-      <p>We have added ASLR support to all architectures.  As the
-	primary developers behind this feature have the most access to
-	<tt>amd64</tt>, the focus of development is on the
-	<tt>amd64</tt> architecture.  Other architectures, such as
-	ARM, have known bugs with our current ASLR implementation and
-	we are working hard to fix them.  We added support for
-	Position-Independent Executables (PIEs) in a number of
-	applications in base.</p>
-    <h3>Open tasks:</h3><ol><li>Shawn has access to a Raspberry Pi (RPI).  PIE is 90%
-	broken.  Debug and fix major issues on the RPI.  The existing
-	NX stack protections are not obeyed on RPI.  Properly
-	implemented ASLR requires a NX stack.</li><li>Shawn will be receiving a <tt>sparc64</tt> box on April 6,
-	2014.  He will test ASLR on <tt>sparc64</tt>, identifying and
-	fixing any bugs that pop up.</li><li>Oliv�r has identified one or more bugs with the
-	Linuxulator.  He will be looking into that and fixing
-	those.</li><li>Shawn will be cleaning up code and adding support for PIE to
-	more applications in base.  He will also add PIE support to the
-	ports framework for general consumption.</li><li>Shawn will be giving a presentation regarding ASLR at
-	BSDCan�2014.</li></ol><hr /><h2><a name="Intel-GPU-Driver-Update" href="#Intel-GPU-Driver-Update" id="Intel-GPU-Driver-Update">Intel GPU Driver Update</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project to update the Intel graphics chipset driver
-	(<tt>i915kms</tt>) to a recent snapshot of the Linux upstream
-	code continues.  Progress was delayed by external
-	circumstances, but it is hoped to reach a useful milestone in
-	the near future.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Native-iSCSI-Stack" href="#Native-iSCSI-Stack" id="Native-iSCSI-Stack">Native iSCSI Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="https://wiki.freebsd.org/Native%20iSCSI%20target"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="">https://wiki.freebsd.org/Native%20iSCSI%20target</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new FreeBSD in-kernel iSCSI stack was functionally complete
-	in FreeBSD 10.0-RELEASE, but ongoing enhancements and bug fixes
-	are being committed to FreeBSD <tt>head</tt>, with a plan to
-	merge them back to <tt>stable/10</tt> in time for FreeBSD
-	10.1-RELEASE.</p>
-
-      <p>Many issues have been resolved, including very slow operation
-	with data digests enabled, bugs in persistent reservations
-	which impacted Hyper-V Failover Cluster, and a negotiation
-	problem affecting Dell Equallogic users.</p>
-
-      <p>There have also been numerous enhancements, such as support
-	for redirections, which are necessary for some High
-	Availability setups, and the ability to modify session
-	parameters in the iscsictl utility.  Previously it was
-	necessary to remove the session and add it again.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="New-Automounter" href="#New-Automounter" id="New-Automounter">New Automounter</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The automount project is nearing the functional prototype
-	stage, and a call for testing is expected in the next month.
-	The userspace portion consists of the <tt>automountd(8)</tt>
-	daemon, which is designed to be fully compatible with its
-	counterparts in OS X, Solaris, and Linux, and which is nearly
-	complete.  Work on the kernel component continues.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="PCI-SR-IOV-Infrastructure" href="#PCI-SR-IOV-Infrastructure" id="PCI-SR-IOV-Infrastructure">PCI SR-IOV Infrastructure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/rysto32/freebsd/tree/iov_ixgbe" title="https://github.com/rysto32/freebsd/tree/iov_ixgbe">Work in progress on GitHub</a></td><td>
-	    URL: <a href="https://github.com/rysto32/freebsd/tree/iov_ixgbe" title="Work in progress on GitHub">https://github.com/rysto32/freebsd/tree/iov_ixgbe</a></td></tr></table><p>
-	Contact:
-	  Ryan
-	  Stone
-	 &lt;<a href="mailto:rstone@FreeBSD.org">rstone@FreeBSD.org</a>&gt;
-	</p>
-      <p>PCI Single Root I/O Virtualization (SR-IOV) is an optional
-	part of the PCIe standard that provides hardware acceleration
-	for the virtualization of PCIe devices.  When SR-IOV is in
-	use, a function in a PCI device (known as a Physical Function,
-	or PF) will present multiple Virtual PCI Functions (VF) on the
-	PCI bus. These VFs are fully independent PCI devices that have
-	access to the resources of the PF.  For example, on a network
-	interface card, VFs could transmit and receive packets
-	independent of the PF.</p>
-
-      <p>The most obvious use case for SR-IOV is virtualization.  A
-	hypervisor like bhyve could instantiate a VF for every VM and
-	use PCI passthrough to assign the VFs to the VMs.  This would
-	allow multiple VMs to share access to the PCI device without
-	having to do any expensive communication with the hypervisor,
-	greatly increasing performance of performing I/O from a
-	VM.</p>
-
-      <p>There are two parts to this project.  The first is
-	implementing an API in the PCI subsystem for creating VFs and
-	configuring standard PCI features like BARs.  The second part
-	is updating individual drivers for PCI devices that support
-	SR-IOV to configure their VFs.  For example, a network
-	interface driver will typically have to assign a MAC address
-	to a VF and configure the interface to route packets destined
-	for that MAC address to the VF.</p>
-
-      <p>At this point only SR-IOV support for the <tt>ixgbe(4)</tt>
-	driver is planned.  The PCI subsystem API is designed to be
-	generic and should support SR-IOV on any device, but fairly
-	extensive driver work is necessary to support SR-IOV, which is
-	currently not planned due to lack of time and hardware.</p>
-
-      <p>At present, <tt>ixgbe(4)</tt> is able to create VFs and the
-	<tt>ixgbevf</tt> driver is able to pass traffic.  There is
-	still a fair amount of work to support VLAN tags, multicast
-	addresses, and other features on the VFs.  Also, the VF
-	configuration needs to be better integrated with the PF
-	initialization path to ensure that resets of the PF do not
-	interrupt operation of the VFs.</p>
-    <p>This project was sponsored by Sandvine, Inc.</p><hr /><h2><a name="SDIO-Driver" href="#SDIO-Driver" id="SDIO-Driver">SDIO Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SDIO" title="https://wiki.freebsd.org/SDIO">SDIO project page on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SDIO" title="SDIO project page on FreeBSD wiki">https://wiki.freebsd.org/SDIO</a></td></tr><tr><td><a href="https://github.com/kibab/freebsd/tree/mmccam" title="https://github.com/kibab/freebsd/tree/mmccam">Source code</a></td><td>
-	    URL: <a href="https://github.com/kibab/freebsd/tree/mmccam" title="Source code">https://github.com/kibab/freebsd/tree/mmccam</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>SDIO is an interface designed as an extension of the existing
-	SD card standard, allowing connection of different peripherals
-	to the host with the standard SD controller.  Peripherals
-	currently sold on the general market include WLAN/BT modules,
-	cameras, fingerprint readers, and barcode scanners.  The FreeBSD
-	driver is implemented as an extension to the existing MMC bus,
-	adding a lot of new SDIO-specific bus methods.  A prototype of
-	the driver for the Marvell SDIO WLAN/BT (Avastar 88W8787)
-	module is also being developed, using the existing Linux
-	driver as a reference.</p>
-
-      <p>SDIO card detection and initialization already work; most
-	needed bus methods are implemented and tested.</p>
-
-      <p>The WiFi driver is able to load firmware onto the card and
-	initialize it.  Migration of the MMC stack to the new locking
-	model is necessary in order to work with SDIO cards
-	effectively. The FreeBSD CAM implementation is believed to be a
-	good choice. There is ongoing work to implement an MMC
-	transport for CAM.</p>
-    <h3>Open tasks:</h3><ol><li>SDIO stack: finish CAM migration.  The XPT layer is almost
-	ready.  What is missing is a SIM module, for which a modified
-	version of the SDHCI controller driver will be used, and a
-	peripheral module, where porting the <tt>mmcsd(4)</tt> driver
-	is required.</li><li>Marvell SDIO WiFi: connect it to the FreeBSD network stack,
-	write the code to implement required functions, such as
-	sending and receiving data, network scanning and so on.</li></ol><hr /><h2><a name="UEFI-Boot" href="#UEFI-Boot" id="UEFI-Boot">UEFI Boot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/UEFI" title="https://wiki.freebsd.org/UEFI">Project page on the wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/UEFI" title="Project page on the wiki">https://wiki.freebsd.org/UEFI</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Unified Extensible Firmware Interface (UEFI) provides
-	boot- and run-time services for x86 computers, and is a
-	replacement for the legacy BIOS.  This project will adapt the
-	FreeBSD loader and kernel boot process for compatibility with
-	UEFI firmware, found on contemporary servers, desktops, and
-	laptops.</p>
-
-      <p>Starting with Rui Paulo's <tt>i386</tt> EFI loader,
-	Benno Rice developed a working proof-of-concept <tt>amd64</tt>
-	loader in 2013 under sponsorship from the FreeBSD Foundation.
-	After refinement, that work has now been merged from the
-	<tt>projects/uefi</tt> Subversion branch into FreeBSD
-	<tt>head</tt>.  The project includes the infrastructure to
-	build a UEFI-enabled loader, and the kernel-side changes to
-	parse metadata provided by the loader.</p>
-
-      <p>A number of integration tasks remain, with a plan to have
-	UEFI installation and boot support merged to
-	<tt>stable/10</tt> in time for FreeBSD 10.1-RELEASE.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Document manual installation, including dual-boot
-	configurations.</li><li>Implement chain-loading from UFS/ZFS file systems.</li><li>Integrate UEFI configuration with the FreeBSD
-	installer.</li><li>Support secure boot.</li></ol><hr /><h2><a name="Updated-vt(4)-System-Console" href="#Updated-vt(4)-System-Console" id="Updated-vt(4)-System-Console">Updated vt(4) System Console</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Newcons" title="https://wiki.freebsd.org/Newcons">Project wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Newcons" title="Project wiki page">https://wiki.freebsd.org/Newcons</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>vt(4)</tt> is a modern replacement for the existing,
-	quite old, virtual terminal emulator called
-	<tt>syscons(4)</tt>. Initially motivated by the lack of
-	Unicode support and infrastructural issues in
-	<tt>syscons(4)</tt>, the project was later expanded to cover
-	the new requirement to support Kernel Mode Setting (KMS).</p>
-
-      <p>The project is now in <tt>head</tt>, <tt>stable/10</tt> and
-	<tt>stable/9</tt> branches.  Hence, <tt>vt(4)</tt> can be
-	tested by using the <tt>VT</tt> kernel configuration
-	(<tt>i386</tt> and <tt>amd64</tt>) or by replacing two lines
-	in the <tt>GENERIC</tt> kernel configuration file:</p>
-
-      <pre xml:space="preserve">device sc
-device vga</pre>
-
-      <p>with the following ones:</p>
-
-      <pre xml:space="preserve">device vt
-device vt_vga</pre>
-
-      <p>Or, to use for UEFI testing, add the following lines
-	instead:</p>
-
-      <pre xml:space="preserve">device vt
-device vt_efifb</pre>
-
-      <p>Major highlights:</p>
-
-      <ul>
-	<li>Unicode support.</li>
-	<li>Double-width character support for CJK characters.</li>
-	<li><tt>xterm(1)</tt>-like terminal emulation.</li>
-	<li>Support for Kernel Mode Setting (KMS) drivers
-	  (<tt>i915kms</tt>, <tt>radeonkms</tt>).</li>
-	<li>Support for different fonts per terminal window.</li>
-	<li>Simplified drivers.</li>
-      </ul>
-
-      <p>Brief status of supported architectures and hardware:</p>
-
-      <ul>
-	<li>amd64 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) &#8212;
-	  works.</li>
-	<li>ARM framebuffer &#8212; works.</li>
-	<li>i386 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) &#8212;
-	  works.</li>
-	<li>IA64 &#8212; untested.</li>
-	<li>MIPS &#8212; untested.</li>
-	<li>PPC and PPC64 &#8212; work, but without X.Org yet.</li>
-	<li>SPARC &#8212; works on certain hardware (e.g., Ultra
-	  5).</li>
-	<li><tt>vesa(4)</tt> &#8212; in progress.</li>
-	<li>i386/amd64 nVidia driver &#8212; not supported.  VGA
-	  should be used (VESA planned).</li>
-	<li>Xbox framebuffer driver &#8212; will be deleted as
-	  unused.</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Create sub-directories for <tt>vt(4)</tt> under
-	  <tt>/usr/share/</tt> to store key maps and fonts.</li><li>Implement the remaining features supported by
-	  <tt>vidcontrol(1)</tt>.</li><li>Write the <tt>vt(4)</tt> manual page.  (This is in
-	  progress.)</li><li>Support direct handling of keyboard by the <tt>kbd</tt>
-	  device (without <tt>kbdmux(4)</tt>).</li><li>CJK fonts.  (This is in progress).</li><li>Address performance issues on some architectures.</li><li>Switch to <tt>vt(4)</tt> by default.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="bhyve" href="#bhyve" id="bhyve">bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bhyve.org" title="http://www.bhyve.org">bhyve FAQ and Talks</a></td><td>
-	    URL: <a href="http://www.bhyve.org" title="bhyve FAQ and Talks">http://www.bhyve.org</a></td></tr><tr><td><a href="http://www.youtube.com/watch?v=lTOiSyu0-MA" title="http://www.youtube.com/watch?v=lTOiSyu0-MA">Talk: bhyve Past, Present, Future</a></td><td>
-	    URL: <a href="http://www.youtube.com/watch?v=lTOiSyu0-MA" title="Talk: bhyve Past, Present, Future">http://www.youtube.com/watch?v=lTOiSyu0-MA</a></td></tr></table><p>
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Neel
-	  Natu
-	 &lt;<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Tycho
-	  Nightingale
-	 &lt;<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>&gt;
-	</p>
-      <p>bhyve is a Type-1 hypervisor that runs on the FreeBSD platform.
-	It currently only runs FreeBSD (9.x or later) and Linux guests;
-	current development efforts aim at widening support for other
-	x86 64-bit operating systems.  After a great deal of work by
-	all involved, bhyve was shipped as part of FreeBSD 10.0-RELEASE.
-	Increased interest in bhyve and the first usable versions have
-	provided great feedback and many bug reports.</p>
-
-      <p>A number of important improvements have been made to bhyve
-	this quarter:</p>
-
-      <ul>
-	<li>Optionally ignore accesses to unimplemented MSRs</li>
-
-	<li>Support soft power-off via the ACPI S5 state for bhyve
-	  guests</li>
-
-	<li>Graceful shutdown via ACPI on SIGTERM</li>
-
-	<li>Fix an issue with virtio-blk devices on Linux guests with
-	  more than 4GB of RAM</li>
-
-	<li>Increase the block-layer backend maximum requests to match
-	  AHCI command queue depth</li>
-
-	<li>Add SMBIOS support</li>
-
-	<li>Improve support for nmdm, opening the tty
-	  non-blocking</li>
-
-	<li>Add HPET device emulation</li>
-
-	<li>Implement the <q>Virtual Interrupt Delivery</q> and
-	  <q>Posted Interrupt Processing</q> VT-x features on newer
-	  Intel CPUs</li>
-
-	<li>Add support for booting FreeBSD/i386 guests</li>
-
-	<li>Add virtualized XSAVE support for features like AVX</li>
-
-	<li>Add Support for booting from ZFS with bhyveload</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Improve documentation.</li><li>Write Handbook chapter for bhyve.</li><li>Merge fixes and features back to
-	<tt>stable/10</tt>.</li><li>Support for booting with UEFI instead of userspace
-	loaders.</li><li>CSM BIOS boot support for FreeBSD (which has no UEFI support
-	currently).</li><li>Add support for virtio-scsi.</li><li>Improve virtio-net, add offload features, support multiple
-	queues.</li><li>Implement Intel 82580 and e1000 NIC emulation.</li><li>Netmap support.</li><li>Flexible networking backend: wanproxy, vhost-net.</li><li>Improve resource accounting.</li><li>Move to a single process model, instead of bhyveload and
-	bhyve.</li><li>Support running bhyve as non-root.</li><li>Add filters for popular VM file formats (VMDK, VHD,
-	QCOW2).</li><li>Implement an abstraction layer for video (no X11 or SDL in
-	base system).</li><li>Support for VNC as a video output.</li><li>Implement USB and Sound.</li><li>Suspend/resume support.</li><li>Live Migration.</li><li>Nested VT-x support (bhyve in bhyve).</li><li>Support for other architectures (ARM, MIPS, PPC).</li></ol><hr /><h2><a name="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" id="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openstack.org" title="http://www.openstack.org"></a></td><td>
-	    URL: <a href="http://www.openstack.org" title="">http://www.openstack.org</a></td></tr><tr><td><a href="http://www.opencontrail.org" title="http://www.opencontrail.org"></a></td><td>
-	    URL: <a href="http://www.opencontrail.org" title="">http://www.opencontrail.org</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-devstack" title="https://github.com/Semihalf/openstack-devstack"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/openstack-devstack" title="">https://github.com/Semihalf/openstack-devstack</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-nova" title="https://github.com/Semihalf/openstack-nova"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/openstack-nova" title="">https://github.com/Semihalf/openstack-nova</a></td></tr><tr><td><a href="https://github.com/Semihalf/contrail-vrouter" title="https://github.com/Semihalf/contrail-vrouter"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/contrail-vrouter" title="">https://github.com/Semihalf/contrail-vrouter</a></td></tr><tr><td><a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node"></a></td><td>
-	    URL: <a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="">https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node</a></td></tr></table><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Micha&#322;
-	  Dubiel
-	 &lt;<a href="mailto:md@semihalf.com">md@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Dominik
-	  Ermel
-	 &lt;<a href="mailto:der@semihalf.com">der@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafa&#322;
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>OpenStack is a cloud operating system that controls large
-	pools of compute, storage, and networking resources in a data
-	center.  OpenContrail is a network virtualization (SDN)
-	solution comprising a network controller, virtual router, and
-	analytics engine, which can be integrated with cloud
-	orchestration systems like OpenStack or CloudStack.</p>
-
-      <p>The goal of this work is to make FreeBSD a fully supported
-	compute host for OpenStack using OpenContrail virtualized
-	networking.  The main areas of development are:</p>
-
-      <ul>
-	<li>Libvirt hypervisor driver for bhyve.</li>
-
-	<li>Support for bhyve (via the libvirt compute driver) and the
-	  FreeBSD platform in overall in <tt>nova-compute</tt>.</li>
-
-	<li>Port OpenContrail vRouter (forwarding plane kernel module)
-	  to FreeBSD.</li>
-
-	<li>Port OpenContrail Agent (network controller node) to
-	  FreeBSD.</li>
-
-	<li>Integration, performance optimization.</li>
-      </ul>
-
-      <p>The current state of development allows for a working demo
-	of OpenStack with compute node component running on a FreeBSD
-	host:</p>
-
-      <ul>
-	<li>The native bhyve hypervisor is driven by a
-	  <tt>nova-compute</tt> component for spawning guest instances
-	  using libvirt and a <tt>nova-network</tt> component for
-	  providing simple networking using bridges between guest
-	  VMs.</li>
-
-	<li>QEMU might also be used instead of bhyve this way.</li>
-
-	<li>The main goal on the networking side is to use the
-	  OpenContrail solution, compliant with the modern OpenStack
-	  networking API ("neutron").</li>
-      </ul>
-
-      <p>Also, an initial port of the OpenContrail vRouter kernel
-	module has been completed.  It successfully handles all
-	networking on the host.</p>
-    <p>This project was sponsored by Juniper Networks.</p><hr /><h2><a name="FreeBSD-on-Chromebook" href="#FreeBSD-on-Chromebook" id="FreeBSD-on-Chromebook">FreeBSD on Chromebook</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/FreeBSD/arm/Chromebook" title="https://wiki.freebsd.org/FreeBSD/arm/Chromebook">Manual</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/FreeBSD/arm/Chromebook" title="Manual">https://wiki.freebsd.org/FreeBSD/arm/Chromebook</a></td></tr></table><p>
-	Contact:
-	  Ruslan
-	  Bukin
-	 &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	</p>
-      <p>One model of Chromebook is an ARMv7 Cortex-A15 personal
-	computer powered by a Samsung Exynos 5 Dual System-on-Chip.  As of
-	the current status of this project, such laptops can be booted
-	with FreeBSD from USB flash &#8212; it works stably (including SMP)
-	and it can build third-party applications.  The display and
-	keyboard work.</p>
-
-      <p>Thanks to Peter Grehan for providing hardware.</p>
-    <h3>Open tasks:</h3><ol><li>Implement keyboard polling mode.</li><li>Add support for the upcoming second generation of
-	Chromebook.</li><li>Write SD, SATA drivers.</li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/arm64/" title="http://svnweb.freebsd.org/base/projects/arm64/">Project branch in the Subversion repository</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/projects/arm64/" title="Project branch in the Subversion repository">http://svnweb.freebsd.org/base/projects/arm64/</a></td></tr><tr><td><a href="https://github.com/zxombie/aarch64-freebsd-sandbox" title="https://github.com/zxombie/aarch64-freebsd-sandbox">GitHub repository</a></td><td>
-	    URL: <a href="https://github.com/zxombie/aarch64-freebsd-sandbox" title="GitHub repository">https://github.com/zxombie/aarch64-freebsd-sandbox</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Arm64 is the name of the in-progress port of FreeBSD to the ARMv8
-	CPU when it is in AArch64 mode.  Until recently, all ARM CPU
-	designs were 32-bit only.  With the introduction of the ARMv8
-	architecture, ARM has added a new 64-bit mode.  This new mode
-	has been named AArch64.</p>
-
-      <p>Progress has been good on getting FreeBSD to build and run on
-	the ARM Foundation model.  FreeBSD is able to be built for this
-	architecture, however, it requires a number of external tools
-	including <tt>objdump(1)</tt> and <tt>ld(1)</tt>.  These tools
-	are provided by an external copy of binutils until
-	replacements can be written.</p>
-
-      <p>FreeBSD will run the early boot on the Foundation model.  The
-	loader has been ported to the AArch64 UEFI environment and can
-	load and run the kernel.  The kernel is able to create the
-	initial page tables to be able to run from virtual memory.  It
-	can then execute C code to parse the memory map provided by
-	the loader.  This is as far as the kernel currently boots.</p>
-
-      <p>This work is now happening in the FreeBSD Subversion repository
-	in a project branch, see the links.</p>
-    <h3>Open tasks:</h3><ol><li>Implement an initial <tt>pmap(9)</tt> layer.</li><li>Write the missing machine-dependent code.</li><li>Test on real hardware.</li></ol><hr /><h2><a name="FreeBSD/armv6hf" href="#FreeBSD/armv6hf" id="FreeBSD/armv6hf">FreeBSD/armv6hf</a></h2><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD has been updated to allow it to use the VFP variant of
-	the ARM EABI ABI.  The VFP unit is the ARM hardware to perform
-	floating-point operations.  This changes the ABI to improve
-	the performance of code that uses floating-point operations.
-	By default, FreeBSD already uses the ARM EABI on all releases
-	from 10.0.</p>
-
-      <p>This is important for FreeBSD/arm users running code with
-	floating-point operations on ARMv6 or ARMv7 SoC systems.  It
-	removes the need for the slow software floating-point support
-	in <tt>libc</tt>.  This is mostly compatible with the existing
-	ABI, with the exception of how floating-point values are
-	passed into functions.  Because no floating-point values are
-	passed to the kernel, the <tt>armv6</tt> and <tt>armv6hf</tt>
-	kernels will work with either userland.</p>
-
-      <p>As part of this change, some support functions have been
-	updated to use the VFP unit when available.  The existing
-	<tt>armv6</tt> target architecture will be kept for cases
-	where the SoC lacks a VFP unit, or existing binaries that are
-	incompatible with the new ABI.</p>
-    <h3>Open tasks:</h3><ol><li>Testing.</li><li>More testing.</li></ol><hr /><h2><a name="SMP-on-Multi-Core-ARM-Systems" href="#SMP-on-Multi-Core-ARM-Systems" id="SMP-on-Multi-Core-ARM-Systems">SMP on Multi-Core ARM Systems</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-arm/2014-April/007886.html" title="http://lists.freebsd.org/pipermail/freebsd-arm/2014-April/007886.html">Announcement</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-arm/2014-April/007886.html" title="Announcement">http://lists.freebsd.org/pipermail/freebsd-arm/2014-April/007886.html</a></td></tr></table><p>
-	Contact:
-	  Ian
-	  Lepore
-	 &lt;<a href="mailto:ian@FreeBSD.org">ian@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Olivier
-	  Houchard
-	 &lt;<a href="mailto:cognet@ci0.org">cognet@ci0.org</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Macek
-	 &lt;<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>&gt;
-	</p>
-      <p>FreeBSD now supports Symmetrical MultiProcessing (SMP) on a
-	variety of ARM multi-core systems.  The effort to bring SMP to
-	ARM has been underway for quite some time, but a major push by
-	the FreeBSD ARM developer community over the past two months has
-	resulted in robust production-ready SMP support.</p>
-
-      <p>An ever-growing number of ARM-based development boards and
-	small low-power computer systems are available with multi-core
-	processors.  FreeBSD is now able to make good use of all that
-	computing power, making such systems more attractive to both
-	end users and vendors looking to create products based on
-	similar designs.</p>
-
-      <p>As of r264138 in FreeBSD <tt>head</tt>, SMP is now enabled by
-	default in the configuration files for all currently-supported
-	systems that have multi-core processors.  This includes
-	systems based on the following processor families:</p>
-
-      <ul>
-	<li>Allwinner A20</li>
-	<li>Freescale i.MX6</li>
-	<li>Marvell Armada XP</li>
-	<li>Samsung Exynos 5</li>
-	<li>Texas Instruments OMAP4</li>
-      </ul>
-
-      <p>We plan to merge this work to <tt>stable/10</tt> in time for
-	10.1-RELEASE.</p>
-    <p>This project was sponsored by Microsemi, Inc., and Semihalf sp.j.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="auditdistd(8)" href="#auditdistd(8)" id="auditdistd(8)">auditdistd(8)</a></h2><p>
-	Contact:
-	  Pawel Jakub
-	  Dawidek
-	 &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>auditdistd(8)</tt> daemon is responsible for
-	distributing audit trail files over TCP/IP networks securely
-	and reliably.</p>
-
-      <p>The daemon now supports client-side certificates, which can
-	be used to automatically configure the receiver side &#8212;
-	the directory name for received trail files is determined
-	based on the <tt>commonName</tt> field in client's
-	certificate.  There is no need any more to add every sender to
-	the receiver's configuration file.</p>
-
-      <p>The sender's functionality was extended to allow sending
-	audit trail files to multiple receivers.</p>
-
-      <p>Complete Public Key Infrastructure (PKI) support is now
-	implemented, including full certificate chain verification,
-	Certificate Revocation Lists (CRL) verification at every level
-	and support for multiple Certificate Authority (CA)
-	certificates.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="External-Toolchain-Improvements" href="#External-Toolchain-Improvements" id="External-Toolchain-Improvements">External Toolchain Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/ExternalToolchain" title="https://wiki.freebsd.org/ExternalToolchain">Brooks Davis' XCC work</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/ExternalToolchain" title="Brooks Davis' XCC work">https://wiki.freebsd.org/ExternalToolchain</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Building on the work that Brooks Davis did to enable external
-	Clang toolchains, this project hopes to generalize that to
-	GCC, as well as support different versions of these compilers
-	simultaneously for the FreeBSD base system and the kernel.  We
-	also hope get to the point that a port can be cross-compiled
-	entirely from scratch with no initial binary artifacts.</p>
-    <h3>Open tasks:</h3><ol><li>Setup Subversion project repository.</li><li>Fix issues with differences of interpretation of the
-	<tt>-B</tt> argument between GCC and Clang.</li><li>Support building the entire tree based only on xdev-built
-	compilers.</li><li>Support building the entire tree based only on ports-built
-	GCC compilers.</li><li>Support full bootstrapping of FreeBSD to new
-	platforms.</li></ol><hr /><h2><a name="Forward-Port-FreeBSD-GCC" href="#Forward-Port-FreeBSD-GCC" id="Forward-Port-FreeBSD-GCC">Forward Port FreeBSD GCC</a></h2><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Not all of the FreeBSD changes to GCC have been reflected
-	upstream.  A large amount of the platform support as well as a
-	couple of minor improvements like the kernel formatting
-	checker need to be forward ported (and if possible, moved
-	upstream into GCC).</p>
-
-      <p>We will be targeting the FreeBSD ports tree <tt>lang/gcc*</tt>
-	ports for these efforts to (optionally) include them in these
-	builds.  Some variation from normal builds may be required due
-	to bootstrapping issues when combined with the external
-	toolchain enhancements project.</p>
-    <hr /><h2><a name="FreeBSD-Test-Suite" href="#FreeBSD-Test-Suite" id="FreeBSD-Test-Suite">FreeBSD Test Suite</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/TestSuite" title="http://wiki.FreeBSD.org/TestSuite">Project page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/TestSuite" title="Project page">http://wiki.FreeBSD.org/TestSuite</a></td></tr><tr><td><a href="http://kyua1.nyi.FreeBSD.org/" title="http://kyua1.nyi.FreeBSD.org/">Testing cluster</a></td><td>
-	    URL: <a href="http://kyua1.nyi.FreeBSD.org/" title="Testing cluster">http://kyua1.nyi.FreeBSD.org/</a></td></tr><tr><td><a href="http://julipedia.meroh.net/2014/01/freebsd-test-suite-goals-and-planning.html" title="http://julipedia.meroh.net/2014/01/freebsd-test-suite-goals-and-planning.html">Roadmap for the project</a></td><td>
-	    URL: <a href="http://julipedia.meroh.net/2014/01/freebsd-test-suite-goals-and-planning.html" title="Roadmap for the project">http://julipedia.meroh.net/2014/01/freebsd-test-suite-goals-and-planning.html</a></td></tr><tr><td><a href="https://drive.google.com/a/meroh.net/#folders/0B08g-X1kPkSYNmlEdTB5RjlFbkk" title="https://drive.google.com/a/meroh.net/#folders/0B08g-X1kPkSYNmlEdTB5RjlFbkk">AsiaBSDCon 2014 tutorial materials</a></td><td>
-	    URL: <a href="https://drive.google.com/a/meroh.net/#folders/0B08g-X1kPkSYNmlEdTB5RjlFbkk" title="AsiaBSDCon 2014 tutorial materials">https://drive.google.com/a/meroh.net/#folders/0B08g-X1kPkSYNmlEdTB5RjlFbkk</a></td></tr></table><p>
-	Contact:
-	  Julio
-	  Merino
-	 &lt;<a href="mailto:jmmv@FreeBSD.org">jmmv@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Test Suite project aims to equip FreeBSD with a
-	comprehensive collection of tests that are easy to run out of
-	the box and during the development of the system.  The test
-	suite is installed into <tt>/usr/tests/</tt> and the
-	<tt>kyua(1)</tt> command-line tool (<tt>devel/kyua</tt> in the
-	Ports Collection) is used to run them.  See the project page
-	for more details.</p>
-
-      <p>Since the last status report, we have been hard at work
-	polishing the framework in many different areas.  The
-	highlights are:</p>
-
-      <ul>
-	<li>A roadmap for the project has been prepared and published,
-	  see links.</li>
-
-	<li>Many tests have been added to the test suite thanks to the
-	  work of various developers and, in particular, a good bunch
-	  of old tests from <tt>src/tools/regression/</tt> have been
-	  incorporated into the new test suite.  As of this writing,
-	  there are 509 test cases continuously running.</li>
-
-	<li>The testing infrastructure in the <tt>stable/10</tt>
-	  branch has been synced to <tt>head</tt>.  It should now be
-	  possible to seamlessly MFC changes to the stable branch
-	  along with their tests, if any.</li>
-
-	<li>The testing cluster, which only issued <tt>amd64</tt>
-	  builds, has been extended to perform <tt>i386</tt> builds as
-	  well.  Additionally, a canary machine has been put in place
-	  so that changes to the cluster configuration can be properly
-	  validated before deployment.</li>
-
-	<li>A tutorial on Kyua and the FreeBSD Test Suite was given at
-	  AsiaBSDCon 2014.  The tutorial materials are available for
-	  public consumption, please consult the links.</li>
-
-	<li>Both Kyua's and ATF's upstream sites have been moved to
-	  GitHub, mostly due to the discontinuation of file downloads
-	  in Google Code.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Enable the build of the test suite by default.</li><li>Add alerting for failed or missing test runs from the
-	testing cluster.</li><li>Add bhyve support to the testing cluster for faster
-	turnaround times.</li><li>Simplify and improve Kyua HTML reports.  In particular,
-	reports will be coalesced into single HTML files for easier
-	management and will include more useful details for debugging.
-	Such details are the revision at which the system was built, the
-	date and duration of the whole run, or the list of installed
-	packages, to mention a few examples.</li><li>Add JUnit XML output to Kyua for better integration with
-	Jenkins.  This work is actively ongoing and should be ready
-	for prime time at BSDCan�2014.</li></ol><hr /><h2><a name="LLDB-Debugger-Port" href="#LLDB-Debugger-Port" id="LLDB-Debugger-Port">LLDB Debugger Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/lldb" title="https://wiki.FreeBSD.org/lldb"></a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/lldb" title="">https://wiki.FreeBSD.org/lldb</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLDB is the debugger project associated with Clang/LLVM.  It
-	supports the Mac OS X, Linux, and FreeBSD platforms, with ongoing
-	work on Windows.  It builds on existing components in the larger
-	LLVM project, for example using Clang's expression parser and
-	LLVM's disassembler.</p>
-
-      <p>The majority of work since the last status update has been on
-	bugfixes and implementation of the remaining functionality
-	missing on FreeBSD.  Most of these improvements are now in the LLDB
-	snapshot in the base system, which has been updated to upstream
-	Subversion revision r202189.  Some highlights of the new update
-	include:</p>
-
-      <ul>
-	<li>Improvements to the remote GDB protocol client.</li>
-	<li>Bug fixes for big-endian targets.</li>
-	<li>Initial support for libdispatch (GCD) queues in the
-	  debuggee.</li>
-	<li>Add "step-avoid-libraries" setting.</li>
-	<li>IO subsystem improvements (including initial work on a
-	  curses GUI).</li>
-	<li>Support hardware watchpoints.</li>
-	<li>Improved unwinding through hand-written assembly
-	  functions.</li>
-	<li>Handle DW_TAG_unspecified_parameters for variadic
-	  functions.</li>
-	<li>Fix Ctrl+C interrupting a running inferior process.</li>
-	<li>Various bug fixes for memory leaks, LLDB segfaults, the
-	  C++ demangler, ELF core files, DWARF debug info, and
-	  others.</li>
-      </ul>
-
-      <p>LLDB is currently not yet built by default and may be enabled
-	by adding <tt>WITH_LLDB=</tt> to <tt>src.conf(5)</tt>.  A port
-	will be made available for those who wish to track ongoing
-	development more closely.</p>
-    <p>This project was sponsored by DARP/AFRL, SRI International, and University of Cambridge.</p><h3>Open tasks:</h3><ol><li>Add support for remote debugging (gdbserver-compatible
-	debugserver).</li><li>Add support for local and core file kernel
-	debugging.</li><li>Implement, fix or test support on all non-amd64
-	architectures.</li><li>Verify cross-debugging.</li><li>Investigate and fix test suite failures.</li><li>Package LLDB as a port.</li><li>Enable by default in the base system for working
-	architectures.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium" href="#Chromium" id="Chromium">Chromium</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.chromium.org/Home" title="http://www.chromium.org/Home">Chromium website</a></td><td>
-	    URL: <a href="http://www.chromium.org/Home" title="Chromium website">http://www.chromium.org/Home</a></td></tr><tr><td><a href="https://github.com/gliaskos/freebsd-chromium" title="https://github.com/gliaskos/freebsd-chromium">Development repository on GitHub</a></td><td>
-	    URL: <a href="https://github.com/gliaskos/freebsd-chromium" title="Development repository on GitHub">https://github.com/gliaskos/freebsd-chromium</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Chromium" title="https://wiki.freebsd.org/Chromium">Chromium on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Chromium" title="Chromium on FreeBSD wiki">https://wiki.freebsd.org/Chromium</a></td></tr></table><p>
-	Contact: Chromium on FreeBSD Team &lt;<a href="mailto:freebsd-chromium@FreeBSD.org">freebsd-chromium@FreeBSD.org</a>&gt;
-	</p>
-      <p>Chromium is the open source web browser project from which
-	Google Chrome draws its source code.  The browsers share the
-	majority of code and features, though there are some minor
-	differences in features and they have different licensing.
-	Over the last four years, the Chromium team has been busy with
-	porting Chromium to FreeBSD.  This involves patching the browser
-	so that it runs on FreeBSD, tracking and documenting security
-	updates, and merging patches back upstream.</p>
-
-      <p>While there are already several browsers available for FreeBSD,
-	advantages of Chromium are:</p>
-
-      <ul>
-	<li>Quick response from upstream to security issues, resulting
-	  in approximately bi-weekly updates.</li>
-
-	<li>A testbed for security features of FreeBSD, like Capsicum.
-	  While support for this capability and sandbox framework is
-	  currently not included in the browser, a proof-of-concept
-	  implementation for an early version of Chromium was realized
-	  within a single weekend.</li>
-      </ul>
-
-      <p>George Liaskos and Ren� Ladan are currently busy with
-	submitting the remaining patches specific to FreeBSD back
-	upstream.  Apart from making future updates easier, it
-	sometimes also improves the overall code quality.</p>
-
-      <p>Jonathan Anderson recently updated the Capsicum patches for
-	Chromium and is talking to upstream about them.</p>
-    <h3>Open tasks:</h3><ol><li>Advocate FreeBSD.  While patches are getting accepted by both
-	humans and bots, it is not an official platform so attitude
-	varies from developer to developer.  While Ren� Ladan thinks it
-	is a bit early, it might be fruitful to investigate what is
-	required to make FreeBSD (and possibly OpenBSD) an official
-	platform in terms of both hardware and procedures.</li><li>If you feel comfortable with large source trees, you can
-	try to build the Git version of Chromium on FreeBSD.  If you are
-	also comfortable with signing Google's Contributor License
-	Agreement, you can join in testing and submitting patches
-	upstream.</li></ol><hr /><h2><a name="FreeBSD-Ada-Ports" href="#FreeBSD-Ada-Ports" id="FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.dragonlace.net" title="http://www.dragonlace.net"></a></td><td>
-	    URL: <a href="http://www.dragonlace.net" title="">http://www.dragonlace.net</a></td></tr><tr><td><a href="http://www.spark-2014.org/about/" title="http://www.spark-2014.org/about/">SPARK 2014</a></td><td>
-	    URL: <a href="http://www.spark-2014.org/about/" title="SPARK 2014">http://www.spark-2014.org/about/</a></td></tr></table><p>
-	Contact:
-	  John
-	  Marino
-	 &lt;<a href="mailto:marino@FreeBSD.org">marino@FreeBSD.org</a>&gt;
-	</p>
-      <p>Ada is a structured, statically typed, imperative,
-	wide-spectrum, and object-oriented high-level computer
-	programming language, extended from Pascal and other
-	languages, originally targeted at embedded and real-time
-	systems.  The number of Ada ports in the collection has grown
-	significantly since the last report six months ago.  There are
-	almost 50 Ada-related ports now, with new ones getting added
-	all the time.</p>
-
-      <p>The previous plan was to move from the GCC 4.7-based GNAT
-	compiler to a GCC 4.8-based one, but finally GCC 4.8 was
-	skipped and now a GCC 4.9-based GNAT is the standard Ada
-	compiler, which fully supports the new ISO standard, Ada 2012.
-	Moving to a newer compiler allowed several important ports
-	like PolyOrb and GPRBuild to be upgraded to the latest
-	available versions.  In fact, almost every Ada port is
-	currently at its most recent upstream version.</p>
-
-      <p>For non-Windows-based Ada development, FreeBSD and DragonFly are
-	now undisputed as the go-to platforms.  The other candidates are
-	Debian and Fedora, but there are few Ada softwares on those
-	platforms that are not also in the FreeBSD ports tree, and the FreeBSD
-	versions are much newer.  The Ports Collection also features
-	software not found anywhere else such as the USAFA's Ironsides
-	DNS server, libsparkcrypto, matreshka, GNATDroid (Android
-	cross-compiler) and several developer libraries.</p>
-
-      <p>A desired addition to the Ada ports will be SPARK 2014 (see
-	links), which should cement FreeBSD as an option for
-	professional, safety-critical application development.  This
-	package should have its first release by early summer.</p>
-    <hr /><h2><a name="GCC-in-the-Ports-Collection" href="#GCC-in-the-Ports-Collection" id="GCC-in-the-Ports-Collection">GCC in the Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://gcc.gnu.org" title="http://gcc.gnu.org">Upstream GCC</a></td><td>
-	    URL: <a href="http://gcc.gnu.org" title="Upstream GCC">http://gcc.gnu.org</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	</p>
-      <p>While the age old version of the GNU Compiler Collection
-	(GCC) in the base system is on its way out with FreeBSD�10
-	and later, there are many users who want&#8212;and some
-	platforms which need&#8212;to use GCC.</p>
-
-      <p>For that purpose there are various versions of GCC in the
-	ports tree, including <tt>lang/gcc46</tt>,
-	<tt>lang/gcc47</tt>, <tt>lang/gcc48</tt> and
-	<tt>lang/gcc49</tt> which track upstream snapshots of the
-	respective release branches, and more importantly
-	<tt>lang/gcc</tt> which serves as the canonical version of GCC
-	and is the default when a port requests <tt>USE_GCC=yes</tt>
-	as well as for some cases of <tt>USES=compiler</tt>.</p>
-
-      <p>With a lot of help from Christoph Moench-Tegeder who fixed
-	many ports and made a fair number respect <tt>CXXFLAGS</tt>,
-	<tt>LDFLAGS</tt> and friends, we managed to update the
-	canonical version from GCC 4.6.4 to GCC 4.7.3.  Many of
-	Christoph's fixes also benefit Clang and other modern
-	compilers.</p>
-
-      <p>For users of <tt>lang/gcc</tt>, this upgrade proved very
-	smooth, and we generally recommend using this port over
-	version specific ones.</p>
-
-      <p>After ten years of service <tt>lang/gcc34</tt> retired, as
-	did <tt>lang/gcc44</tt> after half that timespan.</p>
-
-      <p>On a related note, with the help of John Marino, the license
-	of the GCC ports now properly reflects the combination of
-	GPLv3 for the compiler itself and GPLv3 with GCC Runtime
-	Library Exception for the runtime.  The latter is the key in
-	making it possible to use GCC for building and distributing
-	non-free software.</p>
-    <h3>Open tasks:</h3><ol><li>Move <tt>lang/gcc</tt> from GCC 4.7 to GCC 4.8.</li></ol><hr /><h2><a name="GNOME/FreeBSD" href="#GNOME/FreeBSD" id="GNOME/FreeBSD">GNOME/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/gnome" title="http://www.freebsd.org/gnome">GNOME FreeBSD page</a></td><td>
-	    URL: <a href="http://www.freebsd.org/gnome" title="GNOME FreeBSD page">http://www.freebsd.org/gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD">JHbuild info and results</a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="JHbuild info and results">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr><tr><td><a href="https://github.com/jlmess77/mate-ports" title="https://github.com/jlmess77/mate-ports">MATE staging repository (might break)</a></td><td>
-	    URL: <a href="https://github.com/jlmess77/mate-ports" title="MATE staging repository (might break)">https://github.com/jlmess77/mate-ports</a></td></tr><tr><td><a href="http://marcuscom.com/downloads/marcusmerge" title="http://marcuscom.com/downloads/marcusmerge">GNOME staging repository (might break)</a></td><td>
-	    URL: <a href="http://marcuscom.com/downloads/marcusmerge" title="GNOME staging repository (might break)">http://marcuscom.com/downloads/marcusmerge</a></td></tr></table><p>
-	Contact:
-	  FreeBSD GNOME Team
-	 &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>GNOME is a desktop environment and graphical user interface
-	that runs on top of a computer operating system.  GNOME is
-	part of the GNU Project and can be used with various Unix-like
-	operating systems, including FreeBSD.</p>
-
-      <p>Preparations for merging GNOME�3 are moving forward.
-	The work on the documentation is falling behind a bit, but we
-	got some solid feedback on the rough work to keep this moving
-	forward as well.  In the meantime, deprecation of ports that
-	need the old GNOME�2 desktop ports has begun.  These
-	ports will break when the GNOME desktop components are updated
-	to the GNOME�3 version.</p>
-
-      <p>Thanks to a combined effort by Ryan Lortie (GNOME developer),
-	Ting-Wei Lan (upstream contributor), and Koop Mast, we now have
-	a FreeBSD-powered JHbuild tinderbox.  JHbuild is a build system
-	that allows building GNOME upstream code.  Twice a day, it
-	will attempt to build Gnome components from a specific branch,
-	usually the git master branch, to catch compile issues.  A
-	positive side effect is that it lets upstream know GNOME still
-	lives on non-Linux systems.  It also exposes the GNOME code
-	base to the Clang compiler and <tt>libc++</tt>.  Since the
-	start of this project over a hundred issues have been
-	fixed.</p>
-
-      <p>Gustau Perez has stepped up and put together a port set in
-	the <q>ports-experimental</q> tree of our development
-	repository with GNOME 3.12.  It was decided to polish GNOME
-	3.12.  It will be merged when the preparation work has
-	(mostly) finished, and we are happy with the stability of
-	GNOME 3.12.</p>
-
-      <p>Gustau Perez also ported Cinnamon 2.0 to FreeBSD.  It will
-	appear in the Ports Collection after GNOME�3 has been
-	merged.</p>
-
-      <p>MATE 1.8 was released at the beginning of April, Eric Turgeon
-	of GhostBSD had volunteered to do that update for FreeBSD.  Note
-	that this update is still based on GTK+, version 2.  The
-	GTK+�3-based MATE is on the roadmap for 1.10.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the work needed to be done before GNOME�3 can
-	be merged at all.  Documentation work, port deprecation, and
-	so on.</li><li>Finish porting of MATE 1.8.</li><li>Update Cairo to 1.12 in coordination with the Graphics
-	Team.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD Home Page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD Home Page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr><tr><td><a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="http://portscout.freebsd.org/kde@freebsd.org.html">PortScout Status</a></td><td>
-	    URL: <a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="PortScout Status">http://portscout.freebsd.org/kde@freebsd.org.html</a></td></tr></table><p>
-	Contact: KDE/FreeBSD Team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>KDE is an international free software community producing an
-	integrated set of cross-platform applications designed to run
-	on Linux, FreeBSD, Solaris, Microsoft Windows, and OS X systems.
-	The KDE/FreeBSD Team have continued to improve the experience of
-	KDE software and Qt under FreeBSD.</p>
-
-      <p>During this quarter, the team has kept most of the KDE and Qt
-	ports up-to-date, working on the following releases:</p>
-
-      <ul>
-	<li>KDE SC: 4.12.2, 4.12.3, and 4.12.4; Workspace: 4.11.6,
-	  4.11.7, and 4.11.8</li>
-	<li>Qt: 5.2.1</li>
-	<li>KDevelop: 4.6.0</li>
-	<li>Digikam (and KIPI-plugins): 3.5.0</li>
-      </ul>
-
-      <p>As a result &#8212; according to PortScout &#8212;
-	<tt>kde@</tt> has 526 ports (up from 464), of which 98.86% are
-	up-to-date (up from 88.15%).  iXsystems continues to provide a
-	machine for the team to build packages and to test updates.
-	They have been providing the KDE/FreeBSD team with support for
-	quite a long time and we are very grateful for that.</p>
-
-      <p>A major change has been the deprecation of the KDE3 ports and
-	the move of the <tt>KDE4_PREFIX</tt> to <tt>LOCALBASE</tt>.
-	Also, work on Qt5 continues to maturity.  Raphael Kubo da Costa has been
-	working with upstream to ensure Baloo (Nepomuk successor in
-	KDE SC 4.13) compiles and runs on non-Linux systems.  His work
-	not only benefits FreeBSD but other BSDs and OS X.</p>
-
-      <p>As usual, the team is always looking for more testers and
-	porters, so please contact us and visit our home page (see
-	links).  It would be especially useful to have more helping
-	hands on tasks such as getting rid of the dependency on the
-	defunct HAL project and providing integration with KDE's
-	Bluedevil Bluetooth interface.</p>
-    <p>This project was sponsored by iXsystems, Inc.</p><h3>Open tasks:</h3><ol><li>Update out-of-date ports, see PortScout for a list.</li><li>Work on Qt 5.</li><li>Make sure the whole KDE stack (including Qt) builds and
-	works correctly with Clang and <tt>libc++</tt>.</li><li>Remove the dependency on HAL.</li></ol><hr /><h2><a name="libvirt/bhyve-Support" href="#libvirt/bhyve-Support" id="libvirt/bhyve-Support">libvirt/bhyve Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://libvirt.org/drvbhyve.html" title="http://libvirt.org/drvbhyve.html">bhyve Driver</a></td><td>
-	    URL: <a href="http://libvirt.org/drvbhyve.html" title="bhyve Driver">http://libvirt.org/drvbhyve.html</a></td></tr><tr><td><a href="http://libvirt.org/" title="http://libvirt.org/">libvirt Home Page</a></td><td>
-	    URL: <a href="http://libvirt.org/" title="libvirt Home Page">http://libvirt.org/</a></td></tr><tr><td><a href="http://empt1e.blogspot.ru/search/label/libvirt" title="http://empt1e.blogspot.ru/search/label/libvirt">Developer Blog</a></td><td>
-	    URL: <a href="http://empt1e.blogspot.ru/search/label/libvirt" title="Developer Blog">http://empt1e.blogspot.ru/search/label/libvirt</a></td></tr></table><p>
-	Contact:
-	  Roman
-	  Bogorodskiy
-	 &lt;<a href="mailto:novel@FreeBSD.org">novel@FreeBSD.org</a>&gt;
-	</p>
-      <p>Libvirt is a virtualization library providing a common API
-	for various hypervisors (Qemu/KVM, Xen, LXC, and others), and
-	also a popular library used by a number of projects.  Libvirt
-	1.2.2, released on March, 2014, was the first release to
-	include bhyve support.  Enabling bhyve support allows
-	consumers to use bhyve in libvirt-ready applications without
-	major efforts.</p>
-
-      <p>Currently, libvirt supports almost all essential features of
-	bhyve, such as Virtual Machine lifecycle (start, stop),
-	bridged networking, and virtio/SATA driver support.  The work
-	continues to implement more API calls and to cover more of
-	features offered by bhyve.</p>
-    <h3>Open tasks:</h3><ol><li>FreeBSD port of <tt>netcf</tt> is needed for adding interface
-	driver support to libvirt.</li></ol><hr /><h2><a name="OpenAFS-on-FreeBSD" href="#OpenAFS-on-FreeBSD" id="OpenAFS-on-FreeBSD">OpenAFS on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://openafs.org" title="http://openafs.org">OpenAFS homepage</a></td><td>
-	    URL: <a href="http://openafs.org" title="OpenAFS homepage">http://openafs.org</a></td></tr></table><p>
-	Contact:
-	  Benjamin
-	  Kaduk
-	 &lt;<a href="mailto:bjk@FreeBSD.org">bjk@FreeBSD.org</a>&gt;
-	</p>
-      <p>AFS is a distributed network filesystem that originated from
-	the Andrew Project at Carnegie-Mellon University.  OpenAFS is
-	an open-source implementation of the AFS protocol derived from
-	IBM AFS, which was released under the IBM Public License.
-	OpenAFS on FreeBSD (the <tt>net/openafs</tt> port) is suitable
-	for light use, but is not yet production ready.</p>
-
-      <p>We got a chance to pick up this porting project after some
-	hiatus.  Recent work focused on investigating the bugs
-	preventing the use of a disk cache for caching file data.  An
-	internal "lookupname" abstraction was intended to return an
-	unlocked, referenced vnode, but instead returned a locked,
-	referenced vnode, leading to various failure modes depending
-	on the number of kernel debugging options enabled.</p>
-    <h3>Open tasks:</h3><ol><li>Track down an issue involving incorrect reference counts
-	on the AFS root vnode that cause warnings on shutdown.</li><li>Audit the locking in all the vnode operations code &#8212;
-	it is expected that there remain some incorrectly locked
-	areas, though none that present visible issues under light
-	load.</li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics/WITH_NEW_XORG" title="https://wiki.freebsd.org/Graphics/WITH_NEW_XORG">WITH_NEW_XORG status</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics/WITH_NEW_XORG" title="WITH_NEW_XORG status">https://wiki.freebsd.org/Graphics/WITH_NEW_XORG</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related development repository</a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="Ports-related development repository">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:graphics-team@FreeBSD.org">graphics-team@FreeBSD.org</a>&gt;
-	</p>
-      <p>On the kernel side, the Radeon KMS driver was merged in
-	<tt>stable/9</tt> and will be available in FreeBSD 9.3-RELEASE.
-	Now both the 9.x and 10.x branches share the same support for
-	Intel and AMD GPUs.</p>
-
-      <p>The next big tasks are the updates of the DRM generic code and
-	the <tt>i915</tt> driver.  Both are making good progress and the
-	DRM update should hopefully be ready for wider testing during
-	April.  An update of the Radeon driver is on the to-do list, but
-	nothing is scheduled yet.</p>
-
-      <p>On the ports tree and packages side, the update to Cairo 1.12
-	mentioned in the last quarterly report is ready to be committed,
-	as people who tested it either reported improvements or no
-	regressions.  As a reminder, the switch from Cairo 1.10 to 1.12
-	causes display artifacts with xf86-video-intel 2.7.1, but fixes
-	similar problems with other hardware/driver combinations.
-	Furthermore, Cairo 1.12 is required by Pango 1.36.0, GTK+ 3.10
-	and Firefox 27.0.  A <q>Heads up</q> mail will be posted to the
-	<tt>freebsd-x11</tt> mailing-list when this update goes
-	live.</p>
-
-      <p>In the graphics stack's ports development tree, new Mesa ports
-	are being worked on.  Those ports are required to support GLAMOR
-	(the GL-based 2D acceleration library used by Radeon HD 7000+
-	cards for instance) and OpenCL (using the GPU to perform
-	non-graphical calculations).  We were able to execute some
-	"Hello World" OpenCL programs and play with OpenCL in darktable,
-	but there are some compatibility issues between Clover (Mesa's
-	libOpenCL implementation) and Clang/<tt>libc++</tt>.</p>
-
-      <p>We are preparing an alternate <tt>pkg(8)</tt> repository with
-	packages built with <tt>WITH_NEW_XORG</tt>.  The goal is to ease
-	the usage of the KMS drivers and move forward with the graphics
-	stack updates.  The main <tt>pkg(8)</tt> repository will still
-	use the default setting (<tt>WITH_NEW_XORG</tt> set on
-	<tt>head</tt>, but not on the <tt>stable</tt> branches).</p>
-
-      <p>This will pave the way to the deprecation
-	of<tt>WITH_NEW_XORG</tt> and the removal of the older stack.
-	The current plan is to do this after 10.0-RELEASE End-of-Life,
-	scheduled on January 31st, 2015.  By that time, the only
-	supported releases will be 8.4-RELEASE, 9.3-RELEASE and
-	10.1-RELEASE.  FreeBSD 9.3 and 10.1 will be fully equipped to work
-	with the newer stack.  Unfortunately, FreeBSD 8.x misses the
-	required kernel DRM infrastructure: supporting X.Org here
-	cripples progress on the graphics stack and, once
-	<tt>WITH_NEW_XORG</tt> is gone, we will not support 8.x as a
-	desktop any more.  Therefore, please upgrade to 9.3 or 10.1 when
-	they are available.</p>
-    <h3>Open tasks:</h3><ol><li>See the <q>Graphics</q> and <q>WITH_NEW_XORG</q> wiki
-	pages for up-to-date information.</li></ol><hr /><h2><a name="Using-CentOS-6.5-as-Linux-Base" href="#Using-CentOS-6.5-as-Linux-Base" id="Using-CentOS-6.5-as-Linux-Base">Using CentOS 6.5 as Linux Base</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://github.com/xmj/linux-ports" title="http://github.com/xmj/linux-ports">Work in Progress</a></td><td>
-	    URL: <a href="http://github.com/xmj/linux-ports" title="Work in Progress">http://github.com/xmj/linux-ports</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/187786" title="http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/187786">ports/187786</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/187786" title="ports/187786">http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/187786</a></td></tr></table><p>
-	Contact:
-	  Johannes
-	  Meixner
-	 &lt;<a href="mailto:xmj@chaot.net">xmj@chaot.net</a>&gt;
-	</p>
-      <p>The Linux emulation layer relies on a Linux base distribution
-	along with Linux ports of relevant non-base software.  Fedora
-	10 was imported in 2006, and it shows &#8212; current Linux
-	software like Skype 4, Sublime Text 2, or even modern games
-	fail to run with the provided libraries.</p>
-
-      <p>CentOS 6.5 was released in December 2013 and will be
-	supported until 2017, making it an ideal basis for an update
-	to the ports infrastructure.  Built upon the work of Carlos
-	Jacobo Puga Medina, all ports using Linux have been updated to
-	work with either Fedora 10 or CentOS 6.5.</p>
-
-      <p>The goal of this project is to make CentOS 6.5 the default
-	Linux distribution, so that FreeBSD users can enjoy running
-	modern Linux binaries without having to resort to
-	virtualization � la VirtualBox, or even
-	dual-booting.</p>
-    <p>This project was sponsored by Goldener Grund O�.</p><h3>Open tasks:</h3><ol><li>Clean up <tt>Mk/bsd.linux-*.mk</tt> and fix errors
-	detected in <tt>ports/187786</tt>.</li><li>Revert making c6 the default (in the git
-	repository).</li><li>Testing.</li><li>Review patches and import into the ports tree (any help
-	appreciated).</li><li>Make c6 the default (after sufficient testing) within the
-	ports tree.</li></ol><hr /><h2><a name="Wine/FreeBSD" href="#Wine/FreeBSD" id="Wine/FreeBSD">Wine/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Wine" title="http://wiki.FreeBSD.org/Wine">Wine Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Wine" title="Wine Wiki Page">http://wiki.FreeBSD.org/Wine</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/i386-Wine" title="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/i386-Wine" title="Wine on amd64 Wiki Page">http://wiki.FreeBSD.org/i386-Wine</a></td></tr><tr><td><a href="http://www.winehq.org/" title="http://www.winehq.org/">Wine Home Page</a></td><td>
-	    URL: <a href="http://www.winehq.org/" title="Wine Home Page">http://www.winehq.org/</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	</p>
-      <p>Wine is a free and open source software application that aims
-	to allow applications designed for Microsoft Windows to run on
-	Unix-like operating systems, such as FreeBSD.  The Wine project
-	has been in maintenance mode this quarter and has updated the
-	ports for the following versions:</p>
-
-      <ul>
-	<li>Stable releases: 1.6.2</li>
-	<li>Development releases: 1.7.9 through 1.7.15</li>
-      </ul>
-
-      <p>The ports have packages built for <tt>amd64</tt>, available
-	through the ports <tt>emulators/i386-wine</tt> and
-	<tt>emulators/i386-wine-devel</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>See the <q>Open Tasks</q> and <q>Known Problems</q>
-	sections on the Wine wiki page.</li><li>FreeBSD/<tt>amd64</tt> integration, consult the i386-Wine
-	wiki page for the details.</li><li>Port WoW64 (supporting Windows 32-bit and 64-bit from the
-	same port) and Wine64.</li></ol><hr /><h2><a name="Xfce/FreeBSD" href="#Xfce/FreeBSD" id="Xfce/FreeBSD">Xfce/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xfce" title="">https://wiki.freebsd.org/Xfce</a></td></tr><tr><td><a href="https://svn.redports.org/olivierd/xfce4/" title="https://svn.redports.org/olivierd/xfce4/">Development repository</a></td><td>
-	    URL: <a href="https://svn.redports.org/olivierd/xfce4/" title="Development repository">https://svn.redports.org/olivierd/xfce4/</a></td></tr><tr><td><a href="https://people.freebsd.org/~olivierd/xfce-core-unstable.html" title="https://people.freebsd.org/~olivierd/xfce-core-unstable.html"></a></td><td>
-	    URL: <a href="https://people.freebsd.org/~olivierd/xfce-core-unstable.html" title="">https://people.freebsd.org/~olivierd/xfce-core-unstable.html</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=183690" title="http://www.freebsd.org/cgi/query-pr.cgi?pr=183690">ports/183690</a></td><td>
-	    URL: <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=183690" title="ports/183690">http://www.freebsd.org/cgi/query-pr.cgi?pr=183690</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Xfce Team
-	 &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms, such as FreeBSD.  It aims to be fast and
-	lightweight, while still being visually appealing and easy to
-	use.  The Xfce team continues to keep each piece of
-	the Xfce Desktop up to date.</p>
-
-      <p>The latest commits concerned:</p>
-
-      <ul>
-	<li>Applications:</li>
-
-	<ul>
-	  <li>Midori (0.5.7)</li>
-	  <li>xfburn (0.5.0)</li>
-	  <li>xfce4-parole (0.5.4)</li>
-	  <li>xfce4-taskmanager (1.0.1)</li>
-	  <li>xfce4-tumbler (0.1.30)</li>
-	</ul>
-
-	<li>Panel plugins:</li>
-
-	<ul>
-	  <li>xfce4-clipman-plugin (1.2.5)</li>
-	  <li>xfce4-equake-plugin (1.3.4)</li>
-	  <li>xfce4-wavelan-plugin (0.5.11)</li>
-	  <li>xfce4-whiskermenu-plugin (1.3.2)</li>
-	</ul>
-      </ul>
-
-      <p>We also follow development of core components (available in
-	your repository).  See the links for documentation on how to
-	upgrade those libraries.</p>
-
-      <ul>
-	<li>garcon (0.3.0)</li>
-	<li>libxfce4menu (4.11.1)</li>
-	<li>libxfce4util (4.11.0)</li>
-	<li>xfce4-appfinder (4.11.0)</li>
-	<li>xfce4-desktop (4.11.4)</li>
-	<li>xfce4-dev-tools (4.11.0)</li>
-	<li>xfce4-panel (4.11.0)</li>
-	<li>xfce4-parole (0.6.0)</li>
-	<li>xfce4-settings (4.11.2)</li>
-	<li>xfce4-session (4.11.0)</li>
-	<li>xfce4-wm (4.11.1)</li>
-	<li>xfce4-xkb-plugin (0.7.0)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Add support of DragonFly for xfce4-taskmanger.</li><li>Finish replacing Tango icon theme with GNOME, in order to
-	close <tt>ports/183690</tt> (see links, Midori remains to be
-	fixed).</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="ZFS-Chapter-of-the-Handbook" href="#ZFS-Chapter-of-the-Handbook" id="ZFS-Chapter-of-the-Handbook">ZFS Chapter of the Handbook</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.allanjude.com/zfs_handbook/zfs.html" title="http://www.allanjude.com/zfs_handbook/zfs.html">Preview ZFS Handbook</a></td><td>
-	    URL: <a href="http://www.allanjude.com/zfs_handbook/zfs.html" title="Preview ZFS Handbook">http://www.allanjude.com/zfs_handbook/zfs.html</a></td></tr><tr><td><a href="http://www.allanjude.com/talks/AsiaBSDCon_2014_-_WIP_-_ZFS_Handbook.pdf" title="http://www.allanjude.com/talks/AsiaBSDCon_2014_-_WIP_-_ZFS_Handbook.pdf">Slides from AsiaBSDCon 2014</a></td><td>
-	    URL: <a href="http://www.allanjude.com/talks/AsiaBSDCon_2014_-_WIP_-_ZFS_Handbook.pdf" title="Slides from AsiaBSDCon 2014">http://www.allanjude.com/talks/AsiaBSDCon_2014_-_WIP_-_ZFS_Handbook.pdf</a></td></tr></table><p>
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>ZFS is one of the premier features of FreeBSD.  The current
-	documentation in the Handbook and elsewhere online is severely
-	lacking.  Much of the original documentation from Sun and
-	Oracle has disappeared, moved, or is about the proprietary
-	version of ZFS.</p>
-
-      <p>New users have many questions about ZFS and yet there exists
-	a great deal more bad advice about ZFS than proper
-	documentation. The current ZFS chapter of the FreeBSD Handbook
-	starts off with the required steps to configure an i386
-	machine to run ZFS.  This is more likely to scare off a new
-	user than to educate them about how to properly use ZFS.</p>
-
-      <p>At BSDCan�2013, the process of writing an entirely new
-	chapter of the Handbook on ZFS was started.  Currently this
-	chapter consists of approximately 16,000 words covering all
-	subcommands of the <tt>zpool(8)</tt> and <tt>zfs(8)</tt>
-	utilities, delegation, tuning and a section devoted to
-	definitions and explanations of the terms and features of
-	ZFS.</p>
-
-      <p>The remaining section is the FAQ, to help users address the
-	most common problems they might run into with ZFS.  It would be
-	useful to hear experiences, questions, misconceptions, gotchas,
-	stumbling blocks, and suggestions for the FAQ section from other
-	users.  Also, it would be good to have a use cases section that
-	highlights some of the cases where ZFS provides advantages over
-	traditional file systems.</p>
-
-      <p>Please send suggestions to the <tt>freebsd-doc</tt> mailing
-	list.</p>
-    <p>This project was sponsored by ScaleEngine, Inc.</p><h3>Open tasks:</h3><ol><li>Technical review by Matt Ahrens (co-creator of
-	ZFS).</li><li>Improve delegation section.</li><li>Improve tuning section, add new sysctls added in
-	<tt>head</tt>.</li><li>Add section on jails and the jailed property.</li><li>Add FAQ section.</li><li>Add <q>Use Cases</q> section.</li><li>General editing and review.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="FreeBSD-Participating-in-Summer-of-Code-2014" href="#FreeBSD-Participating-in-Summer-of-Code-2014" id="FreeBSD-Participating-in-Summer-of-Code-2014">FreeBSD Participating in Summer of Code 2014</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://gsoc.FreeBSD.org" title="http://gsoc.FreeBSD.org"></a></td><td>
-	    URL: <a href="http://gsoc.FreeBSD.org" title="">http://gsoc.FreeBSD.org</a></td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2014" title="https://wiki.freebsd.org/SummerOfCode2014"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2014" title="">https://wiki.freebsd.org/SummerOfCode2014</a></td></tr></table><p>
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Glen
-	  Barber
-	 &lt;<a href="mailto:gjb@FreeBSD.org">gjb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Koszek
-	 &lt;<a href="mailto:wkoszek@FreeBSD.org">wkoszek@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD is pleased to have been accepted as a participating
-	organization in Google's Summer of Code 2014.  This will be the
-	tenth time we have participated in the program, having been
-	selected to participate every year since its introduction.</p>
-
-      <p>This year, the administrators made a special attempt to spread
-	the word about Summer of Code around universities, including
-	making contact with around 350 mainly Polish, British, African
-	and American universities to advertise the Summer of Code
-	program, with a particular focus on FreeBSD's participation.  We
-	made contact with both technical departments and student
-	societies.  Posters were produced in several languages, and FreeBSD
-	committers and users were encouraged to distribute these posters
-	around their local universities.</p>
-
-      <p>FreeBSD received a total of 39 proposals from students, and were
-	subsequently granted 15 slots from Google.  We are now facing
-	the unpleasant challenge of trying to decide which of the 39
-	proposals to select, taking into account the quality,
-	desirability and feasibility of each proposal, as well as
-	ensuring we will be able to provide an excellent mentoring
-	experience to each selected student.  All mentors have
-	volunteered to mentor, and we pair students with mentors
-	primarily based on the prospective mentor's areas of expertise,
-	interest in the project, also taking into account the desire to
-	pair students up with mentors in similar time zones in order to
-	improve the student experience.  The final list of accepted
-	students is expected to be announced on the 21st April.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Most of the funding is used to support
-	FreeBSD development projects, conferences and developer summits,
-	purchase equipment to grow and improve the FreeBSD
-	infrastructure, and provide legal support for the Project.</p>
-
-      <p>We published the first issue of the FreeBSD Journal, our new
-	on-line FreeBSD magazine. The positive feedback from both the
-	FreeBSD and outside communities has been incredible.  This
-	quarter we began work on articles and promotion for the second
-	issue.  We also started working on a dynamic version of the
-	magazine that can be read in many web browsers including those
-	that run on FreeBSD.</p>
-
-      <p>This year we are earmarking more funding towards FreeBSD
-	advocacy and education.  You will see more literature, white
-	papers, articles, and so on to help promote FreeBSD.</p>
-
-      <p>The Foundation held a board meeting in Berkeley, California,
-	in January.  We discussed longer term strategy and planning
-	for the year.  We put together our 2014 budget with a plan of
-	raising at least $1,000,000 and spending $900,000.</p>
-
-      <p>Two Foundation funded projects were completed.  The first,
-	co-sponsored by Google, integrated the Casper daemon into
-	FreeBSD. The second was <tt>auditdistd(8)</tt> improvements for
-	the FreeBSD cluster.</p>
-
-      <p>Work continued on these Foundation-sponsored projects: Intel
-	graphics driver update by Konstantin Belousov, UEFI boot support for
-	<tt>amd64</tt> by Ed Maste, autofs automounter and in-kernel
-	iSCSI stack enhancements and bug fixes by Edward Tomasz Napiera&#322;a, and updated
-	<tt>vt(4)</tt> system console by Aleksandr Rybalko.  A more detailed
-	project update for each of the above projects can be found
-	within this quarterly status report.</p>
-
-      <p>We were a Gold Sponsor for NYCBSDCon�2014 in New York,
-	February 8, which was attended by several board members.  We
-	were represented at SCALE in Los Angeles, February 22-23, and
-	ICANN in Singapore, March 22-25.</p>
-
-      <p>We were a sponsor for AsiaBSDCon in Tokyo, March 15-16.
-	Board member Hiroki Sato was the conference organizer.  Board
-	members Kirk McKusick and George V. Neville-Neil taught tutorials and Kirk
-	gave a keynote.  Board member Dru Lavigne manned the foundation
-	table and spoke at one of the sessions.</p>
-
-      <p>We became a Gold+ sponsor for BSDCan�2014, May 16-17 and
-	have started reaching out to vendors to attend the developer
-	summit that runs in the two days before BSDCan.</p>
-
-      <p>Board members George, Kirk, and Robert Watson pushed to finish
-	the final draft of the next edition of their book <q>The
-	Design and Implementation of the FreeBSD Operating
-	System</q>.</p>
-
-      <p>ITWire editor Sam Varghese published an interview with Kirk
-	and Foundation technical manager Ed Maste about the status
-	of secure boot on FreeBSD.</p>
-
-      <p>The FreeBSD Logo is now officially a registered trademark to
-	represent the FreeBSD operating system.  We are working to expand
-	the registration beyond just the FreeBSD operating system, but
-	currently still have to use the <q>TM</q> symbol when using it
-	on apparel and other non-operating-system items.  We continued
-	reviewing requests and granting permission to use FreeBSD
-	trademarks.</p>
-
-      <p>After finishing the 10.0-RELEASE, Foundation system
-	administrator and release engineer Glen Barber began work on
-	adding support for FreeBSD/arm image builds as part of the
-	release build process.  As a result of this work, FreeBSD/arm
-	images are produced as part of the weekly development snapshot
-	builds, and are available from any of the FreeBSD FTP mirrors.
-	Supported kernel configurations currently include
-	<tt>BEAGLEBONE</tt>, <tt>RPI-B</tt>, <tt>PANDABOARD</tt>,
-	<tt>WANDBOARD-QUAD</tt>, and <tt>ZEDBOARD</tt>.</p>
-
-      <p>George visited six large FreeBSD users in the Bay Area in
-	February.  These meetings are conducted to help facilitate
-	collaboration between FreeBSD customers and the FreeBSD Project.  It
-	is an opportunity to exchange information on what the
-	customers are doing and what is being worked on in the
-	Project.  It is also an opportunity to try to connect
-	customers with the appropriate FreeBSD developers who may be
-	working on areas of FreeBSD that interest these customers.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2014-04-2014-06.html b/website/content/en/status/report-2014-04-2014-06.html
deleted file mode 100644
index 1a099e3fc5..0000000000
--- a/website/content/en/status/report-2014-04-2014-06.html
+++ /dev/null
@@ -1,1355 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between April and
-      June 2014.  This is the second of four reports planned for
-      2014.</p><p>The second quarter of 2014 was a very busy and productive time
-      for the FreeBSD�Project.  A new FreeBSD�Core Team was
-      elected, the FreeBSD�Ports Management Team branched the second
-      quarterly <q>stable</q> branch, the FreeBSD�Release
-      Engineering Team was in the process of finalizing the
-      FreeBSD�9.3-RELEASE cycle, and many exciting new features have
-      been added to FreeBSD.</p><p>Thanks to all the reporters for the excellent work!  This
-      report contains 24 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering the period from July to
-      September 2014 is October 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Chelsio-iSCSI-Offload-Support">Chelsio iSCSI Offload Support</a></li><li><a href="#CUSE4BSD">CUSE4BSD</a></li><li><a href="#FreeBSD-and-Summer-of-Code-2014">FreeBSD and Summer of Code 2014</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#pkg(8)">pkg(8)</a></li><li><a href="#QEMU-bsd-user-Enabled-Ports-Building">QEMU bsd-user-Enabled Ports Building</a></li><li><a href="#RPC/NFS-and-CTL/iSCSI-Performance-Optimizations">RPC/NFS and CTL/iSCSI Performance Optimizations</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#PostgreSQL-Performance-Improvements">PostgreSQL Performance Improvements</a></li><li><a href="#Running-FreeBSD-as-an-Application-on-Top-of-the-Fiasco.OC-Microkernel">Running FreeBSD as an Application on Top of the Fiasco.OC
-      Microkernel</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#TMPFS-Stability">TMPFS Stability</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#Updated-vt(4)-System-Console">Updated vt(4) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Quarterly-Status-Reports">Quarterly Status Reports</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team constitutes the project's "Board of
-	Directors", responsible for deciding the project's overall
-	goals and direction as well as managing specific areas of the
-	FreeBSD project landscape.</p>
-
-      <p>Topics for core this quarter have included some far-reaching
-	policy reviews and some significant changes to the project
-	development methodology.</p>
-
-      <p>In May, a new release policy was published and
-	presented at the BSDCan developer conference by John Baldwin.
-	The idea is that each major release branch (for example, 10.X)
-	is guaranteed to be supported for at least five years, but
-	individual point releases on each branch, like 10.0-RELEASE,
-	will be issued at regular intervals and only the latest point
-	release will be supported.</p>
-
-      <p>Another significant change did not receive approval.  When
-	the change to the Bylaws reforming the core team election
-	process was put to the vote of all FreeBSD developers, it failed
-	to reach a quorum.</p>
-
-      <p>June saw the culmination of a long running project to replace
-	the project's bug tracking system.  As of June 3, the FreeBSD
-	project has switched to Bugzilla as its bug tracking system.
-	All of the history of GNATS PRs has been preserved, so there
-	is no need to re-open old tickets.  Work is still going on to
-	replicate some of the integration tweaks that had been applied
-	to GNATS, but all necessary functionality has been implemented
-	and the project is already seeing the benefits of the new
-	capabilities brought by Bugzilla.</p>
-
-      <p>An election to select core members for the next two year term
-	of office took place during this period.  We would like to
-	thank retiring members of core for their years of service.
-	The new core team provides continuity with previous core
-	teams: about half are incumbents from the previous team, and
-	several former core team members have returned after a hiatus.
-	Core now includes two members of the FreeBSD Foundation board and
-	one other Foundation staff member, aiding greater coordination
-	at the top level of the project.  At the same time the
-	core-secretary role was passed on to a new volunteer.</p>
-
-      <p>Other activities included providing consultation on licensing
-	terms for software within the FreeBSD source tree, and oversight
-	of changes to the membership of postmaster and clusteradm.</p>
-
-      <p>Three new src commit bits were issued during this quarter,
-	and one was taken into safekeeping.</p>
-    <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Port Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ports tree slowly approaches the 25,000 ports threshold,
-	while the PR count is slightly below 1800.</p>
-
-      <p>In Q2 we added three new committers, took in one commit bit
-	for safekeeping, and reinstated one commit bit.</p>
-
-      <p>In May, Thomas Abthorpe was replaced by Frederic Culot as portmgr
-	secretary, and Steve Wills became a member of the portmgr
-	team.</p>
-
-      <p>Commencing July 1, the third intake of
-	<tt>portmgr-lurkers</tt> started active duty on
-	<tt>portmgr</tt> for a four month duration.  The next two
-	candidates are William Grzybowski and Nicola Vitale.</p>
-
-      <p>This quarter also saw the release of the second quarterly
-	branch, namely 2014Q2. This branch was not only built for 10
-	(as 2014Q1) but for 9 as well (both i386 and amd64).</p>
-    <h3>Open tasks:</h3><ol><li>As previously noted, many PRs continue to languish, we
-	would like to see committers dedicate themselves to closing as
-	many as possible.</li></ol><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/releases/9.3R/schedule.html" title="http://www.freebsd.org/releases/9.3R/schedule.html">FreeBSD�9.3-RELEASE schedule</a></td><td>
-	    URL: <a href="http://www.freebsd.org/releases/9.3R/schedule.html" title="FreeBSD�9.3-RELEASE schedule">http://www.freebsd.org/releases/9.3R/schedule.html</a></td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, and announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>In early May, the FreeBSD�9.3-RELEASE cycle entered the
-	code slush phase.  The FreeBSD�9.3-RELEASE cycle is nearing
-	the final phases, and 9.3-RC3 builds will be starting soon.
-	9.3-RC3 is planned to be the final release candidate for this
-	release cycle, and at the time of this writing, 9.3-RELEASE
-	should be available on schedule.</p>
-
-      <p>Work is ongoing to integrate support for embedded
-	architectures into the release build process.  At this
-	time, support exists for a number of ARM kernels, in
-	particular the Raspberry Pi, BeagleBone, and WandBoard.</p>
-
-      <p>Additionally, work is in progress to produce virtual machine
-	images as part of the release cycle, supporting various cloud
-	services such as Microsoft Azure, Amazon EC2, and Google
-	Compute Engine.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Chelsio-iSCSI-Offload-Support" href="#Chelsio-iSCSI-Offload-Support" id="Chelsio-iSCSI-Offload-Support">Chelsio iSCSI Offload Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Sreenivasa
-	  Honnur
-	 &lt;<a href="mailto:shonnur@chelsio.com">shonnur@chelsio.com</a>&gt;
-	</p>
-      <p>Building on the new in-kernel iSCSI target and initiator
-	stack released in FreeBSD�10.0, Chelsio Communications has
-	begun developing an offload interface to take advantage of the
-	hardware offload capabilities of Chelsio T4 and T5 10 and 40
-	gigabit Ethernet adapters.</p>
-
-      <p>The code currently implements a working prototype of offload
-	for the initiator side, and target side offload should begin
-	shortly.  The code will be released under the BSD license and
-	is expected to be completed later in the year and be committed
-	to FreeBSD-HEAD, and will likely ship in a FreeBSD release in
-	early 2015.</p>
-    <h3>Open tasks:</h3><ol><li>Complete testing and debugging of the initiator
-	offload.</li><li>Start development of target offload.</li><li>Create hardware-independent offload APIs, based on
-	experiences with target and initiator proof-of-concept
-	implementations.</li></ol><hr /><h2><a name="CUSE4BSD" href="#CUSE4BSD" id="CUSE4BSD">CUSE4BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/266581" title="http://svnweb.freebsd.org/changeset/base/266581">Commit</a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/changeset/base/266581" title="Commit">http://svnweb.freebsd.org/changeset/base/266581</a></td></tr></table><p>
-	Contact:
-	  Hans Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>The so-called <quote>CUSE4BSD</quote> has been imported into the base
-	system of FreeBSD-11.  CUSE is short for <quote>character device in
-	  userspace</quote>.  The CUSE library is a wrapper for the
-	<tt>devfs(8)</tt> kernel functionality which is exposed
-	through /dev/cuse.  In order to function, the CUSE kernel code
-	must either be enabled in the kernel configuration file or
-	loaded separately as a module.  Follow the commit message link
-	to get more information.
-      </p>
-    <hr /><h2><a name="FreeBSD-and-Summer-of-Code-2014" href="#FreeBSD-and-Summer-of-Code-2014" id="FreeBSD-and-Summer-of-Code-2014">FreeBSD and Summer of Code 2014</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://gsoc.FreeBSD.org" title="http://gsoc.FreeBSD.org"></a></td><td>
-	    URL: <a href="http://gsoc.FreeBSD.org" title="">http://gsoc.FreeBSD.org</a></td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2014" title="https://wiki.freebsd.org/SummerOfCode2014"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2014" title="">https://wiki.freebsd.org/SummerOfCode2014</a></td></tr></table><p>
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Glen
-	  Barber
-	 &lt;<a href="mailto:gjb@FreeBSD.org">gjb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Koszek
-	 &lt;<a href="mailto:wkoszek@FreeBSD.org">wkoszek@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD received 39 project proposals this year, many of
-	which were of a very high standard.  After a difficult
-	selection process narrowing these down into the slots we had
-	been allocated, a total of 16 projects were selected to
-	participate in Google Summer of Code 2014 with FreeBSD.</p>
-
-      <p>The projects selected span a wide range of areas within FreeBSD,
-	covering both the base system and ports infrastructure,
-	userland and kernel.  We have students working on firewall
-	optimisation, ports packaging tools, embedded systems,
-	debugging infrastructure, improved Unicode support,
-	enhancements to the loader and to the installer, and several
-	other areas of work.  We are just over halfway through the
-	allocated time this year, and are very much looking forward to
-	integrating code produced by these projects into FreeBSD.</p>
-
-      <p>This is the tenth time FreeBSD has taken part in Google's
-	Summer of Code, and we are grateful to Google to have accepted
-	us as a participating organisation.</p>
-    <hr /><h2><a name="New-Automounter" href="#New-Automounter" id="New-Automounter">New Automounter</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Deficiencies in the current automounter, <tt>amd(8)</tt>, are
-	a recurring problem reported by many FreeBSD users.  A new
-	automounter is being developed to address these concerns.</p>
-
-      <p>The automounter is a cleanroom implementation of
-	functionality available in most other Unix systems, using
-	proper kernel support implemented via an autofs filesystem.
-	The automounter supports a standard map format, and will
-	integrate with the Lightweight Directory Access Protocol
-	(LDAP) service.</p>
-
-      <p>The project is at the early testing stage.  A patch will be
-	released as part of a broader call for testing after
-	additional review on some critical components (in particular,
-	the autofs filesystem).  After fixing reported problems, the
-	code will be committed to FreeBSD�11-CURRENT.  It is expected
-	to ship in the FreeBSD�10.2 release.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Fix bad interaction with <tt>fts(3)</tt>.</li><li>Debug a problem with Kerberos NFS mounts.</li></ol><hr /><h2><a name="pkg(8)" href="#pkg(8)" id="pkg(8)">pkg(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/pkg" title="https://github.com/freebsd/pkg">The main pkg(8) git repository.</a></td><td>
-	    URL: <a href="https://github.com/freebsd/pkg" title="The main pkg(8) git repository.">https://github.com/freebsd/pkg</a></td></tr><tr><td><a href="https://github.com/freebsd/pkg/issues" title="https://github.com/freebsd/pkg/issues">The preferred place to raise bug reports concerning pkg(8).</a></td><td>
-	    URL: <a href="https://github.com/freebsd/pkg/issues" title="The preferred place to raise bug reports concerning pkg(8).">https://github.com/freebsd/pkg/issues</a></td></tr></table><p>
-	Contact:
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Bryan
-	  Drewery
-	 &lt;<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Matthew
-	  Seaman
-	 &lt;<a href="mailto:matthew@FreeBSD.org">matthew@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Vsevolod
-	  Stakhov
-	 &lt;<a href="mailto:vsevolod@FreeBSD.org">vsevolod@FreeBSD.org</a>&gt;
-	<br />
-	Contact: The pkg mailing list &lt;<a href="mailto:freebsd-pkg@FreeBSD.org">freebsd-pkg@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>pkg(8)</tt> is the new package management tool for FreeBSD.
-	It is now the only supported package management tool for FreeBSD
-	releases from 10.0-RELEASE, including the upcoming
-	9.3-RELEASE.  <tt>pkg(8)</tt> is available on all currently
-	supported releases.  Support for the legacy pkg_tools is due
-	to be discontinued at the beginning of September 2014.</p>
-
-      <p>The release of <tt>pkg(8)</tt> 1.3 is imminent.  This
-	includes major improvements in the dependency solver.  Now we
-	can:</p>
-
-      <ul>
-	<li>Switch versions of, for example, Perl or PHP and resolve
-	  all the conflicts with packages that depend on them
-	  automatically.  No more need to manually switch package
-	  origins.</li>
-
-	<li>Deal more gracefully with complex upgrade or install
-	  scenarios.</li>
-
-	<li>Sandbox operations dealing with freshly downloaded data
-	  until it can be verified as trustworthy by checking the
-	  package signature.</li>
-
-	<li>Deal with provides-and-requires style of dependencies, so
-	  for example we can say "this package needs to use a web
-	  server" and allow that dependency to be fulfilled by apache
-	  or nginx or any other alternative that provides web-server
-	  functionality.</li>
-      </ul>
-
-      <p>Beyond the next release, we have work in progress on allowing
-	ranges of versions in dependency rules and handling
-	a selection of "foreign" package repositories, such as CPAN or
-	CTAN or PyPi.</p>
-
-      <p>There are plans to use <tt>pkg(8)</tt> to package up the base
-	system.  Along with other benefits, this will allow writing a
-	universal installer: download one installer image and from
-	there install any available version of FreeBSD, including
-	snapshots.</p>
-
-      <p>We are also intending to use <tt>pkg(8)</tt> within the ports
-	tree at package-build time to handle fulfilling build
-	dependencies.  This opens the possibility of installing
-	build-dependencies by downloading binary packages, which means
-	you can install a package with customized options with the
-	minimum amount of time spent compiling anything else.</p>
-    <h3>Open tasks:</h3><ol><li>We are sorely lacking a comprehensive testing setup.
-	Integrating automated regression testing into the development
-	cycle is becoming an imperative.</li><li>We need testers who can run development versions of pkg in
-	as many distinct types of use-cases as possible, and report
-	feedback from their experiences to the freebsd-pkg@freebsd.org
-	mailing list or our issues list on github.</li></ol><hr /><h2><a name="QEMU-bsd-user-Enabled-Ports-Building" href="#QEMU-bsd-user-Enabled-Ports-Building" id="QEMU-bsd-user-Enabled-Ports-Building">QEMU bsd-user-Enabled Ports Building</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/QemuUserModeHowTo" title="https://wiki.freebsd.org/QemuUserModeHowTo">Overview of technology</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/QemuUserModeHowTo" title="Overview of technology">https://wiki.freebsd.org/QemuUserModeHowTo</a></td></tr><tr><td><a href="http://dirty.ysv.freebsd.org/" title="http://dirty.ysv.freebsd.org/">Status of ports building</a></td><td>
-	    URL: <a href="http://dirty.ysv.freebsd.org/" title="Status of ports building">http://dirty.ysv.freebsd.org/</a></td></tr><tr><td><a href="https://github.com/seanbruno/qemu-bsd-user" title="https://github.com/seanbruno/qemu-bsd-user">Master repository for collaboration</a></td><td>
-	    URL: <a href="https://github.com/seanbruno/qemu-bsd-user" title="Master repository for collaboration">https://github.com/seanbruno/qemu-bsd-user</a></td></tr></table><p>
-	Contact:
-	  Stacey
-	  Son
-	 &lt;<a href="mailto:sson@FreeBSD.org">sson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Juergen
-	  Lock
-	 &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Sean
-	  Bruno
-	 &lt;<a href="mailto:sbruno@FreeBSD.org">sbruno@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>ports-mgmt/poudriere-devel</tt> port is capable of
-	building ports via an emulator.  Configuration of the
-	miscellaneous binary image activator is required prior to a
-	poudriere-devel run.</p>
-
-      <p>ARMV6, MIPS32 and MIPS64 packages can be produced via full
-	emulation.  There are several packages that block a full run
-	of builds.  They can be viewed on the "Status of ports
-	building" link.</p>
-
-      <p>To build packages via emulation, on current or latest
-	stable/10:</p>
-
-      <p>Clone the github repository, and switch to the bsd-user
-	branch.  Then run:</p>
-
-      <p><tt>./configure --static \<br clear="none" />
-	  --target-list="arm-bsd-user i386-bsd-user \<br clear="none" />
-	  mips-bsd-user mips64-bsd-user mips64el-bsd-user \<br clear="none" />
-	  mipsel-bsd-user ppc-bsd-user ppc64-bsd-user sparc-bsd-user \<br clear="none" />
-	  sparc64-bsd-user x86_64-bsd-user"</tt></p>
-
-      <p><tt>gmake; gmake install</tt></p>
-
-      <p>Then set up the <tt>binmiscctl</tt> tools to do some evil
-	hackery to redirect execution of armv6 binaries to qemu:</p>
-
-      <p><tt>binmiscctl add armv6 --interpreter \
-	  "/usr/local/bin/qemu-arm" --magic \
-	  "\x7f\x45\x4c\x46\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02 \<br clear="none" />
-	  \x00\x28\x00" --mask "\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff \<br clear="none" />
-	   \xff\xff\xff\xff\xfe\xff\xff\xff" --size 20 --set-enabled</tt></p>
-
-      <p>Install poudriere-devel from ports.  It knows how to set up
-	things.</p>
-
-      <p>Create a poudriere jail to do all the magic:</p>
-
-      <p><tt>poudriere jail -c -j 11armv632 -m svn -a armv6 \<br clear="none" />
-	  -v head</tt></p>
-
-      <p>Now run poudriere against that jail to build all the
-	ports:</p>
-
-      <p><tt>poudriere bulk -j 11armv632 -a</tt></p>
-
-      <p>Nullfs mount the ports tree into the jail:</p>
-
-      <p><tt>mkdir /usr/local/poudriere/jails/11armv632/usr/ports<br clear="none" />
-	  mount -t nullfs /usr/ports /usr/local/poudriere/jails/11armv632/usr/ports</tt></p>
-
-      <p>To chroot into the jail:</p>
-
-      <p><tt>mount -t devfs devfs /usr/local/poudriere/jails/11armv632/dev<br clear="none" />
-	  chroot /usr/local/poudriere/jails/11armv632/</tt></p>
-    <h3>Open tasks:</h3><ol><li>PPC on AMD64 emulation.  This is a work in progress as
-	there appear to be some serious issues running the bsd-user
-	binary on big-endian hardware.  Justin Hibbits is working on
-	this.</li><li>SPARC64 on AMD64 emulation is non-functional and instantly
-	segfaults.  We are looking for someone to poke at the bits
-	here.</li><li>External Toolchain, XDEV support.  There is partial
-	support for using an AMD64 toolchain that can output binaries
-	for other architecture (e.g., using an AMD64 toolchain to
-	build MIPS64 packages).  We are currently tracking a linking
-	issue with <tt>ports-mgmt/pkg</tt>.  Thanks to Warner Losh,
-	Baptiste Daroussin, Dimitry Andric for poking at bits in here
-	to make the XDEV target useful.</li><li>Signal handling. The MIPS/ARMV6 target stills display a
-	failure that manifests itself when building
-	<tt>devel/p5-Sys-SigAction</tt>.</li><li>Massive documentation update needed.  These modifications
-	actually allow chrooting into a MIPS or ARMv6 environment
-	and using native toolchains and libraries to prototype
-	software for a target platform.</li></ol><hr /><h2><a name="RPC/NFS-and-CTL/iSCSI-Performance-Optimizations" href="#RPC/NFS-and-CTL/iSCSI-Performance-Optimizations" id="RPC/NFS-and-CTL/iSCSI-Performance-Optimizations">RPC/NFS and CTL/iSCSI Performance Optimizations</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD RPC stack, used as a base for its NFS server,
-	received multiple optimizations to improve performance and SMP
-	scalability.  Algorithmic optimizations reduced processing
-	overhead, while improved locking allowed it to scale up to at
-	least 40 processor cores without significant lock congestion.
-	Combined with some other kernel optimizations, the peak NFS
-	request rate increased by many times, reaching up to 600K
-	requests per second on modern hardware.</p>
-
-      <p>The CAM Target Layer (CTL), used as the base for the new kernel iSCSI
-	server, also received a series of locking optimizations which
-	allowed its peak request rate to increase from ~200K to ~600K
-	IOPS with the potential of reaching a rate of 1M requests per
-	second.  That rate is sufficient to completely saturate
-	2x10Gbit Ethernet links with 4KB requests.  For comparison,
-	the port of net/istgt (user-level iSCSI server) on the same
-	hardware with an equivalent configuration showed only 100K
-	IOPS.</p>
-
-      <p>There is also ongoing work on improving CTL functionality.
-	It was already made to support three of four VMware VAAI
-	storage acceleration primitives (<tt>net/istgt</tt> supports
-	2), while the goal is to reach full VAAI support during next
-	months.</p>
-
-      <p>With all these improvements, and earlier improvements in CAM,
-	GEOM, ZFS, and a number of other kernel areas coming soon,
-	FreeBSD�10.1 may become the fastest storage release ever.
-	;)</p>
-
-      <p>These projects are sponsored by iXsystems, Inc.</p>
-    <hr /><h2><a name="ZFSguru" href="#ZFSguru" id="ZFSguru">ZFSguru</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zfsguru.com" title="http://zfsguru.com"></a></td><td>
-	    URL: <a href="http://zfsguru.com" title="">http://zfsguru.com</a></td></tr><tr><td><a href="http://zfsguru.com/news/stateoftheproject/2014" title="http://zfsguru.com/news/stateoftheproject/2014"></a></td><td>
-	    URL: <a href="http://zfsguru.com/news/stateoftheproject/2014" title="">http://zfsguru.com/news/stateoftheproject/2014</a></td></tr></table><p>
-	Contact:
-	  Jason
-	  Edwards
-	 &lt;<a href="mailto:sub.mesa@gmail.com">sub.mesa@gmail.com</a>&gt;
-	</p>
-      <p>ZFSguru is a multifunctional server appliance with a strong
-	emphasis on storage.  ZFSguru began as simple web-interface
-	frontend to ZFS, but has since grown into a FreeBSD derivative
-	with its own infrastructure.  The scope of the project has
-	also grown with the inclusion of add-on packages that add
-	functionality beyond the traditional NAS functionality found
-	in similar product like FreeNAS and NAS4Free.  ZFSguru aims to
-	be a true multifunctional server appliance that is extremely
-	easy to setup and can unite both novice and more experienced
-	users in a single user interface.  The modular nature of the
-	project combats the danger of bloat, whilst still allowing
-	extended functionality to be easily deployed.</p>
-
-      <p>Where development in the first quarter of this year brought
-	drag-and-drop permissions for Samba and NFS, development in
-	the second quarter focused on strengthening the infrastructure
-	of the project.  A new library and toolkit solution dubbed
-	'Mesa' is in the works, providing a cleaner foundation to the
-	project.  A new master server providing secure remote services
-	is being setup, to be located in a high-speed datacenter.  But
-	most importantly, a new system build infrastructure has shown
-	great progress and will soon be able to provide automated
-	system builds to our users.  This not only improves the
-	frequency of system releases but also frees much developer
-	time to be spent on different areas of the project.</p>
-
-      <p>Furthermore, a new website and forum is being worked on,
-	replacing the old-fashioned website that offers only limited
-	functionality.  The new website will be linked to the server
-	database, providing real-time updates about the project.</p>
-
-      <p>In addition, a new platform for collaborative development is
-	in the works.  A service addon has been created for the GitLab
-	project, which is a drop-in replacement of the popular GitHub
-	website.  The choice was made to host our own solution and not
-	rely on GitHub itself.  In retrospect this appears to be a
-	good decision.  The recent development where GitHub removed
-	projects after DCMA takedowns being sent is incompatible with
-	the philosophy of free-flow-of-information, which the ZFSguru
-	project is a strong proponent of.  By hosting our own
-	solution, we have avoided any dependency on third party
-	projects.</p>
-
-      <p>It is expected that after the infrastructure of the project
-	has been revamped, work on the web-interface itself can
-	continue.  New functionality such as GuruDB and Service
-	Bulletins provide a tighter connection between the server
-	infrastructure and the web-interface.  The Migration Manager
-	is one of the last remaining features still missing in the
-	web-interface.  This functionality provides an easy way to
-	upgrade the current system by performing a new clean
-	installation, but migrate all relevant configuration to the
-	new installation.  It also allows to backup all system
-	configuration in a single file to be stored on a different
-	machine should things go awry.</p>
-
-      <p>A longer version of this status report giving a wider
-	perspective on the project can be found at the
-	<quote>stateoftheproject</quote> link.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="PostgreSQL-Performance-Improvements" href="#PostgreSQL-Performance-Improvements" id="PostgreSQL-Performance-Improvements">PostgreSQL Performance Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.kib.kiev.ua/kib/pgsql_perf_v2.0.pdf" title="https://www.kib.kiev.ua/kib/pgsql_perf_v2.0.pdf"></a></td><td>
-	    URL: <a href="https://www.kib.kiev.ua/kib/pgsql_perf_v2.0.pdf" title="">https://www.kib.kiev.ua/kib/pgsql_perf_v2.0.pdf</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Analysis of the performance of the latest 9.3 version of
-	PostgreSQL on FreeBSD-CURRENT has been performed.  The issues
-	which prevented good scalability on a 40-core machine were
-	determined, and changes prototyped which solve the
-	bottlenecks.</p>
-
-      <p>The URL above provides a paper which contains a detailed
-	explanation of the issues and solutions, together with a
-	graph demonstrating the effects on scalability.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Running-FreeBSD-as-an-Application-on-Top-of-the-Fiasco.OC-Microkernel" href="#Running-FreeBSD-as-an-Application-on-Top-of-the-Fiasco.OC-Microkernel" id="Running-FreeBSD-as-an-Application-on-Top-of-the-Fiasco.OC-Microkernel">Running FreeBSD as an Application on Top of the Fiasco.OC
-      Microkernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://en.wikipedia.org/wiki/L4_microkernel_family" title="http://en.wikipedia.org/wiki/L4_microkernel_family">L4 microkernel family</a></td><td>
-	    URL: <a href="http://en.wikipedia.org/wiki/L4_microkernel_family" title="L4 microkernel family">http://en.wikipedia.org/wiki/L4_microkernel_family</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201407DevSummit/BSDUserspace" title="https://wiki.freebsd.org/201407DevSummit/BSDUserspace">A brief description of the project on the FreeBSD wiki (short talk during FreeBSD DevSummit in Cambridge)</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201407DevSummit/BSDUserspace" title="A brief description of the project on the FreeBSD wiki (short talk during FreeBSD DevSummit in Cambridge)">https://wiki.freebsd.org/201407DevSummit/BSDUserspace</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>Fiasco.OC belongs to the L4 microkernel family.  A
-	microkernel provides a bare minimum of services to the
-	applications running on top of it, unlike traditional kernels
-	that incorporate complex code like IP stacks and device
-	drivers.  This allows a dramatic decrease in the amount of
-	code running in the privileged mode of the CPU, achieving
-	higher security while still providing an acceptable level of
-	performance.</p>
-
-      <p>Running an operating system kernel on top of the microkernel
-	allows leveraging any software that was developed for that
-	operating system.  The OS kernel runs in user-mode
-	side-by-side with other microkernel applications such as
-	real-time components.  Multiple OSes, each with their userland
-	applications, can even be run in parallel, thus allowing
-	construction of products where processing of corporate data is
-	strictly separated from the processing of private data.</p>
-
-      <p>The project aims to create a port of FreeBSD to the Fiasco.OC
-	microkernel, a high performance L4 microkernel
-	developed by TU Dresden.  Existing ports of OpenBSD and
-	Linux are used as a reference.  This will allow the use of
-	unique FreeBSD features like ZFS in L4-based projects.</p>
-    <h3>Open tasks:</h3><ol><li>Finish opensourcing the port of L4OpenBSD/amd64 made by
-	genua mbh.  This is a work in progress.</li><li>Publish the sources of the L4FreeBSD port that is largely
-	based on the L4OpenBSD code.</li><li>Improve the port, the first task being adopting the
-	<tt>pmap(9)</tt> module to work with L4 microkernel memory
-	allocation services.</li></ol><hr /><h2><a name="SDIO-Driver" href="#SDIO-Driver" id="SDIO-Driver">SDIO Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SDIO" title="https://wiki.freebsd.org/SDIO">SDIO project page on FreeBSD�Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SDIO" title="SDIO project page on FreeBSD�Wiki">https://wiki.freebsd.org/SDIO</a></td></tr><tr><td><a href="https://github.com/kibab/freebsd/tree/mmccam" title="https://github.com/kibab/freebsd/tree/mmccam">Source code</a></td><td>
-	    URL: <a href="https://github.com/kibab/freebsd/tree/mmccam" title="Source code">https://github.com/kibab/freebsd/tree/mmccam</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>SDIO is an interface designed as an extension of the existing
-	SD card standard, which allows the connecting of different
-	peripherals to a host with a standard SD controller.
-	Peripherals currently sold on the general market include
-	WLAN/BT modules, cameras, fingerprint readers, and barcode
-	scanners.  Additionally, SDIO is used to connect some
-	peripherals in products like Chromebooks and Wandboards.  A
-	prototype of the driver for the Marvell SDIO WLAN/BT (Avastar
-	88W8787) module is also being developed, using the existing
-	Linux driver as the reference.</p>
-
-      <p>SDIO card detection and initialization already work.  Most
-	necessary bus methods are implemented and tested.</p>
-
-      <p>The WiFi driver is able to load firmware onto the card and
-	initialize it.  A rewrite of the MMC stack as a transport
-	layer for the CAM framework is in progress.  This will allow
-	utilization of the well-tested CAM locking model and debug
-	features.</p>
-    <h3>Open tasks:</h3><ol><li>SDIO stack: finish CAM migration.  The initialization of
-	the MMC/SD card is implemented in the XPT layer, but cannot be
-	tested with real hardware because of the lack of any device
-	drivers that implement peripheral drivers and SIMs for CAM
-	MMC.  The plan is to use a modified version of the BeagleBone
-	Black SDHCI controller driver for the SIM and a modified version
-	of <tt>mmcsd(4)</tt> as a peripheral driver.</li><li>Marvell SDIO WiFi: connect to the FreeBSD network stack,
-	write the code to implement required functions (such as
-	sending/receiving data, network scanning and so on).</li></ol><hr /><h2><a name="TMPFS-Stability" href="#TMPFS-Stability" id="TMPFS-Stability">TMPFS Stability</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Peter
-	  Holm
-	 &lt;<a href="mailto:pho@FreeBSD.org">pho@FreeBSD.org</a>&gt;
-	</p>
-      <p>Extensive testing of <tt>tmpfs(5)</tt> using the stress2
-	kernel test suite was done.  The issues found were debugged
-	and fixed.</p>
-
-      <p>Most of the problems are related to bugs in the
-	interaction of the vnode and node lifetime, culminating in e.g.,
-	unmount races and dotdot lookup bugs.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="UEFI-Boot" href="#UEFI-Boot" id="UEFI-Boot">UEFI Boot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/UEFI" title="https://wiki.freebsd.org/UEFI">FreeBSD UEFI wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/UEFI" title="FreeBSD UEFI wiki page">https://wiki.freebsd.org/UEFI</a></td></tr><tr><td><a href="http://www.freebsd.org/snapshots/" title="http://www.freebsd.org/snapshots/">FreeBSD�snapshots</a></td><td>
-	    URL: <a href="http://www.freebsd.org/snapshots/" title="FreeBSD�snapshots">http://www.freebsd.org/snapshots/</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Unified Extensible Firmware Interface (UEFI) provides
-	boot- and run-time services for x86 and other computers.  For
-	the x86 architecture it replaces the legacy BIOS.  This
-	project will adapt the FreeBSD loader and kernel boot process for
-	compatibility with UEFI firmware, found on contemporary
-	servers, desktops, and laptops.</p>
-
-      <p>Ed and Nathan completed a number of integration tasks over
-	the past three months.  Nathan added a first-stage loader,
-	boot1.efi, to support chain-loading the rest of the system
-	from a UFS filesystem.  This allows the UEFI boot process to
-	proceed in a similar fashion as with BIOS boot.  Nathan also
-	added UEFI support to the FreeBSD installer and release image
-	creation script.</p>
-
-      <p>The EFI framebuffer requires the <tt>vt(4)</tt> system
-	console &#8212; a framebuffer driver is not implemented for
-	the legacy <tt>syscons(4)</tt> console.  Ed added automatic
-	<tt>vt(4)</tt> selection to the UEFI boot path.</p>
-
-      <p>Snapshots are now built as dual-mode images, and should boot
-	via both BIOS and UEFI.  Our plan is to merge the UEFI and
-	<tt>vt(4)</tt> work to stable/10 to appear in FreeBSD
-	10.1-RELEASE.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Document manual installation, including dual-boot
-	configurations.</li><li>Implement boot1.efi for ZFS file systems.</li><li>Add support for UEFI variables stored in non-volatile
-	memory (NVRAM).</li><li>Debug boot failures with certain UEFI firmware
-	implementations.</li><li>Support secure boot.</li></ol><hr /><h2><a name="Updated-vt(4)-System-Console" href="#Updated-vt(4)-System-Console" id="Updated-vt(4)-System-Console">Updated vt(4) System Console</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Newcons" title="https://wiki.freebsd.org/Newcons">Project wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Newcons" title="Project wiki page">https://wiki.freebsd.org/Newcons</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>vt(4)</tt> (aka <tt>Newcons</tt>) project provides
-	a replacement for the legacy <tt>syscons</tt> system console.
-	It brings a number of improvements, including better
-	integration with graphics modes and broader character set
-	support.</p>
-
-      <p>Since the last <a href="http://www.freebsd.org/news/status/report-2014-01-2014-03.html#Updated-vt%284%29-System-Console" shape="rect">report</a>,
-	<tt>vt(4)</tt> gained the ability to make early driver
-	selection.  <tt>vt(4)</tt> selects the best
-	successfully-probed driver before most other kernel
-	subsystems are initialized.  Also, to facilitate migration from
-	<tt>syscons(4)</tt> to <tt>vt(4)</tt>, multiple virtual
-	terminal subsystems in the kernel are now supported.  It is
-	controlled by a small module with just one kernel environment
-	variable.  Users can select the virtual terminal system to use
-	by setting <tt>kern.vty=sc</tt> or <tt>kern.vty=vt</tt>.</p>
-
-      <p>The GENERIC kernel configuration for the amd64 and i386
-	platforms now includes both <tt>syscons(4)</tt> and
-	<tt>vt(4)</tt> by default.  This configuration is also planned
-	to be in FreeBSD�10.1-RELEASE.</p>
-
-      <p>The project finally received a man page, so now
-	<tt>vt(4)</tt> is not only the project name, but also a link
-	to its documentation.  Great thanks to Warren Block for
-	that.</p>
-
-      <p>Major highlights:</p>
-
-      <ul>
-	<li>Unicode support.</li>
-
-	<li>Double-width character support for CJK characters.</li>
-
-	<li><tt>xterm(1)</tt>-like terminal emulation.</li>
-
-	<li>Support for Kernel Mode Setting (KMS) drivers
-	  (<tt>i915kms</tt>, <tt>radeonkms</tt>).</li>
-
-	<li>Support for different fonts per terminal window.</li>
-
-	<li>Simplified drivers.</li>
-      </ul>
-
-      <p>Brief status of supported architectures and hardware:</p>
-
-      <ul>
-	<li>amd64 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) &#8212;
-	  works.</li>
-
-	<li>ARM framebuffer &#8212; works.</li>
-
-	<li>i386 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) &#8212;
-	  works.</li>
-
-	<li>IA64 &#8212; untested.</li>
-
-	<li>MIPS &#8212; untested.</li>
-
-	<li>PPC and PPC64 &#8212; work, but without X.Org yet.</li>
-
-	<li>SPARC &#8212; works on certain hardware (e.g., Ultra
-	  5).</li>
-
-	<li><tt>vesa(4)</tt> &#8212; in progress.</li>
-
-	<li>i386/amd64 nVidia driver &#8212; not supported.  VGA
-	  should be used (VESA planned).</li>
-
-	<li>Xbox framebuffer driver &#8212; will be deleted as
-	  unused.</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Implement the remaining features supported by
-	<tt>vidcontrol(1)</tt>.</li><li>Write manual pages for <tt>vt(4)</tt> drivers and kernel
-	interfaces.</li><li>Support direct handling of keyboard by the <tt>kbd</tt>
-	device (without <tt>kbdmux(4)</tt>).</li><li>CJK fonts.  (This is in progress).</li><li>Address performance issues on some architectures.</li><li>Switch to <tt>vt(4)</tt> by default.</li><li>Convert keyboard maps for use with <tt>vt(4)</tt>.</li><li>Implement compatibility mode to be able to use single-byte
-	charsets/key-codes in <tt>vt(4)</tt>.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/arm64/" title="http://svnweb.freebsd.org/base/projects/arm64/"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/projects/arm64/" title="">http://svnweb.freebsd.org/base/projects/arm64/</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Arm64 is the name of the in-progress port of FreeBSD to the
-	ARMv8 CPU when it is in AArch64 mode.  Until recently, all ARM
-	CPU designs were 32-bit only.  With the introduction of the
-	ARMv8 architecture, ARM has added a new 64-bit mode.  This new
-	mode has been named AArch64.</p>
-
-      <p>Booting FreeBSD on the ARM Foundation Model has made a lot of
-	progress since the last status report.  An initial pmap
-	implementation has been written.  With this, FreeBSD is able to
-	enter the Machine Independent boot code.  The required
-	autoconf functions have been added allowing FreeBSD to start
-	scheduling tasks.  Finally the cpu_switch and copystr
-	functions were added.  With these two, FreeBSD will boot to the
-	mountroot prompt.</p>
-
-      <p>Work has started on supporting exceptions, including
-	interrupts.  This will allow more developers to start
-	working on device drivers.</p>
-    <h3>Open tasks:</h3><ol><li>Finish exception and interrupt handling</li><li>Read the Device Tree or ACPI tables from UEFI</li><li>Test on real hardware</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Python-Ports" href="#FreeBSD-Python-Ports" id="FreeBSD-Python-Ports">FreeBSD Python Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Python" title="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Python" title="The FreeBSD Python Team Page">https://wiki.FreeBSD.org/Python</a></td></tr><tr><td><a href="irc://freebsd-python@irc.freenode.net" title="irc://freebsd-python@irc.freenode.net">IRC channel</a></td><td>
-	    URL: <a href="irc://freebsd-python@irc.freenode.net" title="IRC channel">irc://freebsd-python@irc.freenode.net</a></td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  Python Team
-	 &lt;<a href="mailto:python@FreeBSD.org">python@FreeBSD.org</a>&gt;
-	</p>
-      <p>We are pleased to announce the availability of conflict-free
-	Python package support across different Python versions based
-	on the USES=uniquefiles feature recently introduced to the
-	Ports framework.  A Python package can be marked as buildable
-	and installable in parallel for different Python versions at
-	the same time on the same host.  The package building tools,
-	however, do not support this feature yet and the Python team
-	will work closely with portmgr and the pkg developers to enable
-	support on a global ports and packages scale.</p>
-
-      <p>In May and June a huge clean-up operation took place to
-	remove the last bits and pieces targeting easy_install.  In
-	the beginning of July we committed the final changes to remove
-	easy_install support completely from the ports framework.
-	This greatly simplifies the infrastructure and allows us to
-	modernize and maintain it with less effort.</p>
-
-      <p>We added Python 3.4, removed Python 3.1 after its end of
-	life, updated the setuptools ports to version 5.1 and PyPy's
-	development version to 2.3.1. The latest Python 2.7.8 and an
-	updated setuptools will hit the tree shortly.</p>
-
-      <p>Our upstreaming effort continues to produce good outcomes for
-	simplifying maintenance and reducing complexity.</p>
-
-      <p>Looking forward, one of the top priorities is to comply with
-	the USES framework in the foreseeable future and to roll out a
-	consistent maintainer policy for integrating new
-	Python-related ports into the tree.</p>
-    <h3>Open tasks:</h3><ol><li>Migrate bsd.python.mk to the Uses framework.</li><li>Develop a high-level and lightweight Python Ports
-	Policy.</li><li>Add support for granular dependencies (for example
-	&gt;=1.0,&lt;2.0).</li><li>See what adding pip (Python Package Index) support will
-	require.</li><li>Add default QA targets and functions for Python ports
-	(TEST_DEPENDS, regression-test, etc.)</li><li>More tasks can be found on the team's wiki page (see
-	links).</li><li>To get involved, come and say "hi" on IRC and let us know
-	what you are interested in!</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
-	    URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr></table><p>
-	Contact: KDE/FreeBSD Team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE/FreeBSD team has continued to improve the experience
-	of KDE software and Qt under FreeBSD.</p>
-
-      <p>During this quarter, the team has kept most of the KDE and Qt
-	ports up-to-date, working on the following releases:</p>
-
-      <ul>
-	<li>KDE SC: 4.12.5; Workspace: 4.11.9</li>
-      </ul>
-
-      <p>As a result &#8212; according to PortScout &#8212; kde@ has
-	526 ports (up from 526), of which 84.63% are up-to-date (down
-	from 98.86%).  iXsystems Inc. continues to provide a machine
-	for the team to build packages and to test updates.
-	iXsystems Inc. has been providing the KDE/FreeBSD team with
-	support for quite a long time and we are very grateful for
-	that.</p>
-
-      <p>As usual, the team is always looking for more testers and
-	porters so please contact us at kde@FreeBSD.org and visit our
-	home page at
-	<a href="http://FreeBSD.kde.org" shape="rect">http://FreeBSD.kde.org</a>.
-	It would be especially useful to have more helping hands on
-	tasks such as getting rid of the dependency on the defunct
-	HAL project and providing integration with KDE's Bluedevil
-	Bluetooth interface.</p>
-    <h3>Open tasks:</h3><ol><li>Updating out-of-date ports, see
-	<a href="http://portscout.freebsd.org/kde@freebsd.org.html" shape="rect">PortScout</a>
-	for a list</li><li>Removing the dependency on HAL</li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-announce/2014-July/001570.html" title="http://lists.freebsd.org/pipermail/freebsd-announce/2014-July/001570.html">WITH_NEW_XORG repository announce</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-announce/2014-July/001570.html" title="WITH_NEW_XORG repository announce">http://lists.freebsd.org/pipermail/freebsd-announce/2014-July/001570.html</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related development repository</a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="Ports-related development repository">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Graphics team
-	 &lt;<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>We were generally short on time this quarter.  We made less
-	progress than expected on all fronts.</p>
-
-      <p>The alternate <tt>pkg(8)</tt> repository, built with
-	WITH_NEW_XORG, is now available.  This alleviates the need for
-	users to rebuild their ports with WITH_NEW_XORG.  See the
-	announcement, linked above for further information.</p>
-
-      <p>Thanks to a contribution from Jan Kokem�ller, Radeon 32bit
-	ioctls are now working on 64bit hosts.  This was tested
-	successfully with Wine and StarCraft II on FreeBSD 9.x and 11.
-	This required modifications to
-	<tt>emulators/i386-wine-devel</tt> so that it works with
-	WITH_NEW_XORG, and the creation of a new port,
-	<tt>libtxc_dxtn</tt>, to support the texture compression used
-	by StarCraft II.  We have not yet had the time to polish
-	everything, so this still requires manual steps.</p>
-
-      <p>The DRM generic code update is ready, but it breaks the
-	current i915 driver.  Therefore, the i915 driver must be
-	updated before anything is committed.</p>
-
-      <p>Compared to the previous status report, OpenCL test programs
-	are running fine now, thanks to upgrades and fixes to libc++
-	and Clang.  The relevant ports are still not ready to hit the
-	ports tree, unfortunately.</p>
-    <h3>Open tasks:</h3><ol><li>See the "Graphics" wiki page for up-to-date
-	information.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Quarterly-Status-Reports" href="#Quarterly-Status-Reports" id="Quarterly-Status-Reports">Quarterly Status Reports</a></h2><p>
-	Contact: Quarterly Status Report Team &lt;<a href="mailto:monthly@FreeBSD.org">monthly@FreeBSD.org</a>&gt;
-	</p>
-      <p>These quarterly status reports help the FreeBSD community stay
-	up-to-date with the happenings in and around the project.
-	Updates from FreeBSD teams, new features being developed in-
-	or out-of-tree, products derived from FreeBSD, and FreeBSD events
-	are all welcome additions to the status reports.</p>
-
-      <p>The Monthly team has been busy since the last report, with
-	longtime organizer G�bor P�li having stepped down from the team
-	&#8212; thank you G�bor for all your hard work!  This
-	has left something of a void in the preparation of this
-	report, for which the call for items was issued quite late.
-	To help fill the void, Warren Block and Benjamin Kaduk have been added
-	to the monthly@ team, joining Glen Barber, Gavin Atkinson, Ed Maste,
-	and the rest of the team in preparing this report.  Special
-	thanks to Glen for doing most of the work while simultaneously
-	getting 9.3-RELEASE out the door!</p>
-
-      <p>The next cycle is sooner than you think!  The deadline for
-	submitting entries for the Q3 report is October 7th, 2014.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Submit reports for Q42014 to monthly@FreeBSD.org!</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" id="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openstack.org" title="http://www.openstack.org"></a></td><td>
-	    URL: <a href="http://www.openstack.org" title="">http://www.openstack.org</a></td></tr><tr><td><a href="http://www.opencontrail.org" title="http://www.opencontrail.org"></a></td><td>
-	    URL: <a href="http://www.opencontrail.org" title="">http://www.opencontrail.org</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-devstack" title="https://github.com/Semihalf/openstack-devstack"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/openstack-devstack" title="">https://github.com/Semihalf/openstack-devstack</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-nova" title="https://github.com/Semihalf/openstack-nova"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/openstack-nova" title="">https://github.com/Semihalf/openstack-nova</a></td></tr><tr><td><a href="https://github.com/Semihalf/contrail-vrouter" title="https://github.com/Semihalf/contrail-vrouter"></a></td><td>
-	    URL: <a href="https://github.com/Semihalf/contrail-vrouter" title="">https://github.com/Semihalf/contrail-vrouter</a></td></tr><tr><td><a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node"></a></td><td>
-	    URL: <a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="">https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node</a></td></tr></table><p>
-	Contact:
-	  Grzegorz
-	  Bernacki
-	 &lt;<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Michal
-	  Dubiel
-	 &lt;<a href="mailto:md@semihalf.com">md@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Dominik
-	  Ermel
-	 &lt;<a href="mailto:der@semihalf.com">der@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Rafal
-	  Jaworowski
-	 &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
-	</p>
-      <p>OpenStack is a cloud operating system that controls large
-	pools of compute, storage, and networking resources in
-	a datacenter.</p>
-
-      <p>OpenContrail is a network virtualization (SDN) solution
-	comprising network controller, virtual router, and analytics
-	engine, which can be integrated with cloud orchestration
-	systems like OpenStack or CloudStack.</p>
-
-      <p>The goal of this work is to enable FreeBSD as a fully supported
-	compute host for OpenStack using OpenContrail virtualized
-	networking.  The main areas of development are:</p>
-
-      <ul>
-	<li>Libvirt hypervisor driver for bhyve.</li>
-	<li>Support for bhyve (via libvirt compute driver) and the
-	  overall FreeBSD platform in nova-compute.</li>
-	<li>OpenContrail vRouter (forwarding plane kernel module) port
-	  to FreeBSD.</li>
-	<li>OpenContrail Agent (network controller node) port to
-	  FreeBSD.</li>
-	<li>Integration and performance optimizations.</li>
-      </ul>
-
-      <p>Since the last report the following items have been
-	completed, which allow for a working demo of an OpenStack compute
-	node on a FreeBSD host using OpenContrail for network
-	virtualization:</p>
-
-      <ul>
-	<li>Port of the OpenContrail vRouter kernel module for FreeBSD
-	  (MPLS over GRE mode only)</li>
-	<li>Port of the OpenContrail Agent for FreeBSD</li>
-	<li>FreeBSD version of a Devstack installation/configuration
-	  script with support for the OpenContrail solution (Compute
-	  node components only)</li>
-      </ul>
-
-      <p>A demo was presented at the DevSummit during BSDCan2014
-	in Ottawa.  Also, a meetup regarding the subject was organized
-	in Krakow, Poland.</p>
-
-      <p>Work on this project is sponsored by Juniper Networks.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD�Project
-	and community worldwide.  Most of the funding is used to
-	support FreeBSD development projects, conferences and developer
-	summits, purchase equipment to grow and improve the FreeBSD
-	infrastructure, and provide legal support for the Project.</p>
-
-      <p>We published our third issue of the FreeBSD Journal.  We have
-	over 2700 subscriptions so far.  We continued working on the
-	digital edition, which will allow subscribers to read the
-	magazine in different web browsers, including those than run
-	on FreeBSD.  This will be available for the July/August issue of
-	the Journal.</p>
-
-      <p>We hired Anne Dickison, on a freelance basis, as our new
-	marketing director, to help us promote the Foundation and
-	Project.</p>
-
-      <p>The annual board meeting was held in Ottawa, Canada, in May.
-	Directors and officers were elected, and we did some long-term
-	planning.  We worked on our vision, core values, project road
-	mapping, and our near-term goals.  We also met with the core
-	team to discuss roles and responsibilities, project
-	roadmapping, and what we can do to help the Project more.</p>
-
-      <p>We were a Gold+ sponsor for BSDCan, May 16-17 and provided
-	7 travel grants for developers to attend the conference.  We
-	also were the sponsor for both the developer and vendor
-	summits.</p>
-
-      <p>Justin Gibbs gave a FreeBSD presentation at a FreeBSD user's
-	internal technology summit.  Company visits like this help
-	users understand the Project structure better and gives us
-	a chance to communicate what FreeBSD people are working on as
-	well as learn what different companies are doing with FreeBSD, as
-	well as what they'd like to see supported.  We can then help
-	facilitate collaboration between the companies and FreeBSD
-	developers.</p>
-
-      <p>We were represented at Great Wide Open, April 2-3
-	(greatwideopen.org), Texas LinuxFest, June 13-14
-	(texaslinuxfest.org), and SouthEast LinuxFest, June 20-22
-	(southeastlinuxfest.org).</p>
-
-      <p>Hardware was purchased to support an upgrade at Sentex.  A
-	new high-capacity 1Gbps switch was deployed to allow for more
-	systems to be added to the test lab.  The main file server and
-	development box was upgraded to allow more users in the lab
-	simultaneously.</p>
-
-      <p>We purchased hardware, including package builders, and
-	a larger server to allow NYI to be a full replica of all
-	Project systems, comparable to what is in place at Yahoo Inc.
-	and ISC.</p>
-
-      <p>We worked with our lawyer to create an NDA between the
-	Foundation and individuals for third party NDAs.  This allows
-	developers who need access to proprietary documents, to go
-	through the Foundation, via an NDA for access.</p>
-
-      <p>FreeBSD Foundation Systems Administrator and Release Engineer,
-	Glen Barber, continued work on producing regularly-updated
-	FreeBSD/arm snapshots for embedded devices, such as the
-	Raspberry Pi, ZedBoard, and BeagleBone.</p>
-
-      <p>In addition to producing weekly development snapshots from
-	the head/ and stable/ branches, with feedback and help from Ed
-	Maste, Glen finished work to produce release images that will,
-	by default, provide debugging files for userland and kernel
-	available on the FreeBSD�Project FTP mirrors.  Note that the
-	debugging files will not be included on the bootonly.iso,
-	disc1.iso, or dvd1.iso images due to the size of the resulting
-	images.</p>
-
-      <p>Foundation staff member Konstantin Belousov completed an
-	investigation into poor performance of PostgreSQL on FreeBSD.
-	This uncovered scalability problems in the FreeBSD kernel, and
-	changes to address these issues are in progress.</p>
-
-      <p>Some previously completed Foundation-sponsored projects
-	received enhancements or additional work.  The ARM
-	superpages project was completed last year, but is now enabled
-	by default in FreeBSD-CURRENT.  Many stability fixes and
-	enhancements have been committed to the in-kernel iSCSI stack.
-	The iSCSI project was released in FreeBSD�10.0.  Many
-	stability fixes and enhancements have been committed and will
-	be included in FreeBSD�10.1.</p>
-
-      <p>Work continues on the Foundation-sponsored autofs automount
-	daemon, UEFI boot support, the updated <tt>vt(4)</tt> system
-	video console, virtual machine images, and the Intel graphics
-	driver update.  Foundation-sponsored work resulted in 226
-	commits to FreeBSD over the April to June period.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2014-07-2014-09.html b/website/content/en/status/report-2014-07-2014-09.html
deleted file mode 100644
index 5705677da3..0000000000
--- a/website/content/en/status/report-2014-07-2014-09.html
+++ /dev/null
@@ -1,1832 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between July and
-      September 2014.  This is the third of four reports planned for
-      2014.</p><p>The third quarter of 2014 was another productive quarter for
-      the FreeBSD project.  A lot of work has been done on various ARM
-      platforms, with the goal of bringing them to Tier 1 status in
-      FreeBSD 11.  The various ports teams have also worked hard to
-      improve the state of FreeBSD as a desktop operating system.  As
-      usual, performance improvements feature in several places in
-      this report and many of these can benefit from user benchmarking
-      to validate our results.</p><p>Thanks to all the reporters for the excellent work!</p><p>The deadline for submissions covering the period from October
-      to December 2014 is January 7th, 2015.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Address-Space-Layout-Randomization-(ASLR)">Address Space Layout Randomization (ASLR)</a></li><li><a href="#amd64-Xen-Paravirtualization">amd64 Xen Paravirtualization</a></li><li><a href="#bhyve">bhyve</a></li><li><a href="#Chelsio-iSCSI-Offload-Support">Chelsio iSCSI Offload Support</a></li><li><a href="#Debian-GNU/kFreeBSD">Debian GNU/kFreeBSD</a></li><li><a href="#FreeBSD-Preseed-Installation-(PXE)">FreeBSD Preseed Installation (PXE)</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#QEMU-bsd-user-Enabled-Ports-Building">QEMU bsd-user-Enabled Ports Building</a></li><li><a href="#VMWare-VAAI-and-Microsoft-ODX-Acceleration-in-CTL">VMWare VAAI and Microsoft ODX Acceleration in CTL</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#Updated-vt(4)-System-Console">Updated vt(4) System Console</a></li><li><a href="#Updating-OpenCrypto">Updating OpenCrypto</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li><li><a href="#LLVM-Address-Sanitizer-(Asan)">LLVM Address Sanitizer (Asan)</a></li><li><a href="#SSE-Variants-of-libc-Routines-for-amd64">SSE Variants of libc Routines for amd64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#Xfce">Xfce</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Handbook-ezjail-Section">Handbook ezjail Section</a></li><li><a href="#Michael-Lucas-Books">Michael Lucas Books</a></li><li><a href="#ZFS-Chapter-of-the-Handbook">ZFS Chapter of the Handbook</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p>
-	Contact: FreeBSD Cluster Administration Team &lt;<a href="mailto:clusteradm@">clusteradm@</a>&gt;
-	</p>
-      <p>The FreeBSD Cluster Administration Team consists of the people
-	responsible for administering the machines that the project
-	relies on for its distributed work and communications to be
-	synchronised.  In this quarter, the team has worked on:</p>
-
-      <ul>
-	<li>Implemented a central, FreeBSD�cluster-specific package
-	  building node using <tt>ports-mgmt/poudriere-devel</tt>,
-	  providing a single consistent set of third-party binary
-	  packages throughout the FreeBSD�cluster from a common,
-	  known-working configuration.</li>
-
-	<li>Converted all machines running in the FreeBSD cluster from
-	  individual (and sometimes different) userland and kernel
-	  configurations to a single configuration for the base
-	  system.  This enabled the implementation of
-	  a FreeBSD.org-specific binary update mechanism currently
-	  deployed throughout the cluster.</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/releases/10.1R/schedule.html" title="http://www.freebsd.org/releases/10.1R/schedule.html">FreeBSD�10.1-RELEASE schedule</a></td><td>
-	    URL: <a href="http://www.freebsd.org/releases/10.1R/schedule.html" title="FreeBSD�10.1-RELEASE schedule">http://www.freebsd.org/releases/10.1R/schedule.html</a></td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  Release Engineering Team
-	 &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>In mid-July, FreeBSD�9.3-RELEASE was released without delay
-	in release cycle.</p>
-
-      <p>In late August, the FreeBSD�10.1-RELEASE cycle began, and as of
-	this writing, is expected to stay on schedule.</p>
-
-      <p>Work to produce virtual machine images as part
-	of the release cycle has continued,
-	supporting various cloud services such
-	as Microsoft Azure, Amazon EC2, and Google Compute Engine.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://portscout.freebsd.org/" title="http://portscout.freebsd.org/"></a></td><td>
-	    URL: <a href="http://portscout.freebsd.org/" title="">http://portscout.freebsd.org/</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Port
-	  Management Team
-	 &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of Q3, the ports tree holds a bit more than
-	24,000 ports, and the PR count is below 1,400.  Despite the
-	summer holidays the tree saw sustained activity with more than
-	9,000 commits and almost 2,000 ports PRs closed!</p>
-
-      <p>In Q3, five new developers were granted a ports commit bit.
-	None were taken in for safekeeping.</p>
-
-      <p>On the management side, tabthorpe@ decided to step down from
-	his portmgr duties in July.  No other changes were made to the
-	team during Q3.</p>
-
-      <p>This quarter also saw the release of the third quarterly
-	branch, namely 2014Q3.</p>
-
-      <p>On the QA side, 34 exp-runs were performed to validate
-	sensitive updates or cleanups.</p>
-
-      <p>Last, the 20th anniversary of the ports tree was commemorated
-	during Q3 and a video was published for this event.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Tremendous work was done on the PR front in Q3 and we would
-	  be very pleased to see committers dedicate themselves to
-	  closing as many as possible in Q4 as well.</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team constitutes the project's "Board of
-	Directors", responsible for deciding the project's overall
-	goals and direction as well as managing specific areas of the
-	FreeBSD project landscape.</p>
-
-      <p>The third quarter of this year was a relatively quiet time in
-	terms of Core Team activity.  No major policy changes were
-	decided, but the criterea for awarding commit bits were reviewed
-	and the existing requirements were clarified and documented
-	at <a href="http://www.freebsd.org/internal/proposing-committers.html" shape="rect">http://www.freebsd.org/internal/proposing-committers.html</a>.</p>
-
-      <p>Other items dealt with by core during this period:</p>
-
-      <ul>
-	<li>Confirmed with Microsoft that it is permissible to include
-	  DCTCP in FreeBSD.</li>
-
-	<li>Promoted git-beta.freebsd.org out of beta-test to an
-	  official service, consequently renaming it to
-	  git.freebsd.org.</li>
-
-	<li>Mediated between groups of contributors and committers
-	  adopting different positions on the on-going work to
-	  introduce ASLR and associated technologies.</li>
-
-	<li>Worked with the FreeBSD Foundation to obtain a license for
-	  XenForo, and with the forum administrators on plans to
-	  migrate the FreeBSD forums onto the FreeBSD cluster and to
-	  switch to XenForo.</li>
-      </ul>
-
-      <p>During this period, three commit bits were granted, and two
-	commit bits were taken in for safe keeping.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Address-Space-Layout-Randomization-(ASLR)" href="#Address-Space-Layout-Randomization-(ASLR)" id="Address-Space-Layout-Randomization-(ASLR)">Address Space Layout Randomization (ASLR)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://hardenedbsd.org/" title="http://hardenedbsd.org/">The HardenedBSD Project</a></td><td>
-	    URL: <a href="http://hardenedbsd.org/" title="The HardenedBSD Project">http://hardenedbsd.org/</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D473" title="https://reviews.freebsd.org/D473">ASLR review on Phabricator</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D473" title="ASLR review on Phabricator">https://reviews.freebsd.org/D473</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193940" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193940">EXP-RUN test results</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193940" title="EXP-RUN test results">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193940</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201409DevSummit/ASLR" title="https://wiki.freebsd.org/201409DevSummit/ASLR">EuroBSDCon 2014 Devsummit page on ASLR</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201409DevSummit/ASLR" title="EuroBSDCon 2014 Devsummit page on ASLR">https://wiki.freebsd.org/201409DevSummit/ASLR</a></td></tr><tr><td><a href="https://wiki.freebsd.org/AddressSpaceLayoutRandomization" title="https://wiki.freebsd.org/AddressSpaceLayoutRandomization">FreeBSD wiki page on ASLR</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/AddressSpaceLayoutRandomization" title="FreeBSD wiki page on ASLR">https://wiki.freebsd.org/AddressSpaceLayoutRandomization</a></td></tr></table><p>
-	Contact:
-	  Shawn
-	  Webb
-	 &lt;<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>&gt;
-	<br />
-	Contact:
-	  Oliver
-	  Pinter
-	 &lt;<a href="mailto:oliver.pinter@hardenedbsd.org">oliver.pinter@hardenedbsd.org</a>&gt;
-	</p>
-      <p>Address Space Layout Randomization (ASLR) is a computer
-	security technique that aids in mitigating low-level
-	vulnerabilities such as buffer overflows.  ASLR randomizes the
-	memory layout of running applications, to prevent an attacker
-	from knowing where a given exploitable vulnerability lies in
-	memory.</p>
-
-      <p>A lot has happened in the last few months.  Shawn Webb gave
-	presentations at both BSDCan 2014 and EuroBSDCon 2014. The
-	presentations were met with a lot of support and backing.
-	At the end of EuroBSDCon Ilya Bakulin fixed the known bug with
-	ASLR on ARM systems.
-	Shawn Webb and Oliver Pinter have submitted our patch to
-	the Phabricator code review system.  Shawn Webb added
-	an API for allowing a debugger to disable ASLR to
-	support deterministic debugging.  Oliver Pinter enhanced the
-	performance of our ASLR implementation.  A package building
-	exp-run was ran and came out favorably in terms of
-	performance.  Shawn Webb bumped up the maximum number of bits
-	allowed to be randomized to 20 and set the default to 14.</p>
-
-      <p>Shawn Webb and Oliver Pinter founded The HardenedBSD project
-	to serve as a staging area for their work on security-related
-	projects for FreeBSD.</p>
-    <p>This project was sponsored by SoldierX.</p><h3>Open tasks:</h3><ol><li>
-	<p>Get more people testing and reviewing our patch</p>
-      </li><li>
-	<p>Run more performance tests</p>
-      </li><li>
-	<p>Figure out why the two ports failed in the EXP-RUN.
-	  Involve the port maintainers.</p>
-      </li><li>
-	<p>Test on different architectures (we need help with
-	  this)</p>
-      </li></ol><hr /><h2><a name="amd64-Xen-Paravirtualization" href="#amd64-Xen-Paravirtualization" id="amd64-Xen-Paravirtualization">amd64 Xen Paravirtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/FreeBSD/Xen" title="https://wiki.freebsd.org/FreeBSD/Xen">FreeBSD/Xen paravirtualised kernel support.</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/FreeBSD/Xen" title="FreeBSD/Xen paravirtualised kernel support.">https://wiki.freebsd.org/FreeBSD/Xen</a></td></tr></table><p>
-	Contact:
-	  Cherry
-	  Mathew
-	 &lt;<a href="mailto:cherry@FreeBSD.org">cherry@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project aims to add support to the FreeBSD kernel for
-	running in Xen Paravirtualised mode on amd64 systems.  This
-	project has finally reached a "Proof of Concept" stage on the
-	branch
-	<url href="http://svnweb.freebsd.org/base/projects/amd64_xen_pv/">projects/amd64_xen_pv</url>.</p>
-
-      <p>Testing and bug reports on various configurations is
-	encouraged!  The author is also seeking bounties to help
-	complete the effort and assess potential interest.  Please
-	send email if interested.</p>
-
-      <p>PV kernels are still supported by most cloud providers for a
-	range of configurations, although they are expected to be
-	phased out in the future.</p>
-    <p>This project was sponsored by Spectralogic Corporation (2012-2013).</p><h3>Open tasks:</h3><ol><li>
-	<p>Large page support</p>
-      </li><li>
-	<p>SMP support</p>
-      </li><li>
-	<p>Debug and cleanup</p>
-      </li><li>
-	<p>Security vetting</p>
-      </li><li>
-	<p>Performance tweaks</p>
-      </li></ol><hr /><h2><a name="bhyve" href="#bhyve" id="bhyve">bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bhyve.org" title="http://www.bhyve.org">bhyve FAQ and talks</a></td><td>
-	    URL: <a href="http://www.bhyve.org" title="bhyve FAQ and talks">http://www.bhyve.org</a></td></tr><tr><td><a href="http://www.youtube.com/watch?v=lTOiSyu0-MA" title="http://www.youtube.com/watch?v=lTOiSyu0-MA">bhyve past, present, future</a></td><td>
-	    URL: <a href="http://www.youtube.com/watch?v=lTOiSyu0-MA" title="bhyve past, present, future">http://www.youtube.com/watch?v=lTOiSyu0-MA</a></td></tr></table><p>
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Neel
-	  Natu
-	 &lt;<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Tycho
-	  Nightingale
-	 &lt;<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>&gt;
-	</p>
-      <p><tt>bhyve</tt> is a hypervisor that runs on the FreeBSD/amd64
-	platform.  At present, it runs FreeBSD (8.x or later), Linux
-	i386/x64, OpenBSD i386/amd64, and NetBSD/amd64 guests.
-	Current development is focused on enabling additional guest
-	operating systems and implementing features found in other
-	hypervisors.</p>
-
-      <p>A significant amount of progress has been made since the last
-	status report.  Most importantly, all of this work has been
-	MFCed to the 10-STABLE branch and will be included in the 10.1
-	release.</p>
-
-      <p>Support for AMD processors is being developed in the
-	<tt>bhyve_svm</tt> SVN project branch.  The branch is almost
-	at feature-parity with mainline Intel VT-x support, and will
-	be committed into -CURRENT in the near future.</p>
-
-      <p>New features added this quarter:</p>
-
-      <ul>
-	<li>Guest support for recent Linux i386/x64, OpenBSD
-	  i386/amd64, and NetBSD amd64.</li>
-
-	<li>Force guest reset and poweroff with <tt>bhyvectl</tt></li>
-
-	<li>Allow the SMBIOS UUID to be set from the command line</li>
-
-	<li>PCI MMIO extended config space access</li>
-
-	<li>Improved AHCI error handling, legacy interrupt mode</li>
-
-	<li>Additional instruction emulation required by a number of
-	  guests</li>
-
-	<li>Legacy x86 task switching to support double-faults in
-	  FreeBSD/i386</li>
-
-	<li>Legacy PCI interrupts, operation without an APIC (OpenBSD
-	  install)</li>
-
-	<li>Guest memory not included by default in core dumps</li>
-
-	<li>Allow guest vCPUs to be pinned to individual host
-	  CPUs</li>
-
-	<li>Virtio RNG device emulation</li>
-
-	<li>Chapter about <tt>bhyve</tt> added to FreeBSD
-	  Handbook</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Improve documentation</p>
-      </li><li>
-	<p>CSM BIOS boot support for non UEFI-aware guests</p>
-      </li><li>
-	<p>Add support for virtio-scsi</p>
-      </li><li>
-	<p>Improve virtio-net, add offload features, support multiple
-	  queues</p>
-      </li><li>
-	<p>Implement Intel 82580 and e1000 NIC emulation</p>
-      </li><li>
-	<p>Netmap support</p>
-      </li><li>
-	<p>Flexible networking backend: wanproxy, vhost-net</p>
-      </li><li>
-	<p>Move to a single process model, instead of
-	  <tt>bhyveload</tt> and <tt>bhyve</tt></p>
-      </li><li>
-	<p>Support running <tt>bhyve</tt> as non-root</p>
-      </li><li>
-	<p>Add filters for popular VM file formats (VMDK, VHD,
-	  QCOW2)</p>
-      </li><li>
-	<p>Implement an abstraction layer for video (no X11 or SDL in
-	  base system)</p>
-      </li><li>
-	<p>Support for VNC as a video output</p>
-      </li><li>
-	<p>Suspend/resume support</p>
-      </li><li>
-	<p>Live Migration</p>
-      </li><li>
-	<p>Nested VT-x support (bhyve in bhyve)</p>
-      </li><li>
-	<p>Support for other architectures (ARM, MIPS, PPC)</p>
-      </li></ol><hr /><h2><a name="Chelsio-iSCSI-Offload-Support" href="#Chelsio-iSCSI-Offload-Support" id="Chelsio-iSCSI-Offload-Support">Chelsio iSCSI Offload Support</a></h2><p>
-	Contact:
-	  Sreenivasa
-	  Honnur
-	 &lt;<a href="mailto:shonnur@chelsio.com">shonnur@chelsio.com</a>&gt;
-	<br />
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Building on the new in-kernel iSCSI target and initiator
-	stack released in FreeBSD 10.0, Chelsio Communications has begun
-	developing an offload interface to take advantage of the
-	hardware offload capabilities of Chelsio T4 and T5 10 and 40
-	gigabit Ethernet adapters.</p>
-
-      <p>The code implements hardware PDU offload for both target and
-	initiator.  The iSCSI stack has been modified to provide a
-	hardware-independent offload API, allowing offload drivers to
-	be loaded as kernel modules, and to provide mechanisms for the
-	system administrator to configure this feature.  The project
-	is entering a testing phase.  The code will be released under
-	the BSD license and is expected to be completed later in the
-	year and ship in FreeBSD 10.2-RELEASE.</p>
-    <p>This project was sponsored by Chelsio Communications, and The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Complete testing</p>
-      </li></ol><hr /><h2><a name="Debian-GNU/kFreeBSD" href="#Debian-GNU/kFreeBSD" id="Debian-GNU/kFreeBSD">Debian GNU/kFreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.debian.org/Debian_GNU/kFreeBSD" title="https://wiki.debian.org/Debian_GNU/kFreeBSD">Debian GNU/kFreeBSD on the Debian Wiki</a></td><td>
-	    URL: <a href="https://wiki.debian.org/Debian_GNU/kFreeBSD" title="Debian GNU/kFreeBSD on the Debian Wiki">https://wiki.debian.org/Debian_GNU/kFreeBSD</a></td></tr><tr><td><a href="https://www.debian.org/ports/kfreebsd-gnu/" title="https://www.debian.org/ports/kfreebsd-gnu/"></a></td><td>
-	    URL: <a href="https://www.debian.org/ports/kfreebsd-gnu/" title="">https://www.debian.org/ports/kfreebsd-gnu/</a></td></tr></table><p>
-	Contact: Debian GNU/kFreeBSD Maintainers &lt;<a href="mailto:debian-bsd@lists.debian.org">debian-bsd@lists.debian.org</a>&gt;
-	</p>
-      <p>Debian GNU/kFreeBSD is a software distribution produced by
-	Debian, based on the kernel of FreeBSD (instead of Linux) and GNU
-	libc.  Around 90% of Debian's software archive has now been
-	ported to it, for amd64 and i386 architectures.  It was first
-	released with Debian "squeeze" as a development preview in
-	2011, featured again in the "wheezy" release, and hopes to be
-	part of the official Debian "jessie" release in early 2015.</p>
-
-      <p>In 2003 there were several attempts to bootstrap a minimal
-	Debian system upon FreeBSD or NetBSD kernels, some also trying to
-	use the native BSD libc.  The most successful and
-	longest-lived of these was a "GNU/FreeBSD" chroot bootstrapped
-	by Robert Millan with the GNU libc that most of Debian's core
-	packages were designed to work with.  The "k" was later added
-	to the name to reflect that it takes just the kernel from
-	FreeBSD, with most everything else from the Debian archive.  We
-	do also package some FreeBSD utilities as needed to boot it
-	and take advantage of certain features.</p>
-
-      <p>FreeBSD support within GNU libc is now mostly maintained by Petr
-	Salinger, who recently converted it from an older threading
-	implementation based on LinuxThreads to NPTL, which is much
-	more compatible with the software we run.  We have the GNU
-	compiler toolchain as well as Clang 3.4; Perl, Python and
-	Ruby; and OpenJDK 7, based the on work done in FreeBSD's own
-	ports collection.  We use linprocfs for <tt>/proc</tt> because
-	much of Debian GNU software expects this.  The Linuxulator
-	is not needed at all, but could make for interesting future
-	uses.  Porting work mostly focuses now on individual packages'
-	build systems, on preprocessor #ifdefs that do not clearly
-	distinguish between kernel and libc, or fixing testsuites'
-	presumptions of Linux-specific behaviour.  In the course of
-	this, we even found the odd FreeBSD kernel bug, including
-	EN-14:06 / CVE-2014-3880.</p>
-
-      <p>GNU/kFreeBSD has already seen production use, mostly on
-	webservers, email servers and file servers; one such machine
-	has 475 days' uptime receiving around 10,000 emails per day.
-	It has become increasingly practical for desktop/laptop uses
-	thanks largely to new features coming in from FreeBSD 10.1.</p>
-
-      <p>KMS graphics mean that 3D gaming and high-definition video
-	playback perform brilliantly.  We have great support for Intel
-	graphics chipsets, but only an older nvidia Xorg driver.  For
-	radeonkms, Robert Millan was able to add firmware-loading
-	support so that non-free binary blobs can be packaged
-	separately, outside of Debian's main archive.  Proprietary
-	drivers are not useful to us as they would need to be rebuilt
-	from source to port them.</p>
-
-      <p><tt>vt(4)</tt> was necessary for KMS to not break VT
-	switching.  But it has also improved the console's handling of
-	non-ASCII character sets and we do look forward to having
-	console fonts for non-Latin scripts.</p>
-
-      <p>We have supported ZFS for some time, even as a root/boot
-	filesystem (using GRUB 2; Robert Millan added the ZFS support
-	which now FreeBSD itself is able to benefit from).  Enhancements
-	coming from OpenZFS, especially LZ4 compression, in
-	combination with better memory management and GEOM
-	improvements, mean that "jessie" should see a noticeable
-	performance boost.</p>
-
-      <p>debian-installer already allows for pre-seeded, unattended
-	installs and there are PXE-bootable install images
-	available.</p>
-
-      <p>virtio drivers are new to the "jessie" release, enabling
-	support for some public clouds.  We are now compiling Xen domU
-	and PVHVM support into our standard kernel builds.</p>
-
-      <p>We already have userland tools to configure the PF firewall.
-	As an experiment, we are compiling in IPSEC support by
-	default for the upcoming release, and would like to see it put
-	to good use against present-day privacy and security
-	threats.</p>
-
-      <p>We try to support the use of Debian GNU/kFreeBSD inside a jail
-	on a FreeBSD host system, and hopefully vice-versa.  Some of the
-	jail utilities are not yet packaged, but we have documentation
-	on the Debian Wiki on how to set up jails on "wheezy", which
-	are fully functional.</p>
-
-      <p>The init system we currently use is a parallel System V-style
-	init, although Debian GNU/Linux will be switching away from
-	that to systemd.  For the next release we may switch to
-	OpenRC, which is mostly ported already.</p>
-
-      <p>Not having systemd or udev means that we will be unable to
-	support GNOME 3.14 in the upcoming release.  We have very good
-	support for XFCE, also have KDE, LXDE and the
-	recently-packaged MATE desktop environment.  The Debian
-	software archive provides many alternative window managers for
-	Xorg such as IceWM, dozens of terminal emulators, and so
-	on.</p>
-
-      <p>As we approach the freeze of the Debian "jessie" release,
-	we would love for anyone to test GNU/kFreeBSD, try to use it
-	for whatever would be useful to you, and let us know what
-	issues you run into.  Ask for help on our project mailing list
-	or IRC channel, and let us know of any bugs you find.  We
-	still have time to fix problems before release, and we would
-	be happy to improve our documentation at any time.</p>
-    <hr /><h2><a name="FreeBSD-Preseed-Installation-(PXE)" href="#FreeBSD-Preseed-Installation-(PXE)" id="FreeBSD-Preseed-Installation-(PXE)">FreeBSD Preseed Installation (PXE)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2014/FreeBSD_PXE_preseed" title="https://wiki.freebsd.org/SummerOfCode2014/FreeBSD_PXE_preseed"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2014/FreeBSD_PXE_preseed" title="">https://wiki.freebsd.org/SummerOfCode2014/FreeBSD_PXE_preseed</a></td></tr></table><p>
-	Contact:
-	  Kamil
-	  Czekirda
-	 &lt;<a href="mailto:kczekirda@FreeBSD.org">kczekirda@FreeBSD.org</a>&gt;
-	</p>
-      <p>This is a Google Summer of code project to provide
-	a noninteractive FreeBSD installation process from the network.  In
-	the first part, an implementation was added for scripted
-	<tt>bsdinstall(8)</tt>.  It supports variables such as KEYMAP,
-	HOSTNAME, MIRROR, RELEASE, TIMEZONE, DAEMONS, ROOTPWHASH, and
-	USERS.  Network configuration, ZFS options, and others are
-	also included.</p>
-
-      <p>The second part of the project is about booting the
-	<tt>fai</tt> (Fully Automatic Installer) from the network by
-	PXE.  An installer distro was created based on mfsBSD.  After
-	boot, <tt>fai</tt> looks for the "bootfile-name" parameter
-	from the DHCP server.  This parameter tells <tt>fai</tt> where
-	the <tt>bsdinstall</tt> script is located.  <tt>fai</tt>
-	supports MAC-based configuration, or a default if a MAC-based
-	configuration file does not exist.</p>
-    <p>This project was sponsored by Google Summer of Code 2014.</p><h3>Open tasks:</h3><ol><li>
-	<p>Documentation, including a HOWTO and handbook</p>
-      </li><li>
-	<p>More tests in different configurations</p>
-      </li><li>
-	<p>Support for more than one network interface is planned</p>
-      </li></ol><hr /><h2><a name="Jenkins-Continuous-Integration-for-FreeBSD" href="#Jenkins-Continuous-Integration-for-FreeBSD" id="Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://jenkins.freebsd.org" title="https://jenkins.freebsd.org">Jenkins CI server in FreeBSD cluster</a></td><td>
-	    URL: <a href="https://jenkins.freebsd.org" title="Jenkins CI server in FreeBSD cluster">https://jenkins.freebsd.org</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201405DevSummit/Jenkins" title="https://wiki.freebsd.org/201405DevSummit/Jenkins">Jenkins working group at DevSummit</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201405DevSummit/Jenkins" title="Jenkins working group at DevSummit">https://wiki.freebsd.org/201405DevSummit/Jenkins</a></td></tr><tr><td><a href="http://www.bsdcan.org/2014/schedule/events/445.en.html" title="http://www.bsdcan.org/2014/schedule/events/445.en.html">Jenkins presentation at BSDCan</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2014/schedule/events/445.en.html" title="Jenkins presentation at BSDCan">http://www.bsdcan.org/2014/schedule/events/445.en.html</a></td></tr><tr><td><a href="http://clang-analyzer.llvm.org/scan-build.html" title="http://clang-analyzer.llvm.org/scan-build.html">clang static analyzer</a></td><td>
-	    URL: <a href="http://clang-analyzer.llvm.org/scan-build.html" title="clang static analyzer">http://clang-analyzer.llvm.org/scan-build.html</a></td></tr><tr><td><a href="http://scan.freebsd.org" title="http://scan.freebsd.org">FreeBSD static analysis results</a></td><td>
-	    URL: <a href="http://scan.freebsd.org" title="FreeBSD static analysis results">http://scan.freebsd.org</a></td></tr><tr><td><a href="http://www.bsdnow.tv/episodes/2014_07_02-base_iso_100" title="http://www.bsdnow.tv/episodes/2014_07_02-base_iso_100">BSD Now episode 44</a></td><td>
-	    URL: <a href="http://www.bsdnow.tv/episodes/2014_07_02-base_iso_100" title="BSD Now episode 44">http://www.bsdnow.tv/episodes/2014_07_02-base_iso_100</a></td></tr><tr><td><a href="http://www.slideshare.net/CraigRodrigues1/libvirt-bhyve" title="http://www.slideshare.net/CraigRodrigues1/libvirt-bhyve">livirt and bhyve"</a></td><td>
-	    URL: <a href="http://www.slideshare.net/CraigRodrigues1/libvirt-bhyve" title="livirt and bhyve&quot;">http://www.slideshare.net/CraigRodrigues1/libvirt-bhyve</a></td></tr><tr><td><a href="https://github.com/jmmv/kyua" title="https://github.com/jmmv/kyua">Kyua testing framework</a></td><td>
-	    URL: <a href="https://github.com/jmmv/kyua" title="Kyua testing framework">https://github.com/jmmv/kyua</a></td></tr><tr><td><a href="https://issues.jenkins-ci.org/browse/JENKINS-24521" title="https://issues.jenkins-ci.org/browse/JENKINS-24521">Issue to update Jenkins to JNA 4.1.0 for FreeBSD</a></td><td>
-	    URL: <a href="https://issues.jenkins-ci.org/browse/JENKINS-24521" title="Issue to update Jenkins to JNA 4.1.0 for FreeBSD">https://issues.jenkins-ci.org/browse/JENKINS-24521</a></td></tr><tr><td><a href="https://github.com/jenkinsci/jenkins/pull/1387" title="https://github.com/jenkinsci/jenkins/pull/1387">Pull request #1 to upgrade JNA in Jenkins</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/jenkins/pull/1387" title="Pull request #1 to upgrade JNA in Jenkins">https://github.com/jenkinsci/jenkins/pull/1387</a></td></tr><tr><td><a href="https://github.com/jenkinsci/jenkins/pull/1410" title="https://github.com/jenkinsci/jenkins/pull/1410">Pull request #2 to upgrade JNA in Jenkins</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/jenkins/pull/1410" title="Pull request #2 to upgrade JNA in Jenkins">https://github.com/jenkinsci/jenkins/pull/1410</a></td></tr><tr><td><a href="http://jenkins.mouf.net/job/pkg/" title="http://jenkins.mouf.net/job/pkg/">Jenkins job for testing pkg</a></td><td>
-	    URL: <a href="http://jenkins.mouf.net/job/pkg/" title="Jenkins job for testing pkg">http://jenkins.mouf.net/job/pkg/</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499">yacc bug found by kyua</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499" title="yacc bug found by kyua">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246">IPv6 multicast join() problem found by Jenkins</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246" title="IPv6 multicast join() problem found by Jenkins">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246</a></td></tr><tr><td><a href="https://github.com/rodrigc/kyua/wiki/Quickstart-Guide" title="https://github.com/rodrigc/kyua/wiki/Quickstart-Guide">Kyua Quickstart Guide</a></td><td>
-	    URL: <a href="https://github.com/rodrigc/kyua/wiki/Quickstart-Guide" title="Kyua Quickstart Guide">https://github.com/rodrigc/kyua/wiki/Quickstart-Guide</a></td></tr></table><p>
-	Contact:
-	  Craig
-	  Rodrigues
-	 &lt;<a href="mailto:rodrigc@FreeBSD.org">rodrigc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jenkins Administrators &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Testing &lt;<a href="mailto:freebsd-testing@FreeBSD.org">freebsd-testing@FreeBSD.org</a>&gt;
-	</p>
-      <p>In May, Craig Rodrigues led a working group <em>Continuous
-	  Integration and Testing with Jenkins for FreeBSD</em> at the
-	FreeBSD Devsummit in Ottawa.  Craig Rodrigues also gave a Jenkins
-	presentation at BSDCan.</p>
-
-      <p>At BSDCan, Craig Rodrigues had some discussions with Julio Merino
-	about how to better integrate FreeBSD testing efforts with
-	Jenkins and kyua.  As a result of this discussion, Julio Merino
-	enhanced the <tt>kyua</tt> testing framework with a
-	<tt>kyua report-junit</tt> command.  This command takes kyua
-	test results and outputs a test report in JUnit XML format.
-	Jenkins can directly import JUnit XML test results and display
-	them nicely.</p>
-
-      <p>In June, Craig Rodrigues was interviewed for episode 44 of BSD
-	Now.  The interview covered Jenkins and Continuous Integration
-	in the FreeBSD project.</p>
-
-      <p>In July, Craig Rodrigues gave a presentation to the Bay Area FreeBSD
-	Users Group (BAFUG), <em>Libvirt and bhyve</em>, based on
-	experience he had with those technologies when used with
-	Jenkins.</p>
-
-      <p>Li-Wen Hsu set up a Jenkins job to run the LLVM scan-build
-	tool to perform static analysis of the FreeBSD code, and make the
-	results availalble at <tt>scan.freebsd.org</tt>.</p>
-
-      <p>Steve Wills modified the Jenkins job which builds
-	<tt>pkg(8)</tt> to use the <tt>kyua report-junit</tt> command
-	to integrate <tt>pkg(8)</tt> test results in Jenkins.</p>
-
-      <p>Anthony Williams reported that the version of the Java
-	Native Access (JNA) library bundled with Jenkins has problems
-	on FreeBSD.  This causes problems with Jenkins using libpam and
-	other plugins that use JNA.  Craig filed JENKINS-24521
-	against Jenkins.  Craig submitted patches to Jenkins to update
-	Jenkins to use JNA 4.1.0, which has fixes for FreeBSD.  </p>
-
-      <p>Craig Rodrigues worked on automatically running the tests in the
-	FreeBSD <tt>/usr/tests</tt> directory under Jenkins using the
-	<tt>kyua</tt> test framework.  Craig Rodrigues provided feedback
-	to Julio Merino about <tt>kyua</tt> and Julio Merino incorporated some
-	of the feedback as bugfixes and feature enhancements to
-	<tt>kyua</tt>.  Craig Rodrigues committed some fixes to FreeBSD to
-	eliminate some test failures.  One of the tests still results
-	in a crash in byacc.  This is being tracked in PR 193499.
-	Thomas E. Dickey (byacc maintainer) submitted a patch to fix
-	the problem, and this has been committed to FreeBSD.</p>
-
-      <p>Craig Rodrigues analyzed the cause of some startup errors in
-	Jenkins when opening a multicast socket.  He had some
-	discussion with Bruce M. Simpson captured in PR 193246.  The Java JDK
-	depends on functionality in Solaris where it is possible to
-	open an IPv4 multicast socket, but with an IPv4 multicast
-	address mapped to an IPv6 address.  On Linux, there are
-	modifications to the JDK itself to work around this.  Bruce M. Simpson
-	said that the work to make the FreeBSD IPv6 stack behave like
-	Solaris would require some work.</p>
-
-      <p>Craig Rodrigues started writing a Kyua Quickstart Guide.  This
-	guide is meant to help new kyua users who want to write tests
-	and run them under kyua.  Craig Rodrigues is seeking feedback to
-	help improve this guide.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Upstream more fixes to Jenkins for FreeBSD, such as JNA
-	  fixes.</p>
-      </li><li>
-	<p>Automate the build of <tt>/usr/tests</tt>.</p>
-      </li><li>
-	<p>Set up more builds based on examples from the existing FreeBSD
-	  Tinderbox.</p>
-      </li><li>
-	<p>Get feedback for improving the Kyua Quickstart Guide.</p>
-      </li><li>
-	<p>We need more people to join us on
-	  freebsd-testing@FreeBSD.org and help out.  We especially
-	  need people with devops and scripting experience to help us
-	  set up more builds and tests.  We would also like to
-	  integrate with other parts of the project, such as
-	  Phabricator.</p>
-      </li></ol><hr /><h2><a name="New-Automounter" href="#New-Automounter" id="New-Automounter">New Automounter</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Automounter" title="https://wiki.freebsd.org/Automounter"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Automounter" title="">https://wiki.freebsd.org/Automounter</a></td></tr><tr><td><a href="http://people.freebsd.org/~trasz/autofs.pdf" title="http://people.freebsd.org/~trasz/autofs.pdf"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~trasz/autofs.pdf" title="">http://people.freebsd.org/~trasz/autofs.pdf</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Limitations of the current automounter, <tt>amd(8)</tt>, are
-	a recurring problem reported by many FreeBSD users.  A new
-	automounter is being developed to address these concerns.</p>
-
-      <p>The automounter is a cleanroom implementation of
-	functionality available in most other Unix systems, using
-	proper kernel support implemented via an autofs filesystem.
-	The automounter supports a standard map format, and will
-	integrate with the Lightweight Directory Access Protocol
-	(LDAP) service.</p>
-
-      <p>The FreeBSD Foundation worked with enterprise and university
-	users to test the new automounter in existing LDAP-based
-	environments, including some with thousands of map
-	entries.</p>
-
-      <p>The code is now ready to use.  It has been committed to
-	11-CURRENT and 10-STABLE, and will ship as part of
-	10.1-RELEASE.  There is ongoing work on improving performance
-	and fixing possible bugs.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="QEMU-bsd-user-Enabled-Ports-Building" href="#QEMU-bsd-user-Enabled-Ports-Building" id="QEMU-bsd-user-Enabled-Ports-Building">QEMU bsd-user-Enabled Ports Building</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/QemuUserModeHowTo" title="https://wiki.freebsd.org/QemuUserModeHowTo">Generic Explanation of QEMU bsd-user</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/QemuUserModeHowTo" title="Generic Explanation of QEMU bsd-user">https://wiki.freebsd.org/QemuUserModeHowTo</a></td></tr><tr><td><a href="http://chips.ysv.freebsd.org/packages" title="http://chips.ysv.freebsd.org/packages">Current ARMv6 Packages</a></td><td>
-	    URL: <a href="http://chips.ysv.freebsd.org/packages" title="Current ARMv6 Packages">http://chips.ysv.freebsd.org/packages</a></td></tr><tr><td><a href="https://github.com/seanbruno/qemu-bsd-user" title="https://github.com/seanbruno/qemu-bsd-user">Github repo of development source</a></td><td>
-	    URL: <a href="https://github.com/seanbruno/qemu-bsd-user" title="Github repo of development source">https://github.com/seanbruno/qemu-bsd-user</a></td></tr></table><p>
-	Contact:
-	  Sean
-	  Bruno
-	 &lt;<a href="mailto:sbruno@FreeBSD.org">sbruno@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Juergen
-	  Lock
-	 &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Stacey
-	  Son
-	 &lt;<a href="mailto:sson@FreeBSD.org">sson@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD packages for the Tier-1 i386 and amd64 CPU architectures
-	are built by a single very high-performance machine.  Other
-	architectures lack equivalent hardware, and we began
-	experimenting with QEMU's user-mode emulation to cross-build
-	packages from an amd64 builder.</p>
-
-      <p>We have moved from just being able to produce packages to
-	providing a stable repo of packages for ARMv6.</p>
-
-      <p><tt>ports-mgmt/poudriere-devel</tt> is still the current
-	method for building packages.  See the previous status report for
-	explanations and details on methods.</p>
-    <hr /><h2><a name="VMWare-VAAI-and-Microsoft-ODX-Acceleration-in-CTL" href="#VMWare-VAAI-and-Microsoft-ODX-Acceleration-in-CTL" id="VMWare-VAAI-and-Microsoft-ODX-Acceleration-in-CTL">VMWare VAAI and Microsoft ODX Acceleration in CTL</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>The CAM Target Layer (CTL), used as base for the kernel iSCSI
-	server, got support for VMWare VAAI and Microsoft ODX
-	storage acceleration.  It permits avoiding network
-	bottlenecks and improves storage efficiency on sets of large
-	operations, such as virtual machine (or large file) creation,
-	initialization to zeros, copy, delete, etc..</p>
-
-      <p>VMWare VAAI includes support for these primitives/SCSI
-	commands: Atomic Test and Set (ATS) &#8212; COMPARE AND
-	WRITE command; Extended Copy (Clone) &#8212; SPC-3 subset
-	of XCOPY commands; Write Same (Zero) &#8212; set of WRITE
-	SAME commands; and Dead Space Reclamation (Delete) &#8212; UNMAP
-	command.</p>
-
-      <p>Microsoft ODX includes support for these SCSI commands:
-	POPULATE TOKEN/WRITE USING TOKEN (SPC-4 extensions of
-	XCOPY), WRITE SAME and UNMAP.</p>
-
-      <p>All XCOPY operations are currently limited to one storage
-	host.  ODX operations are currently limited only to iSCSI
-	disks.  Accelerated inter-host copying or copying to/from
-	files on Samba shares is not implemented and is handled by
-	initiators in the legacy way.</p>
-
-      <p>The code is committed to FreeBSD head and stable/10 branches,
-	and will be present in FreeBSD 10.1 and FreeNAS 9.2.1.8 /
-	9.3 releases.</p>
-    <p>This project was sponsored by iXsystems, Inc..</p><h3>Open tasks:</h3><ol><li>
-	<p>Full support for thin provisioning, including capacity
-	  usage reporting and threshold notifications.</p>
-      </li><li>
-	<p>Inter-host XCOPY operations.</p>
-      </li></ol><hr /><h2><a name="ZFSguru" href="#ZFSguru" id="ZFSguru">ZFSguru</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zfsguru.com" title="http://zfsguru.com"></a></td><td>
-	    URL: <a href="http://zfsguru.com" title="">http://zfsguru.com</a></td></tr><tr><td><a href="http://zfsguru.com/news/stateoftheproject/2014" title="http://zfsguru.com/news/stateoftheproject/2014"></a></td><td>
-	    URL: <a href="http://zfsguru.com/news/stateoftheproject/2014" title="">http://zfsguru.com/news/stateoftheproject/2014</a></td></tr><tr><td><a href="http://zfsguru.com/forum/zfsgurudevelopment/876" title="http://zfsguru.com/forum/zfsgurudevelopment/876"></a></td><td>
-	    URL: <a href="http://zfsguru.com/forum/zfsgurudevelopment/876" title="">http://zfsguru.com/forum/zfsgurudevelopment/876</a></td></tr></table><p>
-	Contact:
-	  Jason
-	  Edwards
-	 &lt;<a href="mailto:sub.mesa@gmail.com">sub.mesa@gmail.com</a>&gt;
-	</p>
-      <p>ZFSguru is a multifunctional server appliance with a strong
-	emphasis on storage.  ZFSguru began as simple web-interface
-	frontend to ZFS, but has since grown into a FreeBSD derivative
-	with its own infrastructure.  The scope of the project has
-	also grown with the inclusion of add-on packages that add
-	functionality beyond the traditional NAS functionality found
-	in similar product like FreeNAS and NAS4Free.  ZFSguru aims to
-	be a true multifunctional server appliance that is extremely
-	easy to set up and can unite both novice and more experienced
-	users in a single user interface.  The modular nature of the
-	project combats the danger of bloat, whilst still allowing
-	extended functionality to be easily deployed.</p>
-
-      <p>The development work in Q3 focused heavily on the new build
-	infrastructure.  This allows the ZFSguru project to release
-	new system images together with addon services at much higher
-	frequency and with much less manual intervention.  This should
-	free up a lot of development time to be spent on the core of
-	the project: the web interface.</p>
-
-      <p>Furthermore, a new website and forum is being worked on,
-	replacing the old-fashioned website that offers only limited
-	functionality.  The new website will be linked to the server
-	database, providing real-time updates about the project.</p>
-
-      <p>In addition, a new platform for collaborated development is
-	in the works.  A service addon has been created for the GitLab
-	project, which is a drop-in replacement of the popular GitHub
-	website.  The choice was made to host our own solution and not
-	rely on GitHub itself.  In retrospect this appears to have
-	been a good decision.  The recent development where GitHub
-	removed projects after DCMA-takedowns being sent is
-	incompatible with the philosophy of free-flow-of-information,
-	of which the ZFSguru project is a strong proponent.  By
-	hosting our own solution, we have avoided any dependency on
-	third party projects.</p>
-
-      <p>The next task will be to introduce a new remote database
-	structure, dubbed GuruDB.  This will speed up the
-	web-interface as well as introduce Service Bulletins which
-	address important notifications to our users, as well as
-	announce new releases.</p>
-
-      <p>After GuruDB, the Migration Manager is one of the last
-	remaining features still missing in the web-interface.  This
-	functionality provides an easy way to upgrade the current
-	system by performing a new clean installation, but migrate all
-	relevant configuration to the new installation.  It also
-	allows users to 'backup' all system configuration in a single
-	file to be stored on a different machine should things go
-	awry.</p>
-
-      <p>A longer version of the 2014 development progress of the
-	ZFSguru project and information specific to the newly-released
-	10.1-002 system image can be found in the Links section.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Intel-GPU-Driver-Update" href="#Intel-GPU-Driver-Update" id="Intel-GPU-Driver-Update">Intel GPU Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052532.html" title="https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052532.html">Email thread with patch updates and regression test reports.</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052532.html" title="Email thread with patch updates and regression test reports.">https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052532.html</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project to update the Intel graphics chipset driver
-	(i915kms) to a recent snapshot of the Linux upstream code
-	continues.  A patch with a large chunk of updates has been
-	made available to test for regressions against current
-	functionality, but is not yet expected to provide working new
-	functions. The GEM I/O ioctl code path has been modified to
-	more closely resemble the Linux code structure (easing future
-	imports).</p>
-    <p>This project was sponsored by FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Fix any bugs reported against the latest versions of the patch.</p>
-      </li><li>
-	<p>Make Haswell graphics work with Mesa.</p>
-      </li></ol><hr /><h2><a name="SDIO-Driver" href="#SDIO-Driver" id="SDIO-Driver">SDIO Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SDIO" title="https://wiki.freebsd.org/SDIO">SDIO project page on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SDIO" title="SDIO project page on FreeBSD wiki">https://wiki.freebsd.org/SDIO</a></td></tr><tr><td><a href="https://github.com/kibab/freebsd/tree/mmccam" title="https://github.com/kibab/freebsd/tree/mmccam">Source code</a></td><td>
-	    URL: <a href="https://github.com/kibab/freebsd/tree/mmccam" title="Source code">https://github.com/kibab/freebsd/tree/mmccam</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D862" title="https://reviews.freebsd.org/D862">Patch for review</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D862" title="Patch for review">https://reviews.freebsd.org/D862</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>SDIO is an interface designed as an extension of the existing
-	SD card standard, allowing the connection of different peripherals
-	to a host with a standard SD controller.  Peripherals
-	currently sold in the general market include WLAN/BT modules,
-	cameras, fingerprint readers, and barcode scanners.  SDIO is
-	also used to connect some peripherals in products like
-	Chromebooks and Wandboard.</p>
-
-      <p>The current main focus of the project is to reimplement the
-	existing MMC/SD stack using the CAM framework.  This will
-	allow utilizing the well-tested CAM locking model and debug
-	features.</p>
-
-      <p>The first version of the code was uploaded on Phabricator for
-	review.  The new stack is able to attach to the SD card and
-	bring it to an operational state.  The only supported SD
-	controller driver is <tt>ti_sdhci</tt> which is used by the
-	BeagleBone Black.  Modifying other SDHCI-compliant drivers
-	should not be a hard task.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>At this point, feedback from kernel developers is really
-	  needed.  This may be done in the form of code review.  If
-	  the chosen way of implementing the CAM-aware MMC stack is
-	  considered correct, then adding code for interacting with SD
-	  cards (for example, setting the optimal transfer rates) will
-	  be the next task.</p>
-      </li><li>
-	<p>Write a CAM peripheral driver that implements an interface
-	  to the FreeBSD <tt>disk(9)</tt>.  It will send MMC I/O
-	  commands using the MMC XPT layer.</p>
-      </li><li>
-	<p>Extending <tt>camcontrol(8)</tt> to make it possible to
-	  send MMC-specific commands directly to the MMC/SD card using
-	  pass(4) will greatly assist in developing new features for
-	  the stack.</p>
-      </li><li>
-	<p>Modify the <tt>sdhci(4)</tt> driver to work with the new
-	  stack.  This is required to work on the new stack using PC
-	  hardware, not only the BeagleBone Black.</p>
-      </li></ol><hr /><h2><a name="UEFI-Boot" href="#UEFI-Boot" id="UEFI-Boot">UEFI Boot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/UEFI" title="https://wiki.freebsd.org/UEFI">FreeBSD UEFI wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/UEFI" title="FreeBSD UEFI wiki page">https://wiki.freebsd.org/UEFI</a></td></tr><tr><td><a href="http://www.freebsd.org/snapshots/" title="http://www.freebsd.org/snapshots/">FreeBSD�snapshots</a></td><td>
-	    URL: <a href="http://www.freebsd.org/snapshots/" title="FreeBSD�snapshots">http://www.freebsd.org/snapshots/</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Unified Extensible Firmware Interface, or UEFI, provides
-	boot- and run-time services for x86 and other computers.  For
-	the x86 architecture it replaces the legacy BIOS.  This
-	project will adapt the FreeBSD loader and kernel boot process for
-	compatibility with UEFI firmware, found on contemporary
-	servers, desktops, and laptops.</p>
-
-      <p>Over the last three months Ed and others refined the existing
-	UEFI support and merged it to the stable/10 branch for the
-	upcoming FreeBSD 10.1 release.</p>
-
-      <p>To avoid the risk of a regression, the standard FreeBSD 10.1
-	install images continue to use the existing partitioning
-	scheme and support only legacy BIOS boot.  Separate
-	UEFI-enabled installer images will be included with 10.1.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Document manual installation, including dual-boot
-	  configurations.</p>
-      </li><li>
-	<p>Implement boot1.efi for ZFS file systems.</p>
-      </li><li>
-	<p>Add support for UEFI variables stored in non-volatile
-	  memory (NVRAM).</p>
-      </li><li>
-	<p>Debug boot failures with certain UEFI firmware
-	  implementations.</p>
-      </li><li>
-	<p>Support secure boot.</p>
-      </li></ol><hr /><h2><a name="Updated-vt(4)-System-Console" href="#Updated-vt(4)-System-Console" id="Updated-vt(4)-System-Console">Updated vt(4) System Console</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Newcons" title="https://wiki.freebsd.org/Newcons">Project wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Newcons" title="Project wiki page">https://wiki.freebsd.org/Newcons</a></td></tr></table><p>
-	Contact:
-	  Aleksandr
-	  Rybalko
-	 &lt;<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jean-S�bastien
-	  P�dron
-	 &lt;<a href="mailto:dumbbell@FreeBSD.org">dumbbell@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>vt(4)</tt> (aka <tt>Newcons</tt>) project provides
-	a replacement for the legacy <tt>syscons</tt> system console.
-	It brings a number of improvements, including better
-	integration with graphics modes and broader character set
-	support.</p>
-
-      <p>A large number of improvements were committed to
-	<tt>vt(4)</tt> over the last three months.
-	Jean-S�bastien P�dron fixed significant
-	performance regressions observed with <tt>vt_vga</tt>,
-	particularly noticeable on virtual machines.  Stefan Esser
-	converted and cleaned up all of the keyboard map files for use
-	with <tt>vt(4)</tt>.</p>
-
-      <p>The EFI framebuffer driver and the ofwfb driver now work
-	with the xf86-video-scfb X11 video driver, supporting
-	native-resolution (albeit unaccelerated) X.</p>
-
-      <p>The fixes and improvements have all been merged and will be
-	available in the upcoming FreeBSD 10.1 release.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Implement the remaining features supported by
-	  <tt>vidcontrol(1)</tt>.</p>
-      </li><li>
-	<p>Write manual pages for <tt>vt(4)</tt> drivers and kernel
-	  interfaces.</p>
-      </li><li>
-	<p>Support direct handling of keyboards by the <tt>kbd</tt>
-	  device (without <tt>kbdmux(4)</tt>).</p>
-      </li><li>
-	<p>CJK fonts.  This is in progress.</p>
-      </li><li>
-	<p>Switch to <tt>vt(4)</tt> by default.</p>
-      </li><li>
-	<p>Implement compatibility mode to be able to use single-byte
-	  charsets/key-codes in <tt>vt(4)</tt>.</p>
-      </li></ol><hr /><h2><a name="Updating-OpenCrypto" href="#Updating-OpenCrypto" id="Updating-OpenCrypto">Updating OpenCrypto</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/opencrypto" title="https://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/opencrypto">Source in Perforce</a></td><td>
-	    URL: <a href="https://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/opencrypto" title="Source in Perforce">https://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/opencrypto</a></td></tr><tr><td><a href="http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html" title="http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html">FreeBSD Foundation announces IPsec Enhancement Project</a></td><td>
-	    URL: <a href="http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html" title="FreeBSD Foundation announces IPsec Enhancement Project">http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html</a></td></tr></table><p>
-	Contact:
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project adds support for the AES-GCM and AES-CTR
-	cryptography modes to the OpenCrypto framework.  Both software
-	and AES-NI accelerated versions are now functional and
-	working.  Ermal Lu�i (eri@) is working on adding support for
-	these additional modes to IPsec.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, and Netgate.</p><h3>Open tasks:</h3><ol><li>
-	<p>Create a test suite for the most common modes.</p>
-      </li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Newer-ARM-Boards" href="#FreeBSD-on-Newer-ARM-Boards" id="FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/tsgan/qualcomm" title="https://github.com/tsgan/qualcomm">Some preliminary code for Snapdragon board IFC6410</a></td><td>
-	    URL: <a href="https://github.com/tsgan/qualcomm" title="Some preliminary code for Snapdragon board IFC6410">https://github.com/tsgan/qualcomm</a></td></tr></table><p>
-	Contact:
-	  Ganbold
-	  Tsagaankhuu
-	 &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on initial support of the IFC6410 board, which was
-	stopped due to a bricked bootloader, has been started again.
-	This board has the Qualcomm Snapdragon S4 SoC, featuring the
-	Krait CPU.  This CPU is considered a "platform" for use in
-	smartphones, tablets, and smartbook devices.  Krait has many
-	similarities with the ARM Cortex-A15 CPU and is also based on
-	the ARMv7 instruction set.  These peripherals are working:</p>
-
-      <ul>
-	<li>Qualcomm High Speed UART driver for MSM 7000/8000 series
-	  chips (included in <tt>src</tt> tree)</li>
-
-	<li>Krait Timer</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Get the MMC driver working.  May need more help from
-	  experts.</p>
-      </li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/arm64/" title="http://svnweb.freebsd.org/base/projects/arm64/"></a></td><td>
-	    URL: <a href="http://svnweb.freebsd.org/base/projects/arm64/" title="">http://svnweb.freebsd.org/base/projects/arm64/</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Until recently, all ARM CPU designs were 32-bit only.  With
-	the introduction of the ARMv8 architecture, ARM has added a
-	new 64-bit mode.  This new mode has been named AArch64.  Arm64
-	is the name of the in-progress port of FreeBSD to ARMv8 CPUs when
-	in AArch64 mode.</p>
-
-      <p>Since the last status report, FreeBSD has started to execute
-	userland instructions.  This includes implementing more of the
-	needed kernel functions to handle creation of processes.
-	Using clang to compile userland has found a few issues with
-	the version in the base system.  These issues are expected to
-	be resolved when clang 3.5 is imported.</p>
-
-      <p>Initial support for device drivers has been added.  This
-	includes the start of the <tt>bus_space</tt> functions and
-	interrupt handling.  This allowed the existing timer and
-	interrupt controller drivers from armv6 to be used as these
-	devices are similar.  The FDT data is now being passed from
-	the loader to the kernel using the standard mechanism.</p>
-
-      <p>The pmap implementation has been changed to be based on the
-	amd64 code.  This fixes a number of issues with the old
-	implementation.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Boot to multi-user mode</p>
-      </li><li>
-	<p>Get dynamic libraries working</p>
-      </li><li>
-	<p>Test on real hardware</p>
-      </li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="LLDB-Debugger-Port" href="#LLDB-Debugger-Port" id="LLDB-Debugger-Port">LLDB Debugger Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/lldb" title="https://wiki.FreeBSD.org/lldb"></a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/lldb" title="">https://wiki.FreeBSD.org/lldb</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLDB is the debugger project associated with Clang/LLVM.  It
-	supports the Mac OS X, Linux, and FreeBSD platforms, with Windows
-	support under development.  It builds on existing components
-	in the larger LLVM project, for example using Clang's
-	expression parser and LLVM's disassembler.</p>
-
-      <p>Work over the last three months consisted mainly of
-	maintenance, ensuring that the upstream FreeBSD port continues to
-	build and that testsuite failures are promptly addressed.</p>
-
-      <p>I plan to import a new LLDB snapshot after the base system
-	Clang is updated to 3.5.  Some upstream improvements that will
-	be in that import include:</p>
-
-      <ul>
-	<li>Ability to specify a count to thread step-*
-	  operations.</li>
-
-	<li>Ongoing AArch64 development.</li>
-
-	<li>Significant progress on the lldb-gdbserver debug
-	  stub.</li>
-
-	<li>I/O handling improvements.</li>
-
-	<li>A much faster C++ name demangler for most symbols.</li>
-      </ul>
-
-      <p>A proof-of-concept implementation of kernel debugging support
-	for amd64 was completed as part of Google Summer of Code.  It
-	is not ready to be committed, but will form the basis for
-	upcoming kernel debugging support.</p>
-    <p>This project was sponsored by DARPA/AFRL, SRI International, and University of Cambridge.</p><h3>Open tasks:</h3><ol><li>
-	<p>Port remote debug stub (lldb-gdbserver) from Linux to
-	FreeBSD.</p>
-      </li><li>
-	<p>Add support for local and core file kernel debugging.</p>
-      </li><li>
-	<p>Implement, fix or test support on all non-amd64
-	  architectures.</p>
-      </li><li>
-	<p>Verify cross-debugging.</p>
-      </li><li>
-	<p>Investigate and fix test suite failures.</p>
-      </li><li>
-	<p>Package LLDB as a port.</p>
-      </li><li>
-	<p>Enable by default in the base system for working
-	  architectures.</p>
-      </li></ol><hr /><h2><a name="LLVM-Address-Sanitizer-(Asan)" href="#LLVM-Address-Sanitizer-(Asan)" id="LLVM-Address-Sanitizer-(Asan)">LLVM Address Sanitizer (Asan)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://code.google.com/p/address-sanitizer/" title="https://code.google.com/p/address-sanitizer/"></a></td><td>
-	    URL: <a href="https://code.google.com/p/address-sanitizer/" title="">https://code.google.com/p/address-sanitizer/</a></td></tr><tr><td><a href="http://clang.llvm.org/docs/AddressSanitizer.html" title="http://clang.llvm.org/docs/AddressSanitizer.html"></a></td><td>
-	    URL: <a href="http://clang.llvm.org/docs/AddressSanitizer.html" title="">http://clang.llvm.org/docs/AddressSanitizer.html</a></td></tr><tr><td><a href="http://lab.llvm.org:8011/builders/sanitizer_x86_64-freebsd" title="http://lab.llvm.org:8011/builders/sanitizer_x86_64-freebsd">Buildbot</a></td><td>
-	    URL: <a href="http://lab.llvm.org:8011/builders/sanitizer_x86_64-freebsd" title="Buildbot">http://lab.llvm.org:8011/builders/sanitizer_x86_64-freebsd</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060270.html" title="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060270.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060270.html" title="">http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060270.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060504.html" title="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060504.html"></a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060504.html" title="">http://lists.freebsd.org/pipermail/svn-src-head/2014-July/060504.html</a></td></tr></table><p>
-	Contact:
-	  Viktor
-	  Kuzutov
-	 &lt;<a href="mailto:vkutuzov@accesssoftek.com">vkutuzov@accesssoftek.com</a>&gt;
-	</p>
-      <p>The LLVM address sanitizer (Asan) is a fast memory error
-	detector that can detect use-after-free errors and buffer
-	overflows.  It has been ported to FreeBSD.  The mainline version
-	of LLVM is known to pass all of the tests in the LLVM and Asan
-	test suites without unexpected failures on FreeBSD 10.0.</p>
-
-      <p>A buildbot running sanitizer tests under FreeBSD stable/10
-	has been established.  See the Links section.</p>
-
-      <p>To make it possible to run programs with sanitizer
-	checks enabled on FreeBSD, a new sysctl named
-	<tt>kern.proc_vmmap_skip_resident_count</tt> has been added.
-	See the Links section.  Running the address sanitizer checks
-	on stable/10 requires this sysctl to be set to 1.</p>
-
-      <p>A similar work is in progress to add FreeBSD support to the
-	thread sanitizer (Tsan), which detects data races in parallel
-	programs.</p>
-    <hr /><h2><a name="SSE-Variants-of-libc-Routines-for-amd64" href="#SSE-Variants-of-libc-Routines-for-amd64" id="SSE-Variants-of-libc-Routines-for-amd64">SSE Variants of libc Routines for amd64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://trac.baldwin.cx:8080/freebsd/wiki/LibCSSE" title="http://trac.baldwin.cx:8080/freebsd/wiki/LibCSSE"></a></td><td>
-	    URL: <a href="http://trac.baldwin.cx:8080/freebsd/wiki/LibCSSE" title="">http://trac.baldwin.cx:8080/freebsd/wiki/LibCSSE</a></td></tr></table><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have written SSE/AVX-optimized versions of a few
-	<tt>libc</tt> routines for amd64.  So far the list includes
-	<tt>memcpy</tt>, <tt>memset</tt>, and <tt>strlen</tt>.  For
-	each routine I have written a simple regression test as well
-	as performed some simple microbenchmarks on various AMD and
-	Intel CPUs.</p>
-
-      <p>The simplest routine is <tt>strlen</tt> which appears to be a
-	general win in microbenchmarks.  <tt>memcpy</tt> and
-	<tt>memset</tt> have proven trickier as different variants can
-	behave quite differently on different CPUs.</p>
-
-      <p>At present, I do not yet have a patch relative to
-	<tt>libc</tt>.  Once I do, this will be suitable for more
-	testing.  I would like to see some real-world benchmarks that
-	show measurable improvement before pushing any of this up into
-	the tree.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Create a branch that holds a modified <tt>libc</tt> and is
-	  suitable for testing</p>
-      </li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Python-Ports" href="#FreeBSD-Python-Ports" id="FreeBSD-Python-Ports">FreeBSD Python Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Python" title="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Python" title="The FreeBSD Python Team Page">https://wiki.FreeBSD.org/Python</a></td></tr><tr><td><a href="irc://freebsd-python@irc.freenode.net" title="irc://freebsd-python@irc.freenode.net">IRC channel</a></td><td>
-	    URL: <a href="irc://freebsd-python@irc.freenode.net" title="IRC channel">irc://freebsd-python@irc.freenode.net</a></td></tr></table><p>
-	Contact:
-	  FreeBSD
-	  Python Team
-	 &lt;<a href="mailto:python@FreeBSD.org">python@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Python team continued to improve the overall
-	experience with Python-based software on FreeBSD.</p>
-
-      <p>During the last quarter, the <tt>bsd.python.mk</tt> bits of
-	the ports infrastructure were converted to the more modern
-	<tt>USES</tt> format.  Several options, such as support for
-	<tt>easy_install</tt>, were deprecated or removed to make the
-	infrastructure easier to maintain and less complex for
-	port maintainers.</p>
-
-      <p>The Python ports were refactored and simplified to improve
-	maintainability and to get rid of long-standing issues due to the
-	previously complex and error-prone build process.</p>
-
-      <p>The Python 2 branch was updated to Python 2.7.8 and
-	<tt>setuptools</tt> to 5.5.1.</p>
-
-      <p>With the availability of pkg 1.3, installing Python packages
-	and modules for different Python versions is now supported in
-	the package management infrastructure.  This allows us to
-	remove the previously required port duplicates for Python 2
-	and Python 3.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Retire the Python 3 specific port duplicates</p>
-      </li><li>
-	<p>Convert ports to the new <tt>USES</tt> syntax</p>
-      </li><li>
-	<p>More tasks can be found on the team's wiki page (see
-	  Links).</p>
-      </li><li>
-	<p>To get involved, interested people can say hello on IRC
-	  and let us know their areas of interest!</p>
-      </li></ol><hr /><h2><a name="GNOME/FreeBSD" href="#GNOME/FreeBSD" id="GNOME/FreeBSD">GNOME/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/gnome" title="http://www.freebsd.org/gnome"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/gnome" title="">http://www.freebsd.org/gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD"></a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr><tr><td><a href="http://marcuscom.com/downloads/marcusmerge" title="http://marcuscom.com/downloads/marcusmerge"></a></td><td>
-	    URL: <a href="http://marcuscom.com/downloads/marcusmerge" title="">http://marcuscom.com/downloads/marcusmerge</a></td></tr></table><p>
-	Contact:
-	  FreeBSD GNOME Team
-	 &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>GNOME is a desktop environment and graphical user interface
-	that runs on top of a computer operating system.  GNOME is
-	part of the GNU Project and can be used with various Unix-like
-	operating systems, including FreeBSD.</p>
-
-      <p>MATE is a fork of GNOME 2.  The MATE ports were updated to
-	the 1.8 versions.</p>
-
-      <p>Cairo, the vector graphics library used by GNOME, has been
-	updated to 1.12.  This allowed the merge of GNOME 3 to begin.
-	We are currently doing test builds to find ports broken by the
-	update and pruning ports that do not build any more because of
-	incompatible updates.</p>
-
-      <p>Gustau Perez started preliminary work on the next development
-	version of GNOME in MC, to be ready for GNOME 3.15.  We will
-	skip 3.14 entirely.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Finish the GNOME 3.12 merge, and start tracking GNOME 3.15
-	  (development series).</p>
-      </li></ol><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/"></a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://freebsd.kde.org/area51.php" title="https://freebsd.kde.org/area51.php"></a></td><td>
-	    URL: <a href="https://freebsd.kde.org/area51.php" title="">https://freebsd.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.freebsd.org/KDE" title="https://wiki.freebsd.org/KDE"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/KDE" title="">https://wiki.freebsd.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="https://mail.kde.org/mailman/listinfo/kde-freebsd"></a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="">https://mail.kde.org/mailman/listinfo/kde-freebsd</a></td></tr><tr><td><a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="http://portscout.freebsd.org/kde@freebsd.org.html">PortScout</a></td><td>
-	    URL: <a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="PortScout">http://portscout.freebsd.org/kde@freebsd.org.html</a></td></tr></table><p>
-	Contact:
-	  KDE on FreeBSD team
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging and making sure the
-	experience of KDE and Qt on FreeBSD is as good as possible.</p>
-
-      <p>First of all, we are happy to announce that Alonso Schaich,
-	longtime contributor to our experimental area51 repositories,
-	has become a ports committer, mentored by KDE on FreeBSD members
-	Raphael Kubo da Costa (rakuco@) and Max Brazhnikov
-	(makc@).</p>
-
-      <p>During this quarter, the team has kept most of the KDE and Qt
-	ports up-to-date, working on the following releases:</p>
-
-      <ul>
-	<li>CMake 3.0.1 and 3.0.2</li>
-
-	<li>PyQt 4.11.1, SIP 4.16.2, QScintilla 2.8.3</li>
-
-	<li>DigiKam 4.2.0 (in area51)</li>
-
-	<li>KDE 4.13.3, 4.14.0 and 4.14.1 (in area51)</li>
-
-	<li>KDE Telepathy 0.8.0 (in area51)</li>
-      </ul>
-
-      <p>Additionally, work on updating the Qt5 ports to the 5.3
-	series has begun, and we intend to commit the updated ports in
-	our experimental area51 repository to the ports tree in
-	Q4.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Updating out-of-date ports, see the Links Portscout entry
-	  for a list.</p>
-      </li><li>
-	<p>Committing all the updated ports we have been accumulating
-	  in our experimental repositories into the ports tree.</p>
-      </li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk">Graphics stack ports-related development repository</a></td><td>
-	    URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="Graphics stack ports-related development repository">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html" title="http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html">Removal of legacy X.Org announcement</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html" title="Removal of legacy X.Org announcement">http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-October/000096.html</a></td></tr><tr><td><a href="http://wiki.x.org/wiki/Events/XDC2014/" title="http://wiki.x.org/wiki/Events/XDC2014/">XDC 2014</a></td><td>
-	    URL: <a href="http://wiki.x.org/wiki/Events/XDC2014/" title="XDC 2014">http://wiki.x.org/wiki/Events/XDC2014/</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Graphics team
-	 &lt;<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>&gt;
-	</p>
-
-      <p>The newest graphics stack (that is, the set of ports conditional on the
-	<tt>WITH_NEW_XORG</tt> knob) was enabled on all architectures.
-	The only regression is for users of Intel GPUs and FreeBSD 8.X or
-	9.0.  Those releases lack the required kernel driver and
-	therefore <tt>xf86-video-intel</tt> will not work (the last
-	UMS-aware version does not work with xserver 1.12).  Users can
-	still use <tt>xf86-video-vesa</tt> if they cannot or do not
-	want to update their FreeBSD workstation.  Owners of Radeon GPUs
-	can use <tt>xf86-video-ati-ums</tt> 6.14.6 with
-	<tt>xserver</tt> 1.12 if the KMS driver is not available (that
-	is, before FreeBSD 9.3).</p>
-
-      <p>The old graphics stack will be removed with the next update
-	to these ports.  See the announcement in the Links
-	section.</p>
-
-      <p>Hardware context support was added to the i915 driver in both
-	HEAD and 10.1-RELEASE. This will allow us to update libglapi,
-	libGL, dri, libEGL and libglesv2 ports to a newer version of
-	Mesa.  The latest version is already available from our
-	development ports tree (see the links section).</p>
-
-      <p>Cairo was updated to 1.12.  This will allow the FreeBSD GNOME
-	team to upgrade pango and Gtk+ 3.  Unfortunately, the update
-	also revealed that xf86-video-intel 2.7.1 was in a much worse
-	state than previously assumed.</p>
-
-      <p>We will attend XDC 2014 (X.Org Developer's Conference) from
-	October 8th through 10th in Bordeaux, France.  The goal is to
-	reconnect with graphics stack developers, who are mostly working with
-	Linux these days.  We will give a presentation on the current
-	state of this stack on FreeBSD.  See the XDC website in the Links
-	section for the program and live streaming.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>See the "Graphics" wiki page for up-to-date
-	  information.</p>
-      </li></ol><hr /><h2><a name="Xfce" href="#Xfce" id="Xfce">Xfce</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xfce" title="">https://wiki.freebsd.org/Xfce</a></td></tr><tr><td><a href="http://www.redports.org/browser/olivierd/xfce4" title="http://www.redports.org/browser/olivierd/xfce4">devel repo</a></td><td>
-	    URL: <a href="http://www.redports.org/browser/olivierd/xfce4" title="devel repo">http://www.redports.org/browser/olivierd/xfce4</a></td></tr><tr><td><a href="https://people.freebsd.org/~olivierd/xfce4-4.11-screencast.webm" title="https://people.freebsd.org/~olivierd/xfce4-4.11-screencast.webm">Video showing significant changes</a></td><td>
-	    URL: <a href="https://people.freebsd.org/~olivierd/xfce4-4.11-screencast.webm" title="Video showing significant changes">https://people.freebsd.org/~olivierd/xfce4-4.11-screencast.webm</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Xfce Team
-	 &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms including FreeBSD.  It aims to be fast and
-	lightweight while still being visually appealing and easy to
-	use.</p>
-
-      <p>The Xfce team continues to keep each piece of the Xfce
-	Desktop up to date.  That is why we are working on the next
-	stable release (no date scheduled).  There were no major
-	updates in the ports tree except for cosmetic changes this
-	quarter.</p>
-
-      <p>Major upcoming changes include:</p>
-
-      <ul>
-	<li>Switch to the <tt>USES</tt> framework</li>
-
-	<li>Support both GTK2 and GTK3, with GTK2 being the
-	  default.</li>
-
-	<li>A GNOME-like default icons theme</li>
-
-	<li>Enhanced documentation (handbooks, FAQ)</li>
-      </ul>
-
-      <p>Below is a list of current ports in the devel repository (see
-	link).</p>
-
-      <ul>
-	<li>deskutils/xfce4-xkb-plugin 0.7.0</li>
-
-	<li>devel/xfce4-dev-tools 4.11.0</li>
-
-	<li>misc/xfce4-appfinder 4.11.0</li>
-
-	<li>multimedia/xfce4-parole 0.6.1 and 0.7.0</li>
-
-	<li>sysutils/garcon 0.3.0</li>
-
-	<li>sysutils/xfce4-settings 4.11.3</li>
-
-	<li>x11/libxfce4menu 4.11.1</li>
-
-	<li>x11/libxfce4util 4.11.0</li>
-
-	<li>x11-wm/xfce4-desktop 4.11.8</li>
-
-	<li>x11-wm/xfce4-panel 4.11.1</li>
-
-	<li>x11-wm/xfce4-session 4.11.0</li>
-      </ul>
-
-      <p>There are also two new ports</p>
-
-      <ul>
-	<li>deskutils/xfce4-volumed-pulse 0.2.0</li>
-
-	<li>x11/xfce4-dashboard 0.2.3 and 0.3.2</li>
-      </ul>
-
-      <p>For more details, please see our wiki page in the Links
-	section.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Finish patching the ACPI helper (xfce4-power-manager).</p>
-      </li><li>
-	<p>Continue to work on documentation, especially the Porter's
-	  Handbook, and creata a FAQ).</p>
-      </li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Handbook-ezjail-Section" href="#Handbook-ezjail-Section" id="Handbook-ezjail-Section">Handbook ezjail Section</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-ezjail.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-ezjail.html">Managing Jails with ezjail</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-ezjail.html" title="Managing Jails with ezjail">https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-ezjail.html</a></td></tr></table><p>
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>ezjail</tt> is a very popular jails management utility,
-	but was only mentioned in passing in the Handbook.  This new
-	section describes basic setup and usage.  An in-depth example
-	shows how to create and configure a jail.  It also serves as
-	an example of how to run a simple caching-only BIND in a
-	jail.</p>
-    <hr /><h2><a name="Michael-Lucas-Books" href="#Michael-Lucas-Books" id="Michael-Lucas-Books">Michael Lucas Books</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://blather.michaelwlucas.com/archives/2088" title="http://blather.michaelwlucas.com/archives/2088">book announcement</a></td><td>
-	    URL: <a href="http://blather.michaelwlucas.com/archives/2088" title="book announcement">http://blather.michaelwlucas.com/archives/2088</a></td></tr><tr><td><a href="http://blather.michaelwlucas.com/archives/2119" title="http://blather.michaelwlucas.com/archives/2119">pre-pub availability announcement</a></td><td>
-	    URL: <a href="http://blather.michaelwlucas.com/archives/2119" title="pre-pub availability announcement">http://blather.michaelwlucas.com/archives/2119</a></td></tr><tr><td><a href="https://www.tiltedwindmillpress.com/?product=freebsd-mastery-storage-essentials" title="https://www.tiltedwindmillpress.com/?product=freebsd-mastery-storage-essentials">in-progress draft</a></td><td>
-	    URL: <a href="https://www.tiltedwindmillpress.com/?product=freebsd-mastery-storage-essentials" title="in-progress draft">https://www.tiltedwindmillpress.com/?product=freebsd-mastery-storage-essentials</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	</p>
-      <p>Lucas is working on a series of small FreeBSD books.  The
-	first one, FreeBSD Mastery: Storage Essentials, is underway,
-	and covers GEOM, gpart, MBR, UFS, GELI, GBDE, disk sector
-	alignment, and more.  You can pre-order the book at a discount
-	from his web site, or wait for it to hit print and all major
-	ebook retailers.</p>
-
-      <p>Get status updates on his blog, or check @mwlauthor on
-	Twitter.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Lucas needs to write faster.</p>
-      </li></ol><hr /><h2><a name="ZFS-Chapter-of-the-Handbook" href="#ZFS-Chapter-of-the-Handbook" id="ZFS-Chapter-of-the-Handbook">ZFS Chapter of the Handbook</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/zfs.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/zfs.html">ZFS Section of the FreeBSD Handbook</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/zfs.html" title="ZFS Section of the FreeBSD Handbook">https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/zfs.html</a></td></tr></table><p>
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:allanjude@FreeBSD.org">allanjude@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>ZFS is one of the premier features of FreeBSD, and the quality
-	of the documentation should match that of other important
-	features.  Much of the original documentation from Sun and
-	Oracle has disappeared, moved, or is about the proprietary
-	version of ZFS.  The OpenZFS project does not provide much
-	documentation and instead provides users with a few links,
-	including the FreeBSD Handbook.  New users have many questions
-	about ZFS and yet there exists a great deal more bad advice
-	about ZFS than proper documentation.</p>
-
-      <p>After over a year of work, a new ZFS chapter has been added
-	to the FreeBSD Handbook.  Over 20,000 words describe the basics
-	of creating, managing, and maintaining a ZFS pool.  Advanced
-	features like compression, deduplication, and delegation are
-	covered.  The chapter also contains a glossary of terms,
-	explaining a number of the concepts unique to ZFS, and
-	documents some of the many <tt>sysctl</tt> variables that can
-	be used for tuning.</p>
-
-      <p>The remaining work to be done is in the FAQ section, which
-	aims to help users address the most common questions or
-	problems they might face with ZFS.  We would like to hear
-	experiences, questions, misconceptions, gotchas, stumbling
-	blocks and suggestions for the FAQ section from other users.
-	A use cases section that highlights some of the cases where
-	ZFS provides advantages over traditional file systems is also
-	planned.</p>
-
-      <p>Please send suggestions to the docs mailing list.</p>
-    <p>This project was sponsored by ScaleEngine Inc..</p><h3>Open tasks:</h3><ol><li>
-	<p>Technical review by Matt Ahrens (co-creator of
-	  ZFS)</p>
-      </li><li>
-	<p>Improve the delegation section</p>
-      </li><li>
-	<p>Improve the tuning section, and cover recently added sysctls</p>
-      </li><li>
-	<p>Add a section on jails and the jailed property</p>
-      </li><li>
-	<p>Add an FAQ section</p>
-      </li><li>
-	<p>Add a Use Cases section</p>
-      </li><li>
-	<p>General editing and review</p>
-      </li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD�Project
-	and community worldwide.  Most of the funding is used to
-	support FreeBSD development projects, conferences, and developer
-	summits, purchase equipment to grow and improve the FreeBSD
-	infrastructure, and provide legal support for the Project.</p>
-
-      <p>We published our fourth issue of the FreeBSD Journal.  We
-	have over 4500 subscriptions to date.  Work continued on
-	adding support for the Dynamic Edition which will be available
-	soon.  The fifth issue is also due out soon.</p>
-
-      <p>Foundation staff member Konstantin Belousov wrapped up the
-	PostgreSQL performance investigation project.  Kostik reran
-	the benchmarks as a configuration error may have affected
-	earlier results.  Improvements arising from the investigation
-	are merged to the FreeBSD 10 development branch and will be in
-	the 10.1 release.  Kostik also committed a variety of virtual
-	memory and file system bug fixes and improvements.</p>
-
-      <p>Over the quarter, Foundation staff member Edward Napiera&#322;a
-	refined the new autofs-based automounter and incorporated
-	feedback from testers in enterprise and university contexts.
-	The automounter is available in the development branch of
-	FreeBSD and will be included in FreeBSD 10.1.  Edward also
-	supported engineers at Chelsio in preparing iSCSI offload
-	support for Chelsio's 10- and 40-gigabit per second Ethernet
-	adapters.</p>
-
-      <p>Ed Maste, our project manager, tested and integrated UEFI
-	system boot and new vt(4) console work into the release branch
-	for the upcoming FreeBSD 10.1 release.  He committed a number
-	of small toolchain and build infrastructure improvements.  He
-	also wrote an article on LLDB for the FreeBSD Journal and
-	presented the LLDB work at EuroBSDCon.</p>
-
-      <p>FreeBSD Foundation Systems Administrator and Release Engineer
-	Glen Barber continued work on finalizing the 9.3-RELEASE
-	process, followed by starting the 10.1-RELEASE process.</p>
-
-      <p>Work has continued on producing regularly-updated FreeBSD
-	development snapshot builds for the various supported
-	architectures, which include amd64, i386, ia64, powerpc,
-	powerpc64, sparc64, and arm.</p>
-
-      <p>In addition, work has been committed to a project branch
-	which allows FreeBSD virtual machine disk images to be produced
-	by default as part of the release process.</p>
-
-      <p>A plan has been put together for the upcoming Secure Boot work.</p>
-
-      <p>More hardware has been purchased to support FreeBSD infrastructure at NYI
-	and Sentex.</p>
-
-      <p>We announced a collaboration between the Foundation and Cavium to
-	deliver a FreeBSD ARMv8 based implementation.</p>
-
-      <p>We signed a license agreement with Oracle to get access to the
-	TCKs for Java 7 and 8.</p>
-
-      <p>Robert Watson ran and organized the Cambridge Developer
-	Summit.  We provided a travel grant to a Google Summer of Code
-	student to attend the summit.</p>
-
-      <p>We provided a travel grant to a developer who organized and ran
-	BSDDay in Argentina.</p>
-
-      <p>We were a Gold Sponsor for EuroBSDCon 2014 and sponsored the
-	Developer Summit.  We provided 4 travel grants to assist FreeBSD
-	contributors with their travel expenses to attend the
-	conference.  We also had 6 board/staff members attend the
-	conference and some gave talks, tutorials, and chaired some
-	sessions.  We held our Fall Fundraising campaign there and
-	raised over $2,000 in donations from attendees.</p>
-
-      <p>We organized the Silicon Valley Vendor/Developer Summit that is
-	happening November 3 and 4.</p>
-
-      <p>Kirk McKusick, Robert Watson, and George Neville-Neil
-	published the second edition of "The Design and Implementation
-	of the FreeBSD Operating System."</p>
-
-      <p>Kirk McKusick presented a 2-day tutorial on the FreeBSD kernel
-	and gave a talk on the implementation of ZFS at EuroBSDCon.</p>
-
-      <p>Dru Lavigne attended Fossetcon: September 11-13
-	(fossetcon.org).</p>
-
-      <p>We created new recruiting fliers for upcoming events,
-	including the Grace Hopper conference.</p>
-
-      <p>We started sending out Foundation monthly update emails to keep
-	the FreeBSD community informed on some of the activities we did
-	the previous month to support FreeBSD.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2014-10-2014-12.html b/website/content/en/status/report-2014-10-2014-12.html
deleted file mode 100644
index 021b2e7cab..0000000000
--- a/website/content/en/status/report-2014-10-2014-12.html
+++ /dev/null
@@ -1,2131 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between October and
-      December 2014.  This is the last of four reports planned for
-      2014.</p><p>The fourth quarter of 2014 included a number of significant
-      improvements to the FreeBSD system.  In particular, compatibility
-      with other systems was enhanced.  This included significant
-      improvements to the Linux compatibility layer, used to run Linux
-      binaries on FreeBSD, and the port of WINE, used to run Windows
-      applications.  Hypervisor support improved, with FreeBSD gaining
-      the ability to run as domain 0 on Xen's new high-performance PVH
-      mode, bhyve gaining AMD support, and new tools for creating FreeBSD
-      VM images arriving.</p><p>This quarter was also an active time for the toolchain, with
-      numerous improvements to the compiler, debugger, and other
-      components, including initial support for C++14, which should be
-      complete by FreeBSD�10.2.</p><p>Thanks to all the reporters for the excellent work!</p><p>The deadline for submissions covering the period from January
-      to March 2015 is April 7th, 2015.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#bhyve">bhyve</a></li><li><a href="#Clang,-llvm,-and-lldb-Updated-to-3.5.0">Clang, llvm, and lldb Updated to 3.5.0</a></li><li><a href="#External-Toolchain">External Toolchain</a></li><li><a href="#FreeBSD-on-Google-Cloud">FreeBSD on Google Cloud</a></li><li><a href="#FreeBSD-on-the-Acer-C720-Chromebook">FreeBSD on the Acer C720 Chromebook</a></li><li><a href="#Git-Integration">Git Integration</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li><li><a href="#Migration-to-ELF-Tool-Chain-Tools">Migration to ELF Tool Chain Tools</a></li><li><a href="#pkg(8)">pkg(8)</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD-Xen">FreeBSD Xen</a></li><li><a href="#Linux-Emulation-Layer,-the-Linuxulator">Linux Emulation Layer, the Linuxulator</a></li><li><a href="#PCI-SR-IOV-Infrastructure">PCI SR-IOV Infrastructure</a></li><li><a href="#Process-Management">Process Management</a></li><li><a href="#Secure-Boot">Secure Boot</a></li><li><a href="#Timer-Function-Support-for-Linuxulator">Timer Function Support for Linuxulator</a></li><li><a href="#Updating-OpenCrypto">Updating OpenCrypto</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-POWER8">FreeBSD on POWER8</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#libxo:-Generate-Text,-XML,-JSON,-and-HTML-Output">libxo: Generate Text, XML, JSON, and HTML Output</a></li><li><a href="#mandoc(1)-Support">mandoc(1) Support</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#GNOME-on-FreeBSD">GNOME on FreeBSD</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Linux-Emulation-Ports">Linux Emulation Ports</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#Xfce">Xfce</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#More-Michael-Lucas-Books">More Michael Lucas Books</a></li><li><a href="#New-Translators-Mailing-List">New Translators Mailing List</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#Creating-Vagrant-Images-with-Packer">Creating Vagrant Images with Packer</a></li><li><a href="#FreeBSD-Forum-Software-Migration">FreeBSD Forum Software Migration</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD�10.1-RELEASE cycle completed on November 14th,
-	marking the second official release point from the
-	<tt>stable/10</tt> branch, just short of three weeks later
-	than the original schedule anticipated.</p>
-
-      <p>Work to produce virtual machine images for platforms not
-	currently supported has continued, with focus aimed primarily
-	at Amazon EC2, Google Compute Engine, and Openstack.</p>
-
-      <p>With huge thanks to Ian Lepore and Warner Losh, new ports exist for
-	FreeBSD/arm where u-boot is required.  Work has been in progress
-	since late December to migrate the existing FreeBSD/arm release
-	build tools to utilize the new ports.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://portscout.freebsd.org/" title="http://portscout.freebsd.org/"></a></td><td>
-	    URL: <a href="http://portscout.freebsd.org/" title="">http://portscout.freebsd.org/</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Port Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of Q4 the ports tree holds more than 24,000
-	ports, and the PR count is just over 1,400.  As during the
-	previous quarter the tree saw a sustained activity with
-	almost 6,000 commits and more than 1,600 ports PRs closed!</p>
-
-      <p>In Q4, five new developers were granted a ports commit bit
-	(gordon@, jmg@, jmmv@, bofh@, truckman@) and six were taken
-	in for safekeeping (sylvio@, pclin@, flz@, jsa@, anders@,
-	motoyuki@).</p>
-
-      <p>On the management side, miwi@ decided to step down from his
-	portmgr duties in November.  No other changes were made to the
-	team during Q4.</p>
-
-      <p>This quarter also saw the release of the fourth quarterly
-	branch, namely 2014Q4.</p>
-
-      <p>On the QA side, 39 exp-runs were performed to validate
-	sensitive updates or cleanups.</p>
-
-    <h3>Open tasks:</h3><ol><li>
-	<p>A tremendous work was done on the PR front in Q4 and we
-	  would be very pleased to see committers dedicate themselves
-	  to closing as many as possible in 2015 as well!</p>
-      </li><li>
-	<p>2014 is the year that saw the highest number of commits
-	  in all of our ports tree's history!  As for the PR front and
-	  to keep our beloved tree in good shape, we would love to see
-	  the same commitment from our developers next year!</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team constitutes the project's "Board of
-	Directors", responsible for deciding the project's overall
-	goals and direction as well as managing specific areas of the
-	FreeBSD project landscape.</p>
-
-      <p>During the fourth quarter of 2014, the FreeBSD Core team saw the
-	culmination of a long-running project to rebuild the FreeBSD
-	Forums.  The chosen solution was to license XenForo; core
-	would like to thank the FreeBSD Foundation for paying the
-	licensing costs of this software.</p>
-
-      <p>Much discussion ensued concerning the "New Support Model"
-	following Core's meeting at EuroBSDCon in September.  It was
-	recognised that trying to change the model immediately before
-	10.1-RELEASE was far too late, and the change will be targeted
-	at 11.0-RELEASE.</p>
-
-      <p>In order to ensure that 10.1-RELEASE shipped with support for
-	up-to-date X Window Systems and KDE4, core approved the switch to
-	'new Xorg' as the default in time for building the packages
-	for that release.</p>
-
-      <p>Git was officially promoted from beta to an officially
-	supported version control system.  Git is available as a
-	read-only resource for downstream consumers and contains an
-	exported copy from SVN, the primary and only read-write
-	repository.  The FreeBSD git repositories (exported from the
-	master SVN version control) will shortly be available at
-	https://git.freebsd.org/, and core has been active in ensuring
-	that there is a sufficient body of Git administrators
-	available with access to appropriate documentation in order to
-	maintain a good git service.</p>
-
-      <p>Core mediated in disputes between a number of committers over
-	some updates to system sources, and fielded complaints about
-	code quality of some other work in critical areas.  While such
-	disagreements will occasionally occur, core is promoting the
-	routine use of the Phabricator service in order to review work
-	before committal.  Catching problems early is in the project's
-	best interests, and discussion of changes in an open review
-	context should minimize confrontational demands for immediate
-	back-out of changes.</p>
-
-      <p>Core is working on a charter for a proposed new QA team, to
-	encompass members of the Release Engineering and Security
-	teams, as well as committers with interests in standards
-	compliance.  It is envisioned that the QA team will take
-	responsibility for merging code from HEAD into the STABLE
-	branches, run integration testing against those updates and
-	handle merging patches and bug-fixes submitted to the FreeBSD
-	project from third parties.</p>
-
-      <p>During this quarter, core issued two new commit bits, and
-	also took two commit bits into safe-keeping.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="bhyve" href="#bhyve" id="bhyve">bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bhyve.org" title="http://www.bhyve.org">bhyve FAQ and talks</a></td><td>
-	    URL: <a href="http://www.bhyve.org" title="bhyve FAQ and talks">http://www.bhyve.org</a></td></tr></table><p>
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Neel
-	  Natu
-	 &lt;<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Tycho
-	  Nightingale
-	 &lt;<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>&gt;
-	</p>
-      <p>bhyve is a hypervisor that runs on the FreeBSD/amd64
-	platform.  At present, it runs FreeBSD (8.x or later), Linux
-	i386/x64, OpenBSD i386/amd64, and NetBSD/amd64 guests.
-	Current development is focused on enabling additional guest
-	operating systems and implementing features found in other
-	hypervisors.</p>
-
-      <p>Support for AMD processors was committed to -CURRENT in
-	October 2014.  This has also been merged to 10-STABLE and will
-	be included in the 10.2 release.</p>
-
-      <p>A bhyve status update presentation was given at the FreeBSD
-	Vendor Summit in Nov 2014. The slides are available at
-	<url href="http://people.freebsd.org/~neel/bhyve/bhyve_update_vendor_summit_2014.pdf">http://people.freebsd.org/~neel/bhyve/bhyve_update_vendor_summit_2014.pdf</url>.</p>
-
-      <p>A number of improvements have been made to bhyve this
-	quarter:</p>
-
-      <ul>
-	<li>OpenBSD/i386 guests are now able to boot with multiple
-	  vcpus.</li>
-
-	<li>NetBSD/amd64 guests are now fully supported.</li>
-
-	<li>Improvements to the AHCI emulation to be more resilient
-	  under heavy load.</li>
-
-	<li>Various improvements to PIC emulation to be able to boot
-	  legacy guests.</li>
-
-	<li>A fully featured RTC device emulation that allows
-	  date/time changes by the guest and supports periodic and
-	  alarm interrupts.</li>
-
-	<li>Consolidate all timer emulations in vmm.ko.  This enables
-	  the use of a single clocksource for all timer
-	  emulations.</li>
-
-	<li>Allow tracing of every exception incurred by a guest.
-	  This is useful when debugging guest double and triple
-	  faults.</li>
-
-	<li>Emulate platform-specific MSRs accessed by recent Linux
-	  guests.</li>
-
-	<li>Various bug fixes to grub-bhyve to boot OpenBSD/i386 and
-	  Centos 4.x guests.</li>
-
-	<li>grub-bhyve is now able to connect to an nmdm(4) console
-	  using the <tt>--cons-dev</tt> option.</li> </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Improve documentation.</p>
-      </li><li>
-	<p>bhyveucl is a script for starting bhyve instances based
-	  on a libUCL config file.  More information at
-	  <url href="https://github.com/allanjude/bhyveucl">https://github.com/allanjude/bhyveucl</url>.</p>
-      </li><li>
-	<p>CSM BIOS boot support for non UEFI-aware guests.</p>
-      </li><li>
-	<p>Add support for virtio-scsi.</p>
-      </li><li>
-	<p>Improve virtio-net, add offload features, support multiple
-	  queues.</p>
-      </li><li>
-	<p>Implement Intel 82580 and e1000 NIC emulation.</p>
-      </li><li>
-	<p>Netmap support.</p>
-      </li><li>
-	<p>Flexible networking backend: wanproxy, vhost-net.</p>
-      </li><li>
-	<p>Move to a single process model, instead of bhyveload +
-	  bhyve.</p>
-      </li><li>
-	<p>Support running bhyve as non-root.</p>
-      </li><li>
-	<p>Add filters for popular VM file formats (VMDK, VHD,
-	  QCOW2).</p>
-      </li><li>
-	<p>Implement an abstraction layer for video (no X11 or SDL in
-	  base system).</p>
-      </li><li>
-	<p>Support for VNC as a video output.</p>
-      </li><li>
-	<p>Suspend/resume support.</p>
-      </li><li>
-	<p>Live Migration.</p>
-      </li><li>
-	<p>Nested VT-x support (bhyve in bhyve).</p>
-      </li><li>
-	<p>Support for other architectures (ARM, MIPS, PPC).</p>
-      </li></ol><hr /><h2><a name="Clang,-llvm,-and-lldb-Updated-to-3.5.0" href="#Clang,-llvm,-and-lldb-Updated-to-3.5.0" id="Clang,-llvm,-and-lldb-Updated-to-3.5.0">Clang, llvm, and lldb Updated to 3.5.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://llvm.org/releases/3.5.0/docs/ReleaseNotes.html" title="http://llvm.org/releases/3.5.0/docs/ReleaseNotes.html">LLVM 3.5.0 Release Notes</a></td><td>
-	    URL: <a href="http://llvm.org/releases/3.5.0/docs/ReleaseNotes.html" title="LLVM 3.5.0 Release Notes">http://llvm.org/releases/3.5.0/docs/ReleaseNotes.html</a></td></tr><tr><td><a href="http://llvm.org/releases/3.5.0/tools/clang/docs/ReleaseNotes.html" title="http://llvm.org/releases/3.5.0/tools/clang/docs/ReleaseNotes.html">Clang 3.5.0 Release Notes</a></td><td>
-	    URL: <a href="http://llvm.org/releases/3.5.0/tools/clang/docs/ReleaseNotes.html" title="Clang 3.5.0 Release Notes">http://llvm.org/releases/3.5.0/tools/clang/docs/ReleaseNotes.html</a></td></tr></table><p>
-	Contact:
-	  Dimitry
-	  Andric
-	 &lt;<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	</p>
-      <p>Just before the end of the year, we updated clang, llvm, and
-	lldb in the base system to 3.5.0 release.  These all contain
-	numerous improvements.  Please see the linked release notes
-	for more detailed information.</p>
-
-      <p>This is the first release that requires C++11 support to
-	build.  At this point, FreeBSD 10.0 and later provide that
-	support, at least on x86.</p>
-
-      <p>In the near future, more components from llvm.org will be
-	updated in base, with libc++ and libcompiler-rt most likely
-	being the first to be updated.</p>
-
-      <p>Thanks to Ed Maste, Roman Divacky, Andrew Turner, Justin
-	Hibbits, and Antoine Brodin for their invaluable help with
-	this import.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>While most ports that were impacted by this update have
-	  already been fixed, there are still a few that do not work
-	  with the clang 3.5.0 update.</p>
-
-	<p>In most cases, this is due to relatively simple issues,
-	  such as new warnings, or slightly stricter error checking
-	  (primarily for C++ programs).  Fixing those issues should
-	  not take too much work.</p>
-      </li><li>
-	<p>There are still some open issues with the ARM, PowerPC,
-	  and Sparc64 architectures, and any help in this area is very
-	  much appreciated.</p>
-      </li></ol><hr /><h2><a name="External-Toolchain" href="#External-Toolchain" id="External-Toolchain">External Toolchain</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/ExternalToolchain" title="https://wiki.freebsd.org/ExternalToolchain"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/ExternalToolchain" title="">https://wiki.freebsd.org/ExternalToolchain</a></td></tr></table><p>
-	Contact:
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>The main goal of the external toolchain project is to be able
-	to build world and kernel with a non-default toolchain.  It can
-	be helpful to:
-	<ul>
-	  <li>Prepare a migration to a newer version of toolchain
-	    components.</li>
-
-	  <li>Port FreeBSD to a new architecture</li>
-
-	  <li>Upgrade from a FreeBSD that ships with GCC 4.2 to a version
-	    that ships with clang 3.5+ (which needs a more modern
-	    toolchain than GCC 4.2 to bootstrap).</li>
-	</ul>
-      </p>
-
-      <p>The initial external toolchain work only supported clang.  It
-	has been extended to support recent GCC (4.9.1 has been
-	tested) and recent binutils (2.24 and 2.25).</p>
-
-      <p>A large number of fixes have been committed to HEAD to
-	support incompatible behaviour changes between <tt>ld(1)</tt>
-	from binutils 2.17.50 (the version in base) and binutils
-	2.24+.</p>
-
-      <p>A large number of warnings have been deactivated when
-	building the kernel to make sure it is possible to build the
-	kernel with recent GCC (first 4.6 and then 4.9.1)</p>
-
-      <p>The build system has been changed to build libc++ as the C++
-	standard library implementation when a recent enough GCC
-	(4.6+) is used to build world.</p>
-
-      <p>To simplify using an external toolchain, the following
-	pre-seeded configurations have been added to the ports tree:
-	<ul>
-	  <li>amd64-xtoolchain-gcc</li>
-
-	  <li>powerpc64-xtoolchain-gcc</li>
-
-	  <li>sparc64-xtoolchain-gcc</li>
-	</ul>
-      </p>
-
-      <p>Those packages will depend on special versions of GCC
-	(minimalistic cross-built ready GCC) and on binutils.  To use
-	them, run: <tt>make CROSS_TOOLCHAIN=powerpc64-gcc
-	  TARGET=powerpc TARGET_ARCH=powerpc64</tt></p>
-
-      <p>As a result of this effort, it is possible to
-	successfully build and run a kernel and world built with GCC
-	4.9.1 and binutils 2.24 on sparc64, amd64 (with minor tweaks),
-	powerpc and powerpc64.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Patch GCC 4.9 to support FreeBSD mips, arm and aarch64 and
-	  submit the patches to upstream.</p>
-      </li><li>
-	<p>Adapt and upstream the aarch64 patches for binutils
-	  2.25.</p>
-      </li><li>
-	<p>Add more pre-seeded configurations.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-on-Google-Cloud" href="#FreeBSD-on-Google-Cloud" id="FreeBSD-on-Google-Cloud">FreeBSD on Google Cloud</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/swills/FreeBSD-gcloud" title="https://github.com/swills/FreeBSD-gcloud">The script used to create gcloud images</a></td><td>
-	    URL: <a href="https://github.com/swills/FreeBSD-gcloud" title="The script used to create gcloud images">https://github.com/swills/FreeBSD-gcloud</a></td></tr><tr><td><a href="https://plus.google.com/112202779615695172291/posts/eYajb8JKerY" title="https://plus.google.com/112202779615695172291/posts/eYajb8JKerY">More detail on how to create and use a gcloud image</a></td><td>
-	    URL: <a href="https://plus.google.com/112202779615695172291/posts/eYajb8JKerY" title="More detail on how to create and use a gcloud image">https://plus.google.com/112202779615695172291/posts/eYajb8JKerY</a></td></tr></table><p>
-	Contact:
-	  Steve
-	  Wills
-	 &lt;<a href="mailto:swills@FreeBSD.org">swills@FreeBSD.org</a>&gt;
-	</p>
-      <p>Google Cloud is a cloud computing platform that allows users to
-	run hosted services and servers in a cloud maintained by
-	Google.  The goal of this project is to provide an easy way to
-	create and manage FreeBSD installations running on Google
-	Cloud.</p>
-
-      <p>The good news:</p>
-
-      <p>FreeBSD 10.1 runs fine. You can create an image and start it
-	up and login via standard ssh, via the <tt>gcloud</tt> command
-	or via the web console (ssh in a web browser window). More
-	details on how to do all this can be found in the links.
-	Basically, you should be able to <tt>gcutil addimage
-	  freebsd-101-release-amd64-20150101032704
-	  gs://swills-test-bucket/FreeBSD-10.1-RELEASE-amd64-20150101032704.tar.gz</tt></p>
-
-      <p>Then spin up an image using <tt>gcloud compute instances
-	  create --zone us-central1-b --image
-	  freebsd-101-release-amd64-20150101032704 --boot-disk-size 20GB
-	  gtest1</tt></p>
-
-      <p>These commands are part of the google-cloud-sdk port, which
-	contains all the commands to interact with Google Cloud. There
-	is also a google-daemon port which is used in running instances to
-	create users and set them up and a google-startup-scripts port which
-	handles running startup/shutdown scripts as specified in node
-	metadata.</p>
-
-      <p>Additionally, the firstboot-growfs port has been brought back so
-	that new instances will grow their root filesystem. (Thanks to Colin
-	Percival for having created that port initially.)</p>
-
-      <p>There is also a firstboot-freebsd-update port which can be used
-	to update a system on first boot but is currently disabled (see
-	below).  Similarly, the firstboot-pkgs port/scripts will install
-	specified packages on first boot.</p>
-
-      <p>Overall, Google Cloud Compute is quite nice; instances spin up
-	in about 60 seconds and it is very reasonably priced with
-	automatic discounts for longer term usage.  There is a $300 credit
-	for first time users that also makes it free to try out.  That
-	credit covers quite a lot of time, and the instances are pretty
-	fast, as well, even the ones without SSDs.</p>
-
-      <p>The bad news:</p>
-
-      <p>Google does not make sharing non-official images as easy as
-	AWS, so you have to create your own using my public tar file. The
-	tar file was created using the script in the links section.  That
-	script can be used to produce customized images, even though there
-	are no official image (nor will there be any time soon).</p>
-
-      <p>There are some issues running FreeBSD on Google Cloud,
-	listed in the tasks section.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The 8 and 16 cpu instances seem to reboot randomly.</p>
-      </li><li>
-	<p>Repeated UFS panics that Google folks have reported, but
-	  I do not think those are particular to Google Cloud. The panic
-	  message is "ffs_valloc dup alloc".</p>
-      </li><li>
-	<p>Running freebsd-update causes the system to become
-	  unbootable, so updates do not work. (Reboots work fine
-	  otherwise.)</p>
-      </li><li>
-	<p>There is no <tt>gcimagebundle</tt> command in the Ports
-	  Collection so you cannot easily create an image from a running
-	  machine.</p>
-      </li><li>
-	<p>There are a few minor issue with the startup script
-	  that is supposed to regenerate ssh keys (for when you
-	  create an image from an existing system).</p>
-      </li><li>
-	<p>10.1 works, but 10.0 does not boot; other versions remain
-	  untested.</p>
-      </li><li>
-	<p>The kern.vm_guest sysctl node does not detect that it is in a
-	  guest.</p>
-      </li><li>
-	<p>The vtnet driver needs wq disabled on 16 cpu boxes, but it
-	  is just disabled everywhere for now since that is easier.</p>
-      </li><li>
-	<p>There is work needed for the Google
-	  <tt>safe_format_and_mount</tt> command which formats and
-	  mounts newly attached disks, but this is just a nicety really.</p>
-      </li><li>
-	<p>I need to look into irq affinity for vtnet.</p>
-      </li><li>
-	<p>We need to support virtualized clocks; bryanv@ is
-	  working on this. In fact, all his ongoing work in the
-	  virtualization area would probably make things work better.</p>
-      </li><li>
-	<p>It would be nice if there was the ability to disable the
-	  spinner before the loader, which clutters up the console log.  The
-	  ability to disable it is in HEAD; hopefully it will be MFCd to
-	  10-STABLE before 10.2.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-on-the-Acer-C720-Chromebook" href="#FreeBSD-on-the-Acer-C720-Chromebook" id="FreeBSD-on-the-Acer-C720-Chromebook">FreeBSD on the Acer C720 Chromebook</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://blog.grem.de/pages/c720.html" title="http://blog.grem.de/pages/c720.html"></a></td><td>
-	    URL: <a href="http://blog.grem.de/pages/c720.html" title="">http://blog.grem.de/pages/c720.html</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Gmelin
-	 &lt;<a href="mailto:freebsd@grem.de">freebsd@grem.de</a>&gt;
-	</p>
-      <p>The Acer C720 Chromebook is a powerful but inexpensive laptop
-	designed to run Google's Chrome OS.  This project aims to
-	bring FreeBSD to the C720, providing an easy way for people to
-	experience FreeBSD on hardware which is widely available and
-	inexpensive.</p>
-
-      <p>As of this update, most system features work, including the
-	keyboard, WiFi, sound, VESA graphics, touchpad, and USB.  The battery
-	life is a reasonable 5 to 6 hours (compare to the published 8.5 hour
-	lifetime for Chrome OS.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Streamline patches and merge them into HEAD.</p>
-      </li><li>
-	<p>Make suspend/resume work (depends on Haswell support).</p>
-      </li></ol><hr /><h2><a name="Git-Integration" href="#Git-Integration" id="Git-Integration">Git Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="https://lists.freebsd.org/mailman/listinfo/freebsd-git"></a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="">https://lists.freebsd.org/mailman/listinfo/freebsd-git</a></td></tr><tr><td><a href="https://www.kernel.org/pub/software/scm/git/docs/git-svn.html" title="https://www.kernel.org/pub/software/scm/git/docs/git-svn.html"></a></td><td>
-	    URL: <a href="https://www.kernel.org/pub/software/scm/git/docs/git-svn.html" title="">https://www.kernel.org/pub/software/scm/git/docs/git-svn.html</a></td></tr><tr><td><a href="https://github.com/git/git/commit/83c9433e679635f8fbf8961081ea3581c93ca778" title="https://github.com/git/git/commit/83c9433e679635f8fbf8961081ea3581c93ca778"></a></td><td>
-	    URL: <a href="https://github.com/git/git/commit/83c9433e679635f8fbf8961081ea3581c93ca778" title="">https://github.com/git/git/commit/83c9433e679635f8fbf8961081ea3581c93ca778</a></td></tr><tr><td><a href="https://wiki.freebsd.org/GitWorkflow" title="https://wiki.freebsd.org/GitWorkflow"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/GitWorkflow" title="">https://wiki.freebsd.org/GitWorkflow</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd" title="https://github.com/freebsd/freebsd"></a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd" title="">https://github.com/freebsd/freebsd</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla" title="https://bugs.freebsd.org/bugzilla"></a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla" title="">https://bugs.freebsd.org/bugzilla</a></td></tr></table><p>
-	Contact: Git discussion list &lt;<a href="mailto:freebsd-git@FreeBSD.org">freebsd-git@FreeBSD.org</a>&gt;
-	</p>
-      <p>Several FreeBSD developers have expressed interest in improving
-	the tools and documentation to facilitate the use of the Git
-	source code management (SCM) system when working with FreeBSD
-	code.  Some highlights of the work in this area include the
-	following:</p>
-
-      <ul>
-	<li>At Alfred Perlstein's request, a new mailing list
-	  freebsd-git@FreeBSD.org was created for discussion of
-	  git use in the FreeBSD project.</li>
-
-	<li>Alfred Perlstein submitted a patch to git.  This patch allows a
-	  developer to work on a source code tree in git and use
-	  git-svn to push changes from this tree directly to a
-	  Subversion repository and set Subversion properties.  Before
-	  this patch, git-svn did not properly set Subversion
-	  properties.  This is important for FreeBSD developers because
-	  the FreeBSD Subversion repo will block commits which do not
-	  properly set certain Subversion properties.  The git project
-	  accepted this change in changeset 83c9433.</li>
-
-	<li>Alfred Perlstein updated the Git Workflow wiki document to
-	  include information for using git-svn to commit to the
-	  FreeBSD Subversion repository.</li>
-
-	<li>Bartek Rutkowski wrote a script which integrates Github and FreeBSD
-	  Bugzilla.  When a user files a Github pull request against
-	  the FreeBSD source code tree on Github, this script will open a
-	  new PR in FreeBSD Bugzilla.  This will allow users to
-	  contribute code and patches via Github pull requests, and
-	  have the request tracked by FreeBSD developers in Bugzilla.
-	  Github pull requests cannot currently be directly merged
-	  into the FreeBSD source tree on Github, because the main source
-	  code repository is currently Subversion.  The FreeBSD source
-	  code tree on Github is a read-only mirror of the FreeBSD
-	  Subversion repository.  Craig Rodrigues coordinated with
-	  Bartek Rutkowski and bugmeister@FreeBSD.org to move forward on
-	  this, and provide Bartek Rutkowski with enough access to Bugzilla
-	  to open PR's via a script.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The Github integration script is not deployed yet and is
-	  not active for all pull requests against the FreeBSD source
-	  tree on Github.  Bartek Rutkowski and bugmeister@FreeBSD.org need
-	  to work out the final details for deploying this script into
-	  production.  The script must be accessible via HTTP POST
-	  requests because it uses the Github REST API.  Bartek Rutkowski and
-	  bugmeister@FreeBSD.org need to reach agreement on where this
-	  script lives, and do a security audit.</p>
-      </li></ol><hr /><h2><a name="Jenkins-Continuous-Integration-for-FreeBSD" href="#Jenkins-Continuous-Integration-for-FreeBSD" id="Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://jenkins.freebsd.org" title="https://jenkins.freebsd.org">Jenkins CI server in FreeBSD cluster</a></td><td>
-	    URL: <a href="https://jenkins.freebsd.org" title="Jenkins CI server in FreeBSD cluster">https://jenkins.freebsd.org</a></td></tr><tr><td><a href="http://jenkins-ci.org/content/freebsd-project-use-jenkins-os-testing" title="http://jenkins-ci.org/content/freebsd-project-use-jenkins-os-testing">FreeBSD and Jenkins OS Testing</a></td><td>
-	    URL: <a href="http://jenkins-ci.org/content/freebsd-project-use-jenkins-os-testing" title="FreeBSD and Jenkins OS Testing">http://jenkins-ci.org/content/freebsd-project-use-jenkins-os-testing</a></td></tr><tr><td><a href="https://wiki.freebsd.org/201411DevAndVendorSummit?action=AttachFile&amp;do=view&amp;target=kyua_jenkins.pdf" title="https://wiki.freebsd.org/201411DevAndVendorSummit?action=AttachFile&amp;do=view&amp;target=kyua_jenkins.pdf">Kyua and Jenkins Testing Framework for BSD</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/201411DevAndVendorSummit?action=AttachFile&amp;do=view&amp;target=kyua_jenkins.pdf" title="Kyua and Jenkins Testing Framework for BSD">https://wiki.freebsd.org/201411DevAndVendorSummit?action=AttachFile&amp;do=view&amp;target=kyua_jenkins.pdf</a></td></tr><tr><td><a href="https://issues.jenkins-ci.org/browse/JENKINS-21507" title="https://issues.jenkins-ci.org/browse/JENKINS-21507">PAM authentication problems in FreeBSD</a></td><td>
-	    URL: <a href="https://issues.jenkins-ci.org/browse/JENKINS-21507" title="PAM authentication problems in FreeBSD">https://issues.jenkins-ci.org/browse/JENKINS-21507</a></td></tr><tr><td><a href="https://issues.jenkins-ci.org/browse/JENKINS-24521" title="https://issues.jenkins-ci.org/browse/JENKINS-24521">Issue to update Jenkins to JNA 4.1.0 for FreeBSD</a></td><td>
-	    URL: <a href="https://issues.jenkins-ci.org/browse/JENKINS-24521" title="Issue to update Jenkins to JNA 4.1.0 for FreeBSD">https://issues.jenkins-ci.org/browse/JENKINS-24521</a></td></tr><tr><td><a href="https://github.com/rodrigc/kyua/wiki/Quickstart-Guide" title="https://github.com/rodrigc/kyua/wiki/Quickstart-Guide">Kyua Quickstart Guide</a></td><td>
-	    URL: <a href="https://github.com/rodrigc/kyua/wiki/Quickstart-Guide" title="Kyua Quickstart Guide">https://github.com/rodrigc/kyua/wiki/Quickstart-Guide</a></td></tr><tr><td><a href="http://www.freshports.org/textproc/igor/" title="http://www.freshports.org/textproc/igor/">Igor tool for proofreading documentation</a></td><td>
-	    URL: <a href="http://www.freshports.org/textproc/igor/" title="Igor tool for proofreading documentation">http://www.freshports.org/textproc/igor/</a></td></tr><tr><td><a href="https://jenkins.freebsd.org/job/FreeBSD_Doc-igor" title="https://jenkins.freebsd.org/job/FreeBSD_Doc-igor">FreeBSD_Doc-igor Jenkins build</a></td><td>
-	    URL: <a href="https://jenkins.freebsd.org/job/FreeBSD_Doc-igor" title="FreeBSD_Doc-igor Jenkins build">https://jenkins.freebsd.org/job/FreeBSD_Doc-igor</a></td></tr><tr><td><a href="https://jenkins.freebsd.org/job/FreeBSD_HEAD_sparc64/" title="https://jenkins.freebsd.org/job/FreeBSD_HEAD_sparc64/">FreeBSD_HEAD_sparc64 Jenkins build</a></td><td>
-	    URL: <a href="https://jenkins.freebsd.org/job/FreeBSD_HEAD_sparc64/" title="FreeBSD_HEAD_sparc64 Jenkins build">https://jenkins.freebsd.org/job/FreeBSD_HEAD_sparc64/</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-testing/2014-November/000609.html" title="https://lists.freebsd.org/pipermail/freebsd-testing/2014-November/000609.html">Susan Stanziano from Xinuous ran kyua tests</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-testing/2014-November/000609.html" title="Susan Stanziano from Xinuous ran kyua tests">https://lists.freebsd.org/pipermail/freebsd-testing/2014-November/000609.html</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-testing/2014-December/000697.html" title="https://lists.freebsd.org/pipermail/freebsd-testing/2014-December/000697.html">Andy Zhang from Microsoft ran kyua tests</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-testing/2014-December/000697.html" title="Andy Zhang from Microsoft ran kyua tests">https://lists.freebsd.org/pipermail/freebsd-testing/2014-December/000697.html</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092212.html" title="https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092212.html">Ngie Cooper imported NetBSD tests</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092212.html" title="Ngie Cooper imported NetBSD tests">https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092212.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000713.html" title="http://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000713.html">Steve Wills ran tests in Google Compute Engine</a></td><td>
-	    URL: <a href="http://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000713.html" title="Steve Wills ran tests in Google Compute Engine">http://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000713.html</a></td></tr><tr><td><a href="https://github.com/Homebrew/homebrew/pull/32346" title="https://github.com/Homebrew/homebrew/pull/32346">Kyua submitted to Homebrew project</a></td><td>
-	    URL: <a href="https://github.com/Homebrew/homebrew/pull/32346" title="Kyua submitted to Homebrew project">https://github.com/Homebrew/homebrew/pull/32346</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci/pull/3" title="https://github.com/freebsd/freebsd-ci/pull/3">Brian Gardner submits jtreg tests</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci/pull/3" title="Brian Gardner submits jtreg tests">https://github.com/freebsd/freebsd-ci/pull/3</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000723.html" title="https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000723.html">Ahmed Kamal offers to help with Saltstack</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000723.html" title="Ahmed Kamal offers to help with Saltstack">https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000723.html</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000722.html" title="https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000722.html">MIPS builds</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000722.html" title="MIPS builds">https://lists.freebsd.org/pipermail/freebsd-testing/2015-January/000722.html</a></td></tr></table><p>
-	Contact:
-	  Craig
-	  Rodrigues
-	 &lt;<a href="mailto:rodrigc@FreeBSD.org">rodrigc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jenkins Administrators &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Testing &lt;<a href="mailto:freebsd-testing@FreeBSD.org">freebsd-testing@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report, many people have contributed
-	help in various areas to help with Continuous Integration
-	and Testing in FreeBSD.  Some of the highlights include:</p>
-
-      <ul>
-	<li>The Jenkins project mentioned on their blog how FreeBSD is
-	  using Jenkins and kyua to run OS-level tests.</li>
-
-	<li>Craig Rodrigues submitted patches to upgrade Jenkins to use
-	  JNA 4.1.0.  The Jenkins project accepted these patches
-	  [JENKINS-24521] in the Jenkins 1.586 release.  This fixed
-	  problems with PAM authentication support in Jenkins on
-	  FreeBSD [JENKINS-21507].</li>
-
-	<li>Craig Rodrigues gave a presentation "Kyua and Jenkins Testing
-	  Framework" for BSD at the Developer and Vendor summit on
-	  November 3, 2014 in San Jose, California.  In the
-	  presentation, Craig Rodrigues described how, for every commit to
-	  the FreeBSD source tree, nearly 3000 tests are run using
-	  kyua inside a bhyve virtual machine.  The kyua test results
-	  are exported to JUnit XML format, which is then used by
-	  Jenkins to generate web-based test reports with graphs.</li>
-
-	<li>Li-Wen Hsu set up a Jenkins build named FreeBSD_Doc-igor
-	  to run the Igor tool written by Warren Block.  Igor proofreads
-	  FreeBSD documentation and reports various errors.</li>
-
-	<li>Craig Rodrigues set up a Jenkins build named
-	  FreeBSD_HEAD_sparc64 to build the FreeBSD HEAD branch for
-	  the sparc64 architecture</li>
-
-	<li>Ngie Cooper imported more tests from NetBSD.  After this
-	  import, there are now over 3000 tests in the /usr/tests
-	  directory.</li>
-
-	<li>Susan Stanziano from Xinuous ran kyua tests and provided
-	  feedback about test errors, running the tests in a bhyve
-	  VM.</li>
-
-	<li>Andy Zhang from Microsoft ran kyua tests and provided
-	  feedback about test errors running in a Hyper-V 2012R2
-	  VM.</li>
-
-	<li>Steve Wills ran the FreeBSD tests in Google Compute Engine and
-	  provided the test results.</li>
-
-	<li>Craig Rodrigues submitted a formula to create a package for
-	  kyua in the Homebrew packaging system on OS X.  The Homebrew
-	  project accepted this.  Now, kyua can easily be installed on
-	  OS X via a Homebrew package.  Hopefully this will make it
-	  easier to share more test infrastructure and scripts with OS
-	  X.</li>
-
-	<li>Craig Rodrigues submitted to the Debian project a kyua
-	  package.  Approval for this is still pending.  A package
-	  will make it much easier to install kyua on Linux
-	  distributions which use Debian packages such as Debian,
-	  Ubuntu, and Linux Mint.  Hopefully this will make it
-	  easier to share more test infrastructure and scripts with
-	  Linux.</li>
-
-	<li>Brian Gardner submitted scripts to run the Regression Test
-	  Harness for OpenJDK (jtreg).  The test results are in JUnit
-	  XML format, which can be natively imported into
-	  Jenkins.</li>
-
-	<li>Ahmed Kamal, an experienced devops expert and past
-	  contributor to the Ubuntu project, offered to help
-	  Craig Rodrigues with improving the automation and deployment of
-	  Jenkins nodes in the FreeBSD cluster using the Saltstack
-	  automation framework.  Ahmed is interested in helping the
-	  FreeBSD project.</li>
-
-	<li>Craig Rodrigues worked with Adrian Chadd to set up Jenkins
-	  builds of MIPS targets.  The next step will be to get kyua
-	  tests running inside a QEMU MIPS VM.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Set up more builds based on different architectures.</p>
-      </li><li>
-	<p>Improve the maintenance of nodes in the Jenkins cluster
-	  using devops frameworks such as Saltstack.</p>
-      </li><li>
-	<p>Get feedback for improving the Kyua Quickstart Guide.</p>
-      </li><li>
-	<p>People interested in helping out should join the
-	  freebsd-testing@FreeBSD.org list.</p>
-      </li></ol><hr /><h2><a name="Migration-to-ELF-Tool-Chain-Tools" href="#Migration-to-ELF-Tool-Chain-Tools" id="Migration-to-ELF-Tool-Chain-Tools">Migration to ELF Tool Chain Tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://elftoolchain.sourceforge.net" title="http://elftoolchain.sourceforge.net"></a></td><td>
-	    URL: <a href="http://elftoolchain.sourceforge.net" title="">http://elftoolchain.sourceforge.net</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	</p>
-      <p>The ELF Tool Chain project provides BSD-licensed
-	implementations of compilation tools and libraries for
-	building and analyzing ELF objects.  It started as part of
-	FreeBSD but has moved to a standalone project to encourage wider
-	participation from others in the open-source developer
-	community.  FreeBSD's libelf and libdwarf are now imported from
-	upstream sources in contrib/elftoolchain.</p>
-
-      <p>ELF Tool Chain provides a set of tools equivalent to the
-	GNU Binutils suite.  This project's goal is to import these
-	tools into the FreeBSD base system so that we have a set of
-	up-to-date and maintained tools that also provide support for
-	new CPU architectures of interest, such as arm64.</p>
-
-      <p>The following tools have now been imported and are available
-	by setting the src.conf knob WITH_ELFTOOLCHAIN_TOOLS=yes:</p>
-
-      <ul>
-	<li>addr2line</li>
-
-	<li>nm</li>
-
-	<li>size</li>
-
-	<li>strings</li>
-
-	<li>strip (elfcopy)</li>
-      </ul>
-
-      <p>A ports exp-run uncovered some bugs in these tools.  The
-	bugs are being fixed in the FreeBSD source tree and are in the
-	process of being committed to the upstream project.</p>
-
-      <p>ELF Tool Chain's readelf will be enabled as well once some
-	missing functionality in ELF note parsing is added.  ELF Tool
-	Chain's elfcopy provides equivalent functionality to Binutils'
-	objcopy, and accepts the same command-line arguments.  For it
-	to be a viable replacement for all uses of objcopy in the base
-	system, it must gain support for writing portable exectuable
-	(PE) format binaries, which are used by UEFI boot code.</p>
-
-      <p>The ELF Tool Chain project does not currently provide
-	replacements for as, ld, and objdump.  For FreeBSD these tools
-	will likely be obtained from the LLVM project.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Import readelf.</p>
-      </li><li>
-	<p>Add missing functionality to readelf.</p>
-      </li><li>
-	<p>Add missing functionality to elfcopy and migrate the base
-	  system build.</p>
-      </li><li>
-	<p>Fix issues found by fuzzing inputs to the tools.</p>
-      </li><li>
-	<p>Switch the default to WITH_ELFTOOLCHAIN_TOOLS.</p>
-      </li></ol><hr /><h2><a name="pkg(8)" href="#pkg(8)" id="pkg(8)">pkg(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/pkg" title="https://github.com/freebsd/pkg"></a></td><td>
-	    URL: <a href="https://github.com/freebsd/pkg" title="">https://github.com/freebsd/pkg</a></td></tr></table><p>
-	Contact: The pkg team &lt;<a href="mailto:pkg@FreeBSD.org">pkg@FreeBSD.org</a>&gt;
-	</p>
-      <p>The package development team has released <tt>pkg(8)</tt>
-	1.4.  This release fixes lots of bugs and adds some new
-	features:
-	<ul>
-	  <li>Stricter checking of paths passed via the plist</li>
-
-	  <li>Change the ABI string to be closer to MACHINE_ARCH</li>
-
-	  <li>Add three-way merge functionality</li>
-
-	  <li>Add conservative upgrade support for multi repository
-	    configurations</li>
-
-	  <li>Multirepository priority</li>
-	</ul>
-      </p>
-
-      <p>An important part of the development direction for the 1.4
-	release was stabilizing the existing features and improving
-	the <tt>pkg(8)</tt> experience on small/embedded machines
-	(reducing memory usage and speeding up operations).</p>
-
-      <p><tt>pkg(8)</tt> is not only the FreeBSD Package Manager, but
-	also the Package Manager for DragonflyBSD.  Support has been
-	added to build <tt>pkg(8)</tt> on OS X and Linux.  This work
-	will allow other Operating Systems the option of adopting
-	<tt>pkg(8)</tt> to manage their packages and bring new
-	developers into the project.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Add more regression tests.</p>
-      </li><li>
-	<p>Package the FreeBSD base system.</p>
-      </li><li>
-	<p>Allow using mtree as a plist when creating a package.</p>
-      </li><li>
-	<p>Implement flexible dependencies.</p>
-      </li><li>
-	<p>Test the development branch.</p>
-      </li><li>
-	<p>More developers are needed, check the Issues on Github.</p>
-      </li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="FreeBSD-Xen" href="#FreeBSD-Xen" id="FreeBSD-Xen">FreeBSD Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="http://wiki.xen.org/wiki/FreeBSD_PVH">FreeBSD PVH DomU wiki page</a></td><td>
-	    URL: <a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="FreeBSD PVH DomU wiki page">http://wiki.xen.org/wiki/FreeBSD_PVH</a></td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="http://wiki.xen.org/wiki/FreeBSD_Dom0">FreeBSD PVH Dom0 wiki page</a></td><td>
-	    URL: <a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="FreeBSD PVH Dom0 wiki page">http://wiki.xen.org/wiki/FreeBSD_Dom0</a></td></tr></table><p>
-	Contact:
-	  Roger
-	  Pau Monn�
-	 &lt;<a href="mailto:royger@FreeBSD.org">royger@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Justin T.
-	  Gibbs
-	 &lt;<a href="mailto:gibbs@FreeBSD.org">gibbs@FreeBSD.org</a>&gt;
-	</p>
-      <p>During this quarter almost all pending Xen changes have been
-	committed, enabling FreeBSD to be used as Dom0 under the new PVH
-	mode.  The set of features supported by FreeBSD is still limited,
-	but it should allow for basic usage of FreeBSD as Dom0.  Support
-	for booting Xen from the FreeBSD boot loader will be committed
-	very soon to HEAD.</p>
-
-      <p>Apart from testing on a variety of hardware, work has now
-	shifted to improve PVH support in Xen itself in order to have
-	feature parity with a traditional PV Dom0 and to declare the
-	PVH ABI as stable.</p>
-
-      <p>Regarding guest improvements (running FreeBSD as a DomU),
-	there is also ongoing work to add unmapped IO support to Xen
-	blkfront, which is blocked pending some modifications to the
-	generic bounce buffer code.</p>
-    <p>This project was sponsored by Citrix Systems R&amp;D, and Spectra Logic Corporation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Test on different hardware.</p>
-      </li><li>
-	<p>Improve the performance of the netback and blkback
-	  backends.</p>
-      </li><li>
-	<p>Work with upstream Xen to improve PVH and make it
-	  stable.</p>
-      </li><li>
-	<p>Improve generic bounce buffer code for unmapped bios in
-	  order to support blkfront alignment requirements.</p>
-      </li></ol><hr /><h2><a name="Linux-Emulation-Layer,-the-Linuxulator" href="#Linux-Emulation-Layer,-the-Linuxulator" id="Linux-Emulation-Layer,-the-Linuxulator">Linux Emulation Layer, the Linuxulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base/user/dchagin/lemul/" title="https://svnweb.freebsd.org/base/user/dchagin/lemul/"></a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base/user/dchagin/lemul/" title="">https://svnweb.freebsd.org/base/user/dchagin/lemul/</a></td></tr><tr><td><a href="https://reviews.freebsd.org/differential/query/i9Ua2XMYQtNX/" title="https://reviews.freebsd.org/differential/query/i9Ua2XMYQtNX/"></a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/differential/query/i9Ua2XMYQtNX/" title="">https://reviews.freebsd.org/differential/query/i9Ua2XMYQtNX/</a></td></tr></table><p>
-	Contact:
-	  Dmitry
-	  Chagin
-	 &lt;<a href="mailto:dchagin@FreeBSD.org">dchagin@FreeBSD.org</a>&gt;
-	</p>
-      <p>The main goal of the Linux emulation layer project
-	is the execution on FreeBSD of
-	multithreaded Linux applications that require the glibc
-	library version 2.20 or later to be available.  Glibc
-	2.20 requires a Linux kernel (or emulation thereof) of version
-	2.6.32 or later.  The main obstacle preventing this is that
-	the current Linuxulator uses native FreeBSD processes for
-	emulating Linux threads.  This leads to several problems,
-	including problems with process reparenting and dethreading,
-	<tt>wait()</tt> and signal handling.  It would be much better
-	to reuse the FreeBSD kernel code for thread management than to
-	create a completely new codebase for pseudothread management
-	in the Linuxulator.</p>
-
-      <p>At present, the linux emulation layer project has implemented
-	all of the necessary system calls for supporting glibc 2.20,
-	and more, bringing the emulated Linux kernel version to
-	2.6.32:</p>
-
-      <ul>
-	<li>Using native threads for emulating Linux threads</li>
-
-	<li>Implemented VDSO support, including DWARF for signal
-	  trampolines, which are needed for stack unwinding in
-	  <tt>pthread_cancel()</tt></li>
-
-	<li>Implemented the "vsyscall hack", used by some
-	  Linux-based distributions, including CentOS 6</li>
-
-	<li>Implemented the <tt>epoll()</tt> system call
-	  emulation</li>
-
-	<li>Added support for x86_64</li>
-
-	<li>Many bugs were fixed</li>
-      </ul>
-
-      <p>The project's code is located in the FreeBSD Project's
-	Subversion repository at <tt>base/user/dchagin/lemul</tt> (a
-	little bit old).  To facilitate merging the improvements back
-	to head, several patches have been placed on
-	reviews.FreeBSD.org with the tag <tt>#lemul</tt>.  Nearly half
-	of the patches have already been approved by Ed Maste and
-	Edward Tomasz Napiera&#322;a.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Review and merge the lemul branch to head within the next
-	  month or two.</p>
-      </li><li>
-	<p>Implement native and Linuxulator <tt>inotify()</tt>
-	  system calls.</p>
-      </li><li>
-	<p>Implement the <tt>ptrace()</tt> system call for the x86_64
-	  Linuxulator.</p>
-      </li><li>
-	<p>Implement the <tt>signalfd()</tt> and <tt>timerfd()</tt>
-	  system calls for the Linuxulator.</p>
-      </li><li>
-	<p>Implement Priority Inheritance Futexes for
-	  the Linuxulator.</p>
-      </li><li>
-	<p>Extend xucred support, required for many Linux
-	  applications.</p>
-      </li></ol><hr /><h2><a name="PCI-SR-IOV-Infrastructure" href="#PCI-SR-IOV-Infrastructure" id="PCI-SR-IOV-Infrastructure">PCI SR-IOV Infrastructure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/rysto32/freebsd/commits/iov_ixl" title="https://github.com/rysto32/freebsd/commits/iov_ixl"></a></td><td>
-	    URL: <a href="https://github.com/rysto32/freebsd/commits/iov_ixl" title="">https://github.com/rysto32/freebsd/commits/iov_ixl</a></td></tr></table><p>
-	Contact:
-	  Ryan
-	  Stone
-	 &lt;<a href="mailto:rstone@FreeBSD.org">rstone@FreeBSD.org</a>&gt;
-	</p>
-      <p>PCI Single Root I/O Virtualization (SR-IOV) is an optional
-	part of the PCIe standard that provides hardware acceleration
-	for the virtualization of PCIe devices.  When SR-IOV is in
-	use, a function in a PCI device (known as a Physical Function,
-	or PF) will present multiple Virtual PCI Functions (VF) on the
-	PCI bus.  These VFs are fully independent PCI devices that
-	have access to the resources of the PF.  For example, on a
-	network interface card, VFs could transmit and receive packets
-	independently of the PF.</p>
-
-      <p>The most obvious use case for SR-IOV is virtualization.  A
-	hypervisor like bhyve could instantiate a VF for every VM and
-	use PCI passthrough to assign the VFs to the VMs.  This would
-	allow multiple VMs to share access to the PCI device without
-	having to do any expensive communication with the hypervisor,
-	greatly increasing the performance of I/O within a
-	VM.</p>
-
-      <p>Work on the core PCI infrastructure is complete and
-	undergoing review.  Currently it is planned to commit the PCI
-	infrastructure to head by the end of January.</p>
-
-      <p>In addition to the PCI infrastructure, individual PCI drivers
-	must be extended to implement SR-IOV.  An SR-IOV
-	implementation is in progress for the ixl(4) driver, which
-	supports the Intel XL710 family of 40G and 10G NICs.
-	Currently it is planned to have this in review by the end of
-	January.  An implementation for ixgbe(4) is also in progress,
-	but there is no timeline for completion.</p>
-    <p>This project was sponsored by Sandvine Inc..</p><hr /><h2><a name="Process-Management" href="#Process-Management" id="Process-Management">Process Management</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Peter
-	  Holm
-	 &lt;<a href="mailto:pho@FreeBSD.org">pho@FreeBSD.org</a>&gt;
-	</p>
-      <p>There were several improvements made to FreeBSD's process
-	management last quarter.</p>
-
-      <p>The Reaper facility was added, allowing a process to reliably
-	track the running and exiting state of the whole subtree of
-	its processes.  It is intended to improve tools like
-	timeout(1) or poudriere, by making it impossible for a
-	runaway grandchild to escape the controlling process.  The
-	feature was designed based on similar facilities in
-	DragonFlyBSD and Linux, with some references to Solaris
-	contracts.  Committed to HEAD in r275800.</p>
-
-      <p>The FreeBSD suspension code does not ensure that the system,
-	both software and hardware, is in a steady and consistent
-	state.  One aspect is usermode process activity, which is not
-	yet stopped, continuing to making requests to the hardware.
-	It is not realistic to expect drivers to be able to correctly
-	handle the calls after SUSPEND_CHILD.</p>
-
-      <p>We developed a facility to stop usermode threads at safe
-	points, where they are known to not own and to not wait for
-	kernel resources, in particular, not waiting for device
-	requests finishing.  It is based on the existing
-	single-threading code, but extending it to allow external
-	thread to put some processes into stopped state.  Also, a
-	facility to sync filesystems before suspend was added, to
-	ensure that consistent metadata and as much as possible of the
-	cached user data are on stable storage, to minimize the damage
-	that could be caused by a failed resume.</p>
-
-      <p>The code stressed some parts of the system and has led to
-	discovery of a number of bugs in different areas, including
-	process management, buffer cache, and syscall handlers.  The
-	bugs were fixed, and the fixes and features commmitted by a
-	series culminating in r275745.</p>
-
-      <p>During the work described above, it was noted that process
-	spinlock duties are significantly overloaded (the same is true
-	for the process lock).  The spinlock was split into
-	per-feature locks in r275121.  As a result, it was also possible
-	to eliminate recursion on it in r275372.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Secure-Boot" href="#Secure-Boot" id="Secure-Boot">Secure Boot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SecureBoot" title="https://wiki.freebsd.org/SecureBoot"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SecureBoot" title="">https://wiki.freebsd.org/SecureBoot</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>UEFI Secure Boot is a mechanism that requires boot drivers
-	and operating system loaders to be cryptographically signed by
-	an authorized key.  It will refuse to execute any software
-	that is not correctly signed, and is intended to secure boot
-	drivers and operating system loaders from malicious tampering
-	or replacement.</p>
-
-      <p>This project will deliver the initial phase of secure boot
-	support for FreeBSD and consists of:</p>
-
-      <ul>
-	<li>creating ports/packages of the gnu-efi toolchain,
-	  Matthew Garrett's shim loader, and sbsigntools</li>
-
-	<li>extending the shim to provide an API for boot1.efi to
-	  load and verify binaries signed by keys known to the
-	  shim</li>
-
-	<li>writing uefisign(8), a BSD-licensed utility to sign EFI
-	  binaries using Authenticode, as mandated by the UEFI
-	  specification.</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Ensure that the signature format properly matches UEFI spec
-	  requirements.</p>
-      </li><li>
-	<p>Verify that correctly signed, incorrectly signed, and
-	  unsigned loader components are handled properly.</p>
-      </li><li>
-	<p>Investigate signed kernel ELF objects (including
-	  modules).</p>
-      </li></ol><hr /><h2><a name="Timer-Function-Support-for-Linuxulator" href="#Timer-Function-Support-for-Linuxulator" id="Timer-Function-Support-for-Linuxulator">Timer Function Support for Linuxulator</a></h2><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since 2006, initial support for Linux timer function
-	compatibility support was present but untested.  This update
-	corrects the initial implementation and makes it available to
-	the 32-bit Linuxulator on amd64, not just on i386.</p>
-
-      <p>Starting with FreeBSD 10.1, this enables users to run another
-	FPGA high-level synthesis toolchain and emulation platform
-	on a FreeBSD system.
-      </p>
-    <p>This project was sponsored by DARPA, and AFRL.</p><hr /><h2><a name="Updating-OpenCrypto" href="#Updating-OpenCrypto" id="Updating-OpenCrypto">Updating OpenCrypto</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/r275732" title="https://svnweb.freebsd.org/changeset/base/r275732">r275732 changeset</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/r275732" title="r275732 changeset">https://svnweb.freebsd.org/changeset/base/r275732</a></td></tr><tr><td><a href="http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html" title="http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html">FreeBSD Foundation announces IPsec Enhancement Project</a></td><td>
-	    URL: <a href="http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html" title="FreeBSD Foundation announces IPsec Enhancement Project">http://freebsdfoundation.blogspot.com/2014/08/freebsd-foundation-announces-ipsec.html</a></td></tr></table><p>
-	Contact:
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project adds support for AES-GCM and AES-CTR modes to the
-	OpenCrypto framework.  Both software and AES-NI accelerated
-	versions are functional, working and committed.  Ermal Lu�i
-	(eri@) is working on adding support for the additional modes
-	to IPsec.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, and Netgate.</p><h3>Open tasks:</h3><ol><li>
-	<p>Commit the port that provides the NIST KAT vectors so that
-	  the tests committed can run.</p>
-      </li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-POWER8" href="#FreeBSD-on-POWER8" id="FreeBSD-on-POWER8">FreeBSD on POWER8</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/POWER8" title="https://wiki.freebsd.org/POWER8"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/POWER8" title="">https://wiki.freebsd.org/POWER8</a></td></tr><tr><td><a href="http://www.tyan.com/campaign/openpower/" title="http://www.tyan.com/campaign/openpower/"></a></td><td>
-	    URL: <a href="http://www.tyan.com/campaign/openpower/" title="">http://www.tyan.com/campaign/openpower/</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@freebsd.org">nwhitehorn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Justin
-	  Hibbits
-	 &lt;<a href="mailto:jhibbits@freebsd.org">jhibbits@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@freebsd.org">adrian@freebsd.org</a>&gt;
-	</p>
-      <p>IBM and the OpenPOWER Foundation are pushing for a wider
-	software and hardware ecosystem for POWER8-based systems.
-	Beginning January 3, we have been doing bringup work on a Tyan
-	GN70-BP010 POWER8 server, a quad-core 3 GHz system with 32
-	hardware threads.</p>
-
-      <p>The main target for the port is the PowerKVM hypervisor
-	provided on OpenPOWER hardware.  This uses the same software
-	interfaces as the PowerVM hypervisor already supported on
-	earlier POWER hardware.  The target is to have this operation
-	mode fully supported by FreeBSD 10.2.  FreeBSD currently runs under
-	the hypervisor when using a mass storage driver other than the
-	built-in virtualized SCSI; the issues with the SCSI driver
-	should be solved shortly.</p>
-
-      <p>The longer-term goal is to also operate on the bare system.
-	This requires interaction with the OPAL system firmware and
-	the development of device drivers for the on-board PCI,
-	console, and interrupt controller hardware.  As of January 4,
-	the FreeBSD kernel had printed initial messages to the
-	console.</p>
-    <p>This project was sponsored by FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Fix virtualized SCSI driver in PowerKVM.</p>
-      </li><li>
-	<p>Write OPAL drivers.</p>
-      </li><li>
-	<p>Integrate loader(8) with petitboot bootloader.</p>
-      </li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/arm64" title="https://wiki.freebsd.org/arm64"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/arm64" title="">https://wiki.freebsd.org/arm64</a></td></tr><tr><td><a href="https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev" title="https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev"></a></td><td>
-	    URL: <a href="https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev" title="">https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	</p>
-      <p>There is growing interest in ARM's 64-bit architecture.
-	Officially named AArch64, it is also known as ARMv8 and arm64.
-	Andrew Turner started initial work on the FreeBSD/arm64 port at
-	the end of 2012.</p>
-
-      <p>The FreeBSD Foundation is now collaborating with ARM, Cavium,
-	the Semihalf team, and Andrew Turner to port FreeBSD to arm64,
-	and significant progress was made on the port over the last
-	quarter of 2014.</p>
-
-      <p>As of the end of the year, FreeBSD boots to single-user mode on
-	arm64, executing both static and dynamic applications.
-	Patches in review allow FreeBSD to boot to multi-user mode, and
-	these are expected to be merged soon.  This includes
-	implementing many stub functions in userland and the kernel.
-	With this, FreeBSD has booted to multi-user mode on both the ARM
-	Foundation Model and the QEMU full system emulation.</p>
-
-      <p>Cavium has supplied a software simulator of their Thunder X
-	hardware.  Bringup of FreeBSD has started on this including
-	writing new drivers for the ARM Generic Interrupt Controller
-	v3 (GICv3) and a preliminary driver for the PCIe root complex.
-	With these, FreeBSD is able to boot on this simulator in
-	preparation for testing on hardware.  Further work is
-	progressing to add full PCIe bringup and to add support for
-	the GICv3 Interrupt Translation Services (ITS) for MSI-X.</p>
-
-      <p>Further improvements have been made to the loader to allow it
-	to take the Flattened Device Tree data from UEFI and pass it
-	to the kernel.  In the kernel, busdma, CPU identification, and
-	improvements to interrupt handling have been made, along with
-	preliminary KDB support.</p>
-
-      <p>Hardware for testing the port will be installed in the FreeBSD
-	Test Cluster hosted by Sentex Communications.  The first
-	reference platform, Cavium's ThunderX, is expected to arrive
-	in the cluster in mid-January.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, ARM, and Cavium.</p><h3>Open tasks:</h3><ol><li>
-	<p>Bring up and test kernel support on real hardware.</p>
-      </li><li>
-	<p>Implement the remaining userland libraries and binaries.</p>
-      </li><li>
-	<p>Produce installable images.</p>
-      </li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="libxo:-Generate-Text,-XML,-JSON,-and-HTML-Output" href="#libxo:-Generate-Text,-XML,-JSON,-and-HTML-Output" id="libxo:-Generate-Text,-XML,-JSON,-and-HTML-Output">libxo: Generate Text, XML, JSON, and HTML Output</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://juniper.github.io/libxo/libxo-manual.html" title="http://juniper.github.io/libxo/libxo-manual.html">libxo: The Easy Way to Generate text, XML, JSON, and HTML output.</a></td><td>
-	    URL: <a href="http://juniper.github.io/libxo/libxo-manual.html" title="libxo: The Easy Way to Generate text, XML, JSON, and HTML output.">http://juniper.github.io/libxo/libxo-manual.html</a></td></tr></table><p>
-	Contact:
-	  Marcel
-	  Moolenaar
-	 &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
-	</p>
-      <p>Many FreeBSD utilities provide insight into the operational
-	state of a running FreeBSD system and as such are used regularly
-	to monitor the system.  These utilities provide their output
-	in a human readable form and sometimes even optimized for the
-	limited width of traditional terminals.  Often times these
-	utilities are used by other programs that want to present the
-	output in different ways or as part of other user interfaces.
-	For such use cases, it is infinitely better to work with
-	machine-readable output instead of human-readable output.</p>
-
-      <p>Juniper Networks has created a library called libxo, which
-	makes it easy for utilities to emit output in various formats.
-	By default, text output is emitted, but with the introduction
-	of the <tt>--libxo</tt> option this can be changed to XML,
-	JSON, and HTML.  The FreeBSD project has imported this library
-	into the base system and is in the process of rewriting
-	utilities to use libxo.</p>
-
-      <p>Related to this, FreeBSD now also has the <tt>xo</tt> utility
-	that allows scripts to grow the same capabilities.  Instead of
-	using <tt>echo</tt> or <tt>printf</tt> in scripts, output can
-	be done using the <tt>xo</tt> utility.</p>
-
-      <p>The <tt>df</tt>, <tt>w</tt>, and <tt>wc</tt> utilities have
-	been converted to use libxo.  The <tt>netstat</tt> utility is
-	in the process of being converted and others are planned.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>FreeBSD contains a lot of utilities that could benefit from
-	  having the ability to emit various output formats, too many
-	  for a few people to convert in time for FreeBSD 11.0-RELEASE.
-	  If you or your company would like to see a particular
-	  utility converted, consider learning about libxo and trying
-	  to perform the conversion of said utility to help out.</p>
-      </li></ol><hr /><h2><a name="mandoc(1)-Support" href="#mandoc(1)-Support" id="mandoc(1)-Support">mandoc(1) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mdocml.bsd.lv" title="http://mdocml.bsd.lv"></a></td><td>
-	    URL: <a href="http://mdocml.bsd.lv" title="">http://mdocml.bsd.lv</a></td></tr></table><p>
-	Contact:
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ulrich
-	  Spoerlein
-	 &lt;<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  The Documentation Team
-	 &lt;<a href="mailto:docs@FreeBSD.org">docs@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>mandoc(1)</tt> has been made the default manual page
-	formatter on HEAD &#8212; man(1) will use <tt>mandoc(1)</tt> to
-	format manual pages by default, then fall back to
-	<tt>groff(1)</tt> if it fails.</p>
-
-      <p>This change also fixes an issue with the FreeBSD <tt>man(1)</tt>
-	command not being able to properly deal with ".so" in gzipped
-	manual pages.</p>
-
-      <p>The documentation team has spent a lot of time fixing issues
-	reported by <tt>mandoc(1)</tt> in the FreeBSD manual pages.
-	This greatly improves the quality of our manual pages.</p>
-
-      <p>Most manual pages with remaining issues are from contrib/,
-	for which changes should be reported and fixed upstream.</p>
-
-      <p>The "manlint" target has also been switched to use
-	<tt>mandoc -Tlint</tt>, which results in the target being more
-	useful when working on manual pages.</p>
-
-      <p>Some <tt>groff(1)</tt> versus <tt>mandoc(1)</tt> formatting
-	differences have been spotted and reported to mandoc's
-	upstream developers.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Switch <tt>makewhatis(1)</tt> to the version shipped with
-	  <tt>mandoc(1)</tt>.</p>
-      </li><li>
-	<p>Figure out a way to detect <tt>mandoc(1)</tt>-unfriendly
-	  manpages in ports and create catpages with <tt>groff(1)</tt>
-	  for them.</p>
-      </li><li>
-	<p>Remove <tt>groff(1)</tt> from the base system.</p>
-      </li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="GNOME-on-FreeBSD" href="#GNOME-on-FreeBSD" id="GNOME-on-FreeBSD">GNOME on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/gnome" title="http://www.freebsd.org/gnome">FreeBSD GNOME Team website</a></td><td>
-	    URL: <a href="http://www.freebsd.org/gnome" title="FreeBSD GNOME Team website">http://www.freebsd.org/gnome</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-gnome" title="https://github.com/freebsd/freebsd-ports-gnome">FreeBSD Team development repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-gnome" title="FreeBSD Team development repo">https://github.com/freebsd/freebsd-ports-gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD">GNOME jhbuild buildbot wiki pages.</a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="GNOME jhbuild buildbot wiki pages.">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD GNOME Team maintains the GNOME, MATE, and CINNAMON
-	desktop environments and graphical user interfaces for FreeBSD.
-	GNOME 3 is part of the GNU Project.  MATE is a fork of the
-	GNOME 2 desktop.  CINNAMON is a desktop environment using
-	GNOME 3 technologies but with a GNOME 2 look and feel.</p>
-
-      <p>This quarter was an exciting time for the GNOME Team.  We
-	imported GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree.
-	At the same time, we removed the old GNOME 2.32 desktop.  And
-	two weeks later we updated GNOME to 3.14.2 and CINNAMON to
-	2.4.2, which was collected while the preparation for the
-	initial GNOME 3.14.0 import was under way.</p>
-
-      <p>We moved our development repo to GitHub.  The repo is
-	structured as follows: the <tt>master</tt> branch is vanilla
-	FreeBSD Ports, and we have theme branches for topics
-	such as the porting of MATE 1.9 (the mate-1.10 branch) and GNOME
-	3.15 (the gnome-3.16 branch).  The GNOME 3.14 branch (gnome-3.14)
-	is not used or updated any more because the content has been
-	committed to ports, but is kept around for the history.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The GNOME website is stale.  Work is starting on updating
-	  the development section.  We could use some help here.</p>
-      </li><li>
-	<p>MATE 1.10 porting is under way; the latest 1.9 releases are
-	  available in the mate-1.10 branch.</p>
-      </li><li>
-	<p>GNOME 3.16 porting is under way, and is available in the
-	  gnome-3.16 branch.</p>
-      </li></ol><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/"></a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://freebsd.kde.org/area51.php" title="https://freebsd.kde.org/area51.php"></a></td><td>
-	    URL: <a href="https://freebsd.kde.org/area51.php" title="">https://freebsd.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.freebsd.org/KDE" title="https://wiki.freebsd.org/KDE"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/KDE" title="">https://wiki.freebsd.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="https://mail.kde.org/mailman/listinfo/kde-freebsd"></a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="">https://mail.kde.org/mailman/listinfo/kde-freebsd</a></td></tr><tr><td><a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="http://portscout.freebsd.org/kde@freebsd.org.html"></a></td><td>
-	    URL: <a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="">http://portscout.freebsd.org/kde@freebsd.org.html</a></td></tr></table><p>
-	Contact:
-	  KDE on FreeBSD team
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging and making sure
-	that the experience of KDE and Qt on FreeBSD is as good as
-	possible.</p>
-
-      <p>As mentioned last quarter, Alonso Schaich (alonso@) became a
-	committer and since then has made good progress helping his
-	mentors Raphael Kubo da Costa (rakuco@) and Max Brazhnikov
-	(makc@) maintain all Qt and KDE-related ports.</p>
-
-      <p>This quarter, Qt 5.3 was finally committed to the ports tree.
-	Extensive work was required, including cleaning up and/or
-	changing a lot of the Qt5 ports infrastructure to make it both
-	easier to maintain the Qt ports as well as finally make it
-	possible to build newer versions when older ones are already
-	installed on the system.</p>
-
-      <p>We have also updated KDE in our experimental area51
-	repository and committed several updates to other ports such
-	as KDevelop and KDE Telepathy.  Overall, we have worked on the
-	following releases:
-	<ul>
-	  <li>CMake 3.1.0 (in area51, exp-run in progress for it to be
-	    committed to the ports tree)</li>
-
-	  <li>Calligra 2.8.6 (in area51)</li>
-
-	  <li>KDE 4.14.2 (committed to ports), 4.14.3 (in area51)</li>
-
-	  <li>KDE Telepathy 0.8.0 (committed to ports)</li>
-
-	  <li>KDevelop 4.7.0 (committed to ports)</li>
-
-	  <li>Qt 5.3.2 (committed to ports)</li>
-	</ul>
-      </p>
-
-      <p>Tobias Berner has contributed patches to update QtCreator to
-	3.3.0 as well as KDE Frameworks 5 ports which are under review
-	for inclusion in our experimental area51 repository.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Update Qt5 to 5.4.0.</p>
-      </li><li>
-	<p>Try to contribute to the work on getting rid of HAL on
-	  FreeBSD, which seems to be gaining more traction recently.</p>
-      </li><li>
-	<p>Add KDE Frameworks 5 ports to our experimental
-	  repository.</p>
-      </li></ol><hr /><h2><a name="Linux-Emulation-Ports" href="#Linux-Emulation-Ports" id="Linux-Emulation-Ports">Linux Emulation Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/allanjude/linux-ports" title="https://github.com/allanjude/linux-ports">contains additions for CentOS 6.5 64bit ports</a></td><td>
-	    URL: <a href="https://github.com/allanjude/linux-ports" title="contains additions for CentOS 6.5 64bit ports">https://github.com/allanjude/linux-ports</a></td></tr><tr><td><a href="https://github.com/vassilisl/freebsd-linux_base-f20" title="https://github.com/vassilisl/freebsd-linux_base-f20">contains a work in progress of the Fedora 20 ports</a></td><td>
-	    URL: <a href="https://github.com/vassilisl/freebsd-linux_base-f20" title="contains a work in progress of the Fedora 20 ports">https://github.com/vassilisl/freebsd-linux_base-f20</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base/user/dchagin/lemul/" title="https://svnweb.freebsd.org/base/user/dchagin/lemul/">contains base Linux emulation enhancements required for 64 bit support</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base/user/dchagin/lemul/" title="contains base Linux emulation enhancements required for 64 bit support">https://svnweb.freebsd.org/base/user/dchagin/lemul/</a></td></tr></table><p>
-	Contact:
-	  Johannes
-	  Meixner
-	 &lt;<a href="mailto:xmj@FreeBSD.org">xmj@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:allanjude@FreeBSD.org">allanjude@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Vassilis
-	  Laganakos
-	 &lt;<a href="mailto:vassilis@einval.com ">vassilis@einval.com </a>&gt;
-	</p>
-      <p>The Linux emulation stack in the ports collection was upgraded to
-	include CentOS�6.6 on November�11.  After smoothing
-	out several bugs that had been introduced, we were able
-	to bump the default version of the Linux userland from Fedora
-	10 to CentOS�6.6 on December�9th.  Providing a more
-	modern Linux userland and support libraries allows a large
-	number of Linux applications to be run on FreeBSD.</p>
-
-      <p>The goal behind providing an updated Fedora-based userland is
-	to support more desktop-oriented applications, which require
-	newer libraries than are provided by CentOS�6.  Providing
-	64-bit versions of the CentOS userland will allow applications
-	that are only available in 64-bit form, such as a number of
-	scientific and math related applications, to be run on FreeBSD.
-	Support for 64-bit binaries also requires the 64-bit Linux
-	kernel emulation layer from the lemul branch, which requires
-	more testing and review before being merged into HEAD.</p>
-    <p>This project was sponsored by Perceivon Hosting Inc., and ScaleEngine Inc..</p><h3>Open tasks:</h3><ol><li>
-	<p>Update Allan Jude's 64-bit Linux ports to
-	  CentOS�6.6.</p>
-      </li><li>
-	<p>Add Fedora�20 base/userland ports to ports/head.</p>
-      </li><li>
-	<p>Refactor <tt>Mk/bsd.linux-*.mk</tt> to facilitate the above
-	  additions.</p>
-      </li><li>
-	<p>Promote testing and merging of Dmitry Chagin's lemul
-	  branch.  (Updated Linux kernel emulation, and 64-bit
-	  support)</p>
-      </li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/graphics/" title="http://blogs.freebsdish.org/graphics/">Graphics stack team blog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/graphics/" title="Graphics stack team blog">http://blogs.freebsdish.org/graphics/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-graphics" title="https://github.com/freebsd/freebsd-ports-graphics">Ports development tree on GitHub</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-graphics" title="Ports development tree on GitHub">https://github.com/freebsd/freebsd-ports-graphics</a></td></tr></table><p>
-	Contact: FreeBSD Graphics team &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>Mesa was upgraded to 10.3, then 10.4 for FreeBSD 10.1-RELEASE
-	and 11-CURRENT.  We test release candidates and therefore this
-	port is now usually updated shortly after a new release.  Mesa
-	10.x brings huge improvements in terms of OpenGL standards
-	support, performance and stability, especially for Radeon
-	owners.  Mesa 9.1 is kept for FreeBSD 9.x, but we have plans to
-	fix this; see below.</p>
-
-      <p><tt>graphics/gbm</tt> and <tt>devel/libclc</tt> are new ports
-	used by Mesa to implement OpenCL.  The next step is to finish
-	the port for Mesa's libOpenCL.so, named Clover.  This will
-	permit users to run OpenCL programs on Radeon GPUs for
-	now.</p>
-
-      <p>xserver was upgraded from 1.12 to 1.14.  This is the last
-	version of xserver supporting Mesa 9.1.  Changes are described
-	in an article on the blog.  The most noticeable one is the
-	switch from the input device detection back-end based on HAL
-	to the one based on <tt>devd(8)</tt>.  <tt>hald(8)</tt> is
-	still required by many desktop environments, but the X.Org
-	server itself is free from it.</p>
-
-      <p>xserver was the last port supporting the
-	<tt>WITH_NEW_XORG</tt> knob.  The knob is now completely
-	removed.  This was the occasion to add <tt>WITH_NEW_XORG</tt>
-	and <tt>WITH_KMS</tt> to the list of deprecated knobs to help
-	people clean up their <tt>make.conf</tt>.  At the same time,
-	the new-xorg alternate pkg repository was deprecated.</p>
-
-      <p>After discussion, two options were enabled by default:</p>
-      <ul>
-	<li><tt>TEXTURE_FLOAT</tt> in graphics/dri, which allows Mesa
-	  to advertise the support for OpenGL 3.0+;</li>
-
-	<li><tt>LCD_FILTERING</tt> in <tt>print/freetype2</tt>, which
-	  enables the subpixel rendering engine, improving font
-	  anti-aliasing.</li>
-      </ul>
-
-      <p>These two packages now provide a better user experience
-	out-of-the-box.  Users who are uncomfortable with the options
-	may unset them and rebuild the ports.  There is no need to
-	rebuild anything else.</p>
-
-      <p>On the kernel side, Tijl Coosemans added AGP support back to
-	the TTM memory manager and therefore to the Radeon driver.
-	His work was merged back to stable/10 and will be available in
-	FreeBSD 10.2-RELEASE.</p>
-
-      <p>We migrated our Ports development tree to Git and GitHub.
-	Tracking changes in the official Ports tree and preparing
-	patches is much easier.  Furthermore, we can accept pull
-	requests.  All of the reasons behind this change are detailed
-	on the blog and the workflow is described on the wiki.</p>
-
-      <p>The XDC 2014 (X Developer's Conference) was a great
-	conference.  Reviving the relationship with the developers of
-	the graphics stack was a success! A report is available on the
-	blog.</p>
-
-      <p>Our next items on the roadmap are:</p>
-
-      <ol>
-	<li>Provide FreeBSD 10.1-RELEASE's i915 driver to FreeBSD 9.x users
-	  through a new port.  This is a work in progress, but it
-	  would allow us to remove Mesa 9.1 and make Mesa 10.4
-	  available everywhere.</li>
-	<li>Once Mesa 9.1 is gone, we can update xserver to 1.16.</li>
-      </ol>
-    <h3>Open tasks:</h3><ol><li>
-	<p>See the "Graphics" wiki page for up-to-date
-	  information.</p>
-      </li></ol><hr /><h2><a name="Wine/FreeBSD" href="#Wine/FreeBSD" id="Wine/FreeBSD">Wine/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Wine" title="http://wiki.FreeBSD.org/Wine">Wine wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Wine" title="Wine wiki page">http://wiki.FreeBSD.org/Wine</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/i386-Wine" title="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 wiki page</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/i386-Wine" title="Wine on amd64 wiki page">http://wiki.FreeBSD.org/i386-Wine</a></td></tr><tr><td><a href="http://www.winehq.org" title="http://www.winehq.org">Wine homepage</a></td><td>
-	    URL: <a href="http://www.winehq.org" title="Wine homepage">http://www.winehq.org</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kris
-	  Moore
-	 &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Wine on FreeBSD project has been steadily forging ahead for
-	the past three quarters and has updated the ports for the
-	following versions:</p>
-
-      <ul>
-	<li>Stable releases: 1.6.2 (3 port revisions)</li>
-	<li>Development releases: 1.7.16 through 1.7.33</li>
-      </ul>
-
-      <p>The ports have packages built for amd64 (available through
-	the ports emulators/i386-wine and i386-wine-devel) for FreeBSD
-	8.4, 9.1+, 10.0+, and CURRENT.</p>
-
-      <p>Accomplishments include:</p>
-
-      <ul>
-	<li>Upstreaming 33 patches to fix Wine on FreeBSD &#8212; many
-	  thanks to Gerald for this work.</li>
-
-	<li>Migrating to the USES framework.</li>
-
-	<li>Building Wine with the X compositing extension.</li>
-
-	<li>Adding support for MPG123 and V4L.</li>
-
-	<li>Backporting changes made to the -devel ports to the stable
-	  ones and fixing minutiae here and there.</li>
-
-	<li>Creating a new Wine port for the Compholio patches.</li>
-
-	<li>Changing i386-wine(-devel) to set the
-	  <tt>LD_LIBRARY_PATH_RPATH</tt> variable.</li>
-
-	<li>Improving library bundling for i386-wine(-devel).</li>
-
-	<li>Various improvements to the patch-nvidia.sh script for
-	  i386-wine(-devel).</li>
-
-	<li>Various smaller changes.</li>
-      </ul>
-
-      <p>We would like to thank all the volunteers who contributed
-	feedback or even patches.  We would also like to welcome
-	kmoore@ to the Wine team.  He has been extensively involved in
-	bringing wine-compholio to the Ports Collection.</p>
-
-      <p>Future development on Wine will focus on:</p>
-
-      <ul>
-	<li>Creating a 64-bit capable port of Wine (aka Wine64).</li>
-
-	<li>Creating a WoW64 capable port of Wine (aka Wine +
-	  Wine64).</li>
-
-	<li>Fixing directory listing on FreeBSD 8 and 9.</li>
-      </ul>
-
-      <p>Maintaining and improving Wine is a major undertaking that
-	directly impacts end-users on FreeBSD, including many gamers.  If
-	you are interested in helping, please contact us.  We will
-	happily accept patches, suggest areas of focus, or have a
-	chat.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Open Tasks and Known Problems (see the
-	  <a href="http://wiki.FreeBSD.org/Wine" shape="rect">Wine wiki page</a>).</p>
-      </li><li>
-	<p>FreeBSD/amd64 integration (see the
-	  <a href="http://wiki.FreeBSD.org/i386-Wine" shape="rect">i386-Wine wiki page</a>).</p>
-      </li><li>
-	<p>Porting WoW64 and Wine64.</p>
-      </li></ol><hr /><h2><a name="Xfce" href="#Xfce" id="Xfce">Xfce</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xfce" title="">https://wiki.freebsd.org/Xfce</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms, such as FreeBSD.  It aims to be fast and
-	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>
-
-      <ul>
-	<li>misc/xfce4-weather-plugin 0.8.5</li>
-
-	<li>science/xfce4-equake-plugin 1.3.6</li>
-
-	<li>sysutils/xfce4-netload-plugin 1.2.4</li>
-
-	<li>sysutils/xfce4-systemload-plugin 1.1.2</li>
-
-	<li>www/midori 0.5.9</li>
-
-	<li>x11/xfce4-taskmanager 1.1.0</li>
-
-	<li>x11/xfce4-whiskermenu-plugin 1.4.2</li>
-
-	<li>x11-wm/xfce4-desktop 4.10.3</li>
-      </ul>
-
-      <p>Two new ports have also been added (taken from our
-	repository):</p>
-
-      <ul>
-	<li>deskutils/xfce4-volumed-pulse</li>
-
-	<li>x11/xfce4-dashboard</li>
-      </ul>
-
-      <p>Moreover, we are working on the next stable release, with
-	these ports being updated:</p>
-
-      <ul>
-	<li>sysutils/xfce4-power-manager 1.4.2</li>
-
-	<li>x11/xfce4-dashboard 0.3.4</li>
-
-	<li>x11-wm/xfce4-session 4.11.1</li>
-      </ul>
-
-      <p>We sent some patches to upstream.</p>
-
-      <ul>
-	<li>bug <a href="https://bugzilla.xfce.org/show_bug.cgi?id=11104" shape="rect">#11104</a>, to keep 'wallpaper settings' in Ristretto with xfdesktop &gt;= 4.11</li>
-
-	<li>bug <a href="https://bugzilla.xfce.org/show_bug.cgi?id=11249" shape="rect">#11249</a>, add 'Hidden' option in desktop item editor (refused)</li>
-
-	<li>bug <a href="https://bugzilla.xfce.org/show_bug.cgi?id=11413" shape="rect">#11413</a>, to use sysctl(3) and acpi_video(4) for backlight support</li>
-      </ul>
-
-      <p>A FAQ is being written
-	<a href="https://reviews.freebsd.org/D1305" shape="rect">D1305</a>.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Find a workaround for when <tt>acpi_video(4)</tt> is not
-	  functional (panel crashes); OpenBSD seems to have same
-	  problem.</p>
-      </li><li>
-	<p>Clean up patch in order to add new panel plugin in ports
-	  tree.</p>
-      </li><li>
-	<p>Continue to work on documentation, especially the Porter's
-	  Handbook.</p>
-      </li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="More-Michael-Lucas-Books" href="#More-Michael-Lucas-Books" id="More-Michael-Lucas-Books">More Michael Lucas Books</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.michaelwlucas.com/nonfiction/freebsd-mastery-storage-essentials" title="https://www.michaelwlucas.com/nonfiction/freebsd-mastery-storage-essentials">FreeBSD Mastery: Storage Essentials page</a></td><td>
-	    URL: <a href="https://www.michaelwlucas.com/nonfiction/freebsd-mastery-storage-essentials" title="FreeBSD Mastery: Storage Essentials page">https://www.michaelwlucas.com/nonfiction/freebsd-mastery-storage-essentials</a></td></tr><tr><td><a href="http://blather.michaelwlucas.com" title="http://blather.michaelwlucas.com">blog</a></td><td>
-	    URL: <a href="http://blather.michaelwlucas.com" title="blog">http://blather.michaelwlucas.com</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	</p>
-      <p>The first small FreeBSD Book, "FreeBSD Mastery: Storage
-	Essentials" is available.</p>
-
-      <p>Lucas is moving on to FreeBSD books on ZFS, Specialty
-	Filesystems, and jails.  They will hopefully be available by
-	BSDCan 2015.</p>
-
-      <p>Get status updates on his blog, or follow @mwlauthor on
-	Twitter.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Push BSDCan out to June, so he has more time to write the
-	  new books.</p>
-      </li></ol><hr /><h2><a name="New-Translators-Mailing-List" href="#New-Translators-Mailing-List" id="New-Translators-Mailing-List">New Translators Mailing List</a></h2><p>
-	Contact: FreeBSD Translators Mailing List &lt;<a href="mailto:freebsd-translators@FreeBSD.org">freebsd-translators@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new mailing list has been created for people translating
-	FreeBSD documents and programs from English into other languages.
-	Discussions can include methods, tools, and techniques.
-	Existing translators are encouraged to join so there is a
-	single point of contact.  New translators and those who wish
-	to help with translation are welcome.</p>
-
-      <p>New members are asked to introduce themselves and mention the
-	languages they are interested in translating.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Encourage existing translators to join.</p>
-      </li><li>
-	<p>Welcome and educate new volunteers.</p>
-      </li><li>
-	<p>Work on implementing newer and easier translation
-	  systems and tools.</p>
-      </li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="Creating-Vagrant-Images-with-Packer" href="#Creating-Vagrant-Images-with-Packer" id="Creating-Vagrant-Images-with-Packer">Creating Vagrant Images with Packer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://blogs.freebsdish.org/brd/2014/12/22/freebsd-packer-vagrant/" title="http://blogs.freebsdish.org/brd/2014/12/22/freebsd-packer-vagrant/">Blog Announcement</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/brd/2014/12/22/freebsd-packer-vagrant/" title="Blog Announcement">http://blogs.freebsdish.org/brd/2014/12/22/freebsd-packer-vagrant/</a></td></tr><tr><td><a href="https://github.com/so14k/packer-freebsd" title="https://github.com/so14k/packer-freebsd">Git Repo</a></td><td>
-	    URL: <a href="https://github.com/so14k/packer-freebsd" title="Git Repo">https://github.com/so14k/packer-freebsd</a></td></tr></table><p>
-	Contact:
-	  Brad
-	  Davis
-	 &lt;<a href="mailto:brd@FreeBSD.org">brd@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have developed a recipe to use Packer to create FreeBSD
-	Vagrant images to run on VMware and VirtualBox.</p>
-
-      <p><a href="https://www.packer.io/" shape="rect">Packer</a> is a tool for
-	creating identical machine images for multiple platforms from
-	a single source configuration.</p>
-
-      <p><a href="https://www.vagrantup.com/" shape="rect">Vagrant</a> is a tool to
-	create and configure lightweight, reproducible, and portable
-	development environments.</p>
-
-      <p>To get started, clone the Git repo and follow the directions
-	in the README.  More information is available from the Packer
-	and Vagrant websites.</p>
-    <hr /><h2><a name="FreeBSD-Forum-Software-Migration" href="#FreeBSD-Forum-Software-Migration" id="FreeBSD-Forum-Software-Migration">FreeBSD Forum Software Migration</a></h2><p>
-	Contact: FreeBSD Forums Administration Team &lt;<a href="mailto:forum-admins@">forum-admins@</a>&gt;
-	</p>
-      <p>With funding from the FreeBSD Foundation, the FreeBSD forums
-	were migrated to XenForo software.  The new software is
-	far more capable and easy to use.  While the entire forum team
-	contributed, Daniel Ger&#382;o did an excellent job importing
-	existing users and messages and bringing back the
-	often-requested "Thanks" feature.  The upgrade was completed
-	in time to be ready for the influx of new users from the
-	release of FreeBSD 10.1, and we have already seen an increase in
-	usage.</p>
-
-      <p>Developers with an @FreeBSD.org address can contact forum
-	administrators to obtain the highly-desired "@" suffix on
-	their forum user name along with a Developer flag.</p>
-
-      <p>We want to thank the Foundation for making this possible, and
-	the users for their patience and continued presence on the
-	forums!</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Encourage more developers and users to try the new
-	  forums.</p>
-      </li><li>
-	<p>Continue getting feedback from users for tuning and
-	  improvements.</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD�Project
-	and community worldwide.  Most of the funding is used to
-	support FreeBSD development projects, conferences, and developer
-	summits; purchase equipment to grow and improve the FreeBSD
-	infrastructure; and provide legal support for the Project.</p>
-
-      <p>We ended the year exceeding our fundraising goal, by raising
-	over $2,372,132, from 1670 donors! Thank you to everyone who
-	made a donation in 2014.</p>
-
-      <p>We produced issues five and six of the FreeBSD Journal,
-	ending the year with over 6300 subscribers, exceeding our
-	first-year goal of 5000 subscribers.  We also added the
-	desktop/digital edition, so people can read the magazine from
-	their browsers.  We also hosted a meeting with the Journal
-	Editorial Board and worked out the editorial calendar for the
-	next two years.  This includes topics and articles for the
-	future issues.</p>
-
-      <p>We were a gold sponsor of EuroBSDCon 2014, and a sponsor of
-	the preceding Developer Summit.  A few of our team members
-	attended, which allowed us to have an informal face-to-face
-	board meeting, with a focus on supporting the European region.
-	Kirk McKusick gave a two-day FreeBSD tutorial and Erwin
-	Lansing helped run the Developer Summit.  We sponsored 5
-	FreeBSD contributors to attend the conference.</p>
-
-      <p>We were a sponsor of the
-	<a href="http://gracehopper.org/2014/" shape="rect">Grace Hopper
-	Conference</a>.
-	Dru Lavigne gave an "introduction to FreeBSD" presentation, that
-	was well attended.  We also sponsored Shteryana Shopova to
-	represent FreeBSD, along with Dru, at our booth.</p>
-
-      <p>We were a sponsor of
-	<a href="https://www.meetbsd.com/" shape="rect">MeetBSD</a>.
-	Most of our team members attended this conference.
-	Kirk McKusick gave a talk on BSD history.
-	We also had a booth, and raised over $2,200 in donations.
-	We sponsored one person to attend this conference.</p>
-
-      <p>George organized and ran the two-day Silicon Valley Vendor
-	and Developer Summit following MeetBSD.
-	A lot of work gets started and accomplished at these summits,
-	for example, Kirk worked with various folks to get the ino64
-	(64-bit inode numbers) project moving.
-	It started in 2011 as a Summer of Code project and has
-	sputtered since getting pushed into the system.</p>
-
-      <p>In addition to the above conferences, we helped promote FreeBSD at
-	the following conferences:
-
-	<ul>
-	  <li><a href="http://allthingsopen.org/2014/" shape="rect">All Things
-	    Open</a></li>
-	  <li><a href="https://ohiolinux.org/" shape="rect">Ohio Linux
-	    Fest</a></li>
-	  <li><a href="https://www.usenix.org/conference/lisa14" shape="rect">LISA</a></li>
-	</ul>
-
-	LISA had a great turnout for Dru Lavigne's FreeBSD BoF talk.
-      </p>
-
-      <p>We visited a few large FreeBSD users in the Bay Area to
-	discuss their use of FreeBSD, plans, and needs, and help
-	facilitate collaboration between them and the Project.</p>
-
-      <p>Cheryl Blain joined our board, bringing a strong background
-	in business development and fundraising.</p>
-
-      <p>We received the largest donation in our history, and our
-	treasurer put together an endowment strategy for us to
-	follow.</p>
-
-      <p>We increased our FreeBSD marketing efforts to help promote
-	and advocate for FreeBSD, as well as educate people on
-	FreeBSD.  Some our FreeBSD marketing highlights include:
-	<ul>
-	  <li>Created the FreeBSD 10 brochure</li>
-	  <li>Created the Get Involved brochure for recruiting</li>
-	  <li>Created a testimonial flyer to encourage more companies
-	    to write FreeBSD testimonials for us.</li>
-	</ul>
-	These flyers are available on the
-	<a href="https://www.freebsdfoundation.org/documents/#marketing" shape="rect">FreeBSD
-	  Foundation site</a>
-	for FreeBSD advocates to promote FreeBSD at conferences around
-	the world.
-	We also put ads for the Foundation and FreeBSD in the FreeBSD
-	Journal and USENIX ;login: magazine.</p>
-
-      <p>We are producing a monthly newsletter to highlight what we
-	did the previous month to support the FreeBSD Project.
-	We also produced our
-	<a href="https://www.freebsdfoundation.org/press/2014dec-newsletter.html" shape="rect">December
-	semi-annual newsletter</a>.</p>
-
-      <p>We redesigned and launched phase 1 of our website.
-	It should be easier to navigate and find the information you
-	need to get help from or to help the Foundation.</p>
-
-      <p>Glen Barber visited the Microsoft main campus and worked with
-	Microsoft Hyper-V developers to resolve outstanding issues
-	with providing FreeBSD images for the Microsoft Azure
-	platform.</p>
-
-      <p>Glen also visited the NYI colocation facility to install and
-	configure new servers purchased by the Foundation.</p>
-
-      <p>We finished the 10.1-RELEASE cycle.</p>
-
-      <p>Our project development staff and contractors have been
-	working on various projects to add features to and improve
-	FreeBSD. Some of their reports are included in this overall
-	report.  Some projects that were worked on this quarter were
-	adding support for 64-bit ARM architecture to FreeBSD,
-	integration work on the vt(4) updated console and UEFI boot
-	support, Secure Boot, refining the in-kernel iSCSI target and
-	initiator stack, an autofs-based automount daemon, migrating to
-	the ELF Tool Chain, and implementing modern AES modes in
-	FreeBSD's cryptographic framework.</p>
-
-      <p>To read more about how we helped support the FreeBSD Project
-	and community, read our
-	<a href="https://www.freebsdfoundation.org/press/2014dec-newsletter.html" shape="rect">semi-annual
-	newsletter</a>.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2015-01-2015-03.html b/website/content/en/status/report-2015-01-2015-03.html
deleted file mode 100644
index 3db2012018..0000000000
--- a/website/content/en/status/report-2015-01-2015-03.html
+++ /dev/null
@@ -1,2070 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD-related projects between January and
-      March 2015.  This is the first of four reports planned for
-      2015.</p><p>The first quarter of 2015 was another productive quarter for
-      the FreeBSD project and community.  FreeBSD is being used in research
-      projects, and those projects are making their way back into FreeBSD
-      as new and exciting features, bringing improved network performance
-      and security features to the system.  Work continues to improve
-      support for more architectures and architecture features,
-      including progress towards the goal of making ARM (32- and 64-bit) a
-      Tier 1 platform in FreeBSD 11.  The toolchain is receiving updates, with
-      new versions of clang/LLVM in place, migrations to ELF Tool Chain
-      tools, and updates to the LLDB and gdb debuggers.  Work by ports
-      teams and kernel developers is maintaining and improving the state of
-      FreeBSD as a desktop operating system.  The pkg team is continuing to
-      make binary packages easier to use and upgrade.</p><p>Thanks to all the reporters for the excellent work!</p><p>The deadline for submissions covering the period from April
-      to June 2015 is July 7th, 2015.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugmeister">FreeBSD Bugmeister</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#bhyve">bhyve</a></li><li><a href="#CheriBSD">CheriBSD</a></li><li><a href="#Clang,-llvm-and-lldb-updated-to-3.6.0">Clang, llvm and lldb updated to 3.6.0</a></li><li><a href="#FreeBSD-on-POWER8">FreeBSD on POWER8</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li><li><a href="#Lua-boot-loader">Lua boot loader</a></li><li><a href="#Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support">Mellanox iSCSI Extensions for RDMA (iSER) Support</a></li><li><a href="#Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#Opaque-ifnet">Opaque ifnet</a></li><li><a href="#pkg">pkg</a></li><li><a href="#Secure-Boot">Secure Boot</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Adding-PCIe-Hot-plug-Support">Adding PCIe Hot-plug Support</a></li><li><a href="#Address-Space-Layout-Randomization-(ASLR)">Address Space Layout Randomization (ASLR)</a></li><li><a href="#Modern-x86-platform-support-and-VT-d">Modern x86 platform support and VT-d</a></li><li><a href="#Nanosecond-file-timestamps">Nanosecond file timestamps</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-newer-ARM-boards">FreeBSD on newer ARM boards</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#Nested-Kernel">Nested Kernel</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#libthr-improvements">libthr improvements</a></li><li><a href="#Migration-to-ELF-Tool-Chain-tools">Migration to ELF Tool Chain tools</a></li><li><a href="#The-LLDB-Debugger">The LLDB Debugger</a></li><li><a href="#Updates-to-GDB">Updates to GDB</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></li><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME-on-FreeBSD">GNOME on FreeBSD</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#The-Graphics-stack-on-FreeBSD">The Graphics stack on FreeBSD</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#More-Michael-Lucas-FreeBSD-books">More Michael Lucas FreeBSD books</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugmeister" href="#FreeBSD-Bugmeister" id="FreeBSD-Bugmeister">FreeBSD Bugmeister</a></h2><p>
-	Contact: FreeBSD Bugmeister &lt;<a href="mailto:bugmeister@FreeBSD.org">bugmeister@FreeBSD.org</a>&gt;
-	</p>
-      <p>Bugzilla replaced GNATS in June 2014 as the bug
-	management tool of choice for FreeBSD, granting GNATS its
-	well-deserved retirement after more than 20 years of operation.
-	The following months were rough for Bugzilla: a lot of
-	functionality was still missing and several uncertainties caused
-	users and committers to adapt only slowly to the new system.</p>
-
-      <p>Over the last six months, a lot of missing features were
-	brought into place to allow users and committers to focus on
-	getting bugs solved.  Categories, the status model and many
-	workflow-related knobs were continuously reworked and improved to
-	provide the necessary information without getting in the
-	way.</p>
-
-      <p>An auto-assigner for ports issues was implemented,
-	resembling what GNATS successfully did in the past.  A <a href="https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html" shape="rect">dashboard</a>
-	page within Bugzilla provides users and committers with quick
-	access to common
-	queries and overall statistics; many other smaller tweaks,
-	configurations, and extensions were implemented to improve the
-	usability of the system.</p>
-
-      <p>An improved reporting system is currently being
-	implemented to provide graphs and statistics for users and
-	committers.  Handling MFCs and a better feedback mechanism for
-	requests (flags in Bugzilla) will be the next things to do.</p>
-
-      <p>Bugmeister is also working closely with the FreeBSD GitHub
-	team to establish a workflow between GitHub's issue tracker and
-	our Bugzilla system.  The technical solution already exists as a
-	proof of concept, but its usage in production will have to wait
-	until Bugzilla 5.0 has been adopted.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Create a solid <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198244" shape="rect">charting
-	    extension</a> for FreeBSD Bugzilla.</p>
-      </li><li>
-	<p>Improve <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193772" shape="rect">MFC
-	    handling</a>.</p>
-      </li><li>
-	<p>Do you feel that something important is missing?
-	  <a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Services&amp;component=Bug%20Tracker" shape="rect">Let
-	    us know!</a></p>
-      </li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://portscout.freebsd.org/" title="http://portscout.freebsd.org/"></a></td><td>
-	    URL: <a href="http://portscout.freebsd.org/" title="">http://portscout.freebsd.org/</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Port Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of Q1 the ports tree holds almost 25,000
-	ports, and the PR count is just over 1,500.  The tree saw
-	more activity than during the previous quarter, with
-	almost 7,000 commits performed by 163 active committers.
-	The number of problem reports closed also increased by
-	about 20%, with nearly 2,000 PRs closed!</p>
-
-      <p>In Q1 two new developers were granted a ports commit bit
-	(jbeich@ and brd@) and one bit was taken in for safekeeping
-	(rafan@, on his request).</p>
-
-      <p>On the management side, decke@ decided to step down from
-	his portmgr duties in February.  No other changes were made
-	to the team during Q1.</p>
-
-      <p>This quarter also saw the release of the first quarterly
-	branch of the year, 2015Q1.  On this branch, 140 changes were
-	applied by 35 committers.</p>
-
-      <p>On the QA side, 29 exp-runs were performed to validate sensitive
-	updates or cleanups.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>As during the previous quarter a tremendous amount
-	  of work was done on the tree to update major ports and to
-	  close even more PRs than in 2014Q4.  However, we sometimes
-	  lag behind with regards to documentation, so volunteers
-	  are welcome to help on this important task.</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team constitutes the project's "Board of
-	Directors", responsible for deciding the project's overall goals
-	and direction as well as managing specific areas of the FreeBSD
-	project landscape.</p>
-
-      <p>January began with members of core dealing with the fallout
-	from the accidental deletion of the Bugzilla database.  This
-	incident highlighted the fact that backup and recovery mechanisms
-	in the cluster were not up to the task.  Core has discussed what
-	measures are appropriate with clusteradm and is reviewing their
-	implementation.</p>
-
-      <p>After a long process of consultation, plans for introducing the
-	new support model with 11.0-RELEASE were finally agreed on and
-	published in early February.  This announcement puts the practical
-	detail onto the motion that was adopted at BSDCan 2014, and
-	clarifies the steps needed for implementation.</p>
-
-      <p>Also in February core revisited discussions on making the
-	blogs.freebsdish.org blog aggregator an official project service
-	and also providing a blogging platform directly to developers.
-	However, security and man-power are both major concerns.  Given
-	the track records of most freely available blogging platforms,
-	core is rightly wary of introducing them into the cluster.
-	Similarly, curating a blogging platform will take a substantial
-	volunteer effort to ensure all posts are appropriate and to remove
-	spam.</p>
-
-      <p>March has seen two discussions about potentially divisive
-	topics.  Should the ZFS ARC Responsiveness patches be committed
-	and MFC'd as a pragmatic fix to performance problems in
-	10.1-RELEASE, understanding that this is not an ideal solution to
-	the problem and will need rework?  Should we stop maintaining
-	support for older (C89 or earlier) compilers in kernel code, and
-	just code directly to the C11 standard?  Broadening out from this
-	last point: should we have a formal mechanism for deciding what
-	has become obsolete in the system and when it should be
-	removed?</p>
-
-      <p>During this quarter five new src commit bits were granted and
-	two were taken in for safe-keeping.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="bhyve" href="#bhyve" id="bhyve">bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bhyve.org" title="http://www.bhyve.org">bhyve FAQ and talks</a></td><td>
-	    URL: <a href="http://www.bhyve.org" title="bhyve FAQ and talks">http://www.bhyve.org</a></td></tr></table><p>
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Neel
-	  Natu
-	 &lt;<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Tycho
-	  Nightingale
-	 &lt;<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:allanjude@FreeBSD.org">allanjude@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>bhyve is a hypervisor that runs on the FreeBSD/amd64
-	platform.  At present, it runs FreeBSD (8.x or later), Linux
-	i386/x64, OpenBSD i386/amd64, and NetBSD/amd64 guests.  Current
-	development is focused on enabling additional guest operating
-	systems and implementing features found in other hypervisors.</p>
-
-      <p>Peter Grehan did a status update at bhyvecon 2015 in
-	Tokyo.  The slides are available at <a href="http://bhyvecon.org/bhyvecon2015-Peter.pdf" shape="rect">
-	http://bhyvecon.org/bhyvecon2015-Peter.pdf</a>.</p>
-
-      <p>Mihai Carabas presented the results of his GSoC project
-	on implementing instruction caching in bhyve at AsiaBSDCon
-	2015 in Tokyo.  The slides are available at <a href="http://people.freebsd.org/~neel/bhyve/bhyve-cache-emul-slides.pdf" shape="rect">
-	http://people.freebsd.org/~neel/bhyve/bhyve-cache-emul-slides.pdf</a>.</p>
-
-      <p>A number of improvements were made to bhyve this quarter:</p>
-
-      <ul>
-	<li>The RTC device model can now be instructed to keep UTC time
-	  instead of localtime.  This is useful for guests like OpenBSD
-	  that expect the RTC to keep UTC time.</li>
-	<li>The virtio-blk device now does I/O asynchronously without
-	  blocking the vcpu thread that initiated the I/O.</li>
-	<li>The virtio-blk and ahci-hd devices are now able to execute
-	  multiple I/O requests in parallel.  This can significantly
-	  boost virtual disk throughput.</li>
-	<li>The ahci-hd device emulation advertises TRIM to the guest
-	  if the backend device supports it (e.g., ZVOL).</li>
-	<li>The virtio-blk and ahci-hd devices now advertise the proper
-	  logical and physical block size of the backend device or file.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Improve documentation.</p>
-      </li><li>
-	<p>bhyveucl is a tool for starting bhyve instances based on a
-	  UCL formatted config file.  More information is at
-	  <a href="https://github.com/allanjude/bhyveucl" shape="rect">https://github.com/allanjude/bhyveucl</a></p>
-      </li><li>
-	<p>Add support for virtio-scsi.</p>
-      </li><li>
-	<p>Flexible networking backends such as wanproxy and vhost-net.</p>
-      </li><li>
-	<p>Move to a single process model, instead of bhyveload
-	  and bhyve.</p>
-      </li><li>
-	<p>Support running bhyve as non-root.</p>
-      </li><li>
-	<p>Add filters for popular VM file formats (VMDK, VHD,
-	  QCOW2).</p>
-      </li><li>
-	<p>Implement an abstraction layer for video (no X11 or SDL in
-	  the base system).</p>
-      </li><li>
-	<p>Suspend/resume support.</p>
-      </li><li>
-	<p>Live Migration.</p>
-      </li><li>
-	<p>Nested VT-x support (bhyve in bhyve).</p>
-      </li><li>
-	<p>Support for other architectures (ARM, MIPS, PPC).</p>
-      </li></ol><hr /><h2><a name="CheriBSD" href="#CheriBSD" id="CheriBSD">CheriBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://cheri-cpu.org/" title="http://cheri-cpu.org/"></a></td><td>
-	    URL: <a href="http://cheri-cpu.org/" title="">http://cheri-cpu.org/</a></td></tr></table><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Chisnall
-	 &lt;<a href="mailto:theraven@FreeBSD.org">theraven@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ruslan
-	  Bukin
-	 &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	</p>
-      <p>CheriBSD is a fork of FreeBSD to support the CHERI
-	research CPU.  We have extended the kernel to provide support
-	for CHERI memory capabilities as well as modifying applications
-	and libraries including tcpdump, libmagic, and libz to take
-	advantage of these capabilities for improved memory safety and
-	compartmentalization.  We have also developed custom demo
-	applications and deployment infrastructure for our table demo
-	platform.</p>
-
-      <p>As this goes to press, we are finalizing our first open
-	source release of the CHERI CPU which will be available from
-	the CHERI CPU <a href="http://cheri-cpu.org/" shape="rect">website</a>.</p>
-
-      <p>We have been merging support for the BERI CPU platform
-	to FreeBSD since 2012 and continue to do so as new features are
-	developed.  Most recently, Ruslan has added support for the
-	Terasis SoCkit board which combines an ARM processor with an
-	FPGA capable of running BERI (and soon CHERI) in a single
-	package.</p>
-    <p>This project was sponsored by DARPA/AFRL.</p><hr /><h2><a name="Clang,-llvm-and-lldb-updated-to-3.6.0" href="#Clang,-llvm-and-lldb-updated-to-3.6.0" id="Clang,-llvm-and-lldb-updated-to-3.6.0">Clang, llvm and lldb updated to 3.6.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://llvm.org/releases/3.6.0/docs/ReleaseNotes.html" title="http://llvm.org/releases/3.6.0/docs/ReleaseNotes.html">LLVM 3.6.0 Release Notes</a></td><td>
-	    URL: <a href="http://llvm.org/releases/3.6.0/docs/ReleaseNotes.html" title="LLVM 3.6.0 Release Notes">http://llvm.org/releases/3.6.0/docs/ReleaseNotes.html</a></td></tr><tr><td><a href="http://llvm.org/releases/3.6.0/tools/clang/docs/ReleaseNotes.html" title="http://llvm.org/releases/3.6.0/tools/clang/docs/ReleaseNotes.html">Clang 3.6.0 Release Notes</a></td><td>
-	    URL: <a href="http://llvm.org/releases/3.6.0/tools/clang/docs/ReleaseNotes.html" title="Clang 3.6.0 Release Notes">http://llvm.org/releases/3.6.0/tools/clang/docs/ReleaseNotes.html</a></td></tr></table><p>
-	Contact:
-	  Dimitry
-	  Andric
-	 &lt;<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Davide
-	  Italiano
-	 &lt;<a href="mailto:davide@FreeBSD.org">davide@FreeBSD.org</a>&gt;
-	</p>
-      <p>Just before the end of the quarter, we updated clang, llvm
-	and lldb in the base system to the 3.6.0 release.  These all
-	contain numerous improvements; please see the linked release
-	notes for more detailed information.</p>
-
-      <p>We have also imported a newer snapshot of compiler-rt,
-	with better support for the Address Sanitizer and the Undefined
-	Behavior Sanitizer, and arm64 runtime support routines.
-	With the updated clang, llvm, and compiler-rt, we now support the
-	Address and Undefined Behavior Sanitizers in the base system
-	toolchain.</p>
-
-      <p>As with the 3.5.0 release, these components require C++11
-	support to build.  C++11 support is available in FreeBSD 10.0 and
-	later on the x86 architectures.</p>
-
-      <p>It is still unclear whether we will be able to MFC these
-	updates to any of the stable branches, due to the difficulty it will
-	introduce for upgrading from a system without C++11 support,
-	either from older releases or from architectures still using gcc.</p>
-
-      <p>In the lld-import branch, we have also imported a recent
-	snapshot of lld, a linker produced by the LLVM project.  This
-	is a very preliminary effort of making it available as a
-	system linker.</p>
-
-      <p>Thanks to Ed Maste, Roman Divacky, Andrew Turner and
-	Davide Italiano for their help with this import, and thanks to
-	Antoine Brodin for performing a ports exp-run.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>After the ports exp-run, a small number of ports
-	  turned out to have problems, and for almost all of these, PRs
-	  with fixes or workarounds were filed.  While most of these PRs
-	  have been processed and closed, there are still a few left
-	  that need attention, from either the maintainer(s) or other
-	  volunteers.</p>
-      </li><li>
-	<p>Andrew Turner is working on bringing up the arm64
-	  architecture, which is now fully supported in clang and llvm.
-	  This will be a very interesting new area for solving
-	  challenging problems.</p>
-      </li><li>
-	<p>There are still issues with the powerpc and sparc64
-	  architectures, and any help in these areas is very much
-	  appreciated.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-on-POWER8" href="#FreeBSD-on-POWER8" id="FreeBSD-on-POWER8">FreeBSD on POWER8</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.tyan.com/campaign/openpower/" title="http://www.tyan.com/campaign/openpower/">Tyan development reference platform</a></td><td>
-	    URL: <a href="http://www.tyan.com/campaign/openpower/" title="Tyan development reference platform">http://www.tyan.com/campaign/openpower/</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nwhitehorn@freebsd.org">nwhitehorn@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Justin
-	  Hibbits
-	 &lt;<a href="mailto:jhibbits@freebsd.org">jhibbits@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Adrian
-	  Chadd
-	 &lt;<a href="mailto:adrian@freebsd.org">adrian@freebsd.org</a>&gt;
-	</p>
-      <p>IBM and the OpenPOWER Foundation are pushing for a wider
-	software and hardware ecosystem for POWER8-based systems.
-	Starting in January 2014, we have been doing bringup work on a
-	Tyan GN70-BP010 POWER8 server, a quad-core 3 GHz system with a
-	total of 32 hardware threads.</p>
-
-      <p>Updates since the previous report:</p>
-
-      <ul>
-	<li>FreeBSD now boots under a hypervisor with the virtual SCSI
-	  block device; the issue previously preventing this has
-	  been fixed.</li>
-
-	<li>The powerpc64 pmap code was rewritten to be more
-	  scalable, as the previous pmap code did not scale beyond a small
-	  number of CPUs.</li>
-
-	<li>Initial support for IBM's Vector-Scalar Extensions
-	  (VSX) was added.</li>
-
-	<li>The FreeBSD kernel was made completely position
-	  independent for powerpc64, and later powerpc32 as well.</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Get FreeBSD booting natively, rather than under KVM.  This
-	  requires writing OPAL drivers for the various hardware
-	  devices in the system.</p>
-      </li><li>
-	<p>Integrate loader(8) with petitboot.</p>
-      </li></ol><hr /><h2><a name="Jenkins-Continuous-Integration-for-FreeBSD" href="#Jenkins-Continuous-Integration-for-FreeBSD" id="Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://jenkins.freebsd.org" title="https://jenkins.freebsd.org">The Jenkins CI server in the FreeBSD cluster</a></td><td>
-	    URL: <a href="https://jenkins.freebsd.org" title="The Jenkins CI server in the FreeBSD cluster">https://jenkins.freebsd.org</a></td></tr><tr><td><a href="http://www.cloud9ers.com/" title="http://www.cloud9ers.com/">Cloud9ers</a></td><td>
-	    URL: <a href="http://www.cloud9ers.com/" title="Cloud9ers">http://www.cloud9ers.com/</a></td></tr><tr><td><a href="https://wiki.ubuntu.com/AhmedKamal" title="https://wiki.ubuntu.com/AhmedKamal">Ahmed Kamal</a></td><td>
-	    URL: <a href="https://wiki.ubuntu.com/AhmedKamal" title="Ahmed Kamal">https://wiki.ubuntu.com/AhmedKamal</a></td></tr><tr><td><a href="https://github.com/saltstack/salt/pulls?q=is%3Apr+author%3Akim0" title="https://github.com/saltstack/salt/pulls?q=is%3Apr+author%3Akim0">Ahmed's contributions to SaltStack</a></td><td>
-	    URL: <a href="https://github.com/saltstack/salt/pulls?q=is%3Apr+author%3Akim0" title="Ahmed's contributions to SaltStack">https://github.com/saltstack/salt/pulls?q=is%3Apr+author%3Akim0</a></td></tr><tr><td><a href="http://julipedia.meroh.net/2015/02/kyua-turns-parallel.html" title="http://julipedia.meroh.net/2015/02/kyua-turns-parallel.html">Kyua turns parallel</a></td><td>
-	    URL: <a href="http://julipedia.meroh.net/2015/02/kyua-turns-parallel.html" title="Kyua turns parallel">http://julipedia.meroh.net/2015/02/kyua-turns-parallel.html</a></td></tr><tr><td><a href="https://github.com/jenkinsci/multiple-scms-plugin/commits?author=rodrigc" title="https://github.com/jenkinsci/multiple-scms-plugin/commits?author=rodrigc">Jenkins Multiple SCM's plugin fixes</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/multiple-scms-plugin/commits?author=rodrigc" title="Jenkins Multiple SCM's plugin fixes">https://github.com/jenkinsci/multiple-scms-plugin/commits?author=rodrigc</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html" title="https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html">GCC 4.9 problems</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html" title="GCC 4.9 problems">https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html</a></td></tr><tr><td><a href="https://wiki.freebsd.org/ExternalToolchain" title="https://wiki.freebsd.org/ExternalToolchain">External Toolchain Support</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/ExternalToolchain" title="External Toolchain Support">https://wiki.freebsd.org/ExternalToolchain</a></td></tr></table><p>
-	Contact:
-	  Craig
-	  Rodrigues
-	 &lt;<a href="mailto:rodrigc@FreeBSD.org">rodrigc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jenkins Administrators &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Testing &lt;<a href="mailto:freebsd-testing@FreeBSD.org">freebsd-testing@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Jenkins Continuous Integration and Testing
-	project has been helping to improve the quality of FreeBSD.
-	Since the last status report, we have quickly found commits
-	which caused build breakage or test failures.  FreeBSD developers
-	saw these problems and quickly fixed them.  Some of the
-	highlights include:</p>
-
-      <ul>
-	<li><p>Ahmed Kamal agreed to join the jenkins-admin
-	    team.  Even though he is not a FreeBSD committer, he is
-	    subscribed to the jenkins-admin alias, and is contributing
-	    code via GitHub.  Ahmed has contributed multiple SaltStack
-	    scripts which are in the freebsd-ci GitHub repository.  Ahmed
-	    has also found multiple bugs in SaltStack's FreeBSD support.  He
-	    has fixed these bugs and pushed them back to SaltStack via
-	    GitHub pull requests.</p>
-	  <p>Ahmed is a software developer who lives in
-	    Cairo, Egypt.  He presently works for Cloud9ers, a cloud and
-	    devops consulting firm.  In the past, he has worked for
-	    Canonical as the Ubuntu Cloud and Server community liaison.</p>
-	  <p>Ahmed found out about the Request for Help sent
-	    out by Craig Rodrigues for help with Jenkins in FreeBSD via a random
-	    web search.  Ahmed found FreeBSD to be a very nice project, and
-	    was eager to volunteer and help out, and responded to the
-	    Request.  Ahmed will attend BSDCan, where he will learn more
-	    about the BSD Community.</p>
-	</li>
-
-	<li>Julio Merino extended Kyua to support executing test
-	  cases in parallel.  This should help the scaling of testing in
-	  environments with thousands of test cases.</li>
-
-	<li>Craig Rodrigues got a commit bit to the Jenkins
-	  Multiple SCM's plugin, and committed fixes to that plugin to
-	  help it work with Subversion 1.8 </li>
-
-	<li>Craig Rodrigues worked with Dimitry Andric in the
-	  freebsd-toolchain team to help identify and fix several
-	  compile problems in the FreeBSD src tree when using GCC 4.9.
-	  This work will help with the External Toolchain project.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Set up more builds based on different architectures.</p>
-      </li><li>
-	<p>Improve the maintenance of nodes in the Jenkins cluster
-	   using devops frameworks such as Saltstack.</p>
-      </li><li>
-	<p>People interested in helping out should join the
-	  freebsd-testing@FreeBSD.org list.</p>
-      </li></ol><hr /><h2><a name="Lua-boot-loader" href="#Lua-boot-loader" id="Lua-boot-loader">Lua boot loader</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base/projects/lua-bootloader/" title="https://svnweb.freebsd.org/base/projects/lua-bootloader/"></a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base/projects/lua-bootloader/" title="">https://svnweb.freebsd.org/base/projects/lua-bootloader/</a></td></tr></table><p>
-	Contact:
-	  Rui
-	  Paulo
-	 &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Pedro
-	  Souza
-	 &lt;<a href="mailto:pedrosouza@FreeBSD.org">pedrosouza@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Koszek
-	 &lt;<a href="mailto:wkoszek@FreeBSD.org">wkoszek@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Lua boot loader project is in its final stage and
-	it can be used on x86 already.  The aim of this project is to
-	replace the Forth boot loader with a Lua boot loader.  All the
-	scripts were re-written in Lua and are available in
-	sys/boot/lua.  Once all the Forth features have been tested
-	and the boot menus look exactly like in Forth, we will
-	start merging this project to FreeBSD HEAD.  Both loaders can
-	co-exist in the source tree with no problems because a
-	pluggable loader was introduced for this purpose.</p>
-
-      <p>The project was initially started by Wojciech
-	Koszek, and Pedro Souza wrote most of the Lua code last year in
-	his Google Summer of Code project.</p>
-
-      <p>To build a Lua boot loader just use:</p>
-<pre xml:space="preserve">WITH_LUA=y
-WITHOUT_FORTH=y</pre>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Feature/appearance parity with Forth.</p>
-      </li><li>
-	<p>Investigate use of floating point by Lua.</p>
-      </li><li>
-	<p>Test the EFI Lua loader.</p>
-      </li><li>
-	<p>Test the U-Boot Lua loader.</p>
-      </li><li>
-	<p>Test the serial console.</p>
-      </li></ol><hr /><h2><a name="Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support" href="#Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support" id="Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support">Mellanox iSCSI Extensions for RDMA (iSER) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact:
-	  Max
-	  Gurtovoy
-	 &lt;<a href="mailto:maxg@mellanox.com">maxg@mellanox.com</a>&gt;
-	<br />
-	Contact:
-	  Sagi
-	  Grimberg
-	 &lt;<a href="mailto:sagig@mellanox.com">sagig@mellanox.com</a>&gt;
-	</p>
-      <p>Building on the new in-kernel iSCSI initiator stack
-	released in FreeBSD 10.0, and the recently added iSCSI offload
-	interface, Mellanox Technologies has begun developing iSCSI
-	extensions for RDMA (iSER) initiator support to enable efficient
-	data movement using the hardware offload capabilities of
-	Mellanox's 10, 40, 56, and 100 gigabit IB/Ethernet adapters.</p>
-
-      <p>Remote Direct Memory Access (RDMA) has been shown to
-	have a great value for storage applications.  RDMA
-	infrastructure provides benefits such as zero-copy, CPU offload,
-	reliable transport, fabric consolidation and many more.  The
-	iSER protocol eliminates some of the bottlenecks in the
-	traditional iSCSI/TCP stack, provides low latency and high
-	throughput, and is well suited for latency-aware workloads.</p>
-
-      <p>This work includes a new ICL module that implements the
-	iSER initiator.  The iSCSI stack is slightly modified to support
-	some extra features such as asynchronous IO completions,
-	unmapped data buffers, and data-transfer offloads.  The user will
-	be able to choose iSER as the iSCSI transport with iscsictl(8).</p>
-
-      <p> The project is in its initial implementation phase.  The
-	code will be released under the BSD license and is expected to
-	be completed later this year.  </p>
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="Multipath-TCP-for-FreeBSD" href="#Multipath-TCP-for-FreeBSD" id="Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="http://caia.swin.edu.au/urp/newtcp/mptcp/"></a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="">http://caia.swin.edu.au/urp/newtcp/mptcp/</a></td></tr></table><p>
-	Contact:
-	  Nigel
-	  Williams
-	 &lt;<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>&gt;
-	</p>
-      <p>Multipath TCP (MPTCP) is an extension to TCP that allows
-	for the use of multiple network interfaces on a standard TCP
-	session.  The addition of new addresses and scheduling of data
-	across these occurs transparently from the perspective of the
-	TCP application.</p>
-
-      <p>The goal of this project is to deliver an MPTCP
-	kernel patch that interoperates with the reference MPTCP
-	implementation, along with additional enhancements to aid
-	network research.</p>
-
-      <p>After a major re-design of the earlier prototype
-	implementation, the patch is again able to establish and carry
-	out multi-path connections that incorporate multiple addresses.
-	Improvements have also been made to path management and to the
-	code handling the addition of subflows to a connection.</p>
-
-      <p>Most recently data-level re-transmission support has been added
-	and is being tested.  Soon more extensive testing of the patch
-	in different multi-path scenarios will begin, with plans for a
-	public release of v0.5 in May.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Testing of data-level re-transmission.</p>
-      </li><li>
-	<p>Basic support for per-subflow congestion control
-	  algorithm selection.</p>
-      </li><li>
-	<p>Testing and release of v0.5 patch.</p>
-      </li></ol><hr /><h2><a name="New-Automounter" href="#New-Automounter" id="New-Automounter">New Automounter</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Automounter" title="https://wiki.freebsd.org/Automounter"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Automounter" title="">https://wiki.freebsd.org/Automounter</a></td></tr><tr><td><a href="http://people.freebsd.org/~trasz/autofs.pdf" title="http://people.freebsd.org/~trasz/autofs.pdf"></a></td><td>
-	    URL: <a href="http://people.freebsd.org/~trasz/autofs.pdf" title="">http://people.freebsd.org/~trasz/autofs.pdf</a></td></tr><tr><td><a href="http://freebsdfoundation.blogspot.com/2015/03/freebsd-from-trenches-using-autofs5-to_13.html" title="http://freebsdfoundation.blogspot.com/2015/03/freebsd-from-trenches-using-autofs5-to_13.html"></a></td><td>
-	    URL: <a href="http://freebsdfoundation.blogspot.com/2015/03/freebsd-from-trenches-using-autofs5-to_13.html" title="">http://freebsdfoundation.blogspot.com/2015/03/freebsd-from-trenches-using-autofs5-to_13.html</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new automounter is a cleanroom implementation of
-	functionality available in most other Unix systems, using proper
-	kernel support implemented via an autofs filesystem.  The
-	automounter supports a standard map format, and integrates with
-	the Lightweight Directory Access Protocol (LDAP) service.</p>
-
-      <p>After shipping in 10.1-RELEASE, most of the work focused
-	on bug fixing, improving documentation, and optimization.  The
-	biggest new feature was the addition of a "-media" map, designed
-	to handle removable media, such as flash drives or DVDs, and the
-	necessary elements of infrastructure to support it, namely
-	fstyp(8) and GEOM devd notifications.  Also, the "-noauto" map
-	was added, for automatic mounting of filesystems marked "noauto"
-	in fstab(5), instead of having to write an autofs map for them.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Opaque-ifnet" href="#Opaque-ifnet" id="Opaque-ifnet">Opaque ifnet</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/projects/ifnet" title="https://wiki.freebsd.org/projects/ifnet">Project wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/projects/ifnet" title="Project wiki page">https://wiki.freebsd.org/projects/ifnet</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Smirnoff
-	 &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project aims to design a new KPI for network drivers
-	that would allow the network stack to evolve without
-	breaking compatibility with older drivers.  The core idea is to
-	hide <tt>struct ifnet</tt> from drivers, giving the
-	project the name "opaque ifnet".  However, the
-	project will include more changes than just hiding the
-	struct's definition.</p>
-
-      <p>At present, the new KPI has been prototyped, most of the
-	important parts of network stack have been modified
-	appropriately, and several drivers have been converted to the new
-	KPI.</p>
-
-      <p>The project needs more manpower, since there are many
-	network drivers in the tree, with a total of 245 sites where a
-	<tt>struct ifnet</tt> is allocated.</p>
-    <p>This project was sponsored by Netflix.</p><h3>Open tasks:</h3><ol><li>
-	<p>Convert more drivers.</p>
-      </li></ol><hr /><h2><a name="pkg" href="#pkg" id="pkg">pkg</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/pkg" title="https://github.com/freebsd/pkg">pkg's Github Repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/pkg" title="pkg's Github Repo">https://github.com/freebsd/pkg</a></td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-pkg" title="https://lists.freebsd.org/mailman/listinfo/freebsd-pkg">The pkg Mailing List</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-pkg" title="The pkg Mailing List">https://lists.freebsd.org/mailman/listinfo/freebsd-pkg</a></td></tr></table><p>
-	Contact:
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Vsevolod
-	  Stakhov
-	 &lt;<a href="mailto:vsevolod@FreeBSD.org">vsevolod@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Andrej
-	  Zverev
-	 &lt;<a href="mailto:az@FreeBSD.org">az@FreeBSD.org</a>&gt;
-	</p>
-      <p>Lots of work has been done on the pkg(8) front, which has brought
-	pkg(8) to the 1.5.0 release.</p>
-
-      <p>Special attention has been spent on the test suite; the
-	number of tests went from around 20 to more than 70.  They
-	are mostly functional tests, each of which tests many different
-	features, with less emphasis on unit tests.</p>
-
-      <p>One of the main highlights is initial support for
-	provides/requires.  This is still
-	simple but is good enough to allow fixing a lot of situations when
-	dealing with php-related ports: PHP can now safely upgrade from one
-	major version to another.  This allows for the pecl/pear
-	packages to be reinstalled each time a minor php upgrade is
-	done.</p>
-
-      <p>Some pkg internals have been reworked to allow cross installation
-	of packages without the need for chroot(2) or jail(2) calls.</p>
-
-      <p>The plist and keyword parser have been improved to keep simplifying
-	creating new ports:</p>
-	<ul>
-	  <li>Keywords can now have arguments</li>
-	  <li>A lazy mode is available for setting credentials via the
-	    plist</li>
-	  <li>Flags (immutable and others) can now be specified in
-	    the plist</li>
-	</ul>
-
-       <p>pkg now supports resume for http/ftp downloads.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Populate the ports tree with provides/requires.</p>
-      </li><li>
-	<p>Make all scripts in the ports tree support cross
-	  installation.</p>
-      </li><li>
-	<p>Improve provides/requires.</p>
-      </li><li>
-	<p>Continue adding more tests.</p>
-      </li></ol><hr /><h2><a name="Secure-Boot" href="#Secure-Boot" id="Secure-Boot">Secure Boot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SecureBoot" title="https://wiki.freebsd.org/SecureBoot"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SecureBoot" title="">https://wiki.freebsd.org/SecureBoot</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>UEFI Secure Boot is a mechanism that requires boot
-	drivers and operating system loaders to be cryptographically
-	signed by an authorized key.  It will refuse to execute any
-	software that is not correctly signed, and is intended to secure
-	boot drivers and operating system loaders from malicious
-	tampering or replacement.</p>
-
-      <p>The utility to add Authenticode signatures to EFI files,
-	uefisign(8), was committed to 11-CURRENT and will ship in
-	10.2-RELEASE.  Ports for other open source utilities were added
-	to the Ports Collection, as <tt>sysutils/pesign</tt>,
-	<tt>sysutils/sbsigntool</tt>, and <tt>sysutils/shim</tt>.  There
-	is a prototype patch that makes boot1 use the Secure Boot shim, and
-	modifies the shim to provide the functionality necessary
-	for a successful bootstrap.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Finalize the shim API extension and get it accepted
-	  upstream.</p>
-      </li><li>
-	<p>Commit boot1 changes.</p>
-      </li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Adding-PCIe-Hot-plug-Support" href="#Adding-PCIe-Hot-plug-Support" id="Adding-PCIe-Hot-plug-Support">Adding PCIe Hot-plug Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=LQ6@//depot/projects/pciehotplug/?ac=83" title="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=LQ6@//depot/projects/pciehotplug/?ac=83">PCIe Hot-plug Perforce Branch</a></td><td>
-	    URL: <a href="http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=LQ6@//depot/projects/pciehotplug/?ac=83" title="PCIe Hot-plug Perforce Branch">http://p4web.freebsd.org/@md=d&amp;cd=//depot/projects/&amp;c=LQ6@//depot/projects/pciehotplug/?ac=83</a></td></tr></table><p>
-	Contact:
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>PCI Express (PCIe) hot-plug is used on both laptops and
-	servers to allow peripheral devices to be added or removed
-	while the system is running.  Laptops commonly include
-	hot-pluggable PCIe as either an ExpressCard slot or
-	a Thunderbolt interface.  ExpressCard has built-in USB support
-	that is already supported by FreeBSD, but ExpressCard PCIe
-	devices like Gigabit Ethernet adapters and eSATA cards are
-	only supported when they are present at boot, and removal may
-	cause a kernel panic.</p>
-
-      <p>The goal of this project is to allow these devices to
-	be inserted and removed while FreeBSD is running.  The work
-	will provide the basic infrastructure to support adding and
-	removing devices, though it is expected that additional work
-	will be needed to update individual drivers to support
-	hot-plug.</p>
-
-      <p>Current testing is focused on getting a simple UART
-	device functional.  Basic hot swap is functional.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Get suspend/resume functional by saving/restoring the necessary
-	  registers.</p>
-      </li><li>
-	<p>Make sure that upon suspend, devices are removed so that
-	  if they are replaced while the machine is suspended, the
-	  new devices will be detected.</p>
-      </li><li>
-	<p>Improve how state transitions are handled, possibly by
-	  using a proper state machine.</p>
-      </li></ol><hr /><h2><a name="Address-Space-Layout-Randomization-(ASLR)" href="#Address-Space-Layout-Randomization-(ASLR)" id="Address-Space-Layout-Randomization-(ASLR)">Address Space Layout Randomization (ASLR)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://hardenedbsd.org/" title="https://hardenedbsd.org/">HardenedBSD</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/" title="HardenedBSD">https://hardenedbsd.org/</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054669.html" title="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054669.html">ASLR Call For Testing</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054669.html" title="ASLR Call For Testing">https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054669.html</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D473" title="https://reviews.freebsd.org/D473">FreeBSD Code Review of ASLR</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D473" title="FreeBSD Code Review of ASLR">https://reviews.freebsd.org/D473</a></td></tr></table><p>
-	Contact:
-	  Shawn
-	  Webb
-	 &lt;<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>&gt;
-	<br />
-	Contact:
-	  Oliver
-	  Pinter
-	 &lt;<a href="mailto:oliver.pinter@hardenedbsd.org">oliver.pinter@hardenedbsd.org</a>&gt;
-	</p>
-      <p>Address Space Layout Randomization (ASLR) is a
-	computer security technique that aids in mitigating
-	low-level vulnerabilities such as buffer overflows.
-	ASLR randomizes the memory layout of running
-	applications to prevent an attacker from knowing where
-	a given exploitable vulnerability lies in memory.</p>
-
-      <p>We have been working hard the last few months to ensure
-	the robustness of our ASLR implementation.  We have
-	written a manpage and updated the patch on
-	FreeBSD's code review system (Phabricator).  Our ASLR
-	implementation is in use by the HardenedBSD team
-	in production environments and is performing
-	robustly.</p>
-
-      <p>The next task is to compile the base system applications as
-	Position-Independent Executables (PIEs).  For
-	ASLR to be effective, applications must be compiled as
-	PIEs to allow the main binary, as well as shared libraries, to be
-	located at random addresses.  It is likely that this part will take a
-	long time to accomplish, given the complexity surrounding
-	building the libraries in the base system.  Even if applications
-	are not compiled as PIEs, having ASLR available still
-	helps those applications (like HardenedBSD's secadm)
-	which force compilation as PIE for themselves.</p>
-    <p>This project was sponsored by SoldierX.</p><h3>Open tasks:</h3><ol><li>
-	<p>Test our patch against 11-CURRENT.</p>
-      </li></ol><hr /><h2><a name="Modern-x86-platform-support-and-VT-d" href="#Modern-x86-platform-support-and-VT-d" id="Modern-x86-platform-support-and-VT-d">Modern x86 platform support and VT-d</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Modern x86 platforms include a number of architectural
-	enhancements.  Work is ongoing to support these features in
-	FreeBSD.</p>
-
-      <p>Starting with SandyBridge CPUs, Intel introduced an
-	enhanced local interrupt controller (APIC) mode, called x2APIC.
-	Instead of using a mapped page, registers are now accessed using
-	special Model-Specific Registers (MSR) read and write
-	instructions.  This is intended to support virtualization.  The
-	access overhead is also reduced by not requiring serialization,
-	and by simplification of Inter-Process Interrupt (IPI)
-	generation.  The main commit introducing the feature was
-	r278473, with fixes following on.</p>
-
-      <p>End Of Interrupt (EOI) suppression is a mode of EOI
-	delivery to Input/Output Interrupt Controllers (IO-APICs) where
-	the EOI message for a level-triggered interrupt is not broadcast
-	by an EOI write to the local APIC, but instead an explicit EOI
-	command is sent to the source IO-APIC.  The optimization reduces
-	the number of APIC messages that must be broadcast; it should
-	be used on all modern Intel systems.  Support for EOI
-	suppression was committed in r279319.</p>
-
-      <p>VT-d Interrupt Remapping (IR) is provided by hardware
-	with the VT-d feature.  It translates interrupt messages on the
-	way from the root complex to the north bridge and allows control
-	of interrupt delivery without reprogramming MSI/MSI-X registers
-	or IO-APICs.  The original intent was to allow hypervisors to
-	safely delegate interrupt programming for devices owned by
-	guests to the guest OS.  IR is also needed to avoid some
-	limitations in IO-APICs and to make interrupt rebalancing atomic
-	and transparent.  Support has been committed as r280260.</p>
-
-      <p>Both x2APIC mode and IR are required to send IPIs and
-	device interrupts to processors with LAPIC ID greater then 254.
-	It is believed that the only missing platform code to handle big
-	machines is parsing the "Processor Local x2APIC Structure" and
-	"Local x2APIC NMI Structure" from the ACPI Multiple APIC
-	Description Table (MADT), which report LAPIC IDs &gt; 255, and
-	handling boot on such systems with the x2APIC mode enabled by
-	firmware.  The work to complete that is expected to be
-	relatively trivial, and can be done with access to a real
-	high-core-count machine.  But an audit of the common
-	machine-independent code must be finished to ensure that large
-	CPU IDs are handled correctly, before such support can
-	safely be enabled.</p>
-
-      <p>Additional work remains in progress: split domains and
-	contexts for DMA Remapper Unit (DMAR) driver.  Right now, the
-	DMAR driver is only used to implement busdma(9), which is done
-	by assigning a dedicated domain to each translation context.
-	Some devices could issue PCIe Transaction Layer Packets (TLPs)
-	with several originators IDs, e.g.,  PCIe/PCI bridges, or
-	phantom functions of PCIe devices, or such TLPs could occur just
-	due to hardware bugs.  To handle them, a single domain (which
-	shares the translation page tables) must handle several
-	contexts.</p>
-
-      <p>Splitting domains and contexts is also required for the
-	DMAR driver to start handling PCI pass-through in bhyve, instead
-	of the less complete implementation which is currently provided
-	by bhyve itself.  All PCIe devices passed to the guest must
-	share a domain.  The splitting patch is written and is being
-	tested, and external interfaces to manage domains are being
-	formed.</p>
-
-      <p>Stability work for the VT-d code is ongoing.  In
-	particular, nvme(4) and ixgbe(4)'s use of busdma interfaces was
-	debugged and improved, and tested on a very large-memory
-	machine.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Nanosecond-file-timestamps" href="#Nanosecond-file-timestamps" id="Nanosecond-file-timestamps">Nanosecond file timestamps</a></h2><p>
-	Contact:
-	  Jilles
-	  Tjoelker
-	 &lt;<a href="mailto:jilles@FreeBSD.org">jilles@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Sergey
-	  Kandaurov
-	 &lt;<a href="mailto:pluknet@FreeBSD.org">pluknet@FreeBSD.org</a>&gt;
-	</p>
-      <p>Two new system calls, futimens() and utimensat(), were
-	added, making it possible to set file timestamps with nanosecond
-	accuracy.  Various utilities like cp, mv and touch were updated
-	to use the new calls to preserve and set timestamps with full
-	precision.</p>
-
-      <p>The stat() and related system calls have returned file
-	timestamps with nanosecond accuracy for a long time, but there
-	was no way to set a timestamp more accurately than
-	microseconds.</p>
-
-      <p>With these changes, it will be possible to use more
-	accurate timestamps (sysctl vfs.timestamp_precision=3) without
-	anomalies such as a copy of a file (from cp -p) appearing older
-	than the original.  This is particularly useful for NFS servers,
-	which use file timestamps for cache invalidation.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Where possible, fix code that still sets inaccurate
-	  timestamps on files, typically by calling futimes(),
-	  futimesat(), lutimes(), utime() or utimes() with a non-null
-	  times pointer.  There may be a reason for this such as a limited
-	  network protocol or file format, but there is some code left
-	  that can be fixed.</p>
-      </li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-newer-ARM-boards" href="#FreeBSD-on-newer-ARM-boards" id="FreeBSD-on-newer-ARM-boards">FreeBSD on newer ARM boards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1" title="https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1">FreeBSD on Odroid-C1</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1" title="FreeBSD on Odroid-C1">https://wiki.freebsd.org/FreeBSD/arm/Odroid-C1</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/280905" title="https://svnweb.freebsd.org/changeset/base/280905"></a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/280905" title="">https://svnweb.freebsd.org/changeset/base/280905</a></td></tr></table><p>
-	Contact:
-	John
-	Wehle
-       &lt;<a href="mailto:john@feith.com">john@feith.com</a>&gt;
-	<br />
-	Contact:
-	Ganbold
-	Tsagaankhuu
-       &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-     <p>We made the changes necessary to support various Amlogic SoC
-      devices, specifically aml8726-m6 and aml8726-m8b SoC-based devices.
-      The aml8726-m6 SoC is used in devices such as the Visson
-      ATV-102, and the Hardkernel ODROID-C1 board uses the
-      aml8726-m8b SoC.  The following support is included:</p>
-
-      <ul>
-	<li>Basic machdep code</li>
-	<li>SMP</li>
-	<li>Interrupt controller</li>
-	<li>Clock control driver (aka gate)</li>
-	<li>Pinctrl</li>
-	<li>Timer</li>
-	<li>Real time clock</li>
-	<li>UART</li>
-	<li>GPIO</li>
-	<li>I2C</li>
-	<li>SD controller</li>
-	<li>SDXC controller</li>
-	<li>USB</li>
-	<li>Watchdog</li>
-	<li>Random number generator</li>
-	<li>PLL/Clock frequency measurement</li>
-	<li>Frame buffer</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Get the DWC driver working.</p>
-      </li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/arm64" title="https://wiki.freebsd.org/arm64">FreeBSD arm64 wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/arm64" title="FreeBSD arm64 wiki page">https://wiki.freebsd.org/arm64</a></td></tr><tr><td><a href="https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev" title="https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev">GitHub arm64 development repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev" title="GitHub arm64 development repository">https://github.com/FreeBSDFoundation/freebsd/tree/arm64-dev</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	</p>
-      <p>The collaborative development on the FreeBSD arm64 port
-	made significant progress over the last quarter.  The FreeBSD
-	Foundation is collaborating with ARM, Cavium, the Semihalf team,
-	and Andrew Turner to port FreeBSD to the arm64 architecture,
-	also known as ARMv8 and AArch64.</p>
-
-      <p>After significant review and refinement, the initial set
-	of changes are being delivered into FreeBSD-HEAD.  This initial
-	support targets the QEMU and ARM Foundation Model emulators, and
-	boots to a usable multiuser environment.</p>
-
-      <p>Cavium's ThunderX platform is the initial hardware
-	reference target for the FreeBSD arm64 port.  The platform
-	currently boots to multiuser, with a root file system mounted
-	over NFS via a PCIe 10 Gbps Ethernet NIC.  Reference hardware is
-	installed in the FreeBSD test lab hosted by Sentex Communications
-	and in Semihalf's offices.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, ARM, and Cavium.</p><h3>Open tasks:</h3><ol><li>
-	<p>Merge kernel changes to HEAD.</p>
-      </li><li>
-	<p>Finish remaining userland and kernel support.</p>
-      </li><li>
-	<p>Produce installable images.</p>
-      </li></ol><hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-on-ec2/" title="http://www.daemonology.net/freebsd-on-ec2/"></a></td><td>
-	    URL: <a href="http://www.daemonology.net/freebsd-on-ec2/" title="">http://www.daemonology.net/freebsd-on-ec2/</a></td></tr></table><p>
-	Contact:
-	  Colin
-	  Percival
-	 &lt;<a href="mailto:cperciva@freebsd.org">cperciva@freebsd.org</a>&gt;
-	</p>
-      <p>Support for building Amazon Machine Images ("AMIs") for
-	Amazon EC2 is now in the src tree, via <tt>make
-	  ec2ami</tt> in src/release.  The platform is functional and
-	stable, and pre-built images are available in all of the public
-	EC2 regions.</p>
-
-      <p>The Amazon Web Services Marketplace reports that
-	approximately 400 users are running approximately 800 FreeBSD EC2
-	instances.  This is an underestimate since it only counts
-	instances launched via the AWS Marketplace.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>MFC AMI-building code to stable/10 in time for FreeBSD
-	  10.2-RELEASE.</p>
-      </li><li>
-	<p>Complete the AMI-building handoff to the release
-	  engineering team.</p>
-      </li><li>
-	<p>Teach the blkfront driver to use indirect segment
-	  requests in order to significantly increase I/O performance.</p>
-      </li><li>
-	<p>Get working SR-IOV driver for the Intel network cards
-	  found in EC2 "Enhanced Networking" in order to significantly
-	  increase networking performance.</p>
-      </li></ol><hr /><h2><a name="Nested-Kernel" href="#Nested-Kernel" id="Nested-Kernel">Nested Kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://nestedkernel.org" title="http://nestedkernel.org">Home page for the project that includes links to papers and build instructions.</a></td><td>
-	    URL: <a href="http://nestedkernel.org" title="Home page for the project that includes links to papers and build instructions.">http://nestedkernel.org</a></td></tr><tr><td><a href="http://web.engr.illinois.edu/~dautenh1//downloads/publications/asplos200-dautenhahn.pdf" title="http://web.engr.illinois.edu/~dautenh1//downloads/publications/asplos200-dautenhahn.pdf">Conference publication detailing the problem, design, implementation, and evaluation of our prototype.</a></td><td>
-	    URL: <a href="http://web.engr.illinois.edu/~dautenh1//downloads/publications/asplos200-dautenhahn.pdf" title="Conference publication detailing the problem, design, implementation, and evaluation of our prototype.">http://web.engr.illinois.edu/~dautenh1//downloads/publications/asplos200-dautenhahn.pdf</a></td></tr><tr><td><a href="http://prezi.com/in6qr3l92ffc/?utm_campaign=share&amp;utm_medium=copy" title="http://prezi.com/in6qr3l92ffc/?utm_campaign=share&amp;utm_medium=copy">Presentation on the nested kernel</a></td><td>
-	    URL: <a href="http://prezi.com/in6qr3l92ffc/?utm_campaign=share&amp;utm_medium=copy" title="Presentation on the nested kernel">http://prezi.com/in6qr3l92ffc/?utm_campaign=share&amp;utm_medium=copy</a></td></tr><tr><td><a href="https://github.com/HardenedBSD/hardenedBSD/tree/hardened/9/kernsep" title="https://github.com/HardenedBSD/hardenedBSD/tree/hardened/9/kernsep">HardenedBSD branch of the nested kernel being refactored.</a></td><td>
-	    URL: <a href="https://github.com/HardenedBSD/hardenedBSD/tree/hardened/9/kernsep" title="HardenedBSD branch of the nested kernel being refactored.">https://github.com/HardenedBSD/hardenedBSD/tree/hardened/9/kernsep</a></td></tr></table><p>
-	Contact:
-	  Nathan
-	  Dautenhahn
-	 &lt;<a href="mailto:dautenh1@illinois.edu">dautenh1@illinois.edu</a>&gt;
-	<br />
-	Contact:
-	  Theodoros
-	  Kasampalis
-	 &lt;<a href="mailto:kasampa2@illinois.edu">kasampa2@illinois.edu</a>&gt;
-	<br />
-	Contact:
-	  Will
-	  Dietz
-	 &lt;<a href="mailto:wdietz2@illinois.edu">wdietz2@illinois.edu</a>&gt;
-	</p>
-      <p>This work on a nested kernel architecture is part of
-	Nathan's doctoral thesis work at the University of Illinois at
-	Urbana-Champaign.  It attempts to improve upon the traditional
-	monolithic operating system kernel, where a single exploit
-	anywhere in the kernel grants the attacker full superuser
-	privileges.  The nested kernel operating system architecture
-	addresses this problem by "nesting" a small, isolated kernel
-	within a traditional monolithic kernel.  This "nested kernel"
-	interposes on all updates to virtual memory translations to
-	assert protections on physical memory, thus significantly
-	reducing the trusted computing base for memory access control
-	enforcement.  </p>
-
-      <p>We incorporated the nested kernel
-	architecture into FreeBSD on x86-64 hardware by write-protecting
-	Memory-Management Unit (MMU) translations and de-privileging the
-	untrusted part of the kernel, thereby enabling the entire
-	operating system, trusted and untrusted components alike, to
-	operate at the highest hardware privilege level.  Our
-	implementation inherently enforces kernel code integrity while
-	still allowing dynamically loaded kernel modules, thus defending
-	against code injection attacks.  We also demonstrate, by
-	introducing write-mediation and write-logging services, that the
-	nested kernel architecture allows kernel developers to isolate
-	memory in ways not possible in monolithic kernels, though
-	gaining security benefits from this will require adding
-	policies that have not yet been designed.</p>
-
-      <p>The performance of the nested kernel prototype shows modest
-	overheads: less than 1% average for Apache, 3.7% average for
-	sshd, and 2.7% average for kernel compilation.  Overall, our
-	results and experience show that the nested kernel design can be
-	retrofitted onto existing monolithic kernels, providing defense
-	in depth.</p>
-
-      <p>The basic idea is that the nested kernel initializes the
-	system so that all page tables are mapped as read-only.  Then
-	all MMU-modifying operations are removed from the untrusted
-	portion of the kernel; runtime code integrity is enforced by
-	write-protecting all code pages, marking all non-code
-	pages as non-executable (NX-bit), and preventing execution of
-	privileged MMU operations located in userspace mappings
-	(Supervisor Mode Execution Prevention, SMEP).  Because the
-	nested kernel has control of the page tables it can enforce
-	these integrity properties, leading to virtualization of the
-	MMU.</p>
-
-      <p>The links include a recent conference publication that
-	details the design, implementation, and evaluation of our
-	prototype nested kernel architecture on top of FreeBSD 9.0.
-	There is also a link to a presentation on the nested
-	kernel, and a website with information about the project and
-	instructions on how to get the source and build it.</p>
-
-      <p>We are very interested in feedback on the design of the
-	nested kernel, and having discussions about how it might get
-	upstreamed.</p>
-
-      <p>We are also hoping to gain additional contributors and
-	interest in the project!  The nested kernel has the potential to
-	enhance commodity operating system design, and FreeBSD is a major
-	operating system in use today which has high impact.
-	The current implementation is merely a research prototype and
-	requires significant effort to make production-ready (see the
-	list of tasks).</p>
-
-      <p>Finally, we have developed an interface to write-protect
-	data structures in the kernel and are soliciting ideas for uses
-	of this service.  Section 2.4 in the paper details the
-	interface, and section 4 presents some simple uses of the nested
-	kernel services.  We are interested in ways that the nested
-	kernel could be used to protect critical kernel data structures
-	from malware or even just buggy code.</p>
-    <p>This project was sponsored by University of Illinois at Urbana-Champaign, and ONR via grant number N00014-12-1-0552.</p><h3>Open tasks:</h3><ol><li>
-	<p>Finish implementing core mechanisms: verify DMAP is
-	  properly protected and that we are not using superpages (I think
-	  we have this completed but need to fully verify), full NX
-	  support for all non-kernel code pages (we might need to
-	  specially consider the stack if it is used to execute code),
-	  protect IDT and SMM, and add IOMMU protections.  We also need to
-	  do some optimizations where we batch calls into the nested
-	  kernel on process creation (<tt>fork</tt>) and
-	  <tt>mmap</tt> operations.  The
-	  motivation for these implementation directives can be reviewed
-	  in the paper.</p>
-      </li><li>
-	<p>Implement SMP functionality and evaluate performance.</p>
-      </li><li>
-	<p>Port and refactor for FreeBSD-HEAD.  The
-	  current implementation is a research prototype and requires some
-	  refactoring to make it clean and consistent, as well as make it
-	  relevant to modern versions of FreeBSD.</p>
-      </li><li>
-	<p>The nested kernel isolation depends upon certain
-	  hardware instructions to be completely removed from a subset of
-	  the kernel.  Therefore, we need to utilize automated linker/loader
-	  techniques to identify and remove privileged MMU operations from
-	  untrusted kernel components to make it maintainable in
-	  practice.</p>
-      </li><li>
-	<p>Detailed review on the design and implementation with
-	  particular focus on a plan for upstreaming.</p>
-      </li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="libthr-improvements" href="#libthr-improvements" id="libthr-improvements">libthr improvements</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Historically, dynamic loading of the libthr.so thread
-	library into a single-threaded process did not work in FreeBSD.
-	The longstanding recommendation to work around the problem has
-	been to always link the main binary with -lpthread if there was
-	any chance of a need for threading functionality.  This project
-	converted libthr.so into a plugin for libc, which fixed the
-	known issues preventing dynamic loading of libthr.so.</p>
-
-      <p>After the fix, linking the main binary with -lpthread is
-	no longer required, but is not harmful.  I recommend thoroughly
-	testing before removing libpthread from the library list in
-	favor of dynamic loading, though.  Note that potential problems
-	will be subtle and their user-visible manifestations in the
-	affected program even more surprising.</p>
-
-      <p>The following issues were present in the old version of
-	libthr with respect to dynamic loading, but are fixed as
-	a result of this work:</p>
-
-      <ul>
-	<li>Invalid errno value seen after failed syscalls.</li>
-	<li>Broken libthr internal locks and critical sections ignored
-	  by signals.</li>
-	<li>Hung attempts to lock mutexes.</li>
-	<li>Thread cancellation not occurring at guaranteed cancellation
-	  points.</li>
-      </ul>
-
-      <p>The main change was committed as r276630 to HEAD, with many
-	follow ups.  It was merged to stable/10 in r277317.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Migration-to-ELF-Tool-Chain-tools" href="#Migration-to-ELF-Tool-Chain-tools" id="Migration-to-ELF-Tool-Chain-tools">Migration to ELF Tool Chain tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://elftoolchain.sourceforge.net" title="http://elftoolchain.sourceforge.net">FreeBSD LLDB wiki page</a></td><td>
-	    URL: <a href="http://elftoolchain.sourceforge.net" title="FreeBSD LLDB wiki page">http://elftoolchain.sourceforge.net</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ELF Tool Chain project provides BSD-licensed
-	implementations of compilation tools and libraries for building
-	and analyzing ELF objects.  The project began as part of FreeBSD
-	but later became an independent project to encourage wider
-	participation from others in the open-source developer
-	community.</p>
-
-      <p>ELF Tool Chain provides a set of tools equivalent to the
-	GNU Binutils suite.  This project's goal is to import these
-	tools into the FreeBSD base system so that we have a set of
-	up-to-date and maintained tools that also provide support for
-	new CPU architectures of interest, such as arm64.</p>
-
-      <p>In addition to the libelf and libdwarf libraries, the
-	following tools are now provided by the ELF Tool Chain
-	project:</p>
-
-      <ul>
-	<li>addr2line</li>
-	<li>nm</li>
-	<li>readelf</li>
-	<li>size</li>
-	<li>strings</li>
-	<li>strip (elfcopy)</li>
-      </ul>
-
-      <p>ELF Tool Chain's elfcopy provides equivalent
-	functionality to Binutils' objcopy, and accepts the same
-	command-line arguments.  For it to be a viable replacement for
-	all uses of objcopy in the base system, it must gain support for
-	writing portable executable (PE) format binaries, which are used
-	by UEFI boot code.</p>
-
-      <p>The ELF Tool Chain project does not currently provide
-	replacements for as, ld, or objdump.  For FreeBSD, these tools will
-	likely be obtained from the LLVM project.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Add missing functionality to elfcopy and migrate the base
-	  system build.</p>
-      </li><li>
-	<p>Fix issues found by fuzzing inputs to the tools.</p>
-      </li><li>
-	<p>Add automatic support for separate debug files.</p>
-      </li></ol><hr /><h2><a name="The-LLDB-Debugger" href="#The-LLDB-Debugger" id="The-LLDB-Debugger">The LLDB Debugger</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/lldb" title="https://wiki.freebsd.org/lldb">FreeBSD LLDB wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/lldb" title="FreeBSD LLDB wiki page">https://wiki.freebsd.org/lldb</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLDB is the debugger project associated with Clang/LLVM.
-	It supports the Mac OS X, Linux, FreeBSD and Windows platforms.  It
-	builds on existing components in the larger LLVM project, for
-	example using Clang's expression parser and LLVM's disassembler.</p>
-
-      <p>The LLDB in the base system was upgraded to version 3.6.0
-	as part of the Clang and LLVM upgrade.  In the upstream
-	repository, Justin Hibbits added support for live and core file
-	debugging on PowerPC, and Ed Maste added core file support for
-	FreeBSD/arm64.</p>
-    <p>This project was sponsored by DARP/AFRL, SRI International, and University of Cambridge.</p><h3>Open tasks:</h3><ol><li>
-	<p>Rework the LLDB build to use LLVM and Clang shared libraries.</p>
-      </li><li>
-	<p>Port remote debug stub to FreeBSD.</p>
-      </li><li>
-	<p>Add support for local and core file kernel debugging.</p>
-      </li><li>
-	<p>Improve support on non-amd64 architectures.</p>
-      </li><li>
-	<p>Enable by default in the base system.</p>
-      </li></ol><hr /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/bsdjhb/gdb/tree/freebsd-7.9.0-kgdb" title="https://github.com/bsdjhb/gdb/tree/freebsd-7.9.0-kgdb">Port of kgdb to gdb 7.9</a></td><td>
-	    URL: <a href="https://github.com/bsdjhb/gdb/tree/freebsd-7.9.0-kgdb" title="Port of kgdb to gdb 7.9">https://github.com/bsdjhb/gdb/tree/freebsd-7.9.0-kgdb</a></td></tr></table><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Several improvements to GDB have been merged upstream to GDB's
-	master branch over the past few months, including fixes for
-	unwinding across signal trampoline frames on x86, removing the
-	procfs dependency from the gcore command, and support for XSAVE
-	extensions (such as AVX registers) on x86.  These fixes are
-	already available in the existing devel/gdb port as patches
-	relative to 7.8.</p>
-
-      <p>In addition, progress has been made on porting kgdb to a newer
-	gdb.  Currently, only support for the amd64 backend has been
-	ported, but it is functional both for remote debugging and
-	against crash dumps.  The current port generally has feature
-	parity with the kgdb in the base system.  The plan for kgdb is
-	to fix it to always include all platform targets (so that it
-	always supports cross debugging for remote targets out of the
-	box).  At some point it may also include cross debugging support
-	for crash dumps as well (this would require changes to libkvm).
-      </p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Tidy the amd64 port of kgdb and finish the i386 port.  This
-	  includes fixing these platform-specific targets to work with
-	  cross-debugging for remote targets.</p>
-      </li><li>
-	<p>Add a KGDB option to the devel/gdb port to include kgdb
-	  support.</p>
-      </li><li>
-	<p>Port the rest of the platform-specific targets for kgdb.</p>
-      </li><li>
-	<p>Write a new 1:1-only thread target for FreeBSD that can be
-	  sent upstream.</p>
-      </li><li>
-	<p>Add support for debugging powerpc vector registers.</p>
-      </li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Ada-Ports" href="#FreeBSD-Ada-Ports" id="FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://home.gna.org/ghdl/" title="http://home.gna.org/ghdl/"></a></td><td>
-	    URL: <a href="http://home.gna.org/ghdl/" title="">http://home.gna.org/ghdl/</a></td></tr><tr><td><a href="http://sourceforge.net/projects/ghdl-updates/" title="http://sourceforge.net/projects/ghdl-updates/"></a></td><td>
-	    URL: <a href="http://sourceforge.net/projects/ghdl-updates/" title="">http://sourceforge.net/projects/ghdl-updates/</a></td></tr></table><p>
-	Contact:
-	  John
-	  Marino
-	 &lt;<a href="mailto:marino@FreeBSD.org">marino@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are 51 Ada-related ports currently, but two of them
-	are being retired: the GCC 4.7-based <tt>lang/gcc47-aux</tt> and
-	the BSD-&gt;android cross-compiler for ARMv5
-	(<tt>lang/gnatdroid-armv5</tt>).  The former has no advantage
-	over the newer GCC 4.9-based <tt>lang/gcc-aux</tt>, and the
-	latter has not built for over a year.  Android enthusiasts can
-	still use the the ARMv7 cross-compiler
-	(<tt>lang/gnatdroid-armv7</tt>).</p>
-
-      <p>A new port is <tt>lang/gcc5-aux</tt>, which includes GNAT
-	from the upcoming release of gcc5.  This compiler already builds
-	all Ada ports except gtkada3 (which blocks
-	<tt>devel/gps</tt>, the GNAT Programming Studio), and
-	<tt>gtkada3</tt> should be fixed soon.  When GCC5 is released,
-	the Ada framework will switch to using <tt>gcc5-aux</tt> as the
-	default compiler.  For those that cannot wait, it is possible to
-	use it now by putting <tt>ADA_DEFAULT=5</tt> in /etc/make.conf,
-	but this requires rebuilding all Ada ports from source.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>It is a near-term objective to bring the Ada-based GDHL
-	  (VHDL simulator) to ports.  The upcoming 0.32 release will be
-	  based on GCC 4.9 and the port will be based on this release.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-Python-Ports" href="#FreeBSD-Python-Ports" id="FreeBSD-Python-Ports">FreeBSD Python Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Python" title="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Python" title="The FreeBSD Python Team Page">https://wiki.FreeBSD.org/Python</a></td></tr><tr><td><a href="irc://freebsd-python@irc.freenode.net" title="irc://freebsd-python@irc.freenode.net">IRC channel</a></td><td>
-	    URL: <a href="irc://freebsd-python@irc.freenode.net" title="IRC channel">irc://freebsd-python@irc.freenode.net</a></td></tr></table><p>
-	Contact: FreeBSD Python Team &lt;<a href="mailto:python@FreeBSD.org">python@FreeBSD.org</a>&gt;
-	</p>
-
-      <p>The FreeBSD Python team continued to improve the overall
-	experience with Python-based software on FreeBSD.  A lot of
-	previously deprecated code and option knobs were removed to improve
-	the maintainability of the Python Ports infrastructure.</p>
-
-      <p>The CPython interpreters were updated to version 2.7.9 and 3.4.3
-	and Twisted was updated to version 15.0.0.</p>
-   <h3>Open tasks:</h3><ol><li>
-	<p>Retire the Python 3-specific port duplicates.</p>
-      </li><li>
-	<p>More tasks can be found on the team's wiki page (see
-	  the links).</p>
-      </li><li>
-	<p>To get involved, interested people can say hello on IRC
-	  in #freebsd-python on freenode and let us know their areas
-	  of interest!</p>
-      </li></ol><hr /><h2><a name="GNOME-on-FreeBSD" href="#GNOME-on-FreeBSD" id="GNOME-on-FreeBSD">GNOME on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/gnome" title="http://www.freebsd.org/gnome"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/gnome" title="">http://www.freebsd.org/gnome</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-gnome" title="https://github.com/freebsd/freebsd-ports-gnome">GNOME development repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-gnome" title="GNOME development repo">https://github.com/freebsd/freebsd-ports-gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD"></a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:freebsd-gnome@freebsd.org">freebsd-gnome@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD GNOME Team maintains the GNOME, MATE, and
-	CINNAMON  desktop environments and graphical user interfaces for
-	FreeBSD.  GNOME 3 is part of the GNU Project.  MATE is a fork of
-	the GNOME 2 desktop.  CINNAMON is a desktop environment using
-	GNOME 3 technologies but with a GNOME 2 look and feel.</p>
-
-      <p>At the end of this quarter we updated GNOME and CINNAMON
-	to the latest versions on their branches, 3.14 and 2.4,
-	respectively.</p>
-
-      <p>GNOME 3.16 was released February 25th; we ported it to
-	FreeBSD.  There are still some showstopper problems that appeared.
-	During testing of the current versions of the 3.16 ports a bug
-	in pkg was uncovered in the multiple repository support, and
-	swiftly fixed in pkg 1.4.99.15.</p>
-
-      <p>For the GNOME 3.18 cycle we are going to work closely with
-	the x11 team on porting libinput and testing Wayland.  When that
-	is done we need to see if we want to enable Wayland for our
-	stable releases and we probably need XWayland from
-	<tt>xorg-server</tt> 1.16+ to support X applications.  The
-	estimate is that Wayland arriving in ports will have to wait
-	until 8.4-Release is EOL.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The GNOME website is stale.  Work is underway, although
-	  slowly, on the development section.  We could use some
-	  help here.</p>
-      </li><li>
-	<p>MATE 1.10 porting is under way; the latest 1.9 releases
-	  are available in the mate-1.10 branch.</p>
-      </li></ol><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/"></a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://freebsd.kde.org/area51.php" title="https://freebsd.kde.org/area51.php"></a></td><td>
-	    URL: <a href="https://freebsd.kde.org/area51.php" title="">https://freebsd.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.freebsd.org/KDE" title="https://wiki.freebsd.org/KDE"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/KDE" title="">https://wiki.freebsd.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="https://mail.kde.org/mailman/listinfo/kde-freebsd"></a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="">https://mail.kde.org/mailman/listinfo/kde-freebsd</a></td></tr><tr><td><a href="https://github.com/tcberner/kde5" title="https://github.com/tcberner/kde5"></a></td><td>
-	    URL: <a href="https://github.com/tcberner/kde5" title="">https://github.com/tcberner/kde5</a></td></tr></table><p>
-	Contact:
-	  KDE on FreeBSD team
-	 &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging and making
-	sure that the experience of KDE and Qt on FreeBSD is as good as
-	possible.</p>
-
-      <p>First of all, we would like to welcome Tobias Berner to
-	the ranks of the area51 (the KDE ports staging area) committers.
-	He has been regularly mentioned
-	in our recent status reports, and has finally received committer
-	privileges to our experimental repository.  Becoming an area51
-	committer is usually the first step towards becoming a kde@
-	ports committer.  We hope that Tobias can fix and update our ports
-	more easily, and start committing his KDE Frameworks 5 ports to
-	area51.</p>
-
-      <p>Additionally, this quarter Qt 5.4.1 was committed to
-	the ports tree.  This marks the first time ever since Qt 5 was
-	released that we have the latest upstream stable release in our
-	ports tree!  This was made possible by all the work we had to put
-	into cleaning up the Qt 5 ports infrastructure for the 5.3 update,
-	mentioned in our previous status report.</p>
-
-      <p>Last but not least, Alonso Schaich finally landed an
-	update to our KDE4 ports that had been in our experimental
-	repository for a while, bringing them to the latest 4.14
-	release, 4.14.3.</p>
-
-      <p>Overall, we have updated the following ports in this
-	quarter:</p>
-
-      <ul>
-	<li>Calligra 2.9.1 (committed to area51)</li>
-	<li>CMake 3.1.0, 3.1.1, 3.1.3 (committed to ports)</li>
-	<li>DigiKam 4.2.0 (committed to ports), 4.8.0 (committed to
-	  area51)</li>
-	<li>PyQt 4.11.3 + QScintilla 2.8.4 + sip 4.16.5 (committed to
-	  ports), sip 4.16.7 (committed to area51)</li>
-	<li>Qt 5.4.1 (committed to ports)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Put more effort into Qt5-related ports: KDE Frameworks
-	  5 (currently worked on by Tobias Berner) and PyQt 5.</p>
-      </li></ol><hr /><h2><a name="The-Graphics-stack-on-FreeBSD" href="#The-Graphics-stack-on-FreeBSD" id="The-Graphics-stack-on-FreeBSD">The Graphics stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/graphics/" title="http://blogs.freebsdish.org/graphics/">Graphics stack team blog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/graphics/" title="Graphics stack team blog">http://blogs.freebsdish.org/graphics/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-graphics" title="https://github.com/freebsd/freebsd-ports-graphics">Ports development tree on GitHub</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-graphics" title="Ports development tree on GitHub">https://github.com/freebsd/freebsd-ports-graphics</a></td></tr></table><p>
-	Contact: FreeBSD Graphics team &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the official Ports tree, the Mesa ports
-	(<tt>libglapi</tt>, <tt>libGL</tt>, <tt>libEGL</tt>,
-	<tt>libglesv2</tt>, <tt>gbm</tt>, and <tt>dri</tt>) are kept close
-	to the latest Mesa 10.4.x release.</p>
-
-      <p>In the development tree (see the GitHub link), the update
-	to Mesa 10.5 came, along with several improvements and cleanup to
-	the ports themselves.  Now all ports share the same configure
-	flags and build dependencies.  As Mesa is built from scratch for
-	each port, this ensures that all libraries and drivers are
-	consistent with each other.  This fixes at least two
-	problems:</p>
-
-      <ul>
-	<li>A long standing bug: the <tt>drm</tt> EGL platform is now
-	  functional, meaning we will be able to enable Glamor (the 2D
-	  acceleration engine based on OpenGL) in the X.Org server.  This is
-	  required to provide 2D acceleration for Radeon HD 7000 and later
-	  GPUs, for instance.</li>
-	<li>Clover, the Mesa OpenCL implementation, now works; see the next
-	  paragraph.</li>
-      </ul>
-
-      <p>The downside of this unification is that all ports will depend on
-	LLVM.  This work is happening in the <tt>mesa-10.5</tt> branch.</p>
-
-      <p>Progress has been made on OpenCL, thanks to help from
-	Johannes Dieterich.  Clover (Mesa's implementation) and Beignet
-	(Intel's implementation) were added as ports to the development
-	tree.  They were tested successfully on Radeon and Intel GPUs, but
-	see the wiki for an up-to-date status.  Initially developed in
-	the <tt>opencl</tt> branch, everything has now been merged into the
-	<tt>mesa-10.5</tt> branch.  This cannot go into the official
-	Ports tree yet because it requires the unification explained
-	above.</p>
-
-      <p>A new port, <tt>drm-kmod</tt>, was added to the official
-	Ports tree.  It provides updated <tt>drm2</tt>, <tt>i915kms</tt>
-	and <tt>radeonkms</tt> kernel modules for FreeBSD 9.3-RELEASE
-	and 9.3-STABLE.  The only difference from the vanilla modules is
-	the addition of hardware context support to the i915 driver.
-	The <tt>xf86-video-radeon</tt> and <tt>xf86-video-intel</tt>
-	drivers were patched to use the <tt>drm-kmod</tt> port on these
-	versions of FreeBSD.  This will allow us to remove the duality
-	of the Mesa ports (<tt>libGL</tt>/<tt>libEGL</tt>/<tt>dri</tt>)
-	and only support one version (as is already the case in the
-	<tt>mesa-10.5</tt> branch where Mesa 9.1.7 is gone).  There is
-	no ETA yet for when this last part will happen.</p>
-
-      <p>In the development Ports tree, the <tt>xserver-next</tt>
-	branch was updated from xorg-server 1.16 to be tracking 1.17.
-	Again, this depends on the previous step: the removal of Mesa
-	9.1.7.</p>
-
-      <p>Work is finishing up on an update of miscellaneous X.Org
-	components.  Apart from updates to several X.Org ports, this
-	update also removes the use of <tt>.la</tt> files from the X.Org
-	libraries that still have them.  Also, the
-	<tt>xf86-video-intel</tt> driver will receive patches to allow
-	it to compile against a newer xorg-server than 1.14.  Most of
-	the X.Org component updates were submitted by Matthew Rezny.</p>
-
-      <p>The location where fonts get installed was overhauled and
-	the way to handle fonts from the plist has been simplified.  Now all
-	fonts are installed in <tt>/usr/local/share/fonts</tt> as
-	required by the XDG rules.  Furthermore, making a port for fonts
-	should be easier: more aspects, such as calling fc-cache(1), are
-	handled by the Ports framework.  Therefore, the font ports'
-	consistency was greatly improved.</p>
-
-      <p>In the kernel, the DRM device-independent code was
-	updated to match Linux 3.8.  A merge to 10-STABLE is pending.
-	The i915kms kernel driver received an update, too, which is
-	already merged to 10-STABLE.</p>
-
-      <p>Having both updates in place enables work on a
-	second update of the i915 driver: this time it will be
-	synchronized with Linux 3.8, like the rest of the DRM subsystem,
-	and include Haswell support.  This work was started recently.
-	Our hope is that it will be ready in time for
-	FreeBSD 10.2-RELEASE.</p>
-
-      <p>During Q2, we are going to work with the GNOME team on
-	porting libinput and testing Wayland.  Currently we know that
-	GTK+3 and GNOME 3 have full support for Wayland.  We also need
-	to test Xwayland from xorg-server 1.16+ to support X
-	applications on Wayland desktops.  If you know of more software
-	that uses Wayland, we would like to hear about them.  At this point
-	there are no plans to port the Weston reference implementation
-	of a Wayland compositor.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>See the "Graphics" wiki page for up-to-date
-	  information.</p>
-      </li></ol><hr /><h2><a name="Wine/FreeBSD" href="#Wine/FreeBSD" id="Wine/FreeBSD">Wine/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Wine" title="http://wiki.FreeBSD.org/Wine">Wine wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Wine" title="Wine wiki">http://wiki.FreeBSD.org/Wine</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/i386-Wine" title="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/i386-Wine" title="Wine on amd64 wiki">http://wiki.FreeBSD.org/i386-Wine</a></td></tr><tr><td><a href="http://www.winehq.org" title="http://www.winehq.org">Wine homepage</a></td><td>
-	    URL: <a href="http://www.winehq.org" title="Wine homepage">http://www.winehq.org</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	</p>
-      <p>This quarter has seen five updates to the
-	<tt>wine-devel</tt> port that closely tracks upstream
-	development, as well as updates to helper ports
-	(<tt>wine-gecko-devel</tt> and <tt>wine-mono-devel</tt>):</p>
-
-      <ul>
-	<li>Stable releases: 1.6.2 (1 port revision)</li>
-	<li>Development releases: 1.7.34 through 1.7.39</li>
-      </ul>
-
-      <p>A major development has been the introduction of Wine64
-	(i.e.,  the ability to run 64-bit Windows applications).  This
-	is currently available through the wine-devel port.  At this
-	stage it is currently mutually exclusive with the
-	i386-wine-devel port, however, we have plans to integrate these
-	ports to offer a full Wine experience on amd64.  The
-	i386-wine-devel port has packages built for amd64 for FreeBSD
-	8.4, 9.1+, 10.1+ and CURRENT.</p>
-
-      <p>Accomplishments include:</p>
-
-      <ul>
-	<li>Upstreaming 8 patches to fix Wine on FreeBSD &#8212; many
-	  thanks to Gerald and David.</li>
-	<li>Optional support for V4L has been added to the stable
-	  <tt>emulators/wine</tt> port.</li>
-	<li>Optionally building wine with the X composite extension
-	  (if one selects the X11 option).</li>
-	<li>Support for alternative toolchains that require
-	  <tt>LD</tt> to be honoured.</li>
-	<li>Fixing and tidying up the pkg-plist.</li>
-	<li>Wine64 support</li>
-	<li>Updating the patch-nvidia.sh script to support
-	  arbitrary suffixes.</li>
-	<li>Removing support for the old pkg_ tools from
-	  patch-nvidia.sh.</li>
-	<li>Developing a patch to fix usage of getdirentries(2).
-	  This fixes Steam, EVE Online and other applications.</li>
-      </ul>
-
-      <p>We would like to thank all volunteers who contributed
-	feedback and patches.</p>
-
-      <p>Future development on Wine will focus on:</p>
-
-      <ul>
-	<li>Rename <tt>wine-compholio</tt> to
-	  <tt>wine-staging</tt> (to match upstream development).</li>
-	<li>Add the getdirentries(2) patch to the
-	  <tt>wine-devel</tt> port.</li>
-	<li>Redevelop and upstream the getdirentries(2) patch.</li>
-	<li>Redevelop and upstream the kernel32 Makefile patch.</li>
-	<li>Add support to the <tt>i386-wine</tt> port for pkg 1.5
-	  (conflicts with libraries currently prevent such support).</li>
-	<li>Add support for WoW64:
-	  <ul>
-	    <li>Reduce the <tt>i386-wine</tt> port to just the
-	      components required for WoW64.</li>
-	    <li>Rename the i386-wine port to wow64.</li>
-	    <li>Make the wine ports depend on the wow64 ports when
-	      built on amd64.</li>
-	    <li>Investigate and verify the interactions between Wine64
-	      and WoW64.</li>
-	    <li>Investigate possible update approaches for the wow64
-	      ports (that have to be pre-compiled) and how updating
-	      with the wine ports will work.</li>
-	  </ul>
-	</li>
-      </ul>
-
-      <p>Maintaining and improving Wine is a major undertaking
-	that directly impacts end-users on FreeBSD (including many
-	gamers).  If you are interested in helping, please contact us.
-	We will happily accept patches, suggest areas of focus or have
-	a chat.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>FreeBSD/amd64 integration (see the <a href="http://wiki.FreeBSD.org/i386-Wine" shape="rect">i386-Wine
-	    wiki</a>).</p>
-      </li><li>
-	<p>Porting WoW64.</p>
-      </li></ol><hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce"></a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xfce" title="">https://wiki.freebsd.org/Xfce</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms, such as FreeBSD.  It aims to be fast and
-	lightweight, while still being visually appealing and easy to
-	use.</p>
-
-      <p>This quarter was an exciting time for the Xfce Team.  We
-	imported version 4.12 of the Xfce desktop environment into
-	the ports tree, after more than two years of development.</p>
-
-      <p>Overall, we have updated the following ports:</p>
-
-      <ul>
-	<li>Xfce core (4.12)</li>
-	<li><tt>audio/xfce4-mpc-plugin</tt> (0.4.5)</li>
-	<li><tt>deskutils/xfce4-tumbler</tt> (0.1.31</li>
-	<li><tt>deskutils/xfce4-xkb-plugin</tt> (0.7.1)</li>
-	<li><tt>editors/mousepad</tt> (0.4.0)</li>
-	<li><tt>graphics/ristretto</tt> (0.8.0)</li>
-	<li><tt>multimedia/xfce4-parole</tt> (0.8.0)</li>
-	<li><tt>sysutils/garcon</tt> (0.4.0)</li>
-	<li><tt>sysutils/xfce4-diskperf-plugin</tt> (2.5.5)</li>
-	<li><tt>sysutils/xfce4-fsguard-plugin</tt> (1.0.2)</li>
-	<li><tt>sysutils/xfce4-power-manager</tt> (1.4.4)</li>
-	<li><tt>sysutils/xfce4-wavelan-plugin</tt> (0.5.12)</li>
-	<li><tt>textproc/xfce4-dict-plugin</tt> (0.7.1)</li>
-	<li><tt>www/xfce4-smartbookmark-plugin</tt> (0.4.6)</li>
-	<li><tt>x11/libexo</tt> (0.10.4)</li>
-	<li><tt>x11-clocks/xfce4-timer-out-plugin</tt> (1.0.2)</li>
-	<li><tt>x11-fm/thunar</tt> (1.6.6)</li>
-	<li><tt>x11-themes/gtk-xfce-engine</tt> (3.2.0)</li>
-      </ul>
-
-      <p>At the same time we switched to the USES framework, and a new
-	plugin has been added, called
-	<tt>audio/xfce4-pulseaudio-plugin</tt>.</p>
-
-      <p>We also follow the unstable releases (available in our
-	experimental repository) of:</p>
-
-      <ul>
-	<li><tt>x11/xfce4-dashboard</tt> (0.3.91)</li>
-	<li><tt>x11/xfce4-notes-plugin</tt> (1.8.0 beta)</li>
-      </ul>
-
-      <p>The following documentation patches are ready:</p>
-      <ul>
-	<li><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197878" shape="rect">PR197878</a>,
-	  Update Xfce section in Porter's Handbook</li>
-	<li><a href="https://reviews.freebsd.org/D1305" shape="rect">D1305</a>, FAQ</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Work on support for Compact Disc Digital Audio (CD-DA) in
-	  <tt>multimedia/xfce4-parole</tt>.</p>
-      </li><li>
-	<p>Add a new property (through xfconf-query) to
-	  allow users to change the greyscale value of quicklaunch
-	  icons in <tt>x11/xfce4-dashboard</tt> (this feature is only available
-	  in the unstable release).</p>
-      </li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="More-Michael-Lucas-FreeBSD-books" href="#More-Michael-Lucas-FreeBSD-books" id="More-Michael-Lucas-FreeBSD-books">More Michael Lucas FreeBSD books</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://blather.michaelwlucas.com/archives/2352" title="http://blather.michaelwlucas.com/archives/2352"></a></td><td>
-	    URL: <a href="http://blather.michaelwlucas.com/archives/2352" title="">http://blather.michaelwlucas.com/archives/2352</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	</p>
-      <p>The FreeBSD storage books are proceeding slower than expected.
-	This is a complex project.</p>
-
-      <p>It appears that ZFS will be a two-book topic.  The
-	first book will cover basic ZFS, while the second will cover
-	advanced cases like live and cold replication, sharing,
-	performance, and using ZFS on top of less common GEOM
-	providers.  More details can be found in the links section.</p>
-
-      <p>Allan Jude (allanjude@) is co-authoring the ZFS
-	books.  Little did he know of the magnitude of the task
-	ahead of him when he signed up....</p>
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">Foundation website</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="Foundation website">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr><tr><td><a href="http://www.bsdnow.tv/episodes/2015_03_11-the_pcbsd_tour_ii" title="http://www.bsdnow.tv/episodes/2015_03_11-the_pcbsd_tour_ii">BSDNow PC-BSD Tour</a></td><td>
-	    URL: <a href="http://www.bsdnow.tv/episodes/2015_03_11-the_pcbsd_tour_ii" title="BSDNow PC-BSD Tour">http://www.bsdnow.tv/episodes/2015_03_11-the_pcbsd_tour_ii</a></td></tr><tr><td><a href="http://www.bsdnow.tv/episodes/2015_02_25-from_the_foundation_2" title="http://www.bsdnow.tv/episodes/2015_02_25-from_the_foundation_2">BSDNow "From the Foundation"</a></td><td>
-	    URL: <a href="http://www.bsdnow.tv/episodes/2015_02_25-from_the_foundation_2" title="BSDNow &quot;From the Foundation&quot;">http://www.bsdnow.tv/episodes/2015_02_25-from_the_foundation_2</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The Foundation turned 15 on March 15th!  We kicked off
-	our anniversary celebration by launching a spring fundraising
-	campaign, to bring in 500 new community investors.  In
-	conjunction with our anniversary, BSDNow interviewed Justin
-	Gibbs about our history and plans for the future as part of
-	the PC-BSD tour.  BSDNow also interviewed Ed Maste about FreeBSD
-	projects and processes in a "From the Foundation" episode.</p>
-
-      <p>We were a Platinum Sponsor of AsiaBSDCon and had five team
-	members attend the conference.  Kirk McKusick taught a two-day
-	FreeBSD kernel tutorial and gave a talk on Journaled Soft
-	Updates, and George Neville-Neil gave a talk on network
-	performance in FreeBSD; George also taught a two day tutorial
-	(A Look Inside FreeBSD with DTrace).  This is from ongoing work
-	with Robert Watson in support of both academic and
-	practitioner educational material for FreeBSD.  Dru gave a talk
-	on Advanced OpenSource Storage with FreeNAS 9.3, and Ed Maste
-	gave a talk on the LLDB Debugger in FreeBSD.</p>
-
-      <p>We became a Platinum Sponsor for BSDCan, and have approved six
-	travel grants to FreeBSD contributors.  We also sponsored
-	Michael Dexter to attend SCALE so he could give a talk on
-	virtualization.</p>
-
-      <p>In addition to the above conferences, we helped promote FreeBSD
-	at the following conferences:</p>
-
-      <ul>
-	<li><a href="https://www.usenix.org/conference/fast15" shape="rect">USENIX
-	    FAST '15</a></li>
-	<li><a href="https://fosdem.org/2015/" shape="rect">FOSDEM</a></li>
-	<li><a href="http://www.socallinuxexpo.org/scale/13x/" shape="rect">SCALE</a></li>
-      </ul>
-
-      <p>We received and published FreeBSD testimonials from Xinuos,
-	Netgate, and Tarsnap.</p>
-
-      <p>We launched the "From the Trenches" series to provide stories
-	from FreeBSD contributors on what they are doing with FreeBSD.
-	Glen Barber wrote an article called ZFS and How to Make a Foot
-	Cannon.  Glen also investigated a deadlock issue when rebooting
-	after upgrades (PR 195458), and he released weekly 11-CURRENT and
-	10-STABLE snapshot builds.</p>
-
-      <p>The FreeBSD Journal now has over 8300 subscribers and has a 98%
-	renewal rate.  We are now publishing a few free <a href="https://www.freebsdfoundation.org/journal/articles" shape="rect">FreeBSD
-	  Journal articles</a>.  We also created landing pages for each
-	Journal issue for easier promotion.</p>
-
-      <p>We started work on the Ottawa Vendor and Developer Summits and
-	another one that has not yet been officially announced on the East
-	Coast in the fall.</p>
-
-      <p>Our development staff and project grant recipients were
-	responsible for a large number of feature improvements and bug
-	fixes over this past quarter.  We have nine individual reports
-	in this quarterly update for Foundation-sponsored projects
-	that demonstrate a number of different ways the Foundation
-	supports the FreeBSD project.</p>
-
-      <p>One project is the subject of a research master's
-	project at Swinburne University in Melbourne: the Multipath
-	TCP (MPTCP) implementation for FreeBSD.  The PCIe hot plug
-	project is an individual project grant.  The FreeBSD/arm64
-	project represents a collaborative development effort, where
-	the Foundation facilitates a broader project with multiple
-	participants.</p>
-
-      <p>There are also a number of projects undertaken directly by
-	Foundation staff.  In this quarterly report we have several
-	reports in this category: Secure Boot, the autofs-based
-	automount daemon, dynamically loadable libthr, Intel DMA
-	remapping, and migration to the ELF Tool Chain project tools.</p>
-
-      <p>Additionally, one of the benefits of having long-term
-	permanent staff is the ability to continue to maintain
-	projects and contribute improvements beyond a fixed timeline.
-	Over the last quarter, Foundation staff contributed
-	improvements to the UEFI boot process, vt(4) system console,
-	in-kernel iSCSI stack, virtual memory subsystem, and many
-	others.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2015-04-2015-06.html b/website/content/en/status/report-2015-04-2015-06.html
deleted file mode 100644
index 9f5fc98249..0000000000
--- a/website/content/en/status/report-2015-04-2015-06.html
+++ /dev/null
@@ -1,2423 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The second quarter of 2015, from April to June, was another
-      period of busy activity for FreeBSD.  This report is the largest we
-      have published so far.</p><p>The cluster and release engineering teams continued to improve
-      the structures that support FreeBSD's build, maintenance, and
-      installation.  Projects ran the gamut from security and speed
-      improvements to virtualization and storage appliances.  New
-      kernel drivers and capabilities were added, while work to make
-      FreeBSD run on various ARM architectures continued at a rapid pace.
-      The Ports Collection grew, even while adding capabilities and
-      fixing problems.  Outside projects like <tt>pkgsrc</tt> have
-      become interested in adding support.  Documentation was a major
-      focus, one that is often complimented by people new to FreeBSD.
-      BSDCan 2015 was a great success, turning many hours of sleep
-      deprivation into an even greater amount of inspiration.</p><p>As always, a great deal of this activity was directly sponsored
-      by the Foundation.  The project's status as a first-class
-      operating system owes a great deal to the Foundation's past and
-      ongoing work.</p><p>The number and detail of these reports really gives only a tiny
-      glimpse of all that is happening.  A huge portion of FreeBSD
-      development takes place all the time, including bug fixes,
-      feature improvements, rewrites, and imports of new code.  This
-      ongoing work is difficult, time-consuming, and, far too often,
-      unrecognized.  We should take a moment to consider and thank
-      not just the contributors listed here, but also the end users,
-      bug submitters, port maintainers, coders, security analysts,
-      infrastructure defenders, tinkerers, scientists, designers,
-      questioners, answerers, rule makers, testers, documenters,
-      sysadmins, dogmatists, iconoclasts, and crazed geniuses who make
-      FreeBSD such an effective and useful operating system.  If you are
-      reading this, you are one of these people, too.  Thank you.</p><p><i>&#8212;Warren Block</i></p><p><hr /></p><p>This status report was compiled by
-      <a href="mailto:bjk@FreeBSD.org" shape="rect">Benjamin Kaduk</a> and
-      <a href="mailto:wblock@FreeBSD.org" shape="rect">Warren Block</a>.  Please
-      submit status reports for the third quarter of 2015 (July to
-      September) by October 7, 2015.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Address-Space-Layout-Randomization-(ASLR)">Address Space Layout Randomization (ASLR)</a></li><li><a href="#bhyve">bhyve</a></li><li><a href="#Linux-Binary-Emulation-Layer-Upgrade">Linux Binary Emulation Layer Upgrade</a></li><li><a href="#Mellanox-iSCSI-Extensions-For-RDMA-(iSER)-Support">Mellanox iSCSI Extensions For RDMA (iSER) Support</a></li><li><a href="#Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></li><li><a href="#OpenBSM">OpenBSM</a></li><li><a href="#OPNsense">OPNsense</a></li><li><a href="#Root-Remount">Root Remount</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#1-Wire-Kernel-Driver-Implementation">1-Wire Kernel Driver Implementation</a></li><li><a href="#Adding-PCIe-Hot-plug-Support">Adding PCIe Hot-plug Support</a></li><li><a href="#CloudABI:-Capability-Based-Runtime-Environment">CloudABI: Capability-Based Runtime Environment</a></li><li><a href="#Rewritten-PCID-Support">Rewritten PCID Support</a></li><li><a href="#Sleep-States-Enhancements-on-x86">Sleep States Enhancements on x86</a></li><li><a href="#Warner's-ARMv6-Hard-Float-Experiment">Warner's ARMv6 Hard Float Experiment</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Cavium-ThunderX-(arm64)">FreeBSD on Cavium ThunderX (arm64)</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Cleanup-on-pw(8)">Cleanup on pw(8)</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Official-Packages">Official Packages</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Documentation-Working-Group-at-BSDCan">Documentation Working Group at BSDCan</a></li><li><a href="#FreeBSD-Mastery:-ZFS-Now-Available">FreeBSD Mastery: ZFS Now Available</a></li><li><a href="#Leap-Seconds-Article">Leap Seconds Article</a></li><li><a href="#New-Documentation-Committers">New Documentation Committers</a></li><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#GSoC-2015:-libc-Security-Extensions">GSoC 2015: libc Security Extensions</a></li><li><a href="#Multiqueue-Testing">Multiqueue Testing</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan-2015">BSDCan 2015</a></li><li><a href="#FreeBSD-Support-in-pkgsrc">FreeBSD Support in pkgsrc</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li><li><a href="#ZFS-Support-for-UEFI-Boot/Loader">ZFS Support for UEFI Boot/Loader</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p>
-	Contact: FreeBSD Cluster Administration Team &lt;<a href="mailto:clusteradm@">clusteradm@</a>&gt;
-	</p>
-      <p>The FreeBSD Cluster Administration Team consists of the people
-	responsible for administering the machines that the project
-	relies on for its distributed work and communications to be
-	synchronised.  In this quarter, the team has been extremely
-	busy with work both visible and invisible from outside of the
-	FreeBSD�infrastructure.</p>
-
-      <ul>
-	<li>Migrated reference machines used by FreeBSD developers to the
-	  new machines purchased by the FreeBSD�Foundation at
-	  New York Internet</li>
-
-	<li>Separated email services (and single-point-of-failure
-	  cases) from the machine that has been handling this task for
-	  over 18 years, to new, single-purpose service
-	  installations</li>
-
-	<li>Reorganized the infrastructure, serving repositories
-	  hosted by <tt>svn.freebsd.org</tt> to GeoDNS-backed mirrors,
-	  all with a single, official SSL certificate</li>
-
-	<li>Increased multi-site redundancy for public and non-public
-	  services throughout, at present, eight world-wide geographic
-	  sites</li>
-      </ul>
-
-      <p>While an enormous amount of this work was volunteer-driven,
-	resources (time and hardware) were generously provided by the
-	FreeBSD�Foundation.</p>
-    <p>This project was sponsored by The FreeBSD Foundation (time and hardware).</p><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/10.2R/schedule.html" title="https://www.freebsd.org/releases/10.2R/schedule.html">FreeBSD�10.2-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/10.2R/schedule.html" title="FreeBSD�10.2-RELEASE schedule">https://www.freebsd.org/releases/10.2R/schedule.html</a></td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-snapshots/" title="https://lists.freebsd.org/pipermail/freebsd-snapshots/">FreeBSD development snapshots announcements list</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-snapshots/" title="FreeBSD development snapshots announcements list">https://lists.freebsd.org/pipermail/freebsd-snapshots/</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD�10.2-RELEASE cycle began in mid-June, with the
-	final release expected to be available in late August, and as
-	this quarterly status update shows, FreeBSD�10.2-RELEASE is
-	going to be a very exciting release.</p>
-
-      <p>The FreeBSD Release Engineering Team has been extremely busy
-	this quarter, with much of the focus targeted at adding
-	support for additional hardware and integration with
-	third-party hosting providers (aka "cloud"
-	hosting).</p>
-
-      <p>Following up on the work done by Andrew Turner to port FreeBSD to
-	the arm64 (aarch64) architecture, the Release Engineering
-	build tools were updated to produce FreeBSD/aarch64 memory stick
-	images and virtual machine images for use with Qemu
-	(<tt>emulators/qemu-devel</tt>).  At present, the Qemu virtual
-	machine images require an external EFI file to boot.  Details
-	on how to boot FreeBSD/aarch64 virtual machine images are
-	available in the linked FreeBSD development snapshot announcement email
-	archives.</p>
-
-      <p>Last quarter, several parts of the build tools were rewritten
-	to allow greater extensibility and granularity, which has
-	simplified the code required for new virtual machine
-	images.</p>
-
-      <p>In collaboration with several developers, the Release
-	Engineering build tools were updated to provide new support
-	for several hosting providers, as well as provide mechanisms
-	to automatically upload (and publish, where possible) FreeBSD
-	virtual machine images.</p>
-
-      <p>This quarter, in addition to the existing support for the
-	Microsoft Azure platform, the build tools also natively
-	support:</p>
-
-      <ul>
-	<li>Amazon EC2 (thanks to Colin Percival)</li>
-	<li>Google Compute Engine (thanks to Steve Wills)</li>
-	<li>Vagrant/Hashicorp Atlas (thanks to Brad Davis)</li>
-      </ul>
-
-      <p>The FreeBSD Release Engineering Team would like to thank these
-	developers for all of the work that went into making this
-	possible, and would like to especially thank Marcel Moolenaar for
-	all of his work on the <tt>mkimg(1)</tt> utility, especially
-	for adding support for the various file formats requested.</p>
-
-      <p>In addition to the enhancements to the virtual machine build
-	tools, a significant amount of work went into refactoring the
-	build code used to produce FreeBSD/arm images.</p>
-
-      <p>With much of the logic resembling how the <tt>Crochet</tt>
-	utility (written by Tim Kientzle) works, and a significant
-	amount of work, input, and advice from Ian Lepore, Warner Losh,
-	Andrew Turner, Luiz Otavio O Souza, and a large number of contributors on
-	the <tt>freebsd-arm@FreeBSD.org</tt> mailing list, the FreeBSD
-	Release Engineering tools now natively support producing
-	FreeBSD/arm images without external build tools.</p>
-
-      <p>At present, the build tools support building FreeBSD/arm
-	images for:</p>
-
-      <ul>
-	<li><tt>BEAGLEBONE</tt></li>
-	<li><tt>CUBOX/HUMMINGBOARD</tt></li>
-	<li><tt>GUMSTIX</tt></li>
-	<li><tt>RPI-B</tt></li>
-	<li><tt>RPI2</tt> (FreeBSD-CURRENT only)</li>
-	<li><tt>PANDABOARD</tt></li>
-	<li><tt>WANDBOARD</tt></li>
-      </ul>
-
-      <p>The FreeBSD Release Engineering Team would like to thank each
-	of these people for their support and input, and would like to
-	especially thank Tim Kientzle for his work on
-	<tt>Crochet</tt>.  Without it, we might not have been able to
-	produce images for the various boards that we are able to
-	now.</p>
-
-      <p>For more information on what else has changed in FreeBSD since
-	10.1-RELEASE, see the
-	<a href="https://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html" shape="rect">FreeBSD�10.1-STABLE release notes</a>
-	(which will become the release notes for 10.2-RELEASE).</p>
-
-      <p>Additionally, Glen Barber would like to thank Jim Thompson for
-	providing a BeagleBone Black board (replacing one that no
-	longer worked), and Benjamin Perrault for providing
-	a PandaBoard ES, both of which are used for locally testing
-	the images produced by the build tools.</p>
-
-      <p>Last, and certainly not least, Glen Barber would also like to
-	thank the FreeBSD�Foundation for their support, and for
-	providing the resources (time and hardware) required to make
-	all of the items mentioned in this status report possible.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team constitutes the project's "Board of
-	Directors", responsible for deciding the project's overall
-	goals and direction as well as managing specific areas of the
-	FreeBSD project landscape.</p>
-
-      <p>In order to help attract fresh developer talent to FreeBSD, Core
-	has a general policy to make available an up-to-the-minute
-	suite of developer tools and services.  Core has long been
-	encouraging FreeBSD committers to make full use of the project's
-	Phabricator instance at
-	<a href="https://reviews.FreeBSD.org/" shape="rect">https://reviews.FreeBSD.org</a>,
-	and now has supported the Phabricator admins in opening access
-	to anyone interested enough to sign up for an account.</p>
-
-      <p>Further developments under consideration include setting up a
-	FreeBSD.org OAuth 2 provider and permitting OAuth-style Single
-	Sign-On access to most FreeBSD web-based services.  Developers
-	and members of the public would additionally be able to use
-	credentials from other providers such as GitHub, Twitter, or
-	Google to authenticate themselves to FreeBSD web services.</p>
-
-      <p>Mark Murray raised a problem he has been having for some time
-	with getting adequate security review of his proposed changes
-	to <tt>random(9)</tt>.  This is an extremely security
-	sensitive area of the kernel where errors can have disastrous
-	consequences.  Core has been able to drum up a number of
-	reviewers and they have made significant progress in
-	simplifying the design, eliminating some difficult portions of
-	code, and reducing any potential attack surface.  Work is
-	still ongoing and Core remains open to the idea of bringing in
-	external reviewers with specialist cryptographic
-	knowledge.</p>
-
-      <p>Dag-Erling Sm�rgrav resigned as Security Officer
-	towards the end of May.  Core was sorry to see him step down,
-	but unanimously pleased to welcome his nominee and former
-	deputy, Xin Li, as his successor.  Xin has since appointed
-	Gleb Smirnoff (who also happens to be a current member of
-	core) as his new deputy.  Between them and Core they have some
-	fairly radical ideas under discussion about how to improve the
-	project's responsiveness to security issues.</p>
-
-      <p>In mid-June, a change to <tt>style(9)</tt> was proposed, and
-	resulted in much lively discussion.  Warner Losh conducted an
-	informal poll with Phabricator and the change was approved and
-	committed within a couple of days.  Unfortunately, complaints
-	were raised about the timing and voting methods and Core was
-	called upon to arbitrate.  The change was backed out
-	voluntarily, a new poll was held with more time to vote, and
-	the change was approved.</p>
-
-      <p>During this period we had two new commit bits awarded, and
-	one taken in for safekeeping.  Welcome aboard to Chris Torek
-	and Mariusz Zaborski, and we were very sorry indeed to see
-	Steve Kargl decide to call it a day.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Address-Space-Layout-Randomization-(ASLR)" href="#Address-Space-Layout-Randomization-(ASLR)" id="Address-Space-Layout-Randomization-(ASLR)">Address Space Layout Randomization (ASLR)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://hardenedbsd.org/" title="https://hardenedbsd.org/">HardenedBSD</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/" title="HardenedBSD">https://hardenedbsd.org/</a></td></tr><tr><td><a href="https://hardenedbsd.org/article/shawn-webb/2015-06-30/introducing-true-stack-randomization" title="https://hardenedbsd.org/article/shawn-webb/2015-06-30/introducing-true-stack-randomization">True Stack Randomization</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/article/shawn-webb/2015-06-30/introducing-true-stack-randomization" title="True Stack Randomization">https://hardenedbsd.org/article/shawn-webb/2015-06-30/introducing-true-stack-randomization</a></td></tr><tr><td><a href="https://hardenedbsd.org/article/shawn-webb/2015-07-06/announcing-aslr-completion" title="https://hardenedbsd.org/article/shawn-webb/2015-07-06/announcing-aslr-completion">Announcing ASLR Completion</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/article/shawn-webb/2015-07-06/announcing-aslr-completion" title="Announcing ASLR Completion">https://hardenedbsd.org/article/shawn-webb/2015-07-06/announcing-aslr-completion</a></td></tr><tr><td><a href="https://hardenedbsd.org/article/shawn-webb/2015-07-11/call-donations" title="https://hardenedbsd.org/article/shawn-webb/2015-07-11/call-donations">Call for Donations</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/article/shawn-webb/2015-07-11/call-donations" title="Call for Donations">https://hardenedbsd.org/article/shawn-webb/2015-07-11/call-donations</a></td></tr><tr><td><a href="https://www.soldierx.com/" title="https://www.soldierx.com/">SoldierX</a></td><td>
-	    URL: <a href="https://www.soldierx.com/" title="SoldierX">https://www.soldierx.com/</a></td></tr></table><p>
-	Contact:
-	  Shawn
-	  Webb
-	 &lt;<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>&gt;
-	<br />
-	Contact:
-	  Oliver
-	  Pinter
-	 &lt;<a href="mailto:oliver.pinter@hardenedbsd.org">oliver.pinter@hardenedbsd.org</a>&gt;
-	<br />
-	Contact: HardenedBSD &lt;<a href="mailto:core@hardenedbsd.org">core@hardenedbsd.org</a>&gt;
-	</p>
-      <p>HardenedBSD is a downstream distribution of FreeBSD aimed at
-	implementing exploit mitigation and security technologies.
-	The HardenedBSD development team has focused on several key
-	features, one being Address Space Layout Randomization (ASLR).
-	ASLR is a computer security technique that aids in mitigating
-	low-level vulnerabilities such as buffer overflows.  ASLR
-	randomizes the memory layout of running applications to
-	prevent an attacker from knowing where a given vulnerability
-	lies in memory.</p>
-
-      <p>This last quarter, the HardenedBSD team has finalized the
-	core implementation of ASLR.  We implemented true stack
-	randomization along with a random stack gap.  This change
-	allows us to apply 42 bits of entropy to the stack, the
-	highest of any operating system.  We bumped the
-	<tt>hardening.pax.aslr.stack_len</tt> <tt>sysctl(8)</tt> to 42
-	by default on amd64.</p>
-
-      <p>We also now randomize the Virtual Dynamic Shared Object
-	(VDSO).  The VDSO is one or more pages of memory shared
-	between the kernel and the userland.  On amd64, it contains
-	the signal trampoline and timing code
-	(<tt>gettimeofday(4)</tt>, for example).</p>
-
-      <p>With these two changes, the ASLR implementation is now
-	complete.  There are still tasks to work on, however.  We need
-	to update our documentation and enhance a few pieces of code.
-	Our ASLR implementation is in use in production by HardenedBSD
-	and is performing robustly.</p>
-
-      <p>Additionally, we are currently running a fundraiser to help
-	us establish a not-for-profit organization and for hardware
-	updates.  We have received a lot of help from the community
-	and we greatly appreciate the help.  We need further help
-	to take the project to the next level.  We look forward to
-	working with the FreeBSD project in providing excellent
-	security.</p>
-    <p>This project was sponsored by SoldierX.</p><h3>Open tasks:</h3><ol><li>
-	<p>Update the <tt>aslr(4)</tt> manpage and the wiki
-	page.</p>
-      </li><li>
-	<p>Improve the Shared Object load order feature with Michael
-	  Zandi's improvements.</p>
-      </li><li>
-	<p>Re-port the ASLR work to vanilla FreeBSD.  Include the
-	  custom work requested by FreeBSD developers.</p>
-      </li><li>
-	<p>Close the existing review on Phabricator.</p>
-      </li><li>
-	<p>Open multiple smaller reviews for pieces of the ASLR
-	  patch that can be split out logically.</p>
-      </li><li>
-	<p>Perform a special backport to HardenedBSD 10-STABLE for
-	  OPNSense to pull in.</p>
-      </li><li>
-	<p><tt>golang</tt> segfaults in HardenedBSD.  Help would be
-	  nice in debugging.</p>
-      </li></ol><hr /><h2><a name="bhyve" href="#bhyve" id="bhyve">bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bhyve.org" title="http://www.bhyve.org">bhyve FAQ and talks</a></td><td>
-	    URL: <a href="http://www.bhyve.org" title="bhyve FAQ and talks">http://www.bhyve.org</a></td></tr></table><p>
-	Contact:
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Neel
-	  Natu
-	 &lt;<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Tycho
-	  Nightingale
-	 &lt;<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>&gt;
-	<br />
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Marcelo
-	  Araujo
-	 &lt;<a href="mailto:araujo@FreeBSD.org">araujo@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>bhyve</tt> is a hypervisor that runs on the FreeBSD/amd64
-	platform.  At present, it runs FreeBSD (8.x or later), Linux
-	i386/x64, OpenBSD i386/amd64, and NetBSD/amd64 guests.
-	Current development is focused on enabling additional guest
-	operating systems and implementing features found in other
-	hypervisors.</p>
-
-      <p><tt>bhyve</tt> BoF at BSDCan 2015</p>
-
-      <p>A <tt>bhyve</tt> BoF was held during lunch hour at BSDCan
-	2015.  It was attended by approximately 60 people.</p>
-
-      <p>Michael Dexter showed Windows Server 2012 running inside
-	bhyve.</p>
-
-      <p>Common themes that came up during the discussion were:
-	<tt>bhyve</tt> configuration, libvirt and OpenStack
-	integration, best practices, <tt>bhyve</tt> with ZFS,
-	additional guest support and live migration.</p>
-
-      <p>Google Summer of Code 2015</p>
-
-      <p>A number of bhyve-related proposals were submitted for GSoC
-	2015 and these four were accepted:</p>
-
-      <ul>
-	<li><a href="https://wiki.freebsd.org/SummerOfCode2015/NE2000EmulationForBhyve" shape="rect">NE2000
-	    device emulation</a></li>
-
-	<li><a href="https://wiki.freebsd.org/SummerOfCode2015/PortingBhyveToArm" shape="rect">Porting
-	    bhyve to ARM</a></li>
-
-	<li><a href="https://wiki.freebsd.org/SummerOfCode2015/ptnetmapOnBhyve" shape="rect">ptnetmap
-	    support in bhyve</a></li>
-
-	<li><a href="https://wiki.freebsd.org/SummerOfCode2015/PXEbhyve" shape="rect">PXE
-	    boot support in bhyveload</a></li>
-      </ul>
-
-      <p>A number of improvements were made to <tt>bhyve</tt> this
-	quarter:</p>
-
-      <ul>
-	<li>GEOM storage backend now works properly with
-	  <tt>bhyve</tt>.</li>
-
-	<li>Device model enhancements and new instruction emulations
-	  to support Windows guests.</li>
-
-	<li>Improve virtio-net performance by disabling queue
-	  notifications when not needed.</li>
-
-	<li>The dtrace FBT provider now works properly with
-	  vmm.ko.</li>
-      </ul>
-
-      <p>Marcelo Araujo and Allan Jude created a rough patch to make
-	<tt>bhyve</tt> parse a config file to replace the existing
-	method of configuration by command line invocation.  The rapid
-	pace of advancement in <tt>bhyve</tt> resulted in requiring a
-	much more complex config file.  A new design for the config
-	file, with support for the plugin architecture that will
-	eventually be introduced into <tt>bhyve</tt>, is now being
-	discussed.</p>
-    <h3>Open tasks:</h3><ol><li>Improve documentation.</li><li><tt>bhyveucl</tt> is a script for starting <tt>bhyve</tt>
-	instances based on a libUCL config file.  More information at
-	<a href="https://github.com/allanjude/bhyveucl" shape="rect">https://github.com/allanjude/bhyveucl</a>.</li><li>Add support for <tt>virtio-scsi</tt>.</li><li>Flexible networking backend: <tt>wanproxy</tt>,
-	<tt>vhost-net</tt></li><li>Support running <tt>bhyve</tt> as non-root.</li><li>Add filters for popular VM file formats (VMDK, VHD,
-	QCOW2).</li><li>Implement an abstraction layer for video (no X11 or SDL in
-	base system).</li><li>Suspend/resume support.</li><li>Live Migration.</li><li>Nested VT-x support (<tt>bhyve</tt> in
-	<tt>bhyve</tt>).</li><li>Support for other architectures (ARM, MIPS, PPC).</li></ol><hr /><h2><a name="Linux-Binary-Emulation-Layer-Upgrade" href="#Linux-Binary-Emulation-Layer-Upgrade" id="Linux-Binary-Emulation-Layer-Upgrade">Linux Binary Emulation Layer Upgrade</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Emulation" title="https://wiki.FreeBSD.org/Emulation">Emulation team on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Emulation" title="Emulation team on FreeBSD wiki">https://wiki.FreeBSD.org/Emulation</a></td></tr></table><p>
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:AllanJude@FreeBSD.org">AllanJude@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Dmitry
-	  Chagin
-	 &lt;<a href="mailto:dchagin@FreeBSD.org">dchagin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Johannes
-	  Meixner
-	 &lt;<a href="mailto:xmj@FreeBSD.org">xmj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Emulation Team &lt;<a href="mailto:emulation@FreeBSD.org">emulation@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD emulation team has done extensive work on polishing
-	FreeBSD's Linux emulation layer.  After more than a year and a
-	half, Dmitry Chagin's changes to the Linux binary emulation
-	layer were merged into FreeBSD 11.0-CURRENT.  Before merging the
-	more than 115 individual changes into <tt>base/head</tt>, Ed
-	Maste and Edward Tomasz Napiera&#322;a were able to help by
-	reviewing and improving the code quality.</p>
-
-      <p>Work has begun on backporting these changes into FreeBSD
-	10-STABLE, with the current 10.2 release cycle in mind.  We
-	hope to have that backport ready before 10.2-PRERELEASE turns
-	into 10.2-RELEASE.</p>
-
-      <p>In that same vein, Allan Jude was able to upload and improve
-	a recent Differential Revision that will eventually lead to
-	our having both 32-bit and 64-bit ports for CentOS 6.  Port
-	review activity started during the BSDCan conference's
-	developer summit, and will be continued extensively during the
-	Cambridge Developer Summit.</p>
-
-      <p>We are currently expecting to have both Fedora 10, Centos 6
-	32-bit- and CentOS 6 64-bit-compatible frameworks available by
-	Q4/2015.</p>
-
-      <p>Call for Help: Contributing</p>
-
-      <p>People can contribute to the Emulation team's efforts by
-	testing the CentOS 64-bit changes on a FreeBSD 11.0-CURRENT
-	system.  Please use Bugzilla to report any bugs or oddities
-	encountered.</p>
-
-      <p>For the ambitious: we are planning to start working on a
-	CentOS 7 framework.  CentOS7 is 64-bit only, uses a newer
-	kernel, and has <tt>systemd</tt>, so this work is highly
-	experimental.  We hope to have a usable port by Q2/2016.</p>
-    <p>This project was sponsored by Perceivon Hosting Inc., ScaleEngine Inc., and The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Test 64-bit Linux emulation on 11.0-CURRENT</p>
-      </li><li>
-	<p>Backport 64-bit Linux emulation to 10-STABLE</p>
-      </li><li>
-	<p>Review 64-bit CentOS 6 ports and merge changes</p>
-      </li><li>
-	<p>Create/heavily update existing 64-bit CentOS 7 ports</p>
-      </li><li>
-	<p>Anyone who would like to get in touch should not hesitate
-	  to contact any of the <tt>emulation@</tt> team members.
-	  Similarly, a mail to <tt>emulation@FreeBSD.org</tt> is
-	  always welcome.</p>
-      </li></ol><hr /><h2><a name="Mellanox-iSCSI-Extensions-For-RDMA-(iSER)-Support" href="#Mellanox-iSCSI-Extensions-For-RDMA-(iSER)-Support" id="Mellanox-iSCSI-Extensions-For-RDMA-(iSER)-Support">Mellanox iSCSI Extensions For RDMA (iSER) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/sagigrimberg/iser-freebsd" title="https://github.com/sagigrimberg/iser-freebsd">iser-freebsd on GitHub</a></td><td>
-	    URL: <a href="https://github.com/sagigrimberg/iser-freebsd" title="iser-freebsd on GitHub">https://github.com/sagigrimberg/iser-freebsd</a></td></tr></table><p>
-	Contact:
-	  Max
-	  Gurtovoy
-	 &lt;<a href="mailto:maxg@mellanox.com">maxg@mellanox.com</a>&gt;
-	<br />
-	Contact:
-	  Sagi
-	  Grimberg
-	 &lt;<a href="mailto:sagig@mellanox.com">sagig@mellanox.com</a>&gt;
-	</p>
-      <p>Building on the new in-kernel iSCSI initiator stack released
-	in FreeBSD 10.0 and the recently added iSCSI offload interface,
-	Mellanox Technologies has begun developing iSCSI extensions
-	for RDMA (iSER) initiator support to enable efficient data
-	movement using the hardware offload capabilities of Mellanox's
-	10, 40, 56 and 100 Gigabit IB/Ethernet adapters.</p>
-
-      <p>Remote Direct Memory Access (RDMA) has been shown to have a
-	great value for storage applications.  RDMA infrastructure
-	provides benefits such as Zero-Copy, CPU offload, Reliable
-	transport, Fabric consolidation, and many more.  The iSER
-	protocol eliminates some of the bottlenecks in the traditional
-	iSCSI/TCP stack, provides low latency and high throughput, and
-	is well suited for latency aware workloads.</p>
-
-      <p>This work includes a new ICL module that implements the iSER
-	initiator.  The iSCSI stack is slightly modified to support
-	some extra features such as asynchronous IO completions,
-	unmapped data buffers, and data-transfer offloads.  The user
-	will be able to choose iSER as the iSCSI transport with
-	<tt>iscsictl</tt>.</p>
-
-      <p>The project is in its beta phase.  Recent additions
-	include:</p>
-
-      <ul>
-	<li>Rebased on top of 11-CURRENT (r284921)</li>
-	<li>Added discovery over iSER support</li>
-	<li>HA and automatic session re-establishment support</li>
-	<li>Split iSER from iSCSI module</li>
-      </ul>
-
-      <p>In addition, the <tt>iser</tt> driver has been and continues
-	to be thoroughly tested.  The test suite includes:</p>
-
-      <ul>
-	<li>traffic</li>
-	<li>FS tests</li>
-	<li>compliance tests</li>
-	<li>traffic failover/failback</li>
-	<li>session recovery</li>
-	<li>dynamic module load/unload</li>
-      </ul>
-
-      <p>The code is ready for inclusion and will be released under
-	the BSD license.</p>
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="Multipath-TCP-for-FreeBSD" href="#Multipath-TCP-for-FreeBSD" id="Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/newtcp/mptcp" title="http://caia.swin.edu.au/newtcp/mptcp">MPTCP Project Website</a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/newtcp/mptcp" title="MPTCP Project Website">http://caia.swin.edu.au/newtcp/mptcp</a></td></tr></table><p>
-	Contact:
-	  Nigel
-	  Williams
-	 &lt;<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>&gt;
-	</p>
-      <p> Multipath TCP (MPTCP) is an extension to TCP that
-	allows for the use of multiple network interfaces on a
-	standard TCP session.  The addition of new addresses and
-	scheduling of data across these occurs transparently from the
-	perspective of the TCP application.</p>
-
-      <p>The goal of this project is to deliver an MPTCP kernel
-	patch that interoperates with the reference MPTCP
-	implementation, along with additional enhancements to aid
-	network research.</p>
-
-      <p>The patch now supports the core mechanisms of the MPTCP
-	protocol (multi-address operation, data-level retransmission,
-	etc).</p>
-
-      <p>Recent additions include improved socket-option
-	handling and the transfer of some logging output to DTRACE.  The
-	patch has been updated to build against r285254 of HEAD.</p>
-
-      <p>A patch (v0.5) is currently being tested and will be
-	made available to the public shortly, with a plan to release
-	further patches on a more frequent basis following that.</p>
-    <p>This project was sponsored by FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Complete documentation and testing for release of the v0.5
-	  patch.</p>
-      </li><li>
-	<p>Release Technical Report describing the implementation
-	  of v0.5.</p>
-      </li></ol><hr /><h2><a name="OpenBSM" href="#OpenBSM" id="OpenBSM">OpenBSM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openbsm.org/" title="http://www.openbsm.org/">OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation</a></td><td>
-	    URL: <a href="http://www.openbsm.org/" title="OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation">http://www.openbsm.org/</a></td></tr><tr><td><a href="https://github.com/openbsm/openbsm" title="https://github.com/openbsm/openbsm">openbsm on GitHub</a></td><td>
-	    URL: <a href="https://github.com/openbsm/openbsm" title="openbsm on GitHub">https://github.com/openbsm/openbsm</a></td></tr></table><p>
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Christian
-	  Brueffer
-	 &lt;<a href="mailto:brueffer@FreeBSD.org">brueffer@FreeBSD.org</a>&gt;
-	<br />
-	Contact: TrustedBSD audit mailing list &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <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 FreeBSD and Mac
-	OS X.  Additionally, the audit trail processing tools are
-	expected to work on Linux.</p>
-
-      <p>After a period of dormancy, the project is slowly picking up
-	steam again.  The OpenBSM source code repository was migrated
-	from FreeBSD's Perforce server to GitHub.  We hope this will make
-	the code more accessible and stimulate outside contributions.
-	In addition to the repository migration, automated build
-	testing using Travis CI has been enabled, and initial steps
-	towards a new test release have been made.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Test the code on GitHub on different releases of Mac OS X
-	  and Linux.  Especially testing on Mac OS X 10.9 (Mavericks)
-	  and newer would be greatly appreciated.</p>
-      </li></ol><hr /><h2><a name="OPNsense" href="#OPNsense" id="OPNsense">OPNsense</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://opnsense.org" title="https://opnsense.org">OPNsense website</a></td><td>
-	    URL: <a href="https://opnsense.org" title="OPNsense website">https://opnsense.org</a></td></tr><tr><td><a href="https://github.com/opnsense" title="https://github.com/opnsense">OPNsense source code</a></td><td>
-	    URL: <a href="https://github.com/opnsense" title="OPNsense source code">https://github.com/opnsense</a></td></tr></table><p>
-	Contact:
-	  Franco
-	  Fichtner
-	 &lt;<a href="mailto:franco@opnsense.org">franco@opnsense.org</a>&gt;
-	<br />
-	Contact:
-	  Ad
-	  Schellevis
-	 &lt;<a href="mailto:ad@opnsense.org">ad@opnsense.org</a>&gt;
-	<br />
-	Contact:
-	  Jos
-	  Schellevis
-	 &lt;<a href="mailto:jos@opnsense.org">jos@opnsense.org</a>&gt;
-	</p>
-      <p>OPNsense is a fork of pfSense that aims to follow FreeBSD's
-	code base and ecosystem quickly and closely while retaining
-	the parent's powerful firewall capabilities.  The new 15.7
-	release includes efforts such as firmware upgrades and
-	packaging fully based on <tt>pkg</tt>, weekly security
-	updates, the replacement of ALTQ-based traffic shaping with
-	IPFW/dummynet, and production-ready LibreSSL integration as an
-	alternative to OpenSSL.</p>
-
-      <p>Contributors and testers are welcome as we work on
-	redesigning plugin support, rework the GUI according to modern
-	coding standards (MVC) and privilege separation.</p>
-    <p>This project was sponsored by Deciso.</p><hr /><h2><a name="Root-Remount" href="#Root-Remount" id="Root-Remount">Root Remount</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>One of the long missing features of FreeBSD was the ability to
-	boot 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
-	<tt>pivot_root</tt>.  The reroot project aims to provide
-	similar functionality in a different, slightly more
-	user-friendly way: rerooting.  Simply put, from the user point
-	of view it looks like 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 project is in the late implementation phase.  A working
-	prototype was written, and work is in process to rewrite it in
-	an architecturally nicer way.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Complete debugging</p>
-      </li></ol><hr /><h2><a name="ZFSguru" href="#ZFSguru" id="ZFSguru">ZFSguru</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zfsguru.com" title="http://zfsguru.com">ZFSguru</a></td><td>
-	    URL: <a href="http://zfsguru.com" title="ZFSguru">http://zfsguru.com</a></td></tr></table><p>
-	Contact:
-	  Jason
-	  Edwards
-	 &lt;<a href="mailto:sub.mesa@gmail.com">sub.mesa@gmail.com</a>&gt;
-	</p>
-      <p>ZFSguru is a multifunctional server appliance with a strong
-	emphasis on storage.  ZFSguru began as simple web-interface
-	frontend to ZFS, but has since grown into a FreeBSD derivative
-	with its own infrastructure.  The scope of the project has
-	also grown with the inclusion of add-on packages that add
-	functionality beyond the traditional NAS functionality found
-	in similar product like FreeNAS and NAS4Free.  ZFSguru aims to
-	be a true multifunctional server appliance that is extremely
-	easy to set up and can unite both novice and more experienced
-	users in a single user interface.  The modular nature of the
-	project combats the danger of bloat, whilst still allowing
-	extended functionality to be easily deployed.</p>
-
-      <p>The ZFSguru project is nearing the release of version 0.3, a
-	major milestone for the project.  In this new version, major
-	work has been done on fundamentals.  An overview:</p>
-
-      <ul>
-	<li>New build infrastructure allows for frequent releases of
-	  system images and services in a semi-automated way.</li>
-
-	<li>New GuruDB database allows for a growing number of system
-	  images and servers, and provides good caching to accelerate
-	  pages.</li>
-
-	<li>Redesigned installation procedure, and addition of new
-	  distributions Root-on-RAM and Root-on-Media aside from the
-	  already supported Root-on-ZFS.</li>
-
-	<li>Both LiveCD and USB images will be provided.  The USB
-	  image also has UEFI boot support working alongside the
-	  regular MBR boot support so both are available.</li>
-
-	<li>Many overhauled libraries and additions to the web
-	  interface.</li>
-
-	<li>Many improvements to services, such as the new Gnome 3
-	  graphical environment.</li>
-      </ul>
-
-      <p>ZFSguru version 0.3 will be released on the first of
-	August.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="1-Wire-Kernel-Driver-Implementation" href="#1-Wire-Kernel-Driver-Implementation" id="1-Wire-Kernel-Driver-Implementation">1-Wire Kernel Driver Implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D2956" title="https://reviews.freebsd.org/D2956">1-Wire Stuff: Basics and Temperature</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D2956" title="1-Wire Stuff: Basics and Temperature">https://reviews.freebsd.org/D2956</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>This is a kernel driver implemetation of the Dallas
-	Semiconductor 1-Wire bus in a generic fashion.  While
-	temperature sensors are the only devices initially supported,
-	other devices should be easy to add.  Multiple devices on one
-	bus are supported.  Both normal and overdrive modes are
-	supported.</p>
-
-      <p>Multiple temperature sensors have been well tested, but
-	there is a high bit error rate.  There are indications that
-	this is due to bad bit-read times.  The code is written with
-	enough resilience to cope with the problem by retrying, and
-	the error rate is low enough that a couple of retries paper
-	over many marginal issues.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Implement the overdrive device.  Add overdrive capability
-	  to <tt>owc</tt> and provide an <tt>own</tt> method to allow
-	  the presentation drivers to know when it is safe to use the
-	  overdrive ROM commands.</p>
-      </li><li>
-	<p>Implement the Identification device.  This device just has
-	a class of 1 and no registers.</p>
-      </li><li>
-	<p>Implement non-FDT <tt>gpiobus</tt> attachment.</p>
-      </li><li>
-	<p>Test overdrive timings.</p>
-      </li><li>
-	<p>Implement other attachments for things like serial port or
-	  specialized 1-Wire controllers.</p>
-      </li><li>
-	<p>Use the system clock to implement more precise delays
-	  to improve the error rate.</p>
-      </li><li>
-	<p>Use interrupt mode for GPIO pins to time the transitions
-	  of the line to determine the bit values without busy
-	  waiting.  Use FreeBSD's fine-grained sleeping to do the same
-	  for write-one and write-zero routines.</p>
-      </li><li>
-	<p>Review the code at the URL above.</p>
-      </li><li>
-	<p>Test the code on a device other than a RPi, RPi 2, or
-	  BeagleBone Black.</p>
-      </li><li>
-	<p>Test the code on architectures besides <tt>armv6</tt>.</p>
-      </li><li>
-	<p>Implement streamlined temperature mode where the
-	  <tt>convert_t</tt> command is broadcast and a callback
-	  reads the values for all the devices detected on the
-	  bus.</p>
-      </li><li>
-	<p>Implement parasitic power mode.</p>
-      </li></ol><hr /><h2><a name="Adding-PCIe-Hot-plug-Support" href="#Adding-PCIe-Hot-plug-Support" id="Adding-PCIe-Hot-plug-Support">Adding PCIe Hot-plug Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug" title="http://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug">PCIe Hot-plug P4 Branch</a></td><td>
-	    URL: <a href="http://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug" title="PCIe Hot-plug P4 Branch">http://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/r281874" title="https://svnweb.freebsd.org/changeset/base/r281874">Commit adding bridge save/restore.</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/r281874" title="Commit adding bridge save/restore.">https://svnweb.freebsd.org/changeset/base/r281874</a></td></tr><tr><td><a href="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp" title="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp">Github branch with patches</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp" title="Github branch with patches">https://github.com/FreeBSDFoundation/freebsd/tree/pciehp</a></td></tr></table><p>
-	Contact:
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>PCI Express (PCIe) hot-plug is used on both laptops and
-	servers to allow peripheral devices to be added or removed
-	while the system is running.  Laptops commonly include
-	hot-pluggable PCIe as either an ExpressCard slot or
-	a Thunderbolt interface.  ExpressCard has built in USB support
-	that is already supported by FreeBSD, but ExpressCard PCIe
-	devices like Gigabit Ethernet adapters and eSATA cards are
-	only supported when they are present at boot, and removal may
-	cause FreeBSD to crash.</p>
-
-      <p>The goal of this project is to allow these devices to be
-	inserted and removed while FreeBSD is running.  The work will
-	provide the basic infrastructure to support adding and
-	removing devices, though it is expected that additional work
-	will be needed to update individual drivers to support
-	hot-plug.</p>
-
-      <p>Current testing is focused on getting a simple UART device
-	functional.  Basic hot swap is functional.</p>
-
-      <p>A set of the patches is now available on github.com.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Get suspend/resume functional by save/restoring necessary
-	  registers.  This should be addressed by r281874.</p>
-      </li><li>
-	<p>Make sure that upon suspend, devices are removed so that
-	  any hardware changes made while the machine is suspended
-	  are correctly handled.</p>
-      </li><li>
-	<p>Improve how state transitions are handled, possibly by
-	  using a proper state machine.</p>
-      </li></ol><hr /><h2><a name="CloudABI:-Capability-Based-Runtime-Environment" href="#CloudABI:-Capability-Based-Runtime-Environment" id="CloudABI:-Capability-Based-Runtime-Environment">CloudABI: Capability-Based Runtime Environment</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/NuxiNL/cloudlibc" title="https://github.com/NuxiNL/cloudlibc">CloudABI on GitHub</a></td><td>
-	    URL: <a href="https://github.com/NuxiNL/cloudlibc" title="CloudABI on GitHub">https://github.com/NuxiNL/cloudlibc</a></td></tr><tr><td><a href="https://github.com/NuxiNL/freebsd" title="https://github.com/NuxiNL/freebsd">FreeBSD patchset on GitHub</a></td><td>
-	    URL: <a href="https://github.com/NuxiNL/freebsd" title="FreeBSD patchset on GitHub">https://github.com/NuxiNL/freebsd</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p>CloudABI is a compact UNIX-like runtime environment that is
-	purely based on capability-based security (Capsicum).  All
-	features that are incompatible with this model have been
-	removed.  Advantages of using a pure capability-based
-	environment include improved security, testability, and
-	reusability.  CloudABI should make it possible to run
-	arbitrary third-party executables directly on top of FreeBSD
-	without any impact on system security, making it a good
-	building block for a cluster/cloud computing setup.  See
-	<a href="https://github.com/NuxiNL/cloudlibc" shape="rect">the project on GitHub</a>
-	for a more detailed explanation.</p>
-
-      <p>Last month I added a number of packages for the FreeBSD Ports
-	tree.  We now have a full C/C++ cross compiler that can be
-	installed very easily
-	(<a href="http://www.freshports.org/devel/cloudabi-toolchain" shape="rect">devel/cloudabi-toolchain</a>).
-	I also imported a tool called <tt>cloudabi-run</tt> that can
-	be used to start programs safely, only granting access to
-	files and network sockets listed in the program's
-	configuration file
-	(<a href="http://www.freshports.org/sysutils/cloudabi-utils" shape="rect">sysutils/cloudabi-utils</a>).</p>
-
-      <p>I have also imported some kernelspace modifications into the
-	FreeBSD source tree for executing CloudABI programs.  After all
-	of these changes have been imported, just loading a kernel
-	module will allow executing CloudABI programs.  Right now, the
-	"cloudabi" branch on GitHub is still required.</p>
-    <p>This project was sponsored by Nuxi, the Netherlands.</p><h3>Open tasks:</h3><ol><li>
-	<p>Polish up the kernelspace modifications and send them out
-	  for review.</p>
-      </li><li>
-	<p>Complete the Linux and NetBSD kernel patchsets and send
-	  those out to the respective maintainers.</p>
-      </li></ol><hr /><h2><a name="Rewritten-PCID-Support" href="#Rewritten-PCID-Support" id="Rewritten-PCID-Support">Rewritten PCID Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=282684" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=282684">Commit r282684</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=282684" title="Commit r282684">https://svnweb.freebsd.org/base?view=revision&amp;revision=282684</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>A Process-Context Identifier (PCID) is a
-	performance-enhancing feature of the Translation Lookaside
-	Buffer (TLB) on Intel processors, introduced with the Sandy
-	Bridge micro-architecture.  It allows the TLB to
-	simultaneously cache translation information for several
-	address spaces, and gives an opportunity for the operating
-	system context switch code to avoid flushing the TLB upon
-	process switch.  Each cached translation is tagged with some
-	context identifier, and at context switch time, the operating
-	system instructs the processor which context is becoming
-	active.  The feature slightly reduces context switch time by
-	avoiding TLB flushes, and more importantly, reduces the warm-up
-	period for a thread after context switch.</p>
-
-      <p>FreeBSD already used PCID, but the existing implementation
-	had several shortcomings.  The <tt>amd64</tt> pmap (the
-	machine-dependent portion of the virtual memory subsystem)
-	maintained a bitmap of all CPUs which ever loaded a
-	translation for the given address space, and avoided TLB flush
-	on the context switch.  The bitmap was used to direct
-	Inter-Processor Interrupts to the marked CPU when the
-	operating system needed to perform TLB invalidation.  The most
-	significant deficiency of the old implementation was the increase of
-	TLB invalidation IPIs, since the bitmap could only grow until
-	a full TLB shootdown was performed.  It increased the TLB rate,
-	which negated the positive effects of avoiding TLB flushes on
-	large machines.  Secondarily, the bitmap maintenance in both
-	the pmap and the context code was quite complicated, leading
-	to bugs.  These issues resulted in the PCID feature being
-	disabled by default.</p>
-
-      <p>The new PCID implementation uses an algorithm described in
-	the U. Vahalia book "UNIX Internals: The New Frontiers".  The
-	algorithm is already used, for example, by the MIPS pmap for
-	assigning Address Space Identifiers (ASIDs) to
-	software-managed TLB entries.  The pmap maintains a per-CPU
-	generation count, which is assigned to the next unused PCID
-	when the context is activated on CPU.  TLB invalidation
-	includes resetting the generation count, which causes
-	reallocation of the PCID when a context switch is performed.
-	As result, the new implementation issues exactly the same
-	amount of shootdown IPIs as a pmap which does not utilize
-	PCID.</p>
-
-      <p>Another change included with the PCID rewrite is a move of
-	the address space switching code from assembler to C source,
-	making the algorithm easier to understand and validate.</p>
-
-      <p>Measurements done with <tt>hwpmc(4)</tt> on a Haswell machine
-	indicated that the new implementation reduced the TLB miss
-	rate by up to 10 times, without an increase in TLB shootdown
-	IPIs.</p>
-
-      <p>The rewrite was committed to HEAD at r282684.</p>
-
-      <p>Note: AMD processors do not have the PCID feature for host paging
-	(AMD provides ASIDs for SVM use).  But it is likely that AMD
-	processors do cache TLB translations for different address
-	spaces transparently, and snoop writes to the page tables to
-	invalidate the caches.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Sleep-States-Enhancements-on-x86" href="#Sleep-States-Enhancements-on-x86" id="Sleep-States-Enhancements-on-x86">Sleep States Enhancements on x86</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=282678" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=282678">Commit r282678</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=282678" title="Commit r282678">https://svnweb.freebsd.org/base?view=revision&amp;revision=282678</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ACPI specication defines CPU Cx states, which are idle
-	states.  Methods to enter the state and miscellaneous
-	information like the state-leave latency are returned by the _CST
-	ACPI method.  To save energy and reduce useless heating, the
-	operating system enters a Cx state when the CPU has no work
-	to do.  C0 is the non-idle state, while C1, C2, and C3
-	(defined by ACPI) each represent an idle state with
-	sequentially more energy saving, but also with higher latency
-	of leave and possibly greater secondary costs.  For example,
-	C1 is entered by executing the HLT instruction and has no
-	architecturally visible side effects, while entering C3 drops
-	the CPU cache and usually requires special chipset programming
-	to correctly handle requests from I/O devices to the CPU.  Do
-	not confuse Cx, Px and Sx: Cx states are only meaningful when
-	the system is in the fully operational state S0; Px states are
-	only meaningful when the system is not in the idle state,
-	C0.</p>
-
-      <p>Modern Intel CPUs enter Cx (x &gt;= 1) states with the
-	dedicated instruction MWAIT, which enters a specified
-	low-power state until a specific write is observed by the CPU
-	bus logic.  There is a complimentary MONITOR instruction to
-	set the monitored bus address.  The legacy port I/O method of
-	entering Cx state is emulated by CPU microcode, which
-	intercepts the port I/O and executes MWAIT internally.  Using
-	MWAIT as the method of entering Cx requires following
-	processor-specific procedures, which are communicated to the
-	operating system by the vendor-specific extensions in _CST.
-	The operating system must indicate readiness to support MWAIT
-	when calling _CST. Claimed benefits of using MWAIT are reduced
-	latencies of leaving the idle state, and visibility of more
-	deep states than defined by the common ACPI specification.
-	Still, modern Intel platforms report deep states as C2 to
-	avoid the not needed bus-mastering avoidance.</p>
-
-      <p>The new code asks ACPI for the Intel vendor-specific _CST
-	extensions, parses them, and uses MWAIT Cx entrance methods
-	when available.  The change was committed as r282678 to
-	HEAD.</p>
-
-      <p>For Linux, Intel provides a driver which does not depend on
-	the ACPI tables to use MWAIT for entering Cx states.  For all
-	Intel CPUs after Core2, the driver contains the description of
-	the Cx mode latencies and quirks, eliminating dependency on
-	correct BIOS information, since the BIOS information is often
-	incorrect.  The
-	approach of porting the Linux driver was considered by several
-	people, but all evaluators independently concluded that the
-	project cannot maintain such an approach without direct
-	involvement from Intel.</p>
-
-      <p>During the work, around 500 lines of identical code between
-	the i386 and amd64 versions of idle handling were moved to
-	a common location <tt>x86/x86/cpu_machdep.c</tt>.  Now the
-	i386 and amd64 <tt>machdep.c</tt> files contain only unique
-	machine-dependent routines.  This advance depended on John
-	Baldwin's elimination of the unmaintained Xen PVM i386
-	port.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Warner's-ARMv6-Hard-Float-Experiment" href="#Warner's-ARMv6-Hard-Float-Experiment" id="Warner's-ARMv6-Hard-Float-Experiment">Warner's ARMv6 Hard Float Experiment</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/armv6tohardfloat" title="https://wiki.freebsd.org/armv6tohardfloat">Moving armv6 from Soft Float to Hard Float</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/armv6tohardfloat" title="Moving armv6 from Soft Float to Hard Float">https://wiki.freebsd.org/armv6tohardfloat</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The plan for the transition to hard float on ARMv6 involved
-	having a new <tt>MACHINE_ARCH</tt>.  That seemed expedient,
-	but inelegant to me.  The kernel can easily run both soft and
-	hard floating point binaries, assuming that the proper
-	libraries are available.</p>
-
-      <p>As an experiment, I have been investigating how hard it would
-	be to just start generating hard float binaries starting with
-	FreeBSD 11.0 and what issues this causes.  I am most interested
-	in the source, the effects on ports, and any binary/package
-	upgrade issues from FreeBSD 10.X to 11.</p>
-
-      <p>If successful, this will allow the project to move more
-	quickly away from a soft-floating point default.  Users
-	upgrading from FreeBSD 10 will automatically be upgraded to hard
-	float.  All supported ARMv6 and ARMv7 processors have hardware
-	floating point, so this will not be a problem for the vast
-	majority of users.  In addition, many of the build scripts
-	know about all values of <tt>MACHINE_ARCH</tt>, and not
-	changing the <tt>MACHINE_ARCH</tt> will allow those scripts to
-	continue to function without additional changes.</p>
-
-      <p>I am about three fourths of the way through investigating
-	this possibility and coding up solutions to the problems
-	encountered so far.</p>
-
-      <p>The risks from this experiment are that it will encounter
-	unforseen dependencies.  This could force us to go with the
-	original plan for migration to hard floating point.</p>
-
-      <p>The hope for this experiment is to pave the way for using the
-	superior hard floating point in FreeBSD 11 with minimal impact to
-	our users and their current build scripts and processes.
-	Backwards compatibility will be ensured with the libsoft tasks
-	if users need to run FreeBSD 10.X ARMv6 softfloat binaries on
-	FreeBSD 11.0 with its new hardfloat libraries.  Packages should
-	automatically update once the new hardfloat packages are put
-	into place.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Building seat belts into <tt>ld.so</tt> to not cross-thread
-	  libraries of differing floating point implementations.</p>
-      </li><li>
-	<p>Clang should properly mark hard versus soft floating point
-	  <tt>.o</tt>s.  This is a minor issue, since <tt>ld</tt>
-	  handles things correctly.</p>
-      </li><li>
-	<p><tt>libsoft</tt>, the analog of <tt>lib32</tt>, needs to be
-	  completed.</p>
-      </li><li>
-	<p>Patches to flip the switch from soft to hard for builds for
-	  <tt>armv6</tt>.  Some additional code needed to build soft
-	  float may be needed for the prior task.</p>
-      </li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Cavium-ThunderX-(arm64)" href="#FreeBSD-on-Cavium-ThunderX-(arm64)" id="FreeBSD-on-Cavium-ThunderX-(arm64)">FreeBSD on Cavium ThunderX (arm64)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/arm64" title="http://wiki.freebsd.org/arm64">FreeBSD Wiki: arm64 page</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/arm64" title="FreeBSD Wiki: arm64 page">http://wiki.freebsd.org/arm64</a></td></tr><tr><td><a href="https://youtu.be/lLgc4FJLJ3Y" title="https://youtu.be/lLgc4FJLJ3Y">Video: FreeBSD on the 48-core ThunderX (ARMv8)</a></td><td>
-	    URL: <a href="https://youtu.be/lLgc4FJLJ3Y" title="Video: FreeBSD on the 48-core ThunderX (ARMv8)">https://youtu.be/lLgc4FJLJ3Y</a></td></tr></table><p>
-	Contact:
-	  Dominik
-	  Ermel
-	 &lt;<a href="mailto:der@semihalf.com">der@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Macek
-	 &lt;<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Michal
-	  Stanek
-	 &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	</p>
-      <p>Since the previous report, ThunderX gained SMP support and
-	FreeBSD is now running on 48 real-life ARMv8 CPU cores!  The
-	newly introduced functionality was based on initial
-	foundational work submitted by Andrew Turner and Robin
-	Randhawa, with emulation as the primary target.</p>
-
-      <p>Semihalf's efforts focused on hardware, and include:</p>
-
-      <ul>
-	<li>Multicore support for the newer Generic Interrupt
-	  Controller GICv3</li>
-
-	<li>Numerous bug fixes for:
-	  <ul>
-	    <li><tt>pmap(9)</tt> - memory attributes and TLB
-	    management</li>
-
-	    <li><tt>locore.S</tt> - secondary core initialization</li>
-
-	    <li>IPI (inter-processor interrupts)</li>
-
-	    <li>Per-CPU timers</li>
-
-	    <li>Size of early UMA allocations</li>
-
-	    <li>Cache maintenance</li>
-
-	    <li>Exceptions handling</li>
-
-	    <li>Stack issues</li>
-	  </ul></li>
-
-	<li>ThunderX-specific changes and quirks</li>
-      </ul>
-
-      <p>This support was introduced to the public at the FreeBSD 2015
-	Developer Summit in Ottawa at a demo held by Semihalf and the
-	FreeBSD Foundation.  Cavium's ThunderX server CRB (Customer
-	Reference Board) is now capable of booting SMP FreeBSD from both
-	the hard disk and from an NFS root using a PCIe networking
-	card.  The example setup is now available on the FreeBSD test
-	cluster hosted at Sentex Communications.</p>
-
-      <p>ThunderX support changes are currently being reviewed and
-	integrated into mainline FreeBSD.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, ARM Ltd., Cavium, and Semihalf.</p><h3>Open tasks:</h3><ol><li>
-	<p>Upstream ThunderX support to FreeBSD HEAD</p>
-      </li><li>
-	<p>Support for multi-socket configuration of ThunderX (96 CPUs
-	  connected through coherent fabric)</p>
-      </li><li>
-	<p>Implement VNIC support (ThunderX networking controller)</p>
-      </li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/arm64" title="https://wiki.freebsd.org/arm64">FreeBSD arm64 wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/arm64" title="FreeBSD arm64 wiki">https://wiki.freebsd.org/arm64</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ruslan
-	  Bukin
-	 &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the last status report, support for building FreeBSD for
-	AArch64 (arm64) has been committed to Subversion.  This has
-	initially been targeting qemu, with more hardware support
-	being added after review.</p>
-
-      <p>Support for ACPI, SMP, DTrace, and <tt>hwpmc</tt> has been
-	added.  ACPI is able to enumerate devices and get to the
-	<tt>mountroot</tt> prompt.  Further work is needed to get into
-	userland.  SMP has been tested on qemu with two cores, and
-	work is under way to support SMP on hardware.  The
-	<tt>hwpmc</tt> driver includes support for the Cortex-A53,
-	Cortex-A57, and Cortex-A72 cores from ARM.</p>
-
-      <p>Poudriere has been used with user-mode qemu to test building
-	packages.  Over 14,000 ports were successfully built.  A
-	number of issues have been found and fixed from this first
-	run.  These fixes should unblock about 5,000 additional
-	ports.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, ABT Systems Ltd, and ARM Ltd.</p><h3>Open tasks:</h3><ol><li>
-	<p>Port to more SoCs</p>
-      </li><li>
-	<p>Test Poudriere on native hardware</p>
-      </li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="Cleanup-on-pw(8)" href="#Cleanup-on-pw(8)" id="Cleanup-on-pw(8)">Cleanup on pw(8)</a></h2><p>
-	Contact:
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>pw(8)</tt> is the utility to create, delete, and
-	modify users.  This tool has remained mostly untouched since
-	its creation, but needed updating.</p>
-
-      <p>Lots of cleanup has been done:</p>
-
-      <ul>
-	<li>Deduplication of code</li>
-
-	<li>Reduction of complexity by splitting into smaller
-	  functions</li>
-
-	<li>Reuse of existing code in base:
-	  <ul>
-	    <li><tt>sbuf(9)</tt> for buffered string</li>
-
-	    <li><tt>stringlist(3)</tt> for string arrays</li>
-
-	    <li><tt>gr_utils</tt> (from libutil) instead of homemade
-	      group manipulation</li>
-
-	    <li><tt>strptime(3)</tt> to parse time strings</li>
-	  </ul>
-	</li>
-
-	<li>Added validation on most input options, fixing some
-	  serious bugs due to bad usage of <tt>atoi(3)</tt></li>
-
-	<li>many regression tests added to test for regressions due to
-	  all of these changes</li>
-      </ul>
-
-      <p>A new feature was added:
-	<tt>pw -R <u>rootdir</u> <i>cmd</i></tt> which allows
-	cross manipulation of users.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>More cleanup.</p>
-      </li><li>
-	<p>More regression tests.</p>
-      </li><li>
-	<p>LDAP support?</p>
-      </li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE on FreeBSD website</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE on FreeBSD website">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://freebsd.kde.org/area51.php" title="https://freebsd.kde.org/area51.php">KDE ports staging area</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/area51.php" title="KDE ports staging area">https://freebsd.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.freebsd.org/KDE" title="https://wiki.freebsd.org/KDE">KDE on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/KDE" title="KDE on FreeBSD wiki">https://wiki.freebsd.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="https://mail.kde.org/mailman/listinfo/kde-freebsd">KDE/FreeBSD mailing list</a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="KDE/FreeBSD mailing list">https://mail.kde.org/mailman/listinfo/kde-freebsd</a></td></tr><tr><td><a href="https://github.com/tcberner/kde5" title="https://github.com/tcberner/kde5">Development repository for integrating KDE 5</a></td><td>
-	    URL: <a href="https://github.com/tcberner/kde5" title="Development repository for integrating KDE 5">https://github.com/tcberner/kde5</a></td></tr></table><p>
-	Contact: KDE on FreeBSD team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging and making sure
-	that the experience of KDE and Qt on FreeBSD is as good as
-	possible.</p>
-
-      <p>Brad Davis has been working on CMake, resulting in an update
-	to version 3.2.3 being committed to ports.</p>
-
-      <p>Overall, we have updated the following ports in this
-	quarter:</p>
-
-      <ul>
-	<li>CMake 3.2.3 (committed to ports)</li>
-	<li>Qt 4.8.7 (committed to area51)</li>
-	<li>Qt 5.4.1 (refinements committed to ports)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Put more effort into the Qt5-related ports: KDE Frameworks
-	  5 (currently worked on by Tobias Berner) and PyQt 5.</p>
-      </li></ol><hr /><h2><a name="Official-Packages" href="#Official-Packages" id="Official-Packages">Official Packages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pkg-status.FreeBSD.org" title="http://pkg-status.FreeBSD.org">Package Status</a></td><td>
-	    URL: <a href="http://pkg-status.FreeBSD.org" title="Package Status">http://pkg-status.FreeBSD.org</a></td></tr></table><p>
-	Contact:
-	  Bryan
-	  Drewery
-	 &lt;<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Sean
-	  Bruno
-	 &lt;<a href="mailto:sbruno@FreeBSD.org">sbruno@FreeBSD.org</a>&gt;
-	</p>
-      <p>x86 Packages</p>
-
-      <p>With the help of the FreeBSD Foundation providing more
-	build servers, we have increased the build frequency of
-	packages from weekly to about every other day.  Packages are
-	provided for all currently supported releases and head on
-	<tt>i386</tt> and <tt>amd64</tt> from the ports head branch,
-	and quarterly packages for FreeBSD 10.1 and 9.3 release
-	branches.</p>
-
-      <p>We are using eight different systems for building packages.
-	The build process has been fully automated and is
-	more fault tolerant now.  More details on this will be
-	available in an upcoming FreeBSD Journal article.  About eleven
-	servers are used for daily test builds.  To make it simpler for
-	everyone to find the status and results of these builds,
-	<a href="http://pkg-status.FreeBSD.org" shape="rect">pkg-status.FreeBSD.org</a>
-	has been developed by Bryan Drewery.  Its intent is to show
-	all systems and builds in nearly real-time.  It is currently
-	in a beta stage and will be improved over time.  At the time
-	of this writing, it is temporarily down, but will be restored
-	soon.</p>
-
-      <p>ARM/MIPS Packages</p>
-
-      <p>The FreeBSD Foundation purchased servers for the project to
-	begin building and providing ARM and MIPS packages.  These
-	packages are currently built from x86 systems using QEMU.
-	More details on this can be found in the
-	<a href="http://www.bsdcan.org/2015/schedule/events/532.en.html" shape="rect">BSDCan
-	  2015 Presentation</a>.  The work to do this has been
-	shepherded by Sean Bruno and has had help from many people
-	including but not limited to Juergen Lock, Stacey Son, Ed
-	Maste, Peter Wemm, Alexander Kabaev, Adrian Chadd, Baptiste
-	Daroussin, Bryan Drewery, Dimitry Andric, Andrew Turner,
-	Warner Losh, Ian Lapore, and Brooks Davis.</p>
-
-      <p>We are currently targeting packages for head on
-	<tt>mips</tt>, <tt>mips64</tt> and <tt>armv6</tt>.  Each set
-	takes one to two weeks to build on QEMU.  They will be
-	provided on a best effort basis for now on the default
-	repository of <tt>pkg.FreeBSD.org</tt>.</p>
-    <p>This project was sponsored by FreeBSD Foundation (package building hardware).</p><h3>Open tasks:</h3><ol><li>
-	<p>Portmgr met at BSDCan and decided that the default package
-	  set should be provided based on the Ports Quarterly branch.
-	  This will provide more stable packages by default and allow
-	  users who wish to have the bleeding edge to use the head
-	  packages.  The Quarterly branch is currently updated in full
-	  every three months from head and otherwise receives security
-	  and critical fixes.  Moving towards this plan will also
-	  require a change to how we update the Quarterly branch.
-	  More details will be provided later.</p>
-      </li><li>
-	<p>Performance and stability of QEMU continues to improve.
-	  Native cross-building support in ports needs more work and
-	  testing to be viable.</p>
-      </li><li>
-	<p>The package builds currently run from a <tt>crontab</tt>
-	  every other day.  Some of the builds take two hours
-	  (incremental), while others can take up to 30 hours for a
-	  full build.  An open task here is to implement a better
-	  OS ABI check to see if incremental builds can be done, or if
-	  a full rebuild is needed when an SA/EN comes out.  The plan
-	  for this is detailed at
-	  <a href="https://lists.freebsd.org/pipermail/freebsd-arch/2015-April/017025.html" shape="rect">https://lists.freebsd.org/pipermail/freebsd-arch/2015-April/017025.html</a>.</p>
-
-	<p>Another open task is to implement a master queue
-	  coordinator to start the next builds as soon as all others
-	  are done.  This will also allow improving the pkg-status
-	  site's view of everything.</p>
-      </li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">The Ports Collection</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="The Ports Collection">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to Ports</a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to Ports">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring System</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring System">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/">portmgr Blog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="portmgr Blog">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/">portmgr on Twitter</a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="portmgr on Twitter">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr">portmgr on Facebook</a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="portmgr on Facebook">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383">portmgr on Google+</a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="portmgr on Google+">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of the second quarter, the ports tree holds
-	nearly 25,000 ports and the PR count is about 1,800.  Once
-	again, the tree saw more activity than during the previous
-	quarter, with almost 8,000 commits performed by 153 active
-	committers.  On the other hand, the number of problem reports
-	closed decreased slightly, with a bit less than 1,700 problem
-	reports fixed.</p>
-
-      <p>In the second quarter, several commit bits were taken in for
-	safekeeping, following an inactivity period of more than 18
-	months (clsung, dhn, obrien, tmseck), or on committer's
-	request (sahil).  Two new developers were granted a ports
-	commit bit (Michael Moll - mmoll@, and Bernard Spil -
-	brnrd@).</p>
-
-      <p>On the management side, pgollucci@ started his four-month
-	term as portmgr-lurker in June, and no changes were made to
-	the portmgr team during the second quarter.</p>
-
-      <p>This quarter also saw the release of the second quarterly
-	branch, namely <tt>2015Q2</tt>.  On this branch, 39 committers
-	applied 305 patches, which is more than twice as many updates
-	as during the last quarter.</p>
-
-      <p>On the quality assurance side, 30 exp-runs were performed to
-	validate sensitive updates or cleanups.  Amongst those
-	noticeable changes are the update to pkg 1.5.4, three new
-	<tt>USES</tt> (<tt>waf</tt>, <tt>gnustep</tt>, <tt>jpeg</tt>),
-	the Perl default switch to 5.20, Ruby to 2.1.6, Firefox
-	38.0.6, and Chromium 43.0.2357.130.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>As in the previous quarter, a tremendous amount of work
-	  was done on the tree to update major ports and to close even
-	  more PRs than in 2015 Q1, but as always, any additional help
-	  is greatly appreciated!</p>
-      </li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">Graphics stack roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/graphics/" title="http://blogs.freebsdish.org/graphics/">Graphics stack team blog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/graphics/" title="Graphics stack team blog">http://blogs.freebsdish.org/graphics/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-graphics" title="https://github.com/freebsd/freebsd-ports-graphics">Ports development tree on GitHub</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-graphics" title="Ports development tree on GitHub">https://github.com/freebsd/freebsd-ports-graphics</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Graphics Team
-	 &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>The members of the graphics team were lacking spare
-	time during this quarter, and only few things could be
-	improved.</p>
-
-      <p>Our ports development tree still holds an update to Mesa 10.6
-	along with many cleanups and bug fixes.  (It was 10.5 in the
-	previous quarterly report.)  Initially, we planned to commit
-	it in early July, just after the FreeBSD 8.4-RELEASE end-of-life date, but the EOL
-	was delayed to the 31st of July.  Therefore, we will send a
-	Call For Testers near the end of July, with the update to be
-	committed in early August.  Of course, the update can still be
-	obtained and tested directly from the Ports development tree
-	by using the <tt>mesa-next</tt> branch.</p>
-
-      <p>Several smaller updates to X.Org-related ports were committed
-	to the Ports tree.</p>
-
-      <p>The work on the i915 kernel driver update made no progress
-	during this quarter due to the lack of free time.
-	Fortunately, it can resume in Q3 with the hope to have
-	something ready to test in September 2015.</p>
-
-      <p>The update to the DRM device-independent code was merged to
-	<tt>stable/10</tt>.  This means it will be available in the
-	upcoming FreeBSD�10.2-RELEASE.</p>
-
-      <p>Recently, the website hosting our blog has been down
-	frequently.  It is again the case at the time of this
-	writing.  We exported the data the last time it was up,
-	so we will probably move to another system.  Of course, the
-	URL will change as well.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>See the Graphics wiki page for up-to-date information.</p>
-      </li></ol><hr /><h2><a name="Wine/FreeBSD" href="#Wine/FreeBSD" id="Wine/FreeBSD">Wine/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Wine" title="http://wiki.FreeBSD.org/Wine">Wine wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Wine" title="Wine wiki">http://wiki.FreeBSD.org/Wine</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/i386-Wine" title="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 wiki</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/i386-Wine" title="Wine on amd64 wiki">http://wiki.FreeBSD.org/i386-Wine</a></td></tr><tr><td><a href="http://www.winehq.org" title="http://www.winehq.org">Wine homepage</a></td><td>
-	    URL: <a href="http://www.winehq.org" title="Wine homepage">http://www.winehq.org</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	</p>
-      <p>This quarter has seen seven updates to the
-	<tt>wine-devel</tt> port that closely tracks upstream
-	development as well as updates to its helper ports
-	(<tt>wine-gecko-devel</tt> and <tt>wine-mono-devel</tt>):</p>
-
-      <ul>
-	<li>Stable releases: 1.6.2 (1 port revision)</li>
-
-	<li>Development releases: 1.7.40 through 1.7.46</li>
-      </ul>
-
-      <p>The <tt>i386-wine-devel</tt> port has packages built for
-	amd64 for FreeBSD 8.4, 9.1+, 10.1+ and CURRENT.</p>
-
-      <p>Accomplishments include:</p>
-
-      <ul>
-	<li>Rename <tt>wine-compholio</tt> to
-	  <tt>wine-staging</tt> (to match upstream developments).</li>
-      </ul>
-
-      <p>Future development on Wine will focus on:</p>
-      <ul>
-	<li>Add the <tt>getdirentries(2)</tt> patch to the
-	  <tt>wine-devel</tt> port.</li>
-
-	<li>Redevelop and upstream the <tt>getdirentries(2)</tt>
-	  patch.</li>
-
-	<li>Redevelop and upstream the kernel32 <tt>Makefile</tt>
-	  patch.</li>
-
-	<li>Add support to the <tt>i386-wine</tt> port for
-	  <tt>pkg</tt> 1.5 (library conflicts currently prevent
-	  support).</li>
-
-	<li>Add support for Windows 32-bit on Windows 64-bit (WoW64):
-	  <ul>
-	    <li>Reduce the <tt>i386-wine</tt> port to just the
-	      components required for WoW64.</li>
-
-	    <li>Rename the <tt>i386-wine</tt> port to
-	      <tt>wow64</tt>.</li>
-
-	    <li>Make the wine ports depend on the wow64 ports when
-	      built on amd64.</li>
-
-	    <li>Investigate and verify the interactions between Wine64
-	      and WoW64.</li>
-
-	    <li>Investigate possible update approaches for the
-	      wow64 ports (that have to be pre-compiled) and how
-	      updating with the wine ports will work.</li>
-	  </ul>
-	</li>
-      </ul>
-
-      <p> Maintaining and improving Wine is a major undertaking
-	that directly impacts end-users on FreeBSD (including many
-	gamers).  If you are interested in helping please contact us.
-	We will happily accept patches, suggest areas of focus or have
-	a chat.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Open Tasks and Known Problems (see the
-	  <a href="http://wiki.FreeBSD.org/Wine" shape="rect">Wine wiki</a>)</p>
-      </li><li>
-	<p>FreeBSD/amd64 integration (see the
-	  <a href="http://wiki.FreeBSD.org/i386-Wine" shape="rect">i386-Wine
-	    wiki</a>)</p>
-      </li><li>
-	<p>Porting Windows 32-bit on Windows 64-bit (WoW64)</p>
-      </li></ol><hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce">FreeBSD Xfce Project</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Xfce" title="FreeBSD Xfce Project">https://wiki.freebsd.org/Xfce</a></td></tr><tr><td><a href="https://www.assembla.com/code/xfce4/subversion/nodes" title="https://www.assembla.com/code/xfce4/subversion/nodes">FreeBSD Xfce Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/code/xfce4/subversion/nodes" title="FreeBSD Xfce Repository">https://www.assembla.com/code/xfce4/subversion/nodes</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Xfce Team
-	 &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>Xfce</tt> is a free software desktop environment for Unix
-	and Unix-like platforms, such as FreeBSD.  It aims to be fast and
-	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>
-
-      <ul>
-	<li><tt>audio/xfce4-pulseaudio-plugin</tt> 0.2.3</li>
-	<li><tt>deskutils/orage</tt> 4.12.1</li>
-	<li><tt>deskutils/xfce4-notes-plugin</tt> 1.8.1</li>
-	<li><tt>misc/xfce4-weather-plugin</tt> 0.8.6</li>
-	<li><tt>science/xfce4-equake-plugin</tt> 1.3.7</li>
-	<li><tt>sysutils/xfburn</tt> 0.5.4</li>
-	<li><tt>sysutils/xfce4-power-manager</tt> 1.5.0 (committed to
-	  ports), 1.5.2 (committed to devel repository)</li>
-	<li><tt>x11/libexo</tt> 0.10.6</li>
-	<li><tt>x11/xfce4-dashboard</tt> 0.4.2</li>
-	<li><tt>x11-fm/thunar</tt> 1.6.10</li>
-	<li><tt>x11-wm/xfce4-desktop</tt> 4.12.2</li>
-	<li><tt>x11-wm/xfce4-wm</tt> 4.12.3</li>
-	<li><tt>www/midori</tt> 0.5.10</li>
-      </ul>
-
-      <p>Mathieu Arnold (<tt>mat@</tt>) committed
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197878" shape="rect">PR
-	  197878</a>,
-	updating the Xfce section in the Porter's Handbook.</p>
-
-      <p>We also follow the unstable releases (available in our
-	experimental repository) of:</p>
-
-      <ul>
-	<li><tt>sysutils/garcon</tt> 0.5.0 (supports both GTK2 and
-	  GTK3 toolkits)</li>
-	<li><tt>x11/xfce4-dashboard</tt> 0.5.0</li>
-	<li><tt>x11/xfce4-hotcorner-plugin</tt> 0.0.2 (new
-	  plugin)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Create documentation for the usage of
-	  <tt>sysutils/xfce4-power-manager</tt> (it needs some love,
-	  <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199166" shape="rect">PR
-	    199166</a>).</p>
-
-	<p>Some hidden features were introduced in the 1.5.1 release,
-	  and as we also support ConsoleKit2 (a fork of
-	  <tt>sysutils/consolekit</tt>), help for users is
-	  required.</p>
-      </li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Documentation-Working-Group-at-BSDCan" href="#Documentation-Working-Group-at-BSDCan" id="Documentation-Working-Group-at-BSDCan">Documentation Working Group at BSDCan</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/" title="http://www.bsdcan.org/">BSDCan</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/" title="BSDCan">http://www.bsdcan.org/</a></td></tr><tr><td><a href="http://docutils.sourceforge.net/rst.html" title="http://docutils.sourceforge.net/rst.html">reStructured Text</a></td><td>
-	    URL: <a href="http://docutils.sourceforge.net/rst.html" title="reStructured Text">http://docutils.sourceforge.net/rst.html</a></td></tr><tr><td><a href="http://daringfireball.net/projects/markdown/" title="http://daringfireball.net/projects/markdown/">Markdown</a></td><td>
-	    URL: <a href="http://daringfireball.net/projects/markdown/" title="Markdown">http://daringfireball.net/projects/markdown/</a></td></tr><tr><td><a href="http://asciidoc.org/" title="http://asciidoc.org/">AsciiDoc</a></td><td>
-	    URL: <a href="http://asciidoc.org/" title="AsciiDoc">http://asciidoc.org/</a></td></tr><tr><td><a href="https://wiki.freebsd.org/" title="https://wiki.freebsd.org/">FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/" title="FreeBSD Wiki">https://wiki.freebsd.org/</a></td></tr><tr><td><a href="https://www.freebsd.org/" title="https://www.freebsd.org/">FreeBSD Web Site</a></td><td>
-	    URL: <a href="https://www.freebsd.org/" title="FreeBSD Web Site">https://www.freebsd.org/</a></td></tr><tr><td><a href="http://annotatorjs.org/" title="http://annotatorjs.org/">Annotator</a></td><td>
-	    URL: <a href="http://annotatorjs.org/" title="Annotator">http://annotatorjs.org/</a></td></tr><tr><td><a href="https://github.com/openannotation/annotator/wiki#backend-stores" title="https://github.com/openannotation/annotator/wiki#backend-stores">Annotator Backend Stores</a></td><td>
-	    URL: <a href="https://github.com/openannotation/annotator/wiki#backend-stores" title="Annotator Backend Stores">https://github.com/openannotation/annotator/wiki#backend-stores</a></td></tr></table><p>
-	Contact: FreeBSD Documentation Team &lt;<a href="mailto:freebsd-doc@FreeBSD.org">freebsd-doc@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the Developer Summit held in the two days before
-	BSDCan, a documentation working group meeting was held.  We
-	discussed some of the biggest opportunities available to the
-	documentation team.</p>
-
-      <p>Modernizing our translation system was, again, a major topic.
-	Making it easier for translators to do their work is vitally
-	important.  Translations make FreeBSD much more accessible for
-	non-English speakers, and those people and the translators
-	themselves often become valuable technical contributors in
-	other areas.  Progress was made in this area, and we hope to
-	have more news soon.</p>
-
-      <p>Methods of making it easier for people to contribute to
-	documentation was another major topic.  At present, we use
-	DocBook XML for articles and books, and mdoc(7) for man pages.
-	These markup languages are not very welcoming for new users.
-	There are simpler documentation markup languages like
-	reStructured Text (RST),
-	Markdown, and AsciiDoc that take less time to learn and use.
-	In fact, these markup systems are all similar to each other.
-	These systems tend to be more oriented towards visual
-	appearance rather than the semantic markup of our present
-	systems, although there might be ways to work around that.</p>
-
-      <p>Following the theme of making contributing easier, we also
-	discussed whether access to the FreeBSD Wiki can be more easily
-	granted, facilitating user contributions.
-	After the wiki was set up, automated account creation abuse
-	forced access to be limited.
-	It is tricky to allow submissions yet keep the
-	quality of submitted information usefully high.</p>
-
-      <p>Due to the markup systems used, it is difficult to review
-	documents for the quality of their information.  Annotator is
-	a Javascript system that allows adding notes to an existing
-	web page.  This would allow us to hold content-only reviews of
-	documentation web pages.  Reviewers would not see markup, so
-	they could concentrate only on whether the information was
-	accurate and complete.  To use this as desired, we need some
-	help with ports and testing.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Complete a port for the backend storage component of
-	  Annotator.  Preferably this would be the lowest overhead and
-	  most open-licensed version available.  Assistance from those
-	  familiar with Python and Javascript web development is
-	  welcome.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-Mastery:-ZFS-Now-Available" href="#FreeBSD-Mastery:-ZFS-Now-Available" id="FreeBSD-Mastery:-ZFS-Now-Available">FreeBSD Mastery: ZFS Now Available</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.zfsbook.com" title="http://www.zfsbook.com">FreeBSD Mastery: ZFS</a></td><td>
-	    URL: <a href="http://www.zfsbook.com" title="FreeBSD Mastery: ZFS">http://www.zfsbook.com</a></td></tr><tr><td><a href="https://www.michaelwlucas.com" title="https://www.michaelwlucas.com">Michael W. Lucas</a></td><td>
-	    URL: <a href="https://www.michaelwlucas.com" title="Michael W. Lucas">https://www.michaelwlucas.com</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	</p>
-      <p>The first ZFS book is now available at your favorite
-	bookstore.  Find a whole bunch of links at
-	<a href="http://www.zfsbook.com" shape="rect"><tt>zfsbook.com</tt></a>.</p>
-
-      <p>Work is proceeding apace on "FreeBSD Mastery: Advanced ZFS"
-	and "FreeBSD Mastery: Specialty Filesystems."  Lucas hopes to
-	have FMAZ complete and available before the next status
-	report.</p>
-    <hr /><h2><a name="Leap-Seconds-Article" href="#Leap-Seconds-Article" id="Leap-Seconds-Article">Leap Seconds Article</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/leap-seconds/article.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/leap-seconds/article.html">Leap Seconds Article</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/leap-seconds/article.html" title="Leap Seconds Article">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/leap-seconds/article.html</a></td></tr></table><p>
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>As the leap second scheduled for the end of June approached,
-	Bartek Rutkowski and others raised questions about how FreeBSD
-	handled leap seconds.  Leap seconds have caused serious
-	problems for other operating systems in the last few years,
-	and there was understandable concern.</p>
-
-      <p>It was reasonably pointed out that FreeBSD had encountered leap
-	seconds before, and would be fine this time also.  Still, the
-	absence of reported problems is not really a substitute for a
-	description of what to expect and how to know if a system is
-	prepared.</p>
-
-      <p>To address concerns and also provide a resource for future
-	leap seconds, several experts were pestered relentlessly,
-	with the results compiled into a short article.  Beyond merely
-	allaying fears about what might happen, this article received
-	positive responses on the web for how it demonstrated FreeBSD's
-	maturity and preparedness.</p>
-
-      <p>Great thanks for their patience and expertise are owed to
-	Peter Jeremy, Poul-Henning Kamp, Ian Lepore, Xin LI, Warner
-	Losh, and George Neville-Neil.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Compile other short articles on things that FreeBSD does
-	  really well.  Of particular interest are features that make
-	  life easier for sysadmins, or how problems on other systems
-	  are dealt with or even made non-problems on FreeBSD.</p>
-      </li></ol><hr /><h2><a name="New-Documentation-Committers" href="#New-Documentation-Committers" id="New-Documentation-Committers">New Documentation Committers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/">FreeBSD Porter's Handbook</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/" title="FreeBSD Porter's Handbook">https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/</a></td></tr><tr><td><a href="https://www.freebsd.org/" title="https://www.freebsd.org/">FreeBSD Web Site</a></td><td>
-	    URL: <a href="https://www.freebsd.org/" title="FreeBSD Web Site">https://www.freebsd.org/</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/" title="https://www.freebsdfoundation.org/">FreeBSD Foundation Web Site</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/" title="FreeBSD Foundation Web Site">https://www.freebsdfoundation.org/</a></td></tr></table><p>
-	Contact: FreeBSD Documentation Engineering Team &lt;<a href="mailto:doceng@FreeBSD.org">doceng@FreeBSD.org</a>&gt;
-	</p>
-      <p>Two new documentation committers were added to the team in
-	the second quarter of 2015.</p>
-
-      <p>Mathieu Arnold is a member of the FreeBSD Ports Management Team.
-	Over the past year, he has worked on many large and complex
-	updates to keep the Porter's Handbook current, and
-	continues to update this important document.</p>
-
-      <p>Anne Dickison is Marketing Director for the FreeBSD Foundation.
-	She will focus on updating and improving the FreeBSD main web
-	site.</p>
-
-      <p>We welcome both new committers and look forward to their
-	additional contributions!</p>
-    <hr /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/de/docs.html" title="https://www.freebsd.org/de/docs.html">Main German Documentation Project page</a></td><td>
-	    URL: <a href="https://www.freebsd.org/de/docs.html" title="Main German Documentation Project page">https://www.freebsd.org/de/docs.html</a></td></tr><tr><td><a href="https://people.freebsd.org/~jkois/FreeBSDde/de/" title="https://people.freebsd.org/~jkois/FreeBSDde/de/">How you can help with German translations</a></td><td>
-	    URL: <a href="https://people.freebsd.org/~jkois/FreeBSDde/de/" title="How you can help with German translations">https://people.freebsd.org/~jkois/FreeBSDde/de/</a></td></tr></table><p>
-	Contact:
-	  Bj�rn
-	  Heidotting
-	 &lt;<a href="mailto:bhd@FreeBSD.org">bhd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD German Documentation project maintains the German
-	translations of FreeBSD's documents such as the Handbook and the
-	website.</p>
-
-      <p>In the second quarter of 2015, we managed to catch up with
-	the translation work of the Handbook.  Two chapters are now
-	back in sync with their English reference chapters:
-	filesystems and ZFS.  The former was mainly done by Bj�rn
-	Heidotting as part of his mentee process.  The latter was done
-	by Benedict Reuschling, with valuable corrections by
-	Bj�rn.</p>
-
-      <p>Additionally, we updated many of our translation markers from
-	pre-SVN times.  This will help us get an overview of the
-	outstanding work in each chapter.  We are working on
-	integrating this into our website using a script, so people
-	can see which chapters need the most work or are most
-	up-to-date.</p>
-
-      <p>Johann made efforts to update the FreeBSD Documentation Project
-	Primer as well, so that translators willing to help us can
-	read the information in German.  He also made efforts to
-	revive the Documentation Project website, which was previously
-	hosted elsewhere, but disappeared.  Now, it is tied into the
-	German FreeBSD.org website again and has the same look and
-	feel.</p>
-
-      <p>Occasionally, people contact us and offer their help with the
-	translation effort.  We are happy to help newcomers get to
-	know everything about the translation process and look forward
-	to more contributions.  Even small updates make a big
-	difference and if you are considering helping, please contact
-	us.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Continue translating the Handbook and website into
-	  German.</p>
-      </li><li>
-	<p>Integrate a script that shows outstanding work into the
-	  German documentation webpages.</p>
-      </li></ol><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="GSoC-2015:-libc-Security-Extensions" href="#GSoC-2015:-libc-Security-Extensions" id="GSoC-2015:-libc-Security-Extensions">GSoC 2015: libc Security Extensions</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2015/FreeBSDLibcSecurityExtensions" title="https://wiki.freebsd.org/SummerOfCode2015/FreeBSDLibcSecurityExtensions">Project Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2015/FreeBSDLibcSecurityExtensions" title="Project Wiki Page">https://wiki.freebsd.org/SummerOfCode2015/FreeBSDLibcSecurityExtensions</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D3043" title="https://reviews.freebsd.org/D3043">Code Review Differential</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D3043" title="Code Review Differential">https://reviews.freebsd.org/D3043</a></td></tr></table><p>
-	Contact:
-	  Pedro
-	  Giffuni
-	 &lt;<a href="mailto:pfg@FreeBSD.org">pfg@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oliver
-	  Pinter
-	 &lt;<a href="mailto:op@FreeBSD.org">op@FreeBSD.org</a>&gt;
-	</p>
-      <p>As part of this year's Google Summer of Code, we have been
-	adding support for the <tt>_FORTIFY_SOURCE</tt> extension to
-	<tt>libc</tt>.  This extension uses the GCC
-	<tt>builtin_object_size</tt> information to prevent buffer overflows in
-	existing code.  The compiler and the C library can effectively
-	detect a set of common programming mistakes.</p>
-
-      <p>A mixed version of the NetBSD and
-	Android implementations has been ported and is currently
-	undergoing heavy testing.  On FreeBSD, this code has already
-	found two small bugs.  On the other hand, the FreeBSD codebase
-	is extremely useful to test the framework.</p>
-    <p>This project was sponsored by Google Summer of Code Program.</p><h3>Open tasks:</h3><ol><li>
-	<p>Code review and more buildworld testing with GCC.</p>
-      </li><li>
-	<p>Integration tests, especially on non-x86 platforms.</p>
-      </li><li>
-	<p>Documentation: the framework is relatively popular on GNU
-	  <tt>libc</tt> but we still have to work on better documentation.</p>
-      </li><li>
-	<p>Testing and possibly integrating with ports.</p>
-      </li><li>
-	<p>We will have to re-schedule the GSoC project, as we were
-	  expecting to spend less time on this.</p>
-      </li></ol><hr /><h2><a name="Multiqueue-Testing" href="#Multiqueue-Testing" id="Multiqueue-Testing">Multiqueue Testing</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2015/MultiqueueTestingProject" title="https://wiki.freebsd.org/SummerOfCode2015/MultiqueueTestingProject">Multiqueue Testing Project</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2015/MultiqueueTestingProject" title="Multiqueue Testing Project">https://wiki.freebsd.org/SummerOfCode2015/MultiqueueTestingProject</a></td></tr></table><p>
-	Contact:
-	  Tiwei
-	  Bie
-	 &lt;<a href="mailto:btw@FreeBSD.org">btw@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Hiren
-	  Panchasara
-	 &lt;<a href="mailto:hiren@FreeBSD.org">hiren@FreeBSD.org</a>&gt;
-	</p>
-      <p>The aim of this project is to design and implement an
-	infrastructure to validate that a number of the network
-	stack's multiqueue behaviours are as expected.</p>
-
-      <p>It mainly consists of extending <tt>tap(4)</tt> to provide
-	the same RSS behaviours as the hardware multiqueue network
-	cards, developing simple test applications using multiqueue
-	<tt>tap(4)</tt> and <tt>socket(2)</tt>, adding hooks in each
-	layer of the network stack to collect the per-ring per-cpu
-	per-layer statistics, and extending <tt>netstat(1)</tt> to
-	report these statistics.</p>
-
-      <p>At present, most parts of this project have been implemented.
-	The focus is on the code review, and API/KPI freeze.</p>
-    <p>This project was sponsored by Google Summer of Code 2015.</p><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan-2015" href="#BSDCan-2015" id="BSDCan-2015">BSDCan 2015</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdcan.org/2015/" title="http://www.bsdcan.org/2015/">BSDCan 2015</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2015/" title="BSDCan 2015">http://www.bsdcan.org/2015/</a></td></tr><tr><td><a href="https://www.youtube.com/playlist?list=PLWW0CjV-TafY0NqFDvD4k31CtnX-CGn8f" title="https://www.youtube.com/playlist?list=PLWW0CjV-TafY0NqFDvD4k31CtnX-CGn8f">BSDCan 2015 Video Playlist</a></td><td>
-	    URL: <a href="https://www.youtube.com/playlist?list=PLWW0CjV-TafY0NqFDvD4k31CtnX-CGn8f" title="BSDCan 2015 Video Playlist">https://www.youtube.com/playlist?list=PLWW0CjV-TafY0NqFDvD4k31CtnX-CGn8f</a></td></tr></table><p>
-	Contact:
-	  Dan
-	  Langille
-	 &lt;<a href="mailto:dvl@FreeBSD.org">dvl@FreeBSD.org</a>&gt;
-	</p>
-      <p>BSDCan, a conference for people working on and with
-	4.4BSD-based operating systems and related projects, was held
-	in Ottawa, Ontario on June 12 and 13.  A two-day FreeBSD
-	developer summit event preceded it on June 10 and 11.</p>
-
-      <p>This was the largest BSDCan ever, with over 280 attendees, up
-	by more than 40 people over the 2014 event.  There were a
-	record number of speakers and talks.  An additional room and
-	"track" was added to provide even more choices for concurrent
-	talks on both days of the conference.  Social media response
-	to the whole conference has been very positive.</p>
-
-      <p>The keynote talk by Stephen Bourne was very popular.  So
-	popular, in fact, that the main conference room could not hold
-	all the attendees.  An overflow room with live video was set
-	up to hold the extra people.  The
-	<a href="https://www.youtube.com/watch?v=2kEJoWfobpA" shape="rect">video</a>
-	of the presentation has had over 6300 views in the first
-	twelve days.</p>
-
-      <p>Andrew Tanenbaum's talk on
-	<a href="https://www.youtube.com/watch?v=0pebP891V0c" shape="rect">reimplementing NetBSD using a MicroKernel</a>
-	was so well-attended it was standing room only.</p>
-
-      <p>There were many other excellent talks, and we recommend
-	browsing through the playlist in the links above.</p>
-
-      <p>Activity was not limited to the talks.  Each night, the
-	"Hacker Lounge" was used by developers to cooperate and
-	interact on projects.  Embedded projects were popular this
-	year, as FreeBSD was installed directly on wireless
-	routers.</p>
-
-      <p>The very successful and well-attended closing event, held
-	at the Lowerton Brewery, provided an elegant closure to the
-	whole conference.</p>
-
-      <p>We would like to thank everyone who made BSDCan 2015 such a
-	success, and look forward to next year!</p>
-    <hr /><h2><a name="FreeBSD-Support-in-pkgsrc" href="#FreeBSD-Support-in-pkgsrc" id="FreeBSD-Support-in-pkgsrc">FreeBSD Support in pkgsrc</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.pkgsrc.org" title="https://www.pkgsrc.org">pkgsrc home page</a></td><td>
-	    URL: <a href="https://www.pkgsrc.org" title="pkgsrc home page">https://www.pkgsrc.org</a></td></tr><tr><td><a href="http://bulktracker.appspot.com" title="http://bulktracker.appspot.com">BulkTracker: Track bulk build status</a></td><td>
-	    URL: <a href="http://bulktracker.appspot.com" title="BulkTracker: Track bulk build status">http://bulktracker.appspot.com</a></td></tr><tr><td><a href="https://www.geeklan.co.uk/?tag=pkgsrc" title="https://www.geeklan.co.uk/?tag=pkgsrc">Blog posts on pkgsrc</a></td><td>
-	    URL: <a href="https://www.geeklan.co.uk/?tag=pkgsrc" title="Blog posts on pkgsrc">https://www.geeklan.co.uk/?tag=pkgsrc</a></td></tr></table><p>
-	Contact:
-	  Sevan
-	  Janiyan
-	 &lt;<a href="mailto:venture37@geeklan.co.uk">venture37@geeklan.co.uk</a>&gt;
-	</p>
-      <p><tt>pkgsrc</tt> is a fork of the FreeBSD Ports Collection by
-	the NetBSD
-	project with a focus on portability and multi-platform
-	support.  At present, pkgsrc supports building packages on 23
-	different platforms from a single tree, including FreeBSD</p>
-
-      <p>While <tt>pkgsrc</tt> is not a replacement for ports in most
-	use cases, it holds a unique position in mixed-platform
-	environments where software needs to be the same
-	version across all systems and built in a consistent
-	manner, saving the user from having to resort to manually
-	building programs or re-implementing a mechanism to do so.</p>
-
-      <p>With the recent
-	<a href="http://mail-index.netbsd.org/pkgsrc-users/2015/07/06/msg021778.html" shape="rect">2015Q2 release</a>
-	earlier this month, it is now possible to generate over 14000
-	packages on FreeBSD 10.1-RELEASE (up from 12800 last
-	quarter).</p>
-
-      <p>Work is in progress to add
-	<a href="https://vimeo.com/132766052" shape="rect">pkg support to pkgsrc.</a></p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Improve platform support to skip libusb on FreeBSD where
-	libusb is bundled in base.  This is causing the biggest
-	breakage at the moment.</p>
-      </li><li>
-	<p>Expand the effort to the -STABLE and -CURRENT branches and, if
-	  possible, architectures other than amd64.  Contributing
-	  shell access to such machines would be helpful (an unprivileged
-	  account is sufficient).</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">Foundation website</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="Foundation website">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Funding comes from individual and
-	corporate donations and is used to fund and manage development
-	projects, conferences and developer summits, and provide
-	travel grants to FreeBSD developers.  The Foundation purchases
-	hardware to improve and maintain FreeBSD infrastructure and
-	publishes FreeBSD white papers and marketing material to promote,
-	educate, and advocate for the FreeBSD Project.  The Foundation
-	also represents the FreeBSD Project in executing contracts,
-	license agreements, and other legal arrangements that require
-	a recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD during
-	the last quarter:</p>
-
-      <ul>
-	<li>
-	  <p>We were a Platinum Sponsor for BSDCan 2015 and the
-	    sponsor for the Ottawa developer and vendor summits.  We
-	    were pleased to provide 12 travel grants for FreeBSD
-	    contributors to attend the conference and have
-	    opportunities to meet face-to-face with other FreeBSD
-	    contributors.  You can read some of their trip reports
-	    <a href="http://freebsdfoundation.blogspot.com/2015_06_01_archive.html" shape="rect">here</a>.</p>
-
-	  <p>In celebration of our 15th anniversary we provided a
-	    delicious FreeBSD cake, which was happily devoured by
-	    conference attendees.</p>
-
-	  <p>Various Foundation team members gave talks, attended
-	    talks, participated in doc sprints, worked on efforts to
-	    improve FreeBSD, worked at our booth, and spent time
-	    talking to our constituents about areas where we can help
-	    with FreeBSD.</p>
-
-	  <p>Foundation members gave these talks:</p>
-
-	  <p><ul>
-	    <li> Anne Dickison: "FreeBSD Advocacy: How you can spread
-	      the word"</li>
-
-	    <li>Kirk McKusick:
-	      <a href="http://www.bsdcan.org/2015/schedule/events/525.en.html" shape="rect">"An Introduction to the Implementation of ZFS"</a>
-	    </li>
-
-	    <li>George Neville-Neil:
-	      <a href="http://www.bsdcan.org/2015/schedule/events/528.en.html" shape="rect">"Measure Twice, Code Once"</a>
-	      and
-	      <a href="http://www.bsdcan.org/2015/schedule/events/566.en.html" shape="rect">"Cambridge L41: Teaching Advanced Operating Systems with FreeBSD"</a>
-	    </li>
-
-	    <li>Ed Maste:
-	      <a href="http://www.bsdcan.org/2015/schedule/events/567.en.html" shape="rect">"The LLDB Debugger in FreeBSD"</a>
-	      and Ed Maste also ran the Vendor Summit.
-	    </li>
-	  </ul></p>
-	</li>
-
-	<li>
-	  <p>We held our annual board meeting in Ottawa.  We are
-	    pleased to announce the addition of Benedict Reuschling to
-	    our board of directors.  Read his interview
-	    <a href="http://freebsdfoundation.blogspot.com/2015/07/freebsd-foundation-welcomes-new-board.html" shape="rect">here</a>.
-	    The current board of directors and officers were all
-	    re-elected.  You can find out who is on our board
-	    <a href="https://www.freebsdfoundation.org/board" shape="rect">here</a>.
-	    We spent the day planning our 12-month goals, project
-	    roadmapping, FreeBSD education offerings, fundraising, and
-	    advocacy efforts.</p>
-	</li>
-
-	<li>
-	  <p>Dru Lavigne promoted and gave a presentation on FreeBSD
-	    at
-	    <a href="http://linuxfestnorthwest.org/2015" shape="rect">LinuxFest
-	      Northwest 2015</a>.</p>
-	</li>
-
-	<li>
-	  <p>We have committed to sponsoring several upcoming conferences:
-	    vBSDCon, womENcourage 2015, EuroBSDCon 2015, Grace Hopper
-	    conference, BSDCon Brasil, Cambridge Developer Summit, and
-	    OpenZFS. You'll also find us at OSCON, July 21-23, and the
-	    SNIA Storage Developer Conference, Sept 21-24.</p>
-	</li>
-
-	<li>
-	  <p>Fundraising</p>
-
-	  <p>So far, we have raised $361,000 for 2015 from over 500
-	    donors.  Juniper became a Gold level donor.  We are
-	    actively approaching commercial FreeBSD users for Silver-plus
-	    donations, and asking large tech companies for separate
-	    women in tech funding, to help us recruit more women to
-	    the FreeBSD Project.  We are also asking companies for
-	    funding to help with our FreeBSD education efforts.</p>
-	</li>
-
-	<li>
-	  <p>We had the pleasure of hosting Groff the BSD Goat here in
-	    Colorado in April.</p>
-	</li>
-
-	<li>
-	  <p>Infrastructure Support</p>
-
-	  <p>The Foundation funded almost $50,000 of equipment to support FreeBSD
-	    infrastructure.  Most of this went towards new and
-	    upgraded servers at the NYI facility.  We sent Glen Barber
-	    there to install the new servers.  You can read all about
-	    <a href="http://freebsdfoundation.blogspot.com/2015/05/another-data-center-site-visit-nyi.html" shape="rect">his
-	      trip</a>.</p>
-	</li>
-
-	<li>
-	  <p>Advocacy Work</p>
-
-	  <p>The FreeBSD Journal has over 9200 subscribers, with a 98%
-	    renewal rate.  Our marketing director, Anne Dickison, was
-	    busy providing advocacy work for the Project.  She helped
-	    provide more FreeBSD marketing literature and material.  This
-	    included the cool <i>I Choose FreeBSD</i> sticker and very
-	    popular <i>I Love FreeBSD</i> temporary tattoos that are available
-	    at conferences.  We published April, May, and June
-	    Foundation Newsletters to highlight the work being done by
-	    the Foundation to support FreeBSD.  These newsletters also
-	    include company FreeBSD testimonials, upcoming events where
-	    FreeBSD will be promoted, and the new From the Trenches
-	    articles from FreeBSD contributor experiences working with
-	    FreeBSD.</p>
-	</li>
-
-	<li>
-	  <p>One of the Foundation's responsibilities is to protect
-	    FreeBSD intellectual property (IP).  This includes protecting
-	    the FreeBSD trademarks.  We granted trademark usage
-	    permission to various companies who want to show their
-	    support for FreeBSD.  To get permission to use the
-	    trademarks, interested parties must agree to our
-	    <a href="https://www.freebsdfoundation.org/documents/guidelines" shape="rect">Trademark
-	      Usage Terms and Conditions</a>.</p>
-	</li>
-
-	<li>
-	  <p>Project Development Work</p>
-
-	  <p>George Neville-Neil signed up new universities to look at
-	    the FreeBSD course including George Washington University,
-	    Johns Hopkins, and UC Santa Cruz.  He is working with
-	    Verisign on the DevSummit that will be held at vBSDCon.
-	    He also worked with ARM to set up meeting with 18 hardware
-	    and silicon vendors at the ARM Partner Meeting in
-	    August.</p>
-
-	  <p>Ed Maste continued managing the FreeBSD/arm64 porting
-	    project.  He also continued with updates to the ELF
-	    Toolchain tools in the FreeBSD base system and incorporated a
-	    set of fixes from the upstream project to fix issues with
-	    the <tt>strip</tt> tool.  Ed investigated and fixed a set
-	    of outstanding issues with the new <tt>vt(4)</tt> console
-	    in the FreeBSD installer.</p>
-
-	  <p>Staff member Edward Napiera&#322;a committed a number of bug
-	    fix merges to the stable/10 branch for inclusion in FreeBSD
-	    10.2, and continued investigation of a project to support
-	    runtime switching of the root file system.  He merged a
-	    large number of improvements to the <tt>autofs</tt>
-	    <tt>automount</tt> daemon.  He also supported FreeBSD
-	    developer Dmitry Chagin's work on 64-bit Linux binary
-	    emulation support by reviewing the extensive patch set.
-	    Those changes are now committed to FreeBSD's Subversion
-	    tree, and will arrive in FreeBSD 11.0.</p>
-
-	  <p>Staff member Konstantin Belousov continued development on
-	    the Intel DMA remap (DMAR) and Process Context Identifier
-	    (PCID) infrastructure projects.  Kostik also contributed
-	    an extensive set of changes to multiple aspects of FreeBSD:
-	    stability improvements in the virtual memory subsystem,
-	    improved compatibility in options handling in the runtime
-	    loader, thread library improvements, and GDB debugger
-	    enhancements.</p>
-
-	  <p>Glen Barber, who is a Foundation employee, is also a
-	    release engineer for the Project.  Here are some
-	    highlights of what he did to help the Project:</p>
-
-	  <ul>
-	    <li>Added support to the release build code in 11-CURRENT
-	      for producing FreeBSD/aarch64 (arm64) memory stick images
-	      and virtual machine disk images for use within
-	      Qemu.</li>
-
-	    <li>Worked with Colin Percival and Brad Davis on testing
-	      and refining the release build code to support building
-	      Amazon EC2 images, and Vagrant images for Hashicorp
-	      Atlas, respectively.</li>
-
-	    <li>Reworked the FreeBSD/arm build code to provide a
-	      fully-native build infrastructure for the existing
-	      images (BEAGLEBONE, RPI-B, PANDABOARD, WANDBOARD), and
-	      add support for additional images (GUMSTIX,
-	      CUBOX/HUMMINGBOARD).</li>
-
-	    <li>Wrote several additional utilities to reduce human
-	      error in several areas of Release Engineering, including
-	      producing the filesystem hierarchy used by the FTP
-	      mirrors, enhancements to the internal build scripts used
-	      by Release Engineering, and support for automatically
-	      uploading and publishing virtual machine images.</li>
-
-	    <li>While attending BSDCan 2015, Glen worked with several
-	      developers and teams on various items, such as
-	      discussing packaging the base system with
-	      <tt>pkg(8)</tt>, migrating internal FreeBSD servers to the
-	      new machines the Foundation purchased for the NYI
-	      facility, and discussing further possible future
-	      enhancements to the FreeBSD build infrastructure.</li>
-
-	    <li>Started the 10.2-RELEASE cycle.</li>
-
-	  </ul>
-	</li>
-      </ul>
-    <hr /><h2><a name="ZFS-Support-for-UEFI-Boot/Loader" href="#ZFS-Support-for-UEFI-Boot/Loader" id="ZFS-Support-for-UEFI-Boot/Loader">ZFS Support for UEFI Boot/Loader</a></h2><p>
-	Contact:
-	  Eric
-	  McCorkle
-	 &lt;<a href="mailto:emc2@metricspace.net">emc2@metricspace.net</a>&gt;
-	</p>
-      <p>UEFI-enabled <tt>boot1.efi</tt> and <tt>loader.efi</tt> have
-	been modified to support loading and booting from a ZFS
-	filesystem.  The patch currently works with
-	<tt>buildworld</tt>, and successfully boots on a test machine
-	with a ZFS partition.  In addition, the ZFS-enabled
-	<tt>loader.efi</tt> can be treated as a chainloader using
-	ZFS-enabled GRUB.</p>
-
-      <p>The work on <tt>boot1.efi</tt> also reorganizes the code
-	somewhat, splitting out the filesystem-specific parts into a
-	modular framework.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>More testing is needed for the following use cases: ZFS with
-	  GRUB+<tt>loader.efi</tt>, ZFS with
-	  <tt>boot1</tt>+<tt>loader.efi</tt>, UFS with
-	  <tt>boot1</tt>+<tt>loader.efi</tt> (to test the modularization of
-	  <tt>boot1.efi</tt>)</p>
-      </li><li>
-	<p>Have <tt>boot1.efi</tt> check partition type GUIDs before
-	  probing for filesystems.</p>
-      </li><li>
-	<p>Get patch accepted upstream and committed.</p>
-      </li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2015-07-2015-09.html b/website/content/en/status/report-2015-07-2015-09.html
deleted file mode 100644
index 74ca5c551f..0000000000
--- a/website/content/en/status/report-2015-07-2015-09.html
+++ /dev/null
@@ -1,2639 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" src="../../layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The third quarter of 2015, from July to September, was
-      again a period of busy activity for FreeBSD: for the second quarter
-      in a row we have the largest report yet published.</p><p>The Foundation continues to play a strong role, bringing
-      both a developer and evangelist presence to conferences, funding
-      much of the hardware that the cluster administration team uses to
-      keep things running, and sponsoring many development projects for
-      FreeBSD.  This quarter we also hear from some of the student projects
-      funded by Google Summer of Code 2015, ranging a wide gamut from
-      the bootloader to additional ARM support, but also at a range of
-      completion status.  Some of the GSoC output is in the tree
-      already, but others could benefit from additional attention to
-      help out our budding new contributors as their schedules fill with
-      the return to classes.</p><p>ZFS and the network stack continue to be strong areas for
-      FreeBSD, with both receiving active maintenance and feature
-      improvements during this quarter.  Substantial work continues on
-      arm64, potentially putting it on the path toward a promotion to
-      Tier-1 status, and a new port to the RISC-V architecture has
-      made great headway in a short period of time.  But it is not just
-      our strengths and exciting new areas that have seen attention this
-      cycle; there are also some parts of the system that are frequently
-      perceived as unchanging infrastructure that have received
-      attention and improvements, with <tt>truss</tt> and
-      (<tt>k</tt>)<tt>gdb</tt> receiving significant overhauls, new
-      implementations for the man page tools being brought in, the
-      website receiving a new skin, and a brand new system for
-      translating documentation that greatly lowers the barrier to
-      entry.</p><p>Nonetheless, despite its record length, this report does
-      not and cannot cover all of the work being done on FreeBSD throughout
-      the reporting period &#8212; there are many bug fixes too minor to
-      mention here, and developers too busy working on the next project
-      to write up an entry for the previous project.  It is not just the
-      developers committing to Subversion that comprise the ongoing
-      activities of FreeBSD, but also the users testing unreleased
-      code or reporting bugs in released code, and participants on the
-      mailing lists and forums helping each other solve their problems.
-      Even the chats on IRC that wander far from the stated topic of a
-      channel contribute to the community around FreeBSD; it is that
-      community whose effectiveness and helpfulness is a key component
-      of the effectiveness and usefulness of FreeBSD itself.  Not just to
-      the developers listed in this report, but to everyone in the
-      community, thank you for making FreeBSD a great operating system.</p><p><i>&#8212;Ben Kaduk</i></p><p><hr /></p><p>Please submit status reports for the fourth quarter of 2015
-      (from October to December) by January 7, 2016.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#automtud:-Better-Jumbo-Frame-Support">automtud: Better Jumbo Frame Support</a></li><li><a href="#bhyve">bhyve</a></li><li><a href="#Clang,-llvm,-lldb,-compiler-rt-and-libc++-Updated-to-3.7.0">Clang, llvm, lldb, compiler-rt and libc++ Updated to 3.7.0</a></li><li><a href="#DTrace-and-TCP">DTrace and TCP</a></li><li><a href="#FreeBSD-on-the-Acer-C720-Chromebook">FreeBSD on the Acer C720 Chromebook</a></li><li><a href="#High-Availability-Clustering-in-CTL">High Availability Clustering in CTL</a></li><li><a href="#Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></li><li><a href="#Porting-bhyve-to-ARM-based-Platforms">Porting bhyve to ARM-based Platforms</a></li><li><a href="#Root-Remount">Root Remount</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#The-nosh-Project">The nosh Project</a></li><li><a href="#UEFI-Boot-and-Framebuffer-Support">UEFI Boot and Framebuffer Support</a></li><li><a href="#ZFS-Code-Sync-with-Latest-Illumos">ZFS Code Sync with Latest Illumos</a></li><li><a href="#ZFS-Support-for-UEFI-Boot/Loader">ZFS Support for UEFI Boot/Loader</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Adding-PCIe-Hot-plug-Support">Adding PCIe Hot-plug Support</a></li><li><a href="#Cavium-LiquidIO-Smart-NIC-Driver">Cavium LiquidIO Smart NIC Driver</a></li><li><a href="#CloudABI:-Pure-Capabilities-Runtime-Environment">CloudABI: Pure Capabilities Runtime Environment</a></li><li><a href="#FreeBSD-Xen">FreeBSD Xen</a></li><li><a href="#ioat(4)-Driver-Import">ioat(4) Driver Import</a></li><li><a href="#IPsec-Upgrades">IPsec Upgrades</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Atomics">Atomics</a></li><li><a href="#FreeBSD-on-Cavium-ThunderX-(arm64)">FreeBSD on Cavium ThunderX (arm64)</a></li><li><a href="#FreeBSD-on-the-HiKey-ARMv8-Board">FreeBSD on the HiKey ARMv8 Board</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#FreeBSD/RISC-V-Port">FreeBSD/RISC-V Port</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#mandoc-and-roff-Toolchain">mandoc and roff Toolchain</a></li><li><a href="#pkg-1.6">pkg 1.6</a></li><li><a href="#sesutil(8)">sesutil(8)</a></li><li><a href="#truss(1)">truss(1)</a></li><li><a href="#Updates-to-GDB">Updates to GDB</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Bringing-GitLab-into-the-Ports-Collection">Bringing GitLab into the Ports Collection</a></li><li><a href="#GNOME-on-FreeBSD">GNOME on FreeBSD</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Node.js-Modules">Node.js Modules</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Ports-on-PowerPC">Ports on PowerPC</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#PO-Translation-Project">PO Translation Project</a></li><li><a href="#Website-CSS-Update">Website CSS Update</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Allwinner-A10/A20-Support">Allwinner A10/A20 Support</a></li><li><a href="#mtree-Parsing-and-Manipulation-Library">mtree Parsing and Manipulation Library</a></li><li><a href="#Multiqueue-Testing">Multiqueue Testing</a></li><li><a href="#Update-Ficl-in-Bootloader">Update Ficl in Bootloader</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p>
-	Contact: FreeBSD Cluster Administration Team &lt;<a href="mailto:clusteradm@">clusteradm@</a>&gt;
-	</p>
-      <p>The FreeBSD Cluster Administration Team consists of the people
-	responsible for administering the machines that the project
-	relies on for its distributed work and communications to be
-	synchronised.</p>
-
-      <p>Our primary cluster has been hosted as a guest in California
-	for many years.  Our ongoing project is relocating the core
-	functionality to a location in New Jersey with a formal
-	hosting arrangement.  This is an equipment refresh,
-	consolidation for better use of resources, and for better
-	continuity of service.</p>
-
-      <p>There is a significant amount of behind-the-scenes work to
-	make this happen.  The original cluster was implemented with
-	a common, shared, assumed-to-be secure network with
-	ubiquitous NFS everywhere.  This structure does not lend
-	itself well to being distributed across geographically
-	diverse locations, particularly when Internet transit is
-	required.  The bulk of the work is rebuilding services to be
-	portable, stand-alone components that do not depend on
-	shared-network access and are safe enough to use across the
-	insecure Internet.</p>
-
-      <p>Highlights this quarter:</p>
-
-      <ul>
-	<li>Many internal distribution systems switched from rsync to
-	  a distribution mesh using "syncthing".</li>
-
-	<li>We have implemented more code/data signing infrastructure
-	  with out-of-band verification.</li>
-
-	<li>New 32-core reference build hosts are online.</li>
-
-	<li>Internal admbugs switched from bugzilla 4.4 to 5.0 and
-	  packages were made available for the bugmeister team.</li>
-
-	<li>Finally switched from varnish3 to varnish4.</li>
-
-	<li>We exorcised hub.FreeBSD.org, the last survivor of the
-	  2012 security incident.</li>
-
-	<li>vuxml and the legacy portaudit build system were converted
-	  to components and integrated.</li>
-
-	<li>https://download.FreeBSD.org/ is nearing completion
-	  (please do not use until officially announced).</li>
-
-	<li>A Taiwan node was brought into service for pkg, ftp,
-	  svn, and vuxml mirroring.</li>
-
-	<li>One of the freebsd-update mirrors was converted from
-	  lighttpd to nginx due to a data corruption bug.</li>
-
-	<li>We completed detachment of the svn repository from the old
-	  cluster and moved it to its new location.</li>
-      </ul>
-
-      <p>Ongoing:</p>
-
-      <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 current code.</li>
-
-	<li>We build internal base system snapshots every few days
-	  and packages every day.</li>
-
-	<li>We also provide support for non-clusteradm-operated
-	  services including jenkins, reviews, portsnap,
-	  freebsd-update, bugzilla, package builders, git, and
-	  mercurial.  This varies from as little as maintaining SSL
-	  front-ends through operating servers, distributing data or
-	  building packages/binaries to run.</li>
-      </ul>
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/10.2R/announce.html" title="https://www.freebsd.org/releases/10.2R/announce.html">FreeBSD�10.2-RELEASE announcement</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/10.2R/announce.html" title="FreeBSD�10.2-RELEASE announcement">https://www.freebsd.org/releases/10.2R/announce.html</a></td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/10.3R/schedule.html" title="https://www.freebsd.org/releases/10.3R/schedule.html">FreeBSD�10.3-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/10.3R/schedule.html" title="FreeBSD�10.3-RELEASE schedule">https://www.freebsd.org/releases/10.3R/schedule.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/11.0R/schedule.html" title="https://www.freebsd.org/releases/11.0R/schedule.html">FreeBSD�11.0-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.0R/schedule.html" title="FreeBSD�11.0-RELEASE schedule">https://www.freebsd.org/releases/11.0R/schedule.html</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>In mid-August, the FreeBSD�Release Engineering Team
-	released FreeBSD�10.2-RELEASE, two weeks earlier than the
-	original schedule anticipated.</p>
-
-      <p>The FreeBSD�Release Engineering Team would like to thank
-	all that have tested the BETA and RC builds and reported
-	issues during the release cycle.</p>
-
-      <p>The FreeBSD�Release Engineering Team, with approval from
-	the FreeBSD�Core Team, appointed Marius Strobl as the Deputy
-	Lead.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The biggest task handled by the Core Team during this quarter
-	was developing and publishing the new Code of Conduct.  The
-	Code of Conduct describes how people are expected to behave on
-	all FreeBSD official communication channels, as well as how
-	developers and other people involved with the project are to
-	behave when representing the project in public.</p>
-
-      <p>The Code of Conduct was generally well received and elicited
-	numerous comments and suggestions for improvements from the
-	community, many of which have been integrated.</p>
-
-      <p>The next task handled by Core was the restoration of Babak
-	Farrokhi's ports commit bit.  Babak resides in Iran.  A few
-	years ago, legal advice suggested that allowing contributions
-	from Iranian residents might violate US trade sanctions.
-	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 residing in Iran.</p>
-
-      <p>The CTM service came under security review.  Given that the
-	lack of use of routine authenticity checking made the
-	injection of trivial exploit code relatively easy, the service
-	was held to be too risky to continue as an official part of
-	the FreeBSD base system.  CTM has very few remaining users but
-	they should be able to install CTM from the Ports Collection
-	in order to continue doing so.</p>
-
-      <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 FreeBSD cluster to that data center.
-	Cluster administration has taken ownership of the situation
-	and is making progress.</p>
-
-      <p>Core fielded an enquiry about NextBSD and whether this should
-	be the future direction for the whole FreeBSD project.  Core's
-	position is that NextBSD is an interesting project, and we
-	regard it, like the other BSD projects, as a potential source
-	of good ideas.  However, we currently have no plans to adopt
-	NextBSD as the official FreeBSD distribution.</p>
-
-      <p>Beyond these issues, Core also spent time in various routine
-	activities.  During this quarter we issued three new src
-	commit bits, and took none in for safekeeping.  Welcome to
-	Allan Jude, Marcelo Araujo, and Andriy Voskoboinyk.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="automtud:-Better-Jumbo-Frame-Support" href="#automtud:-Better-Jumbo-Frame-Support" id="automtud:-Better-Jumbo-Frame-Support">automtud: Better Jumbo Frame Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/jmgurney/automtud" title="https://github.com/jmgurney/automtud">jmgurney/automtud on github</a></td><td>
-	    URL: <a href="https://github.com/jmgurney/automtud" title="jmgurney/automtud on github">https://github.com/jmgurney/automtud</a></td></tr></table><p>
-	Contact: 
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>automtud</tt> script will allow a FreeBSD machine to
-	send jumbo frames to machines that support them, while using
-	normal-sized frames for other machines.</p>
-
-      <p>There are various advantages to using jumbo frames, such as
-	reduced protocol overhead.  It also means that TCP streams
-	will not be segmented as much, although TSO helps mitigate the
-	disadvantages of such segmentation.  In cases where LRO does
-	not work well, fewer packets will be received.</p>
-
-      <p>The script currently does not restore the system to its
-	original state when it exits.  This means that you must
-	manually change the interface MTU and delete host routes
-	after stopping the script.
-      </p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Fix up various Ethernet drivers to better support jumbo
-	  frames.  Most Ethernet drivers, though they support
-	  scatter/gather, use a physically contiguous zone to do so,
-	  which can cause resource shortages.</p>
-      </li><li>
-	<p>More testing is needed to ensure that things behave as
-	  expected.  This means that when running the script,
-	  communication to all machines functions normally, without
-	  slowdown or connectivity issues.  Check
-	  <tt>vmstat -z | grep mbuf</tt> to ensure that such issues
-	  are not due to running out of <tt>jumbo_9k</tt> or
-	  <tt>jumbo_16k</tt> buffers due to Ethernet driver
-	  issues.</p>
-      </li></ol><hr /><h2><a name="bhyve" href="#bhyve" id="bhyve">bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bhyve.org" title="http://www.bhyve.org">bhyve FAQ and talks</a></td><td>
-	    URL: <a href="http://www.bhyve.org" title="bhyve FAQ and talks">http://www.bhyve.org</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/NE2000EmulationForBhyve" title="https://wiki.FreeBSD.org/SummerOfCode2015/NE2000EmulationForBhyve">NE2000 device emulation GSoC project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/NE2000EmulationForBhyve" title="NE2000 device emulation GSoC project">https://wiki.FreeBSD.org/SummerOfCode2015/NE2000EmulationForBhyve</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm" title="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm">Porting bhyve to ARM GSoC project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm" title="Porting bhyve to ARM GSoC project">https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/ptnetmapOnBhyve" title="https://wiki.FreeBSD.org/SummerOfCode2015/ptnetmapOnBhyve">ptnetmap support in bhyve GSoC project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/ptnetmapOnBhyve" title="ptnetmap support in bhyve GSoC project">https://wiki.FreeBSD.org/SummerOfCode2015/ptnetmapOnBhyve</a></td></tr><tr><td><a href="http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506" title="http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506">Windows support</a></td><td>
-	    URL: <a href="http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506" title="Windows support">http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506</a></td></tr><tr><td><a href="http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101" title="http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101">Illumos support</a></td><td>
-	    URL: <a href="http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101" title="Illumos support">http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101</a></td></tr></table><p>
-	Contact: 
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Neel
-	  Natu
-	 &lt;<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Tycho
-	  Nightingale
-	 &lt;<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>&gt;
-	<br />
-	Contact: 
-	  Michael
-	  Dexter
-	 &lt;<a href="mailto:editor@callfortesting.org">editor@callfortesting.org</a>&gt;
-	</p>
-      <p><tt>bhyve</tt> is a hypervisor that runs on the FreeBSD/amd64
-	platform.  At present, it runs FreeBSD (8.x or later), Linux
-	i386/x64, OpenBSD i386/amd64, NetBSD/amd64, Illumos, and
-	Windows Vista/7/8/10/2008r2/2012r2/2016 x64 guests.  Current
-	development is focused on enabling additional guest operating
-	systems and implementing features found in other
-	hypervisors.</p>
-
-      <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> included live migration and
-	suspend/resume support, and configurations using ZFS.</p>
-
-      <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 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>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Improve the documentation.</p>
-      </li><li>
-	<p><tt>bhyveucl</tt> is a work-in-progress script for
-	  starting <tt>bhyve</tt> instances based on a libUCL config
-	  file.  More information at
-	  <a href="https://github.com/allanjude/bhyveucl" shape="rect">https://github.com/allanjude/bhyveucl</a>.</p>
-      </li><li>
-	<p>Add support for virtio-scsi.</p>
-      </li><li>
-	<p>Flexible networking backends: wanproxy, vhost-net.</p>
-      </li><li>
-	<p>Support running <tt>bhyve</tt> as non-root.</p>
-      </li><li>
-	<p>Add filters for popular VM file formats (VMDK, VHD,
-	  QCOW2).</p>
-      </li><li>
-	<p>Implement an abstraction layer for video (no X11 or SDL in
-	  base system).</p>
-      </li><li>
-	<p>Suspend/resume support.</p>
-      </li><li>
-	<p>Live migration.</p>
-      </li><li>
-	<p>Nested VT-x support (<tt>bhyve</tt> in <tt>bhyve</tt>).</p>
-      </li><li>
-	<p>Support for other architectures (ARM, MIPS, PPC).</p>
-      </li></ol><hr /><h2><a name="Clang,-llvm,-lldb,-compiler-rt-and-libc++-Updated-to-3.7.0" href="#Clang,-llvm,-lldb,-compiler-rt-and-libc++-Updated-to-3.7.0" id="Clang,-llvm,-lldb,-compiler-rt-and-libc++-Updated-to-3.7.0">Clang, llvm, lldb, compiler-rt and libc++ Updated to 3.7.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html" title="http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html">LLVM 3.7.0 Release Notes</a></td><td>
-	    URL: <a href="http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html" title="LLVM 3.7.0 Release Notes">http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html</a></td></tr><tr><td><a href="http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html" title="http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html">Clang 3.7.0 Release Notes</a></td><td>
-	    URL: <a href="http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html" title="Clang 3.7.0 Release Notes">http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html</a></td></tr><tr><td><a href="https://bugs.freebsd.org/201377" title="https://bugs.freebsd.org/201377">PR 201377 Ports exp-run</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/201377" title="PR 201377 Ports exp-run">https://bugs.freebsd.org/201377</a></td></tr></table><p>
-	Contact: 
-	  Dimitry
-	  Andric
-	 &lt;<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Roman
-	  Divacky
-	 &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Davide
-	  Italiano
-	 &lt;<a href="mailto:davide@FreeBSD.org">davide@FreeBSD.org</a>&gt;
-	</p>
-      <p>We have updated <tt>clang</tt>, <tt>llvm</tt>, <tt>lldb</tt>,
-	<tt>compiler-rt</tt>, and <tt>libc++</tt> in base to the 3.7.0
-	release.  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, Ed Maste is working
-	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
-	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 introduce for the usual upgrade
-	scenarios.</p>
-
-      <p>Thanks to Ed Maste and Andrew Turner for their help with this
-	import, and thanks to Antoine Brodin for several ports
-	exp-runs.</p>
-
-      <p>During the first ports exp-run, some major problems were
-	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 the exp-run.</p>
-    <h3>Open tasks:</h3><ol><li>
-	Commit ports fixes for dependencies of PR 201377.
-      </li><li>
-	Test and report issues with the new tool chain.
-      </li></ol><hr /><h2><a name="DTrace-and-TCP" href="#DTrace-and-TCP" id="DTrace-and-TCP">DTrace and TCP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/287759" title="https://svnweb.freebsd.org/changeset/base/287759">Commit adding trace points replacing TCPDEBUG</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/287759" title="Commit adding trace points replacing TCPDEBUG">https://svnweb.freebsd.org/changeset/base/287759</a></td></tr></table><p>
-	Contact: 
-	  George
-	  Neville-Neil
-	 &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	</p>
-      <p>With the advent of DTrace we are able to replace many of
-	the internal kernel debugging options, such as TCPDEBUG, with
-	statically defined tracepoints (SDTs).  Tracepoints have now
-	been added to the system that replicate the functionality of
-	the TCPDEBUG kernel option.  No new kernel options need to be
-	added &#8212; they are standard with any kernel that has
-	DTrace, which is included in the default GENERIC kernels in
-	10.X and HEAD.</p>
-    <p>This project was sponsored by Limelight Networks.</p><hr /><h2><a name="FreeBSD-on-the-Acer-C720-Chromebook" href="#FreeBSD-on-the-Acer-C720-Chromebook" id="FreeBSD-on-the-Acer-C720-Chromebook">FreeBSD on the Acer C720 Chromebook</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://blog.grem.de/pages/c720.html" title="http://blog.grem.de/pages/c720.html">Blog post on how to get things working</a></td><td>
-	    URL: <a href="http://blog.grem.de/pages/c720.html" title="Blog post on how to get things working">http://blog.grem.de/pages/c720.html</a></td></tr><tr><td><a href="http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html" title="http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html">Blog post with links to commits in HEAD</a></td><td>
-	    URL: <a href="http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html" title="Blog post with links to commits in HEAD">http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html</a></td></tr><tr><td><a href="http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html" title="http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html">Backported patch for 10.2-RELEASE</a></td><td>
-	    URL: <a href="http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html" title="Backported patch for 10.2-RELEASE">http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html</a></td></tr></table><p>
-	Contact: 
-	  Michael
-	  Gmelin
-	 &lt;<a href="mailto:freebsd@grem.de">freebsd@grem.de</a>&gt;
-	</p>
-      <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 coding in general.  The machine is fully functional,
-	meaning that 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>
-
-      <p>This quarter, this project extended previous work on the
-	boot process and keyboard driver as well as the
-	<tt>smbus(4)</tt> driver.  It added three new drivers:
-	<tt>ig4(4)</tt> for the I2C bus, <tt>cyapa(4)</tt> for the
-	trackpad, and <tt>isl(4)</tt>, for the ambient light sensor.</p>
-
-      <p>Much of the development was originally done in late 2014.
-	Since then, the patches have been massively improved and
-	merged into HEAD, so that all relevant devices work without
-	manual patching.</p>
-
-      <p>For those who are unable to run HEAD, there is a
-	backported patch to 10.2-RELEASE.</p>
-
-      <p>Thanks to everyone who helped in the process.  I couldn't
-	have done it without you (you know who you are).</p>
-    <hr /><h2><a name="High-Availability-Clustering-in-CTL" href="#High-Availability-Clustering-in-CTL" id="High-Availability-Clustering-in-CTL">High Availability Clustering in CTL</a></h2><p>
-	Contact: 
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>CAM Target Layer (CTL), when originally developed by
-	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, fixed, and
-	improved.</p>
-
-      <p>This code supports dual-node HA with Asynchronous LUN Unit
-	Access (ALUA) in four modes:</p>
-
-      <ul>
-	<li>Active/Unavailable without interlink between nodes, where
-	  the secondary node can report nothing except its
-	  presence.</li>
-
-	<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 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 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, and so on.</p>
-
-      <p>The code is committed to FreeBSD head and was recently merged to
-	the stable/10 branch.</p>
-    <p>This project was sponsored by iXsystems, Inc..</p><hr /><h2><a name="Multipath-TCP-for-FreeBSD" href="#Multipath-TCP-for-FreeBSD" id="Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="http://caia.swin.edu.au/urp/newtcp/mptcp/">MPTCP for FreeBSD Project Website</a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="MPTCP for FreeBSD Project Website">http://caia.swin.edu.au/urp/newtcp/mptcp/</a></td></tr><tr><td><a href="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/" title="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/">MPTCP for FreeBSD Source Repository</a></td><td>
-	    URL: <a href="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/" title="MPTCP for FreeBSD Source Repository">https://bitbucket.org/nw-swin/caia-mptcp-freebsd/</a></td></tr></table><p>
-	Contact: 
-	  Nigel
-	  Williams
-	 &lt;<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>&gt;
-	</p>
-      <p>Multipath TCP (MPTCP) is an extension to TCP that allows
-	for the use of multiple network interfaces on a standard TCP
-	session.  The addition of new addresses and scheduling of data
-	across them occurs transparently from the perspective of the
-	TCP application.</p>
-
-      <p>The goal of this project is to deliver an MPTCP kernel
-	patch that interoperates with the reference MPTCP
-	implementation, along with additional enhancements to aid
-	network research.</p>
-
-      <p>The v0.5 patch was released, which is the first patch
-	of the re-written implementation.  We are in the process of
-	documenting the new design and addressing some feedback as
-	provided from the community.</p>
-
-      <p>Work has commenced on improved input handling, as the current
-	method of receiving and reassembling segments has been the
-	cause of some instability and stalls during connection
-	shutdown.  This will involve re-using the subflow receive
-	buffers and an upcall to enqueue a MP-layer reassembly task
-	without the need to take a lock on the MP control block.  The
-	improvements should also allow bypassing <tt>mptcp_usrreq</tt>
-	for standard TCP connections.</p>
-
-      <p>The MPTCP commit history was synchronized with
-	hg-beta.FreeBSD.org, and we have made the repository available on
-	BitBucket (see links).  Future patch releases will be tagged
-	there.  The tree is now merged with FreeBSD head weekly.  An
-	updated v0.51 patch is ready for release.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Release the v0.51 patch.</p>
-      </li><li>
-	<p>Populate documentation and the issue tracker on the
-	  BitBucket repository.</p>
-      </li><li>
-	<p>Improvements to receive-side code before further
-	  testing.</p>
-      </li><li>
-	<p>Prepare a technical report detailing the design of the
-	  current patch.</p>
-      </li></ol><hr /><h2><a name="Porting-bhyve-to-ARM-based-Platforms" href="#Porting-bhyve-to-ARM-based-Platforms" id="Porting-bhyve-to-ARM-based-Platforms">Porting bhyve to ARM-based Platforms</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm" title="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm">Project Wiki page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm" title="Project Wiki page">https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm</a></td></tr></table><p>
-	Contact: 
-	  Mihai
-	  Carabas
-	 &lt;<a href="mailto:mihai@FreeBSD.org">mihai@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Peter
-	  Grehan
-	 &lt;<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>&gt;
-	</p>
-      <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 FreeBSD guest up to the point of initializing
-	interrupts.  There is still work to be 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>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Virtualize interrupts and timer.</p>
-      </li><li>
-	<p>Port to a real hardware platform.</p>
-      </li><li>
-	<p>Create SMP support for bhyve-on-arm.</p>
-      </li><li>
-	<p>Port to ARMv8.</p>
-      </li></ol><hr /><h2><a name="Root-Remount" href="#Root-Remount" id="Root-Remount">Root Remount</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D3693" title="https://reviews.freebsd.org/D3693">Userland code review</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D3693" title="Userland code review">https://reviews.freebsd.org/D3693</a></td></tr></table><p>
-	Contact: 
-	  Edward Tomasz
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>A feature long missing from FreeBSD 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, this functionality is known as
-	pivot_root.  The reroot project aims to provide similar
-	functionality in a different, slightly more user-friendly, way.
-	Simply put, from the user's 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 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 is planned be included
-	in FreeBSD 10.3.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Graphics" title="https://wiki.FreeBSD.org/Graphics">Graphics stack roadmap and supported hardware matrix</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.FreeBSD.org/Graphics</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/graphics/" title="http://blogs.freebsdish.org/graphics/">Graphics stack team blog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/graphics/" title="Graphics stack team blog">http://blogs.freebsdish.org/graphics/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-graphics" title="https://github.com/freebsd/freebsd-ports-graphics">Ports development tree on GitHub</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-graphics" title="Ports development tree on GitHub">https://github.com/freebsd/freebsd-ports-graphics</a></td></tr></table><p>
-	Contact: 
-	  FreeBSD Graphics team
-	 &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	</p>
-      <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.  Dual version support was removed.
-	There is only one Mesa version for all supported FreeBSD
-	versions.  The <tt>libosmesa</tt> port, which provided
-	the off-screen version of
-	Mesa,  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:
-	<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>
-
-      <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 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 in the i915 update
-	article (see links).  At this stage, we can only accept
-	patches, though &#8212; we will not be able to provide
-	support.</p>
-
-      <p>We attended two conferences: XDC 2015 in Toronto and
-	EuroBSDcon 2015 in Stockholm.  Reports will be posted on the
-	blog.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>See the Graphics wiki page for up-to-date information.</p>
-      </li></ol><hr /><h2><a name="The-nosh-Project" href="#The-nosh-Project" id="The-nosh-Project">The nosh Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html">Introduction and blurb</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html" title="Introduction and blurb">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html">FreeBSD binary packages</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html" title="FreeBSD binary packages">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html">Installation How-To</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html" title="Installation How-To">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html">Roadmap</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html" title="Roadmap">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html">Commands</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html" title="Commands">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html">A slightly outdated nosh Guide</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html" title="A slightly outdated nosh Guide">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html</a></td></tr></table><p>
-	Contact: 
-	  Jonathan
-	  de Boyne Pollard
-	 &lt;<a href="mailto:J.deBoynePollard-newsgroups@NTLWorld.COM">J.deBoynePollard-newsgroups@NTLWorld.COM</a>&gt;
-	</p>
-      <p>The nosh project is a suite of system-level utilities for
-	initializing, running, and shutting down BSD systems, and for
-	managing daemons, terminals, and logging.  It supersedes BSD
-	<tt>init</tt> and the NetBSD <tt>rc.d</tt> system, drawing
-	inspiration from Solaris SMF for named milestones,
-	daemontools-encore for service control/status mechanisms,
-	UCSPI, and IBM AIX for separated service and system
-	management.  It comprises a range of compatibility mechanisms,
-	including shims for familiar commands from other systems, and
-	an automatic import mechanism that takes existing
-	configuration data from <tt>/etc/fstab</tt>,
-	<tt>/etc/rc.conf{,.local}</tt>, <tt>/etc/ttys</tt>, and
-	elsewhere, applying them to its native service definitions and
-	creating additional native services.  It is portable
-	(including to Linux) and composable, it provides a migration
-	path from the world of systemd Linux, and it does not require new
-	kernel APIs.  It provides clean service environments,
-	orderings and dependencies between services, parallelized
-	startup and shutdown (including <tt>fsck</tt>), strictly
-	size-capped and autorotated logging, the service manager as a
-	"subreaper", and uses <tt>kevent(2)</tt> for
-	event-driven parallelism.</p>
-
-      <p>The past few months have seen a growth in the import
-	mechanism, with full import of <tt>/etc/fstab</tt> and
-	<tt>/etc/ttys</tt> available in version 1.18 in July, and
-	importing PC-BSD Warden and FreeBSD�9 jails, and full import
-	of <tt>gbde</tt> and <tt>geli</tt> mount/unmount mechanisms in
-	version 1.21 in October.  It has also gained the ability to
-	automatically re-generate <tt>host.conf</tt> and
-	<tt>sysctl.conf</tt> whenever their source files change.</p>
-
-      <p>Other developments in the past few months include fully
-	independent shutdown support, no longer relying upon an
-	externally provided shutdown command from another toolset, and
-	a full suite of binary packages.  As of version 1.20, it
-	became possible to have a fully-<tt>nosh</tt>-managed system,
-	on both FreeBSD and Linux, using just precompiled binary
-	packages.</p>
-
-      <p>The biggest task remaining is one that was set a while ago:
-	the creation of enough native service bundles and ancillary
-	utilities to entirely supplant the <tt>rc.d</tt> system.  A
-	lot of this has been achieved, with the original target list
-	of 157 items now down to just 39 remaining.  These are the
-	tricky ones, of course, where help is most needed.
-      </p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>There are still a few rc scripts left that should be easy
-	  to convert, such as <tt>/etc/rc.d/gptboot</tt> and
-	  <tt>/etc/rc.d/growfs</tt> as oneshot services,
-	  <tt>/etc/rc.d/routing</tt>, and
-	  <tt>/etc/rc.d/kldxref</tt>.</p>
-      </li><li>
-	<p>FreeBSD's <tt>/etc/rc.d/bluetooth</tt> is over 360 lines long.
-	  In 2011, Iain Hibbert wrote a "simpler" <tt>bluetooth</tt>
-	  for NetBSD.  This can perhaps be used as a simpler basis for
-	  a <tt>nosh</tt> translation.</p>
-      </li><li>
-	<p>Add kernel support for passing a <tt>-b</tt> option to
-	  pid 1, and support for a <tt>boot_bare</tt> variable in the loader,
-	  to allow "emergency" (where even no shell dotfiles
-	  are loaded) and "rescue" mode bootstraps, akin to
-	  Linux.  (History: The <tt>-b</tt> mechanism and idea date
-	  back to version 2.57d of Miquel van Smoorenburg's System 5
-	  init clone, dated 1995-12-03, and was already known as
-	  "emergency boot" by 1997.)</p>
-      </li><li>
-	<p>Add support to FreeBSD's <tt>fsck(8)</tt> for outputting
-	  machine-readable progress reports to a designated file
-	  descriptor, so that <tt>nosh</tt> can provide progress bars
-	  for multiple <tt>fsck</tt>s running in parallel.
-	  <tt>nosh</tt> already provides this functionality on Linux,
-	  where <tt>fsck(8)</tt> does provide machine-readable
-	  output.</p>
-      </li><li>
-	<p>Identify when the configuration import system needs to be
-	  triggered, such as when <tt>bsdconfig</tt> alters
-	  configuration files, and create the necessary hooks to
-	  import external configuration changes into nosh.</p>
-      </li><li>
-	<p>Investigate how FreeBSD/PC-BSD could be improved by taking
-	  advantage of some available <tt>nosh</tt> package
-	  mechanisms.</p>
-      </li></ol><hr /><h2><a name="UEFI-Boot-and-Framebuffer-Support" href="#UEFI-Boot-and-Framebuffer-Support" id="UEFI-Boot-and-Framebuffer-Support">UEFI Boot and Framebuffer Support</a></h2><p>
-	Contact: 
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	<br />
-	Contact: 
-	  Marcel
-	  Moolenaar
-	 &lt;<a href="mailto:marcel@freebsd.org">marcel@freebsd.org</a>&gt;
-	</p>
-      <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
-	<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 number of recent Apple MacBook Pros and other
-	Macs.</p>
-    <h3>Open tasks:</h3><ol><li>Test FreeBSD head and FreeBSD-STABLE snapshots on
-	a variety of UEFI implementations.</li></ol><hr /><h2><a name="ZFS-Code-Sync-with-Latest-Illumos" href="#ZFS-Code-Sync-with-Latest-Illumos" id="ZFS-Code-Sync-with-Latest-Illumos">ZFS Code Sync with Latest Illumos</a></h2><p>
-	Contact: 
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ZFS codebase received a significant batch of merges, and
-	is now in sync with the latest Illumos.  Among other things, this
-	update includes:</p>
-
-      <ul>
-	<li>LZ4 is now the default compression algorithm.</li>
-
-	<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 checksumming in send/receive stream.</li>
-
-	<li>Reduced import time for pools with many datasets.</li>
-
-	<li>Reworked and simplified predictive prefetcher.</li>
-      </ul>
-
-      <p>The code is committed to FreeBSD head and was recently merged to
-	the stable/10 branch.
-      </p>
-    <hr /><h2><a name="ZFS-Support-for-UEFI-Boot/Loader" href="#ZFS-Support-for-UEFI-Boot/Loader" id="ZFS-Support-for-UEFI-Boot/Loader">ZFS Support for UEFI Boot/Loader</a></h2><p>
-	Contact: 
-	  Eric
-	  McCorkle
-	 &lt;<a href="mailto:eric@metricspace.net">eric@metricspace.net</a>&gt;
-	</p>
-      <p>UEFI-enabled <tt>boot1.efi</tt> and <tt>loader.efi</tt> have
-	been modified to support loading and booting from a ZFS
-	filesystem, as described in the previous report.  The
-	ZFS-enabled <tt>loader.efi</tt> can be treated as a
-	chainloader when using ZFS-enabled GRUB.</p>
-
-      <p>During this quarter, several successful tests have been
-	reported on simple ZFS setups, using both <tt>boot1.efi</tt>
-	with <tt>loader.efi</tt> as well as GRUB and
-	<tt>loader.efi</tt>.</p>
-
-      <p>Successful tests have been reported for UFS with the
-	patched <tt>boot1.efi</tt> and <tt>loader.efi</tt> as well.
-      </p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Test reports are needed for more complex ZFS setups,
-	  such as with log/l2arc vdevs, mirroring, striping, and
-	  raidz.</p>
-      </li><li>
-	<p>Pending successful reports, the patch needs to be
-	  reviewed and committed.</p>
-      </li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Adding-PCIe-Hot-plug-Support" href="#Adding-PCIe-Hot-plug-Support" id="Adding-PCIe-Hot-plug-Support">Adding PCIe Hot-plug Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug">PCIe Hot-plug Perforce Branch</a></td><td>
-	    URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug" title="PCIe Hot-plug Perforce Branch">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/changeset/base/r281874" title="https://svnweb.FreeBSD.org/changeset/base/r281874">Commit adding bridge save/restore</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/changeset/base/r281874" title="Commit adding bridge save/restore">https://svnweb.FreeBSD.org/changeset/base/r281874</a></td></tr><tr><td><a href="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp" title="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp">Github branch with patches</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp" title="Github branch with patches">https://github.com/FreeBSDFoundation/freebsd/tree/pciehp</a></td></tr></table><p>
-	Contact: 
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p>
-      <p>PCI Express (PCIe) hot-plug is used on both laptops and
-	servers to allow peripheral devices to be added or removed
-	while the system is running.  Laptops commonly include
-	hot-pluggable PCIe as either an ExpressCard slot or a
-	Thunderbolt interface.  ExpressCard has built-in USB support
-	that is already supported by FreeBSD, but ExpressCard PCIe
-	devices like Gigabit Ethernet adapters and eSATA cards are
-	only supported when they are present at boot, and their
-	removal may cause FreeBSD to crash.</p>
-
-      <p>The goal of this project is to allow these devices to be
-	inserted and removed while FreeBSD is running.  This work will
-	provide the basic infrastructure to support adding and
-	removing devices, though it is expected that additional work
-	will be needed to update individual drivers to support
-	hot-plug.</p>
-
-      <p>Current testing is focused on getting a simple UART device
-	functional.  Basic hot swap is currently functional.</p>
-
-      <p>A set of the patches for the work done in this project is
-	now available on github.com.
-      </p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Get suspend/resume functional by saving and restoring the
-	  necessary registers.  This should be addressed by
-	  r281874.</p>
-      </li><li>
-	<p>Make sure that upon suspend, devices are removed so that we
-	  are not fooled if they are replaced with different devices
-	  while the machine is suspended.</p>
-      </li><li>
-	<p>Improve how state transitions are handled, possibly by
-	  using a proper state machine.</p>
-      </li></ol><hr /><h2><a name="Cavium-LiquidIO-Smart-NIC-Driver" href="#Cavium-LiquidIO-Smart-NIC-Driver" id="Cavium-LiquidIO-Smart-NIC-Driver">Cavium LiquidIO Smart NIC Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html" title="http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html">LiquidIO product page</a></td><td>
-	    URL: <a href="http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html" title="LiquidIO product page">http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html</a></td></tr></table><p>
-	Contact: 
-	  Stanislaw
-	  Kardach
-	 &lt;<a href="mailto:kda@semihalf.com">kda@semihalf.com</a>&gt;
-	<br />
-	Contact: 
-	  Zyta
-	  Racia
-	 &lt;<a href="mailto:zr@semihalf.com">zr@semihalf.com</a>&gt;
-	</p>
-      <p>This project aims to add support for the LiquidIO family
-	of high-performance programmable accelerator 10/40-gigabit
-	Ethernet network adapters.  The currently developed kernel
-	driver supports CN6640- and CN6880-based PCIe cards, enabling
-	these features:</p>
-
-      <ul>
-	<li>A CNNIC API for controlling/interacting with the smart NIC
-	  from user and kernel space including:
-	  <ul>
-	    <li>Handling multiple concurrent applications running on
-	      the same device</li>
-
-	    <li>A request/reply mechanism for (a)synchronous
-	      ordered/unordered communication</li>
-
-	    <li>Remote memory operations</li>
-
-	    <li>Device shutdown/reset</li>
-	  </ul>
-	</li>
-
-	<li>A basic NIC module utilizing the CNNIC API and a
-	  Cavium-provided NIC firmware.  This module provides:
-	  <ul>
-	    <li>Single/multi-queue TX</li>
-
-	    <li>Hardware TCP/UDP checksum offloading</li>
-
-	    <li>Large Receive Offload</li>
-
-	    <li>Promiscous mode</li>
-	  </ul>
-	</li>
-
-	<li>Sysctl-based device statistics and configuration view</li>
-
-	<li>Custom firmware loading via user-built modules and
-	  FreeBSD's <tt>firmware(9)</tt> mechanism.</li>
-      </ul>
-
-      <p>The project is currently being developed in house and is
-	being prepared for upstream.  We plan on making it
-	available in FreeBSD 11.</p>
-    <p>This project was sponsored by Cavium, and Semihalf.</p><h3>Open tasks:</h3><ol><li>Upstream the code to FreeBSD head.</li></ol><hr /><h2><a name="CloudABI:-Pure-Capabilities-Runtime-Environment" href="#CloudABI:-Pure-Capabilities-Runtime-Environment" id="CloudABI:-Pure-Capabilities-Runtime-Environment">CloudABI: Pure Capabilities Runtime Environment</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/NuxiNL/cloudlibc" title="https://github.com/NuxiNL/cloudlibc">CloudABI project page</a></td><td>
-	    URL: <a href="https://github.com/NuxiNL/cloudlibc" title="CloudABI project page">https://github.com/NuxiNL/cloudlibc</a></td></tr><tr><td><a href="https://github.com/NuxiNL/cloudabi-ports" title="https://github.com/NuxiNL/cloudabi-ports">CloudABI Ports Collection</a></td><td>
-	    URL: <a href="https://github.com/NuxiNL/cloudabi-ports" title="CloudABI Ports Collection">https://github.com/NuxiNL/cloudabi-ports</a></td></tr><tr><td><a href="https://www.youtube.com/watch?v=LTHSZGVvLw4" title="https://www.youtube.com/watch?v=LTHSZGVvLw4">CloudABI presentation at FrOSCon</a></td><td>
-	    URL: <a href="https://www.youtube.com/watch?v=LTHSZGVvLw4" title="CloudABI presentation at FrOSCon">https://www.youtube.com/watch?v=LTHSZGVvLw4</a></td></tr></table><p>
-	Contact: 
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p>CloudABI is a POSIX-like runtime environment that uses
-	Capsicum as its sole access control mechanism.  CloudABI
-	allows you to develop software that is better hardened against
-	security vulnerabilities, is easier to test, and is easier to
-	migrate across systems.</p>
-
-      <p>As of August, all of the kernel modifications that are needed
-	to run CloudABI programs have been integrated into FreeBSD head.
-	After loading the <tt>cloudabi64</tt> kernel module, you can
-	either run CloudABI programs directly from the shell or by
-	using the <tt>cloudabi-run</tt> tool
-	(<tt>sysutils/cloudabi-utils</tt>).  <tt>cloudabi-run</tt>
-	allows you to inject sockets, files, and directories into the
-	launched program in a more structured way.</p>
-
-      <p>In the meantime, work has started on developing a Ports
-	Collection that contains cross-compiled utilities and
-	libraries for CloudABI. The intent is that this framework
-	generates native packages for a number of operating systems,
-	making it possible to develop CloudABI applications on any
-	operating system, regardless of whether that operating system
-	actually supports CloudABI.</p>
-
-      <p>If you are interested in CloudABI, be sure to go to the
-	project page on GitHub, watch recordings of talks at
-	conferences, or wait for the upcoming edition of the FreeBSD
-	Journal, which will feature an article on CloudABI.</p>
-    <p>This project was sponsored by Nuxi, the Netherlands.</p><h3>Open tasks:</h3><ol><li>
-	<p>CloudABI is currently only available for amd64.  It would
-	  make sense to port CloudABI to additional architectures like
-	  aarch64.</p>
-      </li><li>
-	<p>Support for CloudABI has only been integrated into FreeBSD.
-	  If we manage to upstream support for CloudABI into other
-	  operating systems, it should be possible to run the same
-	  binary on multiple operating systems without
-	  recompilation.</p>
-      </li><li>
-	<p>The CloudABI Ports Collection currently has only 60
-	  packages.  Although these packages already the building blocks of
-	  some interesting software, we are always interested in
-	  expanding.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-Xen" href="#FreeBSD-Xen" id="FreeBSD-Xen">FreeBSD Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="http://wiki.xen.org/wiki/FreeBSD_PVH">FreeBSD PVH DomU wiki page</a></td><td>
-	    URL: <a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="FreeBSD PVH DomU wiki page">http://wiki.xen.org/wiki/FreeBSD_PVH</a></td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="http://wiki.xen.org/wiki/FreeBSD_Dom0">FreeBSD PVH Dom0 wiki page</a></td><td>
-	    URL: <a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="FreeBSD PVH Dom0 wiki page">http://wiki.xen.org/wiki/FreeBSD_Dom0</a></td></tr><tr><td><a href="http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html" title="http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html">Porting FreeBSD as a Xen ARM guest</a></td><td>
-	    URL: <a href="http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html" title="Porting FreeBSD as a Xen ARM guest">http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html</a></td></tr></table><p>
-	Contact: 
-	  Roger
-	  Pau Monn�
-	 &lt;<a href="mailto:royger@FreeBSD.org">royger@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Julien
-	  Grall
-	 &lt;<a href="mailto:julien.grall@citrix.com">julien.grall@citrix.com</a>&gt;
-	</p>
-      <p>Xen is a hypervisor using a microkernel design, providing
-	services that allow multiple computer operating systems to
-	execute on the same computer hardware concurrently.  Xen
-	support for FreeBSD on x86 as a guest was introduced in version 8
-	and ARM support is currently being worked on.  Support for
-	running FreeBSD as an amd64 Xen host (Dom0) is available in
-	HEAD.</p>
-
-      <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 is done, work will continue
-	adding new features to both FreeBSD and Xen to have feature
-	parity with traditional PV guests/hosts.</p>
-
-      <p>Apart from this, work is ongoing to import a new netfront
-	from Linux in order to support new features, like split event
-	channel and multiple queue support.</p>
-
-      <p>On the ARM front, this quarter's work focused on getting
-	FreeBSD/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>
-    <p>This project was sponsored by Citrix Systems R&amp;D.</p><h3>Open tasks:</h3><ol><li>
-	<p>Generalize the event channel code so it can be used on
-	  ARM.</p>
-      </li><li>
-	<p>Improve backend (netback, blkback) performance.</p>
-      </li><li>
-	<p>Work with upstream Xen to improve PVH and make it
-	  stable.</p>
-      </li><li>
-	<p>Improve the generic bounce buffer code for unmapped bios in
-	  order to support the alignment requirements of the
-	  blkfront driver.</p>
-      </li></ol><hr /><h2><a name="ioat(4)-Driver-Import" href="#ioat(4)-Driver-Import" id="ioat(4)-Driver-Import">ioat(4) Driver Import</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology" title="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology">Wikipedia article on IOAT</a></td><td>
-	    URL: <a href="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology" title="Wikipedia article on IOAT">https://en.wikipedia.org/wiki/I/O_Acceleration_Technology</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=r287117" title="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=r287117">Commit importing ioat(4)</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=r287117" title="Commit importing ioat(4)">https://svnweb.FreeBSD.org/base?view=revision&amp;revision=r287117</a></td></tr></table><p>
-	Contact: 
-	  Jim
-	  Harris
-	 &lt;<a href="mailto:jimharris@FreeBSD.org">jimharris@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Conrad
-	  Meyer
-	 &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	</p>
-      <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>
-
-      <p>These devices are DMA offload engines, which can accelerate
-	some I/O-heavy applications by offloading memory copies from
-	the main CPU to the I/OAT unit.  This acceleration is not
-	transparent; applications must be adapted to take advantage of
-	the hardware.</p>
-
-      <p>Some I/OAT models support more advanced copying modes, such as 
-	XOR; these modes are not yet supported in the <tt>ioat(4)</tt>
-	driver.</p>
-    <p>This project was sponsored by Intel Corporation, and EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li>
-	<p>Further testing, especially on a range of device models
-	  other than BDXDE (looking for volunteers here).</p>
-      </li><li>
-	<p>Support for the more advanced copy modes.</p>
-      </li></ol><hr /><h2><a name="IPsec-Upgrades" href="#IPsec-Upgrades" id="IPsec-Upgrades">IPsec Upgrades</a></h2><p>
-	Contact: 
-	  George
-	  Neville-Neil
-	 &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  John-Mark
-	  Gurney
-	 &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Ermal
-	  Lu�i
-	 &lt;<a href="mailto:eri@FreeBSD.org">eri@FreeBSD.org</a>&gt;
-	</p>
-      <p>IPsec is now enabled by default in the GENERIC kernel
-	configuration, and work is proceeding to speed things up in
-	various ways.  The latest changes are the addition, by
-	John-Mark Gurney, Ermal Lu�i, and George V. Neville-Neil, of AES modes both in hardware
-	and in software.  Part of this work also includes more
-	benchmarks undertaken using Conductor in the netperf project.
-	Results have been reported at BSDCan and vBSDcon with more to
-	come at EuroBSDcon and BSDCon Brasil.</p>
-    <p>This project was sponsored by Netgate, and The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Performance improvements and other tweaks are ongoing.</p>
-      </li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Atomics" href="#Atomics" id="Atomics">Atomics</a></h2><p>
-	Contact: 
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Alan
-	  Cox
-	 &lt;<a href="mailto:alc@FreeBSD.org">alc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Bruce
-	  Evans
-	 &lt;<a href="mailto:bde@FreeBSD.org">bde@FreeBSD.org</a>&gt;
-	</p>
-      <p>Atomic operations serve two fundamental purposes.  First,
-	they are the building blocks for expressing synchronization
-	algorithms in a single, machine-independent way using
-	high-level languages.  In essense, atomics abstract the
-	different building blocks supported by the various
-	architectures on which FreeBSD runs, making it easier to develop
-	and reason about lock-less code by hiding hardware-level
-	details.</p>
-
-      <p>Atomics also provide the barrier operations that allow
-	software to control the effects on memory of out-of-order and
-	speculative execution in modern processors as well as
-	optimizations by compilers.  This capability is especially
-	important to multithreaded software, such as the FreeBSD kernel,
-	when running on systems where multiple processors communicate
-	through a shared main memory.</p>
-
-      <p>Each machine architecture defines a memory model, which
-	specifies the possible effects on memory of out-of-order and
-	speculative execution.  More precisely, it specifies the
-	extent to which the machine may visibly reorder memory
-	accesses to optimize performance.  Unfortunately,
-	there are almost as many models as architectures.  
-	Some architectures, for example IA32 or Sparcv9 TSO, are
-	relatively strongly ordered.  In contrast, others, like
-	PowerPC or ARM, are very relaxed.  In effect, atomics define a
-	very relaxed abstract memory model for FreeBSD's
-	machine-independent code that can be efficiently realized on
-	any of these architectures.</p>
-
-      <p>Most FreeBSD development and testing still happens on
-	x86 machines, which, when combined with x86's strongly ordered
-	memory model, leads to errors in the use of atomics,
-	specifically, barriers.  In other words, the code is not
-	properly written to FreeBSD's abstract memory model, but the
-	strong ordering of the x86 architecture hides this fact.  The
-	architectures impacted by the code that incorrectly uses
-	atomics are less popular or have limited availability, and the
-	resulting bugs from the misuse of atomics are hard to
-	diagnose.</p>
-
-      <p>The goal of this project is to audit and upgrade the usage of
-	lockless facilities, hopefully fixing bugs before they are
-	observed in the wild.</p>
-
-      <p>FreeBSD defines its own set of atomics operations, like many
-	other operating systems.  But unlike other operating systems,
-	FreeBSD models its atomics and barriers on the release
-	consistency model, which is also known as acquire/release
-	model.  This is the same model which is used by the C11 and
-	C++11 language standards as well as the new 64-bit ARM
-	architecture.  Despite having syntactical differences, C11 and
-	FreeBSD atomics share essentially the same semantics.
-	Consequently, ample tutorials about the C11 memory model and
-	algorithms expressed with C11 atomics can be trivially reused
-	under FreeBSD.</p>
-
-      <p>One facility of C11 that was missing from FreeBSD 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,
-	<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 <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>
-
-      <p>The only reordering in memory accesses which is allowed on
-	x86 is that loads may be reordered with older stores to
-	different locations.  This results from the use of store
-	buffers at the micro-architecural level.  So, to ensure
-	sequentially consistent behavior on x86, a store/load barrier
-	needs to be issued, which can be done with an MFENCE
-	instruction or by any locked read-modify-write operation.  The latter
-	approach is recommended by the optimization guides from Intel
-	and AMD.  It was noted that careful selection of the scratch
-	memory location, which is modified by the locked RMW
-	operation, can reduce the cost of the barrier by avoiding false
-	data dependencies.  The corresponding optimization was
-	committed in r284901.</p>
-
-      <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>
-
-      <p>Some examples of our preemptive fixes to the misuse of
-	atomics that would only become evident on weakly ordered
-	machines are:</p>
-
-      <ul>
-	<li>A very important lockless algorithm, used in both the
-	  kernel and libc, is the timekeeping functionality
-	  implemented in <tt>kern/kern_tc.c</tt> and the userspace
-	  <tt>__vdso_gettimeofday</tt>.  This algorithm relied on x86
-	  total store order (TSO) behavior.  It was fixed in r284178
-	  and r285286.</li>
-
-	<li>The <tt>kern/kern_intr.c</tt> lockless updates to the
-	  <tt>it_need</tt> indicator were corrected in r285607.</li>
-
-	<li>An issue with
-	  <tt>kern/subr_smp.c:smp_rendezvous_cpus()</tt> not
-	  guaranteeing the visibility of updates done on other CPUs to
-	  the caller was fixed in r285771.</li>
-
-	<li>The <tt>pthread_once()</tt> implementation was fixed to
-	  include missed barriers in r287556.</li>
-      </ul>
-    <p>This project was sponsored by The FreeBSD Foundation (Konstantin Belousov's work).</p><hr /><h2><a name="FreeBSD-on-Cavium-ThunderX-(arm64)" href="#FreeBSD-on-Cavium-ThunderX-(arm64)" id="FreeBSD-on-Cavium-ThunderX-(arm64)">FreeBSD on Cavium ThunderX (arm64)</a></h2><p>
-	Contact: 
-	  Dominik
-	  Ermel
-	 &lt;<a href="mailto:der@semihalf.com">der@semihalf.com</a>&gt;
-	<br />
-	Contact: 
-	  Wojciech
-	  Macek
-	 &lt;<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>&gt;
-	<br />
-	Contact: 
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	</p>
-      <p>Cavium&#8217;s ThunderX is a high-performance 64-bit ARMv8 CPU,
-	available in configurations with up to 48 cores per package.
-	ThunderX is the initial reference platform for the FreeBSD/arm64
-	porting effort.</p>
-
-      <p>Additional Semihalf-sponsored work on ThunderX support
-	brought brand new features such as:</p>
-
-      <ul>
-	<li> Multi-socket operation: FreeBSD now runs on a two-node
-	  ThunderX server board with a total of 96 CPU cores!</li>
-
-	<li>Virtual Networking Interface Card driver: The VNIC driver
-	  consists of 4 elements (BGX, MDIO, and Physical and Virtual
-	  Functions) and is the second driver in FreeBSD to utilize
-	  SR-IOV capabilities.  ThunderX is now able to use built-in
-	  networking interfaces at 1&#8211;40 Gbps.</li>
-      </ul>
-
-      <p>Moreover, previously introduced functionalities have been
-	improved and committed to HEAD.  This includes:</p>
-      <ul>
-	<li>PCIe drivers for both internal and external
-	  controllers</li>
-	<li>ITS (Interrupt Translation Services) fixes</li>
-	<li>Platform-specific changes for ThunderX</li>
-	<li>Various other fixes to the kernel (PCI, UMA, etc.)</li>
-      </ul>
-
-      <p>The remaining features are being reviewed and will be
-	integrated into HEAD soon.  However, the GENERIC kernel
-	already supports and runs on ThunderX.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, ARM Ltd., Cavium, and Semihalf.</p><h3>Open tasks:</h3><ol><li>
-	<p>Upstream the remaining features: 2-socket support, VNIC
-	  driver, and PCIe fixes</p>
-      </li></ol><hr /><h2><a name="FreeBSD-on-the-HiKey-ARMv8-Board" href="#FreeBSD-on-the-HiKey-ARMv8-Board" id="FreeBSD-on-the-HiKey-ARMv8-Board">FreeBSD on the HiKey ARMv8 Board</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64/HiKey" title="https://wiki.FreeBSD.org/arm64/HiKey">HiKey wiki entry</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/arm64/HiKey" title="HiKey wiki entry">https://wiki.FreeBSD.org/arm64/HiKey</a></td></tr><tr><td><a href="https://www.96boards.org/products/ce/hikey/" title="https://www.96boards.org/products/ce/hikey/">Hardware description</a></td><td>
-	    URL: <a href="https://www.96boards.org/products/ce/hikey/" title="Hardware description">https://www.96boards.org/products/ce/hikey/</a></td></tr></table><p>
-	Contact: 
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>The HiKey is a low-cost ARMv8 development board from the
-	Linaro 96boards initiative.  It contains a HiSilicon Kirin
-	6220 with eight ARMv8 cores and 1GB of ram.</p>
-
-      <p>FreeBSD has been ported to run on the HiKey with a minimal set
-	of drivers.  As of this report, FreeBSD supports the micro-SD
-	slot and 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 a usable state for people interested in testing FreeBSD
-	on ARMv8 hardware.</p>
-    <p>This project was sponsored by ABT Systems Ltd, and ARM Ltd.</p><h3>Open tasks:</h3><ol><li>
-	<p>A driver for SDIO and the onboard WiFi.</p>
-      </li><li>
-	<p>Fix the MMC driver to access the eMMC.</p>
-      </li><li>
-	<p>Support the USB in OTG mode.</p>
-      </li><li>
-	<p>Support a display via HDMI.</p>
-      </li><li>
-	<p>Add thermal management.</p>
-      </li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64" title="https://wiki.FreeBSD.org/arm64">FreeBSD arm64 wiki page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/arm64" title="FreeBSD arm64 wiki page">https://wiki.FreeBSD.org/arm64</a></td></tr></table><p>
-	Contact: 
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <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 implementing more functions as
-	needed.</p>
-
-      <p>Further work on SMP means that FreeBSD now boots on all 48
-	cores on the Cavium ThunderX platform.  This includes adding
-	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 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>
-    <p>This project was sponsored by The FreeBSD Foundation, and ABT Systems Ltd.</p><h3>Open tasks:</h3><ol><li>
-	<p>Port to more SoCs.</p>
-      </li></ol><hr /><h2><a name="FreeBSD/RISC-V-Port" href="#FreeBSD/RISC-V-Port" id="FreeBSD/RISC-V-Port">FreeBSD/RISC-V Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/riscv" title="https://wiki.freebsd.org/riscv">FreeBSD wiki RISC-V</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/riscv" title="FreeBSD wiki RISC-V">https://wiki.freebsd.org/riscv</a></td></tr><tr><td><a href="https://people.freebsd.org/~br/riscv-singleuser.txt" title="https://people.freebsd.org/~br/riscv-singleuser.txt">Single user boot log</a></td><td>
-	    URL: <a href="https://people.freebsd.org/~br/riscv-singleuser.txt" title="Single user boot log">https://people.freebsd.org/~br/riscv-singleuser.txt</a></td></tr></table><p>
-	Contact: 
-	  Ruslan
-	  Bukin
-	 &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Arun
-	  Thomas
-	 &lt;<a href="mailto:arun.thomas@baesystems.com">arun.thomas@baesystems.com</a>&gt;
-	<br />
-	Contact: 
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>RISC-V is an open source Instruction Set Architecture (ISA)
-	designed at UC Berkeley.  It is freely available for all uses
-	without requiring fees or license agreements.
-	The RISC-V team intends to provide freely available
-	BSD licensed CPU designs.</p>
-
-      <p>Ruslan Bukin (University of Cambridge) now has FreeBSD booting
-	to a single user shell on a RISC-V simulator.
-	The porting effort started only two months ago
-	and is very much a work in progress, requiring significant
-	refactoring and clean up before it reaches a committable
-	state.  Nonetheless, this is exceptional progress in a short
-	time.  The porting effort also identified a number of
-	proposed ISA improvements.</p>
-
-      <p>The port currently uses the GNU tool chain (GCC and
-	binutils), and runs on the Spike simulator.  Improved RISC-V
-	support in Clang/LLVM and related tools is highly desired.</p>
-    <p>This project was sponsored by DARPA, AFRL.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="mandoc-and-roff-Toolchain" href="#mandoc-and-roff-Toolchain" id="mandoc-and-roff-Toolchain">mandoc and roff Toolchain</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/n-t-roff/heirloom-doctools" title="https://github.com/n-t-roff/heirloom-doctools">Heirloom doctools</a></td><td>
-	    URL: <a href="https://github.com/n-t-roff/heirloom-doctools" title="Heirloom doctools">https://github.com/n-t-roff/heirloom-doctools</a></td></tr><tr><td><a href="http://mdocml.bsd.lv/" title="http://mdocml.bsd.lv/">mandoc</a></td><td>
-	    URL: <a href="http://mdocml.bsd.lv/" title="mandoc">http://mdocml.bsd.lv/</a></td></tr></table><p>
-	Contact: 
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>mandoc</tt> is a suite of tools for compiling
-	<tt>mdoc</tt>, the <tt>roff</tt> macro language of choice for
-	BSD manual pages.</p>
-
-      <p><tt>mandoc</tt> is the default renderer for manpages on
-	FreeBSD 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 <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 <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 <tt>soelim(1)</tt> utility has been replaced with a
-	BSD-licensed version which is good enough to work with all
-	available <tt>roff</tt> toolchains to ease the transition.
-	This version of the <tt>soelim(1)</tt> utility, originally
-	written solely for FreeBSD, is now part of the <tt>mandoc</tt>
-	tool suite.</p>
-
-      <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.</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 doctools
-	version.</p>
-
-      <p>Many <tt>roff</tt> fixes were made to documentation and man
-	pages, having been discovered while testing the new
-	toolchain.</p>
-    <hr /><h2><a name="pkg-1.6" href="#pkg-1.6" id="pkg-1.6">pkg 1.6</a></h2><p>
-	Contact: FreeBSD pkg Team &lt;<a href="mailto:pkg@FreeBSD.org">pkg@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>pkg</tt> 1.6.0 has been released.  Many changes have been
-	made since <tt>pkg</tt> 1.5:</p>
-
-      <ul>
-	<li>The dependency solver is greatly improved</li>
-
-	<li>Lots of fixes in the three-way merge code</li>
-
-	<li><tt>pkg add</tt> can now work without a version specified
-	  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 <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 the previous version), or removal</li>
-
-	<li><tt>@keywords</tt> 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
-	  <tt>pkg-comments</tt> of the matched packages</li>
-
-	<li>Lots of bug fixes and code cleanup</li>
-
-	<li>Improvements in cross-installation support</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<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>
-      </li><li>
-	<p>Investigate replacing <tt>openssl</tt> by
-	  <tt>mbedtls</tt>.</p>
-      </li></ol><hr /><h2><a name="sesutil(8)" href="#sesutil(8)" id="sesutil(8)">sesutil(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://en.wikipedia.org/wiki/SCSI_Enclosure_Services" title="https://en.wikipedia.org/wiki/SCSI_Enclosure_Services">Wikipedia: SCSI Enclosure Services (SES)</a></td><td>
-	    URL: <a href="https://en.wikipedia.org/wiki/SCSI_Enclosure_Services" title="Wikipedia: SCSI Enclosure Services (SES)">https://en.wikipedia.org/wiki/SCSI_Enclosure_Services</a></td></tr></table><p>
-	Contact: 
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:allanjude@FreeBSD.org">allanjude@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>sesutil(8)</tt> was originally created as a more
-	universal way to blink the "locate" LEDs on most
-	hot-swappable drive enclosures.</p>
-
-      <p>This work is based on the original SES tools created by
-	Matthew Jacob in 2000, which have been available in the
-	<tt>share/examples</tt> section of the source tree, but were
-	not built by default.</p>
-
-      <p>The new utility extends the original code with a number of
-	very useful features:</p>
-
-      <ul>
-	<li>Print a map of all objects connected to the SES
-	  controller</li>
-
-	<li>Map device names (<tt>/dev/da5</tt>) to SES slot
-	  number</li>
-
-	<li>Blink the Locate and/or Fault LED of a drive by its SES
-	  slot number or device name</li>
-
-	<li>Check the status of the entire SES controller</li>
-      </ul>
-    <p>This project was sponsored by Gandi, and ScaleEngine Inc..</p><h3>Open tasks:</h3><ol><li>
-	<p>Test <tt>sesutil(8)</tt> against more hardware.</p>
-      </li><li>
-	<p>Diagnose an issue where the locate command sometimes
-	  needs to be sent twice to activate the LED.</p>
-      </li><li>
-	<p>Add support for <tt>libxo</tt> output types.</p>
-      </li></ol><hr /><h2><a name="truss(1)" href="#truss(1)" id="truss(1)">truss(1)</a></h2><p>
-	Contact: 
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Bryan
-	  Drewery
-	 &lt;<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>&gt;
-	</p>
-      <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><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 version of
-	<tt>truss</tt>: knowing the correct number of arguments for
-	all system calls.</p>
-
-      <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>
-
-      <p>Support for decoding more arguments has been added in
-	the last quarter as well.
-      </p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Create a new <tt>libsysdecode</tt> library to hold shared
-	  code between <tt>truss(1)</tt> and <tt>kdump(1)</tt>.</p>
-      </li><li>
-	<p>Decode more system call arguments.</p>
-      </li><li>
-	<p>Add appropriate system call decoding specifications for
-	  <tt>freebsd32</tt> system calls.</p>
-      </li><li>
-	<p>Implement an ABI for 64-bit Linux binaries under
-	  FreeBSD/amd64.</p>
-      </li></ol><hr /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D3341" title="https://reviews.FreeBSD.org/D3341">Extend libkvm to support cross-debugging of vmcores</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D3341" title="Extend libkvm to support cross-debugging of vmcores">https://reviews.FreeBSD.org/D3341</a></td></tr></table><p>
-	Contact: 
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for following children after forks for FreeBSD was
-	implemented and merged upstream to GDB's master branch, and
-	was included in GDB 7.10.</p>
-
-      <p>Work has continued on porting <tt>kgdb</tt> to newer
-	<tt>gdb</tt>.  The amd64, i386, powerpc, powerpc64, and
-	sparc64 backends have all been ported and are now available
-	via a new <tt>KGDB</tt> option in the devel/gdb port.</p>
-
-      <p>The MD backends for libkvm have been rewritten to support
-	cross-debugging crashdumps, and the <tt>kgdb</tt> targets for
-	amd64 and i386 have been reworked to support cross-debugging.
-	Both i386 and amd64 kgdb binaries have been able to
-	cross-debug the other architecture's vmcores with these
-	changes.  This changeset for libkvm is not yet in the tree,
-	but is awaiting more testing.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Test the <tt>libkvm</tt> changes on platforms other than
-	  amd64, i386, and powerpc64.</p>
-      </li><li>
-	<p>Figure out why the powerpc <tt>kgdb</tt> targets are not
-	  able to unwind the stack past the initial frame.</p>
-      </li><li>
-	<p>Add support for more platforms (arm, mips, aarch64) to
-	  upstream <tt>gdb</tt> for both userland and
-	  <tt>kgdb</tt>.</p>
-      </li><li>
-	<p>Write a new 1:1-only thread target for FreeBSD that can be
-	  sent upstream.</p>
-      </li><li>
-	<p>Add support for debugging powerpc vector registers.</p>
-      </li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Bringing-GitLab-into-the-Ports-Collection" href="#Bringing-GitLab-into-the-Ports-Collection" id="Bringing-GitLab-into-the-Ports-Collection">Bringing GitLab into the Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468">PR for the new port</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468" title="PR for the new port">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468</a></td></tr><tr><td><a href="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md" title="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md">Installation guide</a></td><td>
-	    URL: <a href="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md" title="Installation guide">https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md</a></td></tr><tr><td><a href="https://github.com/gitlabhq/gitlabhq/" title="https://github.com/gitlabhq/gitlabhq/">GitLab Source Tree</a></td><td>
-	    URL: <a href="https://github.com/gitlabhq/gitlabhq/" title="GitLab Source Tree">https://github.com/gitlabhq/gitlabhq/</a></td></tr></table><p>
-	Contact: 
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:ports@toco-domains.de">ports@toco-domains.de</a>&gt;
-	<br />
-	Contact: 
-	  Michael
-	  Fausten
-	 &lt;<a href="mailto:ports@michael-fausten.de">ports@michael-fausten.de</a>&gt;
-	</p>
-      <p>GitLab is a web-based Git repository manager with many
-	features, used by more than 100.000 organizations, including
-	NASA and Alibaba.  It also is a very long-standing entry on
-	the "Wanted Ports" list on the FreeBSD Wiki.</p>
-
-      <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 Philip M. Gollucci is working on, there was
-	already a 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 &#8212; we nearly hit
-	100 &#8212; making progress takes some time.  In the meantime,
-	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>
-    <p>This project was sponsored by anyMOTION GRAPHICS GmbH, D�sseldorf, Germany.</p><h3>Open tasks:</h3><ol><li>
-	<p>Closing all the PRs of the dependencies</p>
-      </li><li>
-	<p>Committing the GitLab port itself</p>
-      </li><li>
-	<p>Updating the port to the latest version of the 8.x
-	  branch</p>
-      </li></ol><hr /><h2><a name="GNOME-on-FreeBSD" href="#GNOME-on-FreeBSD" id="GNOME-on-FreeBSD">GNOME on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome" title="http://www.FreeBSD.org/gnome">FreeBSD Gnome website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome" title="FreeBSD Gnome website">http://www.FreeBSD.org/gnome</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-gnome" title="https://github.com/freebsd/freebsd-ports-gnome">Devel repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-gnome" title="Devel repository">https://github.com/freebsd/freebsd-ports-gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD">Upstream build bot</a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="Upstream build bot">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html">USE_GNOME Porter's Handbook chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="USE_GNOME Porter's Handbook chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD GNOME Team maintains the GNOME, MATE, and CINNAMON
-	desktop environments and graphical user interfaces for FreeBSD.
-	GNOME 3 is part of the GNU Project.  MATE is a fork of the
-	GNOME 2 desktop.  CINNAMON is a desktop environment using
-	GNOME 3 technologies but with a GNOME 2 look and feel.</p>
-
-      <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'
-	<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
-	ports tree.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The FreeBSD GNOME website is stale.  Work is under way to improve
-	  it.</p>
-      </li><li>
-	<p>Please give feedback on and suggest improvements to the
-	  chapter in the Porter's Handbook on the <tt>USE_GNOME</tt>
-	  functionality.</p>
-      </li><li>
-	<p>Continue working on investigating the issues blocking
-	  GNOME 3.18.</p>
-      </li></ol><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE on FreeBSD website</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE on FreeBSD website">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://freebsd.kde.org/area51.php" title="https://freebsd.kde.org/area51.php">KDE ports staging area</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/area51.php" title="KDE ports staging area">https://freebsd.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/KDE" title="https://wiki.FreeBSD.org/KDE">KDE on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/KDE" title="KDE on FreeBSD wiki">https://wiki.FreeBSD.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="https://mail.kde.org/mailman/listinfo/kde-freebsd">KDE/FreeBSD mailing list</a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="KDE/FreeBSD mailing list">https://mail.kde.org/mailman/listinfo/kde-freebsd</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/plasma5" title="http://src.mouf.net/area51/log/branches/plasma5">Development repository for integrating KDE 5</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/plasma5" title="Development repository for integrating KDE 5">http://src.mouf.net/area51/log/branches/plasma5</a></td></tr></table><p>
-	Contact: KDE on FreeBSD team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>Overall, we have updated the following ports this
-	quarter:</p>
-
-      <ul>
-	<li>CMake 3.3.1 (r396266)</li>
-
-	<li>Qt 4.8.7 (r397043)</li>
-
-	<li>QtCreator 3.5.0 (r395935)</li>
-
-	<li>Fixed some dependencies, typos and plists in Qt5-ports
-	  (r396044-r396047), spotted by Ralf Nolden</li>
-      </ul>
-
-      <p>In our development repository, we have done the following
-	work:</p>
-
-      <ul>
-	<li>Updated PyQt-bindings for qt4 to 4.11.4 and added qt5
-	  bindings 5.5, contributed by Guido Falsi, and modified by
-	  Tobias Berner (area51)</li>
-
-	<li>Updated qt5 to 5.5.0.  Ralf Nolden has contributed a
-	  handful of useful new ports, for example
-	  <tt>lang/qt5-l10n</tt> (<tt>area51/qt-5.5</tt>)</li>
-
-	<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
-	  (<tt>area51/plasma5</tt>)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<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>
-      </li><li>
-	<p>Finalize the work on PyQt5.</p>
-      </li><li>
-	<p>Port <tt>qt5-webengine</tt>.  Qt-5.5 will probably be the
-	  last release shipping a <tt>www/webkit-qt5</tt> port.</p>
-      </li></ol><hr /><h2><a name="Node.js-Modules" href="#Node.js-Modules" id="Node.js-Modules">Node.js Modules</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.assembla.com/spaces/cozycloud/subversion/source" title="https://www.assembla.com/spaces/cozycloud/subversion/source">Node.js modules</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/cozycloud/subversion/source" title="Node.js modules">https://www.assembla.com/spaces/cozycloud/subversion/source</a></td></tr><tr><td><a href="https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html" title="https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html">Pre-draft documentation</a></td><td>
-	    URL: <a href="https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html" title="Pre-draft documentation">https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html</a></td></tr></table><p>
-	Contact: 
-	  Olivier
-	  Duchateau
-	 &lt;<a href="mailto:olivierd@FreeBSD.org">olivierd@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>Node.js</tt> is a platform built on Chrome's JavaScript
-	runtime 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 in the
-	<a href="http://npmjs.org/" shape="rect">npm package registry</a>.</p>
-
-      <p>Currently, the repository contains more than 100 new ports,
-	in particular:</p>
-
-      <ul>
-	<li>CoffeeScript (a programming language that transcompiles to
-	  JavaScript)</li>
-
-	<li>node-gyp (allows building Node.js addons, often written in
-	  C or C++)</li>
-
-	<li>Request (a simplified HTTP client)</li>
-      </ul>
-
-      <p>We have also written several helpers for the porting,
-	available in our experimental repository.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Bring in <tt>grunt.js</tt> (and modules), the JavaScript
-	  task runner.</p>
-      </li><li>
-	<p>Put more effort into support for <tt>node-gyp</tt> in the
-	  USES framework</p>
-      </li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">Ports Collection website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="Ports Collection website">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html">Contributing to the Ports Collection</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html" title="Contributing to the Ports Collection">https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">Port Monitoring service</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="Port Monitoring service">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html">Team Website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="Team Website">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/">Blog</a></td><td>
-	    URL: <a href="http://blogs.freebsdish.org/portmgr/" title="Blog">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/">Twitter feed</a></td><td>
-	    URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="Twitter feed">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr">Facebook page</a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="Facebook page">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383">Google+ page</a></td><td>
-	    URL: <a href="http://plus.google.com/communities/108335846196454338383" title="Google+ page">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact: 
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of Q3 the ports tree holds just over
-	25,000 ports, and the PR count is above 2,000.  The summer
-	period saw less activity on the ports tree than during the
-	previous quarter, with fewer than 7,000 commits performed by
-	120 active committers.  Unfortunately, the number of problem
-	reports closed also decreased significantly, with fewer than
-	1,500 problem reports fixed during Q3.</p>
-
-      <p>In Q3 several commit bits were taken in for safekeeping,
-	following an inactivity period of more than 18 months
-	(fluffy), or on committer's request (xmj, stefan, brix).  One
-	new developer was granted a ports commit bit
-	(Jason Unovitch <email>junovitch@FreeBSD.org</email>), and one returning committer
-	(Babak Farrokhi) had his commit bit reinstated.</p>
-
-      <p>On the management side, no changes were made to the
-	portmgr team during Q3.</p>
-
-      <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 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 changes included the addition of new options
-	helpers: <tt>opt_VARS</tt>, <tt>opt_VARS_OFF</tt>,
-	<tt>opt_IMPLIES</tt>, and <tt>opt_PREVENTS</tt>.  Some macros
-	were also removed, such as <tt>UNIQUENAME</tt> and
-	<tt>LATEST_LINK</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>We would like to remind everyone that the ports tree is
-	  built and run by volunteers, and any help is greatly
-	  appreciated.  This is more important than ever, since the
-	  number of problem 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, 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>
-      </li></ol><hr /><h2><a name="Ports-on-PowerPC" href="#Ports-on-PowerPC" id="Ports-on-PowerPC">Ports on PowerPC</a></h2><p>
-	Contact: 
-	  Alexey
-	  Dokuchaev
-	 &lt;<a href="mailto:danfe@FreeBSD.org">danfe@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Ports Collection typically receives less attention on
-	Tier-2 architectures than on Tier-1 architectures, although
-	several build-runs were performed at various points in the
-	past, and broken ports were marked as such at those times.</p>
-
-      <p>Some of the Tier-2 platforms, such as PowerPC and ARM,
-	have improved considerably recently, both on FreeBSD's and the
-	compilers' sides, but as the tree is not rebuilt on the
-	cluster very often, it was suspected that many ports are
-	marked BROKEN while they in fact now build and run
-	correctly.</p>
-
-      <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 (leftovers from the old times)
-	were marked as working, and fewer than 40 ports still have
-	issues requiring further work.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The Ports Collection could benefit a lot from more frequent
-	  sweeps targeting Tier-2 systems.</p>
-      </li><li>
-	<p>Recent work on QEMU-backed emulators and the
-	  much-anticipated cross-building of ports are essential
-	  pieces to bring FreeBSD packages on par with the base system's
-	  support, architecture-wise.</p>
-      </li></ol><hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Xfce" title="https://wiki.FreeBSD.org/Xfce">FreeBSD Xfce Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Xfce" title="FreeBSD Xfce Project">https://wiki.FreeBSD.org/Xfce</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="https://www.assembla.com/spaces/xfce4/subversion/source">FreeBSD Xfce Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="FreeBSD Xfce Repository">https://www.assembla.com/spaces/xfce4/subversion/source</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms, such as FreeBSD.  It aims to be fast and
-	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>
-
-      <ul>
-	<li><tt>science/xfce4-equake-plugin</tt> 1.3.8</li>
-
-	<li><tt>sysutils/xfce4-power-manager</tt> 1.5.2</li>
-
-	<li><tt>x11/libexo</tt> 0.10.7</li>
-
-	<li><tt>x11/xfce4-embed-plugin</tt> 1.6.0</li>
-
-	<li><tt>x11/xfce4-verve-plugin</tt> 1.1.0</li>
-
-	<li><tt>x11/xfce4-whiskermenu-plugin</tt> 1.5.1</li>
-
-	<li><tt>x11-wm/xfce4-desktop</tt> 4.12.3</li>
-
-	<li><tt>www/midori</tt> 0.5.11</li>
-      </ul>
-
-      <p>We also follow the unstable releases (available in our
-	experimental repository) of:</p>
-
-      <ul>
-	<li><tt>sysutils/xfce4-panel-switch</tt> 1.0.2 (utility to
-	  backup panel layouts)</li>
-
-	<li><tt>x11/xfce4-dashboard</tt> 0.5.1</li>
-      </ul>
-
-      <p>In the <tt>trunk</tt> branch, <tt>x11-wm/xfce4-panel</tt>
-	contains a patch to support
-	<tt>sysutils/xfce4-panel-switch</tt> (available through the
-	panel preferences).</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Test the new stable release of GLib 2.46.x with the
-	  kqueue/kevent backend enabled (it was disabled with revision
-	  <a href="https://svnweb.FreeBSD.org/ports?view=revision&amp;revision=393663" shape="rect">r393663</a>).
-	  Currently several features are broken, especially in Thunar,
-	  xfce4-panel, and Xfdashboard.</p>
-      </li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="PO-Translation-Project" href="#PO-Translation-Project" id="PO-Translation-Project">PO Translation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html">PO Translations</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html" title="PO Translations">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/de_DE.ISO8859-1/articles/leap-seconds/" title="https://www.FreeBSD.org/doc/de_DE.ISO8859-1/articles/leap-seconds/">German translation of the Leap Seconds article</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/de_DE.ISO8859-1/articles/leap-seconds/" title="German translation of the Leap Seconds article">https://www.FreeBSD.org/doc/de_DE.ISO8859-1/articles/leap-seconds/</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/nl_NL.ISO8859-1/articles/explaining-bsd/" title="https://www.FreeBSD.org/doc/nl_NL.ISO8859-1/articles/explaining-bsd/">Dutch translation of the Explaining BSD article</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/nl_NL.ISO8859-1/articles/explaining-bsd/" title="Dutch translation of the Explaining BSD article">https://www.FreeBSD.org/doc/nl_NL.ISO8859-1/articles/explaining-bsd/</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/pipermail/freebsd-translators/" title="https://lists.FreeBSD.org/pipermail/freebsd-translators/">FreeBSD Translators mailing list</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/pipermail/freebsd-translators/" title="FreeBSD Translators mailing list">https://lists.FreeBSD.org/pipermail/freebsd-translators/</a></td></tr></table><p>
-	Contact: FreeBSD Documentation Team &lt;<a href="mailto:freebsd-doc@FreeBSD.org">freebsd-doc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Translators &lt;<a href="mailto:freebsd-translators@FreeBSD.org">freebsd-translators@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD documentation translation process has been in need
-	of modernization for quite some time.  The existing process
-	was just too difficult for translators to keep translations up
-	to date.</p>
-
-      <p>With help from Benedict Reuschling, Shaun McCance, Ryan
-	Lortie, Hiroki Sato, and many others, the availability of a
-	new PO translation system was announced in August.</p>
-
-      <p>PO translations handle most of the overhead of the
-	translation process.  Translators do not have to keep track of
-	commits to the upstream English version.  The actual work of
-	translating is quicker and easier.  PO editors show how much
-	of the document has been translated.  If a translation is
-	already available for a given string, it can be easily
-	reused.</p>
-
-      <p>Early testing has been very successful.  Most issues involve
-	discovering and documenting the new processes rather than
-	fixing bugs.  New translations of English documents have
-	already been committed.</p>
-
-      <p>There will certainly be additional changes and improvements,
-	but the system works.  We will continue to discover how to
-	share work between translation teams and the project as a
-	whole.  This work will be much easier now that the initial
-	hurdle of being able to use PO software has been passed.
-      </p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Continue testing.  The system is new to us and there are
-	  bound to be bugs and situations with unexpected results.</p>
-      </li><li>
-	<p>Improve documentation on using the new PO translations.
-	  Much of this involves things that rarely happened with
-	  the old system, like adding a completely new language
-	  directory.</p>
-      </li><li>
-	<p>Add new translations for existing documents.  There is much
-	  less work to create and update a translated document
-	  now.  Existing and new translators are working on adding and
-	  updating translations of the English documentation.</p>
-      </li><li>
-	<p>Figure out how to generate and share translation memory
-	  with other members of a language team or translators outside
-	  the team.</p>
-      </li><li>
-	<p>Test new PO editors like Pootle and Virtaal.</p>
-      </li><li>
-	<p>Determine a method to allow translators commit access for
-	  translations.</p>
-      </li><li>
-	<p>Develop and test code to translate manual pages.</p>
-      </li></ol><hr /><h2><a name="Website-CSS-Update" href="#Website-CSS-Update" id="Website-CSS-Update">Website CSS Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/" title="https://www.FreeBSD.org/">FreeBSD Main Site</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/" title="FreeBSD Main Site">https://www.FreeBSD.org/</a></td></tr></table><p>
-	Contact: 
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD website has remained essentially unchanged in
-	appearance for many years.  Like other legacy systems, it is
-	difficult to change.  It is heavily used and therefore subject
-	to non-trivial bikeshedding.</p>
-
-      <p>The CSS shrunk the reader's font from the size they had
-	requested.  It specified hardcoded font and object sizes in
-	pixels.  On wide monitors, only the middle third of the screen
-	was used.  Hardware has changed from what existed when
-	this version of the site was created.  Screens have become
-	larger and wider, and increased in resolution at the same
-	time.</p>
-
-      <p>It was time for a change.  Font sizes were set to
-	percentages, with none smaller than 100%.  The width of the
-	main box was changed to 90%.  Other small adjustments were
-	added.  These limited changes produced a rendered site that
-	better respects the reader's settings, is much easier to read,
-	and shows more information.</p>
-
-      <p>Although no content changed, the appearance was so different
-	that some viewers thought we had redesigned the site.  It is
-	gratifying to know that so many people are using it.  We would
-	also like to thank people for the response, which was
-	overwhelmingly positive and hardly bikesheddy at all.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Fix other outdated assumptions in the CSS.  Alternately,
-	  rework the entire site.  However, that is a much more
-	  complex and ambitious project than it might seem.</p>
-      </li></ol><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Allwinner-A10/A20-Support" href="#Allwinner-A10/A20-Support" id="Allwinner-A10/A20-Support">Allwinner A10/A20 Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner">Wiki page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="Wiki page">https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner</a></td></tr></table><p>
-	Contact: 
-	  Luiz Otavio
-	  O Souza
-	 &lt;<a href="mailto:loos@FreeBSD.org">loos@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Pratik
-	  Singhal
-	 &lt;<a href="mailto:ps06756@gmail.com">ps06756@gmail.com</a>&gt;
-	</p>
-      <p>The Allwinner A10 and A20 chips are ARM CPUs found in
-	increasingly common development boards and other devices, such as 
-	the Cubieboard/Cubieboard 2 and the Banana Pi.</p>
-
-      <p>With the end of a GSoC project by Pratik Singhal, our A10 and
-	A20 support has improved.  Pratik helped with the
-	implementation and testing of the SD card and SATA support for
-	the Allwinner chips.</p>
-
-      <p>Luiz Otavio O Souza added support for the <tt>dwc</tt> network interface
-	on the A20, which is capable of gigabit speeds.</p>
-
-      <p>Glen Barber kindly added support for official FreeBSD images for
-	Cubieboard 2 and the Banana Pi.</p>
-    <p>This project was sponsored by Google Summer of Code 2015 (partly).</p><h3>Open tasks:</h3><ol><li>
-	<p>Some drivers are still missing: audio,
-	  video/HDMI/framebuffer, IR, I2C, SPI, PWM.</p>
-      </li><li>
-	<p>Fix <tt>if_dwc</tt> for better performance.</p>
-      </li></ol><hr /><h2><a name="mtree-Parsing-and-Manipulation-Library" href="#mtree-Parsing-and-Manipulation-Library" id="mtree-Parsing-and-Manipulation-Library">mtree Parsing and Manipulation Library</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary" title="https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary">Wiki page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary" title="Wiki page">https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary</a></td></tr></table><p>
-	Contact: 
-	  Michal
-	  Ratajsky
-	 &lt;<a href="mailto:michal@FreeBSD.org">michal@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Brooks
-	  Davis
-	 &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD includes several programs that work with file system
-	hierarchy descriptions in the <tt>mtree(5)</tt> format.  These
-	descriptions, also called specifications, have a broad range
-	of uses, from automatically creating directory structures to
-	security auditing.</p>
-
-      <p> Each of the programs, namely <tt>mtree</tt>,
-	<tt>bsdtar</tt>, <tt>install</tt>, and <tt>makefs</tt>, has
-	its own implementation of the mtree format.  This not only
-	adds maintenance overhead, but also makes interoperability
-	difficult, as each of the implementations only supports a
-	limited subset of the format.</p>
-
-      <p>The goal of this project was to create a new
-	<tt>libmtree</tt> library, implementing everything the mtree
-	format has to offer, and wrapping it with an expressive API
-	which all the listed programs can use.  We also wanted
-	<tt>libmtree</tt> to be portable, as one of the major users of
-	the mtree format is <tt>libarchive</tt>, the library
-	implementing most of <tt>bsdtar</tt>.</p>
-
-      <p>Currently, the library is functionally complete, ready to be
-	downloaded and receive everyone's attention.  We have also
-	decided to bundle the <tt>mtree</tt> program along with it.
-	The bundled <tt>mtree</tt> has also been modified for better
-	portability.</p>
-
-      <p>The project included modifying <tt>libarchive</tt>,
-	<tt>install</tt> and <tt>makefs</tt> to use libmtree.  These
-	modified versions are also available.</p>
-
-      <p>Please see the Wiki page for more information, download
-	locations, and an example of using the <tt>libmtree</tt> API.
-      </p>
-    <p>This project was sponsored by Google Summer of Code 2015.</p><h3>Open tasks:</h3><ol><li>
-	<p>Test and review the library code and API, and the
-	  modifications made to the programs.</p>
-      </li><li>
-	<p>Fix the known problems that are mentioned on the Wiki
-	  page.</p>
-      </li></ol><hr /><h2><a name="Multiqueue-Testing" href="#Multiqueue-Testing" id="Multiqueue-Testing">Multiqueue Testing</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject" title="https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject">Project Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject" title="Project Wiki Page">https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject</a></td></tr></table><p>
-	Contact: 
-	  Tiwei
-	  Bie
-	 &lt;<a href="mailto:btw@FreeBSD.org">btw@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Hiren
-	  Panchasara
-	 &lt;<a href="mailto:hiren@FreeBSD.org">hiren@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  George
-	  Neville-Neil
-	 &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact: 
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p>
-      <p>The aim of this project is to design and implement
-	infrastructure to validate that a number of the network
-	stack's multiqueue behaviours are functioning as expected.</p>
-
-      <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 <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
-	      (<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>
-
-      <p>However, it still needs further refinements to make it
-	suitable for committing to FreeBSD head.</p>
-    <p>This project was sponsored by Google Summer of Code 2015.</p><hr /><h2><a name="Update-Ficl-in-Bootloader" href="#Update-Ficl-in-Bootloader" id="Update-Ficl-in-Bootloader">Update Ficl in Bootloader</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader" title="https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader">Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader" title="Wiki Page">https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader</a></td></tr></table><p>
-	Contact: 
-	  Colin
-	  Lord
-	 &lt;<a href="mailto:clord@FreeBSD.org">clord@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD bootloader has used Ficl 3 for quite some time.
-	This project was intended to update the version of Ficl in use
-	to Ficl 4.  Ficl 4 is not only faster but also has a smaller
-	memory footprint, both being important advantages for a
-	bootloader.</p>
-
-      <p>As part of the Google Summer of Code program, I worked on
-	importing the Ficl 4 sources to get a bootloader running Ficl
-	4. The first half of the summer consisted of setting up my
-	test environment, as well as arranging the sources in the tree
-	properly and modifying the build files to point to the new
-	locations.  Once that was complete, the sources had to be
-	modified to build correctly and to add back in some of the
-	FreeBSD-specific parts from Ficl 3.  Unfortunately, after all
-	those tasks were completed, a few bugs in the Ficl project
-	were discovered that delayed the bootloader update, so it is
-	not finished.  The Illumos project has faced similar issues
-	with Ficl 4 so I received some good tips from them, but since
-	school has started back up I have not been able to put much
-	work into fixing the bugs.</p>
-    <p>This project was sponsored by Google Summer of Code 2015.</p><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">Foundation website</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="Foundation website">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
-	Contact: 
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Funding comes from individual and
-	corporate donations and is used to fund and manage development
-	projects, conferences and developer summits, and provide
-	travel grants to FreeBSD developers.  The Foundation purchases
-	hardware to improve and maintain FreeBSD infrastructure and
-	publishes FreeBSD white papers and marketing material to promote,
-	educate, and advocate for the FreeBSD Project.  The Foundation
-	also represents the FreeBSD Project in executing contracts,
-	license agreements, and other legal arrangements that require
-	a recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD last
-	quarter:</p>
-
-      <p>Anne Dickison and Deb Goodkin attended OSCON to promote
-	FreeBSD.</p>
-
-      <p>Robert Watson organized and ran the Cambridge FreeBSD Developer
-	Summit 2015 ("BSDCam").  We provided travel grants to two FreeBSD
-	developers to attend the summit.  Three Foundation board/staff
-	members attended too.</p>
-
-      <p>George V. Neville-Neil attended the ARM Partner Meeting where he met with 15
-	silicon and systems vendors to present the unique traits and
-	qualities of FreeBSD and work on setting up partnerships with the
-	companies building and deploying ARM hardware.</p>
-
-      <p>George and Robert Watson collaborated in Cambridge on
-	developing further FreeBSD-based teaching material at
-	undergraduate and masters levels.  Part of this project was
-	funded by the Foundation.</p>
-
-      <p>George planned and ran the DevSummit at vBSDCon 2015.</p>
-
-      <p>We were  proud to be a sponsor of
-	<url href="http://www.verisign.com/en_US/internet-technology-news/verisign-events/vbsdcon/index.xhtml">vBSDCon
-	  2015</url>, Sept 11-13 in Washington DC.  George V. Neville-Neil and
-	Ed Maste presented "Supporting a BSD Project" at the
-	conference.  Dru Lavigne, Glen Barber, George V. Neville-Neil, and Ed Maste
-	attended and represented the Foundation at both vBSDCon and
-	the FreeBSD Developer Summit that preceded it.  We had many
-	people stop by our table to make a donation, and it was
-	another great opportunity to talk and work with people
-	face-to-face.</p>
-
-      <p>Cheryl Blain and John Baldwin promoted the Foundation and FreeBSD at
-	the SNIA 2015 Storage Developer Conference, in Santa Clara,
-	California, Sept 21-24.  The Foundation was also a
-	sponsor.</p>
-
-      <p>We sponsored Andy Turner to attend Linaro Connect in San
-	Francisco, Sept 21-25.</p>
-
-      <p>Ed Maste, our project development director, attended the
-	X.Org Developer's Conference (XDC) in Toronto, Ontario.</p>
-
-      <p>We sponsored the 2015 nginx Conference and sent FreeBSD
-	community member John Baldwin.</p>
-
-      <p>George Neville-Neil continued planning the
-	<url href="https://wiki.freebsd.org/201511VendorDevSummit">2015
-	  Silicon Valley Vendor Summit</url>, including securing
-	the venue.</p>
-
-      <p>Benedict Reuschling and Erwin Lansing helped plan and organize the EuroBSDCon
-	FreeBSD Developer Summit.  This included setting up the working
-	groups, securing the venue, and getting the T-shirts made.</p>
-
-      <p>Benedict helped organize, and he and Dru Lavigne participated
-	in the
-	<url href="https://wiki.freebsd.org/201507DevSummit">FreeBSD
-	Hackathon</url> in the Linuxhotel in Essen, Germany.  It was a
-	successful weekend of fixing bugs and collaborating with
-	others.</p>
-
-      <p>Dru Lavigne taught a FreeBSD class in Berlin, Germany July
-	29-31.</p>
-
-      <p>We were a sponsor of
-	<url href="http://womencourage.acm.org/index.cfm">womENcourage
-	  2015</url>, in Uppsala Sweden, Sept 24-26.  Dru was the
-	moderator for a panel on
-	<url href="http://womencourage.acm.org/panel2.cfm">Open Source
-	  as a Career Path</url>.  All the panelists were FreeBSD
-	contributors including Dan Langille, Allan Jude, Benedict
-	Reuschling, and Deb Goodkin.  We also had a table at the job
-	fair and talked to a lot of students and professors about the
-	benefits of working on FreeBSD as an alternative to an
-	internship, teaching about FreeBSD in university classes, and
-	hosting FreeBSD events at their schools.  Dan taught a workshop
-	on How to Contribute to an Open Source project.  Deb
-	participated in this workshop and started a discussion on
-	offering a similar workshop at BSD and non-BSD conferences.
-	The workshop would be titled "How to Contribute to FreeBSD", and
-	participants would learn how to contribute documentation to
-	the Project.</p>
-
-      <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
-	ScaleEngine.  We also continued to approach companies to
-	provide us with testimonials to help promote their use of
-	FreeBSD.</p>
-
-      <p>Anne Dickison rebooted the Faces of FreeBSD series and is
-	working with FreeBSD contributors on writing their stories.
-	She continued to produce more FreeBSD Swag and literature to
-	promote FreeBSD, as well as advocating for FreeBSD over our social
-	channels and with new partnerships.</p>
-
-      <p>We reached our 2015 goal of 10,000 FreeBSD Journal subscribers,
-	and we published a new Open Journal article on our website, to
-	help promote the Journal.  We also started offering a new
-	subscription bundle, where you can buy all the 2014 issues.
-	The July/August issue was published.</p>
-
-      <p>Justin T. Gibbs began teaching a semester-long FreeBSD class at a middle school
-	in Boulder, Colorado.  We are using the BeagleBone Black (BBB)
-	to run FreeBSD connected to Macs and PCs.  We have received a lot
-	of support, both internally, and from the Project, to get the
-	FreeBSD images to work on the BBB with the Macs and PCs.  It has
-	been a great collaborative effort with community members, and
-	this will help future classes in being able to support
-	inexpensive platforms for teaching FreeBSD.</p>
-
-      <p>Work continued on creating a FreeBSD curriculum for a half day
-	workshop.  Hopefully this will be available in late
-	Spring.</p>
-
-      <p>We provided legal support for the Project including granting
-	trademark permission for some users and companies who
-	requested permission to put the FreeBSD logo on their websites
-	and marketing literature.</p>
-
-      <p>We met with commercial users to get their input on what
-	they would like to see supported in FreeBSD.  We also do this to
-	help connect FreeBSD developers with commercial users to help
-	facilitate collaboration.</p>
-
-      <p>FreeBSD Foundation employee and Release Engineer Glen Barber was
-	extremely busy during this quarter, working on a number of
-	exciting areas of the FreeBSD Project.  Some of the highlights
-	include:
-
-	<ul>
-	  <li>Code cleanup and bug fixes to several parts of the
-	    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,
-	    starting from the code slush.</li>
-
-	  <li> With the FreeBSD Release Engineering Team, released two
-	    BETA builds and three RC builds for the 10.2-RELEASE
-	    cycle, with the final release announced mid-August,
-	    two weeks ahead of the original schedule.</li>
-
-	  <li>With the FreeBSD Cluster Administrators Team, assisted with
-	    a number of general updates and enhancements to the FreeBSD
-	    infrastructure.</li>
-	</ul></p>
-    <hr /><h2><a name="ZFSguru" href="#ZFSguru" id="ZFSguru">ZFSguru</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zfsguru.com" title="http://zfsguru.com">Home page</a></td><td>
-	    URL: <a href="http://zfsguru.com" title="Home page">http://zfsguru.com</a></td></tr><tr><td><a href="http://zfsguru.com/forum/zfsgurudevelopment/1038" title="http://zfsguru.com/forum/zfsgurudevelopment/1038">Forum post on Gnome�3 debugging</a></td><td>
-	    URL: <a href="http://zfsguru.com/forum/zfsgurudevelopment/1038" title="Forum post on Gnome�3 debugging">http://zfsguru.com/forum/zfsgurudevelopment/1038</a></td></tr></table><p>
-	Contact: 
-	  Jason
-	  Edwards
-	 &lt;<a href="mailto:jason@zfsguru.com">jason@zfsguru.com</a>&gt;
-	</p>
-      <p>ZFSguru started as a front-end to ZFS but has since grown
-	into a multifunctional server appliance with its own unique
-	features.  While the project is still in early development, it
-	already offers multiple unique features not found in other
-	projects.  Unlike similar projects, nothing is stripped away
-	from the base operating system, meaning ZFSguru behaves as a
-	normal FreeBSD installation and thus is very versatile.  The
-	web-interface is designed to unite both novice and advanced
-	users, providing both very easy to use basic functionality as
-	well as features to be appreciated by more experienced users.
-	The modular nature of the project combats the danger of bloat,
-	whilst still allowing extended functionality to be easily
-	deployed.</p>
-
-      <p>On the 15th of August, version 0.3 of ZFSguru was released.
-	Some highlights of the new version:</p>
-
-      <ul>
-	<li>New build infrastructure allows for frequent releases of
-	  system images and services in a semi-automated way.</li>
-
-	<li>A new GuruDB database allows for a growing number of
-	  system images and servers, and provides good caching to
-	  accelerate pages.</li>
-
-	<li>The installation procedure was given a major
-	  overhaul.</li>
-
-	<li>In addition to the LiveCD, USB images are now available.
-	  The USB image supports both legacy MBR bootcode and UEFI
-	  boot.</li>
-
-	<li>Many libraries in the web-interface have been
-	  overhauled, in addition to many other additions to the
-	  web interface.</li>
-
-	<li>Many improvements were made to optional add-on services,
-	  such as the new Gnome 3 graphical environment.</li>
-      </ul>
-
-      <p>Other progress made in the months July, August, and
-	September:</p>
-
-      <ul>
-	<li>System image builds 001, 002, 003, and 004 have been
-	  released for all supported branches: 10.0, 10.1, 10.2, 10.3
-	  (-STABLE), and 11.0 (-CURRENT).</li>
-
-	<li>Work on the 0.4 web-interface has started, which focuses
-	  on improving network support in the web-interface.</li>
-
-	<li>Work on a new visual theme for the web-interface has
-	  started.  The new interface is likely to be included in the
-	  upcoming 0.4 release.</li>
-
-	<li>A new master server is being prepared, which is likely to
-	  be operational in December.</li>
-
-	<li>A new website is being worked on, to be launched the first
-	  of January, 2016.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The new Gnome�3 desktop does not work for everyone
-	  and still has issues.  Anyone capable of diagnosing these
-	  issues can give the Gnome�3 LiveCD a try.  Please see
-	  the linked forum thread for more information.</p>
-      </li><li>
-	<p>Several ports fail to compile with our own build
-	  infrastructure, and require bug reports in order to get
-	  them fixed upstream.</p>
-      </li><li>
-	<p>A 'State of the Project 2015' is due in Q4, providing an
-	  overview for future development of the project.</p>
-      </li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2015-10-2015-12.html b/website/content/en/status/report-2015-10-2015-12.html
deleted file mode 100644
index f32802619e..0000000000
--- a/website/content/en/status/report-2015-10-2015-12.html
+++ /dev/null
@@ -1,3387 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The fourth quarter of 2015 saw a great deal of activity for
-      FreeBSD.  This is now the third quarter running for which I can say
-      that this is the largest report yet published!  Many thanks to
-      everyone who proactively submitted topics and entries &#8212; it
-      is great to have more complete coverage of ongoing development for
-      the community to learn about in these reports.</p><p>An experimental new Triage Team was formed this quarter to
-      create a new way for community members to participate,
-      and to improve issue management and productivity in general.
-      Making more effective use of automation
-      and tooling can help to increase developer productivity and the
-      quality of FreeBSD, just as the adoption of Jenkins and continual
-      integration tooling catches regressions quickly and maintains the
-      high standards for the system.</p><p>Efforts to bring our BSD high standards to new
-      architectures continue, with impressive work on arm64 leading to
-      its promotion to Tier-2 status and a flurry of work bringing up
-      the new RISC-V hardware architecture.  Software architecture is
-      also under active development, including system startup and
-      service management.  A handful of potential init system
-      replacements are mentioned in this report: <tt>launchd</tt>,
-      <tt>relaunchd</tt>, and <tt>nosh</tt>.  Architectural changes
-      originating both from academic research (multipath TCP) and from
-      the realities of industry (<tt>sendfile(2)</tt> improvements) are
-      also under way.  It is heartening to see how FreeBSD provides a
-      welcoming platform for contributions from both research and
-      industry.</p><p>To all the readers, whether from academia or industry,
-      hobbyist or professional: I hope you are as excited as I am to
-      read about all of the progress and projects covered in this
-      report, and the future of FreeBSD!</p><p>&#8212;Ben Kaduk</p><p><hr /></p><p>The deadline for submissions covering the period from January
-      to March 2016 is April 7, 2016.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Issue-Tracking-(Bugzilla)">Issue Tracking (Bugzilla)</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Issue-Triage-Team">The FreeBSD Issue Triage Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#CAM-I/O-Scheduler">CAM I/O Scheduler</a></li><li><a href="#Encrypted-Kernel-Crash-Dumps">Encrypted Kernel Crash Dumps</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li><li><a href="#Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support">Mellanox iSCSI Extensions for RDMA (iSER) Support</a></li><li><a href="#MIPS:-Ralink/Mediatek-Support">MIPS: Ralink/Mediatek Support</a></li><li><a href="#Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></li><li><a href="#OpenBSM">OpenBSM</a></li><li><a href="#Raspberry-Pi:-VideoCore-Userland-Application-Packaging">Raspberry Pi: VideoCore Userland Application
-      Packaging</a></li><li><a href="#RCTL-Disk-IO-Limits">RCTL Disk IO Limits</a></li><li><a href="#Root-Remount">Root Remount</a></li><li><a href="#Routing-Stack-Update">Routing Stack Update</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#The-nosh-Project">The nosh Project</a></li><li><a href="#UEFI-Boot-and-Framebuffer-Support">UEFI Boot and Framebuffer Support</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Chelsio-iSCSI-Offload-Driver-(Initiator-and-Target)">Chelsio iSCSI Offload Driver (Initiator and Target)</a></li><li><a href="#FreeBSD-Integration-Services-(BIS)">FreeBSD Integration Services (BIS)</a></li><li><a href="#FreeBSD-Xen">FreeBSD Xen</a></li><li><a href="#Improvements-to-the-QLogic-HBA-Driver">Improvements to the QLogic HBA Driver</a></li><li><a href="#iMX.6-Video-Output-Support">iMX.6 Video Output Support</a></li><li><a href="#ioat(4)-Driver-Enhancements">ioat(4) Driver Enhancements</a></li><li><a href="#Kernel-Vnode-Cache-Tuning">Kernel Vnode Cache Tuning</a></li><li><a href="#Mellanox-Drivers">Mellanox Drivers</a></li><li><a href="#Minimal-Kernel-with-PNP-Based-Autoloading">Minimal Kernel with PNP-Based Autoloading</a></li><li><a href="#MMC-Stack-Under-CAM-Framework">MMC Stack Under CAM Framework</a></li><li><a href="#ntb_hw(4)/if_ntb(4)-Driver-Synced-up-to-Linux">ntb_hw(4)/if_ntb(4) Driver Synced up to
-      Linux</a></li><li><a href="#Out-of-Memory-Handler-Rewrite">Out of Memory Handler Rewrite</a></li><li><a href="#sendfile(2)-Improvements">sendfile(2) Improvements</a></li><li><a href="#sysctl-Enhancements">sysctl Enhancements</a></li><li><a href="#Touchscreen-Support-for-Raspberry-Pi-and-Beaglebone-Black">Touchscreen Support for Raspberry Pi and Beaglebone
-      Black</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#armv6-Hard-Float-Default-ABI">armv6 Hard Float Default ABI</a></li><li><a href="#FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></li><li><a href="#FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></li><li><a href="#FreeBSD-on-SoftIron-Overdrive-3000">FreeBSD on SoftIron Overdrive 3000</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#FreeBSD/RISC-V">FreeBSD/RISC-V</a></li><li><a href="#Improvements-for-ARMv6/v7-Support">Improvements for ARMv6/v7 Support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Base-System-Build-Improvements">Base System Build Improvements</a></li><li><a href="#ELF-Tool-Chain-Tools">ELF Tool Chain Tools</a></li><li><a href="#The-LLDB-Debugger">The LLDB Debugger</a></li><li><a href="#Updates-to-GDB">Updates to GDB</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Bringing-GitLab-into-the-Ports-Collection">Bringing GitLab into the Ports Collection</a></li><li><a href="#GNOME-on-FreeBSD">GNOME on FreeBSD</a></li><li><a href="#IPv6-Promotion-Campaign">IPv6 Promotion Campaign</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Linux-Kernel-as-a-Library-Added-to-the-Ports-Collection">Linux Kernel as a Library Added to the Ports
-      Collection</a></li><li><a href="#LXQt-on-FreeBSD">LXQt on FreeBSD</a></li><li><a href="#New-Tools-to-Enhance-the-Porting-Experience">New Tools to Enhance the Porting Experience</a></li><li><a href="#Node.js-Modules">Node.js Modules</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Supporting-Variants-in-the-Ports-Framework">Supporting Variants in the Ports Framework</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#&quot;FreeBSD-Mastery:-Specialty-Filesystems&quot;-Early-Access-Version-Now-Available">"FreeBSD Mastery: Specialty Filesystems" Early Access Version Now Available</a></li><li><a href="#style(9)-Enhanced-to-Allow-C99-bool">style(9) Enhanced to Allow C99
-      bool</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#HardenedBSD">HardenedBSD</a></li><li><a href="#NanoBSD-Modernization">NanoBSD Modernization</a></li><li><a href="#relaunchd">relaunchd</a></li><li><a href="#System-Initialization-and-Service-Management">System Initialization and Service Management</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/10.3R/schedule.html" title="https://www.freebsd.org/releases/10.3R/schedule.html">FreeBSD�10.3-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/10.3R/schedule.html" title="FreeBSD�10.3-RELEASE schedule">https://www.freebsd.org/releases/10.3R/schedule.html</a></td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD Development Snapshots</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD Development Snapshots">http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>During the last quarter of 2015, the Release Engineering team
-	added support for three additional FreeBSD/arm systems:
-	<tt>BANANAPI</tt>, <tt>CUBIEBOARD</tt>, and
-	<tt>CUBIEBOARD2</tt>.</p>
-
-      <p>In addition to regular development snapshot builds for
-	FreeBSD�11.0-CURRENT and FreeBSD�10.2-STABLE, several
-	changes and enhancements were made to the release build code.
-	Of note, the release build code no longer produces MD5
-	checksums, in favor of SHA512.</p>
-
-      <p>Toward the end of the year, focus was primarily
-	centered on the upcoming FreeBSD�10.3 release cycle,
-	which will begin in January 2016.</p>
-
-      <p>As always, help testing development snapshot builds is
-	crucial to producing quality releases, and we encourage
-	testing development snapshots whenever possible.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Issue-Tracking-(Bugzilla)" href="#Issue-Tracking-(Bugzilla)" id="Issue-Tracking-(Bugzilla)">Issue Tracking (Bugzilla)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/" title="https://bugs.freebsd.org/bugzilla/">Bugzilla Home Page</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/" title="Bugzilla Home Page">https://bugs.freebsd.org/bugzilla/</a></td></tr></table><p>
-	Contact: Bugmeisters &lt;<a href="mailto:bugmeister@FreeBSD.org">bugmeister@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kubilay
-	  Kocak
-	 &lt;<a href="mailto:koobs@FreeBSD.org">koobs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mahdi
-	  Mokhtari
-	 &lt;<a href="mailto:mokhi64@gmail.com">mokhi64@gmail.com</a>&gt;
-	</p>
-      <p>The bugmeister team has gained a new member, Mahdi Mokhtari
-	(mokhi64@gmail.com).  Mahdi has been contributing to the FreeBSD
-	Project for just over one month.  After getting started by
-	creating ports for Chef-Server and MySQL 5.7 (with Bernard
-	Spil's help), an introduction to Kubilay Kocak led to guidance on
-	appropriate projects, such as Bugzilla development to help
-	Bugmeister, the Bugzilla Triage team, Developers, and the
-	community by making issue tracking better.  This is how things
-	are going so far:</p>
-
-      <p>Issue Tracking can be either "Defect Tracking for
-	Systems" or "Bug-Tracking for Systems".  System
-	Defect Tracking is to allow individual or groups of developers
-	to keep track of outstanding issues in their product
-	effectively.  We use Bugzilla to manage issues for the FreeBSD
-	project.</p>
-
-      <p>We are pleased to announce some developments on our issue
-	management systems:</p>
-
-      <ul>
-	<li>We have made improvements to the AutoAssigner module
-	  (not yet deployed) that was previously developed by Marcus von Appen
-	  to assign port bugs to their maintainers by default, such
-	  as:
-
-	  <ul>
-	    <li>Improvements and bugfixes to port detection in
-	      the Summary: field of issues, for automatic assignment
-	      to their maintainers in a better way.</li>
-
-	    <li>Refactoring code to make future development easier
-	      and faster in a more modular way.</li>
-	  </ul>
-	</li>
-
-	<li>We have developed a new module (FBSDAttachment), which
-	  automates setting maintainer-approval flag values on
-	  attachments under most conditions.  This will improve time
-	  to resolution, consistency of triage, and reduce manual
-	  effort by triagers and maintainers.</li>
-
-	<li>We reported and upstreamed a number of bugs in Bugzilla,
-	  working with the upstream Bugzilla developers.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Major improvements to templates for usability and
-	  simplicity.</p>
-      </li><li>
-	<p>Further improvements to automation (for example,
-	  additional processing of commit logs).</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>Two major issues have occupied much of core's attention
-	during the last quarter: the reorganisation of the Security
-	Team and the question of whether to import GPLv3 licensed code
-	into the source repository.</p>
-
-      <ol>
-	<li>
-	  <p>The idea of reorganizing the Security team was first
-	    proposed to Core during a meeting at BSDCan this year by
-	    Gleb Smirnoff &#8212; core member and newly-appointed
-	    deputy Security Officer (SO).  The "Security
-	    Team", which previously could contain several people
-	    (a varying number over time, but more than two) has been
-	    refashioned into just two roles: Security Officer and
-	    Deputy Security Officer.  Accordingly, the role of the SO
-	    team has been redefined to be the controller of the
-	    distribution of security sensitive information into and
-	    within the project: they are responsible for interfacing
-	    with external bodies and individuals reporting security
-	    problems to the project, and connecting those reports to
-	    the appropriate individuals within the project with the
-	    technical expertise to address the identified concerns.
-	    These changes will improve the project's responsiveness to
-	    security alerts, help maintain security on privileged
-	    information received in confidence before general
-	    publication and, not least, reduce the work load on the
-	    security officer.  The SO team will continue to benefit
-	    from liasons with the Core, Cluster Administration, and
-	    Release Engineering teams, and will be assisted by a
-	    secretary; they will also be able to obtain input and
-	    assistance in drafting security advisories from former and
-	    potential future (Deputy) Security Officers.</p>
-
-	  <p>Core would particularly like to thank the former members
-	    of the Security Team group for their past contributions,
-	    now that the Security Team role has been merged into the
-	    Security Officer's responsibilities.</p>
-	</li>
-
-	<li>
-	  <p>The other large question concerning Core is how to
-	    provide a modern toolchain for all supported achitectures.
-	    Tier 1 architectures are required to ship with a toolchain
-	    unencumbered by onerous license terms.  This is currently
-	    provided for i386 and amd64 by the LLVM suite, including
-	    the Clang compiler, LLD and LLDB.  However LLVM support
-	    for other (Tier 2 or below) architectures is not yet of
-	    sufficient quality to be viable, and the older but
-	    pre-existing GPLv2 toolchain cannot support some of the
-	    interesting new architectures such as arm64 and RISC-V.
-	    Pragmatically, in order for the project to support
-	    these architectures,
-	    until LLVM support arrives we must turn to the GNU
-	    project's GPLv3 licenced toolchain.</p>
-
-	  <p>The argument here is whether to import GPLv3 licensed
-	    code into the FreeBSD src repository with all of the
-	    obligations on patent terms and source code redistribution
-	    that would entail, not only for the FreeBSD project itself
-	    but for numerous downstream consumers of FreeBSD code.  Not
-	    having a toolchain readily available is a big impediment
-	    to working on a new architecture.</p>
-
-	  <p>One potential solution is to create a range of
-	    "GPLv3 toolchain" base-system packages out of a
-	    completely separate source code repository, for instance
-	    within the FreeBSD area on Github.  These would be
-	    distributed equivalently to the other base system binary
-	    packages when that mechanism is introduced.</p>
-
-	  <p>Core recognises that this is a decision with wide-ranging
-	    consequences and will be producing a position paper for
-	    circulation amongst all interested parties in order to
-	    judge community opinion on the matter.  Core welcomes
-	    feedback from all interested parties on the subject.</p>
-	</li>
-      </ol>
-
-      <p>Beyond these two big questions, Core has handled a number of
-	other items:</p>
-
-      <ul>
-	<li>Core approved the formation of a wiki-admin team to take
-	  over managing the Wiki, to curate the Wiki content and work
-	  on navigation and organization of existing technical content
-	  and to evaluate new Wiki software with the aim of opening up
-	  the Wiki to contributions from the public.</li>
-
-	<li>An external review board has been assembled to look at
-	  the Code of Conduct, including a mixture of project members
-	  and experts from external groups.  The review process is
-	  getting under way and Core is awaiting their report.</li>
-
-	<li>The standard documentation license was found to be
-	  unfit for its purpose, and the doceng group had temporarily
-	  reverted to the previous license while a new replacement was
-	  drafted.  This new license is now the default for new
-	  documentation submissions.  However, one factor emerging
-	  from this review was the difficulty of maintaining correct
-	  authorial attributions for sections of documentation, some
-	  of which may only be a few words long.  Unlike source code,
-	  blocks of documentation are frequently moved around within
-	  individual files, or even between files.  Consequently, Core
-	  would like to introduce a Voluntary Contribution
-	  Agreement along the lines of the one operated by the
-	  Apache Foundation.  With this, copyrights are signed over to
-	  the FreeBSD Foundation, with individual contributions being
-	  recognised by recording names in a general
-	  "Authors" file.  This will be another alternative
-	  alongside the existing copyright mechanisms used in the
-	  project.  Core is interested to hear any opinions on the
-	  subject.</li>
-
-	<li>Core approved the formation of a new
-	  "dev-announce" mailing list, which all FreeBSD
-	  committers should be members of.  This will be a low-traffic
-	  moderated list to contain important announcements,
-	  heads-ups, warnings of code freezes, changes in policy and
-	  notifications of events that affect the project as a
-	  whole.</li>
-
-	<li>Around eight years ago, an attempt was made to import the
-	  OpenBSD sensors framework.  This was rejected at the time as
-	  potentially blocking the development of a better designed
-	  framework.  However, no such development has occurred in the
-	  intervening time whilst the sensors framework has been in
-	  use successfully by both OpenBSD and FreeNAS.  Despite some
-	  concerns about the efficiency of the framework and potential
-	  impacts on power consumption and hence battery lifetime,
-	  core is minded to approve the import, but wants to consult
-	  with interested developers first.</li>
-
-	<li>Core is exploring the legal ramifications for the project
-	  of the "Right to Be Forgotten" established by
-	  the European Court of Justice.</li>
-
-	<li>Core is also seeking an alternative means for holding
-	  their regular monthly conference calls.  The current,
-	  paid-for, service has less than satisfactory sound quality
-	  and reliability, and Core would like to switch to a free
-	  video conferencing solution.</li>
-      </ul>
-
-      <p>This quarter also saw a particularly large influx of new
-	commit bit requests, with on occasion, four votes running
-	simultaneously.  Please welcome Kurt Lidl, Svatopluk Kraus,
-	Michal Meloun, Jonathan Looney (Juniper), Daisuke Aoyama, Phil
-	Shafer (Juniper), Ravi Pokala (Panasas), Anish Gupta and Mark
-	Bloch (Mellanox) to the ranks of src committers.  In addition,
-	core was delighted to restore commit privileges for Eric
-	Melville after a hiatus of many years.</p>
-
-      <p>No commit bits were taken in during the quarter.  A
-	non-committer account was approved for Kevin Bowling of
-	LimeLight Networks.  Kevin will be doing systems
-	administration work with clusteradm, with particular interest
-	in the parts of the cluster that are now hosted in LLNW's
-	facilities.  Deb Goodkin of the FreeBSD Foundation was added to
-	the developers mailing list: she was one of the few members of
-	the Foundation Board not already on the list, and having
-	awareness of what is going on in the developer community will
-	help her to support the project more effectively.</p>
-    <hr /><h2><a name="The-FreeBSD-Issue-Triage-Team" href="#The-FreeBSD-Issue-Triage-Team" id="The-FreeBSD-Issue-Triage-Team">The FreeBSD Issue Triage Team</a></h2><p>
-	Contact: Bugmeister &lt;<a href="mailto:bugmeister@FreeBSD.org">bugmeister@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kubilay
-	  Kocak
-	 &lt;<a href="mailto:koobs@FreeBSD.org">koobs@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Vladimir
-	  Krstulja
-	 &lt;<a href="mailto:vlad-fbsd@acheronmedia.com">vlad-fbsd@acheronmedia.com</a>&gt;
-	<br />
-	Contact:
-	  Rodrigo N.
-	  Hernandez
-	 &lt;<a href="mailto:rodrigo.FreeBSD@minasambiente.com.br">rodrigo.FreeBSD@minasambiente.com.br</a>&gt;
-	</p>
-      <p>By the end of the Q4 2015 period, Kubilay Kocak (koobs@)
-	started an initiative to form an experimental Bugzilla Triage
-	Team.  The main goals of the team are to increase community
-	involvement (addition/training of new triagers) and enhance
-	current procedures and tools, among others.  This experiment
-	was started with the participation of Vladimir (blackflow on
-	irc/freenode) and Rodrigo (DanDare on irc/freenode), who
-	approached koobs@ with a desire to contribute and get more
-	involved with the FreeBSD Project.  This experimental pilot
-	project has the task of setting up procedures for enhanced
-	Issue (Problem Report) management that include better
-	classification and prioritization, eventually leading to
-	faster resolution of issues.</p>
-
-      <p>We are now happy to report on the progress of this
-	experimental team:</p>
-
-      <ul>
-	<li>The #FreeBSD-bugs IRC channel has been set up on Freenode
-	  and we are successfully using it to exchange information
-	  about triage processes, ask for help, propose changes and
-	  discuss related topics.</li>
-
-	<li>We have identified the primary role of an Issue Triage
-	  Team to be that of classification of problem reports of all
-	  kinds (currently limited mostly to ports and obvious src
-	  issues) and facilitation of issue assignment, which is
-	  making sure that the reported issues are explained well,
-	  contain all the appropriate information (or as much of it as
-	  possible), and are brought to attention of the people who
-	  can act upon them.</li>
-
-	<li>Vladimir and Rodrigo are successfully training in bug
-	  triage as well as porting processes (Vladimir is also taking
-	  maintainership of some ports).</li>
-
-	<li>This experiment is benefiting from the introduction of
-	  newcomers to issue tracking.  It naturally resulted in a
-	  entire review of the tracking process from its very
-	  elementary aspects.  This "fresh eyes"
-	  participation spotted minor details during the process,
-	  giving the opportunity to scrutinize actual procedures on a
-	  number of smaller points, followed by proposals on how to
-	  improve the overall Issue Tracking and Management.  The new
-	  ideas include both organizational and technical ideas and
-	  solutions, such as new or modified keywords or flags for
-	  better classification, the triage workflow, and Bugzilla
-	  technical improvements, among others.</li>
-
-	<li>An important goal is producing documentation about best
-	  practices for using Bugzilla and issue management workflow.
-	  This documentation should be aimed not only at people
-	  directly engaged in issue triage tasks, but also at general
-	  users.  Another relevant point is that feedback from the triage
-	  team can be used to improve Bugzilla in terms of adjusting
-	  existing features to best fit FreeBSD's needs, and the development
-	  of new features (please see Mahdi "Magic"
-	  Mokhtari's report on "Bugzilla
-	  improvements").</li>
-
-	<li>We are still collating ideas in preparation of setting up
-	  a Wiki namespace for the overall topic of issue management,
-	  containing information for all the parties involved in issue
-	  tracking: from users (reporters) to maintainers and
-	  committers.  The unorganized brainstorming document is
-	  linked in this report.</li> </ul>
-
-      <p>Since the Issue Triage Team is very young, we expect more
-	information be available and more actions to be reported in the
-	next status report.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Set up the Wiki namespace and organize the brainstorming
-	  document into a meaningful set of documents.</p>
-      </li><li>
-	<p>We are actively recruiting to grow our FreeBSD Triage Team.
-	  If you are interested in participating and contributing to
-	  one of the most important community-facing areas of the FreeBSD
-	  project, join #freebsd-bugs on the freenode IRC and let us
-	  know!</p>
-
-	<p>Experience with issue tracking is desirable, but not
-	  required.  No prior internal project knowledge or technical
-	  skills are required, just bring your communication skills
-	  and awesome attitude.  Training is provided.</p>
-      </li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="CAM-I/O-Scheduler" href="#CAM-I/O-Scheduler" id="CAM-I/O-Scheduler">CAM I/O Scheduler</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://people.FreeBSD.org/~imp/bsdcan2015/iosched-v3.pdf" title="https://people.FreeBSD.org/~imp/bsdcan2015/iosched-v3.pdf">BSDCan Paper</a></td><td>
-	    URL: <a href="https://people.FreeBSD.org/~imp/bsdcan2015/iosched-v3.pdf" title="BSDCan Paper">https://people.FreeBSD.org/~imp/bsdcan2015/iosched-v3.pdf</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D4609" title="https://reviews.FreeBSD.org/D4609">Phabricator Review</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D4609" title="Phabricator Review">https://reviews.FreeBSD.org/D4609</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Reviews have begun on the CAM I/O scheduler that I wrote
-	for Netflix.  It is anticipated that this process will be done
-	in time for the FreeBSD 11 branch.</p>
-
-      <p>Details about this work can be found in the linked BSDcan
-	paper from last year.</p>
-
-      <p>Briefly, the scheduler allows one to differentiate I/O types
-	and limit I/O based on the type and characteristics of the
-	I/Os (including the latency of recent requests relative to
-	historical averages).  This is most useful when tuning system
-	loads to SSD performance.  Both a simple default scheduler,
-	the same that we use today in FreeBSD, as well as a scheduler
-	that can be well-tuned for system loads related to video
-	streaming will be included.</p>
-    <p>This project was sponsored by Netflix, Inc.</p><hr /><h2><a name="Encrypted-Kernel-Crash-Dumps" href="#Encrypted-Kernel-Crash-Dumps" id="Encrypted-Kernel-Crash-Dumps">Encrypted Kernel Crash Dumps</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.FreeBSD.org/pipermail/freebsd-security/2015-December/008780.html" title="https://lists.FreeBSD.org/pipermail/freebsd-security/2015-December/008780.html">Technical Details</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/pipermail/freebsd-security/2015-December/008780.html" title="Technical Details">https://lists.FreeBSD.org/pipermail/freebsd-security/2015-December/008780.html</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D4712" title="https://reviews.FreeBSD.org/D4712">Patch Review</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D4712" title="Patch Review">https://reviews.FreeBSD.org/D4712</a></td></tr></table><p>
-	Contact:
-	  Konrad
-	  Witaszczyk
-	 &lt;<a href="mailto:def@FreeBSD.org">def@FreeBSD.org</a>&gt;
-	</p>
-      <p>Kernel crash dumps contain information about currently
-	running processes.  This can include sensitive data, for
-	example passwords kept in memory by a browser when a kernel
-	panic occurred.  An entity that can read data from a dump
-	device or a crash directory can also extract this information
-	from a core dump.  To prevent this situation, the core dump
-	should be encrypted before it is stored on the dump
-	device.</p>
-
-      <p>This project allows a kernel to encrypt a core dump during
-	a panic.  A user can configure the kernel for encrypted dumps
-	and save the core dump after reboot using the existing tools,
-	<tt>dumpon(8)</tt> and <tt>savecore(8)</tt>.  A new tool
-	<tt>decryptcore(8)</tt> was added to decrypt the core
-	files.</p>
-
-      <p>A patch has been uploaded to Phabricator for review.  The
-	patch is currently being updated to address the review
-	comments, and should be committed as soon as it is accepted.
-	For more technical details, please visit the FreeBSD-security
-	mailing list archive or see the Phabricator review.</p>
-    <hr /><h2><a name="Jenkins-Continuous-Integration-for-FreeBSD" href="#Jenkins-Continuous-Integration-for-FreeBSD" id="Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://jenkins.FreeBSD.org" title="https://jenkins.FreeBSD.org">The Jenkins CI Server in the FreeBSD Cluster</a></td><td>
-	    URL: <a href="https://jenkins.FreeBSD.org" title="The Jenkins CI Server in the FreeBSD Cluster">https://jenkins.FreeBSD.org</a></td></tr><tr><td><a href="https://github.com/Ultima1252/portest" title="https://github.com/Ultima1252/portest">Portest Script</a></td><td>
-	    URL: <a href="https://github.com/Ultima1252/portest" title="Portest Script">https://github.com/Ultima1252/portest</a></td></tr><tr><td><a href="https://github.com/jenkinsci/workflow-plugin" title="https://github.com/jenkinsci/workflow-plugin">Jenkins Workflow Plugin</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/workflow-plugin" title="Jenkins Workflow Plugin">https://github.com/jenkinsci/workflow-plugin</a></td></tr><tr><td><a href="https://cloudbees.com" title="https://cloudbees.com">Cloudbees</a></td><td>
-	    URL: <a href="https://cloudbees.com" title="Cloudbees">https://cloudbees.com</a></td></tr><tr><td><a href="https://github.com/uber/phabricator-jenkins-plugin" title="https://github.com/uber/phabricator-jenkins-plugin">Jenkins Phabricator Plugin</a></td><td>
-	    URL: <a href="https://github.com/uber/phabricator-jenkins-plugin" title="Jenkins Phabricator Plugin">https://github.com/uber/phabricator-jenkins-plugin</a></td></tr><tr><td><a href="https://github.com/uber/phabricator-jenkins-plugin/pull/110" title="https://github.com/uber/phabricator-jenkins-plugin/pull/110">Phabricator Plugin Fixes</a></td><td>
-	    URL: <a href="https://github.com/uber/phabricator-jenkins-plugin/pull/110" title="Phabricator Plugin Fixes">https://github.com/uber/phabricator-jenkins-plugin/pull/110</a></td></tr><tr><td><a href="https://github.com/jenkinsci/durable-task-plugin/pull/14" title="https://github.com/jenkinsci/durable-task-plugin/pull/14">Durable Task Plugin Fixes</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/durable-task-plugin/pull/14" title="Durable Task Plugin Fixes">https://github.com/jenkinsci/durable-task-plugin/pull/14</a></td></tr><tr><td><a href="https://github.com/jenkinsci/clang-scanbuild-plugin/commits/master" title="https://github.com/jenkinsci/clang-scanbuild-plugin/commits/master">Clang Scanbuild Plugin Fixes</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/clang-scanbuild-plugin/commits/master" title="Clang Scanbuild Plugin Fixes">https://github.com/jenkinsci/clang-scanbuild-plugin/commits/master</a></td></tr><tr><td><a href="https://github.com/jenkinsci/multiple-scms-plugin/commits/master" title="https://github.com/jenkinsci/multiple-scms-plugin/commits/master">Multiple SCMs Plugin Fixes</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/multiple-scms-plugin/commits/master" title="Multiple SCMs Plugin Fixes">https://github.com/jenkinsci/multiple-scms-plugin/commits/master</a></td></tr><tr><td><a href="https://github.com/jenkinsci/scm-sync-configuration-plugin/commits/master" title="https://github.com/jenkinsci/scm-sync-configuration-plugin/commits/master">SCM Sync Configuration Plugin Fixes</a></td><td>
-	    URL: <a href="https://github.com/jenkinsci/scm-sync-configuration-plugin/commits/master" title="SCM Sync Configuration Plugin Fixes">https://github.com/jenkinsci/scm-sync-configuration-plugin/commits/master</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/pipermail/freebsd-testing/2016-January/001285.html" title="https://lists.FreeBSD.org/pipermail/freebsd-testing/2016-January/001285.html">Porting Jobs to the Workflow Plugin</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/pipermail/freebsd-testing/2016-January/001285.html" title="Porting Jobs to the Workflow Plugin">https://lists.FreeBSD.org/pipermail/freebsd-testing/2016-January/001285.html</a></td></tr><tr><td><a href="https://github.com/kohsuke/akuma/pull/9" title="https://github.com/kohsuke/akuma/pull/9">Akuma Fixes for FreeBSD</a></td><td>
-	    URL: <a href="https://github.com/kohsuke/akuma/pull/9" title="Akuma Fixes for FreeBSD">https://github.com/kohsuke/akuma/pull/9</a></td></tr><tr><td><a href="https://github.com/jmmv/kyua/pull/148" title="https://github.com/jmmv/kyua/pull/148">Kyua Fix for Invalid Characters</a></td><td>
-	    URL: <a href="https://github.com/jmmv/kyua/pull/148" title="Kyua Fix for Invalid Characters">https://github.com/jmmv/kyua/pull/148</a></td></tr></table><p>
-	Contact:
-	  Craig
-	  Rodrigues
-	 &lt;<a href="mailto:rodrigc@FreeBSD.org">rodrigc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jenkins Administrators &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Testing &lt;<a href="mailto:FreeBSD-testing@freebsd.org">FreeBSD-testing@freebsd.org</a>&gt;
-	</p>
-      <p>The Jenkins Continuous Integration and Testing project
-	has been helping to improve the quality of FreeBSD.  Since the
-	last status report, we have quickly found commits that caused
-	build breakage or test failures.  FreeBSD developers saw these
-	problems and quickly fixed them.  Some of the highlights
-	include:</p>
-
-      <ul>
-	<li>Ricky Gallagher wrote a script named <tt>portest</tt>,
-	  which can take a patch to the FreeBSD ports tree as input, and
-	  can generate a sequence of commands to check out the ports
-	  tree from Subversion, apply the patch, and then invoke
-	  <tt>poudriere</tt> to build the affected part of the ports
-	  tree.  Ricky consulted with Torsten Z�hlsdorff
-	  during its development.
-	  This script will be used later to test changes to the ports
-	  tree.</li>
-
-	<li>
-	  <p>Craig Rodrigues converted some Jenkins builds to use the
-	    Workflow plugin.  Workflow is a plugin written by Jesse
-	    Glick and other developers at Cloudbees, the main company
-	    providing commercial support for Jenkins.  With this
-	    plugin, a Jenkins job can be written in a Domain Specific
-	    Language (DSL) which is written in the Groovy scripting
-	    language.  Workflow scripts are meant to provide
-	    sophisticated access to Jenkins functionality, in a simple
-	    scripting language.  As Jenkins jobs get more complicated
-	    and have more interdependencies, using a DSL is easier for
-	    maintainability instead of creating Jenkins jobs via
-	    menus.</p>
-
-	  <p>Craig Rodrigues worked with Jesse Glick to identify and fix a
-	    problem with the Durable Task plugin used by the workflow
-	    plugin.  This problem seemed to show up mostly on
-	    non-Linux platforms such as OS X and FreeBSD.</p>
-	</li>
-
-	<li>
-	  <p>Eitan Adler worked with Craig Rodrigues to test a Jenkins
-	    plugin written by Aiden Scandella at Uber which integrates
-	    Phabricator and Jenkins.  With this plugin, if someone
-	    submits a code review with Phabricator's Differential
-	    tool, a Jenkins build with this code change will be
-	    triggered.  The Phabricator code review would then be
-	    updated with the result of the build.</p>
-
-	  <p>Eitan Adler and Craig Rodrigues had some initial success
-	    testing this plugin using the FreeBSD docs repository, but
-	    this plugin still has a lot of hardcoded dependencies
-	    specific to Uber's environment which make it difficult to
-	    use out-of-the-box for FreeBSD.  Alexander Yerenkow submitted
-	    some patches upstream to fix some of these problems, but
-	    this plugin still needs more work.  Craig Rodrigues thinks
-	    that it might be better to write a workflow script to call
-	    Phabricator commands directly.</p>
-	</li>
-
-	<li>
-	  <p>Craig Rodrigues pushed fixes upstream to several
-	    plugins including:</p>
-
-	  <ul>
-	    <li>SCM Sync configuration plugin</li>
-
-	    <li>NodeLabel parameter plugin</li>
-
-	    <li>Subversion plugin</li>
-
-	    <li>Multiple SCMs plugin</li>
-
-	    <li>Clang Scanbuild plugin</li>
-	  </ul>
-
-	  <p>Craig Rodrigues was granted commit access to the SCM
-	    Sync configuration plugin, Multiple SCMs plugin, and Clang
-	    Scanbuild plugin.</p>
-	</li>
-
-	<li>Li-Wen Hsu set up multiple builds using jails on machines
-	  located at NYI and administered by the FreeBSD Cluster
-	  Administrators.  One of these builds targets 64-bit
-	  ARM.</li>
-
-	<li>Michael Zhilin fixed the Akuma library for FreeBSD.  The
-	  Akuma library is used by Jenkins to determine what
-	  command-line arguments were passed to a running process.  To
-	  fix it, Michael invoked an FreeBSD-specific <tt>sysctl()</tt>
-	  with KERN_PROC_ARGS to determine the arguments for a running
-	  pid.  This fix allows a running Jenkins instance to restart
-	  itself after new plugins are installed.</li>
-
-	<li>Julio Merino accepted a fix for Kyua from Craig Rodrigues to fix
-	  writing out XML characters to test report files.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Work more on using the workflow plugin for various
-	  builds.</p>
-      </li><li>
-	<p>Set up a build to test <tt>bmake</tt>'s meta-mode.</p>
-      </li><li>
-	<p>Finish off integration with Phabricator.</p>
-      </li><li>
-	<p>People interested in helping out should join the
-	  freebsd-testing@FreeBSD.org list.</p>
-      </li></ol><hr /><h2><a name="Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support" href="#Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support" id="Mellanox-iSCSI-Extensions-for-RDMA-(iSER)-Support">Mellanox iSCSI Extensions for RDMA (iSER) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/sagigrimberg/iser-FreeBSD" title="https://github.com/sagigrimberg/iser-FreeBSD">GitHub repository</a></td><td>
-	    URL: <a href="https://github.com/sagigrimberg/iser-FreeBSD" title="GitHub repository">https://github.com/sagigrimberg/iser-FreeBSD</a></td></tr></table><p>
-	Contact:
-	  Max
-	  Gurtovoy
-	 &lt;<a href="mailto:maxg@mellanox.com">maxg@mellanox.com</a>&gt;
-	<br />
-	Contact:
-	  Sagi
-	  Grimberg
-	 &lt;<a href="mailto:sagig@mellanox.com">sagig@mellanox.com</a>&gt;
-	</p>
-      <p>Building on the new in-kernel iSCSI initiator stack
-	released in FreeBSD 10.0 and the recently added iSCSI offload
-	interface, Mellanox Technologies has developed iSCSI
-	extensions for RDMA (iSER) initiator support to enable
-	efficient data movement using the hardware offload
-	capabilities of Mellanox's 10, 40, 56, and 100 Gigabit
-	Infiniband (IB)/Ethernet adapters.</p>
-
-      <p>Remote Direct Memory Access (RDMA) has been shown to have
-	great value for storage applications.  RDMA infrastructure
-	provides benefits such as zero-copy, CPU offload, reliable
-	transport, fabric consolidation, and many more.  The iSER
-	protocol eliminates some of the bottlenecks in the traditional
-	iSCSI/TCP stack, provides low latency and high throughput, and
-	is well suited for latency aware workloads.</p>
-
-      <p>This work includes a new ICL module that implements the iSER
-	initiator.  The iSCSI stack is slightly modified to support
-	some extra features such as asynchronous IO completions,
-	unmapped data buffers, and data-transfer offloads.  The user
-	will be able to choose iSER as the iSCSI transport with
-	iscsictl.</p>
-
-      <p>The project is in the process of being merged to FreeBSD
-	11-CURRENT and is expected to ship with FreeBSD 11.0.</p>
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="MIPS:-Ralink/Mediatek-Support" href="#MIPS:-Ralink/Mediatek-Support" id="MIPS:-Ralink/Mediatek-Support">MIPS: Ralink/Mediatek Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/sgalabov/FreeBSD/tree/local/sgalabov_mtk" title="https://github.com/sgalabov/FreeBSD/tree/local/sgalabov_mtk">Github Branch With Work in Progress</a></td><td>
-	    URL: <a href="https://github.com/sgalabov/FreeBSD/tree/local/sgalabov_mtk" title="Github Branch With Work in Progress">https://github.com/sgalabov/FreeBSD/tree/local/sgalabov_mtk</a></td></tr></table><p>
-	Contact:
-	  Stanislav
-	  Galabov
-	 &lt;<a href="mailto:sgalabov@gmail.com">sgalabov@gmail.com</a>&gt;
-	</p>
-      <p>This project is aimed at adding FreeBSD support for
-	Ralink/Mediatek's family of WiFi router system-on-chip (SoC)
-	devices based on MIPS processors.  These SoCs are commonly
-	found in embedded network devices such as WiFi routers.
-	Having support for these SoCs would allow FreeBSD to run on a
-	number of additional low-cost devices, which could help spread
-	FreeBSD's popularity in the embedded systems world.</p>
-
-      <p>The project currently aims to support the following
-	Ralink/Mediatek chipsets: RT3050, RT3052, RT3350, RT3352,
-	RT3662, RT3883, RT5350, RT6855, RT6856, MT7620, MT7621, MT7628
-	and MT7688. The following functionality (where applicable) is
-	currently planned to be supported: Interrupt controller, UART,
-	GPIO, USB, PCI/PCIe, Ethernet, and SPI.</p>
-    <p>This project was sponsored by Smartcom - Bulgaria AD.</p><h3>Open tasks:</h3><ol><li>
-	<p>Help with adding WiFi driver support (possibly to
-	  <tt>ral(4)</tt>) for the above SoCs would be greatly
-	  appreciated.</p>
-      </li><li>
-	<p>Help with refactoring <tt>if_rt(4)</tt> to be usable on
-	  all of the above SoCs would be appreciated.</p>
-      </li><li>
-	<p>Help wth testing target boards (e.g., WiFi routers)
-	  would be appreciated.</p>
-      </li></ol><hr /><h2><a name="Multipath-TCP-for-FreeBSD" href="#Multipath-TCP-for-FreeBSD" id="Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/" title="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/">MPTCP for FreeBSD Repository</a></td><td>
-	    URL: <a href="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/" title="MPTCP for FreeBSD Repository">https://bitbucket.org/nw-swin/caia-mptcp-freebsd/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="http://caia.swin.edu.au/urp/newtcp/mptcp/">MPTCP for FreeBSD Project Website</a></td><td>
-	    URL: <a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="MPTCP for FreeBSD Project Website">http://caia.swin.edu.au/urp/newtcp/mptcp/</a></td></tr></table><p>
-	Contact:
-	  Nigel
-	  Williams
-	 &lt;<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>&gt;
-	</p>
-      <p>Multipath TCP (MPTCP) is an extension to TCP that allows for
-	the use of multiple network interfaces on a standard TCP
-	session.  The addition of new addresses and scheduling of data
-	across these occurs transparently from the perspective of the
-	TCP application.</p>
-
-      <p>The goal of this project is to deliver an MPTCP kernel patch
-	that interoperates with the reference MPTCP implementation,
-	along with additional enhancements to aid network
-	research.</p>
-
-      <p>A v0.51 release has been tagged in our repository, with
-	some minor improvements over v0.5.</p>
-
-      <p>We have now removed much of the MPTCP code that was inside
-	the functions <tt>tcp_do_segment</tt>, <tt>tcp_output</tt>,
-	and other code used for standard TCP connections.  The goal of
-	this is to restrict the added MPTCP code to just MPTCP
-	connections, leaving regular TCP connections using the
-	existing code.</p>
-
-      <p>We are currently in the process of implementing a subflow
-	socket buffer upcall and event processing.  These will handle
-	changes in subflow socket state, MP-signalling, and incoming
-	data segments.</p>
-
-      <p>This also requires some re-working of the MP option
-	processing, particularly how incoming DSN maps are parsed and
-	stored for use during MP-layer reassembly.</p>
-
-      <p>We are also looking at how our changes might take advantage
-	of the new TCP stack modularisation enhancements to create
-	subflow-specific TCP functions.</p>
-    <p>This project was sponsored by The Cisco University Research Program Fund at Community Foundation Silicon Valley, and The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Complete the implementations of subflow event processing
-	  and new option parsing.</p>
-      </li><li>
-	<p>Update documentation and task lists.</p>
-      </li></ol><hr /><h2><a name="OpenBSM" href="#OpenBSM" id="OpenBSM">OpenBSM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openbsm.org" title="http://www.openbsm.org">OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation</a></td><td>
-	    URL: <a href="http://www.openbsm.org" title="OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation">http://www.openbsm.org</a></td></tr><tr><td><a href="https://github.com/openbsm/openbsm" title="https://github.com/openbsm/openbsm">OpenBSM on GitHub</a></td><td>
-	    URL: <a href="https://github.com/openbsm/openbsm" title="OpenBSM on GitHub">https://github.com/openbsm/openbsm</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html">FreeBSD Audit Handbook Chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html" title="FreeBSD Audit Handbook Chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html</a></td></tr></table><p>
-	Contact:
-	  Christian
-	  Brueffer
-	 &lt;<a href="mailto:brueffer@FreeBSD.org">brueffer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: TrustedBSD audit mailing list &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <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 FreeBSD and
-	Mac OS X. Additionally, the audit trail processing tools are
-	expected to work on Linux.</p>
-
-      <p>Progress has been slow but steady this quarter, culminating
-	in OpenBSM 1.2 alpha 4, the first release in three years.  It
-	features various bug fixes and documentation improvements; the
-	complete list of changes is documented in the
-	<a href="https://github.com/openbsm/openbsm/blob/master/NEWS" shape="rect">NEWS</a>
-	file on GitHub.  The release was imported into FreeBSD head and
-	merged to FreeBSD 10-STABLE.  As such, it will be part of FreeBSD
-	10.3-RELEASE.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Test the new release on different versions of FreeBSD, Mac OS
-	  X, and Linux.  In particular, testing on Mac OS X 10.9
-	  (Mavericks) and newer would be greatly appreciated.</p>
-      </li><li>
-	<p>Fix problems that have been reported via GitHub and the
-	  FreeBSD bug tracker.</p>
-      </li><li>
-	<p>Implement features mentioned in the
-	  <a href="https://github.com/openbsm/openbsm/blob/master/TODO" shape="rect">TODO</a>
-	  list on GitHub.</p>
-      </li></ol><hr /><h2><a name="Raspberry-Pi:-VideoCore-Userland-Application-Packaging" href="#Raspberry-Pi:-VideoCore-Userland-Application-Packaging" id="Raspberry-Pi:-VideoCore-Userland-Application-Packaging">Raspberry Pi: VideoCore Userland Application
-      Packaging</a></h2><p>
-	Contact:
-	  Mika�l
-	  Urankar
-	 &lt;<a href="mailto:mikael.urankar@gmail.com">mikael.urankar@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Raspberry Pi SoC consists of two parts: ARM and GPU
-	(VideoCore).  Many interesting features like OpenGL, video
-	playback, and HDMI controls are implemented on the VideoCore
-	side and can be accessed from the OS through libraries
-	provided by Broadcom (userland repo).  These libraries were
-	ported to FreeBSD some time ago, so Mika�l created the port
-	<tt>misc/raspberrypi-userland</tt> for them.  He also created
-	a port for <tt>omxplayer</tt> (a low-level video player that
-	utilizes VideoCore APIs) and is working on a port for Kodi
-	(formerly XBMC), a more user-firendly media player software
-	with Raspberry Pi support.</p>
-    <hr /><h2><a name="RCTL-Disk-IO-Limits" href="#RCTL-Disk-IO-Limits" id="RCTL-Disk-IO-Limits">RCTL Disk IO Limits</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>An important missing piece of the RCTL resource limits
-	mechanism was the ability to limit disk throughput.  This
-	project aims to fill that hole by making it possible to add
-	RCTL rules for read bytes per second (BPS), write BPS, read
-	I/O operations per second (IOPS), and write IOPS.  It also
-	adds a new throttling mechanism to delay process execution
-	when a limit is reached.</p>
-
-      <p>The project is at the late implementation stage.  The major
-	piece of work left apart from testing is to integrate it with
-	ZFS.  The project is expected to ship with FreeBSD 11.0.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Root-Remount" href="#Root-Remount" id="Root-Remount">Root Remount</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=290548" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=290548">Commit to Head</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=290548" title="Commit to Head">https://svnweb.freebsd.org/base?view=revision&amp;revision=290548</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base/head/sbin/reboot/reboot.8?r1=290548&amp;r2=290547&amp;pathrev=290548" title="https://svnweb.freebsd.org/base/head/sbin/reboot/reboot.8?r1=290548&amp;r2=290547&amp;pathrev=290548">reboot(8) Manual Page Changes</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base/head/sbin/reboot/reboot.8?r1=290548&amp;r2=290547&amp;pathrev=290548" title="reboot(8) Manual Page Changes">https://svnweb.freebsd.org/base/head/sbin/reboot/reboot.8?r1=290548&amp;r2=290547&amp;pathrev=290548</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napierala
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>One of the long-missing features of FreeBSD 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, this functionality is known
-	as pivot_root.  The reroot projects provides similar
-	functionality in a different, slightly more user-friendly way:
-	rerooting.  Simply put, from the user point of view it looks
-	like 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 project is finished.  All the relevant code has been
-	committed to FreeBSD 11-CURRENT and is expected to ship with FreeBSD
-	11.0.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Routing-Stack-Update" href="#Routing-Stack-Update" id="Routing-Stack-Update">Routing Stack Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/ProjectsRoutingProposal" title="http://wiki.freebsd.org/ProjectsRoutingProposal">Initial Proposal</a></td><td>
-	    URL: <a href="http://wiki.freebsd.org/ProjectsRoutingProposal" title="Initial Proposal">http://wiki.freebsd.org/ProjectsRoutingProposal</a></td></tr></table><p>
-	Contact:
-	  Alexander
-	  Chernikov
-	 &lt;<a href="mailto:melifaro@FreeBSD.org">melifaro@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>projects/routing</tt> Subversion branch is a FreeBSD
-	routing system rework aimed at providing performance,
-	scalability and the ability to add advanced features to the
-	routing stack.</p>
-
-      <p>The current packet output path suffers from excessive
-	locking.  Acquiring and releasing four distinct contested
-	locks is required to convert a packet to a frame suitable to
-	put on the wire.  The first project goal is to reduce the
-	number of locks needed to just two <tt>rmlock(9)</tt>s for the
-	output path, which permits close-to-linear scaling.</p>
-
-      <p>Since September, one of the locks (used to protect
-	link-level entries) has been completely eliminated from the
-	packet data path.  A new routing API was introduced, featuring
-	better scalability and hiding routing internals.  Most of the
-	consumers of the old routing API were converted to use the new
-	API.</p>
-    <hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Graphics" title="https://wiki.FreeBSD.org/Graphics">Graphics Stack Roadmap and Supported Hardware Matrix</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Graphics" title="Graphics Stack Roadmap and Supported Hardware Matrix">https://wiki.FreeBSD.org/Graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSD/freebsd-ports-graphics" title="https://github.com/FreeBSD/freebsd-ports-graphics">Ports Development Tree on GitHub</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/freebsd-ports-graphics" title="Ports Development Tree on GitHub">https://github.com/FreeBSD/freebsd-ports-graphics</a></td></tr></table><p>
-	Contact: FreeBSD Graphics team &lt;<a href="mailto:freebsd-x11@freebsd.org">freebsd-x11@freebsd.org</a>&gt;
-	</p>
-      <p>Several important ports were updated: Mesa to 11.0.8, the
-	X.Org server to 1.17.4, libdrm to 2.4.65, as well as many
-	applications and libraries.  The latest release of the X.Org
-	server, 1.18, is being tested in our Ports development
-	tree.</p>
-
-      <p>On the kernel side, the i915 update is almost ready to
-	land.  There are a couple known regressions for currently
-	supported GPUs that we want to fix before committing.</p>
-
-      <p>We started a discussion on the FreeBSD-x11@ mailing list to
-	organize future contributions to the kernel drivers.  We have
-	already received some valuable comments.  We are confident
-	that future updates will happen at a faster pace, thanks to
-	several motivated people!</p>
-
-      <p>FOSDEM is held in Brussels on the 30th and 31st of January.
-	We will attend this conference.  It will be a perfect time to
-	see people again from FreeBSD and from the XDC.  On Sunday, we
-	will give a talk about how to contribute to the Graphics
-	Stack.</p>
-
-      <p>Our blog is currently down because the service was
-	discontinued.  We hope to get a dump of our data to put it
-	back online elsewhere.  Unfortunately, there is no ETA for
-	this item.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>See the "Graphics" wiki page for up-to-date
-	  information.</p>
-      </li></ol><hr /><h2><a name="The-nosh-Project" href="#The-nosh-Project" id="The-nosh-Project">The nosh Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html">Introduction</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html" title="Introduction">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html">FreeBSD binary packages</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html" title="FreeBSD binary packages">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html">Installation How-To</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html" title="Installation How-To">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/timorous-admin-installation-how-to.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html">Roadmap</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html" title="Roadmap">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html">Commands</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html" title="Commands">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html">A Slightly Outdated User Guide</a></td><td>
-	    URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html" title="A Slightly Outdated User Guide">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html</a></td></tr><tr><td><a href="https://www.mail-archive.com/supervision@list.skarnet.org/" title="https://www.mail-archive.com/supervision@list.skarnet.org/">The Supervision Mailing List</a></td><td>
-	    URL: <a href="https://www.mail-archive.com/supervision@list.skarnet.org/" title="The Supervision Mailing List">https://www.mail-archive.com/supervision@list.skarnet.org/</a></td></tr></table><p>
-	Contact:
-	  Jonathan
-	  de Boyne Pollard
-	 &lt;<a href="mailto:J.deBoynePollard-newsgroups@NTLWorld.COM">J.deBoynePollard-newsgroups@NTLWorld.COM</a>&gt;
-	</p>
-      <p>The nosh project is a suite of system-level utilities for
-	initializing, running, and shutting down BSD systems, and for
-	managing daemons, terminals, and logging.  It supersedes BSD
-	<tt>init</tt> and the NetBSD <tt>rc.d</tt> system, drawing
-	inspiration from Solaris SMF for named milestones,
-	daemontools-encore for service control/status mechanisms,
-	UCSPI, and IBM AIX for separated service and system
-	management.  It comprises a range of compatibility mechanisms,
-	including shims for familiar commands from other systems, and
-	an automatic import mechanism that takes existing
-	configuration data from <tt>/etc/fstab</tt>,
-	<tt>/etc/rc.conf{,.local}</tt>, <tt>/etc/ttys</tt>, and
-	elsewhere, applying them to its native service definitions and
-	creating additional native services.  It is portable
-	(including to Linux) and composable, it provides a migration
-	path from the world of systemd Linux, and it does not require
-	new kernel APIs.  It provides clean service environments,
-	orderings and dependencies between services, parallelized
-	startup and shutdown (including <tt>fsck</tt>), strictly
-	size-capped and autorotated logging, the service manager as a
-	"subreaper", and uses <tt>kevent(2)</tt> for
-	event-driven parallelism.</p>
-
-      <p>Since the last status report, in October 2015, the project
-	has seen: the complete replacement of its event-handling
-	subsystem on Linux; the introduction of tools for exporting
-	cyclog/multilog logs via RFC 5426 to remote log handlers (such
-	as logstash); and the switching of the user-mode virtual
-	terminal subsystem on BSD to using USB devices directly, a
-	more powerful device interface than sysmouse et al. because it
-	permits directly positioning touch devices for mice and other
-	things (thus permitting "mouse integration" under
-	VirtualBox for those who run PC-BSD/FreeBSD on VirtualBox virtual
-	machines), but sysmouse et al. can still be used if
-	desired.</p>
-
-      <p>In version 1.24, released shortly before publication of this
-	report, there are extensive additions for supporting a
-	purely-ZFS system with an empty <tt>/etc/fstab</tt> (as the
-	PC-BSD 10.2 system installer creates), and the ability to
-	convert <tt>systemd</tt> unit files' process priority settings
-	to BSD's rtprio/idprio.</p>
-
-      <p>Version 1.24 also sees a large chunk taken out of the
-	remainder of the on-going project to create enough native
-	service bundles and ancillary utilities to entirely supplant
-	the <tt>rc.d</tt> system.  The progress of this project has
-	been open from the start, and can be followed on the nosh
-	roadmap web page.  As of version 1.24, there are a mere 27
-	items remaining out of the original target list of 157, with a
-	28th and a 29th (from PC-BSD 10.2) added.  Items crossed off
-	by version 1.24 include (amongst others) <tt>mfs</tt> support
-	for <tt>/tmp</tt>, static ARP and networking, persistent
-	entropy for the randomness subsystem,
-	<tt>pefs</tt>, and <tt>hald</tt>.</p>
-
-      <p>The remaining items in the task list are mostly aimed at
-	making the overall system integration cleaner and friendlier
-	to modern systems.  We are also interested in receiving
-	suggestions, bug reports, and other feedback from users.  Try
-	following the how-to guide and see how things go!</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Add kernel support for passing a <tt>-b</tt> option to
-	  PID 1, and support for a <tt>boot_bare</tt> variable in the
-	  loader, to allow "emergency" (where no shell
-	  dotfiles are loaded) and "rescue" mode bootstraps,
-	  akin to Linux.  (History: the <tt>-b</tt> mechanism and idea
-	  date back to version 2.57d of Miquel van Smoorenburg's
-	  System 5 init clone, dated 1995-12-03, and was already known
-	  as "emergency boot" by 1997.)</p>
-      </li><li>
-	<p>Add support to FreeBSD's <tt>fsck(8)</tt> for outputting
-	  machine-readable progress reports to a designated file
-	  descriptor, so that <tt>nosh</tt> can provide progress bars
-	  for multiple <tt>fsck</tt>s running in parallel.
-	  <tt>nosh</tt> already provides this functionality on Linux,
-	  where <tt>fsck(8)</tt> does provide machine-readable
-	  output.</p>
-      </li><li>
-	<p>Identify when the configuration import system needs to be
-	  triggered, such as when <tt>bsdconfig</tt> alters
-	  configuration files, and create the necessary hooks to
-	  import external configuration changes into nosh.</p>
-      </li></ol><hr /><h2><a name="UEFI-Boot-and-Framebuffer-Support" href="#UEFI-Boot-and-Framebuffer-Support" id="UEFI-Boot-and-Framebuffer-Support">UEFI Boot and Framebuffer Support</a></h2><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>A number of UEFI bug fixes were committed over the last
-	quarter, further improving compatibility with different UEFI
-	implementations.  Specifically: on some implementations, FreeBSD
-	failed to boot with an "ExitBootServices() returned
-	0x8000000000000002" error.  This has been fixed with a
-	retry loop (as required by UEFI) in r292515 and r292338.</p>
-
-      <p>UEFI improvements from other developers have recently been
-	committed or are in progress.  These include support for
-	environment variables set on the EFI loader command line,
-	improved text console mode setting, support for nvram
-	variables, and root-on-ZFS support.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Test FreeBSD-CURRENT snapshots on a variety of UEFI
-	  implementations.</p></li><li>
-	<p>Merge UEFI changes to stable/10 for FreeBSD
-	  10.3-RELEASE.</p>
-      </li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Chelsio-iSCSI-Offload-Driver-(Initiator-and-Target)" href="#Chelsio-iSCSI-Offload-Driver-(Initiator-and-Target)" id="Chelsio-iSCSI-Offload-Driver-(Initiator-and-Target)">Chelsio iSCSI Offload Driver (Initiator and Target)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/292740" title="https://svnweb.freebsd.org/changeset/base/292740">Commit Adding Hardware Acceleration Support</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/292740" title="Commit Adding Hardware Acceleration Support">https://svnweb.freebsd.org/changeset/base/292740</a></td></tr></table><p>
-	Contact:
-	  Navdeep
-	  Parhar
-	 &lt;<a href="mailto:navdeep@chelsio.com">navdeep@chelsio.com</a>&gt;
-	</p>
-      <p>A new driver, <tt>cxgbei</tt>, enabling hardware accelerated
-	iSCSI with Chelsio's T5- and T4-based offload-capable cards,
-	has been committed to head.  Both Initiator and Target are
-	supported.  The wire traffic is standard iSCSI (SCSI over TCP
-	as per RFC 3720, etc.) so an Initiator/Target using this
-	driver will interoperate with all other standards-compliant
-	implementations.</p>
-
-      <p>Hardware assistance provided by the T5 and T4 ASICs
-	includes:</p>
-
-      <ul>
-	<li>Complete TCP processing.</li>
-
-	<li>iSCSI PDU identification and extraction from the byte
-	  oriented TCP stream.</li>
-
-	<li>Header and/or data digest generation and
-	  verification.</li>
-
-	<li>Zero copy support for both transmit and receive.</li>
-      </ul>
-    <p>This project was sponsored by Chelsio Communications.</p><h3>Open tasks:</h3><ol><li>
-	<p>The <tt>cxgbei(4)</tt> man page is missing but will be
-	  committed shortly.</p>
-      </li><li>
-	<p>The driver is in advanced stage QA and will see some
-	  bugfixes and performance enhancements in the very near
-	  future.  MFC is possible as soon as the QA cycle
-	  completes.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-Integration-Services-(BIS)" href="#FreeBSD-Integration-Services-(BIS)" id="FreeBSD-Integration-Services-(BIS)">FreeBSD Integration Services (BIS)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/HyperV" title="https://wiki.FreeBSD.org/HyperV">FreeBSD Virtual Machines on Microsoft Hyper-V</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/HyperV" title="FreeBSD Virtual Machines on Microsoft Hyper-V">https://wiki.FreeBSD.org/HyperV</a></td></tr><tr><td><a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="https://technet.microsoft.com/en-us/library/dn531030.aspx">Linux and FreeBSD Virtual Machines on Hyper-V</a></td><td>
-	    URL: <a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="Linux and FreeBSD Virtual Machines on Hyper-V">https://technet.microsoft.com/en-us/library/dn531030.aspx</a></td></tr></table><p>
-	Contact:
-	  Dexuan
-	  Cui
-	 &lt;<a href="mailto:decui@microsoft.com">decui@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Hongjiang
-	  Zhang
-	 &lt;<a href="mailto:honzhan@microsoft.com">honzhan@microsoft.com</a>&gt;
-	</p>
-      <p>When FreeBSD virtual machines (VMs) run on Hyper-V, using
-	Hyper-V synthetic devices is recommended to get the best
-	network and storage performance and make full use of all the
-	benefits that Hyper-V provides.  The collection of drivers
-	that are required to run Hyper-V synthetic devices in FreeBSD are
-	known as FreeBSD Integration Services (BIS).  Some of the BIS
-	drivers (like network and storage drivers) have existed in
-	FreeBSD 9.x and 10.x for years, but there are still some
-	performance and stability issues and bugs.  Compared with
-	Windows and Linux VMs, the current BIS lacks some important
-	features, such as virtual Receive Side Scaling (vRSS) support
-	in the Hyper-V network driver and support for UEFI VM (boot
-	from UEFI), among others.</p>
-
-      <p>We are now working more on the issues and performance tuning
-	to make FreeBSD VMs run better on Hyper-V and the Hyper-V based
-	cloud platform Azure.</p>
-
-      <p>Our work during 2015Q4 is documented below:</p>
-
-      <ul>
-	<li>Optimizing the VMBus driver and Hyper-V network driver
-	  for performance:
-	  <ul>
-	    <li>Sent out patches to enable <tt>INTR_MPSAFE</tt> for
-	      the interrupt handling thread, speed up relid-to-channel
-	      lookup in the thread by map table, and optimize the
-	      VMBus ringbuffer writable notification to the host.</li>
-
-	    <li>Developing a patch to enable the virtual Receive
-	      Side Scaling (vRSS) for Hyper-V network device driver.
-	      This will greatly improve the network performance for
-	      SMP virtual machine (VM).</li>
-
-	    <li>Sent out a patch to enable the Hyper-V timer, which
-	      will improve the accuracy of timekeeping when FreeBSD VMs
-	      run on Hyper-V.</li>
-	  </ul>
-	</li>
-
-	<li>Fixing bugs and cleaning up the code:
-	  <ul>
-	    <li>Fixed a bug in checksum offloading (PR 203630
-	      &#8212; [Hyper-V] [nat] [tcp] 10.2 NAT bug in TCP stack
-	      or hyperv netsvc driver) in the Hyper-V network driver,
-	      making FreeBSD VM based NAT gateways work more
-	      reliably.</li>
-
-	    <li>Fixed a serialization issue in the initialization of
-	      VMBus devices, fixing PR 205156 ([Hyper-V] NICs' (hn0,
-	      hn1) MAC addresses can appear in an uncertain way across
-	      reboot).</li>
-
-	    <li>Fixed a KVP (Key-Value Pair) issue (retrieving a
-	      key's value can hang for an uncertain period of
-	      time).</li>
-
-	    <li>Added ioctl support for SIOCGIFMEDIA for the Hyper-V
-	      network driver, fixing PR 187006 ([Hyper-V] dynamic
-	      address (DHCP) obtaining does not work on HYPER-V OS
-	      2012 R2).</li>
-
-	    <li>Sent out patches to add an interrupt counter for
-	      Hyper-V VMBus interrupts (so the user can easily get
-	      statistical information about VMBus interrupts),
-	      and fix the KVP daemon's poll timeout (so the daemon
-	      will avoid unnecessary polling every 100
-	      milliseconds.</li>
-
-	    <li>Identified a TSC calibration issue: the i8254 PIT
-	      timer emulation of Hyper-V is not fully reliable, so
-	      the Hyper-V time counter should be used to calibrate
-	      the TSC.  A patch was drafted.  With the patch, it looks
-	      the warning kernel message (e.g., "calcru: runtime
-	      went backwards from 46204978 usec to 23362331 usec for
-	      pid 0 (kernel)") will go away, and the time-based
-	      tracing of Dtrace will be more accurate.</li>
-	  </ul>
-	</li>
-
-	<li>We plan to add support for UEFI VMs (Hyper-V Generation-2
-	  VMs).  Currently some issues and to-do items were
-	  identified.  For example, we cannot use the i8254 PIT to
-	  calibrate the TSC because the i8254 PIT does not exist in a
-	  UEFI VM, and we need to add support for the Hyper-V
-	  synthetic keyboard/mouse/framebuffer device.</li>
-
-	<li>We are working on a disk detection issue: when a FreeBSD VM
-	  runs on a Windows Server 2016 Technical Preview host, the VM
-	  will detect 16 disks when only one disk is configured for
-	  the VM.  VMs running on these hosts can fail to boot.  A
-	  workaround patch was created and we are trying to make a
-	  formal fix.</li>
-
-	<li>We are tidying up some internal BIS test cases and plan
-	  to publish them on github.</li>
-      </ul>
-    <p>This project was sponsored by Microsoft.</p><hr /><h2><a name="FreeBSD-Xen" href="#FreeBSD-Xen" id="FreeBSD-Xen">FreeBSD Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="http://wiki.xen.org/wiki/FreeBSD_PVH">FreeBSD PVH DomU Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="FreeBSD PVH DomU Wiki Page">http://wiki.xen.org/wiki/FreeBSD_PVH</a></td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="http://wiki.xen.org/wiki/FreeBSD_Dom0">FreeBSD PVH Dom0 Wiki Page</a></td><td>
-	    URL: <a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="FreeBSD PVH Dom0 Wiki Page">http://wiki.xen.org/wiki/FreeBSD_Dom0</a></td></tr><tr><td><a href="http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/new_entry_point_v5" title="http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/new_entry_point_v5">FreeBSD/Xen HVMlite Implementation</a></td><td>
-	    URL: <a href="http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/new_entry_point_v5" title="FreeBSD/Xen HVMlite Implementation">http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/new_entry_point_v5</a></td></tr></table><p>
-	Contact:
-	  Roger
-	  Pau Monn�
-	 &lt;<a href="mailto:royger@FreeBSD.org">royger@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Wei
-	  Liu
-	 &lt;<a href="mailto:wei.liu2@citrix.com">wei.liu2@citrix.com</a>&gt;
-	</p>
-      <p>Xen is a hypervisor using a microkernel design, providing
-	services that allow multiple computer operating systems to
-	execute on the same computer hardware concurrently.  Xen
-	support for FreeBSD on x86 as a guest was introduced in version
-	8, and ARM support is currently being worked on.  Support for
-	running FreeBSD as an amd64 Xen host (Dom0) is available in
-	head.</p>
-
-      <p>The x86 work done during this quarter has been focused on
-	rewriting the PVH implementation inside of Xen, into what is
-	now being called HVMlite to differentiate it with the previous
-	PVH implementation.  The Xen side of patches have already been
-	committed to the Xen source tree, and will be available in Xen
-	4.7, the next version.  Work has also begun on implementing
-	HVMlite Dom0 support, although no patches have yet been
-	published.</p>
-
-      <p>HVMlite support for FreeBSD has not yet been committed,
-	although an initial implementation is available in a personal
-	git repository.  The plan is to completely replace PVH with
-	HVMlite on FreeBSD as soon as HVMlite supports Dom0 mode.</p>
-
-      <p>Apart from this, Wei Liu is working on improving netfront
-	performance on FreeBSD.  Initial patches have been posted to the
-	FreeBSD review system.</p>
-
-      <p>The x86 unmapped bounce buffer code has also been improved,
-	and unmapped IO support has been added to the
-	<tt>blkfront</tt> driver.</p>
-    <p>This project was sponsored by Citrix Systems R&amp;D.</p><h3>Open tasks:</h3><ol><li>
-	<p>Finish HVMlite Dom0 support inside of Xen.</p>
-      </li><li>
-	<p>Deprecate and remove PVH support from Xen.</p>
-      </li><li>
-	<p>Remove PVH support from FreeBSD and switch to HVMlite.</p>
-      </li><li>
-	<p>Generalize the event channel code so it can be used on
-	  ARM.</p>
-      </li><li>
-	<p>Improve the performance of the various backends
-	  (<tt>netback</tt>, <tt>blkback</tt>).</p>
-      </li></ol><hr /><h2><a name="Improvements-to-the-QLogic-HBA-Driver" href="#Improvements-to-the-QLogic-HBA-Driver" id="Improvements-to-the-QLogic-HBA-Driver">Improvements to the QLogic HBA Driver</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>The QLogic HBA driver, <tt>isp(4)</tt>, received a
-	substantial set of changes.  The primary goal was to make the
-	Fibre Channel target role work well with CTL, but many other
-	things were also fixed/improved:</p>
-
-      <ul>
-	<li>Added support for modern 16Gbps 26xx FC cards.</li>
-
-	<li>The firmware in <tt>ispfw(4)</tt> were updated to the
-	  latest versions.</li>
-
-	<li>Target role support was fixed and tested for all FC cards
-	  from ancient 1Gbps 22xx to modern 16Gbps 26xx.</li>
-
-	<li>Port database handling was unified for target and
-	  initiator roles, allowing an HBA port to play both roles at the
-	  same time.</li>
-
-	<li>The maximal number of ports was increased from 256 to
-	  1024.</li>
-
-	<li>Multi-ID (NPIV) functionality was fixed/implemented,
-	  allowing 24xx and above cards to provide up to 255 virtual
-	  FC ports per physical port.</li>
-
-	<li>Added support for 8-byte LUNs for 24xx and above
-	  cards.</li>
-      </ul>
-
-      <p>The code is committed to FreeBSD head and stable/10
-	branches.</p>
-    <p>This project was sponsored by iXsystems, Inc..</p><h3>Open tasks:</h3><ol><li>
-	<p>NVRAM data reading is hackish and requires rework.</p>
-      </li><li>
-	<p>FCoE support for 26xx cards was not tested yet.</p>
-      </li></ol><hr /><h2><a name="iMX.6-Video-Output-Support" href="#iMX.6-Video-Output-Support" id="iMX.6-Video-Output-Support">iMX.6 Video Output Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.FreeBSD.org/changeset/base/292574" title="https://svnweb.FreeBSD.org/changeset/base/292574">Commit Adding Basic Video Support</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/changeset/base/292574" title="Commit Adding Basic Video Support">https://svnweb.FreeBSD.org/changeset/base/292574</a></td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>iMX.6 is a family of SoC used in multiple hobbyist ARM boards
-	such as the Hummingboard, RIoTboard, and Cubox.  Most of these
-	products have HDMI output, but until recently, FreeBSD did not
-	benefit from it.  As of r292574, there is basic video output
-	support so you can use the console on iMX6-based boards and
-	probably run Xorg (not yet tested).</p>
-
-      <p>Due to the lack of some kernel functionality (see open
-	tasks), the only supported mode is 1024x768.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Proper pixel clock initialization (relies on a clock
-	  framework).</p>
-      </li><li>
-	<p>More flexible video output path (support multiple IPUs
-	  and DIs).</p>
-      </li></ol><hr /><h2><a name="ioat(4)-Driver-Enhancements" href="#ioat(4)-Driver-Enhancements" id="ioat(4)-Driver-Enhancements">ioat(4) Driver Enhancements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology" title="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology">Wikipedia on I/OAT</a></td><td>
-	    URL: <a href="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology" title="Wikipedia on I/OAT">https://en.wikipedia.org/wiki/I/O_Acceleration_Technology</a></td></tr><tr><td><a href="https://www.FreeBSD.org/status/report-2015-07-2015-09.html#ioat%284%29-Driver-Import" title="https://www.FreeBSD.org/status/report-2015-07-2015-09.html#ioat%284%29-Driver-Import">Last quarter's ioat(4) report</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/status/report-2015-07-2015-09.html#ioat%284%29-Driver-Import" title="Last quarter's ioat(4) report">https://www.FreeBSD.org/status/report-2015-07-2015-09.html#ioat%284%29-Driver-Import</a></td></tr></table><p>
-	Contact:
-	  Conrad
-	  Meyer
-	 &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	</p>
-      <p>I/OAT DMA engines are bulk memory operation offload engines
-	built into some Intel Server/Storage platform CPUs.</p>
-
-      <p>Several enhancements were made to the driver.  It now avoids
-	memory allocation in locked paths, which should avoid
-	deadlocking in memory pressure scenarios.  Support for
-	Broadwell-EP devices has been added.  The
-	"blockfill" operation and a non-contiguous 8 KB copy
-	operation have been added to the API.  The driver can recover
-	from various programming errors by resetting the hardware.</p>
-    <p>This project was sponsored by EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li>
-	<p>XOR and other advanced ("RAID") operation
-	  support.</p>
-      </li></ol><hr /><h2><a name="Kernel-Vnode-Cache-Tuning" href="#Kernel-Vnode-Cache-Tuning" id="Kernel-Vnode-Cache-Tuning">Kernel Vnode Cache Tuning</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/rS292895" title="https://reviews.FreeBSD.org/rS292895">MFC to stable/10</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/rS292895" title="MFC to stable/10">https://reviews.FreeBSD.org/rS292895</a></td></tr></table><p>
-	Contact:
-	  Kirk
-	  McKusick
-	 &lt;<a href="mailto:mckusick@mckusick.com">mckusick@mckusick.com</a>&gt;
-	<br />
-	Contact:
-	  Bruce
-	  Evans
-	 &lt;<a href="mailto:bde@FreeBSD.org">bde@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Peter
-	  Holm
-	 &lt;<a href="mailto:pho@FreeBSD.org">pho@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mateusz
-	  Guzik
-	 &lt;<a href="mailto:mjg@FreeBSD.org">mjg@FreeBSD.org</a>&gt;
-	</p>
-      <p>This completed project includes changes to better manage
-	the vnode freelist and to streamline the allocation and
-	freeing of vnodes.</p>
-
-      <p>Vnode cache recycling was reworked to meet free and unused
-	vnode targets.  Free vnodes are rarely completely free;
-	rather, they are just ones that are cheap to recycle.  Usually
-	they are for files which have been stat'd but not read; these
-	usually have inode and namecache data attached to them.  The
-	free vnode target is the preferred minimum size of a sub-cache
-	consisting mostly of such files.  The system balances the size
-	of this sub-cache with its complement to try to prevent either
-	from thrashing while the other is relatively inactive.  The
-	targets express a preference for the best balance.</p>
-
-      <p>"Above" this target there are 2 further targets
-	(watermarks) related to the recyling of free vnodes.  In the
-	best-operating case, the cache is exactly full, the free list
-	has size between vlowat and vhiwat above the free target, and
-	recycling from the free list and normal use maintains this
-	state.  Sometimes the free list is below vlowat or even empty,
-	but this state is even better for immediate use, provided the
-	cache is not full.  Otherwise, <tt>vnlru_proc()</tt> runs to
-	reclaim enough vnodes (usually non-free ones) to reach one of
-	these states.  The watermarks are currently hard-coded as 4%
-	and 9% of the available space.  These, and the default of 25%
-	for wantfreevnodes, are too large if the memory size is large.
-	For example, 9% of 75% of MAXVNODES is more than 566000 vnodes
-	to reclaim whenever <tt>vnlru_proc()</tt> becomes active.</p>
-
-      <p>The <tt>vfs.vlru_alloc_cache_src</tt> sysctl is removed.  The new
-	code frees namecache sources as the last chance to satisfy the
-	highest watermark, instead of selecting source vnodes
-	randomly.  This provides good enough behavior to keep
-	<tt>vn_fullpath()</tt> working in most situations.  Filesystem
-	layouts with deep trees, where the removed knob was required,
-	are thus handled automatically.</p>
-
-      <p>As the kernel allocates and frees vnodes, it fully
-	initializes them on every allocation and fully releases them
-	on every free.  These are not trivial costs: it starts by
-	zeroing a large structure, then initializes a mutex, a lock
-	manager lock, an rw lock, four lists, and six pointers.
-	Looking at <tt>vfs.vnodes_created</tt>, these operations are
-	being done millions of times an hour on a busy machine.</p>
-
-      <p>As a performance optimization, this code update uses the
-	uma_init and uma_fini routines to do these initializations and
-	cleanups only as the vnodes enter and leave the vnode zone.
-	With this change, the initializations are done
-	<tt>kern.maxvnodes</tt> times at system startup, and then only
-	rarely again.  The frees are done only if the vnode zone
-	shrinks, which never happens in practice.  For those curious
-	about the avoided work, look at the <tt>vnode_init()</tt> and
-	<tt>vnode_fini()</tt> functions in sys/kern/vfs_subr.c to see
-	the code that has been removed from the main vnode
-	allocation/free path.</p>
-    <hr /><h2><a name="Mellanox-Drivers" href="#Mellanox-Drivers" id="Mellanox-Drivers">Mellanox Drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mellanox.com/page/ethernet_cards_overview" title="http://www.mellanox.com/page/ethernet_cards_overview">Hardware Information</a></td><td>
-	    URL: <a href="http://www.mellanox.com/page/ethernet_cards_overview" title="Hardware Information">http://www.mellanox.com/page/ethernet_cards_overview</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/changeset/base/290650" title="https://svnweb.FreeBSD.org/changeset/base/290650">Commit Adding the Driver</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/changeset/base/290650" title="Commit Adding the Driver">https://svnweb.FreeBSD.org/changeset/base/290650</a></td></tr></table><p>
-	Contact:
-	  Hans Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Mellanox FreeBSD team is proud to announce support for the
-	ConnectX-4 series of network cards in FreeBSD 11-current and FreeBSD
-	10-stable.  These devices deliver top performance, with up to
-	100GBit/s of raw transfer capacity, and support both Ethernet
-	and Infiniband.  Currently, the Ethernet driver is ready for
-	use and the Infiniband support for ConnectX-4 is making good
-	progress.  We hope that it will be complete before FreeBSD 11.0
-	is released.  For more technical information, refer to the
-	<tt>mlx5en(4)</tt> manual page in 11-current.  The new driver
-	for ConnectX-4 cards is called <tt>mlx5</tt> and is put under
-	<tt>/sys/dev</tt> and not under <tt>/sys/ofed</tt> as was done
-	for the previous <tt>mlx4</tt> driver.  The <tt>mlx5en(4)</tt>
-	kernel module is compiled by default in GENERIC kernels.</p>
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="Minimal-Kernel-with-PNP-Based-Autoloading" href="#Minimal-Kernel-with-PNP-Based-Autoloading" id="Minimal-Kernel-with-PNP-Based-Autoloading">Minimal Kernel with PNP-Based Autoloading</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bsdimp.blogspot.com/2016/01/details-on-coming-automatic-module.html" title="http://bsdimp.blogspot.com/2016/01/details-on-coming-automatic-module.html">Blog Post</a></td><td>
-	    URL: <a href="http://bsdimp.blogspot.com/2016/01/details-on-coming-automatic-module.html" title="Blog Post">http://bsdimp.blogspot.com/2016/01/details-on-coming-automatic-module.html</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on automatically loading modules based on the
-	plug-and-play data from devices that are scanned and found to
-	not already have a driver attached is in progress.  Digging
-	this information out from kernel modules, as well as tagging
-	relevant bits of driver tables, has been committed.  PC Card,
-	USB, and some PCI devices now have these markings.  This data
-	is stored in a file that the kernel, boot loader, and userland
-	processes all can access.</p>
-
-      <p>When complete, a user will be able to run a minimal kernel
-	(currently checked in as the <tt>MINIMAL</tt> config).
-	Devices necessary for booting will be loaded by
-	<tt>loader(8)</tt>.  Other devices may be loaded there, or
-	early in the boot (depending on which gives better
-	performance).  Users will still be able to run more
-	monolithic; configurations, as well as limit which
-	kernel modules are available as can be done today, though
-	without the convenience that automatic loading will provide.
-	This work remains ongoing.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Go through all the simplebus drivers and add plug-and-play
-	  information there.  Some additional minor simplebus
-	  functionality is needed.  There is some work in progress for
-	  this.</p>
-      </li><li>
-	<p>Go through all the PCI drivers and add plug-and-play
-	  information to them.  Unlike PC Card or USB, the PCI bus
-	  does not have a stylized table of PCI IDs, so each driver
-	  invents its own method, meaning that the semi-mechanical
-	  conversion that was done with PC Card and USB will not be
-	  possible.  Instead, customized code for each driver will be
-	  needed.  Since a large number of drivers have their own
-	  device tables, the work will be primarily writing a
-	  description of the current table style.</p>
-      </li><li>
-	<p>Run-time parsing and loading is still needed.</p>
-      </li></ol><hr /><h2><a name="MMC-Stack-Under-CAM-Framework" href="#MMC-Stack-Under-CAM-Framework" id="MMC-Stack-Under-CAM-Framework">MMC Stack Under CAM Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bakulin.de/freebsd/mmccam.html" title="https://bakulin.de/freebsd/mmccam.html">Project Information</a></td><td>
-	    URL: <a href="https://bakulin.de/freebsd/mmccam.html" title="Project Information">https://bakulin.de/freebsd/mmccam.html</a></td></tr><tr><td><a href="https://github.com/kibab/FreeBSD/tree/mmccam" title="https://github.com/kibab/FreeBSD/tree/mmccam">Source Code</a></td><td>
-	    URL: <a href="https://github.com/kibab/FreeBSD/tree/mmccam" title="Source Code">https://github.com/kibab/FreeBSD/tree/mmccam</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D4761" title="https://reviews.FreeBSD.org/D4761">Patch for Review</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D4761" title="Patch for Review">https://reviews.FreeBSD.org/D4761</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>The goal of this project is to reimplement the existing
-	MMC/SD stack using the CAM framework.  This will permit
-	utilizing the well-tested CAM locking model and debug
-	features.  It will also be possible to process interrupts
-	generated by the inserted card, which is a prerequisite for
-	implementing the SDIO interface.</p>
-
-      <p>The first version of the code was uploaded to Phabricator for
-	review.  The new stack is able to attach to the SD card and
-	bring it to an operational state so it is possible to read and
-	write to the card.</p>
-
-      <p>The only supported SD controller driver is <tt>ti_sdhci</tt>,
-	which is used on the BeagleBone Black.  Modifying other
-	SDHCI-compliant drivers should not be difficult.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Rework bus/target/LUN enumeration and the locking model.
-	  I do not really understand the CAM locking and am likely to
-	  do it incorrectly.</p>
-      </li><li>
-	<p>Modify the SDHCI driver on at least one x86 platform.
-	  This will make development and collaboration easier.</p>
-      </li><li>
-	<p>Begin implementing SDIO-specific bits.</p>
-      </li></ol><hr /><h2><a name="ntb_hw(4)/if_ntb(4)-Driver-Synced-up-to-Linux" href="#ntb_hw(4)/if_ntb(4)-Driver-Synced-up-to-Linux" id="ntb_hw(4)/if_ntb(4)-Driver-Synced-up-to-Linux">ntb_hw(4)/if_ntb(4) Driver Synced up to
-      Linux</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/jonmason/ntb/wiki" title="https://github.com/jonmason/ntb/wiki">Jon Mason's NTB wiki</a></td><td>
-	    URL: <a href="https://github.com/jonmason/ntb/wiki" title="Jon Mason's NTB wiki">https://github.com/jonmason/ntb/wiki</a></td></tr><tr><td><a href="https://www-ssl.intel.com/content/dam/www/public/us/en/documents/white-papers/xeon-c5500-c3500-non-transparent-bridge-paper.pdf" title="https://www-ssl.intel.com/content/dam/www/public/us/en/documents/white-papers/xeon-c5500-c3500-non-transparent-bridge-paper.pdf">Intel NTB whitepaper</a></td><td>
-	    URL: <a href="https://www-ssl.intel.com/content/dam/www/public/us/en/documents/white-papers/xeon-c5500-c3500-non-transparent-bridge-paper.pdf" title="Intel NTB whitepaper">https://www-ssl.intel.com/content/dam/www/public/us/en/documents/white-papers/xeon-c5500-c3500-non-transparent-bridge-paper.pdf</a></td></tr></table><p>
-	Contact:
-	  Conrad
-	  Meyer
-	 &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>ntb_hw(4)</tt> is now up-to-date with the Linux NTB
-	driver as of the work-in-progress 4.4 kernel (and actually,
-	contains some fixes that haven't landed in the mainline Linux
-	tree yet but will land in 4.5).  Only Back-to-back
-	("B2B") configurations are supported at this time.
-	Going forward, newer hardware may only support the B2B
-	configuration.</p>
-
-      <p><tt>if_ntb(4)</tt> is mostly up-to-date with the Linux NTB
-	netdevice driver.  Notably absent is support for changing the
-	MTU at runtime.</p>
-    <p>This project was sponsored by EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li>
-	<p>Improving <tt>if_ntb(4)</tt> to avoid using the entire Base
-	  Address Register (BAR) when very large BAR sizes are
-	  configured (e.g., 512 GB).</p>
-      </li><li>
-	<p>Improving <tt>pmap_mapdev(9)</tt> to somehow allocate only
-	  superpage mappings for large BARs, on platforms that support
-	  superpages.  (NTB BARs can be as large as 512 GB.)</p>
-      </li></ol><hr /><h2><a name="Out-of-Memory-Handler-Rewrite" href="#Out-of-Memory-Handler-Rewrite" id="Out-of-Memory-Handler-Rewrite">Out of Memory Handler Rewrite</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Out of Memory (OOM) code is intended to handle the
-	situation where the system needs free memory to make progress,
-	but no memory can be reused.  Most often, the situation is
-	that to free memory, the system needs more free memory.
-	Consider a case where the system needs to page-out dirty
-	pages, but needs to allocate structures to track the writes.
-	OOM "solves" the problem by killing some selection
-	of user processes.  In other words, it trades away system
-	deadlock by suffering a partial loss of user data.  The
-	assumption is that it is better to kill a process and recover
-	data in other processes than to lose everything.</p>
-
-      <p>Free memory in the FreeBSD Virtual Memory (VM) system appears
-	from two sources.  One is the voluntary reclamation of pages
-	used by a process, for example unmapping private anonymous
-	regions, or the last unlink of an otherwise unreferenced file
-	with cached pages.  Another source is the pagedaemon, which
-	forcefully frees pages which carry data, of course after the
-	data is moved to some other storage, like swap or file blocks.
-	OOM is triggered when the pagedaemon definitely cannot free
-	memory to satisfy the requests.</p>
-
-      <p>The old criteria to trigger the OOM action was a combination
-	of low free swap space and a low count of free pages (the
-	latter is expressed precisely with the paging targets
-	constants, but this is not relevant to the discussion).  That
-	test is mostly incorrect.  For example, a low free page state
-	might be caused by a greedy consumer allocating all pages
-	freed by the page daemon in the current pass, but this does
-	not preclude the page daemon from producing more pages.  Also,
-	since page-outs are asynchronous, the previous page daemon
-	pass might not immmediately produce any free pages, but they
-	would appear some short time later.</p>
-
-      <p>More seriously, low swap space does not necessarily indicate
-	that we are in trouble: lots of pages might not require swap
-	allocations to be freed, like clean pages or pages backed by
-	files.  The last notion is serious, since swap-less systems
-	were considered as having full swap.</p>
-
-      <p>Instead of trying to deduce the deadlock from looking at the
-	current VM state, the new OOM handler tracks the history of
-	page daemon passes.  Only when several consecutive passes
-	failed to meet the paging target is an OOM kill considered
-	necessary.  The count of consequent failed passes was selected
-	empirically, by testing on small (32M) and large (512G)
-	machines.  Auto-tuning of the counter is possible, but
-	requires some more architectural changes to the I/O
-	subsystem.</p>
-
-      <p>Another issue was identified with the algorithm which selects
-	a victim process for OOM kill.  It compared the counts of
-	pages mapping entries (PTEs) installed into the machine paging
-	structures.  For different reasons, the machine-dependent VM code
-	(pmap) may remove the pte for a memory-resident page.  Under
-	some circumstances related to other measures to prevent low
-	memory deadlock, very large processes which consume all system
-	memory could have few or no ptes.  The old OOM selector
-	ignored the process which caused the deadlock, killing
-	unrelated processes.</p>
-
-      <p>A new function, <tt>vm_pageout_oom_pagecount()</tt>, was
-	written which applies a reasonable heuristic to estimate the
-	number of pages freed by killing the given process.  This
-	eliminates the effect of selecting small unrelated processes
-	for OOM kill.</p>
-
-      <p>The rewrite was committed to head in r290917 and r290920.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="sendfile(2)-Improvements" href="#sendfile(2)-Improvements" id="sendfile(2)-Improvements">sendfile(2) Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=293439" title="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=293439">Commit to Head</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=293439" title="Commit to Head">https://svnweb.FreeBSD.org/base?view=revision&amp;revision=293439</a></td></tr><tr><td><a href="http://www.slideshare.net/facepalmtarbz2/new-sendfile-in-english" title="http://www.slideshare.net/facepalmtarbz2/new-sendfile-in-english">Slides</a></td><td>
-	    URL: <a href="http://www.slideshare.net/facepalmtarbz2/new-sendfile-in-english" title="Slides">http://www.slideshare.net/facepalmtarbz2/new-sendfile-in-english</a></td></tr><tr><td><a href="https://events.yandex.ru/lib/talks/2682/" title="https://events.yandex.ru/lib/talks/2682/">Presentation (in Russian)</a></td><td>
-	    URL: <a href="https://events.yandex.ru/lib/talks/2682/" title="Presentation (in Russian)">https://events.yandex.ru/lib/talks/2682/</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Smirnoff
-	 &lt;<a href="mailto:glebius@FreeBSD.org">glebius@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>sendfile(2)</tt> system call was introduced in
-	1998 as an alternative to a traditional
-	<tt>read(2)</tt>/<tt>write(2)</tt> loop, speeding up server
-	performance by a factor of ten at the time.  Since it was
-	adopted by all major operating systems, it is now used by any
-	serious web server software.  Wherever there is high traffic,
-	there is <tt>sendfile(2)</tt> under the hood.</p>
-
-      <p>Now, with FreeBSD 11, we are making the next revolutinary step
-	in serving traffic.  <tt>sendfile(2)</tt> no longer blocks
-	waiting on disk I/O.  Instead, it immediately returns control
-	to the application, performing the necessary I/O in the
-	background.  The original <tt>sendfile(2)</tt> waited for the
-	disk read operation to complete and then put the data that was
-	read into the socket, then returned to userspace.  If a web
-	server served thousands of clients with thousands of requests,
-	it was forced to spawn extra contexts from which to run
-	<tt>sendfile(2)</tt> to avoid stalls.  Alternatively, it could
-	use special tricks like the <tt>SF_NODISKIO</tt> flag that
-	forces <tt>sendfile(2)</tt> to serve only content that is
-	cached in memory.  Now, these tricks are in the past, and a
-	web server can simply use <tt>sendfile(2)</tt> as it would use
-	<tt>write(2)</tt>, without any extra care.  The new sendfile
-	cuts out the overhead of extra contexts, short writes, and
-	extra syscalls to prepopulate the cache, bringing performance
-	to a new level.</p>
-
-      <p>The new syscall is built on top of two newly-introduced
-	kernel features.  The first is an asynchronous VM pager
-	interface and the corresponding <tt>VOP_GETPAGES_ASYNC()</tt>
-	file system method for UFS.  The second is the concept of
-	"not ready" data in sockets.  When
-	<tt>sendfile(2)</tt> is called, first
-	<tt>VOP_GETPAGES_ASYNC()</tt> is called, which dispatches I/O
-	requests for completion.  Buffers with pages to be populated
-	are put into the socket buffer, but flagged as not-yet-ready.
-	Control immediately returns to the application.  When the I/O
-	is finished, the buffers are marked as ready, and the socket
-	is activated to continue transmission.</p>
-
-      <p>Additional features of the new <tt>sendfile</tt> are new
-	flags that provide the application with extra control over the
-	transmitted content.  Now it is possible to prevent caching of
-	content in memory, which is useful when it is known that the
-	content is unlikely to be reused any time soon.  In such
-	cases, it is better to let the associated storage be freed,
-	rather than putting the data in cache.  It is also possible to
-	specify a readahead with every syscall, if the application can
-	predict client behavior.</p>
-
-      <p>The new <tt>sendfile(2)</tt> is a drop-in replacement, API
-	and ABI compatible with the old one.  Applications do not even
-	need to recompile to benefit from the new implementation.</p>
-
-      <p>This work is a joint effort between two companies: NGINX,
-	Inc., and Netflix.  There were many people involved in the
-	project.  At its initial stage, before code was written, the
-	idea of such an asynchronous drop-in replacement was discussed
-	amongst Gleb Smirnoff, Scott Long, Konstantin Belousov, Adrian Chadd, and Igor
-	Sysoev.  The initial prototype was coded by Gleb under the
-	supervision of Kostik on the VM parts of the patch, and under
-	constant pressure from Igor, who demanded that <tt>nginx</tt> be
-	capable of running with the new <tt>sendfile(2)</tt> with no
-	modifications.  The prototype demonstrated good performance
-	and stability and quickly went into Netflix production in late
-	2014.  During 2015, the code matured and continued serving
-	production traffic at Netflix.  Scott Long, Randall R. Stewart, Maksim Yevmenkin,
-	and Andrew Gallatin added their contributions to the code.</p>
-
-      <p>Now we are releasing the code behind our success to the
-	FreeBSD community, making it available to all FreeBSD users
-	worldwide!</p>
-    <p>This project was sponsored by Netflix, and NGINX, Inc..</p><h3>Open tasks:</h3><ol><li>
-	<p><tt>SSL_sendfile()</tt> &#8212; an extension to the new
-	  <tt>sendfile(2)</tt> that allows uploading session keys to
-	  the kernel, and then using <tt>sendfile(2)</tt> on an
-	  SSL-enabled socket.</p>
-      </li></ol><hr /><h2><a name="sysctl-Enhancements" href="#sysctl-Enhancements" id="sysctl-Enhancements">sysctl Enhancements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://en.wikipedia.org/wiki/C_data_types#Fixed-width_integer_types" title="https://en.wikipedia.org/wiki/C_data_types#Fixed-width_integer_types">Wikipedia Entry on C99 Fixed-Width Integer Types</a></td><td>
-	    URL: <a href="https://en.wikipedia.org/wiki/C_data_types#Fixed-width_integer_types" title="Wikipedia Entry on C99 Fixed-Width Integer Types">https://en.wikipedia.org/wiki/C_data_types#Fixed-width_integer_types</a></td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=203918" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=203918">sysctl(8) -t Submission PR</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=203918" title="sysctl(8) -t Submission PR">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=203918</a></td></tr></table><p>
-	Contact:
-	  Conrad
-	  Meyer
-	 &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ravi
-	  Pokala
-	 &lt;<a href="mailto:rpokala@FreeBSD.org">rpokala@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Marcelo
-	  Araujo
-	 &lt;<a href="mailto:araujo@FreeBSD.org">araujo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support was added for fixed-width sysctls (signed and
-	unsigned 8-bit, 16-bit, 32-bit, and 64-bit integers).  The new
-	KPIs are documented in the <tt>sysctl(9)</tt> manual page.
-	The <tt>sysctl(8)</tt> command line tool supports all of the
-	new types.</p>
-
-      <p><tt>sysctl(8)</tt> gained the <tt>-t</tt> flag, which prints
-	sysctl type information (the original patch was submitted by
-	Yoshihiro Ota).  This support includes the newly added
-	fixed-width types.</p>
-    <p>This project was sponsored by EMC / Isilon Storage Division.</p><hr /><h2><a name="Touchscreen-Support-for-Raspberry-Pi-and-Beaglebone-Black" href="#Touchscreen-Support-for-Raspberry-Pi-and-Beaglebone-Black" id="Touchscreen-Support-for-Raspberry-Pi-and-Beaglebone-Black">Touchscreen Support for Raspberry Pi and Beaglebone
-      Black</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://kernelnomicon.org/?p=534" title="http://kernelnomicon.org/?p=534">Beaglebone Black with 4DCAPE-43T Demo</a></td><td>
-	    URL: <a href="http://kernelnomicon.org/?p=534" title="Beaglebone Black with 4DCAPE-43T Demo">http://kernelnomicon.org/?p=534</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/201510DevSummit/GraphicsStack" title="https://wiki.FreeBSD.org/201510DevSummit/GraphicsStack">Input Stack Plans</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/201510DevSummit/GraphicsStack" title="Input Stack Plans">https://wiki.FreeBSD.org/201510DevSummit/GraphicsStack</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens" title="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens">evdev Port</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens" title="evdev Port">https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens</a></td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are two working proof-of-concept drivers for the
-	AM335x touchscreen and for the official Raspberry Pi's
-	touchscreen LCD.</p>
-
-      <p>Proper touchscreen support would consist of a userland event
-	reading API, a kernel event reporting API, and kernel hardware
-	drivers for specific devices.  There is an ongoing effort to
-	port the Linux <tt>evdev</tt> API to FreeBSD so applications that use
-	libraries like libinput or tslib could be used without any
-	major changes.  Since it is not yet complete, I created a
-	naive <tt>evdev</tt>-like API for both kernel and tslib and was able to
-	run a demo on a Beaglebone Black with 4DCAPE-43T.</p>
-
-      <p>Once <tt>evdev</tt> makes it into the tree, both hardware drivers
-	can be modified to include "report events"
-	portions and committed.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="armv6-Hard-Float-Default-ABI" href="#armv6-Hard-Float-Default-ABI" id="armv6-Hard-Float-Default-ABI">armv6 Hard Float Default ABI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bsdimp.blogspot.com/2015/12/hard-float-api-coming-soon-by-default.html" title="http://bsdimp.blogspot.com/2015/12/hard-float-api-coming-soon-by-default.html">Blog Entry</a></td><td>
-	    URL: <a href="http://bsdimp.blogspot.com/2015/12/hard-float-api-coming-soon-by-default.html" title="Blog Entry">http://bsdimp.blogspot.com/2015/12/hard-float-api-coming-soon-by-default.html</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work on moving armv6 from a "soft float" ABI (but
-	still using hardware floating point) to a fully "hardware
-	float" API moves forward.  The ability to have both soft
-	and hard ABI libraries on the same system is now functional.
-	All armv6 and armv7 systems we support have hardware floating
-	point capabilities.  We currently use the floating-point
-	hardware, but with a slightly un-optimal ABI, for
-	compatibility with older versions of FreeBSD.  The ABI
-	differences are only at the userspace level &#8212; the kernel
-	does not care what floating-point ABI is used, and both types
-	of binaries can run at the same time.</p>
-
-      <p>The run-time linker now knows if a binary uses the hardware
-	float ABI or the software float ABI by examining some fields
-	in the ELF header.  The linker uses different paths and config
-	files for hard versus soft binaries.  The <tt>rc</tt> system
-	has been enhanced to load the software float paths.
-	<tt>ldconfig</tt> now understands soft libraries in much the
-	same way that it understands 32-bit libraries on 64-bit
-	systems.  No additional kernel support was necessary for this,
-	apart from a minor patch to pass the ELF header information to
-	the binary, which has been in the tree since last summer.</p>
-
-      <p>The experimental armv6hf <tt>MACHINE_ARCH</tt> will be
-	retired after a transition period.  It will cease to mean
-	anything different from armv6 after the build system changes
-	go in.  Support for building soft-float ABI libraries will
-	remain in the tree, to support the <tt>WITH_LIBSOFT</tt> build
-	option.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Complete documentation needs to be written.</p>
-      </li><li>
-	<p>Hooks into the FreeBSD build system to generate soft float and
-	  transition to hard float after a flag day need to be
-	  polished up and committed.</p>
-      </li><li>
-	<p>A number of different upgrade/coexistence scenarios need
-	  to be tested, and a full package run needs to be done to
-	  assess the latest state of the ports tree.  This work should
-	  be completed by the end of January.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-on-Marvell-Armada38x" href="#FreeBSD-on-Marvell-Armada38x" id="FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></h2><p>
-	Contact:
-	  Marcin
-	  Wojtas
-	 &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Michal
-	  Stanek
-	 &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Bartosz
-	  Szczepanek
-	 &lt;<a href="mailto:bsz@semihalf.com">bsz@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Jan
-	  Dabros
-	 &lt;<a href="mailto:jsd@semihalf.com">jsd@semihalf.com</a>&gt;
-	</p>
-      <p>FreeBSD has been ported to run on the Marvell Armada38x
-	platform.  This SoC family boasts single/dual high-performance
-	ARM Cortex-A9 CPUs.</p>
-
-      <p>The multi-user SMP system is fully working and has been
-	tested on Marvell DB-88F6288-GP and SolidRun ClearFog
-	development boards.</p>
-
-      <p>The root filesystem can be hosted on a USB 3.0/2.0 drive or
-	via NFS using a PCIe network card.  Experimental support is
-	available for on-chip Gigabit Ethernet (NETA).</p>
-
-      <p>Additional features:</p>
-
-      <ul>
-	<li>GIC+MPIC cascaded interrupts courtesy of INTRNG</li>
-
-	<li>CESA dual-channel cryptographic engine</li>
-
-	<li>USB 3.0 and 2.0</li>
-
-	<li>PCIe 2.0</li>
-
-	<li>I2C</li>
-
-	<li>GPIO</li>
-
-	<li>Watchdog</li>
-
-	<li>RTC</li>
-      </ul>
-
-      <p>The port is under community review and will be integrated
-	into head soon.</p>
-    <p>This project was sponsored by Stormshield, and Semihalf.</p><h3>Open tasks:</h3><ol><li>
-	<p>Optimize performance of NETA and prepare for
-	  submission.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-on-Newer-ARM-Boards" href="#FreeBSD-on-Newer-ARM-Boards" id="FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/FreeBSD/arm/Odroid-C1" title="https://wiki.FreeBSD.org/FreeBSD/arm/Odroid-C1">FreeBSD on Odroid-C1</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/FreeBSD/arm/Odroid-C1" title="FreeBSD on Odroid-C1">https://wiki.FreeBSD.org/FreeBSD/arm/Odroid-C1</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/changeset/base/291683" title="https://svnweb.FreeBSD.org/changeset/base/291683">Commit Adding Glue Driver</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/changeset/base/291683" title="Commit Adding Glue Driver">https://svnweb.FreeBSD.org/changeset/base/291683</a></td></tr></table><p>
-	Contact:
-	  John
-	  Wehle
-	 &lt;<a href="mailto:john@feith.com">john@feith.com</a>&gt;
-	<br />
-	Contact:
-	  Ganbold
-	  Tsagaankhuu
-	 &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>We made the changes required to support the Amlogic Meson
-	Ethernet controller on the Hardkernel ODROID-C1 board, which
-	has an Amlogic aml8726-m8b SoC.  The main effort needed was to
-	write a glue driver for the Ethernet controller &#8212; the
-	Amlogic Meson Ethernet controller is compatible with Synopsys
-	DesignWare 10/100/1000 Ethernet MAC (<tt>if_dwc</tt>).</p>
-    <hr /><h2><a name="FreeBSD-on-SoftIron-Overdrive-3000" href="#FreeBSD-on-SoftIron-Overdrive-3000" id="FreeBSD-on-SoftIron-Overdrive-3000">FreeBSD on SoftIron Overdrive 3000</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://softiron.co.uk/products/" title="http://softiron.co.uk/products/">SoftIron Website</a></td><td>
-	    URL: <a href="http://softiron.co.uk/products/" title="SoftIron Website">http://softiron.co.uk/products/</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>The SoftIron Overdrive 3000 is an ARMv8 based server with an
-	8-core AMD Opteron A1100 processor.  The Overdrive 3000 has
-	two 10Gbase-T Ethernet ports, two PCI Express ports, and eight
-	SATA ports.  FreeBSD has been updated to be able to boot on this
-	hardware.</p>
-
-      <p>Support for the SATA device was added to the
-	<tt>ahci(4)</tt> driver.  Unlike on x86, this is a Memory
-	Mapped (mmio) device, and not on the PCI bus.  To support
-	this, a new ahci mmio driver attachment has been added.</p>
-
-      <p>The generic PCIe driver has been updated to improve interrupt
-	handling.  This includes supporting the interrupt-map
-	devicetree property, and supporting MSI and MSI-X interrupts
-	on arm64.</p>
-
-      <p>Support for MSI and MSI-X interrupts has been added to the
-	ARM Generic Interrupt Controller v2 (gicv2) driver.  This
-	allows devices to use these interrupts.  This has been tested
-	with a collection of PCIe NIC hardware.</p>
-    <p>This project was sponsored by SoftIron Inc..</p><h3>Open tasks:</h3><ol><li>
-	<p>Write a driver for the 10Gbase-T NIC.</p>
-      </li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64" title="https://wiki.FreeBSD.org/arm64">FreeBSD arm64 Wiki Entry</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/arm64" title="FreeBSD arm64 Wiki Entry">https://wiki.FreeBSD.org/arm64</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support was added for kernel modules.  This included adding
-	the needed relocation types to the in-kernel relocator, and
-	updating the build logic to build modules for arm64.  CTF data
-	is currently not generated for modules due to a linker
-	bug.</p>
-
-      <p>Shared page support was added.  This allows
-	<tt>gettimeofday(2)</tt> to be implemented in userland by
-	directly accessing the timer register.  This reduces the
-	overhead of these calls as we no longer need to call into the
-	kernel.  This also moves the signal trampoline code away from
-	the stack, allowing for the stack to become non-executable.</p>
-
-      <p>CloudABI support for arm64 was added.  This included moving
-	the machine-independent code into a separate file to be shared
-	among all architectures.  An issue in the arm64 kernel was
-	found and fixed thanks to the CloudABI test suite.</p>
-
-      <p>Self-hosted poudriere package builds have been tested.
-	These complement the previous build strategy of using qemu
-	usermode emulation.  With this combination of self-hosted and
-	qemu usermode building, many ports that used to be broken on
-	arm64 have been fixed, resulting in over 17,000 ports building
-	for the architecture.</p>
-
-      <p>The machine-dependent portion of kernel support for
-	single-stepping userland binaries has been started.  This will
-	allow debuggers like <tt>lldb</tt> to step through an
-	application while debugging.</p>
-
-      <p>Many small fixes have been made to FreeBSD/arm64.  These
-	include fixing stack tracing through exceptions, printing more
-	information about "data abort" kernel panics,
-	cleaning up the atomic functions, supporting multi-pass driver
-	attachment, fixing userland stack alignment, cleaning up early
-	page table creation, fixing asynchronous software trap
-	handling, and enabling interrupts in exception handlers.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, and ABT Systems Ltd.</p><hr /><h2><a name="FreeBSD/RISC-V" href="#FreeBSD/RISC-V" id="FreeBSD/RISC-V">FreeBSD/RISC-V</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/riscv" title="https://wiki.FreeBSD.org/riscv">Project Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/riscv" title="Project Wiki">https://wiki.FreeBSD.org/riscv</a></td></tr></table><p>
-	Contact:
-	  Ruslan
-	  Bukin
-	 &lt;<a href="mailto:br@bsdpad.com">br@bsdpad.com</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Arun
-	  Thomas
-	 &lt;<a href="mailto:arun.thomas@baesystems.com">arun.thomas@baesystems.com</a>&gt;
-	</p>
-      <p>We have begun work on support for the RISC-V
-	architecture.</p>
-
-      <p>RISC-V is a new ISA designed to support computer architecture
-	research and education that is now set to become a standard
-	open architecture for industry implementations.</p>
-
-      <p>A minimal set of changes needed to compile the kernel
-	toolchain has been committed, along with machine headers,
-	run-time linker (rtld-elf) support, and libc/libstand.</p>
-
-      <p>All development has been happening in a separate branch,
-	with a goal of moving development to head in a few weeks.</p>
-
-      <p>At present, FreeBSD/RISC-V boots to multiuser in the Spike
-	simulator.</p>
-    <p>This project was sponsored by DARPA, AFRL, and HEIF5.</p><h3>Open tasks:</h3><ol><li>
-	<p>We plan to commit the rest of userspace (i.e., libc),
-	  kernel support, etc., in a few weeks.</p>
-      </li></ol><hr /><h2><a name="Improvements-for-ARMv6/v7-Support" href="#Improvements-for-ARMv6/v7-Support" id="Improvements-for-ARMv6/v7-Support">Improvements for ARMv6/v7 Support</a></h2><p>
-	Contact:
-	  Dominik
-	  Ermel
-	 &lt;<a href="mailto:der@semihalf.com">der@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Macek
-	 &lt;<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	</p>
-      <p>Numerous improvements for the ARMv6/v7 kernel and tools
-	have been developed by the Semihalf team.  Those include:</p>
-
-      <ul>
-	<li>Fixes for KGDB support.</li>
-
-	<li>Support for branch instructions in <tt>ptrace</tt> single
-	  stepping.</li>
-
-	<li>Fixes for kernel minidumps.</li>
-
-	<li>Improvements for LIBUSBBOOT.</li>
-
-	<li>Support for Exynos EHCI in the loader.</li>
-
-	<li>A fix for instruction single stepping in DDB.</li>
-
-	<li>Support for hardware watchpoints, including watchpoints
-	  on SMP systems.</li>
-
-	<li>Single stepping using the ARM Debug Architecture.</li>
-
-	<li>Support for gzip-compressed kernel modules in
-	  <tt>kldload</tt>.</li>
-
-	<li>Backport of the new pmap VM code to FreeBSD 10-STABLE (not
-	  yet sent to upstream).</li>
-      </ul>
-
-      <p>Most of the introduced changes have been committed to head
-	and more are on the way.</p>
-    <p>This project was sponsored by Juniper Networks Inc., and Semihalf.</p><h3>Open tasks:</h3><ol><li>
-	<p>Finish upstreaming the hardware watchpoints support.</p>
-      </li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="Base-System-Build-Improvements" href="#Base-System-Build-Improvements" id="Base-System-Build-Improvements">Base System Build Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.FreeBSD.org/pipermail/freebsd-arch/2015-December/017571.html" title="https://lists.FreeBSD.org/pipermail/freebsd-arch/2015-December/017571.html">FreeBSD-Arch Post Describing Plans</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/pipermail/freebsd-arch/2015-December/017571.html" title="FreeBSD-Arch Post Describing Plans">https://lists.FreeBSD.org/pipermail/freebsd-arch/2015-December/017571.html</a></td></tr><tr><td><a href="http://www.bsdcan.org/2014/schedule/events/460.en.html" title="http://www.bsdcan.org/2014/schedule/events/460.en.html">BSDCan 2014 META_MODE Presentation</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2014/schedule/events/460.en.html" title="BSDCan 2014 META_MODE Presentation">http://www.bsdcan.org/2014/schedule/events/460.en.html</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290433" title="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290433">WITH_FAST_DEPEND Details</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290433" title="WITH_FAST_DEPEND Details">https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290433</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290526" title="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290526">WITH_CCACHE_BUILD Details</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290526" title="WITH_CCACHE_BUILD Details">https://svnweb.FreeBSD.org/base?view=revision&amp;revision=290526</a></td></tr></table><p>
-	Contact:
-	  Bryan
-	  Drewery
-	 &lt;<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>&gt;
-	</p>
-      <p>Bryan Drewery (bdrewery@) has been working to improve the
-	build framework as well as <tt>buildworld</tt> build times.
-	The build system has been largely untouched by large-scale
-	changes for many years.  Most of the effort has been on
-	improving the recent <tt>META_MODE</tt> merge that was
-	presented at BSDCan 2014.  This is a new build system that is
-	not currently enabled by default but brings many benefits.
-	Beyond that, some highlights of the work changing
-	<tt>buildworld</tt> are:</p>
-
-      <ul>
-	<li><tt>WITH_FAST_DEPEND</tt>, which avoids calling
-	  "mkdep" during the <tt>make depend</tt> phase and
-	  instead generates dependency files during compilation.  The
-	  old scheme was pre-processing all source files twice.  The
-	  new version saves 16-35% in build times.</li>
-
-	<li><tt>WITH_CCACHE_BUILD</tt> adds built-in <tt>ccache</tt>
-	  support, avoiding many of the historical pitfalls of
-	  changing <tt>CC</tt> in <tt>make.conf</tt> to use
-	  <tt>ccache</tt>.</li>
-
-	<li>Many improvements for parallelization of the build.</li>
-
-	<li><tt>LIBADD</tt> improvements to ensure proper usage of
-	  this tool to replace duplicate <tt>LDADD</tt> and
-	  <tt>DPADD</tt> statements.  Further work is under way to
-	  reduce overlinking.</li>
-
-	<li>A lot of cleanup of improper framework usage.</li>
-
-	<li>Ensuring that installing files from the build tree fails
-	  if the destination directory is missing, rather than
-	  installing a file as the directory name.</li>
-      </ul>
-    <p>This project was sponsored by EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li>
-	<p>See the FreeBSD-arch mail for more information on planned
-	  work.</p>
-      </li></ol><hr /><h2><a name="ELF-Tool-Chain-Tools" href="#ELF-Tool-Chain-Tools" id="ELF-Tool-Chain-Tools">ELF Tool Chain Tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://elftoolchain.sourceforge.net" title="http://elftoolchain.sourceforge.net">ELF Tool Chain Website</a></td><td>
-	    URL: <a href="http://elftoolchain.sourceforge.net" title="ELF Tool Chain Website">http://elftoolchain.sourceforge.net</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ELF Tool Chain project provides BSD-licensed
-	implementations of compilation tools and libraries for
-	building and analyzing ELF objects.  The project began as part
-	of FreeBSD but later became an independent project in order to
-	encourage wider participation from others in the open-source
-	developer community.</p>
-
-      <p>In the last quarter of 2015 the ELF Tool Chain tools were
-	updated to a snapshot of upstream Subversion revision 3272.
-	Improvements include better input file validation, RISC-V
-	support, support for Xen ELF notes, additional MIPS and ARM
-	relocations, better performance, and bug fixes.</p>
-
-      <p>The ELF Tool Chain project is planning a new release in
-	the first quarter of 2016, which will facilitate wider
-	testing and use by projects in addition to FreeBSD.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Add missing functionality (PE/COFF support) to
-	  <tt>elfcopy</tt> and migrate the base system build.</p>
-      </li><li>
-	<p>Fix issues found by fuzzing inputs to the tools.</p>
-      </li><li>
-	<p>Add automatic support for separate debug files.</p>
-      </li></ol><hr /><h2><a name="The-LLDB-Debugger" href="#The-LLDB-Debugger" id="The-LLDB-Debugger">The LLDB Debugger</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/lldb" title="https://wiki.FreeBSD.org/lldb">FreeBSD LLDB Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/lldb" title="FreeBSD LLDB Wiki Page">https://wiki.FreeBSD.org/lldb</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLDB is the debugger from the LLVM family of projects.
-	Originally developed for Mac OS X, it now also supports FreeBSD,
-	NetBSD, Linux, Android, and Windows.  It builds on existing
-	components in the larger LLVM project, for example using
-	Clang's expression parser and LLVM's disassembler.</p>
-
-      <p>LLDB in the FreeBSD base system was upgraded to version 3.7.0
-	as part of the Clang and LLVM upgrade, and it will similarly
-	be upgraded again to 3.8.0 for FreeBSD 11.0-RELEASE.</p>
-
-      <p>LLDB is now enabled by default on the amd64 and arm64
-	platforms.  It is now a functional basic debugger on arm64,
-	after a number of fixes were made in the last quarter to both
-	LLDB and the FreeBSD kernel.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Rework the LLDB build to use LLVM and Clang shared
-	  libraries.</p>
-      </li><li>
-	<p>Port a remote debugging stub to FreeBSD.</p>
-      </li><li>
-	<p>Add support for local and core file kernel debugging.</p>
-      </li><li>
-	<p>Improve support on architectures other than amd64 and
-	  arm64.</p>
-      </li></ol><hr /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/bsdjhb/gdb/tree/freebsd-threads" title="https://github.com/bsdjhb/gdb/tree/freebsd-threads">New 1:1-Only Thread Target for FreeBSD</a></td><td>
-	    URL: <a href="https://github.com/bsdjhb/gdb/tree/freebsd-threads" title="New 1:1-Only Thread Target for FreeBSD">https://github.com/bsdjhb/gdb/tree/freebsd-threads</a></td></tr></table><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KGDB option is now on by default in the
-	<tt>devel/gdb</tt> port.</p>
-
-      <p>Changes to support cross-debugging of crashdumps in libkvm
-	were committed to head in r291406.</p>
-
-      <p>A new thread target for FreeBSD that is suitable for merging
-	upstream has been written and lightly tested.  However, it is
-	not yet available as an option in the port.  This thread
-	target uses <tt>ptrace(2)</tt> directly rather than
-	<tt>libthread_db</tt> and as such supports threads on all ABIs
-	(such as FreeBSD/i386 binaries on FreeBSD/amd64 and possibly Linux
-	binaries, though that is not yet tested).  It also requires
-	less-invasive changes in the MD targets in GDB compared to the
-	<tt>libthread_db</tt>-based target.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Add a port option for the new 1:1-only thread target.</p>
-      </li><li>
-	<p>Test the new 1:1-only thread target.</p>
-      </li><li>
-	<p>Figure out why the powerpc kgdb targets are not able to
-	  unwind the stack past the initial frame.</p>
-      </li><li>
-	<p>Add support for more platforms (arm, mips, aarch64) to
-	  upstream <tt>gdb</tt> for both userland and
-	  <tt>kgdb</tt>.</p>
-      </li><li>
-	<p>Add support for debugging powerpc vector registers.</p>
-      </li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Bringing-GitLab-into-the-Ports-Collection" href="#Bringing-GitLab-into-the-Ports-Collection" id="Bringing-GitLab-into-the-Ports-Collection">Bringing GitLab into the Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468">PR for the New Port</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468" title="PR for the New Port">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468</a></td></tr><tr><td><a href="https://github.com/t-zuehlsdorff/gitlabhq/blob/8-3-docu/doc/install/installation-freebsd.md" title="https://github.com/t-zuehlsdorff/gitlabhq/blob/8-3-docu/doc/install/installation-freebsd.md">Installation Guide</a></td><td>
-	    URL: <a href="https://github.com/t-zuehlsdorff/gitlabhq/blob/8-3-docu/doc/install/installation-freebsd.md" title="Installation Guide">https://github.com/t-zuehlsdorff/gitlabhq/blob/8-3-docu/doc/install/installation-freebsd.md</a></td></tr><tr><td><a href="https://github.com/gitlabhq/gitlabhq/" title="https://github.com/gitlabhq/gitlabhq/">Upstream GitLab website</a></td><td>
-	    URL: <a href="https://github.com/gitlabhq/gitlabhq/" title="Upstream GitLab website">https://github.com/gitlabhq/gitlabhq/</a></td></tr></table><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:ports@toco-domains.de">ports@toco-domains.de</a>&gt;
-	</p>
-      <p>GitLab is a web-based Git repository manager with many
-	features that is used by more than 100,000 organizations
-	including NASA and Alibaba.  It also is a very long-standing
-	entry on the "Wanted Ports" list of the FreeBSD
-	Wiki.</p>
-
-      <p>In the last quarter, there was steady progress in the project
-	itself and the porting.  The current release of GitLab 8.3 is
-	now based on Rails 4.2, which obsoletes the need for around 50
-	new ports.  Now there are only 5 dependencies left to be
-	committed!</p>
-
-      <p>While the new version of GitLab 8.3 eases the porting, there
-	are big changes since the last working port of GitLab 7.14.
-	Nonetheless, it could be expected to see the next working port
-	in the first quarter of 2016.</p>
-    <p>This project was sponsored by anyMOTION GRAPHICS GmbH, D�sseldorf, Germany.</p><h3>Open tasks:</h3><ol><li>
-	<p>Update the patches from GitLab 7.14 to 8.3.</p>
-      </li><li>
-	<p>Update the documentation.</p>
-      </li><li>
-	<p>Provide an updated patch.</p>
-      </li></ol><hr /><h2><a name="GNOME-on-FreeBSD" href="#GNOME-on-FreeBSD" id="GNOME-on-FreeBSD">GNOME on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome" title="http://www.FreeBSD.org/gnome">FreeBSD Gnome Website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome" title="FreeBSD Gnome Website">http://www.FreeBSD.org/gnome</a></td></tr><tr><td><a href="https://github.com/FreeBSD/freebsd-ports-gnome" title="https://github.com/FreeBSD/freebsd-ports-gnome">Devel Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/freebsd-ports-gnome" title="Devel Repository">https://github.com/FreeBSD/freebsd-ports-gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD">Upstream Build Bot</a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="Upstream Build Bot">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html">USE_GNOME Porter's Handbook Chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="USE_GNOME Porter's Handbook Chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD GNOME Team maintains the GNOME, MATE, and CINNAMON
-	desktop environments and graphical user interfaces for FreeBSD.
-	GNOME 3 is part of the GNU Project.  MATE is a fork of the
-	GNOME 2 desktop.  CINNAMON is a desktop environment using
-	GNOME 3 technologies but with a GNOME 2 look and feel.</p>
-
-      <p>This quarter, due to limited available time there was not
-	much progress.  This began to change in December, when work
-	started on porting MATE 1.12 and CINNAMON 2.8 to FreeBSD.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The FreeBSD GNOME website is stale.  Work is under way to
-	  improve it.</p>
-      </li><li>
-	<p>Continue working on investigating the issues blocking
-	  GNOME 3.18.</p>
-      </li></ol><hr /><h2><a name="IPv6-Promotion-Campaign" href="#IPv6-Promotion-Campaign" id="IPv6-Promotion-Campaign">IPv6 Promotion Campaign</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/IPv6PortsTODO" title="https://wiki.FreeBSD.org/IPv6PortsTODO">Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/IPv6PortsTODO" title="Wiki Page">https://wiki.FreeBSD.org/IPv6PortsTODO</a></td></tr></table><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:ports@toco-domains.de">ports@toco-domains.de</a>&gt;
-	</p>
-      <p>There are more and more machines on the internet that
-	<strong>only</strong> support IPv6.  I manage some of them,
-	and was regularly hit by missing IPv6 support when
-	fetching the distfiles needed for building
-	ports.</p>
-
-      <p>I did some research into the impact of missing IPv6 support
-	on the ports tree.  The results are that 10,308 of 25,522
-	ports are not fetchable when using IPv6.  This renders,
-	through dependencies, a total of 17,715 ports unbuildable from
-	IPv6-only systems.  All you can do then is wait and hope that
-	<tt>distcache.FreeBSD.org</tt> caches the distfile.  But this
-	will take some time, which might not be a luxury available
-	when a piece of software in use is hit by a security
-	issue.</p>
-
-      <p>Based on the research, a promotion campaign for IPv6 was
-	started.  Some volunteers will contact the relevant system
-	administrators and try to convince them to support IPv6.  This
-	will start in January 2016 and will hopefully create some
-	progress soon.</p>
-    <hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://FreeBSD.kde.org/" title="https://FreeBSD.kde.org/">KDE on FreeBSD Website</a></td><td>
-	    URL: <a href="https://FreeBSD.kde.org/" title="KDE on FreeBSD Website">https://FreeBSD.kde.org/</a></td></tr><tr><td><a href="https://FreeBSD.kde.org/area51.php" title="https://FreeBSD.kde.org/area51.php">Experimental KDE Ports Staging Area</a></td><td>
-	    URL: <a href="https://FreeBSD.kde.org/area51.php" title="Experimental KDE Ports Staging Area">https://FreeBSD.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/KDE" title="https://wiki.FreeBSD.org/KDE">KDE on FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/KDE" title="KDE on FreeBSD Wiki">https://wiki.FreeBSD.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-FreeBSD" title="https://mail.kde.org/mailman/listinfo/kde-FreeBSD">KDE/FreeBSD Mailing List</a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-FreeBSD" title="KDE/FreeBSD Mailing List">https://mail.kde.org/mailman/listinfo/kde-FreeBSD</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/plasma5" title="http://src.mouf.net/area51/log/branches/plasma5">Development Repository for Integrating KDE Frameworks 5 and Plasma 5</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/plasma5" title="Development Repository for Integrating KDE Frameworks 5 and Plasma 5">http://src.mouf.net/area51/log/branches/plasma5</a></td></tr></table><p>
-	Contact: KDE on FreeBSD team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging and making sure
-	that the experience of KDE and Qt on FreeBSD is as good as
-	possible.</p>
-
-      <p>The team kept busy during the last quarter of 2015.  Quite
-	a few big updates were committed to the ports tree, and a few
-	more are being worked on in our experimental repository.</p>
-
-      <p>As in previous quarters, we would like to thank several
-	people who have contributed with machines, patches, and
-	general help.  Tobias Berner, Guido Falsi (madpilot@),
-	Adriaan de Groot, Ralf Nolden, Steve Wills (swills@), and
-	Josh Paetzel (jpaetzel@) have been essential to our work.</p>
-
-      <p>The following big updates landed in the ports tree this
-	quarter.  In many cases, we have also contributed patches to
-	the upstream projects.</p>
-
-      <ul>
-	<li>CMake 3.4.0 and 3.4.1</li>
-
-	<li>Calligra 2.9.1, the latest release of the integrated
-	  work applications suite.  Calligra had last been updated in
-	  the ports tree at the end of 2013!</li>
-
-	<li>PyQt4 4.11.4, QScintilla2 2.9.1 and SIP 4.17.</li>
-
-	<li>PyQt5 5.5.1.  Thanks to the work spearheaded by Guido
-	  Falsi and Tobias Berner in the previous quarter, the PyQt5
-	  ports have finally been committed to the ports tree.  Not
-	  only was this long-awaited on its own, it allows other ports
-	  to be updated to their latest versions.</li>
-
-	<li>QtCreator 3.5.1 and 3.6.0.</li>
-
-	<li>A couple of Qt5 packaging bugs were fixed: it should now
-	  be more straightforward to use the Qt5 ports to build
-	  software outside the ports tree, and it is now possible to
-	  build ports that require a C++11 compiler and Qt5 on FreeBSD
-	  9.x.</li>
-      </ul>
-
-      <p>Work on updating the Qt5 ports to their latest version, as
-	well as porting KDE Frameworks 5 and Plasma 5 to FreeBSD, is well
-	under way in our experimental area51 repository.  At the
-	moment, it contains Qt5 5.5.1, KDE Frameworks 5.17.0, Plasma
-	5.5.1 and KDE Applications 15.12.0.</p>
-
-      <p>Users interested in testing those ports are encouraged to
-	follow the instructions in
-	<a href="https://FreeBSD.kde.org/area51.php" shape="rect">our website</a>
-	and report their results to our mailing list.  Qt5 5.5.1 is in
-	our "qt-5.5" branch, and Plasma 5 and the rest is in
-	the "plasma5" branch (which also contains Qt
-	5.5.1).</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Commit the Qt5 5.5.1 update.</p>
-      </li><li>
-	<p>Land the KDE Frameworks 5 and Plasma 5 ports in the
-	  tree.</p>
-      </li><li>
-	<p>Investigate what needs to be done to make QtWebEngine,
-	  the Chromium-based replacement for QtWebKit, work on
-	  FreeBSD.</p>
-      </li></ol><hr /><h2><a name="Linux-Kernel-as-a-Library-Added-to-the-Ports-Collection" href="#Linux-Kernel-as-a-Library-Added-to-the-Ports-Collection" id="Linux-Kernel-as-a-Library-Added-to-the-Ports-Collection">Linux Kernel as a Library Added to the Ports
-      Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/lkl/linux" title="https://github.com/lkl/linux">Upstream LKL Github repository</a></td><td>
-	    URL: <a href="https://github.com/lkl/linux" title="Upstream LKL Github repository">https://github.com/lkl/linux</a></td></tr></table><p>
-	Contact:
-	  Conrad
-	  Meyer
-	 &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	</p>
-      <p>LKL ("Linux Kernel as a Library") is a special
-	"architecture" of the full Linux kernel that builds
-	as a userspace library on various platforms, including FreeBSD.
-	One application of such a library is using Linux filesystem
-	drivers to implement a FUSE backend.</p>
-
-      <p>fusefs-lkl's <tt>lklfuse</tt> binary is such a FUSE
-	filesystem.  It can mount <tt>ext4/3/2</tt>, <tt>XFS</tt>, and
-	<tt>BTRFS</tt> read-write, using the native drivers from
-	Linux.</p>
-
-      <p><tt>sysutils/fusefs-lkl</tt> can now be installed either from
-	packages or ports, providing access to these filesystems on
-	FreeBSD via FUSE.</p>
-    <hr /><h2><a name="LXQt-on-FreeBSD" href="#LXQt-on-FreeBSD" id="LXQt-on-FreeBSD">LXQt on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/LXQt" title="https://wiki.FreeBSD.org/LXQt">FreeBSD LXQt Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/LXQt" title="FreeBSD LXQt Project">https://wiki.FreeBSD.org/LXQt</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/lxqt/subversion/source" title="https://www.assembla.com/spaces/lxqt/subversion/source">LXQt Devel Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/lxqt/subversion/source" title="LXQt Devel Repository">https://www.assembla.com/spaces/lxqt/subversion/source</a></td></tr></table><p>
-	Contact:
-	  Olivier
-	  Duchateau
-	 &lt;<a href="mailto:olivierd@FreeBSD.org">olivierd@FreeBSD.org</a>&gt;
-	</p>
-      <p><a href="http://lxqt.org/" shape="rect">LXQt</a> is the Qt port of and
-	the upcoming version of LXDE, the Lightweight Desktop
-	Environment.  It is the product of the merge between the
-	LXDE-Qt and the Razor-qt projects.</p>
-
-      <p>The porting effort remains very much a work in progress: it
-	needs some components of Plasma 5, the new major KDE
-	workspace.</p>
-
-      <p>Currently, only the 0.10 branch is functional.  See our wiki
-	page for a complete list of applications.</p>
-
-      <p>We also sent updates for some components of LXDE, required
-	for the LXQt desktop:</p>
-
-      <ul>
-	<li><tt>x11/menu-cache</tt> 1.0.1</li>
-
-	<li><tt>x11/lxmenu-data</tt> 0.1.4</li>
-      </ul>
-
-      <p>Binary packages are available (only for test purposes) which
-	are regularly tested with the KDE development repository.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Port libsysstat to BSD systems.</p>
-      </li><li>
-	<p>Fix some issues that need to be resolved, especially the
-	  shutdown and reboot commands.</p>
-      </li></ol><hr /><h2><a name="New-Tools-to-Enhance-the-Porting-Experience" href="#New-Tools-to-Enhance-the-Porting-Experience" id="New-Tools-to-Enhance-the-Porting-Experience">New Tools to Enhance the Porting Experience</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSD/pytoport" title="https://github.com/FreeBSD/pytoport">pytoport: Generate FreeBSD Ports from Python modules on PyPI</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/pytoport" title="pytoport: Generate FreeBSD Ports from Python modules on PyPI">https://github.com/FreeBSD/pytoport</a></td></tr><tr><td><a href="https://github.com/bbqsrc/bandar" title="https://github.com/bbqsrc/bandar">bandar: Create Development Overlays for the Ports Tree</a></td><td>
-	    URL: <a href="https://github.com/bbqsrc/bandar" title="bandar: Create Development Overlays for the Ports Tree">https://github.com/bbqsrc/bandar</a></td></tr><tr><td><a href="https://github.com/bbqsrc/skog-python" title="https://github.com/bbqsrc/skog-python">skog: Generate Visual Dependency Trees for FreeBSD Ports</a></td><td>
-	    URL: <a href="https://github.com/bbqsrc/skog-python" title="skog: Generate Visual Dependency Trees for FreeBSD Ports">https://github.com/bbqsrc/skog-python</a></td></tr><tr><td><a href="https://github.com/bbqsrc/spdx-lookup-python" title="https://github.com/bbqsrc/spdx-lookup-python">spdx-lookup: SPDX License List Query Tool</a></td><td>
-	    URL: <a href="https://github.com/bbqsrc/spdx-lookup-python" title="spdx-lookup: SPDX License List Query Tool">https://github.com/bbqsrc/spdx-lookup-python</a></td></tr></table><p>
-	Contact:
-	Brendan
-	Molloy
-       &lt;<a href="mailto:brendan+freebsd@bbqsrc.net">brendan+freebsd@bbqsrc.net</a>&gt;
-	</p>
-      <p>When I starting working on ports for FreeBSD in the last couple
-	of weeks, I found that my workflow was not as efficient as it
-	could be using just the available tools, so I made a few that
-	could be useful to the development community at large.  All of
-	these have been or will soon be added to the Ports tree, so
-	you can play with them today!</p>
-
-      <p><tt>pytoport</tt> is a command-line application that
-	generates a skeleton port for a given PyPI package name.  It
-	attempts to generate the correct dependencies, makes a good
-	attempt at guessing the license using <tt>spdx-lookup</tt>,
-	and generates a <tt>pkg-descr</tt>.  This made generating the
-	fifteen or so ports I was working on a complete breeze.</p>
-
-      <p>While doing this, however, I noticed that some ports were
-	bringing in dependencies that I did not expect, and I needed
-	some way to visualise this.  <tt>skog</tt> builds a dependency
-	tree from the depends lists output by the Ports framework, and
-	displays it on the command line (with extra shiny output if
-	you are using UTF-8).  No more pesky example and documentation
-	dependencies being dragged in when you <em>clearly</em>
-	toggled that <tt>OPTION</tt> as far off as it would go.</p>
-
-      <p>While doing all of this, I found it cumbersome to be copying
-	ports back and forth between my small development tree living
-	in git and the larger upstream SVN tree I was using in
-	poudriere.  I built a tool called <tt>bandar</tt> that takes
-	advantage of the FUSE version of unionfs to easily overlay my
-	dev tree on the upstream tree, run lint checks, poudriere, and
-	generate archives with ease.</p>
-
-      <p>I am very impressed with how easy it was to build more
-	tooling for FreeBSD.  I hope some of these tools will be of some
-	use to you, and as always, I'd love to hear your feedback!</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Improve <tt>skog</tt> to support searching a tree for a
-	  certain port.</p>
-      </li><li>
-	<p>Get the <tt>bandar</tt> port completed.</p>
-      </li><li>
-	<p>Continue to improve <tt>pytoport</tt>, adding
-	  <tt>trove</tt> support and better dependency handling.</p>
-      </li><li>
-	<p>Patches welcome for all of the above!</p>
-      </li></ol><hr /><h2><a name="Node.js-Modules" href="#Node.js-Modules" id="Node.js-Modules">Node.js Modules</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.assembla.com/spaces/cozycloud/subversion/source" title="https://www.assembla.com/spaces/cozycloud/subversion/source">Node.js Modules Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/cozycloud/subversion/source" title="Node.js Modules Repository">https://www.assembla.com/spaces/cozycloud/subversion/source</a></td></tr></table><p>
-	Contact:
-	  Olivier
-	  Duchateau
-	 &lt;<a href="mailto:olivierd@FreeBSD.org">olivierd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Node.js is a platform built on Chrome's JavaScript runtime
-	for easily building fast, scalable network applications.  It
-	uses an event-driven, non-blocking I/O model that makes it
-	lightweight and efficient &#8212; 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 in the
-	<a href="http://npmjs.org/" shape="rect">npm package registry</a>.</p>
-
-      <p>Currently, the repository contains slightly fewer than 300
-	new ports, in particular:</p>
-
-      <ul>
-	<li>Socket.IO, a library for realtime web applications</li>
-
-	<li>Jison, a JavaSript parser generator</li>
-      </ul>
-
-      <p>We have improved the USES framework:</p>
-
-      <ul>
-	<li>Users can define which version of Node.js will be
-	  installed through <tt>/etc/make.conf</tt>.</li>
-
-	<li><tt>node-gyp</tt> is now well-integrated into the USES
-	  framework, via the <strong>build</strong> argument.</li>
-
-	<li>The <tt>pkg-plist</tt> is now automatically generated
-	  to make <tt>portlint</tt> happy.</li>
-      </ul>
-
-      <p>Each port is up-to-date.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Update the pre-draft documentation.</p>
-      </li><li>
-	<p>Bring in grunt.js (and modules), the JavaScript task
-	  runner.</p>
-      </li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">Ports Collection Landing Page</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="Ports Collection Landing Page">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html">Contributor's Guide</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html" title="Contributor's Guide">https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">Ports Monitoring Service</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="Ports Monitoring Service">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html">Ports Management Team Website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="Ports Management Team Website">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr">Portmgr on Facebook</a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="Portmgr on Facebook">http://www.facebook.com/portmgr</a></td></tr></table><p>
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:culot@FreeBSD.org">culot@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of the fourth quarter, the ports tree holds a
-	bit more than 25,000 ports, and the PR count is around 2,000.
-	The activity on the ports tree remains steady, with about
-	7,000 commits performed by almost 120 active committers.</p>
-
-      <p>On the problem reports front, figures show an encouraging
-	trend, with a significant increase in the number of PRs fixed
-	during Q4.  Indeed, almost 1,800 reports were fixed, which
-	makes an increase of about 20% compared to Q3.</p>
-
-      <p>In Q4, eight commit bits were taken in for safekeeping,
-	following an inactivity period of more than 18 months (lioux,
-	lippe, simon, jhay, max, sumikawa, alexey, sperber).  Three
-	new developers were granted a ports commit bit (Kenji Takefu,
-	Carlos Puga Medina, and Ian Lepore), and one returning
-	committer (miwi) had his commit bit reinstated.</p>
-
-      <p>Also related to the management of ports commit bits, nox's
-	grants were revoked, since the FreeBSD developers learned that
-	Juergen Lock had passed away.</p>
-
-      <p>On the management side, no changes were made to the portmgr
-	team during Q4.</p>
-
-      <p>On QA side 33 exp-runs were performed to validate sensitive
-	updates or cleanups.  Amongst those noticeable changes are the
-	update to GCC 4.9, CMake to 3.4.1, PostgreSQL to 9.4, and
-	ruby-gems to 2.5.0.  Some infrastructure changes included the
-	usage of a <tt>WRKSRC</tt> different from <tt>WRKDIR</tt> when
-	<tt>NO_WRKSUBDIR</tt> is set, the removal of
-	<tt>bsd.cpu.mk</tt> from <tt>sys.mk</tt>, and the move of
-	<tt>QT_NONSTANDARD</tt> to <tt>bsd.qt.mk</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>We would like to remind everyone that the ports tree is
-	  built and run by volunteers, and any help is greatly
-	  appreciated.  While Q4 saw a significant increase in the
-	  number of problem reports fixed, we encourage all ports
-	  committers to have a look at the issues reported by our
-	  users and try to fix as many as possible.  Many thanks to
-	  all who made a contribution during Q4, and keep up the
-	  good work in 2016!</p>
-      </li></ol><hr /><h2><a name="Supporting-Variants-in-the-Ports-Framework" href="#Supporting-Variants-in-the-Ports-Framework" id="Supporting-Variants-in-the-Ports-Framework">Supporting Variants in the Ports Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/bbqsrc/poudriere/compare/master...feature/variants" title="https://github.com/bbqsrc/poudriere/compare/master...feature/variants">Poudriere PoC with Variants</a></td><td>
-	    URL: <a href="https://github.com/bbqsrc/poudriere/compare/master...feature/variants" title="Poudriere PoC with Variants">https://github.com/bbqsrc/poudriere/compare/master...feature/variants</a></td></tr><tr><td><a href="https://gist.github.com/bbqsrc/e7e3a54d84706485aa3a" title="https://gist.github.com/bbqsrc/e7e3a54d84706485aa3a">Ports Makefile PoC with Examples</a></td><td>
-	    URL: <a href="https://gist.github.com/bbqsrc/e7e3a54d84706485aa3a" title="Ports Makefile PoC with Examples">https://gist.github.com/bbqsrc/e7e3a54d84706485aa3a</a></td></tr></table><p>
-	Contact:
-	  Brendan
-	  Molloy
-	 &lt;<a href="mailto:brendan+freebsd@bbqsrc.net">brendan+freebsd@bbqsrc.net</a>&gt;
-	</p>
-      <p>I recently became involved with FreeBSD (as in, the last 2-3
-	weeks), and found myself quickly involved with Ports
-	development.  What struck me immediately was the difficulty in
-	providing a Python package that was depended upon by multiple
-	versions of Python.  As it turns out, poudriere can currently
-	only generate one package per port, meaning that a Python
-	version-neutral (compatible with 2.x and 3.x) port cannot
-	simultaneously be packaged for each variant at the same
-	time.</p>
-
-      <p>I discussed the issue with Kubilay Kocak, who suggested that I
-	look into implementing a "variants protocol" within
-	the Ports framework and the necessary changes to poudriere to
-	allow a port to generate more than one package.</p>
-
-      <p>Support for variants is strongly needed in Ports and
-	provides significant benefits.</p>
-
-      <ul>
-	<li>It would allow Python and other languages to provide
-	  packages for dependencies for multiple language versions
-	  from the same port.</li>
-
-	<li>It alleviates the need for so-called "slave
-	  ports", as a single port could now have multiple
-	  generated packages from a single port.</li>
-
-	<li>It would have a very small impact on the greater Ports
-	  ecosystem: adding only two new variables, <tt>VARIANT</tt>
-	  and <tt>VARIANTS</tt>.</li>
-
-	<li>It would provide a more consistent approach between
-	  different packaging teams for handling variations.</li>
-      </ul>
-
-      <p>For a simple example, <tt>editors/vim-lite</tt> could
-	be folded into the <tt>editors/vim</tt> port, while still
-	generating a <tt>vim</tt> and <tt>vim-lite</tt> package.
-	For Python, <tt>VARIANTS</tt> can be derived from the already
-	used <tt>USES</tt> flags and generate compatible packages.
-	<tt>py27-foobar</tt> and <tt>py34-foobar</tt> could now be
-	consistently generated by poudriere without issue.</p>
-
-      <p>Fortunately, this is not a wishful thinking piece.  I dug
-	in my heels and have implemented a proof-of-concept
-	implementation of variants in the Ports framework, including
-	the necessary modifications to poudriere in order to support
-	it.  It was mildly upsettling to find that poudriere is mostly
-	written in Bourne shell scripts, but I pressed on
-	nonetheless.</p>
-
-      <p>I started with
-	<a href="https://github.com/bapt/ports-wip/compare/variants" shape="rect">the prototype made by Baptiste Daroussin</a>
-	as a base, and built from there.  The poudriere PoC aims to
-	limit changes as much as possible to merely adding support for
-	the new variants flags, while also at the request of Kubilay Kocak
-	making the logging output more package-centric (as opposed to
-	port-centric) as a result of these changes.</p>
-
-      <p>This is a <strong>work in progress</strong>, and I would
-	love to hear your feedback.  I have enjoyed my first few weeks
-	working on FreeBSD, and I hope to stay here for quite some
-	time.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Any constructive feedback on the implementation would be
-	  very welcome!</p>
-      </li><li>
-	<p>Hopefully the code will be of sufficient quality to be
-	  considered for formal review in the coming months.</p>
-      </li></ol><hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Xfce" title="https://wiki.FreeBSD.org/Xfce">FreeBSD Xfce Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Xfce" title="FreeBSD Xfce Project">https://wiki.FreeBSD.org/Xfce</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="https://www.assembla.com/spaces/xfce4/subversion/source">FreeBSD Xfce Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="FreeBSD Xfce Repository">https://www.assembla.com/spaces/xfce4/subversion/source</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms, such as FreeBSD.  It aims to be fast and
-	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>
-
-      <ul>
-	<li><tt>audio/xfce4-pulseaudio-plugin</tt> 0.2.4</li>
-	<li><tt>multimedia/xfce4-parole</tt> 0.8.1</li>
-	<li><tt>x11/xfce4-whiskermenu-plugin</tt> 1.5.2</li>
-      </ul>
-
-      <p>We also follow the unstable releases (available in our
-	experimental repository) of:</p>
-
-      <ul>
-	<li><tt>x11/xfce4-dashboard</tt> 0.5.4</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Propose a patch to upstream to fix Xfdashboard with our
-	  version of OpenGL (it currently coredumps).</p>
-      </li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="&quot;FreeBSD-Mastery:-Specialty-Filesystems&quot;-Early-Access-Version-Now-Available" href="#&quot;FreeBSD-Mastery:-Specialty-Filesystems&quot;-Early-Access-Version-Now-Available" id="&quot;FreeBSD-Mastery:-Specialty-Filesystems&quot;-Early-Access-Version-Now-Available">"FreeBSD Mastery: Specialty Filesystems" Early Access Version Now Available</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.michaelwlucas.com/nonfiction/fmsf" title="https://www.michaelwlucas.com/nonfiction/fmsf">Book site</a></td><td>
-	    URL: <a href="https://www.michaelwlucas.com/nonfiction/fmsf" title="Book site">https://www.michaelwlucas.com/nonfiction/fmsf</a></td></tr><tr><td><a href="https://www.tiltedwindmillpress.com/?product=fmspf" title="https://www.tiltedwindmillpress.com/?product=fmspf">Early access version</a></td><td>
-	    URL: <a href="https://www.tiltedwindmillpress.com/?product=fmspf" title="Early access version">https://www.tiltedwindmillpress.com/?product=fmspf</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	</p>
-      <p><u>FreeBSD Mastery: Specialty Filesystems</u> is now in
-	copyediting.  The ebook should be available by the end of
-	January at all major vendors, and the print in February.</p>
-
-      <p>The book covers everything from removable media, to FUSE,
-	NFSv4 ACLs, iSCSI, CIFS, and more.</p>
-
-      <p>If you act really quickly, you can get the electronic early
-	access version at a 10% discount.  You will get the final
-	ebook when it comes out as well.  (This offer evaporates when
-	the final version comes out.)</p>
-    <hr /><h2><a name="style(9)-Enhanced-to-Allow-C99-bool" href="#style(9)-Enhanced-to-Allow-C99-bool" id="style(9)-Enhanced-to-Allow-C99-bool">style(9) Enhanced to Allow C99
-      bool</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.FreeBSD.org/pipermail/svn-src-head/2015-December/079671.html" title="https://lists.FreeBSD.org/pipermail/svn-src-head/2015-December/079671.html">Bruce's Email Requesting bool be Added to style(9)</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/pipermail/svn-src-head/2015-December/079671.html" title="Bruce's Email Requesting bool be Added to style(9)">https://lists.FreeBSD.org/pipermail/svn-src-head/2015-December/079671.html</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D4384" title="https://reviews.FreeBSD.org/D4384">Differential Revision for the Change</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D4384" title="Differential Revision for the Change">https://reviews.FreeBSD.org/D4384</a></td></tr></table><p>
-	Contact:
-	  Bruce
-	  Evans
-	 &lt;<a href="mailto:brde@optusnet.com.au">brde@optusnet.com.au</a>&gt;
-	<br />
-	Contact:
-	  Conrad
-	  Meyer
-	 &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	</p>
-      <p>Use of <tt>bool</tt> is now allowed.  It was allowed
-	previously, as well, but now it is <em>really</em> allowed.
-	Party like it's 1999!</p>
-    <p>This project was sponsored by EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li>
-	<p>Specify <tt>style(9)</tt>'s opinion on
-	  <tt>iso646.h.</tt></p>
-      </li><li>
-	<p>Fix <tt>intmax_t</tt> to be 128-bit on platforms where
-	  <tt>__int128_t</tt> is used.</p>
-      </li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="HardenedBSD" href="#HardenedBSD" id="HardenedBSD">HardenedBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://hardenedbsd.org/" title="https://hardenedbsd.org/">HardenedBSD Website</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/" title="HardenedBSD Website">https://hardenedbsd.org/</a></td></tr><tr><td><a href="https://hardenedbsd.org/article/shawn-webb/2015-12-31/introducing-hardenedbsds-new-binary-updater" title="https://hardenedbsd.org/article/shawn-webb/2015-12-31/introducing-hardenedbsds-new-binary-updater">Introducing HardenedBSD's New Binary Updater</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/article/shawn-webb/2015-12-31/introducing-hardenedbsds-new-binary-updater" title="Introducing HardenedBSD's New Binary Updater">https://hardenedbsd.org/article/shawn-webb/2015-12-31/introducing-hardenedbsds-new-binary-updater</a></td></tr><tr><td><a href="https://hardenedbsd.org/article/shawn-webb/2015-11-22/introducing-secadm-030-beta-01" title="https://hardenedbsd.org/article/shawn-webb/2015-11-22/introducing-secadm-030-beta-01">secadm Beta Published</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/article/shawn-webb/2015-11-22/introducing-secadm-030-beta-01" title="secadm Beta Published">https://hardenedbsd.org/article/shawn-webb/2015-11-22/introducing-secadm-030-beta-01</a></td></tr><tr><td><a href="https://hardenedbsd.org/article/admin/2015-11-22/new-package-building-server" title="https://hardenedbsd.org/article/admin/2015-11-22/new-package-building-server">New Package Building Server</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/article/admin/2015-11-22/new-package-building-server" title="New Package Building Server">https://hardenedbsd.org/article/admin/2015-11-22/new-package-building-server</a></td></tr><tr><td><a href="https://github.com/HardenedBSD/secadm" title="https://github.com/HardenedBSD/secadm">secadm</a></td><td>
-	    URL: <a href="https://github.com/HardenedBSD/secadm" title="secadm">https://github.com/HardenedBSD/secadm</a></td></tr><tr><td><a href="https://github.com/HardenedBSD/hardenedBSD-playground/tree/hardened/experimental/master-i915" title="https://github.com/HardenedBSD/hardenedBSD-playground/tree/hardened/experimental/master-i915">HardenedBSD Haswell Support</a></td><td>
-	    URL: <a href="https://github.com/HardenedBSD/hardenedBSD-playground/tree/hardened/experimental/master-i915" title="HardenedBSD Haswell Support">https://github.com/HardenedBSD/hardenedBSD-playground/tree/hardened/experimental/master-i915</a></td></tr><tr><td><a href="http://jenkins.hardenedbsd.org/builds/HardenedBSD-CURRENT-i915kms-amd64-LATEST/" title="http://jenkins.hardenedbsd.org/builds/HardenedBSD-CURRENT-i915kms-amd64-LATEST/">Nightly Builds for HardenedBSD Haswell Support</a></td><td>
-	    URL: <a href="http://jenkins.hardenedbsd.org/builds/HardenedBSD-CURRENT-i915kms-amd64-LATEST/" title="Nightly Builds for HardenedBSD Haswell Support">http://jenkins.hardenedbsd.org/builds/HardenedBSD-CURRENT-i915kms-amd64-LATEST/</a></td></tr></table><p>
-	Contact:
-	  Shawn
-	  Webb
-	 &lt;<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>&gt;
-	<br />
-	Contact:
-	  Oliver
-	  Pinter
-	 &lt;<a href="mailto:oliver.pinter@hardenedbsd.org">oliver.pinter@hardenedbsd.org</a>&gt;
-	</p>
-      <p>HardenedBSD has been hard at work improving the performance
-	and stability of our security enhancements.  Security flags
-	are now per-thread instead of per-process, removing some
-	locking overhead.  ASLR for mmap(MAP_32BIT) requests has been
-	refactored, but lib32 is now disabled by default.</p>
-
-      <p>We have developed a new binary update utility,
-	<tt>hbsd-update</tt>, akin to <tt>freebsd-update</tt>.  In
-	addition to normal OS installs, it can also update jails and
-	ZFS Boot Environments (ZFS BEs).  Updates are signed using
-	X.509 certificates.</p>
-
-      <p><tt>secadm</tt> 0.3-beta has landed.  It has been rewritten
-	from scratch to be more efficient.  As part of the rewrite,
-	the rule syntax has changed and users must update their
-	rulesets as described in the README.</p>
-
-      <p>Thanks to generous donations of a server from G2, Inc and
-	hosting from Automated Tendencies, we can now do full
-	package builds in just 35 hours, down from 75 hours.
-	This machine will also provide weekly binary updates for
-	the kernel and base system.</p>
-
-      <p>Owing partly to the needs of the developers, we have
-	an experimental branch that includes the work Jean-S�bastien P�dron has
-	under way for Haswell graphics support, on top of FreeBSD
-	11-current.  Binary updates are also provided for this
-	branch.</p>
-
-      <p>Unfortunately, in order to focus our efforts on improving
-	HardenedBSD, we have had to pull back from submitting our ASLR
-	patches to FreeBSD.  The past two years' efforts to address
-	comments on the submission have taken their toll, and the
-	effort is no longer sustainable.  We are proud to be based on
-	FreeBSD and believe that the whole community could benefit from
-	the security technologies we are developing.  We hope that
-	someone else will be able to step forward and finish off the
-	task of integrating ASLR into FreeBSD.</p>
-    <p>This project was sponsored by Automated Tendencies, G2, Inc, and SoldierX.</p><hr /><h2><a name="NanoBSD-Modernization" href="#NanoBSD-Modernization" id="NanoBSD-Modernization">NanoBSD Modernization</a></h2><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	</p>
-      <p>This quarter's NanoBSD updates target three main areas.  First,
-	building a NanoBSD image required root privileges.  Second,
-	building for embedded platforms required detailed knowledge of
-	the format required to boot.  Third, the exact image sizes
-	needed to be known to produce an image.</p>
-
-      <p>When NanoBSD was written, FreeBSD's build system required root
-	privileges for the install step and onward.  NanoBSD added to
-	this by creating a <tt>md(4)</tt> device in which to construct the
-	image.  Some configurations of NanoBSD added further to this
-	by creating a chroot in which to cleanly build packages.
-	NanoBSD solves the first problem using the new
-	<tt>NO_ROOT</tt> build option to create a meta file.  NanoBSD
-	also augments this record as files are created and removed.
-	The meta file is then fed into <tt>makefs(8)</tt> to create a
-	UFS image with the proper permissions.  The UFS image, and
-	sometimes a DOS FAT partition, are then passed to
-	<tt>mkimg(1)</tt> to create the final SD image.  The
-	<tt>mtree</tt> manipulation has been written as a separate
-	script to allow it to move into the base system where it could
-	assist with other build orchestration tools (though the move
-	has not happened yet).</p>
-
-      <p>The detailed knowledge of how to build each embedded image
-	(as well as some of the base images for qemu) has always been
-	hard to enshrine.  Crochet puts this knowledge into its
-	builds.  The FreeBSD release system puts it into its system.
-	NanoBSD, prior to the current work, provided no way to access
-	its knowledge of how to build images.  The current state of
-	this project allows the user to set a simple image type and
-	have NanoBSD deal with all of the details needed to create
-	that image type.  This includes using the u-boot ports and
-	installing the right files into a FAT partition so that FreeBSD
-	can boot with <tt>ubldr(8)</tt>, creating the right
-	<tt>boot1.elf</tt> file for powerpc64 qemu booting, or the
-	more familiar (though needlessly complicated) x86 setup.
-	Previous versions of NanoBSD required too much specialized
-	knowledge from the user.  This work aims to concentrate the
-	knowledge into a set of simple scripts for any build
-	orchestration system to use.</p>
-
-      <p>Finally, NanoBSD images in the past have needed very
-	specific knowledge of the target device.  Part of this is a
-	legacy of the BIOS state-of-the-art a decade ago, which
-	required very careful matching of the image to the actual
-	device in the deployed system.  Although relevant at the time,
-	such systems are now vanishingly rare.  Support for them will
-	be phased out (though given the flexibility of NanoBSD, it can
-	be moved to the few remaining examples in the tree and also
-	partially covered by the generic image scripts).  Today, the
-	typical use case is to create an SD or microSD card image, and
-	have the image resize itself on boot.  NanoBSD now supports
-	that workflow.</p>
-
-      <p>In addition to these items, a number of minor improvements
-	have been made:</p>
-
-      <ul>
-	<li>Support for <tt>CPUTYPE</tt>-specialized builds.  This
-	  includes both NanoBSD support as well as important bug fixes
-	  in the base system.</li>
-
-	<li>Support for marking MBR partitions as active.</li>
-
-	<li>Support for more partition types.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p><tt>mkimg(8)</tt> needs to be augmented to create images
-	  for the i.MX6 and Allwinner (and others) SoCs.  These SoCs
-	  require a boot image to be written after the MBR, but before
-	  the first partition starts.</p>
-      </li><li>
-	<p>The chroot functionality of some NanoBSD configurations
-	  has not yet been migrated for non-privileged builds.</p>
-      </li><li>
-	<p>The functionality to manipulate <tt>mtree(8)</tt> files
-	  should be moved into the base system for use by other build
-	  orchestration tools.</p>
-      </li><li>
-	<p>The script to create a bootable image from one or more
-	  trees of files, as well as some creation of those trees,
-	  should be moved into the base system for use with other
-	  build orchestration tools.</p>
-      </li><li>
-	<p>The <tt>growfs</tt> functionality works great for single
-	  images growing to the whole disk.  However, NanoBSD would
-	  prefer that the boot FS/partition grow to approximately 1/2
-	  the size of the media and another identical (or close)
-	  partition be created for the ping-ponging upgrades that
-	  NanoBSD is setup for.  This needs to be implemented in the
-	  <tt>growfs</tt> <tt>rc.d(8)</tt> script.</p>
-      </li></ol><hr /><h2><a name="relaunchd" href="#relaunchd" id="relaunchd">relaunchd</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/mheily/relaunchd" title="https://github.com/mheily/relaunchd">Development tree on GitHub</a></td><td>
-	    URL: <a href="https://github.com/mheily/relaunchd" title="Development tree on GitHub">https://github.com/mheily/relaunchd</a></td></tr></table><p>
-	Contact:
-	  Mark
-	  Heily
-	 &lt;<a href="mailto:mark@heily.com">mark@heily.com</a>&gt;
-	</p>
-      <p>The <tt>relaunchd</tt> project provides a service
-	management daemon that is similar to the original
-	<a href="https://en.wikipedia.org/wiki/Launchd" shape="rect">launchd</a>
-	introduced in Apple OS X.</p>
-
-      <p>It is not limited to the original features of
-	<tt>launchd</tt>, however: interesting work is being done to
-	add support for launching programs in jails, passing socket
-	descriptors from the host to a jail, and launching programs
-	within a preconfigured <tt>capsicum(4)</tt> sandbox.
-	Additionally, <tt>relaunchd</tt> uses UCL for its
-	configuration files, so jobs can be defined in JSON or other
-	formats supported by UCL.</p>
-
-      <p>While there is still work to be done, most of the important
-	features of the original <tt>launchd</tt> have been
-	implemented, and <tt>relaunchd</tt> has been made available in
-	the FreeBSD Ports Collection.  It should still be considered
-	experimental and not ready for production use, but everyone is
-	welcome to try it, report issues, and contribute code or ideas
-	for improvement.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Add support for restarting jobs if they crash.</p>
-      </li><li>
-	<p>Implement the <tt>cron(8)</tt> emulation feature.</p>
-      </li><li>
-	<p>Add support for monitoring files and directories for
-	  changes and launching jobs when changes are detected.</p>
-      </li><li>
-	<p>Finish things that are incomplete, such as support for
-	  jails and passing open socket descriptors to child
-	  processes.</p>
-      </li><li>
-	<p>Improve the documentation and provide more examples of
-	  usage.</p>
-      </li></ol><hr /><h2><a name="System-Initialization-and-Service-Management" href="#System-Initialization-and-Service-Management" id="System-Initialization-and-Service-Management">System Initialization and Service Management</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonspawn.org/2016/01/a-comparison-of-alternatives-to-init8.html" title="http://www.daemonspawn.org/2016/01/a-comparison-of-alternatives-to-init8.html">A Comparison of init(8) and rc(8) Replacements</a></td><td>
-	    URL: <a href="http://www.daemonspawn.org/2016/01/a-comparison-of-alternatives-to-init8.html" title="A Comparison of init(8) and rc(8) Replacements">http://www.daemonspawn.org/2016/01/a-comparison-of-alternatives-to-init8.html</a></td></tr></table><p>
-	Contact:
-	  Mark
-	  Heily
-	 &lt;<a href="mailto:mark@heily.com">mark@heily.com</a>&gt;
-	<br />
-	Contact:
-	  Jonathan
-	  de Boyne Pollard
-	 &lt;<a href="mailto:J.deBoynePollard-newsgroups@NTLWorld.COM">J.deBoynePollard-newsgroups@NTLWorld.COM</a>&gt;
-	<br />
-	Contact:
-	  Jordan
-	  Hubbard
-	 &lt;<a href="mailto:jkh@FreeBSD.org">jkh@FreeBSD.org</a>&gt;
-	</p>
-      <p>There are three active projects to provide an alternative
-	to the traditional <tt>init(8)</tt> and <tt>rc(8)</tt>
-	subsystems that manage the boot process and system services.
-	There are a number of reasons driving the desire for change,
-	including:</p>
-
-      <ul>
-	<li>Faster boot times, made possible by launching services
-	  in parallel</li>
-
-	<li>Greater reliability, by ensuring that services are
-	  automatically restarted if they terminate unexpectedly</li>
-
-	<li>Simplified dependency management, using socket
-	  activation and similar techniques</li>
-
-	<li>The ability to launch services "on demand",
-	  and have them self-terminate when idle</li>
-
-	<li>Improved security, by removing the need to start common
-	  daemons as the root user</li>
-      </ul>
-
-      <p> Two of the projects, <tt>launchd</tt> and
-	<tt>relaunchd</tt>, are based on the <tt>launchd(8)</tt> API
-	introduced by Apple in Mac OS X.  The NextBSD project has
-	ported the original Apple source code by writing a Mach
-	compatibility layer that allows <tt>launchd</tt> to run on
-	FreeBSD.  The <tt>relaunchd</tt> project started from scratch
-	with the goal of creating a more modular, lightweight, and
-	portable implementation of the <tt>launchd</tt> API.  The
-	third project, <tt>nosh</tt>, is a unique creation that
-	borrows concepts from <tt>launchd</tt>, <tt>systemd</tt>, and
-	several other Unix operating systems.</p>
-
-      <p>While the FreeBSD Project has not made a decision to replace the
-	current <tt>init(8)</tt> and <tt>rc(8)</tt> subsystems, the
-	existence and active development of alternatives will continue
-	to drive innovation in this space.</p>
-
-      <p>Jordan Hubbard is the contact point for the NextBSD
-	<tt>launchd</tt>, Jonathan de Boyne Pollard is the contact
-	point for <tt>nosh</tt>, and Mark Heily is the contact point
-	for <tt>relaunchd</tt>.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">Foundation Website</a></td><td>
-	    URL: <a href="http://www.FreeBSDFoundation.org/" title="Foundation Website">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://FreeBSDJournal.com/" title="http://FreeBSDJournal.com/">FreeBSD Journal</a></td><td>
-	    URL: <a href="http://FreeBSDJournal.com/" title="FreeBSD Journal">http://FreeBSDJournal.com/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to supporting and promoting the FreeBSD
-	Project and community worldwide.  Funding comes from
-	individual and corporate donations and is used to fund and
-	manage development projects, conferences and developer
-	summits, and provide travel grants to FreeBSD developers.  The
-	Foundation purchases hardware to improve and maintain FreeBSD
-	infrastructure and publishes FreeBSD white papers and marketing
-	material to promote, educate, and advocate for the FreeBSD
-	Project.  The Foundation also represents the FreeBSD Project in
-	executing contracts, license agreements, and other legal
-	arrangements that require a recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD
-	last quarter:</p>
-
-      <p>On the advocacy front, the Foundation attended and
-	sponsored EuroBSDcon, which took place Oct 1-4
-	(<a href="https://2015.eurobsdcon.org/" shape="rect">https://2015.eurobsdcon.org/</a>)
-	in Stockholm, Sweden.  Two days prior, during the developer
-	summit, Deb Goodkin ran a session on Recruiting to FreeBSD.  The
-	Foundation was also very active during the event itself; in
-	addition to Deb, we had Dru Lavigne, Kirk McKusick, Erwin Lansing,
-	Ed Maste, Hiroki Sato, Benedict Reuschling, and Edward Tomasz Napiera&#322;a attend the
-	conference.  Deb and Ed gave a presentation on how the
-	Foundation supports a BSD project.  Kirk gave a presentation
-	on "a Brief History of the BSD Fast File System,"
-	and he taught the two-day tutorial "Introduction to the
-	FreeBSD Open-Source Operating System."</p>
-
-      <p>Deb then attended the 2015 Grace Hopper Conference that was
-	held in Houston, TX, October 14-16.  The conference is for
-	women in computing and most of the attendees were female
-	computer science majors, female software developers, and
-	college professors.  The Foundation was proud to be a Silver
-	Sponsor.  The conference was very successful for us.  Our
-	presence allowed us to raise awareness of the Project, help
-	recruit more women, and get more professors to include FreeBSD in
-	their curriculum.</p>
-
-      <p>George V. Neville-Neil traveled to Bangkok, Thailand to present talks on
-	DTrace, FreeBSD, and teaching with DTrace.  The talks were
-	presented at Chulalongkorn University, which is the largest
-	University in Thailand with the largest engineering school.
-	The first talk was the practitioner's introduction to DTrace
-	in which the technology, history and usage is explained
-	without diving into all the kernel subsystems.  The second was
-	the sales pitch for teaching with Dtrace and with FreeBSD.  The
-	pitch was well received and there were some very good points
-	made by the audience.  The facts that the course materials are
-	both open source and hosted on github were also well
-	received.</p>
-
-      <p>Kirk McKusick completed a 10-hour tutorial about FreeBSD for
-	Pearson Education in their "Live Lesson" program.
-	In particular, there is a great free snippet from that course
-	comparing FreeBSD against Linux here:
-	<a href="http://youtu.be/dTpqALCwQ1Y?a" shape="rect">http://youtu.be/dTpqALCwQ1Y?a</a>.
-	Find out more about the whole session at:
-	<a href="http://click.linksynergy.com/fs-bin/click?id=NZS3W7D*uS0&amp;subid=&amp;offerid=163217.1&amp;type=10&amp;tmpid=3559&amp;RD_PARM1=http%253A%252F%252Fwww.informit.com%252Fstore%252Fintroduction-to-the-FreeBSD-open-source-operating-system-9780134305868" shape="rect">http://click.linksynergy.com/fs-bin/click?id=NZS3W7D*uS0&amp;subid=&amp;offerid=163217.1&amp;type=10&amp;tmpid=3559&amp;RD_PARM1=http%253A%252F%252Fwww.informit.com%252Fstore%252Fintroduction-to-the-freebsd-open-source-operating-system-9780134305868</a>.</p>
-
-      <p>Anne Dickison resumed the Faces of FreeBSD series with
-	interviews featuring Michael Dexter and Erin Clark.  She also
-	continued to produce and distribute FreeBSD materials for
-	conferences, as well as advocating for FreeBSD over our social
-	channels.</p>
-
-      <p>George V. Neville-Neil headed up the latest Silicon Valley Vendor and
-	Developer Summit, November 2-3, at the NetApp campus in
-	Sunnyvale, California.  Topics of discussion ranged over new
-	developments in persistent memory, the use of FreeBSD by a
-	company that builds rackscale systems, developments in our
-	compiler and tool suite, as well as others.  Additional
-	Foundation Board and Staff attending the summit included: Deb
-	Goodkin, Glen Barber, Justin T. Gibbs, Kirk McKusick, Ed Maste, and
-	Hiroki Sato.  The complete schedule, and some of the slides, are
-	available on the FreeBSD Wiki
-	<a href="https://wiki.FreeBSD.org/201511VendorDevSummit" shape="rect">https://wiki.freebsd.org/201511VendorDevSummit</a>.</p>
-
-      <p>Notes from the always lively "Have/Need/Want
-	session" are available at
-	<a href="https://wiki.FreeBSD.org/201511VendorDevSummit/HaveNeedWant" shape="rect">https://wiki.freebsd.org/201511VendorDevSummit/HaveNeedWant</a>.</p>
-
-      <p>While in the Bay Area, some Foundation members visited
-	commercial users of FreeBSD to help understand their needs,
-	update them on the work the Foundation is doing, and
-	facilitate collaboration between them and the Project.</p>
-
-      <p>We were a sponsor of the 2015 OpenZFS Developer
-	Summit, which took place October 19-20, in San Francisco, CA.
-	Justin T. Gibbs and Kirk McKusick attended the conference.</p>
-
-      <p>Justin T. Gibbs continued his semester long class teaching
-	Intro to Computer Science using FreeBSD at a middle
-	school.</p>
-
-      <p>Ed Maste, Edward Tomasz Napiera&#322;a, and Konstantin Belousov continue to make
-	progress on Foundation funded development projects.  More
-	specifically:</p>
-
-      <ul>
-	<li>Ed Worked on a number of items relating to the
-	  tool chain: LLD linker, ELF Tool Chain components, and LLDB
-	  debugger, and tested, integrated, and merged outstanding
-	  UEFI work.</li>
-
-	<li>Edward finished work on the reroot project as well as
-	  spending some time on a certificate-transparency port.  He
-	  also implemented a prototype to support disk IO limit in
-	  RCTL.</li>
-
-	<li>Konstantin rewrote the out of memory killer logic, which,
-	  in particular, fixed FreeBSD operation on systems without swap,
-	  especially systems with very little memory.  The latter are
-	  becoming more and more common with the popularity of embedded
-	  ARM platforms where FreeBSD runs, but it also affects large
-	  systems which are usually configured without swap.  He also
-	  finalized and committed the shared page support for the
-	  ARMv7 and ARMv8 systems.  This allows for a non-executable
-	  stack on ARMv7, and a much faster userspace
-	  <tt>gettimeofday(2)</tt> for both, similar to x86.</li>
-      </ul>
-
-      <p>Ed Maste presented a FreeBSD/arm64 talk and a hands-on
-	demo at ARM Techcon, which took place November 10-12, 2015, in
-	Santa Clara, CA.</p>
-
-      <p>We continued publishing our monthly newsletters and
-	acquiring new company testimonials about using FreeBSD, including
-	from Verisign and Nginx.</p>
-
-      <p>Anne Dickison, Dru Lavigne, and Glen Barber represented the
-	Foundation at USENIX LISA '15, which took place November 3-8,
-	in Washington D.C..  The Foundation had a booth in the Expo
-	Hall and participated in a BoF.  Besides connecting with
-	current community members, we spoke with attendees who were
-	interested in getting involved with the Project and helped
-	set them on the correct path.  We also took the opportunity to
-	remind those who had not used FreeBSD in a while what they were
-	missing.  Glen also attended the USENIX Release Engineering
-	Summit, which was co-located with LISA '15.</p>
-
-      <p>We published the Sept/Oct and Nov/Dec issues of the
-	FreeBSD Journal.</p>
-
-      <p>George V. Neville-Neil and Robert Watson announced the release of
-	their TeachBSD initiative:
-	<a href="http://teachbsd.org/" shape="rect">http://teachbsd.org/</a>.
-	TeachBSD offers a set of open source reusable course materials designed to
-	allow others to teach both university students and software
-	practitioners FreeBSD operating system fundamentals.  The
-	Foundation is proud to have partly sponsored their efforts to
-	teach the initial graduate level course on operating systems
-	with tracing at the University of Cambridge.</p>
-
-      <p>Deb Goodkin invited a representative from the
-	Outreachy program to talk at the Ottawa FreeBSD Developer Summit
-	about the program and how we can get involved.</p>
-
-      <p>Deb also started discussions with CS professors from
-	the University of Colorado, Boulder to offer some Intro to
-	FreeBSD workshops.</p>
-
-      <p>Glen Barber continued wearing many hats to support to the
-	Project.  For Release Engineering:
-	<ul>
-	  <li>Added support for building <tt>BANANAPI</tt>,
-	    <tt>CUBIEBOARD</tt>, and <tt>CUBIEBOARD2</tt> arm
-	    images.</li>
-
-	  <li>Deprecated the use of MD5 checksums for verifying
-	    installation media downloaded from the FreeBSD Project
-	    mirrors.</li>
-
-	  <li>Various miscellaneous updates and fixes to release
-	    build code.</li>
-
-	  <li>Continued providing regular development snapshot
-	    builds.</li>
-	</ul>
-	Under Systems Administration:
-	<ul>
-	  <li>Assisted the Admins team with migrating various
-	    services to two new colocation facilities near Sunnyvale,
-	    generously provided by RootBSD and LimeLight
-	    Networks.</li>
-
-	  <li>Moved email services for the Foundation to a new
-	    server.</li>
-	</ul>
-      </p>
-
-      <p>Ed Maste attended the Reproducible Builds World
-	Summit, which took place in Athens, Greece, December 1-3,
-	2015.</p>
-
-      <p>We wrapped up our 2015 fundraising efforts with our
-	End-of-Year fundraising campaign by participating in
-	#GivingTuesday, and continuing with weekly email and social
-	media requests for support of the Foundation.  Final
-	fundraising numbers will be available in Q1 2016.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2016-01-2016-03.html b/website/content/en/status/report-2016-01-2016-03.html
deleted file mode 100644
index 81bd0febdf..0000000000
--- a/website/content/en/status/report-2016-01-2016-03.html
+++ /dev/null
@@ -1,2088 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>The first quarter of 2016 showed that FreeBSD retains a strong
-	sense of ipseity.  Improvements were pervasive, lending
-	credence to the concept of meliorism.</p><p>Panegyrics are relatively scarce, but not for lack of need.
-      Perhaps this missive might serve that function in some
-      infinitesimal way.</p><p>There was propagation, reformation, randomization,
-      accumulation, emulation, transmogrification, debuggenation, and
-      metaphrasal during this quarter.</p><p>In the financioartistic arena, pork snout futures narrowly
-      edged out pointilism, while parietal art remained fixed.</p><p>In all, a discomfiture of abundance.  View the rubrics below,
-      and marvel at their profusion and magnitude!  Marvel!</p><p>&#8212;Warren Block</p><p><hr /></p><p>Please submit status reports for the second quarter of 2016 by
-      July 7.  A thesaurus will be provided for submitters who do not
-      have one of their own.  We will need them back afterwards,
-      preferably with no new teeth marks on the covers.  Thank
-      you!</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Cluster-Admin">Cluster Admin</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Address-Space-Layout-Randomization">Address Space Layout Randomization</a></li><li><a href="#Ceph-on-FreeBSD">Ceph on FreeBSD</a></li><li><a href="#Process-Shared-Locks-for-libthr">Process-Shared Locks for libthr</a></li><li><a href="#RCTL-Disk-IO-Limits">RCTL Disk IO Limits</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ARM-Allwinner-SoC-Support">ARM Allwinner SoC Support</a></li><li><a href="#CAM-I/O-Scheduler">CAM I/O Scheduler</a></li><li><a href="#FDT-Overlay-Support-in-UBLDR">FDT Overlay Support in UBLDR</a></li><li><a href="#Filemon-Performance/Stability-Improvements">Filemon Performance/Stability Improvements</a></li><li><a href="#FreeBSD-Integration-Services-(BIS)">FreeBSD Integration Services (BIS)</a></li><li><a href="#Infiniband">Infiniband</a></li><li><a href="#MMC-Stack-Under-CAM-Framework">MMC Stack Under CAM Framework</a></li><li><a href="#NFS-Server">NFS Server</a></li><li><a href="#Static-Analysis-of-the-FreeBSD-Kernel-with-PVS-Studio">Static Analysis of the FreeBSD Kernel with PVS Studio</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#AmigaOne-X5000-Support">AmigaOne X5000 Support</a></li><li><a href="#FreeBSD-on-Cavium-ThunderX-(arm64)">FreeBSD on Cavium ThunderX (arm64)</a></li><li><a href="#powerpcspe-Target">powerpcspe Target</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#ELF-Tool-Chain-Tools">ELF Tool Chain Tools</a></li><li><a href="#Native-PCI-express-HotPlug">Native PCI-express HotPlug</a></li><li><a href="#Updates-to-GDB">Updates to GDB</a></li><li><a href="#Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD">Using lld, the LLVM Linker, to Link
-      FreeBSD</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#GitLab-Port">GitLab Port</a></li><li><a href="#GNOME-on-FreeBSD">GNOME on FreeBSD</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Obsoleting-Rails-3">Obsoleting Rails 3</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#New-FreeBSD-Mastery-Books">New FreeBSD Mastery Books</a></li><li><a href="#Spanish-FAQ-and-Chinese-Porter's-Handbook-Translations">Spanish FAQ and Chinese Porter's Handbook
-      Translations</a></li><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-Build">FreeBSD Build</a></li><li><a href="#Qt-5.6-on-Raspberry-Pi">Qt 5.6 on Raspberry Pi</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="Cluster-Admin" href="#Cluster-Admin" id="Cluster-Admin">Cluster Admin</a></h2><p>
-	Contact:  &lt;<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>&gt;
-	</p>
-      <p>This quarter, we:</p>
-      <ul>
-	<li>migrated services out of the hosting space in ISC
-	  (peter, sbruno)</li>
-
-	<li>began migration of services into the RootBSD hosting space
-	  (peter, sbruno)</li>
-
-	<li>collaborated with the phabricator admin team to migrate to
-	  a new and improved host in NYI. (allanjude, peter,
-	  sbruno)</li>
-
-	<li>installed a new and beefier Jenkins machine (gnn, lwshu,
-	  sbruno)</li>
-
-	<li>are still looking for more Asian mirrors for pkg, svn, and ftp
-	  (Japan, India). (sbruno)</li>
-
-	<li>completed the migration of the Taiwanese mirror to its new location.
-	  (lwshu)</li>
-
-	<li>started hosting a clang/llvm buildbbot in the FreeBSD cluster
-	  at NYI (sbruno, emaste)</li>
-
-	<li>resolved a UK mirror outage with Bytemark (gavin,
-	  peter)</li>
-      </ul>
-    <hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the first quarter of 2016, the most important business
-	of the FreeBSD Core Team has been to respond to the harassment
-	incident last year.  Core's actions were to assemble a
-	timeline of the events and in the light of that to review
-	Core's actions at the time; and to make recommendations about
-	how better to handle such cases in future.  During this
-	process, draft reports were reviewed by people concerned in
-	the case and in addition a number of interested members of the
-	FreeBSD community.  Core would like to thank everyone involved
-	for their contributions.</p>
-
-      <p>The report was published to the FreeBSD developer community in
-	mid-February, and contained six recommendations for the
-	community to consider.</p>
-
-      <p>Core is also coordinating with the committee headed by Anne
-	Dickison who are reviewing the Code of Conduct.  A corpus of
-	case studies is being assembled, which will be re-examined to
-	see what impact changes to the Code of Conduct would have
-	had.</p>
-
-      <p>Core, together with John Baldwin, are working on a plan to
-	create a separate repository containing GPLv3 toolchain
-	components.  This will allow modernization of code within base
-	beyond what the existing GPLv2 toolchain can handle, and
-	permit support of certain new architectures where a copyfree
-	licensed alternative (i.e., LLVM) is not yet available.  A
-	position paper will soon be circulated to developers for
-	comment.</p>
-
-      <p>During this quarter three new commit bits were issued, and
-	one was returned for safekeeping.  Please welcome Wojciech
-	Macek, Jared McNeil and Stanislav Galabov, and bid farewell to
-	Davide Italiano, who although too busy to work on FreeBSD
-	directly, will still be contributing through his work upstream
-	on lld and other parts of the toolchain.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Address-Space-Layout-Randomization" href="#Address-Space-Layout-Randomization" id="Address-Space-Layout-Randomization">Address Space Layout Randomization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://kib.kiev.ua/kib/aslr" title="https://kib.kiev.ua/kib/aslr">Patch Home</a></td><td>
-	    URL: <a href="https://kib.kiev.ua/kib/aslr" title="Patch Home">https://kib.kiev.ua/kib/aslr</a></td></tr><tr><td><a href="https://www.kib.kiev.ua/kib/aslr/paxtest.log" title="https://www.kib.kiev.ua/kib/aslr/paxtest.log">paxtest.log</a></td><td>
-	    URL: <a href="https://www.kib.kiev.ua/kib/aslr/paxtest.log" title="paxtest.log">https://www.kib.kiev.ua/kib/aslr/paxtest.log</a></td></tr><tr><td><a href="https://www.kib.kiev.ua/kib/aslr/fedora.log" title="https://www.kib.kiev.ua/kib/aslr/fedora.log">fedora.log</a></td><td>
-	    URL: <a href="https://www.kib.kiev.ua/kib/aslr/fedora.log" title="fedora.log">https://www.kib.kiev.ua/kib/aslr/fedora.log</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>I wrote a small and straightforward yet feature-packed patch
-	to implement ASLR for FreeBSD which is now available for broader
-	testing.</p>
-
-      <p>With this change, randomization is applied to all non-fixed
-	mappings.  By randomization, I mean that the base address for the
-	mapping is selected with a guaranteed amount of entropy
-	(bits).  If the mapping was requested to be superpage aligned,
-	the randomization honors the superpage attributes.</p>
-
-      <p>The randomization is done on a best-effort basis.  That is,
-	the allocator falls back to a first fit strategy if
-	fragmentation prevents entropy injection.  It is trivial to
-	implement a strong mode where failure to guarantee the
-	requested amount of entropy results in failure of the mapping
-	request failure, but I do not consider that to be usable.</p>
-
-      <p>I have not fine-tuned the amount of entropy injected right
-	now, but that is only a quantitive change that will not change the
-	implementation.  The current amount is controlled by
-	<tt>aslr_pages_rnd</tt>.</p>
-
-      <p>To not spoil coalescing optimizations, to reduce the page
-	table fragmentation inherent to ASLR, and to retain
-	transient superpage promotion for <tt>malloc</tt>ed
-	memory, locality is implemented for anonymous private
-	mappings, which are automatically grouped until fragmentation
-	kicks in.  The initial location for the anon group range is,
-	of course, randomized.  After some additional tuning, the
-	measures appeared to be quite effective.  In particular, a
-	very address-space-hungry build of PyPy 5.0 on i386
-	successfully finished with the most aggressive functionality
-	of the patch activated.</p>
-
-      <p>The default mode keeps the <tt>sbrk</tt> area unpopulated by
-	other mappings, but this can be turned off, which gives much
-	more breathing room on the small address-space architectures
-	(it is funny that
-	32 bits is now considered small).  This is tied with the question
-	of following an application's hint about the <tt>mmap(2)</tt>
-	base address.  Testing shows that ignoring the hint does not
-	affect the function of common applications, but I would expect that
-	more demanding code could break.  By default <tt>sbrk</tt> is
-	preserved and <tt>mmap</tt> hints are satisfied, which can be
-	changed by using the <tt>kern.elf{32,64}.aslr_care_sbrk</tt>
-	sysctls (currently enabled by default for wider testing).</p>
-
-      <p>Stack gap, W^X, shared page randomization, KASLR and other
-	techniques are explicitly out of scope for this work.</p>
-
-      <p>The <tt>paxtest</tt> results for the run with the previous
-	version 5 of the patch applied and aggressively tuned can be
-	seen at
-	<a href="https://www.kib.kiev.ua/kib/aslr/paxtest.log" shape="rect"><tt>paxtest.log</tt></a>.
-	For comparison, a run on Fedora 23 on the same machine is at
-	<a href="https://www.kib.kiev.ua/kib/aslr/fedora.log" shape="rect"><tt>fedora.log</tt></a>.</p>
-
-      <p>ASLR is enabled on a per-ABI basis, and currently is only
-	enabled on native i386 and amd64 (including compat 32-bit) and
-	ARMv6 ABIs.  I expect to test and enable ASLR for arm64 as
-	well, later.</p>
-
-      <p>A <tt>procctl(2)</tt> control for ASLR is implemented, but
-	I have not provided a userspace wrapper around the syscall.
-	In fact, the most reasonable control needed is per-image and
-	not per-process, but we have no tradition to put the
-	kernel-read attributes into the extattrs of a binary, so I am
-	still pondering that part and this also explains the
-	non-written tool.</p>
-
-      <p>Thanks to Oliver Pinter and Shawn Webb of the HardenedBSD
-	project for pursuing ASLR for FreeBSD.  Although this work is
-	not based on theirs, it was inspired by their efforts.</p>
-
-      <p>Thanks to Ed Maste, Robert Watson, John Baldwin, and Alan Cox
-	for some discussions about the patch, and for The FreeBSD
-	Foundation for directing me.</p>
-
-      <p>Bartek Rutkowski tested PyPy builds on i386, and David Naylor
-	helped with the port which was at the point of turbulence and
-	upgrade during the work.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ceph-on-FreeBSD" href="#Ceph-on-FreeBSD" id="Ceph-on-FreeBSD">Ceph on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ceph.com" title="http://ceph.com">Ceph Main Site</a></td><td>
-	    URL: <a href="http://ceph.com" title="Ceph Main Site">http://ceph.com</a></td></tr><tr><td><a href="https://github.com/ceph/ceph" title="https://github.com/ceph/ceph">Main Repository</a></td><td>
-	    URL: <a href="https://github.com/ceph/ceph" title="Main Repository">https://github.com/ceph/ceph</a></td></tr><tr><td><a href="https://github.com/wjwithagen/ceph" title="https://github.com/wjwithagen/ceph">My Fork</a></td><td>
-	    URL: <a href="https://github.com/wjwithagen/ceph" title="My Fork">https://github.com/wjwithagen/ceph</a></td></tr><tr><td><a href="https://github.com/ceph/ceph/pull/7573" title="https://github.com/ceph/ceph/pull/7573">The git pull with All Changes</a></td><td>
-	    URL: <a href="https://github.com/ceph/ceph/pull/7573" title="The git pull with All Changes">https://github.com/ceph/ceph/pull/7573</a></td></tr></table><p>
-	Contact:
-	  Willem Jan
-	  Withagen
-	 &lt;<a href="mailto:wjw@digiware.nl">wjw@digiware.nl</a>&gt;
-	</p>
-      <p>Ceph is a distributed object store and file system designed
-	to provide excellent performance, reliability and
-	scalability.</p>
-
-      <ul>
-	<li>
-	  <p>Object Storage</p>
-
-	  <p>Ceph provides seamless access to objects using native
-	    language bindings or <tt>radosgw</tt>, a REST interface that is
-	    compatible with applications written for S3 and 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>
-
-	  <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>
-      </ul>
-
-      <p>I started looking into Ceph, because the HAST solution with
-	CARP and <tt>ggate</tt> did not really do what I wanted.  But
-	I am aiming for running a Ceph storage cluster of storage
-	nodes that are running ZFS.  The end station would be running
-	<tt>bhyve</tt> on RBD disk that are stored in Ceph.</p>
-
-      <p>The FreeBSD build will build most of the tools in Ceph.  Note
-	that the RBD-dependent items will not work since FreeBSD does
-	not have RBD yet.</p>
-
-      <p>Compiling and building Ceph is tested on 11-CURRENT.  It uses
-	the Clang toolset that is available, which needs to be at
-	least 3.7.  Clang 3.4 (on 10.2-STABLE) does not have all the
-	required capabilities to compile everything.</p>
-
-      <p>This setup will get things running for FreeBSD:</p>
-
-      <ul>
-	<li>
-	  <p>Install <tt>bash</tt> and link it in <tt>/bin</tt> (requires root
-	    privileges):</p>
-
-	  <p><tt>sudo pkg install bash</tt></p>
-
-	  <p><tt>sudo ln -s /usr/local/bin/bash /bin/bash</tt></p>
-	</li>
-
-	<li>
-	  <p>Building Ceph</p>
-
-	  <p><tt>git clone https://github.com/wjwithagen/ceph.git</tt></p>
-
-	  <p><tt>cd ceph</tt></p>
-
-	  <p><tt>git checkout wip-wjw-freebsd-tests</tt></p>
-
-	  <p><tt>./do_freebsd.sh</tt></p>
-	</li>
-      </ul>
-
-      <p>Parts Not Yet Included:</p>
-
-      <ul>
-	<li>
-	  <p>RBD</p>
-
-	  <p>Rados Block Devices is implemented in the Linux kernel.
-	    It seems that there used to be a userspace implementation
-	    first.  And perhaps <tt>ggated</tt> could be used as a
-	    template since it does some of the same functions, other
-	    than just between two disks.  And it has a userspace
-	    counterpart.</p>
-	</li>
-
-	<li>
-	  <p>BlueStore</p>
-
-	  <p>FreeBSD and Linux have a different AIO API, and that
-	    needs to be made compatible.  Next to that is the
-	    discussion in FreeBSD about <tt>aio_cancel</tt> not
-	    working for all device types.</p>
-	</li>
-
-	<li>
-	  <p>CephFS</p>
-
-	  <p>Cython tries to access an internal field in dirent which
-	    does not compile.</p>
-	</li>
-      </ul>
-
-      <p>Tests that verify the correct working of the above are also
-	excluded from the test set.</p>
-
-      <p>Tests Not Yet Included:</p>
-
-      <ul>
-	<li>
-	  <p><tt>ceph-detect-init/run-tox.sh</tt></p>
-
-	  <p>Because the current implementation does not know anything
-	    about FreeBSD's rc/init.</p>
-	</li>
-
-	<li>
-	  <p>Tests that make use of <tt>nosestests</tt></p>
-
-	  <p>Calling these does not really work since
-	    <tt>nosetests</tt> is not in <tt>/usr/bin</tt>, and
-	    calling through <tt>/usr/bin/env nosetests</tt> does not
-	    work on FreeBSD.</p>
-	</li>
-
-	<li>
-	  <p><tt>test/pybind/test_ceph_argparse.py</tt></p>
-	</li>
-
-	<li>
-	  <p><tt>test/pybind/test_ceph_daemon.py</tt></p>
-	</li>
-      </ul>
-
-      <p>Things To Investigate:</p>
-
-      <ul>
-	<li>
-	  <p><tt>ceph-{osd,mon}</tt> need two signals before they
-	    actually terminate.</p>
-	</li>
-
-	<li>
-	  <p><tt>ceph_erasure_code --debug-osd 20 --plugin_exists jerasure</tt>
-	    crashes due to SIGSEGV.  This is a pointer reference that
-	    gets modified outside the regular programflow.  Probably
-	    due to a programming error but perhaps wrong mixing and
-	    matching of many libraries.</p>
-	</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The current and foremost task is to get the test set to
-	  complete without errors.  This includes fixing several
-	  coredumps.</p>
-
-	<p>Run integration tests to see if the FreeBSD daemons will
-	  work with a Linux Ceph platform.</p>
-      </li><li>
-	<p>Get the Python tests that are currently excluded to work,
-	  and test OKE.</p>
-      </li><li>
-	<p>Compile and test the user space RBD (Rados Block
-	  Device).</p>
-
-	<p>Investigate and see if an in-kernel RBD device could be
-	  developed akin to <tt>ggate</tt>.</p>
-      </li><li>
-	<p>Integrate the FreeBSD <tt>/etc/rc.d</tt> init scripts in
-	  the Ceph stack for testing and running Ceph on production
-	  machines.</p>
-      </li></ol><hr /><h2><a name="Process-Shared-Locks-for-libthr" href="#Process-Shared-Locks-for-libthr" id="Process-Shared-Locks-for-libthr">Process-Shared Locks for libthr</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>POSIX specifies several kinds of <tt>pthread</tt> locks.  For
-	this report, the private and process-shared variants are
-	considered.  Private locks can be used only by the threads of
-	the same process, which share a single common address space.
-	Process-shared locks can be used by threads from any process,
-	assuming the process can map the lock memory into its address
-	space.</p>
-
-      <p>Our <tt>libthr</tt>, the library implementing the POSIX
-	threads and locking operations, uses a pointer as the internal
-	representation behind a lock.  The pointer contains the
-	address of the actual structure carrying the lock.  This has
-	unfortunate consequences for implementing the
-	<tt>PTHREAD_PROCESS_SHARED</tt> attribute for locks, since
-	really only the pointer is shared when a lock is mapped into
-	distinct address spaces.</p>
-
-      <p>A common opinion was that we have no choice but to break the
-	<tt>libthr</tt> Application Binary Interface (ABI) by changing
-	the lock types to be the actual lock structures (and padding
-	for future ABI extension).  This is very painful for users, as
-	our previous experience with non-versioned <tt>libc</tt> and
-	<tt>libc_r</tt> has shown.</p>
-
-      <p>Instead, I proposed and implemented a scheme where
-	process-shared locks can be implemented without breaking the
-	ABI.  The lock memory is used as a key into a system-global
-	hash of shared memory objects (off-pages), which contain the
-	actual lock structures.</p>
-
-      <p>New <tt>umtx</tt> operations to create or look up a shared
-	object by memory key were added.  <tt>libthr</tt> is
-	modified to look up the object and use it for shared locks,
-	instead of using <tt>malloc()</tt> as for private locks.</p>
-
-      <p>The pointer value in the user-visible lock type contains a
-	canary for shared locks.  <tt>libthr</tt> detects the canary
-	and switches into the shared-lock mode.</p>
-
-      <p>The proposal of inlining the lock structures, besides the
-	drawbacks of breaking ABI, has its merits.  Most important,
-	the inlining avoids the need for indirection.  Another
-	important advantage over the off-page approach is that no
-	off-page object needs to be maintained, and the lifecycle of
-	the shared lock naturally finishes with the destruction of the
-	shared memory, without need for explicit cleanup.  Right now, off-pages
-	hook into vm object termination to avoid leakage, but
-	long-livedness of the vnode vm object prolongs the off-page's
-	existence for shared locks backed by files, however unlikely
-	they may be.</p>
-
-      <p><tt>libthr</tt> with inlined locks became informally known as
-	the <tt>libthr2</tt> project, since it is better to change the
-	library name than just bumping the library version.
-	<tt>rtld</tt> should ensure that <tt>libthr</tt> and
-	<tt>libthr2</tt> are not simultaneously loaded into a single
-	address space.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Implement robust mutexes.</p>
-      </li><li>
-	<p>Evaluate and implement <tt>libthr2</tt>.</p>
-      </li></ol><hr /><h2><a name="RCTL-Disk-IO-Limits" href="#RCTL-Disk-IO-Limits" id="RCTL-Disk-IO-Limits">RCTL Disk IO Limits</a></h2><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>An important missing piece of the RCTL resource limits
-	framework was the ability to limit file system throughput.
-	This project aims to fill that hole by making it possible to
-	add RCTL rules for read bytes per second (BPS), write BPS,
-	read I/O operations per second (IOPS), and write IOPS, and
-	adding a new throttling mechanism to slow down offending
-	processes when a limit gets hit.</p>
-
-      <p>The code has been committed and will ship with FreeBSD
-	11.0-RELEASE.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Additional testing</p>
-      </li><li>
-	<p>Simplify locking, getting rid of <tt>rctl_lock</tt> altogether</p>
-      </li><li>
-	<p>Improve statistics gathering by making it possible for
-	  <tt>rctl -u</tt> to retrieve usage counters at a fixed point
-	  in time</p>
-      </li><li>
-	<p>Use the new throttling mechanism for %CPU limits</p>
-      </li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">Graphics Stack Roadmap and Supported Hardware Matrix</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Graphics" title="Graphics Stack Roadmap and Supported Hardware Matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-graphics" title="https://github.com/freebsd/freebsd-ports-graphics">Ports Development Tree on GitHub</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-graphics" title="Ports Development Tree on GitHub">https://github.com/freebsd/freebsd-ports-graphics</a></td></tr><tr><td><a href="https://fosdem.org/2016/schedule/event/freebsd_graphic_stack/" title="https://fosdem.org/2016/schedule/event/freebsd_graphic_stack/">FreeBSD Graphics Team at FOSDEM 2016</a></td><td>
-	    URL: <a href="https://fosdem.org/2016/schedule/event/freebsd_graphic_stack/" title="FreeBSD Graphics Team at FOSDEM 2016">https://fosdem.org/2016/schedule/event/freebsd_graphic_stack/</a></td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes" title="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes">GSoC 2016: link /dev Entries to sysctl Nodes</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes" title="GSoC 2016: link /dev Entries to sysctl Nodes">https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes</a></td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_redesign_and_rewrite_libdevq" title="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_redesign_and_rewrite_libdevq">GSoC 2016: Redesign libdevq</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_redesign_and_rewrite_libdevq" title="GSoC 2016: Redesign libdevq">https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_redesign_and_rewrite_libdevq</a></td></tr><tr><td><a href="http://planet.freebsd.org/graphics/" title="http://planet.freebsd.org/graphics/">Graphics Team Blog</a></td><td>
-	    URL: <a href="http://planet.freebsd.org/graphics/" title="Graphics Team Blog">http://planet.freebsd.org/graphics/</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Graphics team
-	 &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	</p>
-      <p>The major news for this quarter is the update of the i915
-	driver in the kernel!  The driver now matches Linux 3.8.13, so
-	it includes initial Haswell support.  Linux 3.8 is already
-	three years old, but work continues to upgrade DRM further.
-	In particular, work commenced to move to using the
-	<tt>linuxkpi</tt> compatibility.</p>
-
-      <p>In the Ports tree, Mesa was updated to 11.1.2. The next minor
-	release, 11.2.0, is ready for testing in our development tree.
-	We also updated libclc to 0.2.0.20151006, a library used by
-	Mesa to provide OpenCL support.  Upstream patches were added
-	to beignet so all these ports now use the same LLVM
-	version.</p>
-
-      <p>We attended FOSDEM 2016 in Brussels.  Jean-S�bastien P�dron
-	gave a talk to explain the work of the graphics team and show
-	how people can contribute.  It was well received and the
-	presentation was followed by interesting discussions.  FOSDEM
-	was also a nice occasion to meet and talk again to the nice
-	upstream developers of the graphics stack.</p>
-
-      <p>For the first year, we added two ideas for GSoC 2016: one for
-	a kernel task, one to redesign <tt>libdevq</tt>.  Six students
-	submitted proposals for those ideas; that was unexpected!
-	We now need to decide which one we want to mentor and the
-	choice is difficult.</p>
-
-      <p>Our blog has moved to a
-	<a href="http://planet.freebsd.org/graphics/" shape="rect">new location</a>
-	(linked above).</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>See the "Graphics" wiki page for up-to-date
-	  information.</p>
-      </li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="ARM-Allwinner-SoC-Support" href="#ARM-Allwinner-SoC-Support" id="ARM-Allwinner-SoC-Support">ARM Allwinner SoC Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/FreeBSD/arm/Allwinner" title="https://wiki.freebsd.org/FreeBSD/arm/Allwinner">Allwinner FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/FreeBSD/arm/Allwinner" title="Allwinner FreeBSD Wiki">https://wiki.freebsd.org/FreeBSD/arm/Allwinner</a></td></tr></table><p>
-	Contact:
-	  Jared
-	  McNeill
-	 &lt;<a href="mailto:jmcneill@FreeBSD.org">jmcneill@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Emmanuel
-	  Vadot
-	 &lt;<a href="mailto:manu@bidouilliste.com">manu@bidouilliste.com</a>&gt;
-	</p>
-      <p>Allwinner SoCs are used in multiple hobbyist devboards and
-	single-board computers.  Recently, support for these SoCs has
-	received a lot of updates</p>
-
-      <p>Task done during first quarter:</p>
-
-      <ul>
-	<li>I2C</li>
-
-	<li>HDMI output</li>
-
-	<li>Basic AXP209 support (Power Management Unit)</li>
-
-	<li>Switch to upstream DTS for most boards</li>
-
-	<li>Basic Support for A31/A31S SoC</li>
-
-	<li>RTC</li>
-
-	<li>Proper Pinmux/GPIO support</li>
-
-	<li>Audio Codec / Audio HDMI</li>
-
-	<li>A10/A20 DMA support</li>
-
-	<li>A20 now uses the GIC (General Interrupt Controller)</li>
-
-	<li>A20 now uses the ARM Generic Timer</li>
-      </ul>
-
-      <p>Ongoing tasks:</p>
-
-      <ul>
-	<li>Switch to a new clock framework
-	  <a href="https://reviews.freebsd.org/D5752" shape="rect">(In review)</a></li>
-
-	<li>Convert the A10 interrupt controller to INTRNG
-	  <a href="https://reviews.freebsd.org/D5573" shape="rect">(In review)</a></li>
-
-	<li>OHCI support
-	  <a href="https://reviews.freebsd.org/D5481" shape="rect">(In review)</a></li>
-
-	<li>Generic ALLWINNER kernel config file
-	  <a href="https://reviews.freebsd.org/D5580" shape="rect">(In review)</a></li>
-
-	<li>A20/A31 NMI support
-	  <a href="https://reviews.freebsd.org/D5663" shape="rect">(In review)</a></li>
-
-	<li>USB OTG</li>
-
-	<li>Finish the switch to using upstream DTS files</li>
-
-	<li>A83T SoC Support</li>
-
-	<li>H3 SoC Support</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>
-	<p>SPI driver</p>
-      </li><li>
-	<p>LCD Support</p>
-      </li><li>
-	<p>Any unsupported hardware device that might be of
-	  interest.</p>
-      </li></ol><hr /><h2><a name="CAM-I/O-Scheduler" href="#CAM-I/O-Scheduler" id="CAM-I/O-Scheduler">CAM I/O Scheduler</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf" title="https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf">I/O Scheduling in FreeBSD's CAM Subsystem (PDF)</a></td><td>
-	    URL: <a href="https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf" title="I/O Scheduling in FreeBSD's CAM Subsystem (PDF)">https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf</a></td></tr><tr><td><a href="https://www.youtube.com/watch?v=3WqOLolj5EU" title="https://www.youtube.com/watch?v=3WqOLolj5EU">The BSDCan 2015 Talk</a></td><td>
-	    URL: <a href="https://www.youtube.com/watch?v=3WqOLolj5EU" title="The BSDCan 2015 Talk">https://www.youtube.com/watch?v=3WqOLolj5EU</a></td></tr></table><p>
-	Contact:
-	  Warner
-	  Losh
-	 &lt;<a href="mailto:wlosh@netflix.com">wlosh@netflix.com</a>&gt;
-	</p>
-      <p>An enhanced CAM I/O scheduler has been committed to the tree.
-	By default, this scheduler implements the old behavior.
-	In addition, an advanced adaptive scheduler is available.
-	Along with the scheduler, SATA disks can now use Queued Trims
-	with devices that support them.  Details about the new
-	scheduler are available in the
-	<a href="https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf" shape="rect">I/O Scheduling in FreeBSD's CAM Subsystem article (PDF)</a>
-	or from
-	<a href="https://www.youtube.com/watch?v=3WqOLolj5EU" shape="rect">the BSDCan 2015 talk</a>.</p>
-
-      <p>The adaptive I/O scheduler is disabled by default, but can be
-	enabled with <tt>options CAM_ADAPTIVE_IOSCHED</tt> in the kernel config
-	file.  This scheduler allows favoring reads over writes (or
-	vice versa), controlling the IOPs, bandwidth, or concurrent
-	operations (read, write, trim), and permits the selection of
-	static or dynamic control of these operations.  In addition, a
-	number of statistics are collected for drive operations that
-	are published via sysctl.  One advanced use for the adaptive
-	I/O scheduler is to compensate for deficiencies in some
-	consumer-grade SSDs.  These SSDs exhibit a performance cliff
-	if too much data is written to them too quickly due to
-	internal garbage collection.  Without the I/O scheduler, read
-	and write performance drop substantially once garbage
-	collection kicks in.  The adaptive I/O scheduler can be
-	configured to monitor read latency.  As read latency climbs,
-	the I/O scheduler reduces the allowed write throughput, within
-	limits, to attempt to maximize read performance.  A simple use
-	of the adaptive I/O scheduler would be to limit write
-	bandwidth, IOPs or concurrent operations statically.</p>
-
-      <p>Future work on the I/O scheduler will be coupled with
-	improvements to the upper layers.  The upper layers will be
-	enhanced to communicate how urgent I/O requests are.  The I/O
-	scheduler will inform the upper layers of how full the I/O
-	queues are, so less urgent I/O can be submitted to the lower
-	layers as quickly as possible without overwhelming the lower
-	layers or starving other devices of requests.</p>
-    <p>This project was sponsored by Netflix.</p><hr /><h2><a name="FDT-Overlay-Support-in-UBLDR" href="#FDT-Overlay-Support-in-UBLDR" id="FDT-Overlay-Support-in-UBLDR">FDT Overlay Support in UBLDR</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D3180" title="https://reviews.freebsd.org/D3180">ubldr Patch</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D3180" title="ubldr Patch">https://reviews.freebsd.org/D3180</a></td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>A flattened device tree is a way to keep the hardware
-	description separated from code.  During the boot process, the
-	loader passes a pointer to the device-tree blob to the kernel
-	and the kernel instantiates and attaches drivers according to
-	the information in the blob.</p>
-
-      <p>This approach does not work when the hardware is expandable.  For
-	example, the Raspberry Pi and Beaglebone Black have the
-	concept of capes or shields: snap-on PCBs that are connected
-	to IO headers on the main board and provide additional
-	functionality like an LCD screen or GPS receiver.  These
-	shields can be described by their own device trees and these
-	trees can be overlaid on the base tree by the boot loader,
-	thus providing an accurate description to the kernel.</p>
-
-      <p>The proposed patch adds this functionality to <tt>ubldr</tt>.  The user
-	can specify a comma-separated list of overlays to U-Boot or
-	the loader <tt>fdt_overlays</tt> variable and <tt>ubldr</tt> will load
-	them from the <tt>/boot/dtb/</tt> directory and do the
-	overlaying.</p>
-    <hr /><h2><a name="Filemon-Performance/Stability-Improvements" href="#Filemon-Performance/Stability-Improvements" id="Filemon-Performance/Stability-Improvements">Filemon Performance/Stability Improvements</a></h2><p>
-	Contact:
-	  Bryan
-	  Drewery
-	 &lt;<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mateusz
-	  Guzik
-	 &lt;<a href="mailto:mjg@FreeBSD.org">mjg@FreeBSD.org</a>&gt;
-	</p>
-      <p>Filemon is a kernel module for tracing which files a command
-	creates, reads, writes, or executes.  It allows tracking build
-	dependencies in combination with <tt>bmake</tt>'s meta mode.
-	<tt>bmake</tt> stores filemon's output in a <tt>.meta</tt>
-	file along with the build command and later uses this to
-	trigger a rebuild of the target if any of the files referenced
-	are missing or modified, or if the build command changes.  It
-	provides the same functionality as the compiler's <tt>-MF</tt> flag,
-	but for everything.  It will be critical for buildworld's
-	<tt>WITH_META_MODE</tt> (which is the normal buildworld but
-	only using filemon) to provide a reliable incremental build
-	without even the need for <tt>.depend</tt> files or compiler
-	<tt>-MF</tt> flags.  This allows <tt>-DNO_CLEAN</tt> to work
-	all of the time.</p>
-
-      <p>Filemon on -HEAD was improved for stability and performance
-	over this quarter.  It no longer causes every syscall it hooks
-	into to loop over processes looking for a matching filemon
-	struct.  It now just attaches directly to the struct proc with
-	its own pointer.  This improves performance by reducing lock
-	contention during a build.  Much other work went into
-	improving error handling and other stability issues in the
-	module as well.</p>
-
-      <p>All of this work was done by Bryan Drewery, sponsored by EMC,
-	but much help and identification of bugs was provided by
-	Mateusz Guzik.</p>
-    <p>This project was sponsored by EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li>
-	<p>Improve credential handling.</p>
-      </li><li>
-	<p>Improve EVENTHANDLER performance.</p>
-      </li><li>
-	<p>Possibly provide a framework for syscallenter/syscallret
-	  hooking to avoid the need to hook syscalls as Filemon
-	  does.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-Integration-Services-(BIS)" href="#FreeBSD-Integration-Services-(BIS)" id="FreeBSD-Integration-Services-(BIS)">FreeBSD Integration Services (BIS)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/HyperV" title="https://wiki.FreeBSD.org/HyperV">FreeBSD Virtual Machines on Microsoft Hyper-V</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/HyperV" title="FreeBSD Virtual Machines on Microsoft Hyper-V">https://wiki.FreeBSD.org/HyperV</a></td></tr><tr><td><a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="https://technet.microsoft.com/en-us/library/dn531030.aspx">Supported Linux and FreeBSD Virtual Machines for Hyper-V on Windows</a></td><td>
-	    URL: <a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="Supported Linux and FreeBSD Virtual Machines for Hyper-V on Windows">https://technet.microsoft.com/en-us/library/dn531030.aspx</a></td></tr></table><p>
-	Contact:
-	  Sepherosa
-	  Ziehau
-	 &lt;<a href="mailto:sepherosa@gmail.com">sepherosa@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Howard
-	  Su
-	 &lt;<a href="mailto:howard0su@gmail.com">howard0su@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Hongjiang
-	  Zhang
-	 &lt;<a href="mailto:honzhan@microsoft.com">honzhan@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Dexuan
-	  Cui
-	 &lt;<a href="mailto:decui@microsoft.com">decui@microsoft.com</a>&gt;
-	</p>
-      <p>When FreeBSD virtual machines (VMs) run on Hyper-V, using
-	Hyper-V synthetic devices is recommended to get the best
-	network and storage performance and make full use of all the
-	benefits that Hyper-V provides.  The collection of drivers
-	that are required to use Hyper-V synthetic devices in FreeBSD
-	are known as FreeBSD Integration Services (BIS).  Some of the
-	BIS drivers (like network and storage drivers) have existed in
-	FreeBSD 9.x and 10.x for years, but there are still some
-	performance and stability issues and bugs.  Compared with
-	Windows and Linux VMs, the current BIS lacks some useful
-	features, e.g., live virtual machine backup, TRIM/Unmap, the
-	support for UEFI VMs (boot from UEFI), etc.</p>
-
-      <p>During the past quarter, we made a great progress on the
-	performance tuning for Hyper-V network driver.  We also
-	refactored and cleaned up the VMBus driver, and fixed some
-	important bugs.  All the work makes FreeBSD VMs run even
-	better on Hyper-V and the Hyper-V based cloud platform
-	Azure!</p>
-
-      <p>Our work during 2016Q1 is documented below:</p>
-
-      <p>Optimizing the performance of Hyper-V network driver:</p>
-
-      <ul>
-	<li>We added LRO (Large Receive Offloading) support to the
-	  driver and properly handle ACK packets.  This
-	  effectively reduces the CPU cycles used in the TCP/IP stack
-	  and dramatically boosts network performance!</li>
-
-	<li>We enabled vRSS (virtual Receive Side Scaling) support
-	  for the driver.  This greatly improved the network
-	  performance for SMP virtual machines.</li>
-
-	<li>We used a separate Tx kernel thread to relieve the Rx
-	  thread of transmitting packets (the Rx thread tried to
-	  transmit packets after receiving ACKs), so the Rx thread can
-	  receive packets and send ACKs faster.</li>
-
-	<li>Now we can reach a VM-to-VM throughput of 9.1Gbps on a
-	  host with a 10Gbps physical NIC, and over 20Gbps on a host
-	  with a 40Gbps NIC, all the while with plenty of CPU cycles
-	  left for applications.</li>
-
-	<li>We also enabled IP header checksum offloading, and Rx
-	  checksum offloading for UDP.</li>
-
-	<li>Further performance tuning is working in progress.</li>
-      </ul>
-
-      <p>Refactoring and cleaning up the VMBus driver code:</p>
-
-      <ul>
-	<li>Instead of using <tt>swi</tt> threads directly, we now use per-CPU
-	  <tt>taskqueue_create_fast()</tt> threads for event and message
-	  handling, making the code more conventional for FreeBSD.</li>
-
-	<li>We did a lot of cleanup to the <tt>hv_utils</tt> code (HeartBeat,
-	  TimeSync and Shutdown) and we are further cleaning up the
-	  KVP code.</li>
-
-	<li>We used a new message/interrupt slot for the Hyper-V timer, so
-	  the handling of timer and non-timer messages can be
-	  distinguished, fixing a potential issue.</li>
-
-	<li>Instead of finding an available IDT vector by hacking,
-	  we are changing to use the normal method,
-	  <tt>lapic_ipi_alloc()</tt>.</li>
-
-	<li>We are modularizing the Hyper-V modules:
-	  <ol>
-	    <li>they will be loaded in the loader;</li>
-	    <li>we are going to enhance <tt>devd(8)</tt> to improve
-	      the hot plug case.</li>
-	  </ol>
-	</li>
-      </ul>
-
-      <p>Bug Fixing:</p>
-
-      <ul>
-	<li>Fixed the "spurious multiple disks" issue (PR
-	  206630 &#8212; FreeBSD 10.2 on Windows 10 and 2016 server may not
-	  boot due to multiple invalid disks) in the Hyper-V storage
-	  driver and now FreeBSD VMs can reliably boot on Win10 and 2016
-	  hosts.</li>
-
-	<li>Fixed the OACTIVE issue (PR 207297 &#8212; [Hyper-V] FreeBSD
-	  10.2 on hyperv lost network under heavy load for
-	  OACTIVE).</li>
-
-	<li>Fixed a TSC calibration issue (PR 208238 &#8212; [Hyper-V] TSC
-	  frequency is not correctly detected: "calcru: runtime went
-	  backwards") and we will not see the "runtime went
-	  backwards" messages any more!</li>
-
-	<li>Fixed the "very slow terminal" issue of 11-CURRENT by
-	  enabling text mode when we are running on hypervisors.</li>
-
-	<li>Fixed the "unknown dhcp option value 0xf5" issue in
-	  <tt>dhclient(8)</tt> by asking <tt>dhclient(8)</tt> to
-	  ignore the option, and FreeBSD VMs on Azure can now reliably get
-	  IP addresses.</li>
-
-	<li>Found a workaround for PR 20824 ([Hyper-V] VM network may not
-	  work over virtual switch based on wireless NIC): add
-	  "net.link.ether.inet.max_age=60" in
-	  /etc/sysctl.conf.</li>
-      </ul>
-
-      <p>We plan to add support for live virtual machine backup,
-	TRIM/Unmap, and UEFI VMs (Hyper-V Generation-2 VMs).</p>
-
-      <p>We published errata (FreeBSD-EN-16:04.hyperv,
-	FreeBSD-EN-16:05.hv_netvsc) with the Release Engineering team,
-	so 10.1 and 10.2 users can easily get the fixes for KVP and TCP
-	checksums by upgrading the system.</p>
-
-      <p>We published BIS test cases for Hyper-V on github:
-	<a href="https://github.com/FreeBSDonHyper-V/Test-BIS" shape="rect">https://github.com/FreeBSDonHyper-V/Test-BIS</a>
-	and we are going to publish the test cases for Azure soon.</p>
-    <p>This project was sponsored by Microsoft.</p><hr /><h2><a name="Infiniband" href="#Infiniband" id="Infiniband">Infiniband</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-infiniband/2016-March/000190.html" title="https://lists.freebsd.org/pipermail/freebsd-infiniband/2016-March/000190.html">Call for Testing</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-infiniband/2016-March/000190.html" title="Call for Testing">https://lists.freebsd.org/pipermail/freebsd-infiniband/2016-March/000190.html</a></td></tr></table><p>
-	Contact:
-	  Hans Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
-	</p>
-      <p>Mellanox is working on a big infiniband update towards
-	Mellanox OFED v3.2 of the infiniband stack in FreeBSD.  The
-	updates include both userland and kernel components.
-	Infiniband patches for FreeBSD are available in the link above
-	which can be downloaded and applied to a recent FreeBSD-head
-	checkout.</p>
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="MMC-Stack-Under-CAM-Framework" href="#MMC-Stack-Under-CAM-Framework" id="MMC-Stack-Under-CAM-Framework">MMC Stack Under CAM Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bakulin.de/freebsd/mmccam.html" title="https://bakulin.de/freebsd/mmccam.html">Project Information</a></td><td>
-	    URL: <a href="https://bakulin.de/freebsd/mmccam.html" title="Project Information">https://bakulin.de/freebsd/mmccam.html</a></td></tr><tr><td><a href="https://github.com/kibab/FreeBSD/tree/mmccam" title="https://github.com/kibab/FreeBSD/tree/mmccam">Source Code</a></td><td>
-	    URL: <a href="https://github.com/kibab/FreeBSD/tree/mmccam" title="Source Code">https://github.com/kibab/FreeBSD/tree/mmccam</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D4761" title="https://reviews.FreeBSD.org/D4761">Patch for Review</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D4761" title="Patch for Review">https://reviews.FreeBSD.org/D4761</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:ilya@bakulin.de">ilya@bakulin.de</a>&gt;
-	</p>
-      <p>The goal of this project is to reimplement the existing
-	MMC/SD stack using the CAM framework.  This will permit
-	utilizing the well-tested CAM locking model and debugging
-	features.  It will also be possible to process interrupts
-	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 Wan 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 first version of the code was uploaded to Phabricator for
-	review.  The new stack is able to attach to the SD card and
-	bring it to an operational state so it is possible to read and
-	write to the card.</p>
-
-      <p>Support for the <tt>imx_sdhci</tt> SD Host Controller (used
-	on iMX-based boards, for example Wandboard) was added in
-	2016Q1, along with <tt>ti_sdhci</tt>, which is used on the
-	BeagleBone Black.  Modifying other SDHCI-compliant drivers
-	should not be difficult.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Modify the SDHCI driver on at least one x86 platform.  This
-	  will make development and collaboration easier.</p>
-      </li><li>
-	<p>Begin implementing SDIO-specific bits.</p>
-      </li></ol><hr /><h2><a name="NFS-Server" href="#NFS-Server" id="NFS-Server">NFS Server</a></h2><p>
-	Contact:
-	  Rick
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new <tt>-manage-gids</tt> option was added to the
-	<tt>nfsuserd</tt> daemon.  This option tells the NFS server to
-	use the list of groups for a uid on the server and not the
-	list of groups in the NFS RPC request.  Use of this option
-	avoids the 16 group limit for NFS RPCs using AUTH_SYS (the
-	default).</p>
-
-      <p>Work is ongoing with respect to development of pNFS support
-	for the NFS server using GlusterFS as a back end.  This will
-	be a long-term project with the eventual goal of allowing the
-	NFS server to scale beyond a single server system.  Hopefully
-	it will be available for testing in late Spring 2016.  pNFS
-	allows an NFSv4.1 client to do reads/writes directly to a data
-	server and not the NFS server.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>The pNFS server will be in need of testing during
-	  development or it will never progress to a near-production
-	  status.  I hope to have code available in FreeBSD's Subversion
-	  project branch for testing in late spring 2016.</p>
-      </li></ol><hr /><h2><img src="./images/32/kern.png" style="display: inline" /><a name="Static-Analysis-of-the-FreeBSD-Kernel-with-PVS-Studio" href="#Static-Analysis-of-the-FreeBSD-Kernel-with-PVS-Studio" id="Static-Analysis-of-the-FreeBSD-Kernel-with-PVS-Studio">Static Analysis of the FreeBSD Kernel with PVS Studio</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.viva64.com/en/b/0377/" title="http://www.viva64.com/en/b/0377/">PVS-Studio Delved into the FreeBSD Kernel</a></td><td>
-	    URL: <a href="http://www.viva64.com/en/b/0377/" title="PVS-Studio Delved into the FreeBSD Kernel">http://www.viva64.com/en/b/0377/</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D5245" title="https://reviews.freebsd.org/D5245">PVS Static Analysis Phabricator Review</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D5245" title="PVS Static Analysis Phabricator Review">https://reviews.freebsd.org/D5245</a></td></tr></table><p>
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>In February, Program Verification Systems used their
-	PVS-Studio tool to run a static analysis of the FreeBSD kernel.
-	A Phabricator review was created to allow developers to share
-	comments on the results.  A number of bugs ranging from
-	trivial typos to redundant code to important logic errors were
-	found and fixed.  Some results were false positives.  Several
-	of these were addressed by changing code that misled the
-	static analyzer and could also mislead a human reader.</p>
-
-      <p>The cooperation that Program Verification Systems offers to
-	open-source projects like FreeBSD benefits everyone.  We thank
-	them for sharing this analysis and their insights with us.</p>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="AmigaOne-X5000-Support" href="#AmigaOne-X5000-Support" id="AmigaOne-X5000-Support">AmigaOne X5000 Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.amigaos.net/hardware/133/amigaone-x5000" title="http://www.amigaos.net/hardware/133/amigaone-x5000"></a></td><td>
-	    URL: <a href="http://www.amigaos.net/hardware/133/amigaone-x5000" title="">http://www.amigaos.net/hardware/133/amigaone-x5000</a></td></tr></table><p>
-	Contact:
-	  Justin
-	  Hibbits
-	 &lt;<a href="mailto:jhibbits@FreeBSD.org">jhibbits@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project is a continuation of the Book-E QorIQ support
-	enhancements by Semihalf dating back to 2012.</p>
-
-      <p>The AmigaOne X5000 series of AmigaOS-compatible systems uses
-	the Freescale QorIQ series of SoCs for a desktop-class form
-	factor.  The work here entails adding support for the e5500
-	core itself, in addition to support for the SoC
-	peripherals.</p>
-
-      <p>Currently, most of the code to enable basic support is checked
-	in: dTSEC (ethernet), core support (e500mc, e5500).  As part of
-	this, <tt>rman</tt>, the kernel resource manager, was enhanced
-	to use <tt>uintmax_t</tt> for resources.  This allows devices to
-	be physically above the 4GB boundary on 32-bit systems.  With a
-	statically compiled device tree, it boots to multiuser mode with
-	nfsroot, and can be used as normal (serial and SSH logins once
-	configured).</p> <p>This project was sponsored by Alex Perez (Inertial Computing).</p><h3>Open tasks:</h3><ol><li>
-	<p>eSDHC driver: Work has been started on this, hijacking the
-	  <tt>imx_sdhc.c</tt> from Ian Lepore, but there are still
-	  bugs: missing DMA from the iMX driver, and odd timeouts
-	  after the system starts up.</p>
-      </li><li>
-	<p>SATA support: There is a WIP driver for the SATA
-	  controller, but it is currently very slow, about 11MB/s on a
-	  SATA 2 link.  It currently relies on a 10ms delay on every
-	  SATA transaction for it to be even somewhat
-	  stable.  Without this delay, the disk scan never works and I
-	  have not yet figured out why.</p>
-      </li><li>
-	<p>Local console (VGA) support: It currently boots with a
-	  serial console.  <tt>vgapci0</tt> is seen if there is a PCIe graphics
-	  card, but <tt>vt(4)</tt> does not attach to it yet.</p>
-      </li><li>
-	<p>64-bit support: The CPU on the board is a P5020, a 64-bit
-	  e5500 dual-core SoC.  Currently, booke support in FreeBSD is
-	  32-bit only.</p>
-      </li><li>
-	<p>SMP: SMP support on Book-E hardware is currently
-	  broken.</p>
-      </li><li>
-	<p>U-boot support: Currently this uses a compiled-in device
-	  tree, but it would be preferable to use the device
-	  tree provided by u-boot, or at least the Linux-compatible
-	  device tree.</p>
-      </li><li>
-	<p>More work is needed on the DPAA front (Datapath
-	  Acceleration Architecture) to improve the Ethernet driver
-	  and utilize the SEC engine for crypto, <tt>random(4)</tt>,
-	  and IPSec.</p>
-      </li></ol><hr /><h2><a name="FreeBSD-on-Cavium-ThunderX-(arm64)" href="#FreeBSD-on-Cavium-ThunderX-(arm64)" id="FreeBSD-on-Cavium-ThunderX-(arm64)">FreeBSD on Cavium ThunderX (arm64)</a></h2><p>
-	Contact:
-	  Dominik
-	  Ermel
-	 &lt;<a href="mailto:der@semihalf.com">der@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Macek
-	 &lt;<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	</p>
-      <p>Since the last report, FreeBSD support for ThunderX has been
-	significantly improved and stabilized.  Semihalf contributions
-	include the following items:</p>
-
-      <ul>
-	<li>Support for the newest ThunderX chip revisions (Pass 2.0)
-	  and current Cavium firmware.  Backward compatibility is
-	  maintained.</li>
-
-	<li>Moved to using <tt>pci_host_generic.c</tt> as a main
-	  driver for the internal PCIe bridge.  This involved a
-	  significant rework of PCIe code to support both generic and
-	  ThunderX based platforms.</li>
-
-	<li> Serious networking performance boost and bug fixes:</li>
-	  <ul>
-	    <li>Fixed race condition on Rx path causing a very rare
-	      "use after free" issue</li>
-
-	    <li>Hardware L3 and L4 checksums support</li>
-
-	    <li>Hardware assisted TCP Segmentation Offloading
-	      (TSO)</li>
-
-	    <li>Support for software Large Receive Offload (LRO)</li>
-
-	    <li>Various improvements to Tx and Rx paths and
-	      configuration</li>
-	  </ul>
-      </ul>
-
-      <p>The driver supports all available Ethernet connections (1,
-	10, 40 Gbps) and the system can saturate a 10 Gbps link (on
-	Tx) using 4 CPU cores.</p>
-
-      <ul>
-	<li>Significantly improved overall I/O performance:</li>
-	<ul>
-	  <li>Complete rework of <tt>copyin</tt>/<tt>copyout</tt> and
-	    <tt>bzero</tt> functionalities</li>
-	</ul>
-
-	<li>Other improvements:</li>
-	  <ul>
-	    <li>Support for interrupt to CPU binding (including
-	      GICv3/ITS backends)</li>
-	  </ul>
-      </ul>
-
-      <p>This work is integrated to FreeBSD HEAD on an on-going
-	basis.</p>
-    <p>This project was sponsored by Cavium, and Semihalf.</p><h3>Open tasks:</h3><ol><li>
-	<p>Add support for multi-Queue Set operation in VNIC.</p>
-      </li></ol><hr /><h2><a name="powerpcspe-Target" href="#powerpcspe-Target" id="powerpcspe-Target">powerpcspe Target</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base/projects/powerpcspe/" title="https://svnweb.freebsd.org/base/projects/powerpcspe/">Source Tree</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base/projects/powerpcspe/" title="Source Tree">https://svnweb.freebsd.org/base/projects/powerpcspe/</a></td></tr></table><p>
-	Contact:
-	  Justin
-	  Hibbits
-	 &lt;<a href="mailto:jhibbits@FreeBSD.org">jhibbits@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project aims to enable the use of the Signal Processing
-	Engine found in the NXP/Freescale e500v2 SoC.  The SPE uses
-	opcodes overlapping with those of Altivec, so they are
-	mutually exclusive.  Additionally, the e500v2 does not have a
-	traditional FPU, and instead uses the SPE for all floating
-	point operations (or emulation, as is currently done).
-	Combined with the fact that the SPE ABI is incompatible with
-	the traditional ABI, a new MACHINE_ARCH has been created to
-	address these incompatibilities.</p>
-
-      <p>A project branch has been created for the work.  A
-	powerpcspe kernel boots on the RouterBoard RB800, and the base
-	utilities run properly.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Potentially optimizing <tt>setjmp</tt>/<tt>longjmp</tt> to
-	  not use SPE unless it has already been enabled.  This would
-	  save the kernel switch for processes that do not otherwise
-	  use the SPE.  This is a low priority task which may not be
-	  completed.</p>
-      </li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="ELF-Tool-Chain-Tools" href="#ELF-Tool-Chain-Tools" id="ELF-Tool-Chain-Tools">ELF Tool Chain Tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://elftoolchain.sourceforge.net" title="http://elftoolchain.sourceforge.net">ELF Tool Chain Web Site</a></td><td>
-	    URL: <a href="http://elftoolchain.sourceforge.net" title="ELF Tool Chain Web Site">http://elftoolchain.sourceforge.net</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ELF Tool Chain project provides BSD-licensed
-	implementations of compilation tools and libraries for
-	building and analyzing ELF objects.  The project began as part
-	of FreeBSD but later became an independent project to encourage
-	wider participation from others in the open-source developer
-	community.</p>
-
-      <p>The ELF Tool Chain project released version 0.7.1 in
-	February.  We have been tracking snapshots of the upstream
-	repository in FreeBSD.
-	Having an official release brings the benefit of
-	broader testing and visibility within other open source
-	projects, even if we do not require it in order to
-	update FreeBSD.</p>
-
-      <p>In the first quarter of 2016, the ELF Tool Chain tools were
-	updated to a snapshot of upstream Subversion revision 3400, which
-	is close to the 0.7.1 release.  Additional bug fixes were
-	committed to FreeBSD and subsequently merged into the upstream
-	repository.</p>
-
-      <p>ELF Tool Chain's <tt>elfcopy(1)</tt> is now installed as
-	<tt>objcopy(1)</tt> by default, as it is a viable replacement
-	for the base system and ports tree.</p>
-
-      <p>Significant improvements were made to the
-	<tt>elfcopy(1)</tt>, <tt>readelf(1)</tt>, and
-	<tt>elfdump(1)</tt> tools, including better MIPS, RISC-V, and
-	AArch64 support.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Fix issues found by fuzzing inputs to the tools.</p>
-      </li><li>
-	<p>Add automatic support for separate debug files.</p>
-      </li><li>
-	<p>Investigate replacement <tt>objdump</tt>, <tt>ld</tt> and
-	  <tt>as</tt> implementations.</p>
-      </li></ol><hr /><h2><a name="Native-PCI-express-HotPlug" href="#Native-PCI-express-HotPlug" id="Native-PCI-express-HotPlug">Native PCI-express HotPlug</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/bsdjhb/freebsd/tree/pci_hp" title="https://github.com/bsdjhb/freebsd/tree/pci_hp">Native PCI-express HotPlug Support</a></td><td>
-	    URL: <a href="https://github.com/bsdjhb/freebsd/tree/pci_hp" title="Native PCI-express HotPlug Support">https://github.com/bsdjhb/freebsd/tree/pci_hp</a></td></tr></table><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new implementation of support for native PCI-express
-	hotplug is present at the URL above.  Much of the new code
-	lives in the PCI-PCI bridge driver to handle hotplug events
-	and manage the PCI-express slot registers.  Additional changes
-	in the branch include adding new <tt>rescan</tt> and
-	<tt>delete</tt> commands to <tt>devctl(8)</tt>, as well as
-	support for rescanning PCI busses.</p>
-
-      <p>The current implementation has been tested on systems with
-	ExpressCard slots but could use additional testing, especially on
-	systems with other PCI-express HotPlug features such as
-	mechanical latches, attention buttons, indicators, and so
-	on.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Split the branch into separate logical changes as commit
-	  candidates.</p>
-      </li><li>
-	<p>Additional testing.</p>
-      </li></ol><hr /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new thread target that directly uses <tt>ptrace(2)</tt>
-	was committed upstream and included in GDB 7.11.  The port was
-	also updated to GDB 7.11.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Figure out why the powerpc kgdb targets are not able to
-	  unwind the stack past the initial frame.</p>
-      </li><li>
-	<p>Add support for more platforms (arm, mips, aarch64) to
-	  upstream gdb for both userland and kgdb.</p>
-      </li><li>
-	<p>Add support for debugging powerpc vector registers.</p>
-      </li><li>
-	<p>Add support for catching system calls.</p>
-      </li><li>
-	<p>Add support for <tt>$_siginfo</tt>.</p>
-      </li><li>
-	<p>Add support for ELF auxv data via <tt>info auxv</tt>.</p>
-      </li><li>
-	<p>Implement <tt>info os</tt> commands.</p>
-      </li><li>
-	<p>Implement <tt>gdbserver</tt> for FreeBSD.</p>
-      </li></ol><hr /><h2><a name="Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD" href="#Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD" id="Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD">Using lld, the LLVM Linker, to Link
-      FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/LLD" title="https://wiki.freebsd.org/LLD">FreeBSD lld Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/LLD" title="FreeBSD lld Wiki Page">https://wiki.freebsd.org/LLD</a></td></tr><tr><td><a href="http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html" title="http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html">Status Report on Linking FreeBSD/amd64 with lld</a></td><td>
-	    URL: <a href="http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html" title="Status Report on Linking FreeBSD/amd64 with lld">http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html</a></td></tr></table><p>
-	Contact:
-	  Rafael
-	  Esp�ndola
-	 &lt;<a href="mailto:rafael.espindola@gmail.com">rafael.espindola@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Davide
-	  Italiano
-	 &lt;<a href="mailto:davide@FreeBSD.org">davide@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>lld</tt> is the linker in the LLVM family of projects.
-	It is intended to be a high-performance linker and supports
-	the ELF, COFF and Mach-O object formats.  Where possible,
-	<tt>lld</tt> maintains command-line and functional
-	compatibility with existing linkers (GNU BFD <tt>ld</tt> and
-	<tt>gold</tt>), but <tt>lld</tt>'s authors are not constrained
-	by strict compatibility where it would hamper performance or
-	desired functionality.</p>
-
-      <p>The upstream <tt>lld</tt> project made significant progress
-	in adding new functionality to <tt>lld</tt>'s ELF support over
-	the first quarter of 2016.  The <tt>lld</tt> ELF linker is
-	capable of self-hosting on FreeBSD/amd64 and is capable of
-	linking many test applications.</p>
-
-      <p>Highlights of upstream development over the quarter include:
-	<ul>
-	  <li><tt>lld</tt> gained Link Time Optimization (LTO) support
-	    and is able to link Clang with LTO</li>
-	  <li>The relocation code has been overhauled for better
-	    maintainability</li>
-	  <li>Improvements to linker script support, including better
-	    diagnostics</li>
-	  <li>Many bug fixes in x86_64, AArch64, and MIPS support</li>
-	</ul></p>
-
-      <p><tt>lld</tt> currently lacks comprehensive linker script
-	expression evaluation support, and therefore cannot yet be
-	used to link the FreeBSD kernel.  It also lacks versioned
-	symbol support, and does not implement some options used in
-	the FreeBSD boot loader components.</p>
-
-      <p>Ed has been running experimental world builds of
-	FreeBSD/amd64 with <tt>lld</tt> installed in place of
-	<tt>ld.bfd</tt> as the linker.  With workarounds for the
-	current gaps in functionality (using the
-	<tt>WITHOUT_SYMVER</tt> option to disable symbol versioning
-	use, and linking the loader components with GNU <tt>ld</tt>),
-	<tt>lld</tt> is now able to link a working FreeBSD
-	userland.</p>
-    <p>This project was sponsored in part by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>
-	<p>Enable the <tt>lld</tt> option by default in the llvm-devel
-	  (and later llvm) ports for testing.</p>
-      </li><li>
-	<p>Develop symbol version support and linker script expression
-	  improvements in the upstream lld project.</p>
-      </li><li>
-	<p>Add or improve support for the remaining FreeBSD
-	  architectures.</p>
-      </li><li>
-	<p>Import a newer lld snapshot into the vendor area, add build
-	  infrastructure and connect it to the world build, installed
-	  as <tt>ld.lld</tt>.</p>
-      </li><li>
-	<p>Request a ports exp-run with <tt>/usr/bin/ld</tt> a symlink
-	  to <tt>ld.lld</tt>.</p>
-      </li><li>
-	<p>Extensive testing.</p>
-      </li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="GitLab-Port" href="#GitLab-Port" id="GitLab-Port">GitLab Port</a></h2><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:ports@toco-domains.de">ports@toco-domains.de</a>&gt;
-	</p>
-      <p>After nearly a year of work on this project, GitLab 8.5.5 was
-	committed into the ports tree.  A big thanks to the enormous
-	number of people involved! Since GitLab is a fast-moving
-	project, there is also ongoing work to stay in sync with
-	upstream.  Have fun!</p>
-    <hr /><h2><a name="GNOME-on-FreeBSD" href="#GNOME-on-FreeBSD" id="GNOME-on-FreeBSD">GNOME on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome" title="http://www.FreeBSD.org/gnome">FreeBSD GNOME Website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome" title="FreeBSD GNOME Website">http://www.FreeBSD.org/gnome</a></td></tr><tr><td><a href="https://github.com/FreeBSD/freebsd-ports-gnome" title="https://github.com/FreeBSD/freebsd-ports-gnome">Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/freebsd-ports-gnome" title="Development Repository">https://github.com/FreeBSD/freebsd-ports-gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD">Upstream Build Bot</a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="Upstream Build Bot">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html">USE_GNOME Porter's Handbook Chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="USE_GNOME Porter's Handbook Chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD GNOME Team maintains the GNOME, MATE, and
-      CINNAMON desktop environments and graphical user interfaces for
-      FreeBSD.  GNOME 3 is part of the GNU Project.  MATE is a fork of
-      the GNOME 2 desktop.  CINNAMON is a desktop environment using
-      GNOME 3 technologies but with a GNOME 2 look and feel.</p>
-
-      <p>This quarter, GNOME 3.18 and MATE 1.12 were committed to the
-	ports tree.</p>
-
-      <p>The <tt>bsd.gnome.mk</tt> and <tt>bsd.mate.mk</tt> frameworks
-	were replaced by the simpler <tt>Uses/gnome.mk</tt> and
-	<tt>Uses/mate.mk</tt> style.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Tracking MATE 1.13, the development version that will
-	  become MATE 1.14.</p>
-      </li><li>
-	<p>Work started on porting GNOME 3.20.</p>
-      </li><li>
-	<p>We have Cinnamon 2.8 in our development tree, but we do not
-	  have the time to properly test and fix the issues before
-	  this Cinnamon can be committed to ports.  Interested in
-	  helping or taking maintainership of Cinnamon?  Please let us
-	  know.</p>
-      </li></ol><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE on FreeBSD Website</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE on FreeBSD Website">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://freebsd.kde.org/area51.php" title="https://freebsd.kde.org/area51.php">Experimental KDE Ports Staging Area</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/area51.php" title="Experimental KDE Ports Staging Area">https://freebsd.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/KDE" title="https://wiki.FreeBSD.org/KDE">KDE on FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/KDE" title="KDE on FreeBSD Wiki">https://wiki.FreeBSD.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="https://mail.kde.org/mailman/listinfo/kde-freebsd">KDE/FreeBSD Mailing List</a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="KDE/FreeBSD Mailing List">https://mail.kde.org/mailman/listinfo/kde-freebsd</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/plasma5" title="http://src.mouf.net/area51/log/branches/plasma5">Development Repository for Integrating KDE Frameworks 5 and Plasma 5</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/plasma5" title="Development Repository for Integrating KDE Frameworks 5 and Plasma 5">http://src.mouf.net/area51/log/branches/plasma5</a></td></tr></table><p>
-	Contact: KDE on FreeBSD team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging and making sure
-	that the experience of KDE and Qt on FreeBSD is as good as
-	possible.</p>
-
-      <p>While the list of updates is shorter than that for the
-	previous quarter, the team remained busy and work on KDE
-	Frameworks 5 and Plasma 5 continues.</p>
-
-      <p>Tobias Berner, who has been driving our KDE Frameworks 5 and
-	Plasma 5 efforts from the beginning, received a KDE commit
-	bit, and has been putting it to good use by upstreaming
-	FreeBSD across several KDE repositories.  Another team
-	highlight in the beginning of this year is the (re)addition of
-	another committer to our experimental repository: Adriaan de
-	Groot, a longtime KDE contributor who also used to work on KDE
-	and FreeBSD almost a decade ago when our team was first
-	formed.  Welcome back, Ade!</p>
-
-      <p>The following big updates were landed in the ports tree this
-	quarter.  In many cases, we have also contributed patches to
-	the upstream projects.</p>
-
-      <ul>
-	<li>CMake 3.4.2 and 3.5.0</li>
-
-	<li>Calligra 2.9.11, the latest release of the integrated work
-	  applications suite.  We have managed to keep in sync with
-	  the upstream releases since 2.9.10.</li>
-
-	<li>KDE Telepathy was updated to 0.9.0 and Telepathy-Qt4 was
-	  updated to 0.9.6.1, the latest upstream releases.</li>
-
-	<li>The Qt 5 ports were finally updated to 5.5.1, which were
-	  the latest stable version at the time.</li>
-
-	<li>The first commit preparing the groundwork for KDE
-	  Frameworks 5 and Plasma 5
-	  <a href="https://svnweb.freebsd.org/changeset/ports/411156" shape="rect">was
-	    landed to the ports tree</a>.</li>
-      </ul>
-
-      <p>Work on Qt 5.6.0 is
-	under way in our experimental repositories.  At
-	the time of this writing, it also contains KDE Frameworks 5.20.0,
-	Plasma 5.6.1, and KDE Applications 16.03.80.</p>
-
-      <p>Users interested in testing those ports are encouraged to
-	follow the instructions in
-	<a href="https://freebsd.kde.org/area51.php" shape="rect">our website</a>
-	and report their results to our mailing list.  Qt5 5.6.0 is in
-	our <tt>qt-5.6</tt> branch, and Plasma 5 and the rest is in
-	the <tt>plasma5</tt> branch.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Land the KDE Frameworks 5 and Plasma 5 ports to the
-	  tree.</p>
-      </li><li>
-	<p>Commit the DigiKam 4.14.0 update currently being worked on
-	  in our experimental repository.</p>
-      </li></ol><hr /><h2><a name="Obsoleting-Rails-3" href="#Obsoleting-Rails-3" id="Obsoleting-Rails-3">Obsoleting Rails 3</a></h2><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:ports@toco-domains.de">ports@toco-domains.de</a>&gt;
-	</p>
-      <p>Ruby on Rails is the base for most of the rubygems in the
-	Ports Collection.  Currently, versions 3.2 and 4.2 coexist, but since
-	Rails 3.2 is running out of support, the time has come to
-	switch.</p>
-
-      <p>There is an ongoing progress to remove Rails 3.2 from the
-	ports tree.  While many gems already work with the new
-	version, there are some exceptions.  For example, www/redmine
-	needs a big update (which is currently being tested) because it
-	depends on gems that depends on Rails 3.2.</p>
-
-      <p>If you want to help with porting or testing, feel free to contact
-	me or the mailinglist <tt>ruby@FreeBSD.org</tt>.</p>
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
-	    URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
-	    URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr></table><p>
-	Contact:
-	  Frederic
-	  Culot
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As of the end of Q1, the ports tree holds a bit more
-	than 25,000 ports, and the PR count is below 1,900.  The
-	activity on the ports tree remains steady, with almost 7,000
-	commits performed by around 120 active committers.</p>
-
-      <p>On the problem reports front, the encouraging trend
-	observed during the previous quarter is confirmed, with again
-	a significant increase in the number of PRs fixed during Q1.
-	Indeed, almost 2,400 reports were fixed, which allows us to go
-	below the threshold value of 2,000 open PRs.</p>
-
-      <p>In Q1, three commit bits were taken in for safekeeping,
-	following an inactivity period of more than 18 months (milki,
-	brian), or on committer's request (mmoll).  We had one
-	returning committer (fluffy) who had his commit bit
-	reinstated.  Two new developers were granted a ports commit
-	bit (Olivier Cochard-Labbe and Christoph Moench-Tegeder).</p>
-
-      <p>On the management side, we had the pleasure to welcome miwi
-	back to the portmgr team.</p>
-
-      <p>On the QA side, 39 exp-runs were performed to validate
-	sensitive updates or cleanups.  The most noticeable change
-	might be the removal of the now unneeded
-	<tt>${PORTSDIR}</tt> when specifying dependencies in
-	Makefiles (see the <tt>/usr/ports/CHANGES</tt> entry dated
-	20160402).  Amongst other noticeable changes are the update to
-	ruby 2.3, ruby-gems to 2.5.1, CMake to 3.5.0, clang to
-	3.8.0-r258968, Qt5 to 5.5.1, Gnome to 3.18, boost to 1.60.0,
-	the update of libc++ in base to 3.8.0 release, and the
-	enabling of LLVM libunwind by default on x86.  The CentOS
-	ports were also updated.  Some infrastructure changes included
-	the switch from <tt>bsd.gnome.mk</tt> and <tt>bsd.mate.mk</tt>
-	to the simpler <tt>Uses/gnome.mk</tt> and
-	<tt>Uses/mate.mk</tt>.  Some work was also done to improve
-	poudriere builds by reducing dependency calculation and
-	general overheads.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>We would like to remind everyone that the ports tree is
-	  built and run by volunteers, and any help is greatly
-	  appreciated.  A great amount of effort was spent on the
-	  ports front in Q1, which allowed us to decrease the number
-	  of pending problem reports significantly, as well as on the
-	  ports infrastructure.  Many thanks to all who
-	  contributed!</p>
-      </li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="New-FreeBSD-Mastery-Books" href="#New-FreeBSD-Mastery-Books" id="New-FreeBSD-Mastery-Books">New FreeBSD Mastery Books</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.michaelwlucas.com/nonfiction/fmsf" title="https://www.michaelwlucas.com/nonfiction/fmsf">FreeBSD Mastery: Specialty Filesystems</a></td><td>
-	    URL: <a href="https://www.michaelwlucas.com/nonfiction/fmsf" title="FreeBSD Mastery: Specialty Filesystems">https://www.michaelwlucas.com/nonfiction/fmsf</a></td></tr><tr><td><a href="https://www.michaelwlucas.com/nonfiction/fmaz" title="https://www.michaelwlucas.com/nonfiction/fmaz">FreeBSD Mastery: Advanced ZFS</a></td><td>
-	    URL: <a href="https://www.michaelwlucas.com/nonfiction/fmaz" title="FreeBSD Mastery: Advanced ZFS">https://www.michaelwlucas.com/nonfiction/fmaz</a></td></tr><tr><td><a href="https://www.tiltedwindmillpress.com/" title="https://www.tiltedwindmillpress.com/">Tilted Windmill Press</a></td><td>
-	    URL: <a href="https://www.tiltedwindmillpress.com/" title="Tilted Windmill Press">https://www.tiltedwindmillpress.com/</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	<br />
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:allanjude@FreeBSD.org">allanjude@FreeBSD.org</a>&gt;
-	</p>
-      <p>Two new <em>FreeBSD Mastery</em> books are out:</p>
-
-      <p><em>FreeBSD Mastery: Specialty Filesystems</em> by Michael
-	W. Lucas, and the long-awaited
-	<em>FreeBSD Mastery: Advanced ZFS</em> by Lucas
-	and Allan Jude.</p>
-
-      <p>Both books are available in print and ebook formats now.</p>
-
-      <p>A bundle containing all the FreeBSD Mastery books is
-	available at a discount from
-	<a href="https://www.tiltedwindmillpress.com/" shape="rect">tiltedwindmillpress.com</a>.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Write more books!</p>
-      </li></ol><hr /><h2><img src="./images/32/doc.jpg" style="display: inline" /><a name="Spanish-FAQ-and-Chinese-Porter's-Handbook-Translations" href="#Spanish-FAQ-and-Chinese-Porter's-Handbook-Translations" id="Spanish-FAQ-and-Chinese-Porter's-Handbook-Translations">Spanish FAQ and Chinese Porter's Handbook
-      Translations</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/es_ES.ISO8859-1/books/faq/" title="https://www.freebsd.org/doc/es_ES.ISO8859-1/books/faq/">Preguntas Frecuentes para FreeBSD 9.X y 10.X</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/es_ES.ISO8859-1/books/faq/" title="Preguntas Frecuentes para FreeBSD 9.X y 10.X">https://www.freebsd.org/doc/es_ES.ISO8859-1/books/faq/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/zh_TW.UTF-8/books/porters-handbook/" title="https://www.freebsd.org/doc/zh_TW.UTF-8/books/porters-handbook/">FreeBSD Porter &#25163;&#20874;</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/zh_TW.UTF-8/books/porters-handbook/" title="FreeBSD Porter &#25163;&#20874;">https://www.freebsd.org/doc/zh_TW.UTF-8/books/porters-handbook/</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-translators/" title="https://lists.freebsd.org/pipermail/freebsd-translators/">FreeBSD Translators Mailing List</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-translators/" title="FreeBSD Translators Mailing List">https://lists.freebsd.org/pipermail/freebsd-translators/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html">PO Translations</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html" title="PO Translations">https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/">FreeBSD Documentation Project Primer for New Contributors</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="FreeBSD Documentation Project Primer for New Contributors">https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/</a></td></tr></table><p>
-	Contact:
-	  Federico
-	  Caminiti
-	 &lt;<a href="mailto:demian.fc@gmail.com">demian.fc@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Carlos
-	  J Puga Medina
-	 &lt;<a href="mailto:cpm@fbsd.es">cpm@fbsd.es</a>&gt;
-	<br />
-	Contact:
-	  Ruey-Cherng
-	  Yu
-	 &lt;<a href="mailto:raycherng@gmail.com">raycherng@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>Federico Caminiti created an entirely new Spanish translation
-	of the 31,000-word
-	<a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/" shape="rect">FAQ</a>
-	with editorial help from Carlos J Puga Medina.</p>
-
-      <p>This landmark accomplishment marks the first use of the new
-	PO translation system to translate an entire book!</p>
-
-      <p>Ruey-Cherng Yu has begun an ambitious Traditional Chinese
-	(zh_TW) translation of the 64,000-word
-	<a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/" shape="rect">Porter's Handbook</a>.
-	About half of the strings in the book have been translated so
-	far.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Help add and improve translations of FreeBSD documents into
-	  Spanish:
-	  <a href="https://lists.freebsd.org/pipermail/freebsd-translators/2016-March/000113.html" shape="rect">start of <tt>freebsd-translators</tt> thread</a>.</p>
-      </li><li>
-	<p>Help add and improve translations of FreeBSD documents into
-	  Chinese or other languages.</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://people.freebsd.org/~jkois/FreeBSDde/de/" title="https://people.freebsd.org/~jkois/FreeBSDde/de/">Homepage of the FreeBSD German Documentation Project</a></td><td>
-	    URL: <a href="https://people.freebsd.org/~jkois/FreeBSDde/de/" title="Homepage of the FreeBSD German Documentation Project">https://people.freebsd.org/~jkois/FreeBSDde/de/</a></td></tr></table><p>
-	Contact:
-	  Bj�rn
-	  Heidotting
-	 &lt;<a href="mailto:bhd@FreeBSD.org">bhd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Johann
-	  Kois
-	 &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD German Documentation Project translates FreeBSD's
-	documentation (handbook, articles, website, etc.) into the
-	German language.</p>
-
-      <p>Due to the tireless effort of Bj�rn Heidotting, we made huge
-	improvements in catching up with the translation of the German
-	handbook.  Benedict helped with reviewing the changes using
-	FreeBSD's review system Phabricator, which helped a lot.  We
-	now have the following handbook chapters in sync with the
-	latest version in the English tree:</p>
-
-      <ul>
-	<li>filesystems</li>
-
-	<li>kernelconfig</li>
-
-	<li>ports</li>
-
-	<li>x11</li>
-      </ul>
-
-      <p>We try to keep up the good work, while also looking at new
-	ways to translate like the PO/gettext-based system.  We are
-	always looking for volunteers who are interested in
-	translating small sections or even entire documents.  The
-	process is relatively easy and contributors do not have to
-	know much to get started.  The members of the FreeBSD German
-	Documentation Team are also willing to mentor people who are
-	interested in helping out.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Translate more documents.</p>
-      </li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="FreeBSD-Build" href="#FreeBSD-Build" id="FreeBSD-Build">FreeBSD Build</a></h2><p>
-	Contact:
-	  Bryan
-	  Drewery
-	 &lt;<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>&gt;
-	</p>
-      <p>Build improvements for buildworld on FreeBSD head continue.
-	Some highlights include:</p>
-
-      <ul>
-	<li><tt>WITH_FAST_DEPEND</tt> was made the default in r296668, and
-	  later made the only option in r297434.  The new depend code
-	  avoids a <tt>make depend</tt> tree walk and generates
-	  <tt>.depend</tt> files during the build as a side-effect of
-	  compilation.  This is done by using the <tt>-MF</tt> flags of the
-	  compiler.  This speeds up the build by 15-35%.</li>
-
-	<li><a href="http://bugs.freebsd.org/196193" shape="rect">PR 196193</a>:
-	  <tt>WITHOUT_CROSS_COMPILER</tt> was fixed to properly use
-	  <tt>--sysroot</tt> which allows the option to work in more
-	  cases.  It is still unsafe when major compiler upgrades
-	  occur.  Further work is planned to improve that still.</li>
-
-	<li><tt>WITHOUT_TOOLCHAIN</tt> now properly builds.</li>
-      </ul>
-    <p>This project was sponsored by EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li>
-	<p>Opportunistically skipping the bootstrap compiler phase of
-	  buildworld.</p>
-      </li><li>
-	<p>Skipping the <tt>make obj</tt> tree walk.</p>
-      </li><li>
-	<p>Enabling <tt>WITH_META_MODE</tt> in buildworld to provide a
-	  reliable incremental build using <tt>filemon(4)</tt> and
-	  <tt>bmake</tt>'s <tt>.MAKE.MODE=meta</tt>.  This should not
-	  be confused with <tt>WITH_DIRDEPS_BUILD</tt> which
-	  previously was named <tt>WITH_META_MODE</tt> and is a
-	  drastically different build system presented at BSDCan 2014
-	  by Simon Gerraty.</p>
-      </li></ol><hr /><h2><a name="Qt-5.6-on-Raspberry-Pi" href="#Qt-5.6-on-Raspberry-Pi" id="Qt-5.6-on-Raspberry-Pi">Qt 5.6 on Raspberry Pi</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://kernelnomicon.org/?p=598" title="http://kernelnomicon.org/?p=598">Qt 5.6 on FreeBSD/Pi</a></td><td>
-	    URL: <a href="http://kernelnomicon.org/?p=598" title="Qt 5.6 on FreeBSD/Pi">http://kernelnomicon.org/?p=598</a></td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Qt 5.6 is a great framework for building embedded GUI
-	applications, so when Qt 5.6 was released it was natural to
-	bring it up on the Raspberry Pi.  The current Qt support in ports is
-	very Xorg-centric, so as a proof of concept I created an
-	experimental <tt>qt56-base</tt> and <tt>qt56-multimedia</tt>.</p>
-
-      <p><tt>qt56-base</tt> can be configured for a generic ARM device with the
-	<tt>scfb</tt> video driver, and specifically for Raspberry Pi in which
-	case it supports EGLFS mode with hardware OpenGL
-	acceleration.</p>
-    <h3>Open tasks:</h3><ol><li>
-	<p>Check how embedded use cases can be fit into the current
-	  <tt>bsd.qt.mk</tt> or whether a new port should be
-	  introduced.</p>
-      </li></ol><hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsdfoundation.org/" title="https://www.freebsdfoundation.org/">FreeBSD Foundation Site</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/" title="FreeBSD Foundation Site">https://www.freebsdfoundation.org/</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/donors/" title="https://www.freebsdfoundation.org/donors/">Donors</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/donors/" title="Donors">https://www.freebsdfoundation.org/donors/</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/what-we-do/education-advocacy/" title="https://www.freebsdfoundation.org/what-we-do/education-advocacy/">Education and Advocacy Materials</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/what-we-do/education-advocacy/" title="Education and Advocacy Materials">https://www.freebsdfoundation.org/what-we-do/education-advocacy/</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-scott-long/" title="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-scott-long/">Faces of FreeBSD: Scott Long</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-scott-long/" title="Faces of FreeBSD: Scott Long">https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-scott-long/</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-sean-bruno/" title="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-sean-bruno/">Faces of FreeBSD: Sean Bruno</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-sean-bruno/" title="Faces of FreeBSD: Sean Bruno">https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-sean-bruno/</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/blog/freebsd-and-zfs/" title="https://www.freebsdfoundation.org/blog/freebsd-and-zfs/">The Longstanding Relationship Between FreeBSD and ZFS</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/blog/freebsd-and-zfs/" title="The Longstanding Relationship Between FreeBSD and ZFS">https://www.freebsdfoundation.org/blog/freebsd-and-zfs/</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/blog/initial-freebsd-risc-v-architecture-port-committed/" title="https://www.freebsdfoundation.org/blog/initial-freebsd-risc-v-architecture-port-committed/">FreeBSD RISC-V Work</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/blog/initial-freebsd-risc-v-architecture-port-committed/" title="FreeBSD RISC-V Work">https://www.freebsdfoundation.org/blog/initial-freebsd-risc-v-architecture-port-committed/</a></td></tr><tr><td><a href="http://www.mellanox.com/page/press_release_item?id=1688" title="http://www.mellanox.com/page/press_release_item?id=1688">Mellanox's Work with NetFlix</a></td><td>
-	    URL: <a href="http://www.mellanox.com/page/press_release_item?id=1688" title="Mellanox's Work with NetFlix">http://www.mellanox.com/page/press_release_item?id=1688</a></td></tr><tr><td><a href="https://chemnitzer.linux-tage.de/2016/de/programm/beitrag/194" title="https://chemnitzer.linux-tage.de/2016/de/programm/beitrag/194">FreeBSD &#8211; The Power to Serve a Community</a></td><td>
-	    URL: <a href="https://chemnitzer.linux-tage.de/2016/de/programm/beitrag/194" title="FreeBSD &#8211; The Power to Serve a Community">https://chemnitzer.linux-tage.de/2016/de/programm/beitrag/194</a></td></tr><tr><td><a href="https://www.freebsdfoundation.org/blog/introducing-a-new-look-for-the-foundation/" title="https://www.freebsdfoundation.org/blog/introducing-a-new-look-for-the-foundation/">The FreeBSD Foundation's New Look</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/blog/introducing-a-new-look-for-the-foundation/" title="The FreeBSD Foundation's New Look">https://www.freebsdfoundation.org/blog/introducing-a-new-look-for-the-foundation/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Funding comes from individual and
-	corporate donations and is used to fund and manage development
-	projects, conferences and developer summits, and provide
-	travel grants to FreeBSD developers.  The Foundation purchases
-	hardware to improve and maintain FreeBSD infrastructure and
-	publishes FreeBSD white papers and marketing material to
-	promote, educate, and advocate for the FreeBSD Project.  The
-	Foundation also represents the FreeBSD Project in executing
-	contracts, license agreements, and other legal arrangements
-	that require a recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD last
-	quarter:</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>We raised $204,000 last quarter from individual and corporate
-	donors.  Thank you to everyone who made a donation this year!
-	The
-	<a href="https://www.freebsdfoundation.org/donors/" shape="rect">list of donors</a>
-	is available.</p>
-
-      <p>OS Improvements</p>
-
-      <p>The Foundation improves FreeBSD by funding software
-	development projects approved through our proposal submission
-	process, and our three software developer staff members.  Two
-	Foundation-funded projects were started last quarter, the
-	first to improve the stability of the vnet network stack
-	virtualization infrastructure, and the second for phase two of
-	the FreeBSD/arm64 port project.</p>
-
-      <p>Foundation staff members were responsible for many changes
-	over the quarter.  Some notable items include process-shared
-	pthread locks, address mapping randomization, disk I/O
-	bandwidth limits, porting <tt>libunwind</tt> to FreeBSD/arm,
-	bug fixes in the <tt>autofs</tt> automount daemon, an updated
-	version of the ELF Tool Chain, investigation of the
-	<tt>lld</tt> linker, improved x86 hardware support, and VM
-	subsystem stability improvements.  Several of these projects
-	are described elsewhere in this quarterly report.</p>
-
-      <p>Release Engineering</p>
-
-      <p>Foundation employee and release engineer Glen Barber worked
-	on packaging the base system with <tt>pkg(8)</tt>, separating
-	debug files from the default base system so they can be
-	selected or deselected during an install, supporting
-	preparations, testing for the on-time release of FreeBSD
-	10.3, and producing 11-CURRENT and 10-STABLE snapshot
-	builds.</p>
-
-      <p>FreeBSD Advocacy</p>
-
-      <p>Anne Dickison, our Marketing Director, focused on creating
-	and updating marketing material to promote and teach people
-	about FreeBSD.
-	<a href="https://www.freebsdfoundation.org/what-we-do/education-advocacy/" shape="rect">This material is available</a>
-	for FreeBSD advocates to hand out at conferences and events to
-	promote FreeBSD.  She also worked on promoting FreeBSD work
-	being done over social media, blog posts, and articles.</p>
-
-      <p>Last quarter, we continued our Faces of FreeBSD series by
-	publishing stories about
-	<a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-scott-long/" shape="rect">Scott Long</a>
-	and
-	<a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-sean-bruno/" shape="rect">Sean Bruno</a>.
-	This is an opportunity to put a face to a name in the FreeBSD
-	community and get to know more about the people who
-	contribute to FreeBSD.</p>
-
-      <p>Work began on updating the FreeBSD 10.X brochure to
-	include the new 10.3 features.</p>
-
-      <p>We love getting stories from companies who are successfully
-	using FreeBSD.  Testimonials were received last quarter from
-	Chelsio and Acceleration Systems.</p>
-
-      <p>ZFS was making some headlines, so we wrote a blog entry on
-	<a href="https://www.freebsdfoundation.org/blog/freebsd-and-zfs/" shape="rect">the
-	  longstanding relationship between FreeBSD and ZFS</a>.</p>
-
-      <p>We helped promote
-	<a href="https://www.freebsdfoundation.org/blog/initial-freebsd-risc-v-architecture-port-committed/" shape="rect">the
-	  FreeBSD RISC-V</a> work being done.</p>
-
-      <p>Assistance was provided to Mellanox for their press release
-	highlighting
-	<a href="http://www.mellanox.com/page/press_release_item?id=1688" shape="rect">their work with NetFlix</a>.</p>
-
-      <p>Conferences and Events</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events, and
-	summits around the globe.  These events can be BSD-related,
-	open source, or technology events geared towards
-	underrepresented groups.  We provide financial support to the
-	major BSD conferences like BSDCan, AsiaBSDCon, and EuroBSDCon,
-	and give financial and/or other support for smaller events
-	like BSDDays, FreeBSD Summits, and FreeBSD workshops, camps,
-	and hackathons.  For open source conferences, we will attend
-	when we can get a free non-profit booth.</p>
-
-      <p>The year kicked off with sending Ed Maste, Benedict
-	Reuschling, and George Neville-Neil to promote and give talks
-	on FreeBSD at FOSDEM, the largest open source conference in
-	Europe.  Ed, our Project Development Director, had a chance to
-	talk to developers from other projects based on FreeBSD, and
-	various people about reproducible builds in FreeBSD.</p>
-
-      <p>Dru Lavigne and Deb Goodkin promoted FreeBSD at SCALE in
-	Pasadena, California.  Dru gave a presentation called "Doc
-	Like an Egyptian."  We were a Gold Sponsor for AsiaBSDCon in
-	Tokyo, and five Foundation members attended.  Kirk McKusick
-	taught a two-day FreeBSD Kernel tutorial and gave a talk on
-	the history of the BSD filesystem.  Dru Lavigne and Benedict
-	Reuschling gave a documentation tutorial.  Board members
-	Hiroki Sato and George Neville-Neil helped organize the
-	conference.  BSDnow.tv interviewed Benedict at AsiaBSDCon
-	about his role as a new Foundation board member and the
-	Foundation's work.</p>
-
-      <p>We planned and organized our first-ever FreeBSD Storage
-	Summit in association with the USENIX FAST Conference.  Led by
-	our President and Founder, Justin Gibbs, we had over 50
-	attendees participating and working together on technically
-	focused topics.  Benedict was busy promoting FreeBSD in
-	Europe, where he also attended Linuxtage in Chemnitz, Germany
-	to give a talk on FreeBSD (in German):
-	<a href="https://chemnitzer.linux-tage.de/2016/de/programm/beitrag/194" shape="rect">FreeBSD &#8212; The Power to Serve a Community</a>.</p>
-
-      <p>The Foundation committed to being a Gold Sponsor for BSDCan
-	and the upcoming Hackathon/DevSummit in Essen, Germany in
-	April.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them.  We continued to review
-	requests for permission to use the trademarks.</p>
-
-      <p>FreeBSD Community Engagement</p>
-
-      <p>Code of Conduct &#8212; 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>
-
-      <p>We have been reaching out to other open source communities to
-	get help with our efforts in making this a diverse community
-	and help us achieve our goals mentioned above of making the
-	FreeBSD community safe, inclusive, and welcoming.</p>
-
-      <p>Continuing with our diversity efforts, we have been
-	connecting with women in technology groups to work on how we
-	can recruit more women to FreeBSD and offer Intro to FreeBSD
-	workshops.</p>
-
-      <p>Meetings were held with a number of commercial vendors to
-	help facilitate collaboration with the Project.  This included
-	presenting how the Project is organized, and how companies can
-	get help, contribute back to the Project, promote their use of
-	FreeBSD, and for us to get their feedback on the work we are
-	doing to help with our fundraising efforts.</p>
-
-      <p>The new Foundation website and logo was launched, signaling
-	the ongoing evolution of the Foundation identity and ability
-	to better serve the FreeBSD Project and community.  Find our
-	more about our
-	<a href="https://www.freebsdfoundation.org/blog/introducing-a-new-look-for-the-foundation/" shape="rect">new look</a>.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2016-04-2016-06.html b/website/content/en/status/report-2016-04-2016-06.html
deleted file mode 100644
index 4d5a4b77f3..0000000000
--- a/website/content/en/status/report-2016-04-2016-06.html
+++ /dev/null
@@ -1,2011 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Now available: the 2016Q2 model of the FreeBSD Project Status
-      Report!</p><p>This quarter brings several exciting improvements over previous
-      models.  We have enhancements from different teams, new features
-      like robust mutexes and support for full disk encryption with
-      GELI.  You'll find expanded graphics support, both at the chipset
-      and window manager levels, and ongoing development in many pending
-      features.</p><p>Perhaps most exciting, under the hood you'll find a brand-new
-      Core Team.</p><p>Don't wait.  Take FreeBSD for a spin today.</p><p>&#8212;Michael W. Lucas</p><p><hr /></p><p>Please submit status reports for the third quarter of 2016 by
-      October 7.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-IRC-Admin-Team">FreeBSD IRC Admin Team</a></li><li><a href="#FreeBSD-Issue-Triage-Team">FreeBSD Issue Triage Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#ASLR-Interim-State">ASLR Interim State</a></li><li><a href="#Ceph-on-FreeBSD">Ceph on FreeBSD</a></li><li><a href="#EFI-Refactoring-and-GELI-Support">EFI Refactoring and GELI Support</a></li><li><a href="#Robust-Mutexes">Robust Mutexes</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ARM-Allwinner-SoC-Support">ARM Allwinner SoC Support</a></li><li><a href="#FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></li><li><a href="#VIMAGE-Virtualized-Network-Stack-Update">VIMAGE Virtualized Network Stack Update</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Reproducible-Builds-in-FreeBSD">Reproducible Builds in FreeBSD</a></li><li><a href="#Updates-to-GDB">Updates to GDB</a></li><li><a href="#Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD">Using lld, the LLVM Linker, to Link FreeBSD</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Bringing-GitLab-into-the-Ports-Collection">Bringing GitLab into the Ports Collection</a></li><li><a href="#GNOME-on-FreeBSD">GNOME on FreeBSD</a></li><li><a href="#Intel-Networking-Tools">Intel Networking Tools</a></li><li><a href="#IPv6-Promotion-Campaign">IPv6 Promotion Campaign</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Obsoleting-Rails-3">Obsoleting Rails 3</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-IRC-Admin-Team" href="#FreeBSD-IRC-Admin-Team" id="FreeBSD-IRC-Admin-Team">FreeBSD IRC Admin Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/IRC/" title="https://wiki.FreeBSD.org/IRC/">FreeBSD IRC Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/IRC/" title="FreeBSD IRC Wiki">https://wiki.FreeBSD.org/IRC/</a></td></tr></table><p>
-	Contact: IRC Admin Team &lt;<a href="mailto:irc@FreeBSD.org">irc@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-	  Kubilay
-	  Kocak
-	 &lt;<a href="mailto:koobs@FreeBSD.org">koobs@FreeBSD.org</a>&gt;
-	</p><p>
-	Contact:
-	  Eitan
-	  Adler
-	 &lt;<a href="mailto:eadler@FreeBSD.org">eadler@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD IRC Admin team manages the FreeBSD Project's IRC
-	presence on the freenode IRC network, looking after:</p>
-
-      <ul>
-	<li>Registrations and ongoing management of channels within
-	  the official namespace (<tt>#freebsd*</tt>).</li>
-
-	<li>Liaising with freenode staff.</li>
-
-	<li>Allocating freebsd hostmask cloaks for users.</li>
-
-	<li>General user support.</li>
-      </ul>
-
-      <p>In order to facilitate a constructive and positive
-	environment for all members of the FreeBSD community, IRC Admin
-	over the past 3-9 months has established and consolidated a
-	consistent baseline with respect to the management of its
-	channels on freenode.  This report is a summary of what has
-	happened so far and things to come.</p>
-
-      <p>These activities were completed over the last few
-	quarters:</p>
-
-      <ul>
-	<li>Registered FreeBSD Group Contacts (GC) with freenode
-	  staff.  For information on what this means, see <a href="https://freenode.net/groupreg" shape="rect">the group
-	    registration page</a>.</li>
-
-	<li>Created a FreeBSD NickServ account to assign as primary
-	  owner/founder of the <tt>#freebsd*</tt> namespace
-	  channels.</li>
-
-	<li>The primary channels are owned/founded by a generic FreeBSD
-	  account that is owned and managed by the FreeBSD Project.</li>
-
-	<li>Created the <tt>Services::IRC</tt> component in Bugzilla
-	  for change requests and issue reports.</li>
-
-	<li>Obtained a report of all registered freenode channels
-	  matching the <tt>#freebsd*</tt> namespace and assessed the
-	  list for current ownership and activity status.</li>
-
-	<li>Assigned <tt>freebsd/</tt> user cloaks to users requesting
-	  them.  For more information, see <a href="https://wiki.FreeBSD.org/IRC/Cloaks" shape="rect">IRC
-	    Cloaks</a>.</li>
-
-	<li>Obtained a report on all nicknames and accounts with
-	  existing <tt>freebsd/*</tt> user cloaks.</li>
-
-	<li>Liaised with freenode staff on upcoming changes to freebsd
-	  channels.</li>
-      </ul>
-
-      <p>The goals for the next few quarters are to:</p>
-
-      <ul>
-	<li>Complete the transfer of founder ownership for all
-	  <tt>#freebsd*</tt> channels.  Existing channel creators,
-	  some of whom are project members and others who are not,
-	  will be contacted using known contact information or contact
-	  information set in their registered NickServ account, in
-	  order to initiate the transfer of the channel to the FreeBSD
-	  Project.  If the contact information of the existing channel
-	  owner cannot be obtained, or if no response is received
-	  after a suitable period of time has elapsed, IRC Admin will
-	  complete the ownership transfer with freenode staff.</li>
-
-	<li>Deregister defunct and inactive <tt>#freebsd*</tt>
-	  channels.  Channels which have no visible signs of activity
-	  based on last active time or registered owner last seen,
-	  have been deprecated by alternative channels, or have no
-	  other way of having ownership transferred will be
-	  deregistered.  For channels where a sunset period may be
-	  suitable, a channel topic will be set, and optionally a
-	  forwarding channel, informing users of the changes,
-	  including support and contact information.</li>
-
-	<li>Create and document baseline procedures and guidelines.
-	  These include: Community and User Guidelines, a Code of
-	  Conduct, Operator and Moderator Guidelines and Expectations,
-	  Abuse Reporting and Dispute Resolution Guidelines, and
-	  procedures for delegation of channel management.</li>
-
-	<li>Standardize and re-create channel access lists.
-	  Existing access lists and user permissions for all
-	  <tt>#freebsd*</tt> channels remain in their states prior to
-	  FreeBSD Group Registration.  Consolidation and reassignment to
-	  the FreeBSD Project is needed.  In order to ensure a consistent
-	  user and community experience in official FreeBSD channels
-	  going forward, access lists for all channels will be created
-	  from the ground up.  Users with existing access to channels
-	  may, at the IRC Admin team's discretion, be provided with
-	  the opportunity to re-apply for access subject to any
-	  conditions, terms, or guidelines that may be
-	  appropriate.</li>
-
-	<li>Determine the methods for informing project members and
-	  the community of future changes to IRC services, procedures,
-	  and policies.</li>
-
-	<li>Determine methods to designate existing channel founders
-	  as channel managers or similar.</li>
-
-	<li>Update the channels list on the Wiki to distinguish
-	  official and unofficial channels.</li>
-
-	<li>Establish consistent modes, entry messages, and topics for
-	  all channels.</li>
-      </ul>
-
-      <p>Users are invited to <tt>/join #freebsd-irc</tt> on the
-	freenode IRC network.  The IRC Admin team welcomes ideas,
-	contructive criticism, and feedback on how the FreeBSD Project
-	can improve the service and experience it provides to the
-	community.</p>
-
-      <p>While the vast majority of the broader community interacts on
-	the freenode IRC network, the FreeBSD developer presence there
-	needs to be significantly improved.</p>
-
-      <p>There are many opportunities to be had by increasing the
-	amount and quality of interaction between FreeBSD users and
-	developers, both in terms of developers keeping their finger
-	on the pulse of the community and in encouraging and
-	cultivating greater contributions to the Project over the long
-	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
-	join the FreeBSD freenode channels to help support that
-	presence.  We are the FreeBSD giants on whose shoulders the
-	future contributors stand.  It is important to be there, in
-	force.</p>
-    <hr /><h2><a name="FreeBSD-Issue-Triage-Team" href="#FreeBSD-Issue-Triage-Team" id="FreeBSD-Issue-Triage-Team">FreeBSD Issue Triage Team</a></h2><p>
-	Contact:
-	  Vladimir
-	  Krstulja
-	 &lt;<a href="mailto:vlad-fbsd@acheronmedia.com">vlad-fbsd@acheronmedia.com</a>&gt;
-	<br />
-	Contact:
-	  Kubilay
-	  Kocak
-	 &lt;<a href="mailto:koobs@FreeBSD.org">koobs@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Bugmeister &lt;<a href="mailto:bugmeister@FreeBSD.org">bugmeister@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since the Triage Team was introduced in the October&#8211;December
-	2015 report, it has been working on the following three major
-	aspects of issue triage:</p>
-
-      <ul>
-	<li>Recruiting and educating more users to assist in issue
-	  triage.</li>
-
-	<li>Identifying problem areas, especially from the fresh eyes
-	  perspective, revealing issues not immediately obvious to
-	  contributors with experience.</li>
-
-	<li>Proposing changes to improve the issue triage
-	  process.</li>
-      </ul>
-
-      <p>Our efforts have almost exclusively focused on issues in the
-	"Ports &amp; Packages" component as that is the easiest
-	starting point.  Other categories like "Base System" require
-	more knowledge and experience with problem content and
-	workflow.</p>
-
-      <p>During this time, Rodrigo was inactive due to lack of
-	available time, and Vladimir was unable to commit enough time
-	during the first quarter of the year, but provided active
-	contribution during the second.  It became obvious that the
-	Issue Triage Team must concentrate on additional recruitment
-	in the coming quarter.</p>
-
-      <p>In the last two quarters, several problems were identified
-	and the formulated solutions will be published on our upcoming
-	Wiki page.  A summary of those issues is given here:</p>
-
-      <ol>
-	<li>Issue triage, defined as "ensure that an issue is summarized,
-	  classified, and assigned to appropriate people", is too time
-	  consuming.  Bugzilla automation through auto-assign helps,
-	  but is insufficient.  If the triage process is extended to
-	  include "track the issue through its entire life to
-	  resolution", the time and effort required grows
-	  exponentially.  Fortunately, there are many things the
-	  community can do, with minimum effort, that help greatly.
-	  Part of the recruitment and education process is educating
-	  users on how to properly treat their own issues and issues
-	  they interact with, in order to maximize the efficiency of
-	  issue tracking and problem resolution.</li>
-
-	<li>Various timeouts are inadequate.  For example, the
-	  maintainer timeout is too long and does not differentiate
-	  between classes of issues, such as a non-security and a
-	  security timeout.  Other timeouts are not covered, such as
-	  assignee timeouts, when an issue has been assigned with no
-	  follow-up activity.  Another example is a timeout where
-	  additional information was requested but never provided.
-	  We will be recommending several changes and documenting
-	  these in our Wiki.</li>
-
-	<li>Partially as a consequence of inadequate timeouts and
-	  inadequate ability to efficiently track issues through their
-	  entire lifecycle, a great number of issues are open for too
-	  long.   We have identified several classes of those issues
-	  and will document the solutions to each in the near
-	  future.</li>
-
-	<li>Bugzilla is not perfect and at times it can hinder the
-	  ability to properly track issues clearly and accurately, in
-	  order to resolve them quickly.  However, changing bug
-	  tracking software is a tremendous effort, so we will instead
-	  recommend technical and workflow improvements in order to
-	  improve the user experience as much as possible.  For
-	  example, we identified additional saved searches to help
-	  track and quickly find issue categories and, more
-	  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
-	  misapplied.</li>
-
-	<li>Issue statistics are lacking, and for the next quarter we
-	  intend to change that.  Statistics help to provide insight
-	  into potential bottlenecks and inform the prioritization of
-	  improvements to the issue tracker and workflows.</li>
-      </ol>
-    <h3>Open tasks:</h3><ol><li>Recruit more suitable triagers into the team, both
-	committers and community members.</li><li>Gather and present some interesting statistics for the
-	next report.</li><li>Set up the Wiki page with identified problems and
-	recommended guidelines and policies.</li><li>Find common use patterns and add more saved searches to
-	Bugzilla.</li></ol><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/releases/10.3R/schedule.html" title="https://www.FreeBSD.org/releases/10.3R/schedule.html">FreeBSD�10.3-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/10.3R/schedule.html" title="FreeBSD�10.3-RELEASE schedule">https://www.FreeBSD.org/releases/10.3R/schedule.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/releases/11.0R/schedule.html" title="https://www.FreeBSD.org/releases/11.0R/schedule.html">FreeBSD�11.0-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/11.0R/schedule.html" title="FreeBSD�11.0-RELEASE schedule">https://www.FreeBSD.org/releases/11.0R/schedule.html</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD Development Snapshots</a></td><td>
-	    URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD Development Snapshots">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD Release Engineering Team completed the 10.3-RELEASE
-	cycle late April, led by Marius Strobl.  The release was one week
-	behind the original schedule, to accommodate for a few
-	last-minute critical issues that were essential to fix in the
-	final release.</p>
-
-      <p>The FreeBSD�11.0-RELEASE cycle started late May, one month
-	behind the original schedule.  The schedule slip was primarily
-	to accommodate efforts for packaging the FreeBSD 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
-	for 11.0-RELEASE, with the goal of promoting it to a
-	first-class feature in 11.1-RELEASE.  It is expected that
-	provisions will be made to ensure a seamless transition from older
-	supported releases.</p>
-
-      <p>Despite the fact that packaged base is not going to be a
-	prime feature for FreeBSD�11.0-RELEASE, the Release
-	Engineering Team would like to thank everyone who tested,
-	provided patches, provided ideas and feedback, and in some
-	cases, shot themselves in the foot due to bugs.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">FreeBSD Ports Website</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="FreeBSD Ports Website">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">How to Contribute</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="How to Contribute">https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">Ports Monitoring Website</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="Ports Monitoring Website">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/portmgr/index.html" title="https://www.FreeBSD.org/portmgr/index.html">Ports Management Team Website</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/portmgr/index.html" title="Ports Management Team Website">https://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/freebsd_portmgr/" title="https://twitter.com/freebsd_portmgr/">Ports Management Team on Twitter</a></td><td>
-	    URL: <a href="https://twitter.com/freebsd_portmgr/" title="Ports Management Team on Twitter">https://twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">Ports Management Team on Facebook</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">Ports Management Team on Google+</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The 2016Q3 branch of the Ports Tree currently contains over
-	26,100 ports, with the PR count around 2,000.  Of those,
-	around 425 are unassigned.  The activity dropped somewhat,
-	with 5,300 commits made by 125 active committers.  Almost
-	1,760 PRs were closed in the last quarter.</p>
-
-      <p>In the last quarter, we added two new committers: Ben Woods
-	(<tt>woodsb02</tt>) and Torsten Z�hlsdorff (<tt>tz</tt>).  No
-	commit bits were taken in for safe keeping.</p>
-
-      <p>On the management side, <tt>mat</tt> took over the role of
-	cluster admin liaison from <tt>erwin</tt>, who decided to step
-	down from portmgr.  <tt>rene</tt> took over the role of port
-	manager secretary from <tt>culot</tt>.  No other changes were
-	made.</p>
-
-      <p>A lot of work was done on modernizing the infrastructure of
-	the Ports Tree, by introducing 6 new <tt>USES</tt> knobs, one new
-	keyword, and splitting out the larger targets of
-	<tt>bsd.port.mk</tt> into separate scripts.  There were a
-	total of 42 exp-runs to validate these and other
-	infrastructure changes and package updates.  Furthermore,
-	checks were added to the quality assurance phase of Poudriere
-	to check for missing indirect dependencies, and advancements
-	were made for reproducable package builds.</p>
-
-      <p>Some noticeable package updates are: Firefox 47.0.1, Firefox
-	ESR 45.2.0, Thunderbird 45.1.1, Chromium 51.0.2704.106, Ruby
-	2.2.5, Ruby Gems 2.6.2, pkg 1.8.6, gmake 4.2.1, KDE 4.14.10,
-	Python 2.7.12, libc++ 3.8.0, and binutils 2.26.</p>
-
-      <p>Behind the scenes, <tt>antoine</tt> made sure that the
-	exp-run- and package builders were kept up-to-date.
-	<tt>bdrewery</tt> worked on further automating and hardening
-	the package building infrastructure.</p>
-
-      <p>During BSDCan, <tt>mat</tt> worked on various items,
-	including updating the Porter's Handbook, and portmgr held a
-	meeting to discuss various items.</p>
-    <hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The highlight of Core's second quarter has been the
-	regular biennial election of a new Core team.  Core would like
-	to thank Dag-Erling Sm�rgrav and Glen Barber for running
-	the vote.  Despite an initially slow uptake on nominations,
-	fourteen candidates eventually stood, including four incumbent
-	members of core.  The ninth FreeBSD Core team will be:</p>
-
-      <ul>
-	<li>John Baldwin</li>
-
-	<li>Baptiste Daroussin</li>
-
-	<li>Allan Jude</li>
-
-	<li>Ed Maste</li>
-
-	<li>Kris Moore</li>
-
-	<li>George V. Neville-Neil</li>
-
-	<li>Benedict Reuschling</li>
-
-	<li>Benno Rice</li>
-
-	<li>Hiroki Sato</li>
-      </ul>
-
-      <p>The new Core Team would like to thank the departing members
-	for their many years of service.  Members stepping down
-	are:</p>
-
-      <ul>
-	<li>Gavin Atkinson</li>
-
-	<li>Gleb Smirnoff</li>
-
-	<li>David Chisnall</li>
-
-	<li>Robert Watson</li>
-
-	<li>Peter Wemm</li>
-      </ul>
-
-      <p>The second most notable achievement this quarter was the
-	successful conclusion of an issue that had been on Core's
-	agenda for many years.  With the creation of <a href="https://planet.FreeBSD.org/" shape="rect">planet.FreeBSD.org</a>,
-	the FreeBSD Project finally has an official blog aggregation
-	service.</p>
-
-      <p>Core spent a significant amount of time reviewing licensing
-	and ensuring that the FreeBSD source remains unencumbered by
-	onerous license terms.  This quarter involved approving Adrian
-	Chadd's plan to import GPLv2 licensed code, allowing
-	<tt>bwn(4)</tt> to be built as a loadable module with support
-	for 802.11n networking.  This required confirmation that the
-	license terms on the latest dummynet AQM patches were
-	acceptable and that its variant on the BSD 2-clause license is
-	suitable for use in the FreeBSD base system.</p>
-
-      <p>Core applied for, and received, a project-wide license for
-	the use of the JetBrains static analysis tool suite, at the
-	behest of Mathieu Previot.</p>
-
-      <p>Another of Core's important functions is to ensure good
-	relations amongst developers.  To that end, members of Core
-	provided oversight over the backing-out of disputed
-	<tt>blacklistd</tt>-related patches to OpenSSH, and acted to
-	smooth over ruffled tempers.</p>
-
-      <p>This quarter saw the usual quota of gentle reminders to avoid
-	intemperate language and other counter-productive behavior.
-	Core had to take immediate action about death threats
-	appearing on some of the mailing lists.  The culprit was
-	immediately banned from the mailing lists and reported to
-	their email service provider.  That person will be similarly
-	removed should they be identified as having rejoined under a
-	different alias.</p>
-
-      <p>Other activities included:</p>
-
-      <ul>
-	<li>Working with university authorities in an attempt to get
-	  documentation certifying that a prospective GSoC student was
-	  legally allowed to work on FreeBSD code as a foreigner enrolled
-	  at a USA university.  This issue was eventually solved by
-	  the student returning home for the summer and working from
-	  there.</li>
-
-	<li>Issuing guidance on policy around forced commits, or
-	  trivial changes used as a means of correcting a commit
-	  message.  In these cases, the correct approach is to revert
-	  the commit and re-commit with the correct message.  This
-	  ensures the continuing usefulness of
-	  <tt>svn blame</tt>.</li>
-
-	<li>Approving a delay to the planned introduction of packaged
-	  base and confirming that this did not require any change to
-	  the new support policies to be introduced with
-	  11.0-RELEASE.</li>
-      </ul>
-
-      <p>During this quarter, four new commit bits were awarded and
-	none were taken in.  Please welcome Emmanuel Vadot, Landon
-	Fuller, Mike Karels, and Eric Badger as new src committers.
-	Yes, that is the same Mike Karels who was once a member of the
-	CSRG at Berkeley and co-author of <i>The Design and
-	  Implementation of the 4.3BSD UNIX Operating System</i>.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsdfoundation.org/" title="https://www.freebsdfoundation.org/">FreeBSD Foundation Website</a></td><td>
-	    URL: <a href="https://www.freebsdfoundation.org/" title="FreeBSD Foundation Website">https://www.freebsdfoundation.org/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to supporting and promoting the FreeBSD
-	Project and community worldwide.  Funding comes from individual and
-	corporate donations and is used to fund and manage development
-	projects, conferences and developer summits, and provide travel
-	grants to FreeBSD developers.  The Foundation purchases hardware to
-	improve and maintain FreeBSD infrastructure and publishes FreeBSD
-	white papers and marketing material to promote, educate, and
-	advocate for the FreeBSD Project.  The Foundation also represents
-	the FreeBSD Project in executing contracts, license agreements,
-	and other legal arrangements that require a recognized legal
-	entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD
-	last quarter:</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>Our work is 100% funded by your donations.  Our spending
-	budget for 2016 is $1,250,000 and we've raised $265,000 so far.
-	Our Q1-Q2 financial reports will be posted by August 1.  As you can
-	see, we need your donations to continue supporting FreeBSD at our
-	current level.  Please consider making a donation here:
-	<a href="http://freebsdfoundation.org/donate" shape="rect">freebsdfoundation.org/donate</a>.</p>
-
-      <p>OS Improvements</p>
-
-      <p>The Foundation improves FreeBSD by funding software
-	development projects approved through our proposal submission
-	process, and our internal software developer staff members.  Two
-	Foundation-funded projects continued last quarter; one project is
-	to improve the stability of the vnet network stack virtualization
-	infrastructure, and the second is phase two of the FreeBSD/arm64
-	port project.</p>
-
-      <p>Foundation staff members were responsible for many changes
-	over the quarter.  Kostik Belousov accomplished the following work
-	last quarter: implemented robust mutexes support, as part of
-	ongoing efforts to bring our threading library into POSIX
-	compliance and feature completeness; documented kernel interfaces
-	used by the threading library and produced almost 30 pages of
-	technical text; completed and committed the elimination of the
-	pvh_global_lock from the amd64 pmap, which removed a hot contested
-	lock; and fixed bugs that help keep FreeBSD stable and
-	reliable.</p>
-
-      <p>Edward Napierala accomplished the following work last
-	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
-	iSCSI sessions.</p>
-
-      <p>Ed Maste, our Project Development Director,  accomplished
-	the following work last quarter: investigated the state of
-	reproducible builds in the ports tree, with some work in progress
-	to address issues; updated the ELF Tool Chain tools with bug fixes
-	and improved handling of malformed input; investigated using
-	<tt>lld</tt>, the linker from the LLVM family, to link the FreeBSD
-	base system; and reported on and tested patches for issues found.
-	He also managed the <tt>arm64</tt> development project and
-	investigated and fixed a number of bugs.  Lastly, he imported
-	LLVM's <tt>libunwind</tt> and prepared it for use in FreeBSD 11, and
-	investigated and reviewed the <tt>blacklistd</tt> proposal and
-	patches.</p>
-
-      <p>George Neville-Neil continued hosting the bi-weekly Transport
-	conference call (notes at <a href="https://wiki.FreeBSD.org/TransportProtocols" shape="rect">https://wiki.FreeBSD.org/TransportProtocols</a>)
-	and the bi-weekly DTrace conference call (notes at <a href="https://wiki.FreeBSD.org/DTrace" shape="rect">https://wiki.FreeBSD.org/DTrace</a>.</p>
-
-      <p>Ed continued facilitating the bi-weekly graphics call to
-	coordinate efforts on the <tt>i915</tt> driver and other graphics
-	stack work.</p>
-
-      <p>Several of these projects are described elsewhere in this
-	quarterly report.</p>
-
-      <p>Release Engineering</p>
-
-      <p>Foundation employee and release engineer Glen Barber worked
-	closely with Marius Strobl on the 10.3-RELEASE, which was
-	completed in April.  Glen also merged the release-pkg branch to
-	11-CURRENT, though this will be a beta feature for 11.0-RELEASE.
-	Lastly, with the Release Engineering Team, he started the
-	11.0-RELEASE cycle.  Find out more in the Release Engineering Team
-	status entry in this report.</p>
-
-      <p>"Getting Started with FreeBSD" Project</p>
-
-      <p>We hired a summer intern, with no FreeBSD, Linux, or any
-	command line operating system experience, to figure out on his own
-	how to install and use FreeBSD.  He is writing easy-to-follow how-to
-	guides to help make the new user experience straightforward and
-	positive.  He's also been submitting bug reports and problems
-	through the appropriate channels.  You can check out his first
-	how-to guide at <a href="https://www.freebsdfoundation.org/freebsd/how-to-guides/" shape="rect">https://www.freebsdfoundation.org/freebsd/how-to-guides/</a>.</p>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating for
-	the Project.  This includes promoting work being done by others
-	with FreeBSD; producing advocacy literature to teach people about
-	FreeBSD and help make the path to starting using FreeBSD or
-	contributing to the Project easier; and attending and getting
-	other FreeBSD contributors to volunteer to run FreeBSD events,
-  staff FreeBSD tables, and give FreeBSD presentations.</p>
-
-      <p>Some of the work we did last quarter to support FreeBSD
-	advocacy included:  Creating a FreeBSD page on our website to promote
-	FreeBSD derivative projects and showcase FreeBSD users (<a href="https://www.freebsdfoundation.org/freebsd/" shape="rect">https://www.freebsdfoundation.org/freebsd/</a>),
-	and promoting FreeBSD research by creating a Research page on our
-	site and conference handout (<a href="https://www.freebsdfoundation.org/what-we-do/research/" shape="rect">https://www.freebsdfoundation.org/what-we-do/research/</a>).</p>
-
-      <p>We created guidelines and a repository for using the Project and
-	Foundation logos (<a href="https://www.freebsdfoundation.org/about/brand-assets/" shape="rect">https://www.freebsdfoundation.org/about/brand-assets/</a>).</p>
-
-      <p>To help showcase FreeBSD contributors, we published two new Faces
-	of FreeBSD stories, about Michael Lucas (<a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-michael-lucas/" shape="rect">https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-michael-lucas/</a>)
-	and Kris Moore <a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-kris-moore/" shape="rect">https://www.freebsdfoundation.org/blog/faces-of-freebsd-2016-kris-moore/</a>).</p>
-
-      <p>We published the March/April and May/June issues of the
-	FreeBSD Journal and participated in editorial board work.  Kirk
-	McKusick wrote a feature article on the Fast Filesystem for the
-	March/April issue, and other team members helped review and edit
-	Journal articles.</p>
-
-      <p>We also published monthly newsletters to highlight work being
-	done to support FreeBSD, tell you about upcoming events, and provide
-	other information to keep you in the loop on what we're doing to
-	support the FreeBSD Project and community.</p>
-
-      <p>George Neville-Neil and Robert Watson continued teaching
-	and developing open source FreeBSD teaching materials at
-	<a href="http://teachbsd.org" shape="rect">teachbsd.org</a>.</p>
-
-      <p>We launched the first Hosting Partner Spotlight to showcase
-	the Project's partnership with NYI (<a href="https://www.freebsdfoundation.org/blog/hosting-partner-spotlight-nyi-at-the-heart-of-freebsd/" shape="rect">https://www.freebsdfoundation.org/blog/hosting-partner-spotlight-nyi-at-the-heart-of-freebsd/</a>)</p>
-
-      <p>We worked with Microsoft to get FreeBSD onto Azure (<a href="https://www.freebsdfoundation.org/blog/more-from-the-freebsd-foundation-on-the-projects-partnership-with-microsoft/" shape="rect">https://www.freebsdfoundation.org/blog/more-from-the-freebsd-foundation-on-the-projects-partnership-with-microsoft/</a>).</p>
-
-      <p>The Foundation was quoted in Cavium's Thunder X2 press release
-	(<a href="http://www.prnewswire.com/news-releases/cavium-announces-thunderx2-300276536.html" shape="rect">http://www.prnewswire.com/news-releases/cavium-announces-thunderx2-300276536.html</a></p>
-
-      <p>George worked with ARM to coordinate the upcoming ARM Partner
-	Meeting in Cambridge.</p>
-
-      <p>Conferences and Events</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events,
-	and summits around the globe.  These events can be BSD-related,
-	open source, or technology events geared towards underrepresented
-	groups.</p>
-
-      <p>We support the FreeBSD-focused events to help provide a
-	venue for sharing knowledge, to work together on projects, and to
-	facilitate collaboration between developers and commercial users.
-	This all helps provide a healthy ecosystem.  We support the
-	non-FreeBSD events to promote and raise awareness about FreeBSD, to
-	increase the use of FreeBSD in different applications, and to recruit
-	more contributors to the Project.</p>
-
-      <p>In April, Benedict Reuschling helped organize and run a
-	hackathon in Essen April 22-24.  He then attended the Open Source
-	Datacenter conference in Berlin, with Allan Jude, to give a talk
-	about "Interesting things you can do with ZFS," which highlighted
-	OpenZFS features and how well they work on FreeBSD
-	(<a href="https://www.netways.de/index.php?id=3445#c44065" shape="rect">https://www.netways.de/index.php?id=3445#c44065</a>).</p>
-
-      <p>We promoted FreeBSD at:</p>
-
-      <ul>
-	<li>Flourish &#8212; April 1-2 in Chicago
-	  (<a href="http://flourishconf.com/2016/" shape="rect">http://flourishconf.com/2016/</a>)</li>
-
-	<li>LFNW &#8212; April 23-24 in Bellingham WA
-	  (<a href="https://www.linuxfestnorthwest.org/2016" shape="rect">https://www.linuxfestnorthwest.org/2016</a>).</li>
-
-	<li>OSCON &#8212; May 18-19 in Austin, TX
-	  (<a href="http://conferences.oreilly.com/oscon/open-source-us" shape="rect">http://conferences.oreilly.com/oscon/open-source-us</a></li>
-      </ul>
-
-      <p>Deb Goodkin and Dru Lavigne attended the Community
-	Leadership Summit in Austin: May 14, 15
-	(<a href="http://www.communityleadershipsummit.com/schedule/" shape="rect">http://www.communityleadershipsummit.com/schedule/</a>)</p>
-
-      <p>Deb promoted FreeBSD at USENIX ATC June 22-23 in Denver, CO.</p>
-
-      <p>Our team attended BSDCan and the Ottawa Developer Summit.
-	We held our annual board meeting to vote on officers, board
-	members, and work on our strategic planning.  Most of us attended
-	the developer/vendor summits.  Kirk McKusick presented "A
-	Brief History of the BSD Fast Filesystem" (<a href="http://www.bsdcan.org/2016/schedule/events/654.en.html" shape="rect">http://www.bsdcan.org/2016/schedule/events/654.en.html</a>).
-	Ed Maste gave a presentation on "Reproducible Builds in
-	FreeBSD".  George helped run the vendor summit.</p>
-
-      <p>We sponsored five FreeBSD contributors to attend BSDCan.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them.  We continued to review requests
-	and grant permission to use the trademarks.</p>
-
-      <p>FreeBSD Community Engagement</p>
-
-      <p>We launched our first Community Survey.  The purpose was to get
-	input from the community on why they use FreeBSD, what they'd like to
-	see the Foundation support, and other input to help us determine
-	our direction and how we should support the Project.</p>
-
-      <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>
-
-      <p>Other Stuff We Did</p>
-
-      <p>Last quarter we purchased a server to reside at NYI to
-	improve the continuous integration tools within the Project.</p>
-
-      <p>We had two face-to-face board meetings last quarter to work
-	on strategic planning and identify areas in the project we should
-	support.</p>
-
-      <p>We also held our first ever staff retreat in Boulder,
-	Colorado to give our small team an opportunity to work together
-	in person.</p>
-
-      <p>We hired Sabine Percarpio as our Administration Manager.
-	She is helping us manage donations, accounting, travel grant
-	applications, handle questions that come in to the Foundation, and
-	run our organization smoothly.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="ASLR-Interim-State" href="#ASLR-Interim-State" id="ASLR-Interim-State">ASLR Interim State</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://kib.kiev.ua/kib/aslr" title="http://kib.kiev.ua/kib/aslr">Patch Home</a></td><td>
-	    URL: <a href="http://kib.kiev.ua/kib/aslr" title="Patch Home">http://kib.kiev.ua/kib/aslr</a></td></tr></table><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>This is an interim report on the technical state of my
-	work towards ASLR support in the FreeBSD 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
-	for analyzing ASLR failures in specific programs.  This
-	utility leverages the <tt>procctl(2)</tt> interface which was
-	added to the previous version of the patch, with some bug
-	fixes.</p>
-
-      <p>With r300792, ASLR settings are reset to system-wide defaults
-	whenever a setuid binary is executed.</p>
-
-      <p>The command's syntax is:</p>
-
-      <p><tt>proccontrol -m (trace|aslr) [-q] [-s (enable|disable)]
-	[-p pid | command]</tt></p>
-
-      <p>with possible arguments</p>
-
-      <p><tt>-m</tt> (specifies the trace mode to control debugger
-	attachments)</p>
-
-      <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>-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
-	settings from <tt>proccontrol</tt>.  For instance, to start a
-	build of a program with ASLR disabled, use
-	<tt>proccontrol -m aslr -s disable make</tt>.</p>
-
-      <p>A ports exp-run was done with ASLR tuned up to the most
-	aggressive settings.  The results can be found in <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=208580" shape="rect">PR 208580</a>.</p>
-
-      <p>Case study: Lisp</p>
-
-      <p>SBCL is an interesting case which illustrates several points.
-	It is much smaller than JDK, and its build system is easier to
-	work with.  The code provides a very non C-like language
-	runtime which utilizes a lot of corner cases and makes non-standard
-	uses of the VM system, at least from the point of view of a typical C
-	programmer.</p>
-
-      <p>SBCL compiles Lisp forms into the machine native code and
-	manages its own arena for objects.  The precompiled Lisp
-	runtime is mapped from a <tt>core</tt> file.  SBCL relies on
-	the operating system's C runtime for the initial load of Lisp,
-	and needs a functional <tt>libc</tt> to issue many system
-	calls, including syscalls, as well as the dynamic loader.  The
-	end result is that there are unfixed <tt>mmap(2)</tt> calls
-	during both startup and runtime, interfering with other
-	<tt>MAP_FIXED mmaps</tt>.  The loading of the core file
-	and the private arenas are hard-coded to exist at fixed
-	addresses.</p>
-
-      <p>This happens to work on the default address map, which is not
-	changed often, so the SBCL choices of the base addresses
-	evolved to work.  But any significant distortion of the
-	standard map results in <tt>SBCL mmap(MAP_FIXED)</tt> requests
-	attempting to override memory from other allocators.</p>
-
-      <p>FreeBSD uses the <tt>MAP_EXCL</tt> flag to <tt>mmap(2)</tt>,
-	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
-	later use with <tt>MAP_FIXED</tt>.  So, <tt>MAP_EXCL</tt>
-	mappings failed, dumping the process into <tt>ldb</tt>.</p>
-
-      <p>On Linux, if it is detected that the kernel is in AS-randomization mode,
-	the initial SBCL runtime sets its personality to non-random and
-	re-execs.  This might be a solution for FreeBSD as well, after
-	the ASLR patch is committed, so that the <tt>procctl(2)</tt>
-	knob is officially available.</p>
-
-      <p>SBCL still has issues on Linux, even with re-exec, when
-	more aggressive randomization from the PaX patch is applied, as
-	seen in <a href="https://bugs.launchpad.net/sbcl/+bug/1523213" shape="rect">bug
-	  1523213</a>.</p>
-
-      <p>Case study: Emacs</p>
-
-      <p>The Emacs build procedure involves loading the
-	<tt>temacs</tt> image with the compiled Emacs Lisp files and
-	then dumping its memory to create an image with the content
-	preloaded, in order to reduce startup time.</p>
-
-      <p>Recent Emacs sources seem to generally avoid
-	<tt>MAP_FIXED</tt>, except in some situations.  When Emacs
-	does use the flag, it carefully checks that the selected
-	region is not busy.  In fact, Emacs would benefit from using
-	<tt>MAP_EXCL</tt>.</p>
-
-      <p>I tried several runs of building Emacs and running the dumped
-	binary, but was not able to reproduce any issues.  It seems
-	that the code improved enough to tolerate ASLR both in Linux
-	and NetBSD without turning it off.</p>
-
-      <p>In my opinion, it is not reasonable to fight the issues in
-	the kernel as most of it is not fixable from the kernel side.
-	The <tt>procctl(2)</tt> interface and <tt>proccontrol(1)</tt>
-	utilities provide an override when needed, but are not
-	automated.</p>
-
-      <p>Conclusions</p>
-
-      <p>The set of ports which cannot be built with ASLR turned on
-	should be limited but fluid.  However, exp-runs may not
-	reliably uncover all problems due to randomization, as seen in
-	the Emacs example.  In the route to enable ASLR by default (with
-	non-aggressive settings), the ports framework should provide an
-	option like <tt>ASLR_UNSAFE=yes</tt> which spawns
-	<tt>proccontrol -m aslr -s disable make</tt> for the build
-	stages of the unsafe port.  Users would still need to be aware
-	of <tt>proccontrol(1)</tt> in order to run the resulting
-	binary or wrapper scripts provided to do so.</p>
-
-      <p>A recommended approach is a flag in the ELF binary to mark
-	it as not compatible with non-standard AS layouts.  This frees
-	users from having to use <tt>proccontrol(1)</tt>, but still
-	requires patching the application's build process and
-	upstreaming the changes.  This approach is also
-	useful outside the context of ASLR.  However, that
-	mechanism is not yet ready, and developing it is a larger work
-	than ASLR itself.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ceph-on-FreeBSD" href="#Ceph-on-FreeBSD" id="Ceph-on-FreeBSD">Ceph on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ceph.com" title="http://ceph.com">Ceph Main Site</a></td><td>
-	    URL: <a href="http://ceph.com" title="Ceph Main Site">http://ceph.com</a></td></tr><tr><td><a href="https://github.com/ceph/ceph" title="https://github.com/ceph/ceph">Main Repository</a></td><td>
-	    URL: <a href="https://github.com/ceph/ceph" title="Main Repository">https://github.com/ceph/ceph</a></td></tr><tr><td><a href="https://github.com/wjwithagen/ceph" title="https://github.com/wjwithagen/ceph">My Fork</a></td><td>
-	    URL: <a href="https://github.com/wjwithagen/ceph" title="My Fork">https://github.com/wjwithagen/ceph</a></td></tr><tr><td><a href="https://github.com/ceph/ceph/pull/7573" title="https://github.com/ceph/ceph/pull/7573">Pull Request With FreeBSD-Specific Changes to Ceph</a></td><td>
-	    URL: <a href="https://github.com/ceph/ceph/pull/7573" title="Pull Request With FreeBSD-Specific Changes to Ceph">https://github.com/ceph/ceph/pull/7573</a></td></tr></table><p>
-	Contact:
-	  Willem Jan
-	  Withagen
-	 &lt;<a href="mailto:wjw@digiware.nl">wjw@digiware.nl</a>&gt;
-	</p>
-      <p>Ceph is a distributed object store and filesystem designed
-	to provide excellent performance, reliability, and
-	scalability.  It provides the following features:</p>
-
-      <ol>
-	<li>Object Storage: Ceph provides seamless access to objects
-	  using native language bindings or <tt>radosgw</tt>, a REST
-	  interface that is compatible with applications written for
-	  S3 and Swift.</li>
-
-	<li>Block Storage: Ceph&#8217;s RADOS Block Device (RBD) provides
-	  access to block device images that are striped and
-	  replicated across the entire storage cluster.</li>
-
-	<li>File System: Ceph provides a POSIX-compliant network
-	  filesystem that aims for high performance, large data storage,
-	  and maximum compatibility with legacy applications.</li>
-      </ol>
-
-      <p>I started looking into Ceph because using HAST with CARP and
-	<tt>ggate</tt> did not meet my requirements.  My primary goal
-	with Ceph is to run a storage cluster of ZFS storage nodes
-	where the clients run <tt>bhyve</tt> on RBD disks stored in Ceph.</p>
-
-      <p>The FreeBSD build process can build most of the tools in
-	Ceph.  However, the RBD-dependent items do not work, since
-	FreeBSD does not yet provide RBD support.</p>
-
-      <p>Since the last quarterly report, the following progress was
-	made:</p>
-
-      <ol>
-	<li>Switching to using CMake from Automake results in a
-	  much cleaner development environment and better test output.
-	  The changes can be found in the
-	  <tt>wip-wjw-freebsd-cmake</tt> branch.</li>
-
-	<li>The throttling code has been overhauled to prevent live locks.
-	  These mainly occur on FreeBSD but also manifest on Linux.</li>
-
-	  <li>A few more tests were fixed.  On one occasion, I was able to
-	  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 the Clang 3.4
-	available on stable/10
-	does not have all of the capabilities required to compile
-	everything.</p>
-
-      <p>This setup will get things running for FreeBSD:</p>
-
-      <ul>
-	<li>
-	  <p>Install <tt>bash</tt> and link to it in <tt>/bin</tt>
-	    (requires root privileges):</p>
-
-	  <p><tt>sudo pkg install bash</tt></p>
-
-	  <p><tt>sudo ln -s /usr/local/bin/bash /bin/bash</tt></p>
-	</li>
-
-	<li>
-	  <p>Build Ceph:</p>
-
-	  <p><tt>git clone https://github.com/wjwithagen/ceph.git</tt></p>
-
-	  <p><tt>cd ceph</tt></p>
-
-	  <p><tt>git checkout wip-wjw-freebsd-tests</tt></p>
-
-	  <p><tt>./do_freebsd-cmake.sh --deps</tt></p>
-	</li>
-      </ul>
-
-      <p>The <tt>--deps</tt> argument is only needed for the initial
-	installation, to pull in the necessary dependencies; it should be
-	omitted for subsequent builds.</p>
-
-      <p>CMake is now used to build Ceph on FreeBSD; the old method
-	using automake is no longer used.</p>
-
-      <p>Parts Not Yet Included:</p>
-
-      <ul>
-	<li>RBD: Rados Block Devices are currently implemented in the
-	  Linux kernel, but there used to be a userspace
-	  implementation.  It is possible that <tt>ggated</tt> could
-	  be used as a template, since it provides some of the same
-	  functionality and it has a userspace counterpart.</li>
-
-	<li>BlueStore: FreeBSD and Linux have a different AIO API which
-	  needs to be bridged.  There has been some
-	  discussion about <tt>aio_cancel</tt> not working for all
-	  device types in FreeBSD.</li>
-
-	<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 features are
-	  also excluded from the test suite.</li>
-      </ul>
-
-      <p>Tests Not Yet Included:</p>
-
-      <ul>
-	<li><tt>ceph-detect-init/run-tox.sh</tt>: the current
-	  implementation does not know anything about FreeBSD's
-	  <tt>rc</tt> system.</li>
-
-	<li>Tests that make use of <tt>nosetests</tt> do not really
-	  work since <tt>nosetests</tt> is not in <tt>/usr/bin</tt>,
-	  and calling <tt>/usr/bin/env nosetests</tt> does not work on
-	  FreeBSD.</li>
-
-	<li><tt>test/pybind/test_ceph_argparse.py</tt></li>
-
-	<li><tt>test/pybind/test_ceph_daemon.py</tt></li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>The current and foremost task is to get the test suite to
-	complete without errors.</li><li>Build an automated test platform that will build
-	<tt>ceph/master</tt> on FreeBSD and report the results back to
-	the Ceph developers.  This will increase the maintainability
-	of the FreeBSD side of things, as developers are signaled that
-	they are using Linux-isms that will not compile or run on
-	FreeBSD.  Ceph has several projects that support this: Jenkins,
-	teuthology, and palpito.  But even a
-	<tt>while { compile }</tt> loop that reports the build data on
-	a static webpage is a good start.</li><li>Run integration tests to see if the FreeBSD daemons will work
-	with a Linux Ceph platform.</li><li>Get the currently excluded Python tests to work.</li><li>Compile and test the userspace RBD (Rados Block
-	Device).</li><li>Investigate if an in-kernel RBD device could be developed
-	akin to <tt>ggate</tt>.</li><li>Investigate the keystore which currently prevents the
-	building of Cephfs and some other parts.</li><li>Integrate the FreeBSD <tt>/etc/rc.d</tt> init scripts in the
-	Ceph stack for testing and for running Ceph on production
-	machines.</li></ol><hr /><h2><a name="EFI-Refactoring-and-GELI-Support" href="#EFI-Refactoring-and-GELI-Support" id="EFI-Refactoring-and-GELI-Support">EFI Refactoring and GELI Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/emc2/freebsd/tree/geli_efi" title="https://github.com/emc2/freebsd/tree/geli_efi">GELI Support Branch</a></td><td>
-	    URL: <a href="https://github.com/emc2/freebsd/tree/geli_efi" title="GELI Support Branch">https://github.com/emc2/freebsd/tree/geli_efi</a></td></tr><tr><td><a href="https://github.com/emc2/freebsd/tree/efize" title="https://github.com/emc2/freebsd/tree/efize">EFI Refactoring Branch</a></td><td>
-	    URL: <a href="https://github.com/emc2/freebsd/tree/efize" title="EFI Refactoring Branch">https://github.com/emc2/freebsd/tree/efize</a></td></tr></table><p>
-	Contact:
-	  Eric
-	  McCorkle
-	 &lt;<a href="mailto:eric@metricspace.net">eric@metricspace.net</a>&gt;
-	</p>
-      <p>The EFI bootloader has undergone considerable refactoring to
-	make more use of the EFI API.  The filesystem code in
-	<tt>boot1</tt> has been eliminated, and a single codebase for
-	filesystems now serves both <tt>boot1</tt> and
-	<tt>loader</tt>.  This codebase is organized around the EFI
-	driver model and it should be possible to export any
-	filesystem implementation as a standalone EFI driver without
-	too much effort.</p>
-
-      <p>Both <tt>boot1</tt> and <tt>loader</tt> have been refactored
-	to utilize the <tt>EFI_SIMPLE_FILE_SYSTEM</tt> interface.
-	In the loader, this is accomplished with a dummy
-	filesystem driver that is just a translation layer between the
-	loader filesystem interface and
-	<tt>EFI_SIMPLE_FILE_SYSTEM</tt>.  A reverse translation layer
-	allows the existing filesystem drivers to function as EFI
-	drivers.</p>
-
-      <p>The EFI refactoring by itself exists in a
-	<a href="https://github.com/emc2/freebsd/tree/efize" shape="rect">branch
-	  on github</a>.</p>
-
-      <p>Additionally, GELI support has been added using the EFI
-	refactoring.  This allows booting from a GELI-encrypted
-	filesystem.  Note that the EFI system partition, which
-	contains <tt>boot1</tt>, must be a plaintext msdosfs
-	partition.  This patch adds an intake buffer to the crypto
-	framework, which allows injection of keys directly into a
-	loaded kernel, without the need to pass them through
-	arguments or environment variables.  This patch only uses the
-	intake buffer for EFI GELI support, as legacy BIOS GELI support
-	still uses environment variables.</p>
-
-      <p>EFI GELI support depends on the
-	<a href="https://github.com/emc2/freebsd/tree/geli_efi" shape="rect">efize branch</a>.</p>
-
-      <p>These patches have been tested and used and should be able
-	to handle use by early adopters.  Note that the
-	<tt>LOADER_PATH</tt> variable has been changed to
-	<tt>/boot/loader.tst</tt>, to facilitate safe testing.</p>
-
-      <strong>IMPORTANT:</strong>
-
-      <p>As this is an encrypted filesystem patch, an error can
-	potentially leave data inaccessible.  It is
-	<em>strongly</em> recommended to use the following procedure
-	for testing:</p>
-
-      <ol>
-	<li>
-	  <p>Back up your data!</p>
-	</li>
-
-	<li>
-	  <p>Do not forget to back up your data!</p>
-	</li>
-
-	<li>
-	  <p>Install an EFI shell on the EFI System Partition (ESP).</p>
-	</li>
-
-	<li>
-	  <p>Install the patched <tt>boot1</tt> on the ESP to
-	    something like <tt>/boot/efi/BOOTX64.TST</tt>.</p>
-	</li>
-
-	<li>
-	  <p>Install the patched loader to <tt>/boot/loader.tst</tt>
-	    on your machine.</p>
-	</li>
-
-	<li>
-	  <p>Create a GELI partition outside of the normal boot
-	    partition.</p>
-	</li>
-
-	<li>
-	  <p>First, try booting <tt>/boot/efi/BOOTX64.TST</tt> and
-	    make sure it properly handles the encrypted partition.</p>
-	</li>
-
-	<li>
-	  <p>Copy a boot environment, including the patched loader, to
-	    the encrypted partition.</p>
-	</li>
-
-	<li>
-	  <p>Use the loader prompt to load a kernel from the encrypted
-	    partition.</p>
-	</li>
-
-	<li>
-	  <p>Try switching over to an encrypted main partition once
-	    everything else is working.</p>
-	</li>
-      </ol>
-    <h3>Open tasks:</h3><ol><li>Testing is needed.</li><li>The code will need review, and some <tt>style(9)</tt>
-	normalization must occur before it goes into FreeBSD.</li></ol><hr /><h2><a name="Robust-Mutexes" href="#Robust-Mutexes" id="Robust-Mutexes">Robust Mutexes</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>Now that process-shared locks are implemented for our
-	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
-	modifying the shared state.  The supported model is to protect
-	shared state by a <tt>pthread_mutex</tt>, and the crash is
-	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
-	mutexes.</p>
-
-      <p>An application must be specifically modified to handle and
-	recover from failures.  The <tt>pthread_mutex_lock()</tt>
-	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
-	application may detect the error and refuse to operate until
-	the persistent shared data is recovered, such as by manual
-	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 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.
-      </p>
-
-      <p>It is curious but not unexpected that this interface is not
-	used widely.  The only real-life application which utilizes it
-	is Samba.  Using Samba with an updated FreeBSD base uncovered
-	minor bugs both in the FreeBSD robust mutex implementation, and
-	in Samba itself.</p>
-
-      <p>It is believed that <tt>libthr</tt> in FreeBSD 11 is
-	POSIX-compliant for major features.  Further work is planned
-	to look at inlining the lock structures to remove overhead
-	and improve the performance of the library.</p>
-
-      <p>Most of the implementation of the robustness feature
-	consisted of making small changes in the lock and unlock
-	paths, both in <tt>libthr</tt> and in <tt>kern_umtx.c</tt>.
-	This literally required reading all of the code dealing with
-	mutexes and condition variables, which was something I
-	wanted to help future developers with.  In the end, with the
-	help of Ed Maste, man pages for <tt>umtx(2)</tt> and all
-	<tt>thr*(2)</tt> syscalls were written and added to the base
-	system's documentation set.
-      </p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Use the implementation in real-word applications and
-	report issues.</li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/freebsd-base-graphics" title="https://github.com/FreeBSDDesktop/freebsd-base-graphics">GitHub Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop/freebsd-base-graphics" title="GitHub Repository">https://github.com/FreeBSDDesktop/freebsd-base-graphics</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/Graphics" title="http://wiki.FreeBSD.org/Graphics">Graphics Stack Roadmap and Supported Hardware Matrix</a></td><td>
-	    URL: <a href="http://wiki.FreeBSD.org/Graphics" title="Graphics Stack Roadmap and Supported Hardware Matrix">http://wiki.FreeBSD.org/Graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSD/freebsd-ports-graphics" title="https://github.com/FreeBSD/freebsd-ports-graphics">Ports Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/freebsd-ports-graphics" title="Ports Development Repository">https://github.com/FreeBSD/freebsd-ports-graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next-4.6" title="https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next-4.6">DRM 4.6 Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next-4.6" title="DRM 4.6 Development Repository">https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next-4.6</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes" title="https://wiki.FreeBSD.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes">GSoC 2016: Link /dev Entries to Sysctl Nodes</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes" title="GSoC 2016: Link /dev Entries to Sysctl Nodes">https://wiki.FreeBSD.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq" title="https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq">GSoC 2016: Redesign libdevq</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq" title="GSoC 2016: Redesign libdevq">https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq</a></td></tr><tr><td><a href="http://planet.FreeBSD.org/graphics" title="http://planet.FreeBSD.org/graphics">Graphics Team Blog</a></td><td>
-	    URL: <a href="http://planet.FreeBSD.org/graphics" title="Graphics Team Blog">http://planet.FreeBSD.org/graphics</a></td></tr></table><p>
-	Contact: FreeBSD Graphics team &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Matthew
-	  Macy
-	 &lt;<a href="mailto:mmacy@nextbsd.org">mmacy@nextbsd.org</a>&gt;
-	</p>
-      <p>In the Ports tree, Mesa was updated to 11.2.2.  The next
-	major release, 12.0.0 release candidate 4, is ready for
-	testing in our development tree.</p>
-
-      <p>The GSoC project about being able to connect a <tt>/dev</tt>
-	entry to <tt>sysctl</tt> nodes is making progress.  After some
-	fruitful discussons on the <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-arch" shape="rect">freebsd-arch@
-	  mailing-list</a>,
-	Kiloreux finished the design and is now implementing the
-	solution.  The GSoC project on <tt>libdevq</tt> was
-	abandoned.</p>
-
-      <p>All Intel GPUs up to and including the unreleased Kaby Lake
-	are supported.  The <tt>xf86-video-intel</tt> driver will be
-	updated soon.  Updating this driver requires updating
-	<tt>Xorg</tt>, which in turn is blocked on Nvidia updates.</p>
-
-      <p>Several problems remain to be solved:</p>
-
-      <ul>
-	<li>There are instances of visual artifacts that appear with
-	  varying frequency, depending on workload.  Of particular
-	  note is the lack of redraw when a Qt5 window is partially
-	  covered by a menu and then uncovered.</li>
-
-	<li>WebGL demos will sometimes fail due to a recoverable
-	  render ring hang.</li>
-
-	<li>There are still some known stability issues with
-	  processors prior to Sandy Bridge (pre-2010).</li>
-      </ul>
-
-      <p>Matt Macy is hoping to be able to diagnose the first two
-	issues, along with others, by updating Linux support to the
-	point where the Intel GPU Tools work on FreeBSD.</p>
-
-      <p>The Radeon AMD/ATI driver has been updated to GCN 1.0.  This has
-	only been tested on an R7 240.  2D-accelerated X works.  Due
-	to apparent issues with user library support, X does not
-	recognize the KMS driver as being 3D-capable and reports it as
-	"not DRI2 capable".  The OpenCL benchmark <tt>clpeak</tt>
-	fails in <tt>drm/ttm</tt>, so there may in fact be issues in
-	the underlying 3D support.</p>
-
-      <p>The Amdgpu AMD/ATI driver has been updated to GCN 1.1 and
-	higher.  The KMS driver loads and attaches on discrete GPUs,
-	though problems still exist on the Carizzo APU.  X will not
-	start due to unimplemented functions in <tt>libdrm</tt>.  Koop
-	Mast is actively working on this and should have it fixed
-	soon.</p>
-
-      <p>None of the required patches to <tt>src/sys</tt> were
-	committed in time for FreeBSD 11.  Although the plan is to
-	ultimately make <tt>linuxkpi</tt>, <tt>drm</tt>,
-	<tt>i915</tt>, <tt>radeon</tt>, and <tt>amdgpu</tt> updates
-	available as ports, this will likely not happen until
-	development has slowed to the point where it is economical to
-	backport them to FreeBSD in svn.  Until that time, modern GPU
-	support will be available in PC-BSD snapshots and in the
-	<tt>drm-next-4.6</tt> branch on GitHub.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="ARM-Allwinner-SoC-Support" href="#ARM-Allwinner-SoC-Support" id="ARM-Allwinner-SoC-Support">ARM Allwinner SoC Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner">Allwinner FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="Allwinner FreeBSD Wiki">https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner</a></td></tr></table><p>
-	Contact:
-	  Jared
-	  McNeill
-	 &lt;<a href="mailto:jmcneill@FreeBSD.org">jmcneill@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Emmanuel
-	  Vadot
-	 &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>Allwinner SoCs are used in multiple hobbyist devboards and
-	single-board computers.  Recently, support for these SoCs
-	received many updates.</p>
-
-      <p>Theses tasks were completed during the second quarter of
-	2016:</p>
-
-      <ul>
-	<li>Switch to upstream DTS</li>
-
-	<li>A83T SoC support</li>
-
-	<li>H3 SoC support</li>
-
-	<li>Switch to the new clock framework</li>
-
-	<li>Convert the A10 interrupt controller to <tt>INTRNG</tt></li>
-
-	<li>OHCI support</li>
-
-	<li>A generic <tt>ALLWINNER</tt> kernel config file</li>
-
-	<li>A20/A31 NMI support</li>
-
-	<li>AXP209 PMU interrupts, GPIO, and sensors support</li>
-
-	<li>A83T thermal sensor support</li>
-
-	<li>RSB (Reduced Serial Bus) support</li>
-
-	<li>AXP813/AXP818 PMU support</li>
-
-	<li>A83T Security ID support</li>
-
-	<li>Support for the Allwinner Gigabit Ethernet controller found
-	  in H3/A83T/A64</li>
-
-	<li>USB OTG
-	  <a href="https://reviews.FreeBSD.org/D5881" shape="rect">(in review)</a></li>
-
-	<li>A10/A20 Security ID support
-	  <a href="https://reviews.FreeBSD.org/D6383" shape="rect">(in review)</a></li>
-
-	<li>A13 SoC Support
-	  <a href="https://reviews.FreeBSD.org/D6809" shape="rect">(in review)</a></li>
-      </ul>
-
-      <p>Ongoing work:</p>
-
-      <ul>
-	<li>A64 support</li>
-
-	<li>Use U-Boot EFI implementation for ARM32/ARM64</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>SPI driver</li><li>LCD Support</li><li>Any unsupported hardware device that might be of
-	interest.</li></ol><hr /><h2><a name="FreeBSD-on-Hyper-V-and-Azure" href="#FreeBSD-on-Hyper-V-and-Azure" id="FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/HyperV" title="https://wiki.FreeBSD.org/HyperV">FreeBSD Virtual Machines on Microsoft Hyper-V</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/HyperV" title="FreeBSD Virtual Machines on Microsoft Hyper-V">https://wiki.FreeBSD.org/HyperV</a></td></tr><tr><td><a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="https://technet.microsoft.com/en-us/library/dn531030.aspx">Supported Linux and FreeBSD virtual machines for Hyper-V on Windows</a></td><td>
-	    URL: <a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="Supported Linux and FreeBSD virtual machines for Hyper-V on Windows">https://technet.microsoft.com/en-us/library/dn531030.aspx</a></td></tr></table><p>
-	Contact:
-	  Sepherosa
-	  Ziehau
-	 &lt;<a href="mailto:sepherosa@gmail.com">sepherosa@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Hongjiang
-	  Zhang
-	 &lt;<a href="mailto:honzhan@microsoft.com">honzhan@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Dexuan
-	  Cui
-	 &lt;<a href="mailto:decui@microsoft.com">decui@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Kylie
-	  Liang
-	 &lt;<a href="mailto:kyliel@microsoft.com">kyliel@microsoft.com</a>&gt;
-	</p>
-      <p>During BSDCan 2016, Microsoft <a href="https://azure.microsoft.com/en-us/blog/freebsd-now-available-in-azure-marketplace/" shape="rect">announced</a>
-	the global availability of FreeBSD 10.3 images in Azure.
-	There are many FreeBSD-based Azure virtual appliances in the
-	Azure Marketplace, including Citrix Systems' NetScaler and
-	Netgate's pfSense.  Microsoft also made an in-depth technical
-	presentation to introduce how the performance of the Hyper-V
-	network device driver was optimized to reach full line rate on
-	10Gb networks and achieved decent performance on 40Gb
-	networks.  The slides and video from the presentation are
-	available from the <a href="http://www.bsdcan.org/2016/schedule/events/681.en.html" shape="rect">BSDCan website</a>.</p>
-
-      <p>Microsoft continues to strive to further optimize the
-	performance of Hyper-V network and storage device drivers.
-	Work is ongoing to replace the internal data structure in the
-	LRO kernel API from a singly-linked list to a double-linked
-	list, to speed up the LRO lookup by hash table, and to evaluate
-	the performance with <tt>tcp_lro_queue_mbuf()</tt>.</p>
-
-      <p>The handling of SCSI inquiry in the Hyper-V storage driver is
-	enhanced to make sure that disk hotplug and <tt>smartctl(8)</tt>
-	work reliably.  Refer to <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=210425" shape="rect">PR 210425</a>
-	and <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=209443" shape="rect">PR 209443</a>
-	for details.</p>
-
-      <p>BIS test cases are available on GitHub for <a href="https://github.com/FreeBSDonHyper-V/Test-BIS" shape="rect">Hyper-V</a>
-	and for <a href="https://github.com/FreeBSDonHyper-V/azure-freebsd-automation" shape="rect">Azure</a>.</p>
-    <p>This project was sponsored by Microsoft.</p><hr /><h2><a name="VIMAGE-Virtualized-Network-Stack-Update" href="#VIMAGE-Virtualized-Network-Stack-Update" id="VIMAGE-Virtualized-Network-Stack-Update">VIMAGE Virtualized Network Stack Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base/projects/vnet/" title="https://svnweb.FreeBSD.org/base/projects/vnet/">Project Workspace (Now Merged to Head).</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base/projects/vnet/" title="Project Workspace (Now Merged to Head).">https://svnweb.FreeBSD.org/base/projects/vnet/</a></td></tr></table><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>VIMAGE is a virtualization framework on top of FreeBSD jails
-	that was introduced to the kernel about eight years ago with
-	the <tt>vnet</tt> virtualized network stack.</p>
-
-      <p>Over the last few years, many people started to use VIMAGE
-	in production, production-like setups, and appliances.  This
-	adoption increased the urgency to finish the work to avoid
-	panics on network stack teardown and to avoid memory
-	leaks.</p>
-
-      <p>The <tt>vnet</tt> teardown has been changed to be from top to
-	bottom, trying to tear down layer by layer.  This is
-	preferable to removing interfaces first and then cleaning
-	everything up, as no more packets could flow once the
-	interfaces are gone.  Along with this
-	work, various paths with potential memory leaks were plugged.
-	Lastly, <tt>vnet</tt> support was added to formerly
-	unvirtualized components, such as the <tt>pf</tt> and
-	<tt>ipfilter</tt> firewalls and some virtual interfaces.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Please test FreeBSD 11.0-ALPHA6 or later.  When reporting
-	a problem, use the <tt>vimage</tt> keyword in the FreeBSD bug
-	tracker.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64" title="https://wiki.FreeBSD.org/arm64">FreeBSD/arm64 Wiki Entry</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/arm64" title="FreeBSD/arm64 Wiki Entry">https://wiki.FreeBSD.org/arm64</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <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 a concomittant increase of the
-	kernel virtual address space.  It also allows an increase in
-	the size of the physical memory FreeBSD can handle to up to
-	2TB.</p>
-
-      <p>The interrupt framework has been replaced with
-	<tt>intrng</tt> on <tt>arm64</tt>.  This allows both
-	<tt>arm</tt> and <tt>arm64</tt> to share interrupt controller
-	drivers, as is the case with the <tt>GICv2</tt> driver.  The
-	<tt>GICv3 ITS</tt> driver has been rewritten to better
-	integrate with <tt>intrng</tt>.</p>
-
-      <p>Busdma was updated to handle the cache.  The updated code
-	assumes that devices are non-coherent by default, unless the
-	device driver marks the DMA tag as coherent when creating it.
-	The generic and ThunderX PCIe drivers have been updated to
-	create coherent mappings when the device tree marks the
-	hardware as coherent.  This work also fixed issues found with
-	the sync operation where it was missing memory barriers.</p>
-
-      <p>A number of issues with <tt>hwpmc</tt> have been fixed.  This
-	improves the stability of <tt>hwpmc</tt> on <tt>arm64</tt>,
-	with no known software issues.  There is a single known issue
-	which seems to be hardware-related, however, further testing is
-	required.</p>
-
-      <p><tt>NEW_PCIB</tt> has been enabled on <tt>arm64</tt>.  This
-	includes handling the <tt>PCI_RES_BUS</tt> resource type.</p>
-
-      <p>Old interfaces replaced before FreeBSD-11 have been removed from the
-	<tt>arm64</tt> kernel and libraries.  This includes support
-	for compatibility with <tt>libc</tt> from releases prior to
-	11.0.  The <tt>brk</tt> and <tt>sbrk</tt> functions have also
-	been removed.  This allows a workaround for these functions in
-	the <tt>arm64</tt> C runtime to be removed.</p>
-
-      <p><tt>loader.efi</tt> has been updated to use an event timer to
-	implement its internal time function.  This is needed, as many
-	UEFI implementations do not handle the <tt>GetTime</tt>
-	runtime service method.  This means that <tt>loader.efi</tt> will
-	now correctly count down before automatically booting.</p>
-
-      <p>Initial support for the ARM Juno reference platform has been
-	added.  This hardware is common within ARM, and has been
-	useful for finding assumptions on cpuids.  Booting on the Juno
-	required fixing the kernel to remove the assumption that it is
-	booting from CPU zero.  This included assigning cpuids and
-	fixing assumptions within the <tt>GICv2</tt> driver that the
-	cpuid is the same as the <tt>GIC</tt> cpuid.  FreeBSD can now
-	boot on the 4 Cortex-A53 CPUs of the Juno board.
-	Further investigation is needed to track down why the boot
-	fails when the 2 Cortex-A57 CPUs are enabled.</p>
-
-      <p>Initial work has started on booting FreeBSD on the Pine64 and
-	Raspberry Pi 3 boards.  Both can boot to multiuser mode with
-	out-of-tree patches.  Further work is needed to bring these
-	patches into the tree, but it is expected this will happen
-	soon after the end of the code freeze.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, and ABT Systems Ltd.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="Reproducible-Builds-in-FreeBSD" href="#Reproducible-Builds-in-FreeBSD" id="Reproducible-Builds-in-FreeBSD">Reproducible Builds in FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/ReproducibleBuilds" title="https://wiki.FreeBSD.org/ReproducibleBuilds">Base System Reproducible Builds Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/ReproducibleBuilds" title="Base System Reproducible Builds Wiki Page">https://wiki.FreeBSD.org/ReproducibleBuilds</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/PortsReproducibleBuilds" title="https://wiki.FreeBSD.org/PortsReproducibleBuilds">Ports Reproducible Builds Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/PortsReproducibleBuilds" title="Ports Reproducible Builds Wiki Page">https://wiki.FreeBSD.org/PortsReproducibleBuilds</a></td></tr><tr><td><a href="http://www.bsdcan.org/2016/schedule/events/714.en.html" title="http://www.bsdcan.org/2016/schedule/events/714.en.html">BSDCan 2016 Reproducible Builds in FreeBSD talk</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2016/schedule/events/714.en.html" title="BSDCan 2016 Reproducible Builds in FreeBSD talk">http://www.bsdcan.org/2016/schedule/events/714.en.html</a></td></tr><tr><td><a href="https://reproducible-builds.org/" title="https://reproducible-builds.org/">Reproducible Builds Website</a></td><td>
-	    URL: <a href="https://reproducible-builds.org/" title="Reproducible Builds Website">https://reproducible-builds.org/</a></td></tr><tr><td><a href="https://diffoscope.org/" title="https://diffoscope.org/">Diffoscope Home Page</a></td><td>
-	    URL: <a href="https://diffoscope.org/" title="Diffoscope Home Page">https://diffoscope.org/</a></td></tr><tr><td><a href="https://people.FreeBSD.org/~emaste/reproducible-builds/iteration-1/diffoscope/" title="https://people.FreeBSD.org/~emaste/reproducible-builds/iteration-1/diffoscope/">Diffoscope Results from the BSDCan Reproducible Builds Talk</a></td><td>
-	    URL: <a href="https://people.FreeBSD.org/~emaste/reproducible-builds/iteration-1/diffoscope/" title="Diffoscope Results from the BSDCan Reproducible Builds Talk">https://people.FreeBSD.org/~emaste/reproducible-builds/iteration-1/diffoscope/</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>Reproducible builds are a set of software development
-	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
-	produces identical output.  The <a href="https://reproducible-builds.org/" shape="rect">reproducible-builds.org
-	  website</a>
-	provides background information and documentation on making
-	builds reproducible.</p>
-
-      <p>Many folks have contributed to the reproducible build effort
-	in FreeBSD src and ports over the last decade.  There are many
-	practical benefits of reproducible builds, such as bandwidth
-	and storage savings.  However, there is a growing interest in
-	the broad open source and free software communities,
-	primarily from a software and toolchain integrity perspective.
-	Over the last few years, some members of the Debian Project
-	have led a comprehensive and structured reproducible builds
-	effort.</p>
-
-      <p>Baptiste Daroussin and Ed Maste attended the first
-	Reproducible Builds Summit in Athens last year.  Since then,
-	Ed investigated the state of build reproducibility
-	in the ports tree, and presented
-	<i>Reproducible Builds in FreeBSD</i> at BSDCan 2016.  With
-	some work-in-progress patches, over 80% of the FreeBSD ports tree
-	builds reproducibly.</p>
-
-      <p>The Diffoscope tool performs in-depth comparison of files,
-	archives, or directories to understand why a binary artifact
-	does not build reproducibly.  Diffoscope results for the
-	nonreproducible builds in Ed's talk are available at one of
-	the links above.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Integrate FreeBSD ports builds into the
-	reproducible-builds.org continuous integration
-	infrastructure.</li><li>Integrate reproducible build patches into the ports
-	tree.</li><li>Investigate sources of nonreproducibility in individual
-	ports.</li></ol><hr /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Luca
-	  Pizzamiglio
-	 &lt;<a href="mailto:luca.pizzamiglio@gmail.com">luca.pizzamiglio@gmail.com</a>&gt;
-	</p>
-      <p>The <tt>devel/gdb</tt> port has been updated to GDB 7.11.1.</p>
-
-      <p>Support for system call catchpoints has been committed
-	upstream.  Support for examining ELF auxiliary vector data via
-	<tt>info auxv</tt> has been committed upstream.  Both features
-	will be included in GDB 7.12.</p>
-    <h3>Open tasks:</h3><ol><li>Figure out why the <tt>powerpc</tt> <tt>kgdb</tt> targets are not
-	able to unwind the stack past the initial frame.</li><li>Add support for more platforms, such as <tt>arm</tt>,
-	<tt>mips</tt>, and <tt>aarch64</tt>, to upstream <tt>gdb</tt> for both
-	userland and <tt>kgdb</tt>.</li><li>Add support for debugging <tt>powerpc</tt> vector
-	registers.</li><li>Add support for <tt>$_siginfo</tt>.</li><li>Implement <tt>info proc</tt> commands.</li><li>Implement <tt>info os</tt> commands.</li></ol><hr /><h2><a name="Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD" href="#Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD" id="Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD">Using lld, the LLVM Linker, to Link FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/LLD" title="https://wiki.FreeBSD.org/LLD">FreeBSD lld Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/LLD" title="FreeBSD lld Wiki Page">https://wiki.FreeBSD.org/LLD</a></td></tr><tr><td><a href="http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html" title="http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html">Status Report on Linking FreeBSD/amd64 With lld</a></td><td>
-	    URL: <a href="http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html" title="Status Report on Linking FreeBSD/amd64 With lld">http://lists.llvm.org/pipermail/llvm-dev/2016-March/096449.html</a></td></tr><tr><td><a href="http://www.bsdcan.org/2016/schedule/events/656.en.html" title="http://www.bsdcan.org/2016/schedule/events/656.en.html">BSDCan 2016 Talk on lld for FreeBSD</a></td><td>
-	    URL: <a href="http://www.bsdcan.org/2016/schedule/events/656.en.html" title="BSDCan 2016 Talk on lld for FreeBSD">http://www.bsdcan.org/2016/schedule/events/656.en.html</a></td></tr></table><p>
-	Contact:
-	  Rafael
-	  Esp�ndola
-	 &lt;<a href="mailto:rafael.espindola@gmail.com">rafael.espindola@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Davide
-	  Italiano
-	 &lt;<a href="mailto:dccitaliano@gmail.com">dccitaliano@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>lld</tt> is the linker in the LLVM family of projects.
-	It is intended to be a high-performance linker and supports
-	the <tt>ELF</tt>, <tt>COFF</tt>, and <tt>Mach-O</tt> object
-	formats.  Where possible, <tt>lld</tt> maintains command-line
-	and functional compatibility with the existing
-	<tt>GNU BFD ld</tt> and <tt>gold</tt> linkers.  However, the
-	authors of <tt>lld</tt> are not constrained by strict
-	compatibility where it would hamper performance or desired
-	functionality.</p>
-
-      <p>Over the last quarter, the <tt>lld</tt> project implemented
-	version script support sufficient to handle the FreeBSD base
-	system.  This is an important milestone on the path to having
-	<tt>lld</tt> as a viable system linker.</p>
-
-      <p><tt>lld</tt> still lacks comprehensive linker script
-	expression evaluation support, and therefore cannot yet be
-	used to link the FreeBSD kernel.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Develop linker script expression improvements in the
-	upstream <tt>lld</tt> project.</li><li>Import a newer <tt>lld</tt> snapshot into the vendor
-	area, add the build infrastructure, and connect it to the
-	world build, installed as <tt>ld.lld</tt>.</li><li>Request a ports exp-run with <tt>/usr/bin/ld</tt> a
-	symlink to <tt>ld.lld</tt>.</li><li>Extensive testing.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Bringing-GitLab-into-the-Ports-Collection" href="#Bringing-GitLab-into-the-Ports-Collection" id="Bringing-GitLab-into-the-Ports-Collection">Bringing GitLab into the Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freshports.org/www/gitlab" title="http://freshports.org/www/gitlab">GitLab Port</a></td><td>
-	    URL: <a href="http://freshports.org/www/gitlab" title="GitLab Port">http://freshports.org/www/gitlab</a></td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=208793" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=208793">PR: Not Starting on Boot</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=208793" title="PR: Not Starting on Boot">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=208793</a></td></tr></table><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:tz@FreeBSD.org">tz@FreeBSD.org</a>&gt;
-	</p>
-      <p>After being in the FreeBSD Ports Collection for three months,
-	GitLab continues to mature and gain adoption.  Most of its
-	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>
-
-      <p>Staying in sync with upstream is now easy for minor versions.
-	But, some of the monthly major releases create a big workload
-	by introducing a number of new dependencies.  This makes
-	testing and updating an expensive process.</p>
-
-      <p>The GitLab project itself now mentions native support on
-	FreeBSD, which is quite a commendation.</p>
-
-      <p>Current work aims to fix the open problems, get the latest
-	major version into the port, and create documentation for
-	the update progress.</p>
-    <hr /><h2><a name="GNOME-on-FreeBSD" href="#GNOME-on-FreeBSD" id="GNOME-on-FreeBSD">GNOME on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome" title="http://www.FreeBSD.org/gnome">FreeBSD GNOME Website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome" title="FreeBSD GNOME Website">http://www.FreeBSD.org/gnome</a></td></tr><tr><td><a href="https://github.com/FreeBSD/freebsd-ports-gnome" title="https://github.com/FreeBSD/freebsd-ports-gnome">Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/freebsd-ports-gnome" title="Development Repository">https://github.com/FreeBSD/freebsd-ports-gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD">Upstream Build Bot</a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="Upstream Build Bot">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html">USE_GNOME Porter's Handbook Chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="USE_GNOME Porter's Handbook Chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html</a></td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=210272" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=210272">GNOME/Gtk+ 3.20 Update Bug</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=210272" title="GNOME/Gtk+ 3.20 Update Bug">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=210272</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD GNOME Team maintains the GNOME, MATE, and CINNAMON
-	desktop environments and graphical user interfaces for FreeBSD.
-	GNOME 3 is part of the GNU Project.  MATE is a fork of the
-	GNOME 2 desktop.  CINNAMON is a desktop environment using
-	GNOME 3 technologies, but with a GNOME 2 look and feel.</p>
-
-      <p>GNOME 3.20 was ported with help from Ruslan Makhmatkhanov and
-	Gustau Perez.  Work is being done on updating GDM from the old
-	3.16 version to the 3.20 version.  For some reason, scrollbars
-	in Firefox are no longer working, though this has not been
-	investigated.</p>
-
-      <p>With Gtk+ 3.20, theme support was again changed, and the
-	changes are not backwards compatible.  If you have a theme
-	update that requires the new Gtk+ version, feel free to add it
-	as a blocker bug to the GNOME/Gtk+ 3.20 update bug.  This bug
-	will be used for the exp-run of GNOME 3.20, when it is ready,
-	and to track the theme-related ports.  Also, there is a
-	problem with the open and save dialog content going
-	invisible.</p>
-    <h3>Open tasks:</h3><ol><li>Finish GDM 3.20 porting.</li><li>Investigate why the scrollbars in Firefox are missing and
-	why the open/save dialog content is missing.</li></ol><hr /><h2><a name="Intel-Networking-Tools" href="#Intel-Networking-Tools" id="Intel-Networking-Tools">Intel Networking Tools</a></h2><p>
-	Contact:
-	  Sergey
-	  Kozlov
-	 &lt;<a href="mailto:sergey.kozlov@intel.com">sergey.kozlov@intel.com</a>&gt;
-	</p>
-      <p>Several tools for Intel(R) Ethernet networking products are
-	now available as ports and packages for FreeBSD:</p>
-
-      <ul>
-	<li><tt>sysutils/intel-nvmupdate</tt>: An application that is used
-	  to update non-volatile memory on XL710- and X710-based network
-	  devices.</li>
-
-	<li><tt>sysutils/intel-qcu</tt>: An application used to switch
-	  QSFP+ ports between 1x40Gbps and 4x10Gbps mode on XL710-based
-	  network devices.</li>
-
-	<li><tt>net/intel-ixl-kmod</tt>: An updated driver which enables
-	  the tools support on FreeBSD-10.x.</li>
-      </ul>
-    <p>This project was sponsored by Intel Corporation.</p><h3>Open tasks:</h3><ol><li>FreeBSD 11 support is under development and will be included in the
-	next release.</li></ol><hr /><h2><a name="IPv6-Promotion-Campaign" href="#IPv6-Promotion-Campaign" id="IPv6-Promotion-Campaign">IPv6 Promotion Campaign</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/IPv6PortsTODO" title="https://wiki.FreeBSD.org/IPv6PortsTODO">Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/IPv6PortsTODO" title="Wiki Page">https://wiki.FreeBSD.org/IPv6PortsTODO</a></td></tr></table><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:tz@FreeBSD.org">tz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Half a year ago, I started a promotion campaign to improve
-	support for fetching ports via IPv6.  Research performed in
-	December 2015 showed that 10,308 of 25,522 ports were not
-	fetchable when using IPv6-only, as these ports ignore the <a href="http://distcache.FreeBSD.org" shape="rect">FreeBSD.org <tt>pkg</tt> mirror</a>.</p>
-
-      <p>As a result of the campaign, the following servers now
-	successfully support IPv6:</p>
-
-      <ol>
-	<li><a href="http://mirror.amdmi3.ru" shape="rect">mirror.amdmi3.ru</a></li>
-
-	<li><a href="http://vault.centos.org" shape="rect">vault.centos.org</a></li>
-
-	<li><a href="http://mirror.centos.org" shape="rect">mirror.centos.org</a></li>
-
-	<li><a href="http://gstreamer.freedesktop.org" shape="rect">gstreamer.freedesktop.org</a></li>
-
-	<li><a href="http://people.FreeBSD.org" shape="rect">people.FreeBSD.org</a></li>
-      </ol>
-
-      <p>This enables 711 more ports to be fetched via IPv6.</p>
-
-      <p>I would like to thank Wolfgang Zenker, who is very active in
-	supporting the adoption of IPv6.  During the latest RIPE
-	meeting, he brought up the topic of non-support of IPv6
-	being a hindrance to business.  I am hopeful that his talk
-	changed some more minds and will help widen the support of
-	IPv6.</p>
-    <hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE on FreeBSD Website</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE on FreeBSD Website">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://freebsd.kde.org/area51.php" title="https://freebsd.kde.org/area51.php">KDE Ports Staging Area</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/area51.php" title="KDE Ports Staging Area">https://freebsd.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/KDE" title="https://wiki.FreeBSD.org/KDE">KDE on FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/KDE" title="KDE on FreeBSD Wiki">https://wiki.FreeBSD.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="https://mail.kde.org/mailman/listinfo/kde-freebsd">KDE/FreeBSD Mailing List</a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" title="KDE/FreeBSD Mailing List">https://mail.kde.org/mailman/listinfo/kde-freebsd</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/plasma5" title="http://src.mouf.net/area51/log/branches/plasma5">Development Repository for Integrating KDE 5</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/plasma5" title="Development Repository for Integrating KDE 5">http://src.mouf.net/area51/log/branches/plasma5</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/qt-5.6" title="http://src.mouf.net/area51/log/branches/qt-5.6">Development Repository for Integrating Qt 5.6</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/qt-5.6" title="Development Repository for Integrating Qt 5.6">http://src.mouf.net/area51/log/branches/qt-5.6</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/qt-5.7" title="http://src.mouf.net/area51/log/branches/qt-5.7">Development Repository for Integrating Qt 5.7</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/qt-5.7" title="Development Repository for Integrating Qt 5.7">http://src.mouf.net/area51/log/branches/qt-5.7</a></td></tr></table><p>
-	Contact: KDE on FreeBSD team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging and improving the
-	user experience of KDE and Qt on FreeBSD.</p>
-
-      <p>Many updates were committed to the ports tree this quarter,
-	and even more were committed to our experimental ports
-	repository.  Tobias Berner, Adriaan de Groot, and Ralf Nolden
-	were responsible for most of the work.</p>
-
-      <p>The following notable updates landed in the ports tree this
-	quarter:</p>
-
-      <ul>
-	<li>The CMake ports were updated to 3.5.1 and 3.5.2.</li>
-
-	<li>The DigiKam ports were updated to 4.14.0.</li>
-
-	<li>The KDevelop ports were updated to 4.7.3.</li>
-
-	<li>The <tt>devel/qbs</tt> port was added for Qt's future
-	  build system,
-	  <a href="https://wiki.qt.io/Qt_Build_Suite" shape="rect">QBS</a>.</li>
-
-	<li>Qt Creator was updated to 3.4.0, 3.5.0, 3.5.1, 3.6.0,
-	  4.0.0, 4.0.1, and 4.0.2.</li>
-
-	<li>A new port <tt>misc/qt5-examples</tt> was added for the
-	  project examples provided by Qt.  This makes Qt Creator more
-	  functional.</li>
-
-	<li>A new port <tt>misc/qt5-doc</tt> was added for Qt's API
-	  documentation, used by Qt Creator and other programs.</li>
-
-	<li>The base KDE4 ports were updated to 4.14.10.</li>
-      </ul>
-
-      <p>The following work occurred in our development
-	repository:</p>
-
-      <ul>
-	<li>Created ports for Qt 5.6.1-1
-	  (<tt>branches/qt-5.6</tt>).</li>
-
-	<li>Created ports for Qt 5.7.0
-	  (<tt>branches/qt-5.7</tt>).</li>
-
-	<li>The plasma5 branch is up-to-date with KDE's upstream and
-	  contains ports for Frameworks 5.24.0, Plasma Desktop 5.7.0,
-	  and Applications 16.04.2 (<tt>branches/plasma5</tt>).</li>
-      </ul>
-    <hr /><h2><a name="Obsoleting-Rails-3" href="#Obsoleting-Rails-3" id="Obsoleting-Rails-3">Obsoleting Rails 3</a></h2><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:tz@FreeBSD.org">tz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Ruby on Rails is the base for most of the rubygems in the
-	Ports Collection.  Currently, versions 3.2 and 4.2 coexist.
-	Since Rails 3.2 is running out of support, the time has
-	come to switch to 4.2.</p>
-
-      <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 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>
-
-      <p>To help with porting or testing, feel free to contact me or
-	the <tt>ruby@FreeBSD.org</tt> mailing list.</p>
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2016-07-2016-09.html b/website/content/en/status/report-2016-07-2016-09.html
deleted file mode 100644
index 7c459a4b4c..0000000000
--- a/website/content/en/status/report-2016-07-2016-09.html
+++ /dev/null
@@ -1,1853 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>As focused as we are on the present and what is happening
-      now, it is sometimes useful to take a fresh look at where we have
-      come from, and where we are going.  This quarter, we had our
-      newest doc committer working to trace through the tangled
-      history of many utilities, and we also get a glimpse looking
-      forward at what may come in FreeBSD 12.</p><p>Though 11.0-RELEASE was not finalized until after the period
-      covered in this report, we can still have some anticipatory
-      excitement for the features that will be coming in 12.0.  The
-      possibilities are tantalizing: a base system with no GPL
-      components, arm64 as a Tier-1 architecture, capsicum protection
-      for common utilities, and the CloudABI for custom software are
-      just a few.</p><p>The work of the present is no less exciting, with 11.0
-      making its way out just after the end of Q3, the new core
-      coming into its own, and much more that you'll have to read
-      and find out.</p><p>&#8212;Benjamin Kaduk</p><p><hr /></p><p>Please submit status reports for the fourth quarter of 2016
-      by January 7.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Capsicum-Update">Capsicum Update</a></li><li><a href="#ClonOS:-New-FreeBSD-Based-Free/Open-Hosting-Platform">ClonOS: New FreeBSD-Based Free/Open Hosting Platform</a></li><li><a href="#CloudABI:-Running-Untrusted-Programs-Directly-on-top-of-FreeBSD">CloudABI: Running Untrusted Programs Directly on top of
-      FreeBSD</a></li><li><a href="#Improvements-to-Non-Transparent-Bridge-Subsystem">Improvements to Non-Transparent Bridge Subsystem</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD">Using lld, the LLVM Linker, to Link FreeBSD</a></li><li><a href="#VirtualBox-Shared-Folders-Filesystem">VirtualBox Shared Folders Filesystem</a></li><li><a href="#ZFS-Code-Sync-with-Latest-OpenZFS/Illumos">ZFS Code Sync with Latest OpenZFS/Illumos</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#evdev-Support">evdev Support</a></li><li><a href="#FreeBSD-Driver-for-the-Annapurna-Labs-ENA">FreeBSD Driver for the Annapurna Labs ENA</a></li><li><a href="#FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></li><li><a href="#Timekeeping-Code-Improvements">Timekeeping Code Improvements</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Google-Summer-of-Code-2016">Google Summer of Code 2016</a></li><li><a href="#Non-BSM-to-BSM-Conversion-Tools">Non-BSM to BSM Conversion Tools</a></li><li><a href="#ptnet-Driver-and-bhyve-Device-Model">ptnet Driver and bhyve Device
-      Model</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Annapurna-Labs-Alpine">FreeBSD on Annapurna Labs Alpine</a></li><li><a href="#FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#UEFI-Runtime-Services">UEFI Runtime Services</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#LXQt-on-FreeBSD">LXQt on FreeBSD</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Documenting-the-History-of-Utilities-in-/bin-and-/sbin">Documenting the History of Utilities in /bin and
-      /sbin</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/releases/11.0R/schedule.html" title="https://www.FreeBSD.org/releases/11.0R/schedule.html">FreeBSD�11.0-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/11.0R/schedule.html" title="FreeBSD�11.0-RELEASE schedule">https://www.FreeBSD.org/releases/11.0R/schedule.html</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD Release Engineering Team continued the 11.0-RELEASE
-	cycle which was planned to be released in September, but as a
-	result of several last-minute issues, the final release
-	announcement was delayed.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">FreeBSD Ports Website</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="FreeBSD Ports Website">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">How to Contribute</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="How to Contribute">https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">Ports Monitoring Website</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="Ports Monitoring Website">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/portmgr/index.html" title="https://www.FreeBSD.org/portmgr/index.html">Ports Management Team Website</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/portmgr/index.html" title="Ports Management Team Website">https://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/FreeBSD_portmgr/" title="https://twitter.com/FreeBSD_portmgr/">Ports Management Team on Twitter</a></td><td>
-	    URL: <a href="https://twitter.com/FreeBSD_portmgr/" title="Ports Management Team on Twitter">https://twitter.com/FreeBSD_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">Ports Management Team on Facebook</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">Ports Management Team on Google+</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Ports Tree currently contains over 26,300 ports, with the
-	PR count around 2,150.  Of these PRs, 516 are unassigned.  The
-	last quarter saw 5,295 commits by 117 active committers.
-	Compared to the preceding quarter, there is both a slight
-	increase in the number of PRs and the number of unassigned
-	PRs, and a slight decrease in the number of committers.</p>
-
-      <p>In the last quarter, four commits bits were taken in for safe
-	keeping: erwin, miwi, and sem left by their own request and
-	jase was inactive for more than 18 months.  We welcomed two
-	new committers: Tobias Berner (tcberner) and Joseph Mingrone
-	(jrm).</p>
-
-      <p>On the management side, erwin and miwi left portmgr.  bapt
-	also left portmgr but is still the liaison for core.</p>
-
-      <p>On the infrastructure side, three new USES (grantlee, kde,
-	linux) and one new Keyword (javavm) were introduced.  The
-	default version of the Linux ports is now CentOS 6, with the
-	Fedora 10 ports scheduled for removal at the end of the year.
-	The license framework has been extended with a NONE license to
-	indicate that a port has no clearly defined licensing terms.
-	For those ports, no packages or distribution files are
-	distributed.  Also, support for the complete set of Creative
-	Commons licenses has been added.</p>
-
-      <p>Some major user-visible ports were updated: Firefox to 49.0
-	and Firefox Extended Service Release to 45.4.0; Chromium to
-	52.0.2743.116; the default version of <tt>gcc</tt> to 4.8.5;
-	and <tt>pkg</tt> itself to 1.8.7.</p>
-
-      <p>Behind the scenes, antoine ran 24 exp-runs to validate
-	various package updates, framework changes, and changes to the
-	base system.  bdrewery added two new package building
-	machines, supervised the package builds for 11.0-RELEASE, and
-	added support for building arm64 packages.</p>
-
-      <p>At EuroBSDcon, rene visited a presentation by Landry Breuil
-	&lt;landry@openbsd.org&gt; explaining how packages are built
-	in the OpenBSD world and explaining various design
-	decisions.</p>
-    <h3>Open tasks:</h3><ol><li>If you have some spare time, please take up a PR for
-	testing and committing.</li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The third quarter started with the handover to the ninth Core
-	team as it took office.  With four members returning from the
-	previous core (Baptiste Daroussin, Ed Maste, George
-	Neville-Neil and Hiroki Sato), one returning member after a
-	term away (John Baldwin), and four members new to core (Allan
-	Jude, Kris Moore, Benedict Reuschling and Benno Rice), the new
-	core team represents just about the ideal balance between
-	experience and fresh blood.</p>
-
-      <p>Beyond handing over all of the ongoing business, reviewing
-	everything on Core's agenda, and other routine changeover
-	activities, the first action of the new core was to respond to
-	a query from Craig Rodrigues concerning how hardware supplied
-	to the project through donations to the FreeBSD Foundation was
-	being used.</p>
-
-      <p>The Foundation does keep records of what hardware has been
-	supplied over time and has some idea of the original purpose
-	that hardware was provisioned for, but does not track the
-	current usage of the project's hardware assets.  Cluster
-	administration keeps their own configuration database, but
-	this is not suitable for general publication and covers much
-	more than Foundation supplied equipment.  After some
-	discussion it was decided that updated information about the
-	current disposition of Foundation supplied equipment should be
-	incorporated in the Foundation's annual report.</p>
-
-      <p>Ensuring that all of the FreeBSD code base is supplied under
-	open and unencumbered licensing terms and that we do not
-	infringe on patent terms or otherwise act counter to any legal
-	requirements are some of Core's primary concerns.  During this
-	quarter, there were three items of this nature.</p>
-
-      <ul>
-	<li>Importing Concurrency Kit.  In consultation with the
-	  Foundation's legal counsel, it was determined that
-	  importing selected parts of concurrency kit is acceptable,
-	  and has been approved.</li>
-
-	<li>The proposal to create a shadow GPLv3 toolchain repository
-	  was put to the community.  Ultimately the whole idea has
-	  been rendered largely redundant by faster than anticipated
-	  progress on the external toolchain ports and packages for
-	  those architectures where LLVM is not yet sufficiently
-	  mature.</li>
-
-	<li>Concerns were raised about handling GPL code in work in
-	  progress on the linuxkpi shim. This issue is not related to
-	  the FreeBSD svn repository but Core would like to stress
-	  that care must be taken to avoid license infringement and
-	  plans to write a set of guidelines for handling GPL
-	  code.</li>
-      </ul>
-
-      <p>The item that has absorbed the largest portion of Core's
-	attention this quarter concerns the project's handling of
-	security vulnerabilities in <tt>bspatch(1)</tt>,
-	<tt>libarchive(3)</tt>,
-	<tt>freebsd-update(8)</tt> and <tt>portsnap(8)</tt>.
-	A partial fix was applied
-	in FreeBSD-SA-16:25.bspatch but this lacks fixes to <tt>libarchive</tt>
-	code that were not yet available from upstream.</p>
-
-      <p>SecTeam receives privileged early reports of many
-	vulnerabilities and consequently has a strict policy of not
-	commenting publicly until an advisory and patches have been
-	published.  Early access to information about vulnerabilities
-	is contingent on their ability to avoid premature disclosure,
-	and without such, they could not have security advisories and
-	patches ready to go immediately when a vulnerability is
-	published.</p>
-
-      <p>However, in this case, vulnerabilities were already public
-	and the lack of any official response from the FreeBSD Project
-	was leading to concern amongst users and some critical press
-	coverage.  Core stepped in and published a statement
-	clarifying the situation and the particular difficulties
-	involved in securely modifying the mechanisms used to deliver
-	security patches.  Core believes that prompt notification and
-	discussion of the implications and possible workarounds to any
-	<i>public</i> vulnerability should not wait on the
-	availability of formal OS patches.</p>
-
-      <p>The OpenSSH project has deprecated DSA keys upstream.  FreeBSD
-	had kept DSA keys enabled in the later 10.x releases for
-	compatibility reasons, but with the release of 11.0 the time
-	has come to synchronize again with upstream.  Since there are
-	numerous DSA keys in use in the FreeBSD cluster, this
-	necessitated an exercise to get replacement keys installed.
-	Core would like to thank David Wolfskill and the accounts team
-	for handling the surge in key changes with a great deal of
-	aplomb.</p>
-
-      <p>During this quarter we welcomed Michael Zhilin, Imre Vadasz,
-	Steve Kiernan and Toomas Soome as new source committers.  Over
-	the same period, we said farewell to Martin Wilke and Erwin
-	Lansing who have handed in their commit bits.  We wish them
-	well in their future endeavours and hope to see them return as
-	soon as they can.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSDFoundation.org/" title="https://www.FreeBSDFoundation.org/">FreeBSD Foundation Website</a></td><td>
-	    URL: <a href="https://www.FreeBSDFoundation.org/" title="FreeBSD Foundation Website">https://www.FreeBSDFoundation.org/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Funding comes from individual and
-	corporate donations and is used to fund and manage software
-	development projects, conferences and developer summits, and
-	provide travel grants to FreeBSD contributors.  The Foundation
-	purchases hardware to improve and maintain FreeBSD infrastructure
-	and publishes FreeBSD white papers and marketing material to
-	promote, educate, and advocate for the FreeBSD Project.  The
-	Foundation also represents the FreeBSD Project in executing
-	contracts, license agreements, and other legal arrangements
-	that require a recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD last
-	quarter:</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>Our work is 100% funded by your donations.  Our spending
-	budget for 2016 is $1,250,000 and we have raised $271,500 so
-	far.  Our Q1-Q3 financial reports will be posted in early
-	November.  As you can see, we need your donations to
-	continue supporting FreeBSD at our current level.  Please
-	consider making a donation at <a href="https://www.FreeBSDFoundation.org/donate/" shape="rect">https://www.FreeBSDFoundation.org/donate/</a>.</p>
-
-      <p>OS Improvements</p>
-
-      <p>The Foundation improves FreeBSD by funding software development
-	projects approved through our proposal submission process, and
-	our internal software developer staff members.  Two
-	Foundation-funded projects continued last quarter: one project
-	is to port NetBSD's <tt>blacklistd</tt> daemon and related
-	elements to FreeBSD, and the second is phase two of the
-	FreeBSD/arm64 port.</p>
-
-      <p>Foundation staff members were responsible for many changes
-	over the quarter.  Kostik Belousov accomplished this
-	work last quarter:</p>
-
-      <ul>
-	<li>Provided kernel support for EFI Runtime Services
-	  calls</li>
-
-	<li>Implemented <tt>gettimeofday(2)</tt> purely in userspace
-	  for HPET timers</li>
-
-	<li>Implemented <tt>fdatasync(2)</tt></li>
-
-	<li>Improved the locking of the time keeping code</li>
-
-	<li>Made the sleepqueue code immune to rapid callout
-	  changes</li>
-
-	<li>Made many stability fixes, the most important of which
-	  were UFS issues and an i386 bug</li>
-
-	<li>Improved the process management and ptrace code</li>
-      </ul>
-
-      <p>Ed Maste, our Project Development Director, accomplished this
-	work last quarter:</p>
-
-      <ul>
-	<li>Worked on FreeBSD/arm64 issues and Cavium ThunderX
-	  deployment (including RMAs)</li>
-
-	<li>Worked with upstream developers to test works in progress
-	  and prepare LLD as the replacement linker in the FreeBSD base
-	  system</li>
-
-	<li>Switched to using LLVM's <tt>libunwind</tt> in the base
-	  system</li>
-
-	<li>Improved the reproducibility of builds in the FreeBSD base
-	  system and ports</li>
-
-	<li>Reviewed the <tt>blacklistd</tt> work that is in
-	  progress</li>
-
-	<li>Attended BSDCam 2016, with a primary focus on toolchain
-	  discussions</li>
-
-	<li>Participated in ongoing Capsicum calls, and helped with
-	  the Capsicumization of several base system utilities</li>
-
-	<li>Fixed a number of ELF Tool Chain issues, and integrated a
-	  new upstream version into the FreeBSD base system</li>
-
-	<li>Hosted biweekly graphics calls to coordinate work in
-	  progress by funded and volunteer developers</li>
-
-	<li>Implemented fixes for security issues in some FreeBSD update
-	  tools, and coordinated their integration into the stable and
-	  release branches</li>
-      </ul>
-
-      <p>George Neville-Neil continued hosting a bi-weekly Transport
-	conference call (notes at <a href="https://wiki.FreeBSD.org/TransportProtocols" shape="rect">https://wiki.FreeBSD.org/TransportProtocols</a>)
-	and the bi-weekly DTrace conference call (notes at <a href="https://wiki.FreeBSD.org/DTrace" shape="rect">https://wiki.FreeBSD.org/DTrace</a>).</p>
-
-      <p>Release Engineering</p>
-
-      <p>Foundation staff member Glen Barber  worked with the Release
-	Engineering team to continue finalizing the 11.0-RELEASE
-	cycle, which was delayed to address several last-minute
-	issues.</p>
-
-      <p>As part of the Cluster Administration team, Glen worked with
-	the amazing on-site staff at NYI to rack and install two
-	Cavium ThunderX machines, one of which is used for native
-	package builds for the FreeBSD/arm64 architecture, and the
-	other of which is targeted to be used as a reference machine
-	in the FreeBSD infrastructure.</p>
-
-      <p>Getting Started with FreeBSD Project</p>
-
-      <p>We hired a summer intern, with no experience on FreeBSD, Linux,
-	or any command-line operating system, to figure out on his own
-	how to install and use FreeBSD.  He wrote easy-to-follow how-to
-	guides to help make the new-user experience straightforward
-	and positive.  He submitted bug reports and reported issues
-	through the appropriate channels, and worked with Glen Barber
-	and Brad Davis to improve the new user information on
-	FreeBSD.org to make it easier for new people to get started
-	with FreeBSD.  You can find his how-to guides at <a href="https://www.FreeBSDFoundation.org/FreeBSD/how-to-guides/" shape="rect">https://www.FreeBSDFoundation.org/FreeBSD/how-to-guides/</a>
-	and check out his interview on BSDNow at <a href="http://www.bsdnow.tv/episodes/2016_08_24-the_fresh_bsd_experience" shape="rect">http://www.bsdnow.tv/episodes/2016_08_24-the_fresh_bsd_experience</a>.</p>
-
-      <p>Supporting FreeBSD Infrastructure</p>
-
-      <p>We provide hardware and support for FreeBSD infrastructure.
-	Last quarter we purchased and brought up two 48-core Cavium
-	ThunderX machines to build FreeBSD package sets for the arm64
-	platform.  We also purchased more servers to help with
-	continuous integration efforts.</p>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating for
-	the Project.  This includes promoting work being done by
-	others using FreeBSD, producing advocacy literature to teach
-	people about FreeBSD and ease the path to starting out with FreeBSD,
-	contributing to the Project, and attending and getting other
-	FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD
-	tables, and give FreeBSD presentations.</p>
-
-      <p>We created new handouts to promote TeachBSD.org (<a href="https://www.FreeBSDFoundation.org/wp-content/uploads/2016/08/TeachBSD_half_final.pdf" shape="rect">https://www.FreeBSDFoundation.org/wp-content/uploads/2016/08/TeachBSD_half_final.pdf</a>)
-	and the Google Summer of Code program (<a href="https://www.FreeBSDFoundation.org/wp-content/uploads/2016/08/GSOC-flyerv2.pdf" shape="rect">https://www.FreeBSDFoundation.org/wp-content/uploads/2016/08/GSOC-flyerv2.pdf</a>).</p>
-
-      <p>We published the July/August issue of the FreeBSD Journal: <a href="https://www.FreeBSDFoundation.org/past-issues/FreeBSD-and-rtems/" shape="rect">https://www.FreeBSDFoundation.org/past-issues/FreeBSD-and-rtems/</a>.</p>
-
-      <p>We also published monthly newsletters to highlight work being
-	done to support FreeBSD, tell you about upcoming events, and
-	provide other information to keep you in the loop of what we are doing
-	to support the FreeBSD Project and community: <a href="https://www.FreeBSDFoundation.org/news-and-events/newsletter/" shape="rect">https://www.FreeBSDFoundation.org/news-and-events/newsletter/</a>.</p>
-
-      <p>Conferences and Events</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events, and
-	summits around the globe.  These events can be BSD-related,
-	open source, or technology events geared towards
-	underrepresented groups.</p>
-
-      <p>We support the FreeBSD-focused events to help provide a venue
-	for sharing knowledge, to work together on projects, and
-	facilitate collaboration between developers and commercial
-	users.  This all helps provide a healthy ecosystem.  We
-	support the non-FreeBSD events to promote and raise awareness
-	about FreeBSD, to increase the use of FreeBSD in different
-	applications, and to recruit more contributors to the
-	Project.</p>
-
-      <p>This quarter, we sponsored and/or attended the following
-	events:</p>
-
-      <ul>
-	<li>Texas Linux Fest, July 8-9, 2016, Austin, TX
-	  (<a href="http://2016.texaslinuxfest.org/" shape="rect">http://2016.texaslinuxfest.org/</a>)</li>
-
-	<li>The Eleventh HOPE, July 22-24, 2016, New York, NY
-	  (<a href="https://hope.net/index.html" shape="rect">https://hope.net/index.html</a>)</li>
-
-	<li>BSDCam 2016, August 15-17, 2016, Cambridge, UK (sponsor,
-	  organizer, and participated) (<a href="https://wiki.FreeBSD.org/DevSummit/201608" shape="rect">https://wiki.FreeBSD.org/DevSummit/201608</a>)</li>
-
-	<li>FOSSCON 2016, August 20, 2016, Philadelphia, PA
-	  (<a href="https://fosscon.us/" shape="rect">https://fosscon.us/</a>)</li>
-
-	<li>womENcourage 2016, September 12-13, 2016, Linz, Austria
-	  (Silver Sponsor) (<a href="http://womencourage.acm.org" shape="rect">http://womencourage.acm.org</a>)</li>
-
-	<li>SNIA Storage Developer Conference 2016, September 19-22,
-	  2016, Santa Clara, CA (Industry Partner Sponsor) (<a href="http://www.snia.org/events/storage-developer" shape="rect">http://www.snia.org/events/storage-developer</a>)</li>
-
-	<li><p>EuroBSDcon 2016 and FreeBSD Developer Summit, September
-	  22-25, 2016, Belgrade, Serbia (Silver Sponsor) (<a href="https://2016.eurobsdcon.org/" shape="rect">https://2016.eurobsdcon.org/</a>)</p>
-
-	  <p>Our EuroBSDcon involvement included:</p>
-
-	  <ul>
-	    <li>Held a Women in Tech BoF in partnership with ACM-W
-	      Europe</li>
-
-	    <li>Benedict organized the EuroBSDcon Developer
-	    Summit</li>
-
-	    <li>Deb gave a Foundation Update talk and Hiroki Sato and
-	      Benedict Reuschling joined her for a Q&amp;A
-	      session.</li>
-
-	    <li>Kirk McKusick taught his two-day FreeBSD tutorial (<a href="https://2016.eurobsdcon.org/speakers/#kirkmckusick" shape="rect">https://2016.eurobsdcon.org/speakers/#kirkmckusick</a>)</li>
-
-	    <li>George Neville-Neil taught a tutorial on Tracing FreeBSD
-	      for DevOps and Developers (<a href="https://2016.eurobsdcon.org/speakers/#georgenevilleneil" shape="rect">https://2016.eurobsdcon.org/speakers/#georgenevilleneil</a>)</li>
-
-	    <li>George also gave the Keynote talk, titled The Coming
-	      Decades of BSD</li>
-
-	    <li>Phillip Paeps was one of the primary organizers for
-	      this conference.</li>
-	  </ul>
-	</li>
-
-	<li><p>OpenZFS Developer Summit 2016, September 26-27, 2016,
-	  San Francisco, CA (Silver) (<a href="http://open-zfs.org/wiki/OpenZFS_Developer_Summit" shape="rect">http://open-zfs.org/wiki/OpenZFS_Developer_Summit</a>)</p>
-
-	  <ul>
-	    <li>Justin Gibbs gave a talk on Fault Management (<a href="http://open-zfs.org/wiki/Fault_Management" shape="rect">http://open-zfs.org/wiki/Fault_Management</a>)</li>
-	  </ul>
-	</li>
-      </ul>
-
-      <p>We sponsored three FreeBSD contributors to attend
-	EuroBSDcon.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them.  We continued to review
-	requests and grant permission to use the trademarks.</p>
-
-      <p>FreeBSD Community Engagement</p>
-
-      <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>
-
-      <p>Other Stuff We Did</p>
-
-      <p>We welcomed Kylie Liang and Philip Paeps to the Board of
-	Directors.  More information and interviews can be found at:
-	<a href="https://www.FreeBSDFoundation.org/blog/FreeBSD-foundation-welcomes-new-board-members/" shape="rect">https://www.FreeBSDFoundation.org/blog/FreeBSD-foundation-welcomes-new-board-members/</a>.</p>
-
-      <p>George attended the ARM Partner Meeting in Cambridge.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Capsicum-Update" href="#Capsicum-Update" id="Capsicum-Update">Capsicum Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Capsicum" title="https://wiki.FreeBSD.org/Capsicum">Capsicum Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Capsicum" title="Capsicum Wiki Page">https://wiki.FreeBSD.org/Capsicum</a></td></tr></table><p>
-	Contact:
-	  Allan
-	  Jude
-	 &lt;<a href="mailto:allanjude@FreeBSD.org">allanjude@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Conrad
-	  Meyer
-	 &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mariusz
-	  Zaborski
-	 &lt;<a href="mailto:oshogbo@FreeBSD.org">oshogbo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Several developers have undertaken a recent effort to
-	sandbox additional applications in the base system.  This work
-	is proceeding nicely and one of the goals is to target basic
-	utilities used in security sensitive applications, like
-	<tt>freebsd-update</tt> and <tt>portsnap</tt>.</p>
-
-      <p>This work highlighted two longstanding challenges in
-	applying Capsicum.  First, there are a number of common
-	constructs shared by many simple programs, such as limiting
-	capability rights on the stdio file descriptors.  To address
-	this, a set of capsicum helper routines has been added for
-	these common cases.</p>
-
-      <p>Second, a common challenge occurs where applications need
-	to open an arbitrarily large number of files, possibly from
-	various directories, where preopening the file descriptors may
-	not be suitable.  Several possible solutions for this are in
-	discussion.</p>
-
-      <p>Recently Capsicumized utilities include:</p>
-
-      <ul>
-	<li><tt>bspatch</tt></li>
-
-	<li><tt>cmp</tt></li>
-
-	<li><tt>ident</tt></li>
-
-	<li><tt>primes</tt></li>
-
-	<li><tt>tee</tt></li>
-
-	<li><tt>tr</tt></li>
-
-	<li><tt>write</tt></li>
-      </ul>
-
-      <p>Additional Capsicum changes are in review:</p>
-
-      <ul>
-	<li><tt>b64decode</tt>, <tt>b64encode</tt>,
-	  <tt>uudecode</tt>, <tt>uuencode</tt></li>
-
-	<li><tt>brandelf</tt></li>
-
-	<li><tt>dma-mbox-create</tt></li>
-
-	<li><tt>elf2aout</tt></li>
-
-	<li><tt>file</tt></li>
-
-	<li><tt>head</tt></li>
-
-	<li><tt>hexdump</tt></li>
-
-	<li><tt>iconv</tt></li>
-
-	<li><tt>ident</tt></li>
-
-	<li><tt>jot</tt></li>
-
-	<li><tt>ktrdump</tt></li>
-
-	<li><tt>lam</tt></li>
-
-	<li><tt>last</tt></li>
-
-	<li><tt>ministat</tt></li>
-
-	<li><tt>praudit</tt></li>
-
-	<li><tt>strings</tt></li>
-      </ul>
-
-      <p>An additional syscall (<tt>getdtablesize</tt>) and
-	additional sysctls (<tt>kern.proc.nfds</tt>,
-	<tt>kern.hostname</tt>, etc.) are now permitted in capability
-	mode.  </p>
-
-      <p>Capability rights are now propagated to child descriptors on
-	accept(2).</p>
-
-      <p>Capsicum is now enabled in the 32-bit compatibility syscall
-	layer.</p>
-
-      <p>Per-process (<tt>procctl</tt>) and global (<tt>sysctl</tt>)
-	settings have been added to aid in debugging while
-	Capsicumizing existing applications.  When enabled, instead of
-	returning ENOTCAPABLE or ECAPMODE for a system call, the
-	kernel will issue a SIGTRAP to generate a core dump or enter
-	the debugger.  </p>
-    <p>This project was sponsored by Dell EMC Isilon, ScaleEngine Inc., and The FreeBSD Foundation.</p><hr /><h2><a name="ClonOS:-New-FreeBSD-Based-Free/Open-Hosting-Platform" href="#ClonOS:-New-FreeBSD-Based-Free/Open-Hosting-Platform" id="ClonOS:-New-FreeBSD-Based-Free/Open-Hosting-Platform">ClonOS: New FreeBSD-Based Free/Open Hosting Platform</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://clonos.tekroutine.com" title="http://clonos.tekroutine.com">ClonOS Homepage</a></td><td>
-	    URL: <a href="http://clonos.tekroutine.com" title="ClonOS Homepage">http://clonos.tekroutine.com</a></td></tr></table><p>
-	Contact:
-	  Oleg
-	  Ginzburg
-	 &lt;<a href="mailto:olevole@olevole.ru">olevole@olevole.ru</a>&gt;
-	</p>
-      <p>Currently, FreeBSD is well proven as a base for routers
-	(<strong>pfSense</strong>, <strong>OPNSense</strong>,
-	<strong>BSDRP</strong>) and NAS (<strong>FreeNAS</strong>,
-	<strong>zfsGuru</strong>, <strong>NAS4Free</strong>).
-	However, FreeBSD-based solutions are almost completely absent in
-	the virtualization area, and <strong>ClonOS</strong> is one of
-	the attempts to change that.</p>
-
-      <p>ClonOS is a new free open-source FreeBSD-based platform for
-	virtual environment creation and management.  In the core
-	platform are:</p>
-
-      <ul>
-	<li>FreeBSD as the host OS</li>
-
-	<li><a href="https://man.FreeBSD.org/bhyve/8" shape="rect">bhyve</a></li>
-
-	<li><a href="https://www.xenproject.org/" shape="rect">xen</a></li>
-
-	<li><a href="https://man.FreeBSD.org/vale/4" shape="rect">vale</a></li>
-
-	<li><a href="https://man.FreeBSD.org/jail/8" shape="rect">jail</a></li>
-
-	<li><a href="https://www.bsdstore.ru/" shape="rect">CBSD</a> (as a
-	  management tool)</li>
-
-	<li><a href="https://puppet.com/" shape="rect">puppet</a> (for
-	  configuration management)</li>
-
-	<li>additional features such as go-micro services (obtaining
-	  VMs, resizing disks, and so on)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>We would like to see ClonOS in real-world use.  In this
-	regard we are interested in finding more people and companies
-	that use FreeBSD in hosting tasks.  In addition, it could be
-	great to work with the developers of existing NAS solutions
-	(zfsGuru, NAS4Free).
-      </li></ol><hr /><h2><a name="CloudABI:-Running-Untrusted-Programs-Directly-on-top-of-FreeBSD" href="#CloudABI:-Running-Untrusted-Programs-Directly-on-top-of-FreeBSD" id="CloudABI:-Running-Untrusted-Programs-Directly-on-top-of-FreeBSD">CloudABI: Running Untrusted Programs Directly on top of
-      FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://nuxi.nl/" title="https://nuxi.nl/">Official CloudABI Website</a></td><td>
-	    URL: <a href="https://nuxi.nl/" title="Official CloudABI Website">https://nuxi.nl/</a></td></tr><tr><td><a href="https://nuxi.nl/cloudabi/freebsd/" title="https://nuxi.nl/cloudabi/freebsd/">Using CloudABI on FreeBSD</a></td><td>
-	    URL: <a href="https://nuxi.nl/cloudabi/freebsd/" title="Using CloudABI on FreeBSD">https://nuxi.nl/cloudabi/freebsd/</a></td></tr><tr><td><a href="https://nuxi.nl/blog/2016/08/01/cloudabi-python.html" title="https://nuxi.nl/blog/2016/08/01/cloudabi-python.html">Python for CloudABI</a></td><td>
-	    URL: <a href="https://nuxi.nl/blog/2016/08/01/cloudabi-python.html" title="Python for CloudABI">https://nuxi.nl/blog/2016/08/01/cloudabi-python.html</a></td></tr><tr><td><a href="https://github.com/NuxiNL" title="https://github.com/NuxiNL">CloudABI on GitHub</a></td><td>
-	    URL: <a href="https://github.com/NuxiNL" title="CloudABI on GitHub">https://github.com/NuxiNL</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	<br />
-	Contact: The CloudABI mailing list &lt;<a href="mailto:cloudabi-devel@googlegroups.com">cloudabi-devel@googlegroups.com</a>&gt;
-	</p>
-      <p>CloudABI is a compact UNIX-like runtime environment inspired
-	by FreeBSD's Capsicum security framework.  It allows you to
-	safely run potentially untrusted programs directly on top of
-	FreeBSD, Linux and macOS, without requiring the use of
-	virtualisation, jails, etc.  This makes it a useful building
-	block for cluster/cloud computing.</p>
-
-      <p>Over the last couple of months, several new libraries and
-	applications have been ported over to CloudABI, the most
-	important addition being Python 3.6.  This means that you can
-	now write strongly sandboxed apps in Python!</p>
-
-      <p>Support for different hardware platforms has also improved.
-	In addition to amd64 and arm64, we now support i686 and armv6.
-	The release of LLVM 3.9 was important to us, as it has
-	integrated all the necessary changes to support the first
-	three platforms.  Full armv6 support is still blocked on some
-	issues with LLVM's linker, LLD.</p>
-    <p>This project was sponsored by Nuxi, the Netherlands.</p><h3>Open tasks:</h3><ol><li>Play around with CloudABI and let us know what you think
-	of it!  Full support for amd64 and arm64 is part of FreeBSD 11.0.
-	i686 and armv6 support is only available on head, but will be
-	merged to the stable/11 branch in the future.</li><li>Interested in Python programming? Give our copy of Python
-	a try and share your experiences!</li><li>Do you maintain pieces of software that could benefit from
-	strong sandboxing?  Try building them using the CloudABI cross
-	compiler!</li></ol><hr /><h2><a name="Improvements-to-Non-Transparent-Bridge-Subsystem" href="#Improvements-to-Non-Transparent-Bridge-Subsystem" id="Improvements-to-Non-Transparent-Bridge-Subsystem">Improvements to Non-Transparent Bridge Subsystem</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	</p>
-      <p>Non-Transparent Bridges allow the creation of memory windows
-	between different systems using the regular PCIe links of CPUs
-	as a transport.  During the last quarter, the NTB subsystem
-	gained a significant set of improvements and fixes:</p>
-
-      <ul>
-	<li>The code was modularized, utilizing FreeBSD's NewBus
-	  interfaces to allow support for different hardware types
-	  with different drivers, support for multiple NTB instances
-	  in a system, using the <tt>ntb_transport</tt> module for
-	  consumers other than <tt>if_ntb</tt>, etc.</li>
-
-	<li>Support for splitting NTB resources between different
-	  applications was added, such as doing direct access to some
-	  range of remote memory and to a virtual network interface
-	  between nodes at the same time, etc.</li>
-
-	<li>The virtual network interface driver gained support for
-	  many modern features, such as multiple queues, new locking,
-	  etc.</li>
-
-	<li>NTB performance and SMP scalability was improved.</li>
-
-	<li>Multiple workarounds for hardware issues were added.</li>
-      </ul>
-
-      <p>The code is committed to the FreeBSD head, stable/11 and
-	stable/10 branches.</p>
-    <p>This project was sponsored by iXsystems, Inc.</p><h3>Open tasks:</h3><ol><li>Support for the next generation of Intel hardware.</li><li>Support for non-Intel hardware (AMD, PLX, etc.).</li><li>Support for I/OAT and other DMA offloads.</li><li>Creating a more efficient packet transport
-	protocol.</li><li>Creating a greater variety of NTB applications.</li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/FreeBSD-base-graphics" title="https://github.com/FreeBSDDesktop/FreeBSD-base-graphics">GitHub Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop/FreeBSD-base-graphics" title="GitHub Repository">https://github.com/FreeBSDDesktop/FreeBSD-base-graphics</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/Graphics" title="https://wiki.FreeBSD.org/Graphics">Graphics Stack Roadmap and Supported Hardware Matrix</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Graphics" title="Graphics Stack Roadmap and Supported Hardware Matrix">https://wiki.FreeBSD.org/Graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSD/FreeBSD-ports-graphics" title="https://github.com/FreeBSD/FreeBSD-ports-graphics">Ports Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/FreeBSD-ports-graphics" title="Ports Development Repository">https://github.com/FreeBSD/FreeBSD-ports-graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/FreeBSD-base-graphics/tree/drm-next-4.7" title="https://github.com/FreeBSDDesktop/FreeBSD-base-graphics/tree/drm-next-4.7">DRM 4.7 Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop/FreeBSD-base-graphics/tree/drm-next-4.7" title="DRM 4.7 Development Repository">https://github.com/FreeBSDDesktop/FreeBSD-base-graphics/tree/drm-next-4.7</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/action/recall/SummerOfCodeIdeas?action=recall&amp;rev=67#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes" title="https://wiki.FreeBSD.org/action/recall/SummerOfCodeIdeas?action=recall&amp;rev=67#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes">GSoC 2016: Link /dev Entries to Sysctl Nodes</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/action/recall/SummerOfCodeIdeas?action=recall&amp;rev=67#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes" title="GSoC 2016: Link /dev Entries to Sysctl Nodes">https://wiki.FreeBSD.org/action/recall/SummerOfCodeIdeas?action=recall&amp;rev=67#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq" title="https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq">GSoC 2016: Redesign libdevq</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq" title="GSoC 2016: Redesign libdevq">https://wiki.FreeBSD.org/SummerOfCode2016/RethinkLibdevq</a></td></tr><tr><td><a href="https://github.com/yohanesu75/FreeBSD-base-graphics/wiki/Wayland-on-FreeBSD" title="https://github.com/yohanesu75/FreeBSD-base-graphics/wiki/Wayland-on-FreeBSD">Wayland Notes</a></td><td>
-	    URL: <a href="https://github.com/yohanesu75/FreeBSD-base-graphics/wiki/Wayland-on-FreeBSD" title="Wayland Notes">https://github.com/yohanesu75/FreeBSD-base-graphics/wiki/Wayland-on-FreeBSD</a></td></tr><tr><td><a href="https://planet.FreeBSD.org/graphics" title="https://planet.FreeBSD.org/graphics">Graphics Team Blog</a></td><td>
-	    URL: <a href="https://planet.FreeBSD.org/graphics" title="Graphics Team Blog">https://planet.FreeBSD.org/graphics</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Matthew
-	  Macy
-	 &lt;<a href="mailto:mmacy@nextbsd.org">mmacy@nextbsd.org</a>&gt;
-	<br />
-	Contact:
-	  Johannes
-	  Lundberg
-	 &lt;<a href="mailto:yohanesu75@me.com">yohanesu75@me.com</a>&gt;
-	</p>
-      <p>We are sad to report that both GSoc projects failed.  The
-	<tt>libdevq</tt> project was abandoned as the student
-	disappeared.  The kernel project was incomplete because the
-	student could not work for personal reasons.  He plans to
-	resume work and complete the task, even though GSoC 2016 is
-	finished.</p>
-
-      <p>X.org server version 1.18.4 and updates for
-	the <tt>xf86-video-ati</tt> and <tt>xf86-video-intel</tt> DDX
-	drivers are ready for wider testing.  A CFT will be sent out
-	shortly.  These updates are required to use newer DRM
-	versions.</p>
-
-      <p>The missing functionality from <tt>libdrm</tt> that is
-	needed by the <tt>amdgpu</tt> driver has been added.  These
-	changes will be committed to the ports tree shortly after the
-	xorg-server update.</p>
-
-      <p>DRM from Linux 4.8 was ported to the <tt>drm-next</tt>
-	branch.  This branch should be used for <tt>radeon</tt> and
-	<tt>amdgpu</tt> cards.  The <tt>drm-next-4.7</tt> branch
-	should be used for <tt>i915</tt> cards due to instabilities
-	in the <tt>intel</tt> driver in the <tt>drm-next</tt> branch.</p>
-
-      <p>Johannes Lundberg has been working on getting the Wayland
-	environment running on FreeBSD.  The Wayland ports are in
-	a working state except for the Weston compositor.</p>
-
-      <p>The current Weston port (from DragonFlyBSD) might be
-	scrapped and a new port created from scratch based on the
-	upstream source code.  With the use of <tt>libinput</tt>,
-	<tt>libudev-devd</tt>, and <tt>epoll-shim</tt>, the diff will
-	not be very large and will be easier to maintain.</p>
-
-      <p>Patches for <tt>wlc</tt> (another Wayland compositor) are
-	being pushed upstream.  On the TODO list is refactoring the
-	tty code into selectable backends (linux, FreeBSD, etc), as
-	recommended by the author of <tt>wlc</tt>.  For now, it is
-	running on FreeBSD with patches in the ports tree.</p>
-    <hr /><h2><a name="Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD" href="#Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD" id="Using-lld,-the-LLVM-Linker,-to-Link-FreeBSD">Using lld, the LLVM Linker, to Link FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/LLD" title="https://wiki.FreeBSD.org/LLD">LLD Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/LLD" title="LLD Wiki Page">https://wiki.FreeBSD.org/LLD</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>lld</tt> is the linker in the LLVM family of projects.
-	It is a high-performance linker that supports the ELF, COFF,
-	and Mach-O object formats.  Where possible, <tt>lld</tt>
-	maintains command-line and functional compatibility with the
-	existing GNU BFD ld and gold linkers.  However, the authors of
-	<tt>lld</tt> are not constrained by strict compatibility where
-	it would hamper performance or desired functionality.</p>
-
-      <p>Compared to the GNU <tt>ld</tt> 2.17.50 currently in the base system,
-	<tt>lld</tt> will bring:</p>
-
-      <ul>
-	<li>AArch64 (arm64) support</li>
-
-	<li>Link Time Optimization (LTO)</li>
-
-	<li>New ABI support</li>
-
-	<li>Other linker optimizations</li>
-
-	<li>Much faster link times</li>
-
-	<li>Maintained code base</li>
-      </ul>
-
-      <p>The upstream <tt>lld</tt> project has now implemented
-	nearly all of the functionality required to link the amd64
-	FreeBSD base system, including the kernel.  The boot loader
-	components and <tt>rescue</tt> utilities currently do not
-	build with <tt>lld</tt>.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Merge <tt>lld</tt> to FreeBSD head as part of the Clang
-	3.9.0 import.</li><li>Request a ports exp-run with <tt>lld</tt> installed as
-	<tt>/usr/bin/ld</tt>.</li><li>Fix building the boot loader with <tt>lld</tt>.</li><li>Fix building <tt>rescue</tt> with <tt>lld</tt>.</li><li>Test and iterate making <tt>lld</tt> fixes for
-	additional architectures.</li></ol><hr /><h2><a name="VirtualBox-Shared-Folders-Filesystem" href="#VirtualBox-Shared-Folders-Filesystem" id="VirtualBox-Shared-Folders-Filesystem">VirtualBox Shared Folders Filesystem</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/lwhsu/FreeBSD-vboxfs" title="https://github.com/lwhsu/FreeBSD-vboxfs">Project Repository</a></td><td>
-	    URL: <a href="https://github.com/lwhsu/FreeBSD-vboxfs" title="Project Repository">https://github.com/lwhsu/FreeBSD-vboxfs</a></td></tr></table><p>
-	Contact:
-	  Li-Wen
-	  Hsu
-	 &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD provides an API for guest operating systems to access
-	shared folders on the host so that the kernel driver can
-	expose them to the guest's userland.  This project aims to add
-	such functionality to the VirtualBox Guest Additions
-	driver.</p>
-
-      <p>Good progress was made over the last few months.  Developers were
-	able to mount a filesystem in read-only mode and, with some
-	limitations, in read-write mode.  The implementation still
-	lacks some critical pieces, but the roadmap is clear.</p>
-    <h3>Open tasks:</h3><ol><li>Finish the missing pieces.</li><li>Implement proper locking.</li><li>General clean-up and bugfixes.</li></ol><hr /><h2><a name="ZFS-Code-Sync-with-Latest-OpenZFS/Illumos" href="#ZFS-Code-Sync-with-Latest-OpenZFS/Illumos" id="ZFS-Code-Sync-with-Latest-OpenZFS/Illumos">ZFS Code Sync with Latest OpenZFS/Illumos</a></h2><p>
-	Contact:
-	  Alexander
-	  Motin
-	 &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Andriy
-	  Gapon
-	 &lt;<a href="mailto:avg@FreeBSD.org">avg@FreeBSD.org</a>&gt;
-	</p>
-      <p>The ZFS code base in FreeBSD regularly gets merges of new code,
-	staying in sync with the latest OpenZFS/Illumos sources.  Among
-	other things, the latest merge included the following
-	improvements:</p>
-
-      <ul>
-	<li>The ARC now mostly stores compressed data, the same as is
-	  stored on disk, decompressing them on demand.</li>
-
-	<li>The L2ARC now stores the same (compressed) data as the ARC
-	  without recompression, and its RAM usage was further
-	  reduced.</li>
-
-	<li>The largest size of indirect block possible has been
-	  increased from 16KB to 128KB, and speculative prefetching of
-	  indirect blocks is now performed.</li>
-
-	<li>Improved ordering of space allocation.</li>
-
-	<li>The SHA-512t256 and Skein hashing algorithms are now
-	  supported.</li>
-      </ul>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="evdev-Support" href="#evdev-Support" id="evdev-Support">evdev Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/wulf7/FreeBSD" title="https://github.com/wulf7/FreeBSD">evdev WIP Repository</a></td><td>
-	    URL: <a href="https://github.com/wulf7/FreeBSD" title="evdev WIP Repository">https://github.com/wulf7/FreeBSD</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens" title="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens">Original evdev Proposal</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens" title="Original evdev Proposal">https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens</a></td></tr></table><p>
-	Contact:
-	  Vladimir
-	  Kondratiev
-	 &lt;<a href="mailto:wulf@cicgroup.ru">wulf@cicgroup.ru</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>evdev</tt> is a portable, API-compatible implementation
-	of the Linux <tt>/dev/input/eventX</tt> interface.  It covers
-	a wide variety of input devices like keyboards, mice, and
-	touchscreens (with multitouch support), and support for it is
-	implemented in a lot of existing userland components like Qt,
-	<tt>libinput</tt>, and <tt>tslib</tt>.</p>
-
-      <p><tt>evdev</tt> support was started by Jakub Klama as a Google
-	SoC 2014 project, and later picked up and finished by Vladimir
-	Kondratiev.  General API and <tt>evdev</tt> support bits for
-	<tt>ukbd</tt> and <tt>ums</tt> were committed to head.
-	Support was also added for TI's AM33xx touchstreen controller
-	(the popular BeagleBone is based on the AM33xx) and the
-	official touchscreen for the Raspberry Pi.  Multitouch support
-	for the Raspberry Pi was successfully demonstrated using the
-	latest Qt development branch.</p>
-    <h3>Open tasks:</h3><ol><li>Documentation.  In particular, manual pages are needed for
-	the KPI.</li><li>Support additional hardware.</li><li>Enable <tt>evdev</tt> support in existing ports, and add
-	new <tt>evdev</tt>-dependent ports.</li></ol><hr /><h2><a name="FreeBSD-Driver-for-the-Annapurna-Labs-ENA" href="#FreeBSD-Driver-for-the-Annapurna-Labs-ENA" id="FreeBSD-Driver-for-the-Annapurna-Labs-ENA">FreeBSD Driver for the Annapurna Labs ENA</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html" title="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html">Amazon AWS Documentation of the ENA</a></td><td>
-	    URL: <a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html" title="Amazon AWS Documentation of the ENA">http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html</a></td></tr></table><p>
-	Contact:
-	  Jan
-	  Medala
-	 &lt;<a href="mailto:jan@semihalf.com">jan@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Jakub
-	  Palider
-	 &lt;<a href="mailto:jpa@semihalf.com">jpa@semihalf.com</a>&gt;
-	</p>
-      <p>The Elastic Network Adapter (ENA) is a 25G SmartNIC developed
-	by Annapurna Labs based on a custom ARMv8 chip.  This is a
-	high-performance networking card that is available to AWS
-	virtual machines.  It introduces enhancements in network
-	utilization scalability on EC2 machines running various
-	operating systems, in particular FreeBSD.</p>
-
-      <p>The goal of FreeBSD enablement is to provide top performance and
-	a wide range of monitoring and management features such
-	as:</p>
-
-      <ul>
-	<li>multiple queue modes</li>
-
-	<li>various offload functionality</li>
-
-	<li>admin queue</li>
-
-	<li>asynchronous notification</li>
-
-	<li>robust hardware access</li>
-
-	<li>scalable number of MSI-X interrupts</li>
-
-	<li>counters</li>
-      </ul>
-
-      <p>The current state offers stable driver operation with good
-	performance on machines running FreeBSD directly on the
-	hardware.</p>
-    <p>This project was sponsored by Annapurna Labs &#8212; an Amazon company.</p><h3>Open tasks:</h3><ol><li>Optimize performance for virtualized environments.</li><li>Prepare for submitting the driver as a Phabricator
-	review.</li></ol><hr /><h2><a name="FreeBSD-on-Hyper-V-and-Azure" href="#FreeBSD-on-Hyper-V-and-Azure" id="FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/HyperV" title="https://wiki.FreeBSD.org/HyperV">FreeBSD Virtual Machines on Microsoft Hyper-V</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/HyperV" title="FreeBSD Virtual Machines on Microsoft Hyper-V">https://wiki.FreeBSD.org/HyperV</a></td></tr><tr><td><a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="https://technet.microsoft.com/en-us/library/dn531030.aspx">Supported Linux and FreeBSD virtual machines for Hyper-V on Windows</a></td><td>
-	    URL: <a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="Supported Linux and FreeBSD virtual machines for Hyper-V on Windows">https://technet.microsoft.com/en-us/library/dn531030.aspx</a></td></tr></table><p>
-	Contact:
-	  Sepherosa
-	  Ziehau
-	 &lt;<a href="mailto:sepherosa@gmail.com">sepherosa@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Hongjiang
-	  Zhang
-	 &lt;<a href="mailto:honzhan@microsoft.com">honzhan@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Dexuan
-	  Cui
-	 &lt;<a href="mailto:decui@microsoft.com">decui@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Kylie
-	  Liang
-	 &lt;<a href="mailto:kyliel@microsoft.com">kyliel@microsoft.com</a>&gt;
-	</p>
-      <p>This quarter, the Hyper-V storage driver was greatly
-	improved: its performance was increased by a factor of 1.2-2
-	by applying BUS_DMA and UNMAP_IO, enlarging the request queue,
-	and selecting the outgoing channel with the LUN considered;
-	TRIM/UNMAP was enabled; and some critical bugs (PRs 209443,
-	211000, 212998) were fixed so that disk hot add/remove and
-	VHDX online resizing should work now.</p>
-
-      <p>The VMBus driver also received attention, with enhancements
-	made for the handling of device hot add/remove.</p>
-
-      <p> In the Hyper-V network driver, configurable RSS key and
-	dynamic MTU change are now supported.</p>
-
-      <p>FreeBSD images on Azure continue to be updated &#8212; after
-	publishing the FreeBSD 10.3 VM image on the global Microsoft
-	Azure in June, Microsoft also published the VM image on the
-	Microsoft Azure operated by 21Vianet in China in
-	September.</p>
-
-      <p>Patches have been developed to support PCIe pass-through
-	(also known as Discrete Device Assignment); this feature
-	allows physical PCIe devices to be passed through to FreeBSD VMs
-	running on Hyper-V (Windows Server 2016), giving them
-	near-native performance with low CPU utilization.  The patch
-	to enable the feature will be posted for review soon.</p>
-    <p>This project was sponsored by Microsoft.</p><hr /><h2><a name="Timekeeping-Code-Improvements" href="#Timekeeping-Code-Improvements" id="Timekeeping-Code-Improvements">Timekeeping Code Improvements</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work was done to properly lock the time-keeping code.  The
-	existing code correctly interoperated with readers, both
-	kernel- and user-space, giving them lock-less access to the
-	actual data ('timehands') needed to derive the time of day
-	from the timecounter hardware in the presence of updaters.
-	But updates of the timehands, which are performed by periodic
-	clock interrupts, the ntpd-driven <tt>sys_ntp_adjtime(2)</tt>
-	syscall, the <tt>settimeofday(2)</tt> syscall, pps sync, and
-	possibly other sources, were not coordinated.  Moreso, the NTP
-	code was locked by Giant, which did not really serve any
-	purpose.</p>
-
-      <p>As a result of the work, locking was applied to ensure that
-	any timehands adjustments are performed by a single mutator.
-	An interesting case is the parallel modification of the
-	timehands from the top of the kernel, for instance the
-	<tt>settimeoday(2)</tt> syscall, and a simultaneous clock tick
-	event, where the syscall has already acquired the resources.
-	In this case, it is highly desirable to not block (spin) in
-	the tick handler, and the required adjustments are performed
-	by the already executing call from the top half.  There, the
-	typical trylock operation is desired, which was surprisingly
-	lacking in our spinlock implementation.
-	<tt>mtx_trylock_spin(9)</tt> was implemented and is used for
-	this purpose.</p>
-
-      <p>The userspace <tt>gettimeofday(2)</tt> implementation was
-	enhanced to allow syscall-less operation on machines that use
-	HPET hardware for timecounters.  The HPET algorithm coexists
-	with older RDTSC-based code, allowing dynamic switching of
-	timecounters.  A page with HPET registers is
-	<tt>mmap(2)</tt>-ed readonly by libc into userland application
-	programs' address space as needed.  Measurements demonstrated
-	modest improvements in <tt>gettimeofday(2)</tt> performance,
-	but, not unexpectedly, even the syscall-less HPET timecounter
-	is slower than invoking a syscall for RDTSC.</p>
-
-      <p>Some not strictly intertwined but related code is the
-	time-bound sleep implementation.  Handling of races between
-	callouts and the top-half code that sets and processes the
-	timeouts depended on the many fine details of the
-	<tt>callout_stop(9)</tt> KPI (kernel programming interface).
-	In particular, races or unpunctual KPI changes usually result
-	in the "catch-all" unkillable thread state with the
-	"-" waitchain bug.  The sleepqueue timeout code was
-	rewritten to stop depending on the KPI details, which removed
-	the source of recurring bugs, and also surprisingly simplified
-	the code.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Google-Summer-of-Code-2016" href="#Google-Summer-of-Code-2016" id="Google-Summer-of-Code-2016">Google Summer of Code 2016</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2016Projects" title="https://wiki.FreeBSD.org/SummerOfCode2016Projects">GSoC 2016 Projects</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2016Projects" title="GSoC 2016 Projects">https://wiki.FreeBSD.org/SummerOfCode2016Projects</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCodeIdeas" title="https://wiki.FreeBSD.org/SummerOfCodeIdeas">GSoC Ideas page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCodeIdeas" title="GSoC Ideas page">https://wiki.FreeBSD.org/SummerOfCodeIdeas</a></td></tr></table><p>
-	Contact:
-	  Gavin
-	  Atkinson
-	 &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Pedro
-	  Giffuni
-	 &lt;<a href="mailto:pfg@FreeBSD.org">pfg@FreeBSD.org</a>&gt;
-	</p>
-      <p>As in all previous editions of the Google Summer of Code,
-	FreeBSD was an accepted organization, and we had the chance to
-	mentor 15 projects.  Huge thanks to all our mentors for
-	keeping the high quality standards that make our community
-	shine.</p>
-
-      <p>This year was rather unique in that we accepted for the first
-	time well-known members of the community that are not src
-	committers to co-mentor.  We also accepted projects that have
-	a different upstream than FreeBSD.  Both are clear signs that
-	FreeBSD is growing and adapting to the wider community.</p>
-
-      <p>This year we are also had administrative issues with Perforce
-	and have officially accepted the use of external repositories,
-	in particular github, as requested by students.</p>
-
-      <p>12 of 15 projects were successful, which we think is an
-	excellent result for a Google Summer of Code.</p>
-    <p>This project was sponsored by Google Inc, and The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>The world is changing and we need fresh project ideas.  We
-	need to start looking for those ideas
-	<strong>now</strong>.</li><li>The project ideas wiki page has been reset and we need to
-	get it populated before applying for the next Google Summer of
-	Code.  Please help unleash the next stream of projects you
-	want to see in FreeBSD.</li></ol><hr /><h2><a name="Non-BSM-to-BSM-Conversion-Tools" href="#Non-BSM-to-BSM-Conversion-Tools" id="Non-BSM-to-BSM-Conversion-Tools">Non-BSM to BSM Conversion Tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2016/NonBSMtoBSMConversionTools" title="https://wiki.FreeBSD.org/SummerOfCode2016/NonBSMtoBSMConversionTools">Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2016/NonBSMtoBSMConversionTools" title="Wiki Page">https://wiki.FreeBSD.org/SummerOfCode2016/NonBSMtoBSMConversionTools</a></td></tr><tr><td><a href="https://github.com/0mp/FreeBSD" title="https://github.com/0mp/FreeBSD">GitHub Repository</a></td><td>
-	    URL: <a href="https://github.com/0mp/FreeBSD" title="GitHub Repository">https://github.com/0mp/FreeBSD</a></td></tr><tr><td><a href="https://github.com/0mp/FreeBSD/pull/9" title="https://github.com/0mp/FreeBSD/pull/9">Pull Request With Consolidated Patch</a></td><td>
-	    URL: <a href="https://github.com/0mp/FreeBSD/pull/9" title="Pull Request With Consolidated Patch">https://github.com/0mp/FreeBSD/pull/9</a></td></tr></table><p>
-	Contact:
-	  Mateusz
-	  Piotrowski
-	 &lt;<a href="mailto:0mp@FreeBSD.org">0mp@FreeBSD.org</a>&gt;
-	</p>
-      <p>This project was started during Google Summer of Code this
-	year.  The aim was to create a library which can convert the
-	audit trail files in Linux Audit format or the format used by
-	Windows to the BSM format used by FreeBSD for its audit logs.
-	Apart from that, I wanted to create a simple command-line tool
-	and extend <tt>auditdistd</tt> so that it is possible to send
-	non-BSM logs to it over a secure connection and save those
-	audit logs on disk, preferably in the BSM format.</p>
-
-      <p>So far, it is possible to reasonably convert some of the most
-	common Linux audit log events to BSM, but it still needs a lot
-	of work.  Secondly, I was able to configure
-	<tt>auditdistd</tt> to communicate with CentOS over an
-	insecure connection.  Thirdly, the command-line tool is usable
-	but not perfect.</p>
-
-      <p>The present work focuses on configuring the secure TLS
-	connection between CentOS and <tt>auditdistd</tt>.  I have
-	already tried using <tt>rsyslogd</tt> but was not able to make it
-	work.</p>
-    <p>This project was sponsored by Google Summer of Code.</p><h3>Open tasks:</h3><ol><li>I need more examples of rare Linux Audit logs; please send
-	me some examples if you have any.  It is much easier to
-	improve the conversion process with real-life examples of
-	audit events as you write the code to convert them.</li><li>Configure <tt>auditdistd</tt> to be able to communicate
-	with some software on CentOS over TLS in order to receive
-	audit logs.  I was not able to come up with a simple solution
-	for that.</li><li>Additional open tasks are listed on the Wiki page and in
-	the <tt>TODO</tt> file in the root directory of the project.</li></ol><hr /><h2><a name="ptnet-Driver-and-bhyve-Device-Model" href="#ptnet-Driver-and-bhyve-Device-Model" id="ptnet-Driver-and-bhyve-Device-Model">ptnet Driver and bhyve Device
-      Model</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2016/PtnetDriverAndDeviceModel" title="https://wiki.FreeBSD.org/SummerOfCode2016/PtnetDriverAndDeviceModel">FreeBSD Wiki Page for Project Overview</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2016/PtnetDriverAndDeviceModel" title="FreeBSD Wiki Page for Project Overview">https://wiki.FreeBSD.org/SummerOfCode2016/PtnetDriverAndDeviceModel</a></td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/papers/20160613-ptnet.pdf" title="http://info.iet.unipi.it/~luigi/papers/20160613-ptnet.pdf">Conference Paper</a></td><td>
-	    URL: <a href="http://info.iet.unipi.it/~luigi/papers/20160613-ptnet.pdf" title="Conference Paper">http://info.iet.unipi.it/~luigi/papers/20160613-ptnet.pdf</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/socsvn/soc2016/vincenzo/head/" title="https://svnweb.FreeBSD.org/socsvn/soc2016/vincenzo/head/">Subversion Repository</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/socsvn/soc2016/vincenzo/head/" title="Subversion Repository">https://svnweb.FreeBSD.org/socsvn/soc2016/vincenzo/head/</a></td></tr></table><p>
-	Contact:
-	  Vincenzo
-	  Maffione
-	 &lt;<a href="mailto:v.maffione@gmail.com">v.maffione@gmail.com</a>&gt;
-	</p>
-      <p>This project provides:</p>
-
-      <ul>
-	<li>A new driver (<tt>if_ptnet</tt>) for a paravirtualized
-	  network device, modeled after the netmap API.  The driver
-	  supports multi-queue netmap ports, and it is able to work
-	  both in netmap mode and in normal mode.</li>
-
-	<li>The emulation of the <tt>ptnet</tt> device model as a
-	  module of the <tt>bhyve</tt> hypervisor.</li>
-      </ul>
-
-      <p>The <tt>ptnet</tt> device and driver has been introduced to
-	overcome the performance limitations of TCP/IP networking
-	between bhyve VMs.  Prior to this work, the most performant
-	solution for VM-to-VM intra-host TCP communication provided
-	less than 2 Gbps TCP throughput.  With <tt>ptnet</tt>, in the
-	same VM-to-VM TCP communication scenario, it is possible to
-	obtain up to 20 Gbps.</p>
-    <p>This project was sponsored by Google Summer of Code.</p><h3>Open tasks:</h3><ol><li>Share <tt>virtio-net</tt> header management code with the
-	<tt>if_vtnet</tt> driver.  In the current code, about 100
-	lines of code have been copied and pasted from
-	<tt>if_vtnet.c</tt>.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Annapurna-Labs-Alpine" href="#FreeBSD-on-Annapurna-Labs-Alpine" id="FreeBSD-on-Annapurna-Labs-Alpine">FreeBSD on Annapurna Labs Alpine</a></h2><p>
-	Contact:
-	  Jan
-	  Medala
-	 &lt;<a href="mailto:jan@semihalf.com">jan@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Michal
-	  Stanek
-	 &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Macek
-	 &lt;<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>&gt;
-	</p>
-      <p>Alpine is a family of Platform-on-Chip devices, including
-	multi-core 32-bit (first-gen Alpine) and 64-bit (Alpine V2)
-	ARM CPUs, developed by Annapurna Labs.</p>
-
-      <p>The primary focus areas of the Alpine platform are
-	high-performance networking, storage, and embedded
-	applications.  The network subsystem features 10-, 25-, and
-	50-Gbit Ethernet controllers with support for virtualization,
-	load-balancing, hardware offload and other advanced
-	features.</p>
-
-      <p>A basic patch set has already been committed to head
-	including:</p>
-
-      <ul>
-	<li>PCIe Root Complex support</li>
-
-	<li>Cache Coherency Unit driver</li>
-
-	<li>North Bridge Service driver</li>
-
-	<li>Updated Alpine HAL</li>
-
-	<li>Extended MSI support in GICv2 and GICv3 code</li>
-      </ul>
-
-      <p>Additional work, such as an MSI-X driver and full Ethernet
-	support, is currently undergoing community review on
-	Phabricator.</p>
-
-      <p>The multi-user SMP system is stable and fully working, along
-	with the 1G and 10G Ethernet links.</p>
-
-      <p>The interrupt management code has been adjusted to work with
-	the new INTRNG framework on both ARM32 and ARM64.</p>
-    <p>This project was sponsored by Annapurna Labs &#8212; an Amazon company, and Semihalf.</p><hr /><h2><a name="FreeBSD-on-Marvell-Armada38x" href="#FreeBSD-on-Marvell-Armada38x" id="FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></h2><p>
-	Contact:
-	  Marcin
-	  Wojtas
-	 &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Bartosz
-	  Szczepanek
-	 &lt;<a href="mailto:bsz@semihalf.com">bsz@semihalf.com</a>&gt;
-	</p>
-      <p>FreeBSD includes support for the Marvell Armada38x platform,
-	which has been tested and improved in order to gain production
-	quality.  Most of this effort has been invested in development
-	and benchmarking of the on-chip Gigabit Ethernet (NETA)
-	functionality.  Numerous bug fixes and some new features have
-	been introduced.</p>
-
-      <p>Work completed this quarter includes:</p>
-
-      <ul>
-	<li>NETA rework and improvements.</li>
-
-	<li>Enable multi-port support in PCIe 2.0 driver
-	  (<tt>mv_pci_ctrl</tt>).</li>
-
-	<li>Introduce an alternative, coherent, <tt>bus_dma</tt> for
-	  the armv7 arch.</li>
-
-	<li>AHCI controller support.</li>
-
-	<li>SDHCI controller support.</li>
-
-	<li>Improve the <tt>e6000sw</tt> etherswitch driver.</li>
-
-	<li>Fix Marvell bus configuration for numerous
-	  interfaces.</li>
-      </ul>
-
-      <p>Along with support for new boards (SolidRun ClearFog and
-	DB-88F6285-AP), all changes will be submitted upstream.</p>
-    <p>This project was sponsored by Stormshield, and Semihalf.</p><h3>Open tasks:</h3><ol><li>Finalize NETA and prepare for submission.</li><li>Submit remaining fixes and drivers.</li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64" title="https://wiki.FreeBSD.org/arm64">FreeBSD arm64 Wiki Entry</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/arm64" title="FreeBSD arm64 Wiki Entry">https://wiki.FreeBSD.org/arm64</a></td></tr><tr><td><a href="https://github.com/wca/crochet/tree/add-pine64-support" title="https://github.com/wca/crochet/tree/add-pine64-support">Using Crochet to Build FreeBSD Images</a></td><td>
-	    URL: <a href="https://github.com/wca/crochet/tree/add-pine64-support" title="Using Crochet to Build FreeBSD Images">https://github.com/wca/crochet/tree/add-pine64-support</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jared
-	  McNeill
-	 &lt;<a href="mailto:jmcneill@FreeBSD.org">jmcneill@FreeBSD.org</a>&gt;
-	</p>
-      <p>Transparent superpage support has been added.  This allows
-	FreeBSD to create 2MiB blocks with a single pagetable and TLB
-	entry.  This shows a small but significant improvement in the
-	buildworld time on ThunderX machines.  Superpages have been
-	enabled in head and merged to stable/11, but they are disabled
-	by default on stable/11 due to a lack of testing there.</p>
-
-      <p>Support for the pre-INTRNG interrupt framework has been
-	removed.  This means that arm64 requires INTRNG to even build.
-	This has allowed various cleanups within the arm64 drivers
-	that interact with the interrupt controller.</p>
-
-      <p>The cortex Strings library from Linaro has been imported.
-	The parts of this that have been shown to be improvements over
-	the previous C code were attached to the libc build.</p>
-
-      <p>There is ongoing work to add ACPI support to the kernel.  On
-	ThunderX, FreeBSD can get to the mountroot prompt, however, due
-	to incomplete ACPI tables the external PCIe support needed to
-	support the netboot setup in the test cluster is not
-	functional.</p>
-
-      <p>Pine64 support has been committed to head.  FreeBSD can now boot
-	to multiuser with SMP enabled.  This includes support for
-	clocks, secure ID controller, USB Host controller, GPIOs,
-	non-maskable interrupts, AXP81x power management unit, cpu
-	freqency and voltage scaling, MMC, UART, gigabit networking,
-	watchdog, and thermal sensors.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, and ABT Systems Ltd.</p><hr /><h2><a name="UEFI-Runtime-Services" href="#UEFI-Runtime-Services" id="UEFI-Runtime-Services">UEFI Runtime Services</a></h2><p>
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>UEFI (Unified Extensible Firmware Interface) specifies two
-	kinds of services for use by operating systems.  Boot Services
-	are designed for OS loaders to load and initialize kernels,
-	while Runtime Services are meant to be used by kernels during
-	regular system operations.  The boot and runtime phases are
-	explicitly separated.  During boot, when loaders are executed,
-	the machine configuration is owned by UEFI.  During runtime,
-	the kernel manages the configuration, but needs to inform the
-	firmware about any changes that are made.</p>
-
-      <p>The model of split boot/runtime configuration makes
-	assumptions about the OS architecture that do not quite apply
-	to the existing FreeBSD codebase.  For instance, the firmware
-	notification of the future runtime configuration must be done
-	while the loader is effectively still in control.  In
-	technical terms, the <tt>SetVirtualAddressMap()</tt> call must
-	be made with the 1:1 physical:virtual mapping on amd64
-	systems, which for FreeBSD means that the call can only be issued
-	by the loader.  But the loader needs to know intimate details
-	of the kernel address map to provide the requested
-	information.  This creates a new, unfortunate, coupling
-	between loader and kernel.</p>
-
-      <p>Reading the publicly available information about the MS
-	Windows boot process explained the UEFI control transfer
-	model.  The Windows loader constructs the address map for the
-	kernel, and with such a division of work the UEFI model is
-	reasonable.  The FreeBSD kernel constructs its own address
-	space, only relying on a minimal map constructed by the
-	loader, which is enough for the pmap subsystem to bootstrap
-	itself and then to perform machine initialization in common
-	code.</p>
-
-      <p>Initial experiments with enabling runtime services were
-	centered around utilizing the direct address map (DMAP) on
-	amd64, which currently always exists and linearly maps at
-	least the lower 4G of physical addresses at some KVA location.
-	It was supposed that the kernel would export the DMAP details
-	like linear base and guaranteed size for loader from its ELF
-	image, and provide the needed overflow map if the DMAP cannot
-	completely serve.  Unfortunately, two show-stopper bugs were
-	discovered with this approach.</p>
-
-      <p>First, EDK-based firmware apparently requires that the
-	runtime mapping exists simultaneously with the physical
-	mapping for the <tt>SetVirtualAddressMap()</tt> call.  Second,
-	there were references from other open-source projects
-	mentioning that some firmware required the presence of the
-	physical mapping during the runtime call.  Effectively, this
-	forces both kernel and loader to provide both mappings for all
-	runtime calls.</p>
-
-      <p>With such restrictions, informing the firmware about the
-	details of the kernel address space only adds useless work.
-	We could just as easily establish the 1:1 physical mapping
-	during runtime and get rid of
-	<tt>SetVirtualAddressMap()</tt> entirely.  This approach was
-	coded and the kernel interface to access runtime services is
-	based on it.</p>
-
-      <p>During development, particularly when trying to make
-	the loader modifications, it was quickly realized that there
-	were no fault-reporting facilities in <tt>loader.efi</tt>.
-	Machine exceptions resulted in a silent hang.  Curiously, in
-	such a situation the Intel firmware outputs the error code
-	over the serial port over 115200/8/1 settings, regardless of
-	UEFI console configuration, which was discovered by accident.
-	Unfortunately, the error code alone is not enough to diagnose
-	most problems.</p>
-
-      <p>A primitive fault reporter was written for
-	<tt>loader.efi</tt> on amd64, which intercepts exceptions from
-	the firmware IDT and dumps the machine state to the loader
-	console.  Due to the complexity of the interception and
-	possible bugs which might do more harm than good there, the
-	dumper is only activated on explicit administrator
-	action.</p>
-
-      <p>Note that the described work only provides the kernel
-	interfaces to make calling the EFI runtime services as easy as
-	calling a regular C function.  User-visible feature
-	development making use of the new interfaces is being
-	performed right now.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://FreeBSD.kde.org/" title="https://FreeBSD.kde.org/">KDE on FreeBSD website</a></td><td>
-	    URL: <a href="https://FreeBSD.kde.org/" title="KDE on FreeBSD website">https://FreeBSD.kde.org/</a></td></tr><tr><td><a href="https://FreeBSD.kde.org/area51.php" title="https://FreeBSD.kde.org/area51.php">KDE ports staging area</a></td><td>
-	    URL: <a href="https://FreeBSD.kde.org/area51.php" title="KDE ports staging area">https://FreeBSD.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/KDE" title="https://wiki.FreeBSD.org/KDE">KDE on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/KDE" title="KDE on FreeBSD wiki">https://wiki.FreeBSD.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-FreeBSD" title="https://mail.kde.org/mailman/listinfo/kde-FreeBSD">KDE/FreeBSD mailing list</a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-FreeBSD" title="KDE/FreeBSD mailing list">https://mail.kde.org/mailman/listinfo/kde-FreeBSD</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/plasma5" title="http://src.mouf.net/area51/log/branches/plasma5">Development repository for integrating Plasma 5 and KDE Frameworks 5</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/plasma5" title="Development repository for integrating Plasma 5 and KDE Frameworks 5">http://src.mouf.net/area51/log/branches/plasma5</a></td></tr><tr><td><a href="http://src.mouf.net/area51/log/branches/qt-5.7" title="http://src.mouf.net/area51/log/branches/qt-5.7">Development repository for integrating Qt 5.7</a></td><td>
-	    URL: <a href="http://src.mouf.net/area51/log/branches/qt-5.7" title="Development repository for integrating Qt 5.7">http://src.mouf.net/area51/log/branches/qt-5.7</a></td></tr></table><p>
-	Contact: KDE on FreeBSD Team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging the KDE software
-	and making sure that the experience of KDE and Qt on FreeBSD is
-	as good as possible.</p>
-
-      <p>The following big updates were landed in the ports tree this
-	quarter:</p>
-
-      <ul>
-	<li>Added a Qt5 option to <tt>multimedia/mlt</tt>.</li>
-
-	<li>Added the <tt>devel/grantlee5</tt> port and, with it,
-	  <tt>Uses/grantlee.mk</tt>.</li>
-
-	<li>Added the <tt>multimedia/gstreamer1-qt5</tt> port.</li>
-
-	<li>Added the <tt>net-im/telepathy-qt5</tt> port.</li>
-
-	<li>CMake was updated to versions 3.6.1 and 3.6.2.</li>
-
-	<li>An important fix was made to <tt>qmake</tt>, where the
-	  clang version was not correctly detected.</li>
-
-	<li>Qt 5.6.1 was committed to ports.</li>
-
-	<li>Phonon and its backend to were updated to 4.9.0 in
-	  preparation for Qt 5.6.1.</li>
-
-	<li>Updated the <tt>net-im/telepathy-qt4</tt> port to
-	  0.9.7.</li>
-
-	<li>Various LibreSSL related fixes by Matthew Rezny.</li>
-
-	<li>bsd.kde4.mk has been replaced by Uses/kde.mk.</li>
-
-	<li><tt>www/webkit-qt5</tt> was fixed to depend on the systems
-	  leveldb.</li>
-      </ul>
-
-      <p>In our development repository, we have done this
-	work:</p>
-
-      <ul>
-	<li>The plasma5 branch has been kept up to date with KDE's
-	  upstream and contains ports for Frameworks 5.26.0, Plasma
-	  Desktop 5.8.0, and Applications 16.08.1
-	  (branches/plasma5).</li>
-      </ul>
-    <hr /><h2><a name="LXQt-on-FreeBSD" href="#LXQt-on-FreeBSD" id="LXQt-on-FreeBSD">LXQt on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/LXQt" title="https://wiki.FreeBSD.org/LXQt">FreeBSD LXQt Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/LXQt" title="FreeBSD LXQt Project">https://wiki.FreeBSD.org/LXQt</a></td></tr><tr><td><a href="http://lxqt.org/" title="http://lxqt.org/">LXQt Project</a></td><td>
-	    URL: <a href="http://lxqt.org/" title="LXQt Project">http://lxqt.org/</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/lxqt/subversion/source" title="https://www.assembla.com/spaces/lxqt/subversion/source">LXQt Development Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/lxqt/subversion/source" title="LXQt Development Repository">https://www.assembla.com/spaces/lxqt/subversion/source</a></td></tr></table><p>
-	Contact:
-	  Olivier
-	  Duchateau
-	 &lt;<a href="mailto:olivierd@FreeBSD.org">olivierd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jesper
-	  Schmitz Mouridsen
-	 &lt;<a href="mailto:jesper@schmitz.computer">jesper@schmitz.computer</a>&gt;
-	</p>
-      <p>LXQt is the Qt port of and the upcoming version of LXDE, the
-	Lightweight Desktop Environment.  It is the product of a merge
-	between the LXDE-Qt and Razor-qt projects.</p>
-
-      <p>The porting effort remains very much a work in progress: it
-	requires some components of Plasma 5, the new major KDE
-	workspace.</p>
-
-      <p>The porting of the 0.11 branch is now complete, with new
-	ports (compared to the previous release).  See our wiki page
-	for a complete list of applications.</p>
-
-      <p>We also have updates for:</p>
-
-      <ul>
-
-	<li><tt>x11-toolkits/qtermwidget</tt> (0.7.0)</li>
-
-	<li><tt>x11/qterminal</tt> (0.7.0)</li>
-
-	<li><tt>x11/qterminal-l10n</tt></li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li> Improve FreeBSD support in <tt>sysutils/lxqt-admin</tt>,
-	especially with respect to user management.</li><li>Add additional panel plugins.</li></ol><hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Xfce" title="https://wiki.FreeBSD.org/Xfce">FreeBSD Xfce Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Xfce" title="FreeBSD Xfce Project">https://wiki.FreeBSD.org/Xfce</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="https://www.assembla.com/spaces/xfce4/subversion/source">FreeBSD Xfce Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="FreeBSD Xfce Repository">https://www.assembla.com/spaces/xfce4/subversion/source</a></td></tr></table><p>
-	Contact:
-	  FreeBSD Xfce Team
-	 &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms such as FreeBSD.  It aims to be fast and
-	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>
-
-      <ul>
-	<li><tt>audio/xfmpc</tt> (0.2.3)</li>
-
-	<li><tt>deskutils/xfce4-notifyd</tt> (0.3.2)</li>
-
-	<li><tt>deskutils/xfce4-volumed-pulse</tt> (0.2.2)</li>
-
-	<li><tt>devel/thunar-vcs-plugin</tt> (0.1.5)</li>
-
-	<li><tt>misc/xfce4-weather-plugin</tt> (0.8.8)</li>
-
-	<li><tt>sysutils/xfce4-settings</tt> (4.12.1)</li>
-
-	<li><tt>x11/xfce4-clipman-plugin</tt> (1.4.0)</li>
-
-	<li><tt>x11/xfce4-dashboard</tt> (0.6.0)</li>
-
-	<li><tt>x11/xfce4-goodies</tt>, the meta-port for the Xfce4
-	  Goodies Project (plugins, applications)</li>
-
-	<li><tt>x11/xfce4-whiskermenu-plugin</tt> (1.6.0)</li>
-      </ul>
-
-      <p>We also follow the unstable releases; the current unstable
-	release brings support for Gtk3 (available in our experimental
-	repository) to:</p>
-
-      <ul>
-	<li><tt>audio/xfce4-mpc-plugin</tt> (0.4.99)</li>
-
-	<li><tt>sysutils/garcon</tt> (0.5.0)</li>
-
-	<li><tt>sysutils/xfce4-battery-plugin</tt> (1.0.99)</li>
-
-	<li><tt>sysutils/xfce4-diskperf-plugin</tt> (2.5.99)</li>
-
-	<li><tt>sysutils/xfce4-fsguard-plugin</tt> (1.0.99)</li>
-
-	<li><tt>sysutils/xfce4-netload-plugin</tt> (1.2.99)</li>
-
-	<li><tt>sysutils/xfce4-systemload-plugin</tt> (1.1.99)</li>
-
-	<li><tt>www/xfce4-smartbookmark-plugin</tt> (0.4.99)</li>
-
-	<li><tt>x11/libexo</tt> (0.11.1)</li>
-
-	<li><tt>x11/libxfce4menu</tt> (4.13.1)</li>
-
-	<li><tt>x11/xfce4-dashboard</tt> (0.7.0)</li>
-
-	<li><tt>x11/xfce4-terminal</tt> (0.6.92)</li>
-
-	<li><tt>x11/xfce4-whiskermenu-plugin</tt> (2.0.1)</li>
-
-	<li><tt>x11-clocks/xfce4-datetime-plugin</tt> (0.6.99)</li>
-      </ul>
-
-      <p>Currently the unstable releases work fine with our Gtk3
-	ports available in the ports tree, but in the future support
-	for 3.18 will be removed in preference of 3.20.x.</p>
-    <h3>Open tasks:</h3><ol><li>Continue working on unstable releases.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Documenting-the-History-of-Utilities-in-/bin-and-/sbin" href="#Documenting-the-History-of-Utilities-in-/bin-and-/sbin" id="Documenting-the-History-of-Utilities-in-/bin-and-/sbin">Documenting the History of Utilities in /bin and
-      /sbin</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.FreeBSD.org/ports/head/textproc/igor" title="https://svnweb.FreeBSD.org/ports/head/textproc/igor">The igor Port</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/ports/head/textproc/igor" title="The igor Port">https://svnweb.FreeBSD.org/ports/head/textproc/igor</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base/head/share/misc/bsd-family-tree?view=log" title="https://svnweb.FreeBSD.org/base/head/share/misc/bsd-family-tree?view=log">BSD Family Tree in Subversion</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base/head/share/misc/bsd-family-tree?view=log" title="BSD Family Tree in Subversion">https://svnweb.FreeBSD.org/base/head/share/misc/bsd-family-tree?view=log</a></td></tr><tr><td><a href="http://www.tuhs.org" title="http://www.tuhs.org">The UNIX Heritage Society</a></td><td>
-	    URL: <a href="http://www.tuhs.org" title="The UNIX Heritage Society">http://www.tuhs.org</a></td></tr><tr><td><a href="http://man.cat-v.org" title="http://man.cat-v.org">Cat-V Manual Library</a></td><td>
-	    URL: <a href="http://man.cat-v.org" title="Cat-V Manual Library">http://man.cat-v.org</a></td></tr></table><p>
-	Contact:
-	  Sevan
-	  Janiyan
-	 &lt;<a href="mailto:sevan@FreeBSD.org">sevan@FreeBSD.org</a>&gt;
-	</p>
-      <p>For EuroBSDcon, I began looking into inconsistencies within
-	components inside our family of operating systems.  My
-	workflow consisted of reading the documentation for a given
-	utility and checking the history in the revision control
-	system for missing fixes or functionality in the trees of
-	NetBSD, FreeBSD, OpenBSD, and DragonFly BSD.</p>
-
-      <p>One thing which became obvious very quickly was the
-	inconsistency between operating systems about where and/or
-	which version a utility originated in, despite our common
-	heritage.</p>
-
-      <p>I began working through the man pages in FreeBSD, verifying
-	the details in pages which already had a history section and
-	making patches for those which did not.</p>
-
-      <p>From there, changes were propogated out to NetBSD, OpenBSD,
-	and Dragonfly BSD where applicable (not all utilities
-	originated from the same source or implementation, for
-	example).</p>
-
-      <p>This was a good exercise in:</p>
-
-      <ul>
-	<li>Becoming familiar with
-	  <a href="http://mdocml.bsd.lv/man" shape="rect">mandoc</a>.</li>
-
-	<li>Using tools such as the linting functionality in mandoc
-	  and the <tt>igor</tt> documentation script.</li>
-
-	<li>Becoming familiar with the locations where things are
-	  documented and with external sources of historical
-	  information, such as the BSD Family Tree included in the
-	  FreeBSD base system, and projects like
-	  <a href="http://www.tuhs.org" shape="rect">The UNIX Heritage Society</a>
-	  and the <a href="http://man.cat-v.org" shape="rect">manual library</a>
-	  on <a href="http://cat-v.org" shape="rect">cat-v.org</a> which hosts
-	  copies of manuals such as those shipped with
-	  <a href="https://en.wikipedia.org/wiki/Research_Unix" shape="rect">Research UNIX</a>.
-	  These manuals are not commonly available elsewhere.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Cover the remaining manuals for userland utilities, and
-	maybe expand into library and syscall APIs, though I say that
-	without estimating the feasibility.  The history of components
-	originating from a closed-source operating system is tricky to
-	document, since older versions are not always
-	available.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2016-10-2016-12.html b/website/content/en/status/report-2016-10-2016-12.html
deleted file mode 100644
index 688a25a99b..0000000000
--- a/website/content/en/status/report-2016-10-2016-12.html
+++ /dev/null
@@ -1,1550 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Another year has passed (and another has gotten well
-      underway, while we worked to assemble this report).  Over the
-      past two years that I have been part of the monthly@ team that
-      assembles these reports, it has been enlightening to watch the
-      individual entries pass through my emacs and/or vim.  These
-      reports give me a picture of what is going on with FreeBSD that I
-      could not get just from reading commit mail; I hope that is
-      also true for our readers.</p><p>This quarter brings the usual mix of continuations of many
-      stalwart projects and entires of new participants, as well as
-      the return of some items after a few quarters' hiatus.  Enjoy
-      and be enlightened!</p><p>&#8212;Benjamin Kaduk</p><p><hr /></p><p>The deadline for submissions covering the period from January
-      to March 2017 is April 7, 2017.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Ceph-on-FreeBSD">Ceph on FreeBSD</a></li><li><a href="#OpenBSM">OpenBSM</a></li><li><a href="#Sysctl-Exporter-for-Prometheus">Sysctl Exporter for Prometheus</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></li><li><a href="#I2C,-GPIO,-and-SPI-Support-for-MinnowBoard">I2C, GPIO, and SPI Support for MinnowBoard</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-ARM-Boards">FreeBSD on ARM Boards</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#libarchive">libarchive</a></li><li><a href="#Reproducible-Builds-in-FreeBSD">Reproducible Builds in FreeBSD</a></li><li><a href="#Updates-to-GDB">Updates to GDB</a></li><li><a href="#Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker">Using LLVM's LLD Linker as FreeBSD's System Linker</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#GCC-(GNU-Compiler-Collection)">GCC (GNU Compiler Collection)</a></li><li><a href="#LXQt-on-FreeBSD">LXQt on FreeBSD</a></li><li><a href="#Mono">Mono</a></li><li><a href="#Wine">Wine</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/releases/11.0R/announce.html" title="https://www.FreeBSD.org/releases/11.0R/announce.html">FreeBSD�11.0-RELEASE Announcement</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/11.0R/announce.html" title="FreeBSD�11.0-RELEASE Announcement">https://www.FreeBSD.org/releases/11.0R/announce.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/releases/11.0R/relnotes.html" title="https://www.FreeBSD.org/releases/11.0R/relnotes.html">FreeBSD�11.0-RELEASE Release Notes</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/11.0R/relnotes.html" title="FreeBSD�11.0-RELEASE Release Notes">https://www.FreeBSD.org/releases/11.0R/relnotes.html</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD Development Snapshots</a></td><td>
-	    URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD Development Snapshots">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD�Release Engineering Team in concert with
-	the FreeBSD Security Team finalized FreeBSD�11.0-RELEASE.
-	FreeBSD�11.0-RELEASE was announced on October 10, 2016,
-	roughly four weeks after the original schedule.</p>
-
-      <p>The FreeBSD�Release Engineering Team would like to
-	specifically thank Colin Percival and all members of the
-	FreeBSD�Security Team for their extra diligence in ensuring
-	that user-facing upgrade paths were properly addressed and
-	documented.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/portmgr/index.html" title="https://www.FreeBSD.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/portmgr/index.html" title="Ports Management Team">https://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/FreeBSD_portmgr/" title="https://twitter.com/FreeBSD_portmgr/">FreeBSD portmgr on Twitter (@FreeBSD_portmgr)</a></td><td>
-	    URL: <a href="https://twitter.com/FreeBSD_portmgr/" title="FreeBSD portmgr on Twitter (@FreeBSD_portmgr)">https://twitter.com/FreeBSD_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">FreeBSD Ports Management Team on Facebook</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="FreeBSD Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team on Google+</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="FreeBSD Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</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 FreeBSD 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: <tt>pkg</tt>
-	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
-	FreeBSD 11 for mips, mips64, and armv6.  He also improved the
-	balancing, monitoring, automation of the package builders.</p>
-    <h3>Open tasks:</h3><ol><li>If you have some spare time, please take up a PR for
-	testing and committing.</li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <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
-	FreeBSD 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" shape="rect">security</a>
-	page of the FreeBSD 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 FreeBSD
-	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>
-
-      <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,
-	FreeBSD 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.  FreeBSD is already standards conformant, but the
-	propsal is to switch to a <tt>__STDC_ISO_10646_</tt>
-	implementation, similar to what Linux glibc currently uses.
-	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>
-
-      <ul>
-	<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>
-
-	<li>
-	  The trademarks page on the website was updated to show the
-	  current owners of a number of trademarks in their approved
-	  form.
-	</li>
-
-	<li>
-	  In the absence 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
-	  Forgotten" only applies to search engines, and the FreeBSD
-	  project is not one of those, so it need not take any
-	  action.
-	</li>
-
-	<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>
-      </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>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSDFoundation.org/" title="https://www.FreeBSDFoundation.org/">FreeBSD Foundation Website</a></td><td>
-	    URL: <a href="https://www.FreeBSDFoundation.org/" title="FreeBSD Foundation Website">https://www.FreeBSDFoundation.org/</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Funding comes from individual and
-	corporate donations and is used to fund and manage software
-	development projects, conferences and developer summits, and
-	provide travel grants to FreeBSD contributors.  The Foundation
-	purchases and supports hardware to improve and maintain FreeBSD
-	infrastructure; publishes marketing material to promote,
-	educate, and advocate for the FreeBSD Project; facilitates
-	collaboration between commercial vendors and FreeBSD developers;
-	and finally, represents the FreeBSD Project in executing
-	contracts, license agreements, and other legal arrangements
-	that require a recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD last
-	quarter:</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>Our work is 100% funded by your donations.  We raised
-	$1,527,540 in 2016 from 1471 donors!  Thank you to everyone
-	who made a donation to help us continue our efforts in 2017 to
-	support the FreeBSD Project and community worldwide!  You can
-	make a donation here to our 2017 fundraising campaign:
-	<a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">https://www.FreeBSDfoundation.org/donate/</a>.</p>
-
-      <p>OS Improvements</p>
-
-      <p>The Foundation improves the FreeBSD 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
-	like the arm64 port, <tt>blacklistd</tt> access control
-	daemon, and integration of VIMAGE support, to make sure that FreeBSD
-	remains a viable solution for research, education, computing,
-	products and more.</p>
-
-      <p>Large projects supported last year include:</p>
-
-      <ul>
-	<li>arm64 port</li>
-
-	<li>VIMAGE Integration</li>
-
-	<li>Toolchain work</li>
-
-	<li><tt>blacklistd</tt> access control daemon</li>
-      </ul>
-
-      <p>The Foundation team worked on a technology roadmap for
-	2017&#8211;2018 during our board meeting in November.</p>
-
-      <p>Staff and board members continued hosting bi-weekly
-	conference calls to facilitate efforts for individuals to
-	collaborate on different technologies.</p>
-
-      <p>You can find out more about the support we provided by
-	reading individual updates from Ed Maste, Konstatin Belousov,
-	and Edward Napierala in this report.</p>
-
-      <p>Release Engineering</p>
-
-      <p>The Foundation provides a full-time staff member to lead the
-	release engineering efforts.  This has provided timely and
-	reliable releases over the last few years.</p>
-
-      <p>Last quarter, our full-time staff member worked with the
-	FreeBSD Release Engineering and Security Teams to finalize
-	11.0-RELEASE.  He also added support for the powerpcspe
-	architecture to the 12-CURRENT snapshot builds, and continued
-	work on packaging the base system with <tt>pkg(8)</tt>.  He
-	also continued producing 10-STABLE, 11-STABLE, and 12-CURRENT
-	development snapshot builds throughout the quarter.</p>
-
-      <p>You can find out more about the support we provided to the
-	Release Engineering Team by reading their status update in
-	this report.</p>
-
-      <p>Supporting FreeBSD Infrastructure</p>
-
-      <p>The Foundation provides hardware and support to improve the
-	FreeBSD infrastructure.  This year, we purchased the following
-	hardware to improve the build, continuous integration, and
-	platform processes:</p>
-
-      <ul>
-	<li>A server to reduce the build time from over an hour to 20
-	  minutes for the continuous integration process.  You can
-	  find out more information here:
-	  <a href="https://ci.FreeBSD.org/" shape="rect">https://ci.FreeBSD.org/</a>.</li>
-
-	<li>Two ThunderX servers for native package builds for the
-	  FreeBSD/arm64 architecture.</li>
-
-	<li>Two servers to improve release engineering builds.</li>
-
-	<li>Four servers to improve package builds.</li>
-
-	<li>Four servers as build slaves to increase the number of
-	  builds in the continuous integration process.</li>
-      </ul>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating for
-	the Project.  This includes promoting work being done by
-	others with FreeBSD; producing advocacy literature to teach
-	people about FreeBSD and help make the path to starting using
-	FreeBSD or contributing to the Project easier; and attending and
-	getting other FreeBSD contributors to volunteer to run FreeBSD
-	events, staff FreeBSD tables, and give FreeBSD presentations.</p>
-
-      <p>Here is a list highlighting some of the advocacy and
-	education work we did last year:</p>
-
-      <ul>
-	<li>Attended and/or sponsored 24 events around the world</li>
-
-	<li>Provided 15 Travel Grants to developers</li>
-
-	<li>Created new and updated marketing literature including:
-	  <ul>
-	    <li>Updated FreeBSD 10 Brochure</li>
-
-	    <li>New TeachBSD postcard to spread the word about the
-	      program</li>
-
-	    <li>Google Summer of Code flyer</li>
-
-	    <li>FreeBSD 11 Brochure</li>
-
-	    <li>Updated Recruiting Flyer</li>
-
-	    <li>Updated Get Involved Flyer</li>
-
-	    <li>FreeBSD as a Platform for Research Flyer</li>
-	  </ul>
-	</li>
-
-	<li>Created a series of FreeBSD How-to Guides:
-	  <ul>
-	    <li>Installing FreeBSD with VirtualBox (Mac/Windows)</li>
-
-	    <li>Installing a Desktop Environment on FreeBSD</li>
-
-	    <li>Installing FreeBSD for Raspberry Pi</li>
-
-	    <li>Installing PC-BSD as a Primary Operating System</li>
-
-	    <li>FreeBSD Setup Tips</li>
-	  </ul>
-	</li>
-
-	<li>Acquired New Testimonials:
-	  <ul>
-	    <li>Accelerations Systems</li>
-
-	    <li>NeoSmart Technologies</li>
-
-	    <li>Chelsio Communications</li>
-
-	    <li>Crescent River Port Pilots' Association</li>
-
-	    <li>IXC</li>
-
-	    <li>Stormshield</li>
-	  </ul>
-	</li>
-
-	<li>Updated the FreeBSD Project and Foundation Branding:
-	  <ul>
-	    <li>New FreeBSD Foundation website and logo</li>
-
-	    <li>Updated Brand Assets page to include more information
-	      about the FreeBSD Project and FreeBSD Foundation
-	      logos.</li>
-	  </ul>
-	</li>
-      </ul>
-
-      <p>We published our September/October and November/December
-	Journal issues at
-	<a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>.</p>
-
-      <p>We also published monthly newsletters to highlight work being
-	done to support FreeBSD, tell you about upcoming events, and
-	provide other information to keep you in the loop of what we
-	are doing to support the FreeBSD Project and community:
-	<a href="https://www.FreeBSDfoundation.org/news-and-events/newsletter/" shape="rect">https://www.FreeBSDfoundation.org/news-and-events/newsletter/</a>.</p>
-
-      <p>Conferences and Events</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events, and
-	summits around the globe.  These events can be BSD-related,
-	open source, or technology events geared towards
-	underrepresented groups.</p>
-
-      <p>We support the FreeBSD-focused events to help provide a venue
-	for sharing knowledge, to work together on projects, and to
-	facilitate collaboration between developers and commercial
-	users.  This all helps provide a healthy ecosystem.  We
-	support the non-FreeBSD events to promote and raise awareness
-	of FreeBSD, to increase the use of FreeBSD in different
-	applications, and to recruit more contributors to the
-	Project.</p>
-
-      <p>We also sponsored or attended the following events last
-	quarter:</p>
-
-      <ul>
-	<li>Ohio LinuxFest, October, Columbus, Ohio</li>
-
-	<li>Grace Hopper 2016, October, Houston, TX</li>
-
-	<li>COSC 2016, October, Beijing, China</li>
-
-	<li>Bay Area FreeBSD Vendor and Devoloper's Summit and MeetBSD
-	  2016, November, Berkely, CA</li>
-
-	<li>USENIX LISA '16, December, Boston, MA</li>
-
-	<li>OSC 2016, December, Beijing, China</li>
-      </ul>
-
-      <p>Get the whole list of conferences we supported in 2016 at:
-	<a href="https://www.FreeBSDfoundation.org/blog/recap-of-2016-advocacy-efforts/" shape="rect">https://www.FreeBSDfoundation.org/blog/recap-of-2016-advocacy-efforts/</a>.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them.  We continued to review
-	requests and grant permission to use the trademarks.  We also
-	provided legal support for the core team to investigate the
-	status of certain patents.</p>
-
-      <p>FreeBSD Community Engagement</p>
-
-      <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.  The
-	updated Code of Conduct and Report Guidelines are going
-	through the final review process, and will be handed off to
-	the Core Team for approval in Q1 2017.</p>
-
-      <p>Go to
-	<a href="https://www.FreeBSDfoundation.org" shape="rect">http://www.FreeBSDfoundation.org</a>
-	to find out how we support FreeBSD and how we can help you!</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Ceph-on-FreeBSD" href="#Ceph-on-FreeBSD" id="Ceph-on-FreeBSD">Ceph on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ceph.com" title="http://ceph.com">Ceph Main Site</a></td><td>
-	    URL: <a href="http://ceph.com" title="Ceph Main Site">http://ceph.com</a></td></tr><tr><td><a href="https://github.com/ceph/ceph" title="https://github.com/ceph/ceph">Main Repository</a></td><td>
-	    URL: <a href="https://github.com/ceph/ceph" title="Main Repository">https://github.com/ceph/ceph</a></td></tr><tr><td><a href="https://github.com/wjwithagen/ceph/tree/wip.FreeBSD" title="https://github.com/wjwithagen/ceph/tree/wip.FreeBSD">My FreeBSD Fork</a></td><td>
-	    URL: <a href="https://github.com/wjwithagen/ceph/tree/wip.FreeBSD" title="My FreeBSD Fork">https://github.com/wjwithagen/ceph/tree/wip.FreeBSD</a></td></tr></table><p>
-	Contact:
-	  Willem Jan
-	  Withagen
-	 &lt;<a href="mailto:wjw@digiware.nl">wjw@digiware.nl</a>&gt;
-	</p>
-      <p>Ceph is a distributed object store and file system designed
-	to provide excellent performance, reliability and
-	scalability:</p>
-
-      <ul>
-	<li>
-	  <p>Object Storage</p>
-
-	  <p>Ceph provides seamless access to objects using native
-	    language bindings or <tt>radosgw</tt>, a REST interface that is
-	    compatible with applications written for S3 and
-	    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>
-
-	  <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>
-      </ul>
-
-      <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 disks that are stored in Ceph.</p>
-
-      <p>The FreeBSD build of Ceph includes most of the tools Ceph provides.  Note
-	that the RBD-dependent items will not work, since FreeBSD does
-	not have RBD (yet).</p>
-
-      <p>The 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
-	  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 FreeBSD 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/" shape="rect">http://cephdev.digiware.nl:8180/jenkins/</a>.</li>
-      </ul>
-
-
-      <p>Build Prerequisites</p>
-
-      <p>Compiling and building Ceph is tested on 12-CURRENT with
-	its clang 3.9.0, but 11-RELEASE will probably also work, given
-	experience with clang 3.7.0 from 11-CURRENT.  Interestingly,
-	when 12-CURRENT had clang 3.8.0, that did not work as well as
-	either 3.7.0 or 3.9.0.  The clang 3.4 present in 10-STABLE
-	does not have the required capabilities to compile
-	everything.</p>
-
-      <p>The following setup will get things running for FreeBSD:</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
-	  (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>
-      </ol>
-
-      <p>The old build method using automake is no longer used; see
-	the README.FreeBSD for more details.</p>
-
-      <p>Parts not (yet) included:</p>
-
-      <ul>
-	<li>KRBD: Kernel Rados Block Devices is implemented in the Linux
-	  kernel, but not in the FreeBSD 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: FreeBSD and Linux have different AIO APIs, and
-	  that incompatibility needs to be resolved somehow.
-	  Additionally, there is discussion in FreeBSD 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>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Run integration tests to see if the FreeBSD daemons will work
-	with a Linux Ceph platform.</li><li>Compile and test the user space RBD (Rados Block Device).
-	This currently works, but testing has been limitted.</li><li>Investigate and see if an in-kernel RBD device could be
-	developed akin to FreeBSD's <tt>ggate</tt>.</li><li>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.</li><li>Scheduler information is not used at the moment, because
-	the schedulers work rather differently between FreeBSD and Linux.
-	But at a certain point in time, this would need some attention
-	in <tt>src/common/Thread.cc</tt>.</li><li>Integrate the FreeBSD <tt>/etc/rc.d</tt> initscripts in the
-	Ceph stack.  This helps with testing, but also enables running
-	Ceph on production machines.</li><li>Build a testcluster and start running some of the
-	<tt>teuthology</tt> integration tests on it.</li><li>Design a virtual disk implementation that can be used with
-	<tt>bhyve</tt> and attached to an RBD image.</li></ol><hr /><h2><a name="OpenBSM" href="#OpenBSM" id="OpenBSM">OpenBSM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openbsm.org" title="http://www.openbsm.org">OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation</a></td><td>
-	    URL: <a href="http://www.openbsm.org" title="OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation">http://www.openbsm.org</a></td></tr><tr><td><a href="https://github.com/openbsm/openbsm" title="https://github.com/openbsm/openbsm">OpenBSM on GitHub</a></td><td>
-	    URL: <a href="https://github.com/openbsm/openbsm" title="OpenBSM on GitHub">https://github.com/openbsm/openbsm</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html">FreeBSD Audit Handbook Chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html" title="FreeBSD Audit Handbook Chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/pipermail/trustedbsd-announce/2016-December/000008.html" title="https://lists.FreeBSD.org/pipermail/trustedbsd-announce/2016-December/000008.html">OpenBSM 1.2 alpha 5 announcement</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/pipermail/trustedbsd-announce/2016-December/000008.html" title="OpenBSM 1.2 alpha 5 announcement">https://lists.FreeBSD.org/pipermail/trustedbsd-announce/2016-December/000008.html</a></td></tr><tr><td><a href="https://www.cl.cam.ac.uk/research/security/cadets/" title="https://www.cl.cam.ac.uk/research/security/cadets/">DARPA CADETS project</a></td><td>
-	    URL: <a href="https://www.cl.cam.ac.uk/research/security/cadets/" title="DARPA CADETS project">https://www.cl.cam.ac.uk/research/security/cadets/</a></td></tr></table><p>
-	Contact:
-	  Christian
-	  Brueffer
-	 &lt;<a href="mailto:brueffer@FreeBSD.org">brueffer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  TrustedBSD Audit Mailing Mist
-	 &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <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 FreeBSD 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
-	specify the kernel's maximum audit queue length, sandboxing
-	support for <tt>auditreduce(1)</tt> and <tt>praudit(1)</tt> on
-	FreeBSD and other systems that support Capsicum, as well as the
-	addition of event identifiers for more FreeBSD system calls.  The
-	complete list of changes is documented in the
-	<a href="https://github.com/openbsm/openbsm/blob/master/NEWS" shape="rect">NEWS</a>
-	file on GitHub.  The new release will be merged into FreeBSD HEAD
-	and the supported STABLE branches shortly.</p>
-    <p>This project was sponsored by DARPA/AFRL (in part).</p><h3>Open tasks:</h3><ol><li>Test the new release on different versions of FreeBSD, Mac OS
-	X, and Linux.  In particular, testing on the latest versions
-	of Mac OS X would be greatly appreciated.</li><li>Fix problems that have been reported via GitHub and the
-	FreeBSD bug tracker.</li><li>Implement the features mentioned in the
-	<a href="https://github.com/openbsm/openbsm/blob/master/TODO" shape="rect">TODO</a>
-	list on GitHub.</li></ol><hr /><h2><a name="Sysctl-Exporter-for-Prometheus" href="#Sysctl-Exporter-for-Prometheus" id="Sysctl-Exporter-for-Prometheus">Sysctl Exporter for Prometheus</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://prometheus.io/" title="https://prometheus.io/">The Prometheus Project</a></td><td>
-	    URL: <a href="https://prometheus.io/" title="The Prometheus Project">https://prometheus.io/</a></td></tr><tr><td><a href="https://github.com/prometheus/node_exporter" title="https://github.com/prometheus/node_exporter">Node Exporter</a></td><td>
-	    URL: <a href="https://github.com/prometheus/node_exporter" title="Node Exporter">https://github.com/prometheus/node_exporter</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base/head/usr.sbin/prometheus_sysctl_exporter/" title="https://svnweb.FreeBSD.org/base/head/usr.sbin/prometheus_sysctl_exporter/">Sysctl Exporter</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base/head/usr.sbin/prometheus_sysctl_exporter/" title="Sysctl Exporter">https://svnweb.FreeBSD.org/base/head/usr.sbin/prometheus_sysctl_exporter/</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <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>
-
-      <p>The Prometheus project provides a utility called
-	<tt>node_exporter</tt> 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 FreeBSD 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>
-
-      <p>An initial version of the sysctl exporter has been integrated
-	into the FreeBSD base system in December.  It can be run through
-	<tt>inetd</tt> by uncommenting the example provided in
-	<tt>inetd.conf</tt>.  Unfortunately, this exporter cannot be
-	merged back to FreeBSD 10.x/11.x, as it depends on KBI-breaking
-	changes to <tt>sysctl(9)</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>Are you using Prometheus or are you interested in using
-	it?  Be sure to give both Prometheus and this <tt>sysctl</tt>
-	exporter a try!</li><li>It would be nice if we created a set of useful alerting
-	rules and placed those in <tt>/usr/share/examples</tt>.  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>?</li><li>Prometheus uses a rather clever format for exporting
-	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
-	data types to <tt>sysctl</tt>?  If so, is there any chance they can be
-	implemented without picking up any kernel locks?</li></ol><hr /><h2><a name="The-Graphics-Stack-on-FreeBSD" href="#The-Graphics-Stack-on-FreeBSD" id="The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Graphics" title="https://wiki.FreeBSD.org/Graphics">Graphics Stack Roadmap and Supported Hardware Matrix</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Graphics" title="Graphics Stack Roadmap and Supported Hardware Matrix">https://wiki.FreeBSD.org/Graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/freebsd-base-graphics" title="https://github.com/FreeBSDDesktop/freebsd-base-graphics">GitHub Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop/freebsd-base-graphics" title="GitHub Repository">https://github.com/FreeBSDDesktop/freebsd-base-graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSD/freebsd-ports-graphics" title="https://github.com/FreeBSD/freebsd-ports-graphics">Ports Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/freebsd-ports-graphics" title="Ports Development Repository">https://github.com/FreeBSD/freebsd-ports-graphics</a></td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/libudev-devd" title="https://github.com/FreeBSDDesktop/libudev-devd">Fork of libudevd-devd Shim</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop/libudev-devd" title="Fork of libudevd-devd Shim">https://github.com/FreeBSDDesktop/libudev-devd</a></td></tr><tr><td><a href="https://planet.FreeBSD.org/graphics" title="https://planet.FreeBSD.org/graphics">Graphics Team Blog</a></td><td>
-	    URL: <a href="https://planet.FreeBSD.org/graphics" title="Graphics Team Blog">https://planet.FreeBSD.org/graphics</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:FreeBSD-x11@FreeBSD.org">FreeBSD-x11@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Matthew
-	  Macy
-	 &lt;<a href="mailto:mmacy@nextbsd.org">mmacy@nextbsd.org</a>&gt;
-	</p>
-      <p>Good progress on graphics support was made during the weeks
-	around Christmas and the new year with the import of Linux
-	4.9's 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
-	<tt>pg_populate</tt>.  This new interface is the source of a couple of
-	regressions causing panics on <tt>i915</tt> and severe artifacts with
-	<tt>amdgpu</tt> 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
-	newer AMD GPUs.  It uses a fork of the <tt>libudev-devd</tt> shim, also
-	bringing Mesa closer to the Linux upstream.  I plan to keep
-	updating <tt>drm</tt> and <tt>amdgpu</tt> (for use on my
-	desktop and potentially longer term for GPGPU computations) as
-	well as work with Mark to address the existing bugs in
-	<tt>i915</tt> (assuming that two new porters are approved).
-	However, the Linux <tt>i915</tt> developers seem to
-	aggressively explore the space of possible implementations and
-	use of Linux internal APIs, making it prohibitively time
-	consuming to track upstream.  I am helping someone to learn
-	the ropes of how to replay a subset of changes from a Linux
-	release into FreeBSD in the hope that he will take over the
-	mantle of drm-next <tt>i915</tt> maintainer.  Assuming the
-	issues listed above are addressed, a port of the linuxkpi,
-	DRM, and KMS drivers for use on standard amd64 CURRENT
-	installations is planned.  Together with upgrades to the
-	relevant graphics ports, this will provide experimental
-	support for new AMD and Intel GPUs.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="FreeBSD-on-Hyper-V-and-Azure" href="#FreeBSD-on-Hyper-V-and-Azure" id="FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/HyperV" title="https://wiki.FreeBSD.org/HyperV">FreeBSD Virtual Machines on Microsoft Hyper-V</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/HyperV" title="FreeBSD Virtual Machines on Microsoft Hyper-V">https://wiki.FreeBSD.org/HyperV</a></td></tr><tr><td><a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="https://technet.microsoft.com/en-us/library/dn531030.aspx">Supported Linux and FreeBSD Virtual Machines for Hyper-V on Windows</a></td><td>
-	    URL: <a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="Supported Linux and FreeBSD Virtual Machines for Hyper-V on Windows">https://technet.microsoft.com/en-us/library/dn531030.aspx</a></td></tr></table><p>
-	Contact:
-	  Sepherosa
-	  Ziehau
-	 &lt;<a href="mailto:sepherosa@gmail.com">sepherosa@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Hongjiang
-	  Zhang
-	 &lt;<a href="mailto:honzhan@microsoft.com">honzhan@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Dexuan
-	  Cui
-	 &lt;<a href="mailto:decui@microsoft.com">decui@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Kylie
-	  Liang
-	 &lt;<a href="mailto:kyliel@microsoft.com">kyliel@microsoft.com</a>&gt;
-	</p>
-      <p>This project provides native virtualized interfaces
-	for FreeBSD systems running on Hyper-V virtualization, improving
-	on the performance of traditional emulated evices.</p>
-
-      <p>Per-ring polling, multi-packet RNDIS messages, and system RSS
-	integration have been implemented, further optimizing the
-	throughput and latency of the Hyper-V network driver.</p>
-
-      <p>Live virtual machine backup is implemented (for now, only for
-	UFS), after the VSS (Volume Shadow Copy Service), which it
-	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>
-
-      <p>vDSO support for speeding up <tt>gettimeofday(2)</tt> is now
-	implemented.</p>
-
-      <p>The FreeBSD 11.0 image on Azure (<a href="https://azure.microsoft.com/en-us/marketplace/partners/microsoft/FreeBSD110/" shape="rect">https://azure.microsoft.com/en-us/marketplace/partners/microsoft/FreeBSD110/</a>)
-	is now available, in addition to the existing 10.3
-	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>
-    <p>This project was sponsored by Microsoft.</p><hr /><h2><a name="I2C,-GPIO,-and-SPI-Support-for-MinnowBoard" href="#I2C,-GPIO,-and-SPI-Support-for-MinnowBoard" id="I2C,-GPIO,-and-SPI-Support-for-MinnowBoard">I2C, GPIO, and SPI Support for MinnowBoard</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://kernelnomicon.org/?p=767" title="https://kernelnomicon.org/?p=767">Blog Post</a></td><td>
-	    URL: <a href="https://kernelnomicon.org/?p=767" title="Blog Post">https://kernelnomicon.org/?p=767</a></td></tr><tr><td><a href="https://www.minnowboard.org" title="https://www.minnowboard.org">MinnowBoard Website</a></td><td>
-	    URL: <a href="https://www.minnowboard.org" title="MinnowBoard Website">https://www.minnowboard.org</a></td></tr></table><p>
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <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 FreeBSD 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 the
-	<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>
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-ARM-Boards" href="#FreeBSD-on-ARM-Boards" id="FreeBSD-on-ARM-Boards">FreeBSD on ARM Boards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner">FreeBSD on Allwinner (Sunxi) Systems</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="FreeBSD on Allwinner (Sunxi) Systems">https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=307984" title="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=307984">FreeBSD Commit Adding Support for IR Interfaces</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=307984" title="FreeBSD Commit Adding Support for IR Interfaces">https://svnweb.FreeBSD.org/base?view=revision&amp;revision=307984</a></td></tr></table><p>
-	Contact:
-	  Ganbold
-	  Tsagaankhuu
-	 &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>The changes necessary to support the Allwinner Consumer IR
-	interface in FreeBSD 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>
-    <hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64" title="https://wiki.FreeBSD.org/arm64">FreeBSD arm64 Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/arm64" title="FreeBSD arm64 Wiki Page">https://wiki.FreeBSD.org/arm64</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Oleksandr
-	  Tymoshenko
-	 &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for accessing floating-point registers from the kernel has been
-	added.  This uses the same KPI as i386 and amd64.  This will
-	allow for handling places where the floating-point state may
-	be modified, for example when calling into UEFI.</p>
-
-      <p>Support for the optional ARMv8 AES instructions was added to
-	the kernel.  This makes use of the ability to store and
-	restore the floating point state.  Tests have shown a
-	significant improvement in AES performance on ThunderX
-	hardware.</p>
-
-      <p>The Cortex Strings <tt>memcpy</tt> and <tt>memmove</tt>
-	functions have been imported into the kernel.  These are
-	optimised implementations of these common functions.</p>
-
-      <p>FreeBSD now boots on the SoftIron Overdrive 3000 using ACPI.
-	The needed changes for this have been submitted to phabricator
-	for review.  This includes booting with SMP enabled, and all
-	currently supported devices.</p>
-
-      <p>Support for the Raspberry Pi 3 has been committed.  Most
-	devices work, with the exception of WiFi and Bluetooth, as
-	these are attached via an as-yet unsupported SDIO bus.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, and ABT Systems Ltd.</p><hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><p>
-	Contact:
-	  Colin
-	  Percival
-	 &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p>
-      <p>This report covers work since the last FreeBSD/EC2 status report
-	(2015Q1).</p>
-
-      <p>FreeBSD/EC2 is now part of the regular FreeBSD release build,
-	with snapshots and releases being automatically uploaded and
-	copied to all available regions.  Due to legal restrictions,
-	this does not currently include the GovCloud or China
-	(Beijing) regions; anyone wishing to use FreeBSD in those regions
-	is encouraged to contact the author.</p>
-
-      <p>The AWS Marketplace reports that approximately 800 users
-	are running roughly 2000 FreeBSD EC2 instances.  This does not
-	count the likely significantly larger number of EC2 instances
-	launched directly through the EC2 API and Console, but at
-	least places a lower bound on usage.</p>
-
-      <p>FreeBSD 11.0-RELEASE shipped with support for the "enhanced
-	networking" capabilities of 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 FreeBSD.</p>
-
-      <p>FreeBSD 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>
-
-      <p> FreeBSD now supports the Amazon Simple Systems Manager service
-	("run command").</p>
-    <h3>Open tasks:</h3><ol><li>Complete a pending reorganization of the accounts used for
-	FreeBSD/EC2 releases.</li><li>Support "second generation enhanced networking"
-	via the new Elastic Network Adapter found in P2, R4, X1, and
-	m4.16xlarge instances.</li><li>Provide tools for improved functionality via the Simple
-	Systems Manager service: listing installed packages, checking
-	for updates, adding/removing users, [your favourite sysadmin
-	task goes here].</li><li>Add support for EC2's IPv6 networking to the default
-	FreeBSD/EC2 configuration.</li><li>Continue ongoing interoperability testing between FreeBSD's
-	NFS client and the Amazon Elastic File System
-	(NFS-as-a-service).</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="libarchive" href="#libarchive" id="libarchive">libarchive</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.libarchive.org" title="http://www.libarchive.org">Official Libarchive Homepage</a></td><td>
-	    URL: <a href="http://www.libarchive.org" title="Official Libarchive Homepage">http://www.libarchive.org</a></td></tr><tr><td><a href="https://github.com/libarchive/libarchive" title="https://github.com/libarchive/libarchive">Libarchive on GitHub</a></td><td>
-	    URL: <a href="https://github.com/libarchive/libarchive" title="Libarchive on GitHub">https://github.com/libarchive/libarchive</a></td></tr></table><p>
-	Contact:
-	  Tim
-	  Kientzle
-	 &lt;<a href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Martin
-	  Matuska
-	 &lt;<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>&gt;
-	</p>
-      <p>Libarchive is a BSD-licensed archive and compression library
-	originally developed as part of FreeBSD.  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 FreeBSD <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
-	functions.</p>
-
-      <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>
-
-      <p>Over the last few months, NFSv4 ACL support for the pax and
-	restricted pax (the default for <tt>bsdtar</tt>) formats has
-	been completed and merged to FreeBSD-CURRENT.  NFSv4 ACL entries
-	can now be stored to and restored from tar archives.</p>
-    <h3>Open tasks:</h3><ol><li>More extensive CI testing with FreeBSD on different platforms
-	and releases.  Currently only 11.0-RELEASE-amd64 gets tested
-	via an automated Jenkins job.</li><li>As every commit to <tt>libarchive</tt> may influence the build
-	process of FreeBSD ports, the ability to trigger a
-	(semi-)automated exp-run for the ports tree would be
-	great.</li></ol><hr /><h2><a name="Reproducible-Builds-in-FreeBSD" href="#Reproducible-Builds-in-FreeBSD" id="Reproducible-Builds-in-FreeBSD">Reproducible Builds in FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/ReproducibleBuilds" title="https://wiki.FreeBSD.org/ReproducibleBuilds">Base System Reproducible Builds Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/ReproducibleBuilds" title="Base System Reproducible Builds Wiki Page">https://wiki.FreeBSD.org/ReproducibleBuilds</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/PortsReproducibleBuilds" title="https://wiki.FreeBSD.org/PortsReproducibleBuilds">Ports Reproducible Builds Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/PortsReproducibleBuilds" title="Ports Reproducible Builds Wiki Page">https://wiki.FreeBSD.org/PortsReproducibleBuilds</a></td></tr><tr><td><a href="https://reproducible-builds.org/" title="https://reproducible-builds.org/">Reproducible Builds Website</a></td><td>
-	    URL: <a href="https://reproducible-builds.org/" title="Reproducible Builds Website">https://reproducible-builds.org/</a></td></tr></table><p>
-	Contact:
-	  Baptiste
-	  Daroussin
-	 &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>Reproducible builds are a set of software development
-	practices which create a verifiable path from human readable
-	source code to the binary code used by computers.  A build is
-	reproducible if given the same source code, build environment
-	and build instructions, any party can recreate bit-for-bit
-	identical copies of all specified artifacts.</p>
-
-      <p>Baptiste Daroussin and Ed Maste attended the second
-	Reproducible Builds Summit last December, in Berin.  We
-	discussed issues of common interest to operating system
-	providers, including other BSDs and Linux distributions.</p>
-
-      <p>Following the summit, changes were committed to the FreeBSD
-	base system to address outstanding sources of
-	non-reproducibility.  It is now possible to build the FreeBSD
-	base system (kernel and userland) completely reproducibly,
-	although it currently requires a few non-default settings.</p>
-
-      <p>Approximately 80% of the ports tree builds reproducibly,
-	with a few work-in-progress patches.  Now that the base system
-	can be built reproducibly, focus will move on to the ports
-	tree.</p>
-    <p>This project was sponsored by The FreeBSD Foundation, and The Linux Foundation.</p><h3>Open tasks:</h3><ol><li>Integrate FreeBSD ports builds into the
-	reprodcible-builds.org continuous integration
-	infrastructure.</li><li>Integrate reproducible build patches into the ports
-	tree.</li><li>Investigate sources of non-reproducibility in individual
-	ports.</li></ol><hr /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Luca
-	  Pizzamiglio
-	 &lt;<a href="mailto:luca.pizzamiglio@gmail.com">luca.pizzamiglio@gmail.com</a>&gt;
-	</p>
-      <p>The <tt>devel/gdb</tt> port has been updated to GDB 7.12.</p>
-
-      <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>
-
-      <p>Support for FreeBSD/mips userland binaries has been committed
-	upstream.  These patches, along with support for debugging
-	FreeBSD/mips kernels, should be added to the port soon.</p>
-    <h3>Open tasks:</h3><ol><li>Figure out why the powerpc <tt>kgdb</tt> targets are not
-	able to unwind the stack past the initial frame.</li><li>Add support for more platforms (arm, aarch64) to upstream
-	<tt>gdb</tt> for both userland and <tt>kgdb</tt>.</li><li>Add support for debugging powerpc vector registers.</li><li>Add support for <tt>$_siginfo</tt>.</li><li>Implement 'info proc' commands.</li><li>Implement 'info os' commands.</li><li>Debug <tt>gdb</tt> hangs related to the 'kill'
-	command.</li></ol><hr /><h2><a name="Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker" href="#Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker" id="Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker">Using LLVM's LLD Linker as FreeBSD's System Linker</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/LLD" title="https://wiki.FreeBSD.org/LLD">FreeBSD LLD Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/LLD" title="FreeBSD LLD Wiki Page">https://wiki.FreeBSD.org/LLD</a></td></tr><tr><td><a href="http://llvm.org/pr23214" title="http://llvm.org/pr23214">FreeBSD/LLD Tracking PR (LLVM Bugzilla)</a></td><td>
-	    URL: <a href="http://llvm.org/pr23214" title="FreeBSD/LLD Tracking PR (LLVM Bugzilla)">http://llvm.org/pr23214</a></td></tr></table><p>
-	Contact:
-	  Rafael
-	  Esp�ndola
-	 &lt;<a href="mailto:rafael.espindola@gmail.com">rafael.espindola@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLD is the linker in the LLVM family of projects.  It is a
-	high-performance linker that supports the ELF, COFF and Mach-O
-	object formats.  It aims to be compatible with the common
-	linkers used for each file format.  For ELF this is the GNU
-	Binary File Descriptor (BFD) ld and GNU gold.  However, LLD's
-	authors are not constrained by strict compatibility where it
-	would hamper performance or desired functionality.</p>
-
-      <p>LLD developers made significant progress over the last
-	quarter.  With changes committed to both LLD and FreeBSD we
-	reached a major milestone: it is now possible to link the
-	entire FreeBSD/amd64 base system (kernel and userland)
-	with LLD.</p>
-
-      <p>Now that the base system links with LLD, we have started
-	investigating linking applications in the ports tree with LLD.
-	Through this process we are identifying limitations or bugs in
-	both LLD and a number of FreeBSD ports.  With a few
-	work-in-progress patches we can link approximately 95% of the
-	ports collection with LLD on amd64.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Fix <tt>libtool</tt> to detect LLD and pass the same
-	command line arguments as for GNU ld and gold.</li><li>Investigate the remaining amd64 port build
-	failures.</li><li>Investigate and improve LLD on arm64, i386, arm, and
-	other non-amd64 architectures.</li><li>Extensive testing.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="GCC-(GNU-Compiler-Collection)" href="#GCC-(GNU-Compiler-Collection)" id="GCC-(GNU-Compiler-Collection)">GCC (GNU Compiler Collection)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gcc.gnu.org" title="https://gcc.gnu.org">GCC Home Page</a></td><td>
-	    URL: <a href="https://gcc.gnu.org" title="GCC Home Page">https://gcc.gnu.org</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Andreas
-	  Tobler
-	 &lt;<a href="mailto:andreast@FreeBSD.org">andreast@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Antoine
-	  Brodin
-	 &lt;<a href="mailto:antoine@FreeBSD.org">antoine@FreeBSD.org</a>&gt;
-	</p>
-      <p>Long awaited, the update to GCC 4.9 as the default version of
-	GCC in the Ports Collection (<tt>lang/gcc</tt> port,
-	<tt>USE_GCC=yes</tt> in Makefiles) has arrived, an update from GCC
-	4.8. This brings quite a number of improvements; see
-	<a href="https://gcc.gnu.org/gcc-4.9/changes.html" shape="rect">https://gcc.gnu.org/gcc-4.9/changes.html</a>
-	for details.</p>
-
-      <p><tt>lang/gcc49</tt> has moved to the GCC 4.9.4 release which
-	marks the closure of the GCC 4.9 branch and release
-	series.</p>
-
-      <p>(Yes, this means we should rather get the next version
-	upgrade for <tt>lang/gcc</tt> in place soon.  That update per
-	se is straightforward, but any help in addressing the fallout
-	of broken ports would be great &#8212; please let us know if
-	you want to help!)</p>
-
-      <p><tt>lang/gcc6</tt> has been updated first to GCC 6.2 and then
-	GCC 6.3, bringing a fair number of fixes, and should now be
-	suitable for production use.</p>
-    <h3>Open tasks:</h3><ol><li>Update <tt>lang/gcc</tt> (and hence <tt>USE_GCC=yes</tt>)
-	to GCC 5.</li><li>Support for AArch64.</li></ol><hr /><h2><a name="LXQt-on-FreeBSD" href="#LXQt-on-FreeBSD" id="LXQt-on-FreeBSD">LXQt on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lxqt.org/" title="http://lxqt.org/">LXQt Project</a></td><td>
-	    URL: <a href="http://lxqt.org/" title="LXQt Project">http://lxqt.org/</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/LXQt" title="https://wiki.FreeBSD.org/LXQt">FreeBSD LXQt Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/LXQt" title="FreeBSD LXQt Project">https://wiki.FreeBSD.org/LXQt</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/lxqt/subversion/source" title="https://www.assembla.com/spaces/lxqt/subversion/source">LXQt Development Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/lxqt/subversion/source" title="LXQt Development Repository">https://www.assembla.com/spaces/lxqt/subversion/source</a></td></tr></table><p>
-	Contact:
-	  Olivier
-	  Duchateau
-	 &lt;<a href="mailto:olivierd@FreeBSD.org">olivierd@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Jesper
-	  Schmitz Mouridsen
-	 &lt;<a href="mailto:jesper@schmitz.computer">jesper@schmitz.computer</a>&gt;
-	</p>
-      <p>LXQt is the Qt port of and the upcoming version of LXDE, the
-	Lightweight Desktop Environment.  It is the product of a merge
-	between the LXDE-Qt and Razor-qt projects.</p>
-
-      <p>The porting effort remains very much a work in progress: LXQt
-	requires some components of Plasma 5, the new major KDE
-	workspace.</p>
-
-      <p>We imported some core components (it was necessary to update
-	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>
-      </ul>
-
-      <p>Standalone applications:</p>
-
-      <ul>
-	<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" shape="rect">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650</a>)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Improve support in <tt>sysutils/lxqt-admin</tt>
-	(especially date and time settings).</li></ol><hr /><h2><a name="Mono" href="#Mono" id="Mono">Mono</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mono-project.com/" title="http://www.mono-project.com/">Mono Homepage</a></td><td>
-	    URL: <a href="http://www.mono-project.com/" title="Mono Homepage">http://www.mono-project.com/</a></td></tr><tr><td><a href="https://github.com/dotnet/core" title="https://github.com/dotnet/core">.NET Core Homepage</a></td><td>
-	    URL: <a href="https://github.com/dotnet/core" title=".NET Core Homepage">https://github.com/dotnet/core</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/Mono" title="https://wiki.FreeBSD.org/Mono">Mono Project Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Mono" title="Mono Project Page">https://wiki.FreeBSD.org/Mono</a></td></tr></table><p>
-	Contact: Mono on FreeBSD team &lt;<a href="mailto:mono@FreeBSD.org">mono@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the last quarter, many ports within the mono project
-	have been updated:</p>
-
-      <ul>
-	<li>Mono: 4.6.2.7</li>
-
-	<li>MonoDevelop: 6.1.1.15, 6.1.2.44</li>
-
-	<li>FSharp: 4.0.1.20</li>
-      </ul>
-
-      <p><tt>USES=mono</tt> has been extended to allow for easier use
-	of Nuget packages.  This extension has been used adopted by
-	FSharp, MonoDevelop and OpenRA.</p>
-
-      <p>Work has started on porting Microsoft's open-sourced
-	.NET Core.  Thanks to the work of another team, the native
-	components of <tt>coreclr</tt> and <tt>corefx</tt> already
-	support FreeBSD, however, there is further work required in
-	bootstrapping the build process and compiling the managed
-	code.</p>
-    <h3>Open tasks:</h3><ol><li>Port .NET Core.</li><li>Test patches for Mono.</li></ol><hr /><h2><a name="Wine" href="#Wine" id="Wine">Wine</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.winehq.org/" title="https://www.winehq.org/">Wine Homepage</a></td><td>
-	    URL: <a href="https://www.winehq.org/" title="Wine Homepage">https://www.winehq.org/</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Wine" title="https://wiki.freebsd.org/Wine">Project Page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Wine" title="Project Page">https://wiki.freebsd.org/Wine</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  David
-	  Naylor
-	 &lt;<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>&gt;
-	</p>
-      <p>The stable version of Wine (aka <tt>emulators/wine</tt>) has
-	seen three maintenance releases in the last half year, and
-	Xinerama support (in case you have more than one screen) and
-	GNUTLS (helpful for Evernote or World of Warcraft, for
-	example) are now active by default.</p>
-
-      <p>The development version (aka <tt>emulators/wine-devel</tt>)
-	has seen steady progress and reached the RC phase of Wine 2.0.
-	We are looking forward to a new major release soon that
-	combines the progress of a year of active development with the
-	stability of a release.</p>
-    <h3>Open tasks:</h3><ol><li>Port WoW64</li></ol><hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Xfce" title="https://wiki.FreeBSD.org/Xfce">FreeBSD Xfce Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Xfce" title="FreeBSD Xfce Project">https://wiki.FreeBSD.org/Xfce</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="https://www.assembla.com/spaces/xfce4/subversion/source">FreeBSD Xfce Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="FreeBSD Xfce Repository">https://www.assembla.com/spaces/xfce4/subversion/source</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms such as FreeBSD.  It aims to be fast and
-	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>
-
-      <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>
-      </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+
-	    &gt; 3.20)</li>
-
-	<li><tt>x11/libexo</tt> 0.11.2</li>
-
-	<li><tt>x11/xfce4-whiskermenu-plugin</tt> 2.0.3</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Apply the changes discussed in
-	<a href="https://reviews.FreeBSD.org/D8416" shape="rect">D8416</a>
-	(simplify the <tt>MASTER_SITES</tt> macro in port
-	Makefiles).</li><li>Commit the stable panel plugins.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2017-01-2017-03.html b/website/content/en/status/report-2017-01-2017-03.html
deleted file mode 100644
index aad5c3e851..0000000000
--- a/website/content/en/status/report-2017-01-2017-03.html
+++ /dev/null
@@ -1,1278 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>While a few of these projects indicate they are a
-      "plan�B" or an "attempt III", many
-      are still hewing to their original plans, and all have
-      produced impressive results.  Please enjoy this vibrant
-      collection of reports, covering the first quarter of 2017.</p><p>&#8212;Benjamin Kaduk</p><p><hr /></p><p>The deadline for submissions covering the period from April
-      to June 2017 is July 7, 2017.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li><li><a href="#The-FreeBSD-Ports-Collection">The FreeBSD Ports Collection</a></li><li><a href="#The-FreeBSD-Release-Engineering-Team">The FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Ceph-on-FreeBSD">Ceph on FreeBSD</a></li><li><a href="#OpenBSM">OpenBSM</a></li><li><a href="#Porting-Software-to-CloudABI:-Sandboxed-Bitcoin!">Porting Software to CloudABI: Sandboxed Bitcoin!</a></li><li><a href="#Support-for-eMMC-Flash-and-Faster-SD-Card-Modes">Support for eMMC Flash and Faster SD Card Modes</a></li><li><a href="#TrustedBSD">TrustedBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></li><li><a href="#Intel-10G-and-40G-Network-Driver-Updates">Intel 10G and 40G Network Driver Updates</a></li><li><a href="#Linuxulator">Linuxulator</a></li><li><a href="#MMC-Stack-Using-the-CAM-Framework">MMC Stack Using the CAM Framework</a></li><li><a href="#pNFS-Server-Plan-B">pNFS Server Plan B</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#64-bit-PowerPC-Book-E-Support">64-bit PowerPC Book-E Support</a></li><li><a href="#FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></li><li><a href="#FreeBSD/s390x-Attempt-III">FreeBSD/s390x Attempt III</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#MySQL">MySQL</a></li><li><a href="#Rust">Rust</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>Core's primary function is to ensure the long-term viability of
-	the FreeBSD project.  A very large part of that is to ensure that the
-	interactions between developers remain cordial, and consequently
-	that the project appears welcoming to newcomers.</p>
-
-      <p>Normally, most of Core's activities around this are done in
-	private &#8212; a quiet word in the right ear, some discrete
-	peacemaking, occasional reading of the riot act.  Most of the time,
-	this is all that is necessary.</p>
-
-      <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.  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,
-	the project was better off overall to sever his connection to
-	itself, and core backed them up in that.  We are sorry that
-	events came to this sad conclusion, but we remain convinced
-	that this was a necessary step to safeguard the character of
-	our community.</p>
-
-      <p>In a more positive light, Core has been working on a proposal
-	to recognise notable contributors to the FreeBSD 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
-	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 FreeBSD events
-	or who promote FreeBSD through social media.  A formal announcement
-	of Core's proposal is imminent.</p>
-
-      <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
-	were not planning to resume working on FreeBSD 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
-	several years ago, and we needed to clear the decks before
-	restarting.  Ultimately, this resulted in some 20
-	developers-emeritus handing in their commit bits.</p>
-
-      <p>No new commit bits were awarded during this quarter.</p>
-
-      <p>Core is also taking soundings on producing a 10.4-RELEASE.
-	This is not in the current plan, but a number of developers and
-	important FreeBSD 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 represent an additional
-	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
-	not result in extending the support lifetime of the stable/10
-	branch.</p>
-
-      <p>In other news, Core arranged for the old and largely inactive
-	marketing@FreeBSD.org mailing list to be wound up, and for any
-	remaining activities to be transferred to the FreeBSD Foundation.</p>
-
-      <p>Core also asked clusteradm to turn off Internet-wide access to
-	the <tt>finger</tt> server on freefall.freebsd.org.  Many
-	developers have included details such as phone numbers into
-	the GECOS field of their FreeBSD password database entries, and
-	these would be revealed by the <tt>finger</tt> server &#8212;
-	details which are nowadays generally felt inadvisable to
-	expose publicly.  <tt>finger</tt> is still available
-	internally within freefall.freebsd.org.  Core recommends that
-	GECOS data is limited to just your full name, and we have
-	updated the standard "new committer" e-mail template
-	to reflect that.</p>
-
-      <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 the Security Team are in need of new blood.
-	Recruiting for a new member of the Security Team is well under way, 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>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSDFoundation.org/" title="https://www.FreeBSDFoundation.org/">FreeBSD Foundation Website</a></td><td>
-	    URL: <a href="https://www.FreeBSDFoundation.org/" title="FreeBSD Foundation Website">https://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/03/FreeBSD-Foundation-Q1-2017-Update.pdf" title="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/03/FreeBSD-Foundation-Q1-2017-Update.pdf">Quarterly Newsletter</a></td><td>
-	    URL: <a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/03/FreeBSD-Foundation-Q1-2017-Update.pdf" title="Quarterly Newsletter">https://www.FreeBSDfoundation.org/wp-content/uploads/2017/03/FreeBSD-Foundation-Q1-2017-Update.pdf</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/201702StorageSummit" title="https://wiki.FreeBSD.org/201702StorageSummit">2017 Storage Summit</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/201702StorageSummit" title="2017 Storage Summit">https://wiki.FreeBSD.org/201702StorageSummit</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit organization
-	dedicated to supporting and promoting the FreeBSD Project and
-	community worldwide.  Funding comes from individual and
-	corporate donations and is used to fund and manage software
-	development projects, conferences and developer summits, and
-	provide travel grants to FreeBSD contributors.  The Foundation
-	purchases and supports hardware to improve and maintain FreeBSD
-	infrastructure; publishes marketing material to promote,
-	educate, and advocate for the FreeBSD Project; facilitates
-	collaboration between commercial vendors and FreeBSD
-	developers; and finally, represents the FreeBSD Project in
-	executing contracts, license agreements, and other legal
-	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,
-	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
-	to ask for financial contributions to help us keep FreeBSD the
-	innovative, secure, and reliable operating system they depend
-	on.  Please consider making a donation today!  <a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">https://www.FreeBSDfoundation.org/donate/</a>.</p>
-
-      <p>The Foundation improves the FreeBSD operating system by
-	employing our technical staff to maintain and improve critical
-	kernel subsystems, add features and functionality, and fix
-	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 FreeBSD remains a viable solution for research, education,
-	computing, products and more.</p>
-
-      <p>This quarter's project development highlights include:</p>
-
-      <ul>
-	<li>168 commits sponsored by the FreeBSD Foundation in the src
-	  tree (base system) development branch, across three staff
-	  members and four grant recipients/other developers.</li>
-
-	<li>Multiple funded grants, including the <tt>cfumass</tt> project, now
-	  committed to FreeBSD-HEAD, and improvements to the
-	  <tt>blacklistd</tt> daemon and FreeBSD/arm64 port.</li>
-
-	<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>
-
-	<li>Significant progress on the 64-bit inode project, which
-	  is nearly ready for commit.</li>
-      </ul>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating for
-	the Project.  This includes promoting work being done by
-	others with FreeBSD; producing advocacy literature to teach
-	people about FreeBSD and help make the path to starting to use
-	FreeBSD or contribute to the Project easier; and attending and
-	getting other FreeBSD contributors to volunteer to run FreeBSD
-	events, staff FreeBSD tables, and give FreeBSD presentations.</p>
-
-      <p>Some of the highlights of our advocacy and education work
-	over the last quarter:</p>
-
-      <ul>
-	<li>Promoted FreeBSD at: FOSDEM, SCALE, AsiaBSDcon, and
-	  FOSSASIA</li>
-
-	<li>Promoted BSDCan, SCALE, USENIX LISA, vBSDcon and
-	  EuroBSDcon Calls for Participation</li>
-
-	<li>Promoted Google Summer of Code participation on social
-	  media and created a flyer for people to post at their
-	  universities</li>
-
-	<li>Published a New Faces of FreeBSD Story: Joseph Kong</li>
-
-	<li>Set up a Marketing Partnership with the USENIX Association
-	  and SNIA</li>
-
-	<li>Published and Promoted the Jan/Feb 2017 issue of the FreeBSD
-	  Journal: https://www.FreeBSDfoundation.org/journal/</li>
-
-	<li>Published monthly Development Projects Updates on our
-	  blog</li>
-
-	<li>Secured a FreeBSD table at OSCON and promoted available
-	  discounts</li>
-      </ul>
-
-      <p>Conferences and Events</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events, and
-	summits around the globe.  These events can be BSD-related, open
-	source, or technology events geared towards underrepresented
-	groups.</p>
-
-      <p>We support the FreeBSD-focused events to help provide a venue
-	for sharing knowledge, to work together on projects, and to
-	facilitate collaboration between developers and commercial
-	users; this all helps provide a healthy ecosystem.  We support
-	the non-FreeBSD events to promote and raise awareness about FreeBSD,
-	to increase the use of FreeBSD in different applications, and to
-	recruit more contributors to the Project.</p>
-
-      <p>We also sponsored and/or attended the following events last
-	quarter:</p>
-
-      <ul>
-	<li>FOSDEM FreeBSD developer summit (sponsor)</li>
-
-	<li>AsiaBSDCon &#8212; Tokyo, Japan (sponsor)</li>
-
-	<li>Organized and ran the FreeBSD Storage Summit in Santa Clara,
-	  CA</li>
-
-	<li>Board member Philip Paeps gave a FreeBSD presentation at
-	  FOSSASIA</li>
-
-	<li>Attended FOSSASIA, FOSDEM, and SCALE</li>
-      </ul>
-
-      <p>Release Engineering</p>
-
-      <p>The Foundation provides a full-time staff member to lead the
-	release engineering efforts.  This has provided timely and
-	reliable releases over the last few years.  Some highlights
-	from last quarter include:</p>
-
-      <ul>
-	<li>Continued the production of weekly development snapshots
-	  for the 12-CURRENT, 11-STABLE, and 10-STABLE branches.</li>
-
-	<li>Published the initial FreeBSD 11.1-RELEASE schedule to the
-	  Project website.</li>
-      </ul>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them.  We continued to review
-	requests and grant permission to use the trademarks.</p>
-
-
-      <p>Many more details about how we supported FreeBSD last quarter
-	can be found in our Q1 newsletter!</p>
-    <hr /><h2><a name="The-FreeBSD-Ports-Collection" href="#The-FreeBSD-Ports-Collection" id="The-FreeBSD-Ports-Collection">The FreeBSD Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/portmgr/index.html" title="https://www.FreeBSD.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/portmgr/index.html" title="Ports Management Team">https://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/FreeBSD_portmgr/" title="https://twitter.com/FreeBSD_portmgr/">FreeBSD portmgr on Twitter (@FreeBSD_portmgr)</a></td><td>
-	    URL: <a href="https://twitter.com/FreeBSD_portmgr/" title="FreeBSD portmgr on Twitter (@FreeBSD_portmgr)">https://twitter.com/FreeBSD_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">FreeBSD Ports Management Team on Facebook</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="FreeBSD Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team on Google+</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="FreeBSD Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The number of ports is currently just 500 short of 30,000.  The current
-	number of PRs is close to 2,400, of which 620 are unassigned.  The last
-	quarter saw 6656 commits from 167 comitters.  Both the number of ports and
-	the number of unassigned PRs have increased in the last quarter.</p>
-
-      <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
-	Kondratyev (wulf).  dumbbell@ was already a src committer and got an extension
-	for the Ports Tree.  We also welcomed back krion@ and miwi@.  We took 6
-	bits in for safe-keeping: itetcu@, leeym@, mva@, olivierd@, pgollucci@,
-	and sanpei@.</p>
-
-      <p>There were no changes to the membership of portmgr.</p>
-
-      <p>antoine@ worked on <tt>USES=samba</tt> to prepare for the
-	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 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>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,
-	Xorg 1.18.4, Qt 4.8.7 and 5.7.1, and PHP 7.1.</p>
-
-      <p>antoine@ ran 31 exp-runs to test version updates and under-the-hood
-	changes.</p>
-    <h3>Open tasks:</h3><ol><li>The number of unassigned and open PRs is still growing, so if you
-	have some spare time, please close some of those.</li></ol><hr /><h2><a name="The-FreeBSD-Release-Engineering-Team" href="#The-FreeBSD-Release-Engineering-Team" id="The-FreeBSD-Release-Engineering-Team">The FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/11.1R/schedule.html" title="https://www.freebsd.org/releases/11.1R/schedule.html">FreeBSD�11.1-RELEASE Schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.1R/schedule.html" title="FreeBSD�11.1-RELEASE Schedule">https://www.freebsd.org/releases/11.1R/schedule.html</a></td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD development Snapshots</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD development Snapshots">http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD�Release Engineering Team continued producing
-	weekly development snapshots for the 12-CURRENT, 11-STABLE,
-	and 10-STABLE branches.</p>
-
-      <p>In addition, the FreeBSD�11.1-RELEASE schedule was added to
-	the Project website.  Please note, however, the schedule on
-	the website is still subject to change.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Ceph-on-FreeBSD" href="#Ceph-on-FreeBSD" id="Ceph-on-FreeBSD">Ceph on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ceph.com" title="http://ceph.com">Ceph Main Site</a></td><td>
-	    URL: <a href="http://ceph.com" title="Ceph Main Site">http://ceph.com</a></td></tr><tr><td><a href="https://github.com/ceph/ceph" title="https://github.com/ceph/ceph">Main Repository</a></td><td>
-	    URL: <a href="https://github.com/ceph/ceph" title="Main Repository">https://github.com/ceph/ceph</a></td></tr><tr><td><a href="https://github.com/wjwithagen/ceph" title="https://github.com/wjwithagen/ceph">My FreeBSD Fork</a></td><td>
-	    URL: <a href="https://github.com/wjwithagen/ceph" title="My FreeBSD Fork">https://github.com/wjwithagen/ceph</a></td></tr></table><p>
-	Contact:
-	  Willem Jan
-	  Withagen
-	 &lt;<a href="mailto:wjw@digiware.nl">wjw@digiware.nl</a>&gt;
-	</p>
-      <p>Ceph is a distributed object store and file system designed to provide
-	excellent performance, reliability and scalability.</p>
-
-      <ul>
-	<li><p>Object Storage</p>
-
-	  <p>Ceph provides seamless access to objects using native
-	    language bindings or <tt>radosgw</tt>, a REST interface
-	    that is compatible with applications written for S3 and
-	    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>
-
-	  <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>
-      </ul>
-
-      <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 disks that are stored in Ceph.</p>
-
-      <p>Compiling for FreeBSD will now build most of the tools
-	available in Ceph.</p>
-
-      <p>Notable progress since the last report:</p>
-
-      <ul>
-	<li>The most important change is that a port has been
-	  submitted: <tt>net/ceph-devel</tt>.  However, it does not
-	  yet contain <tt>ceph-fuse</tt>.</li>
-
-	<li>Regular updates to the <tt>ceph-devel</tt> port are
-	  expected, with the next one coming in April.</li>
-
-	<li><tt>ceph-fuse</tt> works, allowing one to mount a CephFS
-	  filesystem on a FreeBSD system and perform normal operations.</li>
-
-	<li><tt>ceph-disk prepare</tt> and <tt>activate</tt> work for
-	  FileStore on ZFS, allowing for easy creation of OSDs.</li>
-
-	<li>RBD is actually buildable and can be used to manage RADOS BLOCK
-	  DEVICEs.</li>
-
-	<li>Most of the awkward dependencies on Linux-isms are deleted
-	  &#8212; only <tt>/bin/bash</tt> is here to stay.</li>
-      </ul>
-
-      <p>To get things running on a FreeBSD system, run <tt>pkg install
-	  net/ceph-devel</tt> or clone <a href="https://github.com/wjwithagen/ceph" shape="rect">https://github.com/wjwithagen/ceph</a>
-	and build manually by running <tt>./do_freebsd.sh</tt> in the
-	checkout root.</p>
-
-      <p>Parts not (yet) included:</p>
-
-      <ul>
-	<li>KRBD: Kernel Rados Block Devices are implemented in the
-	  Linux kernel, but not yet in the FreeBSD kernel.  It is possible
-	  that <tt>ggated</tt> could be used as a template, since it
-	  does similar things, just between two disks.  It also has a
-	  userspace counterpart, which could ease development.</li>
-
-	<li>BlueStore: FreeBSD and Linux have different AIO APIs, and
-	  that incompatibility needs to resolved somehow.  Additionally,
-	  there is discussion in FreeBSD about <tt>aio_cancel</tt> not
-	  working for all devicetypes.</li>
-
-	<li>CephFS as native filesystem: though <tt>ceph-fuse</tt>
-	  works, it can be advantageous to have an in-kernel
-	  implementation for heavy workloads.  Cython tries to access
-	  an internal field in <tt>struct dirent</tt>, which does not
-	  compile.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Run integration tests to see if the FreeBSD daemons will work
-	with a Linux Ceph platform.</li><li>Compile and test the userspace RBD (Rados Block Device).
-	This currently works but testing has been limitted.</li><li>Investigate and see if an in-kernel RBD device could be
-	developed akin to <tt>ggate</tt>.</li><li>Investigate the keystore, which can be embedded in the
-	kernel on Linux and currently prevents building Cephfs and
-	some other parts.  The first question is whether it is really
-	required, or only KRBD requires it.</li><li>Scheduler information is not used at the moment, because the
-	schedulers work rather differently between Linux and FreeBSD.
-	But at a certain point in time, this will need some attention
-	(in <tt>src/common/Thread.cc</tt>).</li><li>Improve the FreeBSD 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 FreeBSD- and ZFS-compatible.</li><li>Build a test cluster and start running some of the
-	teuthology integration tests on it.  Teuthology wants to build
-	its own <tt>libvirt</tt> and that does not quite work with all
-	the packages FreeBSD already has in place.  There are many
-	details to work out here.</li><li>Design a vitual disk implementation that can be used with
-	<tt>bhyve</tt> and attached to an RBD image.</li></ol><hr /><h2><a name="OpenBSM" href="#OpenBSM" id="OpenBSM">OpenBSM</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openbsm.org" title="http://www.openbsm.org">OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation</a></td><td>
-	    URL: <a href="http://www.openbsm.org" title="OpenBSM: Open Source Basic Security Module (BSM) Audit Implementation">http://www.openbsm.org</a></td></tr><tr><td><a href="https://github.com/openbsm/openbsm" title="https://github.com/openbsm/openbsm">OpenBSM on GitHub</a></td><td>
-	    URL: <a href="https://github.com/openbsm/openbsm" title="OpenBSM on GitHub">https://github.com/openbsm/openbsm</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html">FreeBSD Audit Handbook Chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html" title="FreeBSD Audit Handbook Chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/audit.html</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D10149" title="https://reviews.FreeBSD.org/D10149">DTrace Audit Provider</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D10149" title="DTrace Audit Provider">https://reviews.FreeBSD.org/D10149</a></td></tr><tr><td><a href="https://www.cl.cam.ac.uk/research/security/cadets/" title="https://www.cl.cam.ac.uk/research/security/cadets/">DARPA CADETS project</a></td><td>
-	    URL: <a href="https://www.cl.cam.ac.uk/research/security/cadets/" title="DARPA CADETS project">https://www.cl.cam.ac.uk/research/security/cadets/</a></td></tr><tr><td><a href="https://github.com/openbsm/openbsm/blob/master/TODO" title="https://github.com/openbsm/openbsm/blob/master/TODO">TODO List on GitHub</a></td><td>
-	    URL: <a href="https://github.com/openbsm/openbsm/blob/master/TODO" title="TODO List on GitHub">https://github.com/openbsm/openbsm/blob/master/TODO</a></td></tr></table><p>
-	Contact:
-	  Christian
-	  Brueffer
-	 &lt;<a href="mailto:brueffer@FreeBSD.org">brueffer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: TrustedBSD audit mailing list &lt;<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>&gt;
-	</p>
-      <p>OpenBSM is a BSD-licensed implementation of Sun's Basic Security
-	Module (BSM) API and file format.  It is the userspace side of the
-	CAPP Audit implementations in FreeBSD and Mac OS X.  Additionally,
-	the audit trail processing tools are expected to work on Linux.</p>
-
-      <p>During this quarter, experimental support for UUIDs in BSM trails
-	was added to OpenBSM.  A DTrace audit provider using this
-	functionality has been developed as part of the DARPA CADETS
-	project and is in review (<a href="https://reviews.FreeBSD.org/D10149" shape="rect">https://reviews.FreeBSD.org/D10149</a>).
-	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 FreeBSD HEAD
-	branch.</p>
-    <p>This project was sponsored by DARPA/AFRL (in part).</p><h3>Open tasks:</h3><ol><li>Test the latest release on different versions of FreeBSD, Mac OS X
-	and Linux.  Testing on the latest versions of Mac OS X
-	would be particularly appreciated.</li><li>Fix problems that have been reported via GitHub and the
-	FreeBSD bug tracker.</li><li>Implement the features mentioned in the TODO list on
-	GitHub.</li></ol><hr /><h2><a name="Porting-Software-to-CloudABI:-Sandboxed-Bitcoin!" href="#Porting-Software-to-CloudABI:-Sandboxed-Bitcoin!" id="Porting-Software-to-CloudABI:-Sandboxed-Bitcoin!">Porting Software to CloudABI: Sandboxed Bitcoin!</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://nuxi.nl/cloudabi/freebsd/" title="https://nuxi.nl/cloudabi/freebsd/">How to Use CloudABI on FreeBSD</a></td><td>
-	    URL: <a href="https://nuxi.nl/cloudabi/freebsd/" title="How to Use CloudABI on FreeBSD">https://nuxi.nl/cloudabi/freebsd/</a></td></tr><tr><td><a href="https://nuxi.nl/blog/2017/02/18/porting-leveldb-to-cloudabi.html" title="https://nuxi.nl/blog/2017/02/18/porting-leveldb-to-cloudabi.html">LevelDB for CloudABI</a></td><td>
-	    URL: <a href="https://nuxi.nl/blog/2017/02/18/porting-leveldb-to-cloudabi.html" title="LevelDB for CloudABI">https://nuxi.nl/blog/2017/02/18/porting-leveldb-to-cloudabi.html</a></td></tr><tr><td><a href="https://nuxi.nl/blog/2017/03/15/sandboxed-memcached.html" title="https://nuxi.nl/blog/2017/03/15/sandboxed-memcached.html">Memcached for CloudABI</a></td><td>
-	    URL: <a href="https://nuxi.nl/blog/2017/03/15/sandboxed-memcached.html" title="Memcached for CloudABI">https://nuxi.nl/blog/2017/03/15/sandboxed-memcached.html</a></td></tr><tr><td><a href="https://laanwj.github.io/2017/03/02/porting-bitcoin-core-to-cloudabi.html" title="https://laanwj.github.io/2017/03/02/porting-bitcoin-core-to-cloudabi.html">Bitcoin for CloudABI</a></td><td>
-	    URL: <a href="https://laanwj.github.io/2017/03/02/porting-bitcoin-core-to-cloudabi.html" title="Bitcoin for CloudABI">https://laanwj.github.io/2017/03/02/porting-bitcoin-core-to-cloudabi.html</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
-	</p>
-      <p>CloudABI is a framework that allows you to develop strongly
-	sandboxed applications a lot more easily.  It is a programming
-	environment that exclusively uses FreeBSD's Capsicum facilities.  Any
-	features incompatible with Capsicum have been removed entirely,
-	which means that it is easier to determine how code needs to be
-	adjusted to behave correctly while sandboxed.  In essence, you only
-	need to patch up the code until it builds.</p>
-
-      <p>Last year we have managed to port a lot of exciting libraries over
-	to CloudABI.  Highlights include sandboxing aware versions of
-	<a href="http://www.boost.org/" shape="rect">Boost</a> and
-	<a href="http://leveldb.org/" shape="rect">LevelDB</a>.  Now that these
-	libraries are readily available, we are at the point where we can
-	shift our focus towards porting full applications.</p>
-
-      <p>In late February one of the lead developers of
-	<a href="https://github.com/bitcoin/bitcoin" shape="rect">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 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
-	of CloudABI well, I've made addressing any issues reported by the
-	Bitcoin developers a top priority.  Once the Bitcoin port is
-	complete, we want to provide binary packages of it as well.</p>
-    <p>This project was sponsored by Nuxi, the Netherlands.</p><h3>Open tasks:</h3><ol><li>Though getting Bitcoin to work is pretty awesome, don't let
-	that distract us from porting other pieces of software over as
-	well!  Are you the maintainer of a piece of software that could
-	benefit from sandboxing?  Be sure to try building it using the
-	CloudABI toolchain!</li><li>One of the pieces of software that got ported over to
-	CloudABI some time ago is Memcached.  Are you a user of
-	Memcached? If so, feel free to give the sandboxed version of
-	Memcached for CloudABI a try!</li><li>So far, CloudABI can be used to run software written in C, C++
-	and Python.  Would you like to see any other programming language
-	work on CloudABI as well?  Be sure to help out!</li></ol><hr /><h2><a name="Support-for-eMMC-Flash-and-Faster-SD-Card-Modes" href="#Support-for-eMMC-Flash-and-Faster-SD-Card-Modes" id="Support-for-eMMC-Flash-and-Faster-SD-Card-Modes">Support for eMMC Flash and Faster SD Card Modes</a></h2><p>
-	Contact:
-	  Marius
-	  Strobl
-	 &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
-	</p>
-      <p>In r315430, support for eMMC partitions has been added to
-	<tt>mmc(4)</tt> and <tt>mmcsd(4)</tt> in FreeBSD 12.  Besides the
-	user data area, i.e., the default partition, eMMC v4.41 and
-	later devices can additionally provide up to:</p>
-
-      <ul>
-	<li>1 enhanced user data area partition</li>
-
-	<li>2 boot partitions</li>
-
-	<li>1 RPMB (Replay Protected Memory Block) partition</li>
-
-	<li>4 general purpose partitions (optionally with an enhanced
-	  or extended attribute)</li>
-      </ul>
-
-      <p>Apart from simply subdividing eMMC flash devices or having
-	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"
-	attribute of general purpose partitions.</p>
-
-      <p>In order to be able to partition eMMC devices, r315430 also
-	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 FreeBSD.  Besides partitioning
-	eMMC devices, the <tt>mmc</tt> tool can also be used to query
-	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
-	operation.</p>
-
-      <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, which will appear in FreeBSD 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 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).
-	The only viable workaround for that problem appears to be the
-	implementation of support for ADMA2 mode in <tt>sdhci(4)</tt>
-	(currently, <tt>sdhci(4)</tt> supports only the encumbered SDMA
-	mode or no DMA at all).</p>
-
-      <p>However, r315598 also brought in infrastructure and
-	a fair amount of code for using even faster transfer modes with eMMC
-	devices and SD cards respectively, i.e., up to HS400ES with eMMC
-	and the UHS-I modes up to SDR104 with SD cards.</p>
-
-      <p>The intent is to merge these changes back to FreeBSD 10 and 11.</p>
-    <h3>Open tasks:</h3><ol><li>Add support for eMMC HS200, HS400, and HS400ES transfer
-	modes.</li><li>Add support for SD card UHS-I transfer modes (SDR12 to
-	SDR104).</li><li>Make <tt>mmcsd(4)</tt> more robust and correctly follow
-	the relevant specifications for existing features, e.g.,
-	calculate and handle erase timeouts, do a <tt>SEND_STATUS</tt>
-	when CMD6 is invoked with an R1B response to the extent not
-	already fixed as part of r315430, get the remainder of the
-	existing code to properly check and handle return codes,
-	etc.</li></ol><hr /><h2><a name="TrustedBSD" href="#TrustedBSD" id="TrustedBSD">TrustedBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.trustedbsd.org" title="http://www.trustedbsd.org">TrustedBSD Website</a></td><td>
-	    URL: <a href="http://www.trustedbsd.org" title="TrustedBSD Website">http://www.trustedbsd.org</a></td></tr><tr><td><a href="https://github.com/trustedbsd" title="https://github.com/trustedbsd">TrustedBSD on GitHub</a></td><td>
-	    URL: <a href="https://github.com/trustedbsd" title="TrustedBSD on GitHub">https://github.com/trustedbsd</a></td></tr></table><p>
-	Contact:
-	  Christian
-	  Brueffer
-	 &lt;<a href="mailto:brueffer@FreeBSD.org">brueffer@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Robert
-	  Watson
-	 &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  TrustedBSD announce mailing list
-	 &lt;<a href="mailto:trustedbsd-announce@TrustedBSD.org">trustedbsd-announce@TrustedBSD.org</a>&gt;
-	</p>
-      <p>The TrustedBSD Project is an open-source community developing
-	advanced security features for the open-source FreeBSD operating
-	system.  Started in April 2000, the project developed support
-	for extended attributes, access control lists (ACLs), UFS2,
-	OpenPAM, security event auditing, OpenBSM, a flexible kernel
-	access control framework, mandatory access control, and the
-	GEOM storage layer.  The results of this work may be found not
-	just in FreeBSD, but also NetBSD, OpenBSD, Linux, and Apple's Mac
-	OS X and iOS operating systems.  Today, the project continues
-	to maintain and enhance these mature features in FreeBSD.</p>
-
-      <p>During this quarter, the TrustedBSD project transitioned from the
-	FreeBSD Perforce server to GitHub.  This was made possible by
-	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>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="FreeBSD-on-Hyper-V-and-Azure" href="#FreeBSD-on-Hyper-V-and-Azure" id="FreeBSD-on-Hyper-V-and-Azure">FreeBSD on Hyper-V and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/HyperV" title="https://wiki.FreeBSD.org/HyperV">FreeBSD Virtual Machines on Microsoft Hyper-V</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/HyperV" title="FreeBSD Virtual Machines on Microsoft Hyper-V">https://wiki.FreeBSD.org/HyperV</a></td></tr><tr><td><a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="https://technet.microsoft.com/en-us/library/dn531030.aspx">Supported Linux and FreeBSD Virtual Machines for Hyper-V on Windows</a></td><td>
-	    URL: <a href="https://technet.microsoft.com/en-us/library/dn531030.aspx" title="Supported Linux and FreeBSD Virtual Machines for Hyper-V on Windows">https://technet.microsoft.com/en-us/library/dn531030.aspx</a></td></tr></table><p>
-	Contact:
-	  Sepherosa
-	  Ziehau
-	 &lt;<a href="mailto:sepherosa@gmail.com">sepherosa@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Hongjiang
-	  Zhang
-	 &lt;<a href="mailto:honzhan@microsoft.com">honzhan@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Dexuan
-	  Cui
-	 &lt;<a href="mailto:decui@microsoft.com">decui@microsoft.com</a>&gt;
-	<br />
-	Contact:
-	  Kylie
-	  Liang
-	 &lt;<a href="mailto:kyliel@microsoft.com">kyliel@microsoft.com</a>&gt;
-	</p>
-      <p>SR-IOV support for NICs is implemented.  So far, we have only
-	tested with the Mellanox ConnectX-3 VF card, which works
-	despite some issues (Bug 216493: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216493" shape="rect">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216493</a>).</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
-	  now boot with Secure Boot disabled;</li>
-
-	<li>A synthetic keyboard driver has been added.  Currently it
-	  is only in HEAD, but MFCs to stable/10 and stable/11 are
-	  planned to occur soon;</li>
-
-	<li>A SCSI DVD detection issue (Bug 218248) was fixed.
-	  Without the fix, the VM would fail to boot.</li>
-      </ol>
-    <p>This project was sponsored by Microsoft.</p><hr /><h2><a name="Intel-10G-and-40G-Network-Driver-Updates" href="#Intel-10G-and-40G-Network-Driver-Updates" id="Intel-10G-and-40G-Network-Driver-Updates">Intel 10G and 40G Network Driver Updates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D9851" title="https://reviews.FreeBSD.org/D9851">Commit adding X553 ix/ixv Support for iflib</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D9851" title="Commit adding X553 ix/ixv Support for iflib">https://reviews.FreeBSD.org/D9851</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D5213" title="https://reviews.FreeBSD.org/D5213">Commit converting ixgbe to iflib</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D5213" title="Commit converting ixgbe to iflib">https://reviews.FreeBSD.org/D5213</a></td></tr></table><p>
-	Contact:
-	  Jeb
-	  Cramer
-	 &lt;<a href="mailto:jeb.j.cramer@intel.com">jeb.j.cramer@intel.com</a>&gt;
-	<br />
-	Contact:
-	  Eric
-	  Joyner
-	 &lt;<a href="mailto:eric.joyner@intel.com">eric.joyner@intel.com</a>&gt;
-	<br />
-	Contact:
-	  Krzysztof
-	  Galazka
-	 &lt;<a href="mailto:krzysztof.galazka@intel.com">krzysztof.galazka@intel.com</a>&gt;
-	</p>
-      <p>This driver update is for the Intel <tt>ix</tt>/<tt>ixv</tt>
-	and <tt>ixl</tt>/<tt>ixlv</tt> network drivers, and includes
-	support for several new hardware releases.</p>
-
-      <p><tt>ix</tt>/<tt>ixv</tt>:</p>
-
-      <ul>
-	<li>Added support for X553 SoC devices based on the Denverton
-	  platform</li>
-      </ul>
-
-      <p><tt>ixl</tt>/<tt>ixlv</tt>:</p>
-
-      <ul>
-	<li>Added support for X722 10G SoC devices based on the
-	  Lewisburg chipset</li>
-
-	<li>Added an interface for the upcoming iWarp driver for X722
-	  devices</li>
-
-	<li>Added support for XXV710 25G devices</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li><tt>ix</tt>/<tt>ixv</tt> <tt>iflib</tt> support is
-	currently under review in Phabricator.  It will be refactored to
-	include D5213.</li><li>Initial work for <tt>ixl</tt>/<tt>ixlv</tt> <tt>iflib</tt>
-	support is in progress.</li></ol><hr /><h2><a name="Linuxulator" href="#Linuxulator" id="Linuxulator">Linuxulator</a></h2><p>
-	Contact:
-	  Dimitry
-	  Chagin
-	 &lt;<a href="mailto:dchagin@FreeBSD.org">dchagin@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mahdi
-	  Mokhtari
-	 &lt;<a href="mailto:mmokhi@FreeBSD.org">mmokhi@FreeBSD.org</a>&gt;
-	</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 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>
-    <h3>Open tasks:</h3><ol><li>We plan to implement the <tt>execveat</tt> syscall for the
-	native FreeBSD syscall table and then port/wrap it for use in
-	the Linuxulator.</li></ol><hr /><h2><a name="MMC-Stack-Using-the-CAM-Framework" href="#MMC-Stack-Using-the-CAM-Framework" id="MMC-Stack-Using-the-CAM-Framework">MMC Stack Using the CAM Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bakulin.de/freebsd/mmccam.html" title="https://bakulin.de/freebsd/mmccam.html">Project Information</a></td><td>
-	    URL: <a href="https://bakulin.de/freebsd/mmccam.html" title="Project Information">https://bakulin.de/freebsd/mmccam.html</a></td></tr><tr><td><a href="https://github.com/kibab/FreeBSD/tree/mmccam-collapsed-commits" title="https://github.com/kibab/FreeBSD/tree/mmccam-collapsed-commits">Source Code</a></td><td>
-	    URL: <a href="https://github.com/kibab/FreeBSD/tree/mmccam-collapsed-commits" title="Source Code">https://github.com/kibab/FreeBSD/tree/mmccam-collapsed-commits</a></td></tr></table><p>
-	Contact:
-	  Ilya
-	  Bakulin
-	 &lt;<a href="mailto:kibab@FreeBSD.org">kibab@FreeBSD.org</a>&gt;
-	</p>
-      <p>The goal of this project is to reimplement the existing
-	MMC/SD stack using the CAM framework.  This will permit
-	utilizing the well-tested CAM locking model and debugging
-	features.  It will also be possible to process interrupts
-	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, such as 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 an SD card and bring it
-	to an operational state so that it is possible to read and
-	write to the card.</p>
-
-      <p>The stack has been tested to work on the Beaglebone Black and
-	Wandboard Quad platforms.</p>
-
-      <p>Currently the code is being prepared for inclusion in the
-	FreeBSD source tree.  <tt>cam(3)</tt> is being extended to
-	support SDIO-specific functions (reading registers, managing
-	interrupts, etc.).</p>
-    <h3>Open tasks:</h3><ol><li>Integrate the code into FreeBSD HEAD to facilitate
-	testing.</li><li>Begin writing a driver for Broadcom-based WLAN chips (found
-	on the Raspberry Pi 3 and Wandboard).</li><li>Begin writing a driver for Marvell-based WLAN chips (found
-	on the GlobalScale Dreamplug and some Chromebooks).</li></ol><hr /><h2><a name="pNFS-Server-Plan-B" href="#pNFS-Server-Plan-B" id="pNFS-Server-Plan-B">pNFS Server Plan B</a></h2><p>
-	Contact:
-	  Rick
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>&gt;
-	</p>
-      <p>Parallel NFS (pNFS) is an extension to the NFSv4 protocol that
-	allows for file accesses within a single logical mount to be
-	performed against multiple file servers, with the potential
-	for data access to occur in parallel.  The pNFS
-	"layout" in use specifies how the division occurs, with
-	metadata operations occurring against the main server, and
-	bulk data operations (read/write/setattr/etc.) occurring via
-	a layout-specific scheme between the client and data
-	servers.</p>
-
-      <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 FreeBSD,
-	with one FreeBSD server handling the metadata operations and multiple
-	FreeBSD servers configured to serve data.  An NFSv4.1 client
-	that supports the pNFS File Layout will be able to
-	read and write to the data servers directly, spreading out the
-	RPC load and allowing growth beyond that of what a single
-	FreeBSD NFS server could achieve.</p>
-
-      <p>There is no support for the Flex Files Layout or mirroring
-	at this time.  I hope to use the Flex Files Layout to add
-	mirroring support over the next year or so.  Striping is
-	also not supported, but I have no plans for implementing it
-	at the moment.</p>
-
-      <p>Plan B is working quite well now and should be available
-	for testing by the end of April.  I will announce how to do this on
-	the freebsd-fs@FreeBSD.org mailing list when it is available.</p>
-    <h3>Open tasks:</h3><ol><li>Testing by others will be needed, once it is available.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="64-bit-PowerPC-Book-E-Support" href="#64-bit-PowerPC-Book-E-Support" id="64-bit-PowerPC-Book-E-Support">64-bit PowerPC Book-E Support</a></h2><p>
-	Contact:
-	  Justin
-	  Hibbits
-	 &lt;<a href="mailto:jhibbits@FreeBSD.org">jhibbits@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Book-E platform target now supports 64-bit mode
-	("powerpc64").  It includes a 63-bit address space
-	split, but the page table directory list uses holes to expand
-	to the full address space, leaving gaps in the address space
-	where page mappings are repeated.  This may change in the
-	future.</p>
-
-      <p>As with the AIM powerpc64 port, Book-E supports running powerpc
-	(32-bit) binaries as well, and has even been tested with a
-	32-bit <tt>init</tt> and 64-bit shell.</p>
-
-      <p>Several of the SoC drivers are supported, however, the dTSEC
-	ethernet controller is not yet supported.  Work is ongoing to
-	support it.</p>
-
-      <p>A QORIQ64 config is included, targeting the P5 and T* series
-	SoCs from Freescale.</p>
-
-      <p>Thanks to Juniper Networks for providing patches against an
-	older internally maintained FreeBSD version, which enabled this
-	porting effort, and for providing historical context for quirks
-	of the pmap changes.</p>
-    <h3>Open tasks:</h3><ol><li>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 for this ethernet controller.</li><li>Take advantage of pointer alignment to squeeze more bits
-	out of the page tables; it should be possible to squeeze at
-	least 3 more bits out, one at each level.</li></ol><hr /><h2><a name="FreeBSD-on-Marvell-Armada38x" href="#FreeBSD-on-Marvell-Armada38x" id="FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></h2><p>
-	Contact:
-	  Marcin
-	  Wojtas
-	 &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>&gt;
-	</p>
-      <p>Final testing and productionization of support for the
-	Marvell Armada38x platform is under way.  The rebase and cleanup
-	is going well, with patches functioning on top of HEAD and ready for
-	upstreaming.</p>
-
-      <p>Specific tasks completed include:</p>
-
-      <ul>
-	<li>Platform benchmarking and low-level optimizations
-	  (internal bus, L1/L2 cache prefetch) &#8212; already
-	  submitted)</li>
-
-	<li>Enable the PL310 L2 cache controller &#8212; currently under
-	  review</li>
-
-	<li>NETA tests, optimizations and PHY-handling rework</li>
-
-	<li><tt>e6000sw</tt> PHY handling rework and fixes</li>
-
-	<li>Fix and enable performance counter support</li>
-
-	<li>Fix timers and extract watchdog support to a separate driver</li>
-
-	<li>Crypto driver fixes &#8212; merged</li>
-
-	<li>AHCI controller support &#8212; merged</li>
-
-	<li>Thermal driver &#8212; merged</li>
-
-	<li>Merge additional support for new boards (SolidRun ClearFog
-	  and DB-88F6285-AP)</li>
-      </ul>
-    <p>This project was sponsored by Stormshield, and Semihalf.</p><h3>Open tasks:</h3><ol><li>Submit the remaining fixes and drivers.</li></ol><hr /><h2><a name="FreeBSD/s390x-Attempt-III" href="#FreeBSD/s390x-Attempt-III" id="FreeBSD/s390x-Attempt-III">FreeBSD/s390x Attempt III</a></h2><p>
-	Contact:
-	  Bjoern A.
-	  Zeeb
-	 &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p>
-      <p>A long time ago, in the FreeBSD 5 times, there was an initial
-	port of FreeBSD to s390 (32bit) and s390x (64bit)
-	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 FreeBSD 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 for
-	incremental addition of the necessary 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 FreeBSD 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 facilitate collaboration.</p>
-    <h3>Open tasks:</h3><ol><li>Write a wiki page with per-architecture specific tasks
-	that need to be done, based on the current work and the experience
-	from arm64 and riscv.</li><li>Implement both the userspace and kernel per-architecture
-	gaps.</li><li>Figure out a way to get access to IBM's zPDT or better
-	emulators to ease implementation, testing, and debugging.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="MySQL" href="#MySQL" id="MySQL">MySQL</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.mysql.com/why-mysql/presentations/mysql-80-overview/" title="https://www.mysql.com/why-mysql/presentations/mysql-80-overview/">MySQL80 Overview</a></td><td>
-	    URL: <a href="https://www.mysql.com/why-mysql/presentations/mysql-80-overview/" title="MySQL80 Overview">https://www.mysql.com/why-mysql/presentations/mysql-80-overview/</a></td></tr><tr><td><a href="https://www.mysql.com/why-mysql/presentations/innodb-whats-new-mysql-80/" title="https://www.mysql.com/why-mysql/presentations/innodb-whats-new-mysql-80/">MySQL80 InnoDB New Features</a></td><td>
-	    URL: <a href="https://www.mysql.com/why-mysql/presentations/innodb-whats-new-mysql-80/" title="MySQL80 InnoDB New Features">https://www.mysql.com/why-mysql/presentations/innodb-whats-new-mysql-80/</a></td></tr></table><p>
-	Contact:
-	  Mahdi
-	  Mokhtari
-	 &lt;<a href="mailto:mmokhi@FreeBSD.org">mmokhi@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Mark
-	  Felder
-	 &lt;<a href="mailto:feld@FreeBSD.org">feld@FreeBSD.org</a>&gt;
-	</p>
-      <p>This quarter a new <tt>-dev</tt> version of MySQL landed in
-	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 its latest version and closed many
-	PRs related to it, mostly relating to using FreeBSD-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>
-    <h3>Open tasks:</h3><ol><li>Test the new version and report problems.</li></ol><hr /><h2><a name="Rust" href="#Rust" id="Rust">Rust</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Rust" title="https://wiki.FreeBSD.org/Rust">Wiki Portal</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Rust" title="Wiki Portal">https://wiki.FreeBSD.org/Rust</a></td></tr><tr><td><a href="https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad" title="https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad">Guide to Bootstraping Rust on FreeBSD</a></td><td>
-	    URL: <a href="https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad" title="Guide to Bootstraping Rust on FreeBSD">https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad</a></td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143">Bug Report to Track Progress on Bootstrapping</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143" title="Bug Report to Track Progress on Bootstrapping">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143</a></td></tr></table><p>
-	Contact:
-	  Jean-S�bastien
-	  P�dron
-	 &lt;<a href="mailto:dumbbell@FreeBSD.org">dumbbell@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Thomas
-	  Zander
-	 &lt;<a href="mailto:riggs@FreeBSD.org">riggs@FreeBSD.org</a>&gt;
-	</p>
-      <p>In the Ports Collection, Rust was updated to 1.16.0 and Cargo
-	to 0.17.0, the latest versions at the time of this writing.</p>
-
-      <p><tt>lang/rust-nightly</tt> was also updated to a snapshot from
-	February and it is now enabled on <tt>i386</tt>.  It is
-	lagging a bit behind upstream, but <a href="https://rustup.rs/" shape="rect">Rustup</a> works nicely on FreeBSD if
-	you need to try any versions/channels of Rust.</p>
-
-      <p>Work has started to bootstrap Rust on non-<tt>x86</tt> architectures.
-	Patches to add FreeBSD/aarch64 support were submitted and accepted
-	upstream.  FreeBSD/sparc64 is in progress.  The <tt>lang/rust-nightly</tt>
-	port is also being adapted to compile natively on FreeBSD/aarch64.  This
-	work is critical, in particular because Firefox will shortly require
-	Rust.  If you want to help, please refer to the guide linked above.</p>
-
-      <p>The compiler, <tt>rustc</tt>, is crashing sometimes when there is a
-	compilation error.  Therefore, there is a bit of work to do to improve
-	stability.</p>
-
-      <p>There is some code duplication between <tt>lang/rust*</tt> and
-	<tt>devel/cargo</tt>.  Those Makefiles deserve a bit of cleanup.  It
-	might be useful to create a <tt>USES=rust</tt> Makefile helper.</p>
-    <h3>Open tasks:</h3><ol><li>Bootstrap Rust on more platforms.</li><li>Investigate compiler crashes.</li><li>Create a <tt>USES=rust</tt> Makefile helper and simplify
-	the Rust and Cargo ports.</li><li>Investigate how to speed up <tt>lang/rust*</tt>
-	compilation time.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/docproj/translations.html#dutch" title="https://www.FreeBSD.org/docproj/translations.html#dutch">The Dutch Translation Project</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/docproj/translations.html#dutch" title="The Dutch Translation Project">https://www.FreeBSD.org/docproj/translations.html#dutch</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has started on an initial translation of the FreeBSD
-	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 two articles already and did some
-	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 whether we
-	can merge them easily into the PO structure.  If you have ideas
-	on that, contact us a.s.a.p.</p>
-    <p>This project was sponsored by Snow�B.V. (in part).</p><h3>Open tasks:</h3><ol><li>Identify a way to merge the current XML translations into
-	the nl_NL.po files.</li><li>Merge the translations into the .po files.</li><li>Update the remaining open items into the po files.</li><li>Remove the old/outdated translation files from the main
-	repo and use the <tt>po</tt> and <tt>book.xml</tt> files to generate the Dutch
-	handbook and other files.</li><li>Identify whether we can also translate the <tt>htdocs</tt> pages
-	via the PO system.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2017-04-2017-06.html b/website/content/en/status/report-2017-04-2017-06.html
deleted file mode 100644
index 5cae9e6f63..0000000000
--- a/website/content/en/status/report-2017-04-2017-06.html
+++ /dev/null
@@ -1,2156 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>FreeBSD continues to defy the rumors of its demise.</p><p>Much of the development work done this quarter was not
-      particularly visible, especially the effort needed to ensure
-      the upcoming 11.1 release has as few regressions as possible.
-      Planning is also well under way for the 10.4 maintenance release
-      which will quickly follow it.</p><p>Further work focused on moving the arm architectures' support
-      closer to tier-1 status and improving documentation.  In addition,
-      large changes were made to the src and ports trees.</p><p>These projects and others are further detailed below.</p><p>&#8212;Mark Linimon</p><p><hr /></p><p>The deadline for submissions covering the period from July
-      to September 2017 is October 21, 2017.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li><li><a href="#The-Postmaster-Team">The Postmaster Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#64-bit-Inode-Numbers">64-bit Inode Numbers</a></li><li><a href="#Capability-Based-Network-Communication-for-Capsicum/CloudABI">Capability-Based Network Communication for Capsicum/CloudABI</a></li><li><a href="#Ceph-on-FreeBSD">Ceph on FreeBSD</a></li><li><a href="#DTS-Updates">DTS Updates</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Coda-revival">Coda revival</a></li><li><a href="#FreeBSD-Driver-for-the-Annapurna-Labs-ENA">FreeBSD Driver for the Annapurna Labs ENA</a></li><li><a href="#Intel-10G-Driver-Update">Intel 10G Driver Update</a></li><li><a href="#pNFS-Server-Plan-B">pNFS Server Plan B</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#DTC">DTC</a></li><li><a href="#Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker">Using LLVM's LLD Linker as FreeBSD's System Linker</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#A-New-USES-Macro-for-Porting-Cargo-Based-Rust-Applications">A New USES Macro for Porting Cargo-Based Rust Applications</a></li><li><a href="#GCC-(GNU-Compiler-Collection)">GCC (GNU Compiler Collection)</a></li><li><a href="#GNOME-on-FreeBSD">GNOME on FreeBSD</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#New-Port:-FRRouting">New Port: FRRouting</a></li><li><a href="#PHP-Ports:-Help-Improving-QA">PHP Ports: Help Improving QA</a></li><li><a href="#Rust">Rust</a></li><li><a href="#sndio-Support-in-the-FreeBSD-Ports-Collection">sndio Support in the FreeBSD Ports Collection</a></li><li><a href="#TensorFlow">TensorFlow</a></li><li><a href="#Updating-Port-Metadata-for-non-x86-Architectures">Updating Port Metadata for non-x86 Architectures</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Absolute-FreeBSD,-3rd-Edition">Absolute FreeBSD, 3rd Edition</a></li><li><a href="#Doc-Version-Strings-Improved-by-Their-Absence">Doc Version Strings Improved by Their Absence</a></li><li><a href="#New-Xen-Handbook-Section">New Xen Handbook Section</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSD-Meetups-at-Rennes-(France)">BSD Meetups at Rennes (France)</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#HardenedBSD">HardenedBSD</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/releases/11.1R/schedule.html" title="https://www.FreeBSD.org/releases/11.1R/schedule.html">FreeBSD�11.1-RELEASE Schedule</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/11.1R/schedule.html" title="FreeBSD�11.1-RELEASE Schedule">https://www.FreeBSD.org/releases/11.1R/schedule.html</a></td></tr><tr><td><a href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/" title="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/">FreeBSD Development Snapshots</a></td><td>
-	    URL: <a href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD Development Snapshots">https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD�11.1-RELEASE cycle started on May 19, and
-	continued as scheduled.  FreeBSD consumers are urged to test
-	whenever possible to help ensure the reliability and stability
-	of the upcoming second release from the <tt>stable/11</tt>
-	branch.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team Website</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team Website">https://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/freebsd_portmgr/" title="https://twitter.com/freebsd_portmgr/">FreeBSD portmgr on Twitter (@freebsd_portmgr)</a></td><td>
-	    URL: <a href="https://twitter.com/freebsd_portmgr/" title="FreeBSD portmgr on Twitter (@freebsd_portmgr)">https://twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">FreeBSD Ports Management Team on Facebook</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="FreeBSD Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team on Google+</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="FreeBSD Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>This quarter, 2017Q2, broke the 30,000 ports landmark for the
-	first time.  The PR count is currently just under 2,500, with
-	almost 600 of them unassigned.  This quarter saw almost 7,400
-	commits from 171 committers.  More PRs got closed this
-	quarter than last quarter, but also more PRs got sent in,
-	both of which are good to see.</p>
-
-      <p>Over the past three months, we welcomed four new committers:
-	Bradley T.  Hughes (bhughes@), Danilo G. Baio (dbaio@), Jochen
-	Neumeister (joneum@), and Richard Gallamore (ultima@).  kan@
-	re-joined us as a ports committer.  One commit bit, that of
-	bf@, was taken in for safekeeping after a long period of
-	inactivity.</p>
-
-      <p>On the management side, the Ports Management Team welcomed
-	back bapt@, who is working on several new features for the
-	Ports Tree.  The Ports Management Team also had its annual
-	real-life meeting during BSDCan.</p>
-
-      <p>On the infrastructure side, three new <tt>USES</tt> values
-	were introduced:</p>
-
-      <ul>
-	<li><tt>cargo</tt>, to ease the porting of Rust packages or
-	  binaries using the <tt>cargo</tt> command (also covered
-	  separately in this report)</li>
-
-	<li><tt>groff</tt>, to handle a dependency on the
-	  <tt>groff</tt> document formatting system, that has been
-	  removed from the base system for FreeBSD 12</li>
-
-	<li><tt>meson</tt>, to provide support for projects based on
-	  Meson</li>
-      </ul>
-
-      <p>The default version of PostgreSQL switched from 9.3 to 9.5,
-	and that of Python3 from 3.5 to 3.6.  The default generator
-	for ports using <tt>cmake</tt> has been switched to
-	<tt>ninja</tt>.</p>
-
-      <p>Some major version updates are: <tt>pkg</tt> 1.10.1, Firefox
-	54.0.1, and Chromium 59.0.3071.115.</p>
-
-      <p>Behind the scenes, antoine@ ran 36 exp-runs to test version
-	updates, make the CRAN ports platform-independent, test installing
-	bsdgrep(1) as <tt>/usr/bin/grep</tt>, test LLVM updates, test
-	the ino64 project, and perform Makefile cleanups.</p>
-    <hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>Core's activities during the second quarter culminated in
-	the introduction of two new initiatives during BSDCan:</p>
-
-      <ul>
-	<li>Extending FreeBSD Project Membership</li>
-
-	<li>The FreeBSD Community Process</li>
-      </ul>
-
-      <h3>FreeBSD Project Members</h3>
-
-      <p>FreeBSD Project Membership being extended to more than just
-	committers is a step that enables the Project to recognise and
-	reward people who support us in ways other than by writing
-	code.  People that organise conferences or user groups; who
-	are prominent supporters on social media; who triage bug
-	reports and who test changes; and many others who contribute
-	in various ways, are deserving of recognition for the support
-	that they give to the Project.  Core hopes that this will both
-	encourage more people to volunteer their time and effort on
-	behalf of the Project, and encourage those who already do to stick
-	with the Project, if not become more deeply involved.</p>
-
-      <p>The naming for the new group of non-committer Project members
-	took a few tries to get right: having tried, and rejected,
-	"Contributor" and then "Associate", Core
-	took the view that since what they were offerring was formal
-	Project Membership, then that was the right thing to call it.
-	Committers thus become those Project Members with access to
-	commit to the Project's code repositories.  Project Members
-	receive an @FreeBSD.org e-mail address, access to various
-	Project hardware, access to internal mailing lists and other
-	communications channels, and invitations to attend Developer
-	Summits in their own right.  Committers in addition have
-	commit rights in the Subversion repositories and GitHub, and
-	active Committers can vote in Core team elections.</p>
-
-      <h3>The FreeBSD Community Process</h3>
-
-      <p>This is an idea that has a long pedigree within other projects,
-	and FreeBSD is very consciously modelling its implementation on
-	what has worked elsewhere.  When a significantly disruptive or
-	wide-scale change is proposed, we should have a formal
-	mechanism for documenting the change and what it implies.
-	Interested parties can then respond and the change can be
-	evolved into the best fit for all users, or else it can be
-	found to be impracticable and withdrawn.  The documentation of
-	the change will remain as a point of reference should the same
-	or a similar proposal come up in the future.  Creating a more
-	formal process should help avoid endless sterile arguments
-	about what needs to be done, without anyone feeling they have
-	sufficient investment in the idea nor backing from the
-	majority of the project to justify putting in the work to
-	achieve the desired result.</p>
-
-      <p>The very first FCP &#8212; FCP 0 &#8212; describes the
-	process itself.  At the time of this writing, Core is voting on
-	accepting the initial document, which can be viewed in the
-	Project's <a href="https://github.com/freebsd/fcp/blob/master/fcp-0000.md" shape="rect">Github
-	repository</a>.  Two new mailing lists have been created:
-	fcp@FreeBSD.org is the channel for receiving notifications of
-	new FCP proposals and discussing their content, whilst
-	fcp-editors@FreeBSD.org exists to provide help with the
-	process of drafting the FCP documents.</p>
-
-      <h3>Other Core activities</h3>
-
-      <p>Core is delighted to announce that Gordon Tetlow has joined
-	the Security Officer team, and will be working on managing the
-	Security Team caseload, freeing up other members to concentrate on
-	the more technical aspects of vulnerability remediation.  In
-	addition, Ed Maste has joined the Security Team and is available to
-	assist the Security Officers where necessary.</p>
-
-      <p>Although Florian Smeets had to step down, the postmaster team
-	has recruited three new members and is now back up to
-	strength.</p>
-
-      <p>Considering the desirability of a number of fixes that have
-	been merged into 10-STABLE since the 10.3 release, core has
-	approved a 10.4 release to occur shortly after the 11.1
-	release.  This will be a normal support-lifetime release,
-	unlike the extended lifetime of the 10.3 release, so the
-	overall support lifetime for the 10.x branch will not be
-	significantly extended.</p>
-
-      <p>During this quarter, Core has approved issuing three new
-	commit bits.  Please welcome:</p>
-
-      <ul>
-	<li>Vladimir Kondratyev (wulf@)</li>
-
-	<li>Ryan Libby (rlibby@)</li>
-
-	<li>Kyle Evans (kevans@)</li>
-      </ul>
-
-      <p>Also, during this quarter, we had one person give up their
-	commit bit:</p>
-
-      <ul>
-	<li>Jordan Hubbard (jkh@)</li>
-      </ul>
-
-      <p>It is always unsettling when one of the Project's founding
-	members decides to move on, but Jordan's interests have
-	migrated away from FreeBSD-related projects and he has decided to
-	hang up his bit once and for all.</p>
-
-      <p>Core would like to thank NTTA (formerly Verio) for providing
-	hosting for a <tt>cvsup</tt> mirror for many years, and also for their
-	kind offer to provide ongoing hosting for a machine in their
-	Seattle facility.  Since we have no need for additional North
-	America hosting, we have declined their offer.</p>
-
-      <p>As usual, a number of questions have been raised about code
-	licensing and other matters related to intellectual property.
-	Ed Maste has registered "freebsd" on behalf of the
-	FreeBSD Foundation on the Mastodon social media network. The
-	"Unlicense" is suitable for code being imported into
-	libc.  We still have some code published under the old
-	4-clause style BSD license, where the extra clause refers
-	specifically to the University of California.  While UC has
-	generally approved removing that clause, we need to check with
-	all copyright holders before changing any remaining 4-clause
-	licensing.</p>
-
-      <p>Core, along with the Security Team, are monitoring developments
-	concerning the "Stack Clash" vulnerability that hit
-	the headlines during June.  Changes to the stack-guard
-	mitigation system are underway as a response to the
-	proof-of-concept published by Qualys.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSDFoundation.org/" title="https://www.FreeBSDFoundation.org/">FreeBSD Foundation Website</a></td><td>
-	    URL: <a href="https://www.FreeBSDFoundation.org/" title="FreeBSD Foundation Website">https://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/06/FreeBSD-Foundation-Q2-2017-Update.pdf" title="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/06/FreeBSD-Foundation-Q2-2017-Update.pdf">FreeBSD Foundation Quarterly Newsletter</a></td><td>
-	    URL: <a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/06/FreeBSD-Foundation-Q2-2017-Update.pdf" title="FreeBSD Foundation Quarterly Newsletter">https://www.FreeBSDfoundation.org/wp-content/uploads/2017/06/FreeBSD-Foundation-Q2-2017-Update.pdf</a></td></tr></table><p>
-	Contact:
-	  Deb
-	  Goodkin
-	 &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>Last quarter the Foundation was busy supporting the FreeBSD
-	Project in so many ways!  We brought on two interns from the
-	University of Waterloo who were extremely productive, from
-	working on a continuous integration project to adding MSDOS
-	FAT filesystem support to <tt>makefs</tt>.  We continued
-	helping to accelerate OS changes with our internal staff of
-	software developers, as well as funding outside software
-	development projects, and continued promoting FreeBSD by
-	participating in technology conferences around the world.  To
-	encourage more commercial users to donate to the Foundation,
-	we launched a new partnership program.  The FreeBSD 11.1
-	release effort has been led by a full-time Foundation
-	employee, to continue keeping releases timely and reliable.
-	Finally, we led the effort to celebrate the newly declared
-	FreeBSD Day, to help raise awareness of FreeBSD around the
-	world!</p>
-
-      <p>Below, you can read some of the highlights from our Q2
-	newsletter, and find writeups throughout this status report
-	from Foundation staff members including Ed Maste, Kostik
-	Belousov, and Glen Barber.  Don't forget, we are 100%
-	funded by donations.  Please take a moment to <a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">donate
-	  now</a>, so we can continue supporting the FreeBSD Project and
-	community worldwide!</p>
-
-      <p>Q2 Development Projects Summary</p>
-
-      <p>Our hard work continues into the 2nd quarter of 2017.
-	Please take a look at the highlights from our more recent
-	Development Projects summaries.</p>
-
-      <p>April: FreeBSD USB Mass Storage Target Project Update</p>
-
-      <p>The Foundation awarded a project grant to Edward Tomasz
-	Napiera&#322;a to develop a USB mass storage target driver, using
-	the FreeBSD CAM Target Layer (CTL) as a backend.  This project
-	allows FreeBSD on an embedded platform, such as a BeagleBone
-	Black or Raspberry Pi Zero, to emulate a USB mass storage
-	target, commonly known as a USB flash stick.  Read more at
-	<a href="https://www.FreeBSDfoundation.org/blog/april-2017-development-projects-update/" shape="rect">https://www.FreeBSDfoundation.org/blog/april-2017-development-projects-update/</a>.</p>
-
-      <p>May: Foundation Brings on Co-Op Students</p>
-
-      <p>At the beginning of May we embarked on a new path in the
-	FreeBSD Foundation, with the hiring of co-operative education
-	(co-op) students from the University of Waterloo.  The
-	University of Waterloo is a pioneer and leader in
-	co-operative education, with 100% of Engineering students
-	and a majority of Computer Science students participating in
-	co-op programs.  Read more at <a href="https://www.FreeBSDfoundation.org/blog/may-2017-development-projects-update/" shape="rect">https://www.FreeBSDfoundation.org/blog/may-2017-development-projects-update/</a>.</p>
-
-      <p>June: FreeBSD Foundation 2017 Project Proposal
-	Solicitation (contributed by Ed Maste)</p>
-
-      <p>One of the ways the Foundation supports FreeBSD is by
-	providing development grants for work on individual
-	projects.  These allow developers to propose projects they
-	would like to undertake to improve FreeBSD and request funding
-	to perform that work.  The Foundation is always willing to
-	receive proposals, but will occasionally issue a call for
-	proposals to highlight specific areas of focus and to be
-	able to collect and evaluate a group of proposals.</p>
-
-      <p>The proposal submission deadline was July 14, 2017, but as
-	mentioned above, people are welcome to submit proposals at
-	any time.</p>
-
-      <p>Although proposals may address any FreeBSD subsystem or
-	infrastructure, we are particularly interested in receiving
-	proposals related to:</p>
-
-      <ul>
-	<li>Improvements to the security of FreeBSD itself, or of
-	  applications running on FreeBSD</li>
-
-	<li>New test cases, improved test infrastructure, and
-	  quality assurance</li>
-
-	<li>Improved software development tools</li>
-
-	<li>Projects to improve community collaboration and
-	  communication</li>
-
-	<li>Improving the FreeBSD "out of the box" experience
-	  for new users on various hardware platforms</li>
-
-	<li>Establishing FreeBSD as a leader in advancing projects of
-	  shared interest (such as ZFS, LLVM, or
-	  <tt>libarchive</tt>)</li>
-      </ul>
-
-      <p>More details can be found at <a href="https://www.FreeBSDfoundation.org/blog/FreeBSD-foundation-2017-project-proposal-solicitation/" shape="rect">https://www.FreeBSDfoundation.org/blog/FreeBSD-foundation-2017-project-proposal-solicitation/</a>.
-	The full project proposal submission guidelines can be found
-	at <a href="http://cts.vresp.com/c/?FreeBSDFoundation/d364934d4d/TEST/1b229d9af7" shape="rect">http://cts.vresp.com/c/?FreeBSDFoundation/d364934d4d/TEST/1b229d9af7</a>.</p>
-
-      <p>Please do not hesitate to contact
-	proposals@FreeBSDfoundation.org with any questions.</p>
-
-      <p>Announcing the New Partnership Program (contributed by Deb
-	Goodkin)</p>
-
-      <p>I'm excited to announce our new FreeBSD Foundation
-	Partnership Program!  Our work is 100% supported by
-	donations from individuals and organizations.  With a
-	spending budget of $1,500,000, we rely on large donations
-	from our commercial users to help us sustain and increase
-	our support.  Recognizing the value of these donations, and
-	putting together a sustainable funding model, we wanted to
-	institute benefits that highlighted this support, and
-	recognize these donors in productive ways.  Partnerships are
-	an avenue to assist commercial users by helping them get on
-	board more quickly with FreeBSD, share their needs with the
-	community, and facilitate collaboration with FreeBSD
-	developers.  We believe that building these relationships
-	with commercial users will contribute to keeping FreeBSD
-	relevant and help provide a sustainable and healthy
-	ecosystem.</p>
-
-      <p>You can check out our updated donor pages to see how we are
-	acknowledging our Partners at <a href="https://www.FreeBSDfoundation.org/donors/" shape="rect">https://www.FreeBSDfoundation.org/donors/</a>.
-	You can also find out more about this new program at <a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>.</p>
-
-      <p>When I was in China last week, I had a chance to talk to a
-	few companies about our new partnership program, and it
-	definitely generated more interest in supporting our
-	efforts.</p>
-
-      <p>We are continuing to reach out to commercial users for help
-	that will enable us to provide more outreach and support for
-	FreeBSD.  This includes funding more projects to improve FreeBSD,
-	providing FreeBSD education and training, and recruiting more
-	contributors to the Project.  We can only provide the above
-	support with your donations, and we need your help to
-	connect us with your companies.  Please consider notifying
-	your organization about our new Partnership Program and helping
-	to connect us with the appropriate contacts at your
-	company.</p>
-
-      <p>Your donations will help us:</p>
-
-      <ul>
-	<li>Accelerate improvements and add new features to
-	  FreeBSD</li>
-
-	<li>Support release engineering efforts full-time</li>
-
-	<li>Create and provide FreeBSD educational and training
-	  material</li>
-
-	<li>Provide face-to-face opportunities for developers to
-	  work together</li>
-
-	<li>Improve and support FreeBSD infrastructure</li>
-      </ul>
-
-      <p>We need your support to continue improving FreeBSD.</p>
-
-      <p>Q2 2017 Conference Recaps</p>
-
-      <p>From sponsoring events to attending conferences, the
-	Foundation continued its mission of advocacy in the second
-	quarter of 2017.  Over the past few weeks, members of the
-	Foundation team represented the Project and the Foundation
-	at events around the world.  Below are just a few of the
-	conference recaps.</p>
-
-      <p>FOSSASIA 2017 (contributed by Philip Paeps)</p>
-
-      <p>The Foundation kindly funded part of my travel from Tokyo to
-	Singapore to attend FOSSASIA.  I gave the "FreeBSD is not
-	a Linux Distribution" presentation that Foundation
-	board member George Neville-Neil wrote for Open Source China
-	in December.  My presentation was well-attended, and I got a
-	lot of good questions from the primarily Linux-oriented
-	audience.  Read more at <a href="https://www.FreeBSDfoundation.org/blog/fossasia-2017-trip-report-philip-paeps/" shape="rect">https://www.FreeBSDfoundation.org/blog/fossasia-2017-trip-report-philip-paeps/</a>.</p>
-
-      <p>OSCON 2017 (contributed by Ed Maste)</p>
-
-      <p>I represented the FreeBSD Foundation at OSCON 2017, which took place
-	May 8-11, 2017, in Austin, TX: <a href="https://conferences.oreilly.com/oscon/oscon-tx" shape="rect">https://conferences.oreilly.com/oscon/oscon-tx</a>.</p>
-
-      <p>The Foundation booth was also staffed by FreeBSD committer
-	Brad Davis and Doug Mcintire from Netgate.  We met up
-	Wednesday morning to set up the table.  We were part of a
-	"nonprofit pavilion" which consisted of eight or
-	so tables, located between Open Camps and Operation
-	Code.</p>
-
-      <p>To help attract booth traffic, I brought a Raspberry Pi 3,
-	with a small LCD display attached.  As a demo, the Raspberry
-	Pi showed a video of a Gource rendering of changes to the
-	FreeBSD source tree over time (see example at <a href="https://www.youtube.com/watch?v=vZ8Sspua0Ks" shape="rect">https://www.youtube.com/watch?v=vZ8Sspua0Ks</a>).
-	Read more at <a href="https://www.FreeBSDfoundation.org/blog/conference-recap-oscon-2017/" shape="rect">https://www.FreeBSDfoundation.org/blog/conference-recap-oscon-2017/</a>.</p>
-
-      <p>Rootconf 2017 (contributed by Philip Paeps)</p>
-
-      <p>In mid-May I presented at Rootconf 2017 in Bangalore.
-	Rootconf is India's principal conference where systems and
-	operations engineers share real-world knowledge about
-	building reliable systems: <a href="https://rootconf.in/2017/" shape="rect">https://rootconf.in/2017/</a>.</p>
-
-      <p>As always, it was interesting to hear the difficulties
-	people face trying to run reliable systems on less reliable
-	platforms.  While many of the presentations were very
-	Linux-specific and not very exciting to me, a couple of
-	talks did catch my eye.</p>
-
-      <p>I particularly enjoyed the talk by Aruna Sankaranarayanan
-	(<a href="https://www.youtube.com/watch?v=XQJ7YhVoSWI&amp;feature=youtu.be" shape="rect">https://www.youtube.com/watch?v=XQJ7YhVoSWI&amp;feature=youtu.be</a>)
-	explaining how Mapbox takes advantage of Amazon's "spot
-	pricing" mechanism by spawning and shutting down
-	machines at different price points to optimize for cost
-	without compromising availability.  Their spotswap <a href="https://github.com/mapbox/spotswap/" shape="rect">https://github.com/mapbox/spotswap/</a>
-	software has been released under a BSD license.  It sounds
-	as though it should be possible to port this to FreeBSD with
-	minimal effort.  Read more at <a href="https://www.FreeBSDfoundation.org/blog/rootconf-2017-trip-report-philip-paeps/" shape="rect">https://www.FreeBSDfoundation.org/blog/rootconf-2017-trip-report-philip-paeps/</a>.</p>
-
-      <p>BSDCan 2017/FreeBSD Developers Summit (contributed by Deb
-	Goodkin)</p>
-
-      <p>One of our initiatives is to assist in providing
-	face-to-face knowledge sharing and development opportunities
-	around the world.  One way we do this is by sponsoring
-	BSD-related conferences and FreeBSD Developer and Vendor
-	Summits.  We recently sponsored both BSDCan 2017 and the
-	FreeBSD Developer and Vendor Summit in Ottawa, Ontario, Canada,
-	which took place June 7-10, 2017.  Many of our board and
-	staff members attended the summit and conference to run
-	tutorials, give presentations, lead sessions, work with
-	developers, give demos, and share knowledge.</p>
-
-      <p>In addition, this year we were pleased to bring our new
-	University of Waterloo interns to the conference where they
-	had the opportunity to demonstrate some of their projects at
-	the Foundation table.  Read more at <a href="https://www.FreeBSDfoundation.org/blog/conference-recap-bsdcan-2017FreeBSD-developers-summit/" shape="rect">https://www.FreeBSDfoundation.org/blog/conference-recap-bsdcan-2017FreeBSD-developers-summit/</a>.</p>
-
-      <p>Open Travel Grant Applications</p>
-
-      <p>The Foundation recognizes the importance of bringing
-	members of the FreeBSD community face-to-face to both further
-	development of the Project and spread the word about FreeBSD.
-	Travel grants are available to community members who need
-	assistance with travel expenses for attending conferences
-	related to FreeBSD development and advocacy.  Please note: the
-	travel grant policy has been recently updated.  Please
-	carefully review it before submitting your application.</p>
-
-      <p>More information about travel grants is available at: <a href="https://www.FreeBSDfoundation.org/what-we-do/grants/travel-grants/" shape="rect">https://www.FreeBSDfoundation.org/what-we-do/grants/travel-grants/</a>.</p>
-
-      <p>FreeBSD Day was June 19! (contributed by Anne Dickison)</p>
-
-      <p>June 19th was declared FreeBSD Day!  Thank you to everyone who
-	joined us in honoring the FreeBSD Project's pioneering legacy
-	and continuing impact on technology.  Find out more about
-	FreeBSD Day and how we celebrated here at <a href="https://www.FreeBSDfoundation.org/blog/happy-FreeBSD-day/" shape="rect">https://www.FreeBSDfoundation.org/blog/happy-FreeBSD-day/</a>.</p>
-
-      <p>Upcoming Events</p>
-
-      <p>Find out about upcoming Foundation events at <a href="https://www.FreeBSDfoundation.org/news-and-events/upcoming-events/" shape="rect">https://www.FreeBSDfoundation.org/news-and-events/upcoming-events/</a>.</p>
-
-      <p>FreeBSD Journal</p>
-
-      <p>The May/June 2017 Issue of the FreeBSD Journal is now
-	available.  Don't miss articles on FreeBSD's Firewall Feast,
-	CADETS: Blending Tracing and Security on FreeBSD, Toward
-	Oblivious Sandboxing with Capsicum, and more.  (<a href="https://www.FreeBSDfoundation.org/past-issues/security/" shape="rect">https://www.FreeBSDfoundation.org/past-issues/security/</a>)</p>
-
-      <p>Did you miss the March/April issue?  Check out articles on
-	CFEngine, Puppet on FreeBSD, Vagrant, and more!  (<a href="https://www.FreeBSDfoundation.org/past-issues/configuration-management/" shape="rect">https://www.FreeBSDfoundation.org/past-issues/configuration-management/</a>)
-	As a recent addition of functionality, browser-based
-	subscribers now have the ability to download and share PDFs
-	of the articles!</p>
-
-      <p>Sample Issue!  If you've ever wanted to read through an
-	entire issue of the FreeBSD Journal, now's your chance.
-	Download the sample issue from <a href="https://mydigitalpublication.com/publication/?i=296880#{&quot;issue_id&quot;:296880,&quot;numpages&quot;:1,&quot;page&quot;:1}" shape="rect">https://mydigitalpublication.com/publication/?i=296880#{"issue_id":296880,"numpages":1,"page":1}</a>
-	and be sure to share with your friends and colleagues.  Not
-	a subscriber?  Sign up today at <a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>.</p>
-
-      <p>More information about the Foundation's doings and
-	goings-on can be found in our own quarterly newsletter, linked
-	above.</p>
-    <hr /><h2><a name="The-Postmaster-Team" href="#The-Postmaster-Team" id="The-Postmaster-Team">The Postmaster Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/administration.html#t-postmaster" title="https://www.FreeBSD.org/administration.html#t-postmaster">The Postmaster Team</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/administration.html#t-postmaster" title="The Postmaster Team">https://www.FreeBSD.org/administration.html#t-postmaster</a></td></tr></table><p>
-	Contact:
-	  David
-	  Wolfskill
-	 &lt;<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Larry
-	  Rosenman
-	 &lt;<a href="mailto:ler@FreeBSD.org">ler@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Ryan
-	  Steinmetz
-	 &lt;<a href="mailto:zi@FreeBSD.org">zi@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Eygene
-	  Ryabinkin
-	 &lt;<a href="mailto:rea@FreeBSD.org">rea@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Remko
-	  Lodder
-	 &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kurt
-	  Jaeger
-	 &lt;<a href="mailto:pi@FreeBSD.org">pi@FreeBSD.org</a>&gt;
-	</p>
-      <p> Postmaster handles the mail flow for the FreeBSD project.</p>
-
-      <p>Clusteradm provides us with four jails: mailman, mailarchive,
-	mx1, and mx2.  In addition, there is some part of the setup
-	running on freefall.FreeBSD.org.  The system uses
-	<tt>postfix</tt>, <tt>mailman</tt>, <tt>spamassassin</tt>, and
-	some other tools from the ports tree to handle the mail flow.
-	We use a very small, non-public Subversion repository for
-	parts of the configuration.</p>
-
-      <p>During Q2, Larry Rosenman, Kurt Jaeger, Eygene Ryabinkin,
-	Remko Lodder and Ryan Steinmetz joined the Postmaster Team,
-	and Florian Smeets left the Postmaster Team.</p>
-
-      <p>Thanks to Florian for his long service in that role!  David
-	Wolfskill is planning to leave the role as soon as the new
-	team members are settled.  Vsevolod Stakhov plans to provide
-	us with support to integrate <tt>rspamd</tt> into the setup,
-	as well.</p>
-
-      <p>The workload for the Postmaster Team is not high, but the
-	complexity of the setup has its own demands.</p>
-    <h3>Open tasks:</h3><ol><li>We need to improve our internal documentation of workflows and
-	processes.</li><li>We should consider adding some monitoring to provide
-	quarterly numbers on the mail flow.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="64-bit-Inode-Numbers" href="#64-bit-Inode-Numbers" id="64-bit-Inode-Numbers">64-bit Inode Numbers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D10439" title="https://reviews.FreeBSD.org/D10439">Phabricator Review</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D10439" title="Phabricator Review">https://reviews.FreeBSD.org/D10439</a></td></tr></table><p>
-	Contact:
-	  Gleb
-	  Kurtsou
-	 &lt;<a href="mailto:gleb@FreeBSD.org">gleb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Konstantin
-	  Belousov
-	 &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Kirk
-	  McKusick
-	 &lt;<a href="mailto:mckusick@FreeBSD.org">mckusick@FreeBSD.org</a>&gt;
-	</p>
-      <p>The 64-bit inode project was completed and merged into
-	FreeBSD�12 on May 23, 2017.  It extends the <tt>ino_t</tt>,
-	<tt>dev_t</tt>, and <tt>nlink_t</tt> types to be 64-bit
-	integers.  It modifies the <tt>struct dirent</tt> layout to
-	add a <tt>d_off</tt> field, increases the size of
-	<tt>d_fileno</tt> to 64 bits, increases the size of
-	<tt>d_namlen</tt> to 16 bits, and changes the required
-	alignment of the structure.  It increases the <tt>struct
-	statfs</tt> <tt>f_mntfromname[]</tt> and
-	<tt>f_mntonname[]</tt> array lengths from MNAMELEN to
-	1024.</p>
-
-      <p>ABI breakage is mitigated by providing compatibility using
-	versioned symbols, ingenious use of the existing padding in
-	structures, and employing various other tricks.
-	Unfortunately, not everything can be fixed, especially outside
-	the base system.  For instance, third-party APIs which pass
-	<tt>struct stat</tt> as parameters are broken in backward- and
-	forward-incompatible ways.</p>
-
-      <p>The ABI for <tt>kinfo</tt>-consuming sysctl MIBs is changed in a
-	backward-compatible way, but there is no general mechanism to
-	handle other sysctl MIBS which return structures where the
-	layout has changed.  In our consideration, this breakage is
-	either in management interfaces, where we usually allow ABI
-	slippage, or is not important.</p>
-
-      <p>The layout of <tt>struct xvnode</tt> changed, and no
-	compatibility shims are provided.</p>
-
-      <p>For <tt>struct xtty</tt>, the <tt>dev_t tty</tt> device
-	member was reduced to be just <tt>uint32_t</tt>.  It was
-	decided that maintaining ABI compatability in this case is
-	more useful than reporting a 64-bit <tt>dev_t</tt> value, for
-	the sake of <tt>pstat</tt>.</p>
-
-      <p>Updating note: <strong>strictly</strong> follow the instructions
-	in <tt>UPDATING</tt>.  Build and install the new kernel with the
-	<tt>COMPAT_FREEBSD11</tt> option enabled, then reboot, and
-	only then install the new world.</p>
-
-      <p>Credits: The 64-bit inode project, also known as ino64,
-	started life many years ago as a project by Gleb Kurtsou
-	(gleb).  Kirk McKusick (mckusick) then picked up and updated
-	the patch, and acted as a flag-waver.  Feedback, suggestions,
-	and discussions were carried out by Ed Maste (emaste), John
-	Baldwin (jhb), Jilles Tjoelker (jilles), and Rick Macklem
-	(rmacklem).  Kris Moore (kris) performed an initial ports
-	investigation followed by an exp-run by Antoine Brodin
-	(antoine).  Essential and all-embracing testing was done by
-	Peter Holm (pho).  The heavy lifting of coordinating all these
-	efforts and bringing the project to completion were done by
-	Konstantin Belousov (kib).  </p>
-    <p>This project was sponsored by The FreeBSD Foundation (emaste, kib).</p><hr /><h2><a name="Capability-Based-Network-Communication-for-Capsicum/CloudABI" href="#Capability-Based-Network-Communication-for-Capsicum/CloudABI" id="Capability-Based-Network-Communication-for-Capsicum/CloudABI">Capability-Based Network Communication for Capsicum/CloudABI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/NuxiNL/arpc" title="https://github.com/NuxiNL/arpc">ARPC: GRPC-Like RPC Library That Supports File Descriptor Passing</a></td><td>
-	    URL: <a href="https://github.com/NuxiNL/arpc" title="ARPC: GRPC-Like RPC Library That Supports File Descriptor Passing">https://github.com/NuxiNL/arpc</a></td></tr><tr><td><a href="https://github.com/NuxiNL/flower" title="https://github.com/NuxiNL/flower">Flower: A Label-Based Network Backplane</a></td><td>
-	    URL: <a href="https://github.com/NuxiNL/flower" title="Flower: A Label-Based Network Backplane">https://github.com/NuxiNL/flower</a></td></tr></table><p>
-	Contact:
-	  Ed
-	  Schouten
-	 &lt;<a href="mailto:ed@nuxi.nl">ed@nuxi.nl</a>&gt;
-	</p>
-      <p>One of the weaknesses of Capsicum and CloudABI is that it is
-	not easy to develop applications that need to make outgoing
-	network connections, since system calls like
-	<tt>connect()</tt> and <tt>sendto()</tt> are disabled.  Though
-	we can sometimes work around this by ensuring that the
-	sandboxed process already possesses socket file descriptors on
-	startup, this does not allow the destination process to be
-	restarted, moved to a different network address, be load
-	balanced, etc..</p>
-
-      <p>Coming up with a solution for this is quite important for me,
-	as I am currently working on making CloudABI work on top of
-	Kubernetes, Google's open source cluster management suite.
-	The idea is that Kubernetes will schedule CloudABI processes
-	instead of Docker containers.  All of these CloudABI processes
-	will have their dependencies on other services in the cluster
-	injected explicitly, making internal communication very
-	secure.  All of this is intended to work on FreeBSD as well, of
-	course!</p>
-
-      <p>To solve this problem, I've been working on a daemon called
-	Flower (read: flow-er) that allows software to register
-	services and connect to them.  Servers are identified by a set
-	of labels with values (e.g., <tt>{datacenter: 'frankfurt',
-	service: 'mysql'}</tt>).  Clients can connect these servers by
-	providing the corresponding label(s).  Flower's security model is
-	capability-based, just like Capsicum.  The ability to bind and
-	connect can be limited by permanently constraining labels to
-	certain values.</p>
-
-      <p>Flower has been designed not to act as a proxy.  It does
-	not copy any data.  It merely forwards existing socket file
-	descriptors or creates UNIX socket pairs and hands these out
-	to its clients and servers.  To realize this, processes
-	communicate with Flower using an RPC library called ARPC.
-	ARPC is a very simple clone of Google's GRPC, with the special
-	feature that messages (Protobufs) can have file descriptors
-	attached.</p>
-    <p>This project was sponsored by Nuxi, the Netherlands.</p><h3>Open tasks:</h3><ol><li>Finish implementing the Flower code.</li><li>Integrate Flower with the Kubernetes/CloudABI runtime.</li><li>Release the Kubernetes/CloudABI runtime as open source
-	software.</li></ol><hr /><h2><a name="Ceph-on-FreeBSD" href="#Ceph-on-FreeBSD" id="Ceph-on-FreeBSD">Ceph on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ceph.com" title="http://ceph.com">Ceph Main Site</a></td><td>
-	    URL: <a href="http://ceph.com" title="Ceph Main Site">http://ceph.com</a></td></tr><tr><td><a href="https://github.com/ceph/ceph" title="https://github.com/ceph/ceph">Main Repository</a></td><td>
-	    URL: <a href="https://github.com/ceph/ceph" title="Main Repository">https://github.com/ceph/ceph</a></td></tr><tr><td><a href="https://github.com/wjwithagen/ceph" title="https://github.com/wjwithagen/ceph">My FreeBSD Fork</a></td><td>
-	    URL: <a href="https://github.com/wjwithagen/ceph" title="My FreeBSD Fork">https://github.com/wjwithagen/ceph</a></td></tr></table><p>
-	Contact:
-	  Willem Jan
-	  Withagen
-	 &lt;<a href="mailto:wjw@digiware.nl">wjw@digiware.nl</a>&gt;
-	</p>
-      <p>Ceph is a distributed object store and file system designed to provide
-	excellent performance, reliability and scalability.</p>
-
-      <ul>
-	<li><p>Object Storage</p>
-
-	  <p>Ceph provides seamless access to objects using native
-	    language bindings or <tt>radosgw</tt>, a REST interface
-	    that is compatible with applications written for S3 and
-	    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>
-
-	  <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>
-      </ul>
-
-      <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.  I aim to run a Ceph storage cluster of storage nodes
-	that are running ZFS, with user workstations running
-	<tt>bhyve</tt> on RBD disks that are stored in Ceph.</p>
-
-      <p>Compiling for FreeBSD will now build most of the tools
-	available in Ceph.</p>
-
-      <p>The most important changes since the last report are:</p>
-
-      <ul>
-	<li>Ceph has released release candidate v12.1.0 (aka
-	  Luminous); the corresponding packaging is sitting in my tree
-	  waiting for Luminous to be actually released.</li>
-
-	<li><tt>ceph-fuse</tt> works, and allows mounting of
-	  <tt>cephfs</tt> filesystems.  The speed is not impressive,
-	  but it does work.</li>
-
-	<li><tt>rbd-ggate</tt> is available to create a Ceph
-	  <tt>rbd</tt> backed device.  <tt>rbd-ggate</tt> was
-	  submitted by Mykola Golub.  It works in a rather simple
-	  fashion: once a cluster is functioning, <tt>rbd
-	  import</tt> and <tt>rbd-ggate map</tt> are used to create
-	  <tt>ggate</tt>-like devices backed by the Ceph cluster.</li>
-      </ul>
-
-      <p>Other improvements since the previous report:</p>
-
-      <ul>
-	<li>Some bugs in the <tt>init-ceph</tt> code (needed for
-	  <tt>rc.d</tt>) are being fixed.</li>
-
-	<li>RBD and rados are functioning.</li>
-
-	<li>The needed compatability code was written so that FreeBSD and
-	  Linux daemons can operate together in a single cluster.</li>
-
-	<li>More of the awkward dependancies on Linux-isms are deleted
-	  &#8212; only <tt>/bin/bash</tt> is there to stay.</li>
-      </ul>
-
-      <p>The next forthcoming official release of Ceph is called
-	Luminous (v12.1.0).  As soon as it is available from upstream,
-	a port will be provided for FreeBSD.</p>
-
-      <p>To get things running on a FreeBSD system, run <tt>pkg install
-	  net/ceph-devel</tt> or clone <a href="https://github.com/wjwithagen/ceph" shape="rect">https://github.com/wjwithagen/ceph</a>,
-	check out the <tt>wip.freebsd.201707</tt> branch, and build
-	manually by running <tt>./do_freebsd.sh</tt> in the checkout
-	root.</p>
-
-      <p>Parts not (yet) included:</p>
-
-      <ul>
-	<li>KRBD &#8212; but <tt>rbd-ggate</tt> is usable in its
-	  stead.</li>
-
-	<li>BlueStore &#8212; FreeBSD and Linux have different AIO APIs,
-	  and that incompatibility needs to be resolved somehow.
-	  Additionally, there is discussion in FreeBSD about
-	  <tt>aio_cancel</tt> not working for all device types.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Run integration tests to see if the FreeBSD daemons will work
-	with a Linux Ceph platform.</li><li>Investigate the keystore, which can be embedded in the
-	kernel on Linux and currently prevents building Cephfs and
-	some other parts.  The first question is whether it is really
-	required, or if only KRBD requires it.</li><li>Scheduler information is not used at the moment, because the
-	schedulers work rather differently between Linux and FreeBSD.
-	But at a certain point in time, this will need some attention
-	(in <tt>src/common/Thread.cc</tt>).</li><li>Improve the FreeBSD 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 FreeBSD- and ZFS-compatible.</li><li>Build a test cluster and start running some of the
-	teuthology integration tests on it.  Teuthology wants to build
-	its own <tt>libvirt</tt>, and that does not quite work with all
-	the packages FreeBSD already has in place.  There are many
-	details to work out here.</li><li>Design a virtual disk implementation that can be used with
-	<tt>bhyve</tt> and attached to an RBD image.</li></ol><hr /><h2><a name="DTS-Updates" href="#DTS-Updates" id="DTS-Updates">DTS Updates</a></h2><p>
-	Contact:
-	  Emmanuel
-	  Vadot
-	 &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>DTS (Device Tree Source) files provide a human-readable
-	source description of the hardware resources for a given
-	computer system (such as ARM- or MIPS-based embedded boards).
-	The DTS source representation must be compiled into a binary
-	format in order to be linked into the kernel and used to
-	locate devices at runtime.</p>
-
-      <p>The DTS files in FreeBSD were updated to match the versions from
-	Linux 4.11, to represent more modern devices and provide more
-	accurate representations.</p>
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Coda-revival" href="#Coda-revival" id="Coda-revival">Coda revival</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/trasz/FreeBSD/tree/coda" title="https://github.com/trasz/FreeBSD/tree/coda">GitHub Repository</a></td><td>
-	    URL: <a href="https://github.com/trasz/FreeBSD/tree/coda" title="GitHub Repository">https://github.com/trasz/FreeBSD/tree/coda</a></td></tr></table><p>
-	Contact:
-	  Edward Tomasz
-	  Napiera&#322;a
-	 &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Coda is a distributed file system developed as a research
-	project at Carnegie Mellon University, descended from a older
-	version of the Andrew File System.  It got dropped from FreeBSD
-	some five years ago, due to not having been adopted for a
-	MPSAFE world.  The focus for this current project is to bring
-	it back into sufficiently workable shape that it could return
-	to the kernel.  It is currently in a working condition.  Work
-	is underway to test it better, fix whatever issues are found,
-	and commit it to 12-CURRENT.</p>
-    <p>This project was sponsored by Chalmers University of Technology.</p><h3>Open tasks:</h3><ol><li>Additional testing.</li><li>Update the userspace components (<tt>net/coda_client</tt>
-	and <tt>net/coda_server</tt>).</li></ol><hr /><h2><a name="FreeBSD-Driver-for-the-Annapurna-Labs-ENA" href="#FreeBSD-Driver-for-the-Annapurna-Labs-ENA" id="FreeBSD-Driver-for-the-Annapurna-Labs-ENA">FreeBSD Driver for the Annapurna Labs ENA</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html" title="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html">Enhanced Networking Guide</a></td><td>
-	    URL: <a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html" title="Enhanced Networking Guide">http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html</a></td></tr></table><p>
-	Contact:
-	  Marcin
-	  Wojtas
-	 &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Micha&#322;
-	  Krawczyk
-	 &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	</p>
-      <p>The ENA (Elastic Network Adapter) is a 25G SmartNIC developed by
-	Annapurna Labs and is based on a custom ARMv8 chip.  This is a
-	high-performance networking card available in the AWS offerings.
-	It introduces enhancements in network utilization scalability
-	on EC2 machines under the control of various operating systems, in
-	particular FreeBSD.</p>
-
-      <p>The goal of FreeBSD enablement is to provide top performance and
-	a wide range of monitoring and management features such
-	as:</p>
-
-      <ul>
-	<li>multiple queue modes</li>
-
-	<li>hardware offloads (rx and tx checksum)</li>
-
-	<li>an admin queue</li>
-
-	<li>asynchronous notifications</li>
-
-	<li>robust hardware access</li>
-
-	<li>a scalable number of MSI-X vectors</li>
-
-	<li>hardware counters</li>
-
-	<li>watchdog mechanism</li>
-
-	<li>LRO</li>
-
-	<li>RSS</li>
-      </ul>
-
-      <p>The driver is available in the kernel source tree as of
-	r318647.</p>
-    <p>This project was sponsored by Annapurna Labs &#8212; an Amazon company.</p><h3>Open tasks:</h3><ol><li>Add RSS configuration from userspace (via sysctls).</li><li>Add support for LLQ mechanisms.</li></ol><hr /><h2><a name="Intel-10G-Driver-Update" href="#Intel-10G-Driver-Update" id="Intel-10G-Driver-Update">Intel 10G Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D11232" title="https://reviews.FreeBSD.org/D11232">Commit Adding X553 ix/ixv Support</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D11232" title="Commit Adding X553 ix/ixv Support">https://reviews.FreeBSD.org/D11232</a></td></tr></table><p>
-	Contact:
-	  Chris
-	  Galazka
-	 &lt;<a href="mailto:krzysztof.galazka@intel.com">krzysztof.galazka@intel.com</a>&gt;
-	<br />
-	Contact:
-	  Jeb
-	  Cramer
-	 &lt;<a href="mailto:jeb.j.cramer@intel.com">jeb.j.cramer@intel.com</a>&gt;
-	</p>
-      <p>The <tt>ix</tt> and <tt>ixv</tt> network interface drivers
-      support a variety of Intel network interfaces, with line
-      speeds at 10 Gbit/second.</p>
-
-      <p>This quarter, the drivers gained support for the X553
-      network interface, which is found on System-on-a-Chip devices
-      based on the Denverton platform.  This update should allow
-      FreeBSD to be more useful on a new class of hardware
-      platform.</p>
-
-    <p>Work is also underway to convert these drivers to use the
-      <tt>iflib</tt> network driver library, which should ease
-      future maintenance of the drivers, as well as the network
-      subsystem as a whole.</p>
-    <hr /><h2><a name="pNFS-Server-Plan-B" href="#pNFS-Server-Plan-B" id="pNFS-Server-Plan-B">pNFS Server Plan B</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt" title="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt">Testing Instructions</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt" title="Testing Instructions">http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt</a></td></tr></table><p>
-	Contact:
-	  Rick
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>&gt;
-	</p>
-      <p>Parallel NFS (pNFS) is an extension to the NFSv4 protocol that
-	allows for file accesses within a single logical mount to be
-	performed against multiple file servers, with the potential
-	for data access to occur in parallel.  The pNFS
-	"layout" in use specifies how the division occurs, with
-	metadata operations occurring against the main server, and
-	bulk data operations (read/write/setattr/etc.) occurring via
-	a layout-specific scheme between the client and the data
-	servers.</p>
-
-      <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 FreeBSD, with one FreeBSD server handling the metadata
-	operations and multiple FreeBSD servers configured to serve
-	data, is now ready for third-party testing.  If testing by
-	third parties goes well, I anticipate the code will be
-	merged into FreeBSD head in time for FreeBSD�12.  Fairly
-	recent FreeBSD or Linux systems should be usable as pNFS
-	clients for testing.  This server supports the File Layout,
-	which is supported by both of these clients.</p>
-
-      <p>There is no support for the Flex Files Layout or mirroring
-	at this time.  I hope to use the Flex Files Layout to add
-	mirroring support over the next year or so.  Striping is not
-	supported, and I have no plans for implementing this at the
-	moment.</p>
-
-      <p>The patched FreeBSD sources may now be accessed for testing
-	via either Subversion or download of a gzipped tarball.
-	They consist of a patched kernel and <tt>nfsd</tt> and can be
-	used on any FreeBSD�11 or later system.</p>
-    <h3>Open tasks:</h3><ol><li>Testing by others will be needed, now that the code is
-	available.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Marvell-Armada38x" href="#FreeBSD-on-Marvell-Armada38x" id="FreeBSD-on-Marvell-Armada38x">FreeBSD on Marvell Armada38x</a></h2><p>
-	Contact:
-	  Marcin
-	  Wojtas
-	 &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Zbigniew
-	  Bodek
-	 &lt;<a href="mailto:zbb@FreeBSD.org">zbb@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work proceeds to finalize the process of bringing support
-	for the Marvell Armada38x platform into FreeBSD head.</p>
-
-      <p>The most important parts of the recent effort are:</p>
-
-      <ul>
-	<li>Add the network driver (NETA)</li>
-
-	<li>Enable coherent <tt>busdma</tt> operation for all ARMv7 SoCs</li>
-
-	<li>Add various low-level optimizations, such as L1 cache
-	  prefetch and MBUS quirks</li>
-
-	<li>Enable PL310 L2 cache controller</li>
-
-	<li>Add SDHCI support</li>
-
-	<li>Fixes for the <tt>e6000sw</tt> driver and a rework of its
-	  PHY handling</li>
-
-	<li>Support multi-port PCIe operation</li>
-
-	<li>Various fixes and enhancements of the common Marvell code</li>
-
-	<li>Fix and enable support for performance counters (HWPMC)</li>
-      </ul>
-    <p>This project was sponsored by Stormshield, Semihalf, and Netgate.</p><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64" title="https://wiki.FreeBSD.org/arm64">FreeBSD arm64 Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/arm64" title="FreeBSD arm64 Wiki Page">https://wiki.FreeBSD.org/arm64</a></td></tr></table><p>
-	Contact:
-	  Andrew
-	  Turner
-	 &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for the Privilege Access Never (PAN) feature was
-	added.  This stops the kernel from accessing userspace
-	memory, except through specific instructions.  This helps
-	security by only allowing access to userspace via the
-	correct accessor functions.  This is enabled on all
-	supported CPUs that implement ARMv8.1 or later.</p>
-
-      <p>The <tt>pmap</tt> code now supports the Unprivileged
-	execute-never (UXN) and Privileged execute-never (PXN) bits
-	in the page tables.  These bits stop userspace and the
-	kernel, respectively, from executing instructions on any
-	marked page.</p>
-
-      <p>The performance of the pmap layer has been improved.  Many
-	of the cache handling function calls have been removed.
-	Some were needed early on to work around other bugs that
-	have now been fixed.  The removal of these calls has led to
-	a large performance improvement.</p>
-
-      <p>The kernel now uses <tt>crc32c</tt> instructions where
-	appropriate.  These are an optional set of instructions to
-	perform <tt>crc32c</tt> checksumming quickly without using a lookup
-	table.c</p>
-
-      <p>The <tt>VM_MEMATTR_WRITE_THROUGH</tt> memory attribute is
-	now supported.  This is used to allocate memory for the
-	framebuffer.  Previously, the kernel would use cached
-	memory; however, this leads to visual artifacts.  The
-	write-through flag fixes these by writing data out to
-	RAM.</p>
-
-      <p>The default linker on arm64 is now <tt>lld</tt>.  This
-	means that FreeBSD is able to build itself with just the components
-	in the base system, a big milestone!</p>
-    <hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="DTC" href="#DTC" id="DTC">DTC</a></h2><p>
-	Contact:
-	  Emmanuel
-	  Vadot
-	 &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>The in-tree DTC (Device Tree Compiler) was switched to use the
-	BSD-licensed version by default.  (The previous default DTC is
-	licensed under the GPL.) The current version supports overlays
-	and is able to compile every DTS (Device Tree Source) used by the FreeBSD arm
-	releases.  The ports GPL version was updated to the latest
-	release (1.4.4).  The in-tree GPL version is still present but
-	the goal is to remove it before FreeBSD 12.0.</p>
-    <hr /><h2><a name="Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker" href="#Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker" id="Using-LLVM's-LLD-Linker-as-FreeBSD's-System-Linker">Using LLVM's LLD Linker as FreeBSD's System Linker</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/LLD" title="https://wiki.FreeBSD.org/LLD">FreeBSD lld Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/LLD" title="FreeBSD lld Wiki Page">https://wiki.FreeBSD.org/LLD</a></td></tr><tr><td><a href="http://llvm.org/pr23214" title="http://llvm.org/pr23214">FreeBSD/LLD Tracking PR (LLVM Bugzilla)</a></td><td>
-	    URL: <a href="http://llvm.org/pr23214" title="FreeBSD/LLD Tracking PR (LLVM Bugzilla)">http://llvm.org/pr23214</a></td></tr><tr><td><a href="https://bugs.FreeBSD.org/214864" title="https://bugs.FreeBSD.org/214864">Exp-Run Request Using lld as /usr/bin/ld</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/214864" title="Exp-Run Request Using lld as /usr/bin/ld">https://bugs.FreeBSD.org/214864</a></td></tr></table><p>
-	Contact:
-	  Rafael
-	  Esp�ndola
-	 &lt;<a href="mailto:rafael.espindola@gmail.com">rafael.espindola@gmail.com</a>&gt;
-	<br />
-	Contact:
-	  Ed
-	  Maste
-	 &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>LLD is the linker in the LLVM family of projects.  It is a
-	high-performance linker that supports the ELF, COFF and
-	Mach-O object formats.  It is broadly compatible with the
-	common linkers used for each file format.  For ELF this is
-	the GNU Binary File Descriptor (BFD) <tt>ld</tt> and GNU
-	<tt>gold</tt>.  However, LLD's authors are not constrained
-	by strict compatibility where it would hamper performance or
-	desired functionality.</p>
-
-      <p>LLD is now used as the default system linker for
-	FreeBSD/arm64 and can link a working kernel, kernel modules, and
-	userland for FreeBSD/amd64.  LLD can also link a working
-	kernel and modules (but not userland) for FreeBSD/arm and
-	FreeBSD/i386.</p>
-
-      <p>Work is ongoing to address ports that do not build with LLD
-	as the system linker (either by fixing the port, or
-	configuring the port to be linked by GNU <tt>ld</tt>).</p>
-
-      <p>For FreeBSD�12.0 we expect to use LLD as the system linker for
-	the same set of architectures that use Clang by default:
-	32- and 64-bit arm and x86.</p>
-    <p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Fix <tt>libtool</tt> to detect LLD and pass the same
-	command line arguments as for GNU <tt>ld</tt> and
-	<tt>gold</tt>.</li><li>Investigate the remaining amd64 and arm64 port
-	build failures.</li><li>Investigate and improve LLD on i386 and arm, before
-	the creation of the stable/12 branch.</li><li>Investigate and improve LLD on all other
-	architectures.</li><li>Extensive testing.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="A-New-USES-Macro-for-Porting-Cargo-Based-Rust-Applications" href="#A-New-USES-Macro-for-Porting-Cargo-Based-Rust-Applications" id="A-New-USES-Macro-for-Porting-Cargo-Based-Rust-Applications">A New USES Macro for Porting Cargo-Based Rust Applications</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.rust-lang.org/" title="https://www.rust-lang.org/">Rust Homepage</a></td><td>
-	    URL: <a href="https://www.rust-lang.org/" title="Rust Homepage">https://www.rust-lang.org/</a></td></tr><tr><td><a href="https://crates.io/" title="https://crates.io/">Cargo Homepage</a></td><td>
-	    URL: <a href="https://crates.io/" title="Cargo Homepage">https://crates.io/</a></td></tr><tr><td><a href="https://github.com/jwilm/alacritty" title="https://github.com/jwilm/alacritty">Alacritty Homepage</a></td><td>
-	    URL: <a href="https://github.com/jwilm/alacritty" title="Alacritty Homepage">https://github.com/jwilm/alacritty</a></td></tr><tr><td><a href="https://the.exa.website/" title="https://the.exa.website/">Exa Homepage</a></td><td>
-	    URL: <a href="https://the.exa.website/" title="Exa Homepage">https://the.exa.website/</a></td></tr><tr><td><a href="https://github.com/BurntSushi/ripgrep" title="https://github.com/BurntSushi/ripgrep">Ripgrep Homepage</a></td><td>
-	    URL: <a href="https://github.com/BurntSushi/ripgrep" title="Ripgrep Homepage">https://github.com/BurntSushi/ripgrep</a></td></tr><tr><td><a href="https://asciinema.org/a/SM2sOLi6iBUOmGWrxn5W1QI8U" title="https://asciinema.org/a/SM2sOLi6iBUOmGWrxn5W1QI8U">Short Screencast About How to Use the USES=cargo Macro</a></td><td>
-	    URL: <a href="https://asciinema.org/a/SM2sOLi6iBUOmGWrxn5W1QI8U" title="Short Screencast About How to Use the USES=cargo Macro">https://asciinema.org/a/SM2sOLi6iBUOmGWrxn5W1QI8U</a></td></tr></table><p>
-	Contact:
-	  Tobias
-	  Kortkamp
-	 &lt;<a href="mailto:tobik@FreeBSD.org">tobik@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support in the Ports Collection for applications written in
-	the Rust programming language that use Rust's package
-	manager Cargo was added, via a new <tt>USES=cargo</tt>
-	setting.  The work is based on the <tt>cargo</tt> module
-	from the OpenBSD ports tree.</p>
-
-      <p>This should significantly ease the porting of Rust
-	applications, as previously porters had to create their own
-	tarball of the application's dependencies or find other
-	manual ways of bringing them in.</p>
-
-      <p>Several new ports were added that use it, for example:</p>
-
-      <ul>
-	<li>Alacritty, a GPU-accelerated terminal emulator</li>
-
-	<li>Exa, a modern replacement for <tt>ls</tt></li>
-
-	<li>Ripgrep, a line-oriented search tool that combines the
-	  usability of The Silver Searcher with the raw speed of GNU
-	  <tt>grep</tt></li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Add documentation for the new feature.</li></ol><hr /><h2><a name="GCC-(GNU-Compiler-Collection)" href="#GCC-(GNU-Compiler-Collection)" id="GCC-(GNU-Compiler-Collection)">GCC (GNU Compiler Collection)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gcc.gnu.org" title="https://gcc.gnu.org">GCC Homepage</a></td><td>
-	    URL: <a href="https://gcc.gnu.org" title="GCC Homepage">https://gcc.gnu.org</a></td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219275" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219275">Issue Tracker Entry for the Update to GCC 6</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219275" title="Issue Tracker Entry for the Update to GCC 6">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219275</a></td></tr><tr><td><a href="https://gcc.gnu.org/gcc-5/changes.html" title="https://gcc.gnu.org/gcc-5/changes.html">GCC 5 Changelog</a></td><td>
-	    URL: <a href="https://gcc.gnu.org/gcc-5/changes.html" title="GCC 5 Changelog">https://gcc.gnu.org/gcc-5/changes.html</a></td></tr><tr><td><a href="https://gcc.gnu.org/gcc-5/porting_to.html" title="https://gcc.gnu.org/gcc-5/porting_to.html">GCC 5 Porting Issues</a></td><td>
-	    URL: <a href="https://gcc.gnu.org/gcc-5/porting_to.html" title="GCC 5 Porting Issues">https://gcc.gnu.org/gcc-5/porting_to.html</a></td></tr></table><p>
-	Contact:
-	  Gerald
-	  Pfeifer
-	 &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Andreas
-	  Tobler
-	 &lt;<a href="mailto:andreast@FreeBSD.org">andreast@FreeBSD.org</a>&gt;
-	</p>
-      <p>The default version of GCC in the Ports Collection (the one
-	requested by <tt>USE_GCC=yes</tt> and various
-	<tt>USES=compiler</tt> invocations) has been updated from
-	GCC 4.9.4 to GCC 5.4.</p>
-
-      <p>This new major version brings many new capabilities and
-	improvements, as well as some changes that may require
-	adjustments.  The latter category includes many new compiler
-	warnings, significant
-	improvements to inter-procedural optimizations, and link-time
-	optimization.</p>
-
-      <p>The default mode for C is now <tt>-std=gnu11</tt> instead of
-	<tt>-std=gnu89</tt>.  The C++ front end has full C++14
-	language support, including C++14 variable templates, C++14
-	aggregates with non-static data member initializers, C++14
-	extended <tt>constexpr</tt>, and more.  The Standard C++
-	Library (libstdc++) has full C++11 support and experimental
-	full C++14 support.  It uses a new ABI by default.</p>
-
-      <p>The <tt>lang/gcc</tt> port now is a meta-port that pulls in the
-	respective <tt>lang/gccX</tt> port (based on the setting of
-	<tt>$GCC_DEFAULT</tt>) and defines <tt>gcc</tt>, <tt>g++</tt>,
-	and <tt>gfortran</tt> as symlinks to the respective versioned
-	binaries.</p>
-
-      <p>This is the end of a long journey establishing this infrastructure,
-	which is now similar that used by the python ports, for example.
-	Having the new infrastructure makes upgrading the default, as
-	well as locally adjusting the default version, a lot
-	easier.</p>
-
-      <p><tt>gcc8-devel</tt> has been added, and armv6hf support removed,
-	and we made adjustments for newer versions of FreeBSD.  Also of note
-	are various cleanups and changes to improve the robustness of our
-	packages and the addition of support for aarch64 to many
-	ports.</p>
-
-      <p>Thanks to dim@, jbeich@, tijl@, mat@, miwi@, linimon@ for
-	assisting with this work.</p>
-    <h3>Open tasks:</h3><ol><li>The update of the default version of GCC from GCC 5.4 to
-	GCC 6.4 is stalled, unfortunately.  The work on the GCC and
-	insfrastructure sides is complete, but unfortunately there are
-	a number of broken ports that need to be adjusted/fixed.  Any
-	help is very appreciated; see <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219275" shape="rect">PR
-	  219275</a> for details.</li></ol><hr /><h2><a name="GNOME-on-FreeBSD" href="#GNOME-on-FreeBSD" id="GNOME-on-FreeBSD">GNOME on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome" title="http://www.FreeBSD.org/gnome">FreeBSD GNOME Website</a></td><td>
-	    URL: <a href="http://www.FreeBSD.org/gnome" title="FreeBSD GNOME Website">http://www.FreeBSD.org/gnome</a></td></tr><tr><td><a href="https://github.com/FreeBSD/FreeBSD-ports-gnome" title="https://github.com/FreeBSD/FreeBSD-ports-gnome">Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/FreeBSD-ports-gnome" title="Development Repository">https://github.com/FreeBSD/FreeBSD-ports-gnome</a></td></tr><tr><td><a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD">Upstream Build Bot</a></td><td>
-	    URL: <a href="https://wiki.gnome.org/Projects/Jhbuild/FreeBSD" title="Upstream Build Bot">https://wiki.gnome.org/Projects/Jhbuild/FreeBSD</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html">USE_GNOME Porter's Handbook Chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html" title="USE_GNOME Porter's Handbook Chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html</a></td></tr></table><p>
-	Contact: FreeBSD GNOME Team &lt;<a href="mailto:FreeBSD-gnome@FreeBSD.org">FreeBSD-gnome@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD GNOME Team maintains the GNOME, MATE, and CINNAMON
-	desktop environments and graphical user interfaces for FreeBSD.
-	GNOME 3 is part of the GNU Project.  MATE is a fork of the
-	GNOME 2 desktop.  CINNAMON is a desktop environment using
-	GNOME 3 technologies but with a GNOME 2 look and feel.</p>
-
-      <p>After a period of not much activity, this quarter we
-	started a little experiment in how we merge ports from the
-	development repo to the FreeBSD Ports Collection.  Instead of
-	merging everything in one big commit, we have been updating
-	the GNOME ports one at a time or in small groups.  For
-	example, the GTK+ stack and the Evolution Suite were updated
-	as groups, and all the <tt>gnome-games</tt> components were
-	done in one commit.  It might be a bit more work preparing
-	and testing the updates, but on the plus side, it easy to
-	keep track of what is going on, and allows us to pay
-	attention to the details.  It should also make it easier to commit
-	smaller changes.</p>
-
-      <p>This quarter started with the update of GTK+ 3 to 3.22.15,
-	and the underlying libraries to their latest stable
-	versions.  After the GTK+ update, work started on getting
-	newer versions of other GNOME applications updated.</p>
-
-      <p>The <tt>webkit2-gtk3</tt> port was first updated to the
-	2.14 series and later to 2.16.3, which is the latest stable
-	version.  This step was needed because 2.16 couldn't be
-	built on FreeBSD�10.3 without some required framework
-	changes.</p>
-
-      <p><tt>harfbuzz-icu</tt> was split off from the main
-	<tt>harfbuzz</tt> port.  This drops the heavy <tt>icu</tt>
-	dependency from the main <tt>harfbuzz</tt> port.</p>
-
-      <p>A longstanding GLib/<tt>gio</tt> bug was fixed that had
-	previously caused crashes of <tt>gnome-shell</tt> and other
-	applications when <tt>share/applications</tt> was modified,
-	as happens on <tt>pkg install</tt> or
-	<tt>deinstall</tt>.</p>
-
-      <p>Many of these updates are based on work previously done in
-	the Gnome development branch by Ruslan Makhmatkhanov, Gustau
-	Perez and Koop Mast.</p>
-    <h3>Open tasks:</h3><ol><li>Porting of Mutter/Gnome-shell/GDM 3.24 is complete.
-	Unfortunately, GDM is blocking the update because of a
-	"handoff" bug to the session after login.</li><li>Fix the printer submenu in <tt>gnome-control-center</tt>.  As a
-	workaround, <tt>system-config-printer</tt> can be used to
-	configure printers.</li><li>MATE 1.18 is being QA tested and should arrive in early
-	July.</li></ol><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://FreeBSD.kde.org/" title="https://FreeBSD.kde.org/">KDE on FreeBSD Website</a></td><td>
-	    URL: <a href="https://FreeBSD.kde.org/" title="KDE on FreeBSD Website">https://FreeBSD.kde.org/</a></td></tr><tr><td><a href="https://FreeBSD.kde.org/area51.php" title="https://FreeBSD.kde.org/area51.php">KDE Ports Staging Area</a></td><td>
-	    URL: <a href="https://FreeBSD.kde.org/area51.php" title="KDE Ports Staging Area">https://FreeBSD.kde.org/area51.php</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/KDE" title="https://wiki.FreeBSD.org/KDE">KDE on FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/KDE" title="KDE on FreeBSD Wiki">https://wiki.FreeBSD.org/KDE</a></td></tr><tr><td><a href="https://mail.kde.org/mailman/listinfo/kde-FreeBSD" title="https://mail.kde.org/mailman/listinfo/kde-FreeBSD">KDE/FreeBSD Mailing List</a></td><td>
-	    URL: <a href="https://mail.kde.org/mailman/listinfo/kde-FreeBSD" title="KDE/FreeBSD Mailing List">https://mail.kde.org/mailman/listinfo/kde-FreeBSD</a></td></tr><tr><td><a href="https://github.com/FreeBSD/FreeBSD-ports-kde" title="https://github.com/FreeBSD/FreeBSD-ports-kde">Development Repository</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD/FreeBSD-ports-kde" title="Development Repository">https://github.com/FreeBSD/FreeBSD-ports-kde</a></td></tr><tr><td><a href="https://build.kde.org" title="https://build.kde.org">KDE's Continous Integration Dashboard</a></td><td>
-	    URL: <a href="https://build.kde.org" title="KDE's Continous Integration Dashboard">https://build.kde.org</a></td></tr><tr><td><a href="https://euroquis.nl/bobulate/?p=1600" title="https://euroquis.nl/bobulate/?p=1600">Blog Post on Using the Ninja CMake Generator</a></td><td>
-	    URL: <a href="https://euroquis.nl/bobulate/?p=1600" title="Blog Post on Using the Ninja CMake Generator">https://euroquis.nl/bobulate/?p=1600</a></td></tr></table><p>
-	Contact: KDE on FreeBSD Team &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The KDE on FreeBSD team focuses on packaging KDE and Qt, and making sure
-	that their experience on FreeBSD is as good as
-	possible.</p>
-
-      <p>This quarter, in addition to the regular updates to the KDE,
-	Qt, and related ports, there have also been some changes behind
-	the scenes: our development repository has moved to GitHub,
-	and FreeBSD is now part of KDE's official continuous integration
-	(CI infrastructure).</p>
-
-      <p>After the X.Org and GNOME ports teams, the KDE on FreeBSD team
-	has moved its development repository to GitHub.  This should
-	make it easier for others to collaborate with us via pull
-	requests, and by basing all our changes on top of the official
-	ports tree we also hope this reduces the amount of conflicts
-	and churn we need to deal with when landing big updates across
-	the tree.  We would like to thank iXsystems for hosting and
-	supporting our area51 Subversion repository for many
-	years.</p>
-
-      <p>FreeBSD has finally joined KDE's CI (Continuous Integration)
-	system as a tier-1 platform.  KDE CI builds all the KDE
-	sources &#8212; 70 frameworks, the KDE Plasma Desktop and a
-	plethora of KDE Applications &#8212; continuously, straight
-	from KDE's git repositories.  There is strong commitment from
-	upstream and the downstream KDE-FreeBSD team to reduce the amount
-	of patching in the KDE ports to as little as possible.  The
-	first effects are being felt in expanding the set of unit tests to
-	include FreeBSD-specific situations, and in extending Qt to handle FreeBSD
-	filesystems better.  In addition to the KDE sysadmins, we
-	would also like to extend our thanks to Adriaan de Groot, who
-	is both a KDE committer and part of our KDE on FreeBSD team, for
-	spearheading these efforts.</p>
-
-      <p>The following big updates landed in the ports tree this
-	quarter:</p>
-
-      <ul>
-	<li>CMake was updated to 3.8.0 and 3.8.2</li>
-
-	<li>KDE Frameworks was updated to 5.33, 5.34 and 5.35</li>
-
-	<li>The Calligra office suite was updated to 3.0.1, the first
-	  release in the ports tree to be based on KDE Frameworks 5,
-	  and the latest stable release upstream</li>
-
-	<li>The Konversation IRC client was updated to 1.7.2, the
-	  latest upstream release and the first ports version based on
-	  KDE Frameworks 5</li>
-
-	<li>KchmViewer was updated to 7.7, which is based on KDE
-	  Frameworks 5</li>
-
-	<li>LabPlot was updated to 2.3.0 and 2.4.0, and is now based
-	  on KDE Frameworks 5</li>
-
-	<li>QtCreator was upated to 4.2.2 and subsequently to
-	  4.3.0</li>
-
-	<li><tt>py-sip</tt> was updated to 4.19.2, PyQt4 to 4.12 and PyQt5 to
-	  5.7.1</li>
-
-	<li>Several fixes for ARMv6 landed in the Qt4 and Qt5
-	  ports &#8212; thanks to Mika�l Urankar</li>
-      </ul>
-
-      <p>After several review rounds and exp-runs, Tobias Berner
-	(tcberner@) finally made the Ninja generator the default for
-	CMake-based ports, so that <tt>devel/ninja</tt> is used
-	instead of (<tt>g</tt>)<tt>make</tt> in most cases.  This
-	should make most builds faster, even if only by a small margin.
-	Adriaan de Groot also wrote a blog post about the change.</p>
-    <hr /><h2><a name="New-Port:-FRRouting" href="#New-Port:-FRRouting" id="New-Port:-FRRouting">New Port: FRRouting</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://frrouting.org/" title="https://frrouting.org/">FRRouting Home Page</a></td><td>
-	    URL: <a href="https://frrouting.org/" title="FRRouting Home Page">https://frrouting.org/</a></td></tr></table><p>
-	Contact:
-	  Olivier
-	  Cochard-Labb�
-	 &lt;<a href="mailto:olivier@cochard.me">olivier@cochard.me</a>&gt;
-	</p>
-      <p>FRRouting (FRR), a Quagga fork, is an IP routing protocol
-	suite for Linux and Unix platforms which includes protocol
-	daemons for BGP, IS-IS, OSPF and RIP (LPD and PIM support need to be
-	fixed on FreeBSD).  FRR is a Linux Foundation Collaborative
-	Project with contributors including 6WIND, Architecture
-	Technology Corporation, Big Switch Networks, Cumulus Networks,
-	LabN Consulting, NetDEF (OpenSourceRouting), Orange, Volta
-	Networks, and other companies.</p>
-      <p>This project was sponsored by Orange.</p><hr /><h2><a name="PHP-Ports:-Help-Improving-QA" href="#PHP-Ports:-Help-Improving-QA" id="PHP-Ports:-Help-Improving-QA">PHP Ports: Help Improving QA</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.patreon.com/TorstenZuehlsdorff" title="https://www.patreon.com/TorstenZuehlsdorff">My Patreon Page</a></td><td>
-	    URL: <a href="https://www.patreon.com/TorstenZuehlsdorff" title="My Patreon Page">https://www.patreon.com/TorstenZuehlsdorff</a></td></tr></table><p>
-	Contact:
-	  Torsten
-	  Z�hlsdorff
-	 &lt;<a href="mailto:tz@FreeBSD.org">tz@FreeBSD.org</a>&gt;
-	</p>
-      <p>As maintainer of the PHP ports, I first want to thank you all
-	for the great feedback and patches I receive, in many forms.
-	You keep my life interesting!</p>
-
-      <p>In the past few months I learned a lot about various
-	configurations, settings and bugs.  Also, sadly, there are
-	always PRs, patches and emails left unanswered, because of
-	missing time on my side.</p>
-
-      <p>I want to improve the situation by adding more automatic QA
-	testing, but I need help to do so.  Please send me your
-	non-standard PHP-configurations or describe your exotic
-	setups!  These can be as simple as changed default versions,
-	like LibreSSL instead of OpenSSL or the GCC version used for
-	compiling.  I, for example, always use another
-	PostgreSQL-version than the default (and always PHP 7.1).  Of
-	course, this also covers port options set in an non-default way or
-	setups that change variables to allow for multiple PHP
-	installations, etc..</p>
-
-      <p>I plan to test on all supported FreeBSD versions, so you only
-	need to mention if you are using an unsupported version.</p>
-
-      <p>Note: Since PHP 7.2 is coming (hopefully on schedule), I will
-	test PHP 7.2 from the onset with all the provided
-	configurations, too.</p>
-    <h3>Open tasks:</h3><ol><li>Document the various configurations to be tested.</li><li>Setup the automatic QA infrastructure.</li></ol><hr /><h2><a name="Rust" href="#Rust" id="Rust">Rust</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Rust" title="https://wiki.FreeBSD.org/Rust">Wiki Portal</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Rust" title="Wiki Portal">https://wiki.FreeBSD.org/Rust</a></td></tr><tr><td><a href="https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad" title="https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad">Guide to Bootstrap Rust on FreeBSD</a></td><td>
-	    URL: <a href="https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad" title="Guide to Bootstrap Rust on FreeBSD">https://gist.github.com/dumbbell/b587da50ef014078da9e732a4331ebad</a></td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143">Bug Report to Track Progress on Bootstrapping</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143" title="Bug Report to Track Progress on Bootstrapping">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216143</a></td></tr><tr><td><a href="https://internals.rust-lang.org/t/pre-rfc-target-extension-dealing-with-breaking-changes-at-os-level/5289" title="https://internals.rust-lang.org/t/pre-rfc-target-extension-dealing-with-breaking-changes-at-os-level/5289">Upstream Discussion of API/ABI-Breaking Changes</a></td><td>
-	    URL: <a href="https://internals.rust-lang.org/t/pre-rfc-target-extension-dealing-with-breaking-changes-at-os-level/5289" title="Upstream Discussion of API/ABI-Breaking Changes">https://internals.rust-lang.org/t/pre-rfc-target-extension-dealing-with-breaking-changes-at-os-level/5289</a></td></tr></table><p>
-	Contact: FreeBSD Rust team &lt;<a href="mailto:rust@FreeBSD.org">rust@FreeBSD.org</a>&gt;
-	</p>
-      <p>Rust was updated to 1.18.0 and Cargo to 0.19.0, the latest
-	versions at the time of this writing.</p>
-
-      <p><tt>lang/rust</tt> was enabled on FreeBSD/aarch64 and work has
-	continued on <tt>devel/cargo</tt> to achieve the same.  We are
-	also making slow progress to add support for even more
-	platforms.</p>
-
-      <p>Discussion has started upstream to support API/ABI-breaking
-	changes between major releases of operating systems.  For
-	instance, this is required to be able to target both FreeBSD 11.x
-	and 12.x, which have ABI changes involving important
-	structures.  Once support is added upstream, it will be
-	possible to target a specific ABI and do
-	cross-compilation.</p>
-
-      <p><tt>lang/rust-nightly</tt> was marked as broken for now.  We
-	need to revisit how the port is built so we can use the
-	<tt>x.py</tt> script as recommended by upstream.</p>
-
-      <p>Tobias Kortkamp (<tt>tobik@</tt>) created the
-	<tt>USES=cargo</tt> setting to make it easy to add Rust
-	applications to the Ports Collection.  This is further
-	detailed in a separate entry in this quarterly status
-	report.</p>
-
-      <p>The compiler, <tt>rustc</tt>, is crashing sometimes when
-	there is a compilation error.  Therefore, there is a bit of
-	work to do to improve its stability.</p>
-
-      <p>There is some code duplication between the
-	<tt>lang/rust*</tt> and <tt>devel/cargo</tt> Makefiles.  These
-	all deserve a bit of cleanup, and it might be useful to create
-	a <tt>USES=rust</tt> Makefile helper.</p>
-    <h3>Open tasks:</h3><ol><li>Bootstrap Rust on more platforms.</li><li>Investigate compiler crashes.</li><li>Investigate how to speed up <tt>lang/rust*</tt>
-	compilation times.</li></ol><hr /><h2><a name="sndio-Support-in-the-FreeBSD-Ports-Collection" href="#sndio-Support-in-the-FreeBSD-Ports-Collection" id="sndio-Support-in-the-FreeBSD-Ports-Collection">sndio Support in the FreeBSD Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.sndio.org" title="http://www.sndio.org">Sndio Homepage</a></td><td>
-	    URL: <a href="http://www.sndio.org" title="Sndio Homepage">http://www.sndio.org</a></td></tr><tr><td><a href="https://www.openbsd.org/papers/asiabsdcon2010_sndio.pdf" title="https://www.openbsd.org/papers/asiabsdcon2010_sndio.pdf">Sndio Paper</a></td><td>
-	    URL: <a href="https://www.openbsd.org/papers/asiabsdcon2010_sndio.pdf" title="Sndio Paper">https://www.openbsd.org/papers/asiabsdcon2010_sndio.pdf</a></td></tr><tr><td><a href="https://www.bsdfrog.org/pub/events/my_bsd_sucks_less_than_yours-AsiaBSDCon2017-paper.pdf" title="https://www.bsdfrog.org/pub/events/my_bsd_sucks_less_than_yours-AsiaBSDCon2017-paper.pdf">Comprehensive and Biased Comparison of OpenBSD and FreeBSD (Section 17)</a></td><td>
-	    URL: <a href="https://www.bsdfrog.org/pub/events/my_bsd_sucks_less_than_yours-AsiaBSDCon2017-paper.pdf" title="Comprehensive and Biased Comparison of OpenBSD and FreeBSD (Section 17)">https://www.bsdfrog.org/pub/events/my_bsd_sucks_less_than_yours-AsiaBSDCon2017-paper.pdf</a></td></tr></table><p>
-	Contact:
-	  Tobias
-	  Kortkamp
-	 &lt;<a href="mailto:tobik@FreeBSD.org">tobik@FreeBSD.org</a>&gt;
-	</p>
-      <p><tt>sndio</tt> is a small audio and MIDI framework that
-	is part of the OpenBSD project.  It provides a lightweight
-	audio and MIDI server, <tt>sndiod</tt>.  It currently supports
-	OpenBSD, FreeBSD, DragonFly BSD, and Linux.</p>
-
-      <p>The porting effort to FreeBSD and OSS started last year and
-	the <tt>sndio</tt> backend support in the FreeBSD Ports
-	Collection can now be considered good enough for daily
-	use.</p>
-
-      <p>Sndio offers network transparency through <tt>sndiod</tt>,
-	which provides an easy way to share your audio devices with
-	other machines/VMs/jails on your network.  However,
-	applications and libraries need to support playing and
-	recording through it.  To that end, I submitted several patches
-	to various ports over the course of the last year.</p>
-
-      <p>Here's a short selection of ports that now support <tt>sndio</tt> in
-	the FreeBSD Ports Collection:</p>
-
-      <ul>
-	<li>Most games, via <tt>audio/openal-soft</tt>,
-	  <tt>devel/sdl12</tt>, and <tt>devel/sdl20.</tt></li>
-
-	<li>GStreamer-based applications and WebKit-based browsers
-	  through two new GStreamer plugins
-	  (<tt>audio/gstreamer1-plugins-sndio</tt> and
-	  <tt>audio/gstreamer-plugins-sndio</tt>).</li>
-
-	<li>Firefox, Firefox ESR, Seamonkey, Chromium, and Iridium.
-	  The browsers currently lack or have a non-functional OSS
-	  backend.  Sndio support provides a BSD-native alternative to
-	  the ALSA and PulseAudio backends.</li>
-
-	<li>Video players like VLC, Totem, <tt>mpv</tt>,
-	  <tt>mplayer</tt>, etc..</li>
-
-	<li>Audio players like Clementine, <tt>cmus</tt>,
-	  <tt>mpd</tt>, <tt>mpg123</tt>, <tt>siren</tt>, <tt>xmp</tt>,
-	  etc..</li>
-
-	<li>SoX.</li>
-
-	<li>Shairport Sync, through a newly implemented backend.</li>
-
-	<li>JACK.</li>
-
-	<li>PulseAudio, through
-	  <tt>audio/pulseaudio-module-sndio</tt>.</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Commit a backport of Kodi's new <tt>sndio</tt> backend to
-	the Ports Collection.</li><li>If you maintain or use an audio-related port, consider
-	checking whether it includes an <tt>sndio</tt> backend, and adding
-	an <tt>SNDIO</tt> option.  Thanks to the OpenBSD developers,
-	several open-source projects already include one, so adding it
-	might be very easy to do.</li></ol><hr /><h2><a name="TensorFlow" href="#TensorFlow" id="TensorFlow">TensorFlow</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219609" title="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219609">TensorFlow PR</a></td><td>
-	    URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219609" title="TensorFlow PR">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219609</a></td></tr><tr><td><a href="https://reviews.FreeBSD.org/D11194" title="https://reviews.FreeBSD.org/D11194">Phabricator Review</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D11194" title="Phabricator Review">https://reviews.FreeBSD.org/D11194</a></td></tr><tr><td><a href="https://github.com/amutu/tf-FreeBSD-pkg" title="https://github.com/amutu/tf-FreeBSD-pkg">Prebuilt Packages</a></td><td>
-	    URL: <a href="https://github.com/amutu/tf-FreeBSD-pkg" title="Prebuilt Packages">https://github.com/amutu/tf-FreeBSD-pkg</a></td></tr><tr><td><a href="https://www.tensorflow.org" title="https://www.tensorflow.org">TensorFlow Upstream</a></td><td>
-	    URL: <a href="https://www.tensorflow.org" title="TensorFlow Upstream">https://www.tensorflow.org</a></td></tr></table><p>
-	Contact:
-	  Jov
-	 &lt;<a href="mailto:amutu@amutu.com">amutu@amutu.com</a>&gt;
-	</p>
-      <p>As described on its website, "TensorFlow&#8482; is an open
-	source software library for numerical computation using data
-	flow graphs.  Nodes in the graph represent mathematical
-	operations, while the graph edges represent the
-	multidimensional data arrays (tensors) communicated between
-	them.  The flexible architecture allows you to deploy
-	computation to one or more CPUs or GPUs in a desktop, server,
-	or mobile device with a single API.  TensorFlow was originally
-	developed by researchers and engineers working on the Google
-	Brain Team within Google's Machine Intelligence research
-	organization for the purposes of conducting machine learning
-	and deep neural networks research, but the system is general
-	enough to be applicable in a wide variety of other domains as
-	well."</p>
-
-      <p>TensorFlow now is the most popular platform/library for machine
-	learning and AI.  There are official binaries for Linux, Mac,
-	Windows, and Android, but no official support for FreeBSD.  For
-	the last several months, I have done some work to make
-	TensorFlow available on FreeBSD.  Some notable items include:</p>
-
-      <ul>
-	<li><tt>bazel</tt> was patched to not depend on <tt>/proc</tt> at
-	  build time. <tt>bazel</tt> is a build tool made by Google.
-	  It uses <tt>/proc</tt> to get path-to-self when building C++
-	  code, but mounting <tt>/proc</tt> is usually not allowed
-	  when building as an unprivileged user.</li>
-
-	<li>TensorFlow can now be built on FreeBSD�10.x by using
-	  <tt>clang38</tt> as the default <tt>bazel</tt> cross-build
-	  tool.</li>
-
-	<li>Patch the <tt>bazel</tt> workspace files to allow
-	  TensorFlow to be built using offline third-party
-	  dependencies.  This work is needed because the FreeBSD Ports
-	  framework does not allow network access except during the
-	  fetch stage.</li>
-
-	<li>Fix the build on FreeBSD i386.</li>
-
-	<li>Make TensorFlow build with either Python 2 or Python 3.</li>
-
-	<li>Update to the latest version, which is
-	  <tt>tensorflow</tt>-1.2.0.</li>
-      </ul>
-
-      <p>TensorFlow can now be run on FreeBSD in CPU-only mode. Some
-	functional tests have been performed on some combinations of
-	FreeBSD 10.3-RELEASE and 11.0-RELEASE, amd64 and i386, and
-	Python 2.7 and Python 3.6.</p>
-
-      <p>This port would not be possible without substantial
-	assistance from bapt@, lwhsu@, mat@, and koobs@ &#8212; thank
-	you for your advice, review, and help!  You are very nice
-	and I learned a lot about FreeBSD and the Ports framework from
-	you.</p>
-    <h3>Open tasks:</h3><ol><li>Review, test, comment, and most importantly, commit to the
-	Ports Collection.</li><li>Fix OpenCL (GPU acceleration) support on FreeBSD.</li><li>Port <tt>tensorflow-serving</tt>, which is a flexible,
-	high-performance serving system for machine learning models
-	produced by TensorFlow.</li><li>Set up a CI for TensorFlow on FreeBSD and give early notice
-	to upstream when they break TensorFlow on FreeBSD.</li></ol><hr /><h2><a name="Updating-Port-Metadata-for-non-x86-Architectures" href="#Updating-Port-Metadata-for-non-x86-Architectures" id="Updating-Port-Metadata-for-non-x86-Architectures">Updating Port Metadata for non-x86 Architectures</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://thunderx1.nyi.FreeBSD.org/jail.html?mastername=110arm64-default" title="http://thunderx1.nyi.FreeBSD.org/jail.html?mastername=110arm64-default">aarch64 Poudriere Machine</a></td><td>
-	    URL: <a href="http://thunderx1.nyi.FreeBSD.org/jail.html?mastername=110arm64-default" title="aarch64 Poudriere Machine">http://thunderx1.nyi.FreeBSD.org/jail.html?mastername=110arm64-default</a></td></tr><tr><td><a href="http://beefy8.nyi.FreeBSD.org/jail.html?mastername=head-armv6-default" title="http://beefy8.nyi.FreeBSD.org/jail.html?mastername=head-armv6-default">armv6 Poudriere Machine</a></td><td>
-	    URL: <a href="http://beefy8.nyi.FreeBSD.org/jail.html?mastername=head-armv6-default" title="armv6 Poudriere Machine">http://beefy8.nyi.FreeBSD.org/jail.html?mastername=head-armv6-default</a></td></tr></table><p>
-	Contact:
-	  Mark
-	  Linimon
-	 &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p>
-      <p>I have been analyzing the error logs from ports builds for
-	all non-x86 architectures, including both the logs published
-	on the package build cluster and also other builds of
-	powerpc64 and sparc64.</p>
-
-      <p>From this analysis, I have marked almost all the failing
-	ports as either <tt>BROKEN</tt> or
-	<tt>NOT_FOR</tt>/<tt>ONLY_FOR</tt>, as appropriate.</p>
-
-      <p>The intent of this work is not to make life harder for
-	anyone, but rather, in fact, the opposite.  With these
-	definitions in place, it is possible to scan the poudriere
-	bulk build output (the "Ignored ports" portion, in
-	particular) and see quickly what ports are failing to build
-	and why.  Previously, finding the exact reason why a build
-	failed needed some research (<tt>portsmon</tt> only analyzes
-	failure messages on amd64).  Additionally, it is extremely
-	difficult to work through several hundred logs that simply say
-	"failed to compile", "failed to link", and
-	so forth.</p>
-
-      <p>This is part of an effort to identify where we need further
-	work to bring sufficient Ports Collection support to, e.g.,
-	armv6 and aarch64 to bring them closer to true Tier-1
-	status.</p>
-
-      <p>To further facilitate locating patterns in the Poudriere
-	output, I have begun reworking some existing
-	<tt>BROKEN</tt>/<tt>NOT_FOR</tt>/<tt>ONLY_FOR</tt> messages so
-	that they will sort more easily.  This includes sorting the
-	order in which architectures appear in the lists.</p>
-
-      <p>Many people have been doing great work on fixing the
-	individual ports.  I hope that my work makes their jobs
-	somewhat easier.</p>
-    <hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Xfce" title="https://wiki.FreeBSD.org/Xfce">FreeBSD Xfce Project</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Xfce" title="FreeBSD Xfce Project">https://wiki.FreeBSD.org/Xfce</a></td></tr><tr><td><a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="https://www.assembla.com/spaces/xfce4/subversion/source">Ports Development Repository</a></td><td>
-	    URL: <a href="https://www.assembla.com/spaces/xfce4/subversion/source" title="Ports Development Repository">https://www.assembla.com/spaces/xfce4/subversion/source</a></td></tr></table><p>
-	Contact: FreeBSD Xfce Team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Olivier
-	  Duchateau
-	 &lt;<a href="mailto:duchateau.olivier@gmail.com">duchateau.olivier@gmail.com</a>&gt;
-	</p>
-      <p>Xfce is a free software desktop environment for Unix and
-	Unix-like platforms such as FreeBSD.  It aims to be fast and
-	lightweight, while still being visually appealing and easy to
-	use.</p>
-
-      <p>During this quarter, we have kept these applications up-to-date:</p>
-
-      <ul>
-	<li><tt>audio/xfce4-pulseaudio-plugin</tt> (0.2.5, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219357" shape="rect">PR219357</a>)</li>
-
-	<li><tt>deskutils/xfce4-tumbler</tt> (0.1.32, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219848" shape="rect">PR219848</a>)</li>
-
-	<li><tt>deskutils/xfce4-xkb-plugin</tt> (0.8.0, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=220071" shape="rect">PR220071</a>)</li>
-
-	<li><tt>sysutils/garcon</tt> (0.6.1, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219928" shape="rect">PR219928</a>,
-	  and <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219334" shape="rect">PR219334</a>
-	  for <tt>Mk/Uses/xfce.mk</tt>)</li>
-
-	<li><tt>textproc/xfce4-dict-plugin</tt> (0.8.0, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=220266" shape="rect">PR220266</a>)</li>
-
-	<li><tt>x11/xfce4-terminal</tt> (0.8.5.1, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219312" shape="rect">PR219312</a>)</li>
-
-	<li><tt>x11/xfce4-whiskermenu-plugin</tt> (1.7.2, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=219347" shape="rect">PR219347</a>)</li>
-
-	<li><tt>x11-wm/xfce4-desktop</tt> (4.12.4, <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=220290" shape="rect">PR220290</a>)</li>
-      </ul>
-
-      <p>We have created a new Subversion tag (<em>4.13</em>) in order
-	to follow the unstable releases.  The separate tag was
-	necessary in order to support changes in the <tt>USES=xfce</tt>
-	infrastucture, and due to some incompatible changes to the
-	<tt>xfconf</tt> API.  Ports following the unstable release are:</p>
-
-      <ul>
-	<li><tt>deskutils/xfce4-tumbler</tt> (0.1.92.1)</li>
-
-	<li><tt>multimedia/xfce4-parole</tt> (0.9.2)</li>
-
-	<li><tt>sysutils/xfce4-settings</tt> (4.13.1)</li>
-
-	<li><tt>x11/libexo</tt> (0.11.3)</li>
-
-	<li><tt>x11/libxfce4menu</tt> (4.13.2)</li>
-
-	<li><tt>x11/libxfce4util</tt> (4.13.1)</li>
-
-	<li><tt>x11/xfce4-conf</tt> (4.13.2)</li>
-
-	<li><tt>x11/xfce4-dashboard</tt> (0.7.2)</li>
-
-	<li><tt>x11/xfce4-screenshooter</tt> (1.9.1)</li>
-
-	<li><tt>x11/xfce4-whiskermenu-plugin</tt> (2.1.2)</li>
-
-	<li><tt>x11-wm/xfce4-desktop</tt> (4.13.1)</li>
-
-	<li><tt>x11-wm/xfce4-panel</tt> (4.13.0)</li>
-
-	<li><tt>x11-wm/xfce4-session</tt> (4.13.0)</li>
-
-	<li><tt>x11-wm/xfce4-wm</tt> (4.13.0)</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Make the transition to Gtk3 smoother for end users.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Absolute-FreeBSD,-3rd-Edition" href="#Absolute-FreeBSD,-3rd-Edition" id="Absolute-FreeBSD,-3rd-Edition">Absolute FreeBSD, 3rd Edition</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://blather.michaelwlucas.com/archives/2972" title="https://blather.michaelwlucas.com/archives/2972">Status as of 30 June</a></td><td>
-	    URL: <a href="https://blather.michaelwlucas.com/archives/2972" title="Status as of 30 June">https://blather.michaelwlucas.com/archives/2972</a></td></tr><tr><td><a href="https://www.michaelwlucas.com/os/af2e" title="https://www.michaelwlucas.com/os/af2e">Second Edition</a></td><td>
-	    URL: <a href="https://www.michaelwlucas.com/os/af2e" title="Second Edition">https://www.michaelwlucas.com/os/af2e</a></td></tr><tr><td><a href="https://twitter.com/search?q=%23af3e&amp;src=typd" title="https://twitter.com/search?q=%23af3e&amp;src=typd">Trivial Updates</a></td><td>
-	    URL: <a href="https://twitter.com/search?q=%23af3e&amp;src=typd" title="Trivial Updates">https://twitter.com/search?q=%23af3e&amp;src=typd</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	</p>
-      <p>I'm working on a third edition of <i>Absolute FreeBSD</i>. This
-	will be a nearly complete rewrite, thanks to the addition of
-	little details like ZFS, GPT, <tt>dma</tt>, GELI, new boot
-	procedures, disk labeling, <tt>pkg(8)</tt>, <tt>blacklistd</tt>,
-	jails, etc..</p>
-
-      <p>My current (delusional) plan is to have a first draft
-	finished by the end of October 2017, so we can have print
-	copies for BSDCan 2018.</p>
-    <h3>Open tasks:</h3><ol><li>Write the remaining 75% of the book.</li></ol><hr /><h2><a name="Doc-Version-Strings-Improved-by-Their-Absence" href="#Doc-Version-Strings-Improved-by-Their-Absence" id="Doc-Version-Strings-Improved-by-Their-Absence">Doc Version Strings Improved by Their Absence</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/">FreeBSD Documentation Project Primer</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="FreeBSD Documentation Project Primer">https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/doc/head/share/mk/doc.docbook.mk?r1=50233&amp;r2=50232&amp;pathrev=50233" title="https://svnweb.freebsd.org/doc/head/share/mk/doc.docbook.mk?r1=50233&amp;r2=50232&amp;pathrev=50233">Get Version Information from Subversion Metadata</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/doc/head/share/mk/doc.docbook.mk?r1=50233&amp;r2=50232&amp;pathrev=50233" title="Get Version Information from Subversion Metadata">https://svnweb.freebsd.org/doc/head/share/mk/doc.docbook.mk?r1=50233&amp;r2=50232&amp;pathrev=50233</a></td></tr></table><p>
-	Contact:
-          Warren
-          Block
-         &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>In retrospect, our <tt>$FreeBSD$</tt> strings in
-	source files are kind of weird, like a vestigial tail.  The
-	version control system stores all of that information in
-	metadata.  Yet here we are, not only allowing the version
-	control system to alter our source files on every commit, but
-	forcing it to do so.</p>
-
-      <p>The reason for doing so is that the previous version control
-	system did it.  Really.</p>
-
-      <p>Version control strings are a headache for translators using
-	the new PO toolchain.  It is an ever-changing string that offers
-	nothing to the translation, yet can cause conflicts with earlier
-	versions of itself.</p>
-
-      <p>We also had complaints about how the Handbook was always months
-	out of date.  It was not, of course... but looking at just the
-	version string in the main, rarely-changing book.xml file gave
-	that impression.  We fixed that problem last year, so the build
-	system checks all the source files for the latest commit, but it
-	seems easier to not have to fix the problem at all.</p>
-
-      <p>Of course, that was really only one aspect of an ongoing
-	problem.  Our documentation build system was checking the
-	version string in the source file, not the metadata.  In 1973,
-	metadata, like cars not composed chiefly of rust, had not yet
-	been invented.  I modified the build system to extract the
-	information from the metadata (and noted, with some surprise,
-	that this is a task at which Git is much better than
-	Subversion).</p>
-
-      <p>The next step was to remove the
-	<tt>$FreeBSD$</tt> strings from the source files
-	and remove the <tt>FreeBSD=%H</tt> property that forces
-	Subversion, against its better judgement, to substitute text in
-	the actual contents of the file.  The version information is not
-	lost.  It lives in the metadata, so retrieving it is as simple
-	as <tt>svn info</tt> &#8212; it does not need to be in the
-	source at all.  However, as with anything that touches code or
-	processes which have not been touched in living memory, there
-	was some debate over this.  At that point, I offered to remove
-	the version strings from the FreeBSD Documentation Project Primer
-	book as a test.</p>
-
-      <p>The change allowed the <tt>zh_TW</tt> translation team to turn
-	off the <tt>FreeBSD=%H</tt> property on their translation and
-	continue their work without fighting with the version strings.
-	Rendered versions of the book still display the name of the last
-	committer and the date and revision number of the last commit,
-	but all of that information comes from metadata.  As such, it is
-	also more likely to be correct.</p>
-
-      <p>Since the change, there have not been any complaints, at least
-	not to me.  In fairness, the removal of version strings from the
-	FDP Primer alone is a small change in a tiny corner of the
-	project.  Looking at it another way, it might be that some
-	things that seem to be necessary are more about the comfort of
-	familiarity than actual utility.</p>
-
-      <p>At present, this is strictly a change to the documentation
-	build toolchain and a single documentation book.  However, there
-	does not appear to be any reason why it could not be extended to the
-	rest of the documents.  It might even serve as tiny test of
-	whether the expansion of <tt>$FreeBSD$</tt> tags
-	is needed throughout the rest of the FreeBSD tree.</p>
-    <hr /><h2><a name="New-Xen-Handbook-Section" href="#New-Xen-Handbook-Section" id="New-Xen-Handbook-Section">New Xen Handbook Section</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-xen.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-xen.html">Handbook Section About FreeBSD as a Xen Host</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-xen.html" title="Handbook Section About FreeBSD as a Xen Host">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-xen.html</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D10774" title="https://reviews.freebsd.org/D10774">Original Phabricator Review</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D10774" title="Original Phabricator Review">https://reviews.freebsd.org/D10774</a></td></tr></table><p>
-	Contact:
-	  Benedict
-	  Reuschling
-	 &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD supports the Xen hypervisor, with DomU (guest) support since
-	FreeBSD�8.0 and Dom0 (host) available since FreeBSD�11.0.  The
-	FreeBSD Handbook was lacking instructions on how to run a Xen
-	host and VMs.  The steps were outlined in the FreeBSD wiki, but
-	needed some extra bits of text from the upstream Xen wiki in
-	order to form a complete guide.  The new handbook section
-	briefly explains what Xen is, how it differs from other
-	hypervisors, and what features are currently available in
-	FreeBSD.  It then goes on to describe how to set up the Dom0, as
-	well as detailing the guest VM support known as DomU.</p>
-
-      <p>Reviewers Nikolai Lifanov, Roger Pau Monn�, and Warren Block
-	provided valuable feedback on the initial version in
-	Phabricator.  Additional corrections were made by Bj�rn
-	Heidotting while translating the section into German.</p>
-    <h3>Open tasks:</h3><ol><li>More options for the Dom0 and DomU could be provided.</li><li>People should test these instructions on their hardware
-	and provide feedback.  This would also help us get better
-	testing of the Xen port for FreeBSD.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSD-Meetups-at-Rennes-(France)" href="#BSD-Meetups-at-Rennes-(France)" id="BSD-Meetups-at-Rennes-(France)">BSD Meetups at Rennes (France)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/239248155/" title="https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/239248155/">First Event</a></td><td>
-	    URL: <a href="https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/239248155/" title="First Event">https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/239248155/</a></td></tr><tr><td><a href="https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/240202297/" title="https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/240202297/">Second Event</a></td><td>
-	    URL: <a href="https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/240202297/" title="Second Event">https://www.meetup.com/fr-FR/Meetup-BSD-Rennes/events/240202297/</a></td></tr></table><p>
-	Contact:
-	  Mathieu
-	  Kerjouan
-	 &lt;<a href="mailto:contact@steepath.eu">contact@steepath.eu</a>&gt;
-	</p>
-      <p>Two meetups dedicated to BSD systems were held in Rennes,
-	France.  The first one was hosted in the OVH office in Rennes
-	and included presentations on multiple subjects: the
-	non-technical history of FreeNAS (presented by olivier@), how
-	OVH is using ZFS, an introduction to jails, and a use case for
-	BGP/bird on FreeBSD.</p>
-
-      <p>The second meetup, also hosted in the OVH office, presented these
-	subjects: how to create a FreeBSD port (presented by jadawin@),
-	how OVH is using Finite State Machines for managing their
-	storage system, network high-availability with FreeBSD, and a
-	jail tutorial by means of a demonstration running 200 OSPF
-	(using <tt>net/bird</tt>) routers using jails and vnets on a
-	small PC Engines APU2 system with only 4 CPU cores (1Ghz AMD)
-	and 4GB RAM).</p>
-    <p>This project was sponsored by OVH.</p><hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="HardenedBSD" href="#HardenedBSD" id="HardenedBSD">HardenedBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://hardenedbsd.org/" title="https://hardenedbsd.org/">HardenedBSD Homepage</a></td><td>
-	    URL: <a href="https://hardenedbsd.org/" title="HardenedBSD Homepage">https://hardenedbsd.org/</a></td></tr><tr><td><a href="http://clang.llvm.org/docs/SafeStack.html" title="http://clang.llvm.org/docs/SafeStack.html">SafeStack</a></td><td>
-	    URL: <a href="http://clang.llvm.org/docs/SafeStack.html" title="SafeStack">http://clang.llvm.org/docs/SafeStack.html</a></td></tr><tr><td><a href="http://t3a73imee26zfb3d.onion/" title="http://t3a73imee26zfb3d.onion/">HardenedBSD Tor Hidden Service</a></td><td>
-	    URL: <a href="http://t3a73imee26zfb3d.onion/" title="HardenedBSD Tor Hidden Service">http://t3a73imee26zfb3d.onion/</a></td></tr><tr><td><a href="https://github.com/HardenedBSD/hardenedBSD/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22" title="https://github.com/HardenedBSD/hardenedBSD/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22">Projects HardenedBSD Would Like Help With</a></td><td>
-	    URL: <a href="https://github.com/HardenedBSD/hardenedBSD/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22" title="Projects HardenedBSD Would Like Help With">https://github.com/HardenedBSD/hardenedBSD/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22</a></td></tr></table><p>
-	Contact:
-	  Shawn
-	  Webb
-	 &lt;<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>&gt;
-	<br />
-	Contact:
-	  Oliver
-	  Pinter
-	 &lt;<a href="mailto:oliver.pinter@hardenedbsd.org">oliver.pinter@hardenedbsd.org</a>&gt;
-	</p>
-      <p>HardenedBSD is a derivative of FreeBSD that gives special attention to
-	security-related enhancements and exploit-mitigation
-	technologies.  From an initial focus on Address Space Layout
-	Randomization (ASLR), it has now branched out to explore
-	additional exploit mitigation techniques.</p>
-
-      <p>It has been a long while since HardenedBSD's last entry
-	in a quarterly status report, back in 2015Q4.  The
-	intervening year saw HardenedBSD gain new developers
-	Bernard Spil and Franco Fichtner, import LibreSSL and
-	OpenNTPd into base as the default crypto library and NTP
-	client, respectively, and introduce the <tt>hbsd-update</tt>
-	binary update mechanism for the base system.  The
-	<tt>secadm</tt> application got a rewrite and Trusted Path
-	Execution (TPE).  PIE is now enabled for the base system for
-	arm64 and amd64 as well as the bulk of the ports tree, and the
-	ports tree also gained RELRO and BIND_NOW.  Integriforce
-	(similar to NetBSD's verified exec, <tt>veriexec</tt>) was
-	introduced for the base system, as well as SafeStack, a
-	technology for protection against stack-based buffer
-	overflows that's developed by the Clang/LLVM community.
-	SafeStack relies and builds on top of Address Space Layout
-	Randomization (ASLR), and is strengthened by the presence of
-	PaX NOEXEC.  Certain high-profile ports also have SafeStack
-	enabled.</p>
-
-      <p>Extremely generous hardware donations from G2, Inc. have
-	provided for dedicated package building and binary update
-	servers, as well as development and test servers.</p>
-
-      <p>In March of 2017, we added Control Flow Integrity (CFI) to
-	the base system.  CFI is an exploit mitigation technique that
-	helps prevent attackers from modifying the behavior of a
-	program and jumping to undefined or arbitrary memory
-	locations.  This type of technique is gaining adoption across
-	the industry &#8212; Microsoft has implemented a variant of
-	CFI, which they term Control Flow Guard, or CFG, and the PaX
-	team has spent the last few years perfecting their Reuse
-	Attack Protector, RAP.  Of these, RAP is the most complete and
-	effective implementation, followed by Clang's CFI.  RAP would
-	be a great addition to HardenedBSD; however, it requires a
-	GPLv3 toolchain and is patent-pending.</p>
-
-      <p>CFI can be implemented either on a per-DSO basis, or across
-	all DSOs in a process.  Currently only the former is
-	implemented, but we are working hard to enable cross-DSO CFI.
-	As is the case for SafeStack, cross-DSO CFI requires both ASLR
-	and PaX NOEXEC in order to be effective.  If an attacker
-	knows the memory layout of an application, the attacker might
-	be able to craft a data-only attack, modifying the CFI control
-	data.</p>
-
-      <p>The behavior of several system control (<tt>sysctl</tt>)
-	nodes has been tighened up, limiting write access and
-	introducing additional safety checks for write accesses.
-	Kernel module APIs received a similar treatment.
-	HardenedBSD's PaX SEGVGUARD implementation received a few
-	updates to make it more stable and performant.</p>
-
-      <p>As of March 2017, HardenedBSD is now accessible through a
-	Tor hidden service.  The main website, binary updates, and
-	package distribution are all available over the hidden
-	service.</p>
-
-      <p>We now maintain our own version of the <tt>drm-next</tt>
-	branch for updated graphics support.  Binary updates are also
-	provided for this branch.</p>
-
-      <p>HardenedBSD would like to thank all those who have generously
-	donated time, money, or other resources to the project.</p>
-    <p>This project was sponsored by SoldierX, and G2, Inc.</p><h3>Open tasks:</h3><ol><li>Port SafeStack to arm64.</li><li>Integrate Cross-DSO CFI.</li><li>Add documentation to the HardenedBSD Handbook.</li><li>Start porting grsecurity's RBAC.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2017-07-2017-09.html b/website/content/en/status/report-2017-07-2017-09.html
deleted file mode 100644
index 46205b9d94..0000000000
--- a/website/content/en/status/report-2017-07-2017-09.html
+++ /dev/null
@@ -1,1122 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This quarter's FreeBSD developments continue to provide
-      excitement and promise for further developments.  I myself
-      have a soft spot for manual pages, so it is especially good to
-      see that we have gained some documentation for writing them
-      (and I hope that this will translate to more and improved
-      manual pages in the future!).  The core@ entry is also of
-      particular note, with the introduction of the FCP process and
-      the recognition of the first non-committer FreeBSD Project Member
-      (and more).  Read on to find out more about these, as well as
-      improved support for the AMD Zen family of processors (e.g.,
-      Ryzen), and a whole lot more!</p><p>&#8212;Benjamin Kaduk</p><p><hr /></p><p>The deadline for submissions covering the period from October
-      to December 2017 is January 14, 2017.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-CI">FreeBSD CI</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Intel-10G-iflib-Driver-Update">Intel 10G iflib Driver Update</a></li><li><a href="#Intel-iWARP-Support">Intel iWARP Support</a></li><li><a href="#pNFS-Server-Plan-B">pNFS Server Plan B</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#AMD-Zen-(family-17h)-support">AMD Zen (family 17h) support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Updates-to-GDB">Updates to GDB</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSDDesktop">FreeBSDDesktop</a></li><li><a href="#OpenJFX-8">OpenJFX 8</a></li><li><a href="#Puppet">Puppet</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Absolute-FreeBSD,-3rd-Edition">Absolute FreeBSD, 3rd Edition</a></li><li><a href="#Manual-Pages">Manual Pages</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#The-nosh-Project">The nosh Project</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-	Page</a>.</p><br /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/releases/11.1R/announce.html" title="https://www.FreeBSD.org/releases/11.1R/announce.html">FreeBSD�11.1-RELEASE Announcement</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/11.1R/announce.html" title="FreeBSD�11.1-RELEASE Announcement">https://www.FreeBSD.org/releases/11.1R/announce.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/releases/10.4R/schedule.html" title="https://www.FreeBSD.org/releases/10.4R/schedule.html">FreeBSD�10.4-RELEASE Schedule</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/10.4R/schedule.html" title="FreeBSD�10.4-RELEASE Schedule">https://www.FreeBSD.org/releases/10.4R/schedule.html</a></td></tr><tr><td><a href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/" title="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/">FreeBSD Development Snapshots</a></td><td>
-	    URL: <a href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD Development Snapshots">https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD�Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for setting
-	and publishing release schedules for official project releases
-	of FreeBSD, announcing code freezes, and maintaining the
-	respective branches, among other things.</p>
-
-      <p>The FreeBSD Release Engineering Team continued finalizing the
-	11.1-RELEASE cycle, with the final release builds starting on
-	July 21 and the official release announcement email sent on
-	July 26.  Thank you to everyone who helped test 11.1-RELEASE,
-	ensuring its quality and stability.�[1]</p>
-
-      <p>FreeBSD�11.1-RELEASE is the second release from the
-	<tt>stable/11</tt> branch.</p>
-
-      <p>Additionally, the FreeBSD Release Engineering Team started the
-	10.4-RELEASE cycle, with the code slush starting on July 28.
-	With the final release build expected to start on September 29
-	and the official announcement overlapping the end of the
-	quarter, everything is on schedule as of this
-	writing.�[2]</p>
-
-      <p>FreeBSD�10.4-RELEASE will be the fifth release from the
-	<tt>stable/10</tt> branch, and is planned to be the final release
-	of the 10.x series.</p>
-    <p>This project was sponsored by The FreeBSD Foundation�[1].</p><p>This project was sponsored in part by The FreeBSD Foundation�[2].</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team Website</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team Website">https://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/freebsd_portmgr/" title="https://twitter.com/freebsd_portmgr/">FreeBSD portmgr on Twitter (@freebsd_portmgr)</a></td><td>
-	    URL: <a href="https://twitter.com/freebsd_portmgr/" title="FreeBSD portmgr on Twitter (@freebsd_portmgr)">https://twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">FreeBSD Ports Management Team on Facebook</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="FreeBSD Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team on Google+</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="FreeBSD Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Ports Collection now features over 31,600 ports.  There are currently
-	2671 problem reports, of which 718 are unassigned.  This quarter saw
-	almost 5,900 commits from 175 committers.  The number of open PRs grew
-	compared to last quarter, and outpaced the number of changes.</p>
-
-      <p>This quarter, we welcomed Zach Leslie (zleslie@), Luca Pizzamiglio
-	(pizzamig@), Craig Leres (leres@), Adriaan de Groot (adridg@), and Dave
-	Cottlehuber (dch@) as new committers.  The commit bits of the following
-	committers were taken in for safekeeping: alonso@ after 19 months of
-	inactivity, rpaulo@ per his request, and ache@ after he passed away.
-	Despite several tries and changing mentors, kami@ lacked interest in
-	completing his mentorship, so his commit bit was also taken in for
-	safekeeping.</p>
-
-      <p>On the infrastructure side, two <tt>USES</tt> values were
-	removed because they outlived their usefulness:</p>
-
-      <ul>
-	<li><tt>execinfo</tt>: <tt>libexecinfo</tt> is now available in the
-	  base system of all supported FreeBSD versions</li>
-
-	<li><tt>twisted</tt>: there is only one Twisted port left</li>
-      </ul>
-
-      <p>The default version of GCC was bumped from 5 to 6.  Firefox was updated
-	to version 56.0 and Chromium to version 61.0.3163.100.  The version of
-	<tt>pkg</tt> itself was updated to 1.10.1.</p>
-
-      <p>During this quarter, antoine@ performed 28 exp-runs to test version
-	updates of major ports, improving <tt>USE_GITHUB</tt> and
-	<tt>SHEBANG_FILES</tt>, and API changes to the base system.
-	This quarter, the foundation for ports "flavors" was
-	committed, though more development and testing will be
-	performed in the coming quarter before it goes live.</p>
-    <h3>Open tasks:</h3><ol><li>The PR load needs more attention, as the number of open PRs
-	has started to increase again.</li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The new "FreeBSD Community Process" was drafted during BSDCan
-	earlier this year.  The first such document, FCP 0, defines how
-	the whole process works.  After some time for discussion and
-	revision, FCP 0 was voted on and accepted by core, following the
-	procedure laid down within that document.  Currently the use of FCPs
-	is entirely optional; we shall see how the community begins to
-	adopt their usage and evolve the process based on experience.</p>
-
-      <p>A draft update to the Code of Conduct has been prepared by the
-	advisory committee.  Core is currently reviewing the text, and
-	will soon vote on accepting it.  Core is keen to avoid the trap of
-	"rules lawyering".  At the moment, the feeling is
-	that we need to add a preamble to the CoC to articulate the
-	goals of the project and to act as a general guide to the
-	exercise of the code.</p>
-
-      <p>This quarter has been quite a busy one concerning changes to
-	the roster of committers and project members.  We have elected our
-	first new Project Member: John Hixson, who will be familiar from
-	many conferences where he has given presentations and ably
-	represented iXsystems.  A second proposed Project Member was not
-	accepted by core, but only because core felt that Fedor Uporov
-	really deserved a commit bit instead.</p>
-
-      <p>In addition to Fedor Uporov, please also welcome (in no
-	particular order) Matt Joras, Marcin Wojtas, Chuck Tuffli, Ilya
-	Bakulin and Alex Richardson as brand-new committers.  We have also
-	awarded Steven Hurd and Eugene Grosbein src commit bits to go with
-	their existing ports bits.  Welcome back Gordon Tetlow as a src
-	committer, essential for his new role within secteam.  Eric Davis
-	and Rui Paulo have both decided to hang up their commit bits: we
-	wish them well in their future endeavours.  Finally, we must
-	report the sad death of Andrey Chernov, who will be sorely missed
-	by his colleagues and collaborators.</p>
-
-      <p>Andrey's death has highlighted another question which is only
-	going to become more complex over time.  Keeping track of
-	copyrights is already hard enough within a mature source tree with
-	many contributors, such as the FreeBSD sources.  Now we need to
-	consider trying to keep track of the heirs and beneficiaries of
-	contributors who have sadly passed away.  Core will consult with
-	the Foundation legal team to discuss possible approaches to
-	alleviate this.</p>
-
-      <p>There have been complaints that the workings of Core are being
-	kept overly confidential, and that consequently the majority of
-	the project has too little idea of what is going on.  This is
-	certainly not intentional by Core, and we are keen to open up
-	Core's business to more general community scrutiny as far as seems
-	reasonable.</p>
-
-      <p>Core dealt with a number of licensing questions:</p>
-
-      <ul>
-	<li>When upstreaming patches and other original works to
-	  VirtualBox or other Oracle properties, pragmatically it works
-	  best to provide them under the terms of the MIT license (one
-	  of two opensource licenses accepted by Oracle).  Of course,
-	  this only applies to work upstreamed by or with the permission
-	  of the original author.</li>
-
-	<li>The Viking software license is sufficiently BSD-like that
-	  magic constants from their drivers can be used in FreeBSD
-	  code.</li>
-
-	<li>There is no separate register of deviations from the allowed
-	  BSD-like licenses in the source tree: any code in the tree
-	  under other than BSD-like license terms can be assumed to have
-	  been approved by core.</li>
-
-	<li>At the moment the FreeBSD copyright requirement to include
-	  the copyright notice in redistributions in binary form is
-	  satisfied by making the FreeBSD sources, with all of the
-	  detailed copyright information included in the different source
-	  code files, available alongside pre-compiled system images.
-	  However, this does not necessarily meet the needs of downstream
-	  projects based on FreeBSD, and given the new "packaged base",
-	  adding per-package licensing metadata in a way similar to how
-	  the Ports Collection works is under consideration as an alternative
-	  mechanism.</li>
-      </ul>
-
-      <p>Concerns were raised regarding the pending HardenedBSD entry in the
-	previous quarterly report prior to publication.  The FreeBSD
-	project welcomes reports from separate (but derived) projects in
-	quarterly reports and has included similar reports in the past
-	from other projects (such as TrueOS and pfSense).  The HardenedBSD
-	report was edited for length and to concentrate on activities
-	during the quarter in question.</p>
-
-      <p>Amazon is proposing to set up mirrors of the <tt>freebsd-update</tt> and
-	<tt>pkg</tt> servers within AWS in order to provide faster
-	access for EC2 users.  These mirrors will be publicly
-	accessible, but the expectation is that use will primarily be
-	from within EC2.  FreeBSD AMIs will have a preset configuration
-	that references the Amazon servers.</p>
-
-      <p>The old, long-deprecated, and insecure "r-commands"
-        (<tt>rsh</tt>, <tt>rlogin</tt>, <tt>rcp</tt>) are being removed
-	from the base system for
-	12.0-RELEASE.  Notice of this was added to the man pages and
-	release notes in time for 11.1-RELEASE and 10.4-RELEASE.  Anyone
-	requiring these commands for backwards compatibility can use the
-	new <tt>net/bsdrcmds</tt> port.</p>
-
-      <p>Work to replace Heimdal Kerberos in base with the more widely
-	compatible MIT Kerberos has begun in a new
-	<tt>projects/krb5</tt> branch.  This should not fall afoul of
-	any US cryptography export regulations: the project is
-	required to notify the US government that cryptographic
-	software can be downloaded from FreeBSD servers, and this already
-	covers MIT Kerberos, already available within ports.</p>
-
-      <p>A number of Bay Area FreeBSD User Group-related domain names
-	are being given up by their original owner.  The current BAFUG
-	organisers have been made aware.</p>
-
-      <p>Core has voted on a change to the Doceng voting rules to
-	provide for a "did not vote" status during doceng
-	voting similar to how portmgr and core voting operates.  The
-	current requirement for all five members of doceng to register
-	a vote on issues was proving to be a significant
-	bottleneck.</p>
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSDFoundation.org/" title="https://www.FreeBSDFoundation.org/">FreeBSD Foundation Website</a></td><td>
-	    URL: <a href="https://www.FreeBSDFoundation.org/" title="FreeBSD Foundation Website">https://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf" title="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf">FreeBSD Foundation Quarterly Newsletter</a></td><td>
-	    URL: <a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf" title="FreeBSD Foundation Quarterly Newsletter">https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf</a></td></tr></table><p>
-	Contact:
-	    Deb
-	    Goodkin
-	   &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-	<p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	  organization dedicated to supporting and promoting the
-	  FreeBSD Project and community worldwide.  Funding comes from
-	  individual and corporate donations and is used to fund and
-	  manage software development projects, conferences and
-	  developer summits, and provide travel grants to FreeBSD
-	  contributors.  The Foundation purchases and supports hardware
-	  to improve and maintain FreeBSD infrastructure and provides
-	  full-time Release Engineering support; publishes marketing
-	  material to promote, educate, and advocate for the FreeBSD
-	  Project; facilitates collaboration between commercial
-	  vendors and FreeBSD developers; and finally, represents the
-	  FreeBSD Project in executing contracts, license agreements,
-	  and other legal arrangements that require a recognized legal
-	  entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD last
-	quarter:</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>Our work is 100% funded by your donations.  This year we have
-	raised over $860,000 from over 500 donors.  Our 2017 fundraising
-	goal is $1,250,00 and we are continuing to work hard to meet
-	and exceed this goal!  Please consider making a donation to
-	help us continue and increase our support for FreeBSD: <a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">https://www.FreeBSDfoundation.org/donate/</a>.</p>
-
-      <p>We also have a new Partnership Program, to provide more benefits
-	for our larger commercial donors.  Find out more information at
-	<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>
-	and share with your companies!</p>
-
-      <p>OS Improvements</p>
-
-      <p>The Foundation improves the FreeBSD 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
-	like the arm64 port, <tt>blacklistd</tt> access control
-	daemon, and the integration of VIMAGE support, to make sure
-	that FreeBSD remains a viable solution for research,
-	education, computing, products and more.</p>
-
-      <p>We kicked off or continued the following projects last
-	quarter:</p>
-
-      <ul>
-	<li>OpenZFS RAID-Z Expansion project</li>
-
-	<li>Broadcom Wi-Fi infrastructural improvements
-	  (<tt>bhnd(4)</tt> driver)</li>
-
-	<li>Headless mode out-of-the-box for the Beaglebone Black</li>
-
-	<li>Extending <tt>bhyve</tt>/ARMv7 features</li>
-
-	<li>Porting <tt>bhyve</tt>/ARM to an ARMv8 platform</li>
-      </ul>
-
-      <p>Having software developers on staff has allowed us to jump in
-	and work directly on projects to improve FreeBSD like:</p>
-
-      <ul>
-	<li>ZFS improvements</li>
-
-	<li>New Intel server support</li>
-
-	<li><tt>kqueue(2)</tt> updates</li>
-
-	<li>64-bit inode support</li>
-
-	<li>Stack guard</li>
-
-	<li>Kernel Undefined Behavior Sanitizer</li>
-
-	<li>Toolchain projects</li>
-
-	<li><tt>i915</tt> driver investigation</li>
-
-	<li>NVDIMM support in <tt>acpiconf(8)</tt></li>
-
-	<li>Continuous integration dashboard (web page and physical
-	  hardware)</li>
-
-	<li>FAT filesystem support in makefs(8)</li>
-      </ul>
-
-      <p>Staff and board members continued hosting bi-weekly
-	conference calls to facilitate efforts for individuals to
-	collaborate on different technologies.</p>
-
-      <p>Release Engineering</p>
-
-      <p>The Foundation provides a full-time staff member to lead the
-	release engineering efforts.  This has provided timely and
-	reliable releases over the last few years.</p>
-
-      <p>Last quarter, our full-time staff member worked with the
-	FreeBSD Release Engineering and Security Teams to finalize
-	11.1-RELEASE.  He also supported the 10.4 release effort, and
-	has continued producing 10-STABLE, 11-STABLE, and 12-CURRENT
-	development snapshot builds throughout the quarter.  At the
-	vBSDCon Developer Summit, he gave a presentation on the state
-	of the release engineering team.</p>
-
-      <p>You can find out more about the support we provided to the
-	Release Engineering Team by reading their status update in
-	this report.</p>
-
-      <p>Supporting FreeBSD Infrastructure</p>
-
-      <p>The Foundation provides hardware and support to improve the
-	FreeBSD infrastructure.  Last quarter, we continued supporting
-	FreeBSD hardware located around the world.</p>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating for
-	the Project.  This includes promoting work being done by
-	others with FreeBSD; producing advocacy literature to teach
-	people about FreeBSD and help make the path to starting using
-	FreeBSD or contributing to the Project easier; and attending
-	and getting other FreeBSD contributors to volunteer to run
-	FreeBSD events, staff FreeBSD tables, and give FreeBSD
-	presentations.</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events, and
-	summits around the globe.  These events can be BSD-related,
-	open source, or technology events geared towards
-	underrepresented groups.  We support the FreeBSD-focused events
-	to help provide a venue for sharing knowledge, to work
-	together on projects, and to facilitate collaboration
-	between developers and commercial users.  This all helps
-	provide a healthy ecosystem.  We support the non-FreeBSD events
-	to promote and raise awareness of FreeBSD, to increase the use
-	of FreeBSD in different applications, and to recruit more
-	contributors to the Project.</p>
-
-      <p>Here is a list highlighting some of the advocacy and
-	education work we did last quarter:</p>
-
-      <ul>
-	<li>Organized and ran the Essen FreeBSD Hackathon in Essen
-	  Germany</li>
-
-	<li>Sponsored and participated in the FreeBSD Developer Summit
-	  BSDCam, in Cambridge, England</li>
-
-	<li>Represented FreeBSD at the ARM Partner Meeting</li>
-
-	<li>Presented and taught about FreeBSD at SdNOG 4 in Khartoum,
-	  Sudan</li>
-
-	<li>Sponsored and gave presentations and tutorials at
-	  EuroBSDCon in Paris, France</li>
-
-	<li>Organized and ran the Paris FreeBSD Developer Summit</li>
-
-	<li>Organized and ran the FreeBSD Developer Summit at vBSDCon</li>
-
-	<li>Sponsored and attended vBSDCon</li>
-
-	<li>Proved travel grants to FreeBSD contributors to attend the
-	  above events.</li>
-
-	<li>Sponsored the 2017 USENIX Security Symposium in Vancouver
-	  BC as an Industry Partner</li>
-
-	<li>Provided FreeBSD advocacy material</li>
-
-	<li>Sponsored the 2017 USENIX Annual Technical Conference in
-	  Santa Clara, CA as an Industry Partner</li>
-      </ul>
-
-      <p>We continued producing FreeBSD advocacy material to help
-	people promote FreeBSD around the world.</p>
-
-      <p>We help educate the world about FreeBSD by publishing the
-	professionally produced FreeBSD Journal.  Last quarter we
-	published the July/August issue that you can find at <a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>.</p>
-
-      <p>You can find out more about events we attended and upcoming
-	events at <a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">https://www.FreeBSDfoundation.org/news-and-events/</a>.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them.  We also provide legal support
-	for the core team to investigate questions that arise.</p>
-
-      <p>Go to <a href="https://www.FreeBSDfoundation.org/" shape="rect">http://www.FreeBSDfoundation.org</a>
-	to find out how we support FreeBSD and how we can help you!</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="FreeBSD-CI" href="#FreeBSD-CI" id="FreeBSD-CI">FreeBSD CI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="freebsd-ci Repository">https://github.com/freebsd/freebsd-ci</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="http://ci.FreeBSD.org" title="http://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="http://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">http://ci.FreeBSD.org</a></td></tr></table><p>
-	Contact: Jenkins Admins &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD CI team runs various continuous integration
-	solutions for FreeBSD, regularly checking that the current state
-	of the Subversion repository can successfully build, and
-	performing various tests and analysis upon the build
-	results.</p>
-
-      <p>We have introduced a DTrace test pipeline, with the results
-	and artifacts available at:</p>
-
-      <ul>
-	<li><a href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-dtrace_test/" shape="rect">https://ci.FreeBSD.org/job/FreeBSD-head-amd64-dtrace_test/</a></li>
-
-	<li><a href="https://artifact.ci.FreeBSD.org/dtrace-test/" shape="rect">https://artifact.ci.FreeBSD.org/dtrace-test/</a></li>
-      </ul>
-
-      <p>We had team meetings at two developer summits during Q3:</p>
-
-      <ul>
-	<li><a href="https://wiki.FreeBSD.org/DevSummit/201708/Testing" shape="rect">BSDcam</a></li>
-	<li><a href="https://wiki.FreeBSD.org/DevSummit/201709" shape="rect">EuroBSDCon</a></li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Fix the failing test cases and builds.</li><li>Create builds for additional architectures.</li><li>Add more tests.</li><li>The additional TODO items listed at <a href="https://wiki.FreeBSD.org/Jenkins/TODO" shape="rect">https://wiki.FreeBSD.org/Jenkins/TODO</a>.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><h2><a name="Intel-10G-iflib-Driver-Update" href="#Intel-10G-iflib-Driver-Update" id="Intel-10G-iflib-Driver-Update">Intel 10G iflib Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D11727" title="https://reviews.FreeBSD.org/D11727">ixgbe iflib Conversion</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D11727" title="ixgbe iflib Conversion">https://reviews.FreeBSD.org/D11727</a></td></tr></table><p>
-	Contact:
-	  Chris
-	  Galazka
-	 &lt;<a href="mailto:krzysztof.galazka@intel.com">krzysztof.galazka@intel.com</a>&gt;
-	<br />
-	Contact:
-	  Piotr
-	  Pietruszewski
-	 &lt;<a href="mailto:piotr.pietruszewski@intel.com">piotr.pietruszewski@intel.com</a>&gt;
-	</p>
-      <p>The <tt>ix</tt> and <tt>ixv</tt> network interface drivers
-	support a variety of Intel network interfaces, with line
-	speeds at 10 Gbit/second.</p>
-
-      <p>This quarter, with the help of Matt Macy and Sean Bruno (among
-	others), we have submitted a review in Phabricator for the
-	conversion of the <tt>ixgbe</tt> driver to use the new (and evolving)
-	<tt>iflib</tt> framework.</p>
-
-      <p>Stay tuned for the conversion of the 40G driver
-	(<tt>ixl</tt>), as it is currently being ported to use
-	<tt>iflib</tt>.</p>
-    <h3>Open tasks:</h3><ol><li>Additional testing.</li></ol><hr /><h2><a name="Intel-iWARP-Support" href="#Intel-iWARP-Support" id="Intel-iWARP-Support">Intel iWARP Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D11378" title="https://reviews.FreeBSD.org/D11378">iWARP for ixl</a></td><td>
-	    URL: <a href="https://reviews.FreeBSD.org/D11378" title="iWARP for ixl">https://reviews.FreeBSD.org/D11378</a></td></tr></table><p>
-	Contact:
-	  Bartosz
-	  Sobczak
-	 &lt;<a href="mailto:bartosz.sobczak@intel.com">bartosz.sobczak@intel.com</a>&gt;
-	</p>
-      <p>iWARP is a protocol suite that enables efficient movement
-	of data across the network, building on Remote Direct Memory
-	Access, Direct Data Placement, and Marker PDU Aligned Framing.
-	It endeavors to avoid unnecessary (local) data copies and to
-	offload work from the main CPU to dedicated hardware.</p>
-
-      <p>An initial commit adding iWARP support for the Intel X722
-	family of network adapters is under review.  This is an
-	important step towards introducing full iWARP support on
-	systems equipped with Intel C620 Series Chipsets.  Currently,
-	with the <tt>iw_ixl</tt> driver, only the kVerbs API is
-	supported.</p>
-    <h3>Open tasks:</h3><ol><li>Additional testing.</li></ol><hr /><h2><a name="pNFS-Server-Plan-B" href="#pNFS-Server-Plan-B" id="pNFS-Server-Plan-B">pNFS Server Plan B</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt" title="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt">Instructions for Testing</a></td><td>
-	    URL: <a href="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt" title="Instructions for Testing">http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt</a></td></tr></table><p>
-	Contact:
-	  Rick
-	  Macklem
-	 &lt;<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>&gt;
-	</p>
-      <p>A pNFS server allows an NFS service to be spread over
-	multiple servers, separating the MetaData operations from the
-	Data operations (Read and Write).  This project will add the
-	ability to use FreeBSD systems to create a pNFS service
-	consisting of a single MetaData Server plus a set of Data
-	Servers.  The Data Servers can be mirrored, so that redundant
-	copies of the file data are maintained.</p>
-
-      <p>The support for non-mirrored Data Servers is now believed
-	to be complete.  Support for mirrored Data Servers using the
-	Flexible File Layout, which will soon be published as an RFC,
-	is implemented.  However, there is still significant work to
-	be done, since the current implementation of mirrored Data
-	Servers does not handle failed Data Servers or their
-	resilvering/recovery.  It is hoped that support for
-	failure/recovery of Data Servers will be implemented in the
-	next six months.</p>
-
-      <p>The patched FreeBSD sources may now be accessed for testing
-	via either Subversion or downloading a gzipped tarball.
-	They consist of a patched kernel and <tt>nfsd</tt> and can be
-	used on any FreeBSD 11 or later system.  The installation
-	procedure is covered in the linked document.</p>
-    <h3>Open tasks:</h3><ol><li>Testing by others will be needed, now that the
-	implementation is available.</li><li>Implementation and testing of mirror failure/recovery.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="AMD-Zen-(family-17h)-support" href="#AMD-Zen-(family-17h)-support" id="AMD-Zen-(family-17h)-support">AMD Zen (family 17h) support</a></h2><p>
-	Contact:
-	  Conrad
-	  Meyer
-	  cem@FreeBSD.org
-	 &lt;<a href="mailto:"></a>&gt;
-	</p>
-      <p>This quarter, a bit of work was done to enhance platform
-	support for AMD Zen (Ryzen, Threadripper, Epyc) processors:</p>
-
-      <ul>
-	<li>The CPU topology detection code was enhanced to properly
-	  detect Zen dies and CPU Complexes.  This gives the scheduler more
-	  locality information to use when making scheduling decisions.</li>
-
-	<li>The x86 topology analysis was enhanced to report dies and
-	  CPU Complexes, in addition to the existing reporting on packages,
-	  cores, and threads.  An example of the new output is
-	  <tt>FreeBSD/SMP: 1 package(s) x 2 groups x 2 cache groups
-	    x 4 core(s) x 2 hardware threads</tt>.</li>
-
-	<li>The amdsmn(4) driver for accessing SMN (System Management
-	  Network) registers was added.</li>
-
-	<li>CPU temperature monitoring support for Zen was added to
-	  amdtemp(4).</li>
-
-	<li>In cpufreq(4):
-	  <ul>
-	    <li>Added support for decoding Zen P-state information
-	      from Machine State Registers (which is usually not
-	      necessary, since it is largely redundant with ACPI
-	      P-state information, but is potentially useful)</li>
-
-	    <li>Work around the apparent Ryzen inability to achieve
-	      the P1 state by not busying cores waiting to
-	      transition to it</li>
-	  </ul>
-	</li>
-
-	<li>The intpm(4) smbus driver was fixed to attach to the AMD
-	  FCH (Fusion Controller Hub).</li>
-
-	<li>All MCA banks are now enabled and monitored on Zen
-	  CPUs.</li>
-
-	<li>Feature-bit decoding was added for: CLZERO, SVM features,
-	  and RAS capabilities.</li>
-
-	<li>SHA intrinsic support was added to the aesni(4) driver.
-	  Ryzen is currently the only desktop processor to feature
-	  these intrinsics.  Support for these intrinsics is also
-	  present in Intel's Goldmont line of low-end SoCs.</li>
-      </ul>
-
-      <p>Overall, Zen is now a very usable platform for x86
-	workstations and servers.</p>
-    <p>This project was sponsored by Dell EMC Isilon.</p><h3>Open tasks:</h3><ol><li>Add HWPMC support for the new performance counters
-	avilable on the Zen architecture.</li><li>Add support for the CCP (Crypto Co-Processor).</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><p>
-	Contact:
-	  John
-	  Baldwin
-	 &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Luca
-	  Pizzamiglio
-	 &lt;<a href="mailto:pizzamig@FreeBSD.org">pizzamig@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <tt>devel/gdb</tt> port has been updated to GDB 8.0.1.</p>
-
-      <p>Support for FreeBSD/aarch64 userland binaries has been committed
-	upstream.  These patches, along with support for debugging
-	FreeBSD/aarch64 kernels, have been committed to the port.</p>
-
-      <p>Upstream patches adding improved support for FreeBSD/arm userland
-	binaries are currently in review.  FreeBSD 12 has recently grown
-	support for debugging VFP registers via <tt>ptrace()</tt> and
-	core dumps as part of this work.  Support for FreeBSD/arm kernels
-	will be added to the port after the upstream patches are added
-	to the port.</p>
-
-       <p>Support for <tt>$_siginfo</tt> has been committed upstream.
-	 This uses the recently added NT_LWPINFO note to extract
-	 signal information from process cores.</p>
-
-       <p>Hangs that occured when GDB's <tt>kill</tt> command was used
-	 were fixed in FreeBSD in r313992.</p>
-    <h3>Open tasks:</h3><ol><li>Figure out why the powerpc <tt>kgdb</tt> targets are not able to
-	unwind the stack past the initial frame.</li><li>Test support for sparc64 binaries and kernels.</li><li>Add support for debugging powerpc vector registers.</li><li>Implement <tt>info proc</tt> commands.</li><li>Implement <tt>info os</tt> commands.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="FreeBSDDesktop" href="#FreeBSDDesktop" id="FreeBSDDesktop">FreeBSDDesktop</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/" title="https://github.com/FreeBSDDesktop/">FreeBSDDesktop on GitHub</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop/" title="FreeBSDDesktop on GitHub">https://github.com/FreeBSDDesktop/</a></td></tr></table><p>
-	Contact:
-	  Johannes
-	  Dieterich
-	 &lt;<a href="mailto:jmd@freebsd.org">jmd@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Mark
-	  Johnston
-	 &lt;<a href="mailto:markj@freebsd.org">markj@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Hans Petter
-	  Selasky
-	 &lt;<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>&gt;
-	<br />
-	Contact:
-	  Matthew
-	  Macy
-	 &lt;<a href="mailto:mmacy@nextbsd.org">mmacy@nextbsd.org</a>&gt;
-	</p>
-      <p>The FreeBSDDesktop team is happy to announce the availability of
-	<tt>graphics/drm-next-kmod</tt>.  This port for FreeBSD-CURRENT
-	(amd64) provides support for the <tt>amdgpu</tt>,
-	<tt>i915</tt>, and <tt>radeon</tt> DRM
-	modules using the <tt>linuxkpi</tt> compatibility framework.
-	The port currently corresponds to the DRM from Linux 4.9 and is in
-	an experimental state.  It works reliably for many testers
-	with modern GPU hardware (AMD HD7000 series/Tahiti to Polaris
-	and Intel HD3000/Sandy Bridge to Skylake).  Broader testing and
-	reporting/fixing of bugs is appreciated.</p> <h3>Open tasks:</h3><ol><li>Resolve issues that cause <tt>radeonkms</tt> and
-	<tt>amdgpu</tt> to fail with EFI boot (though there is a
-	workaround available).</li><li>Upgrade to Linux 4.10 and higher DRM versions.</li><li>Get feedback from broader testing.</li></ol><hr /><h2><a name="OpenJFX-8" href="#OpenJFX-8" id="OpenJFX-8">OpenJFX 8</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.openjdk.java.net/display/OpenJFX/Main" title="https://wiki.openjdk.java.net/display/OpenJFX/Main">OpenJFX Wiki</a></td><td>
-	    URL: <a href="https://wiki.openjdk.java.net/display/OpenJFX/Main" title="OpenJFX Wiki">https://wiki.openjdk.java.net/display/OpenJFX/Main</a></td></tr><tr><td><a href="https://www.freshports.org/java/openjfx8-devel" title="https://www.freshports.org/java/openjfx8-devel">java/openjfx8-devel</a></td><td>
-	    URL: <a href="https://www.freshports.org/java/openjfx8-devel" title="java/openjfx8-devel">https://www.freshports.org/java/openjfx8-devel</a></td></tr><tr><td><a href="https://www.freshports.org/java/openjfx8-scenebuilder" title="https://www.freshports.org/java/openjfx8-scenebuilder">java/openjfx8-scenebuilder</a></td><td>
-	    URL: <a href="https://www.freshports.org/java/openjfx8-scenebuilder" title="java/openjfx8-scenebuilder">https://www.freshports.org/java/openjfx8-scenebuilder</a></td></tr><tr><td><a href="https://github.com/asciidocfx/AsciidocFX" title="https://github.com/asciidocfx/AsciidocFX">AsciidocFX</a></td><td>
-	    URL: <a href="https://github.com/asciidocfx/AsciidocFX" title="AsciidocFX">https://github.com/asciidocfx/AsciidocFX</a></td></tr></table><p>
-	Contact:
-	  Tobias
-	  Kortkamp
-	 &lt;<a href="mailto:tobik@FreeBSD.org">tobik@FreeBSD.org</a>&gt;
-	</p>
-	<p>OpenJFX is an open source, next generation, client
-	  application platform for desktop and embedded systems,
-	  based on JavaSE.  This quarter, the OpenJFX port was
-	  reworked and has received some significant improvements.</p>
-
-	<p>More modules are being built.  With the new web module we
-	  gain support for applications that have their own builtin
-	  web browser such as AsciidocFX.  The new media module
-	  allows JavaFX applications to play audio and video
-	  files.</p>
-
-	<p>A port of the JavaFX scenebuilder, a RAD tool for
-	  building JavaFX scenes, was added to the ports tree.</p>
-
-	<p>The OpenGL Prism backend for GPU acceleration was enabled
-	  by default.</p>
-
-	<p>From a mainainer's and contributor's perspective, the
-	  port was simplified by moving all FreeBSD-local patches to
-	  the ports tree and fetching the upstream sources directly,
-	  instead of using a separate repository for them.</p>
-    <h3>Open tasks:</h3><ol><li>Upstream some of the patches in the Ports Collection.</li></ol><hr /><h2><a name="Puppet" href="#Puppet" id="Puppet">Puppet</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="https://puppetcommunity.slack.com/messages/C6CK0UGB1/">Puppetlab's FreeBSD Slack Channel</a></td><td>
-	    URL: <a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="Puppetlab's FreeBSD Slack Channel">https://puppetcommunity.slack.com/messages/C6CK0UGB1/</a></td></tr></table><p>
-	Contact: Puppet Team &lt;<a href="mailto:puppet@FreeBSD.org">puppet@FreeBSD.org</a>&gt;
-	</p>
-      <p>This summer has seen the creation of a puppet@ team to help
-	maintain the approximately 30 Puppet-related ports in the FreeBSD
-	Ports Collection.
-	These ports were previously maintained by various committers,
-	and from time to time the distributed maintainership
-	introduced some delays when
-	updating a port, due to the need to wait for a maintainer's
-	approval for a related change to a different port.</p>
-
-      <p>Puppet 5 is now in the ports tree (as
-	<tt>sysutils/puppet5</tt>).  The C++ version of Facter
-	(<tt>sysutils/facter</tt>) got a lot of attention and is now a
-	drop-in replacement for the previous Ruby version
-	(<tt>sysutils/rubygem-facter</tt>); it is the default facts
-	source for the Puppet 5 port.</p>
-
-      <p>Work continues on bringing in Puppetserver 5 to the ports
-	tree, and on keeping all the ports up-to-date.</p>
-    <h3>Open tasks:</h3><ol><li>The <tt>pkg</tt> package provider has some minor issues
-	(it breaks things when no repos are configured, and is not
-	working properly from the context of the MCollective package
-	agent).</li><li>The <tt>databases/puppetdb[345]</tt> and
-	<tt>sysutils/puppetserver[45]</tt> ports rely on Clojure and
-	Java, and download compiled jar files instead of building them
-	from source.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree or new external
-      books/documents.</p><br /><h2><a name="Absolute-FreeBSD,-3rd-Edition" href="#Absolute-FreeBSD,-3rd-Edition" id="Absolute-FreeBSD,-3rd-Edition">Absolute FreeBSD, 3rd Edition</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://blather.michaelwlucas.com/archives/3020" title="https://blather.michaelwlucas.com/archives/3020">Official Announcement</a></td><td>
-	    URL: <a href="https://blather.michaelwlucas.com/archives/3020" title="Official Announcement">https://blather.michaelwlucas.com/archives/3020</a></td></tr></table><p>
-	Contact:
-	  Michael
-	  Lucas
-	 &lt;<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>&gt;
-	</p>
-      <p>The first draft of the third edition of <em>Absolute
-	FreeBSD</em> is finished.  It is 220,200 words, or roughly enough to
-	stun a medium-sized ox.  It's on target to be in print before
-	BSDCan 2018.</p>
-    <h3>Open tasks:</h3><ol><li>Stare at the wall blankly for a few days.</li><li>Fix all the problems pointed out by dozens of community
-	reviewers.</li><li>Fix all the problems pointed out by John Baldwin, tech
-	reviewer extraordinaire.</li><li>Editing.  Copyediting.  Page layout.  Page editing.
-	Re-editing.  Indexing.  Edits discovered by indexer.</li><li>Pre-orders should open some time next year.</li><li>Restrain myself from strangling people who ask when the
-	fourth edition is coming.</li></ol><hr /><h2><a name="Manual-Pages" href="#Manual-Pages" id="Manual-Pages">Manual Pages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/">FreeBSD Documentation Project Primer</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="FreeBSD Documentation Project Primer">https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/</a></td></tr></table><p>
-	Contact:
-	  Warren
-	  Block
-	 &lt;<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>&gt;
-	</p>
-      <p>Over the last year, interest has increased in manual pages, in
-	large part due to excellent infrastructure work by Baptiste
-	Daroussin and others, and promotion by George Neville-Neil and
-	others.  This increased interest has been both gratifying and
-	problematic.  Our man pages are underappreciated gems, but we
-	have sadly lacked any substantial documentation on how to write
-	new ones.</p>
-
-      <p>In September, I added a new chapter to the
-	<a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" shape="rect">FreeBSD
-	  Documentation Project Primer</a> describing the basics of
-	creating a man page.  It includes descriptions of the
-	markup, section structure, recommended optional material
-	such as examples, and sample templates for the most common
-	types of man pages.  The Resources section includes links to
-	several external resources, including the excellent <a href="http://manpages.bsd.lv/mdoc.html" shape="rect">Practical UNIX
-	Manuals: mdoc</a>.</p>
-
-      <p>While this chapter is not a full tutorial, it does begin to fill
-	in a large gap in our documentation resources and provide a
-	starting point from which to grow.</p>
-    <h3>Open tasks:</h3><ol><li>Add more explanation and examples of markup usage.</li><li>Expand the sample templates with additional desired standard
-	features, like an EXAMPLES section.</li><li>Add more sample templates.</li></ol><hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="The-nosh-Project" href="#The-nosh-Project" id="The-nosh-Project">The nosh Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/" title="http://jdebp.eu./Softwares/nosh/">Introduction</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/" title="Introduction">http://jdebp.eu./Softwares/nosh/</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html" title="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html">FreeBSD Binary Packages</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html" title="FreeBSD Binary Packages">http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html" title="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html">Installation How-To</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html" title="Installation How-To">http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/roadmap.html" title="http://jdebp.eu./Softwares/nosh/roadmap.html">Roadmap</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/roadmap.html" title="Roadmap">http://jdebp.eu./Softwares/nosh/roadmap.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/guide/index.html" title="http://jdebp.eu./Softwares/nosh/guide/index.html">A Slightly Outdated User Guide</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/guide/index.html" title="A Slightly Outdated User Guide">http://jdebp.eu./Softwares/nosh/guide/index.html</a></td></tr><tr><td><a href="http://framagit.org/taca/archnosh" title="http://framagit.org/taca/archnosh">Archnosh</a></td><td>
-	    URL: <a href="http://framagit.org/taca/archnosh" title="Archnosh">http://framagit.org/taca/archnosh</a></td></tr></table><p>
-	Contact:
-	  Jonathan
-	  de Boyne Pollard
-	 &lt;<a href="mailto:J.deBoynePollard-newsgroups@NTLWorld.COM">J.deBoynePollard-newsgroups@NTLWorld.COM</a>&gt;
-	</p>
-      <p>The <tt>nosh</tt> project is a suite of system-level utilities for
-	initializing, running, and shutting down BSD systems; and for
-	managing daemons, terminals, and logging.  It attempts to
-	supersede BSD <tt>init</tt>, the Mewburn <tt>rc.d</tt> system,
-	and OpenRC as used on FreeBSD and TrueOS, drawing inspiration
-	from Solaris SMF for named milestones, daemontools-encore for
-	service control/status mechanisms, UCSPI, and IBM AIX for
-	separated service and system management.  It includes a range
-	of compatibility mechanisms, including shims for familiar
-	commands from other systems, and an automatic import mechanism
-	that takes existing configuration data from
-	<tt>/etc/fstab</tt>, <tt>/etc/rc.conf{,.local}</tt>,
-	<tt>/etc/ttys</tt>, and elsewhere, applying them to its native
-	service definitions and creating additional native services.
-	It is portable (including to Linux) and composable, it
-	provides a migration path from the world of <tt>systemd</tt> Linux, and
-	it does not require new kernel APIs.  It provides clean
-	service environments, orderings and dependencies between
-	services, parallelized startup and shutdown (including
-	<tt>fsck</tt>), strictly size-capped and autorotated logging,
-	the service manager as a "subreaper", and uses
-	<tt>kevent(2)</tt> for event-driven parallelism.</p>
-
-      <p>Since the last status report, in December 2015, the project
-	has seen: restructured and finer-grained packaging that has
-	fewer conflicts with other toolsets; the addition of
-	<tt>zsh</tt> completion files; improvements to the virtual
-	terminal subsystem, keyboard map, mouse support, and ugen and
-	DECSCUSR support; RFC 5424/5426 remote logging support;
-	replacement of libkqueue and the C library's environment
-	handling functions; several new helper commands; support for
-	Java VM autolocation; improved socket-passing code; an
-	extended status API and "one-shot" service support;
-	additional pre-supplied service bundles; support for service
-	aliases; improved handling of per-user D-Bus services;
-	improved importing of MySQL, MariaDB, Percona, and OpenVPN
-	services; improved configuration import support; and extensive
-	additions to the <tt>nosh</tt> Guide.</p>
-
-      <p>On the recently updated roadmap you can see plans for even
-	more documentation, continuing the work to extend the
-	capabilities of the networking subsystem, and the scant
-	handful of <tt>rc.d</tt>-related items remaining.  There are
-	also some ideas still in the speculative or planning phases,
-	including work that may depend on incorporating <tt>nosh</tt>
-	support into other software.</p>
-    <h3>Open tasks:</h3><ol><li>Improve Ansible and SaltStack integration (the maintainer
-	of the Arch Linux <tt>nosh</tt> integration has some
-	ideas).</li><li>Command-line completions are still needed for
-	<tt>bash</tt>, <tt>csh</tt>, and <tt>fish</tt>.</li><li>Document <tt>convert-systemd-units</tt> for use by port
-	maintainers in making packaged service bundles from
-	<tt>systemd</tt> unit files.</li><li><tt>nosh</tt> could take advantage of several proposed
-	features for the base system:
-
-	<ul>
-	  <li>the boot loader signaling "emergency" and
-	    "rescue" modes of operation</li>
-
-	  <li>adding machine-readable status output to
-	    <tt>fsck</tt></li>
-
-	  <li>adding runtime support for more
-	    <tt>clang</tt>-compilable languages in the early bootstrap
-	    stage</li>
-
-	  <li>adding hooks for invoking external configuration import
-	    mechanisms</li>
-	</ul>
-      </li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2017-10-2017-12.html b/website/content/en/status/report-2017-10-2017-12.html
deleted file mode 100644
index ecd6b159bb..0000000000
--- a/website/content/en/status/report-2017-10-2017-12.html
+++ /dev/null
@@ -1,644 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p><strong>This is a draft of the October&#8211;December 2017
-      status report.  Please check back after it is finalized, and
-      an announcement email is sent to the FreeBSD-Announce mailing
-      list.</strong></p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#RDMA-stack-update-based-on-Linux-v4.9">RDMA stack update based on Linux v4.9</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-PowerNV-(ppc64)">FreeBSD on PowerNV (ppc64)</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul></ul><h3><a href="#Ports">Ports</a></h3><ul></ul><h3><a href="#Documentation">Documentation</a></h3><ul></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#LibreNMS">LibreNMS</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-	Page</a>.</p><br /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to ports">https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/portmgr/index.html" title="https://www.FreeBSD.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/portmgr/index.html" title="Ports Management Team">https://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/FreeBSD_portmgr/" title="https://twitter.com/FreeBSD_portmgr/">FreeBSD Ports Managemnet Team on Twitter (@FreeBSD_portmgr)</a></td><td>
-	    URL: <a href="https://twitter.com/FreeBSD_portmgr/" title="FreeBSD Ports Managemnet Team on Twitter (@FreeBSD_portmgr)">https://twitter.com/FreeBSD_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">FreeBSD Ports Management Team on Facebook</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="FreeBSD Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team on Google+</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="FreeBSD Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact:
-	  Ren�
-	  Ladan
-	 &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The last quarter of 2017 ended with over 27,000 ports in the
-	repository.  There are currently just under 2,800 open ports
-	PRs with 685 of them unassigned.  There were 6,700 commits
-	made by 178 committers.  The statistics did not change much
-	since last quarter, however the number of unassigned PRs
-	dropped slightly.</p>
-
-      <p>This quarter, we welcomed Yuri Victorovich (yuri@), Jason
-	Bacon (jwb@), and Wolfram Scheider (wosch@) as new or
-	returning port committers.  No commit bits were taken in for
-	safekeeping.</p>
-
-      <p>Portmgr, together with postmaster@, changed the policy of the
-	FreeBSD-ports@ mailing list.  It is now required to be
-	subscribed to the list before one can post to it.  This will
-	help in reducing spam on this list and help users finding
-	better questions to their answers while browsing the list
-	archive.</p>
-
-      <p>This quarter ports "flavors" went live.  Flavors
-	can be used to build multiple variations of a port, for
-	example <tt>py27-sarge</tt> and <tt>py36-sarge</tt>.  All
-	Python ports and some other ports are now flavored.  Other
-	uses of flavors could be including or excluding X11
-	(<tt>foo</tt> vs <tt>foo-x11</tt> or <tt>foo-nox11</tt>) or
-	selecting the printer paper size (A4 vs letter).</p>
-
-      <p><tt>USES=fmake</tt> has been removed as it was no longer
-	useful.</p>
-
-      <p>Some default versions got updated: Ruby to 2.4 and Samba to
-	4.6.  Firefox got updated to version 57.0.3 and <tt>pkg</tt> to
-	1.10.3.</p>
-
-      <p>During the last quarter, antoine@ ran 33 exp-runs to validate changes
-	to the base system, fix Qt5 ports, test Python flavors and other port
-	updates, and make rubygem port builds reproducible.</p>
-    <h3>Open tasks:</h3><ol><li>Clang 6 is being imported into base.  There is a PR that keeps track
-	of ports failing with this compiler, see <url href="http://bugs.FreeBSD.org/224669">PR 224669</url>.  If you use
-	any ports mentioned here, please consider fixing them.</li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The most significant action by Core during the final quarter of
-	2017 was the approval of the new Code of Conduct after a long
-	period of development and review.  Core added a preamble to the
-	text emphasizing the principles behind the Code of Conduct over
-	detailed interpretation of the rules.  The new code delegates
-	the handling of complaints to a Code of Conduct review board; we
-	are currently finalizing practical arrangements around setting
-	up the review board before announcing the adoption of the new
-	code.</p>
-
-      <p>John Hixson of iXsystems was proposed, and accepted, as the
-	first new Project Member under the new rules adopted earlier
-	this year.  Core feels that John is an excellent choice as the
-	first member, and looks forwards to adding many other project
-	members in the future.</p>
-
-      <p>There have been some significant changes around the Security
-	Officer and secteam.  Gordon Tetlow has formally taken over the
-	role of Security Officer from Xin Li.  Xin remains an active
-	member of secteam, and Ed Maste has now joined secteam as well.
-	</p>
-
-      <p>Gordon joined Secteam at a point where they were struggling
-	with handling the widely publicised WPA2 vulnerability
-	(FreeBSD-SA-17:07.wpa), and had an immediate impact simply by
-	making a public response, even though the technical fixes were
-	not entirely ready.  Gordon's remit from Core is to examine how
-	Secteam operates and work out how to manage their case-load while
-	avoiding the problems of burn-out and overload that have impeded
-	Secteam's effectiveness in the past.</p>
-
-      <p>One of the key problems is that security problems are handled
-	in a completely separate bug handling system to general PRs.
-	This is unusual compared to most similar OS projects, and leads
-	to difficulties in bringing in available talent from amongst the
-	entire body of FreeBSD developers in order to be able to share
-	the load and react quickly.  Secteam is working with Bugmeister
-	to enable suitable access controls within our main Bugzilla
-	instance, so that we can both conform to bug embargoes and other
-	confidentiality requirements but also make it easy to solicit
-	fixes from a wider range of developers and to transition
-	security bugs to open handling like any other bug once there is
-	no more need for secrecy.</p>
-
-      <p>This quarter also saw the creation of a 10.4-RELEASE branch,
-	and the extension of the lifetime of 11.0-RELEASE by one month.
-	The former was in response to requests from a number of
-	prominent FreeBSD consumers, who needed access to new
-	functionality but could not immediately upgrade to 11.0-RELEASE.
-	Releasing 10.4 permitted this without making a significant
-	extension to the lifetime of the 10.x release series.</p>
-
-      <p>The extension to 11.0-RELEASE EoL was a consequence of failing
-	to communicate the impending switch to 11.1-RELEASE in good
-	time.  Since this was the first minor version transition under
-	the new release schedule, in discussion with Secteam and Release
-	Engineering, we concluded that a delay was necessary to allow
-	the userbase sufficient warning to upgrade before 11.0-RELEASE
-	went out of support.  This was not a cost-free decision: as
-	Portmgr reminded us, this affected package building and delayed
-	implementation of some important updates.</p>
-
-      <p>FreeBSD will be participating in Google Summer of Code again in
-	2018.  This has become one of our most important routes for
-	recruiting the new, young developers vital for ensuring the
-	longevity of the project.</p>
-
-      <p>Pedro Giffuni proposed adopting the SPDX license tagging system
-	as used by many other projects, including the Linux kernel, in
-	order to facilitate programatic license management by downstream
-	consumers.  Core agreed enthusiasticly.</p>
-
-      <p>Core has agreed to promote the MIPS architecture to Tier-2
-	status.</p>
-
-      <p>A proposal to enhance security by discontinuing HTTP or other
-	unencrypted channels for all FreeBSD services was not something
-	Core could approve for the immediate future.  While switching to
-	HTTPS has obvious security benefits, we would need to distribute
-	appropriate CA certificates as part of the base system and make
-	certain other changes before this could be achieved relatively
-	seamlessly.  All FreeBSD services are already available over
-	secure channels, but our documentation did not necessarily
-	present secure access methods as the preferred routes.  Action
-	is being taken to address the documentation, and this question
-	will be revisited once the necessary groundwork is in place.</p>
-
-      <p>The <tt>fortune(6)</tt> program has long been a focus for controversy,
-	and previous Cores have needed to impose a lock on updates to
-	the fortune data files.  The argument blew up again over the
-	re-deletion of a number of apparently pro-Nazi quotations.  Core
-	decided that enough was enough and removed all of the fortune
-	data files except for <tt>FreeBSD-tips.dat</tt> from the base system.
-	The tacit approval of many questionable or controversial
-	opinions by shipping them as a part of the base system is a
-	liability the project simply cannot afford.</p>
-
-      <p>No new commit bits were issued during this quarter, but we did
-	see two former committers: Sean Eric Fagan and Wolfram
-	Schneider, reactivate their commit bits.  One committer, Ngie
-	Cooper, has handed back their bit.</p>
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="RDMA-stack-update-based-on-Linux-v4.9" href="#RDMA-stack-update-based-on-Linux-v4.9" id="RDMA-stack-update-based-on-Linux-v4.9">RDMA stack update based on Linux v4.9</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=326169" title="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=326169">Subversion Commit Adding the Driver</a></td><td>
-	    URL: <a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=326169" title="Subversion Commit Adding the Driver">https://svnweb.FreeBSD.org/base?view=revision&amp;revision=326169</a></td></tr></table><p>
-	Contact: Mellanox Drivers Team &lt;<a href="mailto:FreeBSD-drivers@mellanox.com">FreeBSD-drivers@mellanox.com</a>&gt;
-	</p>
-      <p>An update to the FreeBSD RDMA stack based on code from Linux
-	v4.9 was merged into FreeBSD 12-CURRENT on November 4th,
-	including many bug fixes and new features with a focus on
-	RoCEv2 &#8212; Routable RoCE.</p>
-
-      <p>RDMA over Converged Ethernet (RoCE) is a network protocol
-	that leverages Remote Direct Memory Access (RDMA) capabilities
-	to accelerate communications between applications hosted on
-	clusters of servers and storage arrays.  RoCE incorporates the
-	IBTA RDMA semantics to allow devices to perform direct memory
-	to memory transfers at the application level without involving
-	the host CPU.  Both the transport processing and the memory
-	translation and placement are performed by hardware resulting
-	in lower latency, higher throughput, and better performance
-	compared to software based protocols.</p>
-
-      <p>RoCEv2 is the most recent version of RoCE, adding some routing
-	capabilities as both IP and UDP headers are included in the
-	packet format.  To complete the RoCEv2 solution, Support for
-	ECN (Explicit Congestion Notification, lossy fabric) and PFC
-	(Priority Flow Control, lossless fabric) protocols with rate
-	limiting options will be added in the first quarter of
-	2018.</p>
-
-      <p>This project also introduces the following updates:</p>
-
-      <ul>
-	<li><tt>libibverbs</tt>, <tt>librdmacm</tt>,
-	  <tt>libibumad</tt> and vendor-specific libraries
-	  ported from the Linux rdma-core v15+</li>
-
-	<li>InfiniBand diagnostic tools,
-	  <tt>infiniband-diags</tt>, version 1.6.7</li>
-
-	<li>InfiniBand subnet manager &#8212; OpenSM, version 3.3.20+</li>
-
-	<li>LinuxKPI support</li>
-      </ul>
-
-      <p>Important notes:</p>
-
-      <ul>
-	<li>GPL-only (non dual-licensed) portions of the Linux code were either
-	excluded or written from scratch under a BSD license by
-	Hans Petter Selasky.</li>
-
-	<li>The code has been tested by several RDMA vendors
-	  that also support iWARP.</li>
-      </ul>
-    <p>This project was sponsored by Mellanox Technologies.</p><h3>Open tasks:</h3><ol><li>Add ECN (Explicit Congestion Notification) and PFC
-	(Priority Flow Control) support.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="FreeBSD-on-PowerNV-(ppc64)" href="#FreeBSD-on-PowerNV-(ppc64)" id="FreeBSD-on-PowerNV-(ppc64)">FreeBSD on PowerNV (ppc64)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/Semihalf/powernv" title="https://github.com/Semihalf/powernv">Semihalf PowerNV Official Repository</a></td><td>
-	    URL: <a href="https://github.com/Semihalf/powernv" title="Semihalf PowerNV Official Repository">https://github.com/Semihalf/powernv</a></td></tr><tr><td><a href="https://github.com/open-power/skiboot" title="https://github.com/open-power/skiboot">Skiboot Repository with the Latest OPAL Firmware</a></td><td>
-	    URL: <a href="https://github.com/open-power/skiboot" title="Skiboot Repository with the Latest OPAL Firmware">https://github.com/open-power/skiboot</a></td></tr></table><p>
-	Contact:
-	  Patryk
-	  Duda
-	 &lt;<a href="mailto:pdk@semihalf.com">pdk@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Wojciech
-	  Macek
-	 &lt;<a href="mailto:wma@FreeBSD.org">wma@FreeBSD.org</a>&gt;
-	<br />
-	Contact:
-	  Michal
-	  Stanek
-	 &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact:
-	  Nathan
-	  Whitehorn
-	 &lt;<a href="mailto:nw@FreeBSD.org">nw@FreeBSD.org</a>&gt;
-	</p>
-      <p> Semihalf is happy to announce that FreeBSD is running on an IBM
-	Power8 processor.  This project is a continuation of work done
-	by Nathan Whitehorn, who provided a basic support for a
-	PowerNV emulator.</p>
-
-      <p>The IBM Power8 family of CPUs offers superior performance
-	compared to previous CPUs in the Power series.  It provides
-	complete NUMA support with up to 128 execution threads in
-	two-socket system (2 sockets, 8 cores per socket, 8 threads
-	per core).  All I/O communication is handled by an integrated
-	PCIe interface equipped with multiple IOMMU engines.</p>
-
-      <p>The support for Power8 system running FreeBSD in a non-virtualized
-	environment contains:</p>
-
-      <ul>
-	<li>A generic driver for the OPAL hypervisor</li>
-
-	<li><tt>kboot</tt> loader modifications to allow for a
-	  little-endian to load a big-endian kernel ELF image</li>
-
-	<li>An update to the ELF parser in <tt>skiboot</tt>, allowing
-	  it to understand the FreeBSD kernel file format</li>
-
-	<li>Basic support for the PowerNV architecture, including
-	  modes of operation, memory-management unit (MMU), and
-	  interrupt controller</li>
-
-	<li>SMP operation with up to 128 CPUs</li>
-
-	<li>PCI host bridge subsystem driver, including IOMMU mapping
-	  for external busses</li>
-
-	<li>PCIe host controller driver</li>
-
-	<li>USB-3.0 XHCI driver</li>
-
-	<li>Reworked several drivers to be big-endian compatible</li>
-
-	<li>Chelsio cxgbe(4) 10/25G network adapter</li>
-
-	<li>NVMe SSD driver</li>
-      </ul>
-
-      <p>All work is available in the linked GitHub repository.  The
-	process of getting this work into the official repository has
-	already started and eventually, all commits will be integrated
-	into FreeBSD-12 CURRENT.</p>
-    <p>This project was sponsored by IBM, The FreeBSD Foundation, QCM Technologies, Semihalf, and Limelight Networks (Kevin Bowling).</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree or new external
-      books/documents.</p><br /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><p>Objects that defy categorization.</p><br /><h2><a name="LibreNMS" href="#LibreNMS" id="LibreNMS">LibreNMS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/librenms/librenms/pull/7938" title="https://github.com/librenms/librenms/pull/7938">LibreNMS ZFS Addition</a></td><td>
-	    URL: <a href="https://github.com/librenms/librenms/pull/7938" title="LibreNMS ZFS Addition">https://github.com/librenms/librenms/pull/7938</a></td></tr></table><p>
-	Contact:
-	  Zane
-	  Bowers-Hadley
-	 &lt;<a href="mailto:vvelox@vvelox.net">vvelox@vvelox.net</a>&gt;
-	</p>
-      <p>LibreNMS is an autodiscovering PHP/MySQL/SNMP-based network
-	monitoring solution which includes support for a wide range of
-	network hardware and operating systems, including Cisco,
-	Linux, FreeBSD, Juniper, Brocade, Foundry, HP and many more.</p>
-
-      <p>Among other things, it can monitor applications and other
-	functionality running on a server via SNMP extensions.  This
-	has been the area of focus for my present work.</p>
-
-      <p>ZFS support has been committed towards the end of December,
-	which was too late to make the December release, but it will
-	be in the January release.</p>
-
-      <p>This brings the ability to monitor ARC and pool information,
-	with each pool having its own separate set of graphs.</p>
-
-      <p>The ARC graphing is as below.</p>
-
-      <ul>
-	<li>ARC size in bytes</li>
-
-	<li>ARC size, percent of max size</li>
-
-	<li>ARC size breakdown</li>
-
-	<li>ARC efficiency</li>
-
-	<li>ARC cache hits by list</li>
-
-	<li>ARC cache hits by type</li>
-
-	<li>ARC cache misses by type</li>
-
-	<li>ARC cache hits</li>
-
-	<li>ARC cache misses</li>
-
-	<li>ARC misc (deleted, skips, and recycle misses)</li>
-      </ul>
-
-      <p>The pool tracking is comparatively much simpler, using the
-	output from <tt>zpool list</tt>.</p>
-
-      <ul>
-	<li>Pool Space</li>
-
-	<li>Pool Capacity</li>
-
-	<li>Pool Fragmentation</li>
-      </ul>
-    <h3>Open tasks:</h3><ol><li>Suggestions are needed for additional statistics or other
-	information to monitor, whether FreeBSD-specific or
-	otherwise.</li></ol><hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2018-01-2018-09.html b/website/content/en/status/report-2018-01-2018-09.html
deleted file mode 100644
index 7be5653704..0000000000
--- a/website/content/en/status/report-2018-01-2018-09.html
+++ /dev/null
@@ -1,2906 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>With FreeBSD having gone all the way to 12, it is perhaps
-      useful to take a look back at all the things that have been
-      accomplished, in terms of many visible changes, as well as all
-      the things that happen behind the scenes to ensure that FreeBSD
-      continues to offer an alternative in both design,
-      implementation, and execution.</p><p>The things you can look forward to reading about are too
-      numerous to summarize, but cover just about everything from
-      finalizing releases, administrative work, optimizations
-      and depessimizations, features added and fixed, and many areas
-      of improvement that might just surprise you a little.</p><p>Please have a cup of coffee, tea, hot cocoa, or other beverage
-      of choice, and enjoy this culmulative set of reports covering
-      everything that's been done since October, 2017.</p><p>&#8212;Daniel Ebdrup</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#Core-Team">Core Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Release-Engineering-Team">Release Engineering Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#32-bit-compatibility-and-other-ABI-cleanups">32-bit compatibility and other ABI cleanups</a></li><li><a href="#4G/4G-address-space-split-for-i386">4G/4G address space split for i386</a></li><li><a href="#ACPI-NVDIMM-driver">ACPI NVDIMM driver</a></li><li><a href="#Boot-Loader">Boot Loader</a></li><li><a href="#Building-FreeBSD-on-non-FreeBSD-hosts">Building FreeBSD on non-FreeBSD hosts</a></li><li><a href="#Device-Mode-USB">Device Mode USB</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#FreeBSD-Graphics-Team">FreeBSD Graphics Team</a></li><li><a href="#FreeBSD/DTrace">FreeBSD/DTrace</a></li><li><a href="#ifuncs">ifuncs</a></li><li><a href="#Intel-Work-on-Core-Enabling-and-Security">Intel Work on Core Enabling and Security</a></li><li><a href="#Large-scale-package-building">Large scale package building</a></li><li><a href="#LLVM-7.0---Sanitizers-support-improvements-/-Static-code-analysis">LLVM 7.0 - Sanitizers support improvements / Static code analysis</a></li><li><a href="#Performance-improvements">Performance improvements</a></li><li><a href="#Save/Restore/Migration-support-in-bhyve">Save/Restore/Migration support in bhyve</a></li><li><a href="#SMAP">SMAP</a></li><li><a href="#String-functions-on-the-amd64-architecture">String functions on the amd64 architecture</a></li><li><a href="#Usermode-mapping-of-PCI-BARs">Usermode mapping of PCI BARs</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Allwinner-SoC-Support">Allwinner SoC Support</a></li><li><a href="#Armada-38x-FreeBSD-support">Armada 38x FreeBSD support</a></li><li><a href="#ARMv6-and-ARMv7-image-now-use-EFI-loader">ARMv6 and ARMv7 image now use EFI loader</a></li><li><a href="#DTS-Update">DTS Update</a></li><li><a href="#FreeBSD-on-POWER9">FreeBSD on POWER9</a></li><li><a href="#FreeBSD-on-PowerNV-(ppc64)">FreeBSD on PowerNV (ppc64)</a></li><li><a href="#FreeBSD-on-RISC-V">FreeBSD on RISC-V</a></li><li><a href="#PINE64-LTS-Image">PINE64-LTS Image</a></li><li><a href="#PocketBeagle-Support">PocketBeagle Support</a></li><li><a href="#RPI-Firmware/DTB/U-Boot-Update">RPI Firmware/DTB/U-Boot Update</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Puppet">Puppet</a></li><li><a href="#scarab:-CLI-tool-for-Bugzilla-related-workflows">scarab: CLI tool for Bugzilla-related workflows</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Cleaning-up-the-Wiki">Cleaning up the Wiki</a></li><li><a href="#Quarterly-Reports">Quarterly Reports</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#HardenedBSD-2018Q3-Update">HardenedBSD 2018Q3 Update</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-        Page</a>.</p><br /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org/" title="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org/" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org/</a></td></tr><tr><td><a href="https://wiki.FreeBSD.org/Jenkins" title="https://wiki.FreeBSD.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.FreeBSD.org/Jenkins</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="freebsd-ci Repository">https://github.com/freebsd/freebsd-ci</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD CI team maintains continuous integration tasks
-	for FreeBSD. The CI
-	system regularly checks the changes committed to the
-	project's Subversion
-	repository can be successfully built, and performs various
-	tests and analysis
-	with the build results. The CI team also maintains the
-	archive of the artifact
-	built by the CI system, for the further testing and
-	debugging needs.</p>
-
-      <p>Starting from June 2018, the project is sponsored by the
-	FreeBSD Foundation in
-	hardware and staff. For more details of the sponsored
-	projects, please refer
-	to:</p>
-
-      <p><a href="https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-september-2018/" shape="rect">https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-september-2018/</a></p>
-
-      <p>In addition to that, we also helped checking regressions
-	for OpenSSL 1.1.1
-	update and test continuously for 12-STABLE branch.</p>
-
-      <p>We had meetings and working groups at two developer
-	summits during 2018Q3:</p>
-
-      <ul>
-	<li><a href="https://wiki.FreeBSD.org/DevSummit/201808/Testing" shape="rect">BSDCam
-	2018</a></li>
-
-	<li><a href="https://wiki.FreeBSD.org/DevSummit/201809" shape="rect">EuroBSDCon
-	2018</a></li>
-      </ul>
-
-      <p>
-	Work in progress:</p>
-
-      <ul>
-	<li>Fixing the failing test cases and builds</li>
-
-	<li><a href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-dtrace_test/lastCompletedBuild/testReport/" shape="rect">DTrace
-	test</a></li>
-
-	<li><a href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/" shape="rect">ZFS
-	test</a></li>
-
-	<li><a href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-gcc/" shape="rect">GCC
-	build</a></li>
-
-	<li>Adding drm ports building test against -CURRENT</li>
-
-	<li>Adding tests for selected project branches, e.g.:
-	clang700-import</li>
-
-	<li>Adding new hardware to the embedded testbed</li>
-
-	<li>Implementing automatic tests on bare metal hardware</li>
-
-	<li>Planning running ztest and network stack tests</li>
-      </ul>
-
-    <hr /><h2><a name="Core-Team" href="#Core-Team" id="Core-Team">Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>Much of Core's focus for the past months has been on three
-	items:</p>
-
-      <p>1. Coordination between different groups to support the
-	upcoming 12.0 release. The timing of the OpenSSL
-	1.1.1 release posed challenges. The new OpenSSL
-	version included API changes, so many components of
-	the base system and ports required changes.
-	Staying with the older OpenSSL in 12.0 was not a
-	feasible option, because it would have meant
-	backporting many changes to a version of OpenSSL
-	that would be unmaintained by the upstream source.</p>
-
-      <p>2. Discussions with the release engineering team and Scott
-	Long about updating the FreeBSD release process.
-	Topics for exploration include:</p>
-
-      <ul>
-	<li>having more frequent point releases</li>
-
-	<li>changing the support model</li>
-
-	<li>revising and improving the tooling used to manage the tree
-	and releases</li>
-
-	<li>additional topics as they are discovered</li>
-      </ul>
-
-      <p>3. Gathering information to make decisions more
-	data-driven. For example, we are planning
-	developer and user surveys. If there are questions
-	that you think should be added to the survey,
-	please discuss them on freebsd-arch@. We are
-	also exploring ways to collect automated hardware-usage data.
-	This will help the project to understand the changing ways our
-	software is used and to improve hardware support.</p>
-
-      <p>Here are other noteworthy events (in chronological order)
-	since the last quarterly report.</p>
-
-      <p>2017 Q4</p>
-
-      <ul>
-	<li>Sean Eric Fagan's (sef@) commit bit was reactivated with a
-	period of re-mentoring under Alexander Motin
-	(mav@).</li>
-
-	<li>The MIPS architecture was promoted to tier 2 status.</li>
-
-	<li>Core approved changes to the Code of Conduct.</li>
-
-	<li>All fortune data files, except freebsd-tips, were removed
-	in r325828.</li>
-
-	<li>Core approved the adoption of a policy requiring any
-	license exceptions to be recorded alongside code.</li>
-
-	<li>Gordon Tetlow (gordon@) became the new security officer.</li>
-
-	<li>Core approved the use of SPDX tags.</li>
-      </ul>
-
-      <p>2018 Q1</p>
-
-      <ul>
-	<li>Jeb Cramer (jeb@) was awarded a src commit bit under the
-	mentorship of Sean Bruno (sbruno@) and Eric Joyner
-	(erj@).</li>
-
-	<li>Members of the CoC Review Team were approved. The
-	membership is to be reviewed once per year.</li>
-
-	<li>A vendor commit bit was awarded to Slava Shwartsman
-	(slavash@) of Mellanox Technologies under the
-	mentorship of Konstantin Belousov (kib@) and Hans
-	Petter Selasky (hselasky@).</li>
-
-	<li>Walter Schwarzenfeld was awarded project membership.</li>
-
-	<li>Brad Davis (brd@) was awarded a src commit bit under the
-	mentorship of Allan Jude (allanjude@) with
-	Baptiste Daroussin (bapt@) as co-mentor.</li>
-
-	<li>Vincenzo Maffione (vmaffione@) was awarded a src commit
-	bit under the mentorship of Hiroki Sato (hrs@).</li>
-
-	<li>Ram Kishore Vegesna (ram@) was awarded a src commit bit
-	under the mentorship of Kenneth D. Merry (ken@)
-	and Alexander Motin (mav@).</li>
-      </ul>
-
-      <p>2018 Q2</p>
-
-      <ul>
-	<li>Tom Jones (thj@) was awarded a src commit bit under the
-	mentorship of Jonathan T. Looney (jtl@).</li>
-
-	<li>Matt Macy's (mmacy@) commit bit was restored under the
-	mentorship of Sean Bruno (sbruno@).</li>
-
-	<li>Breno Leitao (leitao@) was awarded a src commit bit under
-	the mentorship of Justin Hibbits (jhibbits@) with
-	Nathan Whitehorn (nwhitehorn@) as co-mentor.</li>
-
-	<li>Leandro Lupori (luporl@) was awarded a src commit bit
-	under the mentorship of Justin Hibbits (jhibbits@)
-	with Nathan Whitehorn (nwhitehorn@) as co-mentor.</li>
-
-	<li>The handover from the ninth to the tenth elected Core team
-	took place. The tenth Core members are: Allan Jude
-	(allanjude@), Benedict Reuschling (bcr@), Brooks
-	Davis (brooks@), Hiroki Sato (hrs@), Warner Losh
-	(imp@), Jeff Roberson (jeff@), John Baldwin
-	(jhb@), Kris Moore (kmoore@), and Sean Chittenden
-	(seanc@).</li>
-
-	<li>Joseph Mingrone (jrm@) was appointed the Core secretary
-	under mentorship of the retiring Core secretary,
-	Matthew Seaman (matthew@).</li>
-
-	<li>The new team liaisons were decided. portmgr: Sean, doceng:
-	Hiroki, secteam: Brooks, re: John, clusteradm:
-	Allan, CoC: Warner, Foundation: Benedict,
-	bugmeister: John, CI: Sean.</li>
-
-	<li>David Maxwell (dwm@) was awarded project membership.</li>
-
-	<li>Daichi Goto's (daichi@) commit bit was reactivated with a
-	period of re-mentoring under George Neville-Neil
-	(gnn@).</li>
-
-	<li>A vendor commit bit was awarded to Ben Widawsky
-	(bwidawsk@) of Intel under the mentorship of Ed
-	Maste (emaste@).</li>
-      </ul>
-
-      <p>
-	2018 Q3</p>
-
-      <ul>
-	<li>Core decided to begin meeting twice per month in an
-	attempt to catch up with many new agenda items.</li>
-
-	<li>Li-Wen Hsu (lwhsu@) was awarded a src commit bit under the
-	mentorship of Mark Johnston (markj@) with Ed Maste
-	(emaste@) as co-mentor.</li>
-
-	<li>Samy al Bahra was awarded project membership.</li>
-
-	<li>George Neville-Neil (gnn@) was approved to begin
-	co-mentoring Vincenzo Maffione (vmaffione@).</li>
-      </ul>
-
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to ports">https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring</a></td><td>
-	    URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/portmgr/index.html" title="https://www.FreeBSD.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/portmgr/index.html" title="Ports Management Team">https://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/freebsd_portmgr/" title="https://twitter.com/freebsd_portmgr/">FreeBSD portmgr (@freebsd_portmgr)</a></td><td>
-	    URL: <a href="https://twitter.com/freebsd_portmgr/" title="FreeBSD portmgr (@freebsd_portmgr)">https://twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">FreeBSD Ports Management Team (Facebook)</a></td><td>
-	    URL: <a href="https://www.facebook.com/portmgr" title="FreeBSD Ports Management Team (Facebook)">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team (Google+)</a></td><td>
-	    URL: <a href="https://plus.google.com/communities/108335846196454338383" title="FreeBSD Ports Management Team (Google+)">https://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	</p>
-      <p>During the first quarter of 2018, the number of ports grew
-	to almost 32,000.
-	In 2018Q1, there were
-	2,100 open PRs with fewer than 600 unassigned. There were
-	7,900 commits from 169 committers. Compared to last
-	quarter, the number
-	of commits grew by 18% and the number of PRs dropped by
-	25%. Those are
-	some good numbers!</p>
-
-      <p>During the 2018Q2 and 2018Q3 quarters, the number of ports
-	grew to just under
-	34,000. The number of open PR grew to almost 2,500 with
-	fewer than 600
-	of those unassigned. A total of 175 committers made almost
-	14,200 commits.
-	Compared to the first quarter, the number of commits
-	dropped by 10% and
-	the number of PRs grew by 19%.</p>
-
-      <p>During the last three quarters, portmgr took twelve commit
-	bits in for
-	safekeeping: daichi@, deichen@, ian@, junovitch@, kevlo@,
-	maho@, nemysis@,
-	pawel@, rea@, tabthorpe@, vg@, and wxs@.</p>
-
-      <p>Portmgr welcomed thirteen new committers in 2018Q2 and
-	2018Q3:</p>
-
-      <ul>
-	<li>Devin Teske (dteske@)</li>
-
-	<li>Eric Turgeon (ericbsd@)</li>
-
-	<li>Fernando Apestegu�a (fernape@)</li>
-
-	<li>Fukang Chen (loader@)</li>
-
-	<li>Gleb Popov (arrowd@)</li>
-
-	<li>Jesper Schmitz Mouridsen (jsm@)</li>
-
-	<li>John Hixson (jhixson@)</li>
-
-	<li>Kevin Bowling (kbowling@)</li>
-
-	<li>Koichiro IWAO (meta@)</li>
-
-	<li>Mateusz Piotrowski (0mp@)</li>
-
-	<li>Matthias Fechner (mfechner@)</li>
-
-	<li>Sergey Kozlov (skozlov@)</li>
-      </ul>
-
-      <p>
-	The following committers returned after a hiatus:</p>
-
-      <ul>
-	<li>Ion-Mihai Tetcu (itetcu@)</li>
-
-	<li>Kevin Lo (kevlo@)</li>
-
-	<li>Sean Chittenden (seanc@)</li>
-      </ul>
-
-      <p>
-	During the last three quarters, Antoine Brodin (antoine@)
-	ran no
-	fewer than 113 exp-runs against the ports tree. These runs
-	were
-	executed to test updates, perform cleanups, and make
-	improvements
-	to the framework and the base system. Most of the runs
-	were for
-	port upgrades, but others include LLD progress, changes to
-	the
-	default port versions, improved support for armv6, armv7,
-	and RISC-V
-	architectures, removed old base system functionality, new
-	USES, and
-	better matching pkg-plist with Makefile options (DOCS and
-	EXAMPLES).</p>
-
-      <p>Five new USES values were introduced:</p>
-
-      <ul>
-	<li>apache: handle dependencies on the Apache web server and
-	modules</li>
-
-	<li>eigen: automatically depend on math/eigen2 or math/eigen3</li>
-
-	<li>emacs: handle dependencies on the Emacs editor and
-	modules.</li>
-
-	<li>gl replaces the old USE_GL from bsd.port.mk</li>
-
-	<li>qt-dist, qt:4 and qt:5 replace the old USE_QT from
-	bsd.qt.mk</li>
-      </ul>
-
-      <p>
-	The EXTRA_PATCHES functionality has been extended to
-	support
-	directories, where it will automatically apply all
-	patch-\* files to the port.</p>
-
-      <p>Ports using USES=php:phpize, php:ext, php:zend, and
-	php:pecl have
-	been flavored and packages are now automatically built
-	for all
-	versions of PHP that are supported (5.6, 7.0, 7.1 or 7.2).</p>
-
-      <p>2018Q3 had updates of major ports: pkg 1.10.5, Chromium
-	65.0.3325.181, Firefox 59.0.2, Firefox-ESR 52.7.3, Ruby
-	2.3.7/2.5.1
-	and Qt5 5.9.4.
-	The default version of PHP was changed from 5.6 to 7.1.
-	The former
-	version of PHP is no longer supported by the developers.
-	The
-	default versions of Samba and GCC are now respectively 4.7
-	and 7. The
-	Xorg ports have been reorganized and there have been
-	changes to
-	net/openntpd. Please review the UPDATING file for relevant
-	details.</p>
-
-      <p>Open tasks:</p>
-
-      <ul>
-	<li>The number of commits dropped somewhat over the last three
-	quarters,
-	leaving more PRs unresolved. If possible, please pick up
-	some PRs
-	and improve everyone's experience.</li>
-      </ul>
-
-    <hr /><h2><a name="Release-Engineering-Team" href="#Release-Engineering-Team" id="Release-Engineering-Team">Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/releases/10.4R/announce.html" title="https://www.FreeBSD.org/releases/10.4R/announce.html">FreeBSD 10.4-RELEASE announcement</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/10.4R/announce.html" title="FreeBSD 10.4-RELEASE announcement">https://www.FreeBSD.org/releases/10.4R/announce.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/releases/11.2R/announce.html" title="https://www.FreeBSD.org/releases/11.2R/announce.html">FreeBSD 11.2-RELEASE announcement</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/11.2R/announce.html" title="FreeBSD 11.2-RELEASE announcement">https://www.FreeBSD.org/releases/11.2R/announce.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/releases/12.0R/schedule.html" title="https://www.FreeBSD.org/releases/12.0R/schedule.html">FreeBSD 12.0-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/releases/12.0R/schedule.html" title="FreeBSD 12.0-RELEASE schedule">https://www.FreeBSD.org/releases/12.0R/schedule.html</a></td></tr><tr><td><a href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/" title="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team responsibilities
-	include:</p>
-
-      <ul>
-	<li>setting and publishing release schedules for official
-	project releases of FreeBSD</li>
-
-	<li>announcing code slushes, freezes, and thaws</li>
-
-	<li>maintaining the respective branches for all supported
-	releases</li>
-      </ul>
-
-      <p>
-	The FreeBSD Release Engineering Team, led by Marius
-	Strobl,
-	completed the 10.4-RELEASE in early October 2017. FreeBSD
-	10.4-RELEASE was the
-	fifth release from the <tt>stable/10</tt> branch, which
-	built on the
-	stability and reliability of 10.3-RELEASE.</p>
-
-      <p>The FreeBSD 11.2-RELEASE cycle started April 20, 2018 with
-	the
-	announcement of the code slush. The first stage progress
-	was
-	continued throughout the rest of the quarter with the code
-	freeze,
-	followed by three BETA builds, three RC builds, and the
-	final release
-	build was announced June 27, 2018.</p>
-
-      <p>The FreeBSD Release Engineering Team started the
-	12.0-RELEASE cycle
-	August 10, 2018 with the announcement of the code slush.
-	The code
-	freeze followed on August 24, 2018. The tentative date for
-	the <tt>stable/12</tt> branch was expected to be September 21,
-	2018.</p>
-
-      <p>
-	Due to unforeseen circumstances with upstream code that
-	was necessary
-	to include in 12.0-RELEASE, the tentative release schedule
-	needed
-	to be adjusted several times. The API changes in the
-	updated version
-	of the upstream code required changes to be made for all
-	base system
-	utilities that linked with the upstream code. By the end
-	of the
-	2018Q3 quarter, the <tt>stable/12</tt> branch had not been
-	created due to
-	this delay.</p>
-
-      <p>Throughout the remainder of 2018Q3, several development
-	snapshots builds
-	were released for the <tt>head</tt>, <tt>stable/11</tt>,
-	and <tt>stable/10</tt> branches.</p>
-
-      <p>Much of this work was sponsored by the FreeBSD Foundation.</p>
-
-    <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to supporting and promoting
-	the FreeBSD Project and community worldwide.
-	Funding comes from individual and corporate
-	donations and is used to fund and manage software
-	development projects, conferences and developer
-	summits, and provide travel grants to FreeBSD
-	contributors. The Foundation purchases and
-	supports hardware to improve and maintain FreeBSD
-	infrastructure and provides resources to improve
-	security, quality assurance, and release
-	engineering efforts; publishes marketing material
-	to promote, educate, and advocate for the FreeBSD
-	Project; facilitates collaboration between
-	commercial vendors and FreeBSD developers; and
-	finally, represents the FreeBSD Project in
-	executing contracts, license agreements, and other
-	legal arrangements that require a recognized legal
-	entity.</p>
-
-      <p>Here are some highlights of what the FreeBSD Foundation
-	did to help FreeBSD last quarter:</p>
-
-      <p>Partnerships and Commercial User Support</p>
-
-      <p>As a 501(c)(3) non-profit, we don't directly support
-	commercial users, but we do work with them to
-	understand their needs and help facilitate
-	collaboration with the community. Last quarter we
-	met with a few key FreeBSD users and supporters,
-	to discuss pain points, how they can contribute
-	back to FreeBSD, and what technologies they would
-	like to see supported, to support FreeBSD over
-	more of their technologies and products.</p>
-
-      <p>As many of you know, we formed a partnership with Intel
-	around one and a half years ago. Since then the
-	people we worked directly with left the company,
-	but it moved us into a new relationship with their
-	Open Source Technology Center (OTC).</p>
-
-      <p>We are very encouraged that Intel has dedicated additional
-	resources from the OTC to work on FreeBSD in
-	addition to existing resources from the networking
-	group and other technologies such as QuickAssist.
-	Much of the work has been focused on security and
-	OS mitigations but we're also focusing on other
-	areas such as power management and persistent
-	memory. In May and again in July we traveled to
-	Intel's Hillsboro campus to meet with management
-	and engineers from OTC and the networking team. We
-	presented an overview of the project and
-	Foundation and also discussed key markets and
-	vendors who use FreeBSD in their products or
-	services and their future requirements.</p>
-
-      <p>Intel was also interested in learning more about who
-	contributes to FreeBSD. Along those lines we've
-	done some work with OTC to create scripts and
-	organizational mappings to answer that question.
-	Note that we do need developers
-	to help us update and maintain the organizational
-	mappings as we understand that developers do tend
-	to move around and contractors are often working
-	on behalf of multiple organizations.</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>Our work is 100% funded by your donations. As of September
-	30, we raised $328,482. Our 2018 fundraising goal
-	is $1,250,000 and we are continuing to work hard to
-	meet and exceed this goal! Please consider making
-	a donation to help us continue and increase our
-	support for FreeBSD: <a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">https://www.FreeBSDfoundation.org/donate/</a>.</p>
-
-      <p>We also have a new Partnership Program, to provide more
-	benefits for our larger commercial donors. Find
-	out more information at <a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>
-	and share with your companies!</p>
-
-      <p>OS Improvements</p>
-
-      <p>The Foundation improves the FreeBSD operating system by
-	employing technical staff to maintain and improve
-	critical kernel subsystems, add features and
-	functionality, and fix problems. This also
-	includes funding separate project grants like the
-	arm64 port, porting the blacklistd access control
-	daemon, and the integration of VIMAGE support, to
-	make sure that FreeBSD remains a viable solution
-	for research, education, computing, products and
-	more.</p>
-
-      <p>We kicked off or continued the following projects last
-	quarter:</p>
-
-      <ul>
-	<li>OpenZFS RAID-Z Expansion project</li>
-
-	<li>Headless mode out-of-the-box for embedded ARM boards like
-	the Beaglebone Black</li>
-
-	<li>Performance and scalability improvements</li>
-      </ul>
-
-      <p>
-	Having software developers on staff has allowed us to jump
-	in and work directly on projects to improve
-	FreeBSD such as:</p>
-
-      <ul>
-	<li>ZFS improvements</li>
-
-	<li>New Intel server support</li>
-
-	<li>kqueue(2) updates</li>
-
-	<li>64-bit inode support</li>
-
-	<li>Stack guard</li>
-
-	<li>Kernel Undefined Behavior Sanitizer</li>
-
-	<li>Toolchain projects</li>
-
-	<li>i915 driver investigation</li>
-
-	<li>NVDIMM support in acpiconf(8)</li>
-
-	<li>Continuous integration dashboard (web page and physical
-	hardware)</li>
-
-	<li>FAT filesystem support in makefs(8)</li>
-      </ul>
-
-      <p>
-	Continuous Integration and Quality Assurance</p>
-
-      <p>The Foundation provides a full-time staff member who is
-	working on improving our automated testing,
-	continuous integration, and overall quality
-	assurance efforts.</p>
-
-      <p>Foundation employee Li-Wen Hsu set up new CI servers to
-	speed up amd64 build and test jobs, to reduce the
-	latency between changes being committed and
-	results being available. Li-Wen also set up a
-	staging / development server in order to test
-	changes to the CI system itself without affecting
-	production results. We have also started a small
-	hardware test lab, currently connected to the
-	staging server, that tests the full boot and test
-	cycle on physical hardware. In the near future
-	additional hardware devices will be added, and
-	this will migrate to the production CI server.</p>
-
-      <p>Release Engineering</p>
-
-      <p>The Foundation provides a full-time staff member to lead
-	the release engineering efforts. This has provided
-	timely and reliable releases over the last five
-	years.</p>
-
-      <p>Foundation employee Glen Barber continued leading the
-	efforts on the upcoming 12.0-RELEASE. For details
-	surrounding the work involved and progress thus
-	far on 12.0-RELEASE, please see the FreeBSD
-	Release Engineering Team section of this quarterly
-	status report.</p>
-
-      <p>Supporting FreeBSD Infrastructure</p>
-
-      <p>The Foundation provides hardware and support to improve
-	the FreeBSD infrastructure. Last quarter, we
-	continued supporting FreeBSD hardware located
-	around the world.</p>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating
-	for the Project. This includes promoting work
-	being done by others with FreeBSD; producing
-	advocacy literature to teach people about FreeBSD
-	and help make the path to starting using FreeBSD
-	or contributing to the Project easier; and
-	attending and getting other FreeBSD contributors
-	to volunteer to run FreeBSD events, staff FreeBSD
-	tables, and give FreeBSD presentations.</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events,
-	and summits around the globe. These events can be
-	BSD-related, open source, or technology events
-	geared towards underrepresented groups. We support
-	the FreeBSD-focused events to help provide a venue
-	for sharing knowledge, to work together on
-	projects, and to facilitate collaboration between
-	developers and commercial users. This all helps
-	provide a healthy ecosystem. We support the
-	non-FreeBSD events to promote and raise awareness
-	of FreeBSD, to increase the use of FreeBSD in
-	different applications, and to recruit more
-	contributors to the Project.</p>
-
-      <p>Check out some of the advocacy and education work we did
-	last quarter:</p>
-
-      <ul>
-	<li>Organized and ran the Essen FreeBSD Hackathon in Essen,
-	Germany</li>
-
-	<li>Participated in the FreeBSD Developer Summit BSDCam, in
-	Cambridge, England</li>
-
-	<li>Represented FreeBSD at the ARM Partner Meeting</li>
-
-	<li>Presented and taught about FreeBSD at SdNOG 5 in Khartoum,
-	Sudan</li>
-
-	<li>Exhibited and gave a talk at OSCON 2018 in Portland, OR</li>
-
-	<li>Exhibited at the 2018 Grace Hopper Celebration and
-	sponsored as a Silver Non-Profit Sponsor</li>
-
-	<li>Exhibited at COCON 2018 in Taipei, Taiwan</li>
-
-	<li>Sponsored and gave presentations and tutorials at
-	EuroBSDCon in Bucharest, Romania</li>
-
-	<li>Organized and ran the Bucharest FreeBSD Developer Summit</li>
-
-	<li>Sponsored the 2018 USENIX Security Symposium in Baltimore,
-	MD as an Industry Partner</li>
-
-	<li>Provided FreeBSD advocacy material</li>
-
-	<li>Sponsored the 2018 USENIX Annual Technical Conference in
-	Boston, MA as an Industry Partner</li>
-
-	<li>Sponsored the OpenZFS Developer Summit as a Silver Sponsor</li>
-
-	<li>Presented and taught about FreeBSD at SANOG32 in Dhaka,
-	Bangladesh</li>
-
-	<li>Sponsored the SNIA Storage Developer Conference 2018 as an
-	Association Partner</li>
-
-	<li>Provided 11 travel grants to FreeBSD contributors to
-	attend many of the above events.</li>
-      </ul>
-
-      <p>
-	We continued producing FreeBSD advocacy material to help
-	people promote FreeBSD around the world.</p>
-
-      <p>Read more about our conference adventures in the
-	conference recaps and trip reports in our monthly
-	newsletters: <a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">https://www.freebsdfoundation.org/news-and-events/newsletter/</a></p>
-
-      <p>We help educate the world about FreeBSD by publishing the
-	professionally produced FreeBSD Journal. Last
-	quarter we published the July/August issue that
-	you can find at <a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>.</p>
-
-      <p>You can find out more about events we attended and
-	upcoming events at <a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">https://www.FreeBSDfoundation.org/news-and-events/</a>.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them. We also provide
-	legal support for the core team to investigate
-	questions that arise.</p>
-
-      <p>Go to <a href="http://www.FreeBSDfoundation.org" shape="rect">http://www.FreeBSDfoundation.org</a>
-	to find out how we support FreeBSD and how we can
-	help you!</p>
-
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="32-bit-compatibility-and-other-ABI-cleanups" href="#32-bit-compatibility-and-other-ABI-cleanups" id="32-bit-compatibility-and-other-ABI-cleanups">32-bit compatibility and other ABI cleanups</a></h2><p>
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>As part of maintaining an external ABI (application binary
-	interface)
-	compatibility layer, I've been improving FreeBSD
-	infrastructure,
-	primarily the 32-bit compatibility layer. One of FreeBSD's
-	strengths is
-	that we can easily support many ABIs. This includes
-	support for a.out
-	format executables (vs the standard ELF), support for i386
-	on amd64, the
-	Linux emulation layer, etc.</p>
-
-      <p>This infrastructure has existed for decades and not every
-	design
-	decision has stood the test of time. Support has also been
-	incomplete
-	in a number of areas (e.g. network management under 32-bit
-	emulation).</p>
-
-      <p>Committed improvements include:</p>
-
-      <ul>
-	<li>Improved <tt>ioctl</tt> and <tt>sysctl</tt> support to
-	allow <tt>ifconfig</tt> and
-	<tt>netstat</tt> to work in 32-bit compat mode.</li>
-	<li>Migration from a model of translating <tt>ioctl</tt>
-	commands and data
-	structures at the kernel boundary to translating where the
-	commands
-	are processed. This is a correctness improvement (`ioctl`
-	commands
-	do not have meaning outside the specific file descriptor
-	in question)
-	and improves code reusability (my out-of-tree work will
-	soon include
-	a 64-bit compatibility layer.)</li>
-	<li>Simplifications of the generic ELF process execution path
-	by Ed
-	Maste, John Baldwin, and myself. A number of
-	simplifications including
-	minor speedups have been committed.</li>
-      </ul>
-
-      <p>
-	Portions of this work were developed by SRI International
-	and the
-	University of Cambridge Computer Laboratory (Department of
-	Computer
-	Science and Technology) under DARPA/AFRL contract
-	FA8750-10-C-0237
-	("CTSRD"), as part of the DARPA CRASH research programme
-	and under DARPA
-	contract HR0011-18-C-0016 ("ECATS"), as part of the DARPA
-	SSITH research
-	programme.</p>
-
-      <p>Work in progress includes cleanups to the APIs used by the
-	kernel when
-	creating processes and continued <tt>ioctl</tt>
-	improvements. Work is also
-	underway to generate the 32-bit system call list from the
-	"default"
-	list.</p>
-
-      <p>The remaining <tt>ioctl</tt> commands handled in
-	<a href="https://svnweb.FreeBSD.org/base/head/sys/compat/freebsd32/freebsd32_ioctl.c?view=log" shape="rect">sys/compat/freebsd32/freebsd32_ioctl.c</a>
-	need to be migrated to the point of implementation. Help
-	with the latter
-	would be appreciated.</p>
-
-    <hr /><h2><a name="4G/4G-address-space-split-for-i386" href="#4G/4G-address-space-split-for-i386" id="4G/4G-address-space-split-for-i386">4G/4G address space split for i386</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Most 32-bit FreeBSD architectures, including i386, started
-	to suffer
-	from the rapid growth of the size of software during the
-	past decade.
-	When a 32-bit address space is enough space for a given
-	task, 32-bit
-	mode still has an intrinsic advantage over 64-bit mode,
-	due to less
-	memory traffic and more economical use of caches. It has
-	grown
-	harder to provide the self-hosting i386 system build due
-	to the
-	increase in size of the build tools.</p>
-
-      <p>The FreeBSD i386 kernel, prior to the 12.0-RELEASE
-	version, split
-	the 4GB address space of the platform into 3GB (minus 4MB)
-	accessible
-	to userspace accesses and 1GB for kernel accesses.
-	Neither kernel nor userspace could access a full 4GB
-	address space.
-	Programs that require very large virtual address spaces,
-	such as
-	clang when compiling or lld when linking, could run out of
-	address
-	space: 3GB of address space was insufficient for their
-	operation.
-	The kernel also had trouble fitting into the traditional
-	1GB
-	limitation of address space with the modern sizing for
-	network
-	buffers, ZFS and other KVA-hungry in-kernel subsystems.</p>
-
-      <p>In FreeBSD 12, the i386 architecture has been changed to
-	provide
-	dedicated separate address spaces for userspace and
-	kernel, giving
-	each mode full access to 4GB (minus 8MB) of usable address
-	space.
-	The userspace on the i386 architecture now has access to
-	the same
-	amount of address space as the compat32 subsystem in the
-	amd64
-	architecture kernel. The increase in kernel address space
-	enables
-	further growth and maintainability of the i386
-	architecture.</p>
-
-      <p>The split 4GB/4GB user/kernel implementation uses two page
-	directory
-	entries (PDEs) shared between modes: one for mapping the
-	page table,
-	another for the mode switching trampoline and other
-	required system
-	tables. The required system tables, which must always be
-	mapped,
-	regardless of kernel or user mode, includes such things as
-	the
-	GDT/IDT/TSS entries. Significant changes were made to the
-	locore
-	code. The page table creation portion of the code was
-	completely
-	rewritten from assembly to C, improving readability and
-	maintainability
-	of the code.</p>
-
-      <p>Because the user address space is no longer shared with
-	the kernel,
-	the copyout(9) functions were rewritten to make a
-	transient mapping
-	of userspace pages for the duration of any needed
-	accesses. The initial
-	implementation used the vm_fault_quick_hold_pages()
-	framework, but
-	this was later optimized by temporarily switching to user
-	mode
-	mappings from a trampoline, and then using hand-written
-	assembler
-	routines to perform a faster small block copy operation.</p>
-
-      <p>Future plans for the ongoing maintenance of i386 include
-	making the i386 pmap
-	capable of runtime selection of the PAE or non-PAE page
-	table format
-	and supporting NX (no execute) mappings for regular i386
-	kernel.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="ACPI-NVDIMM-driver" href="#ACPI-NVDIMM-driver" id="ACPI-NVDIMM-driver">ACPI NVDIMM driver</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>NVDIMM is a technology which provides non-volatile memory
-	with
-	access characteristics similar to regular DRAM, which is
-	the
-	technology that implements the normal memory address space
-	of a host.
-	There are ACPI and UEFI specifications that define
-	platform independent
-	ways to detect and enumerate the presence of NVDIMMs.
-	These
-	specifications allow the retrieval of most of the data
-	needed to
-	allow proper application use of the NVDIMM storage.</p>
-
-      <p>A new FreeBSD driver parses the ACPI NFIT table which
-	lists NVDIMMs,
-	their operational characteristics, and the physical
-	address space
-	where the NVDIMM memory is accessible. The driver presents
-	each
-	address region as two devices: One device allows userspace
-	to
-	open(2) a devfs node, which can be read/written/mapped
-	from the
-	application. This mapping is zero-copy. The second device
-	is a
-	geom disk(9), which makes it possible to use NVDIMM for
-	the backing
-	storage for a normal FreeBSD filesystem, such as UFS, ZFS,
-	or msdosfs.
-	Note that buffer cache/mapping of files from a traditional
-	filesystem
-	created over NVDIMM causes an unneeded double-buffering.</p>
-
-      <p>Empirically, on typical modern hardware, NVDIMM regions
-	are located
-	far from the regular DRAM backed memory in the address
-	space, and
-	have attributes that are not compatible with regular DRAM
-	memory.
-	This makes it unfeasible to extend the kernel's direct map
-	to provide
-	the kernel mappings for the NVDIMM regions.
-	A new pmap KPI was designed, pmap_large_map(9),
-	which allows efficient mapping of very large physical
-	regions into
-	the KVA. The new code has some optimizations to the cache
-	flushing
-	operations over the mapped regions, which is needed to
-	efficiently
-	support bio flushes from a filesystems using the NVDIMM
-	storage.
-	The NVDIMM driver is the first user of the new KPI,
-	but the new KPI might also be useful for the NTB driver.</p>
-
-      <p>
-	TODO:</p>
-
-      <ul>
-	<li>Intel is currently working on extending the driver to
-	support
-	UEFI namespaces.</li>
-
-	<li>A DAX-capable filesystem is needed, which solves the issue
-	of
-	double-buffering. Our tmpfs already provides VM facilities
-	which
-	allows it to avoid double-buffering for mmap, which can be
-	reused
-	there.</li>
-      </ul>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Boot-Loader" href="#Boot-Loader" id="Boot-Loader">Boot Loader</a></h2><p>
-	Contact: Warner Losh &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Kyle Evans &lt;<a href="mailto:kevans@FreeBSD.org">kevans@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Toomas Soome &lt;<a href="mailto:tsoome@Freebsd.org">tsoome@Freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD boot loader lives in src/stand (prior releases
-	had it in
-	sys/boot and lib/libstand). It covers all the code that
-	the project
-	provides that interacts with the hardware before the
-	kernel starts.</p>
-
-      <p>The LUA interpreter added earlier in 2018 was made default
-	in 2018Q3.
-	Due to undiagnosed booting issues, the LUA interpreter has
-	been
-	disabled on sparc64 and all powerpc. The LUA interpreter
-	is scheduled
-	to replace the FORTH interpreter entirely in FreeBSD 13,
-	although the
-	FORTH interpreter will remain available as a build option
-	in FreeBSD
-	12. The plans are not to remove the FORTH loader for about
-	a year
-	after 12.0 release, or approximately January 2020.
-	Platforms not
-	currently working with the LUA interpreter
-	have until that date to resolve the issues.</p>
-
-      <p>At this point, the LUA scripts implement everything that
-	the FORTH scripts
-	did. Where there was ambiguity in the spec, or where the
-	FORTH scripts
-	were more forgiving than was strictly documented, every
-	effort has
-	been made to improve the documentation and follow the old
-	FORTH
-	behavior, or document the new behavior where the old
-	behavior was
-	clearly a bug.</p>
-
-      <p>It's anticipated that no further changes to the FORTH
-	loader or the
-	FORTH scripts will happen. They are quite mature and
-	bullet proof at
-	this point and it's unlikely that an undiscovered bug will
-	need to be
-	fixed before retirement.</p>
-
-      <p>Other work in progress includes Toomas Soome's port to
-	OpenIndiana. In
-	addition to porting, he's enhanced the code in a number of
-	ways (both
-	in the block layer, and UEFI). Many of his improvements
-	have been
-	committed to FreeBSD, though a few remain and hopefully
-	will be
-	entering the tree soon after the freeze lifts.</p>
-
-      <p>UEFI booting has been greatly enhanced. There are still
-	some
-	machines that have issues with the default BootXXXX
-	variables or
-	something else in the environment that are being
-	investigated. We hope
-	to understand the problems well enough to provide a fix
-	for FreeBSD
-	12.0.</p>
-
-      <p>Ian Lepore has reworked the GELI support so that it is
-	architecture independent and can be
-	used on any architecture we support.</p>
-
-      <p>There are also efforts underway to support booting signed
-	images, improved
-	crypto booting options, and implement Multiboot 2.0
-	support.</p>
-
-    <hr /><h2><a name="Building-FreeBSD-on-non-FreeBSD-hosts" href="#Building-FreeBSD-on-non-FreeBSD-hosts" id="Building-FreeBSD-on-non-FreeBSD-hosts">Building FreeBSD on non-FreeBSD hosts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/BuildingOnNonFreeBSD" title="https://wiki.FreeBSD.org/BuildingOnNonFreeBSD">Wiki</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/BuildingOnNonFreeBSD" title="Wiki">https://wiki.FreeBSD.org/BuildingOnNonFreeBSD</a></td></tr><tr><td><a href="https://github.com/arichardson/freebsd/tree/crossbuild-aug2018" title="https://github.com/arichardson/freebsd/tree/crossbuild-aug2018">GitHub project</a></td><td>
-	    URL: <a href="https://github.com/arichardson/freebsd/tree/crossbuild-aug2018" title="GitHub project">https://github.com/arichardson/freebsd/tree/crossbuild-aug2018</a></td></tr></table><p>
-	Contact: Alex Richardson &lt;<a href="mailto:arichardson@FreeBSD.org">arichardson@FreeBSD.org</a>&gt;
-	</p>
-      <p>Currently FreeBSD can only be built on a FreeBSD host.
-	However, most free
-	CI tools only allow building on Linux or macOS and
-	therefore can not be used
-	for building the FreeBSD base system. It is sometimes
-	useful to
-	cross-build FreeBSD for a remote machine or an emulator
-	even if the build
-	machine is not running FreeBSD.
-	The goal of this project is to allow building FreeBSD on
-	both Linux and macOS hosts
-	and in the future it may be extended to allow compiling on
-	a Windows host.
-	This work originates from the CHERI project and was
-	motivated by multiple cases of
-	people wanting to try out CheriBSD but not being able to
-	compile it since they did
-	not have a FreeBSD system available for compiling.
-	Once completed this project will also allow developers to
-	contribute to FreeBSD
-	even if they don't have access to a FreeBSD build system.</p>
-
-      <p>The current set of patches for this project can be found
-	on
-	<a href="https://github.com/arichardson/freebsd/tree/crossbuild-aug2018" shape="rect">GitHub</a>.
-	With the current prototype it is possible to compile both
-	world and kernel for
-	architectures that use the clang compiler and for MIPS64,
-	which uses gcc. However, some options such as
-	LOCALES are
-	not supported yet and require further changes before the
-	bootstrap tools can be built
-	on Linux/macOS.</p>
-
-      <p>Some changes required for building on non-FreeBSD have
-	already been merged to
-	HEAD but there are still a rather large number of changes
-	that need review.</p>
-
-      <p>If you are interested in getting this into HEAD and would
-	like to help, please
-	try the current prototype and report any issues to
-	arichardson@FreeBSD.org.
-	If you can help with reviewing the changes please contact
-	arichardson@FreeBSD.org
-	to be added to any pending Phabricator reviews.</p>
-
-    <hr /><h2><a name="Device-Mode-USB" href="#Device-Mode-USB" id="Device-Mode-USB">Device Mode USB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/usb-device-mode.html" title="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/usb-device-mode.html">Handbook chapter</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/usb-device-mode.html" title="Handbook chapter">https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/usb-device-mode.html</a></td></tr></table><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>Many embedded boards include hardware which supports
-	device
-	side USB - the ability for the board to present itself to
-	another
-	system as a USB drive, network adapter, or a virtual
-	serial port.
-	The FreeBSD USB stack has supported this functionality for
-	quite some
-	time, but it has not been used to its fullest extent.</p>
-
-      <p>The goal of this project was to fix that - to document the
-	functionality, possibly fix some bugs, and to make it easy
-	to use, automating it as much as possible.</p>
-
-      <p>Starting with FreeBSD 12.0, this functionality is enabled
-	out of the box. This means you can connect your BeagleBone
-	Black's (using its USB client socket) or a Raspberry Pi 0
-	(using the On-The-Go (OTG) port) to your laptop, and
-	you'll get a virtual
-	USB serial port, which serves as a system console, with
-	getty(8)
-	waiting for you to log in. This means you no longer need
-	to
-	look for a keyboard and a screen, or mess with the console
-	cables just to configure your system. You can also switch
-	it to provide network interface, or present itself as a
-	USB
-	drive - it's all documented in the FreeBSD Handbook.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Micha&#322; Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	</p>
-      <p>ENA (Elastic Network Adapter) is the smart NIC which is
-	used in the virtualised
-	environment of Amazon Web Services (AWS). It supports
-	multiple queues and can handle up to 25 Gb/s,
-	depending on the instance type on which it is
-	used.</p>
-
-      <p>Since last report, ENA versions v0.8.0 and v0.8.1 have
-	been released, which introduced
-	many bug fixes, new features, optimization, stability and
-	error recovery
-	improvements. The last is especially important on the AWS,
-	where the instances
-	have to be reliable as they may be running very sensitive
-	functions and the
-	down time of the VM should be reduced to minimum.</p>
-
-      <p>The v0.8.0 and v0.8.1 release patches included:</p>
-
-      <ul>
-	<li>Upgrade of the HAL to version v1.1.4.3</li>
-
-	<li>Improvement to the reset routine - the driver is now
-	triggering reset from
-	more fault points and is passing the reset reason to the
-	device, which can
-	perform the reset adequately to the encountered error.</li>
-
-	<li>Device statistics (like global Tx and Rx counters) are no
-	longer read directly from the device.
-	The only exception is Rx drops, which are still read using
-	the AENQ
-	descriptor.</li>
-
-	<li>The RX Out Of Order completion feature was added, which
-	enabled to cleanup the
-	RX descriptors out of order by keeping trace of all free
-	descriptors.</li>
-
-	<li>RX ring is now being monitored, to prevent the ring from
-	stalling.</li>
-
-	<li>Error handling paths were reworked and fixed.</li>
-
-	<li>Driver was covered with branch prediction statements, to
-	make the most
-	of this CPU feature in the hot paths.</li>
-
-	<li>Fix handling of the DF flag in the IP packets.</li>
-
-	<li>Add dynamic logging and reduce number of messages being
-	printed by the driver.</li>
-
-	<li>MTU configuration now is being verified using the device
-	capabilities instead
-	of a constant value.</li>
-
-	<li>Do not pass packet header length hint to the device,
-	because for the chained
-	mbufs it may be problematic to determine header length, if
-	the header is split
-	into multiple segments.</li>
-      </ul>
-
-    <p>This project was sponsored by Amazon.com Inc..</p><hr /><h2><a name="FreeBSD-Graphics-Team" href="#FreeBSD-Graphics-Team" id="FreeBSD-Graphics-Team">FreeBSD Graphics Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop" title="https://github.com/FreeBSDDesktop">Project GitHub page</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop" title="Project GitHub page">https://github.com/FreeBSDDesktop</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Niclas Zeising &lt;<a href="mailto:zeising@FreeBSD.org">zeising@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD X11/Graphics team is responsible for the lower
-	levels of the FreeBSD
-	graphics stack. This includes graphics drivers, graphics
-	libraries such as the
-	MESA OpenGL implementation, the X.org xserver with related
-	libraries and
-	applications, and Wayland with related libraries and
-	applications.</p>
-
-      <p>There have been a lot of changes since the last report.
-	The most important one
-	is the change of driver distribution and updates. On
-	FreeBSD 11.2 and later
-	modern graphics drivers using the Linux KPI subsystem are
-	found in ports. These
-	give much improved support for Intel and AMD graphics
-	hardware, however, they
-	are currently only available for amd64.</p>
-
-      <p>The legacy drivers available in the FreeBSD base system
-	are also available in
-	the ports tree, since they cause issues with the new
-	drivers. They will remain
-	in tree for 11.2 and 12, but work is on-going to have them
-	removed for 13,
-	except for arm.</p>
-
-      <p>The easiest way to install the new drivers is to install
-	graphics/drm-kmod which
-	will install the correct driver depending on your
-	architecture and FreeBSD
-	version.</p>
-
-      <p>There have been changes to the ports as well. Most notably
-	is the changed
-	handling of OpenGL dependencies, which has moved to USES
-	instead of being
-	handled directly in bsd.port.mk. Other big infrastructure
-	changes is the move
-	from individual \*proto packages to xorgproto, and turning
-	that into a build
-	time dependency. Many thanks to portmgr for help with
-	exp-runs for these
-	changes.</p>
-
-      <p>There have been updates to applications and libraries as
-	needed.</p>
-
-      <p>On the project management side, there is ongoing work to
-	set up a more efficient
-	way of working, including bi-weekly conference calls to
-	discuss the current
-	works in progress. Notes from these conference calls will
-	be posted on the
-	mailing list.</p>
-
-      <p>Looking forward, the current major work in progress is to
-	update the graphics
-	driver to be on par with Linux 4.17. The code is merged,
-	but patching and bug
-	fixing is ongoing.</p>
-
-      <p>There is also work to port the VMware guest graphics
-	driver, vmwgfx, to FreeBSD
-	and to the Linux KPI, to get better graphics support in
-	VMware.</p>
-
-      <p>Lastly, on the driver side is to get the new graphics
-	drivers to work on i386 as
-	well. Experimental support for this exists in the code
-	repository, but is not
-	yet merged to the FreeBSD ports tree.</p>
-
-      <p>In userland, the biggest things happening is the update of
-	the input stack,
-	including libinput and supporting libraries.</p>
-
-      <p>Work is also ongoing on updating MESA libraries.</p>
-
-      <p>On the project management side, the most important tasks
-	is to continue to work
-	on the team, and how we work internally.</p>
-
-      <p>We are also working on setting up a list of requirements
-	for testing, so that we
-	can be reasonably assured that updates won't cause
-	regressions.</p>
-
-      <p>People who are interested in helping out can find us on
-	the x11@FreeBSD.org
-	mailing list, or on our Gitter chat: <a href="https://gitter.im/FreeBSDDesktop/Lobby" shape="rect">https://gitter.im/FreeBSDDesktop/Lobby</a>.
-	We
-	are also available in #freebsd-xorg on EFNet.</p>
-
-      <p>We also have a team area on GitHub where our work
-	repositories can be found:
-	<a href="https://github.com/FreeBSDDesktop" shape="rect">https://github.com/FreeBSDDesktop</a></p>
-
-    <hr /><h2><a name="FreeBSD/DTrace" href="#FreeBSD/DTrace" id="FreeBSD/DTrace">FreeBSD/DTrace</a></h2><p>
-	Contact: George Neville-Neil &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Domagoj Stolfa &lt;<a href="mailto:domagoj.stolfa@cl.cam.ac.uk">domagoj.stolfa@cl.cam.ac.uk</a>&gt;
-	</p>
-      <p>DTrace is a whole-system debugging tool in FreeBSD and is
-	one of the
-	actively supported projects during the past year.</p>
-
-      <p>A research prototype of a distributed version of DTrace
-	and a version
-	of DTrace that can trace bhyve virtual machines from the
-	host FreeBSD
-	system are currently under development at the University
-	of Cambridge
-	as a part of the CADETS project. Recent developments
-	include the
-	creation of dlog, an in-kernel DTrace consumer which is
-	able to
-	publish to Kafka, and improvements to early boot and
-	shutdown tracing.
-	On the virtualisation front,
-	improvements were made in the ability to dereference and
-	follow
-	pointers inside guests from the host in the probe context
-	by
-	implementing a nested page table walk inside DTrace for
-	Intel
-	architectures. The CADETS project has started formalizing
-	DTrace in HOL4 which enables automated test generation,
-	high assurance
-	of DTrace implementations in terms of adherence to the
-	specification
-	and exploration of all allowable behaviors for a given D
-	script. Currently, the formal model contains most of DIF
-	instructions
-	and a code generator for them, providing the ability to
-	run DIF
-	programs specified using the model using FreeBSD's DTrace
-	implementation.</p>
-
-      <p>As a result of all of this, a number of changes were
-	upstreamed to the
-	FreeBSD auditing subsystem and new variables such as
-	<tt>jid</tt> and
-	<tt>jailname</tt> were added to DTrace which can be
-	accessed from D scripts.</p>
-
-      <p>OpenDTrace Specification 1.0 has been published which
-	covers the
-	internal workings of DTrace in general, and its adaptation
-	to various
-	operating systems in particular. This work was sponsored
-	by
-	AFRL/DARPA through the CADETS project.</p>
-
-      <p>Ruslan Bukin (br@) has added C-compressed ISA extension
-	support to the
-	RISC-V FBT provider as a part of the ECATS project.</p>
-
-      <p>Mark Johnston (markj@) has done some work to fix
-	interactions between
-	FBT and ifuncs. ifuncs are a toolchain feature which allow
-	programmers
-	to select a function's implementation at boot-time, rather
-	than at
-	compile-time. For instance, on amd64, memcpy() is an ifunc
-	and may be
-	implemented by either memcpy_erms() or memcpy_std(). FBT
-	created
-	probes for the implementation functions, but we needed
-	some extra
-	support to ensure that fbt::memcpy:entry continues to work
-	as
-	expected. Similar work is needed for the PID provider, but
-	is still
-	pending.</p>
-
-      <p>Microsoft showed a <a href="https://youtu.be/tG8R5SQGPck?t=891" shape="rect">working
-	demo of DTrace</a>,
-	which was ported from FreeBSD.</p>
-
-      <p>Added to FreeBSD base in 11.2, dwatch is a new DTrace
-	tool, developed
-	by Devin Teske (dteske@), for automating complex queries
-	for data and
-	surgically tapping the kernel. In base there are 85
-	profiles for
-	interpreting domain-specific data with another 17
-	available from ports
-	making a total of over 100 different pipelines from which
-	you can
-	extract data in multiple formats. dwatch also simplifies
-	observation
-	of over 100,000 probe points available in FreeBSD, making
-	it easy to
-	find any process, thread, or jail triggering any probe.
-	On top of all
-	that, dwatch profiles can leverage higher-level languages
-	such as
-	python, perl, sh, and many more.</p>
-
-    <hr /><h2><a name="ifuncs" href="#ifuncs" id="ifuncs">ifuncs</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mateusz Guzik &lt;<a href="mailto:mjg@FreeBSD.org">mjg@FreeBSD.org</a>&gt;
-	</p>
-      <p>An ifunc is a special construct in an ELF object, which
-	allows for
-	the selection of the implementation for the given symbol
-	at runtime,
-	when the ELF module gets the final relocations applied.
-	The selection
-	of which code to use is governed by the small piece of
-	user provided
-	code, attached to the symbol, the so called resolver
-	function.
-	Ifuncs provide a convenient way to select between
-	different
-	machine-specific implementations of the parts of the code,
-	without
-	the ugliness and unsafety of the alternative approach,
-	which is
-	runtime patching.</p>
-
-      <p>Ifuncs require support both from the static linker ld(1),
-	and from the
-	runtime linker for the corresponding execution
-	environment. On
-	FreeBSD, with the switch from the ancient GPLv2 licensed
-	BFD-based
-	ld(1) to either in-tree LLD or external modern BFD ld, the
-	use of
-	ifuncs become possible. Runtime linkers for ifunc support
-	exists for
-	the following environments:</p>
-
-      <ul>
-	<li>i386, amd64, and arm64 kernels</li>
-
-	<li>usermode dynamic linker ld-elf.so.1 on i386 and amd64</li>
-
-	<li>static binaries startup code for i386 and amd64</li>
-      </ul>
-
-      <p>
-	The use of ifuncs were previously applied for optimization
-	of the
-	following areas of the amd64 kernel:</p>
-
-      <ul>
-	<li>context switching code, instead of huge number of runtime
-	checks
-	(PTI vs non-PTI, PCID or not, is INVPCID instruction
-	supported for
-	PCID) now uses set of mode-specific routines, see
-	pmap_activate_sw(). Besides removing checks at runtime, it
-	also
-	makes the code much more cleanly structured and readable.</li>
-
-	<li>TLB and cache flush implementation.</li>
-
-	<li>memcpy/memmove, copyin/copyout variants selection for ERMS
-	and SMAP.</li>
-
-	<li>FPU state save and restore, depending on the support for
-	AVX or not,
-	this is also used on i386.</li>
-      </ul>
-
-      <p>
-	For amd64 userspace, we currently use ifunc for
-	optimization of the
-	architecture dependent TLS base set and get functions.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Intel-Work-on-Core-Enabling-and-Security" href="#Intel-Work-on-Core-Enabling-and-Security" id="Intel-Work-on-Core-Enabling-and-Security">Intel Work on Core Enabling and Security</a></h2><p>
-	Contact: Ben Widawsky &lt;<a href="mailto:bwidawsk@FreeBSD.org">bwidawsk@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new team has been formed within Intel to help with side
-	channel security
-	mitigations as well as core enabling. They are evaluating
-	work from all areas
-	except networking. The team is currently focusing on two
-	areas:</p>
-
-      <ol><li>Power Management improvements</li>
-	<li>NVDIMM namespace support</li></ol>
-
-      <p>The ultimate goal of the power management work is to get
-	runtime power
-	management to hit "opportunistic idle". What this means is
-	when devices are
-	idle, the OS will power them down, and when everything
-	goes idle certain SoCs
-	will allow you to hit very low power states across the
-	platform. FreeBSD
-	currently doesn't have any notion of runtime power
-	management, and many devices
-	don't properly implement suspend and resume. In addition,
-	some preliminary work
-	is in process as it was thought to help when eventually
-	enabling opportunistic
-	idle. That preliminary work has been happening and is now
-	up for review:</p>
-
-      <ul>
-	<li><a href="https://reviews.FreeBSD.org/D17675" shape="rect">https://reviews.FreeBSD.org/D17675</a></li>
-
-	<li><a href="https://reviews.FreeBSD.org/D17676" shape="rect">https://reviews.FreeBSD.org/D17676</a></li>
-      </ul>
-
-      <p>
-	NVDIMM namespace support has also been put up for review.
-	ACPI spec defines
-	namespaces as a way of partitioning the device into
-	separate labels. The current
-	work will integrate with geom(4). How these are used is
-	application dependent.
-	This work is up for review as well: <a href="https://reviews.FreeBSD.org/D17619" shape="rect">https://reviews.FreeBSD.org/D17619</a></p>
-
-      <p>The team has additionally taken on smaller tasks like
-	porting turbostat(8),
-	working on git svn init scripts, some small modifications
-	to acpi tooling, and
-	an effort to create a port PMDK.</p>
-
-    <hr /><h2><a name="Large-scale-package-building" href="#Large-scale-package-building" id="Large-scale-package-building">Large scale package building</a></h2><p>
-	Contact: Mateusz Guzik &lt;<a href="mailto:mjg@FreeBSD.org">mjg@FreeBSD.org</a>&gt;
-	</p>
-      <p>Building packages on a 128-thread machine with poudriere
-	exhibits some
-	bottlenecks.</p>
-
-      <p>See the October FreeBSD Foundation Newsletter for a short
-	write-up:
-	<a href="https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-october-2018/" shape="rect">https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-october-2018/</a></p>
-
-      <p>One encountered problem stems from process handling.</p>
-
-      <p>The standard process life cycle on UNIX-like systems looks
-	like this:</p>
-
-      <ul>
-	<li>a process is created with fork(2)</li>
-
-	<li>it can do regular work or execve(2) a new binary</li>
-
-	<li>it exits, becoming a zombie</li>
-
-	<li>the parent collects the exit code and removes the zombie</li>
-      </ul>
-
-      <p>
-	There are other variations (e.g. vfork(2) can be used
-	instead of
-	fork).</p>
-
-      <p>When you type 'ls' into your shell, it will typically
-	vfork a new process
-	which will then execve /bin/ls.</p>
-
-      <p>All this is guarded with several global kernel locks, but
-	the granularity
-	can be significantly improved.</p>
-
-      <p>A different problem stems from pipes.</p>
-
-      <p>Pipes are used all the time, e.g. "du -s | sort -n"
-	creates a pipe whose
-	one endpoint is standard output for du and another is
-	standard input for sort.</p>
-
-      <p>By default the pipe can hold up to 16KB before it gets
-	filled up.</p>
-
-      <p>The kernel dedicates part of its virtual address space to
-	hold pipe buffers
-	and allocates/deallocates physical pages as pipes get
-	created/destroyed.
-	This induces TLB invalidation requests to other CPUs,
-	which causes an
-	unnecessary slowdown.</p>
-
-      <p>An easy way out is to cache a certain number of buffers.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="LLVM-7.0---Sanitizers-support-improvements-/-Static-code-analysis" href="#LLVM-7.0---Sanitizers-support-improvements-/-Static-code-analysis" id="LLVM-7.0---Sanitizers-support-improvements-/-Static-code-analysis">LLVM 7.0 - Sanitizers support improvements / Static code analysis</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://releases.llvm.org/7.0.0/docs/ReleaseNotes.html" title="http://releases.llvm.org/7.0.0/docs/ReleaseNotes.html">Release notes</a></td><td>
-	    URL: <a href="http://releases.llvm.org/7.0.0/docs/ReleaseNotes.html" title="Release notes">http://releases.llvm.org/7.0.0/docs/ReleaseNotes.html</a></td></tr></table><p>
-	Contact: David Carlier &lt;<a href="mailto:devnexen@gmail.com">devnexen@gmail.com</a>&gt;
-	</p>
-      <p>In order to increase the FreeBSD tooling to uncover
-	code bugs in the userland, further compiler-rt components
-	support and static code analysis improvements had been
-	added
-	since the last 6.0 version.</p>
-
-      <p>Starting with the sanitizers, Memory Sanitizer (for amd64)
-	mainly to
-	detect unitialized pointers. There is also a simple W^X
-	paging
-	requests detection available from most of sanitizers.</p>
-
-      <p>Also libFuzzer support finally had been possible.
-	It allows code to be tested with random values from corpus
-	inputs.
-	Mutation and combination algorithms of those random inputs
-	can be overwritten. Can also be used in addition to ubsan,
-	asan, msan and so on.</p>
-
-      <p>At last, the X-Ray instrumentation feature is also
-	supported.
-	It is mainly about performance profiling purposes for a
-	reasonable performance runtime cost.</p>
-
-      <p>In the static code analysis department, reliable strlcpy
-	(unfortunately strlcat
-	did not get merged in due time for the release) wrong
-	usage
-	cases are now covered and W^X code detection tooling had
-	been added.</p>
-
-      <p>At the moment, this 7.0 version is imported by Dimitry
-	Andric, within
-	its own git branch available only for FreeBSD after 12
-	releases.</p>
-
-    <hr /><h2><a name="Performance-improvements" href="#Performance-improvements" id="Performance-improvements">Performance improvements</a></h2><p>
-	Contact: Matthew Macy &lt;<a href="mailto:mmacy@FreeBSD.org">mmacy@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD 12 saw the introduction of a number of performance
-	improvements:</p>
-
-      <ul>
-	<li>The introduction of the new synchronization primitive
-	epoch(9) to
-	replace the use of reader locks for providing existence
-	guarantees
-	for data structures.</li>
-
-	<li>epoch(9) was used to provide an 85+% reduction in the
-	overhead of
-	pcb lookup in high core count systems.</li>
-
-	<li>epoch(9) was used to provide an 85+% reduction in UDP send
-	overhead
-	on high core count systems. See the link for a bit more
-	detail:
-	<a href="http://scalebsd.org/blog/2018/06/16/UDP-and-epoch-for-liveness-guarantees" shape="rect">http://scalebsd.org/blog/2018/06/16/UDP-and-epoch-for-liveness-guarantees</a></li>
-	<li>System call overhead is now half that of FreeBSD 11.</li>
-
-	<li>UNIX sockets now scale near linearly (previously maxed out
-	at 3-4 threads).</li>
-
-	<li>The NUMA work has lead to a 20x-80x improvement in the
-	scalability
-	of page fault handling.</li>
-      </ul>
-
-    <hr /><h2><a name="Save/Restore/Migration-support-in-bhyve" href="#Save/Restore/Migration-support-in-bhyve" id="Save/Restore/Migration-support-in-bhyve">Save/Restore/Migration support in bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration">Github repository for the save/restore and migration features</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="Github repository for the save/restore and migration features">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve">Github wiki - How to Save and Restore a bhyve guest</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve" title="Github wiki - How to Save and Restore a bhyve guest">https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve">Github wiki - How to Migrate a bhyve guest</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve" title="Github wiki - How to Migrate a bhyve guest">https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix">Github wiki - Suspend/resume test matrix</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix" title="Github wiki - Suspend/resume test matrix">https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix</a></td></tr></table><p>
-	Contact: Elena Mihailescu &lt;<a href="mailto:elenamihailescu22@gmail.com">elenamihailescu22@gmail.com</a>&gt;
-	<br />
-	Contact: Darius Mihai &lt;<a href="mailto:dariusmihaim@gmail.com">dariusmihaim@gmail.com</a>&gt;
-	<br />
-	Contact: Sergiu Weisz &lt;<a href="mailto:sergiu121@gmail.com">sergiu121@gmail.com</a>&gt;
-	<br />
-	Contact: Mihai Carabas &lt;<a href="mailto:mihai@FreeBSD.org">mihai@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Save/Restore feature is a facility to suspend and
-	resume guest
-	virtual images that has been added to the FreeBSD/amd64's
-	hypervisor,
-	bhyve. The bhyvectl tool is used to save the guest virtual
-	machine
-	into three files:</p>
-
-      <ul>
-	<li>a file for the guest memory</li>
-
-	<li>a file for state of each device / CPU state</li>
-
-	<li>a file that has metadata that is used in the restore
-	process</li>
-      </ul>
-
-      <p>
-	To suspend a bhyve guest, the bhyvectl tool must be run
-	with the <tt>--suspend
-	&lt;state_file_name&gt;</tt>
-	option followed by the guest name.</p>
-
-      <p>To restore a bhyve guest from a checkpoint, one simply has
-	to add the <tt>-r</tt> option
-	followed by the main state file (the same file that was
-	given to the <tt>--suspend</tt>
-	option for bhyvectl) when starting the VM.</p>
-
-      <p>The Migration feature uses the Save/Restore implementation
-	to migrate a bhyve guest
-	from one FreeBSD host to another FreeBSD host. To migrate
-	a bhyve guest,
-	one needs to start an empty guest on the destination host
-	from a shared guest
-	image using the bhyve tool with the <tt>-R</tt> option
-	followed by the source host
-	IP and the port to listen to migration request. On the
-	source host, the
-	migration is started by executing the bhyvectl command
-	with the <tt>--migrate</tt>
-	option, followed by the destination host IP and the port
-	to send to the messages.</p>
-
-      <p>New features added:</p>
-
-      <ul>
-	<li>Create the socket connection between source and
-	destination hosts</li>
-
-	<li>Migrate the guest state via sockets</li>
-
-	<li>Separate the suspend/resume/migration code from the
-	bhyverun.c and bhyvectl.c and added two new files
-	for them: migration.c and migration.h</li>
-
-	<li>Added save/restore state for xhci</li>
-
-	<li>Added save/restore state for fbuf</li>
-
-	<li>Fix vhpet restore state issues (timers related)</li>
-
-	<li>Add partially support for suspending and resuming a Linux
-	guest</li>
-      </ul>
-
-      <p>Future tasks:</p>
-
-      <ul>
-	<li>Check if live migration can be implemented using the
-	FreeBSD's Copy-on-Write mechanism</li>
-
-	<li>Add live migration support by using EPT (Intel)</li>
-
-	<li>Add live migration support by using NPT (AMD)</li>
-
-	<li>Add suspend/resume support for nvme</li>
-
-	<li>Add suspend/resume support for virtio-console</li>
-
-	<li>Add suspend/resume support for virtio-scsi</li>
-
-	<li>Fix restore timers issues</li>
-
-	<li>Fix suspending bhyve - threads issues</li>
-
-	<li>Fix suspending bhyve - mutexes issues</li>
-
-	<li>Add suspend/resume support for Windows guests</li>
-      </ul>
-
-    <p>This project was sponsored by Matthew Grooms, and iXsystems.</p><hr /><h2><a name="SMAP" href="#SMAP" id="SMAP">SMAP</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for SMAP (Supervisor-Mode Access Prevention), has
-	been added
-	to the amd64 kernel. The SMAP feature makes any access
-	from the
-	supervisor mode to the pages accessible to user mode cause
-	a fault,
-	unless the %eflags.AC bit is set at the time of the
-	access.</p>
-
-      <p>The SMAP implementation uses the ifunc framework to avoid
-	checking
-	for the SMAP capability of hardware on each call to
-	copyout(9) and
-	other functions.</p>
-
-      <p>In the amd64 architecture, FreeBSD has a common address
-	space between
-	the kernel space and user space. Enabling SMAP virtually
-	splits
-	the shared address space into two disjoint address spaces,
-	which
-	have different access criteria. This splitting of the
-	address space
-	provides a relatively low-overhead way of catching direct
-	accesses
-	from kernel to usermode, when not using the copyout(9)
-	family of
-	functions. The copyout(9) family of functions are
-	permitted direct
-	access to user space. Any direct access from kernel mode
-	to user
-	address space that isn't performed through the copyout(9)
-	family
-	of functions indicates a potential programming error.</p>
-
-      <p>It is interesting that very few bugs were found in the
-	FreeBSD
-	kernel after the SMAP feature was enabled. One issue that
-	was
-	identified existed in the pci(9) user driver. Enabling the
-	SMAP
-	feature identified at least two ports, VBox and acpi_call,
-	which
-	appeared to access userspace in an unsafe manner.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="String-functions-on-the-amd64-architecture" href="#String-functions-on-the-amd64-architecture" id="String-functions-on-the-amd64-architecture">String functions on the amd64 architecture</a></h2><p>
-	Contact: Mateusz Guzik &lt;<a href="mailto:mjg@FreeBSD.org">mjg@FreeBSD.org</a>&gt;
-	</p>
-      <p>Functions like memset, memmove and memcpy are very
-	frequently used by virtually
-	all programs. They can be optimized in various ways, but
-	FreeBSD uses very
-	rudimentary implementations using rep movsq/stosq. rep
-	prefix has high startup
-	latency which is overly expensive when dealing with small
-	sizes.</p>
-
-      <p>Short term goal of this project is to implement faster
-	variants for the kernel
-	and import them into libc. The main speed up comes from
-	not using rep for small
-	sizes (&lt; 256) and from aligning target buffers to 16
-	bytes when rep is used.
-	On top of that runtime detection of the Enhanced REP
-	MOVSB/STOSB extention can
-	be used to only use rep movsb/stosb.</p>
-
-      <p>Mid term goal extends userspace. SIMD extensions can be
-	used to make these functions
-	faster. They can't easily be used in the kernel: SIMD
-	registers are not saved on
-	transitions user&lt;-&gt;kernel for performance reasons.
-	Thus any use would have to
-	take care of saving these registers, which can consume any
-	advantage from using them in
-	the first place. This is not a concern for userspace code.</p>
-
-      <p>There is a BSD-licensed implementation in bionic:
-	<a href="https://android.googlesource.com/platform/bionic/+/master/libc/arch-x86_64/string/" shape="rect">https://android.googlesource.com/platform/bionic/+/master/libc/arch-x86_64/string/</a></p>
-
-      <p>which with some modifications can be used in libc later
-	on.</p>
-
-      <p>See the Intel Optimization Manual for reference:
-	<a href="https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf" shape="rect">https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf</a></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Usermode-mapping-of-PCI-BARs" href="#Usermode-mapping-of-PCI-BARs" id="Usermode-mapping-of-PCI-BARs">Usermode mapping of PCI BARs</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>Modern PCI(e) devices typically define memory-mapped BARs
-	(Base Address Registers) to make a memory region available
-	to the device.
-	Each BAR
-	has a separate page-aligned boundary and memory region
-	associated with it.
-	This is enforced by the need
-	of hypervisors to provide the pass-through using VT-d,
-	which operates
-	with memory and has the granularity of one page for access
-	control.
-	As is, it
-	also means that the BARs have a suitable configuration for
-	providing
-	access to usermode, controlling access by the normal page
-	tables.</p>
-
-      <p>Linux already gives a way for userspace mapping of BARs
-	using sysfs.</p>
-
-      <p>Of course, if a userspace program has enough privileges,
-	it can read a BAR,
-	determine the physical address of the mapping as seen by
-	CPU, and use
-	mem(4) (aka /dev/mem) to mmap() that region of memory.
-	This is very cumbersome, and leaves many unresolved
-	issues.
-	For example, a BAR might be not activated, which would
-	require
-	involvement of the IOMMU on some architectures. Also this
-	rude approach
-	makes it very hard to create mappings with the correct
-	caching
-	attributes.</p>
-
-      <p>The FreeBSD pci(4) driver was enhanced to support such
-	mappings, and pciconf(8) utility was extended to use the
-	new support.
-	See pci(4)
-	for PCIOCBARMMAP ioctl(2) request description for details,
-	and
-	pciconf(8) for the -D switch.</p>
-
-      <p>TODO: automatically activate the BAR on mapping, this is
-	not done yet.
-	There is a problem with avoiding the resource conflicts on
-	possible future attachmens of the kernel driver.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation, and Mellanox Technologies.</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="Allwinner-SoC-Support" href="#Allwinner-SoC-Support" id="Allwinner-SoC-Support">Allwinner SoC Support</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <ul>
-	<li>SPI driver added for A64 SoC</li>
-
-	<li>Thermal driver added/fixed for A64/H3/H5 SoCs</li>
-
-	<li>Lot of bugs where fixed in the mmc driver, stability
-	should be better</li>
-
-	<li>New driver for AXXP803 which is the power chip companion
-	of the A64 SoC</li>
-
-	<li>Add overlays to use another timer controller as the
-	default one in A64 if faulty
-	These overlay is enabled in the PINE64/LTS images by
-	default</li>
-      </ul>
-
-    <hr /><h2><a name="Armada-38x-FreeBSD-support" href="#Armada-38x-FreeBSD-support" id="Armada-38x-FreeBSD-support">Armada 38x FreeBSD support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.marvell.com/documents/egrkpyqzpoebxblyeept/" title="https://www.marvell.com/documents/egrkpyqzpoebxblyeept/">PRODUCT BRIEF</a></td><td>
-	    URL: <a href="https://www.marvell.com/documents/egrkpyqzpoebxblyeept/" title="PRODUCT BRIEF">https://www.marvell.com/documents/egrkpyqzpoebxblyeept/</a></td></tr></table><p>
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Patryk Duda &lt;<a href="mailto:pdk@semihalf.com">pdk@semihalf.com</a>&gt;
-	<br />
-	Contact: Rafa&#322; Kozik &lt;<a href="mailto:rk@semihalf.com">rk@semihalf.com</a>&gt;
-	</p>
-      <p>The Marvell Armada 38x is a very poplular ARMv7-based dual
-	core SoC.
-	Thanks to the multiple low and high speed interfaces
-	the platform is used in a wide range of products, such
-	as Network-Attached Storage (NAS), Wi-Fi Access Point
-	(WAP) and others.</p>
-
-      <p>Since last report, remaining Armada 38x support was
-	integrated to HEAD, which can now compile with the
-	armv7
-	GENERIC config and use unmodified sys/gnu/dts device
-	trees. The details are as follows:</p>
-
-      <ul>
-	<li>GENERIC config</li>
-
-	<li>Introduce a vast rework of the sys/arm/mv directory for
-	arm and armv7 platforms.</li>
-
-	<li>Enable PLATFORM support for Marvell ARMv7 SoCs, which can
-	now can boot with GENERIC kernel.</li>
-
-	<li>Base on dynamic detection of SoC type and device tree
-	instead of using ifdefs
-	and enable more flexible environment for maintaining
-	Marvell platforms.</li>
-
-	<li>sys/gnu/dts device trees</li>
-
-	<li>Improve platform code and the drivers (e.g. CESA, PCIE,
-	GPIO) to properly work with original
-	Linux device trees.</li>
-
-	<li>GPIO</li>
-
-	<li>Add multiple fixes and improvements to the
-	sys/arm/mv/gpio.c</li>
-
-	<li>Rework driver to properly integrate with HEAD GPIO
-	frameworks (main and gpioled)</li>
-
-	<li>Enable support for both old and Linux GPIO device tree
-	bindings, so that multiple controllers
-	can be used.</li>
-      </ul>
-
-    <p>This project was sponsored by Stormshield, and Semihalf.</p><hr /><h2><a name="ARMv6-and-ARMv7-image-now-use-EFI-loader" href="#ARMv6-and-ARMv7-image-now-use-EFI-loader" id="ARMv6-and-ARMv7-image-now-use-EFI-loader">ARMv6 and ARMv7 image now use EFI loader</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>Instead of using the ubldr version of the loader which
-	uses the U-Boot
-	API, all images now use loader.efi as their primary
-	FreeBSD loader.
-	This allow us to have a common boot path for all arm and
-	arm64 images.</p>
-
-    <hr /><h2><a name="DTS-Update" href="#DTS-Update" id="DTS-Update">DTS Update</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>DTS files (Device Tree Sources) were updated to be on par
-	with Linux 4.18 for
-	the 12.0 release.</p>
-
-      <p>The DTS are now compiled for some arm64 boards as the one
-	present in U-Boot are
-	now always up-to-date.</p>
-
-    <hr /><h2><a name="FreeBSD-on-POWER9" href="#FreeBSD-on-POWER9" id="FreeBSD-on-POWER9">FreeBSD on POWER9</a></h2><p>
-	Contact: Matthew Macy &lt;<a href="mailto:mmacy@FreeBSD.org">mmacy@FreeBSD.org</a>&gt;
-	</p>
-      <p>Once Justin Hibbits largely stabilized the powerpc64 port
-	on the POWER9
-	based Talos II I decided to procure one. I've been slowly
-	working towards
-	taking powerpc64 to parity with amd64. I've been working
-	in an out of tree
-	GitHub project - in part to eliminate the need to continue
-	to support the 11
-	year old in tree gcc4.</p>
-
-      <p>Progress so far:</p>
-
-      <ul>
-	<li>Adapted lock_delay to use POWER's SMT scheduling hints
-	rather than
-	using the yield hint from an older ISA</li>
-
-	<li>Added ifunc support</li>
-
-	<li>Ported the amd64 pmap so FreeBSD can use POWER9's new
-	radix tree
-	page tables. This will give us superpages mostly for free.</li>
-
-	<li>Reduced the overhead of copyinout primitives for radix.</li>
-
-	<li>Converted the copyinout primitives to ifuncs to switch
-	between the
-	old and the new at initialization time.</li>
-
-	<li>Converted pmap to use ifuncs to eliminate the overhead of
-	kobj dispatch.</li>
-
-	<li>Hot patch out trap handling paths only needed by the older
-	hashed page
-	table support.</li>
-      </ul>
-
-      <p>
-	Work in Progress:</p>
-
-      <ul>
-	<li>NMI semantics: NMIs need to be emulated by only soft
-	disabling interrupts,
-	disabling interrupts blocks all interrupts except machine
-	check exceptions
-	and system resets.</li>
-
-	<li>Superpage support: Superpages work in the functional
-	simulator running SMT4
-	but currently crash on real hardware due to incomplete
-	page walk cache /
-	TLB invalidation.</li>
-
-	<li>Kernel minidump - with radix MMU enabled minidump support
-	was a fairly
-	straightforward port but time needs to be spent on test /
-	debug.</li>
-
-	<li>EARLY_AP_STARTUP - preliminary patches exist, but this is
-	more work on !x86
-	architectures due to IPI setup not being tied to the CPU
-	code.</li>
-      </ul>
-
-      <p>
-	A list of the other items needed to achieve kernel feature
-	parity with a
-	(wishful) list of milestones can be found at:
-	<a href="https://github.com/POWER9BSD/freebsd/projects/1" shape="rect">https://github.com/POWER9BSD/freebsd/projects/1</a></p>
-
-    <hr /><h2><a name="FreeBSD-on-PowerNV-(ppc64)" href="#FreeBSD-on-PowerNV-(ppc64)" id="FreeBSD-on-PowerNV-(ppc64)">FreeBSD on PowerNV (ppc64)</a></h2><p>
-	Contact: Patryk Duda &lt;<a href="mailto:pdk@semihalf.com">pdk@semihalf.com</a>&gt;
-	<br />
-	Contact: Wojciech Macek &lt;<a href="mailto:wma@FreeBSD.org">wma@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Michal Stanek &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact: Nathan Whitehorn &lt;<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>&gt;
-	</p>
-      <p>Semihalf is happy to announce that FreeBSD is now running
-	on IBM POWER8. This project is a continuation of
-	work done by Nathan Whitehorn who provided basic
-	support for a PowerNV emulator.</p>
-
-      <p>The IBM POWER8 family of CPUs offers superior performance
-	compared to previous Power series. It provides
-	complete NUMA support with up to 192 cores in a
-	two socket system (up to 8 threads per core). All
-	IO communication is handled by integrated PCIe
-	interface equipped with multiple IOMMU engines.</p>
-
-      <p>The support for POWER8 system running FreeBSD in
-	Non-Virtualized environment contains:</p>
-
-      <ul>
-	<li>Generic driver for OPAL hypervisor</li>
-
-	<li>kboot loader modifications to allow Little-Endian loader
-	to load a Big-Endian kernel ELF</li>
-
-	<li>skiboot update for ELF-parser allowing it to understand
-	FreeBSD kernel file format</li>
-
-	<li>Basic support for PowerNV architecture, including modes of
-	operation, MMU, interrupt controller</li>
-
-	<li>SMP operation (tested with 128 CPU configuration)</li>
-
-	<li>PHB subsystem driver, including IOMMU mapping for external
-	buses</li>
-
-	<li>PCIe host controller driver</li>
-
-	<li>USB-3.0 XHCI driver</li>
-
-	<li>Reworked drivers to be Big-Endian compatible:</li>
-
-	<li>Chelsio cxgbe(4) 10/25G network adapter</li>
-
-	<li>NVMe SSD drive</li>
-      </ul>
-
-      <p>
-	All work has been merged into HEAD and will be included in
-	FreeBSD 12.0-RELEASE.</p>
-
-      <p>Sponsors: IBM, FreeBSD Foundation, QCM Technologies,
-	Semihalf, Limelight Networks.</p>
-
-      <p>The project is kindly initiated and supported by Limelight
-	Networks (Kevin Bowling).</p>
-
-    <hr /><h2><a name="FreeBSD-on-RISC-V" href="#FreeBSD-on-RISC-V" id="FreeBSD-on-RISC-V">FreeBSD on RISC-V</a></h2><p>
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreeBSD/RISC-V has been one of the actively supported
-	projects during the past year.</p>
-
-      <p>On a compiler front we have upstreamed FreeBSD
-	OS-dependent bits for GNU toolchain. It was
-	updated to GCC 8.1 and Binutils 2.30. FreeBSD
-	packages are available.</p>
-
-      <p>FreeBSD Testsuite and required dependencies were
-	successfully built for RISC-V and we did a test
-	run: 152 tests failed out of 5186, which
-	demonstrates a very good result for initial run
-	and reveals areas to work on.</p>
-
-      <p>We have added support for compressed ISA extension to KDB
-	debugger and DTrace FBT provider enabling
-	C-compressed kernel and userland by default. The
-	output of disassembling instructions in KDB is
-	looking similar to objdump.</p>
-
-      <p>QEMU has updated to latest privilege spec allowing us to
-	bring up FreeBSD on it. The emulation is quite
-	fast: it takes one second only to boot FreeBSD to
-	single-user mode in QEMU: <a href="https://www.youtube.com/watch?v=FnWpRBaWF18" shape="rect">https://www.youtube.com/watch?v=FnWpRBaWF18</a></p>
-
-      <p>Platform-Level Interrupt Controller (PLIC) driver was
-	added. Interrupt support was converted to INTRNG.
-	PLIC is used in QEMU for virtio network and block devices.
-	With these changes, a full FreeBSD distribution
-	can now be booted in QEMU.</p>
-
-      <p>Network virtualization support (VIMAGE) was fixed and
-	enabled by default now.</p>
-
-      <p>In order to support RocketChip and derivatives we had to
-	work on A(accessed), D(dirty) PTE (page table
-	entry) bits management.
-	We have successfully tested this on a lowRISC board and it
-	is booting to multiuser just fine. lowRISC UART
-	driver was added.</p>
-
-      <p>Superuser-User-Modify (SUM) bit in status register is now
-	used: kernel can access userspace only within
-	certain functions that explicitly handle crossing
-	user/kernel boundary.</p>
-
-    <hr /><h2><a name="PINE64-LTS-Image" href="#PINE64-LTS-Image" id="PINE64-LTS-Image">PINE64-LTS Image</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>We now produce an image for the PINE64-LTS.
-	This image works on the PINE64-LTS and the Sopine with
-	Baseboard.</p>
-
-    <hr /><h2><a name="PocketBeagle-Support" href="#PocketBeagle-Support" id="PocketBeagle-Support">PocketBeagle Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.beagleboard.org/pocket" title="https://www.beagleboard.org/pocket">Pocket Beagle</a></td><td>
-	    URL: <a href="https://www.beagleboard.org/pocket" title="Pocket Beagle">https://www.beagleboard.org/pocket</a></td></tr></table><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Tom Jones &lt;<a href="mailto:thj@FreeBSD.org">thj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Pocket Beagle is the latest member of the BeagleBoard
-	family.
-	Support for it was added and the Beaglebone image can be
-	used on it directly.</p>
-
-    <hr /><h2><a name="RPI-Firmware/DTB/U-Boot-Update" href="#RPI-Firmware/DTB/U-Boot-Update" id="RPI-Firmware/DTB/U-Boot-Update">RPI Firmware/DTB/U-Boot Update</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: U-Boot mailing list &lt;<a href="mailto:uboot@FreeBSD.org">uboot@FreeBSD.org</a>&gt;
-	</p>
-      <p>The RaspberryPi firmware loads the DTB from the FAT
-	partition based on
-	the model. U-Boot now uses this DTB and passes it to the
-	FreeBSD loader/kernel
-	instead of using the DTS embedded in U-Boot.
-	This allow the FreeBSD Kernel to use the RaspberryPi
-	Foundation provided DTB overlays to enable
-	HATs.
-	The overlays can be obtained by installing the
-	rpi-firmware package.</p>
-
-      <p>A new U-Boot port for the W variant of the RPI0 was
-	committed as
-	u-boot-rpi-0-w. Some experiments started by Edward Tomasz
-	Napierala
-	(trasz@) have shown that we could possibly produce a
-	generic image
-	for all armv6 RPI (RPI-B, RPI0 and RPI0W).</p>
-
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://FreeBSD.kde.org/" title="https://FreeBSD.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://FreeBSD.kde.org/" title="KDE FreeBSD">https://FreeBSD.kde.org/</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:adridg@FreeBSD.org">adridg@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Tobias C. Berner &lt;<a href="mailto:tcberner@FreeBSD.org">tcberner@FreeBSD.org</a>&gt;
-	</p>
-      <p>KDE FreeBSD is responsible for the ports of the Plasma5
-	and KDE4 desktops, and
-	all associated applications. Further we also manage the
-	Qt4 and Qt5 ports, as
-	well as CMake.</p>
-
-      <p>We also care for the FreeBSD builders for KDE's upstream
-	CI on build.kde.org.</p>
-
-      <p>Since the last status report a lot of things have changed.
-	First and foremost,
-	the Plasma5 Desktop and the Qt5 based KDE Applications
-	have finally made their
-	way into the official ports tree after lingering for
-	multiple years in our
-	development repository.</p>
-
-      <p>Secondly KDE4 has been marked deprecated and will be
-	removed at the end of the
-	year. With Qt4 following no later than the next year (due
-	to the exponentially
-	increasing burden of maintenance).</p>
-
-      <p>On a more technical side, bsd.qt.mk has been replaced by
-	qt.mk and qt-dist.mk.
-	The porter's handbook is being updated (with thanks to
-	Tobias Kortkamp).</p>
-
-      <p>Further we have been keeping CMake and Qt5 and almost
-	every other port under our
-	control up to date. SDDM has been updated to the
-	next-to-latest release with
-	backported security fixes.</p>
-
-      <p>One big issue we have is www/qt5-webengine, which requires
-	too much time to keep
-	up to date, as the underlying chromium is in need of many
-	patches, which change
-	with every release. Another upcoming issue is the way in
-	which FreeBSD's libinput
-	lags behind. This blocks future updates to KDE Plasma as
-	well as Wayland
-	improvements. Thankfully x11@ is looking at this issue
-	already, so it should be
-	fixed soon -- for the meantime people who want to give the
-	latest KDE Plasma
-	Desktop a try can use the appropriate branch from our
-	GitHub.</p>
-
-      <p>People who are willing to contribute can find us on
-	#kde-freebsd on freenode,
-	the kde@FreeBSD.org mailing list. Further, we accept
-	pull-requests and
-	contributions on github.com/freebsd/freebsd-ports-kde.</p>
-
-    <hr /><h2><a name="Puppet" href="#Puppet" id="Puppet">Puppet</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="https://puppetcommunity.slack.com/messages/C6CK0UGB1/">PuppetLab's FreeBSD slack channel</a></td><td>
-	    URL: <a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="PuppetLab's FreeBSD slack channel">https://puppetcommunity.slack.com/messages/C6CK0UGB1/</a></td></tr><tr><td><a href="https://www.bsdcan.org/2018/schedule/events/930.en.html" title="https://www.bsdcan.org/2018/schedule/events/930.en.html">BSDCan 2018: IT automation with Puppet</a></td><td>
-	    URL: <a href="https://www.bsdcan.org/2018/schedule/events/930.en.html" title="BSDCan 2018: IT automation with Puppet">https://www.bsdcan.org/2018/schedule/events/930.en.html</a></td></tr></table><p>
-	Contact: Puppet Team &lt;<a href="mailto:puppet@FreeBSD.org">puppet@FreeBSD.org</a>&gt;
-	</p>
-      <p>Since our last status report last year, the puppet@ team
-	regularly updated the
-	Puppet ports to catch on upstream releases. We have also
-	held a Puppet talk at
-	BSDCan.</p>
-
-      <p>More recently, Puppet 6 was released, and a bunch of new
-	ports appeared in the
-	FreeBSD ports tree: sysutils/puppet6,
-	sysutils/puppetserver6,
-	databases/puppetdb6 being (obviously) the main ones. In
-	this update, the Puppet
-	language has not been heavily modified. As a consequence,
-	upgrading from Puppet
-	5 to Puppet 6 is an easy task compared to the experience
-	you may have
-	encountered from previous major version bumps. If you are
-	still using Puppet 4,
-	we recommend to schedule an upgrade soon: Puppet 4 is
-	expected to be EOL by the
-	end of 2018.</p>
-
-      <p>Because distributing Marionette Collective modules via
-	Puppet is more efficient
-	than using packages, the
-	sysutils/mcollective-\*-{agent,client} ports have
-	been
-	deprecated. Marionette Collective itself being phased out
-	by PuppetLabs, the
-	sysutils/mcollective port is expected to be deprecated at
-	some point in the
-	future, but we plan to keep it until an alternative is
-	available. This
-	alternative, called Choria, is in active development by
-	R.I.Pienaar the
-	original author of Marionette Collective. We are actively
-	working with him to
-	support FreeBSD out of the box, and will commit
-	sysutils/choria to the tree as
-	soon as it is considered a drop-in replacement for
-	Marionette Collective.</p>
-
-    <hr /><h2><a name="scarab:-CLI-tool-for-Bugzilla-related-workflows" href="#scarab:-CLI-tool-for-Bugzilla-related-workflows" id="scarab:-CLI-tool-for-Bugzilla-related-workflows">scarab: CLI tool for Bugzilla-related workflows</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/scarab" title="https://github.com/gonzoua/scarab">GitHub repo</a></td><td>
-	    URL: <a href="https://github.com/gonzoua/scarab" title="GitHub repo">https://github.com/gonzoua/scarab</a></td></tr></table><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p>
-      <p>scarab is a CLI tool that makes some of Bugzilla
-	functionality
-	available from the command line. Normally users interact
-	with the
-	<a href="https://bugs.FreeBSD.org/bugzilla/" shape="rect">bugtracker</a>
-	using a web browser
-	but for certain workflows, Web UI may be more of an
-	obstacle
-	than help requiring to perform more steps compared to CLI
-	tool.</p>
-
-      <p>Bugzilla provides XML-RPC interfaces that can be used for
-	automation/integration and there are several CLI tools
-	like
-	<a href="https://github.com/williamh/pybugz" shape="rect">pybugz</a>
-	that can be used
-	with bugs.FreeBSD.org as-is. They are generic
-	one-size-fits-all
-	tools which mean they can do a lot of thing at the cost of
-	more complex CLI.</p>
-
-      <p>scarab was created to be more specialized and less complex
-	with following
-	principles in mind:</p>
-
-      <ul>
-	<li>Be an auxiliary tool, not a replacement for the web UI</li>
-
-	<li>Move complexity to a configuration file, keep arguments as
-	simple as possible</li>
-
-	<li>Optimize for most common/tedious tasks</li>
-      </ul>
-
-      <p>
-	Based on my experience with Bugzilla following tasks were
-	identified as
-	candidates for inclusion in the first release of the tool:</p>
-
-      <ul>
-	<li>Downloading attachment on host machine and copying it to
-	devbox</li>
-
-	<li>Creating a file on the devbox and copying it to a host
-	machine to be attached through Web UI</li>
-
-	<li>Creating PRs with common fields' values</li>
-      </ul>
-
-      <p>
-	First two operations were implemented as <tt>files</tt>,
-	<tt>fetch</tt>, <tt>fetchall</tt>, <tt>attach</tt>
-	commands of the tool.</p>
-
-      <p>The third operation was implemented by introducing PR
-	templates, set of
-	predefined field/value pairs, that can be combined
-	run-time to provide higher
-	flexibility. More information and usage examples can be
-	found in the
-	<a href="https://github.com/gonzoua/scarab/blob/master/examples/scarabrc" shape="rect">config
-	file example</a></p>
-
-    <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree or new external
-      books/documents.</p><br /><h2><a name="Cleaning-up-the-Wiki" href="#Cleaning-up-the-Wiki" id="Cleaning-up-the-Wiki">Cleaning up the Wiki</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/WikiFixitGroup/" title="https://wiki.FreeBSD.org/WikiFixitGroup/">Wiki Fixit Group Website</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/WikiFixitGroup/" title="Wiki Fixit Group Website">https://wiki.FreeBSD.org/WikiFixitGroup/</a></td></tr><tr><td><a href="irc://freebsd-wiki@irc.freenode.net" title="irc://freebsd-wiki@irc.freenode.net">IRC channel</a></td><td>
-	    URL: <a href="irc://freebsd-wiki@irc.freenode.net" title="IRC channel">irc://freebsd-wiki@irc.freenode.net</a></td></tr></table><p>
-	Contact:  &lt;<a href="mailto:wiki-admin@FreeBSD.org">wiki-admin@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Wiki used to be a scratch pad for the FreeBSD
-	developers to
-	organize projects, store notes and publish articles that
-	were about to be added
-	to the handbook. Recently, however, the FreeBSD wiki
-	started to attract more
-	and more people from the wider FreeBSD community, which
-	resulted in a change of
-	the character of the wiki.</p>
-
-      <p>As a result we decided to discuss the future of the tools
-	we want to use for
-	documentation in FreeBSD (one of such discussions was held
-	during BSDCam 2018,
-	you may see some notes
-	<a href="https://wiki.FreeBSD.org/DevSummit/201808/DeveloperTools" shape="rect">here</a>).
-	The general
-	conclusion is that wiki is a great tool for what it was
-	meant for: organizing
-	projects and notes in the community of developers. We
-	should not move all our
-	documentation (especially handbooks) to Wiki as the
-	quality and maintainability
-	would suffer. On the other hand, the current workflow of
-	submitting
-	documentation patches, which involves checking out the doc
-	tree and patching
-	XML files is not ideal for many end users. This is why we
-	are trying to approach the problem from various
-	directions:</p>
-
-      <ol><li>The wiki is being cleaned up of old content. We are
-	trying to define a clear
-	hierarchy of subpages and categories to make navigating
-	the wiki easier.</li>
-      <li>Some articles from the wiki are going to be migrated to
-	either the doc tree
-	or manual pages.</li></ol>
-
-    <hr /><h2><a name="Quarterly-Reports" href="#Quarterly-Reports" id="Quarterly-Reports">Quarterly Reports</a></h2><p>
-	Contact: Edward Tomasz Napiera&#322;a &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mateusz Piotrowski &lt;<a href="mailto:0mp@FreeBSD.org">0mp@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Quarterly Reports have been resurrected after almost a
-	year long hiatus.
-	The old workflow, which consisted of users submitting
-	XML-formatted entries,
-	which would then get hand-assembled into DocBook, was
-	replaced with a new
-	one, using Markdown instead. The XML submission form was
-	replaced with
-	GitHub Pull Requests. This should make submissions and
-	editing much easier
-	and user-friendly.</p>
-
-    <hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="HardenedBSD-2018Q3-Update" href="#HardenedBSD-2018Q3-Update" id="HardenedBSD-2018Q3-Update">HardenedBSD 2018Q3 Update</a></h2><p>
-	Contact: Shawn Webb &lt;<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>&gt;
-	</p>
-      <p>Our last report was
-	<a href="https://www.FreeBSD.org/status/report-2017-04-2017-06.html#HardenedBSD" shape="rect">June
-	2017</a>.
-	A lot has transpired since then. In this status report, we
-	will
-	attempt to briefly cover all the progress we've made,
-	including the
-	few commits that made it upstream to FreeBSD.</p>
-
-      <p>On 01 Jul 2018, we switched back to
-	<a href="https://hardenedbsd.org/article/shawn-webb/2018-04-30/hardenedbsd-switching-back-openssl" shape="rect">OpenSSL</a>
-	as the crypto library provider in base. We did this
-	because we lack
-	the resources and the documentation for properly
-	supporting LibreSSL
-	in base. We still maintain LibreSSL in base; however,
-	OpenSSL is
-	simply the default crypto library (aka,
-	<tt>WITHOUT_LIBRESSL</tt> is the
-	default). We look forward to building a development
-	community around
-	LibreSSL in HardenedBSD such that we can re-enable
-	LibreSSL by
-	default, providing enhanced security for our users through
-	the
-	rejection of software monocultures.</p>
-
-      <p>Cross-DSO Control Flow Integrity (Cross-DSO CFI) is an
-	exploit
-	mitigation from llvm that provides forward-edge
-	protections across
-	shared library and application boundaries. With
-	HardenedBSD 12-STABLE,
-	we launched non-Cross-DSO CFI support in base. Meaning,
-	CFI is only
-	applied to applications and not shared libraries. Along
-	with
-	SafeStack, which provides backward-edge protections,
-	Cross-DSO CFI
-	requires both ASLR and W^X for effectiveness as they store
-	crucial
-	metadata needing protection. HardenedBSD expertly,
-	efficiently, and
-	robustly fulfill those requirements through its PaX ASLR
-	and PaX
-	NOEXEC implementations.</p>
-
-      <p>Over the past two years, we have slowly worked on
-	Cross-DSO CFI
-	support in HardenedBSD. In mid-2018, we made enough
-	progress that we
-	could publish an alpha
-	<a href="https://hardenedbsd.org/article/shawn-webb/2018-07-16/preliminary-call-testing-cross-dso-cfi" shape="rect">Call-For-Testing
-	(CFT)</a>.
-	We need to integrate the Cross-DSO CFI support with the
-	RTLD such that
-	function pointers resolved through
-	<tt>dlopen(3)</tt>/`dlsym(3)` work properly
-	with the cfi-icall scheme. We also need to perform
-	experimental
-	package builds, find breakages, and fix those breakages.
-	We hope to
-	officially debut Cross-DSO CFI in the latter half of 2019
-	with the
-	possibility of pushing back to 2020. HardenedBSD remains
-	the first and
-	only enterprise operating system to use CFI across the
-	base set of
-	applications.</p>
-
-      <p>On 20 Aug 2018, we launched a new tool called
-	<tt>hbsdcontrol(8)</tt> to
-	toggle exploit mitigations on a per-application basis.
-	<tt>hbsdcontrol(8)</tt> uses filesystem extended
-	attributes and is the
-	preferred method for exploit mitigation toggling for those
-	filesystem
-	that support extended attributes (UFS, ZFS). Our original
-	utility,
-	<tt>secadm</tt>, should be used with filesystems that do
-	not support extended
-	attributes (NFS).</p>
-
-      <p>In <a href="https://hardenedbsd.org/article/shawn-webb/2018-09-17/announcing-hardenedbsd-foundation" shape="rect">September
-	2018</a>,
-	the HardenedBSD Foundation Corp became a 501(c)(3)
-	tax-exempt,
-	not-for-profit organization in the USA. This means that
-	donations by
-	US persons are eligible for tax deductions. The creation
-	of the
-	HardenedBSD Foundation will ensure that HardenedBSD
-	remains successful
-	long-term. We look forward to working with the BSD
-	community to
-	provide an open source, clean-room reimplementation of the
-	grsecurity
-	patchset based on publicly-available documentation.</p>
-
-      <p>We assisted Kyle Evans with the new <tt>bectl(8)</tt>
-	utility, primarily
-	enhancing jail support and fixing regressions. We are
-	grateful for
-	Kyle Evans' assistance in landing the enhancements
-	upstream in FreeBSD
-	and his overall responsiveness and helpfulness.</p>
-
-      <p>Relevant commits for the <tt>bectl(8)</tt> are:</p>
-
-      <ul>
-	<li><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=339047" shape="rect">r339047</a></li>
-
-	<li><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=338221" shape="rect">r338221</a></li>
-
-	<li><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=337993" shape="rect">r337993</a></li>
-
-	<li><a href="https://svnweb.FreeBSD.org/base?view=revision&amp;revision=337947" shape="rect">r337947</a></li>
-      </ul>
-
-      <p>
-	We taught <tt>bhyve(8)</tt> how to live in a
-	<a href="https://reviews.FreeBSD.org/rS337023" shape="rect">jailed
-	environment</a>, allowing users to
-	jail the hypervisor. We hardened the virtual address space
-	of
-	<tt>bhyve(8)</tt> by using <a href="https://reviews.FreeBSD.org/rS338511" shape="rect">guard
-	pages</a>.
-	This work made it upstream to FreeBSD. We are grateful to
-	those in
-	FreeBSD who provided insight to increase the quality and
-	efficiency
-	of our patches.</p>
-
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2018-09-2018-12.html b/website/content/en/status/report-2018-09-2018-12.html
deleted file mode 100644
index 860069a86d..0000000000
--- a/website/content/en/status/report-2018-09-2018-12.html
+++ /dev/null
@@ -1,1972 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Since we are still on this island among many in this vast ocean of the Internet, we write this message in a bottle to inform you of the work we have finished and what lies ahead of us. These deeds that we have wrought with our minds and hands, they are for all to partake of - in the hopes that anyone of their free will, will join us in making improvements. In todays message the following by no means complete or ordered set of improvements and additions will be covered:</p><p>i386 PAE Pagetables for up to 24GB memory support, Continuous Integration efforts, driver updates to ENA and graphics, ARM enhancements such as RochChip, Marvell 8K, and Broadcom support as well as more DTS files, more Capsicum possibilities, as well as pfsync improvements, and many more things that you can read about for yourselves.</p><p>Additionally, we bring news from some islands further down stream, namely the nosh project, HardenedBSD, ClonOS, and the Polish BSD User-Group.</p><p>We would, selfishly, encourage those of you who give us the good word to please send in your submissions sooner than just before the deadline, and also encourage anyone willing to share the good word to please read the section on which submissions we're also interested in having.</p><p>Yours hopefully,<br clear="none" />
-      Daniel Ebdrup, on behalf of the status report team.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#amd64-Usermode-Protection-Keys">amd64 Usermode Protection Keys</a></li><li><a href="#bhyve---Live-Migration">bhyve - Live Migration</a></li><li><a href="#bhyve---Save/Restore">bhyve - Save/Restore</a></li><li><a href="#Capsicum">Capsicum</a></li><li><a href="#Collection-of-vt(4)-color-schemes">Collection of vt(4) color schemes</a></li><li><a href="#i386-PAE-Pagetables">i386 PAE Pagetables</a></li><li><a href="#Improving-FreeBSD-boot-security">Improving FreeBSD boot security</a></li><li><a href="#pfsync-performance-improvement">pfsync performance improvement</a></li><li><a href="#PWM-Kernel-API-and-userland-utility">PWM Kernel API and userland utility</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></li><li><a href="#DTS-Update">DTS Update</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#FreeBSD-on-Power9-(ppc64)-Parity">FreeBSD on Power9 (ppc64) Parity</a></li><li><a href="#FreeBSD/RISC-V-update">FreeBSD/RISC-V update</a></li><li><a href="#libvdsk---QCOW2-implementation">libvdsk - QCOW2 implementation</a></li><li><a href="#Marvell-8K-SoC-support">Marvell 8K SoC support</a></li><li><a href="#Pinebook-SDCard-Image">Pinebook SDCard Image</a></li><li><a href="#RockChip-Support">RockChip Support</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-KDE-status-report">FreeBSD KDE status report</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSD-PL">BSD PL</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System">ClonOS: virtualization platform on top of FreeBSD Operating System</a></li><li><a href="#HardenedBSD-2018Q4-Update">HardenedBSD 2018Q4 Update</a></li><li><a href="#The-nosh-project">The nosh project</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-        Page</a>.</p><br /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org/" title="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org/" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org/</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="freebsd-ci Repository">https://github.com/freebsd/freebsd-ci</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD CI team maintains continuous integration
-	system and related tasks
-	for the FreeBSD project. The CI system regularly checks
-	the changes committed
-	to the project's Subversion repository can be successfully
-	built, and performs
-	various tests and analysis over the results. The results
-	from build jobs are
-	archived in artifact server, for the further testing and
-	debugging needs.</p>
-
-      <p>The members on the CI team examine the failing builds and
-	unstable tests, and
-	work with the experts in that area to fix the code or
-	build and test
-	infrastructure, to improve the software quality of the
-	FreeBSD base system.
-	The CI team member and the FreeBSD foundation staff Li-Wen
-	is the maintainer of
-	Jenkins and Jenkins related ports.</p>
-
-      <p>In this quarter, we worked on extending test executing
-	environment to improve
-	the coverage, temporarily disabling flakey test cases (and
-	opening tickets to
-	work with domain experts). Please see freebsd-testing@
-	related tickets for
-	more information.</p>
-
-      <p>In addition to that, starting from this quarter, we also
-	work on collaboration
-	with external projects to extend their CI to cover
-	FreeBSD. See "HostedCI"
-	wiki page for more information.</p>
-
-      <p>Work in progress:</p>
-
-      <ul>
-	<li>Fixing the failing test cases and builds</li>
-
-	<li>Adding drm ports building test against -CURRENT</li>
-
-	<li>Adding tests for selected project branches, e.g.:
-	clang800-import</li>
-
-	<li>Implementing automatic tests on bare metal hardware</li>
-
-	<li>Planning the embedded testbed</li>
-
-	<li>Planning running ztest and network stack tests</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>Noteworthy events since the last quarterly report:</p>
-
-      <ul>
-	<li>Yuri Pankov (yuripv@) was awarded a source commit bit
-	under the mentorship of Konstantin Belousov
-	(kib@).</li>
-
-	<li>Core agrees that portmgr@ may enforce a 12-month commit
-	bit expiration for ports committers.</li>
-
-	<li>Thomas Munro (tmunro@) was awarded a source commit bit
-	under the mentorship of Mateusz Guzik (mgj@) and
-	co-mentorship of Allan Jude (allanjude@).</li>
-
-	<li>With the approval of FCP-0101, 10/100 Ethernet drivers
-	will be deprecated.</li>
-
-	<li>Core approved the promotion of Remko Lodder (remko@) to
-	Deputy Security Officer.</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to supporting and promoting
-	the FreeBSD Project and community worldwide.
-	Funding comes from individual and corporate
-	donations and is used to fund and manage software
-	development projects, conferences and developer
-	summits, and provide travel grants to FreeBSD
-	contributors. The Foundation purchases and
-	supports hardware to improve and maintain FreeBSD
-	infrastructure and provides resources to improve
-	security, quality assurance, and release
-	engineering efforts; publishes marketing material
-	to promote, educate, and advocate for the FreeBSD
-	Project; facilitates collaboration between
-	commercial vendors and FreeBSD developers; and
-	finally, represents the FreeBSD Project in
-	executing contracts, license agreements, and other
-	legal arrangements that require a recognized legal
-	entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD
-	last quarter:</p>
-
-      <p>Partnerships and Commercial User Support</p>
-
-      <p>As a 501(c)(3) non-profit, we don&#8217;t directly support
-	commercial users, but we do work with them to
-	understand their needs and help facilitate
-	collaboration with the community. Last quarter, we
-	were able to meet with a number of FreeBSD users
-	and supporters at the October FreeBSD Developer
-	Summit and MeetBSD conference in addition to our
-	regular company meetings. These in-person meetings
-	provide the opportunity to discuss pain points,
-	identify how they can contribute back to FreeBSD,
-	talk about what technologies they would like to
-	see supported, and what can be done to support
-	FreeBSD over more of their technologies and
-	products.</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>By end of last year, we raised over $1.3M and were able to
-	add Juniper, Netflix and Facebook and
-	Handshake.org to our list of Foundation Partners.
-	You can view the entire list here <a href="https://www.freebsdfoundation.org/donors/" shape="rect">https://www.freebsdfoundation.org/donors/</a>.
-	We are still finalizing total donations, and will
-	report the final numbers in early February. Thank
-	you to everyone who supported our efforts in 2018.</p>
-
-      <p>OS Improvements</p>
-
-      <p>In the fourth quarter of 2018 six authors made a total of
-	315 commits to the FreeBSD development tree that were
-	identified as being sponsored by the FreeBSD
-	Foundation. These included staff members
-	Konstantin Belousov, Glen Barber, Li-Wen Hsu and
-	Ed Maste, and grant recipients Mateusz Guzik and
-	Mark Johnston.</p>
-
-      <p>Mateusz' work over the quarter consisted of identifying
-	and fixing bottlenecks in the FreeBSD kernel and
-	system libraries. The FreeBSD base system build,
-	and ports built via Poudriere, were used as
-	motivating cases.</p>
-
-      <p>Mark added an in-kernel Intel CPU microcode loader. This
-	simplifies and increases the robustness of
-	microcode updates, which is increasingly important
-	as mitigations for speculative execution
-	vulnerabilities are delivered in microcode.</p>
-
-      <p>Mark also fixed a number of issues relating to capsicum
-	support in base system utilities, implemented a
-	number of NUMA enhancements and bug fixes, and
-	fixed a number of high profile kernel bugs.</p>
-
-      <p>Ed committed a large number of tool chain fixes to LLVM's
-	lld linker and ELF Tool Chain components.</p>
-
-      <p>Along with several FreeBSD developers Ed worked on the
-	OpenSSL 1.1.1 import in preparation for FreeBSD
-	12.0, including incorporating OpenSSH and ntp
-	changes for compatibility. Ed also added
-	build-time knobs for to enable userland retpoline
-	and to enable BIND_NOW which
-	can be used as part of a vulnerability mitigation
-	strategy.</p>
-
-      <p>Continuous Integration and Quality Assurance</p>
-
-      <p>The Foundation provides a full-time staff member who is
-	working on improving our automated testing,
-	continuous integration, and overall quality
-	assurance efforts.</p>
-
-      <p>During the fourth quarter of 2018, Foundation employee
-	Li-Wen Hsu continuously worked on improving the
-	project's CI infrastructure, examining the failing
-	build and test cases, and work with other teams in
-	the project for their testing needs. In this
-	period, we also worked on collaboration with
-	external projects to improve their CI on FreeBSD.</p>
-
-      <p>See the FreeBSD CI section of this report for more
-	information.</p>
-
-      <p>Release Engineering</p>
-
-      <p>The Foundation provides a full-time staff member to lead
-	the release engineering efforts. This has provided
-	timely and reliable releases over the last five
-	years. During the fourth quarter of 2018, Glen
-	Barber led the the FreeBSD Release Engineering
-	team in continuing working on the 12.0-RELEASE
-	with the official announcement sent December 11.</p>
-
-      <p>See the FreeBSD Release Engineering Team section of this
-	report for more
-	information.</p>
-
-      <p>Supporting FreeBSD Infrastructure</p>
-
-      <p>The Foundation provides hardware and support to improve
-	the FreeBSD infrastructure. Last quarter, we
-	continued supporting FreeBSD hardware located
-	around the world.</p>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating
-	for the Project. This includes promoting work
-	being done by others with FreeBSD; producing
-	advocacy literature to teach people about FreeBSD
-	and help make the path to starting using FreeBSD
-	or contributing to the Project easier; and
-	attending and getting other FreeBSD contributors
-	to volunteer to run FreeBSD events, staff FreeBSD
-	tables, and give FreeBSD presentations.</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events,
-	and summits around the globe. These events can be
-	BSD-related, open source, or technology events
-	geared towards underrepresented groups. We support
-	the FreeBSD-focused events to help provide a venue
-	for sharing knowledge, to work together on
-	projects, and to facilitate collaboration between
-	developers and commercial users. This all helps
-	provide a healthy ecosystem. We support the
-	non-FreeBSD events to promote and raise awareness
-	of FreeBSD, to increase the use of FreeBSD in
-	different applications, and to recruit more
-	contributors to the Project.</p>
-
-      <p>Some of the advocacy and education work we did last
-	quarter includes:</p>
-
-      <ul>
-	<li>Organized, sponsored, and presented at the October 2018
-	FreeBSD Developers Summit in Santa Clara, CA</li>
-
-	<li>Sponsored and exhibited at MeetBSD 2018 in Santa Clara, CA</li>
-
-	<li>Exhibited for the first time at All Things Open in
-	Raleigh, NC</li>
-
-	<li>Exhibited and sponsored as an Industry Partner at LISA&#8217; 18
-	in Nashville, TN</li>
-
-	<li>Sponsored USENIX OSDI &#8216;18 in Carlsbad, CA as an Industry
-	Partner</li>
-
-	<li>Held an Intro to FreeBSD workshop and a &#8220;Why You Should
-	Contribute to FreeBSD&#8221; talk at the Rocky Mountain
-	Celebration of Women in Computing in Lakewood,
-	Colorado</li>
-      </ul>
-
-      <p>
-	We continued producing FreeBSD advocacy material to help
-	people promote FreeBSD around the world.</p>
-
-      <p>Read more about our conference adventures in the
-	conference recaps and trip reports in our monthly
-	newsletters: <a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">https://www.freebsdfoundation.org/news-and-events/newsletter/</a></p>
-
-      <p>We help educate the world about FreeBSD by publishing the
-	professionally produced FreeBSD Journal. We
-	recently announced that the FreeBSD Journal will
-	become a Free publication with the
-	January/February 2019 issue. <a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>.</p>
-
-      <p>You can find out more about events we attended and
-	upcoming events at <a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">https://www.FreeBSDfoundation.org/news-and-events/</a>.</p>
-
-      <p>For a look back at all of efforts in 2018, please see the
-	year-end video at <a href="https://www.freebsdfoundation.org/blog/thank-you-for-supporting-freebsd/" shape="rect">https://www.freebsdfoundation.org/blog/thank-you-for-supporting-freebsd/</a>.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them. We also provide
-	legal support for the core team to investigate
-	questions that arise. Last quarter, we approved 6
-	requests to use the Trademark.
-	Go to <a href="http://www.FreeBSDfoundation.org" shape="rect">http://www.FreeBSDfoundation.org</a>
-	to find out how we support FreeBSD and how we can
-	help you!</p>
-
-    <hr /><h2><a name="FreeBSD-Graphics-Team-status-report" href="#FreeBSD-Graphics-Team-status-report" id="FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop" title="https://github.com/FreeBSDDesktop">Project GitHub page</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop" title="Project GitHub page">https://github.com/FreeBSDDesktop</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:x11@freebsd.org">x11@freebsd.org</a>&gt;
-	<br />
-	Contact: Niclas Zeising &lt;<a href="mailto:zeising@freebsd.org">zeising@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD X11/Graphics team maintains the lower levels
-	of the FreeBSD graphics
-	stack.
-	This includes graphics drivers, graphics libraries such as
-	the
-	MESA OpenGL implementation, the X.org xserver with related
-	libraries and
-	applications, and Wayland with related libraries and
-	applications.</p>
-
-      <p>In the forth quarter, the team focused on stablizing the
-	graphics drivers and
-	ports for the FreeBSD 12.0 release.
-	The graphics drivers have been updated with new versions
-	for both FreeBSD 11.2
-	and FreeBSD 12.0.
-	The ports have been renamed in order to make it clearer
-	which version of a port
-	runs on which version on FreeBSD.
-	We also created a new meta port,
-	<tt>graphics/drm-kmod</tt>, which will install the
-	correct driver based on FreeBSD version and architecture.
-	Moving forward this is the recommended way to install the
-	FreeBSD graphics
-	drivers.</p>
-
-      <p>The DRM drivers themselves are named
-	<tt>graphics/drm-current-kmod</tt> and
-	<tt>graphics/drm-fbsd12.0-kmod</tt> for CURRENT and 12.0
-	respectively, both of which
-	have been updated to use the 4.16 Linux Kernel source.
-	For FreeBSD 11.2 we have
-	<tt>graphics/drm-fbsd11.2-kmod</tt> which uses the
-	4.11 Linux
-	Kernel source.
-	Finally, we created <tt>graphics/drm-legacy-kmod</tt>,
-	which works on FreeBSD 12.0 and
-	CURRENT.
-	This is a copy of the legacy drivers from the FreeBSD base
-	system.
-	This work will make it possible for us to remove the drm2
-	code from CURRENT,
-	something we are planning to do in early February.
-	A remnant of the drm2 code will remain in the base after
-	this due to an
-	unresolved dependency for the NVIDIA Tegra ARM chip.
-	Plans for its migration are expected to be finalized in
-	first quarter in 2019.</p>
-
-      <p>Support for i386 and PowerPC 64 has been added to the drm
-	kernel drivers.
-	This is currently in an alpha state.</p>
-
-      <p>Wayland has been enabled by default in the ports tree,
-	meaning that all packages
-	are build with Wayland support enabled.
-	This makes it much easier to use and test Wayland.</p>
-
-      <p>Support for VMware graphics pass through has been added to
-	the kernel driver.
-	Support for this is still missing in
-	<tt>graphcs/mesa-dri</tt> though, so it currently
-	does not work out of the box.</p>
-
-      <p>The input stack has been updated and is now for the most
-	part current with
-	upstream.
-	Evdev headers were split off from
-	<tt>multimedia/v4l_compat</tt> into their own
-	port,
-	<tt>devel/evdev-proto</tt>.
-	This makes it easier to update those headers and keep them
-	current with
-	upstream, as needed.
-	The input stack is still an area where more work needs to
-	be done to make it
-	easier to use various input devices with X and Wayland on
-	FreeBSD.</p>
-
-      <p>Several meetings has been held over the course of the
-	period.
-	Meeting notes have been sent out to the public
-	<tt>x11@FreeBSD.org</tt> mailing list.</p>
-
-      <p>People who are interested in helping out can find us on
-	the x11@FreeBSD.org
-	mailing list, or on our gitter chat: <a href="https://gitter.im/FreeBSDDesktop/Lobby" shape="rect">https://gitter.im/FreeBSDDesktop/Lobby</a>.
-	We
-	are also available in #freebsd-xorg on EFNet.</p>
-
-      <p>We also have a team area on GitHub where our work
-	repositories can be found:
-	<a href="https://github.com/FreeBSDDesktop" shape="rect">https://github.com/FreeBSDDesktop</a></p>
-
-      <p></p>
-
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2>
-      <p>Category: team</p>
-
-      <p></p>
-
-      <p>The FreeBSD Release Engineering Team is responsible for
-	setting
-	and publishing release schedules for official project
-	releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>During the fourth quarter of 2018, the FreeBSD Release
-	Engineering team
-	continued working on the 12.0-RELEASE. The
-	<tt>stable/12</tt> branch was created
-	on October 19, with the first BETA build being started
-	shortly after. The
-	release cycle slipped slightly with the addition of
-	12.0-BETA4, after which
-	the <tt>releng/12.0</tt> branch was created on November
-	16.</p>
-
-      <p>The remainder of the release cycle continued relatively
-	smoothly for the
-	duration of the release candidate (RC) phase, with the
-	final release builds
-	starting December 7, and the official announcement sent
-	December 11.</p>
-
-      <p>Throughout the quarter, several development snapshots
-	builds were released
-	for the <tt>head</tt> and <tt>stable/11</tt> branches.</p>
-
-      <p>Much of this work was sponsored by the FreeBSD Foundation.</p>
-
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team"&gt;Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team&quot;&gt;Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The number of ports in the last quarter shrunk a bit to
-	32,900. At the end of
-	the quarter there were 2365 open port PRs of which a small
-	500 were unassigned.
-	The last quarter saw 7333 commits from 174 committers.
-	This means that more
-	port PRs were resolved than last quarter and the number of
-	commits remained
-	approximately the same.</p>
-
-      <p>During the last quarter, we welcomed Alexandre C.
-	Guimar�es (rigoletto@) and
-	Vin�cius Zavam (egypcio@). The port commit bits of Alberto
-	Villa (avilla@),
-	Lars Thegler (lth@), Dryice Dong Liu (dryice@), Ion-Mihai
-	Tetcu (itetcu@),
-	Gabor Pali (pgj@), Tom Judge (tj@), Ollivier Robert
-	(roberto@), and Maxim
-	Sobolev (sobomax@) were taken in for safekeeping.</p>
-
-      <p>The number of commit bits safekept is higher than usual
-	because for port commit
-	bits the idle timeout changed from 18 months to 12 months.</p>
-
-      <p>Some default versions were changed:</p>
-
-      <ul>
-	<li>PHP from 7.1 to 7.2</li>
-
-	<li>Perl5 from 5.26 to 5.28</li>
-
-	<li>Ruby from 2.4 to 2.5</li>
-
-	<li>For LLVM, version 7.0 is now supported as a default
-	version.</li>
-      </ul>
-
-      <p>
-	Other big changes are:</p>
-
-      <ul>
-	<li>info files are stored in the share/info directory just as
-	other
-	operating systems do.</li>
-
-	<li>PyQt ports can now be installed concurrently.</li>
-
-	<li>As FreeBSD 10 reached its end of life, support for this
-	branch has been
-	removed from the Ports Collection. People still requiring
-	FreeBSD 10
-	support can use the RELEASE\_10\_EOL tag.</li>
-
-	<li>USES=cmake now defaults to outsource</li>
-
-	<li>KDE 4 has reached its end-of-life and has been removed
-	from the Ports
-	Collection.</li>
-      </ul>
-
-      <p>
-	Eager as ever, antoine@ ran 36 exp-runs this quarter to
-	ensure major port
-	upgrades were correct.</p>
-
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="amd64-Usermode-Protection-Keys" href="#amd64-Usermode-Protection-Keys" id="amd64-Usermode-Protection-Keys">amd64 Usermode Protection Keys</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D18893" title="https://reviews.freebsd.org/D18893">The patch</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D18893" title="The patch">https://reviews.freebsd.org/D18893</a></td></tr></table><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@freebsd.org">kib@freebsd.org</a>&gt;
-	</p>
-      <p>Skylake Xeons have a new feature in 4-level paging
-	implementation
-	called Usermode Protection Keys. It is a complementary
-	page access
-	permission management mechanism, which provides very
-	low-overhead
-	disabling of all accesses or only modifications, on
-	per-page basis.</p>
-
-      <p>Each thread of execution gets 16 slots, called protection
-	keys, while
-	each userspace page mapping is tagged with one key.
-	Processor
-	provides a new 32bit register PKRU, which holds access and
-	modification disable bits per key, the PKRU register is
-	automatically
-	context-switched, and managed by userspace using RDPKRU
-	and WRPKRU
-	instructions. See Intel SDM rev. 68 Vol 3 4.6.2 Protection
-	Keys for
-	further details.</p>
-
-      <p>Since a key index must be always specified, this makes the
-	key zero a
-	default key, which permissions are tricky to modify
-	without breaking
-	the process environment. The rest 15 keys are usable, for
-	instance
-	process might put some sensitive data like decoded private
-	key into
-	the key protected area, and only enable access on as
-	needed basis,
-	without issuing costly mprotect(2) syscall. Note that
-	permissions are
-	enforced even for kernel access, so sneaky read(2) from
-	other thread
-	is subject to the same permission checks.</p>
-
-      <p>I implemented the support for the amd64 pmap and provided
-	convenient
-	wrappers in libc both for 64bit and 32bit processes.
-	Prototypes for
-	the API are presented below and their use should be
-	obvious from the
-	explanation.</p>
-
-      <p>int x86_pkru_get_perm(unsigned int keyidx, int <tt>access,
-	int </tt>modify);
-	int x86_pkru_set_perm(unsigned int keyidx, int access, int
-	modify);
-	int x86_pkru_protect_range(void *addr, unsigned long len,
-	unsigned int keyidx, int flag);
-	int x86_pkru_unprotect_range(void *addr, unsigned long
-	len);</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="bhyve---Live-Migration" href="#bhyve---Live-Migration" id="bhyve---Live-Migration">bhyve - Live Migration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve">Github wiki - How to Warm Migrate a bhyve guest</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve" title="Github wiki - How to Warm Migrate a bhyve guest">https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration">Github - Warm Migration branch</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="Github - Warm Migration branch">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev">Github - Live Migration branch</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev" title="Github - Live Migration branch">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev</a></td></tr></table><p>
-	Contact: Elena Mihailescu &lt;<a href="mailto:elenamihailescu22@gmail.com">elenamihailescu22@gmail.com</a>&gt;
-	<br />
-	Contact: Darius Mihai &lt;<a href="mailto:dariusmihaim@gmail.com">dariusmihaim@gmail.com</a>&gt;
-	<br />
-	Contact: Sergiu Weisz &lt;<a href="mailto:sergiu121@gmail.com">sergiu121@gmail.com</a>&gt;
-	<br />
-	Contact: Mihai Carabas &lt;<a href="mailto:mihai@freebsd.org">mihai@freebsd.org</a>&gt;
-	</p>
-      <p>The Migration feature uses the Save/Restore feature to
-	migrate a bhyve guest
-	from a FreeBSD host to another FreeBSD host. To migrate a
-	bhyve guest,
-	one needs to start an empty guest on the destination host
-	from a shared guest
-	image using the bhyve tool with the <tt>-R</tt> option
-	followed by the source host
-	IP and the port to listen to migration request. On the
-	source host, the
-	migration is started by executing the bhyvectl command
-	with the <tt>--migrate</tt>
-	or <tt>--migrate-live</tt> option, followed by the
-	destination host IP and the
-	port to send to the messages.</p>
-
-      <p>New features added:</p>
-
-      <ul>
-	<li>Prove that live migration cannot be implemented using the
-	FreeBSD's Copy-on-Write mechanism;</li>
-
-	<li>Add <tt>--migrate-live</tt> option to bhyvectl;</li>
-
-	<li>Add additional message exchange between source and
-	destination host to establish the migration type
-	and the number of rounds;</li>
-
-	<li>Implement a dirty-bit approach for live migrating the
-	guest's wired memory;</li>
-      </ul>
-
-      <p>
-	Future tasks:</p>
-
-      <ul>
-	<li>Clear the dirty bit after each migration round;</li>
-
-	<li>Extend live migration to highmem segment;</li>
-
-	<li>Extend live migration to unwired memory;</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by Matthew Grooms.</p><hr /><h2><a name="bhyve---Save/Restore" href="#bhyve---Save/Restore" id="bhyve---Save/Restore">bhyve - Save/Restore</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration">Github repository for the save/restore and migration features</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="Github repository for the save/restore and migration features">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve">Github wiki - How to Save and Restore a bhyve guest</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve" title="Github wiki - How to Save and Restore a bhyve guest">https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix">Github wiki - Suspend/resume test matrix</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix" title="Github wiki - Suspend/resume test matrix">https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix</a></td></tr></table><p>
-	Contact: Elena Mihailescu &lt;<a href="mailto:elenamihailescu22@gmail.com">elenamihailescu22@gmail.com</a>&gt;
-	<br />
-	Contact: Darius Mihai &lt;<a href="mailto:dariusmihaim@gmail.com">dariusmihaim@gmail.com</a>&gt;
-	<br />
-	Contact: Sergiu Weisz &lt;<a href="mailto:sergiu121@gmail.com">sergiu121@gmail.com</a>&gt;
-	<br />
-	Contact: Mihai Carabas &lt;<a href="mailto:mihai@freebsd.org">mihai@freebsd.org</a>&gt;
-	</p>
-      <p>The Save/Restore for bhyve feature is a suspend and resume
-	facility added to the
-	FreeBSD/amd64's hypervisor, bhyve. The bhyvectl tool is
-	used to save the guest
-	state in three files (a file for the guest memory, a file
-	for devices' and CPU's
-	state and another one for some metadata that are used in
-	the restore process).
-	To suspend a bhyve guest, the bhyvectl tool must be run
-	with the <tt>--suspend
-	&lt;state_file_name&gt;</tt>
-	option followed by the guest name.</p>
-
-      <p>To restore a bhyve guest from a checkpoint, one simply has
-	to add the <tt>-r</tt> option
-	followed by the main state file (the same file that was
-	given to the <tt>--suspend</tt>
-	option for bhyvectl) when starting the VM.</p>
-
-      <p>New features added:</p>
-
-      <ul>
-	<li>Improve timers' save and restore state feature;</li>
-
-	<li>Fix synchronization issues related to the ahci device save
-	and restore state feature;</li>
-
-	<li>Add suspend/resume support for Windows guests;</li>
-
-	<li>Refactor save and restore code - save component's state
-	field by field</li>
-      </ul>
-
-      <p>
-	Future tasks:</p>
-
-      <ul>
-	<li>Open ticket on Phabricator;</li>
-
-	<li>Add suspend/resume support for nvme;</li>
-
-	<li>Add suspend/resume support for virtio-console;</li>
-
-	<li>Add suspend/resume support for virtio-scsi;</li>
-
-	<li>Add TSC offseting for restore for AMD CPUs;</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by Matthew Grooms; iXsystems;.</p><hr /><h2><a name="Capsicum" href="#Capsicum" id="Capsicum">Capsicum</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Capsicum" title="https://wiki.FreeBSD.org/Capsicum">Capsicum Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Capsicum" title="Capsicum Wiki Page">https://wiki.FreeBSD.org/Capsicum</a></td></tr></table><p>
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mariusz Zaborski &lt;<a href="mailto:oshogbo@FreeBSD.org">oshogbo@FreeBSD.org</a>&gt;
-	</p>
-      <p>The major improvement in Capsicum is introducing a Casper
-	service
-	fileargs, which is an easy way helps to sandbox the utils
-	which need
-	access to the filesystem. There are several examples of
-	usage fileargs
-	in applications like brandelf(1), wc(1), savecore(1),
-	head(1) and
-	strings(1). The fileargs service also helps to bring new
-	features to
-	the bhyve like audio device which is secured using
-	Capsicum.</p>
-
-      <p>Another big step was introducing a private Casper service
-	and
-	sandboxing the rtsold(8) and rtsol(8).</p>
-
-      <p>Next major improvement, which is still under the review,
-	is rewriting
-	the sysctl service. The new sysctl service will allow in
-	an easy way
-	to use cap_sysctl() and cap_sysctlnametomib().</p>
-
-    <hr /><h2><a name="Collection-of-vt(4)-color-schemes" href="#Collection-of-vt(4)-color-schemes" id="Collection-of-vt(4)-color-schemes">Collection of vt(4) color schemes</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/mbadolato/iTerm2-Color-Schemes" title="https://github.com/mbadolato/iTerm2-Color-Schemes">iTerm2-Color-Schemes repository with previews</a></td><td>
-	    URL: <a href="https://github.com/mbadolato/iTerm2-Color-Schemes" title="iTerm2-Color-Schemes repository with previews">https://github.com/mbadolato/iTerm2-Color-Schemes</a></td></tr><tr><td><a href="https://github.com/mbadolato/iTerm2-Color-Schemes/tree/master/freebsd_vt" title="https://github.com/mbadolato/iTerm2-Color-Schemes/tree/master/freebsd_vt">iTerm2-Color-Schemes vt color schemes</a></td><td>
-	    URL: <a href="https://github.com/mbadolato/iTerm2-Color-Schemes/tree/master/freebsd_vt" title="iTerm2-Color-Schemes vt color schemes">https://github.com/mbadolato/iTerm2-Color-Schemes/tree/master/freebsd_vt</a></td></tr></table><p>
-	Contact: Tobias Kortkamp &lt;<a href="mailto:tobik@FreeSD.org">tobik@FreeSD.org</a>&gt;
-	</p>
-      <p>Since 11.2-RELEASE vt(4) supports setting custom color
-	schemes via
-	the <tt>kern.vt.color.X.rgb</tt> tunables. This is nice
-	but what was
-	missing were some ready to use themes.</p>
-
-      <p>iTerm2-Color-Schemes is a collection of around 200 color
-	schemes
-	for various terminals. It has recently gained support for
-	vt(4).
-	Customizing your console is now as easy as copy and
-	pasting your
-	favorite theme to <tt>/boot/loader.conf</tt> or
-	<tt>/boot/loader.conf.local</tt>.</p>
-
-      <p></p>
-
-    <hr /><h2><a name="i386-PAE-Pagetables" href="#i386-PAE-Pagetables" id="i386-PAE-Pagetables">i386 PAE Pagetables</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D18894" title="https://reviews.freebsd.org/D18894">https://reviews.freebsd.org/D18894</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D18894" title="https://reviews.freebsd.org/D18894">https://reviews.freebsd.org/D18894</a></td></tr></table><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@freebsd.org">kib@freebsd.org</a>&gt;
-	</p>
-      <p>The i386 architecture (in modern terms, x86 architecture
-	in 32bit
-	protected mode), has supported hardware execute-disable
-	since early
-	200x. The only problem preventing the i386 FreeBSD kernel
-	from using
-	it was that default page table format used by the kernel
-	is 2-level
-	paging, while nx bit is only available for PAE (2.5
-	levels) page table
-	structures. PAE option is too intrusive, it changes both
-	vm_paddr_t
-	and bus_addr_t to 64bit, which is not too friendly to many
-	drivers.</p>
-
-      <p>I tried to provide PAE_PAGETABLES kernel option which only
-	changed
-	page table format, without affecting vm_paddr_t or
-	bus_addr_t, thus
-	keeping kernel/driver interfaces intact. But I was not
-	able to make
-	i386 releases carry two kernels, one to support relic
-	hardware which
-	cannot use PAE pagetables, and another for newer machines.</p>
-
-      <p>So I finally did a merge which makes single i386 kernel
-	carry two pmap
-	modules, one for PAE and one for old two-level paging
-	structures.
-	Also I did not find a reason to not expand vm_paddr_t,
-	while I have
-	to keep bus_addr_t at 32bit.</p>
-
-      <p>With a single boot-time knob, i386 kernel can now also
-	utilize up to
-	24G or memory, if drivers correctly use busdma(9). I tried
-	to fix
-	iflib(4) and ahci(4) so that the most common hardware
-	work, but I
-	cannot do the pass over the whole tree.</p>
-
-      <p>Hopefully, together with earlier 4/4G split work, this
-	gives enough
-	life for i386 kernel.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Improving-FreeBSD-boot-security" href="#Improving-FreeBSD-boot-security" id="Improving-FreeBSD-boot-security">Improving FreeBSD boot security</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base/head/sys/dev/tpm/tpm20.c?revision=342084&amp;nview=markup" title="https://svnweb.freebsd.org/base/head/sys/dev/tpm/tpm20.c?revision=342084&amp;nview=markup">TPM 2.0 driver</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base/head/sys/dev/tpm/tpm20.c?revision=342084&amp;nview=markup" title="TPM 2.0 driver">https://svnweb.freebsd.org/base/head/sys/dev/tpm/tpm20.c?revision=342084&amp;nview=markup</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D18798" title="https://reviews.freebsd.org/D18798">Loader Secure Boot support</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D18798" title="Loader Secure Boot support">https://reviews.freebsd.org/D18798</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D18797" title="https://reviews.freebsd.org/D18797">Secure Boot library</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D18797" title="Secure Boot library">https://reviews.freebsd.org/D18797</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D18799" title="https://reviews.freebsd.org/D18799">binsign utility</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D18799" title="binsign utility">https://reviews.freebsd.org/D18799</a></td></tr></table><p>
-	Contact: Michal Stanek &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Kornel Duleba &lt;<a href="mailto:mindal@semihalf.com">mindal@semihalf.com</a>&gt;
-	</p>
-      <p>FreeBSD now supports TPM 2.0 devices. TPM (Trusted
-	Platform Module) is a discrete chip which provides
-	secure computation and secure NVRAM storage. It is
-	most
-	commonly associated with Measured Boot i.e. providing hash
-	measurements of boot elements such as firmware
-	images and boot configuration to the OS. In
-	FreeBSD,
-	the TPM can be used to strengthen security of services
-	such as Strongswan IPsec, SSH or TLS by performing
-	cryptographic operations in the TPM chip itself
-	using
-	embedded keys inaccessible to software. TPM facilities
-	such as secure NVRAM storage, data sealing, random
-	number generation and others are also available to
-	any
-	software via the IBM TSS library.</p>
-
-      <p>UEFI Secure Boot is a technology which provides
-	authentication of images that are executed on the
-	host during boot. This prevents persistence of
-	unauthorized malicious boot code such as rootkits. UEFI
-	stores a list of allowed and blacklisted
-	certificates and verifies signatures of all boot
-	images and
-	UEFI applications before they are executed on the CPU.
-	Semihalf has developed support for X509
-	certificates and signature
-	verification code in EFI loader with the help of the
-	minimal BearSSL library. Lists of allowed and
-	forbidden certificates are retrieved from UEFI
-	environmental
-	variables. This allows users to sign kernel binaries with
-	a self-signed certificate, append the signature
-	and let the loader verify its authenticity.</p>
-
-      <p>UEFI Secure Boot support code will most likely be
-	integrated with sjg's Veriexec support which is
-	currently being reviewed on Phabricator.</p>
-
-      <p>Semihalf is also working on improving security of Veriexec
-	by moving manifest signature verification to the
-	kernel.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by Stormshield.</p><hr /><h2><a name="pfsync-performance-improvement" href="#pfsync-performance-improvement" id="pfsync-performance-improvement">pfsync performance improvement</a></h2><p>
-	Contact: Kristof Provost &lt;<a href="mailto:kp@freebsd.org">kp@freebsd.org</a>&gt;
-	</p>
-      <p>While pf itself can operate on multiple states
-	simultaneously
-	(on different cores), pfsync could not. It used a single
-	PFSYNC_LOCK.
-	This greatly reduced throughput on multicore systems as
-	soon as pfsync
-	was loaded.</p>
-
-      <p>This was improved by splitting the pfsync queues into
-	buckets, based on the
-	state ID. This ensures that updates for a given connection
-	always end up
-	in the same bucket, allowing pfsync to still collapse
-	multiple
-	updates into one, while allowing multiple cores to proceed
-	at the same
-	time.
-	The buckets are independently locked, allowing multiple
-	cores to proceed at once.</p>
-
-      <p>The number of buckets is tunable, but defaults to twice
-	the number of cpus.
-	Benchmarking has shown improvement of 30 to 100% depending
-	on hardware and setup.</p>
-
-      <p>During this effort several vnet-related issues were fixed
-	as well, and a basic
-	pfsync test case was added.</p>
-
-      <p>This was committed into head in r341646, and later merged
-	into stable/12 and stable/11.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by Orange Business Services.</p><hr /><h2><a name="PWM-Kernel-API-and-userland-utility" href="#PWM-Kernel-API-and-userland-utility" id="PWM-Kernel-API-and-userland-utility">PWM Kernel API and userland utility</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>A new subsystem was added to the kernel for PWM drivers to
-	register themselves.
-	In pair with the kernel subsystem, a pwm(8) utility is
-	also available so users
-	can configure PWM on their embedded boards.
-	For now the only PWM driver compatible with this subsystem
-	is for ARM Allwinner SoCs.</p>
-
-      <p></p>
-
-    <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="Broadcom-ARM64-SoC-support" href="#Broadcom-ARM64-SoC-support" id="Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></h2><p>
-	Contact: Michal Stanek &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p>
-      <p>Semihalf has recently started work on FreeBSD support for
-	BCM5871X SoC series.</p>
-
-      <p>
-	These are quad-core 64-bit ARMv8 Cortex-A57 communication
-	processors targeted for
-	networking applications such as 10G routers, gateways,
-	control plane processing and NAS. Initial support
-	will include iProc PCIe, internal BNXT Ethernet
-	controller, OTP (One Time Programmable memory)
-	and crypto engine acceleration for IPsec offloading. This
-	work is expected to be ready for FreeBSD-HEAD
-	before Q3 2019.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by Juniper.</p><hr /><h2><a name="DTS-Update" href="#DTS-Update" id="DTS-Update">DTS Update</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>DTS files (Device Tree Sources) were updated to be on par
-	with Linux 4.20 for
-	head and 4.19 for the 12-STABLE branch.</p>
-
-      <p>The DTS are now compiled for some arm64 boards, as the one
-	present in U-Boot are
-	not always up-to-date.</p>
-
-    <hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	</p>
-      <p>ENA (Elastic Network Adapter) is the smart NIC which is
-	used in the virtualized
-	environment of Amazon Web Services (AWS). It supports
-	multiple queues and can
-	handle up to 25 Gb/s, depending on the instance type on
-	which it is used.</p>
-
-      <p>ENAv2 has been under development for FreeBSD, similar to
-	Linux OS and DPDK.
-	New changes are including:</p>
-
-      <ul>
-	<li>Upgrade of the HAL to the version supporting ENAv2</li>
-
-	<li>Optimization of the logging on the Tx path</li>
-
-	<li>LLQ (Low Latency Queue) feature, which is reducing latency
-	on instances supporting ENAv2</li>
-
-	<li>Optimization of the locks on hot paths by adding Tx queue
-	management and lockless Rx queue cleanup</li>
-
-	<li>Fixes on the error handling paths</li>
-
-	<li>Use bitfield for tracking device states</li>
-
-	<li>Add additional doorbells on Tx path</li>
-
-	<li>Add queue depth setup in the runtime and allows Rx queue
-	depth to be configured independently</li>
-
-	<li>And more minor bug fixes and code reorganization</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Internal review and validation</li>
-
-	<li>Upstream of the patches</li>
-      </ul>
-
-      <p></p>
-
-      <p></p>
-
-    <p>This project was sponsored by Amazon.com Inc.</p><hr /><h2><a name="FreeBSD-on-Power9-(ppc64)-Parity" href="#FreeBSD-on-Power9-(ppc64)-Parity" id="FreeBSD-on-Power9-(ppc64)-Parity">FreeBSD on Power9 (ppc64) Parity</a></h2>
-      <ul>
-	<li>NMI semantics: NMIs need to be emulated by only soft
-	disabling interrupts,
-	disabling interrupts blocks all interrupts except machine
-	check exceptions
-	and system resets.</li>
-
-	<li>Superpage support is stable and on by default in the
-	POWER9BSD staging branch</li>
-
-	<li>NUMA support: Parse OFW and set up appropriate structures
-	for memory
-	to be allocated from the correct domain and interrupts to
-	be bound to the
-	correct socket.</li>
-
-	<li>LKPI support for POWER9, Drm-next supports radeonkms. Some
-	additional big
-	endian changes required for amdgpu.</li>
-
-	<li>Interrupt handling improvements resulting in up to a 10%
-	reduction in
-	buildkernel time.</li>
-
-	<li>Cached XICS IPI vector</li>
-
-	<li>Added XIVE exploitation mode driver</li>
-
-	<li>Rust support in review.</li>
-
-	<li>Successfully booted an LLVM compiled kernel.</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="FreeBSD/RISC-V-update" href="#FreeBSD/RISC-V-update" id="FreeBSD/RISC-V-update">FreeBSD/RISC-V update</a></h2><p>
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@freebsd.org">br@freebsd.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@freebsd.org">markj@freebsd.org</a>&gt;
-	</p>
-      <p>FreeBSD/RISC-V is getting more mature during last quarter.</p>
-
-      <p>We have optimised RISC-V copyin(9)/copyout(9) routines.
-	They now support word-sized copies where possible
-	to dramatically increase speed of copying data
-	between kernel and userspace.</p>
-
-      <p>We made a series of improvements and bug fixes to pmap
-	support (machine-dependent portion of virtual
-	memory subsystem). This part was not touched
-	during the last years, and is now getting
-	attention.</p>
-
-      <p>RISC-V GENERIC kernel gets support for witness(4) (The
-	FreeBSD lock validation facility).</p>
-
-      <p>The British company <a href="https://www.embecosm.com/" shape="rect">Embecosm</a> has
-	reported that they were able to boot FreeBSD on
-	real hardware -- a SiFive Unleashed board. The
-	support is limited to a single core only. We are
-	expecting patches from them.</p>
-
-    <hr /><h2><a name="libvdsk---QCOW2-implementation" href="#libvdsk---QCOW2-implementation" id="libvdsk---QCOW2-implementation">libvdsk - QCOW2 implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_libvdsk" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_libvdsk">Github - Libvdsk QCOW2 branch</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_libvdsk" title="Github - Libvdsk QCOW2 branch">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_libvdsk</a></td></tr></table><p>
-	Contact: Sergiu Weisz &lt;<a href="mailto:sergiu121@gmail.com">sergiu121@gmail.com</a>&gt;
-	<br />
-	Contact: Marcelo Araujo &lt;<a href="mailto:araujo@freebsd.org">araujo@freebsd.org</a>&gt;
-	<br />
-	Contact: Mihai Carabas &lt;<a href="mailto:mihai@freebsd.org">mihai@freebsd.org</a>&gt;
-	</p>
-      <p>New features added:</p>
-
-      <ul>
-	<li>Extend libvdsk to make it easier to implement new formats;</li>
-
-	<li>Implement read/write/probe functionalities in order to
-	parse QCOW2 image files;</li>
-      </ul>
-
-      <p>
-	Future tasks:</p>
-
-      <ul>
-	<li>Add support for Copy-On-Write;</li>
-
-	<li>Add support for multiple snapshots;</li>
-
-	<li>Integrate libvdsk in bhyve</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by Matthew Grooms.</p><hr /><h2><a name="Marvell-8K-SoC-support" href="#Marvell-8K-SoC-support" id="Marvell-8K-SoC-support">Marvell 8K SoC support</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Luis Octavio O Souza &lt;<a href="mailto:loos@FreeBSD.org">loos@FreeBSD.org</a>&gt;
-	</p>
-      <p>Support for booting FreeBSD on Marvell 8K SoC (present on
-	the MacchiatoBin for example)
-	has been commited.
-	As of today, clocks, gpio, thermal, sdcard/eMMC drivers has
-	been commited.
-	SATA and USB were already working.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by Rubicon Communications, LLC ("Netgate").</p><hr /><h2><a name="Pinebook-SDCard-Image" href="#Pinebook-SDCard-Image" id="Pinebook-SDCard-Image">Pinebook SDCard Image</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>SDCard image is now produced for the Pinebook.
-	By default the console is directed in the EFI Framebuffer
-	and the serial
-	console.</p>
-
-      <p></p>
-
-    <hr /><h2><a name="RockChip-Support" href="#RockChip-Support" id="RockChip-Support">RockChip Support</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p>
-      <p>Early support for the RockChip RK3399 has been commited.
-	For now it's only possible to netboot boards (Like the
-	RockPro64).
-	Original patch was submitted by Greg V
-	&lt;greg@unrelenting.technology&gt;.</p>
-
-      <p>Support for the RK805 and RK808 PMIC (Power Management IC)
-	has been added.
-	This allow changing some regulators voltage such as the
-	cores one so cpufreq
-	support works. You can change core frequencies with sysctl
-	or powerd(8).</p>
-
-    <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="FreeBSD-KDE-status-report" href="#FreeBSD-KDE-status-report" id="FreeBSD-KDE-status-report">FreeBSD KDE status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:adridg@FreeBSD.org">adridg@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Tobias C. Berner &lt;<a href="mailto:tcberner@FreeBSD.org">tcberner@FreeBSD.org</a>&gt;
-	</p>
-      <p>First of all, we removed KDE 4 from the ports tree this
-	quarter.
-	Qt4 will follow it by the end of march.</p>
-
-      <p>Thanks to the update of libinput in ports we could finally
-	update Plasma Desktop
-	past 5.12, and are now again in sync with the upstream
-	releases.</p>
-
-      <p>KDE Frameworks and Applications were also kept in sync
-	with upstream.</p>
-
-      <p>We've also updated Qt5 to 5.12 -- with QtWebEngine still
-	hanging on on 5.9.5
-	for now, but thanks to a new contributor we should have
-	5.12 by the end of Q1.</p>
-
-      <p>In the background we changed the default behavior of
-	cmake in the ports tree
-	to default to outsource builds.</p>
-
-      <p>People who are willing to contribute can find us on
-	#kde-freebsd on freenode,
-	and the kde@FreeBSD.org mailing list. Further we accept
-	pull-requests and
-	contributions on github.com/freebsd/freebsd-ports-kde.</p>
-
-      <p></p>
-
-    <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><p>Objects that defy categorization.</p><br /><h2><a name="BSD-PL" href="#BSD-PL" id="BSD-PL">BSD PL</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bsd-pl.org/" title="https://bsd-pl.org/">https://bsd-pl.org/</a></td><td>
-	    URL: <a href="https://bsd-pl.org/" title="https://bsd-pl.org/">https://bsd-pl.org/</a></td></tr></table><p>
-	Contact: Official &lt;<a href="mailto:meetup@bsd-pl.org">meetup@bsd-pl.org</a>&gt;
-	<br />
-	Contact: Konrad Witaszczyk &lt;<a href="mailto:def@FreeBSD.org">def@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mariusz Zaborski &lt;<a href="mailto:oshogbo@FreeBSD.org">oshogbo@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jaros&#322;aw &#379;urek &lt;<a href="mailto:contact@zurek.pro">contact@zurek.pro</a>&gt;
-	</p>
-      <p>The Polish BSD User group is an initiative promoting
-	systems from the
-	BSD family. We organize both meetings and as well as
-	tutorial
-	sessions. In general, we have three presentations which
-	last around 15
-	minutes. Afterwards there&#8217;s an open discussions about
-	topics related
-	to operating systems and security. There&#8217;s something for
-	everybody,
-	and the first presentation is about something connected to
-	BSD and
-	it&#8217;s aimed at beginners. The second presentation is for
-	more advanced
-	BSD users but the final talk is more general and not
-	connected to BSD.
-	Usually it covers an interesting topic related to
-	technology. Everyone
-	can suggest a subject for the presentations and
-	discussions. Some
-	presentations from the past were about: ZFS checkpoints,
-	GELI,
-	FreeNAS, PAM, DTrace, Yubikey, Pytest, ZeroTrust, Jenkins
-	and the
-	iocage training session. Hope to see you there!</p>
-
-    <hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System" href="#ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System" id="ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System">ClonOS: virtualization platform on top of FreeBSD Operating System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://clonos.tekroutine.com" title="https://clonos.tekroutine.com">ClonOS Main Site</a></td><td>
-	    URL: <a href="https://clonos.tekroutine.com" title="ClonOS Main Site">https://clonos.tekroutine.com</a></td></tr></table><p>
-	Contact: Oleg Ginzburg &lt;<a href="mailto:olevole@olevole.ru">olevole@olevole.ru</a>&gt;
-	</p>
-      <p>What is ClonOS?</p>
-
-      <p>ClonOS is a turnkey open-source platform based on FreeBSD
-	and the CBSD
-	framework. ClonOS offers a complete web UI for an easy
-	control, deployment
-	and management of FreeBSD jails containers and bhyve/Xen
-	hypervisor virtual
-	environments.</p>
-
-      <p>ClonOS is currently the only available platform which
-	allows both Xen and bhyve
-	hypervisors to coexist on the same host. Since ClonOS is a
-	FreeBSD-based
-	platform, it has the ability to create and manage jails
-	natively, allowing
-	you to run FreeBSD applications without losing
-	performance.</p>
-
-      <p>Features:</p>
-
-      <ul>
-	<li>easy management via web UI interface</li>
-
-	<li>bhyve management (create, delete VM)</li>
-
-	<li>Xen management (create, delete VM) [coming soon, roadmap]</li>
-
-	<li>connection to the "physical" guest console via VNC from
-	the browser or
-	directly</li>
-
-	<li>real time system monitoring</li>
-
-	<li>access to load statistics through SQLite3 and beanstalkd</li>
-
-	<li>support for ZFS features (cloning, snapshots)</li>
-
-	<li>import/export of virtual environments</li>
-
-	<li>public repository with virtual machine templates</li>
-
-	<li>puppet-based helpers for configuring popular services</li>
-      </ul>
-
-      <p>
-	ClonOS 2018Q4 Status Report</p>
-
-      <p>During this period, work was carried out to:</p>
-
-      <ul>
-	<li>implement real-time graph for jail/bhyve based on RACCT
-	statistics</li>
-
-	<li>test bhyve live migration, support live migration in CBSD</li>
-
-	<li>prepare ClonOS 19.01-RELEASE</li>
-      </ul>
-
-      <p>
-	Open task:</p>
-
-      <ul>
-	<li>ClonOS roadmap: <a href="https://clonos.tekroutine.com/roadmap.html" shape="rect">https://clonos.tekroutine.com/roadmap.html</a></li>
-
-	<li>FreeNAS/XigmaNAS or any other NAS integration</li>
-
-	<li>I would like to see ClonOS in real-world use. In this
-	regard, I am interested
-	in finding more people and companies that use FreeBSD for
-	vm/jail services.</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="HardenedBSD-2018Q4-Update" href="#HardenedBSD-2018Q4-Update" id="HardenedBSD-2018Q4-Update">HardenedBSD 2018Q4 Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://hardenedbsd.org" title="https://hardenedbsd.org">https://hardenedbsd.org</a></td><td>
-	    URL: <a href="https://hardenedbsd.org" title="https://hardenedbsd.org">https://hardenedbsd.org</a></td></tr></table><p>
-	Contact: Shawn Webb &lt;<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>&gt;
-	</p>
-      <p>Introduction to HardenedBSD</p>
-
-      <p>HardenedBSD is a security-enhanced fork of FreeBSD that
-	aims to
-	provide the BSD community with a clean-room
-	reimplementation of the
-	publicly-documented parts of the grsecurity patchset for
-	Linux. We
-	maintain close compatibility with FreeBSD by syncing every
-	six hours
-	with FreeBSD.</p>
-
-      <p>HardenedBSD Foundation Update</p>
-
-      <p>Through a generous donation by DEF CON, the computer
-	security
-	conference held each year in Las Vegas, and an anonymous
-	member of the
-	community, the HardenedBSD Foundation was able to provide
-	the
-	HardenedBSD project with a new Cavium ThunderX2 server.
-	HardenedBSD
-	has been working closely with FreeBSD's and Cavium's
-	Jayachandran
-	(jchandra@freebsd) to gain working support for the
-	ThunderX2. As soon
-	as the ThunderX2 becomes functional, HardenedBSD will be
-	able to
-	support both 12-STABLE and 13-CURRENT for arm64.</p>
-
-      <p>We assisted OPNsense's migration from FreeBSD to
-	HardenedBSD as the
-	base operating system. OPNsense's January 2019 release
-	(19.1) will
-	complete the migration. Further work will be done to
-	enable
-	HardenedBSD's PaX NOEXEC implementation in OPNsense. PaX
-	NOEXEC is a
-	strong form of W^X, which prevents memory allocations from
-	being both
-	writable and executable, and toggling between the two.</p>
-
-      <p>The HardenedBSD Foundation Corp. is a registered 501(c)(3)
-	tax-exempt
-	not-for-profit charitable organization in the United
-	States. We look
-	forward to a productive 2019, with work to support
-	Cross-DSO CFI still
-	ongoing.</p>
-
-      <p>HardenedBSD 12-STABLE Released</p>
-
-      <p>In December 2018, HardenedBSD published is first official
-	release of
-	<a href="https://hardenedbsd.org/article/op/2018-12-17/stable-release-hardenedbsd-stable-12-stable-v1200058" shape="rect">12-STABLE</a>.
-	From the release announcement:</p>
-
-      <p>Improvements in 12-STABLE from 11-STABLE:</p>
-
-      <ul>
-	<li>Non-Cross-DSO Control-Flow Integrity (CFI) for
-	applications on
-	amd64 and arm64. At this time, CFI is not applied to the
-	kernel.
-	More info on CFI is below.</li>
-
-	<li>Jailed bhyve (upstreamed to FreeBSD)</li>
-
-	<li>Per-jail toggles for unprivileged process debugging (the
-	<tt>security.bsd.unprivileged_process_debug</tt> sysctl
-	node. Upstreamed
-	to FreeBSD.)</li>
-
-	<li>Spectre v2 mitigation with retpoline applied to the
-	entirety of
-	base and ports (with only a few ports opting out.)</li>
-
-	<li>Symmetric Multi-Threading (SMT) disabled by default
-	(re-enable by
-	setting <tt>machdep.hyperthreading_allowed</tt> to 1 in
-	loader.conf(5)).</li>
-
-	<li>Migration of more compiler toolchain components to llvm's
-	implementations (llvm-ar, llvm-nm, and llvm-objdump).</li>
-
-	<li>Compilation of applications with Link-Time Optimization
-	(LTO).</li>
-      </ul>
-
-      <p>
-	Non-Cross-DSO CFI</p>
-
-      <p>Non-Cross-DSO CFI is an exploit mitigation technique that
-	helps
-	to prevent attackers from modifying the behavior of a
-	program and
-	jumping to undefined or arbitrary memory locations.
-	Microsoft has
-	implemented a variant of CFI, which they term Control Flow
-	Guard,
-	or CFG. The PaX team has spent the last few years
-	perfecting their
-	Reuse Attack Protector, RAP. CFI, CFG, and RAP all attempt
-	to
-	accomplish the same goal, with RAP being the most complete
-	and
-	effective implementation. Clang's CFI is stronger than
-	Microsoft's
-	CFG and PaX Team's RAP is stronger than both CFI and CFG.
-	RAP would
-	be a great addition to HardenedBSD; however, it requires a
-	GPLv3
-	toolchain and is patented.</p>
-
-      <p>Clang's CFI requires a linker that supports Link-Time
-	Optimization
-	(LTO). HardenedBSD 12-STABLE ships with lld as the default
-	linker.
-	All CFI schemes have been enabled for nearly all
-	applications in
-	base. Please note that any application that calls function
-	pointers
-	resolved via dlopen + dlsym will require the cfi-icall
-	scheme to be
-	disabled.</p>
-
-      <p>HardenedBSD is the first enterprise operating system to
-	apply
-	Non-Cross-DSO CFI broadly to userland.</p>
-
-    <hr /><h2><a name="The-nosh-project" href="#The-nosh-project" id="The-nosh-project">The nosh project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/" title="http://jdebp.eu./Softwares/nosh/">Introduction and blurb</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/" title="Introduction and blurb">http://jdebp.eu./Softwares/nosh/</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/guide.html" title="http://jdebp.eu./Softwares/nosh/guide.html">Guide</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/guide.html" title="Guide">http://jdebp.eu./Softwares/nosh/guide.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html" title="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html">FreeBSD binary packages</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html" title="FreeBSD binary packages">http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html" title="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html">Installation how-to</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html" title="Installation how-to">http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/roadmap.html" title="http://jdebp.eu./Softwares/nosh/roadmap.html">Roadmap</a></td><td>
-	    URL: <a href="http://jdebp.eu./Softwares/nosh/roadmap.html" title="Roadmap">http://jdebp.eu./Softwares/nosh/roadmap.html</a></td></tr></table><p>
-	Contact: Jonathan de Boyne Pollard &lt;<a href="mailto:J.deBoynePollard-newsgroups@NTLWorld.COM">J.deBoynePollard-newsgroups@NTLWorld.COM</a>&gt;
-	</p>
-      <p>Background</p>
-
-      <p>The nosh project is a suite of system-level utilities for
-	initializing,
-	running, and shutting down BSD systems; and for managing
-	daemons,
-	terminals, and logging.</p>
-
-      <p>It supersedes BSD <tt>init</tt>, the Mewburn <tt>rc</tt>
-	system, and OpenRC, drawing
-	inspiration from
-	<a href="http://untroubled.org/daemontools-encore/" shape="rect">daemontools-encore</a>
-	for
-	service control/status mechanisms,
-	<a href="http://jdebp.eu./FGA/UCSPI.html" shape="rect">UCSPI</a> for
-	networked services, Solaris
-	SMF for named milestones, and IBM AIX for separated
-	service and system
-	management. It includes a range of compatibility
-	mechanisms, including
-	shims for familiar commands from other systems, and an
-	automatic import
-	mechanism that takes existing configuration data from
-	<tt>/etc/fstab</tt>,
-	<tt>/etc/rc.conf{,.local}</tt>, <tt>/etc/ttys</tt>, and
-	elsewhere, applying them to
-	its native service definitions and creating additional
-	native services.</p>
-
-      <p>It is portable (including to Linux) and composable, it
-	provides a
-	migration path from the world of systemd Linux, and it
-	does not require
-	new kernel APIs. It provides clean service environments,
-	has orderings
-	and dependencies between services, has parallelized
-	startup and shutdown
-	(including <tt>fsck</tt>), provides strictly size-capped
-	and autorotated
-	logging, has the service manager as a "subreaper",
-	provides per-user
-	service management as well as system-wide, provides
-	user-space virtual
-	terminals, brings TTY login under the general service
-	management
-	umbrella, and uses <tt>kevent</tt>(2) for event-driven
-	parallelism.</p>
-
-      <p>For more, see the aforelinked <tt>Introduction and
-	blurb</tt>, and the
-	<tt>nosh Guide</tt>.</p>
-
-      <p>News</p>
-
-      <p>The project has seen a lot of development since the last
-	status report
-	in 2017. To briefly touch upon just some of the things
-	that have been
-	worked on:</p>
-
-      <ul>
-	<li>There are several more packages for things like running
-	Bruce Guenter's bcron, shims for OpenRC's
-	<tt>rc-update</tt> and <tt>rc-service</tt> tools,
-	and shims for portable substitutes for a couple of
-	Linux's util-linux tools.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>There are quite a lot of new tools, including
-	<tt>getuidgid</tt>, <tt>userenv-fromenv</tt>,
-	<tt>setgid-fromenv</tt>, <tt>envgid</tt>,
-	<tt>printenv</tt>, <tt>setlogin</tt>,
-	<tt>console-decode-ecma48</tt>,
-	<tt>console-control-sequence</tt>,
-	<tt>console-flat-table-viewer</tt>,
-	<tt>console-input-method</tt>, and
-	<tt>local-stream-socket-connect</tt>. To look at
-	just two of these:</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li><a href="http://jdebp.eu./Softwares/nosh/guide/printenv.html" shape="rect">printenv</a>
-	as a built-in allows more convenient use in
-	conjunction with <tt>clearenv</tt>. It can also
-	generate output in some additional formats.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li><a href="http://jdebp.eu./Softwares/nosh/guide/console-control-sequence.html" shape="rect">console-control-sequence</a>
-	also responds to the name <tt>setterm</tt>, and
-	can do most of what the non-portable util-linux
-	tool by that name does; excluding the things that
-	are specific to non-portable Linux
-	<tt>ioctl()</tt>s and control codes (such as
-	display adapter power management), but also
-	including _extra_ standard DEC VT and ECMA-48
-	things that the util-linux tool does _not_ do
-	(such as turning strikethrough, calculator keypad
-	application mode, mouse reports, and the
-	alternative screen buffer on and off).</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>There are a lot of new service bundles for more services,
-	too many to list here. One can find them listed in
-	the 1.37 and 1.38 + 1.39 release announcements.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>There are new chapters in the <tt>nosh Guide</tt>, on
-	packages and ports, on resources for terminals
-	such as keyboard maps, input methods, and fonts,
-	and on how the <tt>head0</tt> user-space virtual
-	terminal is structured.
-	There are also new manual pages - in addition to the ones
-	for all of the new commands, of course - on the
-	subjects of the <a href="http://jdebp.eu./Softwares/nosh/guide/TerminalCapabilities.html" shape="rect">http://jdebp.eu./Softwares/nosh/guide/TerminalCapabilities.html</a>
-	system.
-	There are also <a href="http://jdebp.eu./Proposals/linux-kvt-manual-pages.html" shape="rect">some
-	replacements for some Linux manual pages</a> that
-	have gone missing over the past decade.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>The external format configuration import subsystem has
-	seen some major improvements in per-user service
-	configuration. The per-user service manager itself
-	gained a control FIFO, addressing a long-standing
-	bug.</li>
-      </ul>
-
-      <p>
-	A particular area of improvement since the last status
-	report is the
-	inclusion of input method capabilities in user-space
-	virtual terminals.
-	The input method mechanism uses the same CIN files as used
-	by several
-	other softwares, similar to how one can use existing
-	SCO/FreeBSD
-	keyboard maps and FreeBSD vt fonts. It places a simple
-	textual user
-	interface on top of a user-space virtual terminal, can
-	switch amongst
-	multiple input methods on the fly, and responds to both
-	the dedicated
-	keys on a JIS 106/109-key keyboard or a Korean 103/106-key
-	keyboard and
-	the conventional keys used on other keyboards. The blurb
-	includes
-	<a href="http://jdebp.eu./Softwares/nosh/japanese-input-methods.html" shape="rect">an
-	example of how this works for a Japanese user</a>,
-	and the virtual terminal chapters of the <tt>nosh
-	Guide</tt> now incorporate
-	input methods into the doco.</p>
-
-      <p>Another area of work was eliminating Wide NCurses from
-	almost all of the
-	tools, apart from the one tool that by definition uses it
-	(console-ncurses-realizer). Wide NCurses has long been a
-	porting
-	difficulty for several operating systems, including Gentoo
-	Linux and
-	OpenBSD, and does not really model modern real world
-	terminals and
-	terminal emulators very well. It has been replaced by a
-	new
-	TerminalCapabilities library, in conjunction with a
-	library for handling
-	ECMA-48 character sequence decoding and ECMA-48/DEC VT
-	control sequence
-	generation. The decoder is the basis for the new
-	<tt>console-decode-ecma48</tt> tool, for example, as well
-	as being the decoder
-	for terminal input in <tt>console-termio-realizer</tt> and
-	in full-screen TUI
-	tools like
-	<a href="http://jdebp.eu./Softwares/nosh/guide/chkservice.html" shape="rect">chkservice</a>
-	and the new
-	<a href="http://jdebp.eu./Softwares/nosh/guide/console-flat-table-viewer.html" shape="rect">console-flat-table-viewer</a>.</p>
-
-      <p>The external formats import subsystem will also now make a
-	replacement
-	<tt>/etc/system-control/convert/termcap/termcap.db</tt>
-	that one can use, which
-	includes amongst other things the currently missing
-	<tt>teken</tt> terminal type.</p>
-
-      <p>Roadmap</p>
-
-      <p>In addition to what is on the aforelinked roadmap, several
-	things are on
-	the cards for forthcoming versions. Tools that can feed
-	the process
-	table into <tt>console-flat-table-viewer</tt> in the
-	proper vis(3) form. The
-	ability to have different keyboard maps for different
-	keyboards if one
-	has multiple keyboards. A Linux shim for
-	<tt>login.conf</tt>. Proper handling
-	of CSI sub-parameters in SoftTerm. A manual page for the
-	CIN file
-	format. A <tt>time-env-next-matching</tt> tool.</p>
-
-      <p>How you can help</p>
-
-      <ul>
-	<li>The Z shell completions now have extensive coverage of the
-	toolset, but there are no completions for the
-	Bourne Again shell or the Friendly Interactive
-	shell. Work on such completions would be welcome.
-	The users who use those shells would welcome it
-	especially.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>The <tt>system-manager</tt> already recognizes a
-	<tt>-b</tt> option for <a href="http://jdebp.eu./FGA/emergency-and-rescue-mode-bootstrap.html" shape="rect">emergency
-	mode</a>. Work to make the FreeBSD loader and
-	kernel send such an option to process #1, in
-	response to an additional emergency mode boot menu
-	choice, would be very welcome.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>The <tt>monitor-fsck-progress</tt> and
-	<tt>monitored-fsck</tt> tools stand ready to work
-	with a <tt>-C</tt> option to <tt>fsck</tt> that
-	makes it spit out progress information to an open
-	file descriptor. Another way to help is to add
-	this capability to <tt>fsck</tt>.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li><tt>teken</tt> needs to be added to base termcap. It was
-	put into NCurses terminfo back in 2014.</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2019-01-2019-03.html b/website/content/en/status/report-2019-01-2019-03.html
deleted file mode 100644
index a33267f558..0000000000
--- a/website/content/en/status/report-2019-01-2019-03.html
+++ /dev/null
@@ -1,2227 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>As spring leads into summer, we reflect back on what the
-      FreeBSD project has accomplished in the first quarter of 2019.
-      Events included FOSDEM and AsiaBSDCon, the FreeBSD Journal
-      is now free to everyone, ASLR is available in -CURRENT and KPTI
-      can be controlled per-process. The run up to 11.3-RELEASE
-      has begun, and a team is applying syzkaller guided fuzzing
-      to the kernel, plus so much more. Catch up on many new and
-      ongoing efforts throughout the project, and find where you can
-      pitch in.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#AXP803-PMIC-driver-update">AXP803 PMIC driver update</a></li><li><a href="#Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></li><li><a href="#C-Runtime-changes">C Runtime changes</a></li><li><a href="#Capsicum">Capsicum</a></li><li><a href="#CFT---Package-Base">CFT - Package Base</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#FreeBSD-boot-security-improvements">FreeBSD boot security improvements</a></li><li><a href="#FUSE">FUSE</a></li><li><a href="#Kernel-ZLIB-Update">Kernel ZLIB Update</a></li><li><a href="#LLVM's-lld-as-the-FreeBSD-system-linker">LLVM's lld as the FreeBSD system linker</a></li><li><a href="#mlx5-Drivers-Update">mlx5 Drivers Update</a></li><li><a href="#PCI-Express-Resets">PCI Express Resets</a></li><li><a href="#Security-Related-changes">Security-Related changes</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/RISC-V-Update">FreeBSD/RISC-V Update</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-GNOME-status-report">FreeBSD GNOME status report</a></li><li><a href="#FreeBSD-KDE-status-report">FreeBSD KDE status report</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#FreeBSD-Wiki-Apple-Intel-Mac-mini-update">FreeBSD Wiki Apple Intel Mac mini update</a></li><li><a href="#Fuzzing-FreeBSD-with-syzkaller">Fuzzing FreeBSD with syzkaller</a></li><li><a href="#sysctlmibinfo-API-1.0">sysctlmibinfo API 1.0</a></li><li><a href="#sysctlview-1.0">sysctlview 1.0</a></li><li><a href="#University-of-Waterloo-Co-operative-Education-Students">University of Waterloo Co-operative Education Students</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-        Page</a>.</p><br /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org/" title="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org/" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org/</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="freebsd-ci Repository">https://github.com/freebsd/freebsd-ci</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://hackfoldr.org/freebsd-ci-report/" title="https://hackfoldr.org/freebsd-ci-report/">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackfoldr.org/freebsd-ci-report/" title="FreeBSD CI weekly report">https://hackfoldr.org/freebsd-ci-report/</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD CI team maintains continuous integration
-	system and
-	related tasks for the FreeBSD project. The CI system
-	regularly
-	checks the changes committed to the project's Subversion
-	repository
-	can be successfully built, and performs various tests and
-	analysis
-	of the results. The results from build jobs are archived
-	in an
-	artifact server, for the further testing and debugging
-	needs. The
-	CI team members examine the failing builds and unstable
-	tests, and
-	work with the experts in that area to fix the code or
-	adjust test
-	infrastructure.</p>
-
-      <p>Starting from this quarter, we started to publish CI
-	weekly report at
-	<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing@</a>
-	mailing list. The archive is available at
-	<a href="https://hackfoldr.org/freebsd-ci-report/" shape="rect">https://hackfoldr.org/freebsd-ci-report/</a></p>
-
-      <p>We also worked on extending test executing environment
-	to improve the code coverage, temporarily disabling flakey
-	test cases,
-	and opening tickets to work with domain experts. The
-	details are
-	of these efforts are available in the weekly CI reports.</p>
-
-      <p>We published the
-	<a href="https://github.com/freebsd/fcp/blob/master/fcp-20190401-ci_policy.md" shape="rect">draft
-	FCP for CI policy</a>
-	and are ready to accept comments.</p>
-
-      <p>Please see freebsd-testing@ related tickets for more
-	information.</p>
-
-      <p>Work in progress:</p>
-
-      <ul>
-	<li>Fixing the failing test cases and builds</li>
-
-	<li>Adding drm ports building test against -CURRENT</li>
-
-	<li>Implementing automatic tests on bare metal hardware</li>
-
-	<li>Implementing the embedded testbed</li>
-
-	<li>Planning for running ztest and network stack tests</li>
-
-	<li>Help more 3rd software get CI on FreeBSD through a hosted
-	CI solution</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team is the governing body of FreeBSD.</p>
-
-      <p>Core initiated a <tt>Release Engineering Charter
-	Modernization</tt> working
-	group. The purpose of the working group is to present (to
-	Core) a
-	modernized version of the <tt>Release Engineering
-	Charter</tt> and a first
-	version of a new <tt>Release Engineering Team Operations
-	Plan</tt>. The
-	group hopes to complete its goals and dissolve by
-	2019-06-30.</p>
-
-      <p>The Core Team invites all members of the FreeBSD community
-	to
-	complete the <tt>2019 FreeBSD Community Survey</tt>.</p>
-
-      <p>https://www.research.net/r/freebsd2019</p>
-
-      <p>The purpose of the survey is to collect quantitative data
-	from the
-	public in order to help guide the project's priorities and
-	efforts.
-	It will remain open for 17 days and close at midnight May
-	13 UTC
-	(Monday 5pm PDT).
-	(Editor's note: Survey has finished)</p>
-
-      <p>Core voted to approve source commit bits for Johannes
-	Lundberg
-	(johalun@) and Mitchell Horne (mhorne@) and associate
-	membership
-	for Philip Jocks. Core also voted to revoke Michael
-	Dexter's
-	documentation bit.</p>
-
-      <p>After a long lapse of not closing idle source commit bits,
-	core has
-	taken in the commit bit for these developers. We thank
-	each for
-	contributing to the project as a source committer.</p>
-
-      <ul>
-	<li>Alfred Perlstein (alfred@)</li>
-
-	<li>Eric Badger (badger@)</li>
-
-	<li>Daniel Eischen (deischen@)</li>
-
-	<li>Ermal Lu�i (eri@)</li>
-
-	<li>Tony Finch (fanf@)</li>
-
-	<li>Justin T. Gibbs (gibbs@)</li>
-
-	<li>Imre Vad�sz (ivadasz@)</li>
-
-	<li>Julio Merino (jmmv@)</li>
-
-	<li>John W. De Boskey (jwd@)</li>
-
-	<li>Kai Wang (kaiw@)</li>
-
-	<li>Luigi Rizzo (luigi@)</li>
-
-	<li>Neel Natu (neel@)</li>
-
-	<li>Craig Rodrigues (rodrigc@)</li>
-
-	<li>Stanislav Sedov (stas@)</li>
-
-	<li>Thomas Quinot (thomas@)</li>
-
-	<li>Andrew Thompson (thompsa@)</li>
-
-	<li>Pyun YongHyeon (yongari@)</li>
-
-	<li>Zbigniew Bodek (zbb@)</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to
-	supporting and promoting the FreeBSD Project and community
-	worldwide.
-	Funding comes from individual and corporate donations and
-	is used to fund
-	and manage software development projects, conferences and
-	developer summits,
-	and provide travel grants to FreeBSD contributors.</p>
-
-      <p>The Foundation purchases and supports hardware to improve
-	and maintain
-	FreeBSD infrastructure and provides resources to improve
-	security,
-	quality assurance, and release engineering efforts;
-	publishes
-	marketing material to promote, educate, and advocate for
-	the FreeBSD Project;
-	facilitates collaboration between commercial vendors and
-	FreeBSD developers;
-	and finally, represents the FreeBSD Project in executing
-	contracts,
-	license agreements, and other legal arrangements that
-	require
-	a recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD
-	last quarter:</p>
-
-      <p>We kicked off the year with an all-day board meeting in
-	Berkeley,
-	where FreeBSD began, to put together high-level plans for
-	2019.
-	This included prioritizing technologies and features we
-	should support,
-	long-term planning for the next 2-5 years, and
-	philosophical discussions
-	on our purpose and goals.</p>
-
-      <p>Partnerships and Commercial User Support</p>
-
-      <p>We began the year by meeting with a few commercial users,
-	to help them
-	navigate working with the Project, and understanding how
-	they are using
-	FreeBSD. We're also in the process of setting up meetings
-	for Q2 and
-	throughout the rest of 2019. Because we're a 501(c)(3)
-	non-profit, we
-	don't directly support commercial users.
-	However, these meetings allow us to focus on facilitating
-	collaboration
-	with the community.</p>
-
-      <p>Fundraising Efforts</p>
-
-      <p>Our work is 100% funded by your donations. We kicked off
-	the year with many
-	individual and corporate donations, including donations
-	and commitments from
-	NetApp, Netflix, Intel, Tarsnap, Beckhoff Automation,
-	E-Card, VMware, and
-	Stormshield. We are working hard to get more commercial
-	users to give back
-	to help us continue our work supporting FreeBSD.
-	Please consider making a
-	<a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">donation</a>
-	to help us continue and increase our support for FreeBSD
-	at:
-	<a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">www.FreeBSDfoundation.org/donate/</a>.</p>
-
-      <p>We also have the Partnership Program, to provide more
-	benefits for our
-	larger commercial donors. Find out more information at
-
-	https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/
-	and share with your companies!</p>
-
-      <p>OS Improvements</p>
-
-      <p>The Foundation improves the FreeBSD 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 like
-	the arm64 port, porting the blacklistd access control
-	daemon, and the
-	integration of VIMAGE support,
-	to make sure that FreeBSD remains a viable solution for
-	research, education,
-	computing, products and more.</p>
-
-      <p>Over the quarter there were 241 commits from nine
-	Foundation-sponsored staff
-	members and grant recipients.</p>
-
-      <p>We kicked off or continued the following projects last
-	quarter:</p>
-
-      <ul>
-	<li>FUSE file system kernel support (update and bug fixes)</li>
-
-	<li>Linuxulator testing and diagnostics improvements</li>
-
-	<li>SDIO and WiFi infrastructure improvements</li>
-
-	<li>x86-64 scalability and performance improvements</li>
-
-	<li>OpenZFS Online RAID-Z Expansion</li>
-      </ul>
-
-      <p>
-	Having software developers on staff has allowed us to jump
-	in and
-	work directly on projects to improve FreeBSD like:</p>
-
-      <ul>
-	<li>amd64 and i386 pmap improvements and bugfixes</li>
-
-	<li>address userland threading library issues</li>
-
-	<li>improve i386 support to keep the platform viable</li>
-
-	<li>improve FreeBSD on RISC-V</li>
-
-	<li>application of the Capsicum sandboxing framework</li>
-
-	<li>build system improvements and bug fixes</li>
-
-	<li>respond to reports of security issues</li>
-
-	<li>implement vulnerability mitigations</li>
-
-	<li>tool chain updates and improvements</li>
-
-	<li>adding kernel code coverage support for the
-	<a href="https://github.com/google/syzkaller" shape="rect">Syzkaller</a>
-	coverage-guided system call
-	fuzzer</li>
-
-	<li>improved Syzkaller support for FreeBSD</li>
-
-	<li>improve the usability of <tt>freebsd-update</tt></li>
-
-	<li>improve network stack stability and address race
-	conditions</li>
-
-	<li>ensure FreeBSD provides userland interfaces required by
-	contemporary
-	applications</li>
-
-	<li>implement support for machine-dependent optimized
-	subroutines</li>
-
-	<li>update and correct documentation and manpages</li>
-
-	<li>DTrace bug fixes</li>
-
-	<li>update the FreeBSD Valgrind port and try to upstream the
-	changes</li>
-      </ul>
-
-      <p>
-	Continuous Integration and Quality Assurance</p>
-
-      <p>The Foundation provides a full-time staff member who is
-	working on improving
-	our automated testing, continuous integration, and overall
-	quality assurance
-	efforts.</p>
-
-      <p>During the first quarter of 2019, Foundation staff
-	continued improving the
-	project's CI infrastructure, working with contributors to
-	fix failing build
-	and test cases, and working with other teams in the
-	project for their
-	testing needs. In this quarter, we started publishing the
-	<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-testing" shape="rect">CI
-	weekly report</a>
-	on the freebsd-testing@ mailing list.</p>
-
-      <p>See the FreeBSD CI section of this report for more
-	information.</p>
-
-      <p>Release Engineering</p>
-
-      <p>The Foundation provides a full-time staff member to
-	oversee the
-	release engineering efforts. This has provided timely and
-	reliable releases
-	over the last five years.</p>
-
-      <p>During the first quarter of 2019, the FreeBSD Release
-	Engineering team
-	continued providing weekly development snapshots for
-	13-CURRENT, 12-STABLE,
-	and 11-STABLE.</p>
-
-      <p>In addition, the Release Engineering team published the
-	schedule for the
-	upcoming 11.3-RELEASE cycle, the fourth release from the
-	stable/11 branch,
-	which builds on the stability and reliability of
-	11.2-RELEASE.</p>
-
-      <p>The upcoming
-	<a href="https://www.freebsd.org/releases/11.3R/schedule.html" shape="rect">11.3-RELEASE
-	schedule</a>
-	can be found at:
-	https://www.freebsd.org/releases/11.3R/schedule.html</p>
-
-      <p>FreeBSD 11.3 is currently targeted for final release in
-	early July 2019.</p>
-
-      <p>Please see the FreeBSD Release Engineering Team section of
-	this quarterly
-	status report for additional details surrounding the above
-	mentioned work.</p>
-
-      <p>Supporting FreeBSD Infrastructure</p>
-
-      <p>The Foundation provides hardware and support to improve
-	FreeBSD infrastructure. Last quarter, we continued
-	supporting FreeBSD hardware located
-	around the world.</p>
-
-      <p>FreeBSD Advocacy and Education</p>
-
-      <p>A large part of our efforts are dedicated to advocating
-	for the Project.
-	This includes promoting work being done by others with
-	FreeBSD; producing
-	advocacy literature to teach people about FreeBSD and help
-	make the path to
-	starting using FreeBSD or contributing to the Project
-	easier; and attending
-	and getting other FreeBSD contributors to volunteer to run
-	FreeBSD events,
-	staff FreeBSD tables, and give FreeBSD presentations.</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events,
-	and summits
-	around the globe. These events can be BSD-related, open
-	source,
-	or technology events geared towards underrepresented
-	groups. We support
-	the FreeBSD-focused events to help provide a venue for
-	sharing knowledge,
-	to work together on projects, and to facilitate
-	collaboration between
-	developers and commercial users. This all helps provide a
-	healthy ecosystem.
-	We support the non-FreeBSD events to promote and raise
-	awareness of FreeBSD,
-	to increase the use of FreeBSD in different applications,
-	and to recruit
-	more contributors to the Project.</p>
-
-      <p>Check out some of the advocacy and education work we did
-	last quarter:</p>
-
-      <ul>
-	<li>Attended FOSDEM 2019 where we: staffed the FreeBSD Stand,
-	sponsored the
-	co-located FreeBSD Developer Summit, and gave the 25 Years
-	of FreeBSD
-	presentation in the BSD Dev room.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Sponsored and presented at SANOG33 in Thimphu, Bhutan</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Represented FreeBSD at APRICOT 2019 in Yuseong-gu, Daejeon
-	South Korea</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Sponsored the USENIX FAST conference in Boston, MA as an
-	Industry Partner</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Ran our first ever FreeBSD track at
-	<a href="https://www.socallinuxexpo.org/scale/17x" shape="rect">SCALE
-	17x</a>, which included an
-	all-day
-	<a href="https://www.socallinuxexpo.org/scale/17x/presentations/getting-started-freebsd" shape="rect">Getting
-	Started with FreeBSD</a>
-	workshop. We were thrilled with the turnout of almost 30
-	participants and
-	received a lot of positive feedback. Thanks to Roller
-	Angel who taught the
-	class with the help of Deb Goodkin and Gordon Tetlow. We
-	also promoted
-	FreeBSD at the FreeBSD table in the Expo Hall.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Sponsored, presented, and exhibited at FOSSASIA in
-	Singapore</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Sponsored AsiaBSDCon 2019</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Committed to sponsoring Rootconf, BSDCan, and EuroBSDcon</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Created registration systems for the Aberdeen Hackathon
-	and the upcoming
-	2019 Vienna FreeBSD Security Hackathon</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Provided FreeBSD advocacy material</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Provided 3 travel grants to FreeBSD contributors to attend
-	many
-	of the above events.</li>
-      </ul>
-
-      <p>
-	We continued producing FreeBSD advocacy material to help
-	people promote
-	FreeBSD around the world.</p>
-
-      <p>Read more about our conference adventures in the
-	conference recaps and trip
-	reports in our
-	<a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">monthly
-	newsletters</a>.</p>
-
-      <p>We help educate the world about FreeBSD by publishing the
-	professionally produced FreeBSD Journal. We're excited to
-	announce that with
-	the release of the January/February 2019 issue, the
-	FreeBSD Journal is now a
-	free publication. Find out more and access the latest
-	issues at
-	<a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">www.FreeBSDfoundation.org/journal/</a>.</p>
-
-      <p>You can find out more about events we attended and
-	upcoming events at
-	<a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">www.FreeBSDfoundation.org/news-and-events/</a>.</p>
-
-      <p>We also engaged with a new website developer to help us
-	improve our website
-	to make it easier for community members to find
-	information more easily and
-	to make the site more efficient.</p>
-
-      <p>Legal/FreeBSD IP</p>
-
-      <p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to
-	protect them. We also provide legal support for the core
-	team to investigate
-	questions that arise.</p>
-
-      <p>Go to <a href="http://www.FreeBSDfoundation.org" shape="rect">www.FreeBSDfoundation.org</a>
-	to find out
-	how we support FreeBSD and how we can help you!</p>
-
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/11.3R/schedule.html" title="https://www.freebsd.org/releases/11.3R/schedule.html">FreeBSD 11.3-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.3R/schedule.html" title="FreeBSD 11.3-RELEASE schedule">https://www.freebsd.org/releases/11.3R/schedule.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for
-	setting and
-	publishing release schedules for official project releases
-	of
-	FreeBSD, announcing code freezes and maintaining the
-	respective
-	branches, among other things.</p>
-
-      <p>During the first quarter of 2019, the FreeBSD Release
-	Engineering team
-	published the initial schedule for the upcoming the
-	11.3-RELEASE.</p>
-
-      <p>FreeBSD 11.3-RELEASE will be the fourth release from the
-	<tt>stable/11</tt>
-	branch, building on the stability and reliability of
-	11.2-RELEASE.
-	FreeBSD 11.3-RELEASE is currently targed for release in
-	early July, 2019.</p>
-
-      <p>Additionally throughout the quarter, several development
-	snapshots builds
-	were released for the <tt>head</tt>, <tt>stable/12</tt>,
-	and <tt>stable/11</tt> branches.</p>
-
-      <p>Much of this work was sponsored by the FreeBSD Foundation.</p>
-
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>As always, below is a summary of what happened in the
-	Ports Tree during the
-	last quarter.</p>
-
-      <p>During 2019q1, the number of ports dropped slightly to
-	just over 32,500. At
-	the end of the quarter, we had 2092 open port PRs. The
-	last quarter saw 8205
-	commits from 167 committers. So more PRs were closed and
-	more commits were
-	made than in 2018q4.</p>
-
-      <p>During the last quarter, we welcomed Kai Knoblich (kai@)
-	and said goodbye to
-	Matthew Rezny (rezny@).</p>
-
-      <p>On the infrastructure side, two new USES were introduced
-	(azurepy and sdl) and
-	USES=gecko was removed. The default versions of Lazarus
-	and LLVM were bumped
-	to 2.0.0 and 8.0 respectively. Some big port frameworks
-	that were end-of-life
-	were removed: PHP 5.6, Postgresql 9.3, Qt4, WebKit-Gtk and
-	XPI. Firefox was
-	updated to 66.0.2, Firefox-ESR to 60.6.1, and Chromium was
-	updated to
-	72.0.3626.121.</p>
-
-      <p>During the last quarter, antoine@ ran 30 exp-runs for
-	package updates, moving
-	from GNU ld to LLVM ld, and switching clang to DWARF4.</p>
-
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="AXP803-PMIC-driver-update" href="#AXP803-PMIC-driver-update" id="AXP803-PMIC-driver-update">AXP803 PMIC driver update</a></h2><p>
-	Contact: Ganbold Tsagaankhuu &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>The AXP803 is a highly integrated PMIC that targets
-	Li-battery
-	(Li-ion or Li-polymer) applications. It provides flexible
-	power
-	management solution for processors such as the Allwinner
-	A64 SoC.
-	This SoC is used by <a href="https://www.pine64.org/pinebook/" shape="rect">Pinebook</a>.</p>
-
-      <p>The following updates were performed on the AXP803 driver:</p>
-
-      <ul>
-	<li>Enabled necessary bits when activating interrupts. This
-	allows
-	reading some events from the interrupt status registers.
-	These
-	events are reported to devd via system "PMU" and subsystem
-	"Battery", "AC" and "USB" such as plugged/unplugged,
-	battery
-	absent, charged and charging.</li>
-
-	<li>Added sensors support for AXP803/AXP813. Sensor values
-	such as
-	battery charging, charge state, voltage, charging current,
-	discharging current, battery capacity can be obtained via
-	sysctl.</li>
-
-	<li>Added sysctl for setting battery charging current. The
-	charging
-	current can be set using steps from 0 to 13. These steps
-	correspond to 200mA to 2800mA, with a granularity of
-	200mA/step.</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="Broadcom-ARM64-SoC-support" href="#Broadcom-ARM64-SoC-support" id="Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></h2><p>
-	Contact: Michal Stanek &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p>
-      <p>The Semihalf team continued working on FreeBSD support for
-	the
-	<a href="https://www.broadcom.com/products/embedded-and-networking-processors/communications/bcm58712/" shape="rect">Broadcom
-	BCM5871X SoC series</a></p>
-
-      <p>BCM5871X are quad-core 64-bit ARMv8 Cortex-A57
-	communication
-	processors targeted for networking applications such as
-	10G routers,
-	gateways, control plane processing and NAS.</p>
-
-      <p>Completed since the last update:</p>
-
-      <ul>
-	<li>iProc PCIe root complex (internal and external buses)</li>
-
-	<li>OTP (One Time Programmable memory) driver</li>
-      </ul>
-
-      <p>
-	In progress:</p>
-
-      <ul>
-	<li>BNXT Ethernet support</li>
-
-	<li>Crypto engine acceleration for IPsec offloading.</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Upstreaming of work. This work is expected to be
-	submitted/merged to HEAD in the second half of
-	2019.</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by Juniper Networks, Inc.</p><hr /><h2><a name="C-Runtime-changes" href="#C-Runtime-changes" id="C-Runtime-changes">C Runtime changes</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@freebsd.org">kib@freebsd.org</a>&gt;
-	</p>
-      <p>Several changes where made to the C runtime which
-	generally improves
-	the environment provided to an application.</p>
-
-      <p>Fix for libraries with initial exec TLS mode</p>
-
-      <p>Some libraries, most prominent of which is NVidia-provided
-	and thus
-	binary-only libGL.so.1, use so called initial exec mode
-	for TLS
-	variables access. This is the fastest mode of TLS access,
-	but its
-	drawback is that it only reliably work when the main
-	binary is linked
-	against the library, i.e. dlopen-ing the library to load
-	it at runtime
-	is not guaranteed to work.</p>
-
-      <p>This mode works by placing the TLS variables for objects
-	in one area
-	allocated during the executable initialization, which
-	somewhat
-	explains the name of the mode. An obvious consequence is
-	that if such
-	library is loaded later, there is no space in the TLS area
-	for an
-	application to put its TLS variables.</p>
-
-      <p>The FreeBSD dynamic linker is aware of misbehaviour of the
-	app
-	builders, and provides some amount of slack in the TLS
-	area to give space
-	for such libraries. But it appeared that the initial
-	content of the
-	TLS segment from libraries was not distributed among the
-	threads' TLS
-	areas, still breaking libraries which use initial exec
-	mode for TLS.</p>
-
-      <p>Another issue that somewhat mitigates mis-use of the mode
-	is the
-	<tt>DF_STATIC_TLS</tt> flag in the dynamic section. This
-	flag allows the
-	linker to check for the space earlier and avoid loading
-	dependencies
-	if there is no total required space. This linker flag was
-	implemented
-	by the BFD ld linker, but not by the LLVM lld linker.</p>
-
-      <p>The FreeBSD dynamic linker was fixed to properly
-	distribute TLS
-	initialization data to all threads' initial segments,
-	which required
-	reasonably extensive per-architecture changes to libc and
-	libthr.
-	Simultaneously, LLD was improved to mark libraries using
-	initial exec
-	TLS mode with the appropriate flag.</p>
-
-      <p>These measures should make FreeBSD more resilent to
-	improperly
-	linked libraries. The most interesting fix is to users of
-	the
-	nvidia libgl library, because it cannot be fixed by
-	relinking.</p>
-
-      <p>Use rtld malloc in libthr</p>
-
-      <p>The FreeBSD implementation of mutexes in libthr allocates
-	some
-	memory to keep the mutex data needed for mutex
-	initialization. In
-	contrast, the malloc implementation used by FreeBSD,
-	jemalloc(3),
-	requires working pthread mutexes for operation.</p>
-
-      <p>This creates a chicken-and-egg problem during executable
-	startup, and
-	requires jemalloc to provide fragile hacks to make it
-	possible to
-	initialize mutexes. This has been a constant source of
-	mismatches on
-	imports of new versions of jemalloc.</p>
-
-      <p>The FreeBSD rtld implementation already contained a very
-	light-weight
-	malloc implementation, suitable for limited use in
-	pre-C-runtime
-	environments. This seemed to be the ideal fit for an
-	allocator for the
-	pthread private mutexes memory. By using this allocator, a
-	method
-	to address the cyclic dependencies between jemalloc and
-	libthr could
-	finally be implemented.</p>
-
-      <p>The entry points in the rtld malloc.c were renamed to
-	avoid a clash with
-	the libc exported symbols, and now the file is linked
-	statically into
-	libthr, providing an allocator for private mutexes and
-	pthread key
-	storage. The later was already switched to direct use of
-	mmap(2) for
-	similar reasons. Now less memory is wasted when key
-	storage requires
-	less than a page.</p>
-
-      <p>Destructors order bug</p>
-
-      <p>Alexander Kabaev (kan@) noted that C++ destructors for the
-	static objects from the linked shared libraries are
-	executed before
-	C++ destructors of the static objects from the main
-	binary. This was
-	verified both for clang++ and g++, but amusingly not for
-	<tt>__attribute__(((destructor)))</tt>.</p>
-
-      <p>The bug was introduced when init functions and init arrays
-	for main
-	binary startup are called from the rtld instead of csu (C
-	startup
-	code linked to the binary, typically from crt1.o). The
-	cause is
-	due to the somewhat complicated way of how destructors are
-	called
-	both by fini/fini arrays and rtld-registered atexit(3)
-	handler.</p>
-
-      <p>Solution is to register rtld atexit(3) handler before main
-	binary init
-	functions are called, using new internal ABI
-	<tt>__libc_atexit()</tt> function.</p>
-
-      <p>It is amusing that the bug was not noticed for so many
-	years.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Capsicum" href="#Capsicum" id="Capsicum">Capsicum</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Capsicum" title="https://wiki.FreeBSD.org/Capsicum">Capsicum Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.FreeBSD.org/Capsicum" title="Capsicum Wiki Page">https://wiki.FreeBSD.org/Capsicum</a></td></tr></table><p>
-	Contact: Enji Cooper &lt;<a href="mailto:ngie@freebsd.org">ngie@freebsd.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mariusz Zaborski &lt;<a href="mailto:oshogbo@FreeBSD.org">oshogbo@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Bora �zarslan &lt;<a href="mailto:borako.ozarslan@gmail.com">borako.ozarslan@gmail.com</a>&gt;
-	</p>
-      <p>Three themes for Capsicum work were:</p>
-
-      <ul>
-	<li>Importing Google's Capsicum test suite into FreeBSD</li>
-
-	<li>Porting and sandboxing openrsync for FreeBSD</li>
-
-	<li>Applying capsicum to additional base system utilities</li>
-      </ul>
-
-      <p>
-	The Googletest-based Capsicum test cases are now
-	integrated into
-	FreeBSD. After some discussion with David Drysdale - the
-	main
-	maintainer and developer for the Capsicum port on Linux -
-	we decided that
-	from now the FreeBSD will be upstream for Capsicum test
-	cases.</p>
-
-      <p>The next major step was sandboxing openrsync. In the
-	course of that work we
-	extended our fileargs service with two new
-	functionalities. We modified
-	the fileargs service to allow limiting the operations
-	which can be performed,
-	and can now delegate <tt>lstat</tt> to the Casper service.</p>
-
-      <p>Furthermore, openrsync highly depends on the <tt>fts</tt>
-	API. We spend
-	some time in optimizing <tt>fts</tt> and making it sandbox
-	friendly by
-	introducing <tt>fts_openat</tt> function and removing the
-	need to change the
-	working directory to traverse the paths. The changes to
-	the <tt>fts</tt> API
-	are now in the tests phase.</p>
-
-      <p>Moreover, we improved bootstrapping for non-FreeBSD
-	machines. Thanks
-	to this work we can now build tools needed to bootstrap
-	FreeBSD which
-	use Casper services. In the base system <tt>strings</tt>
-	is now sandboxed as a
-	result.</p>
-
-      <p>We also sandboxed <tt>rtsol</tt>, <tt>rtsold</tt>, and
-	<tt>savecore</tt>.</p>
-
-      <p>We host biweekly Capsicum calls. The notes from the
-	meetings are published
-	in FreeBSD's
-	<a href="https://github.com/freebsd/meetings/tree/master/capsicum" shape="rect">Capsium
-	meeting repository</a>
-	on GitHub.
-	If you would like to join the call do not hesitate to send
-	us an email.</p>
-
-    <hr /><h2><a name="CFT---Package-Base" href="#CFT---Package-Base" id="CFT---Package-Base">CFT - Package Base</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://trueos.github.io/pkgbase-docs/" title="https://trueos.github.io/pkgbase-docs/">Package Base CFT - FAQ</a></td><td>
-	    URL: <a href="https://trueos.github.io/pkgbase-docs/" title="Package Base CFT - FAQ">https://trueos.github.io/pkgbase-docs/</a></td></tr></table><p>
-	Contact: Kris Moore &lt;<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>&gt;
-	</p>
-      <p>The TrueOS project has been working on a Package Base
-	implementation,
-	and is pleased to issue its first
-	<a href="https://lists.freebsd.org/pipermail/freebsd-pkgbase/2019-April/000396.html" shape="rect">CFT
-	to the FreeBSD community</a>.</p>
-
-      <p>The TrueOS packaging work has been in development for
-	close to 6
-	months, and differs from the original FreeBSD package base
-	effort,
-	in that it is an "out of tree" implementation. It allows
-	any version
-	of FreeBSD to be packaged, and only requires a
-	<a href="https://github.com/freebsd/poudriere/pull/664" shape="rect">patch
-	to poudriere</a>, as well
-	as some minor ports enhancements, the first which is
-	<a href="https://reviews.freebsd.org/D20055" shape="rect">currently in
-	review</a>. For more information
-	on the current status, please refer to the FAQ page.</p>
-
-      <p>Additionally there will be a
-	<a href="https://wiki.freebsd.org/DevSummit/201905/PackageBase" shape="rect">working-group
-	at BSDCan 2019</a>, and
-	we encourage porters to attend and join the discussion.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by iXsystems Inc.</p><hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p>
-      <p>ENA (Elastic Network Adapter) is the smart NIC available
-	in the
-	virtualized environment of Amazon Web Services (AWS). The
-	ENA
-	driver supports multiple transmit and receive queues and
-	can handle
-	up to 100 Gb/s of network traffic, depending on the
-	instance type
-	on which it is used.</p>
-
-      <p>ENAv2 has been under development for FreeBSD, similar to
-	Linux
-	and DPDK. Since the last update internal review and
-	improvements
-	of the patches were done, followed by validation on
-	various AWS
-	instances.</p>
-
-      <p>To do:</p>
-
-      <ul>
-	<li>Upstream of the ENAv2 patches</li>
-      </ul>
-
-      <p>
-	Recently, AWS released the A1 instances which are arm64
-	instances.
-	The FreeBSD kernel was fixed, so the ENA can be used on
-	those
-	instances with no issues. There were changes required in
-	resource
-	activation in the ENA driver
-	<a href="https://svnweb.freebsd.org/base?view=revision&amp;amp;revision=345371" shape="rect">r345371</a>
-	and the addition of a missing bus release method to the
-	nexus module
-	for aarch64
-	<a href="https://svnweb.freebsd.org/base?view=revision&amp;amp;revision=345373" shape="rect">r345373</a>.
-	With these changes, the ENA driver can run on A1 instances
-	without
-	any known issues.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by Amazon.com Inc.</p><hr /><h2><a name="FreeBSD-boot-security-improvements" href="#FreeBSD-boot-security-improvements" id="FreeBSD-boot-security-improvements">FreeBSD boot security improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/345830" title="https://svnweb.freebsd.org/changeset/base/345830">Veriexec manifest verification in kernel</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/345830" title="Veriexec manifest verification in kernel">https://svnweb.freebsd.org/changeset/base/345830</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/345438" title="https://svnweb.freebsd.org/changeset/base/345438">TPM as entropy source</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/345438" title="TPM as entropy source">https://svnweb.freebsd.org/changeset/base/345438</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/344840" title="https://svnweb.freebsd.org/changeset/base/344840">UEFI support in libsecureboot</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/344840" title="UEFI support in libsecureboot">https://svnweb.freebsd.org/changeset/base/344840</a></td></tr></table><p>
-	Contact: Michal Stanek &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Kornel Duleba &lt;<a href="mailto:mindal@semihalf.com">mindal@semihalf.com</a>&gt;
-	</p>
-      <p>FreeBSD gained TPM 2.0 (Trusted Platform Module) support
-	at the end
-	of 2018. A kernel configuration option, TPM_HARVEST, was
-	also added
-	to use the TPM RNG as system entropy source. When used
-	this way,
-	the TPM can be harvested every ten seconds for entropy
-	which is
-	mixed into the OS entropy pool. The kernel option is
-	currently
-	disabled by default in amd64 GENERIC kernel configuration.</p>
-
-      <p>UEFI Secure Boot support, developed by Semihalf, has been
-	merged
-	with sjg's Veriexec support, resulting in a unified
-	library named
-	libsecureboot. This library is used for verification of
-	kernel and
-	modules by the loader. The library uses BearSSL as the
-	cryptographic
-	backend. The library supports loading trusted and
-	blacklisted
-	certificates from UEFI (DB/DBx databases) and can use them
-	as trust
-	anchors for the verification.</p>
-
-      <p>The library is also used by Veriexec to verify and parse
-	the
-	authentication database (called 'manifest')
-	in the kernel. Previously the manifest was
-	verified and parsed by a userspace application, then sent
-	to the
-	kernel via /dev/veriexec, which was a significant
-	limitation and a
-	security weakness.</p>
-
-      <p>To do:</p>
-
-      <ul>
-	<li>Backport to stable branches.</li>
-      </ul>
-
-      <p>
-	Special thanks to sjg and Juniper for fruitful cooperation
-	around
-	Veriexec and the libsecureboot development.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by Stormshield.</p><hr /><h2><a name="FUSE" href="#FUSE" id="FUSE">FUSE</a></h2><p>
-	Contact: Alan Somers &lt;<a href="mailto:asomers@FreeBSD.org">asomers@FreeBSD.org</a>&gt;
-	</p>
-      <p>FUSE (File system in USErspace) allows a userspace program
-	to
-	implement a file system. It is widely used to support
-	out-of-tree file
-	systems like NTFS, as well as for exotic pseudo file
-	systems like
-	sshfs. FreeBSD's fuse driver was added as a GSoC project
-	in 2012.
-	Since that time, it has been largely neglected. The FUSE
-	software is
-	<a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&amp;amp;known_name=fusefs&amp;amp;list_id=289348&amp;amp;query_based_on=fusefs&amp;amp;query_format=advanced&amp;amp;short_desc=%5Bfusefs%5D%20sysutils%2Ffusefs-&amp;amp;short_desc_type=anywordssubstr" shape="rect">buggy</a>
-	and out-of-date. Our implementation is about 11 years
-	behind.</p>
-
-      <p>The FreeBSD Foundation has agreed to fund a project to
-	improve the state of the
-	FreeBSD FUSE driver. So far I've written a test suite for
-	the fusefs(5)
-	module, fixed 1 previously reported bug, discovered and
-	fixed 6 new bugs, fixed
-	all of fusefs's Coverity CIDs, made some minor performance
-	enhancements and
-	done some general cleanup. During the next quarter I plan
-	to continue fixing
-	bugs, and I'll also raise the driver's API level as high
-	as I can before the
-	quarter runs out. We're currently at 7.8; the highest
-	defined level is 7.28.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Kernel-ZLIB-Update" href="#Kernel-ZLIB-Update" id="Kernel-ZLIB-Update">Kernel ZLIB Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D19706" title="https://reviews.freebsd.org/D19706">Review D19706</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D19706" title="Review D19706">https://reviews.freebsd.org/D19706</a></td></tr></table><p>
-	Contact: Yoshihiro Ota &lt;<a href="mailto:ota@j.email.ne.jp">ota@j.email.ne.jp</a>&gt;
-	</p>
-      <p>The FreeBSD system still uses an ancient (over 20
-	year-old) version
-	of zlib (version 1.0.4). The FreeBSD kernel zlib
-	implementation
-	has special enhancements only used by netgraph. There is a
-	separate
-	version of code derived from unzip 5.12 used to inflate
-	gzip files
-	in the kernel which could be replaced with a more modern
-	zlib.
-	More detailed information is written in
-	sys/modules/zlib/README in
-	the review.</p>
-
-      <p>In order to use the latest zlib, version 1.2.11, work has
-	been done
-	to revisit all existing zlib uses in the system. Most of
-	the code works
-	with the newer version of zlib as is. The unzip code will
-	need
-	some conversion work to use the newer zlib. A few callers
-	will be
-	made simplier by using some newer APIs available in the
-	updated zlib.
-	There are some zombie programs that have been broken and I
-	would
-	like to delete.</p>
-
-      <p>This will clean up zombie programs and duplicated zlib
-	code.
-	This will also make future zlib version updates easier.</p>
-
-      <p>These changes touch some very sensitive areas of the
-	system, such
-	as kernel loading, or are architecture specific like
-	armv6/armv7,
-	and also touch some legacy code like kgzip+kgzldr on i386.
-	Testers
-	and active users of these legacy zlib code are welcomed.</p>
-
-      <ul>
-	<li>armv elf_trampoline
-	Arm up to v5 can boot from gzipped kernel. This code is
-	modified
-	to use newer API for simplicity. Please verify gzipped
-	kernel
-	still boots with new code (Current code has fall back to
-	legacy
-	zlib in case of failure).
-	Please also elaborate how to link such kernel, too. I'm
-	still
-	trying to figure that out.</li>
-
-	<li>netgraph compression/decompression
-	Please help testing and/or teach how to test. Netgraph
-	compiles
-	in the FreeBSD zlib version inside.</li>
-
-	<li>gzipped a.out
-	Does anyone use gzipped a.out executables, still? If so,
-	does
-	someone have an easy and safe program to run?
-	Is a.out format i386 only?</li>
-
-	<li>zfs boot
-	Can we boot from gzipped file system today?</li>
-
-	<li>CTF
-	Checking how I can test.</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="LLVM's-lld-as-the-FreeBSD-system-linker" href="#LLVM's-lld-as-the-FreeBSD-system-linker" id="LLVM's-lld-as-the-FreeBSD-system-linker">LLVM's lld as the FreeBSD system linker</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/LLD" title="https://wiki.freebsd.org/LLD">LLD on the FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/LLD" title="LLD on the FreeBSD Wiki">https://wiki.freebsd.org/LLD</a></td></tr><tr><td><a href="https://bugs.freebsd.org/214864" title="https://bugs.freebsd.org/214864">lld exp-run</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/214864" title="lld exp-run">https://bugs.freebsd.org/214864</a></td></tr></table><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	</p>
-      <p>In FreeBSD-HEAD and 12.0 the default FreeBSD system linker
-	(i.e., <tt>/usr/bin/ld</tt>) is LLVM's lld, on amd64,
-	arm64, and armv7.
-	For i386 in 12.0 lld is used as the bootstrap linker
-	(i.e., to build the kernel and base system) but it is not
-	enabled
-	as the system linker because of multiple issues building
-	FreeBSD ports
-	with it enabled.</p>
-
-      <p>The primary issue affecting i386 with lld is that many
-	ports build
-	position-dependent code (i.e., non-PIC) for use in shared
-	libraries.
-	This either comes from omitting the <tt>-fPIC</tt>
-	compiler flag, or using
-	hand-written position-dependent assembly. Compared with
-	other
-	CPU architectures i386 position-independent code is rather
-	inefficient,
-	which may be responsible for port authors making an
-	explicit decision
-	to avoid PIC.</p>
-
-      <p>By default lld does not allow position-dependent code in
-	shared objects
-	(in particular, it does not permit relocations against
-	read-only segments -
-	typically containing the`.text` section).</p>
-
-      <p>Over the last quarter many commits were made to the ports
-	tree to fix
-	the build when the system linker is lld - either building
-	PIC code,
-	or adding the <tt>-znotext</tt> linker flag to permit
-	relocations against
-	read-only segments, or just switching the port to link
-	with GNU ld
-	if it is incompatible with lld in some other way.</p>
-
-      <p>At this point there are only a few dozen open bug reports
-	for issues
-	linking ports with lld as the system linker, and I expect
-	FreeBSD 12.1
-	to use lld as the system linker on i386 as well.</p>
-
-      <p>Tasks:</p>
-
-      <ul>
-	<li>Fix freepascal/Lazarus ports with lld</li>
-
-	<li>Triage and address remaining port failures</li>
-
-	<li>Holistic review of lld workarounds in the ports tree, to
-	identify changes
-	that are no longer needed, should be addressed in lld, or
-	should be sent
-	upstream</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="mlx5-Drivers-Update" href="#mlx5-Drivers-Update" id="mlx5-Drivers-Update">mlx5 Drivers Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver" title="http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver">Mellanox OFED for FreeBSD Documentation</a></td><td>
-	    URL: <a href="http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver" title="Mellanox OFED for FreeBSD Documentation">http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver</a></td></tr></table><p>
-	Contact: Slava Shwartsman, Hans Petter Selasky, Konstantin Belousov &lt;<a href="mailto:freebsd-drivers@mellanox.com">freebsd-drivers@mellanox.com</a>&gt;
-	</p>
-      <p>The mlx5 driver provides support for PCI Express adapters
-	based on
-	ConnectX-4(LX), ConnectX-5(EX) and ConnectX-6(DX).
-	The mlx5en driver provides support for Ethernet and the
-	mlx5ib driver provides
-	support for InfiniBand and RDMA over Converged Ethernet,
-	RoCE.</p>
-
-      <p>Following updates done in mlx5 drivers:</p>
-
-      <ul>
-	<li>Added support for ConnectX-6 and ConnectX-6dx devices,
-	which support of
-	up to 200Gb/s interface speeds!</li>
-
-	<li>Added TLS hardware offload support for ConnectX-6dx
-	devices. TLS Tx
-	crypto offload is a new feature for network devices. It
-	enables the kernel
-	TLS socket to skip encryption and authentication
-	operations on the transmit
-	side of the data path, delegating those to the NIC. In
-	turn, the network
-	adapter encrypts packets that belong to an offloaded TLS
-	socket on the fly.
-	The Mellanox network adapter does not modify any packet
-	headers. It expects
-	to receive fully framed TCP packets with TLS records as
-	payload. The NIC
-	replaces plaintext with ciphertext and fills the
-	authentication tag. The
-	adapter does not hold any state beyond the context needed
-	to encrypt the
-	next expected packet, i.e. expected TCP sequence number
-	and crypto state.</li>
-
-	<li>Add support for Dynamic Receive Queue Interrupt
-	Moderation. Dynamic
-	Interrupt Moderation (DIM) refers to any action made by
-	hardware and/or
-	software on run time to control interrupt rate on the
-	system. The
-	moderation action itself should not interfere with the
-	system's operation
-	and should not require any human interaction. In
-	networking, dynamic
-	interrupt moderation is used for controlling the rate of
-	interrupts
-	generated by the hardware for multiple traffic scenarios.</li>
-
-	<li>Enhanced support for self-healing mechanism:
-	In a rare occasion when Mellanox network adapters fail,
-	due to a firmware
-	bug for example, the driver will sense the catastrophic
-	error. As
-	a result of this failure detection, the device driver can
-	trigger a firmware reset for the device so it can recover
-	- without the
-	need to reboot the entire host.</li>
-
-	<li>Added support for in-driver firmware updating using
-	mlx5tool.</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="PCI-Express-Resets" href="#PCI-Express-Resets" id="PCI-Express-Resets">PCI Express Resets</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:konstantinb@mellanox.com">konstantinb@mellanox.com</a>&gt;
-	</p>
-      <p>Sometimes the need to reset a device attached to the
-	system presents
-	itself. Preferrably this device reset can be accomplished
-	without
-	causing the whole machine to reboot. It is easy to do with
-	USB
-	devices if the physical access is available -- you can
-	just re-plug
-	the device. For in-chassis devices, built-in, or on add-on
-	cards,
-	it is not possible to reset the device with physical
-	action, unless
-	the device is hot-plugged. Nonetheless, for typical modern
-	PCIe
-	devices, and most built-in PCI-emulation devices, the
-	reset can be
-	initiated using software actions.</p>
-
-      <p>If device is a real plugged-in PCIe device, then reset can
-	be
-	initiated by disabling and then re-training PCIe-link by
-	the upstream
-	port controls. For most PCI devices, which support the PCI
-	power
-	management specification, the proven way to accomplish the
-	reset
-	is to put the device into state D3 (off) and then return
-	to the
-	previous power state.</p>
-
-      <p>FreeBSD was missing a way to conveniently request user- or
-	driver-initiated reset of devices. While it was possible
-	to manually
-	fiddle with registers using pciconf, this is impractical
-	for users,
-	and requires a lot of boilerplate code from drivers.</p>
-
-      <p>A new BUS_RESET_CHILD() method was added to the newbus bus
-	interface,
-	and implementations added for PCIe bridges and PCI
-	devices. The
-	libdevctl(3) library call and devctl(8) command provide
-	convenient
-	userspace accessors for applications and administrators.</p>
-
-      <p>During the reset, the device driver must stop its
-	operations with
-	the device. One way to achieve this is to detach drivers
-	before
-	reset, and re-attach after the device afterwards. This is
-	mostly
-	fine for network interfaces, but other devices require
-	more
-	coordination to handle properly. For example, an NVMe disk
-	device
-	being detached it means that all mounted volumes abruptly
-	disapper
-	from VFS view. Due to this, the BUS_RESET_CHILD() method
-	allows
-	the caller to select either detach/re-attach or
-	suspend/resume
-	driver actions around the reset.</p>
-
-      <p>Mellanox uses the infrastructure to perform reset of the
-	mlx(5) card
-	after firmware reset without server reboot. It is believed
-	that
-	'devctl reset' will be more widely useful.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="Security-Related-changes" href="#Security-Related-changes" id="Security-Related-changes">Security-Related changes</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@freebsd.org">kib@freebsd.org</a>&gt;
-	</p>
-      <p>ASLR</p>
-
-      <p>The ASLR (Address Space Layout Randomization) patch from
-	<a href="https://reviews.freebsd.org/D5603" shape="rect">review
-	D5603</a> was
-	committed into svn. While debate continues about the
-	current and
-	forward-looking value ASLR provides, having an
-	implementation in
-	the FreeBSD source tree makes it easily available to those
-	who wish
-	to use it. This also moves the conversation past the
-	relative
-	merits to more comprehensive security controls.</p>
-
-      <p>KPTI per-process control</p>
-
-      <p>The KPTI (Kernel Page Table Isolation) implementation was
-	structured
-	so that most selections of page isolation mode were local
-	to the
-	current address space. In other words, the global control
-	variable
-	pti was almost unused in the code paths, instead the
-	user/kernel
-	%cr3 values were directly loaded into registers or
-	compared to see
-	if the user page table was trimmed. Some missed bits of
-	code were
-	provided by Isilon, and then bugs were fixed and last
-	places of
-	direct use of pti were removed.</p>
-
-      <p>Now when the system starts in the pti-enabled mode,
-	proccontrol(1) can
-	be used by root to selectively disable KPTI mode for
-	children of a
-	process. The motivation is that if you trust the program
-	that you
-	run, you can get the speed of non-pti syscalls back, but
-	still run
-	your normal user session in PTI mode. E.g., firefox would
-	be properly
-	isolated.</p>
-
-      <p>Feature-control bits</p>
-
-      <p>Every FreeBSD executable now contains a bit mask intended
-	for
-	enabling/disabling security-related features which makes
-	sense for the
-	binary. This mask is part of the executable segments
-	loaded on image
-	activation, and thus is part of any reasonable way to
-	authenticate the
-	binary content.</p>
-
-      <p>For instance, the ASLR compatibility is de-facto the
-	property of the
-	image and not of the process executing the image. The
-	first (zero)
-	bit in the mask controls ASLR opt-out. Other OSes (e.g.
-	Solaris) used
-	an OS-specific dynamic flag, which has the same runtime
-	properties
-	but leaves less bits to consume in the feature-control
-	mask.</p>
-
-      <p>The feature-control mask is read both by kernel and by
-	rtld during
-	image activation. It is expected that more features will
-	be added
-	to FreeBSD and the mask can be used for enabling/disabling
-	those
-	features..</p>
-
-      <p>It is expected that a tool to manipulate the mask will be
-	provided
-	shortly, see <a href="https://reviews.freebsd.org/D19290" shape="rect">review
-	D19290</a>.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="FreeBSD/RISC-V-Update" href="#FreeBSD/RISC-V-Update" id="FreeBSD/RISC-V-Update">FreeBSD/RISC-V Update</a></h2><p>
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mitchell Horne &lt;<a href="mailto:mhorne@FreeBSD.org">mhorne@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	</p>
-      <p>Work has continued on RISC-V port in the past quarter.</p>
-
-      <p>Support for transparent superpage promotion was added to
-	the RISC-V
-	port, meaning that applications will now automatically use
-	large
-	page mappings when possible. Per-CPU pmap activation
-	tracking was
-	added, reducing the overhead of various pmap operations.
-	This
-	noticeably improves the responsiveness of FreeBSD when
-	running in
-	a multi-CPU virtual machine.</p>
-
-      <p>A RISC-V implementation of minidumps was completed.
-	Support for
-	debugging RISC-V kernel dumps will land in devel/gdb after
-	the
-	next GDB release.</p>
-
-      <p>It is now possible to compile the in-tree LLVM's RISC-V
-	target by
-	setting WITH_LLVM_TARGET_RISCV=YES in /etc/src.conf. The
-	use of
-	LLVM to compile the RISC-V port is currently experimental
-	and
-	further investigation is ongoing.</p>
-
-      <p>Work is ongoing to bring up FreeBSD on SiFive's HiFive
-	Unleashed
-	development board now that one has been obtained by a
-	FreeBSD
-	developer. We also expect to work on support for a new
-	version
-	of the SBI specification.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation, DARPA, AFRL.</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="FreeBSD-GNOME-status-report" href="#FreeBSD-GNOME-status-report" id="FreeBSD-GNOME-status-report">FreeBSD GNOME status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.org/gnome/" title="https://freebsd.org/gnome/">GNOME FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.org/gnome/" title="GNOME FreeBSD">https://freebsd.org/gnome/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-gnome" title="https://github.com/freebsd/freebsd-ports-gnome">GNOME development Repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-gnome" title="GNOME development Repo">https://github.com/freebsd/freebsd-ports-gnome</a></td></tr></table><p>
-	Contact: Koop Mast &lt;<a href="mailto:kwm@FreeBSD.org">kwm@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Eric Turgeon &lt;<a href="mailto:ericbsd@FreeBSD.org">ericbsd@FreeBSD.org</a>&gt;
-	</p>
-      <p>Ports activity in this quarter were:</p>
-
-      <ul>
-	<li>The x11-toolkits/gtk30 port updated to 3.24.5 and later to
-	3.24.7.</li>
-
-	<li>The www/webkit2-gtk3 port was updated to 2.24.0.</li>
-
-	<li>And the old insecure webkit-gtk2 and webkit-gtk3 where
-	finally removed.</li>
-      </ul>
-
-      <p>
-	Work in progress, the branches are available in the GNOME
-	development
-	repo, see the link above.</p>
-
-      <ul>
-	<li>Eric Turgeon is working on MATE 1.22 in the
-	<tt>mate-1.22</tt> branch.
-	And is almost complete.</li>
-
-	<li>Charlie Li (IRC: vishwin) is working on a long overdue
-	update of
-	the cinnamon desktop. This update is almost complete. The
-	only
-	real blocker is that the screensaver can't be unlocked
-	after it
-	activates. The work is in the <tt>cinnamon</tt> branch.</li>
-      </ul>
-
-      <p></p>
-
-      <ul>
-	<li>Koop Mast works on GNOME 3.32. The desktop is usable apart
-	from
-	gdm which is currently non-functional. Due to lack of free
-	time
-	the work is going slowly. This work is available in the
-	<tt>gnome-3.32</tt>
-	branch.</li>
-      </ul>
-
-      <p>
-	People who are willing to contribute can find us on
-	#freebsd-gnome
-	on freenode.</p>
-
-    <hr /><h2><a name="FreeBSD-KDE-status-report" href="#FreeBSD-KDE-status-report" id="FreeBSD-KDE-status-report">FreeBSD KDE status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:adridg@FreeBSD.org">adridg@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Tobias C. Berner &lt;<a href="mailto:tcberner@FreeBSD.org">tcberner@FreeBSD.org</a>&gt;
-	</p>
-      <p>The two biggest accomplishements this quarter were:</p>
-
-      <ul>
-	<li>Qt4 and all its consumers have been removed from the ports
-	tree.</li>
-
-	<li>www/qt5-webengine has been updated from the ancient 5.9.4
-	to 5.12.x by kai@</li>
-      </ul>
-
-      <p>
-	Further we have kept the KDE Frameworks, Plasma and
-	Applications
-	ports up to date with upstreams releases, which thanks to
-	upstreams'
-	FreeBSD-CI uses less and less patches.</p>
-
-      <p>All the kde@ maintained ports (including cmake) have been
-	kept up
-	to date with their releases.</p>
-
-      <p>The plans for the next quarter are in no particular order</p>
-
-      <ul>
-	<li>Cleanup PyQt ports and pyqt.mk</li>
-
-	<li>Improve qt.mk components</li>
-
-	<li>Update sddm to 0.18.x</li>
-
-	<li>Implement user management functionality in system settings
-	(write
-	non-logind backend)</li>
-      </ul>
-
-      <p>
-	People who are willing to contribute can find us on
-	#kde-freebsd
-	on freenode, and the kde@FreeBSD.org mailing list. Further
-	we accept
-	pull-requests and contributions on
-	github.com/freebsd/freebsd-ports-kde.</p>
-
-      <p></p>
-
-    <hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="FreeBSD-Wiki-Apple-Intel-Mac-mini-update" href="#FreeBSD-Wiki-Apple-Intel-Mac-mini-update" id="FreeBSD-Wiki-Apple-Intel-Mac-mini-update">FreeBSD Wiki Apple Intel Mac mini update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/IntelMacMini" title="https://wiki.freebsd.org/IntelMacMini">FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/IntelMacMini" title="FreeBSD Wiki">https://wiki.freebsd.org/IntelMacMini</a></td></tr></table><p>
-	Contact: Trevor Roydhouse &lt;<a href="mailto:fbsdwiki@gmx.net">fbsdwiki@gmx.net</a>&gt;
-	</p>
-      <p>The FreeBSD Wiki page for the Apple Intel Mac minis has
-	been
-	comprehensively updated over the last quarter to drag it
-	from 2009
-	into 2019.</p>
-
-      <p>There are now detailed instructions for installing FreeBSD
-	as the
-	only operating system on models from 2007 through 2014 and
-	itemised
-	model specific information detailing FreeBSD support.</p>
-
-      <p>If anyone is interested, help is needed to provide more
-	specific
-	information for the macmini 1,1 and 6,1 through 8,1 models
-	and to
-	test patches for the asmc(4) driver for temperature sensor
-	feedback
-	and for setting fan speed. If you would like to help and
-	have access
-	to these Mac minis, please contact me.</p>
-
-      <p>Future tasks:</p>
-
-      <ul>
-	<li>Create and test more patches for asmc(4) to cover all
-	Intel Mac minis</li>
-
-	<li>Provide more information for 2006, 2012, 2014 and 2018 Mac
-	minis</li>
-
-	<li>Instructions for dual boot (macOS/FreeBSD) installations</li>
-      </ul>
-
-      <p></p>
-
-    <hr /><h2><a name="Fuzzing-FreeBSD-with-syzkaller" href="#Fuzzing-FreeBSD-with-syzkaller" id="Fuzzing-FreeBSD-with-syzkaller">Fuzzing FreeBSD with syzkaller</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/google/syzkaller" title="https://github.com/google/syzkaller">syzkaller</a></td><td>
-	    URL: <a href="https://github.com/google/syzkaller" title="syzkaller">https://github.com/google/syzkaller</a></td></tr></table><p>
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Michael Tuexen &lt;<a href="mailto:tuexen@FreeBSD.org">tuexen@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>Syzkaller is a coverage-guided system call fuzzer. It was
-	originally
-	developed for Linux. It programmatically creates programs
-	consisting
-	of sequences of random system calls and executes them in a
-	VM
-	(virtual machine). Using feedback from a kernel code
-	coverage
-	facility called kcov, syskaller mutates the generated test
-	programs
-	in an attempt to expand the executed coverage of code
-	paths within
-	the kernel. Sometimes exercising a seldom or infrequently
-	used
-	code path will crash the kernel. When syzkaller manages to
-	crash
-	the running kernel in the VM, it attempts to generate a
-	minimal
-	test case which reproduces the crash, simplifying
-	debugging.
-	Syzkaller is very effective at finding kernel bugs and has
-	uncovered
-	hundreds of issues in Linux. Over the past couple of
-	years,
-	syzkaller's author, Dmitry Vyukov, has added support for
-	other
-	operating systems, including FreeBSD.</p>
-
-      <p>Recently, a number of FreeBSD developers have been using
-	syzkaller
-	to find and fix bugs in the FreeBSD kernel. If interested,
-	one can
-	search the commit logs for "syzkaller" to find examples.
-	Syzkaller
-	can be run on a FreeBSD or Linux host to fuzz FreeBSD
-	running in
-	QEMU instances. It can also fuzz FreeBSD instances running
-	on GCE
-	(Google Compute Engine). Additionally, Google maintains a
-	dedicated
-	cluster of GCE hosts to continuously fuzz the latest
-	builds of
-	several different OS kernels. A
-	<a href="https://syzkaller.appspot.com/freebsd" shape="rect">FreeBSD
-	target</a> was recently added.
-	Subscribe to the
-	<a href="https://groups.google.com/forum/#!forum/syzkaller-freebsd-bugs" shape="rect">syzkaller-freebsd-bugs</a>
-	Google Group to receive notifications for newly discovered
-	bugs.</p>
-
-      <p>Work is ongoing to improve syzkaller's coverage of
-	FreeBSD's system
-	calls. In particular, syzkaller needs to be taught about
-	all of
-	the target kernel's entry points and argument types in
-	order to be
-	useful. Many of the standard POSIX system calls are
-	already covered,
-	but most FreeBSD-specific system calls are not. Similarly,
-	many
-	ioctl(2) definitions are missing.</p>
-
-      <p>Some in-progress work aims to add support for bhyve as a
-	VM backend
-	for syzkaller, making it easier to fuzz FreeBSD VMs hosted
-	on
-	FreeBSD. Currently that can be done using QEMU, but QEMU
-	on FreeBSD
-	lacks support for hardware acceleration. See the
-	<a href="https://github.com/google/syzkaller/pull/1150" shape="rect">PR</a>
-	for the
-	implementation.</p>
-
-      <p>Finally, a number of bugs identified by syzkaller have yet
-	to be
-	fixed. If you are interested in helping out with any of
-	the above,
-	please mail the contacts listed above.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="sysctlmibinfo-API-1.0" href="#sysctlmibinfo-API-1.0" id="sysctlmibinfo-API-1.0">sysctlmibinfo API 1.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/alfix/sysctlmibinfo" title="https://gitlab.com/alfix/sysctlmibinfo">gitlab.com/alfix/sysctlmibinfo</a></td><td>
-	    URL: <a href="https://gitlab.com/alfix/sysctlmibinfo" title="gitlab.com/alfix/sysctlmibinfo">https://gitlab.com/alfix/sysctlmibinfo</a></td></tr></table><p>
-	Contact: Alfonso Sabato Siciliano &lt;<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>&gt;
-	</p>
-      <p>Port: <a href="https://www.freshports.org/devel/libsysctlmibinfo/" shape="rect">devel/libsysctlmibinfo</a></p>
-
-      <p>The <tt>sysctl()</tt> system call can get or set the value
-	of a 'property'
-	of the system. A 'property' has others info (description,
-	type,
-	label, etc.), they are necessary to build an utility like
-	<tt>/sbin/sysctl</tt>,
-	example:</p>
-
-      <p><programlisting>
-	  % sysctl -d kern.ostype<br clear="none" />
-	  kern.ostype: Operating system type<br clear="none" />
-	  % sysctl -t kern.ostype<br clear="none" />
-	  kern.ostype: string<br clear="none" />
-</programlisting></p>
-
-      <p>Primarily <tt>sysctlmibinfo</tt> wraps the undocumented
-	kernel interface
-	and provides an easy C API: <tt>sysctlmif_name()</tt>,
-	<tt>sysctlmif_description()</tt>,
-	<tt>sysctlmif_info()</tt>,
-	<tt>sysctlmif_label()</tt>,
-	<tt>sysctlmif_nextnode()</tt> and
-	<tt>sysctlmif_nextleaf()</tt>, to retrieve
-	the info of a 'property'.</p>
-
-      <p>Moreover <tt>sysctlmibinfo</tt> provides a high level API:
-	defines a
-	<tt>struct sysctlmif_object</tt> and has some function:
-	<tt>sysctlmif_filterlist()</tt>,
-	<tt>sysctlmif_grouplist()</tt> and
-	<tt>sysctlmif_tree()</tt>, to build lists and trees of
-	objects.</p>
-
-      <p>You can use this library to quickly build a custom
-	<tt>sysctl</tt> utility.
-	For example, the core of <tt>deskutils/sysctlview</tt> (a
-	graphical explorer
-	for the sysctl MIB Tree) is just a call to
-	<tt>sysctlmif_tree()</tt> and
-	a visit to the resulting tree to show its
-	<tt>sysctlmif_object</tt> nodes.</p>
-
-      <p>Note, actually a 'property' is an OID of the sysctl MIB,
-	it is
-	implemented by a <tt>struct sysctl_oid</tt> defined in
-	<tt>sys/sysctl.h</tt>.</p>
-
-    <hr /><h2><a name="sysctlview-1.0" href="#sysctlview-1.0" id="sysctlview-1.0">sysctlview 1.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.gitlab.com/alfix/sysctlview" title="https://www.gitlab.com/alfix/sysctlview">gitlab.com/alfix/sysctlview</a></td><td>
-	    URL: <a href="https://www.gitlab.com/alfix/sysctlview" title="gitlab.com/alfix/sysctlview">https://www.gitlab.com/alfix/sysctlview</a></td></tr></table><p>
-	Contact: Alfonso Sabato Siciliano &lt;<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>&gt;
-	</p>
-      <p>Port: <a href="https://www.freshports.org/deskutils/sysctlview/" shape="rect">deskutils/sysctlview</a></p>
-
-      <p>The FreeBSD's kernel maintains a Management Information
-	Base where
-	the objects are properties to tuning the system using the
-	<tt>sysctl()</tt> syscall and the <tt>/sbin/sysctl</tt>
-	utility. The <tt>sysctlview</tt>
-	utility is a "graphical sysctl MIB explorer", it depends
-	on <tt>gtkmm</tt>
-	(to build a GUI) and <tt>sysctlmibinfo</tt> (to retrieve
-	the info from the
-	kernel).</p>
-
-      <p>The version 1.0 provides two "TreeView":</p>
-
-      <ul>
-	<li>"Main" to show 'name', 'description', 'type', 'format' and
-	'value'</li>
-
-	<li>"Flags" to show 'name' and a column for each 'flag'
-	defined in <tt>sys/sysctl.h</tt></li>
-      </ul>
-
-      <p>
-	The rows are "clickable" to display others info (e.g.,
-	'label').
-	Currently <tt>sysctlview</tt> can show numeric and string
-	values, the
-	support for some opaque value will be added in the future.</p>
-
-    <hr /><h2><a name="University-of-Waterloo-Co-operative-Education-Students" href="#University-of-Waterloo-Co-operative-Education-Students" id="University-of-Waterloo-Co-operative-Education-Students">University of Waterloo Co-operative Education Students</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	</p>
-      <p>For the January-April 2019 term the FreeBSD Foundation has
-	again brought
-	on two co-operative education (co-op) students from the
-	University of
-	Waterloo.</p>
-
-      <p>Gerald Aryeetey is a 2nd year Computer Engineering
-	student. Gerald
-	started looking at a FreeBSD tool chain issue - our static
-	library
-	archiver (<literal>ar</literal>) did not read or write archives in the
-	64-bit format.
-	Gerald submitted a
-	<a href="https://github.com/libarchive/libarchive/pull/1116" shape="rect">libarchive
-	change</a>
-	to support 64-bit archives followed by
-	<a href="https://reviews.freebsd.org/D19814" shape="rect">change to
-	FreeBSD's ar</a>
-	to add 64-bit support.</p>
-
-      <p>Gerald later looked at a number of <tt>freebsd-update</tt>
-	issues in FreeBSD's
-	bugzilla database, and submitted many fixes. Around a
-	dozen have been
-	committed to FreeBSD, and more are in review.</p>
-
-      <p>Gerald also worked on the
-	<a href="https://github.com/freebsdfoundation/hardware-ci" shape="rect">FreeBSD
-	Foundation's hardware continuous integration</a>
-	effort.
-	The prototype installation is building FreeBSD on a
-	commit-by-commit basis
-	and testing on a BeagleBone Black and a Pine64 LTS.
-	The prototype will be converted to a permanent, public
-	installation in the
-	near future, after which additional test devices will be
-	added.</p>
-
-      <p>For his final project Gerald intends to write a device
-	driver for the
-	<a href="https://www.microchip.com/wwwproducts/en/LAN7430" shape="rect">Microchip
-	LAN743x PCIe NIC</a>.</p>
-
-      <p>Bora �zarslan is a 3rd year student in Computing and
-	Financial Management.
-	Bora's initial focus was also on tool chain issues in
-	FreeBSD, starting with
-	improvements or bug fixes in FreeBSD's <tt>readelf</tt>
-	(from the
-	<a href="https://sourceforge.net/p/elftoolchain/wiki/Home/" shape="rect">ELF
-	Tool Chain</a> project).</p>
-
-      <p>Bora developed a
-	<a href="https://reviews.freebsd.org/D19290" shape="rect">tool</a> to
-	modify feature control bits
-	in ELF binaries - for example, allowing binaries
-	incompatible with ASLR to
-	request to opt-out.
-	As part of his readelf work Bora also added support to
-	report the status of
-	the feature control bits.</p>
-
-      <p>Bora continued investigating security topics, looking at
-	applying
-	<a href="https://reviews.freebsd.org/D19407" shape="rect">Capsicum
-	sandboxing</a> to
-	Kristaps' BSD licensed rsync implementation,
-	<a href="https://github.com/kristapsdz/openrsync" shape="rect">openrsync</a>.
-	This work required first implementing
-	<a href="https://reviews.freebsd.org/D19548" shape="rect">fileargs_lstat</a>
-	support in <tt>cap_fileargs</tt>
-	(which as now been committed) as well as changes to the
-	<tt>fts</tt> directory hierarchy routines (which have not
-	yet been committed to
-	FreeBSD).</p>
-
-      <p>For the rest of the work term Bora will investigate and
-	test unmodified
-	Linux Docker containers on FreeBSD, to evaluate the state
-	of Linuxulator
-	support.</p>
-
-      <p></p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2019-04-2019-06.html b/website/content/en/status/report-2019-04-2019-06.html
deleted file mode 100644
index 2e2787d9a7..0000000000
--- a/website/content/en/status/report-2019-04-2019-06.html
+++ /dev/null
@@ -1,2402 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This quarter our report includes
-    some interesting topics easily accessible to anyone, even if
-    you are not a programmer: we report the link to a presentation
-    of the 2019 FreeBSD survey results at BSDCan 2019 and describe
-    an interesting experience of a 3-person hackaton, which might
-    encourage you to host one yourself, possibly with more participants.
-    We also provide some up to date information about the status
-    of our IRC channels.</p><p>For those who have some more technical skills, we give some
-      news about the role of git in the FreeBSD project, describe
-      the status of some tools to hunt bugs or enhance security and
-      announce a clone of sysctl.</p><p>Finally, those who are more experienced with programming will
-      probably be interested in the great work that has been done
-      with drivers: in particular, an aknowledgement is due to Alan
-      Somers for having started to bring up to date our FUSE
-      implementation, which was about 11 years behind. Other important
-      improvements include a more user-friendly experience with
-      trackpoints and touchpads enabled by default, much low level
-      work on graphics, many new bhyve features, updates to the
-      linux compatibility layer, various kernel improvements.</p><p>Have a nice read!<br clear="none" />
-
-      -- Lorenzo Salvadore</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></li><li><a href="#IRC-Admin">IRC Admin</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Release-Engineering-Team">Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#bhyve---Live-Migration">bhyve - Live Migration</a></li><li><a href="#bhyve---Save/Restore">bhyve - Save/Restore</a></li><li><a href="#BIO_DELETE-support-for-the-swap-pager">BIO_DELETE support for the swap pager</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#FreeBSD-SDIO-and-Broadcom-FullMAC-WiFi-Support">FreeBSD SDIO and Broadcom FullMAC WiFi Support</a></li><li><a href="#FUSE">FUSE</a></li><li><a href="#Fuzzing-FreeBSD-with-syzkaller">Fuzzing FreeBSD with syzkaller</a></li><li><a href="#Kernel-ZLIB-Update">Kernel ZLIB Update</a></li><li><a href="#Linux-compatibility-layer-update">Linux compatibility layer update</a></li><li><a href="#Lock-less-delayed-invalidation-for-amd64-pmap">Lock-less delayed invalidation for amd64 pmap</a></li><li><a href="#Locking-changes-for-vnodes-during-execve(2)">Locking changes for vnodes during execve(2)</a></li><li><a href="#Mellanox-Drivers-Update">Mellanox Drivers Update</a></li><li><a href="#NFSv4.2-client/server-implementation-for-FreeBSD">NFSv4.2 client/server implementation for FreeBSD</a></li><li><a href="#NUMA-awareness-in-the-FreeBSD-kernel">NUMA awareness in the FreeBSD kernel</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></li><li><a href="#NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#Aberdeen-Hackathon">Aberdeen Hackathon</a></li><li><a href="#Bring-more-Security-Intelligence-to-FreeBSD">Bring more Security Intelligence to FreeBSD</a></li><li><a href="#libvdsk---QCOW2-implementation">libvdsk - QCOW2 implementation</a></li><li><a href="#nsysctl-1.0">nsysctl 1.0</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-        Page</a>.</p><br /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org/" title="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org/" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org/</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="freebsd-ci Repository">https://github.com/freebsd/freebsd-ci</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://hackfoldr.org/freebsd-ci-report/" title="https://hackfoldr.org/freebsd-ci-report/">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackfoldr.org/freebsd-ci-report/" title="FreeBSD CI weekly report">https://hackfoldr.org/freebsd-ci-report/</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD CI team maintains continuous integration
-	system and related tasks
-	for the FreeBSD project. The CI system regularly checks
-	the committed changes
-	can be successfully built, then performs various tests and
-	analysis of the
-	results. The results from build jobs are archived in an
-	artifact server, for
-	the further testing and debugging needs. The CI team
-	members examine the
-	failing builds and unstable tests, and work with the
-	experts in that area to
-	fix the code or adjust test infrastructure. The details
-	are of these efforts
-	are available in the weekly CI reports.</p>
-
-      <p>The
-	<a href="https://github.com/freebsd/fcp/blob/master/fcp-20190401-ci_policy.md" shape="rect">FCP
-	for CI policy</a>
-	is in "feedback" state, please provide any comments to
-	freebsd-testing@ or
-	other suitable lists.</p>
-
-      <p>We had a testing working group in <a href="https://wiki.freebsd.org/DevSummit/201905/TestingCI" shape="rect">201905
-	DevSummit</a></p>
-
-      <p>Please see freebsd-testing@ related tickets for more
-	information.</p>
-
-      <p>Work in progress:</p>
-
-      <ul>
-	<li>Fixing the failing test cases and builds</li>
-
-	<li>Adding drm ports building test against -CURRENT</li>
-
-	<li>Adding powerpc64 tests job: <a href="https://github.com/freebsd/freebsd-ci/pull/33" shape="rect">https://github.com/freebsd/freebsd-ci/pull/33</a></li>
-
-	<li>Implementing automatic tests on bare metal hardware</li>
-
-	<li>Extending and publishing the embedded testbed</li>
-
-	<li>Planning for running ztest and network stack tests</li>
-
-	<li>Help more 3rd software get CI on FreeBSD through a hosted
-	CI solution</li>
-      </ul>
-
-    <hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team is the governing body of FreeBSD.</p>
-
-      <ul>
-	<li>Core approved source commit bits for Doug Moore (dougm),
-	Chuck Silvers
-	(chs), Brandon Bergren (bdragon), and a vendor commit bit
-	for Scott
-	Phillips (scottph).</li>
-      </ul>
-
-      <ul>
-	<li>The annual developer survey closed on 2019-04-02. Of the
-	397
-	developers, 243 took the survey with an average completion
-	time of 12
-	minutes. The public survey closed on 2019-05-13. It was
-	taken by
-	3637 users and had a 79% completion rate.
-	<a href="https://www.youtube.com/watch?v=9nc8N6GtAPg&amp;t=549" shape="rect">A
-	presentation of the survey results</a>
-	took place at BSDCan 2019.</li>
-      </ul>
-
-      <ul>
-	<li>The core team voted to appoint a working group to explore
-	transitioning our source code 'source of truth' from
-	Subversion to
-	Git. Core asked Ed Maste to chair the group as Ed has been
-	researching this topic for some time. For example, Ed gave
-	<a href="https://www.youtube.com/watch?v=G8wQ88d85s4" shape="rect">a
-	MeetBSD 2018 talk on the topic</a>.</li>
-      </ul>
-
-      <p>
-	There is a variety of viewpoints within core regarding
-	where and how
-	to host a Git repository, however core feels that Git is
-	the prudent
-	path forward.</p>
-
-      <ul>
-	<li>The project received many Season of Docs submissions and
-	picked a top
-	candidate. Google will announce the accepted technical
-	writer
-	projects on 2019-08-06. We are hoping for lots of new and
-	refreshed
-	man pages.</li>
-      </ul>
-
-    <hr /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to supporting and promoting
-	the FreeBSD Project and community worldwide.
-	Funding comes from individual and corporate
-	donations and is used to fund and manage software
-	development projects, conferences and developer
-	summits, and provide travel grants to FreeBSD
-	contributors. The Foundation purchases and
-	supports hardware to improve and maintain FreeBSD
-	infrastructure and provides resources to improve
-	security, quality assurance, and release
-	engineering efforts; publishes marketing material
-	to promote, educate, and advocate for the FreeBSD
-	Project; facilitates collaboration between
-	commercial vendors and FreeBSD developers; and
-	finally, represents the FreeBSD Project in
-	executing contracts, license agreements, and other
-	legal arrangements that require a recognized legal
-	entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD
-	last quarter:</p>
-
-      <p>We held our annual board meeting in Ottawa on May 14.
-	Board Director and Officer elections take place
-	each year at this meeting. Justin Gibbs was
-	elected as the new President of the Board of
-	Directors. The new FreeBSD Foundation Board of
-	Directors includes President and Founder Justin T.
-	Gibbs, Vice President Benedict Reuschling,
-	Secretary Philip Paeps, Treasurer Marshall Kirk
-	McKusick, and Directors Hiroki Sato, George
-	Neville-Neil and Robert N. M. Watson. You can read
-        <a href="https://www.freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-names-justin-gibbs-as-new-board-president/" shape="rect">more
-        about the elections</a>.</p>
-
-      <p>After the elections, our management team gave updates to
-	the board on their respective areas. We then
-	discussed the key areas of the Project that need
-	help, and where we can step in to fill those
-	holes. We reviewed and updated our 12 month goals,
-	and identified projects we should support. We then
-	discussed conferences we are likely to attend, and
-	went over the latest on our fundraising efforts.
-	We followed that up with a discussion on how to
-	get more users to contribute back to the Project.
-	While discussing how to increase the number of
-	users and contributors, we talked about methods
-	for making for more training material available.</p>
-
-      <p>
-	Partnerships and Commercial User Support</p>
-      <p>
-	We help facilitate collaboration between commercial users
-	and FreeBSD developers. We also meet with
-	companies to discuss their needs and bring that
-	information back to the Project. In Q2, Ed Maste
-	and Deb Goodkin met with a few commercial users in
-	Germany. It&#8217;s not only beneficial for the above,
-	but it also helps us understand some of the
-	applications where FreeBSD is used. Because BSDCan
-	brings in a high number of commercial users, we
-	have an excellent opportunity to have similar
-	discussions about their needs during the four-day
-	FreeBSD Summit and BSDCan.</p>
-
-      <p>
-	Fundraising Efforts</p>
-      <p>
-	Our work is 100% funded by your donations. We are grateful
-	for the generous donations from Intel, NetApp,
-	VMware and Stormshield last quarter. We are
-	working hard to get more commercial users to give
-	back to help us continue our work supporting
-	FreeBSD. More importantly, we&#8217;d like to thank
-	our individual donors, for making $10-$1,000
-	donations last quarter, for a total of $16,000!</p>
-
-      <p>Please consider making a donation to help us
-	<a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">continue and
-	increase our support for FreeBSD</a>.</p>
-
-      <p>We also have the
-	<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">Partnership
-	Program</a> to provide more
-	benefits for our larger commercial donors.
-	Find out more information at the link and share with your
-	companies!</p>
-
-      <p>OS Improvements</p>
-      <p>
-	The Foundation improves the FreeBSD operating system by
-	employing our technical staff to maintain and
-	improve critical kernel subsystems, add features
-	and functionality, and fix problems. The
-	Foundation also provides grants to fund individual
-	projects.</p>
-
-      <p>There were 243 commits to the FreeBSD base system
-	repository sponsored by the Foundation during the
-	quarter. These include improvements to the tmpfs
-	in-memory, MSDOS, and UFS filesystems, device
-	driver and hardware compatibility fixes, virtual
-	memory (VM), tool chain, documentation, and
-	testing and continuous integration improvements.</p>
-
-      <p>We fixed a number of race conditions and security issues
-	found by Syzkaller, Google&#8217;s
-	code-coverage-guided system call fuzzer.</p>
-
-      <p>Alan Somers&#8217; work on updating FreeBSD&#8217;s support for
-	FUSE (userspace filesystems) continued during the
-	quarter; the full details are elsewhere in this
-	quarterly report. At this point most of the work
-	has been committed to the project branch but some
-	bug fixes and improvements have been committed
-	directly to the FreeBSD development branch.</p>
-
-      <p>Edward Napierala&#8217;s Linuxulator project continued through
-	the quarter, resulting in a number of improvements
-	to the Linuxulator and linux-specific
-	functionality such as linsysfs. This work is part
-	of the path to supporting the Linux strace
-	debugging tool in order to facilitate debugging
-	failures of other Linux binaries under the
-	Linuxulator. Mateusz Guzik continued with
-	scalability and performance improvements during
-	the quarter, and Bjoern Zeeb integrated the SDIO
-	stack (with details elsewhere in the quarterly
-	report).</p>
-
-      <p>Progress was made on the online RAID-Z expansion project
-	over the quarter. Matt Ahrens posted an <a href="https://github.com/zfsonlinux/zfs/pull/8853" shape="rect">alpha
-	preview</a> of the feature for further
-	experimentation and review, and the FreeBSD
-	Foundation will make an alpha release image
-	available for testing in the near future.</p>
-
-      <p>Foundation staff contributed to nine FreeBSD security
-	advisories and errata updates over the quarter,
-	including CPU vulnerability workarounds. Related
-	work included improving Intel microcode update
-	loading.</p>
-
-      <p>Continuous Integration and Quality Assurance</p>
-      <p>
-	The Foundation provides a full-time staff member who is
-	working on improving our automated testing,
-	continuous integration, and overall quality
-	assurance efforts.</p>
-
-      <p>During the second quarter of 2019, Foundation staff
-	continued to improve the project's CI
-	infrastructure, worked with contributors to fix
-	the failing build and test cases, and worked with
-	other teams in the Project for their testing
-	needs. We hosted a CI-focused working group at
-	BSDcan and continue to publish the CI weekly
-	report at <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing@</a>
-	mailing list.</p>
-
-      <p>See the FreeBSD CI section of this report for more
-	information.</p>
-
-      <p>
-	Supporting FreeBSD Infrastructure</p>
-      <p>
-	The Foundation provides hardware and support to improve
-	the FreeBSD infrastructure. Last quarter, we
-	continued supporting FreeBSD hardware located
-	around the world.</p>
-
-      <p>FreeBSD Advocacy and Education</p>
-      <p>
-	A large part of our efforts are dedicated to advocating
-	for the Project. This includes promoting work
-	being done by others with FreeBSD; producing
-	advocacy literature to teach people about FreeBSD
-	and help make the path to starting using FreeBSD
-	or contributing to the Project easier; and
-	attending and getting other FreeBSD contributors
-	to volunteer to run FreeBSD events, staff FreeBSD
-	tables, and give FreeBSD presentations.</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events,
-	and summits around the globe. These events can be
-	BSD-related, open source, or technology events
-	geared towards underrepresented groups. We support
-	the FreeBSD-focused events to help provide a venue
-	for sharing knowledge, to work together on
-	projects, and to facilitate collaboration between
-	developers and commercial users. This all helps
-	provide a healthy ecosystem. We support the
-	non-FreeBSD events to promote and raise awareness
-	of FreeBSD, to increase the use of FreeBSD in
-	different applications, and to recruit more
-	contributors to the Project.</p>
-
-      <p>Check out some of the advocacy and education work we did
-	last quarter:</p>
-
-      <ul>
-	<li>Represented FreeBSD at LinuxFest Northwest In Bellingham,
-	Washington</li>
-
-	<li>Sponsored and helped organize the FreeBSD Developers
-	Summit at BSDCan, in Ottawa, Canada</li>
-
-	<li>Sponsored and attended BSDCan 2019</li>
-
-	<li>Set up registration and attended the Vienna FreeBSD
-	Security Hackathon in Vienna, Austria</li>
-
-	<li>Represented FreeBSD at HKOSCON</li>
-
-	<li>Attended the Berlin FreeBSD Developers Summit</li>
-
-	<li>Presented at 2019 Comcast Labs Connect Open Source
-	Conference</li>
-
-	<li>Sponsored, presented and represented FreeBSD at RootConf
-	2019 in Bangalore, India</li>
-
-	<li>Committed to attend OSCON, and All Things Open</li>
-
-	<li>Committed to sponsor and help organize a Bay Area
-	Developers Summit</li>
-
-	<li>Provided FreeBSD advocacy material</li>
-
-	<li>Provided travel grants to FreeBSD contributors to attend
-	many of the above events</li>
-      </ul>
-
-      <p>
-	We continued producing FreeBSD advocacy material to help
-	people promote FreeBSD around the world.</p>
-
-      <p>Read more about our conference adventures in the
-	conference recaps and trip reports in our
-	<a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">monthly
-	newsletters</a>.</p>
-
-      <p>We help educate the world about FreeBSD by publishing the
-	professionally produced FreeBSD Journal. As we
-	mentioned previously, the FreeBSD Journal is now a
-	free publication. Find out more and access the
-	latest issues at
-	<a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>.</p>
-
-      <p>You can find out more about
-	<a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">events
-	we attended and upcoming events</a>.</p>
-
-      <p>We have continued our work with a new website developer to
-	help us improve our website. Work has begun to
-	make it easier for community members to find
-	information more easily and to make the site more
-	efficient.</p>
-
-      <p>Legal/FreeBSD IP</p>
-      <p>
-	The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to protect them. We also provide
-	legal support for the core team to investigate
-	questions that arise.</p>
-
-      <p>Go to http://www.FreeBSDfoundation.org to find out how we
-	support FreeBSD and how we can help you!</p>
-    <hr /><h2><a name="FreeBSD-Graphics-Team-status-report" href="#FreeBSD-Graphics-Team-status-report" id="FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop" title="https://github.com/FreeBSDDesktop">Project GitHub page</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop" title="Project GitHub page">https://github.com/FreeBSDDesktop</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:x11@freebsd.org">x11@freebsd.org</a>&gt;
-	<br />
-	Contact: Niclas Zeising &lt;<a href="mailto:zeising@freebsd.org">zeising@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD X11/Graphics team maintains the lower levels
-	of the FreeBSD graphics
-	stack.
-	This includes graphics drivers, graphics libraries such as
-	the
-	MESA OpenGL implementation, the X.org xserver with related
-	libraries and
-	applications, and Wayland with related libraries and
-	applications.</p>
-
-      <p>In the last report, half a year ago, several updates and
-	changes had been made
-	to the FreeBSD graphics stack.</p>
-
-      <p>To further improve the user experience, and to improve
-	input device handling,
-	evdev was enabled in the default configuration in late
-	2018. Building on that,
-	we have enabled IBM/Lenovo trackpoints and elantech and
-	synaptics touchpads by
-	default as well.</p>
-
-      <p>The input device library libinput has been updated as the
-	last in a series of
-	updates bringing the userland input stack up to date.
-	This is work that was started in 2018.</p>
-
-      <p>We have made several improvements to the drm kernel
-	drivers.
-	A long-standing memory leak in the Intel (i915) driver has
-	been fixed, and
-	several other updates and improvements have been made to
-	the various drm
-	kernel driver components.</p>
-
-      <p>A port of the drm kernel drivers using the 5.0 Linux
-	kernel sources has been
-	created and committed to FreeBSD ports as
-	<tt>graphics/drm-devel-kmod</tt>.
-	This driver requires a recent Linux KPI and is only
-	available on recent
-	versions of FreeBSD CURRENT.</p>
-
-      <p>This version of the driver contains several development
-	improvements.
-	The generic drm (drm.ko) driver as well as the i915
-	(i915kms.ko) driver
-	can now be unloaded and reloaded to ease in development
-	and testing.
-	This causes issues with the virtual consoles, however, so
-	an SSH connection is
-	recommended.
-	To aid debugging <tt>i915kms.ko</tt> use of debugfs has
-	been improved, but there are
-	still limitations preventing it from being fully
-	functional.
-	Since debugfs is based on pseudofs it is possible that
-	this will prevent a fully
-	functional debugfs in its current state, so we might have
-	to look into adding
-	the required functionality to pseudofs or use another
-	framework.</p>
-
-      <p>The new in-kernel drm driver for VirtualBox,
-	<tt>vboxvideo.ko</tt> has been ported from
-	Linux.
-	Support is currently an experimental work in progress.
-	For example the virtual console won't update after loading
-	the driver, but X-
-	and Wayland-based compositors are working.</p>
-
-      <p>Mesa has been updated to 18.3.2 and switched from using
-	<tt>devel/llvm60</tt> to use
-	the Ports default version of llvm, currently
-	<tt>devel/llvm80</tt>.</p>
-
-      <p>Several userland Xorg drivers, applications, and libraries
-	have been updated,
-	and other improvements to the various userland components
-	that make up the
-	Graphics Stack have been made.</p>
-
-      <p>We have also continued our regularly scheduled bi-weekly
-	meetings, although work
-	remains in sending out timely meeting minutes afterwards.</p>
-
-      <p>People who are interested in helping out can find us on
-	the x11@FreeBSD.org
-	mailing list, or on our gitter chat: <a href="https://gitter.im/FreeBSDDesktop/Lobby" shape="rect">https://gitter.im/FreeBSDDesktop/Lobby</a>.
-	We are also available in #freebsd-xorg on EFNet.</p>
-
-      <p>We also have a team area on GitHub where our work
-	repositories can be found:
-	<a href="https://github.com/FreeBSDDesktop" shape="rect">https://github.com/FreeBSDDesktop</a></p>
-
-    <hr /><h2><a name="IRC-Admin" href="#IRC-Admin" id="IRC-Admin">IRC Admin</a></h2><p>
-	Contact: IRC Admin &lt;<a href="mailto:irc@FreeBSD.org">irc@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD IRC Admin team manages the FreeBSD Project's
-	presence
-	and activity on the freenode IRC network, looking after:</p>
-
-      <ul>
-	<li>Registration and management of channels within the
-	official namespace (#freebsd*)</li>
-
-	<li>Channel moderation</li>
-
-	<li>Liaising with freenode staff</li>
-
-	<li>Allocating <tt>freebsd/*</tt> hostmask cloaks for users</li>
-
-	<li>General user support relating to channel management</li>
-      </ul>
-
-      <p>
-	While the FreeBSD Project does not <tt>currently</tt>
-	endorse IRC as an
-	official support channel (see
-	<a href="https://www.freebsd.org/community/irc.html" shape="rect">here</a>
-	and <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/support.html#irc" shape="rect">here</a>),
-	as it has not been able to guarantee
-	a consistent or positive user experience, IRC Admin has
-	been working
-	toward creating a high quality experience, by
-	standardising channel
-	administration and moderation expectations, and ensuring
-	the projects
-	ability to manage all channels within its namespace.</p>
-
-      <p>In the last quarter, IRC Admin:</p>
-
-      <ul>
-	<li>Cleaned up (deregistered) registrations for channels that
-	were defunct,
-	stale, out of date, or had founders that were inactive
-	(not seen for &gt; 1
-	year). Channels that were found to be otherwise active
-	have been retained.
-	FreeBSD now has ~40 channels registered from a previous
-	total of over 150.</li>
-
-	<li>Documented baseline configuration settings in the Wiki for
-	channels,
-	including ChanServ settings, channel modes, registration
-	policy, etc.</li>
-
-	<li>Established multiple documented methods for reporting user
-	abuse
-	or other channel issues to IRC Admin for resolution</li>
-      </ul>
-
-      <p>
-	Upcoming changes:</p>
-
-      <ul>
-	<li>Work with existing <tt>#freebsd*</tt> channels to
-	standardise channel management,
-	settings and access.</li>
-
-	<li>Migrate, forward and/or consolidate existing or duplicate
-	<tt>#freebsd*</tt>
-	channels to channels with a standard naming convention.</li>
-
-	<li>Work with unofficial <tt>##freebsd*</tt> channels to
-	migrate them to the official
-	<tt>#freebsd*</tt> channels if suitable</li>
-
-	<li>Update existing IRC-related website and documentation
-	sources the describe
-	the official state of project managed IRC presence on
-	freenode.</li>
-      </ul>
-
-      <p>
-	Lastly, and to repeat a previous call, while the vast
-	majority of
-	the broader user community interacts on the freenode IRC
-	network,
-	the FreeBSD developer presence still needs to be
-	significantly
-	improved on freenode.</p>
-
-      <p>There are many opportunities to be had by increasing the
-	amount and
-	quality of interaction between FreeBSD users and
-	developers, both
-	in terms of developers keeping their finger on the pulse
-	of the
-	community and in encouraging and cultivating greater
-	contributions
-	to the Project over the long term.</p>
-
-      <p>It is critical to have a strong developer presence amongst
-	users,
-	and IRC Admin would like again to call on all developers
-	to join
-	the FreeBSD freenode channels to increase that presence.</p>
-
-      <p>Users are invited to <tt>/join #freebsd-irc</tt> on the
-	freenode IRC network
-	if they have questions, ideas, constructive criticism, and
-	feedback
-	on how the FreeBSD Project can improve the service and
-	experience
-	it provides to the community on IRC.</p>
-
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The following was done during the last quarter by portmgr
-	to keep things in
-	the Ports Tree going:</p>
-
-      <p>During the last quarter the number of ports rose to just
-	under 37,000. At the
-	end of the quarter, there were 2146 open PRs and 7837
-	commits (excluding 499 on
-	the quarterly branch) from 172 committers. This shows a
-	slight decrease in
-	activity compared to previous quarter.</p>
-
-      <p>People come and go, last quarter we welcomed Pedro Giffuni
-	(pfg@), Piotr Kubaj
-	(pkubaj@) and Hans Petter Selasky (hselasky@). Pedro and
-	Hans Petter were
-	already active as src committers. We said goodbye to
-	gordon@, kan@, tobez@,
-	and wosch@.</p>
-
-      <p>On the infrastructure side, a new USES=cabal was
-	introduced and various default
-	versions were updated: MySQL to 5.7, Python to 3.6, Ruby
-	to 2.5, Samba to 4.8
-	and Julia gained a default version of 1.0. The web
-	browsers were also updated:
-	Firefox to 68.0 and Chromium to 75.0.3770.100</p>
-
-      <p>During the last quarter, antoine@ ran a total of 41
-	exp-runs to test various
-	package updates, bump the stack protector level to
-	"strong", switch the default
-	Python version to 3.6 as opposed to 2.7, remove sys/dir.h
-	from base which has
-	been deprecated for over 20 years, and convert all Go
-	ports to USES=go.</p>
-
-    <hr /><h2><a name="Release-Engineering-Team" href="#Release-Engineering-Team" id="Release-Engineering-Team">Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/11.3R/schedule.html" title="https://www.freebsd.org/releases/11.3R/schedule.html">FreeBSD 11.3-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.3R/schedule.html" title="FreeBSD 11.3-RELEASE schedule">https://www.freebsd.org/releases/11.3R/schedule.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/11.3R/announce.html" title="https://www.freebsd.org/releases/11.3R/announce.html">FreeBSD 11.3-RELEASE announcement</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.3R/announce.html" title="FreeBSD 11.3-RELEASE announcement">https://www.freebsd.org/releases/11.3R/announce.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/12.1R/schedule.html" title="https://www.freebsd.org/releases/12.1R/schedule.html">FreeBSD 12.1-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/12.1R/schedule.html" title="FreeBSD 12.1-RELEASE schedule">https://www.freebsd.org/releases/12.1R/schedule.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for
-	setting
-	and publishing release schedules for official project
-	releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>During the second quarter of 2019, the FreeBSD Release
-	Engineering team
-	started the 11.3-RELEASE cycle, with the code slush
-	starting May 3rd.
-	Throughout the cycle, there were three BETA builds and
-	three RC builds,
-	all of which in line with the originally-published
-	schedule. The final RC
-	build started June 28th, with the final release build
-	targeted for July 5th.</p>
-
-      <p>FreeBSD 11.3-RELEASE will be the fourth release from the
-	<tt>stable/11</tt>
-	branch, building on the stability and reliability of
-	11.2-RELEASE.</p>
-
-      <p>The FreeBSD Release Engineering Team also published the
-	schedule for the
-	12.1-RELEASE, targeted to start September 6th. One
-	important thing to note
-	regarding the published schedule is it excludes a hard
-	freeze on the
-	<tt>stable/12</tt> branch, as a test run for eliminating
-	code freezes entirely during
-	a release cycle. Commits to what will be the
-	<tt>releng/12.1</tt> branch will still
-	require explicit approval from the Release Engineering
-	Team, however.</p>
-
-      <p>Additionally throughout the quarter, several development
-	snapshots builds
-	were released for the <tt>head</tt>, <tt>stable/12</tt>,
-	and <tt>stable/11</tt> branches.</p>
-
-      <p>Much of this work was sponsored by the FreeBSD Foundation
-	and Rubicon
-	Communications, LLC (Netgate).</p>
-
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="bhyve---Live-Migration" href="#bhyve---Live-Migration" id="bhyve---Live-Migration">bhyve - Live Migration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve">Github wiki - How to Live and Warm Migrate a bhyve guest</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve" title="Github wiki - How to Live and Warm Migrate a bhyve guest">https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration">Github - Warm Migration branch</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration" title="Github - Warm Migration branch">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev">Github - Live Migration branch</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev" title="Github - Live Migration branch">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev</a></td></tr></table><p>
-	Contact: Elena Mihailescu &lt;<a href="mailto:elenamihailescu22@gmail.com">elenamihailescu22@gmail.com</a>&gt;
-	<br />
-	Contact: Darius Mihai &lt;<a href="mailto:dariusmihaim@gmail.com">dariusmihaim@gmail.com</a>&gt;
-	<br />
-	Contact: Mihai Carabas &lt;<a href="mailto:mihai@freebsd.org">mihai@freebsd.org</a>&gt;
-	</p>
-      <p>The Migration feature uses the Save/Restore feature to
-	migrate a bhyve guest
-	from a FreeBSD host to another FreeBSD host. To migrate a
-	bhyve guest,
-	one needs to start an empty guest on the destination host
-	from a shared guest
-	image using the bhyve tool with the <tt>-R</tt> option
-	followed by the source host
-	IP and the port to listen to migration request. On the
-	source host, the
-	migration is started by executing the bhyvectl command
-	with the <tt>--migrate</tt>
-	or <tt>--migrate-live</tt> option, followed by the
-	destination host IP and the
-	port to send to the messages.</p>
-
-      <p>New features added:</p>
-
-      <ul>
-	<li>Clear the dirty bit after each migration round</li>
-
-	<li>Extend live migration to highmem segment</li>
-      </ul>
-
-      <p>
-	Future tasks:</p>
-
-      <ul>
-	<li>Refactor live migration branch</li>
-
-	<li>Rebase live migration</li>
-
-	<li>Extend live migration to unwired memory</li>
-      </ul>
-
-    <p>This project was sponsored by Matthew Grooms.</p><hr /><h2><a name="bhyve---Save/Restore" href="#bhyve---Save/Restore" id="bhyve---Save/Restore">bhyve - Save/Restore</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_snapshot" title="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_snapshot">Github repository for the snapshot feature for bhyve</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_snapshot" title="Github repository for the snapshot feature for bhyve">https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_snapshot</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve">Github wiki - How to Save and Restore a bhyve guest</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve" title="Github wiki - How to Save and Restore a bhyve guest">https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve</a></td></tr><tr><td><a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix" title="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix">Github wiki - Suspend/resume test matrix</a></td><td>
-	    URL: <a href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix" title="Github wiki - Suspend/resume test matrix">https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D19495" title="https://reviews.freebsd.org/D19495">Phabricator review - bhyve Snapshot Save and Restore</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D19495" title="Phabricator review - bhyve Snapshot Save and Restore">https://reviews.freebsd.org/D19495</a></td></tr></table><p>
-	Contact: Elena Mihailescu &lt;<a href="mailto:elenamihailescu22@gmail.com">elenamihailescu22@gmail.com</a>&gt;
-	<br />
-	Contact: Darius Mihai &lt;<a href="mailto:dariusmihaim@gmail.com">dariusmihaim@gmail.com</a>&gt;
-	<br />
-	Contact: Mihai Carabas &lt;<a href="mailto:mihai@freebsd.org">mihai@freebsd.org</a>&gt;
-	</p>
-      <p>The Save/Restore for bhyve feature is a suspend and resume
-	facility added to the
-	FreeBSD/amd64's hypervisor, bhyve. The bhyvectl tool is
-	used to save the guest
-	state in three files (a file for the guest memory, a file
-	for the states of
-	various devices and the state of the CPU, and another one
-	for some metadata that
-	is used in the restore process).
-	To suspend a bhyve guest, the bhyvectl tool must be run
-	with the <tt>--suspend
-	&lt;state_file_name&gt;</tt>
-	option followed by the guest name.</p>
-
-      <p>To restore a bhyve guest from a checkpoint, one simply has
-	to add the <tt>-r</tt> option
-	followed by the main state file (the same file that was
-	given to the <tt>--suspend</tt>
-	option for bhyvectl) when starting the VM.</p>
-
-      <p>New features added:</p>
-
-      <ul>
-	<li>Open ticket on Phabricator</li>
-
-	<li>Apply feedback received from community</li>
-      </ul>
-
-      <p>
-	Future tasks:</p>
-
-      <ul>
-	<li>Add suspend/resume support for nvme</li>
-
-	<li>Add suspend/resume support for virtio-console</li>
-
-	<li>Add suspend/resume support for virtio-scsi</li>
-
-	<li>Add TSC offsetting for restore for AMD CPUs</li>
-      </ul>
-
-    <p>This project was sponsored by Matthew Grooms.</p><hr /><h2><a name="BIO_DELETE-support-for-the-swap-pager" href="#BIO_DELETE-support-for-the-swap-pager" id="BIO_DELETE-support-for-the-swap-pager">BIO_DELETE support for the swap pager</a></h2><p>
-	Contact: Doug Moore &lt;<a href="mailto:dougm@FreeBSD.org">dougm@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Alan Cox &lt;<a href="mailto:alc@FreeBSD.org">alc@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	</p>
-      <p>An ongoing project aims to teach the swap pager to send
-	SCSI UNMAP or
-	ATA TRIM commands to the swap device when a block of swap
-	space has been
-	freed, for example when the application owning that block
-	is exiting.</p>
-
-      <p>SSDs have become commonplace and feature low latency for
-	random I/O
-	requests. This makes them appealing for use as swap
-	devices, since
-	lower latencies mean that applications spend less time
-	blocked while
-	waiting for a page-in from the swap device. To maximize
-	write
-	performance, some SSDs require the operating system to
-	send a
-	notification to the disk when a sector is no longer in
-	use; this helps
-	the disk optimize their usage of NAND flash cells. In
-	FreeBSD such a
-	notification is called a BIO_DELETE.</p>
-
-      <p>FreeBSD's UFS and ZFS filesystems have for a long time
-	been able to
-	transmit BIO_DELETE requests to the devices backing the
-	filesystem. For
-	example, for UFS this support is enabled by specifying -t
-	in newfs(8) or
-	tunefs(8)'s parameters. However, FreeBSD has historically
-	not had a
-	corresponding implementation for swap devices.</p>
-
-      <p>Thanks to Doug Moore, as of r349286 in -CURRENT and
-	r349930 in stable/12
-	swapon(8) can send BIO_DELETE to all blocks on the
-	specified device
-	immediately prior to configuring it as a swap device. This
-	is enabled
-	by specifying -E in the swapon(8) parameters, or by adding
-	the
-	"trimonce" option to the swap device's /etc/fstab entry.
-	Some
-	in-progress work on the swap pager implements online block
-	deletion, in
-	which BIO_DELETE is transmitted for blocks as they are
-	freed by
-	applications; this will hopefully be implemented in
-	FreeBSD 13.0.</p>
-
-    <hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Maciej Bielski &lt;<a href="mailto:mba@semihalf.com">mba@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p>
-      <p>ENA (Elastic Network Adapter) is the smart NIC available
-	in the
-	virtualized environment of Amazon Web Services (AWS). The
-	ENA
-	driver supports multiple transmit and receive queues and
-	can handle
-	up to 100 Gb/s of network traffic, depending on the
-	instance type
-	on which it is used.</p>
-
-      <p>ENAv2 has been under development for FreeBSD, similar to
-	Linux
-	and DPDK. Since the last update internal review and
-	improvements
-	of the patches were done, followed by validation on
-	various AWS
-	instances.</p>
-
-      <p>Completed since the last update:</p>
-
-      <ul>
-	<li>Upstream of the ENAv2 patches - revisions
-	<a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=348383" shape="rect">r348383</a>
-	-
-	<a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=348416" shape="rect">r348416</a>
-	introduce a major driver upgrade to version v2.0.0. Along
-	with various fixes
-	and improvements, the most significant features are LLQ
-	(Low Latency Queues)
-	and independent queues reconfiguration using sysctl
-	commands.</li>
-
-	<li>Implement NETMAP support for ENA</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Internal review and upstream of NETMAP support</li>
-      </ul>
-
-    <p>This project was sponsored by Amazon.com Inc.</p><hr /><h2><a name="FreeBSD-SDIO-and-Broadcom-FullMAC-WiFi-Support" href="#FreeBSD-SDIO-and-Broadcom-FullMAC-WiFi-Support" id="FreeBSD-SDIO-and-Broadcom-FullMAC-WiFi-Support">FreeBSD SDIO and Broadcom FullMAC WiFi Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SDIO" title="https://wiki.freebsd.org/SDIO">FreeBSD Wiki SDIO page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SDIO" title="FreeBSD Wiki SDIO page">https://wiki.freebsd.org/SDIO</a></td></tr></table><p>
-	Contact: Bjoern Zeeb &lt;<a href="mailto:bz@FreeBSD.ORG">bz@FreeBSD.ORG</a>&gt;
-	</p>
-      <p>SDIO is an interface designed as an extension to SD Cards
-	to allow attachments of various other peripherals, e.g.,
-	WiFi or Bluetooth.</p>
-
-      <p>Work has been ongoing by Ilya Bakulin on the MMCCAM stack
-	to provide the infrastructure to be able to have SD cards
-	and SDIO devices attached side-by-side facilitating
-	FreeBSD's CAM framework.
-	Based on this excellent work over the last years,
-	SDIO support was finished earlier this year and committed
-	to FreeBSD HEAD with the intention to merge to 12 at a
-	later time.</p>
-
-      <p>Facilitating the newly available SDIO bus, work started to
-	port Broadcom's FullMAC WiFi driver. This work is still
-	in progress and expected to complete later this year.
-	With this WiFi support for the Raspberry Pi and other
-	embedded boards will become available.
-	Likewise drivers for other SDIO devices can be developed
-	now.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="FUSE" href="#FUSE" id="FUSE">FUSE</a></h2><p>
-	Contact: Alan Somers &lt;<a href="mailto:asomers@FreeBSD.org">asomers@FreeBSD.org</a>&gt;
-	</p>
-      <p>FUSE (File system in USErspace) allows a userspace program
-	to
-	implement a file system. It is widely used to support
-	out-of-tree file
-	systems like NTFS, as well as for exotic pseudo file
-	systems like
-	sshfs. FreeBSD's fuse driver was added as a GSoC project
-	in 2012.
-	Since that time, it has been largely neglected. The FUSE
-	software is
-	<a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&amp;known_name=fusefs&amp;list_id=289348&amp;query_based_on=fusefs&amp;query_format=advanced&amp;short_desc=%5Bfusefs%5D%20sysutils%2Ffusefs-&amp;short_desc_type=anywordssubstr" shape="rect">buggy</a>
-	and out-of-date. Our implementation is about 11 years
-	behind.</p>
-
-      <p>During Q2 I nearly finished the FUSE overhaul that I
-	begain in Q1. I raised
-	the protocol level from 7.8 to 7.23, fixed many bugs (see
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199934" shape="rect">199934</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216391" shape="rect">216391</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233783" shape="rect">233783</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234581" shape="rect">234581</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235773" shape="rect">235773</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235774" shape="rect">235774</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235775" shape="rect">235775</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236226" shape="rect">236226</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236231" shape="rect">236231</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236236" shape="rect">236236</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239291" shape="rect">239291</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236329" shape="rect">236329</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236379" shape="rect">236379</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236381" shape="rect">236381</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236405" shape="rect">236405</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236327" shape="rect">236327</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236466" shape="rect">236466</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236472" shape="rect">236472</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236473" shape="rect">236473</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236474" shape="rect">236474</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236530" shape="rect">236530</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236557" shape="rect">236557</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236560" shape="rect">236560</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236647" shape="rect">236647</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236844" shape="rect">236844</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237052" shape="rect">237052</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237181" shape="rect">237181</a>,
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237588" shape="rect">237588</a>,
-	and
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238565" shape="rect">238565</a>),
-	and added
-	the following features:</p>
-
-      <ul>
-	<li>Optional kernel-side permissions checks (`-o
-	default_permissions`)</li>
-
-	<li>Implement <tt>VOP_MKNOD</tt>, <tt>VOP_BMAP</tt>, and
-	<tt>VOP_ADVLOCK</tt></li>
-
-	<li>Allow interrupting FUSE operations</li>
-
-	<li>Support named pipes and unix-domain sockets in fusefs file
-	systems</li>
-
-	<li>Forward <tt>UTIME_NOW</tt> during <tt>utimensat(2)</tt> to
-	the daemon</li>
-
-	<li><tt>kqueue</tt> support for <tt>/dev/fuse</tt></li>
-
-	<li>Allow updating mounts with <tt>mount -u</tt></li>
-
-	<li>Allow exporting fusefs file systems over NFS</li>
-
-	<li>Server-initiated invalidation of the name cache or data
-	cache</li>
-
-	<li>Respect <tt>RLIMIT_FSIZE</tt></li>
-
-	<li>Try to support servers as old as protocol 7.4</li>
-      </ul>
-
-      <p>
-	I also added the following performance enhancements:</p>
-
-      <ul>
-	<li>Implement FUSE's <tt>FOPEN_KEEP_CACHE</tt> and
-	<tt>FUSE_ASYNC_READ</tt> flags</li>
-
-	<li>Cache file attributes</li>
-
-	<li>Cache lookup entries, both positive and negative</li>
-
-	<li>Server-selectable cache modes: writethrough, writeback, or
-	uncached</li>
-
-	<li>Write clustering</li>
-
-	<li>Readahead</li>
-
-	<li>Use <tt>counter(9)</tt> for statistical reporting</li>
-      </ul>
-
-      <p>
-	All that remains is to finish merging the branch, and deal
-	with any newly
-	introduced bugs.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Fuzzing-FreeBSD-with-syzkaller" href="#Fuzzing-FreeBSD-with-syzkaller" id="Fuzzing-FreeBSD-with-syzkaller">Fuzzing FreeBSD with syzkaller</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/google/syzkaller" title="https://github.com/google/syzkaller">syzkaller</a></td><td>
-	    URL: <a href="https://github.com/google/syzkaller" title="syzkaller">https://github.com/google/syzkaller</a></td></tr></table><p>
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Michael Tuexen &lt;<a href="mailto:tuexen@FreeBSD.org">tuexen@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>See the syzkaller entry in the 2019q1 quarterly report for
-	an
-	introduction to syzkaller.</p>
-
-      <p>syzkaller continues to find FreeBSD kernel bugs. A number
-	of
-	such bugs have been fixed in the past quarter, and we
-	continue
-	to investigate and fix bug reports from syzkaller. Work to
-	extend syzkaller's capabilites has progressed: Andrew
-	Turner
-	has implemented support for fuzzing the 32-bit
-	compatibility
-	layer in amd64 kernels, helping illuminate some of the
-	darker
-	corners of the kernel, and it is now possible to use bhyve
-	as
-	a VM backend to syzkaller, so it is now efficient and
-	convenient
-	to fuzz FreeBSD on FreeBSD.</p>
-
-      <p>Some planned work includes: enabling the use of ZFS as the
-	base filesystem for fuzzer VMs; extending the range of
-	system
-	calls and ioctls covered by syzkaller; enabling LLVM
-	sanitizers
-	in the kernel so as to catch more issues; and making use
-	of
-	netdump(4) to capture kernel dumps for panics found by
-	syzkaller,
-	making it much easier to diagnose bugs for which syzkaller
-	was
-	unable to find a reproducible test case.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Kernel-ZLIB-Update" href="#Kernel-ZLIB-Update" id="Kernel-ZLIB-Update">Kernel ZLIB Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D19706" title="https://reviews.freebsd.org/D19706">Review D19706</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D19706" title="Review D19706">https://reviews.freebsd.org/D19706</a></td></tr></table><p>
-	Contact: Yoshihiro Ota &lt;<a href="mailto:ota@j.email.ne.jp">ota@j.email.ne.jp</a>&gt;
-	</p>
-      <p>Kernel zlib upgrade is in progress.</p>
-
-      <p>Xin (delphij@) and I have been working closely for zlib
-	upgrade.
-	We relocated contrib/zlib to sys/contrib/zlib in order for
-	kernel
-	code to access zlib in the tree. We also deleted dead code
-	that
-	depended on zlib and inflate - inflate is a fork of unzip
-	to
-	uncompress gzip files. We also renamed crc.h to avoid
-	conflicts
-	with zlib/crc.h.</p>
-
-      <p>Next goal is to compile both old zlib and new zlib into
-	the kernel
-	allowing to switch each zlib user independently.</p>
-
-    <hr /><h2><a name="Linux-compatibility-layer-update" href="#Linux-compatibility-layer-update" id="Linux-compatibility-layer-update">Linux compatibility layer update</a></h2><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p>
-      <p>The project aims to improve the Linux compatibility layer,
-	to make
-	it more compatible with recent Linux releases, and also to
-	lower
-	the bar for potential developers who want to start
-	contributing to it.</p>
-
-      <p>The initial effort focused on tooling, to make it easier
-	to debug
-	problems and to prevent future regressions. The first part
-	involved
-	making it possible to use Linux strace(1) utility and
-	providing it
-	as <tt>linux-c7-strace</tt> package. The reason is that
-	while FreeBSD
-	<tt>truss(1)</tt> and <tt>ktrace(1)</tt> can trace Linux
-	binaries, they cannot
-	decode Linux-specific flags and structures.</p>
-
-      <p>The second part involved providing Linux Test Project
-	binaries as
-	<tt>linux-ltp</tt> package. There is ongoing work to hook
-	it up to the
-	FreeBSD CI infrastructure <a href="http://ci.FreeBSD.org" shape="rect">http://ci.FreeBSD.org</a>.</p>
-
-      <p>There was also a number of improvements and fixes to bugs
-	discovered
-	in the process. One of them (not yet committed) fixes
-	binaries
-	linked against newer version of libc, effectively
-	unbreaking binaries
-	from recent Ubuntu releases.</p>
-
-    <p>This project was sponsored by FreeBSD Foundation.</p><hr /><h2><a name="Lock-less-delayed-invalidation-for-amd64-pmap" href="#Lock-less-delayed-invalidation-for-amd64-pmap" id="Lock-less-delayed-invalidation-for-amd64-pmap">Lock-less delayed invalidation for amd64 pmap</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@freebsd.org">kib@freebsd.org</a>&gt;
-	</p>
-      <p>The Virtual Memory machine-dependent layer (pmap) on amd64
-	needs to
-	track all mappings for the managed physical memory pages,
-	to be able
-	to either destroy all of them (for page-out), or change
-	them from
-	writeable to read-only (e.g. to sync the page content to
-	file, without
-	racing with modifications through user writes). The
-	mappings are
-	accounted by creating pv_entry which records the address
-	space
-	(implicitly, by linking the pv entry to pmap) and the
-	virtual address
-	of the mapping.</p>
-
-      <p>Previous work split the lock protecting the pv entries
-	lists from
-	other VM locks into the pvh_global_lock lock, which was
-	global for all
-	address spaces. You can see it in i386 pmap.c still.
-	Later, hashed
-	per-page pv lists locks were introduced, which would
-	reduce contention
-	on pv lists maninulations for different pages, but
-	unfortunately the
-	pvh_global_lock was still needed to guarantee the safety
-	of some
-	operations.</p>
-
-      <p>Problem arises because amd64 pmap uses pmap lock to
-	protect page
-	tables and TLB consistency, which is per-pmap locks
-	different from pv
-	lists locks. When updating page table entry, we never drop
-	pmap lock
-	until the necessary TLB invalidation is done globally,
-	including
-	signalling other CPUs with IPI. But pv list locks can be
-	unlocked
-	before the necessary invalidation is done. So for instance
-	when pmap
-	is asked to remove all mappings of the specific page
-	(pmap_remove_all(9)), it checks pv list of the page to
-	find the
-	mappings. The list might appear empty despite other CPUs
-	TLB were not
-	yet invalidated. If such page is reused, other CPUs might
-	change its
-	content using cached TLB entries. Allowing that means
-	allowing both
-	silent data corruption and opening security hole.</p>
-
-      <p>So the global pvh lock was held until all pmaps
-	invalidated their
-	TLBs. This mechanism has obvious scalability issues, and
-	instead a
-	generation-count based scheme for handling delayed
-	invalidation (DI)
-	was developed, where each thread that might remove entry
-	from pv list
-	acquired a generation number and marked the page with it,
-	see
-	pmap_delayed_invl_page(9). Then, on e.g.
-	pmap_remove_all(9) or
-	pmap_remove_write(9), pmap code waits for the maximum
-	current thread's
-	invalidation generation number to pass the page's
-	generation, which
-	guarantees that all required TLB invalidations are done.</p>
-
-      <p>Original implementation of DI allowed to get rid of
-	pvh_global_lock,
-	and only used a private mutex to handle sequential
-	queueing of the
-	coming and leaving threads, protecting a bounded region. A
-	problem
-	with that appeared e.g. in scalability benchmarks which
-	did massive
-	parallel unmaps, causing most of the threads to contend on
-	DI
-	queueing.</p>
-
-      <p>Current implementation of DI switched to lock-less queue
-	algorithm
-	using the approach proposed by T.L. Harris and relying on
-	double-CAS
-	to coalesce generation count and queueing. It uses ifuncs
-	to select
-	either previous locked DI or current lock-less
-	implementation, only
-	old AMD Athlons which did not implemented the CMPXCHG16B
-	instruction
-	falls to the locked implementation by default. Lock-less
-	implementation still blocks the waiting thread on
-	turnstile to avoid
-	priority-inversion issues, but practically the wait occur
-	very rare,
-	typical parallel buildworld generates single-digit number
-	of the
-	events.</p>
-
-      <p>The patch got a lot of testing from Peter Holm, continuous
-	reviews by
-	Mark Johnston while I worked out bugs and live-lock
-	problems in the
-	implementation, and additional testing by Mateusz Guzik
-	who helped to
-	identify a priority inversion bug with the wait.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Locking-changes-for-vnodes-during-execve(2)" href="#Locking-changes-for-vnodes-during-execve(2)" id="Locking-changes-for-vnodes-during-execve(2)">Locking changes for vnodes during execve(2)</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@freebsd.org">kib@freebsd.org</a>&gt;
-	</p>
-      <p>The execve(2) family of syscalls replaces the executing
-	image in the
-	current process. The file containing the program text,
-	data, and
-	arbitrary other pre-initialized segments for the newly
-	activated image
-	is usually called the text file. FreeBSD marks the text
-	file as such,
-	the mark is mutually exclusive with any opening of the
-	file for write.
-	In other words, file opened for write cannot be executed,
-	and text
-	file cannot be opened for write.</p>
-
-      <p>During the execve(2) syscall processing, kernel needs to
-	lock the text
-	file' vnode. This is done both to satisfy the VFS calls
-	protocol, and
-	to ensure that there is no incompatible parallel changes
-	occuring to
-	the text vnode. A vnode can be locked either in exclusive
-	mode, which
-	is mutually incompatible with any other lock acquisition,
-	or in shared
-	mode, which is only incompatible with exclusive requests,
-	but allows
-	other shared owners.</p>
-
-      <p>In principle, there is no reason why would execve(2) need
-	an exclusive
-	vnode lock, since it does not modify neither content nor
-	metadata for
-	the text vnode. The only exception is the marking of the
-	vnode as
-	text, which was done using VV_TEXT flag in v_vflag and
-	protected by
-	the vnode lock. Since we modify v_vflag, the vnode lock
-	protecting
-	the modification should be taken exclusive.</p>
-
-      <p>The end result is that execve(2)'s of the same file are
-	serialized. For
-	instance, if user runs parallel build, which executes more
-	than one
-	job for compiling, all invocation of the compiler are
-	serialized
-	during execve(2).</p>
-
-      <p>The count of opens for write is contained in other struct
-	vnode member
-	named v_writecount, which was protected by the vnode lock
-	as well.
-	Since text is mutually exclusive with an open for write, I
-	reused
-	v_writecount to indicate text references. Now, negative
-	v_writecount
-	counts the number of text references. The v_writecount
-	content is
-	literally protected by the vnode interlock, but normally
-	all mutators
-	also own vnode lock at least in the shared mode.</p>
-
-      <p>This way, we no longer need to acquire exclusive text
-	vnode lock
-	during execve(2), removing the serializing point.
-	Additional positive
-	effect is that we started to account the precise number of
-	text
-	references on the vnode. Before, we cleared VV_TEXT on the
-	last unmap
-	of the text vnode, potentially allowing obscure DoS where
-	mapping the
-	text file while it is executed prevented writes until the
-	mapping is
-	destroyed. Now we mark the mappings for text explicitly in
-	the
-	vm_map_entry and dereference v_writecount by +1 when such
-	entry is
-	unmapped.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Mellanox-Drivers-Update" href="#Mellanox-Drivers-Update" id="Mellanox-Drivers-Update">Mellanox Drivers Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver" title="http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver">Mellanox OFED for FreeBSD Documentation</a></td><td>
-	    URL: <a href="http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver" title="Mellanox OFED for FreeBSD Documentation">http://www.mellanox.com/page/products_dyn?product_family=193&amp;mtag=freebsd_driver</a></td></tr></table><p>
-	Contact: Slava Shwartsman Hans Petter Selasky Konstantin Belousov &lt;<a href="mailto:freebsd-drivers@mellanox.com">freebsd-drivers@mellanox.com</a>&gt;
-	</p>
-      <p>The mlx5 driver provides support for ConnectX-4 [Lx],
-	ConnectX-5 [Ex] and
-	ConnectX-6 [Dx] adapter cards. The mlx5en driver provides
-	support for Ethernet
-	adapter cards, whereas mlx5ib driver provides support for
-	InfiniBand adapters
-	and RDMA over Converged Ethernet (RoCE).</p>
-
-      <p>Following updates done in mlx5 drivers:</p>
-
-      <ul>
-	<li>200Gb/s ConnectX-6 Ethernet:
-	Added support for <a href="http://www.mellanox.com/page/products_dyn?product_family=285&amp;amp;mtag=socketdc" shape="rect">Mellanox
-	Socket Direct Adapters</a>
-	which allows, among the rest of the capabilities, to run
-	up to 200Gb/s on a
-	PCIe Gen 3.0 on a LAG interface.</li>
-
-	<li>Support for "BlueField" - Multicore System On A Chip:
-	Added support for RShim driver for <a href="http://www.mellanox.com/products/bluefield-overview/" shape="rect">BlueField
-	Multicore System On A Chip(SOC)</a>.
-	The RShim driver provides access to the RShim resources on
-	the BlueField
-	target accessible from an external host machine. The
-	current RShim version
-	provides device files for boot image push and virtual
-	console access. It
-	also creates virtual network interface to connect to the
-	BlueField target
-	and provides access to internal RShim registers.</li>
-
-	<li>Firmware Burning and Diagnostics Tools:
-	Added MSTFLINT to ports, this package contains a burning
-	and diagnostic
-	tools for Mellanox NICs.
-	This package contains following tools:
-	mstflint - Tools which allows to query and burn firmware.
-	mstconfig - This tool queries and sets non-volatile
-	configurable options for
-	Mellanox HCAs.
-	mstregdump - This utility dumps hardware registers from
-	Mellanox hardware.
-	mstmcra - This debug utility reads/writes a to/from the
-	device
-	configuration register space.
-	mstvpd - This utility dumps the on-card VPD.
-	and more.</li>
-
-	<li>OFED-FreeBSD-v3.5.1 Upstream:
-	Pushed upstream and MFCed OFED-FreeBSD-v3.5.1 driver -
-	more details
-	on the content of this update can be found in <a href="http://www.mellanox.com/page/products_dyn?product_family=193&amp;amp;mtag=freebsd_driver" shape="rect">Mellanox
-	OFED for FreeBSD documentation</a> page.</li>
-      </ul>
-
-      <p>
-	General updates:</p>
-
-      <ul>
-	<li>Submitted papers for EuroBSDcon for a joint talk with
-	Netflix titled
-	"Kernel TLS and TLS Hardware Offload". The papers were
-	accepted.</li>
-
-	<li>Mellanox is intensively working to improve its cooperation
-	with the FreeBSD
-	community. As part of this effort, FreeBSD users are
-	invited to propose
-	features and enhancements to further develop and enrich
-	the end-user
-	experience. In addition, Mellanox continues to identify
-	and present the
-	right solutions to meet customers' needs.</li>
-      </ul>
-
-    <p>This project was sponsored by Mellanox Technologies.</p><hr /><h2><a name="NFSv4.2-client/server-implementation-for-FreeBSD" href="#NFSv4.2-client/server-implementation-for-FreeBSD" id="NFSv4.2-client/server-implementation-for-FreeBSD">NFSv4.2 client/server implementation for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base/projects/nfsv42" title="https://svnweb.freebsd.org/base/projects/nfsv42">current sources</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base/projects/nfsv42" title="current sources">https://svnweb.freebsd.org/base/projects/nfsv42</a></td></tr></table><p>
-	Contact: Rick Macklem &lt;<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>&gt;
-	</p>
-      <p>NFSv4.2 is a newer minor version of NFSv4, made up of a
-	set of optional
-	operations/features. A majority of these operations are
-	related to
-	the POSIX operations posix_fadvise(2), posix_fallocate(2)
-	and lseek(2)'s
-	support for SEEKHOLE/SEEKDATA. There is also a Copy
-	operation that allows
-	a byte range of a file to be copied to another file
-	locally on the NFS
-	server, avoiding data transfer over the wire in both
-	directions.
-	FreeBSD-current now has a Linux compatible
-	copy_file_range(2) syscall
-	that will invoke this Copy operation on NFSv4.2 mounts.
-	There is also support for MAC labelling, but it requires
-	changes to the
-	RPCSEC_GSS implementation to add V3 support and, as such,
-	may not happen
-	soon.</p>
-
-      <p>The implementation of NFSv4.2 (RFC-7862) is progressing
-	nicely.
-	At this time, the LayoutError, IOAdvise, Allocate and Copy
-	operations
-	have been implemented. There is still work to be done on
-	Copy, to add
-	asynchronous support, so that large copies do not result
-	in a long delay
-	for the RPC's reply.</p>
-
-      <p>The major operation that will be implemented next is Seek,
-	so that
-	lseek(SEEKHOLE/SEEKDATA) will work for the NFSv4.2 mounts.</p>
-
-      <p>It is hoped that this implementation will be ready for
-	FreeBSD-current/head
-	in time for the FreeBSD-13 release.</p>
-
-      <p>Testing is always appreciated and can be done by
-	downloading the modified
-	kernel from the svn repository in base/rojects/nfsv42 and
-	then building
-	and testing it on a couple of recent FreeBSD-current
-	systems.</p>
-
-      <p>If anyone is conversant with Kerberos and wants to take on
-	the challenge
-	of adding RPCSEC_GSS_V3 support to the kernel RPC, a patch
-	that does
-	that would also be greatly appreciated.</p>
-
-    <hr /><h2><a name="NUMA-awareness-in-the-FreeBSD-kernel" href="#NUMA-awareness-in-the-FreeBSD-kernel" id="NUMA-awareness-in-the-FreeBSD-kernel">NUMA awareness in the FreeBSD kernel</a></h2><p>
-	Contact: Jeff Roberson &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Andrew Gallatin &lt;<a href="mailto:gallatin@FreeBSD.org">gallatin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	</p>
-      <p>A set of patches to improve the state of NUMA awareness in
-	the FreeBSD
-	kernel are being developed and refined. This work also
-	aims to
-	generally improve the performance of FreeBSD's memory
-	management
-	subsystem on systems with many CPUs.</p>
-
-      <p>FreeBSD 12.0 featured a number of large changes which
-	improve its
-	performance on systems with a non-uniform memory
-	architecture. That is,
-	systems in which memory access latency for a given address
-	varies
-	depending on the CPU. Another round of improvements is
-	being developed
-	and will soon be available in FreeBSD-CURRENT. Short
-	descriptions of
-	some of these patches follow; a few have already been
-	committed to
-	FreeBSD-CURRENT.</p>
-
-      <p>In FreeBSD terminology, a memory page whose contents may
-	not be evicted
-	is referred to as "wired." Pages may be wired under
-	different
-	circumstances: for instance, all kernel memory is wired,
-	and userland
-	applications may request that ranges of memory be wired
-	using the
-	mlock(2) and mlockall(2) system calls. FreeBSD has
-	historically defined
-	a system-wide limit on the number of wired pages so as to
-	avoid
-	deadlocks that may arise when too much of a system's
-	memory cannot be
-	reclaimed to satisfy new memory allocations. This limit
-	was applied
-	only to userland wiring requests, but kernel wirings were
-	counted
-	against the limit, so a large source of kernel wirings
-	could cause
-	mlock(2) failures. This occurs frequently with a large ZFS
-	ARC, for
-	example. In FreeBSD-CURRENT this limit has been changed
-	such that only
-	userland wirings are counted against the limit; the kernel
-	contains a
-	number of mechanisms to apply back-pressure to kernel
-	memory usage, so
-	the use of a global limit on all wirings did not provide
-	much benefit.
-	This fixes a common problem on large ZFS systems, and
-	helps enable some
-	other architectural improvements to the code which manages
-	page wirings.</p>
-
-      <p>FreeBSD has historically maintained two separate reference
-	counters in
-	the structure which describes a single physical page of
-	memory. These
-	counters initially had quite different properties, but
-	have over time
-	become more and more similar. Some work to merge the two
-	counters has
-	landed in FreeBSD-CURRENT. This does not have any
-	user-visible effects,
-	but it simplifies the page management code and removes a
-	large amount of
-	code which existed solely to transform references of one
-	type to the
-	other. Such code also made use of heavily contended locks,
-	so the
-	simplification improved kernel scalability for some
-	workloads and has
-	enabled further scalability improvements.</p>
-
-      <p>UMA is the slab allocator used in FreeBSD's kernel. It is
-	the backend
-	which services virtually all dynamic memory allocations
-	performed in the
-	kernel. The first round of NUMA improvements added NUMA
-	awareness to
-	the "keg" layer of UMA, which allocates and manages slabs.
-	However, the
-	frontend of UMA, which provides several layers of caching
-	for objects,
-	did not provide domain-aware caching, so over time the
-	caches would
-	become "polluted" with objects from different memory
-	domains. However,
-	this caching layer is being modified to ensure that
-	objects from
-	different memory domains are partitioned, helping ensure
-	that consumers
-	can perform domain-local allocations and frees
-	efficiently. This will
-	enable a global "first-touch" allocation policy for
-	UMA-managed objects.</p>
-
-      <p>During boot, the FreeBSD kernel allocates a number of
-	static data
-	structures to track physical memory. These structures have
-	historically
-	lived in the lowest available range of physical memory, so
-	they many not
-	inhabit the same NUMA domain as the memory that they
-	track. This is
-	suboptimal when one tries to affinitize a workload to a
-	particular NUMA
-	domain: if while executing the workload the kernel
-	frequently accesses
-	page structures for local memory, and the page structures
-	themselves
-	are not placed in local memory, the kernel will perform
-	many remote
-	memory accesses. Some in-progress work for the amd64
-	platform creates
-	multiple arrays of page tracking structures, one per NUMA
-	domain, and
-	ensures that each array is local to its domain. This
-	complicates the
-	task of initializing kernel data structures during boot,
-	but can
-	substantially reduce the amount of cross-domain
-	communication that
-	occurs while the kernel is performing useful work.
-	Similarly, some
-	patches to affinitize per-CPU structures are being
-	developed; while
-	most per-CPU memory allocations already return CPU-local
-	memory, some
-	structures allocated during boot are not yet properly
-	placed with
-	respect to the accessing CPU's memory domain.</p>
-
-    <p>This project was sponsored by Netflix.</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="Broadcom-ARM64-SoC-support" href="#Broadcom-ARM64-SoC-support" id="Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></h2><p>
-	Contact: Michal Stanek &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact: Kornel Duleba &lt;<a href="mailto:mindal@semihalf.com">mindal@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p>
-      <p>The Semihalf team continued working on FreeBSD support for
-	the
-	<a href="https://www.broadcom.com/products/embedded-and-networking-processors/communications/bcm58712/" shape="rect">Broadcom
-	BCM5871X SoC series</a></p>
-
-      <p>BCM5871X are quad-core 64-bit ARMv8 Cortex-A57
-	communication
-	processors targeted for networking applications such as
-	10G routers,
-	gateways, control plane processing and NAS.</p>
-
-      <p>Completed since the last update:</p>
-
-      <ul>
-	<li>iProc PCIe root complex (internal and external buses):
-	fixes and improvements,
-	including adding a BCM58712 quirk to GICv2m driver</li>
-
-	<li>BNXT Ethernet support: sys/dev/bnxt.c driver has been
-	extended to support
-	the BCM58700 variant, and the iflib was made to work
-	without IO cache coherency</li>
-      </ul>
-
-      <p>
-	In progress:</p>
-
-      <ul>
-	<li>Crypto engine acceleration for IPsec offloading.</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Upstreaming of work. This work is expected to be
-	submitted/merged
-	to HEAD in the second half of 2019.</li>
-      </ul>
-
-    <p>This project was sponsored by Juniper Networks, Inc.</p><hr /><h2><a name="NXP-ARM64-SoC-support" href="#NXP-ARM64-SoC-support" id="NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></h2><p>
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	</p>
-      <p>The Semihalf team initiated working on FreeBSD support for
-	the
-	<a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A" shape="rect">NXP
-	LS1046A SoC</a></p>
-
-      <p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors
-	with
-	integrated packet processing acceleration and high speed
-	peripherals
-	including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0
-	for a wide
-	range of networking, storage, security and industrial
-	applications.</p>
-
-      <p>Already completed:</p>
-
-      <ul>
-	<li>Platform base support (ramp-up multi-user SMP operation
-	with UART)</li>
-
-	<li>SATA 3.0</li>
-      </ul>
-
-      <p>
-	In progress:</p>
-
-      <ul>
-	<li>USB3.0</li>
-
-	<li>SD/MMC</li>
-
-	<li>I2C</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Ethernet support</li>
-
-	<li>GPIO</li>
-
-	<li>QSPI</li>
-
-	<li>Upstreaming of developed features. This work is expected
-	to
-	be submitted/merged to HEAD in the Q4 of 2019.</li>
-      </ul>
-
-    <p>This project was sponsored by Alstom Group.</p><hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="Aberdeen-Hackathon" href="#Aberdeen-Hackathon" id="Aberdeen-Hackathon">Aberdeen Hackathon</a></h2>
-      <p>At BSDCam in Cambridge last year we had a discussion to
-	create a template
-	Hackathon in the same way we have a template for
-	Devsummits. To test out the
-	idea I was convinced (I swear tricked is the correct word)
-	to host a Hackathon
-	in Aberdeen.</p>
-
-      <p>As a project I think we benefit a lot from hackathons, but
-	they do take a
-	little organisation. The worst part of this is dealing
-	with getting money from
-	attendees so you can pay for events. I spoke with Deb
-	Goodkin from the
-	foundation at BSDCam and we arranged to use their new
-	EventBrite based system
-	to handle ticketing.</p>
-
-      <p>Overall this system made it straight forward for attendees
-	to register and get
-	me their details and requirements. After the event the
-	expenses were then
-	recouped from the foundation. This was much easier than me
-	putting together a
-	custom system or even setting up and using EventBrite
-	myself.</p>
-
-      <p>The hackathon went well, you can read in Benedict and
-	Kristof's reports that
-	follow, but it was less well attended than I originally
-	expected.</p>
-
-      <p>For hackers planning future hackathons remember to take
-	heed of common national
-	holidays (we could have planned the event to not land at
-	Easter) and expect
-	major geopolitical events to make things unpredictable (we
-	knew Brexit would do
-	something, but not when).</p>
-
-      <p>I need to thank the University of Aberdeen for providing
-	the location for the
-	Hackathon and to encourage you to run a hackathon where
-	you are. The next one
-	should be in your home town.</p>
-
-      <p>Benedict Reuschling</p>
-
-      <p>The hackathon in Aberdeen was happening in the week of
-	Easter at the University
-	of Aberdeen. Although only Kristof Provost (kp@) and
-	myself joined our host Tom
-	Jones, I still consider it a productive week for us. The
-	overall theme of the
-	hackathon was networking and each of us provided something
-	towards that goal
-	(be it PRs, submitting unfinished work, or other bits and
-	pieces). We got
-	together the night of Tuesday, April 16 over dinner and
-	talked about what our
-	plans were for the week.</p>
-
-      <p>Kristof and I had talked at AsiaBSDcon when I took his
-	tutorial about Testing
-	in FreeBSD that we should add a chapter about it in the
-	developers handbook. We
-	also used our first meeting to synchronize each other
-	about the latest news in
-	FreeBSD from our developers viewpoint.</p>
-
-      <p>The next day, we met up at the Frazer Noble building where
-	the hackathon was
-	taking place. It was one of the newer buildings on campus,
-	nicely integrated
-	into the older houses of the city. Since we were only a
-	handful, we sat in
-	Tom's office for the hackathon, which had plenty of room.
-	He also showed us the
-	room where we are supposed to be having the hackathon if
-	we were more people
-	and Tom gave us a little tour. Working in a university
-	myself, I'm always
-	interested in how other education organizations are
-	structured and the rooms
-	and equipment they provide for learning. Overall, my
-	impression was that there
-	is a good amount of space and equipment available, which
-	we could have used in
-	the hackathon.</p>
-
-      <p>After returning, we decided to use a special tag in the
-	commits we would be
-	doing to identify them as coming from this hackathon. We
-	chose "Event:" for it
-	as it is a general enough term to be used at other events
-	like conferences,
-	too. The "Sponsored by:" line we used in the past is more
-	for companies or
-	individuals sponsoring certain features, so I created a
-	review to add this line
-	to the committers guide.</p>
-
-      <p>Kristof had a couple of changes to the pf chapter in the
-	FreeBSD handbook for
-	me, so I started going through those. I created a review
-	for him and the commit
-	was made there and then, making use of the short feedback
-	cycle. Originally, we
-	thought about bringing in people via hangouts, but then
-	resolved to contact
-	people via our usual IRC channel if we needed their input.</p>
-
-      <p>Kristof and Tom worked on some network specific stuff,
-	whereas I started work
-	on creating an initial draft for the testing chapter. We
-	would occasionally
-	start talking about something and then return to our work
-	in silence. If we
-	needed to coordinate or had questions, we simply asked and
-	could continue once
-	we got our answer. This provided a nice atmosphere to work
-	in. I tackled some
-	doc PRs while Kristof found a bug in pf and fixed it.</p>
-
-      <p>The afternoons were spent at different locations within
-	walking distance. Tom
-	made sure we got a good impression on how it is to be a
-	student and that there
-	is both taste and variety of food available. In the
-	evenings, Tom drove us into
-	town to have dinner at various restaurants over the week.</p>
-
-      <p>Aberdeen has a lot to offer as a city. Starting from the
-	second day, Kristof
-	and I would meet up at my hotel, which was close to the
-	Aberdeen beach and walk
-	along it to the University. According to Tom, it is
-	possible to see Dolphins
-	when the weather is right and the gulf stream provides the
-	city with enough
-	warmth that the winters aren't as bad as you'd think this
-	far up north.</p>
-
-      <p>Tom also gave us a tour of the zoological department of
-	the university, which
-	offered a beautiful garden with various plants and trees,
-	as well as a museum
-	with zoological specimen. This offered a great spot for
-	photographs and to
-	unwind a bit from the technical discussions we've had. Tom
-	also had t-shirts
-	made for the event, which are already rare collectors
-	items.</p>
-
-      <p>I had to return on Sunday, so Tom took us on a tour of the
-	Scottish highlands
-	in his car the day before. We stopped at a couple of
-	places to take pictures
-	and Tom would explain at lot to us having lived there all
-	his life. We came to
-	Stonehaven and had fish and chips there from a take-out
-	restaurant that had a
-	lot of awards for sustainable fishing. This was certainly
-	a highlight for the
-	week and even then, we couldn't stop talking about FreeBSD
-	and networking.</p>
-
-      <p>Although more people would maybe have produced more
-	output, the three of us
-	were certainly productive as a small group. It also made
-	planning and
-	coordination easier and more flexible. Tom Jones had done
-	a lot of preparation
-	and was an excellent guide. I would encourage him to host
-	another such
-	hackathon in the future and hope that next time, more
-	people will take a trip
-	to Aberdeen to spend some time hacking on FreeBSD</p>
-
-      <p>Kristof Provost</p>
-
-      <p>While I&#8217;d been to Scotland before I&#8217;d never seen Aberdeen.
-	It&#8217;s a charming
-	city, and I enthusiastically recommend visiting.</p>
-
-      <p>I arrived a little while after Benedict, but made it to my
-	hotel easily, and
-	turned up in time to join Benedict and Tom for dinner.</p>
-
-      <p>Despite being small (or perhaps because of it), the
-	hackathon was remarkably
-	productive. Benedict and I went through the pf
-	documentation in the handbook,
-	so that Benedict could rework and improve it. (Benedict&#8217;s
-	doing the work, but
-	I&#8217;m going to take credit anyway.)</p>
-
-      <p>Tom and I looked at the GSoC proposals and tried to find
-	potential mentors for
-	two promising proposals. Both of us are candidate mentors
-	as well. We should
-	know soon if our students are awarded slots.</p>
-
-      <p>Tom also proposed a patch to eliminate RFC 2675 IPv6
-	Jumbograms. It has my
-	enthusiastic support.</p>
-
-      <p>I managed to look at a couple of open pf issues:</p>
-
-      <ul>
-	<li>pfctl&#8217;s interface_group() function checks if a name is an
-	interface or an interface group. It still thought
-	that interface names always ended with a number,
-	but this assumption has been wrong for several
-	years now. That&#8217;s fixed in <a href="https://svnweb.freebsd.org/changeset/base/346370" shape="rect">r346370</a>.</li>
-
-	<li>The DIOCRSETTFLAGS ioctl() misused copyin() (It held a
-	lock calling it), which could result in panics.</li>
-
-	<li>That previous issue was actually discovered by my local
-	instance of syzcaller, which I&#8217;d set up to add pf
-	support to it. That support has now been merged,
-	so we may see more issues detected by syzcaller
-	soon.</li>
-
-	<li>Also for the DIOCRSETTFLAGS problem I extended the pf
-	tests to check for this issue.</li>
-
-	<li>The pf tests will now fail if the pft_set_rules call fails
-	to set the rules. That didn&#8217;t actually cause
-	issues yet, but it&#8217;ll make debugging tests
-	slightly easier, and they may catch more problems
-	now.</li>
-      </ul>
-
-      <p>
-	On Saturday Tom took us out to discover some of the pretty
-	bits of Scotland. It
-	turns out there are a lot of them. I can&#8217;t really do it
-	justice, but Tom has a
-	promising career at the Scottish tourism board when this
-	computers fad blows
-	over.</p>
-
-      <p>On my way home I passed through Oslo, and took the
-	opportunity to meet with
-	(have lunch with) two of the EuroBSDCon local organisers.
-	EuroBSDCon is filling
-	up fast, make sure to register now to secure your place!</p>
-
-    <hr /><h2><a name="Bring-more-Security-Intelligence-to-FreeBSD" href="#Bring-more-Security-Intelligence-to-FreeBSD" id="Bring-more-Security-Intelligence-to-FreeBSD">Bring more Security Intelligence to FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/stamparm/maltrail" title="https://github.com/stamparm/maltrail">Maltrail - distributed Malware detection</a></td><td>
-	    URL: <a href="https://github.com/stamparm/maltrail" title="Maltrail - distributed Malware detection">https://github.com/stamparm/maltrail</a></td></tr><tr><td><a href="https://wazuh.com/" title="https://wazuh.com/">Wazuh - thread detection and incident response</a></td><td>
-	    URL: <a href="https://wazuh.com/" title="Wazuh - thread detection and incident response">https://wazuh.com/</a></td></tr></table><p>
-	Contact: Michael Muenz &lt;<a href="mailto:m.muenz@gmail.com">m.muenz@gmail.com</a>&gt;
-	</p>
-      <p>To bring more Security Intelligence we maintain the
-	FreeBSD port
-	of <tt>zmaltail</tt>. This open source project based on
-	Python can act
-	as a sensor and/or as a central server. It listens in
-	defined ports
-	or protocols and compares IP addresses and domains against
-	static
-	and dynamic feeds, contributed by the community.</p>
-
-      <p>As you can install this piece of software on multiple
-	firewalls
-	and let them send to a central server, you are able to
-	detect attacks
-	and compromises very fast. Within Q2 we updated the port
-	to the latest
-	version and are constantly in contact with the core
-	developer
-	(also co-author of <tt>SQLmap</tt>) to bring out new
-	features.</p>
-
-      <p>The second project we are currently trying to add as a
-	port is <tt>Wazuh</tt>.
-	Wazuh is a fork of <tt>Ossec</tt> which is already in the
-	ports tree.
-	Compared to Ossec, Wazuh has some intelligent addition
-	like full
-	<tt>ELK-Stack</tt> integration with own apps and
-	dashboards.</p>
-
-      <p>With Wazuh installed on your webserver, or even on your
-	windows desktop
-	you can monitor file integrity or log files for most kind
-	of attacks.
-	Active response features let you e.g. send API calls to
-	your firewalls
-	to dynamically block this offender.</p>
-
-      <p>As Wazuh offers a complete ELK-Stack you can use it also
-	as a central
-	logging solution for better security insights into your
-	network.</p>
-
-    <p>This project was sponsored by m.a.x. Informationstechnologie AG.</p><hr /><h2><a name="libvdsk---QCOW2-implementation" href="#libvdsk---QCOW2-implementation" id="libvdsk---QCOW2-implementation">libvdsk - QCOW2 implementation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/xcllnt/libvdsk" title="https://github.com/xcllnt/libvdsk">Github - libvdsk repo</a></td><td>
-	    URL: <a href="https://github.com/xcllnt/libvdsk" title="Github - libvdsk repo">https://github.com/xcllnt/libvdsk</a></td></tr></table><p>
-	Contact: Sergiu Weisz &lt;<a href="mailto:sergiu121@gmail.com">sergiu121@gmail.com</a>&gt;
-	<br />
-	Contact: Marcel Molenaar &lt;<a href="mailto:marcel@freebsd.org">marcel@freebsd.org</a>&gt;
-	<br />
-	Contact: Marcelo Araujo &lt;<a href="mailto:araujo@freebsd.org">araujo@freebsd.org</a>&gt;
-	<br />
-	Contact: Mihai Carabas &lt;<a href="mailto:mihai@freebsd.org">mihai@freebsd.org</a>&gt;
-	</p>
-      <p>Add support for using QCOW in bhyve using the libvdsk
-	library. Libvdsk was used
-	to substitute the regular disk operations from bhyve with
-	a call to libvdsk
-	which will in turn call the disk-specific handler for the
-	operation.</p>
-
-      <p>To use this feature one has to install the libvdsk-enabled
-	bhyve version along
-	with libvdsk from the libvdsk repo linked above.</p>
-
-      <p>New features added:</p>
-
-      <ul>
-	<li>Extend libvdsk to make it easier to implement new formats</li>
-
-	<li>Improve read/write performance and stability</li>
-
-	<li>Add support for Copy-On-Write</li>
-      </ul>
-
-      <p>
-	Future tasks:</p>
-
-      <ul>
-	<li>Integrate libvdsk in bhyve</li>
-      </ul>
-
-    <sponsor>
-      Matthew Grooms
-    </sponsor>
-
-    <hr /><h2><a name="nsysctl-1.0" href="#nsysctl-1.0" id="nsysctl-1.0">nsysctl 1.0</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/alfix/nsysctl" title="https://gitlab.com/alfix/nsysctl">gitlab.com/alfix/nsysctl</a></td><td>
-	    URL: <a href="https://gitlab.com/alfix/nsysctl" title="gitlab.com/alfix/nsysctl">https://gitlab.com/alfix/nsysctl</a></td></tr><tr><td><a href="https://www.freshports.org/sysutils/nsysctl/" title="https://www.freshports.org/sysutils/nsysctl/">sysutils/nsysctl port</a></td><td>
-	    URL: <a href="https://www.freshports.org/sysutils/nsysctl/" title="sysutils/nsysctl port">https://www.freshports.org/sysutils/nsysctl/</a></td></tr><tr><td><a href="https://alfix.gitlab.io/bsd/2019/02/19/nsysctl-tutorial.html" title="https://alfix.gitlab.io/bsd/2019/02/19/nsysctl-tutorial.html">Tutorial</a></td><td>
-	    URL: <a href="https://alfix.gitlab.io/bsd/2019/02/19/nsysctl-tutorial.html" title="Tutorial">https://alfix.gitlab.io/bsd/2019/02/19/nsysctl-tutorial.html</a></td></tr></table><p>
-	Contact: Alfonso Sabato Siciliano &lt;<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>&gt;
-	</p>
-      <p>The <tt>nsysctl</tt> utility is a <tt>/sbin/sysctl</tt>
-	clone, to get or set the kernel
-	state, supporting <tt>libxo</tt> and extra options.</p>
-
-      <p><programlisting>
-	  nsysctl [--libxo=opts [-r tagname]]<br clear="none" />
-	  [-DdFGgIilmNpqTt[V|v[h[b|o|x]]]Wy]<br clear="none" />
-	  [-e sep] [-B &lt;bufsize&gt;] [-f filename]<br clear="none" />
-	  name[=value[,value]] ...<br clear="none" />
-	  nsysctl [--libxo=opts [-r tagname]]<br clear="none" />
-	  [-DdFGgIlmNpqTt[V|v[h[b|o|x]]]Wy]<br clear="none" />
-	  [-e sep] [-B &lt;bufsize&gt;] -A|a|X<br clear="none" />
-</programlisting></p>
-
-      <p>You could use <tt>nsysctl</tt> to explore the sysctl MIB
-	showing the value and the
-	info of an object. The output is explicitly indicated by
-	the options and is
-	printed via <tt>libxo</tt> in human and machine readable
-	formats, moreover some value
-	is parsed to display it in a structured mode (e.g.,
-	<tt>vm.phys_free</tt>).
-	The support for <tt>efi_map_header</tt> was added but it
-	is untested, someone could
-	help by trying it via <tt>machdep.efi_map</tt>.</p>
-
-      <p>Please refer to the tutorial for a more thorough
-	description.</p>
-
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2019-07-2019-09.html b/website/content/en/status/report-2019-07-2019-09.html
deleted file mode 100644
index 6bb07e2d42..0000000000
--- a/website/content/en/status/report-2019-07-2019-09.html
+++ /dev/null
@@ -1,2683 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Here is the third quarterly status report for 2019.</p><p>This quarter the reports team has been more active than usual thanks
-to a better organization: calls for reports and reminders have been
-sent regularly, reports have been reviewed and merged quickly (I would
-like to thank debdrup@ in particular for his reviewing work).</p><p>Efficiency could still be improved with the help of our community.
-In particular, the quarterly team has found that many reports have
-arrived in the last days before the deadline or even after. I would
-like to invite the community to follow the guidelines below that
-can help us sending out the reports sooner.</p><p><ul>
-<li>Send a first draft of your report when you receive the first call
-for reports (1 month before the deadline).</li>
-<li>Update your report, if needed, when you receive reminders: you will
-normaly receive two (2 weeks and 1 week before the deadline).</li>
-<li>If after the deadline you still have some more updates ask the team
-(either on IRC via #freebsd-wiki or send an email at monthly@) to
-wait for you if you feel that they are urgent, otherwise start
-putting them in a draft for the next quarter.</li></ul></p><p>Starting from next quarter, all quarterly status reports will be
-prepared the last month of the quarter itself, instead of the first
-month after the quarter's end. This means that deadlines for
-submitting reports will be the 1st of January, April, July and
-October.</p><p>Next quarter will then be a short one, covering the months of November
-and December only and the report will probably be out in mid January.</p><p>-- Lorenzo Salvadore</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#Cluster-Administration-Team">Cluster Administration Team</a></li><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#FreeBSD-Security-Team">FreeBSD Security Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FAT-/-msdosfs-support-for-makefs(8)">FAT / msdosfs support for makefs(8)</a></li><li><a href="#FUSE">FUSE</a></li><li><a href="#Google-Summer-of-Code-2019">Google Summer of Code 2019</a></li><li><a href="#GSoC'19-Project---MAC-policy-on-IP-addresses-in-Jail:-mac_ipacl">GSoC'19 Project - MAC policy on IP addresses in Jail: mac_ipacl</a></li><li><a href="#Improving-laptop-support">Improving laptop support</a></li><li><a href="#NFS-Version-4.2-implementation">NFS Version 4.2 implementation</a></li><li><a href="#Rockchip-RK3399-SoC's-eMMC-support">Rockchip RK3399 SoC's eMMC support</a></li><li><a href="#syzkaller-on-FreeBSD">syzkaller on FreeBSD</a></li><li><a href="#TPM2-Software-Stack-(TSS2)">TPM2 Software Stack (TSS2)</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Casueword(9)-livelock">Casueword(9) livelock</a></li><li><a href="#Kernel-Mapping-Protections">Kernel Mapping Protections</a></li><li><a href="#Kernel-ZLIB-Update">Kernel ZLIB Update</a></li><li><a href="#PROT_MAX-mmap/mprotect-maximum-protections-API">PROT_MAX mmap/mprotect maximum protections API</a></li><li><a href="#Randomized-Top-of-Stack-pointer">Randomized Top of Stack pointer</a></li><li><a href="#Signals-delivered-on-unhandled-Page-Faults">Signals delivered on unhandled Page Faults</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></li><li><a href="#FreeBSD-support-for-the-forthcoming-Arm-Morello-CPU,-SoC,-and-board">FreeBSD support for the forthcoming Arm Morello CPU, SoC, and board</a></li><li><a href="#FreeBSD/powerpc-Project">FreeBSD/powerpc Project</a></li><li><a href="#NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#gets(3)-retirement">gets(3) retirement</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#Java-on-FreeBSD">Java on FreeBSD</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#XFCE-4.14-update">XFCE 4.14 update</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System">ClonOS: virtualization platform on top of FreeBSD Operating System</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#Nomad-pot-driver---Orchestrating-jails-via-nomad">Nomad pot driver - Orchestrating jails via nomad</a></li><li><a href="#sysctlinfo">sysctlinfo</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-        Page</a>.</p><br /><h2><a name="Cluster-Administration-Team" href="#Cluster-Administration-Team" id="Cluster-Administration-Team">Cluster Administration Team</a></h2><p>
-	Contact: Cluster Administration Team &lt;<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Cluster Administration Team consists of the
-	people responsible for administering the machines
-	that the Project relies on for its distributed
-	work and communications to be synchronised. In
-	this quarter, the team has worked on the
-	following:</p>
-
-      <ul>
-	<li>Change IPv6 address in TWN site.</li>
-
-	<li>Solved hardware issues in KWC site (with hrs@).</li>
-
-	<li>Moved remaining infrastructure from the YSV (Yahoo!) site
-	to NYI (New York Internet) (peter@).</li>
-
-	<ul><li>YSV hosted most of FreeBSD.org between 2000 and 2019.</li></ul>
-
-	<li>Installed new machines for portmgr@ courtesy of the
-	FreeBSD Foundation.</li>
-
-	<li>Resolved outtages (thanks uqs@) with GitHub exporter,
-	Bugzilla and hg-beta (thanks bapt@).</li>
-
-	<li>PowerPC64 servers are online (power8) building pkgs and
-	reference hosts.</li>
-
-	<li>Ongoing systems administration work:</li>
-
-	<ul><li>Creating accounts for new committers.</li>
-
-	<li>Backups of critical infrastructure.</li>
-
-	<li>Keeping up with security updates in 3rd party software.</li></ul>
-      </ul>
-
-      <p>
-	Work in progress:</p>
-
-      <ul>
-	<li>Review the service jails and service administrators
-	operation.</li>
-
-	<li>South Africa Mirror (JINX) in progress.</li>
-
-	<li>NVME issues on PowerPC64 Power9 blocking dual socket
-	machine from being used as pkg builder.</li>
-
-	<li>Drive upgrade test for pkg builders (SSDs) courtesy of the
-	FreeBSD Foundation.</li>
-
-	<li>Boot issues with Aarch64 reference machines.</li>
-
-	<li>New NYI.net sponsored colocation space in Chicago-land
-	area.</li>
-
-	<li>Setup new host for CI staging environment.</li>
-      </ul>
-
-    <hr /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org/" title="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org/" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org/</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="FreeBSD CI Repository">https://github.com/freebsd/freebsd-ci</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://hackmd.io/@FreeBSD-CI" title="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackmd.io/@FreeBSD-CI" title="FreeBSD CI weekly report">https://hackmd.io/@FreeBSD-CI</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD CI team maintains continuous integration
-	system and related tasks
-	for the FreeBSD project. The CI system regularly checks
-	the committed changes
-	can be successfully built, then performs various tests and
-	analysis of the
-	results. The results from build jobs are archived in an
-	artifact server, for
-	the further testing and debugging needs. The CI team
-	members examine the
-	failing builds and unstable tests, and work with the
-	experts in that area to
-	fix the code or adjust test infrastructure. The details
-	are of these efforts
-	are available in the weekly CI reports.</p>
-
-      <p>We had a testing working group at the <a href="https://wiki.freebsd.org/DevSummit/201909" shape="rect">201909
-	DevSummit</a>
-	lwhsu@ has presented the Testing/CI project status and
-	"how to work with the FreeBSD CI system", slides
-	are available at the DevSummit page.
-	Some contents have been migrated to
-	https://wiki.freebsd.org/Jenkins/Debug , extending
-	is welcomed.</p>
-
-      <p>We continue publishing CI Weekly Report and moved the
-	archive to https://hackmd.io/@FreeBSD-CI</p>
-
-      <p>Work in progress:</p>
-
-      <ul>
-	<li>Collecting and sorting CI tasks and ideas at
-	https://hackmd.io/bWCGgdDFTTK_FG0X7J1Vmg</li>
-
-	<li>Setup the CI stage environment and put the experimental
-	jobs on it</li>
-
-	<li>Extending and publishing the embedded boards testbed</li>
-
-	<li>Implementing automatic tests on bare metal hardware</li>
-
-	<li>Adding drm ports building test against -CURRENT</li>
-
-	<li>Testing and merging pull requests at
-	https://github.com/freebsd/freebsd-ci/pulls</li>
-
-	<li>Planning for running ztest and network stack tests</li>
-
-	<li>Help more 3rd software get CI on FreeBSD through a hosted
-	CI solution</li>
-      </ul>
-
-      <p>
-	Please see freebsd-testing@ related tickets for more WIP
-	information.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Core Team is the governing body of FreeBSD.</p>
-
-      <ul>
-	<li>Core has provisionally accepted the BSD+patent license for
-	use in some cases.
-	The Core Team must approve the import of new BSD+Patent
-	licensed components or
-	the change of license of existing components to the
-	BSD+Patent License.
-      <br clear="none" />
-	https://opensource.org/licenses/BSDplusPatent</li>
-
-	<li>Kernel Pseudo Random Number Generator (PRNG)
-	maintainership was updated to
-	reduce the contribution barrier for committers who have
-	demonstrated
-	competence in this part of the tree.</li>
-	<li>Core approved a source commit bit for Pawe&#322; Biernacki.
-	Konstantin Belousov
-	&lt;kib@&gt; will mentor Pawe&#322; and Mateusz Guzik
-	&lt;mjg@&gt; will be co-mentor.</li>
-	<li>The Core-initiated Git Transition Working Group met over
-	the last quarter,
-	however a report is still forthcoming. Discussions will
-	continue in the
-	fourth quarter of 2019. There are many issues to resolve
-	including how to
-	deal with contrib/, whether to re-generate hashes in the
-	current Git
-	repository, and how to best implement commit testing.</li>
-      </ul>
-
-    <hr /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to
-	supporting and promoting the FreeBSD Project and community
-	worldwide.
-	Funding comes from individual and corporate donations and
-	is used to fund
-	and manage software development projects, conferences and
-	developer summits,
-	and provide travel grants to FreeBSD contributors. The
-	Foundation purchases
-	and supports hardware to improve and maintain FreeBSD
-	infrastructure and
-	provides resources to improve security and quality
-	assurance efforts;
-	publishes marketing material to promote, educate, and
-	advocate for the
-	FreeBSD Project; facilitates collaboration between
-	commercial vendors and
-	FreeBSD developers; and finally, represents the FreeBSD
-	Project in executing
-	contracts, license agreements, and other legal
-	arrangements that require a
-	recognized legal entity.</p>
-
-      <p>Here are some highlights of what we did to help FreeBSD
-	last quarter:</p>
-
-      <p>Partnerships and Commercial User Support
-	We help facilitate collaboration between commercial users
-	and FreeBSD
-	developers. We also meet with companies to discuss their
-	needs and bring
-	that information back to the Project. In Q3, Ed Maste and
-	Deb Goodkin met
-	with a few commercial users in the US. It is not only
-	beneficial for the
-	above, but it also helps us understand some of the
-	applications where
-	FreeBSD is used. We were also able to meet with a good
-	number of commercial
-	users at vBSDCon and EuroBSDCon. These venues provide an
-	excellent
-	opportunity to meet with commercial and individual users
-	and contributors
-	to FreeBSD.</p>
-
-      <p>Fundraising Efforts
-	Our work is 100% funded by your donations. We are
-	continuing to work hard
-	to get more commercial users to give back to help us
-	continue our work
-	supporting FreeBSD. More importantly, we'd like to thank
-	our individual
-	donors for making $10-$1,000 donations last quarter, for
-	more than $16,000!</p>
-
-      <p>Please consider
-	<a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">making
-	a donation</a> to help us
-	continue and increase our support for FreeBSD!</p>
-
-      <p>We also have the Partnership Program, to provide more
-	benefits for our
-	larger commercial donors. Find out more information at
-	<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>
-	and share with your companies.</p>
-
-      <p>OS Improvements</p>
-      <p>The Foundation supports software development projects to
-	improve the FreeBSD
-	operating system through our full time technical staff,
-	contractors, and
-	project grant recipients. They maintain and improve
-	critical kernel
-	subsystems, add new features and functionality, and fix
-	problems.</p>
-
-      <p>Over the last quarter there were 345 commits to the
-	FreeBSD base system
-	repository sponsored by the FreeBSD Foundation - this
-	represents about
-	one fifth of all commits during this period. Many of these
-	projects have
-	their own entries in this quarterly report (and are not
-	repeated here).</p>
-
-      <p>Foundation staff member Konstantin Belousov committed many
-	improvements to
-	multiple kernel subsystems, as well as low-level 32-bit
-	and 64-bit x86
-	infrastructure. These included fixes for robust mutexes,
-	unionfs, the
-	out of memory (OOM) handler, and per-cpu allocators.</p>
-
-      <p>Additional work included fixes for security issues and
-	introduction and
-	maintenance of vulnerability mitigations, and improving
-	POSIX conformance.</p>
-
-      <p>Ed Maste committed a number of minor security bug fixes
-	and improvements,
-	as well as the first iteration of a tool for editing the
-	mitigation control
-	ELF note. Additional work included effort on build
-	infrastructure and the
-	tool chain.</p>
-
-      <p>Clang's integrated assembler (IAS) is now used more
-	widely, as part of the
-	path to retiring the assembler from GNU binutils 2.17.50.
-	The readelf tool
-	now decodes some additional ELF note information.</p>
-
-      <p>Ed also enabled the Linuxulator (Linux binary support
-	layer) on arm64, and
-	added a trivial implementation of the renameat2 system
-	call (handling common
-	options).</p>
-
-      <p>Mark Johnston added Capsicum support to a number of ELF
-	Tool Chain utilities,
-	and committed a number of other Capsicum kernel and
-	userland fixes.</p>
-
-      <p>Mark worked on a number of changes related to security
-	improvements, including
-	integration and support of the Syzkaller automated system
-	call fuzzer, and
-	fixing issues identified by Syzkaller. Other changes
-	included addressing
-	failures caused by refcount wraparound, improvements to
-	the <tt>prot_max</tt> memory
-	protection. Other work included NUMA, locking, kernel
-	debugging, RISC-V and
-	arm64 kernel improvements.</p>
-
-      <p>Edward Napierala continued working on Linuxulator
-	improvements over the
-	quarter. The primary focus continued to be tool
-	improvements - strace is now
-	more usable for diagnosing issues with Linux binaries
-	running under the
-	Linuxulator. That said, as with previous work a number of
-	issues have been
-	fixed along the way. These are generally minor issues with
-	a large impact -
-	for example, every binary linked against up-to-date glibc
-	previously
-	segfaulted on startup. This is now fixed.</p>
-
-      <p>Continuous Integration and Quality Assurance
-	The Foundation provides a full-time staff member who is
-	working on improving
-	our automated testing, continuous integration, and overall
-	quality assurance
-	efforts.</p>
-
-      <p>During the third quarter of 2019, Foundation staff
-	continued to improve the
-	project's CI infrastructure, worked with contributors to
-	fix the failing build
-	and test cases, and worked with other teams in the Project
-	for their testing
-	needs. We added several new CI jobs and worked on getting
-	the hardware
-	regression testing lab ready.</p>
-
-      <p>Li-Wen Hsu gave presentations "Testing/CI status update"
-	and "How to work with
-	the FreeBSD CI system" at the
-	<a href="https://wiki.freebsd.org/DevSummit/201909" shape="rect">201909
-	DevSummit</a>.
-	Slides are available at the DevSummit page.</p>
-
-      <p>We continue publishing the CI weekly report on the
-	<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing@</a>.
-	mailing list, and an <a href="https://hackmd.io/@freebsd-ci" shape="rect">archive</a>
-	is available.</p>
-
-      <p>See the FreeBSD CI section of this report for completed
-	work items and
-	detailed information.</p>
-
-      <p>Supporting FreeBSD Infrastructure
-	The Foundation provides hardware and support to improve
-	the FreeBSD
-	infrastructure. Last quarter, we continued supporting
-	FreeBSD hardware
-	located around the world.</p>
-
-      <p>FreeBSD Advocacy and Education
-	A large part of our efforts are dedicated to advocating
-	for the Project.
-	This includes promoting work being done by others with
-	FreeBSD; producing
-	advocacy literature to teach people about FreeBSD and help
-	make the path to
-	starting using FreeBSD or contributing to the Project
-	easier; and attending
-	and getting other FreeBSD contributors to volunteer to run
-	FreeBSD events,
-	staff FreeBSD tables, and give FreeBSD presentations.</p>
-
-      <p>The FreeBSD Foundation sponsors many conferences, events,
-	and summits around
-	the globe. These events can be BSD-related, open source,
-	or technology events
-	geared towards underrepresented groups. We support the
-	FreeBSD-focused events
-	to help provide a venue for sharing knowledge, to work
-	together on projects,
-	and to facilitate collaboration between developers and
-	commercial users.
-	This all helps provide a healthy ecosystem. We support the
-	non-FreeBSD events
-	to promote and raise awareness of FreeBSD, to increase the
-	use of FreeBSD in
-	different applications, and to recruit more contributors
-	to the Project.</p>
-
-      <p>Check out some of the advocacy and education work we did
-	last quarter:</p>
-
-      <ul>
-	<li>Sponsored USENIX 2019 Annual Technical Conference as an
-	Industry Partner</li>
-
-	<li>Represented FreeBSD at OSCON 2019 in Portland, OR</li>
-
-	<li>Represented FreeBSD at COSCUP 2019 in Taiwan</li>
-
-	<li>Presented at the Open Source Summit, North American in San
-	Diego, CA</li>
-
-	<li>Executive Director Deb Goodkin was interviewed by TFiR
-	https://www.freebsdfoundation.org/news-and-events/latest-news/tfir-interview-freebsd-meets-linux-at-the-open-source-summit/</li>
-
-	<li>Sponsored FreeBSD Hackathon at vBSDcon 2019 in Reston, VA</li>
-
-	<li>Sponsored the attendee bags and attended vBSDcon 2019 in
-	Reston VA</li>
-
-	<li>Represented FreeBSD at APNIC-48 in Chiang Mai, Thailand</li>
-
-	<li>Represented FreeBSD at MNNOG-1 in Ulaanbaatar, Mongolia</li>
-
-	<li>Served as an administrator for the Project&#8217;s Google Summer
-	of Code Session. See the Google Summer of Code
-	section of this report for more information.</li>
-
-	<li>Sponsored FreeBSD Developers Summit at EuroBSDCon in
-	Lillehammer, Norway</li>
-
-	<li>Sponsored and attended EuroBSDcon 2019 in Lillehammer,
-	Norway</li>
-
-	<li>Applied and was accepted for a FreeBSD Miniconf at
-	linux.conf.au, in Gold Coast, Australia, Jan 14,
-	2020</li>
-
-	<li>Our FreeBSD talk was accepted at seaGL, Seattle, WA,
-	November 15 and 16.</li>
-      </ul>
-
-      <p>
-	We continued producing FreeBSD advocacy material to help
-	people promote
-	FreeBSD. Learn more about our recent efforts to advocate
-	for FreeBSD
-	around the world:
-	https://www.freebsdfoundation.org/blog/freebsd-around-the-world/</p>
-
-      <p>Our Faces of FreeBSD series is back. Check out the latest
-	post:
-	<a href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2019-roller-angel/" shape="rect">Roller
-	Angel</a>.</p>
-
-      <p>Read more about our conference adventures in the
-	conference recaps and trip
-	reports in our monthly newsletters:
-
-	https://www.freebsdfoundation.org/news-and-events/newsletter/</p>
-
-      <p>We help educate the world about FreeBSD by publishing the
-	professionally
-	produced FreeBSD Journal. As we mentioned previously, the
-	FreeBSD Journal
-	is now a free publication. Find out more and access the
-	latest issues at
-	https://www.FreeBSDfoundation.org/journal/.</p>
-
-      <p>You can find out more about
-	<a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">events
-	we attended and upcoming events</a>.</p>
-
-      <p>We opened our official FreeBSD Swag Store. Get stickers,
-	shirts, mugs and
-	more at <a href="https://www.zazzle.com/store/shopfreebsd" shape="rect">ShopFreeBSD</a>.</p>
-
-      <p>We have continued our work with a new website developer to
-	help us improve
-	our website. Work has begun to make it easier for
-	community members to find
-	information and to make the site more efficient.</p>
-
-      <p>Legal/FreeBSD IP
-	The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to
-	protect them. We also provide legal support for the core
-	team to investigate
-	questions that arise.</p>
-
-      <p>Go to http://www.FreeBSDfoundation.org to find out how we
-	support FreeBSD and
-	how we can help you!</p>
-
-    <hr /><h2><a name="FreeBSD-Graphics-Team-status-report" href="#FreeBSD-Graphics-Team-status-report" id="FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop" title="https://github.com/FreeBSDDesktop">Project GitHub page</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop" title="Project GitHub page">https://github.com/FreeBSDDesktop</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:x11@freebsd.org">x11@freebsd.org</a>&gt;
-	<br />
-	Contact: Niclas Zeising &lt;<a href="mailto:zeising@freebsd.org">zeising@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD X11/Graphics team maintains the lower levels
-	of the FreeBSD graphics
-	stack.
-	This includes graphics drivers, graphics libraries such as
-	the
-	MESA OpenGL implementation, the X.org xserver with related
-	libraries and
-	applications, and Wayland with related libraries and
-	applications.</p>
-
-      <p>During the last period, several changes have been made,
-	but most of them has
-	been behind the scene.
-	We have also worked on general clean up of old xorg ports
-	that have been
-	deprecated upstream.</p>
-
-      <p>The ports infrastructure for xorg ports and ports that
-	depend on xorg ports have
-	been updated.
-	We have switched <tt>USE_XORG</tt> and <tt>XORG_CAT</tt>
-	to use the <tt>USES</tt> framework, instead
-	of the old way of including <tt>bsd.xorg.mk</tt> from
-	<tt>bsd.port.mk</tt>.
-	This infrastructure work has been fairly substantial, and
-	new ports depending on
-	xorg ports should add <tt>USES=xorg</tt> to their
-	makefiles.
-	As part of this <tt>bsd.xorg.mk</tt> was split up, and the
-	<tt>XORG_CAT</tt> part was split
-	out to <tt>USES=xorg-cat</tt>.
-	This is used for the xorg ports themselves, and sets up a
-	common environment for
-	building all xorg ports.
-	In addition, framework for pulling xorg ports directly
-	from freedesktop.org
-	gitlab was added, which will make improve development and
-	testing, since it
-	makes it possible to create ports of unreleased versions.
-	Further improvements in this area includes framework for
-	using meson instead of
-	autotools for building xorg ports.
-	This is still a work in progress.</p>
-
-      <p>We have also worked to clean up and deprecate several old
-	xorg ports and
-	libraries.
-	Some of these ports have already been removed, and some
-	are still waiting on
-	removal after a sufficient deprecation period.
-	Most notably amongst the deprecations are
-	<tt>x11/libXp</tt>, which required to fix
-	several dependencies.
-	Several other old libraries have also been deprecated,
-	such as <tt>x11/Xxf86misc</tt>,
-	<tt>x11-fonts/libXfontcache</tt> and
-	<tt>graphics/libGLw</tt>.
-	Some applications and drivers have also been deprecated
-	during the period.
-	With the remaining removals in this area, we should be up
-	to speed with
-	deprecations upstream.
-	We are currently investigating if there are new software
-	added upstream that we
-	need to port to FreeBSD.</p>
-
-      <p>We have also continued our regularly scheduled bi-weekly
-	meetings.</p>
-
-      <p>People who are interested in helping out can find us on
-	the x11@FreeBSD.org
-	mailing list, or on our gitter chat: <a href="https://gitter.im/FreeBSDDesktop/Lobby" shape="rect">https://gitter.im/FreeBSDDesktop/Lobby</a>.
-	We are also available in #freebsd-xorg on EFNet.</p>
-
-      <p>We also have a team area on GitHub where our work
-	repositories can be found:
-	<a href="https://github.com/FreeBSDDesktop" shape="rect">https://github.com/FreeBSDDesktop</a></p>
-
-    <hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/11.3R/announce.html" title="https://www.freebsd.org/releases/11.3R/announce.html">FreeBSD 11.3-RELEASE announcement</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.3R/announce.html" title="FreeBSD 11.3-RELEASE announcement">https://www.freebsd.org/releases/11.3R/announce.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/12.1R/schedule.html" title="https://www.freebsd.org/releases/12.1R/schedule.html">FreeBSD 12.1-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/12.1R/schedule.html" title="FreeBSD 12.1-RELEASE schedule">https://www.freebsd.org/releases/12.1R/schedule.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/" title="https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/">FreeBSD 12.1-RELEASE BETA/RC builds</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/" title="FreeBSD 12.1-RELEASE BETA/RC builds">https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Release Engineering Team is responsible for
-	setting
-	and publishing release schedules for official project
-	releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-
-      <p>During the third quarter of 2019, the FreeBSD Release
-	Engineering team
-	finished the 11.3-RELEASE cycle, with the final release
-	build started on
-	July 5th and the official announcement sent on July 9th.</p>
-
-      <p>FreeBSD 11.3-RELEASE is the fourth release from the
-	<i>stable/11</i> branch,
-	building on the stability and reliability of 11.2-RELEASE.</p>
-
-      <p>The FreeBSD Release Engineering Team also started work on
-	the upcoming
-	12.1-RELEASE, which started September 6th. This release
-	cycle is the
-	first "freeze-less" release from the Subversion
-	repository, and the test bed
-	for eliminating the requirement of a hard code freeze on
-	development branches.
-	Commits to the <i>releng/12.1</i> branch still
-	require explicit approval from
-	the Release Engineering Team, however.</p>
-
-      <p>At present, there have been three BETA builds, and so far,
-	two RC builds, with
-	the final 12.1-RELEASE build scheduled for November 4th.</p>
-
-      <p>Additionally throughout the quarter, several development
-	snapshots builds
-	were released for the <i>head</i> and
-	<i>stable/11</i> branches; snapshots for
-	<i>stable/12</i> were released as well although
-	not during the 12.1-RELEASE cycle.</p>
-
-      <p>Much of this work was sponsored by Rubicon Communications,
-	LLC (Netgate)
-	and the FreeBSD Foundation.</p>
-
-    <hr /><h2><a name="FreeBSD-Security-Team" href="#FreeBSD-Security-Team" id="FreeBSD-Security-Team">FreeBSD Security Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/security/" title="https://www.freebsd.org/security/">FreeBSD security information</a></td><td>
-	    URL: <a href="https://www.freebsd.org/security/" title="FreeBSD security information">https://www.freebsd.org/security/</a></td></tr></table><p>
-	Contact: Security Team &lt;<a href="mailto:secteam@FreeBSD.org">secteam@FreeBSD.org</a>&gt;
-	</p>
-      <p>Several members of the security team met at the Vendor
-	Summit in October to
-	formalize team structure dedicated for architecture and
-	crypto engineering in
-	addition to the existing product security incident
-	response function.</p>
-
-      <p>Since June we have started having fortnightly conference
-	calls to discuss
-	important issues and to collaborate closely on advisories
-	and errata notices in
-	the pipeline.</p>
-
-      <ul>
-	<li>Security advisories sent out in 2019-Q3: 7</li>
-
-	<li>Errata Notices sent out in 2019-Q3: 5</li>
-      </ul>
-
-    <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="FAT-/-msdosfs-support-for-makefs(8)" href="#FAT-/-msdosfs-support-for-makefs(8)" id="FAT-/-msdosfs-support-for-makefs(8)">FAT / msdosfs support for makefs(8)</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>In order to streamline the process of creating install or
-	virtual
-	machine system images we needed FAT filesystem support in
-	makefs(8).
-	Makefs was originally developed in NetBSD, and FAT support
-	was added
-	there not much later, but after the tool was ported to
-	FreeBSD.</p>
-
-      <p>Siva Mahadevan, one of the FreeBSD Foundation's interns
-	from the
-	University of Waterloo, worked on porting FAT support from
-	NetBSD.
-	I <a href="https://reviews.freebsd.org/D16438" shape="rect">rebased and
-	updated</a> Siva's
-	work, and <a href="https://reviews.freebsd.org/rS351273" shape="rect">committed</a>
-	it during
-	this quarter. After a few follow-up fixes we are able to
-	build FAT
-	filesystem images without using md(4) and without
-	requiring root.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="FUSE" href="#FUSE" id="FUSE">FUSE</a></h2><p>
-	Contact: Alan Somers &lt;<a href="mailto:asomers@FreeBSD.org">asomers@FreeBSD.org</a>&gt;
-	</p>
-      <p>FUSE (File system in USErspace) allows a userspace program
-	to
-	implement a file system. It is widely used to support
-	out-of-tree file
-	systems like NTFS, as well as for exotic pseudo file
-	systems like
-	sshfs. FreeBSD's fuse driver was added as a GSoC project
-	in 2012.
-	Since that time, it has been largely neglected. The FUSE
-	software is
-	<a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&amp;known_name=fusefs&amp;list_id=289348&amp;query_based_on=fusefs&amp;query_format=advanced&amp;short_desc=%5Bfusefs%5D%20sysutils%2Ffusefs-&amp;short_desc_type=anywordssubstr" shape="rect">buggy</a>
-	and out-of-date. Our implementation is about 11 years
-	behind.</p>
-
-      <p>I completed this work during Q3. I fixed a few
-	newly-introduced bugs, fixed a
-	long-standing sendfile bug that affects FUSE
-
-	([236466](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236466))
-	and merged
-	everything to head and stable/12. Then I fixed the
-	resulting Coverity CIDs.
-	There have been no new FUSE-related bug reports, so I can
-	only assume that
-	everything is working great. Report any problems to
-	asomers@FreeBSD.org.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Google-Summer-of-Code-2019" href="#Google-Summer-of-Code-2019" id="Google-Summer-of-Code-2019">Google Summer of Code 2019</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2019Projects" title="https://wiki.freebsd.org/SummerOfCode2019Projects">2019 Summer of Code Project Wikis</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2019Projects" title="2019 Summer of Code Project Wikis">https://wiki.freebsd.org/SummerOfCode2019Projects</a></td></tr><tr><td><a href="https://summerofcode.withgoogle.com/archive/2019/organizations/6504969929228288/" title="https://summerofcode.withgoogle.com/archive/2019/organizations/6504969929228288/">2019 Summer of Code Projects</a></td><td>
-	    URL: <a href="https://summerofcode.withgoogle.com/archive/2019/organizations/6504969929228288/" title="2019 Summer of Code Projects">https://summerofcode.withgoogle.com/archive/2019/organizations/6504969929228288/</a></td></tr></table><p>
-	Contact: Summer of Code Admins &lt;<a href="mailto:soc-admins@freebsd.org">soc-admins@freebsd.org</a>&gt;
-	</p>
-      <p>The FreeBSD Project is pleased to have participated in
-	Google Summer of Code 2019 marking our 14th year of
-	participation.
-	This year we had six successful projects:</p>
-
-      <ul>
-	<li><i>Dual-stack ping command</i> by J�n Su&#269;an</li>
-
-	<li><i>Firewall test suite</i> by Ahsan Barkati</li>
-
-	<li><i>Kernel sanitizers</i> by Costin Caraba&#537;</li>
-
-	<li><i>MAC policy on IP addresses for FreeBSD
-	Jail</i> by Shivank Garg</li>
-
-	<li><i>Separation of ports build process from local
-	installation</i> by Theron Tarigo</li>
-
-	<li><i>Virtual memory compression</i> by
-	Paavo-Einari Kaipila</li>
-      </ul>
-
-      <p>
-	We thank Google for the opportunity to work with these
-	students and hope
-	they continue to work with FreeBSD in the future.</p>
-
-    <p>This project was sponsored by Google Summer of Code.</p><hr /><h2><a name="GSoC'19-Project---MAC-policy-on-IP-addresses-in-Jail:-mac_ipacl" href="#GSoC'19-Project---MAC-policy-on-IP-addresses-in-Jail:-mac_ipacl" id="GSoC'19-Project---MAC-policy-on-IP-addresses-in-Jail:-mac_ipacl">GSoC'19 Project - MAC policy on IP addresses in Jail: mac_ipacl</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D20967" title="https://reviews.freebsd.org/D20967">FreeBSD's Phabricator Differential Link</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D20967" title="FreeBSD's Phabricator Differential Link">https://reviews.freebsd.org/D20967</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd/compare/master...shivankgarg98:shivank_MACPolicyIPAddressJail" title="https://github.com/freebsd/freebsd/compare/master...shivankgarg98:shivank_MACPolicyIPAddressJail">Github Diff Link</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd/compare/master...shivankgarg98:shivank_MACPolicyIPAddressJail" title="Github Diff Link">https://github.com/freebsd/freebsd/compare/master...shivankgarg98:shivank_MACPolicyIPAddressJail</a></td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2019Projects/MACPolicyIPAddressJail" title="https://wiki.freebsd.org/SummerOfCode2019Projects/MACPolicyIPAddressJail">Project Wiki Page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2019Projects/MACPolicyIPAddressJail" title="Project Wiki Page">https://wiki.freebsd.org/SummerOfCode2019Projects/MACPolicyIPAddressJail</a></td></tr></table><p>
-	Contact: Shivank Garg &lt;<a href="mailto:shivank@FreeBSD.org">shivank@FreeBSD.org</a>&gt;
-	</p>
-      <p><b>About -</b> With the introduction of VNET(9)
-	in FreeBSD, Jails are free to
-	set their IP addresses. However, this privilege may need
-	to be limited by
-	the host as per its need for multiple security reasons.
-	This project uses mac(9) for an access control framework
-	to impose
-	restrictions on FreeBSD jails according to rules defined
-	by the root of the
-	host using sysctl(8). It involves the development of a
-	dynamically loadable
-	kernel module (mac_ipacl) based on The TrustedBSD MAC
-	Framework to
-	implement a security policy for configuring the network
-	stack.
-	This project allows the root of the host to define the
-	policy rules to
-	limit the root of a jail to a set of IP (v4 or v6)
-	addresses and/or subnets
-	for a set of interfaces.</p>
-
-      <p>Features this new MAC policy module are:</p>
-
-      <ul>
-	<li>The host can define one or more lists of IP
-	addresses/subnets
-      	for the jail to choose from.</li>
-
-	<li>The host can restrict the jail from setting certain IP
-	addresses or
-      	prefixes (subnets).</li>
-
-	<li>The host can restrict this privilege to a few network
-	interfaces.</li>
-      </ul>
-
-      <p>
-	<b>Implementation -</b> The mac_ipacl module is
-	a loadable kernel module. It
-	implements mac checks in netinet/in.c and netinet6/in6.c
-	to check the IP
-	addresses requested by jail. The idea to implement these
-	checks at these
-	places comes from the fact that SIOCAIFADDR (for IPv4) and
-	SIOCAIFADDR_IN6 (for IPv6) ioctl handlers are defined for
-	adding the IP
-	addresses to an interface. This is used by ifconfig (in
-	userspace) for
-	setting the IP address. The MAC Framework acts as
-	multiplexer between the
-	netinet and the module. The requested IP and the
-	credentials are checked
-	with the rules in mac_ipacl and output is returned
-	accordingly to netinet.
-	The module can be tuned with various sysctl and similarly,
-	policy rules are
-	also be defined with sysctl.</p>
-
-      <p><b>TestSuite -</b> Test scripts integrated with
-	kyua and ATF are included with
-	the module.</p>
-
-      <p><b>Using the module -</b> I have written a man
-	page for the module. Please
-	refer to the mac_ipacl(4) for using the new MAC module and
-	various examples.</p>
-
-      <p><b>Final Deliverables -</b></p>
-
-      <ul>
-	<li>A loadable kernel module - <a href="https://github.com/shivankgarg98/freebsd/tree/shivank_MACPolicyIPAddressJail/sys/security/mac_ipacl" shape="rect">mac_ipacl
-	in sys/security/mac_ipacl</a></li>
-	<li>ATF tests for the module in <a href="https://github.com/shivankgarg98/freebsd/tree/shivank_MACPolicyIPAddressJail/tests/sys/mac/ipacl" shape="rect">tests/sys/mac/ipacl</a></li>
-	<li>A man page for this new mac module - mac_ipacl.4 in
-	<a href="https://github.com/shivankgarg98/freebsd/blob/shivank_MACPolicyIPAddressJail/share/man/man4/mac_ipacl.4" shape="rect">share/man/man4/mac_ipacl.4</a></li>
-      </ul>
-
-      <p>This is a new project, developed as part of <b>Google
-	Summer of Code'19</b>
-	under the guidance of <b>Bjoern A. Zeeb</b>
-	&lt;<a href="mailto:bz@FreeBSD.org" shape="rect">bz@FreeBSD.org</a>&gt;. The module is
-	<b>reviewed</b> and <b>Revision for this project
-	is accepted and ready to
-	land</b>. It is yet to be merged with FreeBSD HEAD, and
-	waiting to be tested
-	by few more hands in the industry.</p>
-
-      <p>I'll be very thankful if you can give this module a try
-	and share your
-	valuable experience about it. Please be free to share your
-	ideas and
-	feedback on this module and please do not hesitate to send
-	me an email.</p>
-
-    <hr /><h2><a name="Improving-laptop-support" href="#Improving-laptop-support" id="Improving-laptop-support">Improving laptop support</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Foundation would like to ensure that running
-	FreeBSD on
-	contemporary hardware, including laptops, remains viable.
-	To that end
-	we plan to purchase the latest generation of one or more
-	of a family
-	of laptops preferred by members of the FreeBSD community,
-	evaluate the
-	existing state of hardware support, and implement missing
-	hardware
-	support where possible.</p>
-
-      <p>As the first laptop for this project we have selected a
-	7th Generation
-	Lenovo X1 Carbon.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="NFS-Version-4.2-implementation" href="#NFS-Version-4.2-implementation" id="NFS-Version-4.2-implementation">NFS Version 4.2 implementation</a></h2><p>
-	Contact: Rick Macklem &lt;<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>&gt;
-	</p>
-      <p>RFC-7862 describes a new minor revision to the NFS Version
-	4 protocol.
-	This project implements this new minor revision.</p>
-
-      <p>The NFS Version 4 Minor Version 2 protocol adds several
-	optional
-	features to NFS, such as support for SEEK_DATA/SEEK_HOLE,
-	file
-	copying done on the server that avoids data transfer over
-	the wire
-	and support for posix_fallocate(), posix_fadvise().
-	Hopefully these features can improve performance for
-	certain applications.</p>
-
-      <p>The implementation is now nearing completion and recent
-	work has been
-	mostly testing. A cycle of interoperability testing with
-	Linux has
-	just been completed. The main area that still needs
-	testing is use
-	of the pNFS server with NFSv4.2 and that should start
-	soon.
-	Once testing of pNFS is completed, I believe the code is
-	ready to
-	be incorporated into FreeBSD head/current.</p>
-
-      <p>Testing by others would be appreciated. The modified
-	kernel can be
-	found at https://svn.freebsd.org/base/projects/nfsv42/sys
-	and should
-	run with a recent FreeBSD head/current system. Client
-	mounts need the
-	"minorversion=2" mount option to enable this protocol.</p>
-
-    <hr /><h2><a name="Rockchip-RK3399-SoC's-eMMC-support" href="#Rockchip-RK3399-SoC's-eMMC-support" id="Rockchip-RK3399-SoC's-eMMC-support">Rockchip RK3399 SoC's eMMC support</a></h2><p>
-	Contact: Ganbold Tsagaankhuu &lt;<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>&gt;
-	</p>
-      <p>The followings features have been added to support RK3399
-	SoC eMMC on FreeBSD:</p>
-
-      <ul>
-	<li>Extended simple_mfd driver to expose a syscon interface if
-	that node is also compatible with syscon. For instance,
-	Rockchip RK3399's GRF (General Register Files) is
-	compatible
-	with simple-mfd as well as syscon and has devices like
-	usb2-phy, emmc-phy and pcie-phy etc. under it.</li>
-
-	<li>Made Rockchip's General Register Files driver the subclass
-	of Simple MFD driver</li>
-
-	<li>Added driver for Rockchip RK3399 eMMC PHY.</li>
-
-	<li>Added eMMC support codes for Rockchip RK3399 SoC.</li>
-
-	<li>All above was tested on NanoPC-T4 board.</li>
-      </ul>
-
-    <hr /><h2><a name="syzkaller-on-FreeBSD" href="#syzkaller-on-FreeBSD" id="syzkaller-on-FreeBSD">syzkaller on FreeBSD</a></h2><p>
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Michael Tuexen &lt;<a href="mailto:tuexen@FreeBSD.org">tuexen@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Samy Al Bahra &lt;<a href="mailto:sbahra@freebsd.org">sbahra@freebsd.org</a>&gt;
-	</p>
-      <p>See the syzkaller entry in the 2019q1 quarterly report for
-	an
-	introduction to syzkaller.</p>
-
-      <p>Work has continued on fixing bugs uncovered by syzkaller.
-	Over a dozen
-	kernel bugs fixed in the past three months have been
-	directly attributed
-	to syzkaller, and a number of syzkaller reproducers have
-	been
-	incorporated into our test suite.</p>
-
-      <p>backtrace.io, via Samy, has graciously provided a large
-	server for
-	running a dedicated syzkaller instance to fuzz FreeBSD
-	under bhyve.
-	Though syzbot, the public syzkaller instance run by
-	Google, already
-	fuzzes FreeBSD, it has proven fruitful to run multiple
-	syzkaller
-	instances: different instances find different bugs, and
-	syzkaller.backtrace.io allows us to experiment with
-	FreeBSD-specific
-	extensions. In particular, this instance currently uploads
-	data about
-	each crash to backtrace.io, making it much easier to
-	triage and analyze
-	crashes. We plan to make this service generally available
-	to FreeBSD
-	developers in the near future.</p>
-
-      <p>Going forward we will continue to extend syzkaller
-	coverage and make it
-	simpler for users and developers to run private instances,
-	and
-	optionally collect kernel crash information for debugging
-	or for
-	submission.</p>
-
-    <p>This project was sponsored by backtrace.io, and The FreeBSD Foundation.</p><hr /><h2><a name="TPM2-Software-Stack-(TSS2)" href="#TPM2-Software-Stack-(TSS2)" id="TPM2-Software-Stack-(TSS2)">TPM2 Software Stack (TSS2)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://tpm2-tss.readthedocs.io/en/latest/index.html" title="https://tpm2-tss.readthedocs.io/en/latest/index.html">tpm2-tss Documentation</a></td><td>
-	    URL: <a href="https://tpm2-tss.readthedocs.io/en/latest/index.html" title="tpm2-tss Documentation">https://tpm2-tss.readthedocs.io/en/latest/index.html</a></td></tr><tr><td><a href="https://github.com/tpm2-software/" title="https://github.com/tpm2-software/">tpm2 Source Repository</a></td><td>
-	    URL: <a href="https://github.com/tpm2-software/" title="tpm2 Source Repository">https://github.com/tpm2-software/</a></td></tr><tr><td><a href="https://lists.01.org/postorius/lists/tpm2.lists.01.org/" title="https://lists.01.org/postorius/lists/tpm2.lists.01.org/">tpm2 mailing list</a></td><td>
-	    URL: <a href="https://lists.01.org/postorius/lists/tpm2.lists.01.org/" title="tpm2 mailing list">https://lists.01.org/postorius/lists/tpm2.lists.01.org/</a></td></tr><tr><td><a href="ircs://chat.freenode.net:6697/tpm2.0-tss" title="ircs://chat.freenode.net:6697/tpm2.0-tss">tpm2 irc channel</a></td><td>
-	    URL: <a href="ircs://chat.freenode.net:6697/tpm2.0-tss" title="tpm2 irc channel">ircs://chat.freenode.net:6697/tpm2.0-tss</a></td></tr></table><p>
-	Contact: D Scott Phillips &lt;<a href="mailto:scottph@FreeBSD.org">scottph@FreeBSD.org</a>&gt;
-	</p>
-      <p>Intel has contributed ports of the TPM2 Software Stack to
-	the ports tree, with
-	the new ports security/tpm2-tss, security/tpm2-tools,
-	security/tpm2-abrmd.
-	<tt>tpm2-tss</tt> contains a set of libraries which expose
-	various TPM2 APIs for using
-	a TPM conforming to the TCG TPM 2.0 specification.
-	<tt>tpm2-tools</tt> provides a set
-	of command line tools which use the <tt>tpm2-tss</tt>
-	libraries to perform tpm
-	operations. Finally, <tt>tpm2-abrmd</tt> is a userspace
-	daemon which acts as a TPM
-	Access Broker and Resource Manager, multiplexing many TPM
-	users onto a single
-	TPM device.</p>
-
-      <p>Sponsored by: Intel Corporation</p>
-
-    <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><h2><a name="Casueword(9)-livelock" href="#Casueword(9)-livelock" id="Casueword(9)-livelock">Casueword(9) livelock</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>The Compare-And-Swap (CAS) is one of the fundamental
-	building blocks
-	for hardware-assisted atomic read/modify/write operations.
-	Some
-	architectures support it directly, for instance x86 and
-	sparc. Others
-	provide different building blocks, usually the pair of
-	Load
-	Linked/Store Conditional instructions (ll/sc) which can be
-	used to construct
-	CAS or other atomic operations like Fetch-And-Add or any
-	atomic
-	arithmetic ops using plain arithmetic instructions. An
-	example is the
-	LDXR/STXR pair on AArch64.</p>
-
-      <p>The ll/sc operation is performed by first using the load
-	linked
-	instruction to load a value from memory and simultaneously
-	mark the
-	cache line for exclusive access. The value is then updated
-	by the
-	store conditional instruction, but only if there were not
-	any writes to
-	the marked cache line. Any write by another CPU makes the
-	store
-	instruction fail. So typically atomic primitives on ll/sc
-	architectures retry the whole operation if only store
-	failed, because
-	it just means that this CPU either lost a race, or even
-	the failure
-	was spurious. This is so called strong version of CAS and
-	atomics.
-	If primitive returns failure instead, the CAS variant is
-	called weak
-	by C standard.</p>
-
-      <p>For the FreeBSD threading library lock implementation,
-	when the fast path
-	mode in userspace was not possible, the kernel often needs
-	to do a CAS
-	operation on user memory location. In addition to all
-	guarantees of
-	normal CAS, it also must ensure the safety and tolerance
-	to paging.
-	In FreeBSD, the casueword32(9) primitive provides CAS on
-	usermode
-	32bit words for kernel. Casueword32(9) was implemented as
-	strong CAS,
-	similarly to the mode of operation of hardware CAS
-	instructions on
-	x86.</p>
-
-      <p>Using the strong implementation for casueword may be
-	dangerous,
-	since the same address is potentially accessible to other,
-	potentially
-	malicious, threads in the same or other processes. If
-	such a thread constantly dirties the cache line used by a
-	ll/sc loop, it
-	could practically force the kernel-mode thread to remain
-	stuck in the loop
-	forever. Since the loop is tight, and it does not check
-	for signals,
-	the thread cannot be stopped or killed.</p>
-
-      <p>The solution is to make the casueword implementation weak,
-	which means that
-	the interface of the primitive must be changed to allow
-	notifying the
-	caller about spurious failures. Also, it is now the
-	caller's responsibility
-	to retry as appropriate.</p>
-
-      <p>The change to casueword was made for all architectures.
-	Even on x86,
-	the PSL.ZF value after the CMPXCHG instruction was
-	returned directly
-	for the new casueword. All two dozens uses of the
-	primitive, all
-	located in <i>kern_umtx.c</i>, were inspected
-	and retry added as needed.</p>
-
-      <p>As a somewhat related note, in-kernel
-	<tt>atomic_cmpset(9)</tt> operations are
-	strong, while <tt>atomic_fcmpset(9)</tt> should be weak,
-	unless broken by
-	a specific architecture. The general attitude seems to be
-	that retry is the
-	duty of the primitive's caller.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Kernel-Mapping-Protections" href="#Kernel-Mapping-Protections" id="Kernel-Mapping-Protections">Kernel Mapping Protections</a></h2><p>
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	</p>
-      <p>Modern CPU architectures have the ability to flag memory
-	mappings as
-	"no-execute" (NX), which prevents that memory from being
-	executed by a
-	processor. NX mappings are an important security
-	mitigation since they help
-	segregate code and data, blocking unintentional execution
-	of memory whose
-	contents is controlled by an attacker. W^X (write XOR
-	execute) is a security
-	policy which disallows the creation of mappings that are
-	simultaneously
-	writeable and executable. Under this policy, memory whose
-	contents can be
-	modified must be mapped with the NX flag. This policy
-	makes it harder to exploit
-	bugs that permit an attacker to arbitrarily overwrite
-	data.</p>
-
-      <p>FreeBSD has long made use of the NX flag for userspace
-	mappings whenever
-	possible, but only in the past several years has it been
-	applied to kernel
-	mappings. A recent project has sought to implement a
-	W^X-by-default policy for
-	the amd64 kernel by completing an audit of the remaining
-	executable mappings in
-	the kernel, and making modifications to either apply the
-	NX bit to those
-	mappings or to make them read-only. This work has landed
-	in HEAD and will be
-	available in FreeBSD 13.0 and 12.2. Similar work for other
-	CPU architectures is
-	also planned.</p>
-
-      <p>To help audit kernel mapping protections, the
-	vm.pmap.kernel_maps sysctl was
-	added; it dumps a snapshot of the kernel's page table
-	entries and their
-	attributes. This way, mappings violating the W^X policy
-	can easily be
-	discovered and investigated, and the sysctl provides
-	information useful to
-	anyone interested in kernel memory layout.</p>
-
-      <p>With a few rare exceptions, the only kernel mappings which
-	require execute
-	permission are those of the kernel executable itself, and
-	loadable kernel
-	modules. A number of other regions of memory were
-	unnecessarily being mapped
-	without NX, and these were identified and corrected first.
-	To address the
-	kernel code mappings, the amd64 kernel linker script was
-	modified to pad the
-	.text segment to a 2MB boundary. To improve performance,
-	the kernel creates
-	superpage mappings of its .text segment, but this means
-	that any data cohabiting
-	the final 2MB .text mapping is mapped with execute
-	permissions. The padding
-	allows executable code to be segregated from data which
-	follows in the kernel
-	image, avoiding this problem and maintaining the superpage
-	optimization at the
-	expense of some wasted RAM.</p>
-
-      <p>Enforcing W^X turned out to be somewhat trickier. Unlike
-	other CPU
-	architectures supported by FreeBSD, amd64 kernel modules
-	are linked as
-	relocatable object files, i.e., .o files. (On other
-	architectures, they are
-	dynamically shared objects (DSOs, or .so files), as one
-	might naively expect.)
-	The use of .o files means that amd64 kernel modules
-	contain more efficient code
-	than they would if linked as DSOs, since DSOs inherently
-	make use of certain
-	types of indirection which allow shared libraries to be
-	loaded at arbitrary
-	addresses, and this indirection is useless in the kernel.
-	As part of this
-	project an attempt was made to switch amd64 to using DSOs
-	as well, since the
-	cost of this indirection can largely be mitigated with
-	modern toolchains, but it
-	was found that the use of DSOs would also force a change
-	to the code model used
-	when compiling amd64 kernel code, resulting in a further
-	performance penalty.</p>
-
-      <p>The main obstacle with the use of .o files is that
-	sections are not page-aligned
-	by default; the segregation of sections with differing
-	mapping protection
-	requirements is done by the static linker when linking a
-	DSO or executable file.
-	Since mapping protections are applied at the granularity
-	of the page size (4KB
-	on amd64), the overlap of sections within a page causes
-	problems since, for
-	example, the end of the read-only .text section may
-	overlap with the beginning
-	of the read-write .data section. One possible solution is
-	to perform any
-	required section reordering and padding at kernel module
-	load time, but this
-	approach breaks debugging tools such as dtrace(1) and kgdb
-	which assume that the
-	kernel linker does not modify the layout of loadable
-	modules. As a result, an
-	amd64 kernel module linker script is now used to insert
-	padding for specific
-	sections. Finally, the kernel linker was modified to
-	restrict mapping
-	protections based on section flags.</p>
-
-      <p>As a result of all of this, amd64 kernels now boot without
-	any writeable,
-	executable mappings. Though some of the work was
-	architecture-specific, much of
-	it can and will be leveraged to provide the same policy
-	for our other supported
-	architectures.</p>
-
-    <p>This project was sponsored by Netflix.</p><hr /><h2><a name="Kernel-ZLIB-Update" href="#Kernel-ZLIB-Update" id="Kernel-ZLIB-Update">Kernel ZLIB Update</a></h2><p>
-	Contact: Xin Li &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Yoshihiro Ota &lt;<a href="mailto:ota@j.email.ne.jp">ota@j.email.ne.jp</a>&gt;
-	</p>
-      <p>The ZLIB is a compression library is widely used in
-	various software.
-	The FreeBSD system had used an ancient (over 20 year-old)
-	version
-	of zlib (version 1.0.4) and total of 3 versions, one in
-	user-land,
-	one in ZFS, and one in kernel.
-	Xin and Yoshihiro upgraded zlib to the latest and
-	eliminated 2 extra copies.
-	Along the efforts, zlib version was upgraded to 1.2.11,
-	netgraph's ppp is
-	re-implemented to use the standard zlib, and removed
-	unmaintained code.
-	We now only have one and the latest version of zlib in
-	FreeBSD code base,
-	new compress, compress2, and uncompress APIs exposed in
-	the kernel,
-	and importing changes from zlib will be simple.</p>
-
-      <p>Kernel zlib changes</p>
-
-      <ul>
-	<li><a href="https://reviews.freebsd.org/D20193" shape="rect">sys/crc32.h
-	is split to avoid object file name conflict with
-	ZLIB's</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D20191" shape="rect">contrib/zlib
-	is moved to sys/contrib/zlib</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D19706" shape="rect">Kernel
-	started switching to sys/contrib/zlib and ZFS copy
-	dropped</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D21156" shape="rect">Kernel
-	zcalloc is introduced and compress, compress2, and
-	uncompress APIs are exposed to kernel</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D21375" shape="rect">Removed zlib
-	1.0.4 from kernel</a></li>
-      </ul>
-
-      <p>
-	Kernel zlib user updates</p>
-
-      <ul>
-	<li><a href="https://reviews.freebsd.org/D21176" shape="rect">kern_ctf.c
-	updated</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D20222" shape="rect">opencryptodeflate
-	updated</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D20271" shape="rect">geom_uzip
-	updated</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D21408" shape="rect">subr_compressor
-	updated</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D20272" shape="rect">if_mxge
-	updated</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D21175" shape="rect">bxe
-	updated</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D21186" shape="rect">ng_deflate
-	updated</a></li>
-      </ul>
-
-      <p>
-	Legacy code removals</p>
-
-      <ul>
-	<li><a href="https://reviews.freebsd.org/D20190" shape="rect">Removed MIPS
-	zlib elf trampoline</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D20248" shape="rect">Removed kgzip
-	and kgzldr</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D21099" shape="rect">Removed
-	gzip'ed a.out support</a></li>
-
-	<li><a href="https://reviews.freebsd.org/D21072" shape="rect">Removed ArmvX
-	elf_trampoline.c</a></li>
-      </ul>
-
-    <hr /><h2><a name="PROT_MAX-mmap/mprotect-maximum-protections-API" href="#PROT_MAX-mmap/mprotect-maximum-protections-API" id="PROT_MAX-mmap/mprotect-maximum-protections-API">PROT_MAX mmap/mprotect maximum protections API</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/rS349240" title="https://reviews.freebsd.org/rS349240">PROT_MAX commit</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/rS349240" title="PROT_MAX commit">https://reviews.freebsd.org/rS349240</a></td></tr></table><p>
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@freebsd.org">brooks@freebsd.org</a>&gt;
-	</p>
-      <p>Unix-like systems provide the <tt>mmap(2)</tt> system call
-	to allocate memory or
-	map files or devices into memory with specified access
-	protection, and the
-	<tt>mprotect(2)</tt> system call to change protections on
-	mapped memory. Protection
-	flags specify whether the memory may be read, written,
-	and/or executed
-	(<tt>PROT_READ</tt>, <tt>PROT_WRITE</tt>, <tt>PROT_EXEC</tt>
-	respectively). Traditionally,
-	<tt>mprotect(2)</tt> can be used to set any desired
-	protections (except that a
-	shared mapping of a file opened read-only cannot have
-	<tt>PROT_WRITE</tt> set).</p>
-
-      <p>A new macro <tt>PROT_MAX()</tt> adds a facility for
-	specifying the maximum possible
-	protection flags for <tt>mmap(2)</tt> and
-	<tt>mprotect(2)</tt> calls. The program can then
-	specify whether a mapping may be changed in the future to
-	allow a given access
-	protection. For example, a memory mapping can be set such
-	that it can have
-	read and write protections set, but may never be made
-	executable.</p>
-
-      <p>Maximum protection values are provided to the
-	<tt>PROT_MAX()</tt> macro, and are
-	OR'd with regular protection values.</p>
-
-      <p>This change allows (e.g.) a region that must be writable
-	during run-time
-	linking or JIT code generation to be made permanently
-	read+execute after
-	writes are complete. This complements Write-XOR-Execute
-	(W^X) protections
-	available on other operating systems, allowing more
-	precise control by the
-	programmer.</p>
-
-      <p>For example, to request memory that cannot be made
-	executable:
-	<ttt>
-	mmap(NULL, size, PROT_READ | PROT_WRITE |
-	PROT_MAX(PROT_READ | PROT_WRITE),
-	MAP_ANON, -1, 0);
-	</ttt></p>
-
-      <p>and to request memory that may have execute permission
-	enabled later on, but
-	is not currently executable:</p>
-
-      <p><ttt>
-	mmap(NULL, size,
-	PROT_READ | PROT_WRITE | PROT_MAX(PROT_READ | PROT_WRITE |
-	PROT_EXECUTE),
-	MAP_ANON, -1, 0);
-	</ttt></p>
-
-      <p>This change alters mprotect argument checking and returns
-	an error when
-	unhandled protection flags are set. This differs from
-	POSIX (in that POSIX
-	only specifies an error if a valid permission can not be
-	set), but is the
-	documented behavior on Linux and more closely matches
-	historical mmap behavior.</p>
-
-      <p>In addition to explicit setting of the maximum
-	permissions, an experimental
-	sysctl <tt>vm.imply_prot_max</tt> causes mmap to assume
-	that the initial permissions
-	requested should be the maximum when the sysctl is set to
-	1. This behavior is
-	known to break code that uses <tt>PROT_NONE</tt>
-	reservations before mapping contents
-	into part of the reservation. A later version of this work
-	is expected to
-	provide per-binary and per-process opt-in/out options and
-	this sysctl may be
-	removed in its current form. As such it is undocumented.</p>
-
-      <p>While these flags are non-portable, they can be used in
-	portable code with
-	simple ifdefs to expand <tt>PROT_MAX()</tt> to 0.</p>
-
-      <p>Sponsors: DARPA, AFRL</p>
-
-    <hr /><h2><a name="Randomized-Top-of-Stack-pointer" href="#Randomized-Top-of-Stack-pointer" id="Randomized-Top-of-Stack-pointer">Randomized Top of Stack pointer</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>After the ASLR so useful addition, next in the series of
-	the
-	buzzword-compliant checkboxes is the stack addresses
-	randomization.</p>
-
-      <p>The main userspace thread stack on FreeBSD is
-	traditionally allocated
-	from the top of the user address space and grows down.
-	Besides the
-	initial pointer for the stack on userspace entry, this
-	area also
-	contains structures for program arguments and environment
-	(so called
-	strings), and aux vector data for ELF images.</p>
-
-      <p>Considering the goal of randomizing the addresses of
-	strings and main
-	thread initial frame, moving the main stack area in the
-	address space
-	is not feasible. It would cause significant ABI breakage,
-	invalidates
-	the knowledge already coded into many introspection tools,
-	and causes
-	unneeded additional fragmentation of the user address
-	space.</p>
-
-      <p>Instead a typical approach of adding a gap of randomized
-	size between
-	top of stack and a place for strings was used. It is done
-	in a way
-	which preserves the stack alignment requirement. Stack gap
-	is only
-	enabled if ASLR is enabled (not default) and stack gap
-	itself is
-	enabled (default if ASLR is enabled). Stack gap is
-	specified in
-	percentage of the total stack size that can be used for
-	maximum gap.</p>
-
-      <p>The main drawback of the gap approach was shortly
-	identified. Since
-	gap is cut from the normal stack area, attempts of the
-	programs to
-	reduce stack size using rlimit(RLIMIT_STACK) could cut the
-	active stack
-	region if new limit happens to be smaller than the gap.
-	E.g. on amd64
-	with its default 512M main thread stack, even one percent
-	of the max
-	gap gives approximately 5M of unused stack, that can blow
-	up the limit
-	of several KBs.</p>
-
-      <p>Typical reason for using rlimit(2) this way is for
-	programs that wire
-	all of its address space with mlockall(2), trying to
-	reduce potential
-	wired stack size to avoid exceeding RLIMIT_MEMLOCK.</p>
-
-      <p>First victim of that issue was ntpd, which resets the
-	stack limit
-	after start for a really small value. Currently the wiring
-	was removed
-	from ntpd, because apparently it does not make the
-	timekeeping better
-	by any means, contrary to popular belief.</p>
-
-      <p>My opinion is that the problem is more in the user
-	interface area than
-	in the gap approach itself. We should make it easy to
-	specify small
-	gap sizes, which cannot be done with integral percentage
-	interface.
-	So far I did not formulated a way to do this which I would
-	like, and
-	since nobody looked for a good solution because after ntpd
-	was fixed,
-	the severity of the issue seems very low.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Signals-delivered-on-unhandled-Page-Faults" href="#Signals-delivered-on-unhandled-Page-Faults" id="Signals-delivered-on-unhandled-Page-Faults">Signals delivered on unhandled Page Faults</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p>
-      <p>By necessity, handling of page faults is separated into
-	two pieces. The
-	first is the architecture-dependent low-level machine
-	exception handler,
-	and the second is the architecture-independent
-	<tt>vm_fault()</tt> function in
-	<i>sys/vm/vm_fault.c</i>.</p>
-
-      <p>Machine-dependent code for page faults typically consists
-	of three
-	components: a trampoline written in assembly which creates
-	the C execution
-	environment and gathers hardware-supplied data about page
-	fault reason, a
-	<tt>trap()</tt> function which is common C-level entry
-	point to dispatch all
-	exceptions processing, and the <tt>trap_pfault()</tt> C
-	function to specifically
-	handle page faults. <tt>trap_pfault()</tt> calls
-	<tt>vm_fault()</tt> when help from VM is
-	needed to resolve the situation.</p>
-
-      <p>If the fault was handled either by
-	<tt>trap()</tt>/<tt>trap_pfault()</tt> or
-	<tt>vm_fault()</tt>,
-	the faulting instruction is restarted. If fault cannot be
-	handled for
-	any reason, the next action depends on the mode in which
-	the fault occured.
-	If it was in kernel, and the kernel installed a helper,
-	then the helper is
-	called instead of returning to the faulting instruction.
-	Otherwise,
-	a kernel-mode page fault causes a panic.</p>
-
-      <p>If the unhandled fault occured in usermode, then all
-	Unixes send a
-	signal to the thread whose execution caused the exception.
-	POSIX (or
-	Single Unix Specification) lists several cases where a
-	signal should be
-	sent, and specifies the signal number and <tt>si_code</tt>
-	from siginfo that
-	must be supplied with the signal.</p>
-
-      <p>Unfortunately, FreeBSD was rather non-compliant in this
-	regard. A long
-	time ago, to improve compliance, we changed the signal
-	sent on access
-	to a page with permissions incompatible with the access
-	mode.
-	That caused multiple problems with garbage collection
-	(GC)-based runtimes
-	which incorporated knowledge of the FreeBSD quirks, so the
-	<tt>machdep.prot_fault_translation</tt> sysctl knob was
-	added. More cases of
-	incompatibility were identified recently.</p>
-
-      <p>Part of the problem is that code to calculate the signal
-	and <tt>si_code</tt> from
-	the Mach error returned by <tt>vm_fault()</tt> was located
-	in <tt>trap_pfault()</tt>. In
-	other words, each architecture did that on its own, with a
-	specific set
-	of bugs and non-compliance. Sometimes code even
-	mis-interpreted returned
-	Mach errors as <tt>errno</tt>.</p>
-
-      <p>A new helper function <tt>vm_fault_trap()</tt> was added,
-	that does several
-	things for trap handlers: it creates ktrace points for
-	faults, calls
-	<tt>vm_fault()</tt>, and then interprets the result in
-	terms of the user-visible
-	error condition, returning precalculated signal number and
-	<tt>si_code</tt> to
-	the caller. Now <tt>trap_pfault()</tt> only needs to
-	provide signal numbers
-	for truly machine-dependent errors. For amd64, an example
-	of such a
-	case is a protection key violation.</p>
-
-      <p>Besides compliance and bug fixes, we also provided some
-	refinements to
-	userspace about the reason of the delivered signal. For
-	instance, on
-	SIGBUS caused by copy-on-write failure due to exceeding
-	swap
-	reservation limit, we provide specific <tt>si_code</tt>
-	<tt>BUS_OOMERR</tt>.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="Broadcom-ARM64-SoC-support" href="#Broadcom-ARM64-SoC-support" id="Broadcom-ARM64-SoC-support">Broadcom ARM64 SoC support</a></h2><p>
-	Contact: Michal Stanek &lt;<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>&gt;
-	<br />
-	Contact: Kornel Duleba &lt;<a href="mailto:mindal@semihalf.com">mindal@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p>
-      <p>The Semihalf team continued working on FreeBSD support for
-	the
-	<a href="https://www.broadcom.com/products/embedded-and-networking-processors/communications/bcm58712/" shape="rect">Broadcom
-	BCM5871X SoC series</a></p>
-
-      <p>BCM5871X are quad-core 64-bit ARMv8 Cortex-A57
-	communication
-	processors targeted for networking applications such as
-	10G routers,
-	gateways, control plane processing and NAS.</p>
-
-      <p>Completed since the last update:</p>
-
-      <ul>
-	<li>iProc PCIe root complex (internal and external buses):
-	fixes and improvements,</li>
-
-	<li>Crypto engine acceleration for IPsec offloading.</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Upstreaming of work. This work is expected to be
-	submitted/merged
-	to HEAD in the Q4 of 2019.</li>
-      </ul>
-
-    <p>This project was sponsored by Juniper Networks, Inc.</p><hr /><h2><a name="FreeBSD-support-for-the-forthcoming-Arm-Morello-CPU,-SoC,-and-board" href="#FreeBSD-support-for-the-forthcoming-Arm-Morello-CPU,-SoC,-and-board" id="FreeBSD-support-for-the-forthcoming-Arm-Morello-CPU,-SoC,-and-board">FreeBSD support for the forthcoming Arm Morello CPU, SoC, and board</a></h2><p>
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p>
-      <p>In September 2019, Arm announced Morello, an experimental
-	multicore superscalar
-	ARMv8-A CPU, SoC, and prototype board extended to
-	implement the CHERI
-	protection model. Morello will become available in 2021.
-	More details can be
-	found in
-	<a href="https://www.arm.com/blogs/blueprint/digital-security-by-design" shape="rect">Arm's
-	blog</a>, a
-	<a href="https://www.lightbluetouchpaper.org/2019/10/18/ukri-digital-security-by-design-a-190m-research-programme-around-arms-morello-an-experimental-armv8-a-cpu-soc-and-board-with-cheri-support/" shape="rect">Light
-	Blue Touchpaper blog</a>,
-	and the main
-	<a href="https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/" shape="rect">CHERI
-	website</a>.</p>
-
-      <p>We have updated CheriBSD, a CHERI-adapted version of
-	FreeBSD originally
-	targeted at the MIPS-based SRI/Cambridge CHERI processor
-	prototype, to support
-	the current draft architecture. This includes full
-	userspace spatial and
-	referential memory safety
-
-	<a href="https://www.cl.cam.ac.uk/research/security/ctsrd/pdfs/201904-asplos-cheriabi.pdf" shape="rect">CheriABI</a>,
-	as well as backwards compatibility to support running
-	existing ARMv8-A
-	userspace binaries.</p>
-
-      <p>We will continue to update CheriBSD/Morello as the ISA is
-	finalised. Will also
-	closely track the public CheriBSD/MIPS trunk, picking up
-	new software features
-	utilizing CHERI as they mature, as well as to pick up
-	changes from the baseline
-	FreeBSD development trunk.</p>
-
-      <p>We currently anticipate releasing CheriBSD/Morello as open
-	source once the ISA
-	and toolchain are published in 2020.</p>
-
-      <p>Sponsors: DARPA, AFRL</p>
-
-    <hr /><h2><a name="FreeBSD/powerpc-Project" href="#FreeBSD/powerpc-Project" id="FreeBSD/powerpc-Project">FreeBSD/powerpc Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/powerpc/ports" title="https://wiki.freebsd.org/powerpc/ports">Status of FreeBSD ports on PowerPC</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/powerpc/ports" title="Status of FreeBSD ports on PowerPC">https://wiki.freebsd.org/powerpc/ports</a></td></tr><tr><td><a href="https://wiki.freebsd.org/powerpc/ports/PortsOnGcc" title="https://wiki.freebsd.org/powerpc/ports/PortsOnGcc">Status of FreeBSD ports on PowerPC built using gcc</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/powerpc/ports/PortsOnGcc" title="Status of FreeBSD ports on PowerPC built using gcc">https://wiki.freebsd.org/powerpc/ports/PortsOnGcc</a></td></tr><tr><td><a href="https://wiki.freebsd.org/powerpc/ports/PortsOnClang" title="https://wiki.freebsd.org/powerpc/ports/PortsOnClang">Status of FreeBSD ports on PowerPC built using clang</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/powerpc/ports/PortsOnClang" title="Status of FreeBSD ports on PowerPC built using clang">https://wiki.freebsd.org/powerpc/ports/PortsOnClang</a></td></tr><tr><td><a href="https://wiki.freebsd.org/powerpc/llvm-elfv2" title="https://wiki.freebsd.org/powerpc/llvm-elfv2">Bringing LLVM to PowerPC64 target, using OpenPower ELF v2 ABI</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/powerpc/llvm-elfv2" title="Bringing LLVM to PowerPC64 target, using OpenPower ELF v2 ABI">https://wiki.freebsd.org/powerpc/llvm-elfv2</a></td></tr></table><p>
-	Contact: Mark Linimon (ports) &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Justin Hibbits (src) &lt;<a href="mailto:jhibbits@FreeBSD.org">jhibbits@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Piotr Kubaj (ports) &lt;<a href="mailto:pkubaj@FreeBSD.org">pkubaj@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD/powerpc project continues to make great
-	strides. However,
-	as we discovered at BSDCan 2019, we have not done a great
-	job of letting
-	people know.</p>
-
-      <p>Key points:</p>
-
-      <ul>
-	<li>powerpc64 src on recent hardware has been
-	production-quality for over
-	a year now.</li>
-	<li>powerpc64 ports has been developer-quality for over 18
-	months now.</li>
-      </ul>
-
-      <p>
-	The main targeted platforms:</p>
-
-      <ul>
-	<li>powerpc64 on IBM POWER8 and POWER9 chips (the most recent
-	available).
-	This is the primary focus going forward. FreeBSD 12 is
-	required;
-	FreeBSD 13 is recommended.</li>
-	<li>powerpc64 on older Apple Power Macs, on a continuing but
-	secondary
-	basis. Any FreeBSD version should work.</li>
-	<li>powerpc64 on x5000. However, this is still developer-only
-	quality.
-	FreeBSD 13 is recommended.</li>
-	<li>powerpcspe on Amiga A1222. However, this is still
-	developer-only quality.
-	FreeBSD 13 is recommended.</li>
-      </ul>
-
-      <p>
-	The software status:</p>
-
-      <ul>
-	<li>powerpc*/12 and earlier still remain on the antiquated
-	gcc4.2.1 in
-	base.</li>
-	<li>powerpc*/13 will soon be switched to llvm90 in base. A
-	great deal
-	of work has been undertaken to ensure as few regressions
-	as possible.
-	Once that switch has occurred (see llvm-elfv2 link above),
-	powerpc*/13
-	support on gcc4.2.1 will no longer be a priority.</li>
-	<li>FreeBSD.org package sets are available for powerpc64/12
-	(quarterly)
-	and powerpc64/13 (default) through the usual method.</li>
-	<li>Firefox works on powerpc64 using experimental (not-yet
-	committed) patches,</li>
-	<li>As of the most recent package build on powerpc64/13 (still
-	gcc4.2.1),
-	the following statistics apply:
-	<table class="tblbasic">
-	<tr><th rowspan="1" colspan="1"> Queued </th><th rowspan="1" colspan="1"> Built </th><th rowspan="1" colspan="1"> Failed </th><th rowspan="1" colspan="1"> Skipped </th><th rowspan="1" colspan="1"> Ignored </th></tr>
-	<tr><td rowspan="1" colspan="1"> 33306 </td><td rowspan="1" colspan="1"> 30514 </td><td rowspan="1" colspan="1"> 245 </td><td rowspan="1" colspan="1"> 1686 </td><td rowspan="1" colspan="1"> 861 </td></tr>
-	</table>
-	</li>
-	<li>More ports fixes are being committed every day.</li>
-      </ul>
-
-      <p>
-	Also, Piotr would like to thank the FreeBSD Foundation for
-	funding
-	his personal Talos, and Raptor (via its IntegriCloud
-	subsidiary) for
-	loaning a server on which talos.anongoth.pl runs.</p>
-
-      <p>The team would like to thank IBM for the loan of two
-	POWER8 machines,
-	and Oregon State University (OSU) for providing the
-	hosting. As well,
-	we would like to thank the clusteradm team for keeping the
-	Tyan POWER8
-	machines online that are hosted at <a href="https://www.nyi.net" shape="rect">NYI</a>.</p>
-
-    <hr /><h2><a name="NXP-ARM64-SoC-support" href="#NXP-ARM64-SoC-support" id="NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></h2><p>
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	</p>
-      <p>The Semihalf team initiated working on FreeBSD support for
-	the
-	<a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A" shape="rect">NXP
-	LS1046A SoC</a></p>
-
-      <p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors
-	with
-	integrated packet processing acceleration and high speed
-	peripherals
-	including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0
-	for a wide
-	range of networking, storage, security and industrial
-	applications.</p>
-
-      <p>Completed since the last update:</p>
-
-      <ul>
-	<li>DPAA Network interface support</li>
-
-	<li>SD/MMC</li>
-
-	<li>USB3.0</li>
-
-	<li>I2C</li>
-
-	<li>GPIO</li>
-      </ul>
-
-      <p>
-	In progress:</p>
-
-      <ul>
-	<li>QSPI</li>
-
-	<li>Network performance improvements</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Upstreaming of developed features. This work is expected
-	to
-	be submitted/merged to HEAD in the Q4 of 2019.</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by Alstom Group.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><h2><a name="gets(3)-retirement" href="#gets(3)-retirement" id="gets(3)-retirement">gets(3) retirement</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p>
-      <p>gets is an obsolete C library routine for reading a string
-	from standard
-	input. It was removed from the C standard as of C11
-	because there was no
-	way to use it safely. Prompted by a comment during Paul
-	Vixie's talk at
-	vBSDCon 2017 I started investigating what it would take to
-	remove gets
-	from libc.</p>
-
-      <p><a href="https://reviews.freebsd.org/D12298" shape="rect">The patch</a>
-	was posted to Phabricator
-	and refined several times, and the portmgr team performed
-	several
-	<a href="https://bugs.freebsd.org/222796" shape="rect">exp-runs</a> to
-	identify ports broken by
-	the removal. Symbol versioning is used to preserve binary
-	compatibility
-	for existing software that uses gets.</p>
-
-      <p>The change was <a href="https://reviews.freebsd.org/rS351659" shape="rect">committed</a>
-	in
-	September, and will be in FreeBSD 13.0.</p>
-
-    <p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreshPorts.org/" title="https://www.FreshPorts.org/">FreshPorts</a></td><td>
-	    URL: <a href="https://www.FreshPorts.org/" title="FreshPorts">https://www.FreshPorts.org/</a></td></tr><tr><td><a href="https://github.com/FreshPorts/git_proc_commit" title="https://github.com/FreshPorts/git_proc_commit">git_proc_commit code</a></td><td>
-	    URL: <a href="https://github.com/FreshPorts/git_proc_commit" title="git_proc_commit code">https://github.com/FreshPorts/git_proc_commit</a></td></tr><tr><td><a href="https://news.freshports.org/2019/09/03/things-you-didnt-know-freshports-can-do/" title="https://news.freshports.org/2019/09/03/things-you-didnt-know-freshports-can-do/">Things you didn&#8217;t know FreshPorts can do</a></td><td>
-	    URL: <a href="https://news.freshports.org/2019/09/03/things-you-didnt-know-freshports-can-do/" title="Things you didn&#8217;t know FreshPorts can do">https://news.freshports.org/2019/09/03/things-you-didnt-know-freshports-can-do/</a></td></tr></table><p>
-	Contact: Dan Langille &lt;<a href="mailto:dvl@FreeBSD.org">dvl@FreeBSD.org</a>&gt;
-	</p>
-      <p>FreshPorts consolidates commits into an easy-to-follow
-	format so you can track changes to your favorite ports.
-	It also processes src, doc, and www commit. FreshPorts
-	parses
-	incoming emails and refreshes the database with what it
-	finds.</p>
-
-      <p>In early September I started looking at how FreshPorts
-	could use a git repository for processing commits. The
-	result was <a href="https://news.freshports.org/2019/09/02/git-and-freshports/" shape="rect">an
-	approach</a> for identifying new commits and
-	for iterating through them.</p>
-
-      <p>The next idea was <a href="https://news.freshports.org/2019/09/18/moving-towards-commit-hooks/" shape="rect">commit
-	hooks</a> but the most interesting
-	bit of that exercise was commit iteration.</p>
-
-      <p>At the EuroBSDCon 2019 FreeBSD Developer summit, I wrote
-	up a small requirements section and then received great
-	help from two sources:</p>
-
-      <ul>
-	<li>Jan-Piet MENS recommended a <a href="https://www.freshports.org/devel/py-gitpython/" shape="rect">Python
-	library</a> and
-	it turned out to be great</li>
-	<li>Sergey Kozlov wrote Python code to create xml using
-	that Python library</li>
-      </ul>
-
-      <p>
-	On the trip home, I was able to get the code to parse
-	a git commit into XML and loaded into a FreshPorts
-	database.</p>
-
-      <p>Returning home from the conference, I created a new
-	FreshPorts instance for processing git based on the above.
-	The website has needed no changes related to git.</p>
-
-      <p>The remaining tasks:</p>
-
-      <ul>
-	<li>automate the script (git pull, etc)</li>
-
-	<li>detect new commits (for later iteration)</li>
-
-	<li>design a light-weight git hook</li>
-      </ul>
-
-      <p>
-	Event: EuroBSDCon 2019 Hackathon
-	Sponsored by: Intel Corporation (work done by Sergey
-	Kozlov)</p>
-
-    <hr /><h2><a name="Java-on-FreeBSD" href="#Java-on-FreeBSD" id="Java-on-FreeBSD">Java on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/openjdk-jdk11u" title="https://github.com/freebsd/openjdk-jdk11u">OpenJDK 11 repository at FreeBSD GitHub</a></td><td>
-	    URL: <a href="https://github.com/freebsd/openjdk-jdk11u" title="OpenJDK 11 repository at FreeBSD GitHub">https://github.com/freebsd/openjdk-jdk11u</a></td></tr></table><p>
-	Contact: Greg Lewis &lt;<a href="mailto:glewis@FreeBSD.org">glewis@FreeBSD.org</a>&gt;
-	</p>
-      <p>Over the last few quarters there has been considerable
-	work in improving
-	support for Java 11 and higher, with some work being
-	backported to Java 8.</p>
-
-      <p>Starting with the initial release in March on amd64, over
-	the
-	intervening months FreeBSD support was added for features
-	such as:</p>
-
-      <ul>
-	<li>Java Flight Recorder</li>
-
-	<li>HotSpot Serviceability Agent</li>
-
-	<li>HotSpot Debugger</li>
-
-	<li>DTrace</li>
-
-	<li>Javac Server</li>
-
-	<li>Java Sound</li>
-
-	<li>SCTP</li>
-      </ul>
-
-      <p>
-	In addition, support for the aarch64, i386 and powerpc64
-	architectures
-	was also added.</p>
-
-      <p>With most features supported, attention turned to
-	compliance, using the
-	internal JDK test suite as a method of measuring this.
-	Most work during
-	the third quarter has focused on this, with test failures
-	dropping from
-	50+ failures to only 2 tier1 test failures (which don't
-	appear to impact
-	functionality at all). Some significant fixes include:</p>
-
-      <ul>
-	<li>A stack overflow crash</li>
-
-	<li>Errors in external process handling</li>
-
-	<li>The unpack200 utility (on little endian systems)</li>
-
-	<li>HotSpot Debugger functionality such as thread enumeration</li>
-
-	<li>Networking functionality</li>
-      </ul>
-
-      <p>
-	Finally, this work has been forward ported to Java 12 and
-	13, with FreeBSD
-	gaining support for these versions on or just after the
-	day of release.</p>
-
-      <p>Note that this work has been a collaboration with many
-	others. While there
-	are too many contributors to list here (please take a look
-	at the commit
-	history of the GitHub repository), I'd like to recognise
-	Kurt Miller of
-	OpenBSD for his tireless work as a co-collaborator on Java
-	for BSD through
-	many years.</p>
-
-      <p>I'm also grateful to the sponsorship of the FreeBSD
-	Foundation, which has
-	allowed me to focus on this work for Q3.</p>
-
-    <p>This project was sponsored by FreeBSD Foundation.</p><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://community.kde.org/FreeBSD" title="https://community.kde.org/FreeBSD">KDE Community FreeBSD</a></td><td>
-	    URL: <a href="https://community.kde.org/FreeBSD" title="KDE Community FreeBSD">https://community.kde.org/FreeBSD</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p>
-      <p>The <i>KDE on FreeBSD</i> project packages the
-	software produced by
-	the KDE Community for FreeBSD. The software includes a
-	full desktop environment, the art application
-	<a href="https://kdenlive.org" shape="rect">https://kdenlive.org</a>
-	and hundreds of other applications that can be used on
-	any FreeBSD desktop machine.</p>
-
-      <p>Along with KDE itself, the team maintains the Qt
-	libraries, the CMake
-	build system, and a handful of other C++ libraries used in
-	the KDE stack.</p>
-
-      <p>The upstream releases KDE Frameworks (libraries) on a
-	monthly
-	cycle, KDE Plasma (the desktop environment) quarterly and
-	a collection of KDE Applications (usable everywhere) twice
-	a year.
-	The KDE on FreeBSD team chased a dozen updates to these
-	components
-	so that FreeBSD remains one of the most up-to-date systems
-	with KDE software (and Qt).</p>
-
-      <p>A large (and possibly breaking, still needs more
-	investigation)
-	change came with the release to KDE's Digikam 6.3.0, which
-	stopped
-	using its previous plugins system (the "old" plugins are
-	still used
-	by other KDE software).</p>
-
-      <p>A new entry in the net-im category was added for Ruqola, a
-	Rocket.chat client for rich instant-messaging.</p>
-
-      <p>CMake was updated twice. This forces the rebuild of
-	several thousand
-	C++-based ports. The KDE on FreeBSD team then fixes those
-	ports,
-	regardless of whether the error is in the CMake update, or
-	in
-	the upstream code. These updates tend to take a large
-	amount of effort,
-	since they touch unfamiliar (and often very-very-legacy)
-	code.</p>
-
-      <p>The <a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=New&amp;bug_status=Open&amp;bug_status=In%20Progress&amp;bug_status=UNCONFIRMED&amp;email1=kde%40FreeBSD.org&amp;emailassigned_to1=1&amp;emailtype1=substring&amp;f0=OP&amp;f1=OP&amp;f2=product&amp;f3=component&amp;f4=alias&amp;f5=short_desc&amp;f7=CP&amp;f8=CP&amp;f9=assigned_to&amp;j1=OR&amp;j_top=OR&amp;o2=substring&amp;o3=substring&amp;o4=substring&amp;o5=substring&amp;o9=substring&amp;query_format=advanced&amp;v2=kde%40&amp;v3=kde%40&amp;v4=kde%40&amp;v5=kde%40&amp;v9=kde%40&amp;human=1" shape="rect">open
-	bugs list</a>
-	grew to 24 this quarter.
-	It tends to hover around 20 items as new things come in
-	and old ones are resolved. We welcome detailed bug reports
-	and patches. KDE packaging updates are prepared in
-	a <a href="https://github.com/freebsd/freebsd-ports-kde/" shape="rect">copy
-	of the ports repository</a>
-	on GitHub and then merged in SVN. We welcome pull requests
-	there as well.</p>
-
-    <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p>
-      <p>The FreeBSD Ports Management Team, tasked with overseeing
-	the Ports Tree and
-	its committers, reports that the following events happened
-	during 2019Q3:</p>
-
-      <p>The number of ports grew to just under 38,000 during the
-	last quarter. We have
-	just over 2,000 open ports PRs, of which 400 are
-	unassigned. In this period,
-	169 committers made 7,340 commits to HEAD and 561 commits
-	to the quarterly
-	branch. This shows that the trend of last quarter of
-	increased activity is
-	continuing.</p>
-
-      <p>During the last quarter, we welcomed Santhosh Raju (fox@)
-	and Dmitri Goutnik
-	(dmgk@) to the team, and said goodbye to gabor@. During
-	the last quarter,
-	feld@ decided to step down from the portmgr@ and
-	ports-secteam@ teams. We
-	would like to thank them for their past services.</p>
-
-      <p>In the last three months, bapt@ put on his engineering hat
-	and released a new
-	version of pkg (1.12), added support for overlays to the
-	Ports Tree, fixed
-	two Make targets (deinstall-depends and reinstall), and
-	cleaned up
-	bsd.sites.mk.</p>
-
-      <p>On the infrastructure side, USES=pure became obsolete and
-	has therefore been
-	removed, and two new USES, xorg and xorg-cat have been
-	added and replace the
-	old bsd.xorg.mk. Two new keywords, ldconfig and
-	ldconfig-linux, were added to
-	simplify formatting of package lists.</p>
-
-      <p>A number of default versions changed: Lazarus to 2.0.4,
-	Linux to CentOS 7,
-	LLVM to 9.0, Perl to 5.30, PostgreSQL to 11, and Ruby to
-	2.6. Of the big
-	user-visible ports, Firefox got updated to 69.0.1,
-	Firefox-esr to 68.1.0,
-	Chromium to 76.0.3809.132, and Xfce to 4.14.</p>
-
-      <p>During the last quarter, antoine@ ran 48 exp-runs to test
-	package updates, test
-	updating bsd.java.mk, test the new ldconfig and
-	ldconfig-linux keywords, test
-	default version updates, test the new xorg and xorg-cat
-	USES, test base
-	updates, and test various improvements to Go and Ruby.</p>
-
-    <hr /><h2><a name="XFCE-4.14-update" href="#XFCE-4.14-update" id="XFCE-4.14-update">XFCE 4.14 update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://xfce.org/about/news/?post=1565568000" title="https://xfce.org/about/news/?post=1565568000">XFCE 4.14 announce</a></td><td>
-	    URL: <a href="https://xfce.org/about/news/?post=1565568000" title="XFCE 4.14 announce">https://xfce.org/about/news/?post=1565568000</a></td></tr></table><p>
-	Contact: Guido Falsi &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p>
-      <p>On September 19th the XFCE desktop environment ports have
-	been updated
-	to the recently released XFCE 4.14 version.</p>
-
-      <p>These updates include upgrades of all the main XFCE
-	components to the
-	latest versions which have been migrated to GTK3, with few
-	exceptions.
-	Base components still require and link to GTK2 in addition
-	to GTK3 to
-	allow older GTK2 XFCE applications, for example panel
-	plugins, to keep
-	working.</p>
-
-      <p>Due to this change the gtk-xfce-engine theme is deprecated
-	since it only
-	supports GTK2. The XFCE metaport by default installs the
-	greybird theme,
-	but it is not enabled by default.</p>
-
-      <p>This new version also includes now it's own
-	xfce4-screensaver program
-	which is installed by default.</p>
-
-      <p>Finally the default Display Manager on which XFCE depends
-	has been
-	changed to LightDM.</p>
-
-      <p>Some regressions were reported in bugzilla. In particular
-	the one
-	affecting most users is a regression in the window
-	manager: on specific
-	graphic display hardware the window manager fails to
-	properly draw
-	window decorations, which appear black and blocky on
-	affected systems.</p>
-
-      <p>This problem has also been reported in the upstream bug
-	tracker and a
-	solution is being sought.</p>
-
-      <p>If anyone is experiencing this display glitch and is able
-	to test,
-	please contact xfce@freebsd.org to help trying to figure
-	out a solution.</p>
-
-    <hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System" href="#ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System" id="ClonOS:-virtualization-platform-on-top-of-FreeBSD-Operating-System">ClonOS: virtualization platform on top of FreeBSD Operating System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://clonos.tekroutine.com/download.html" title="https://clonos.tekroutine.com/download.html">ClonOS 19.09</a></td><td>
-	    URL: <a href="https://clonos.tekroutine.com/download.html" title="ClonOS 19.09">https://clonos.tekroutine.com/download.html</a></td></tr><tr><td><a href="https://www.bsdstore.ru/" title="https://www.bsdstore.ru/">CBSD</a></td><td>
-	    URL: <a href="https://www.bsdstore.ru/" title="CBSD">https://www.bsdstore.ru/</a></td></tr></table><p>
-	Contact: Oleg Ginzburg &lt;<a href="mailto:olevole@olevole.ru">olevole@olevole.ru</a>&gt;
-	</p>
-      <h3>What is ClonOS?</h3>
-
-      <p>ClonOS is a turnkey open-source platform based on FreeBSD
-	and the CBSD
-	framework. ClonOS offers a complete web UI for an easy
-	control, deployment
-	and management of FreeBSD jails containers and bhyve/Xen
-	hypervisor virtual
-	environments.</p>
-
-      <p>ClonOS is currently the only available platforms which
-	allow both Xen and bhyve
-	hypervisors to coexist on the same host. Since ClonOS is a
-	FreeBSD-based
-	platform, it has the ability to create and manage jails
-	natively, allowing
-	you to run FreeBSD applications without losing
-	performance.</p>
-
-      <h3>ClonOS/CBSD 2019Q3 Status Report</h3>
-
-      <ul>
-	<li>Added support for cloud-init (Linux/BSD VMs) and
-	cloudbase-init
-	(Windows VMs). It gives the ability to use FreeBSD as IaaS
-	platform
-	for instant deployment and usage of virtual machines based
-	on bhyve
-	hypervisor.</li>
-
-	<li>Project started to use own cloud images for better
-	stability and
-      	resiliency.</li>
-
-	<li>New mirrors in France, US and Canada were added for
-      	distributing ISO/cloud-init images in addition to Russia,
-	Latvia and
-	Ukraine.</li>
-
-	<li>Now we're using Jenkins CI for testing regular ClonOS
-	builds:
-	<a href="https://jenkins.ircdriven.net/job/Update%20clonos%20packages./" shape="rect">Update
-	clonos packages</a> (Thanks to Daniel Shafer)</li>
-
-	<li>New pkg repository was deployed to support ClonOS
-	installation
-	from packages (at this moment only FreeBSD-12 packages are
-	available)
-	<a href="https://pkg.ircdriven.net/packages/12amd64-clonos/" shape="rect">ClonOS
-	package repo</a> (Thanks to Daniel Shafer)</li></ul>
-
-      <p>
-	Open issues and tasks:</p>
-
-      <ul>
-	<li>Volunteers, contributors and testers are urgently needed
-	to
-      	distribute ClonOS on FreeBSD environments.</li>
-
-	<li>We'd like to expand our mirrors number geographically,
-	your help and contribution will be much appriciated.</li>
-
-	<li>We're urgently looking for hosting sponsorship for various
-      developing and testing activities.</li></ul>
-
-    <hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Maciej Bielski &lt;<a href="mailto:mba@semihalf.com">mba@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p>
-      <p>ENA (Elastic Network Adapter) is the smart NIC available
-	in the
-	virtualized environment of Amazon Web Services (AWS). The
-	ENA
-	driver supports multiple transmit and receive queues and
-	can handle
-	up to 100 Gb/s of network traffic, depending on the
-	instance type
-	on which it is used.</p>
-
-      <p>ENAv2 has been under development for FreeBSD, similar to
-	Linux
-	and DPDK. Since the last update internal review and
-	improvements
-	of the patches were done, followed by validation on
-	various AWS
-	instances.</p>
-
-      <p>Completed since the last update:</p>
-
-      <ul>
-	<li>Verification and review of the NETMAP support</li>
-
-	<li>Mapping of the memory as WC on A1 instances in order to
-	enable LLQ mode</li>
-      </ul>
-
-      <p>
-	Todo:</p>
-
-      <ul>
-	<li>Upstream of NETMAP support</li>
-
-	<li>Upstream of the fix for LLQ mode on A1 instances</li>
-      </ul>
-
-      <p></p>
-
-    <sponsor>
-      Amazon.com Inc
-    </sponsor>
-
-    <hr /><h2><a name="Nomad-pot-driver---Orchestrating-jails-via-nomad" href="#Nomad-pot-driver---Orchestrating-jails-via-nomad" id="Nomad-pot-driver---Orchestrating-jails-via-nomad">Nomad pot driver - Orchestrating jails via nomad</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/trivago/nomad-pot-driver" title="https://github.com/trivago/nomad-pot-driver">Nomad pot driver</a></td><td>
-	    URL: <a href="https://github.com/trivago/nomad-pot-driver" title="Nomad pot driver">https://github.com/trivago/nomad-pot-driver</a></td></tr><tr><td><a href="https://github.com/pizzamig/pot" title="https://github.com/pizzamig/pot">Pot project</a></td><td>
-	    URL: <a href="https://github.com/pizzamig/pot" title="Pot project">https://github.com/pizzamig/pot</a></td></tr></table><p>
-	Contact: Luca Pizzamiglio &lt;<a href="mailto:pizzamig@FreeBSD.org">pizzamig@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Esteban Barrios &lt;<a href="mailto:esteban.barrios@trivago.com">esteban.barrios@trivago.com</a>&gt;
-	</p>
-      <p>An experimental project has started to provide jail
-	orchestration
-	based on <tt>nomad</tt> and the jail framework
-	<tt>pot</tt>, similarly to how
-	orchestration works with docker.</p>
-
-      <p>This model allows us to split the jail creation and the
-	jail deployment.
-	Jail images can be created and exported using the
-	<tt>pot</tt> framework.
-	The images can be deployed and orchestrated using
-	<tt>nomad</tt>.
-	A driver has been developed to allow <tt>nomad</tt> to
-	interact with <tt>pot</tt>.</p>
-
-      <p>One of the goals of this project is to use non-persistent
-	jails as
-	containers, allowing us to:</p>
-
-      <ul>
-	<li>define containers similar to Docker (but not identical,
-	because
-	the underlaying OS is different)</li>
-
-	<li>identify potential missing features in FreeBSD to support
-	such a computational model</li>
-      </ul>
-
-      <p>
-	In the next quarter, we will launch the first service
-	based on this
-	project.</p>
-
-      <p>Next steps are:</p>
-
-      <ul>
-	<li>provide more guides and howtos</li>
-
-	<li>improve stability, extending the tests suite</li>
-
-	<li>improving tooling to create/manage images</li>
-      </ul>
-
-      <p></p>
-
-    <p>This project was sponsored by trivago N.V..</p><hr /><h2><a name="sysctlinfo" href="#sysctlinfo" id="sysctlinfo">sysctlinfo</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/alfix/sysctlinfo" title="https://gitlab.com/alfix/sysctlinfo">gitlab.com/alfix/sysctlinfo</a></td><td>
-	    URL: <a href="https://gitlab.com/alfix/sysctlinfo" title="gitlab.com/alfix/sysctlinfo">https://gitlab.com/alfix/sysctlinfo</a></td></tr></table><p>
-	Contact: Alfonso Sabato Siciliano &lt;<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>&gt;
-	</p>
-      <p>The FreeBSD kernel maintains a Management Information Base
-	(MIB) where a
-	component (object) represents a parameter of the system.
-	The <i>sysctl</i> system
-	call explores the MIB to find an object by its Object
-	Identifier (OID) and
-	calls its handler to get or set the value of the
-	parameter. It is often
-	necessary to find an object not to call its handler but to
-	get its info
-	(description, type, name, next object, etc.), so the
-	kernel provides an
-	undocumented interface implemented in kern_sysctl.c.</p>
-
-      <p>sysctlinfo is a new interface to explore the sysctl MIB
-	and to pass the info
-	of an object to the userland. The project provides: a
-	README, a manual, helper
-	macros, examples, tests and converted tools.</p>
-
-      <p>Primarily sysctlinfo provides a new set of sysctl nodes
-	(corresponding to the
-	kernel interface) to handle an object up to CTL_MAXNAME
-	levels:
-	sysctl.entryfakename, sysctl.entrydesc, sysctl.entrylabel,
-	sysctl.entrykind,
-	sysctl.entryfmt and sysctl.entrynextleaf. Moreover new
-	features have been
-	implemented: the support for the capability mode,
-	sysctl.entryname,
-	sysctl.entryidbyname and sysctl.entrynextnode. To get all
-	the info about an
-	object the kernel needs to find it many times, then the
-	new
-	sysctl.entryallinfo* nodes were written, they are 30%
-	more efficient. Finally,
-	*byname nodes were added: they search the object by its
-	name avoiding to call
-	sysctl.name2oid (or similar) to explore the MIB just to
-	find the corresponding
-	OID.</p>
-
-      <p>sysctlinfo can be installed via <i>sysutils/sysctlinfo-kmod</i>
-	or by applying the
-	<i>sysctlinfo.diff</i> patch (more efficient than the module
-	because uses a shared
-	lock). The interface is used by <i>deskutils/sysctlview
-	1.5</i>,
-	<i>sysutils/nsysctl 1.2</i> and the converted version of
-	sysctl(8), sysctlbyname(3),
-	sysctlnametomib(3), they should be used to get the value
-	of an object with 23/24
-	levels or if some level-name has only the '\0' character.
-	In the future a new
-	<i>byname</i> node will be added to allow sysctlbyname() to
-	manage a CTLTYPE_NODE with
-	a no-NULL handler, example
-	sysctlbyname("kern.proc.pid.\&lt;pid\&gt;").</p>
-
-    <hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2019-10-2019-12.html b/website/content/en/status/report-2019-10-2019-12.html
deleted file mode 100644
index b52580a05d..0000000000
--- a/website/content/en/status/report-2019-10-2019-12.html
+++ /dev/null
@@ -1,1620 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Here is the last quarterly status report for 2019. As you
-	might remember
-	from last report, we changed our timeline: now we collect
-	reports the last
-	month of each quarter and we edit and publish the full
-	document the next
-	month. Thus, we cover here the period October 2019 -
-	December 2019.</p><p>If you thought that the FreeBSD community was less active
-	in the
-	Christmas' quarter you will be glad to be proven wrong: a
-	quick glance at
-	the summary will be sufficient to see that much work has
-	been done in the
-	last months.</p><p>Have a nice read!</p><p>-- Lorenzo Salvadore</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Cluster-Administration-Team">Cluster Administration Team</a></li><li><a href="#Continuous-Integration">Continuous Integration</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#IPSec-Extended-Sequence-Number-(ESN)-support">IPSec Extended Sequence Number (ESN) support</a></li><li><a href="#NFS-Version-4.2-implementation">NFS Version 4.2 implementation</a></li><li><a href="#DTS-Update">DTS Update</a></li><li><a href="#RockChip-Support">RockChip Support</a></li><li><a href="#Creating-virtual-FreeBSD-appliances-from-RE-VMDK-images">Creating virtual FreeBSD appliances from RE VMDK images</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#SoC-audio-framework-and-RK3399-audio-drivers">SoC audio framework and RK3399 audio drivers</a></li><li><a href="#FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></li><li><a href="#FreeBSD-on-EC2-ARM64">FreeBSD on EC2 ARM64</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#PowerPC-on-Clang">PowerPC on Clang</a></li><li><a href="#NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Linux-compatibility-layer-update">Linux compatibility layer update</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Java-on-FreeBSD">Java on FreeBSD</a></li><li><a href="#Electron-and-VSCode">Electron and VSCode</a></li><li><a href="#Bastille">Bastille</a></li><li><a href="#Universal-Packaging-Tool-(upt)">Universal Packaging Tool (upt)</a></li><li><a href="#Wine-on-FreeBSD">Wine on FreeBSD</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#sysctlbyname-improved">sysctlbyname-improved</a></li><li><a href="#pot-and-the-nomad-pot-driver">pot and the nomad pot driver</a></li><li><a href="#7-Days-Challenge">7 Days Challenge</a></li><li><a href="#NomadBSD">NomadBSD</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-        Page</a>.</p><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Core Team is the governing body of FreeBSD.</p>
-<ul><li>Julie Saravanos, the sister of Bruce D. Evans (bde),
-	mailed core with the sad
-	news that Bruce passed away on 2019-12-18 at the age of 68
-	years. Bruce was a
-	deeply respected member of the community, served on the
-	Core team, and made
-	over 5,000 commits. Bruce's impact on our culture was so
-	profound that new
-	terminology was spawned. This is an excerpt of a message
-	from Poul-Henning
-	Kamp to Julie.
-<blockquote>
-<p>
-	I don't know precisely when I first communicated with
-	Bruce, it was in the
-	late 1980'ies via "UseNET", but I can say with certainty
-	that few people
-	have inspired me more, or improved my programming more,
-	than Bruce he did
-	over the next half of my life.</p>
-<p>All large projects invent its own vocabulary and in
-	FreeBSD two of the
-	neologisms are "Brucification", and "Brucified".</p>
-<p>A "brucification" meant receiving a short, courteous note
-	pointing out a
-	sometimes subtle deficiency, or an overlooked detail in a
-	source code
-	change. Not necessarily a serious problem, possibly not
-	even a problem to
-	anybody at all, but nonetheless something which was wrong
-	and ought to be
-	fixed. It was not uncommon for the critique to be
-	considerably longer
-	than the change in question.</p>
-<p>If one ignored brucifications one ran the risk of being
-	"brucified", which
-	meant receiving a long and painstakingly detailed list of
-	every single one
-	of the errors, mistakes, typos, shortcomings, bad
-	decisions, questionable
-	choices, style transgressions and general sloppiness of
-	thinking, often
-	expressed with deadpan humor sharpened to a near-fatal
-	point.</p>
-<p>The most frustrating thing was that Bruce would be
-	perfectly justified and
-	correct. I can only recall one or two cases where I were
-	able to respond
-	"Sorry Bruce, but you're wrong there..." - and I confess
-	that on those
-	rare days I felt like I should cut a notch in my keyboard.</p>
-<p>The last email we received from Bruce is a good example of
-	the depth of
-	knowledge and insight he provided for the project:</p>
-<p>
-	https://docs.freebsd.org/cgi/getmsg.cgi?fetch=1163414+0+archive/2019/svn-src-all/20191027.svn-src-all</p>
-</blockquote>
-</li>
-<li>The 12.1 release was dedicated to another FreeBSD
-	developer who passed away in
-	the fourth quarter of 2019, Kurt Lidl. The FreeBSD
-	Foundation has a memorial
-	page to Kurt.
-<p>
-
-	https://www.freebsdfoundation.org/blog/in-memory-of-kurt-lidl/</p>
-<p>We send our condolences to both the families of Bruce and
-	Kurt.</p></li>
-<li>Core has documented The Project's policy on support tiers.
-<p>
-
-	https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/archs.html</p></li>
-<li>Core approved a source commit bit for James Clarke. Brooks
-	Davis (brooks)
-	will mentor James and John Baldwin (jhb) will co-mentor. </li>
-<li>The Project's first Season of Docs ended with a negative
-	result. The work was
-	not completed and contact could not be established with
-	the writer. No
-	payment was made and the financing was set aside for
-	future work. </li>
-<li>Google Summer of Code completed. Information about the
-	seven accepted
-	projects can be found on the wiki page.
-<p>
-	https://wiki.freebsd.org/SummerOfCode2019Projects</p></li>
-<li>Adam Weinberger (adamw) was added to conduct@. Adam has
-	demonstrated
-	competence, understanding, and fairness in personal
-	matters. </li>
-<li>Li-Wen Hsu (lwhsu) contacted Core after receiving a report
-	from concerned
-	local community members about past updates to The
-	Project's
-	internationalization policy. Lengthy discussions took
-	place to determine how
-	to reaffirm that The Project maintains a neutral position
-	in political
-	disputes. Updates were made to the document and it was
-	decided that any
-	future changes would require explicit Core approval.
-<p>
-	https://www.freebsd.org/internal/i18n.html</p></li>
-<li>After nomination by Edward Napiera&#322;a (trasz), core voted
-	to grant Daniel
-	Ebdrup (debdrup) and Lorenzo Salvadore (salvadore)
-	membership in The Project.
-	Both Daniel and Lorenzo have been working on the quarterly
-	reports for the
-	past few quarters. </li>
-<li>The Core-initiated Git Transition Working Group continued
-	to meet over the
-	last quarter of 2019. Their report is still forthcoming. </li></ul>
-<hr /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p><p>The FreeBSD Foundation is a 501(c)(3) non-profit
-	organization dedicated to
-	supporting and promoting the FreeBSD Project and community
-	worldwide. Funding
-	comes from individual and corporate donations and is used
-	to fund and manage
-	software development projects, conferences and developer
-	summits, and provide
-	travel grants to FreeBSD contributors. The Foundation
-	purchases and supports
-	hardware to improve and maintain FreeBSD infrastructure
-	and provides resources
-	to improve security, quality assurance, and release
-	engineering efforts;
-	publishes marketing material to promote, educate, and
-	advocate for the FreeBSD
-	Project; facilitates collaboration between commercial
-	vendors and FreeBSD
-	developers; and finally, represents the FreeBSD Project in
-	executing contracts,
-	license agreements, and other legal arrangements that
-	require a recognized
-	legal entity.</p>
-<p>Here are some highlights of what we did to help FreeBSD
-	last quarter:</p>
-<h3>Partnerships and Commercial User Support</h3>
-<p>We help facilitate collaboration between commercial users
-	and FreeBSD
-	developers. We also meet with companies to discuss their
-	needs and bring that
-	information back to the Project. In Q4, Ed Maste and Deb
-	Goodkin met with a
-	few commercial users in the US. It's not only beneficial
-	for the above, but it
-	also helps us understand some of the applications where
-	FreeBSD is used. We
-	were also able to meet with a good number of commercial
-	users at the Bay Area
-	Vendor/Developer Summit and Open Source Summit Europe.
-	These venues provide an
-	excellent opportunity to meet with commercial and
-	individual users and
-	contributors to FreeBSD.</p>
-<h3>Fundraising Efforts</h3>
-<p>In 2019, we focused on supporting a few key areas where
-	the Project needed the
-	most help. The first area was software development.
-	Whether it was contracting
-	FreeBSD developers to work on projects like wifi support,
-	to providing internal
-	staff to quickly implement hardware workarounds, we've
-	stepped in to help keep
-	FreeBSD innovative, secure, and reliable. Software
-	development includes
-	supporting the tools and infrastructure that make the
-	development process go
-	smoothly, and we're on it with team members heading up the
-	Continuous
-	Integration efforts, and actively involved in the
-	clusteradmin and security
-	teams.</p>
-<p>Our advocacy efforts focused on recruiting new users and
-	contributors to the
-	Project. We attended and participated in 38 conferences
-	and events in 21
-	countries. From giving FreeBSD presentations and workshops
-	to staffing tables,
-	we were able to have 1:1 conversations with thousands of
-	attendees.</p>
-<p>Our travels also provided opportunities to talk directly
-	with FreeBSD
-	commercial and individual users, contributors, and future
-	FreeBSD
-	users/contributors. We've seen an increase in use and
-	interest in FreeBSD from
-	all of these organizations and individuals. These meetings
-	give us a chance to
-	learn more about what organizations need and what they and
-	other individuals
-	are working on. The information helps inform the work we
-	should fund.</p>
-<p>In 2019, your donations helped us continue our efforts of
-	supporting critical
-	areas of FreeBSD such as:</p>
-<ul><li>Operating System Improvements: Providing staff to
-	immediately respond to
-	urgent problems and implement new features and
-	functionality allowing for
-	the innovation and stability you've come to rely on. </li>
-<li>Improving and increasing test coverage, continuous
-	integration, and automated
-	testing with a full-time software engineer to ensure you
-	receive the highest
-	quality, secure, and reliable operating system. </li>
-<li>Security: Providing engineering resources to bolster the
-	capacity and
-	responsiveness of the Security team providing you with
-	peace of mind when
-	security issues arise. </li>
-<li>Growing the number of FreeBSD contributors and users from
-	our global FreeBSD
-	outreach and advocacy efforts, including expanding into
-	regions such as
-	China, India, Africa, and Singapore. </li>
-<li>Offering FreeBSD workshops and presentations at more
-	conferences, meetups,
-	and universities around the world. </li>
-<li>Providing opportunities such as developer and vendor
-	summits and company
-	visits to help facilitate collaboration between commercial
-	users and FreeBSD
-	developers, as well as helping to get changes pushed into
-	the FreeBSD source
-	tree, and creating a bigger and healthier ecosystem. </li></ul>
-<p>
-	We've accomplished a lot this year, but we are still only
-	a small 501(c)3
-	organization focused on supporting FreeBSD and not a trade
-	organization like
-	many other open source Foundations.</p>
-<p>Please consider <a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">making
-	a donation</a>
-	at https://www.FreeBSDfoundation.org/donate/ to help us
-	continue and increase
-	our support for FreeBSD.</p>
-<p>We also have the Partnership Program, to provide more
-	benefits for our larger
-	commercial donors.
-	Find out more information at
-
-	https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/
-	and share with your companies!</p>
-<h3>OS Improvements</h3>
-<p>The Foundation supports software development projects to
-	improve FreeBSD
-	through our full time technical staff, contractors, and
-	project grant
-	recipients. They maintain and improve critical kernel
-	subsystems, add new
-	features and functionality, and fix bugs.</p>
-<p>Between October and December there were 236 commits to the
-	FreeBSD source
-	repository tagged with FreeBSD Foundation sponsorship.
-	This is about 10%
-	of all commits during this period. Some of these projects
-	have their own
-	entries in the quarterly report, and are not repeated
-	here, while others
-	are briefly described below.</p>
-<p>As usual, Foundation staff member Konstantin Belousov
-	committed a large
-	number of UFS, NFS, tmpfs, VM system, and low-level Intel
-	x86 bug fixes and
-	improvements. Kostik also committed improvements to the
-	run-time linker
-	(rtld), and participated in very many code reviews,
-	helping to get changes
-	from other developers integrated into the tree.</p>
-<p>Following on from his work to improve debugging tools in
-	the Linuxulator
-	environment, Edward Napiera&#322;a integrated the Linux Test
-	Project (LTP) with
-	FreeBSD's CI system, and committed a number of small bug
-	fixes to the
-	Linuxulator itself.</p>
-<p>Mark Johnston continued working on infrastructure for the
-	Syzkaller system
-	call fuzzing tool, and committed fixes for many issues
-	identified by it.
-	Mark committed improvements to RISC-V infrastructure, the
-	network stack,
-	performance and locking, and x86 pmap.</p>
-<p>Mark also added support for newer Intel WiFi chipsets to
-	the iwm driver,
-	enabling WiFi support for the Lenovo X1 Carbon 7th
-	generation, and other
-	contemporary laptops.</p>
-<p>Ed Maste committed a number of improvements and cleanups
-	in build
-	infrastructure, vt console fixes including issues with
-	keyboard maps,
-	some blacklistd updates, documentation updates, and other
-	small changes.
-	Ed also committed some work to prepare for the removal of
-	GCC 4.2.1 from
-	the FreeBSD source tree, currently planned for Q1 2020.</p>
-<h3>Continuous Integration and Quality Assurance</h3>
-<p>The Foundation provides a full-time staff member who is
-	working on improving
-	our automated testing, continuous integration, and overall
-	quality assurance
-	efforts.</p>
-<p>During the fourth quarter of 2019, Foundation staff
-	continued to improve the
-	project's CI infrastructure, worked with contributors to
-	fix the failing build
-	and test cases. We worked with other teams in the project
-	for their testing
-	needs and also worked with many external projects and
-	companies to improve
-	their support of FreeBSD. We added several new CI jobs and
-	brought the
-	<a href="https://ci.freebsd.org/hwlab" shape="rect">FreeBSD Hardware
-	Testing Lab</a> online.</p>
-<p>We published
-	<a href="https://www.freebsdfoundation.org/blog/2019-in-review-ci-and-testing-advancements/" shape="rect">2019
-	in Review: CI and Testing Advancements</a>
-	on the Foundation's blog.</p>
-<p>See the FreeBSD CI section of this report for completed
-	work items and detailed
-	information.</p>
-<h3>Supporting FreeBSD Infrastructure</h3>
-<p>The Foundation provides hardware and support to improve
-	the FreeBSD
-	infrastructure. Last quarter, we continued supporting
-	FreeBSD hardware located
-	around the world.</p>
-<h3>FreeBSD Advocacy and Education</h3>
-<p>A large part of our efforts are dedicated to advocating
-	for the Project. This
-	includes promoting work being done by others with FreeBSD;
-	producing advocacy
-	literature to teach people about FreeBSD and help make the
-	path to starting
-	using FreeBSD or contributing to the Project easier; and
-	attending and helping
-	other FreeBSD contributors volunteer to run FreeBSD
-	events, staff FreeBSD
-	tables, and give FreeBSD presentations.</p>
-<p>The FreeBSD Foundation sponsors many conferences, events,
-	and summits around the globe. These events can be
-	BSD-related, open source, or technology events
-	geared towards underrepresented groups. We support
-	the FreeBSD-focused events to help provide a venue
-	for sharing knowledge, to work together on
-	projects, and to facilitate collaboration between
-	developers and commercial users. This all helps
-	provide a healthy ecosystem. We support the
-	non-FreeBSD events to promote and raise awareness
-	of FreeBSD, to increase the use of FreeBSD in
-	different applications, and to recruit more
-	contributors to the Project.</p>
-<p>
-	Check out some of the advocacy and education work we did
-	last quarter:</p>
-<ul><li>Organized the 2019 Bay Area FreeBSD Vendor and Developers
-	Summit
-	in Santa Clara, CA</li>
-<li>Presented at COSCON '19 in Shanghai, China</li>
-<li>Represented FreeBSD at All Things Open 2019, in Raleigh,
-	North Carolina</li>
-<li>Industry Partner Sponsor for LISA '19 in Portland, OR</li>
-<li>Silver Sponsor of OpenZFS in San Francisco, CA</li>
-<li>Gave a technical presentation at School of Mines in
-	Golden, CO</li>
-<li>Presenting and representing FreeBSD at Seagl, in Seattle,
-	WA</li>
-<li>Presented at Open Source Summit Europe in Lyon France</li>
-<li>Committed to sponsoring LinuxConfAu 2020, in Gold Coast,
-	Australia in
-	addition to holding a FreeBSD Mini-Conf</li>
-<li>Accepted to present at the BSD Dev Room at FOSDEM '20, in
-	Brussels, Belgium</li>
-<li>Accepted to have a stand at FOSDEM '20, in Brussels,
-	Belgium</li>
-<li>Committed to sponsoring FOSSASIA 2020, in Singapore</li>
-<li>Committed to hold FreeBSD Day at SCALE 18x, in Pasadena,
-	CA </li></ul>
-<p>
-	We continued producing FreeBSD advocacy material to help
-	people promote
-	FreeBSD. Learn more about our efforts in 2019 to advocate
-	for FreeBSD:
-
-	https://www.freebsdfoundation.org/blog/2019-in-review-advocacy/</p>
-<p>Our Faces of FreeBSD series is back. Check out the latest
-	post: Mahdi Mokhtari.
-
-	https://www.freebsdfoundation.org/blog/faces-of-freebsd-2019-mahdi-mokhtari/</p>
-<p>Read more about our conference adventures in the
-	conference recaps and trip
-	reports in our monthly newsletters:
-
-	https://www.freebsdfoundation.org/news-and-events/newsletter/</p>
-<p>We help educate the world about FreeBSD by publishing the
-	professionally
-	produced FreeBSD Journal. As we mentioned previously, the
-	FreeBSD Journal is
-	now a free publication. Find out more and access the
-	latest issues at
-	https://www.FreeBSDfoundation.org/journal/.</p>
-<p>You can find out more about events we attended and
-	upcoming events at
-	https://www.FreeBSDfoundation.org/news-and-events/.</p>
-<p>We have continued our work with a new website developer to
-	help us improve our
-	website. Work has begun to make it easier for community
-	members to find
-	information more easily and to make the site more
-	efficient.</p>
-<h3>Legal/FreeBSD IP</h3>
-<p>The Foundation owns the FreeBSD trademarks, and it is our
-	responsibility to
-	protect them. We also provide legal support for the core
-	team to investigate
-	questions that arise.</p>
-<p>Go to http://www.FreeBSDfoundation.org to find out how we
-	support FreeBSD and
-	how we can help you!</p>
-<hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/12.1R/schedule.html" title="https://www.freebsd.org/releases/12.1R/schedule.html">FreeBSD 12.1-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/12.1R/schedule.html" title="FreeBSD 12.1-RELEASE schedule">https://www.freebsd.org/releases/12.1R/schedule.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/12.1R/announce.html" title="https://www.freebsd.org/releases/12.1R/announce.html">FreeBSD 12.1-RELEASE announcement</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/12.1R/announce.html" title="FreeBSD 12.1-RELEASE announcement">https://www.freebsd.org/releases/12.1R/announce.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Release Engineering Team is responsible for
-	setting
-	and publishing release schedules for official project
-	releases
-	of FreeBSD, announcing code freezes and maintaining the
-	respective branches, among other things.</p>
-<p>The FreeBSD Release Engineering Team continued work on the
-	12.1-RELEASE, which
-	started September 6th. This release cycle was the first
-	"freeze-less" release
-	from the Subversion repository, and the test bed for
-	eliminating the requirement
-	of a hard code freeze on development branches.</p>
-<p>The 12.1-RELEASE cycle concluded with the final build
-	beginning November 4th,
-	preceded by three BETA builds and two RC builds. The RC3
-	build had been
-	included in the original schedule, but had been decided to
-	not be required.</p>
-<p>Additionally throughout the quarter, several development
-	snapshots builds
-	were released for the <i>head</i>,
-	<i>stable/12</i>, and
-	<i>stable/11</i> branches.</p>
-<p>Much of this work was sponsored by Rubicon Communications,
-	LLC (netgate.com)
-	and the FreeBSD Foundation.</p>
-<hr /><h2><a name="Cluster-Administration-Team" href="#Cluster-Administration-Team" id="Cluster-Administration-Team">Cluster Administration Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/administration.html#t-clusteradm" title="https://www.freebsd.org/administration.html#t-clusteradm">Cluster Administration Team members</a></td><td>
-	    URL: <a href="https://www.freebsd.org/administration.html#t-clusteradm" title="Cluster Administration Team members">https://www.freebsd.org/administration.html#t-clusteradm</a></td></tr></table><p>
-	Contact: Cluster Administration Team &lt;<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Cluster Administration Team consists of the
-	people responsible for administering the machines
-	that the Project relies on for its distributed
-	work and communications to be synchronised. In
-	this quarter, the team has worked on the
-	following:</p>
-<ul><li>Upgrade ref11-{amd64,i386}.freebsd.org to 11.3-STABLE
-	r353313</li>
-<li>Ongoing systems administration work:</li>
-<li>Creating accounts for new committers.</li>
-<li>Backups of critical infrastructure.</li>
-<li>Keeping up with security updates in 3rd party software. </li></ul>
-<p>
-	Work in progress:</p>
-<ul><li>Review the service jails and service administrators
-	operation.</li>
-<li>South Africa Mirror (JINX) in progress.</li>
-<li>NVME issues on PowerPC64 Power9 blocking dual socket
-	machine from being used as pkg builder.</li>
-<li>Drive upgrade test for pkg builders (SSDs) courtesy of the
-	FreeBSD Foundation.</li>
-<li>Boot issues with Aarch64 reference machines.</li>
-<li>New NYI.net sponsored colocation space in Chicago-land
-	area.</li>
-<li>Setup new host for CI staging environment.</li>
-<li>Plan how to add new semi-official pkg mirrors </li></ul>
-<hr /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://ci.FreeBSD.org/hwlab" title="https://ci.FreeBSD.org/hwlab">FreeBSD Hardware Testing Lab</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org/hwlab" title="FreeBSD Hardware Testing Lab">https://ci.FreeBSD.org/hwlab</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org" title="https://artifact.ci.FreeBSD.org">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org</a></td></tr><tr><td><a href="https://hackmd.io/@FreeBSD-CI" title="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackmd.io/@FreeBSD-CI" title="FreeBSD CI weekly report">https://hackmd.io/@FreeBSD-CI</a></td></tr><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
-	    URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="https://wiki.freebsd.org/3rdPartySoftwareCI">3rd Party Software CI</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="3rd Party Software CI">https://wiki.freebsd.org/3rdPartySoftwareCI</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="FreeBSD CI Repository">https://github.com/freebsd/freebsd-ci</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD CI team maintains continuous integration
-	system and related tasks
-	for the FreeBSD project. The CI system regularly checks
-	the committed changes
-	can be successfully built, then performs various tests and
-	analysis of the
-	results. The results from build jobs are archived in an
-	artifact server, for
-	the further testing and debugging needs. The CI team
-	members examine the
-	failing builds and unstable tests, and work with the
-	experts in that area to
-	fix the code or adjust test infrastructure. The details
-	are of these efforts
-	are available in the <a href="https://hackmd.io/@FreeBSD-CI" shape="rect">weekly CI
-	reports</a>.</p>
-<p>During the fourth quarter of 2019, we worked with the
-	contributors and
-	developers in the project for their testing needs and also
-	worked with many
-	external projects and companies to improve their support
-	of FreeBSD. The
-	<a href="https://ci.freebsd.org/hwlab" shape="rect">FreeBSD Hardware
-	Testing Lab</a> is online in this
-	quarter. It's still in work in progress stage and we are
-	merging the different
-	versions and will integrate more tightly to the main CI
-	server. We are also
-	working on make this work more easierly to be reproduced.</p>
-<p>Work in progress:</p>
-<ul><li>Collecting and sorting CI tasks and ideas at
-	https://hackmd.io/bWCGgdDFTTK_FG0X7J1Vmg</li>
-<li>Setup the CI stage environment and put the experimental
-	jobs on it</li>
-<li>Implementing automatic tests on bare metal hardware</li>
-<li>Adding drm ports building test against -CURRENT</li>
-<li>Testing and merging pull requests at
-	https://github.com/freebsd/freebsd-ci/pulls</li>
-<li>Planning for running ztest and network stack tests</li>
-<li>Helping more 3rd software get CI on FreeBSD through a
-	hosted CI solution</li>
-<li>Adding LTP test jobs.</li>
-<li>Adding non-x86 test jobs.</li>
-<li>Adding external toolchin related jobs. </li></ul>
-<p>
-	Please see freebsd-testing@ related tickets for more WIP
-	information.</p>
-<p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="IPSec-Extended-Sequence-Number-(ESN)-support" href="#IPSec-Extended-Sequence-Number-(ESN)-support" id="IPSec-Extended-Sequence-Number-(ESN)-support">IPSec Extended Sequence Number (ESN) support</a></h2><p>
-	Contact: Patryk Duda &lt;<a href="mailto:pdk@semihalf.com">pdk@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p><p>Extended Sequence Number (ESN) is IPSec extension defined
-	in <a href="https://tools.ietf.org/html/rfc4303#section-2.2.1" shape="rect">RFC4303
-	Section 2.2.1</a>.
-	It makes possible to implement high-speed IPSec
-	implementations where standard, 32-bit sequence
-	number is not sufficent.
-	Key feature of the ESN is that only low order 32 bits of
-	sequence number are transmitted over the wire.
-	High-order 32 bits are maintained by sender and receiver.
-	Additionally high-order bits are included in the
-	computation of Integrity Check Value (ICV) field.</p>
-<p>Extended Sequence Number support contains following:</p>
-<ul><li>Modification of existing anti-replay algorithm to fulfil
-	ESN requirements</li>
-<li>Trigger soft lifetime expiration at 80% of UINT32_MAX
-	when ESN is disabled</li>
-<li>Implement support for including ESN into ICV in cryptosoft
-	engine in both
-	encrypt and authenticate mode (eg. AES-CBC and SHA256
-	HMAC) and combined
-	mode (eg. AES-GCM)</li>
-<li>Implement support for including ESN into ICV in AES-NI
-	engine in both
-	encrypt and authenticate mode and combined mode </li></ul>
-<p>
-	Remaining work:</p>
-<ul><li>Upstream patches of the anti-replay algorithm</li>
-<li>Adjust implementation of crypto part after the reworked
-	Open Crypto Framework gets stable </li></ul>
-<p></p>
-<p>This project was sponsored by Stormshield.</p><hr /><h2><a name="NFS-Version-4.2-implementation" href="#NFS-Version-4.2-implementation" id="NFS-Version-4.2-implementation">NFS Version 4.2 implementation</a></h2><p>
-	Contact: Rick Macklem &lt;<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>&gt;
-	</p><p>RFC-7862 describes a new minor revision to the NFS Version
-	4 protocol.
-	This project implements this new minor revision.</p>
-<p>The NFS Version 4 Minorversion 2 protocol adds several
-	optional
-	features to NFS, such as support for SEEK_DATA/SEEK_HOLE,
-	file
-	copying done on the server that avoids data transfer over
-	the wire
-	and support for posix_fallocate(), posix_fadvise().
-	Hopefully these features can improve performance for
-	certain applications.</p>
-<p>This project has basically been completed. The code
-	changes have now
-	all been committed to head/current and should be released
-	in FreeBSD 13.</p>
-<p>Testing by others would be appreciated. To do testing, an
-	up to date
-	head/current system is required. Client mounts need the
-	"minorversion=2" mount option to enable this protocol.
-	The NFS server will have NFSv4.2 enabled by default.</p>
-<hr /><h2><a name="DTS-Update" href="#DTS-Update" id="DTS-Update">DTS Update</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p><p>DTS files (Device Tree Sources) were updated to be on par
-	with Linux 5.4 for
-	HEAD and 5.2 for the 12-STABLE branch.
-	The DTS for the RISC-V architecture are now imported as
-	well.</p>
-<hr /><h2><a name="RockChip-Support" href="#RockChip-Support" id="RockChip-Support">RockChip Support</a></h2><p>
-	Contact:  &lt;<a href="mailto:freebsd-arm@FreeBSD.Org">freebsd-arm@FreeBSD.Org</a>&gt;
-	<br />
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.Org">manu@FreeBSD.Org</a>&gt;
-	<br />
-	Contact: Michal Meloun &lt;<a href="mailto:mmel@FreeBSD.Org">mmel@FreeBSD.Org</a>&gt;
-	</p><p>RockChip RK3399 now has USB3 support, some configuration
-	such as device mode
-	are still not supported however host mode should work on
-	any board.</p>
-<p>Support for SPI has been committed which enables ability
-	to interact with SPI
-	flash if present.</p>
-<p>All regulators for the RK808 PMIC (Power Management IC)
-	have been added.</p>
-<p>All clocks are now supported which completes clock and
-	reset implementation,
-	previously only clocks from devices with drivers were
-	supported.</p>
-<p>The TS-ADC (Temperature Sensor ADC) is now supported, this
-	adds the ability
-	to read temperature of the CPU and GPU via sysctl
-	hw.temperature .</p>
-<p>Initial PCIe support has been committed and verified
-	working on several
-	different boards.
-	Known working devices are NVMe devices and PCIe cards that
-	doesn't utilize PCIe
-	switching or bridge functionality.</p>
-<p>Card Detection for SDCard on RK3328 and RK3399 is now
-	supported. There is still
-	some problems if the board is using a GPIO for CD instead
-	of the internal detection
-	mechanism.</p>
-<hr /><h2><a name="Creating-virtual-FreeBSD-appliances-from-RE-VMDK-images" href="#Creating-virtual-FreeBSD-appliances-from-RE-VMDK-images" id="Creating-virtual-FreeBSD-appliances-from-RE-VMDK-images">Creating virtual FreeBSD appliances from RE VMDK images</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/freebsd-mkova" title="https://github.com/gonzoua/freebsd-mkova">freebsd-mkova</a></td><td>
-	    URL: <a href="https://github.com/gonzoua/freebsd-mkova" title="freebsd-mkova">https://github.com/gonzoua/freebsd-mkova</a></td></tr></table><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p><p>OVA is a file format for packaging and distributing
-	virtual appliances: pre-configured virtual machine
-	images. Virtual appliance file contains full VM
-	information like the number of CPUs, amount of
-	memory, list of virtual devices, it also includes
-	disk images. Applications like VirtualBox or
-	VMWare can import OVA files; this process can be
-	easily automated.</p>
-<p>freebsd-mkova is a CLI tool to create OVA files using VMDK
-	images provided by FreeBSD RE. For now, only a
-	limited set of attributes can be specified: VM
-	name, number of CPU, amount of memory, and disk
-	size. The tool also does only cursory sanity
-	checks on the VMDK file format, assuming it's a
-	monolithic sparse file and that it has to be
-	converted to the stream-optimized format. The
-	script can be extended to make hardware
-	configuration more flexible and VMDK parser more
-	robust.</p>
-<hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><h2><a name="SoC-audio-framework-and-RK3399-audio-drivers" href="#SoC-audio-framework-and-RK3399-audio-drivers" id="SoC-audio-framework-and-RK3399-audio-drivers">SoC audio framework and RK3399 audio drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/freebsd/tree/rk3399_audio" title="https://github.com/gonzoua/freebsd/tree/rk3399_audio">rk3399_audio</a></td><td>
-	    URL: <a href="https://github.com/gonzoua/freebsd/tree/rk3399_audio" title="rk3399_audio">https://github.com/gonzoua/freebsd/tree/rk3399_audio</a></td></tr></table><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p><p>Most modern SoCs and devboards have audio support in one
-	form or another, but it's one of the areas that
-	are overlooked by FreeBSD driver developers. The
-	most common architecture for the audio pipeline on
-	a single-board computer consists of two DAIs
-	(digital audio interfaces): CPU and codec,
-	connected by a serial bus.</p>
-<p>CPU DAI is a SoC IP block that operates with samples:
-	obtains them from the driver for playback or
-	provides them to the driver for recording through
-	FIFOs or DMA requests. Audio samples leave (or
-	arrive at) the SoC through a serial bus, usually
-	I2S, that is connected to Codec DAI.</p>
-<p>Codec DAI is an external (to the SoC) chip that packs one
-	or more DAC/ADC blocks along with mixers,
-	amplifiers, and probably more specialized devices
-	like filters and/or sound effects. The analog part
-	of the codec is connected to
-	microphones/headphones/speakers. On SBCs, the
-	codec usually communicates with SoC through two
-	interfaces: data path, over which audio samples
-	travel, and a control interface that is used to
-	read/write chip registers and configure its
-	behavior. The most common choices for these are
-	I2S and I2C buses, respectively.</p>
-<p>For FDT-enabled devices, an audio pipeline is described as
-	a virtual DTB node that has links to the CPU and
-	codec device(s), and which specifies the data
-	format, and clock details that both the CPU and
-	the codec chips would use. It also may have more
-	than one CPU/codec pair.</p>
-<p>Using Firefly-RK3399 as a test device, I was able to
-	implement I2S driver for RK3399 SoC (PIO mode,
-	playback only), the driver for Realtek's RT5640
-	chip (headphones playback only + mixer controls)
-	and a base outline of SoC audio framework. Some
-	bits of <tt>rk_i2s</tt> and the framework were
-	ported from the NetBSD code developed by Jared
-	McNeill. On my WIP branch, I can play mp3 audio
-	and control playback volume.</p>
-<p>The primary missing functionalities at the moment are
-	recording support, multi-link audio cards, DMA
-	support. The most critical among these is DMA
-	support. In the current implementation, all buffer
-	management is placed at the ausoc layer, which is
-	not going to work for DMA, because only the CPU
-	DAI driver would know about the memory constraints
-	and access mechanisms. The current state of RK3399
-	support does not allow to implement DMA transfers
-	for <tt>rk_i2s</tt> easily, but I plan to look
-	into this right after adding recording support,
-	which should not be a lot of work.</p>
-<hr /><h2><a name="FreeBSD-on-Microsoft-HyperV-and-Azure" href="#FreeBSD-on-Microsoft-HyperV-and-Azure" id="FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/MicrosoftAzure" title="https://wiki.freebsd.org/MicrosoftAzure">FreeBSD on MicrosoftAzure wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/MicrosoftAzure" title="FreeBSD on MicrosoftAzure wiki">https://wiki.freebsd.org/MicrosoftAzure</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HyperV" title="https://wiki.freebsd.org/HyperV">FreeBSD on Microsoft HyperV</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HyperV" title="FreeBSD on Microsoft HyperV">https://wiki.freebsd.org/HyperV</a></td></tr></table><p>
-	Contact: FreeBSD Integration Services Team &lt;<a href="mailto:bsdic@microsoft.com">bsdic@microsoft.com</a>&gt;
-	<br />
-	Contact: Wei Hu &lt;<a href="mailto:whu@FreeBSD.org">whu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>Wei is working on HyperV Socket support for FreeBSD.
-	HyperV Socket provides a way for host and guest to
-	communicate using common socket interfaces without
-	networking support. Some features in Azure require
-	HyperV Socket support in guest.</p>
-<p>It is planned to commit the code by the end of February.</p>
-<p>This project is sponsored by Microsoft. Details of HyperV
-	Socket is available at
-	https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service</p>
-<p>Li-Wen and Wei are working on improving FreeBSD release on
-	Azure. During this quarter, Wei has published the
-	<a href="https://azuremarketplace.microsoft.com/en-us/marketplace/apps/microsoftostc.freebsd-11-3?tab=Overview" shape="rect">11.3-RELEASE
-	on Azure</a>. Li-Wen is working on the FreeBSD
-	release codes related to Azure for the -CURRENT
-	and 12-STABLE branches.</p>
-<p>This project is sponsored by Microsoft and FreeBSD
-	Foundation.</p>
-<hr /><h2><a name="FreeBSD-on-EC2-ARM64" href="#FreeBSD-on-EC2-ARM64" id="FreeBSD-on-EC2-ARM64">FreeBSD on EC2 ARM64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://aws.amazon.com/marketplace/pp/B081NF7BY7" title="https://aws.amazon.com/marketplace/pp/B081NF7BY7">FreeBSD/ARM 12 in AWS Marketplace</a></td><td>
-	    URL: <a href="https://aws.amazon.com/marketplace/pp/B081NF7BY7" title="FreeBSD/ARM 12 in AWS Marketplace">https://aws.amazon.com/marketplace/pp/B081NF7BY7</a></td></tr><tr><td><a href="https://www.patreon.com/cperciva" title="https://www.patreon.com/cperciva">FreeBSD/EC2 Patreon</a></td><td>
-	    URL: <a href="https://www.patreon.com/cperciva" title="FreeBSD/EC2 Patreon">https://www.patreon.com/cperciva</a></td></tr><tr><td><a href="https://twitter.com/cperciva/status/1206688489518985216" title="https://twitter.com/cperciva/status/1206688489518985216">M6G vs M5 buildworld cost/time performance</a></td><td>
-	    URL: <a href="https://twitter.com/cperciva/status/1206688489518985216" title="M6G vs M5 buildworld cost/time performance">https://twitter.com/cperciva/status/1206688489518985216</a></td></tr></table><p>
-	Contact: Colin Percival &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;
-	</p><p>In November 2018, Amazon Web Services announced the first
-	Elastic
-	Compute Cloud (EC2) instances built around the ARM64
-	platform.
-	While FreeBSD supported the ARM64 platform, running on
-	this specific
-	virtual machines took some additional work, but by April
-	2019 the
-	weekly snapshot builds performed by the Release
-	Engineering Team
-	included ARM64 AMIs for FreeBSD HEAD.</p>
-<p>In November 2019 FreeBSD 12.1 was released, including the
-	first
-	"RELEASE" FreeBSD EC2/ARM64 AMIs. A few weeks later,
-	FreeBSD/ARM64
-	was added as a new "product" to the AWS Marketplace.</p>
-<p>At the re:Invent 2019 conference in December 2019, Amazon
-	announced
-	a second family of ARM64 instances, known variously as
-	"Graviton 2"
-	and "M6G". These are far more powerful than the
-	first-generation
-	ARM64 EC2 instances, and have a roughly 40%
-	price/performance advantage
-	over the "M5" family of x86 EC2 instances; and existing
-	FreeBSD 12.1
-	and HEAD AMIs run "out of the box" on these instances.</p>
-<p>Work is currently underway to improve kernel locking
-	scalability on
-	these instances; with high levels of parallelism (e.g.
-	buildworld -j64)
-	the G6M instances have approximately 1.5x higher sys:user
-	ratios than
-	equally-sized M5 instances, suggesting that there is room
-	for improvement
-	here.</p>
-<p>Two issues have been recently identified, both likely
-	relating to ACPI:</p>
-<ul><li>EC2 "StopInstance" API calls, which translate to ACPI
-	"power button"
-	notifications, do not trigger FreeBSD to shut down; this
-	results in a
-	timeout from EC2 and a "hard poweroff".</li>
-<li>Hotplugging/unplugging EBS volumes, which normally
-	operates via ACPI
-	device notifications, does not work. </li></ul>
-<p>
-	Help from developers familiar with ARM64 and ACPI would be
-	much
-	appreciated.</p>
-<p>This project was sponsored by FreeBSD/EC2 Patreon.</p><hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Maciej Bielski &lt;<a href="mailto:mba@semihalf.com">mba@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p><p>ENA (Elastic Network Adapter) is the smart NIC available
-	in the
-	virtualized environment of Amazon Web Services (AWS). The
-	ENA
-	driver supports multiple transmit and receive queues and
-	can handle
-	up to 100 Gb/s of network traffic, depending on the
-	instance type
-	on which it is used.</p>
-<p>Completed since the last update:</p>
-<ul><li>Upstream of the driver v2.1.0 version, introducing:</li>
-<li>Netmap support</li>
-<li>Driver structure rework (split datapath code from
-	initialization)</li>
-<li>Fix for keep-alive timeout due to prolonged reset</li>
-<li>Enable LLQ mode on arm64 instances by enabling memory
-	mapped as WC </li></ul>
-<p>
-	Work in progress::</p>
-<ul><li>ENA v2.2.0 release, introducing new bug fixes, features
-	and other improvements </li></ul>
-<p></p>
-<p>This project was sponsored by Amazon.com Inc.</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="PowerPC-on-Clang" href="#PowerPC-on-Clang" id="PowerPC-on-Clang">PowerPC on Clang</a></h2><p>
-	Contact: Justin Hibbits &lt;<a href="mailto:jhibbits@freebsd.org">jhibbits@freebsd.org</a>&gt;
-	<br />
-	Contact: Brandon Bergren &lt;<a href="mailto:bdragon@freebsd.org">bdragon@freebsd.org</a>&gt;
-	<br />
-	Contact: Alfredo Dal'Ava J�nior &lt;<a href="mailto:alfredo.junior@eldorado.org.br">alfredo.junior@eldorado.org.br</a>&gt;
-	</p><p>Shortly before the end of the year all 3 PowerPC targets
-	(powerpc, powerpc64,
-	powerpcspe) switched to Clang as the base compiler. This
-	was an effort spanning
-	nearly the full year, with several people involved. 32-bit
-	PowerPC platforms
-	(powerpc, powerpcspe) still require GNU ld, but powerpc64
-	uses LLD as the base
-	linker. The other two platforms will migrate as soon as
-	LLD is ready, which
-	should be in the next several months.</p>
-<p>With the switch to Clang and LLD, powerpc64 also switched
-	to ELFv2, a modern ABI
-	initially targeted for Linux powerpc64le (little endian),
-	but the ABI itself is
-	endian agnostic; however, ELFv2 is binary incompatible
-	with ELFv1. FreeBSD is
-	still big endian on all powerpc targets.</p>
-<hr /><h2><a name="NXP-ARM64-SoC-support" href="#NXP-ARM64-SoC-support" id="NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></h2><p>
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	</p><p>The Semihalf team initiated working on FreeBSD support for
-	the
-	<a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A" shape="rect">NXP
-	LS1046A SoC</a></p>
-<p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors
-	with
-	integrated packet processing acceleration and high speed
-	peripherals
-	including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0
-	for a wide
-	range of networking, storage, security and industrial
-	applications.</p>
-<p>Completed since the last update:</p>
-<ul><li>QSPI</li>
-<li>Network performance improvements </li></ul>
-<p>
-	Todo:</p>
-<ul><li>Upstreaming of developed features. This work is expected
-	to
-	be submitted/merged to HEAD in the Q1 of 2020. </li></ul>
-<p></p>
-<p>This project was sponsored by Alstom Group.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><h2><a name="Linux-compatibility-layer-update" href="#Linux-compatibility-layer-update" id="Linux-compatibility-layer-update">Linux compatibility layer update</a></h2><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p><p>Linux binaries of Linux Test Projects tests are now part
-	of the <a href="https://ci.FreeBSD.org" shape="rect">FreeBSD Continuous
-	Integration infrastructure</a>.
-	This makes it easy to track progress in improving the
-	Linux
-	compatibility layer, and to detect regressions.</p>
-<p>There was a fair number of all kinds of improvements to
-	the layer,
-	ranging from updated linux(4) man page, to a new
-	<tt>linux</tt> rc script,
-	which now takes care of eg mounting Linux-specific
-	filesystems
-	or setting ELF fallback brand, to new syscalls, to tiny
-	improvements
-	such as making ^T work for Linux binaries.</p>
-<p>From the user point of view, when running 13-CURRENT,
-	Linux jails
-	are now in a mostly working state: you can SSH into a jail
-	with
-	CentOS 8 binaries, run screen(1), Emacs, Postgres, OpenJDK
-	11,
-	use <tt>yum upgrade</tt>...
-	Of course there's still a bunch of things that need work:</p>
-<ul><li>There is a patch from chuck@ that makes core dumps work
-	for
-	Linux binaries; this will make debugging much easier </li>
-<li>There are pending reviews for patches that add
-	<a href="https://reviews.freebsd.org/D13209" shape="rect">extended
-	attributes support</a>,
-	<a href="https://reviews.freebsd.org/D10275" shape="rect">fexecve(2)
-	syscall</a>,
-	<a href="https://reviews.freebsd.org/D19917" shape="rect">sendfile</a>;
-	they require wrapping
-	up and committing </li>
-<li>There are over <a href="https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/" shape="rect">400
-	failing LTP tests</a>.
-	Some of them are false positives, some are easy to fix
-	bugs, some require adding
-	new system calls. Any help is welcome. </li></ul>
-<p></p>
-<p>This project was sponsored by FreeBSD Foundation.</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p><p>The Ports Management Team is responsible for overseeing
-	the overall direction
-	of the Ports Tree, building packages, and personnel
-	matters. This entry shows
-	what happened in the last quarter.</p>
-<p>2019Q4 closed with a total of 38,200 ports and 2180 open
-	PRs of which a small
-	470 PRs are unassigned. Last quarter saw 7907 commits from
-	157 committers to
-	the HEAD branch and 358 commits from 61 committers to the
-	2019Q4 branch. This
-	seems to suggest a small increase in activity compared to
-	the quarter before.</p>
-<p>During the last quarter, we welcomed Oleksii "Alex"
-	Samorukov (samm@) and
-	Scott Long (scottl@, already a source committer) as new
-	ports committers. We
-	also said goodbye to az@, brd@, dtekse@, eadler@, and
-	johans@.</p>
-<p>The default versions of some ports changed: Lazarus is now
-	at version 2.0.6,
-	Samba at 4.10, and Python at 3.7. The web browsers
-	received their updates too:
-	Chromium is now at version 78.0.3904.108, Firefox at
-	version 72.0 and its ESR
-	counterpart at version 68.4.0. Finally, the Qt stack got
-	updated to version
-	5.13.2.</p>
-<p>Some modernizations took place: the "palm" category was
-	removed as well as the
-	virtual "ipv6" category. IPv6 support (next to IPv4) is
-	now considered the
-	norm. Lastly, the CentOS 6 ports were removed after their
-	CentOS 7 counterparts
-	were made the default in the previous quarter.</p>
-<p>As always, antoine@ was happy to take your exp-runs, this
-	time a total of 30,
-	for various ports and framework updates, default version
-	updates, and the
-	removal of OpenJDK 6 and OpenJRE 6.</p>
-<hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://community.kde.org/FreeBSD" title="https://community.kde.org/FreeBSD">KDE Community FreeBSD</a></td><td>
-	    URL: <a href="https://community.kde.org/FreeBSD" title="KDE Community FreeBSD">https://community.kde.org/FreeBSD</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p><p>The <i>KDE on FreeBSD</i> project packages the
-	software produced by
-	the KDE Community for FreeBSD. The software includes a
-	full desktop environment, the art application
-	<a href="https://kdenlive.org" shape="rect">https://kdenlive.org</a>
-	and hundreds of other applications that can be used on
-	any FreeBSD desktop machine.</p>
-<p>The monthly releases of KDE Frameworks, bugfix-releases of
-	KDE Plasma
-	Desktop and the quarterly feature release of KDE Plasma
-	Desktop
-	were all landed in the ports tree shortly after upstream
-	releases.
-	There were also monthly KDE Applications bugfix-releases
-	which also
-	landed in a timely manner.</p>
-<p>Digikam landed a new release thanks to Dima Panov.
-	We hope this gets rid of the instability caused by the
-	previous release update from last quarter.</p>
-<p>The <a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=New&amp;bug_status=Open&amp;bug_status=In%20Progress&amp;bug_status=UNCONFIRMED&amp;email1=kde%40FreeBSD.org&amp;emailassigned_to1=1&amp;emailtype1=substring&amp;f0=OP&amp;f1=OP&amp;f2=product&amp;f3=component&amp;f4=alias&amp;f5=short_desc&amp;f7=CP&amp;f8=CP&amp;f9=assigned_to&amp;j1=OR&amp;j_top=OR&amp;o2=substring&amp;o3=substring&amp;o4=substring&amp;o5=substring&amp;o9=substring&amp;query_format=advanced&amp;v2=kde%40&amp;v3=kde%40&amp;v4=kde%40&amp;v5=kde%40&amp;v9=kde%40&amp;human=1" shape="rect">open
-	bugs list</a>
-	grew to 32 this quarter with a handful of strange build
-	failures.
-	We welcome detailed bug reports
-	and patches. KDE packaging updates are prepared in
-	a <a href="https://github.com/freebsd/freebsd-ports-kde/" shape="rect">copy
-	of the ports repository</a>
-	on GitHub and then merged in SVN. We welcome pull requests
-	there as well.</p>
-<hr /><h2><a name="Java-on-FreeBSD" href="#Java-on-FreeBSD" id="Java-on-FreeBSD">Java on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/openjdk-jdk11u" title="https://github.com/freebsd/openjdk-jdk11u">OpenJDK 11 repository at FreeBSD GitHub</a></td><td>
-	    URL: <a href="https://github.com/freebsd/openjdk-jdk11u" title="OpenJDK 11 repository at FreeBSD GitHub">https://github.com/freebsd/openjdk-jdk11u</a></td></tr></table><p>
-	Contact: Greg Lewis &lt;<a href="mailto:glewis@FreeBSD.org">glewis@FreeBSD.org</a>&gt;
-	</p><p>During Q4 the FreeBSD java porting effort features smaller
-	updates than
-	those of the previous quarters. However, the following
-	changes are worth
-	mentioning:</p>
-<ul><li>Updated ports for OpenJDK 8u232, 11.0.5, and 13.0.1</li>
-<li>Removal of the EOL'ed Java 6, 9, and 10 ports</li>
-<li>Fixed remote debugging for Java 11+</li>
-<li>Fixed a problem with running external processes for Java
-	11+ </li></ul>
-<p></p>
-<p>This project was sponsored by FreeBSD Foundation.</p><hr /><h2><a name="Electron-and-VSCode" href="#Electron-and-VSCode" id="Electron-and-VSCode">Electron and VSCode</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/tagattie/FreeBSD-Electron" title="https://github.com/tagattie/FreeBSD-Electron">Electron port</a></td><td>
-	    URL: <a href="https://github.com/tagattie/FreeBSD-Electron" title="Electron port">https://github.com/tagattie/FreeBSD-Electron</a></td></tr><tr><td><a href="https://github.com/tagattie/FreeBSD-VSCode" title="https://github.com/tagattie/FreeBSD-VSCode">VSCode port</a></td><td>
-	    URL: <a href="https://github.com/tagattie/FreeBSD-VSCode" title="VSCode port">https://github.com/tagattie/FreeBSD-VSCode</a></td></tr></table><p>
-	Contact: Hiroki Tagato &lt;<a href="mailto:tagattie@yandex.com">tagattie@yandex.com</a>&gt;
-	<br />
-	Contact: Luca Pizzamiglio &lt;<a href="mailto:pizzamig@FreeBSD.org">pizzamig@FreeBSD.org</a>&gt;
-	</p><p>Electron is a popular framework to build desktop
-	application using JavaScript, HTML and CSS.
-	Few months ago, electronjs has been added to the ports
-	tree.
-	Currently version 4.x and 6.x are supported.</p>
-<p>In the last quarter, a popular application, the powerful
-	VSCode editor, has been added to the ports tree as
-	well.
-	VSCode is based on electron 6.x</p>
-<p>atom, another popular editor, is still a work in progress
-	and it's based on electron 4.x</p>
-<p>Many thanks to Hiroki, for the hard work, and to Antoine,
-	for support of the special poudriere configuration
-	needed to build VSCode.</p>
-<hr /><h2><a name="Bastille" href="#Bastille" id="Bastille">Bastille</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/BastilleBSD/bastille" title="https://github.com/BastilleBSD/bastille">Bastille GitHub</a></td><td>
-	    URL: <a href="https://github.com/BastilleBSD/bastille" title="Bastille GitHub">https://github.com/BastilleBSD/bastille</a></td></tr><tr><td><a href="https://gitlab.com/bastillebsd-templates" title="https://gitlab.com/bastillebsd-templates">Bastille Templates</a></td><td>
-	    URL: <a href="https://gitlab.com/bastillebsd-templates" title="Bastille Templates">https://gitlab.com/bastillebsd-templates</a></td></tr><tr><td><a href="https://bastillebsd.org" title="https://bastillebsd.org">Bastille Website</a></td><td>
-	    URL: <a href="https://bastillebsd.org" title="Bastille Website">https://bastillebsd.org</a></td></tr></table><p>
-	Contact: Christer Edwards &lt;<a href="mailto:christer.edwards@gmail.com">christer.edwards@gmail.com</a>&gt;
-	</p><h3>What is Bastille?</h3>
-<p>Bastille is an open-source system for automating
-	deployment and management of
-	containerized applications on FreeBSD.</p>
-<p>Bastille uses FreeBSD jails as a container platform and
-	adds template
-	automation to create a Docker-like collection of
-	containerized software. The
-	template collection currently validates 30-40 applications
-	from the ports tree,
-	and is growing!</p>
-<p>Templates take care of installing, configuring, enabling,
-	and starting the
-	software, providing an automated way of building
-	containerized stacks.</p>
-<p>Bastille is available in ports at
-	<tt>sysutils/bastille</tt>.</p>
-<h3>Q4 2019 Status</h3>
-<p>In Q4 2019 Bastille published three releases (for a total
-	of ten releases in
-	2019). Highlights from these updates include:</p>
-<ul><li>support for "thin" (shared base) and "thick" (unique base)
-	jails</li>
-<li>support for INCLUDE and FSTAB in template system</li>
-<li>upgrade support for shared and unique base jails</li>
-<li>GitLab CI/CD testing for all official templates</li>
-<li>automatic template validation and CVE scan</li>
-<li>dedicated pf table for private IP jails </li></ul>
-<p>
-	Bastille saw an increase in community contributions with
-	six new GitHub
-	contributors. These people generously improved error
-	checking, release
-	validation (sha256), firewall functionality, flexible
-	networking and
-	initial support for resource limits!</p>
-<p>We want to thank everyone that contributed to Bastille in
-	2019. Your support
-	has been amazing!</p>
-<hr /><h2><a name="Universal-Packaging-Tool-(upt)" href="#Universal-Packaging-Tool-(upt)" id="Universal-Packaging-Tool-(upt)">Universal Packaging Tool (upt)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://framagit.org/upt/" title="https://framagit.org/upt/">Upt repositories</a></td><td>
-	    URL: <a href="https://framagit.org/upt/" title="Upt repositories">https://framagit.org/upt/</a></td></tr><tr><td><a href="https://framagit.org/upt/upt/" title="https://framagit.org/upt/upt/">Upt itself</a></td><td>
-	    URL: <a href="https://framagit.org/upt/upt/" title="Upt itself">https://framagit.org/upt/upt/</a></td></tr><tr><td><a href="https://framagit.org/upt/upt-freebsd" title="https://framagit.org/upt/upt-freebsd">The FreeBSD backend</a></td><td>
-	    URL: <a href="https://framagit.org/upt/upt-freebsd" title="The FreeBSD backend">https://framagit.org/upt/upt-freebsd</a></td></tr></table><p>
-	Contact: The upt mailing list &lt;<a href="mailto:upt@framalistes.org">upt@framalistes.org</a>&gt;
-	<br />
-	Contact:  &lt;<a href="mailto:#upt-packaging">#upt-packaging</a>&gt;
-	</p><p>The Universal Package Manager (upt) is a tool designed to
-	easily port
-	software from common upstream package archives (such as
-	<a href="https://rubygems.org/" shape="rect">https://rubygems.org/</a>)
-	to
-	various operating systems, including FreeBSD, of course.</p>
-<p>A lot of similar tools already exist: pytoport (which
-	creates FreeBSD
-	ports for PyPI packages), gem2deb (which creates Debian
-	packages from a
-	Ruby gem), and many others.</p>
-<p>The main difference between these tools and upt is that
-	the latter uses
-	a modular design, allowing it to handle packages from many
-	sources and
-	support many different operating systems through plugins.
-	You may
-	try upt by installing sysutils/py-upt,
-	sysutils/py-upt-pypi and
-	sysutils/py-upt-freebsd. Suppose you would like to package
-	"upt-cran",
-	which is hosted on PyPI. You could do it like so:</p>
-<code><p>
-	# upt package -f pypi -b freebsd -o /usr/ports/sysutils/
-	upt-cran</p>
-<p>$ tree /usr/ports/sysutils/py-upt-cran
-	/usr/ports/sysutils/py-upt-cran
-	|-- Makefile
-	|-- distinfo
-	`-- pkg-descr</p>
-<p>$ cat sysutils/py-upt-cran/Makefile
-	# $FreeBSD$</p>
-<p>PORTNAME= upt-cran
-	DISTVERSION= 0.1
-	CATEGORIES= sysutils python
-	MASTER_SITES= CHEESESHOP
-	PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}</p>
-<p>MAINTAINER= python@FreeBSD.org
-	COMMENT= CRAN frontend for upt</p>
-<p>LICENSE= BSD3CLAUSE
-	LICENSE_FILE= ${WRKSRC}/XXX</p>
-<p>RUN_DEPENDS=
-	${PYTHON_PKGNAMEPREFIX}lxml&gt;0:devel/py-lxml@${PY_FLAVOR}
-	\
-
-	${PYTHON_PKGNAMEPREFIX}requests&gt;0:www/py-requests@${PY_FLAVOR}
-	\
-
-	${PYTHON_PKGNAMEPREFIX}upt&gt;0:sysutils/py-upt@${PY_FLAVOR}
-	TEST_DEPENDS=
-	${PYTHON_PKGNAMEPREFIX}requests-mock&gt;0:www/py-requests-mock@${PY_FLAVOR}</p>
-<p>USES= python
-	USE_PYTHON= autoplist distutils</p>
-<p>.include &lt;bsd.port.mk&gt;</p>
-</code>
-<p></p>
-<p>Note that the Rubygems and CPAN frontends are also
-	available
-	(sysutils/py-upt-rubygems and sysutils/py-upt-cpan).</p>
-<p>Bug reports and comments about this new tool are welcome.</p>
-<hr /><h2><a name="Wine-on-FreeBSD" href="#Wine-on-FreeBSD" id="Wine-on-FreeBSD">Wine on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.winehq.org" title="https://www.winehq.org">Wine homepage</a></td><td>
-	    URL: <a href="https://www.winehq.org" title="Wine homepage">https://www.winehq.org</a></td></tr></table><p>
-	Contact: Gerald Pfeifer &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	</p><p>A lot has happened since our last quarterly report. The
-	Wine 4
-	release series has been in our tree for nearly a year and
-	proven
-	rather stable. Both that port and wine-devel, which tracks
-	bi-weekly development releases, have seen regular
-	adjustments to
-	infrastructure changes and small improvements, in
-	particular also
-	around non-default options.</p>
-<p>Now we need help!</p>
-<p>WoW64 (or Wine on Wine 64) allows running both 32-bit and
-	64-bit
-	Windows applications in one installation. A volunteer has
-	proposed</p>
-<ul><li>a general framework for lib32- companion libraries
-	<a href="https://reviews.freebsd.org/D16830" shape="rect">https://reviews.freebsd.org/D16830</a></li>
-<li>an approach directly using our Wine ports
-	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242625" shape="rect">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242625</a> </li></ul>
-<p>
-	to make this work and we do not have the expertise nor
-	facilities to
-	properly review, test, and maintain those ourselves.</p>
-<p>If you can facilitate getting (at least one of) these into
-	the tree,
-	please help! And if you'd like to assume co-maintainership
-	or sole
-	maintainership of emulators/wine*, that is an option, too.</p>
-<hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="sysctlbyname-improved" href="#sysctlbyname-improved" id="sysctlbyname-improved">sysctlbyname-improved</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/alfix/sysctlbyname-improved" title="https://gitlab.com/alfix/sysctlbyname-improved">gitlab.com/alfix/sysctlbyname-improved</a></td><td>
-	    URL: <a href="https://gitlab.com/alfix/sysctlbyname-improved" title="gitlab.com/alfix/sysctlbyname-improved">https://gitlab.com/alfix/sysctlbyname-improved</a></td></tr></table><p>
-	Contact: Alfonso Sabato Siciliano &lt;<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>&gt;
-	</p><p>The FreeBSD kernel maintains a Management Information Base
-	(MIB) where a
-	component (object) represents a parameter of the system.
-	The sysctl() system
-	call explores the MIB to find an object by its Object
-	Identifier (OID) and
-	calls its handler to get or set the value of the
-	parameter.</p>
-<p>The sysctlbyname() syscall (or the old function) accepts
-	the name of the object
-	(instead of its OID) to identify it. The purpose of this
-	project is to allow
-	sysctlbyname() to handle:</p>
-<ul><li>a CTLTYPE_NODE with a no-NULL handler, example
-	"kern.proc.pid.\&lt;pid\&gt;";</li>
-<li>an object with some level-name equals to the '\0'
-	character, example
-	"security.jail.param.allow.mount."; </li></ul>
-<p>
-	A sysctlbyname() clone is provided:
-	sysctlbyname_improved(), the
-	implementation core is a new sysctl internal node to get
-	the OID of a node
-	by its name eventually expanded with an input for its
-	handler; both, can be
-	installed via _sysutils/sysctlbyname-improved-kmod_.
-	The internal node is also used by the
-	sysctlmif_oidinputbyname() function of
-	the _devel/libsysctlmibinfo2_ userland library and can be
-	handled by the
-	SYSCTLINFO_BYNAME macro of the sysctlinfo interface
-	(described in the previous
-	quarterly status report).</p>
-<hr /><h2><a name="pot-and-the-nomad-pot-driver" href="#pot-and-the-nomad-pot-driver" id="pot-and-the-nomad-pot-driver">pot and the nomad pot driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/trivago/nomad-pot-driver" title="https://github.com/trivago/nomad-pot-driver">Nomad pot driver</a></td><td>
-	    URL: <a href="https://github.com/trivago/nomad-pot-driver" title="Nomad pot driver">https://github.com/trivago/nomad-pot-driver</a></td></tr><tr><td><a href="https://github.com/pizzamig/pot" title="https://github.com/pizzamig/pot">Pot project</a></td><td>
-	    URL: <a href="https://github.com/pizzamig/pot" title="Pot project">https://github.com/pizzamig/pot</a></td></tr><tr><td><a href="https://github.com/pizzamig/minipot" title="https://github.com/pizzamig/minipot">minipot</a></td><td>
-	    URL: <a href="https://github.com/pizzamig/minipot" title="minipot">https://github.com/pizzamig/minipot</a></td></tr></table><p>
-	Contact: Luca Pizzamiglio &lt;<a href="mailto:pizzamig@FreeBSD.org">pizzamig@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Esteban Barrios &lt;<a href="mailto:esteban.barrios@trivago.com">esteban.barrios@trivago.com</a>&gt;
-	</p><p>The pot utility added support to private bridges: a group
-	of jail can now use a dedicated bridge, instead of
-	the public one, improving isolation.
-	Moreover, several small bugs have been found and fixed,
-	and support to pre/post start/stop hook script has
-	been added.</p>
-<p>The nomad pot driver received support for nomad restart
-	without drain and improved configuration
-	stability.</p>
-<p>A new port called minipot has been added: this port will
-	install configuration files and dependencies,
-	converting a FreeBSD machine in a single node
-	cluster. It will install nomad, consul, pot, the
-	nomad pot driver and traefik, already configured
-	and ready to use.</p>
-<p>Experimental work has been done on a tool that allows to
-	create and run pot images (FreeBSD jails) on other
-	operating systems (Linux and Mac), adopting an
-	approach similar to docker machine.
-	We hope to make this tool available soon.</p>
-<p>Next steps:</p>
-<ul><li>add dual IP stack support to pot</li>
-<li>add private bridge support to the nomad pot driver</li>
-<li>improve usability to create images </li></ul>
-<p></p>
-<p>This project was sponsored by trivago N.V..</p><hr /><h2><a name="7-Days-Challenge" href="#7-Days-Challenge" id="7-Days-Challenge">7 Days Challenge</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/MichaelCrilly/7dayschallenge" title="https://wiki.freebsd.org/MichaelCrilly/7dayschallenge">7 Days Challenge</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/MichaelCrilly/7dayschallenge" title="7 Days Challenge">https://wiki.freebsd.org/MichaelCrilly/7dayschallenge</a></td></tr></table><p>
-	Contact: Michael Crilly &lt;<a href="mailto:mike@opsfactory.com.au">mike@opsfactory.com.au</a>&gt;
-	</p><p>The 7 Days Challenge is an educational initiative to help
-	people onboard with FreeBSD more easily.</p>
-<p>It will use a combination of tutorials, guides and how-tos
-	to get users engaged with
-	FreeBSD quickly, target specific end goals the user might
-	have for FreeBSD, and more.</p>
-<p>The primary objective is to demonstrate FreeBSD's
-	capabilities as a modern, relevant operating
-	system in today's Cloud centric, automated business
-	models.</p>
-<p>This project was sponsored by OpsFactory Pty Ltd (Australia).</p><hr /><h2><a name="NomadBSD" href="#NomadBSD" id="NomadBSD">NomadBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.nomadbsd.org/" title="https://www.nomadbsd.org/">NomadBSD Website</a></td><td>
-	    URL: <a href="https://www.nomadbsd.org/" title="NomadBSD Website">https://www.nomadbsd.org/</a></td></tr><tr><td><a href="https://www.github.com/NomadBSD/NomadBSD" title="https://www.github.com/NomadBSD/NomadBSD">NomadBSD Github</a></td><td>
-	    URL: <a href="https://www.github.com/NomadBSD/NomadBSD" title="NomadBSD Github">https://www.github.com/NomadBSD/NomadBSD</a></td></tr><tr><td><a href="https://www.freelists.org/list/nomadbsddevs" title="https://www.freelists.org/list/nomadbsddevs">NomadBSD Developer Mailing List</a></td><td>
-	    URL: <a href="https://www.freelists.org/list/nomadbsddevs" title="NomadBSD Developer Mailing List">https://www.freelists.org/list/nomadbsddevs</a></td></tr></table><p>
-	Contact: NomadBSD Team &lt;<a href="mailto:info@NomadBSD.org">info@NomadBSD.org</a>&gt;
-	</p><p>NomadBSD is a persistent live system for USB flash drives,
-	based on FreeBSD.
-	Together with automatic hardware detection and setup, it
-	is configured to be
-	used as a desktop system that works out of the box, but
-	can also be used for
-	data recovery, for educational purposes, or testing
-	FreeBSD's hardware
-	compatibility.</p>
-<p>After one release candidate the NomadBSD Team finished and
-	released NomadBSD
-	1.3 on December 7th.
-	This release is based on FreeBSD 12.1, fixed a lot of bugs
-	and added new
-	packages and features.
-	Along those features are the option to install NomadBSD on
-	ZFS and the use of an
-	automatic configuration when running NomadBSD in
-	VirtualBox.</p>
-<p>New tools developed by the NomadBSD Team and added to
-	version 1.3 are
-	nomadbsd-dmconfig to select a display manager theme,
-	nomadbsd-adduser which adds
-	new user accounts and DSBBg to change the background
-	image. All these are using
-	the Qt-Toolkit.</p>
-<p>In Q4 we added two mirrors in France and Germany and would
-	like to thank
-	nosheep.fr and fau.de for them.</p>
-<p>We are looking for people to help the project. Help is
-	much appreciated in all areas:</p>
-<ul><li>Translation of program interfaces</li>
-<li>Design artwork</li>
-<li>Programming new tools, extend existing ones</li>
-<li>Tests and Bug reports / UX and feature suggestions</li>
-<li>Mirrors outside of Europe </li></ul>
-<p>
-	Open tasks:</p>
-<ul><li>Support installation on disk partitions and add a
-	partition editor GUI.</li>
-<li>Complete disk encryption</li>
-<li>Add a user-friendly network manager </li></ul>
-<hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2020-01-2020-03.html b/website/content/en/status/report-2020-01-2020-03.html
deleted file mode 100644
index c70646259e..0000000000
--- a/website/content/en/status/report-2020-01-2020-03.html
+++ /dev/null
@@ -1,1710 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>Welcome, to the quarterly reports, of the future! Well, at least the first
-quarterly report from 2020.  The new timeline, mentioned in the last few
-reports, still holds, which brings us to this report, which covers the period
-of January 2020 - March 2020.
-</p><p>As you will see from this report, we've had quite an active quarter with big
-changes to both kernel, userland, documentation, ports, and third-party
-projects in the form of everything from bug and security fixes over new features
-to speed improvements and optimizations.
-</p><p>As this report also covers the start of the epidemic, it's also interesting to
-note that a quick glance at the svn logs reveal that there has been no overall
-drop in number of source commits, that docs commits have also stayed constant,
-and that ports have seen an upwards trend.
-</p><p>We hope that all of you are and yours are as safe as can be managed, and that
-we get through this together by working together.
-</p><p>-- Daniel Ebdrup Jensen, <a href="mailto:debdrup@freebsd.org" shape="rect">debdrup@freebsd.org</a>
-</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Cluster-Administration-Team">Cluster Administration Team</a></li><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#NFS-over-TLS-implementation">NFS over TLS implementation</a></li><li><a href="#Import-of-the-Kyua-test-framework">Import of the Kyua test framework</a></li><li><a href="#Linux-compatibility-layer-update">Linux compatibility layer update</a></li><li><a href="#syzkaller-on-FreeBSD">syzkaller on FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#if_bridge">if_bridge</a></li><li><a href="#sigfastblock(2)">sigfastblock(2)</a></li><li><a href="#arm64-LSE-atomic-instructions">arm64 LSE atomic instructions</a></li><li><a href="#FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></li><li><a href="#FreeBSD-on-the-ARM-Morello-platform">FreeBSD on the ARM Morello platform</a></li><li><a href="#NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/powerpc-Project">FreeBSD/powerpc Project</a></li><li><a href="#FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#GCC-4.2.1-Retirement">GCC 4.2.1 Retirement</a></li><li><a href="#elfctl-utility">elfctl utility</a></li><li><a href="#ELF-Tool-Chain">ELF Tool Chain</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#XFCE">XFCE</a></li><li><a href="#Wine-on-FreeBSD">Wine on FreeBSD</a></li><li><a href="#Go-on-freebsd/arm64">Go on freebsd/arm64</a></li><li><a href="#sysctlmibinfo2-API">sysctlmibinfo2 API</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></li><li><a href="#FreeBSD-Manpages-overhaul">FreeBSD Manpages overhaul</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#pot-and-the-nomad-pot-driver">pot and the nomad pot driver</a></li><li><a href="#NomadBSD">NomadBSD</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-	Page</a>.</p><br /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p><p>The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
-supporting and promoting the FreeBSD Project and community worldwide.  Funding
-comes from individual and corporate donations and is used to fund and manage
-software development projects, conferences and developer summits, and provide
-travel grants to FreeBSD contributors.  The Foundation purchases and supports
-hardware to improve and maintain FreeBSD infrastructure and provides resources
-to improve security, quality assurance, and release engineering efforts;
-publishes marketing material to promote, educate, and advocate for the FreeBSD
-Project; facilitates collaboration between commercial vendors and FreeBSD
-developers; and finally, represents the FreeBSD Project in executing contracts,
-license agreements, and other legal arrangements that require a recognized
-legal entity.
-</p>
-<p>Here are some highlights of what we did to help FreeBSD last quarter:
-</p>
-<h3>General</h3>
-
-<p>We moved! Our new address is:<br clear="none" />
-The FreeBSD Foundation<br clear="none" />
-3980 Broadway St. STE #103-107<br clear="none" />
-Boulder, CO 80304<br clear="none" />
-USA<br clear="none" />
-</p>
-<p>In February, the board of directors had an all-day board meeting in Berkely, CA,
-where FreeBSD began!  We put together our strategic plans for the next 2 years,
-which includes software developments projects we want to support and some
-educational initiatives.
-</p>
-<p>COVID-19 impacts the Foundation.  We put policies in place for all of our staff
-members to work from home.  We also put a temporary ban on travel for staff
-members.  We are continuing our work supporting the community and Project, but
-some of our work and responses are delayed because of changes in some of our
-priorities and the impact of limited childcare for a few of our staff members.
-</p>
-<h3>Partnerships and Commercial User Support</h3>
-
-<p>We help facilitate collaboration between commercial users and FreeBSD
-developers.  We also meet with companies to discuss their needs and bring that
-information back to the Project.  In Q1, Deb Goodkin met with commercial users
-at LinuxConfAu in Australia, FOSDEM in Belgium, and SCALE18x in the US.  These
-venues provide an excellent opportunity to meet with commercial and individual
-users and contributors to FreeBSD. It's not only beneficial for the above, but
-it also helps us understand some of the applications where FreeBSD is used.
-In addition to meeting with commercial users at conferences, we continued
-discussions over email or on calls over the quarter.
-</p>
-<h3>Fundraising Efforts</h3>
-
-<p>Last quarter we raised $57,000!  Thank you to everyone who came through,
-especially in this economic crisis we have found ourselves in.  It heartens us
-deeply that individuals and organizations have supported our efforts, when there
-are so many people, animals, and businesses in need right now.  We also want to
-extend a big thank you to Tarsnap, VMWare, and Stormshield for leading the way
-with Silver level donations.  We hope other organizations will follow their lead
-and give back to help us continue supporting FreeBSD.
-</p>
-<p>We are 100% funded by donations, and those funds go towards software development
-work to improve FreeBSD, FreeBSD advocacy around the world, keeping FreeBSD
-secure, continuous integration improvements, sponsoring BSD-related and
-computing conferences, legal support for the Project, and many other areas.
-</p>
-<p>Please consider making a donation to help us continue and increase our support
-for FreeBSD: https://www.FreeBSDfoundation.org/donate/.
-</p>
-<p>We also have the Partnership Program, to provide more benefits for our larger
-commercial donors.  Find out more information at
-https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/ and
-share with your companies!
-</p>
-<h3>OS Improvements</h3>
-
-<p>The Foundation supports software development projects to improve the FreeBSD
-operating system through our full time technical staff, contractors, and project
-grant recipients.  They maintain and improve critical kernel subsystems, add new
-features and functionality, and fix problems.
-</p>
-<p>Over the last quarter there were 273 commits to the FreeBSD base system source
-repository tagged with FreeBSD Foundation sponsorship, about 12% of base system
-commits over the quarter.  Many of these are part of sponsored or staff projects
-that have their own entries in this FreeBSD Quarterly Report, but Foundation
-staff and contractors (Ed Maste, Konstantin Belousov, Mark Johnston, Li-Wen Hsu)
-also support the project with an ongoing series of bug fixes, build fixes, and
-miscellaneous improvements that don't warrant a separate entry.
-</p>
-<p>Ed committed miscellaneous improvements to various parts of FreeBSD's build
-infrastructure, largely prompted by the work to retire the obsolete GCC 4.2.1.
-This included removal of the <i>LLVM_LIBUNWIND</i> option (now always set), and
-the removal of unused gperf, gcov, and the GPL devicetree compiler (dtc).  Ed
-committed sendfile support for the Linuxulator, submitted by previous intern
-Bora �zarslan, and tested and committed a number of submitted bug fixes for
-the Microchip USB-Ethernet controller <i>if_muge</i> driver.  Ed also updated the
-copy of OpenSSH in the base system to 7.9p1, with additional updates in
-progress, and worked on a number of security advisories released during the
-quarter.
-</p>
-<p>Konstantin Belousov and Mark Johnston both performed a large number of code
-reviews during the quarter under Foundation sponsorship.  This work helps
-developers in the FreeBSD community and those working at companies using
-FreeBSD to integrate their work into FreeBSD.
-</p>
-<p>In addition to work described elsewhere in this report Konstantin also
-continued his usual series of bug fixes and improvements.  This quarter this
-included low-level x86 support, fixing sendfile bugs, file system and vfs
-bug fixes, and dozens of other miscellaneous improvements.  Additional work
-included a variety of commits to support Hygon x86 CPUs and improvements to
-the runtime linker (rtld)'s direct execution mode.
-</p>
-<p>Mark Johnston continued his work on the
-<a href="https://syzkaller.appspot.com/freebsd" shape="rect">Syzkaller</a> system-call fuzzer, and
-committed fixes for many issues reported by Syzkaller.  Mark triaged a large
-number of submitted bug reports and in many cases committed attached patches
-or developed fixes.  Mark also addressed dozens of Coverity Scan reports.
-</p>
-<p>Mark's other changes included arm64 Large System Extensions (LSE) atomic
-operations, low-level arm64 and x86 work, virtual memory (VM) work, and bug
-fixes or other improvements to syslog, the lagg(4) link aggregation driver,
-and build reproducibility.
-</p>
-<p>Li-Wen Hsu committed many changes to tests in the base system, such as turning
-off known failing tests tracked by PRs, test-related pkgbase fixes, and other
-improvements.
-</p>
-<h3>Continuous Integration and Quality Assurance</h3>
-
-<p>The Foundation provides a full-time staff member who is working on improving
-our automated testing, continuous integration, and overall quality assurance
-efforts.
-</p>
-<p>During the first quarter of 2020, Foundation staff continued to improve the
-Project's CI infrastructure, worked with contributors to fix the failing build
-and test cases.  The building of a CI staging environment is in progress on the
-new machine purchased by the Foundation.  We are also working with other teams
-in the Project for their testing needs.  For example, we added a new job for
-running LTP (Linux Testing Project) on the Linuxulator, to validate improvements
-in the Foundation's sponsored Linux emulation work.  We are also working with
-many external projects and companies to improve their support of FreeBSD.
-</p>
-<p>See the FreeBSD CI section of this report for completed work items and detailed
-information.
-</p>
-<h3>Supporting FreeBSD Infrastructure</h3>
-
-<p>The Foundation provides hardware and support to improve the FreeBSD
-infrastructure.  Last quarter, we continued supporting FreeBSD hardware located
-around the world.  We purchased one server for a mirror in Malaysia, and signed
-the MOU for the new NYI colocation facility in Illinois.  NYI generously
-provides this as an in-kind donation to the Project.
-</p>
-<h3>FreeBSD Advocacy and Education</h3>
-
-<p>A large part of our efforts are dedicated to advocating for the Project.  This
-includes promoting work being done by others with FreeBSD; producing advocacy
-literature to teach people about FreeBSD and help make the path to starting
-using FreeBSD or contributing to the Project easier; and attending and getting
-other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD
-tables, and give FreeBSD presentations.
-</p>
-<p>The FreeBSD Foundation sponsors many conferences, events, and summits around the
-globe.  These events can be BSD-related, open source, or technology events
-geared towards underrepresented groups.  We support the FreeBSD-focused events
-to help provide a venue for sharing knowledge, to work together on projects, and
-to facilitate collaboration between developers and commercial users.  This all
-helps provide a healthy ecosystem.  We support the non-FreeBSD events to promote
-and raise awareness of FreeBSD, to increase the use of FreeBSD in different
-applications, and to recruit more contributors to the Project.
-</p>
-<p>Check out some of the advocacy and education work we did last quarter:
-</p>
-<ul>
-<li><p>Organized and presented at the first ever FreeBSD Mini-Conf LinuxConfAu 2020,
-  in Gold Coast, Australia in addition to sponsoring the conference itself.
-  <a href="https://www.freebsdfoundation.org/blog/freebsd-miniconf-at-lca2020-conference-recap/" shape="rect">The recap can be found here</a>.
-</p>
-</li>
-<li><p>Presented BSD Dev Room at FOSDEM '20, in Brussels, Belgium and represented
-  FreeBSD at a stand along with other members of the community.  [Find out more
-  here](https://www.freebsdfoundation.org/blog/fosdem-2020-conference-recap/).
-</p>
-</li>
-<li><p>Represented FreeBSD at Apricot 2020 in Melbourne, Australia and sponsored the
-  event.
-</p>
-</li>
-<li><p>Industry Partner Sponsor for USENIX FAST '20 in Santa Clara, CA
-</p>
-</li>
-<li><p>Sponsored FOSSASIA 2020, in Singapore
-</p>
-</li>
-<li><p>Committed to hold FreeBSD Day at SCALE 18x, in Pasadena, CA
-</p>
-</li>
-<li><p>Held a "Getting Started with FreeBSD Workshop" at SCALE 18x in addition to
-  giving a talk, representing FreeBSD at the Expo and holding a "Why FreeBSD is
-  Me" BoF.  Check out the <a href="https://www.freebsdfoundation.org/blog/scale-18x-conference-recap/" shape="rect">conference recap</a>.
-</p>
-</li></ul>
-We continued producing FreeBSD advocacy material to help people promote FreeBSD.
-<p>Learn more about our efforts in 2019 to <a href="https://www.freebsdfoundation.org/blog/2019-in-review-advocacy/" shape="rect">advocate for FreeBSD</a>.
-</p>
-<p>In addition to the information found in the Development Projects update section
-of this report, take a minute to check out the latest update blogs:
-</p>
-<ul>
-<li><p><a href="https://www.freebsdfoundation.org/blog/power-to-the-people-making-freebsd-a-first-class-citizen-on-power/" shape="rect">POWER to the People: Making FreeBSD a First Class Citizen on POWER</a>.
-</p>
-</li>
-<li><p><a href="https://www.freebsdfoundation.org/blog/project-update-toolchain-modernization/" shape="rect">Development Project Update: Toolchain Modernization</a>.
-</p>
-</li></ul>
-Read more about our conference adventures in the conference recaps and trip
-<p>reports in <a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">our monthly newsletters</a>.
-</p>
-<p>We help educate the world about FreeBSD by publishing the professionally
-produced FreeBSD Journal.  As we mentioned previously, the FreeBSD Journal is
-now a free publication.  <a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">Find out more and access the latest issues</a>.
-</p>
-<p><a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">You can find out more about events we attended and upcoming events here</a>.
-As is the case for most of
-us in this industry, SCALE was the last event we will be attending for a few
-months.  However, we're already working on how we can make more on-line
-tutorials and how-to guides available to facilitate getting more folks to try
-out FreeBSD.  In the meantime, please check out the how-to guides we already
-have available!
-</p>
-<p>We have continued our work with a new website developer to help us improve our
-website.  Work has begun to make it easier for community members to find
-information more easily and to make the site more efficient.
-</p>
-<h3>Legal/FreeBSD IP</h3>
-
-<p>The Foundation owns the FreeBSD trademarks, and it is our responsibility to
-protect them.  We also provide legal support for the core team to investigate
-questions that arise.
-</p>
-<p>Go to http://www.FreeBSDfoundation.org/ to find out how we support FreeBSD and
-how we can help you!
-</p><hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Core Team is the governing body of FreeBSD.
-</p>
-<ul>
-<li><p>Core approved a source commit bit for Alfredo Dal'Ava J�nior.  Alfredo has
-  been working on powerpc64 support.  Justin Hibbits (jhibbits) will mentor
-  Alfredo.
-</p>
-</li>
-<li><p>Core approved a source commit bit for Ryan Moeller.  Ryan has been working on
-  porting ZoL to FreeBSD.  Alexander Motin (mav) and Matt Macy (mmacy) will
-  mentor Ryan.
-</p>
-</li>
-<li><p>Core approved a source commit bit for Nick O'Brien.  Nick has been working on
-  RISC-V at Axiado.  Kristof Provost (kp) and Philip Paeps (philip) will mentor
-  Nick.
-</p>
-</li>
-<li><p>Core approved a source commit bit for Richard Scheffenegger.  Richard has been
-  contributing TCP work.  Michael Tuexen (tuexen) will mentor Richard and Rodney
-  Grimes (rgrimes) will act as co-mentor.
-</p>
-</li>
-<li><p>Core approved a source commit bit for Aleksandr Fedorov.  Aleksandr has been
-  testing and reviewing bhyve networking code.  Vincenzo Maffione (vmaffione)
-  will mentor Aleksandr and John Baldwin (jhb) will act as co-mentor.
-</p>
-</li>
-<li><p>Core requested that the freebsd-mobile@ list be retired as it was almost
-  exclusively receiving spam.  postmaster@ completed core's request.
-</p>
-</li>
-<li><p>Core approved third party authentication for some project services with
-  certain conditions.  For example, for authentication with Google, users must
-  be using a FreeBSD.org account with two-factor authentication enabled.  For
-  GitHub, we will enable and force multi-factor authentication for our
-  organization.
-</p>
-</li>
-<li><p>The Core-initiated Git Transition Working Group continued to meet over the
-  first quarter of 2020.  Their report is still forthcoming.
-</p></li></ul>
-<hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/11.4R/schedule.html" title="https://www.freebsd.org/releases/11.4R/schedule.html">FreeBSD 11.4-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.4R/schedule.html" title="FreeBSD 11.4-RELEASE schedule">https://www.freebsd.org/releases/11.4R/schedule.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/12.2R/schedule.html" title="https://www.freebsd.org/releases/12.2R/schedule.html">FreeBSD 12.2-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/12.2R/schedule.html" title="FreeBSD 12.2-RELEASE schedule">https://www.freebsd.org/releases/12.2R/schedule.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Release Engineering Team is responsible for setting
-and publishing release schedules for official project releases
-of FreeBSD, announcing code freezes and maintaining the
-respective branches, among other things.
-</p>
-<p>The FreeBSD Release Engineering Team published the schedules for the upcoming
-11.4-RELEASE and 12.2-RELEASE cycles.
-</p>
-<p>Much time was spent by Glen Barber working on updates to the various build
-tools adding support for builds from both Subversion and Git.  This is very
-much a work in progress, as there are a number of inter-connected moving
-parts.
-</p>
-<p>Additionally throughout the quarter, several development snapshots builds
-were released for the <i>head</i>, <i>stable/12</i>, and <i>stable/11</i> branches.
-</p>
-<p>Much of this work was sponsored by Rubicon Communications, LLC (netgate.com)
-and the FreeBSD Foundation.
-</p><hr /><h2><a name="Cluster-Administration-Team" href="#Cluster-Administration-Team" id="Cluster-Administration-Team">Cluster Administration Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/administration.html#t-clusteradm" title="https://www.freebsd.org/administration.html#t-clusteradm">Cluster Administration Team members</a></td><td>
-	    URL: <a href="https://www.freebsd.org/administration.html#t-clusteradm" title="Cluster Administration Team members">https://www.freebsd.org/administration.html#t-clusteradm</a></td></tr></table><p>
-	Contact: Cluster Administration Team &lt;<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Cluster Administration Team consists of the people responsible for administering the machines that the Project relies on for its distributed work and communications to be synchronised. In this quarter, the team has worked on the following:
-</p>
-<ul>
-<li><p>Upgrade all ref- and universe- machines
-</p></li>
-<li><p>South Africa mirror (JINX) is online
-</p></li>
-<li><p>Package service of Seattle, USA mirror (TUK) is online
-</p></li>
-<li><p>Ongoing systems administration work:
-</p><ul>
-<li><p>Creating accounts for new committers.
-</p></li>
-<li><p>Backups of critical infrastructure.
-</p></li>
-<li><p>Keeping up with security updates in 3rd party software.
-</p>
-</li></ul>
-</li></ul>
-Work in progress:
-
-<ul>
-<li><p>Setup Malaysia (KUL) mirror
-</p></li>
-<li><p>Setup Brazil (BRA) mirror
-</p></li>
-<li><p>Setup Amsterdam (PKT) mirror
-</p></li>
-<li><p>Review the service jails and service administrators operation.
-</p></li>
-<li><p>Infrastructure of building aarch64 and powerpc64 packages
-</p><ul>
-<li><p>NVME issues on PowerPC64 Power9 blocking dual socket machine from being used as pkg builder.
-</p></li>
-<li><p>Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation.
-</p></li>
-<li><p>Boot issues with Aarch64 reference machines.
-</p></li></ul>
-</li><li><p>New NYI.net sponsored colocation space in Chicago-land area.
-</p></li>
-<li><p>Prepare resource for git working group
-</p></li>
-<li><p>Searching for more mirror providers
-</p><ul>
-<li><p>https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout
-</p></li>
-<li><p>https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror
-</p></li></ul>
-</li></ul>
-<hr /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://ci.FreeBSD.org/hwlab" title="https://ci.FreeBSD.org/hwlab">FreeBSD Hardware Testing Lab</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org/hwlab" title="FreeBSD Hardware Testing Lab">https://ci.FreeBSD.org/hwlab</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org" title="https://artifact.ci.FreeBSD.org">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org</a></td></tr><tr><td><a href="https://hackmd.io/@FreeBSD-CI" title="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackmd.io/@FreeBSD-CI" title="FreeBSD CI weekly report">https://hackmd.io/@FreeBSD-CI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="https://wiki.freebsd.org/3rdPartySoftwareCI">3rd Party Software CI</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="3rd Party Software CI">https://wiki.freebsd.org/3rdPartySoftwareCI</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="FreeBSD CI Repository">https://github.com/freebsd/freebsd-ci</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-ci channel on EFNet<br clear="none" />
-</p>
-<p>The FreeBSD CI team maintains the continuous integration system and related tasks
-for the FreeBSD project.  The CI system regularly checks the committed changes
-can be successfully built, then performs various tests and analysis of the
-results.  The artifacts from the build jobs are archived in the artifact server for
-further testing and debugging needs.  The CI team members examine the
-failing builds and unstable tests and work with the experts in that area to
-fix the codes or adjust test infrastructure.  The details of these efforts
-are available in the <a href="https://hackmd.io/@FreeBSD-CI" shape="rect">weekly CI reports</a>.
-</p>
-<p>During the first quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD.
-</p>
-<p>Important changes:
-</p><ul>
-<li><p>All the -head jobs are using clang/lld toolchain
-</p></li>
-<li><p>All the -head test are using kyua in the base
-</p></li>
-<li><p>RISC-V jobs now generate full disk image and run tests in QEMU with OpenSBI
-</p></li>
-<li><p>freebsd-doc job also checks building of www.freebsd.org
-</p>
-</li></ul>
-New jobs added:
-<ul>
-<li><p>https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/
-</p></li>
-<li><p>https://ci.freebsd.org/job/FreeBSD-head-powerpc64-images/
-</p></li>
-<li><p>https://ci.freebsd.org/job/FreeBSD-head-powerpc64-testvm/
-</p>
-</li></ul>
-Work in progress:
-<ul>
-<li><p>Collecting and sorting CI tasks and ideas <a href="https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo" shape="rect">here</a>
-</p></li>
-<li><p>Setup the CI stage environment and put the experimental jobs on it
-</p></li>
-<li><p>Implementing automatic tests on bare metal hardware
-</p></li>
-<li><p>Adding drm ports building test against -CURRENT
-</p></li>
-<li><p>Testing and merging pull requests in <a href="https://github.com/freebsd/freebsd-ci/pulls" shape="rect">the FreeBSD-ci repo</a>
-</p></li>
-<li><p>Planning for running ztest and network stack tests
-</p></li>
-<li><p>Helping more 3rd software get CI on FreeBSD through a hosted CI solution
-</p></li>
-<li><p>Adding non-x86 test jobs.
-</p></li>
-<li><p>Adding external toolchain related jobs.
-</p></li>
-<li><p>Adding more hardware to the hardware lab
-</p>
-</li></ul>
-Please see freebsd-testing@ related tickets for more WIP information, and join the efforts
-
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p><p>The Ports Management Team is responsible for overseeing the
-overall direction of the Ports Tree, building packages, and
-personnel matters.  Below is what happened in the last quarter.
-</p>
-<p>During the last quarter the number of ports settled in at 39,000.
-There are currently just over 2,400 open PRs of which 640 are
-unassigned.  The last quarter saw 8146 commits by 173 committers
-to the HEAD branch and 357 commits by 52 committers to the
-2020Q1 branch.  This means the number of PRs grew although the
-committer activity remained more or less constant.
-</p>
-<p>As always, people come and go. This time we welcomed Lo�c
-Bartoletti (lbartoletti@), Mikael Urankar (mikael@), Kyle Evans
-(kevans@, who is already a src committer), and Lorenzo Salvadore
-(salvadore@, who we already know for compiling these reports you
-are reading right now).  We said goodbye to dbn@ and theraven@,
-who we hope to see back in the future.
-</p>
-<p>On the infrastructure side, USES=qca was added and USES=zope was
-removed.  The latter was also due to it was incompatible with
-Python 3, and portmgr is in the process of removing Python 2.7 from
-the Ports Tree.  This means that all ports that currently rely on
-Python 2.7 need to be updated to work with Python 3 or be removed.
-</p>
-<p>After a long period of work by multiple people, Xorg got updated
-from the 1.18 to the 1.20 release series.  Also, the web browsers
-were updated: Firefox to version 75.0, Firefox ESR to 68.7.0, and
-Chromium to 80.0.3987.149.  The package manager itself got updated
-to version 1.13.2.
-</p>
-<p>antoine@ ran 29 exp-runs during the last quarter for various updates
-to KDE, poppler, pkg and build tools; and test compatibility with src
-changes: removing procfs-based debugging, fixing TLS alignment, and
-only including libssp_nonshared.a in libc for the i386 and Power
-architectures.
-</p><hr /><h2><a name="FreeBSD-Graphics-Team-status-report" href="#FreeBSD-Graphics-Team-status-report" id="FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop" title="https://github.com/FreeBSDDesktop">Project GitHub page</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop" title="Project GitHub page">https://github.com/FreeBSDDesktop</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:x11@freebsd.org">x11@freebsd.org</a>&gt;
-	<br />
-	Contact: Niclas Zeising &lt;<a href="mailto:zeising@freebsd.org">zeising@freebsd.org</a>&gt;
-	</p><p>The FreeBSD X11/Graphics team maintains the lower levels of the FreeBSD graphics
-stack.
-This includes graphics drivers, graphics libraries such as the
-MESA OpenGL implementation, the X.org xserver with related libraries and
-applications, and Wayland with related libraries and applications.
-</p>
-<p>The biggest highlight by far during the previous quarter was the long awaited
-update of <code>xorg-server</code> to version 1.20.
-After years of work by many people, this update finally landed in the form of
-<code>xorg-server</code> 1.20.7.
-With this update came a couple of new things, most notably, FreeBSD 12 and later
-was switched to use the udev/evdev backend by default for handling input
-devices, such as mice and keyboards.
-Together with this release, the OpenGL library implementation <code>mesa</code> was
-switched to use DRI3 by default, instead of the older DRI2.
-</p>
-<p>These updates caused some fallout when they first were comitted, most notably
-issues with keyboards.
-But with help from Michael Gmelin and others on the mailing lists, most issues
-were sorted fast.
-Unfortunately version 304 of the nVidia graphics driver is no longer supported
-as of this release.
-</p>
-<p>Since this update, xorg-server has also been bumped to 1.20.8, which is the
-latest upstream release.
-</p>
-<p>Apart from this update, there has also been ongoing work to keep the various
-drm-kmod ports and packages up to date, mostly in response to changes in FreeBSD
-CURRENT and to security issues found in the Intel i915 driver.
-</p>
-<p>We have also done updates as needed to keep the graphics and input stack up to
-date and working, and deprecated and removed several old and no longer used
-drivers, applications and libraries.
-</p>
-<p>We have also continued our regularly scheduled bi-weekly meetings.
-</p>
-<p>People who are interested in helping out can find us on the x11@FreeBSD.org
-mailing list, or on our gitter chat: (https://gitter.im/FreeBSDDesktop/Lobby).
-We are also available in #freebsd-xorg on EFNet.
-</p>
-<p>We also have a team area on GitHub where our work repositories can be found:
-(https://github.com/FreeBSDDesktop)
-</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="NFS-over-TLS-implementation" href="#NFS-over-TLS-implementation" id="NFS-over-TLS-implementation">NFS over TLS implementation</a></h2><p>
-	Contact: Rick Macklem &lt;<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>&gt;
-	</p><p>In an effort to improve NFS security, an internet draft
-which I expect will become and RFC soon specifies the
-use of TLS 1.3 to encrypt all data traffic on a Sun RPC
-connection used for NFS.
-</p>
-<p>Although NFS has been able to use sec=krb5p to encrypt data
-on the wire, this requires a Kerberos environment and, as
-such, has not been widely adopted. It also required that
-encryption/decryption be done in software, since only the
-RPC message NFS arguments are encrypted.
-Since Kernel TLS is capable of using hardware assist to
-improve performance and does not require Kerberos, NFS
-over TLS may be more widely adopted, once implementations
-are available.
-</p>
-<p>Since FreeBSD's kernel TLS requires that data be in ext_pgs
-mbufs for transmission, most of the work so far has been
-modifying the NFS code that builds the protocol arguments
-to optionally use ext_pgs mbufs.
-Coding changes to handle received ext_pgs mbufs has also
-been done, although this may not be required by the receive
-kernel TLS.
-</p>
-<p>The kernel RPC has also been modified to do the STARTTLS
-Null RPC and to do upcalls to userland daemons that
-perform the SSL_connect()/SSL_accept(), since the kernel
-TLS does not do this initial handshake.
-So far only a self signed certificate on the server,
-with no requirement for the client to have a certificate
-has been implemented.
-</p>
-<p>Work is still needed to be done for the case where the NFS
-client is expected to have a signed certificate. In particular,
-it is not obvious to me what the correct solution is for
-clients that do not have a fixed IP address/DNS name.
-The code now is about ready for testing, but requires that
-the kernel TLS be able to support receive as well as transmit.
-Patches to the kernel TLS for receive are being worked on
-by jhb@freebsd.org.
-</p>
-<p>Once receive side kernel TLS becomes available, the code in
-subversion under base/projects/nfs-over-tls will need third
-party testing and a security evaluation by someone familiar
-with TLS.
-</p>
-<hr /><h2><a name="Import-of-the-Kyua-test-framework" href="#Import-of-the-Kyua-test-framework" id="Import-of-the-Kyua-test-framework">Import of the Kyua test framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/TestSuite" title="https://wiki.freebsd.org/TestSuite">The FreeBSD Test Suite</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/TestSuite" title="The FreeBSD Test Suite">https://wiki.freebsd.org/TestSuite</a></td></tr></table><p>
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD test suite uses the Kyua test framework to run tests.
-</p>
-<p>Historically Kyua has been installed from the ports collection
-(<code>devel/kyua</code>).  While this is fine for mainstream architectures,
-it can pose bootstrapping issues on new architectures and package
-installation is quite slow under emulation or on FPGA based systems.
-By including it in the FreeBSD base system we can avoid these issues.
-</p>
-<p>We hope that this inclusion will spur testing of embedded platforms
-and simplify the process of testing within continuous integration
-systems.
-</p>
-<p>We currently plan to retain the <code>devel/kyua</code> port to serve FreeBSD
-versions without and to serve as a development version.
-</p>
-<p>Sponsor: DARPA
-</p><hr /><h2><a name="Linux-compatibility-layer-update" href="#Linux-compatibility-layer-update" id="Linux-compatibility-layer-update">Linux compatibility layer update</a></h2><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p><p>Work during this quarter focused on source code cleanup and making
-it easier to debug missing functionality.  There were, however,
-some user-visible changes: added support for <code>TCP_CORK</code> as required by Nginx,
-added support <code>MAP_32BIT</code> flag, which fixes Mono binaries from Ubuntu Bionic,
-and a fix for DNS resolution with glibc newer than 2.30, which affected
-CentOS 8.
-</p>
-<p>The Linux Test Project tests that are being run as part of the
-the <a href="https://ci.FreeBSD.org" shape="rect">FreeBSD Continuous Integration infrastructure</a>
-now include the Open POSIX test suite.
-</p>
-<p>There's still a lot to do:
-</p>
-<ul>
-<li><p>There are pending reviews for patches that add
-   <a href="https://reviews.freebsd.org/D13209" shape="rect">extended attributes support</a>,
-   and <a href="https://reviews.freebsd.org/D10275" shape="rect">fexecve(2) syscall</a>, and
-   they require wrapping up and committing
-</p>
-</li>
-<li><p>There are over <a href="https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/" shape="rect">400 failing LTP tests</a>.
-   Some of them are false positives, some are easy to fix bugs, and some require adding
-   new system calls.  Any help is welcome.
-</p>
-</li></ul>
-Sponsor: The FreeBSD Foundation
-<hr /><h2><a name="syzkaller-on-FreeBSD" href="#syzkaller-on-FreeBSD" id="syzkaller-on-FreeBSD">syzkaller on FreeBSD</a></h2><p>
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Michael Tuexen &lt;<a href="mailto:tuexen@FreeBSD.org">tuexen@FreeBSD.org</a>&gt;
-	</p><p>See the syzkaller entry in the 2019q1 quarterly report for an
-introduction to syzkaller.
-</p>
-<p>A number of kernel bugs have been found by syzkaller and fixed this
-quarter, mostly in the network stack and file descriptor table code.
-Bug investigations have led to improvements in debugging facilities and
-assertions, for example in the SCTP stack.  Syzkaller reproducers have
-been added to Peter Holm's stress2 suite, helping ensure that
-regressions are found quickly.
-</p>
-<p>The syzkaller instance hosted by backtrace.io (see the 2019q3 report)
-has been very useful in testing syzkaller improvements and finding bugs.
-Though Google runs a dedicated syzkaller instance <a href="https://syzkaller.appspot.com/freebsd" shape="rect">targeting FreeBSD</a>,
-it has proved fruitful to run multiple instances since they end up
-building different corpuses and thus discover different, though
-overlapping, sets of bugs.
-</p>
-<p>Support for fuzzing a number of new system calls has been added,
-including the new copy_file_range() and __realpathat() system calls,
-and the Capsicum system calls.  Some work was also done to audit
-existing system call definitions to ensure that FreeBSD-specific
-extensions of POSIX system calls are covered.  Work is ongoing to target
-the Linux emulation layer, and to collect kernel dumps so that one-off
-crashes with no reproducer have a chance at being diagnosed and fixed.
-</p>
-<p>Sponsor: backtrace.io
-Sponsor: The FreeBSD Foundation
-</p>
-<hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><h2><a name="if_bridge" href="#if_bridge" id="if_bridge">if_bridge</a></h2><p>
-	Contact: Kristof Provost &lt;<a href="mailto:kp@FreeBSD.org">kp@FreeBSD.org</a>&gt;
-	</p><p>The current implementation of if_bridge uses a single mutex to protect its
-internal data structures. As a result it&#8217;s nowhere near as fast as it could be.
-This is relevant for users who want to run many vnet jails or virtual machines
-bridged together, for example.
-</p>
-<p>As part of this project several new tests have already been added for
-if_bridge. These are generally very useful for validating any locking changes,
-and will also help to prevent regressions for other future changes.  These
-tests live in /usr/tests/sys/net/if_bridge_test.
-</p>
-<p>The current work is concentrating on investigating if it's possible to leverage
-the ConcurrencyKit epoch code for the datapath (i.e. <code>bridge_input()</code>,
-<code>bridge_output()</code>, <code>bridge_forward()</code>, ...).
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="sigfastblock(2)" href="#sigfastblock(2)" id="sigfastblock(2)">sigfastblock(2)</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p><p>Rtld services need to be async signal safe.  This is needed, for
-instance, to provide working symbol bindings in signal handlers.
-</p>
-<p>For threaded processes, libthr interposes all user-installed signal
-handlers and saves the signals and related context if signal is
-delivered while rtld or libthr are in protected section of code.
-</p>
-<p>In non-threaded processes, the async safety is provided by changing
-signal mask for the thread.  It is actually better than the
-interposing done by libthr, since signals are delivered in the right
-context, instead of libthr attempt of recreate it later.  But the
-unfortunate side-effect is that each rtld entry requires two syscalls,
-one to set mask, and one to restore it.  Typically this adds around 40
-or more syscalls on each process startup.  Worse, rtld services used
-by typical language runtime exception handling systems also have the
-cost of signal mask manipulation.
-</p>
-<p>The new sigfastblock(2) syscall was added that allows thread to
-designate a memory location as fast signal block.  If this word
-contains non-zero value, kernel interprets the thread state same as if
-all blockable signals are blocked.  The facility drastically improves
-exception handling speed on FreeBSD.
-</p>
-<p>Since signals might abort interruptible sleeps, initial implementation
-read the blocking word on each syscall entry.  This is needed to
-ensure that userspace does not see spurious EINTR/ERESTART if the
-signals are blocked by the word.  Since if kernel cached outdated
-value for the block word, it would abort sleep, but then ast sees the
-correct mask and does not deliver the pending signal.
-</p>
-<p>There were concerns that this read of the word causes slowdown in
-syscalls microbenchmarks, esp. on machines with SMAP.  The reason is
-that SMAP requires all userspace access bracketed by STAC/CLAC pair of
-instructions, which are de-facto serializing (this is not
-architectural, but all current microarchitectures do it).  The
-decision was made to eliminate the word read, at the cost of possibly
-returning spurious EINTR.  The impact should be minimal, since
-sigfastblock(2) is not supposed to be the service available to users,
-it is only assumed for rtld and libthr implementations.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="arm64-LSE-atomic-instructions" href="#arm64-LSE-atomic-instructions" id="arm64-LSE-atomic-instructions">arm64 LSE atomic instructions</a></h2><p>
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	</p><p>An investigation of some performance oddities on EC2 Graviton 2
-instances resulted in support for the use of Large System Extension
-(LSE) atomic instructions in the FreeBSD kernel.
-</p>
-<p>LSE is an mandatory ISA extension specified in ARMv8.1.  It consists of
-a number of new atomic instructions, superseding the
-Load-Linked/Store-Conditional (LL/SC) instruction pairs use when LSE is
-not implemented.  The extension is present in a number of ARMv8 server
-platforms, including the Cavium ThunderX2 and AWS Graviton 2.  The new
-instructions provide significantly better scalability.
-</p>
-<p>A recent set of patches modified the FreeBSD kernel to detect support
-for LSE and dynamically select an atomic(9) implementation based on
-the new instructions when all CPUs implement the extension.  The initial
-atomic(9) implementations were provided by Ali Saidi.  Some benchmarking
-on a 64-vCPU Graviton 2 instance shows a ~4% reduction in wall clock
-time for a kernel build, and a ~15% reduction in system CPU time.
-</p>
-<p>Some ARMv8 multi-processor systems implement a heterogenous CPU
-architecture, referred to as big.LITTLE, in which multiple processor
-types are used.  Surprisingly, such systems may implement the LSE on
-only a subset of its CPUs, in which case LSE instructions cannot be used
-by the kernel.  As a result, FreeBSD currently waits until all
-processors are online before selecting the atomic(9) implementation,
-which precludes the use of ifuncs to provide dynamic selection.
-</p>
-<p>Currently atomic(9)'s use of LSE is limited to the kernel.  A future
-project would extend this to userspace, so that FreeBSD system libraries
-can leverage the LSE instructions when they are available.
-</p>
-<p>Sponsor:	The FreeBSD Foundation
-Sponsor:	Amazon
-</p><hr /><h2><a name="FreeBSD-on-Microsoft-HyperV-and-Azure" href="#FreeBSD-on-Microsoft-HyperV-and-Azure" id="FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/MicrosoftAzure" title="https://wiki.freebsd.org/MicrosoftAzure">FreeBSD on MicrosoftAzure wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/MicrosoftAzure" title="FreeBSD on MicrosoftAzure wiki">https://wiki.freebsd.org/MicrosoftAzure</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HyperV" title="https://wiki.freebsd.org/HyperV">FreeBSD on Microsoft HyperV</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HyperV" title="FreeBSD on Microsoft HyperV">https://wiki.freebsd.org/HyperV</a></td></tr></table><p>
-	Contact: FreeBSD Integration Services Team &lt;<a href="mailto:bsdic@microsoft.com">bsdic@microsoft.com</a>&gt;
-	<br />
-	Contact: Wei Hu &lt;<a href="mailto:whu@FreeBSD.org">whu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>Wei is working on HyperV Socket support for FreeBSD.  HyperV Socket provides a way for the HyperV host and guest to communicate using a common socket interface without networking required.  Some features in Azure require HyperV Socket support in the guest.
-</p>
-<p>Details of HyperV Socket is available <a href="https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service" shape="rect">here</a>.
-</p>
-<p>The work-in-progress is available <a href="https://reviews.freebsd.org/D24061" shape="rect">here</a>
-</p>
-<p>This project is sponsored by Microsoft.
-</p>
-<p>Li-Wen is working on the FreeBSD release code related to Azure for the -CURRENT and 12-STABLE branches.  The release of 12.1-RELEASE on Azure is also in progress.
-</p>
-<p>The work-in-progress is available <a href="https://reviews.freebsd.org/D23804" shape="rect">here</a>
-</p>
-<p>This project is sponsored by The FreeBSD Foundation.
-</p><hr /><h2><a name="FreeBSD-on-the-ARM-Morello-platform" href="#FreeBSD-on-the-ARM-Morello-platform" id="FreeBSD-on-the-ARM-Morello-platform">FreeBSD on the ARM Morello platform</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html" title="https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html">The Arm Morello Board</a></td><td>
-	    URL: <a href="https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html" title="The Arm Morello Board">https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html</a></td></tr><tr><td><a href="https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/" title="https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/">The CHERI Project</a></td><td>
-	    URL: <a href="https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/" title="The CHERI Project">https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/</a></td></tr></table><p>
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: John Baldwin &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	</p><p>CHERI (Capability Hardware Enhanced RISC Instructions) extends
-conventional hardware Instruction-Set Architectures (ISAs) with new
-architectural features to enable fine-grained memory protection and
-highly scalable software compartmentalization. The CHERI
-memory-protection features allow historically memory-unsafe programming
-languages such as C and C++ to be adapted to provide strong, compatible,
-and efficient protection against many currently widely exploited
-vulnerabilities. The CHERI scalable compartmentalization features enable
-the fine-grained decomposition of operating-system (OS) and application
-code, to limit the effects of security vulnerabilities in ways that are
-not supported by current architectures. CHERI is a hybrid capability
-architecture in that it is able to blend architectural capabilities with
-conventional MMU-based architectures and microarchitectures, and with
-conventional software stacks based on virtual memory and C/C++. This
-approach allows incremental deployment within existing ecosystems, which
-we have demonstrated through hardware and software prototyping.
-</p>
-<p>On 18 October 2019, Arm announced Morello, an experimental
-CHERI-extended, multicore, superscalar ARMv8-A processor, System-on-Chip
-(SoC), and prototype board to be available from late 2021. Morello is a
-part of the UKRI �187M Digital Security by Design Challenge (DSbD)
-supported by the UK Industrial Strategy Challenge Fund, including a
-commitment of over �50M commitment by Arm.  The aim is to test and
-validate CHERI extensions to the Arm ISA at scale with the idea that
-"successful concepts are expected to be carried forward into the
-architecture."  The Morello board is scheduled to ship in the third
-quarter of 2021.
-</p>
-<p>Over the past decade we have developed CheriBSD, a version of FreeBSD
-supporting CHERI.  Our public facing work has been performed on MIPS64
-and more recently on RISC-V.  Andrew has also developed a port to an
-earlier version of the Morello ISA which we will be merging into
-our public repository as simulators and compilers become available.
-</p>
-<p>The Morello board is based on the Arm Neoverse N1 platform and derived
-from the N1SDP development platform.  (The AWS Graviton2 systems are
-also based on the N1 core.)  Ruslan and Andrew are currently
-working to enable all relevant features of the N1 and the N1SDP to give
-us a solid baseline for work on Morello.  These features include the
-PCI root complex, system memory management unit (SMMU), and CoreSight.
-To the extent practical we are upstreaming these features to FreeBSD.
-</p>
-<p>Sponsor: DARPA, UKRI
-</p><hr /><h2><a name="NXP-ARM64-SoC-support" href="#NXP-ARM64-SoC-support" id="NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></h2><p>
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	<br />
-	Contact: Dawid Gorecki &lt;<a href="mailto:dgr@semihalf.com">dgr@semihalf.com</a>&gt;
-	</p><p>The Semihalf team initiated working on FreeBSD support for the
-<a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A" shape="rect">NXP LS1046A SoC</a>
-</p>
-<p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with
-integrated packet processing acceleration and high speed peripherals
-including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide
-range of networking, storage, security and industrial applications.
-</p>
-<p>Completed since the last update:
-</p><ul>
-<li><p>Clean-up and rebase support on top of FreeBSD-HEAD. Prepare features
-    for the upstream submission:
-</p><ul>
-<li><p>QorIQ platform clockgen driver
-</p></li>
-<li><p>LS1046A clockgen driver
-</p></li>
-<li><p>GPIO support for QorIQ boards
-</p></li>
-<li><p>QorIQ LS10xx AHCI driver
-</p></li>
-<li><p>VF610 I2C controller support
-</p></li>
-<li><p>TCA6416 GPIO expander
-</p></li>
-<li><p>Epson RX-8803 RTC
-</p></li>
-<li><p>QorIQ LS10xx SDHCI driver
-</p>
-</li></ul>
-</li></ul>
-Todo:
-<ul>
-<li><p>Upstreaming of developed features. This work is expected to
-     be submitted/merged to HEAD in the Q2 of 2020.
-</p>
-</li></ul>
-Sponsor: Alstom Group
-
-<hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Maciej Bielski &lt;<a href="mailto:mba@semihalf.com">mba@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p><p>ENA (Elastic Network Adapter) is the smart NIC available in the
-virtualized environment of Amazon Web Services (AWS). The ENA
-driver supports multiple transmit and receive queues and can handle
-up to 100 Gb/s of network traffic, depending on the instance type
-on which it is used.
-</p>
-<p>Completed since the last update:
-</p><ul>
-<li><p>Upstream of the driver to v2.1.1, introducing:
-</p><ul>
-<li><p>Bug fix for LLQ mode which was causing race when multiple IO queues were
-      used
-</p>
-</li></ul>
-</li></ul>
-Work in progress:
-<ul>
-<li><p>Last touches for ENA v2.2.0 release, introducing:
-</p><ul>
-<li><p>Add driver support for the upcoming HW features (like Rx offsets,
-      reporting Tx drops)
-</p></li>
-<li><p>Add sysctl tuneables for IO queue number
-</p></li>
-<li><p>Create IO queues with optional size backoff
-</p></li>
-<li><p>Rework the way of configration of drbr and Rx ring size to be more robust
-      and stable
-</p></li>
-<li><p>New HAL version
-</p></li>
-<li><p>Other minor fixes and improvements
-</p>
-</li></ul>
-</li></ul>
-Sponsor: Amazon.com Inc
-<hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="FreeBSD/powerpc-Project" href="#FreeBSD/powerpc-Project" id="FreeBSD/powerpc-Project">FreeBSD/powerpc Project</a></h2><p>
-	Contact: Mark Linimon &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Justin Hibbits &lt;<a href="mailto:jhibbits@FreeBSD.org">jhibbits@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Piotr Kubaj &lt;<a href="mailto:pkubaj@FreeBSD.org">pkubaj@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD/powerpc project continues to mature.
-</p>
-<p>In addition to the above listed people, we want to acknowledge
-contributions from adalava, bdragon, luporl, and mikael, among
-others.
-</p>
-<p>Key points:
-</p>
-<ul>
-<li><p>On -CURRENT, all platforms have been switched to the
-    LLVM 10.0 compiler and lld10.  Thus, ld.bfd has been removed
-    from base.
-</p></li>
-<li><p>On powerpc64, -CURRENT has been switched to the ELFv2 ABI.
-    Older versions of -CURRENT that either used GCC, or LLVM with
-    the ELFv1 ABI, are no longer supported.
-</p></li>
-<li><p>On powerpc64 FreeBSD-STABLE (11 and 12), the platforms still
-    remain on the antique gcc4.2.1 in base.  Note: that version of
-    GCC has been removed from the -CURRENT src tree.  Support for
-    this configuration is now a "best-effort" status.
-</p></li>
-<li><p>On powerpc (32-bit), the ABI did not change as with powerpc64,
-    so upgrading should be easier than with powerpc64.
-</p>
-</li></ul>
-Hardware status:
-
-<ul>
-<li><p>The aacraid(4) driver has been been fixed for big-endian, thanks
-    to luporl.  This means that Talos customers who got the SAS option
-    can now use the onboard SAS.
-</p></li>
-<li><p>The ixl(4) driver has also been fixed for big-endian, also thanks
-    to luporl.
-</p>
-</li></ul>
-Software status:
-
-<ul>
-<li><p>As a result of -CURRENT switching to LLVM/ELFv2, ifuncs became
-    available, meaning that we now have optimized memcpy/bcopy and
-    strncpy functions when running on processors that supports VSX
-    instructions.
-</p></li>
-<li><p>powerpc64 is now able to run on QEMU without the need of
-    Huge Pages support.
-</p></li>
-<li><p>The virtio drivers have been fixed.
-</p></li>
-<li><p>kernel minidump has been fixed.
-</p>
-</li></ul>
-Package status:
-
-<ul>
-<li><p>A FreeBSD.org package set is available for powerpc64/12
-    (quarterly).  The -quarterly build has just been rebased
-    from 12.0 to 12.1, per the desupport of the older 12.0.
-    The first rebased build has been completed, with 29776
-    packages being available.
-</p></li>
-<li><p>We are currently working on the upgrade of the package
-    builder to a recent -CURRENT.  Therefore, the available
-    packages for -CURRENT are still ELFv1, which are not useful.
-    Please contact Mark Linimon for more information.
-</p></li>
-<li><p>mesa has been switched to llvm90, which fixes certain
-    problems.
-</p></li>
-<li><p>Work continues on firefox and related ports.
-</p></li>
-<li><p>More ports fixes are being committed every day.
-</p>
-</li></ul>
-The team would like to thank IBM for the loan of two POWER8 and one
-<p>POWER9 machines, and Oregon State University (OSU) for providing the
-hosting.  As well, we would like to thank the clusteradm team for
-keeping the Tyan POWER8 machines online that are hosted at
-<a href="https://www.nyi.net" shape="rect">NYI</a>.
-</p>
-<p>Also, Piotr would like to thank the FreeBSD Foundation for
-funding his personal Talos, and Raptor (via its IntegriCloud
-subsidiary) for loaning a server on which talos.anongoth.pl runs.
-</p><hr /><h2><a name="FreeBSD/RISC-V-Project" href="#FreeBSD/RISC-V-Project" id="FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/riscv" title="https://wiki.freebsd.org/riscv">Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/riscv" title="Wiki">https://wiki.freebsd.org/riscv</a></td></tr></table><p>
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mitchell Horne &lt;<a href="mailto:mhorne@FreeBSD.org">mhorne@FreeBSD.org</a>&gt;
-	<br />
-	Contact: John Baldwin &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Kristof Provost &lt;<a href="mailto:kp@FreeBSD.org">kp@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Philip Paeps &lt;<a href="mailto:philip@FreeBSD.org">philip@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-riscv" shape="rect">freebsd-riscv Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-riscv channel on freenode<br clear="none" />
-</p>
-<p>It has been a year since the RISC-V project's last status report. In that time,
-the RISC-V port has benefited from increased attention, and received
-improvements of all kinds.
-</p>
-<p>The RISC-V project has brought in two new src committers. We'd like to welcome
-Jessica Clarke (jrtc27@), who is a member of CheriBSD, and Nick O'Brien (nick@)
-of Axiado to the team.
-</p>
-<p>Some highlights from last year:
-</p><ul>
-<li><p>Bring-up on SiFive's Hifive Unleashed board
-</p></li>
-<li><p>Support for the OpenSBI firmware and version 0.2 of the SBI specification
-</p></li>
-<li><p>Addition of the UART, SPI, and PRCI device drivers for the HiFive Unleashed
-</p>
-</li></ul>
-Last quarter, the default compiler and linker was switched to clang/lld. This
-<p>required a small number of integration changes on our side, but was mainly
-enabled by the upstream improvements to the RISC-V LLVM back-end. LLVM's RISC-V
-support became "official" <a href="https://lists.llvm.org/pipermail/llvm-dev/2019-September/135304.html" shape="rect">with LLVM 9</a>, and LLVM 10 has brought further
-improvements. The LLVM back-end is expected to continue to mature, as there are
-now many parties actively involved in its development. GCC remains supported as
-an external toolchain for RISC-V.
-</p>
-<p>The <a href="https://ci.freebsd.org/job/FreeBSD-head-riscv64-build/" shape="rect">CI job for HEAD</a>
-has been updated to use the clang/lld toolchain, and a GCC job will be added in the future.
-The RISC-V disk image built in the CI system now contains the full base system and
-is available on the <a href="https://artifact.freebsd.org" shape="rect">CI artifact server</a> for
-further testing.  The CI test job was updated to use OpenSBI in qemu. Work on
-running the FreeBSD test suite for RISC-V in the CI system is in progress.
-</p>
-<p>Some progress has been made on supporting the ports framework on RISC-V, which
-was mostly untested until recently. First,
-<code>emulators/qemu-user-static-devel</code> received an update adding support for the
-RISC-V 64-bit ABI, allowing ports to be cross-compiled via <code>poudiere(8)</code>.
-Second, improvements were made to the detection of the soft-float ABI,
-riscv64sf. Systems running either of the hard-float or soft-float ABIs can now
-compile and run ports natively. At the moment a small subset of ports can be
-built successfully, and in the coming months we will look to improve that to
-include a base set of crucial ports (e.g. python or perl).
-</p>
-<p>The CheriBSD project saw an initial port to RISC-V this quarter. Preliminary
-support for the CHERI ISA has been added to the Spike and QEMU emulators, as
-well as the necessary changes on the CheriBSD side. Currently, the CheriBSD
-RISC-V kernel boots, and most statically compiled CHERI binaries run without
-issue.
-</p>
-<p>Although real RISC-V hardware is still scarce, any users with an interest
-trying out or contributing to the RISC-V port are encouraged to do so. Please
-visit the recently updated wiki page for information on getting set up, or check
-out "Getting Started with FreeBSD/RISC-V" in the January/February edition of The
-FreeBSD Journal.
-</p>
-<p>Sponsor: DARPA, AFRL, Axiado, the FreeBSD Foundation
-</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><h2><a name="GCC-4.2.1-Retirement" href="#GCC-4.2.1-Retirement" id="GCC-4.2.1-Retirement">GCC 4.2.1 Retirement</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	<br />
-	Contact: Warner Losh &lt;<a href="mailto:imp@freebsd.org">imp@freebsd.org</a>&gt;
-	</p><p>In 2007 the GNU Compiler Collection (GCC) migrated to GPLv3, which
-prompted discussions about the future of the FreeBSD tool chain.  We held
-a <a href="https://wiki.freebsd.org/201005ToolchainSummit" shape="rect">Tool Chain Summit</a> at
-BSDCan 2010.  Roman Divacky gave an update on the ClangBSD project, building
-FreeBSD using the new and rapidly improving Clang compiler.
-</p>
-<p>Since that time Clang was imported into the FreeBSD base system and was used
-more and more widely - first being installed but not the default <code>cc</code>, then
-used by default on i386 and amd64, and later used on more and more targets.
-In the years since Dimitry Andric has been keeping our copy of Clang
-up-to-date.
-</p>
-<p>GCC 4.2.1 was kept in the tree for a few FreeBSD targets that hadn't migrated
-to Clang, such as MIPS and Sparc64.  By early this year all remaning targets
-had migrated to external toolchain (contemporary GCC from ports or packages),
-or had been deprecated.
-</p>
-<p>With no in-tree consumers remaining, GCC 4.2.1 was removed from FreeBSD in
-<a href="https://svnweb.freebsd.org/changeset/base/358454" shape="rect">r358454</a> on February 29,
-2020.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="elfctl-utility" href="#elfctl-utility" id="elfctl-utility">elfctl utility</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	</p><p>In <a href="https://reviews.freebsd.org/rS340076" shape="rect">r340076</a> Ed added the
-<i>NT_FREEBSD_FEATURE_CTL</i> ELF note, used to allow binaries to opt out of,
-or in to, vulnerability mitigation and other features.  FreeBSD Foundation
-intern Bora �zarslan later added a tool to decode and modify the ELF note,
-but it had yet to be installed by default.
-</p>
-<p>In the previous quarter Ed renamed the tool to <i>elfctl</i>, and installed it
-in /usr/bin.  Ed also committed a number of minor bug fixes, code style
-improvements, etc.
-</p>
-<p>Usage examples - list known feature flags:
-<pre xml:space="preserve"><code>
-$ elfctl -l
-Known features are:
-aslr            Disable ASLR
-protmax         Disable implicit PROT_MAX
-stackgap        Disable stack gap
-wxneeded        Requires W+X mappings
-</code></pre>
-</p>
-<p>List feature tags set on a binary:
-<pre xml:space="preserve"><code>
-$ elfctl /bin/ls
-File '/bin/ls' features:
-aslr            'Disable ASLR' is unset.
-protmax         'Disable implicit PROT_MAX' is unset.
-stackgap        'Disable stack gap' is unset.
-wxneeded        'Requires W+X mappings' is unset.
-</code></pre>
-</p>
-<p>Indicate that a binary requests to opt-out of address randomization:
-<pre xml:space="preserve"><code>
-$ elfctl -e +aslr binary
-</code></pre>
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="ELF-Tool-Chain" href="#ELF-Tool-Chain" id="ELF-Tool-Chain">ELF Tool Chain</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	</p><p>A number of performance and functional improvements were committed to ELF
-Tool Chain tools over the last quarter.
-</p>
-<p>FreeBSD Foundation intern Tiger Gao added DWARF Debug Information Entry
-(DIE) caching to addr2line which provided a substantial improvement when
-translating many entries (even surpassing GNU addr2line with a large list).
-</p>
-<p>Tiger also rebased and updated an upstream ELF Tool Chain submission to
-handle <i>DW_AT_ranges</i> and addressed two elfcopy/objcopy bugs: setting the
-OS/ABI field correctly when converting a binary file to ELF, and correctly
-adding new sections when there is no <i>.shstrtab</i> section.
-</p>
-<p>Ed committed several readelf improvements, including decoding the
-<i>PROTMAX_DISABLE</i>, <i>STKGAP_DISABLE</i>, and <i>WXNEEDED</i> ELF feature control
-flags, decoding Xen and GNU Build-ID ELF notes, and improved input
-validation.
-</p>
-<p>Mark Johnston addressed many memory and file descriptor leaks and similar
-issues reported by Coverity Scan.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://community.kde.org/FreeBSD" title="https://community.kde.org/FreeBSD">KDE Community FreeBSD</a></td><td>
-	    URL: <a href="https://community.kde.org/FreeBSD" title="KDE Community FreeBSD">https://community.kde.org/FreeBSD</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p><p>The <i>KDE on FreeBSD</i> project packages the software produced by
-the KDE Community for FreeBSD. The software includes a
-full desktop environment KDE Plasma, the art application
-<a href="https://krita.org/" shape="rect">Krita</a>, video editor <a href="https://kdenlive.org" shape="rect">Kdenlive</a>
-and hundreds of other applications that can be used on
-any FreeBSD desktop machine.
-</p>
-<p>The quarter opened with a new kstars (amateur astronomy application)
-release landing in ports, and then had the usual regular updates:
-</p>
-<ul>
-<li><p>three KDE Frameworks releases (on a monthly schedule),
-</p></li>
-<li><p>three bugfix releases to the collection of KDE software from
-  the KDE release service (formerly <i>KDE Applications</i>, but it was
-  always more that only-applications),
-</p></li>
-<li><p>three bugfix releases to the KDE Plasma desktop.
-</p>
-</li></ul>
-There were no substantial Qt updates but four bugfix releases for
-<p><code>devel/cmake</code>, and regular work all over the ports tree.
-</p>
-<p>The SDDM login manager was updated to a much newer -- by over a year --
-release and patched to support more FreeBSD features.
-</p>
-<p>One update to <code>devel/qca</code> dropped compatibility with FreeBSD 11
-because upstream no longer supports older OpenSSL versions.
-There is infrastructure in the ports tree now that adds a <code>USES=qca</code>
-for Qt applications needing crypto support.
-</p>
-<p>The <a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=New&amp;bug_status=Open&amp;bug_status=In%20Progress&amp;bug_status=UNCONFIRMED&amp;email1=kde%40FreeBSD.org&amp;emailassigned_to1=1&amp;emailtype1=substring&amp;f0=OP&amp;f1=OP&amp;f2=product&amp;f3=component&amp;f4=alias&amp;f5=short_desc&amp;f7=CP&amp;f8=CP&amp;f9=assigned_to&amp;j1=OR&amp;j_top=OR&amp;o2=substring&amp;o3=substring&amp;o4=substring&amp;o5=substring&amp;o9=substring&amp;query_format=advanced&amp;v2=kde%40&amp;v3=kde%40&amp;v4=kde%40&amp;v5=kde%40&amp;v9=kde%40&amp;human=1" shape="rect">open bugs list</a>
-remains stable around 28 open issues,
-with some interesting xkb issues as a highlight.
-We welcome detailed bug reports
-and patches. KDE packaging updates are prepared in
-a <a href="https://github.com/freebsd/freebsd-ports-kde/" shape="rect">copy of the ports repository</a>
-on GitHub and then merged in SVN. We welcome pull requests
-there as well.
-</p>
-<hr /><h2><a name="XFCE" href="#XFCE" id="XFCE">XFCE</a></h2><p>
-	Contact: Guido Falsi &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	</p><p>After the XFCE update to 4.14 a regression was observed in the XFCE
-window manager xfwm4. It caused window decorations to be drawn wrong
-or missing with certain graphic hardware setups. It has been reported
-that the recent update to Xorg server in the ports tree fixes this
-issue.  The updated Xorg server will be available in the next
-qurterly branch.
-</p><hr /><h2><a name="Wine-on-FreeBSD" href="#Wine-on-FreeBSD" id="Wine-on-FreeBSD">Wine on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.winehq.org" title="https://www.winehq.org">Wine homepage</a></td><td>
-	    URL: <a href="https://www.winehq.org" title="Wine homepage">https://www.winehq.org</a></td></tr></table><p>
-	Contact: Gerald Pfeifer &lt;<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Lorenzo Salvadore &lt;<a href="mailto:salvadore@FreeBSD.org">salvadore@FreeBSD.org</a>&gt;
-	</p><p>The standard Wine port has moved from Wine 4.0.3 to Wine 5.0 which
-represents over 7,400 individual changes including built-in modules in
-PE format, multi-monitor support, Vulkan 1.1 support, and an XAudio2
-re-implementation.
-</p>
-<p>After our request for help in the last quarterly report the i386 wine
-ports have been adopted by salvadore who immediately started resolving
-existing bugs and improving the ports. Most of this work is ready and we
-began committing first pieces in March. Since it takes more time than
-initially expected, we will also update the i386-wine-devel port during
-this process so that users needing a more recent version can easily get it
-from the ports tree (or binary packages). On the other hand, we plan on
-backporting  these improvements to i386-wine after i386-wine-devel is done
-and only then update that port, so that we always guarantee a stable
-version of i386-wine.
-</p><hr /><h2><a name="Go-on-freebsd/arm64" href="#Go-on-freebsd/arm64" id="Go-on-freebsd/arm64">Go on freebsd/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://golang.org/doc/go1.14#freebsd" title="https://golang.org/doc/go1.14#freebsd">Go 1.14 Release Notes</a></td><td>
-	    URL: <a href="https://golang.org/doc/go1.14#freebsd" title="Go 1.14 Release Notes">https://golang.org/doc/go1.14#freebsd</a></td></tr></table><p>
-	Contact: Mika�l Urankar &lt;<a href="mailto:mikael@FreeBSD.org">mikael@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Dmitri Goutnik &lt;<a href="mailto:dmgk@FreeBSD.org">dmgk@FreeBSD.org</a>&gt;
-	</p><p>Starting from the recently released version 1.14, Go now officially supports
-64-bit ARM architecture on FreeBSD 12.0 or later.
-This porting effort was initially started by Greg V (aka myfreeweb) and resumed
-by Shigeru Yamamoto, Dmitri Goutnik and Mika�l Urankar.
-Dmitry has set up a CI builder to catch regression on FreeBSD aarch64 (it's
-required by the golang policy for adding a new port to the main Go repository)
-</p>
-<p>Work in progress:
-</p><ul>
-<li><p>a lot of ports use an old version of golang.org/x/sys or golang.org/x/net
-  (to name a few) that doesn't contain the FreeBSD aarch64 bits,
-  work is being done to fix these ports (details are in the <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242312)" shape="rect">bug tracker entry</a>
-</p></li></ul>
-<hr /><h2><a name="sysctlmibinfo2-API" href="#sysctlmibinfo2-API" id="sysctlmibinfo2-API">sysctlmibinfo2 API</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/alfix/sysctlmibinfo2" title="https://gitlab.com/alfix/sysctlmibinfo2">sysctlmibinfo2</a></td><td>
-	    URL: <a href="https://gitlab.com/alfix/sysctlmibinfo2" title="sysctlmibinfo2">https://gitlab.com/alfix/sysctlmibinfo2</a></td></tr></table><p>
-	Contact: Alfonso Sabato Siciliano &lt;<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>&gt;
-	</p><p>In the previous third and fouth quarterly status reports 2019, the sysctlinfo
-interface and an extension to improve the sysctlbyname() syscall were described,
-they can access to the sysctl MIB and pass the properties of an object to the
-userland, but both are quite low level and kernel related.
-</p>
-<p>The sysctlmibinfo2 library provides an API to explore the sysctl MIB, to convert
-an object name in its corresponding Object Identifier and to find an object to
-get its properties, therefore it is useful to handle an object correctly and to
-build a sysctl-like utility.
-</p>
-<p>Primarily sysctlmibinfo2 wraps the low level interface to provide an easy API,
-some example: sysctlmif_desc() retrieves the description of an object,
-sysctlmif_kind() gets the type (string, integer, etc) and sysctlmif_fmt()
-specifies the format (an integer could represent a deciKelvin, milliKelvin,
-etc), then it is possible to print properly an object value.
-</p>
-<p>Moreover sysctlmibinfo2 provides a high level API: a struct sysctlmif_object
-definition and functions to build data structures of objects.
-Example, let's say we want to manage the sound system,
-sysctlmif_grouplistbyname("hw.snd") returns the list of the Sound Driver
-objects and sysctlmif_treebyname("dev.pcm") returns a tree where "dev.pcm" is
-the root node and each subtree represents an audio device.
-</p>
-<p>Obviously sysctlmibinfo2 benefits of the features of sysctlinfo: handles OIDs
-up to CTL_MAXNAME levels, supports capability mode, can seek an object by its
-name (avoiding to explore the MIB just to find the corresponding OID), gets all
-info about an object in a time, manages a name with a NULL level or expanded
-with an input for the sysctl handler.
-</p>
-<p>The library can be installed via the devel/libsysctlmibinfo2 port, a manual page
-and examples in the Public Domain are available for getting started your
-projects.
-</p><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree, in manpages, or in
-      external books/documents.</p><br /><h2><a name="FreeBSD-Translations-on-Weblate" href="#FreeBSD-Translations-on-Weblate" id="FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="https://wiki.freebsd.org/DocTranslationOnWeblate">Translate FreeBSD on Weblate wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="Translate FreeBSD on Weblate wiki">https://wiki.freebsd.org/DocTranslationOnWeblate</a></td></tr><tr><td><a href="https://translate-dev.freebsd.org/" title="https://translate-dev.freebsd.org/">FreeBSD Weblate Instance</a></td><td>
-	    URL: <a href="https://translate-dev.freebsd.org/" title="FreeBSD Weblate Instance">https://translate-dev.freebsd.org/</a></td></tr></table><p>
-	Contact: Danilo G. Baio &lt;<a href="mailto:dbaio@FreeBSD.org">dbaio@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Edson Brandi &lt;<a href="mailto:ebrandi@FreeBSD.org">ebrandi@FreeBSD.org</a>&gt;
-	</p><p>As announced on <a href="https://www.freebsd.org/news/newsflash.html#event20200121:01" shape="rect">January</a>, The FreeBSD Project is adopting Weblate as its web-based continuous localization platform.
-</p>
-<p>We are getting new volunteers to the effort and so far these are the numbers:
-</p>
-<h3>Q1 2020 Status</h3>
-
-<ul>
-<li><p><b>10</b> languages
-</p></li>
-<li><p><b>47</b> registered users
-</p>
-</li></ul>
-<h4>Languages</h4>
-
-<ul>
-<li><p>Chinese (Simplified) (zh_CN)
-</p></li>
-<li><p>Chinese (Traditional) (zh_TW) - <b><i>Added</i></b>
-</p></li>
-<li><p>French (fr_FR) - <b><i>Added</i></b>
-</p></li>
-<li><p>German (de_DE) - <b><i>Added</i></b>
-</p></li>
-<li><p>Italian (it_IT) - <b><i>Added</i></b>
-</p></li>
-<li><p>Norwegian Bokm�l - <b><i>Added</i></b> - New language on FreeBSD
-</p></li>
-<li><p>Persian (fa_IR) - <b><i>Added</i></b> - New language on FreeBSD
-</p></li>
-<li><p>Portuguese (Brazil)
-</p></li>
-<li><p>Spanish
-</p></li>
-<li><p>Turkish (tr-TR) <b>[1]</b> - <b><i>Added</i></b> - New language on FreeBSD
-</p>
-</li></ul>
-1 - Already had an effort in the past.
-
-<p>We want to thank everyone that contributed, translating or reviewing documents.
-</p>
-<p>And please, help promote this effort on your local user group, we always need more volunteers.
-</p><hr /><h2><a name="FreeBSD-Manpages-overhaul" href="#FreeBSD-Manpages-overhaul" id="FreeBSD-Manpages-overhaul">FreeBSD Manpages overhaul</a></h2><p>
-	Contact: Gordon Bergling &lt;<a href="mailto:gbergling@gmail.com">gbergling@gmail.com</a>&gt;
-	</p><p>I am currently working on an overhaul for the FreeBSD manpages by updating the HISTORY and STANDARDS sections and while here creating new manpages for parts of the system that missing documentation. FreeBSD has already one of the best documentation available for an UNIX-like operation system, but there are parts that could be improved.
-</p>
-<p>For the parts that have been already improved you can have a look at <a href="https://reviews.freebsd.org/p/gbergling_gmail.com/" shape="rect">my Phabricator account</a>.
-</p>
-<p>If you would like to help on improving the documentation effort, please contact Benedict Reuschling <a href="mailto:bcr@freebsd.org" shape="rect">bcr@freebsd.org</a> or me at gbergling@gmail.com.
-</p><hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="pot-and-the-nomad-pot-driver" href="#pot-and-the-nomad-pot-driver" id="pot-and-the-nomad-pot-driver">pot and the nomad pot driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://pot.pizzamig.dev" title="https://pot.pizzamig.dev">pot project</a></td><td>
-	    URL: <a href="https://pot.pizzamig.dev" title="pot project">https://pot.pizzamig.dev</a></td></tr><tr><td><a href="https://github.com/pizzamig/pot" title="https://github.com/pizzamig/pot">pot on github</a></td><td>
-	    URL: <a href="https://github.com/pizzamig/pot" title="pot on github">https://github.com/pizzamig/pot</a></td></tr><tr><td><a href="https://github.com/trivago/nomad-pot-driver" title="https://github.com/trivago/nomad-pot-driver">Nomad pot driver</a></td><td>
-	    URL: <a href="https://github.com/trivago/nomad-pot-driver" title="Nomad pot driver">https://github.com/trivago/nomad-pot-driver</a></td></tr><tr><td><a href="https://github.com/pizzamig/minipot" title="https://github.com/pizzamig/minipot">minipot</a></td><td>
-	    URL: <a href="https://github.com/pizzamig/minipot" title="minipot">https://github.com/pizzamig/minipot</a></td></tr></table><p>
-	Contact: Luca Pizzamiglio &lt;<a href="mailto:pizzamig@FreeBSD.org">pizzamig@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Esteban Barrios &lt;<a href="mailto:esteban.barrios@trivago.com">esteban.barrios@trivago.com</a>&gt;
-	</p><p>An initial effort to write proper documentation and guides for the pot project has started. The documentation, even if incomplete, is available at <a href="https://pot.pizzamig.dev" shape="rect">here</a>. A <a href="https://pot.pizzamig.dev/FAQ/" shape="rect">F.A.Q.</a> page is available and waiting for users to submit their questions.
-</p>
-<p>During the last quarter, some bugs were reported on pot and on the nomad-pot-driver. Both projects released a new bug fix version.
-Many thanks to 'grembo' and 'Crest' that reported issues, tested and tried our solutions.<br clear="none" />
-Thanks also to Mateusz (0mp) for his Pull Requests!
-</p>
-<p>pot will have a new release soon (0.11.0), focused on network:
-</p>
-<ul>
-<li><p>network stack support: ipv4 only, ipv6 only, dual stack.
-</p></li>
-<li><p>flexible network setup for alias: adding the ability to use an arbitrary network setup for alias network type
-</p>
-</li></ul>
-Contributions are welcome! Label "good first issue" has been added to issues to invite newcomers to contribute to the project!
-<hr /><h2><a name="NomadBSD" href="#NomadBSD" id="NomadBSD">NomadBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.nomadbsd.org/" title="https://www.nomadbsd.org/">NomadBSD Website</a></td><td>
-	    URL: <a href="https://www.nomadbsd.org/" title="NomadBSD Website">https://www.nomadbsd.org/</a></td></tr><tr><td><a href="https://www.github.com/NomadBSD/NomadBSD" title="https://www.github.com/NomadBSD/NomadBSD">NomadBSD Github</a></td><td>
-	    URL: <a href="https://www.github.com/NomadBSD/NomadBSD" title="NomadBSD Github">https://www.github.com/NomadBSD/NomadBSD</a></td></tr><tr><td><a href="https://forum.NomadBSD.org/" title="https://forum.NomadBSD.org/">NomadBSD Forum</a></td><td>
-	    URL: <a href="https://forum.NomadBSD.org/" title="NomadBSD Forum">https://forum.NomadBSD.org/</a></td></tr></table><p>
-	Contact: NomadBSD Team &lt;<a href="mailto:info@NomadBSD.org">info@NomadBSD.org</a>&gt;
-	</p><p>NomadBSD is a persistent live system for USB flash drives, based on FreeBSD.
-Together with automatic hardware detection and setup, it is configured to be
-used as a desktop system that works out of the box, but can also be used for
-data recovery, for educational purposes, or testing FreeBSD's hardware
-compatibility.
-</p>
-<p>In March we released a new minor version 1.3.1 which improves the configuration
-of the network interfaces, fixed some bugs and added nomadbsd-chusr and
-nomadbsd-sysinfo. Further some new features found their way into the release.
-</p>
-<p>Some days later the channel explainingcomputers on YouTube released a review video of
-NomadBSD. The explainingcomputers has almost 600,000 followers and the review was positive
-so we saw the highest peak in downloads ever! Along with it came a lot of people looking for
-help on our mailing list and on Twitter so we decided to set up a new support forum.
-</p>
-<p>We are looking for people to help the project. Help is much appreciated in all areas:
-</p>
-<ul>
-<li><p>Translation of program interfaces
-</p></li>
-<li><p>Design artwork
-</p></li>
-<li><p>Programming new tools, extend existing ones
-</p></li>
-<li><p>Tests and Bug reports / UX and feature suggestions
-</p></li>
-<li><p>Mirrors outside of Europe
-</p>
-</li></ul>
-Open tasks:
-
-<ul>
-<li><p>Support installation on disk partitions and add a partition editor GUI.
-</p></li>
-<li><p>Complete disk encryption
-</p></li>
-<li><p>Add a user-friendly network manager
-</p></li></ul>
-<hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2020-04-2020-06.html b/website/content/en/status/report-2020-04-2020-06.html
deleted file mode 100644
index 0f510cf78d..0000000000
--- a/website/content/en/status/report-2020-04-2020-06.html
+++ /dev/null
@@ -1,2477 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="../layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" src="../../layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report will be covering FreeBSD related projects between April and June, 
-and covers a diverse set of topics ranging from kernel updates over userland 
-and ports, as well as third-party work.
-</p><p>Some highlights picked with the roll of a d100 include, but are not limited to,
-the ability to forcibly unmount UFS when the underlying media becomes
-inaccessible, added preliminary support for Bluetooth Low Energy, a introduction to the
-FreeBSD Office Hours, and a repository of software collections called potluck
-to be installed with the pot utility, as well as many many more things.
-</p><p>As a little treat, readers can also get a rare report from the quarterly team.
-</p><p>Finally, on behalf of the quarterly team, I would like to extend my deepest 
-appreciation and thank you to salvadore@, who decided to take down his shingle.
-His contributions to not just the quarterly reports themselves, but also the
-surrounding tooling to many-fold ease the work, are immeasurable.
-</p><p>We hope you find the report as interesting as we have,<br clear="none" />
-Daniel Ebdrup Jensen (debdrup@), on behalf of the quarterly team.
-</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Cluster-Administration-Team">Cluster Administration Team</a></li><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#FreeBSD-Office-Hours">FreeBSD Office Hours</a></li><li><a href="#Quarterly-Status-Reports-Team">Quarterly Status Reports Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></li><li><a href="#Git-Migration-Working-Group">Git Migration Working Group</a></li><li><a href="#Lua-Usage-in-FreeBSD">Lua Usage in FreeBSD</a></li><li><a href="#Linux-compatibility-layer-update">Linux compatibility layer update</a></li><li><a href="#NFS-over-TLS-implementation">NFS over TLS implementation</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#SoC-audio-framework-and-more-audio-drivers">SoC audio framework and more audio drivers</a></li><li><a href="#bhyve---NVMe-emulation-improvements">bhyve - NVMe emulation improvements</a></li><li><a href="#Bluetooth-Support">Bluetooth Support</a></li><li><a href="#DRM-Drivers-Update">DRM Drivers Update</a></li><li><a href="#DTS-Update">DTS Update</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure">Forcible Unmount of UFS/FFS Filesystems on Disk Failure</a></li><li><a href="#i.MX-8M-support">i.MX 8M support</a></li><li><a href="#Intel-wireless-and-11ac-update">Intel wireless and 11ac update</a></li><li><a href="#amd64-5-Level-Paging-Structures-support">amd64 5-Level Paging Structures support</a></li><li><a href="#Not-transparent-superpages">Not-transparent superpages</a></li><li><a href="#NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></li><li><a href="#amd64-pmap-Fine-grained-pv-lists-locking">amd64 pmap Fine-grained pv lists locking</a></li><li><a href="#Lockless-routing-lookups-and-scalable-multipath">Lockless routing lookups and scalable multipath</a></li><li><a href="#ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></li><li><a href="#CheriBSD-2020-Q2">CheriBSD 2020 Q2</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Continuous-Integration-on-!x86">Continuous Integration on !x86</a></li><li><a href="#FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Import-of-new-implementation-of-bc-and-dc">Import of new implementation of bc and dc</a></li><li><a href="#Binutils-Retirement">Binutils Retirement</a></li><li><a href="#Run-Time-Dynamic-Linker-improvements">Run-Time Dynamic Linker improvements</a></li><li><a href="#VHDX-support-in-mkimg(1)">VHDX support in mkimg(1)</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Bastille">Bastille</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Haskell-on-FreeBSD">Haskell on FreeBSD</a></li><li><a href="#rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD">rtsx - Porting driver for Realtek SD card reader from OpenBSD</a></li><li><a href="#Valgrind-updates">Valgrind updates</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests">PCI passthrough with bhyve on Intel and for OpenBSD guests</a></li><li><a href="#SageMath">SageMath</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#chaifi---a-tool-to-simplify-joining-public-WiFi-networks">chaifi - a tool to simplify joining public WiFi networks</a></li><li><a href="#MixerTUI">MixerTUI</a></li><li><a href="#Potluck---Flavour-&amp;-Image-Repository-for-pot">Potluck - Flavour &amp; Image Repository for pot</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-	Page</a>.</p><br /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p><p>The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
-supporting and promoting the FreeBSD Project and community worldwide.  Funding
-comes from individual and corporate donations and is used to fund and manage
-software development projects, conferences and developer summits, and provide
-travel grants to FreeBSD contributors.  The Foundation purchases and supports
-hardware to improve and maintain FreeBSD infrastructure and provides resources
-to improve security, quality assurance, and release engineering efforts;
-publishes marketing material to promote, educate, and advocate for the FreeBSD
-Project; facilitates collaboration between commercial vendors and FreeBSD
-developers; and finally, represents the FreeBSD Project in executing contracts,
-license agreements, and other legal arrangements that require a recognized
-legal entity.
-</p>
-<p>Here are some highlights of what we did to help FreeBSD last quarter:
-</p>
-<h3>COVID-19 Impact on the Foundation</h3>
-
-<p>Like other organizations, we put policies in place for all of our staff members
-to work from home.  We also put a temporary ban on travel for staff members.
-We are continuing our work supporting the community and Project, but some of
-our work and responses may be delayed because of changes in some of our
-priorities and the impact of limited childcare for a few of our staff members.
-</p>
-<h3>Partnerships and Commercial User Support</h3>
-
-<p>We help facilitate collaboration between commercial users and FreeBSD
-developers.  We also meet with companies to discuss their needs and bring that
-information back to the Project.  Not surprisingly, the stay at home orders,
-combined with our company ban on travel during Q2 made in-person meetings
-non-existent.  However, the team was able to continue meeting with our partners
-and commercial users virtually. These meetings help us understand some of the
-applications where FreeBSD is used.
-</p>
-<h3>Fundraising Efforts</h3>
-
-<p>Last quarter we raised $268,400!  Thank you to the individuals and organizations
-that stepped in to help fund our efforts.  We&#8217;d like to thank Netflix, employees
-of Nginx, Beckhoff Automation, and Mozilla Foundation for their large
-contributions last quarter, which helped bring our 2020 fundraising effort to
-$339k.  We hope other organizations will follow their lead and give back to help
-us continue supporting FreeBSD.
-</p>
-<p>These are trying times, and we deeply appreciate every donation that has come in
-from $5 to $150,000. We&#8217;re still here giving 110% to supporting FreeBSD!
-</p>
-<p>We are 100% funded by donations, and those funds go towards software development
-work to improve FreeBSD, FreeBSD advocacy around the world, keeping FreeBSD
-secure, continuous integration improvements, sponsoring BSD-related and
-computing conferences (even the virtual events!), legal support for the Project,
-and many other areas.
-</p>
-<p>Please consider making a
-<a href="https://www.FreeBSDfoundation.org/donate/." shape="rect">donation to help us continue and increase our support for FreeBSD</a>.
-</p>
-<p>We also have the Partnership Program, to provide more benefits for our larger
-commercial donors.  Find out more information about the
-<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">partnership program</a>
-and share with your companies!
-</p>
-<h3>OS Improvements</h3>
-
-<p>A number of FreeBSD Foundation grant recipients started, continued working on,
-or completed projects during the second quarter.  These include:
-</p><ul>
-<li><p>WiFi improvements
-</p></li>
-<li><p>Linuxulator application compatibility
-</p></li>
-<li><p>DRM / Graphics driver updates
-</p></li>
-<li><p>Zstd compression for OpenZFS
-</p></li>
-<li><p>Online RAID-Z expansion
-</p></li>
-<li><p>if_bridge performance improvements
-</p>
-</li></ul>
-<p>You can find more details about most of these projects in other quarterly
-reports.
-</p>
-<p>Staff members also worked on a number of larger projects, including:
-</p><ul>
-<li><p>Run-Time Dynamic Linker (rtld) improvements
-</p></li>
-<li><p>Improved FreeBSD support on Microsoft HyperV and Azure
-</p></li>
-<li><p>Fine-grained locking for amd64 pmap
-</p></li>
-<li><p>5-level paging structures for amd64
-</p></li>
-<li><p>Non-transparent superpages
-</p></li>
-<li><p>Migration to a Git repository
-</p></li>
-<li><p>Tool chain modernization
-</p>
-</li></ul>
-<p>Many of these projects also have detailed entries in other quarterly report
-entries.
-</p>
-<p>Staff members also put in significant effort in many ways other than larger,
-individual projects.  These include assisting with code reviews, bug report
-triage, security report triage and advisory handling, addressing syzkaller
-reports, and ongoing maintenance and bug fixes in functional areas such as the
-tool chain, developer tools, virtual memory kernel subsystem, low-level x86
-infrastructure, sockets and protocols, and others.
-</p>
-<h3>University of Waterloo Co-op</h3>
-
-<p>Foundation co-op students Colin, Tiger, and Yang completed their winter 2020
-work term during the second quarter, and continued on with the next school term
-in their respective programs.  Although COVID-19 presented a unique challenge
-and prompted an abrupt transition to remote work just over half way through the
-term, all three learned a lot and provided positive contributions to the FreeBSD
-Project and to the Foundation.
-</p>
-<p>A few projects that were in progress or completed during the work term were
-committed to the FreeBSD tree in the second quarter.
-</p>
-<h3>Continuous Integration and Quality Assurance</h3>
-
-<p>The Foundation provides a full-time staff member who is working on improving
-continuous integration, automated testing, and overall quality assurance
-efforts for the FreeBSD project.
-</p>
-<p>During the second quarter of 2020, Foundation staff continued improving the
-Project's CI infrastructure, monitoring regressions and working with
-contributors to fix the failing build and test cases.  The setting up of VM host
-for CI jobs and staging environment is in progress.  We are also working with
-other teams in the Project for their testing needs.  For example, we added jobs
-for running full tests on non-x86 architectures.  We are also working with many
-external projects and companies to improve their support of FreeBSD.
-</p>
-<p>See the FreeBSD CI section of this report for completed work items and detailed
-information.
-</p>
-<h3>Supporting FreeBSD Infrastructure</h3>
-
-<p>The Foundation provides hardware and support to improve FreeBSD infrastructure.
-Last quarter, we continued supporting FreeBSD hardware located around the world.
-We started working on getting the new NYI Chicago colocation facility prepared
-for some of the new FreeBSD hardware we are planning on purchasing.
-NYI generously provides this for free to the Project.
-</p>
-<h3>FreeBSD Advocacy and Education</h3>
-
-<p>A large part of our efforts are dedicated to advocating for the Project.  This
-includes promoting work being done by others with FreeBSD; producing advocacy
-literature to teach people about FreeBSD and help make the path to starting
-using FreeBSD or contributing to the Project easier; and attending and getting
-other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD
-tables, and give FreeBSD presentations.
-</p>
-<p>The FreeBSD Foundation sponsors many conferences, events, and summits around the
-globe.  These events can be BSD-related, open source, or technology events
-geared towards underrepresented groups.  We support the FreeBSD-focused events
-to help provide a venue for sharing knowledge, to work together on projects, and
-to facilitate collaboration between developers and commercial users.  This all
-helps provide a healthy ecosystem.  We support the non-FreeBSD events to promote
-and raise awareness of FreeBSD, to increase the use of FreeBSD in different
-applications, and to recruit more contributors to the Project.  As is the case
-for most of us in this industry, COVID-19 has put our in-person events on hold.
-In addition to attending virtual events, we are continually working on new
-training initiatives and updating our selection of how-to guides to facilitate
-getting more folks to try out FreeBSD.
-</p>
-<p>Check out some of the advocacy and education work we did last quarter:
-</p>
-<ul>
-<li><p>Silver sponsor of BSDCan 2020.  The event was held virtually, June 2-6, 2020
-</p></li>
-<li><p>Community Sponsor of Rootconf 2020.  The event was held virtually, June 19-20, 2020
-</p></li>
-<li><p>Annual FreeBSD Day, June 19.  This year&#8217;s celebration was postponed in
-   support of Juneteeth.  However the activities surrounding FreeBSD Day have
-   been transformed into an ongoing series of online sessions.  See
-   <i>FreeBSD Fridays</i> below for more information.
-</p></li>
-<li><p>Presented
-   <a href="https://www.youtube.com/watch?v=Wi5yMvavhQM" shape="rect">27 Years of FreeBSD and Why You Should Get Involved</a>
-   as part of a Linux Professional Institute series of webinars on June 24, 2020.
-</p></li>
-<li><p>Attended and presented at the virtual Open Source Summit 2020.
-</p></li>
-<li><p>Announced <i>FreeBSD Fridays</i>: A series of 101 classes designed to get you
-   started with FreeBSD.  Find out more in the
-   <a href="https://www.freebsdfoundation.org/blog/announcing-freebsd-fridays-a-series-of-101-classes/" shape="rect">announcement</a>
-</p></li>
-<li><p>Participated as an Admin for Google Summer of Code 2020
-</p></li>
-<li><p>Participated in the new FreeBSD Office Hours series including holding our own
-   Foundation led office hours.  Videos from the one hour sessions can be found
-   on the <a href="https://www.youtube.com/channel/UCxLxR_oW-NAmChIcSkAyZGQ" shape="rect">Project&#8217;s YouTube Channel</a>.
-   You can watch ours <a href="https://www.youtube.com/watch?v=Ji4ux4FWpRU" shape="rect">here</a>.
-</p>
-</li></ul>
-<p>In addition to the information found in the Development Projects update section
-of this report, take a minute to check out the latest update blogs:
-</p>
-<ul>
-<li><p><a href="https://www.freebsdfoundation.org/blog/500-if_bridge-performance-improvement/" shape="rect">5x if_bridge Performance Improvement</a>
-</p></li>
-<li><p><a href="https://www.freebsdfoundation.org/blog/my-experience-as-a-freebsd-foundation-co-op-student/" shape="rect">My Experience as a FreeBSD Foundation Co-Op Student</a>
-</p>
-</li></ul>
-<p>Keep up to date with our latest work in our <a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">Bi-Monthly newsletters</a>.
-</p>
-<p>Mellanox provided an update on how and why they use FreeBSD in our latest
-<a href="https://www.freebsdfoundation.org/freebsd-case-study-mellanox/" shape="rect">Contributor Case Study</a>.
-</p>
-<p>We help educate the world about FreeBSD by publishing the professionally
-produced FreeBSD Journal.  As we mentioned previously, the FreeBSD Journal is
-now a free publication.  Find out more and
-<a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">access the latest issues</a> on the
-Journal site.
-</p>
-<p>You can find out more about
-<a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">events we attended and upcoming events</a>.
-</p>
-<p>We have continued our work with a new website developer to help us improve our
-website.  Work is nearly complete to make it easier for community members to
-find information more easily and to make the site more efficient.  We look
-forward to unveiling the refreshed site in Q3.
-</p>
-<h3>Foundation Board Meeting</h3>
-
-<p>Our annual board meeting was held on Tuesday June 2, 2020.  We normally hold
-this meeting the Tuesday before BSDCan, in Ottawa, Ontario, Canada, but with the
-company travel ban, and the conference going virtual, our meeting went virtual
-for the first time.  The purpose of the annual board meeting is to hold our
-board director and officer elections, review work accomplished over the past
-year, and put together strategic goals for the upcoming 12 months.
-</p>
-<p>The board generally has two all-day board meetings each year, this one, and a
-more informal one in January, typically held in Berkeley.  Both meetings allow
-us to connect, reevaluate and discuss new ideas, while assessing what we should
-do to help the Project.
-</p>
-<p>Some of our longer-term goals include Growing User and Developer Communities,
-Developing Training and OS Course Content, Improving desktop/laptop experience,
-Promoting FreeBSD (as you can see in all the advocacy work listed above), and
-Improving Testing Capabilities.
-</p>
-<p>Results of the director and officer elections were:
-</p><ul>
-<li><p>Justin Gibbs (President)
-</p></li>
-<li><p>Benedict Reuschling (Vice President)
-</p></li>
-<li><p>Kirk McKusick (Treasurer)
-</p></li>
-<li><p>Philip Paeps (Secretary)
-</p></li>
-<li><p>Deb Goodkin (Assistant Secretary)
-</p></li>
-<li><p>Robert Watson (Director)
-</p></li>
-<li><p>Hiroki Sato (Director)
-</p></li>
-<li><p>George Neville-Neil (Director)
-</p>
-</li></ul>
-<p>Find out more about the
-<a href="https://www.freebsdfoundation.org/about/board-of-directors/" shape="rect">FreeBSD Foundation Board of Directors</a>
-on our website.
-</p>
-<h3>Legal/FreeBSD IP</h3>
-
-<p>The Foundation owns the FreeBSD trademarks, and it is our responsibility to
-protect them.  We also provide legal support for the core team to investigate
-questions that arise.
-</p>
-<p>Go to <a href="http://www.FreeBSDfoundation.org/" shape="rect">the FreeBSD Foundation's web site</a> to
-find out how we support FreeBSD and how we can help you!
-</p><hr /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p>
-	Contact: FreeBSD Core Team &lt;<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Core Team is the governing body of FreeBSD.
-</p>
-<p>The Core Team held 10 meetings during the second quarter of 2020, including a
-2020-05-21 joint meeting with members of the FreeBSD Foundation.  Here are some
-highlights from that meeting:
-</p>
-<ul>
-<li><p>Deb requested guidance on how the Foundation can support the community.
-    Core and Foundation members believe that more developer support is necessary
-    to fill gaps in areas where commercial customers do not provide backing.
-    The clearest example of such a gap is the desktop experience, including
-    graphics and wireless support.  What makes this request different from past
-    requests is that rather than support for one-time projects, ongoing
-    positions are necessary for a consistently high-quality desktop experience.
-</p>
-<p>        "FreeBSD not being able to run on your laptop is the first step to
-         irrelevance." Ed Maste
-</p>
-</li>
-<li><p>Both teams discussed topics for upcoming sessions of FreeBSD Office Hours,
-    informal FreeBSD video conferences that anyone can attend.  Everyone agreed
-    that the Office Hours have been a useful way for different parts of the
-    Project to engage with each other and with the wider community.  Kudos to
-    Allan Jude for initiating the Office Hours and for everyone who has helped
-    make them a success by hosting or attending sessions.
-</p>
-</li>
-<li><p>Both teams agreed that they should meet once per quarter.
-</p>
-</li></ul>
-<p>The second annual community survey closed on 2020-06-16.  The purpose of the
-survey is to collect data from the public to help guide the Project's efforts
-and priorities.  As an example, last year's survey results helped initiate the
-Project's conversion to Git.  Thank you to all who took the time to respond. The
-results will be released soon.
-</p>
-<p>The Core-initiated Git Working Group continued to make progress, but there are
-still some remaining issues to be worked out with the translation from
-Subversion.  Hopefully the new Git src repository will be ready for use this
-summer.  A <a href="https://cgit-beta.freebsd.org/" shape="rect">beta version</a> has been published for
-people to test and a preliminary version of a <code>Using Git for FreeBSD
-Development</code> primer will soon be ready to share.  Core, the Git Working Group,
-and Release Engineering are working towards the goal of releasing 12.2 from the
-new Git repository.
-</p>
-<p>Following the results of a Core-initiated developer survey, The FreeBSD Project
-has adopted a new LLVM-derived [code of
-conduct](https://www.freebsd.org/internal/code-of-conduct.html).
-</p>
-<p>The eleventh FreeBSD Core Team was elected by active developers.  From a pool of
-23, the 9 successful candidates for core.11 are:
-</p>
-<ul>
-<li><p>Sean Chittenden (seanc, incumbent)
-</p></li>
-<li><p>Baptiste Daroussin (bapt)
-</p></li>
-<li><p>Kyle Evans (kevans)
-</p></li>
-<li><p>Mark Johnston (markj)
-</p></li>
-<li><p>Scott Long (scottl)
-</p></li>
-<li><p>Warner Losh (imp, incumbent)
-</p></li>
-<li><p>Ed Maste (emaste)
-</p></li>
-<li><p>George V. Neville-Neil (gnn)
-</p></li>
-<li><p>Hiroki Sato (hrs, incumbent)
-</p>
-</li></ul>
-<p>A new Core Team secretary, Muhammad Moinur Rahman (bofh), was unanimously
-approved by core.11.  The outgoing core team met three times with the new core
-team to help with the transition.  Core.10 wishes core.11 a successful term.
-</p><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/11.4R/announce.html" title="https://www.freebsd.org/releases/11.4R/announce.html">FreeBSD 11.4-RELEASE announcement</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.4R/announce.html" title="FreeBSD 11.4-RELEASE announcement">https://www.freebsd.org/releases/11.4R/announce.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/11.4R/schedule.html" title="https://www.freebsd.org/releases/11.4R/schedule.html">FreeBSD 11.4-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/11.4R/schedule.html" title="FreeBSD 11.4-RELEASE schedule">https://www.freebsd.org/releases/11.4R/schedule.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Release Engineering Team is responsible for setting
-and publishing release schedules for official project releases
-of FreeBSD, announcing code slushes, and maintaining the respective
-branches, among other things.
-</p>
-<p>During the second quarter of 2020, the Release Engineering Team started
-work on the 11.4-RELEASE cycle, the fifth release from the stable/11
-branch.  The release cycle went quite smoothly, with both BETA3 and RC3
-removed from the schedule.  This allowed the final release to occur one
-week earlier than originally scheduled, which was announced June 16.
-FreeBSD 11.4-RELEASE is expected to be the final 11.x release.
-</p>
-<p>The FreeBSD Release Engineering Team would like to thank everyone involved
-in this cycle for their hard work.
-</p>
-<p>Additionally throughout the quarter, several development snapshots builds
-were released for the <i>head</i>, <i>stable/12</i>, and <i>stable/11</i> branches.
-</p>
-<p>Much of this work was sponsored by Rubicon Communications, LLC (netgate.com)
-and the FreeBSD Foundation.
-</p><hr /><h2><a name="Cluster-Administration-Team" href="#Cluster-Administration-Team" id="Cluster-Administration-Team">Cluster Administration Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/administration.html#t-clusteradm" title="https://www.freebsd.org/administration.html#t-clusteradm">Cluster Administration Team members</a></td><td>
-	    URL: <a href="https://www.freebsd.org/administration.html#t-clusteradm" title="Cluster Administration Team members">https://www.freebsd.org/administration.html#t-clusteradm</a></td></tr></table><p>
-	Contact: Cluster Administration Team &lt;<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Cluster Administration Team consists of the people responsible for administering the machines that the Project relies on for its distributed work and communications to be synchronised. In this quarter, the team has worked on the following:
-</p>
-<ul>
-<li><p>Upgrade all x86 ref- and universe-machines
-</p></li>
-<li><p>Setup Amsterdam (PKT) mirror
-</p></li>
-<li><p>Solve hardware issue for bugzilla and svnweb backend
-</p></li>
-<li><p>Setup public <a href="https://cgit-beta.freebsd.org" shape="rect">beta git server</a>
-</p></li>
-<li><p>Decommission CyberOne Data (CYB) mirror
-</p></li>
-<li><p>Ongoing systems administration work:
-</p><ul>
-<li><p>Accounts management for committers.
-</p></li>
-<li><p>Backups of critical infrastructure.
-</p></li>
-<li><p>Keeping up with security updates in 3rd party software.
-</p>
-</li></ul>
-</li></ul>
-Work in progress:
-
-<ul>
-<li><p>Setup Malaysia (KUL) mirror
-</p></li>
-<li><p>Setup Brazil (BRA) mirror
-</p></li>
-<li><p>Review the service jails and service administrators operation.
-</p></li>
-<li><p>Infrastructure of building aarch64 and powerpc64 packages
-</p><ul>
-<li><p>NVME issues on PowerPC64 Power9 blocking dual socket machine from being used as pkg builder.
-</p></li>
-<li><p>Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation.
-</p></li>
-<li><p>Boot issues with Aarch64 reference machines.
-</p></li></ul>
-</li><li><p>New NYI.net sponsored colocation space in Chicago-land area.
-</p></li>
-<li><p>Work with git working group
-</p></li>
-<li><p>Check new hardware requirement from other teams
-</p></li>
-<li><p>Searching for more providers that can fit the requirements for a <a href="https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout" shape="rect">generic mirrored layout</a> or a <a href="https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror" shape="rect">tiny mirror</a>
-</p></li></ul>
-<hr /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://ci.FreeBSD.org/hwlab" title="https://ci.FreeBSD.org/hwlab">FreeBSD Hardware Testing Lab</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org/hwlab" title="FreeBSD Hardware Testing Lab">https://ci.FreeBSD.org/hwlab</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org" title="https://artifact.ci.FreeBSD.org">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org</a></td></tr><tr><td><a href="https://hackmd.io/@FreeBSD-CI" title="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackmd.io/@FreeBSD-CI" title="FreeBSD CI weekly report">https://hackmd.io/@FreeBSD-CI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="https://wiki.freebsd.org/3rdPartySoftwareCI">3rd Party Software CI</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="3rd Party Software CI">https://wiki.freebsd.org/3rdPartySoftwareCI</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="FreeBSD CI Repository">https://github.com/freebsd/freebsd-ci</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-ci channel on EFNet<br clear="none" />
-</p>
-<p>The FreeBSD CI team maintains the continuous integration system
-for the FreeBSD project.  The CI system firstly checks the committed changes
-can be successfully built, then performs various tests and analysis over the
-newly built results.
-The artifacts from the build jobs are archived in the artifact server for
-further testing and debugging needs.  The CI team members examine the
-failing builds and unstable tests and work with the experts in that area to
-fix the code or adjust test infrastructure.  The details of these efforts
-are available in the <a href="https://hackmd.io/@FreeBSD-CI" shape="rect">weekly CI reports</a>.
-</p>
-<p>During the second quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD.
-</p>
-<p>Important changes:
-</p><ul>
-<li><p>All -test jobs will run tests under <code>/usr/tests</code>, previously only x86 architectures were doing this. See the Continuous Integration on !x86 section in this report for more information.
-</p></li>
-<li><p>Compression algorithm of disk images on the <a href="https://artifacts.ci.freebsd.org" shape="rect">artifact server</a> has been changed to zstd to speed up compression and decompression.
-</p></li>
-<li><p>The build and test results will be sent to the <a href="https://lists.freebsd.org/mailman/listinfo/dev-ci" shape="rect">dev-ci mailing list</a> soon. Feedback and help with analysis is very appreciated!
-</p>
-</li></ul>
-New jobs added:
-<ul>
-<li><p>https://ci.freebsd.org/job/FreeBSD-head-armv7-test/
-</p></li>
-<li><p>https://ci.freebsd.org/job/FreeBSD-head-aarch64-test/
-</p></li>
-<li><p>https://ci.freebsd.org/job/FreeBSD-head-mips64-test/
-</p></li>
-<li><p>https://ci.freebsd.org/job/FreeBSD-head-powerpc64-test/
-</p>
-</li></ul>
-Work in progress:
-<ul>
-<li><p>Collecting and sorting CI tasks and ideas <a href="https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo" shape="rect">here</a>
-</p></li>
-<li><p>Testing and merging pull requests in the <a href="https://github.com/freebsd/freebsd-ci/pulls" shape="rect">the FreeBSD-ci repo</a>
-</p></li>
-<li><p>Setting up a builder dedicated to run jobs using provisioned VMs.
-</p></li>
-<li><p>Setting up the CI stage environment and putting the experimental jobs on it
-</p></li>
-<li><p>Implementing automatic tests on bare metal hardware
-</p></li>
-<li><p>Adding drm ports building tests against -CURRENT
-</p></li>
-<li><p>Planning to run ztest and network stack tests
-</p></li>
-<li><p>Adding external toolchain related jobs
-</p></li>
-<li><p>Improving the hardware lab to be more mature and adding more hardware
-</p></li>
-<li><p>Helping more 3rd software get CI on FreeBSD through a hosted CI solution
-</p></li>
-<li><p>Working with hosted CI providers to have better FreeBSD support
-</p>
-</li></ul>
-Please see freebsd-testing@ related tickets for more WIP information, and don't hesitate to join the effort!
-
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p><p>The Ports Management Team is responsible for overseeing the
-overall direction of the Ports Tree, building packages, and
-personnel matters.  Below is what happened in the last quarter.
-</p>
-<p>There are currently 2,373 open ports PRs of which 526 are
-unassigned, for a total of 39,628 ports.  In the last quarter
-there were 10,315 commits to HEAD and 476 to the quarterly
-branch by respectively 178 and 65 committers.  Compared to the
-quarter before, this means a significant increase in commits and
-also a slight decrease in open PRs.
-</p>
-<p>During the last quarter, we welcomed Hiroki Tagato (tagattie@).
-We said goodbye to seanc@, zleslie@, gnn@ and salvadore@.
-</p>
-<p>A few default versions got bumped:
-</p><ul>
-<li><p>Java (new) at 8
-</p></li>
-<li><p>Lazarus to 2.0.8
-</p>
-</li></ul>
-It is now possible to write pkg scripts in Lua instead of sh.
-<p>They have two advantages over their sh versions:
-</p><ul>
-<li><p>they run in a Capsicum sandbox
-</p></li>
-<li><p>they respect rootdir, the directory which pkg will use as
-    the starting point to install all packages under.
-</p>
-</li></ul>
-Some user-facing packages were also updated:
-<ul>
-<li><p>pkg to 1.14.6
-</p></li>
-<li><p>Firefox to 78.0.1
-</p></li>
-<li><p>Thunderbird to 68.10.0
-</p></li>
-<li><p>Chromium to 83.0.4103.116
-</p></li>
-<li><p>Ruby to 2.5.8, 2.6.6, and 2.7.1
-</p></li>
-<li><p>Qt5 to 5.14.2
-</p>
-</li></ul>
-<p>During the last quarter, antoine@ ran 55 exp-runs to test port
-version updates, make liblzma use libmd, flavor devel/scons and
-Lua ports, add and update library functions in the base system,
-make malloc.h usable again, remove as(1) from the base system, and
-augment sed(1) with -f.
-</p><hr /><h2><a name="FreeBSD-Office-Hours" href="#FreeBSD-Office-Hours" id="FreeBSD-Office-Hours">FreeBSD Office Hours</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/OfficeHours" title="https://wiki.freebsd.org/OfficeHours">Office Hours on the FreeBSD Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/OfficeHours" title="Office Hours on the FreeBSD Wiki">https://wiki.freebsd.org/OfficeHours</a></td></tr><tr><td><a href="https://forms.gle/3HjjRx9KMcM3SL4H7" title="https://forms.gle/3HjjRx9KMcM3SL4H7">Poll: What time would you prefer Office Hours be at</a></td><td>
-	    URL: <a href="https://forms.gle/3HjjRx9KMcM3SL4H7" title="Poll: What time would you prefer Office Hours be at">https://forms.gle/3HjjRx9KMcM3SL4H7</a></td></tr><tr><td><a href="https://live.freebsd.org/" title="https://live.freebsd.org/">live.FreeBSD.org: Aggregation of Live streams</a></td><td>
-	    URL: <a href="https://live.freebsd.org/" title="live.FreeBSD.org: Aggregation of Live streams">https://live.freebsd.org/</a></td></tr></table><p>
-	Contact: Allan Jude &lt;<a href="mailto:allanjude@freebsd.org">allanjude@freebsd.org</a>&gt;
-	</p><p>Starting on the first of April 2020, the FreeBSD project has started
-hosting regular video streams to foster greater communication within
-the wider FreeBSD community. The first of these sessions took the form
-of a public question and answer session, which drew over 60 participants.
-A second session was held two weeks later at a time more appropriate for
-those in Asia, but only drew 20 participants. With the help of the FreeBSD
-Foundation, we ran a poll to discover what times worked best for the
-greatest number of people.
-</p>
-<p>On May 13th the FreeBSD Foundation hosted a session where the community
-could ask questions of or about the foundation. On May 27th many of the
-candidates for the new FreeBSD Core Team joined an office hours session to
-answer questions from the community. Finally on June 24th another general
-question and answer office hours was held.
-</p>
-<p>Each office hours session consists of a video meeting of some FreeBSD
-developers or other subject matter experts, live streamed along with an IRC
-chat room for viewers to pose questions to the panel. The stream is recorded
-and posted to the official FreeBSD youtube channel.
-</p>
-<p>If you would like to host an office hours session, please contact:
-</p><ul>
-<li><p><a href="mailto:allanjude@freebsd.org" shape="rect">Allan Jude</a>
-</p></li>
-<li><p><a href="mailto:anne@freebsdfoundation.org" shape="rect">Anne Dickison</a>
-</p>
-</li></ul>
-<p>Sponsor: ScaleEngine Inc. (video streaming)  
-</p><hr /><h2><a name="Quarterly-Status-Reports-Team" href="#Quarterly-Status-Reports-Team" id="Quarterly-Status-Reports-Team">Quarterly Status Reports Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/news/status/" title="https://www.freebsd.org/news/status/">Quarterly status reports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/news/status/" title="Quarterly status reports">https://www.freebsd.org/news/status/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-quarterly" title="https://github.com/freebsd/freebsd-quarterly">Git repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-quarterly" title="Git repository">https://github.com/freebsd/freebsd-quarterly</a></td></tr></table><p>
-	Contact: Quarterly Status Reports &lt;<a href="mailto:quarterly@FreBSD.org">quarterly@FreBSD.org</a>&gt;
-	<br />
-	Contact: Daniel Ebdrup Jensen &lt;<a href="mailto:debdrup@FreeBSD.org">debdrup@FreeBSD.org</a>&gt;
-	</p><p>The Quarterly Status Reports Team collects and publishes the reports that you are
-reading right now.
-</p>
-<p>Many improvements have been done recently and thus we believe it is useful that
-the Quarterly Status Reports Team submits a report. Not all the changes below
-are specific to the last quarter, but we list them here anyway since we did not
-write an entry for earlier reports.
-</p>
-<ul>
-<li><p>Reports are now built using Makefiles. Among the many advantages, this allows
-  us to easily sort reports logically. Indeed, starting with 2019Q4, all reports
-  are sorted logically, while before they were sorted alphabetically within each
-  category.
-</p>
-</li>
-<li><p>The conversion from markdown to docbook was performed using a python script,
-  with some known bugs. Salvadore has rewritten the script using perl fixing
-  most of the bugs. Some features are missing and many improvements are
-  possible, but the script is very unlikely to receive any change since it will
-  become obsolete as soon as the conversion to Hugo/AsciiDoctor is completed.
-</p>
-</li>
-<li><p>Another perl script to ease the preparation of the mail version of the
-  reports was written.
-</p>
-</li>
-<li><p>One more perl script has been written to allow the quarterly team to send
-  quarterly calls automatically using a cron job. We used it this quarter for
-  the first time.
-</p>
-</li>
-<li><p>As you might have noticed, last quarterly calls have been sent to
-  freebsd-quarterly-calls@: this is a new mailing list to which you can
-  <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-quarterly-calls" shape="rect">subscribe</a>
-  to receive calls for quarterly reports. Please note this is a moderated list, 
-  with very low traffic and a high signal to noise ratio.
-</p>
-</li>
-<li><p>If you read carefully the last quarterly calls, you should have noticed that
-  we now ask you to send reports to quarterly-submissions@ instead of
-  quarterly@. This was done to help the quarterly team distinguishing internal
-  discussions from submissions. Please keep in mind however that the quarterly
-  team prefers receiving pull requests, as they ease the administrative work.
-</p>
-</li></ul>
-<p>We would like to thank philip@, from the postmaster team, for having created the
-freebsd-quarterly-calls@ mailing list and the quarterly-submissions@ address for
-us.
-</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="FreeBSD-on-Microsoft-HyperV-and-Azure" href="#FreeBSD-on-Microsoft-HyperV-and-Azure" id="FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/MicrosoftAzure" title="https://wiki.freebsd.org/MicrosoftAzure">FreeBSD on MicrosoftAzure wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/MicrosoftAzure" title="FreeBSD on MicrosoftAzure wiki">https://wiki.freebsd.org/MicrosoftAzure</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HyperV" title="https://wiki.freebsd.org/HyperV">FreeBSD on Microsoft HyperV</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HyperV" title="FreeBSD on Microsoft HyperV">https://wiki.freebsd.org/HyperV</a></td></tr></table><p>
-	Contact: FreeBSD Integration Services Team &lt;<a href="mailto:bsdic@microsoft.com">bsdic@microsoft.com</a>&gt;
-	<br />
-	Contact: Wei Hu &lt;<a href="mailto:whu@FreeBSD.org">whu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>HyperV socket for FreeBSD implemented by Wei was checked into FreeBSD head
-branch on May 20th as
-<a href="https://svnweb.freebsd.org/changeset/base/r361275" shape="rect">r361275</a>. It supports
-guest/host communications without the need for networking.  Some HyperV
-and Azure features rely on this to be available in guests.
-</p>
-<p>Details of HyperV Socket is available <a href="https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service" shape="rect">here</a>.
-</p>
-<p>This project is sponsored by Microsoft.
-</p>
-<p>Li-Wen is working on the FreeBSD release code related to Azure for the -CURRENT, 12-STABLE and 11-STABLE branches.
-The work-in-progress is available <a href="https://reviews.freebsd.org/D23804" shape="rect">here</a>.
-The <a href="https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-12_1" shape="rect">12.1-RELEASE image on Azure Marketplace</a> is published.
-The work on the 11.4-RELEASE image on Azure Marketplace is in progress.
-</p>
-<p>This project is sponsored by The FreeBSD Foundation.
-</p><hr /><h2><a name="Git-Migration-Working-Group" href="#Git-Migration-Working-Group" id="Git-Migration-Working-Group">Git Migration Working Group</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/git_conv" title="https://github.com/freebsd/git_conv">Git conversion tooling repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/git_conv" title="Git conversion tooling repo">https://github.com/freebsd/git_conv</a></td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="https://lists.freebsd.org/mailman/listinfo/freebsd-git">FreeBSD-git mailing list</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="FreeBSD-git mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-git</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/doc" title="https://cgit-beta.FreeBSD.org/doc">Beta doc git repo</a></td><td>
-	    URL: <a href="https://cgit-beta.FreeBSD.org/doc" title="Beta doc git repo">https://cgit-beta.FreeBSD.org/doc</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/ports" title="https://cgit-beta.FreeBSD.org/ports">Beta ports git repo</a></td><td>
-	    URL: <a href="https://cgit-beta.FreeBSD.org/ports" title="Beta ports git repo">https://cgit-beta.FreeBSD.org/ports</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/src" title="https://cgit-beta.FreeBSD.org/src">Beta src git repo</a></td><td>
-	    URL: <a href="https://cgit-beta.FreeBSD.org/src" title="Beta src git repo">https://cgit-beta.FreeBSD.org/src</a></td></tr></table><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Warner Losh &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ulrich Sp�rlein &lt;<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>&gt;
-	</p><p>Work continues on FreeBSD's migration from Subversion to Git.  Ulrich has
-iterated on updates to svn2git in order to improve the fidelity of the
-conversion, particularly in regards to vendor (contrib) code updates.
-We believe the conversion is now at an acceptable state, but may make minor
-adjustments if additional issues are found.  We expect to push modifications
-to the converter every two weeks (first and third Sunday of the month).  This
-means that commit hashes in the beta repo will remain stable for at least two
-weeks at a time, to allow others to test and experiment with the beta repo.
-</p>
-<p>We are now working on updating FreeBSD processes and documentation.
-This includes:
-</p><ul>
-<li><p>Writing a Git Primer, akin to the existing Subversion primer
-</p></li>
-<li><p>Updates to the Security Team's tools and processes
-</p></li>
-<li><p>Release engineering updates
-</p></li>
-<li><p>Ports and packages process updates
-</p>
-</li></ul>
-<p>Those with an interest in the migration to Git are encouraged to subscribe
-to the
-<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" shape="rect">FreeBSD-git mailing list</a>
-and test out the beta src, ports, and/or doc repositories.
-</p>
-<p>You are also welcome to check out the wiki, issues, README and other documentation at the
-<a href="https://github.com/freebsd/git_conv" shape="rect">Git conversion tooling repo</a>.
-</p>
-<p>We expect to be ready for the migration in the next quarter.
-</p>
-<p>Sponsor: The FreeBSD Foundation (in part)
-</p><hr /><h2><a name="Lua-Usage-in-FreeBSD" href="#Lua-Usage-in-FreeBSD" id="Lua-Usage-in-FreeBSD">Lua Usage in FreeBSD</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Kyle Evans &lt;<a href="mailto:kevans@FreeBSD.org">kevans@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ryan Moeller &lt;<a href="mailto:freqlabs@FreeBSD.org">freqlabs@FreeBSD.org</a>&gt;
-	</p><p>Lua is a small, efficient scripting language that FreeBSD imported before
-FreeBSD 12.0 for use in the bootloader.  Since then, several projects
-outside of the bootloader have gained some amount of traction with Lua usage:
-</p>
-<ul>
-<li><p>/usr/libexec/flua is now installed for internal usage
-</p></li>
-<li><p>makesyscalls.sh was rewritten in Lua
-</p></li>
-<li><p>pkg has gained support for lua scripts
-</p></li>
-<li><p>lldb in the base system now supports lua scripting
-</p>
-</li></ul>
-<p>FreeBSD Lua ("flua") is a version of the lua interpreter that has several
-modules built-in for convenient usage within the base system.  flua is
-installed with a non-standard name and in a location not included in $PATH
-so that it is not accidentally found by third-party software or configure
-scripts.  The FreeBSD project makes no guarantees about upgrade cadence or
-module stability.  That said, it is available for use by downstream projects
-and FreeBSD users aware of those limitations.
-</p>
-<p>Previous work with flua includes, for example, adding libucl support and
-future work includes libifconfig support for scripting usage.
-</p>
-<p>People interested in working with Lua in FreeBSD are welcome to get in
-contact to discuss other project ideas.  To name a couple of potential
-projects, some interesting modules that have not been started but could
-prove useful (listed in no particular order):
-</p>
-<ul>
-<li><p>libcrypt
-</p></li>
-<li><p>libexpat
-</p></li>
-<li><p>libjail
-</p></li>
-<li><p>libnv
-</p></li>
-<li><p>libxo
-</p></li></ul>
-<hr /><h2><a name="Linux-compatibility-layer-update" href="#Linux-compatibility-layer-update" id="Linux-compatibility-layer-update">Linux compatibility layer update</a></h2><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p><p>Earlier Linuxulator work focused on code cleanups and improving
-diagnostic tools.
-Work has now shifted from cleanups to fixing actual applications.
-Current status is being tracked at
-<a href="https://wiki.freebsd.org/LinuxApps" shape="rect">Linux app status Wiki page</a>.
-Initial focus is on applications that don't involve X11, mostly
-because they tend to be easier to test and debug, and the bug fixes
-are not application-specific.
-</p>
-<p>Example problems fixed include buggy madvise(2) handling, which could
-break applications linked against jemalloc; uname(2) returning wrong
-results for 32 bit apps, which caused problems for Steam; recvmsg(2)
-and accept(2) being broken in some circumstances, which was breaking
-Redis; and missing support for <code>SO_REUSEPORT</code>, <code>SO_SNDBUFFORCE</code>,
-<code>SO_RCVBUFFORCE</code>, and <code>SO_PROTOCOL</code>, which spammed the log files when
-running the Python regression test suite.  The default soft open files
-limit is now automatically adjusted to 1024, as several Linux apps
-iterate over all the file descriptors up to that limit instead of using
-closefrom(2).
-</p>
-<p>There's ongoing work on cleanups and the debugging framework for Linux
-compatibility, such as logging warnings for unrecognized system call
-parameters, or adding the <code>compat.linux.debug</code> sysctl to turn the warnings
-off.
-</p>
-<p>The Linux Test Project tests that are being run as part of the
-the <a href="https://ci.FreeBSD.org" shape="rect">FreeBSD Continuous Integration infrastructure</a>
-has been upgraded to 20200605 snapshot.  This raised the number
-of test cases from 3670 to 3749, and, predictably, also the number
-of failures, from 583 to 647.
-</p>
-<p>There's still a lot to do:
-</p>
-<ul>
-<li><p>There are pending reviews for patches that add
-   <a href="https://reviews.freebsd.org/D13209" shape="rect">extended attributes support</a>,
-   and <a href="https://reviews.freebsd.org/D10275" shape="rect">fexecve(2) syscall</a>, and
-   they require wrapping up and committing
-</p>
-</li>
-<li><p>There are over <a href="https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/" shape="rect">500 failing LTP tests</a>.
-   Some of them are false positives, some are easy to fix bugs, and some require adding
-   new system calls.  Any help is welcome.
-</p>
-</li></ul>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="NFS-over-TLS-implementation" href="#NFS-over-TLS-implementation" id="NFS-over-TLS-implementation">NFS over TLS implementation</a></h2><p>
-	Contact: Rick Macklem &lt;<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>&gt;
-	</p><p>In an effort to improve NFS security, an internet draft
-which I expect will become an RFC soon specifies the
-use of TLS 1.3 to encrypt all data traffic on a Sun RPC
-connection used for NFS.
-</p>
-<p>Although NFS has been able to use sec=krb5p to encrypt data
-on the wire, this requires a Kerberos environment and, as
-such, has not been widely adopted. It also required that
-encryption/decryption be done in software, since only the
-RPC message NFS arguments are encrypted.
-Since Kernel TLS is capable of using hardware assist to
-improve performance and does not require Kerberos, NFS
-over TLS may be more widely adopted, once implementations
-are available.
-</p>
-<p>The project to implement this has largely been completed.
-The code will slowly be merged into head/current and at least
-the kernel portion should be in FreeBSD-13.
-</p>
-<p>To support clients such as laptops, the daemons that perform the TLS
-handshake may optionally handle client X.509 certificates from a
-site local CA. There are now exports(5) options to require client(s) to
-provide a valid X.509 certificate.
-</p>
-<p>The code is now available for testing. See:
-https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt
-Setting up system(s) for testing is still a little awkward, as explained
-by the above rough document.
-</p>
-<p>The main limitation in the current implementation is that it uses TLS1.2
-and not TLS1.3. This should change once the KERN_TLS rx patch includes
-TLS1.3 support.
-Also, testing of pNFS configurations has not yet been done, but will
-be tested soon.
-</p>
-<p>Third party testing would be appreciated.
-</p>
-<hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><h2><a name="SoC-audio-framework-and-more-audio-drivers" href="#SoC-audio-framework-and-more-audio-drivers" id="SoC-audio-framework-and-more-audio-drivers">SoC audio framework and more audio drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/freebsd/tree/rk3399_audio" title="https://github.com/gonzoua/freebsd/tree/rk3399_audio">rk3399_audio</a></td><td>
-	    URL: <a href="https://github.com/gonzoua/freebsd/tree/rk3399_audio" title="rk3399_audio">https://github.com/gonzoua/freebsd/tree/rk3399_audio</a></td></tr></table><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p><p>SoC audio framework made a good progress since last report.<br clear="none" /> Support for AUX devices was
-added (devices like auxiliary amplifiers that are not part of main CODEC chip). <br clear="none" /> To verify
-the framework design following audio drivers were added: recording support for RT5640 CODEC(Firefly-RK3399),
-Allwinner I2S, Alwinners sun8i and A64 CODECs (Pine A64+), both recording and playback.<br clear="none" /> Current work in progress
-is RK3328 CODEC (Rock64) and ES8316 CODEC (RockPro64 and Pinebook Pro).
-</p><hr /><h2><a name="bhyve---NVMe-emulation-improvements" href="#bhyve---NVMe-emulation-improvements" id="bhyve---NVMe-emulation-improvements">bhyve - NVMe emulation improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/search/query/xvbcF20W__Km/" title="https://reviews.freebsd.org/search/query/xvbcF20W__Km/">bhyve NVMe reviews</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/search/query/xvbcF20W__Km/" title="bhyve NVMe reviews">https://reviews.freebsd.org/search/query/xvbcF20W__Km/</a></td></tr></table><p>
-	Contact: Chuck Tuffli &lt;<a href="mailto:chuck@freebsd.org">chuck@freebsd.org</a>&gt;
-	</p><p>The University of New Hampshire InterOperability Laboratory
-(a.k.a. UNH IOL) develops a suite of tests to determine if an
-NVMe device conforms to the specification and is interoperable
-with other NVMe products. This quarter, I undertook getting
-bhyve's emulated NVMe device to pass the mandatory tests. Changes
-include:
-</p><ul>
-<li><p>implement Flush command
-</p></li>
-<li><p>implement Format NVM command
-</p></li>
-<li><p>implement AER support
-</p></li>
-<li><p>implement Namespace Identification Descriptor
-</p></li>
-<li><p>fix Active Namespace list
-</p></li>
-<li><p>fix queue creation and deletion
-</p></li>
-<li><p>validate Deallocate range values
-</p></li>
-<li><p>handle zero length DSM ranges
-</p></li>
-<li><p>fix Get Log Page command
-</p></li>
-<li><p>implement SMART data I/O statistics
-</p></li>
-<li><p>validate the LBA start and count
-</p></li>
-<li><p>add basic Firmware Commit support
-</p></li>
-<li><p>add more compliant Get/Set Features
-</p></li>
-<li><p>add Feature, Interrupt Vector Config
-</p></li>
-<li><p>fix Get Features, Predictable Latency
-</p>
-</li></ul>
-<p>This was also a good opportunity to restructure parts of the code
-to make it more modular and easier to enhance. This includes
-</p><ul>
-<li><p>convert logging statements to parameterized macros
-</p></li>
-<li><p>refactor I/O command handling
-</p></li>
-<li><p>add locks around queue accesses
-</p></li>
-<li><p>consolidate CQ update
-</p></li>
-<li><p>base pci_nvme_ioreq size on advertised MDTS
-</p>
-</li></ul>
-<p>You can help by testing and/or commenting on the code reviews.
-</p><hr /><h2><a name="Bluetooth-Support" href="#Bluetooth-Support" id="Bluetooth-Support">Bluetooth Support</a></h2><p>
-	Contact: Marc Veldman &lt;<a href="mailto:marc@bumblingdork.com">marc@bumblingdork.com</a>&gt;
-	</p><p>Bluetooth is a wireless technology for creating personal networks, 
-connecting peripherals like keyboards and mice but also speakers and
-heart rate monitors.
-</p>
-<p>FreeBSD has limited Bluetooth Basic Rate (BR) support and no functional 
-Bluetooth Low Energy (LE) support.
-</p>
-<p>During this quarter many small improvements have been made to help the 
-development of Bluetooth LE support. A number of commands have been added to 
-hccontrol(8), mainly to do LE functions. It is now possible to scan for LE
-devices within range using hccontrol.
-A panic that occurred when enabling LE support has also been fixed.
-</p>
-<p>Work is still needed to add Attribute Protocol (ATT) and Generic Attribute
-Profile (GATT) support.
-</p><hr /><h2><a name="DRM-Drivers-Update" href="#DRM-Drivers-Update" id="DRM-Drivers-Update">DRM Drivers Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/drm-kmod/" title="https://github.com/freebsd/drm-kmod/">drm-kmod</a></td><td>
-	    URL: <a href="https://github.com/freebsd/drm-kmod/" title="drm-kmod">https://github.com/freebsd/drm-kmod/</a></td></tr></table><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.Org">manu@FreeBSD.Org</a>&gt;
-	</p>
-<p>The drm drivers for FreeBSD 13-CURRENT have been updated to match Linux 5.3
-This brings us a little bit closer to the last LTS release of Linux (5.4).
-</p>
-<p>The current plan is to first update the driver to match 5.4 and then look
-at making it work on FreeBSD-12-STABLE to have it ready for the 12.2 release.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="DTS-Update" href="#DTS-Update" id="DTS-Update">DTS Update</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p><p>DTS files (Device Tree Sources) were updated to be on par with Linux 5.7 for
-HEAD and 5.6 for the 12-STABLE branch.
-</p><hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p><p>ENA (Elastic Network Adapter) is the smart NIC available in the
-virtualized environment of Amazon Web Services (AWS). The ENA
-driver supports multiple transmit and receive queues and can handle
-up to 100 Gb/s of network traffic, depending on the instance type
-on which it is used.
-</p>
-<p>Completed since the last update:
-</p><ul>
-<li><p>Fixes for Rx refill to improve stability on low memory conditions (also
-    released as an errata notice for FreeBSD-12.1)
-</p></li>
-<li><p>Upstream of the v2.2.0 driver, introducing:
-</p><ul>
-<li><p>Add driver support for the upcoming HW features (reporting Tx drops,
-      disabling meta caching)
-</p></li>
-<li><p>Add sysctl tuneables for IO queue number
-</p></li>
-<li><p>Create IO queues with optional size backoff
-</p></li>
-<li><p>Rework the way of configration of drbr and Rx ring size to be more robust
-      and stable
-</p></li>
-<li><p>New HAL version
-</p></li>
-<li><p>Driver is now marked as epoch ready
-</p></li>
-<li><p>Default RSS key is created using RNG to improve security
-</p></li>
-<li><p>Other minor fixes and improvements
-</p></li></ul>
-</li><li><p>MFC of the ENA v2.2.0 driver to the FreeBSD 11.4
-</p>
-</li></ul>
-<p>Sponsor: Amazon.com Inc
-</p><hr /><h2><a name="Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure" href="#Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure" id="Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure">Forcible Unmount of UFS/FFS Filesystems on Disk Failure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24088" title="https://reviews.freebsd.org/D24088">Phabricator Details</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D24088" title="Phabricator Details">https://reviews.freebsd.org/D24088</a></td></tr></table><p>
-	Contact: Chuck Silvers &lt;<a href="mailto:chs@freebsd.org">chs@freebsd.org</a>&gt;
-	<br />
-	Contact: Kirk McKusick &lt;<a href="mailto:mckusick@mckusick.com">mckusick@mckusick.com</a>&gt;
-	</p><p>Commit -r361491 on May 25, 2020 enables a UFS file system to do a
-forcible unmount when the underlying media fails or becomes
-inaccessible. For example when a USB flash memory card hosting a
-UFS file system is unplugged.
-</p>
-<p>The rest of this report describes in more detail how forcible
-unmounts are done. Surprisingly, less than 500 lines of file
-system code were added or changed.
-</p>
-<p>The strategy for handling disk I/O errors when soft updates are
-enabled is to stop writing to the disk of the affected file system
-but continue to accept I/O requests and report that all future
-writes by the file system to that disk actually succeed. Then
-initiate an asynchronous forced unmount of the affected file system.
-</p>
-<p>There are two cases for disk I/O errors:
-</p>
-<ul>
-<li><p>ENXIO, which means that this disk is gone and the lower layers
-     of the storage stack already guarantee that no future I/O to
-     this disk will succeed.
-</p>
-</li>
-<li><p>EIO (or most other errors), which means that this particular
-     I/O request has failed but subsequent I/O requests to this
-     disk might still succeed.
-</p>
-</li></ul>
-<p>For ENXIO, we can just clear the error and continue, because we
-know that the file system cannot affect the on-disk state after we
-see this error. For EIO or other errors, we arrange for the geom_vfs
-layer to reject all future I/O requests with ENXIO just like is
-done when the geom_vfs is orphaned. In both cases, the file system
-code can just clear the error and proceed with the forcible unmount.
-</p>
-<p>This new treatment of I/O errors is needed for writes of any buffer
-that is involved in a dependency. Most dependencies are described
-by a structure attached to the buffer's b_dep field, but some are
-created and processed as a result of the completion of the dependencies
-attached to the buffer.
-</p>
-<p>Clearing of some dependencies require a read. For example if there
-is a dependency that requires an inode to be written, the disk block
-containing that inode must be read, the updated inode copied into
-place in that buffer, and the buffer then written back to disk.
-</p>
-<p>Often the needed buffer is already in memory and can be used. But
-if it needs to be read from the disk, the read will fail, so we
-fabricate a buffer full of zeroes and pretend that the read succeeded.
-This zero'ed buffer can be updated and "written" back to disk.
-</p>
-<p>The only case where a buffer full of zeros causes the code to do
-the wrong thing is when reading an inode buffer containing an inode
-that still has an inode dependency in memory that will reinitialize
-the effective link count (i_effnlink) based on the actual link count
-(i_nlink) that we read. To handle this case we now store the i_nlink
-value that we wrote in the inode dependency so that it can be
-restored into the zero'ed buffer thus keeping the tracking of the
-inode link count consistent.
-</p>
-<p>Because applications depend on knowing when an attempt to write
-their data to stable storage has failed, the fsync(2) and msync(2)
-system calls need to return errors if data fails to be written to
-stable storage. So these operations return ENXIO for every call
-made on files in a file system where we have otherwise been ignoring
-I/O errors.
-</p>
-<p>Sponsor:  Netflix
-</p><hr /><h2><a name="i.MX-8M-support" href="#i.MX-8M-support" id="i.MX-8M-support">i.MX 8M support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D25274" title="https://reviews.freebsd.org/D25274">D25274</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D25274" title="D25274">https://reviews.freebsd.org/D25274</a></td></tr></table><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p><p>i.MX 8M is the family of application processors from NXP based on Arm� Cortex�-A53 and Cortex-M4 cores.
-The initial code drop for the platform support includes CCM driver and clock implementation, GPC driver,
-clock tree for i.MX 8M Quad. Most of the drivers from i.MX 6 can be reused for i.MX 8M systems with relatively minor modifications.
-Common changes include adding clock support and extending list of FDT compat strings.
-</p>
-<p>With the linked patch FreeBSD successfully booted to multiuser with NFS root on Nitrogen8M SBC.
-</p><hr /><h2><a name="Intel-wireless-and-11ac-update" href="#Intel-wireless-and-11ac-update" id="Intel-wireless-and-11ac-update">Intel wireless and 11ac update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html" title="https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html">Initial project announcement</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html" title="Initial project announcement">https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html</a></td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless">The freebsd-wireless mailing list</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="The freebsd-wireless mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-wireless</a></td></tr></table><p>
-	Contact: Bjoern A. Zeeb &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p><p>The Intel Wireless cards are one of the most commonly used
-and asked for in FreeBSD notebooks.
-</p>
-<p>This project has three main goals:
-</p><ul>
-<li><p>newer Intel Wireless device support,
-</p></li>
-<li><p>newer WiFi standards support for Intel Wireless,
-</p></li>
-<li><p>integration of 802.11ac client support and infrastructure in FreeBSD.
-</p>
-</li></ul>
-<p>The first one is needed as iwm(4) currently does not support
-the latest generations of Intel Wireless cards at all.
-The second is needed as in FreeBSD iwm(4) does not even support
-802.11n.
-The third one we want to catch up and use the improvements the
-new Wifi standard offers, e.g., speed.
-</p>
-<p>One of the decisions made was: rather than improving iwm(4)
-this work uses the dual-licensed native Linux driver under BSD license
-and the linuxkpi framework to stay as close to upstream as possible as
-a first step.
-This will give us several advantages, such as, the full support for all
-cards, quick support for new chipsets, vendor bug fixes, but also the
-ability to contribute back.
-</p>
-<p>At this point the lower level hardware attachments and the firmware
-loading and initialisation works.
-I plan to release a patchset for testing before mid-July, you can see if
-your currently supported or unsupported hardware will be detected.
-This first cut will not support any wireless operation yet, which will follow
-later in the year.
-</p>
-<p>If you want to help testing, please watch the freebsd-wireless list.
-</p>
-<p>Sponsor: The FreeBSD Foundation<br clear="none" />
-</p><hr /><h2><a name="amd64-5-Level-Paging-Structures-support" href="#amd64-5-Level-Paging-Structures-support" id="amd64-5-Level-Paging-Structures-support">amd64 5-Level Paging Structures support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D25273" title="https://reviews.freebsd.org/D25273">Patch</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D25273" title="Patch">https://reviews.freebsd.org/D25273</a></td></tr><tr><td><a href="https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html" title="https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html">Intel SDM</a></td><td>
-	    URL: <a href="https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html" title="Intel SDM">https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html</a></td></tr><tr><td><a href="https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html" title="https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html">Intel whitepaper</a></td><td>
-	    URL: <a href="https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html" title="Intel whitepaper">https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html</a></td></tr></table><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p><p>Since its introduction, x86 Long Mode (AKA 64bit execution mode, amd64 
-in FreeBSD terminology) uses 4-level paging structures, which provides
-48 bits of virtual address space (LA48).  FreeBSD evenly divides the
-space between userspace and kernel, giving both 47 virtual address
-bits.
-</p>
-<p>In near future Intel CPUs will start providing 5-level paging
-structures, i.e. giving 57 bits for virtual addresses (LA57).  This
-means, with preservation of the existing divide between KVA and UVA,
-56 bit for UVA, or 2^9 = 512 times more virtual memory.
-</p>
-<p>The amd64 pmap was modified to support both LA48 and LA57, defaulting
-to LA57 if hardware supports it.  The tunable is provided to force
-using LA48 even if hardware can do LA57.
-</p>
-<p>The most interesting part of the patch is the switch from boot paging
-mode to LA57.  Loaders, either legacy or UEFI, pass control to the
-kernel in Long Mode, which implies that the paging is turned on.  This
-necessarily means that it is LA48 mode.  SDM states that paging mode
-cannot be switched while Long Mode is active, so kernel has to create
-new page table structures, turn Long Mode off, then load new %cr3 and
-finally re-enable Long Mode.
-</p>
-<p>I decided to only provide the larger virtual address space to usermode
-for the initial step, leaving KVA layout intact. The main motivation
-is that changing KVA arrangements requires changing the auto-tuning
-settings, which deserve separate work.  Another argument for it is
-that most of the kernel memory is non-swappable, so cannot be
-over-commited.  We have 2:1 ratio of useful KVA to physical memory
-(due to direct map), and until machines get more physical address
-lines, increasing KVA is not useful.
-</p>
-<p>After this was decided, creating a 5-level paging structure for kernel
-pmap from existing 4-level one is quite straightforward; we need to
-add one page for top level, create one PML5 entry to point to existing
-PML4 page, and create the famous self-referential entry for
-vtopte()/vtopde().
-</p>
-<p>Care was taken to provide binary compatible layout of UVA for binaries
-that cannot be executed correctly with larger address space.  For
-instance, programs could have knowledge about used bits in the
-addresses and used upper bits for other data, or implemented
-compressed pointers.  Even if system runs in LA57 mode, specific
-binary can request LA48-compatible UVA by procctl(2) or by the flag in
-the FreeBSD features ELF note.
-</p>
-<p>Since I do not have access to a machine with LA57, development was
-done using QEMU.  It would be interesting to try it on the real
-hardware.
-</p>
-<p>Sponsor: The FreeBSD Foundation<br clear="none" />
-</p><hr /><h2><a name="Not-transparent-superpages" href="#Not-transparent-superpages" id="Not-transparent-superpages">Not-transparent superpages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24652" title="https://reviews.freebsd.org/D24652">Patch</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D24652" title="Patch">https://reviews.freebsd.org/D24652</a></td></tr></table><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p><p>FreeBSD already provides excellent support for superpages, in a
-manner completely transparent to applications.  It tries to
-proactively prevent fragmentation, reserves contiguous runs of the
-physical pages for linear allocations in managed objects, and
-auto-promote runs of small pages when they form complete superpage.
-</p>
-<p>The shortcomings of this approach directly follows from its strength:
-some applications want to get guaranteed superpage mappings, typically
-because the underlying physical memory is also offloaded into a
-hardware which also has memory mapping unit.  For instance, Infiniband
-RMDA adapters do memory registration and remapping, which is more
-efficient with large pages.  In such cases transparent
-(non-guaranteed) support cannot be used.
-</p>
-<p>The extension was developed for POSIX shared memory subsystem to allow
-the creator request that the shared memory object was backed by
-physically contiguous pages, with runs of specified size.  The mmap(2)
-syscall is aware of such objects, and if the requested mapping is
-properly aligned, it will be served by superpages.
-</p>
-<p>The new type of the shared memory objects are backed by a modified
-physical pager, which only allocates contiguous physical memory.  The
-VM ensures that mappings of the objects are never split (clipped) on a
-non-superpage boundary.  The fault handler is specially optimized to
-be very fast by quickly installing the superpage PTE, and to avoid
-touching all small pages constituing it.
-</p>
-<p>Currently the required pmap support is provided for amd64 with 2M and
-1G superpage sizes.
-</p>
-<p>Sponsor: The FreeBSD Foundation<br clear="none" />
-</p><hr /><h2><a name="NXP-ARM64-SoC-support" href="#NXP-ARM64-SoC-support" id="NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></h2><p>
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	<br />
-	Contact: Dawid Gorecki &lt;<a href="mailto:dgr@semihalf.com">dgr@semihalf.com</a>&gt;
-	</p><p>The Semihalf team initiated working on FreeBSD support for the
-<a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A" shape="rect">NXP LS1046A SoC</a>
-</p>
-<p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with
-integrated packet processing acceleration and high speed peripherals
-including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide
-range of networking, storage, security and industrial applications.
-</p>
-<p>Completed since the last update:
-</p><ul>
-<li><p>Improve code in a couple of review cycles and merge following new
-    features to the FreeBSD-HEAD (r361458 - r361464):
-</p><ul>
-<li><p>QorIQ platform clockgen driver
-</p></li>
-<li><p>LS1046A clockgen driver
-</p></li>
-<li><p>GPIO support for QorIQ boards
-</p></li>
-<li><p>QorIQ LS10xx AHCI driver
-</p></li>
-<li><p>VF610 I2C controller support
-</p></li>
-<li><p>TCA6416 GPIO expander
-</p></li>
-<li><p>Epson RX-8803 RTC
-</p>
-</li></ul>
-</li></ul>
-Todo:
-<ul>
-<li><p>Upstreaming of the QorIQ SDHCI driver - it is expected to
-   be submitted/merged to HEAD in the Q3 of 2020.
-</p>
-</li></ul>
-<p>Sponsor: Alstom Group
-</p><hr /><h2><a name="amd64-pmap-Fine-grained-pv-lists-locking" href="#amd64-pmap-Fine-grained-pv-lists-locking" id="amd64-pmap-Fine-grained-pv-lists-locking">amd64 pmap Fine-grained pv lists locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24217" title="https://reviews.freebsd.org/D24217">Patch</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D24217" title="Patch">https://reviews.freebsd.org/D24217</a></td></tr></table><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p><p>FreeBSD kernel Virtual Memory subsystem handles 'normal' application
-memory, i.e. anonymous or file-backed shared and private mappings,
-with so called managed pages.  Managed page is fully controlled by VM,
-which tracks it status.  In particular, managed page can be made
-read-only for write-back to the file, or unmapped for reuse (paging).
-</p>
-<p>The machine-dependent VM layer, pmap, must support managed pages, for
-instance it must provide operations such as pmap_remove_write() to
-downgrade all mappings to read-only, or pmap_remove_all() to unmap
-the page from all address spaces.  To implement this kind of
-operations, while not causing the overhead of scanning all page
-tables, pmap must track existing mappings of the page.  The
-tracking is done by allocating a small data structure 'pv entry'
-per mapping, and linking all pv entries for the given page into pv
-list.
-</p>
-<p>Since pv entries come from context of different address spaces, pmap
-must provide synchronization to guarantee correctness of the list
-structures.  Current pmap allocates one mutex per one 2M physical
-superpage in NUMA configurations, and MAXCPU == 256 locks hashed by
-the page physical address for non-NUMA.  The end result is often
-undeserved lock aliasing causing pv list locks contention, since all
-4k pages in the 2M superpage share the same lock, and reservations
-typically cause adjusted pages to come from the same superpage.
-</p>
-<p>The proposed patch creates a new kernel synchronization primitive
-called one byte mutex, which is embedded into the currently unused
-padding in machine-dependent portion of the struct vm_page.  This way
-each page gets dedicated pv list lock without using any more memory.
-In the ever-important buildkernel benchmark on non-NUMA config, this
-change provides 2x reduction of the system time.
-</p>
-<p>One complication is that old locking distribution scheme made a
-natural fit for superpages promotion and demotion, since all embedded
-small pages shared the same pv list lock, and the operations basically
-fold/unfold corresponding pv entries.  Now the promotion and demotion
-operations require taking all locks for constituent small pages, which
-provides small but measurable impact on them.  It is possible to
-optimize it further by providing the 'superlock' on the first page
-from the superpage run, but the affected operations are relatively
-rare so that it is not even obvious that implementing the optimization
-would not slow down other pathes.
-</p>
-<p>Another important nuance of the pv entries handling is that sometimes
-pv entries allocator must not fail.  Typically this is required when
-kernel makes a call to pmap_enter() which must establish new mapping,
-and for managed page this includes allocating the pv entry if existing
-cannot be reused.  If allocator cannot get a fresh page from the
-vm_page_alloc(9), it opts to destroy some other managed mapping to
-either get a reusable pv entry from current pmap, or destroy enough
-managed mappings from some other pmap to free whole page.
-</p>
-<p>To do the reclamation, currently all pages from which with pv entries
-are allocated, are linked in the global pv chunk list, which is
-protected by global (per-NUMA domain) mutex.  Any allocation or free
-of pv entry has to lock the mutex, which is apparently a contention
-point for large machines.
-</p>
-<p>Patch removes the global list of chunks, instead linking all pmaps in
-the global list like it is done on i386 (but for different reason).
-Now the global lock is only taken for pmap creation and free, which
-corresponds to fork/exec and exit of a process, and when pv allocator
-starts reclaiming from other pmaps (which is normally does not
-happen).
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="Lockless-routing-lookups-and-scalable-multipath" href="#Lockless-routing-lookups-and-scalable-multipath" id="Lockless-routing-lookups-and-scalable-multipath">Lockless routing lookups and scalable multipath</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7" title="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7">Implementation of scalable multipath</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7" title="Implementation of scalable multipath">https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7</a></td></tr></table><p>
-	Contact: Alexander Chernikov &lt;<a href="mailto:melifaro@FreeBSD.org">melifaro@FreeBSD.org</a>&gt;
-	</p>
-<p>The primary goal of this work is to bring scalable routing multipath implementation,  enabled by default. Another goal is enabling high-performance routing lookups.
-</p>
-<p>Multipath will close long-standing feature gap that modern networking OS must have.
-Lockless routing lookups will remove lookup bottlenecks, improve both dataplane and control plane performance for the setups with large number of routes.
-</p>
-<h3>Background</h3>
-
-<p>The initial routing kpi was introduced back in 1980. It was a nice generic approach back then, as no one knew how the protocols would evolve. It has been enormously successful as it was able to survive for 20+ years.
-</p>
-<p>Unfortunately, this kpi does not try to protect subsystem internals from the outside users, resulting in tight coupling with other subsystems. As a result, making changes is hard, leading to compromises and piling technical debt. 
-</p>
-<h3>Implementation overview</h3> 
-
-<p>Most changes are based on introduction of the concept of nexthops. Nexthops are separate datastructures, containing all necessary information to perform packet forwarding such as gateway, interface and mtu. They are shared among the routes, providing more pre-computed cache-efficient data while requiring less memory.
-Interested reader can find more detailed description in <a href="https://reviews.freebsd.org/D24141" shape="rect">D24141</a>. Another overview can be found in Nexthop object <a href="https://linuxplumbersconf.org/event/4/contributions/434/attachments/251/436/nexthop-objects-talk.pdf" shape="rect">talk</a> describing Linux implementation.
-</p>
-<p>Multipath implementation extends nexthop concept further by introducing nexthop groups.
-</p>
-<p>Each route has a pointer to either nexthops or a nexthop group, decoupling lookup algorithm from the routing stack internals. Both nexthops and nexthop groups are immutable and use epoch(9)-backed reclamation.
-</p>
-<p>A pre-requisite for lockless routing lookup is the introduction of modular lookup framework, allowing to attach any longest-prefix-match algorithm implementation to any IPv4/IPv6 fib.
-</p>
-<p>Currently there are plans to use modified DIR-24-8 algorithm from DPDK for both IPv4 and IPv6 families as an example of base lockless implementation.
-</p>
-<h3>Status</h3>
-
-<ul>
-<li><p>Nexthop objects [ DONE ]
-</p></li>
-<ul>
-<li><p>Introduction of nexthop objects [ DONE ]
-</p></li>
-<li><p>Conversion of old KPI users to the new one [ DONE ]
-</p></li>
-<li><p>Conversion of route caching to nexthop caching [ DONE ]
-</p></li>
-<li><p>Conversion of struct <code>rtentry</code> field access to nhop field access [ DONE ]
-</p></li>
-<li><p>Eliminating old lookup KPI and hiding struct rtentry [ DONE ]
-</p></li>
-</ul>
-<li><p>Multipath [ IN PROGRESS ]
-</p></li>
-<ul>
-<li><p>Switch control plane consumers to use (rtentry, nhop) pairs instead of rtentry to allow multipath changes happen transparently [ 90% DONE ]
-</p></li>
-<li><p>Introduce nexthop group objects
-</p></li>
-<li><p>Add mutipath support for the rib (routing information base) manipulation functions
-</p></li>
-<li><p>Add flowid generation for outbound traffic to enable load balancing
-</p></li>
-</ul>
-<li><p>Modular longest-prefix-match lookup algorithm [ IN PROGRESS ]
-</p></li>
-<ul>
-<li><p>Design control plane framework for attaching algorithms [ 90% DONE ]
-</p></li>
-<li><p>Port IPv6 lockless lookup algorithm [ DONE ]
-</p></li>
-<li><p>Port IPv4 lockless lookup algorithm
-</p></li>
-</ul></ul><hr /><h2><a name="ZSTD-Compression-in-ZFS" href="#ZSTD-Compression-in-ZFS" id="ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></h2><p>
-	Contact: Allan Jude &lt;<a href="mailto:allanjude@freebsd.org">allanjude@freebsd.org</a>&gt;
-	</p><p>Zstandard (ZSTD) is a modern high-performance compression
-algorithm designed to provide the compression ratios of gzip
-while offering much better performance. ZSTD has been adopted
-in FreeBSD for a number of other uses, including compressing
-kernel crash dumps, as a replacement for gzip or bzip for
-compressing log files, and for future versions of pkg(8).
-</p>
-<p>This effort to complete the integration of ZSTD into ZFS is
-sponsored by the FreeBSD Foundation.
-</p>
-<p>Integrating ZSTD into ZFS will further extend the transparent
-compression feature of ZFS by offering higher compression
-ratios without the performance penalty associated with gzip.
-ZSTD offers compression levels ranging from 1 (low compression)
-to 22 (maximum compression), plus ZSTD-Fast levels that offer
-less compression but even greater speed. This will allow the
-storage administrator to select the performance-vs-compression
-tradeoff that best suits their needs.
-</p>
-<p>Tasks remaining to be completed:
-</p>
-<ul>
-<li><p>Extend ZFS to support compression algorithms with large numbers of levels
-</p></li>
-<li><p>Solve issues around the inheritence of compression settings
-</p></li>
-<li><p>Restore compression level when reading blocks from disk
-</p></li>
-<li><p>Create a future-proofing scheme to handle changing versions of ZSTD
-</p></li>
-<li><p>Extend ZFS replication to handle backwards compatibility with pools that do not yet support ZSTD
-</p></li>
-<li><p>Resolve issues around backwards compatibility when ZSTD is configured but not used
-</p>
-</li></ul>
-<p>Sponsor: The FreeBSD Foundation  
-</p><hr /><h2><a name="CheriBSD-2020-Q2" href="#CheriBSD-2020-Q2" id="CheriBSD-2020-Q2">CheriBSD 2020 Q2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cheri-cpu.org" title="http://www.cheri-cpu.org">CHERI-CPU</a></td><td>
-	    URL: <a href="http://www.cheri-cpu.org" title="CHERI-CPU">http://www.cheri-cpu.org</a></td></tr><tr><td><a href="https://fett.darpa.mil" title="https://fett.darpa.mil">DARPA FETT Bug Bounty Program</a></td><td>
-	    URL: <a href="https://fett.darpa.mil" title="DARPA FETT Bug Bounty Program">https://fett.darpa.mil</a></td></tr></table><p>
-	Contact: Alex Richardson &lt;<a href="mailto:arichardson@FreeBSD.org">arichardson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jessica Clarke &lt;<a href="mailto:jrtc27@FreeBSD.org">jrtc27@FreeBSD.org</a>&gt;
-	<br />
-	Contact: John Baldwin &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	</p><p>CheriBSD extends FreeBSD to implement memory protection and software
-compartmentalization features supported by the CHERI instruction set
-extensions.
-</p>
-<p>Support for CHERI-RISC-V in CheriBSD has continued to mature this
-quarter in tandem with refinements to the CHERI-RISC-V architecture.
-We have recently made CheriBSD's "pure capability" (CheriABI) process
-environment the default ABI rather than a compatibility layer. It has
-grown support for:
-</p>
-<ul>
-<li><p>dynamically linked binaries (previously only statically-linked binaries were supported)
-</p></li>
-<li><p>C++ including exceptions
-</p></li>
-<li><p>sealed return address and function pointer capabilities ("sentries") which provide additional CFI protection
-</p></li>
-<li><p>initial MMU protections for loading and storing tags
-</p>
-</li></ul>
-<p>At this point, CHERI-RISC-V support in CheriBSD is generally on par with
-support for CHERI-MIPS.
-</p>
-<p>Much of this effort has been focused on preparing CheriBSD on
-CHERI-RISC-V for inclusion as a demonstrator system in DARPA's Finding
-Exploits to Thwart Tampering (<a href="https://fett.darpa.mil" shape="rect">FETT</a>) Bug Bounty
-program.
-</p>
-<p>In addition, work has begun this quarter on porting CheriBSD to Arm's
-Morello SoC.  Morello is a prototype demonstrator board which adds CHERI
-extensions to ARMv8-A.
-</p>
-<p>We've recently switched to a dev-branch model where active work takes
-place on the <code>dev</code> branch and we periodically merge to <code>master</code> with
-synchronization between CheriBSD and dependencies like CHERI-LLVM.
-</p>
-<p>For those interested in what it's like to program for CHERI, we've
-recently released a <a href="https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-947.pdf" shape="rect">CHERI C/C++ Programming
-Guide</a>.
-</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="Continuous-Integration-on-!x86" href="#Continuous-Integration-on-!x86" id="Continuous-Integration-on-!x86">Continuous Integration on !x86</a></h2><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p><p>For quite a while the <a href="https://ci.FreeBSD.org" shape="rect">FreeBSD CI infrastructure</a>
-has been running FreeBSD builds and regression tests, making it easy to
-spot regressions.  While CI was building images for all architectures,
-the regression tests were only run on amd64 and i386, which means they
-couldn't detect architecture-specific runtime breakage on non-x86
-architectures.  This poses a problem not only for FreeBSD itself,
-but also for people working on FreeBSD forks for !x86, such as the CHERI
-project at University of Cambridge and SRI International.
-</p>
-<p>The goal of this project is to run regression tests on the remaining
-architectures supported by FreeBSD: ARM, ARM64, MIPS, POWER, and RISC-V.
-The tests are being run using common, mostly machine-independent scripts.
-Those required some changes to make it possible to use QEMU in addition
-to Bhyve, the hypervisor used for x86 tests.  The <code>sysutils/u-boot-qemu-arm</code>
-and <code>sysutils/u-boot-qemu-arm64</code> ports were added to the Ports Collection.
-Finally, each of the architectures required some tweaks, to account for
-different configuration requirements - for example the MIPS kernel
-doesn't support VirtIO disks, or even AHCI, whereas on ARM64 the U-Boot
-gets confused with more than one VirtIO disk.
-</p>
-<p>On ARM, we're currently at 52 failures and 590 skipped tests, of 5925
-tests ran
-(https://ci.freebsd.org/job/FreeBSD-head-armv7-test/lastCompletedBuild/testReport/).
-On ARM64 it's 19 failures and 160 skipped
-(https://ci.freebsd.org/job/FreeBSD-head-aarch64-test/lastCompletedBuild/testReport/).
-On MIPS it's 172 failures and 734 skipped
-(https://ci.freebsd.org/job/FreeBSD-head-mips64-test/lastCompletedBuild/testReport/).
-For POWER, and RISC-V the results are not available yet.
-</p>
-<p>Remaining work:
-</p>
-<ul>
-<li><p>Failing regression tests need to be fixed.
-</p>
-</li>
-<li><p>The tests are quite slow on QEMU, for example the ARM64 run takes about
-   five hours.  Running them automatically after each commit would quickly
-   overload the CI cluster.  A solution would be to e.g. run them daily.
-</p>
-</li>
-<li><p>Some of the jobs still fail to produce results: powerpc64 deadlocks at
-   the end of regression test suite due to an unkillable process, riscv64
-   panics randomly, and on mips64 kyua(1) often crashes on jemalloc assertion.
-   Those might be fixed by an upcoming QEMU port update.
-</p>
-</li></ul>
-<p>Sponsor: DARPA
-</p><hr /><h2><a name="FreeBSD/RISC-V-Project" href="#FreeBSD/RISC-V-Project" id="FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/riscv" title="https://wiki.freebsd.org/riscv">Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/riscv" title="Wiki">https://wiki.freebsd.org/riscv</a></td></tr></table><p>
-	Contact: Mitchell Horne &lt;<a href="mailto:mhorne@FreeBSD.org">mhorne@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-riscv" shape="rect">freebsd-riscv Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-riscv channel on freenode<br clear="none" />
-</p>
-<p>The <i>FreeBSD/RISC-V</i> project is providing support for running FreeBSD on the
-<a href="https://riscv.org/" shape="rect">RISC-V Instruction Set Architecture</a>. Since RISC-V is still
-a young and evolving platform, one of our goals is to have FreeBSD be a
-well-supported option for users as RISC-V hardware increases in availability.
-</p>
-<p>This quarter saw a number of improvements to the boot process. 
-</p>
-<p>The <code>physmem</code> interface used by arm and arm64 to enumerate physical memory
-resources was moved to machine-independent code and adopted on RISC-V. As a
-result, the kernel is now able to detect and exclude physical memory reserved by
-devices or firmware. A bug that prevented the kernel from using physical memory
-below its load address was fixed. This typically did not manifest in much waste,
-as the kernel is loaded 2MB after the start of physical memory by default. In
-future boot configurations, the impact would have been much larger.
-</p>
-<p>Our port for OpenSBI was updated to v0.8, bringing several new features and
-fixes. In particular, it brought the Hardware State Management (HSM) extension,
-which can be used to start and stop CPUs. FreeBSD will now use this extension
-whenever it detects that it is available.
-</p>
-<p>There has also been a lot of work done to port FreeBSD's standard bootloader,
-<code>loader(8)</code>, to RISC-V. This has big advantages in terms of boot flexibility,
-and brings us closer to what's needed to produce official FreeBSD/RISC-V release
-images. By leveraging UEFI support from
-<a href="https://www.denx.de/wiki/U-Boot/" shape="rect">u-boot</a>, <code>loader.efi</code> can be used in a manner
-similar to arm and arm64. Next quarter will likely bring u-boot ports for RISC-V
-targets, pending the v2020.07 release. Booting the kernel directly via SBI
-firmware will continue to be supported.
-</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><h2><a name="Import-of-new-implementation-of-bc-and-dc" href="#Import-of-new-implementation-of-bc-and-dc" id="Import-of-new-implementation-of-bc-and-dc">Import of new implementation of bc and dc</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://git.yzena.com/gavin/bc" title="https://git.yzena.com/gavin/bc">Official repository</a></td><td>
-	    URL: <a href="https://git.yzena.com/gavin/bc" title="Official repository">https://git.yzena.com/gavin/bc</a></td></tr><tr><td><a href="https://github.com/gavinhoward/bc/" title="https://github.com/gavinhoward/bc/">Repository mirror on GitHub</a></td><td>
-	    URL: <a href="https://github.com/gavinhoward/bc/" title="Repository mirror on GitHub">https://github.com/gavinhoward/bc/</a></td></tr></table><p>
-	Contact: Stefan Esser &lt;<a href="mailto:se@FreeBSD.org">se@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Gavin D. Howard &lt;<a href="mailto:yzena.tech@gmail.com">yzena.tech@gmail.com</a>&gt;
-	</p><p>A new version of bc and dc has been imported into FreeBSD-CURRENT
-and enabled by default.
-An import into 12-STABLE is planned before the end of July, but it
-will not be enabled by default (will require "WITH_GH_BC=yes" to
-be set in /etc/src.conf).
-</p>
-<p>This version has been developed by Gavin D. Howard with the goal
-to provide a highly portable and POSIX compatible implementation.
-It offers GNU bc compatibility and should be a drop-in replacement
-for the bc in FreeBSD, except for standard-violating behavior of
-the bc currently in FreeBSD (e.g., the modulo operator).
-</p>
-<p>Additional features:
-</p>
-<ul>
-<li><p>High performance (up to more than a factor of 100 faster than
-  the current FreeBSD implementation in some tests)
-</p></li>
-<li><p>support of message catalogs with a large number of languages
-  supported in the current release (contributions of further
-  translations are welcome).
-</p></li>
-<li><p>Extra built-in functions and operators.
-</p></li>
-<li><p>Extended library of advanced math functions
-</p></li>
-<li><p>Detailed man-page explaining standard conformant and extended
-  features
-</p></li>
-<li><p>One shared binary for bc and dc (bc is not just a pre-processor
-  that relies on dc for the actual computations)
-</p>
-</li></ul>
-<p>The only dc feature not supported by the dc is the execution of
-sub-processes, since the author considers it a security hazard
-for a calculator to have.
-</p>
-<p>This code is also available as a port and package (math/gh-bc or
-gh-bc), e.g. for use with a FreeBSD binary release.
-</p><hr /><h2><a name="Binutils-Retirement" href="#Binutils-Retirement" id="Binutils-Retirement">Binutils Retirement</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/GPLinBase" title="https://wiki.freebsd.org/GPLinBase">GPL in Base wiki page</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/GPLinBase" title="GPL in Base wiki page">https://wiki.freebsd.org/GPLinBase</a></td></tr></table><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p><p>We have been working on migrating to a modern and copyfree or permissively
-licensed toolchain for quite some time.  In the last quarter we retired two
-obsolete GNU bintuils: objdump, and as.
-</p>
-<p>Many uses of objdump can be replaced with readelf, and llvm-objdump is also
-available in the base system.  Ports that depend on objdump have been updated
-to rely on the GNU binutils port or package.
-</p>
-<p>The GNU as utility was used by both the base system and by ports.  As with objdump, ports
-that require GNU as have generally been updated to depend on binutils.  One
-file in the base system (skein_block_asm.s) proved troublesome during earlier
-attempts to migrate to using Clang's integrated assembler (IAS).  However,
-after the update to Clang 10 (and with some trivial modifications to the
-source) IAS can assemble the file.
-</p>
-<p>Both GNU as and objdump have been removed from FreeBSD-CURRENT and will be
-absent from FreeBSD 13.0.
-</p>
-<h3>TODO</h3>
-
-<p>The final task in the binutils retirement project is to remove GNU GDB 6.1.
-It is currently retained for crashinfo(8).
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="Run-Time-Dynamic-Linker-improvements" href="#Run-Time-Dynamic-Linker-improvements" id="Run-Time-Dynamic-Linker-improvements">Run-Time Dynamic Linker improvements</a></h2><p>
-	Contact: Konstantin Belousov &lt;<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>&gt;
-	</p><p>Rtld gets some number of small bug fixes and improvements.
-</p>
-<p>RTLD_DEEPBIND dlopen(3) flag was implemented, despite being a strange
-and even unsafe idea, for compatibility with glibc.
-</p>
-<p>Several improvements to the direct execution mode were made.  Most
-interesting are perhaps the '-v' switch to report some configuration
-parameters for rtld, the ability to specify argv0 different from the
-executed binary name, and fixes to properly set osrel/ABI for the
-directly executed binary.
-</p>
-<p>The link_map structure that is used by tools that need to know the
-list of loaded shared objects (like gdb and wine) was made more
-compatible with glibc, while keeping existing FreeBSD ABI intact.
-</p>
-<p>In the course of the link_map work, it become apparent that rtld sometimes
-needs to report presence of features that cannot be deduced by just a
-runtime test for symbol presence or for function behavior.  For that,
-a scheme of reporting features with uniformingly named symbols was
-designed - see the rtld(1) man-page (in CURRENT) for an explanation.
-</p>
-<p>Position-independent (PIE) binaries on FreeBSD are now marked with the
-DF_1_PIE DT_FLAG1 flag.  Otherwise, such binaries are just ET_DYN
-objects and it is quite hard to distinguish proper dynamically shared
-object (DSO) from PIE binary.  The problem is that for binaries, the static
-linker strips some information which is required for proper loading as a
-DSO, and additonally, binaries contains relocations like copy-relocations
-that cannot be handled for non-main binaries at all.
-</p>
-<p>With the flag addition, rtld properly detects binaries and refuses to
-load them with dlopen() or as DT_NEEDED dependency. ldd(1) also
-misdetected PIE vs. DSO, and required a fix to parse dynamic segments
-to not try to dlopen() them.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="VHDX-support-in-mkimg(1)" href="#VHDX-support-in-mkimg(1)" id="VHDX-support-in-mkimg(1)">VHDX support in mkimg(1)</a></h2><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p><p>VHDX is the successor of Microsoft's VHD virtual drive file format. It
-increases maximum capacity of the virtual drive to 64TB and introduces features
-to better handle power/system failures. <br clear="none" />VHDX is the required format for 2nd
-generation Hyper-V VMs.
-</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="Bastille" href="#Bastille" id="Bastille">Bastille</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/bastillebsd/bastille" title="https://github.com/bastillebsd/bastille">Bastille GitHub</a></td><td>
-	    URL: <a href="https://github.com/bastillebsd/bastille" title="Bastille GitHub">https://github.com/bastillebsd/bastille</a></td></tr><tr><td><a href="https://gitlab.com/bastillebsd-templates" title="https://gitlab.com/bastillebsd-templates">Bastille Templates</a></td><td>
-	    URL: <a href="https://gitlab.com/bastillebsd-templates" title="Bastille Templates">https://gitlab.com/bastillebsd-templates</a></td></tr><tr><td><a href="https://bastillebsd.org" title="https://bastillebsd.org">Bastille Website</a></td><td>
-	    URL: <a href="https://bastillebsd.org" title="Bastille Website">https://bastillebsd.org</a></td></tr></table><p>
-	Contact: Christer Edwards &lt;<a href="mailto:christer.edwards@gmail.com">christer.edwards@gmail.com</a>&gt;
-	</p><p>Bastille is an open-source system for automating deployment and management of
-containerized applications on FreeBSD.
-</p>
-<p>Bastille Templates automate container setup allowing you to easily reproduce
-containers as needed.
-</p>
-<p>Bastille is available in ports at <code>sysutils/bastille</code>.
-</p>
-<h3>Q2 2020 Status</h3>
-
-<p>In Q2 2020 Bastille merged some exciting new features into GitHub. Changes include:
-</p>
-<ul>
-<li><p>experimental support for new <code>Bastillefile</code> template syntax
-</p></li>
-<li><p>added <code>mount</code> and <code>umount</code> sub-commands
-</p></li>
-<li><p>added a default <code>Vagrantfile</code> for simple testing
-</p></li>
-<li><p>experimental support for empty containers
-</p></li>
-<li><p>improvements to VNET DHCP support
-</p></li>
-<li><p>cosmetic bugfixes in error output
-</p></li>
-<li><p>extended config file documentation
-</p></li>
-<li><p>updated <code>bastille help</code> output
-</p></li>
-<li><p>option to <code>(-f)</code> force destroy container
-</p>
-</li></ul>
-<code>sysutils/bastille</code> was updated to <code>0.6.20200414</code> (latest).
-
-<p>New Bastille templates added this quarter include:
-</p>
-<ul>
-<li><p>Percona database server
-</p></li>
-<li><p>Asterisk SIP server
-</p></li>
-<li><p>dnsmasq DNS/DHCP server (VNET required)
-</p></li>
-<li><p>nginx pkg server for poudriere
-</p>
-</li></ul>
-<p>Everything mentioned here was done under COVID-19 quarantine. Special thanks to
-everyone that contributed during this time.
-</p><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://community.kde.org/FreeBSD" title="https://community.kde.org/FreeBSD">KDE Community FreeBSD</a></td><td>
-	    URL: <a href="https://community.kde.org/FreeBSD" title="KDE Community FreeBSD">https://community.kde.org/FreeBSD</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p><p>The <i>KDE on FreeBSD</i> project packages the software produced by
-the KDE Community for FreeBSD. The software includes a
-full desktop environment KDE Plasma, IDE <a href="https://www.kdevelop.org/" shape="rect">KDevelop</a>,
-a PIM suite <a href="https://kontact.kde.org/" shape="rect">Kontact</a>
-and hundreds of other applications that can be used on
-any FreeBSD desktop machine.
-</p>
-<p>This quarter has been an ever-so-peculiar one. While we are used
-to working remotely, collaborating over the internet to update the ports
-tree, it's <i>qualitatively</i> different when
-the whole world locks down. Meanwhile, software continues to be released,
-so this quarter the kde@ team:
-</p>
-<ul>
-<li><p>Restored a patch that closes down a remote TCP held by X11 applications
-  that use the ICE library. Thanks to Colin Percival for reporting it.
-  It went missing in one of the port updates. To prevent this in the future,
-  the patch has been upstreamed. PR 229772.
-</p></li>
-<li><p>Chased KDE-adjacent software like CMake, Cutelyst, Latte-dock and Nheko
-  through new releases. In particular CMake takes a lot of effort every
-  time because it is a build-time dependency of over 2000 ports.
-</p></li>
-<li><p>graphics/poppler was updated to the latest upstream release. This
-  is a low-level dependency for many document-viewing applications,
-  and like CMake requires chasing a lot of other software.
-  Poppler is one of the components shared between various
-  software stacks (and "desktop environments") under the desktop@
-  group, in which kde@ participates.
-</p></li>
-<li><p>KDE Frameworks release like clockwork, reaching KDE Frameworks 5.70 mid-may.
-</p></li>
-<li><p>KDE Applications -- the KDE release service, really, which delivers
-  libraries, applications, and add-ons -- had one large release,
-  with <a href="https://kde.org/announcements/changelog-releases.php?version=20.04.1" shape="rect">20.04.1</a>
-  landing in the ports tree also mid-may and its monthly update
-  20.04.2 in mid-june.
-</p></li>
-<li><p>Some new Wayland support for KDE Plasma -- we have not tested this on FreeBSD --
-  has appeared and has been duly packaged.
-</p></li>
-<li><p>A great deal of preparation has gone into Qt 5.15. Many ports have been
-  pre-emptively patched for this new -- and last -- LTS release of Qt 5.
-  The update itself has not yet landed, pending a few last bits of fallout.
-</p>  
-</li></ul>
-<p>The kde@ team would like to thank Antoine for many exp-runs, mikael@ for useful tips,
-swills@ for patience and kai@ for dealing with WebEngine.
-</p>
-<p>The next big round of updates for the KDE stack is slated:
-CMake 3.18, Qt 5.15 LTS, and KDE Frameworks 5.71.
-</p><hr /><h2><a name="Haskell-on-FreeBSD" href="#Haskell-on-FreeBSD" id="Haskell-on-FreeBSD">Haskell on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.haskell.org/" title="http://www.haskell.org/">Haskell language homepage</a></td><td>
-	    URL: <a href="http://www.haskell.org/" title="Haskell language homepage">http://www.haskell.org/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-haskell" title="https://github.com/freebsd/freebsd-ports-haskell">Ports development repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ports-haskell" title="Ports development repo">https://github.com/freebsd/freebsd-ports-haskell</a></td></tr></table><p>
-	Contact: Gleb Popov &lt;<a href="mailto:haskell@FreeBSD.org">haskell@FreeBSD.org</a>&gt;
-	</p><p>Haskell is a general-purpose strictly-typed pure functional language.
-The Haskell on FreeBSD projects strives to provide the up-to-date
-Haskell toolchain as well as various application written in this language.
-</p>
-<p>This quarter brought the long-awaited GHC update, which is now at
-version 8.8.3. Along the compiler, the Haskell build system frontend,
-cabal-install, was also upgraded to 3.0.2.0. During this update, numerous
-Haskell ports were updated too.
-</p>
-<p>All existing ports of Haskell applications were migrated to USES=cabal,
-which implements Go-style build proccess - all dependencies are compiled as
-part of the build. As a consequence, ports for Haskell libraries have been
-deprecated and removed.
-</p>
-<p>Upgrading GHC became a tedious task for a single person, so a new GitHub
-repository was created under the FreeBSD organization - 
-<a href="https://github.com/freebsd/freebsd-ports-haskell" shape="rect">freebsd-ports-haskell</a>.
-Right now, work is being done on preparing another GHC upgrade in the <code>ghc-upgrade-810</code>
-branch. Any contributions are welcome.
-</p><hr /><h2><a name="rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD" href="#rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD" id="rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD">rtsx - Porting driver for Realtek SD card reader from OpenBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/hlh-restart/rtsx" title="https://github.com/hlh-restart/rtsx">rtsx</a></td><td>
-	    URL: <a href="https://github.com/hlh-restart/rtsx" title="rtsx">https://github.com/hlh-restart/rtsx</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521">PR204521</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521" title="PR204521">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521</a></td></tr></table><p>
-	Contact: Henri Hennebert &lt;<a href="mailto:hlh@restart.be">hlh@restart.be</a>&gt;
-	</p>
-<p>The rtsx driver for Realtek SD card reader has been ported from OpenBSD.
-Its development snapshot is available via the <a href="http://freshports.org/sysutils/rtsx-kmod/" shape="rect">sysutils/rtsx-kmod</a> port.
-</p>
-<p>From March to May 2020, the code has been completed with the help of Gary
-Jennejohn (gj@) and Jesper Schmitz Mouridsen (jsm@).
-Some tweaks have been imported from the Linux counterpart.
-</p>
-<p>The driver has been successfully tested with:
-</p><ul>
-<li><p>RTS5209 under head (Lenovo ThinkPad L520)
-</p></li>
-<li><p>RTS5227 under stable/11 and releng/12.1
-    (HP ProBook 430 g2, Lenovo ThinkPad T450/T450s)
-</p></li>
-<li><p>RTS5229 under releng/12.1 (Lenovo IdeaPad 120S-14IAP)
-</p></li>
-<li><p>RTS522A under releng/12.1 and head (Intel NUC8i5BE, Lenovo ThinkPad P50s)
-</p></li>
-<li><p>RTS525A under releng/12.1 (Dell Latitude E5570)
-</p></li>
-<li><p>RTL8411B under stable/12 (Acer Aspire E 15 E5-576-77W6)
-</p>
-</li></ul>
-The driver should also work for Realtek RTS5249, RTL8402 and RTL8411.
-
-<p>More tests are welcome, especially for the devices not yet tested.  These
-devices may require more tweaks.
-</p>
-<p>PR204521 contains the bulk of exchanges for completion of the code.
-</p><hr /><h2><a name="Valgrind-updates" href="#Valgrind-updates" id="Valgrind-updates">Valgrind updates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D25452" title="https://reviews.freebsd.org/D25452">Patch for valgrind</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D25452" title="Patch for valgrind">https://reviews.freebsd.org/D25452</a></td></tr></table><p>
-	Contact: Paul Floyd &lt;<a href="mailto:paulf@free.fr">paulf@free.fr</a>&gt;
-	<br />
-	Contact: Kyle Evans &lt;<a href="mailto:kevans@FreeBSD.org">kevans@FreeBSD.org</a>&gt;
-	</p><p>A large amount of work has been done to rebase FreeBSD support on top of
-Valgrind 3.17.0, and to address numerous test suite failures.  Currently,
-almost all of the regression tests pass on amd64.  This is a major improvement
-over the current state of affairs, in which the Valgrind is quite out of date
-and is missing important functionality.  Some follow-up work aims to make
-FreeBSD an officially supported target platform for Valgrind.
-</p>
-<p>The devel/valgrind-devel port is in the process of being updated to point at
-the new work.
-</p><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree, in manpages, or in
-      external books/documents.</p><br /><h2><a name="FreeBSD-Translations-on-Weblate" href="#FreeBSD-Translations-on-Weblate" id="FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="https://wiki.freebsd.org/DocTranslationOnWeblate">Translate FreeBSD on Weblate wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="Translate FreeBSD on Weblate wiki">https://wiki.freebsd.org/DocTranslationOnWeblate</a></td></tr><tr><td><a href="https://translate-dev.freebsd.org/" title="https://translate-dev.freebsd.org/">FreeBSD Weblate Instance</a></td><td>
-	    URL: <a href="https://translate-dev.freebsd.org/" title="FreeBSD Weblate Instance">https://translate-dev.freebsd.org/</a></td></tr></table><p>
-	Contact: Danilo G. Baio &lt;<a href="mailto:dbaio@FreeBSD.org">dbaio@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Edson Brandi &lt;<a href="mailto:ebrandi@FreeBSD.org">ebrandi@FreeBSD.org</a>&gt;
-	</p><p>This quarter was improved the renderization of RTL (Right-to-left) languages on the FreeBSD Documentation. We faced this issue after the first RTL language joined the translations effort (fa_IR).
-</p>
-<p>We are looking forward to receive more languages and translators to the project as well.
-</p>
-<h3>Q2 2020 Status</h3>
-
-<ul>
-<li><p><b>10</b> languages (No new languages)
-</p></li>
-<li><p><b>80</b> registered users (33 new users since last quarter)
-</p>
-</li></ul>
-<h4>Languages</h4>
-
-<ul>
-<li><p>Chinese (Simplified) (zh_CN)
-</p></li>
-<li><p>Chinese (Traditional) (zh_TW)
-</p></li>
-<li><p>French (fr_FR)
-</p></li>
-<li><p>German (de_DE)
-</p></li>
-<li><p>Italian (it_IT)
-</p></li>
-<li><p>Norwegian (nb_NO)
-</p></li>
-<li><p>Persian (fa_IR)
-</p></li>
-<li><p>Portuguese (pt_BR)
-</p></li>
-<li><p>Spanish (es_ES)
-</p></li>
-<li><p>Turkish (tr-TR)
-</p>
-</li></ul>
-<p>We want to thank everyone that contributed, translating or reviewing documents.
-And please, help promote this effort on your local user group, we always need more volunteers.
-</p><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><p>Objects that defy categorization.</p><br /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freshports.org/" title="http://freshports.org/">FreshPorts</a></td><td>
-	    URL: <a href="http://freshports.org/" title="FreshPorts">http://freshports.org/</a></td></tr><tr><td><a href="http://news.freshports.org/" title="http://news.freshports.org/">FreshPorts blog</a></td><td>
-	    URL: <a href="http://news.freshports.org/" title="FreshPorts blog">http://news.freshports.org/</a></td></tr></table><p>
-	Contact: Dan Langille &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-<p>FreshPorts, and its sister site, FreshSource, have reported
-upon FreeBSD commits for 20 years. They cover all commits,
-not just ports.
-</p>
-<p>FreshPorts tracks the commits and extracts data from the
-port Makefiles to create a database of information useful
-to both port developers and port users.
-</p>
-<p>For example, https://www.freshports.org/security/acme.sh/ shows
-the history of this port, back to its creation in May 2017.
-</p>
-<h3>git</h3>
-
-<p>Work on git started <a href="https://news.freshports.org/?s=git&amp;searchsubmit=" shape="rect">back in September</a>.
-It was ignored for a while and started back in mid-June with 
-the creation of new git-specific jails for commit ingress (commit
-processing gitdev) and for the website.
-</p>
-<p>Serhii (Sergey) Kozlov <a href="https://github.com/FreshPorts/git_proc_commit/blob/master/git-to-freshports/git-to-freshports.py" shape="rect">created a script</a>
-to transform GIT commit entries into XML digestible by FreshPorts.
-This was a huge step foward for the effort.
-</p>
-<p>The next step include:
-</p>
-<ul>
-<li><p>incorporate a that script the automated processes of FreshPorts
-</p></li>
-<li><p>migrate to new test &amp; stage versions of FreshPorts
-</p></li>
-<li><p>test
-</p></li>
-<li><p>get ready for prod
-</p>
-</li></ul>
-<h4>Help wanted</h4>
-
-<p>git is not far away now. I could use helpers to
-</p>
-<ul>
-<li><p>review code
-</p></li>
-<li><p>watch the commits on the devgit websites
-</p></li>
-<li><p>catch missing stuff
-</p>
-</li></ul>
-Thank you
-
-<h3>Packages</h3>
-
-<p>FreshPorts now displays the packages version available from the
-repo sources. This covers all primary tiers (e.g. FreeBSD:12:amd64)
-and all secondary tiers (e.g. FreeBSD:13:powerpc64). This helps
-uses know what versions they can expect and when then repo was last
-built.
-</p>
-<h3>Dependency lines</h3>
-
-<p>Some things are easiest done via copy/paste. If you are working on a port
-Makefile and need to add a new dependency, FreshPorts shows the dependency
-line for that port.  For example:
-</p>
-<p><pre xml:space="preserve"><code>
-acme.sh&gt;0:security/acme.sh
-</code></pre>
-</p>
-<p>Libraries are also covered by this feature.
-</p>
-<p>Python ports were recently adjusted to display
-</p>
-<p><pre xml:space="preserve"><code>
- ${PYTHON_PKGNAMEPREFIX}virtualenv&gt;0:devel/py-virtualenv
-</code></pre>
-</p>
-<p>instead of
-</p>
-<p><pre xml:space="preserve"><code>
-py37-virtualenv&gt;0:devel/py-virtualenv
-</code></pre>
-</p>
-<p>You can read more about this change in [issue
-#73](https://github.com/FreshPorts/freshports/issues/73).
-</p>
-
-<h3>Watch ports I maintain</h3>
-
-<p>The <a href="https://www.freshports.org/search.php" shape="rect">search page</a> has long had
-the "Ports I Maintain" button (if you are logged in). This feature recently
-branched out to a new automated watch list option: <code>Watch ports I maintain</code>.
-</p>
-<p>This <a href="https://www.freshports.org/report-subscriptions.php" shape="rect">report subscription</a> 
-will notify you of any commits to the ports you maintain. Your email 
-address on FreshPorts must match the value in the MAINTAINER field of the port.
-This is always a daily report.
-</p>
-<p>From time to time, an infrastructure change will occur which touches your
-port. This feature ensures you know about that change.
-</p>
-<h3>Repology links</h3>
-
-<p>Repology links were requested. This allows you to see what versions of that
-port are in the repositories of other systems. A link to repology.org
-appears on every port page.
-</p>
-<h3>Further reading</h3>
-
-<p>Based upon <a href="https://news.freshports.org/2019/09/03/things-you-didnt-know-freshports-can-do/" shape="rect">things you didn&#8217;t know FreshPorts can do</a>
-</p>
-
-<p>There are many things FreshPorts can do, including search Makefile's and
-<code>pkg-plist</code>. This is from a recent blog post:
-</p>
-<ul>
-<li><p>provides example dependency line. e.g. p5-XML-RSS&gt;0:textproc/p5-XML-RSS
-</p></li>
-<li><p>list of dependencies for a port
-</p></li>
-<li><p>list of ports depending upon this port
-</p></li>
-<li><p>see default configuration options
-</p></li>
-<li><p>what packages install a given file (e.g. bin/unzip)
-</p></li>
-<li><p>find out what ports a person maintains
-</p></li>
-<li><p>find Makefiles which contain references to bunzip
-</p></li>
-<li><p>search results can be plain-text consisting of a list of foo/bar ports
-</p></li>
-<li><p>the Maximum Effort checkbox on the search page does nothing
-</p></li>
-<li><p>committers can be notified of sanity test failures after the commit
-</p></li>
-<li><p>find a commit, any commit, based on SVN revision number, e.g. : https://www.freshports.org/commit.php?revision=352332
-</p>
-
-</li></ul>
-<h3>Javascript help wanted</h3>
-
-<p>We <a href="https://github.com/FreshPorts/freshports/commit/f620270161dd7818272dfebacacaaf26df5f37e6" shape="rect">recently upgraded</a>
-some outdated Javascript modules. This broke our [JavaScript based
-graphs](https://www.freshports.org/graphs2.php). We could use some help on
-fixing that please. The starting points are listed on that URL.  If you need
-a working website to play with, please contact me with a ssh public-key.
-</p>
-
-<p>Sponsor: hardware provided by iXsystems
-</p><hr /><h2><a name="PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests" href="#PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests" id="PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests">PCI passthrough with bhyve on Intel and for OpenBSD guests</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852">bhyve Intel bug report</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852" title="bhyve Intel bug report">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392">bhyve OpenBSD bug report</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392" title="bhyve OpenBSD bug report">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392</a></td></tr><tr><td><a href="https://wiki.freebsd.org/bhyve/pci_passthru" title="https://wiki.freebsd.org/bhyve/pci_passthru">PCI passthrough with bhyve (FreeBSD wiki article)</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/bhyve/pci_passthru" title="PCI passthrough with bhyve (FreeBSD wiki article)">https://wiki.freebsd.org/bhyve/pci_passthru</a></td></tr></table><p>
-	Contact: Anatoli &lt;<a href="mailto:me@anatoli.ws">me@anatoli.ws</a>&gt;
-	<br />
-	Contact: Callum &lt;<a href="mailto:callum@aitchison.org">callum@aitchison.org</a>&gt;
-	<br />
-	Contact: Peter Grehan &lt;<a href="mailto:grehan@freebsd.org">grehan@freebsd.org</a>&gt;
-	</p>
-<p>bhyve(8) is a hypervisor that supports running a variety of guest
-operating systems in virtual machines. bhyve(8) includes support for PCI
-devices passthru, a technique to pass host PCI devices to a virtual
-machine for its exclusive control and use.
-</p>
-<p>For some years, PCI passthrough (ppt) in bhyve was not working on some
-Intel systems and for OpenBSD guests due to two bugs. The first one was
-crashing FreeBSD host when bhyve was started with ppt on Intel
-processors with two VT-d translation units (IOMMU), included in most
-Skylake and newer Intel processors.
-</p>
-<p>The second bug was preventing correct interrupts handling for OpenBSD
-guests. As a result, OpenBSD guests running on bhyve were not able to
-use any PCI devices passed through to them from the host.
-</p>
-<p>During the last 2 months the second bug was identified and fixed and
-they both were backported to 12.1-RELEASE (p7). So now it's possible to
-fully take advantage of PCI passthrough (ppt) with bhyve in a
-production-ready RELEASE version.
-</p>
-<p>The most typical case for ppt is to pass to the guest network adapters
-for its complete control, but you can also pass through USB devices
-(including external HDDs). Note though, passthrough of VGA and GPU
-devices is not supported yet (for more details see the 3rd link).
-</p>
-<p>A particularly interesting case for ppt is to use OpenBSD guest as a
-firewall and a router for a FreeBSD server.
-</p>
-<p>With ppt you can achieve this all inside a single server. You could pass
-to the OpenBSD guest a network adapter connected to the internet and it
-would take a complete control of it. After filtering the traffic, it
-could pass good packets via virtual network interfaces to other guests
-or to the host.
-</p>
-<p>Once a network adapter is passed through, a FreeBSD host not only
-doesn't see it and hence doesn't handle the network traffic, it doesn't
-even have to initialize the adapter (e.g. in case of a WiFi card, it's
-the guest that loads the firmware).
-</p>
-<p>In simple terms the host only passes the device interrupts to the guest
-as they come from the hardware. Everything related to the device
-management happens inside the guest so there's no danger that some
-network traffic exploits some issue in the host's network stack and
-causes the host to crash or misbehave in other ways.
-</p><hr /><h2><a name="SageMath" href="#SageMath" id="SageMath">SageMath</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.sagemath.org/" title="https://www.sagemath.org/">SageMath site</a></td><td>
-	    URL: <a href="https://www.sagemath.org/" title="SageMath site">https://www.sagemath.org/</a></td></tr></table><p>
-	Contact: Thierry Thomas &lt;<a href="mailto:thierry@FreeBSD.org">thierry@FreeBSD.org</a>&gt;
-	</p><p>SageMath is a free open-source mathematics software system licensed
-under the GPL. It builds on top of many existing open-source packages:
-NumPy, SciPy, matplotlib, Sympy, Maxima, GAP, FLINT, R and many more.
-Thanks to SageMath it is possible to access their combined power through a
-common, Python-based language or directly via interfaces or wrappers.
-</p>
-<p>The goal is creating a viable free open source alternative to Magma, Maple,
-Mathematica and Matlab.
-</p>
-<p>This is a complex port, with a lot of dependencies, and it has been
-broken for some time. Upstream is working on easing its packaging, and
-many previously bundled applications can now be replaced by external
-packages.
-</p>
-<p>If you are interested, it would be nice to create a team of maintainers
-</p>
-<ul>
-<li><p>to maintain some of the dependencies;
-</p></li>
-<li><p>to maintain SageMath itself and prepare the next release (9.2 is coming!).
-</p></li></ul>
-<hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest 
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="chaifi---a-tool-to-simplify-joining-public-WiFi-networks" href="#chaifi---a-tool-to-simplify-joining-public-WiFi-networks" id="chaifi---a-tool-to-simplify-joining-public-WiFi-networks">chaifi - a tool to simplify joining public WiFi networks</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/chaifi" title="https://github.com/gonzoua/chaifi">chaifi</a></td><td>
-	    URL: <a href="https://github.com/gonzoua/chaifi" title="chaifi">https://github.com/gonzoua/chaifi</a></td></tr></table><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p><p>chaifi is a TUI (text UI) utility aimed at simplifying the process of joining
-public WiFi networks in places like coffee shops or libraries. It replaces the
-process of scanning and manually editing wpa_supplicant.conf with an
-interactive dialog. The utility is in no way a replacement for full-featured
-network managers in major desktop environments. Still, if you're working from a
-console or using a tiling window manager, it may save you some seconds (or in
-worst case minutes) of your time.
-</p><hr /><h2><a name="MixerTUI" href="#MixerTUI" id="MixerTUI">MixerTUI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/alfix/mixertui" title="https://gitlab.com/alfix/mixertui">mixertui</a></td><td>
-	    URL: <a href="https://gitlab.com/alfix/mixertui" title="mixertui">https://gitlab.com/alfix/mixertui</a></td></tr></table><p>
-	Contact: Alfonso Sabato Siciliano &lt;<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>&gt;
-	</p><p>MixerTUI is a volume mixer with a Terminal User Interface built on the FreeBSD
-sound system. It can show the current Sound Driver configuration and select an
-audio device: to get its information, to change the volume or to set it as
-default, the last feature allows to switch easily audio from/to laptop and hdmi,
-headphones and speakers, and so on.<br clear="none" />
-MixerTUI can be installed via the audio/mixertui port.
-</p>
-<p>I would like to thank the FreeBSD community for the tips, feedbacks and patches
-to improve this project.
-</p><hr /><h2><a name="Potluck---Flavour-&amp;-Image-Repository-for-pot" href="#Potluck---Flavour-&amp;-Image-Repository-for-pot" id="Potluck---Flavour-&amp;-Image-Repository-for-pot">Potluck - Flavour &amp; Image Repository for pot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://potluck.honeyguide.net/" title="https://potluck.honeyguide.net/">Potluck Repository &amp; Project</a></td><td>
-	    URL: <a href="https://potluck.honeyguide.net/" title="Potluck Repository &amp; Project">https://potluck.honeyguide.net/</a></td></tr><tr><td><a href="https://github.com/hny-gd/potluck" title="https://github.com/hny-gd/potluck">Potluck on github</a></td><td>
-	    URL: <a href="https://github.com/hny-gd/potluck" title="Potluck on github">https://github.com/hny-gd/potluck</a></td></tr><tr><td><a href="https://pot.pizzamig.dev" title="https://pot.pizzamig.dev">pot project</a></td><td>
-	    URL: <a href="https://pot.pizzamig.dev" title="pot project">https://pot.pizzamig.dev</a></td></tr></table><p>
-	Contact: Stephan Lichtenauer &lt;<a href="mailto:sl@honeyguide.eu">sl@honeyguide.eu</a>&gt;
-	</p><p>pot is a jail management tool that <a href="https://www.freebsd.org/news/status/report-2020-01-2020-03.html#pot-and-the-nomad-pot-driver" shape="rect">also supports orchestration through nomad</a>.
-</p>
-<p>Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: A repository of pot flavours and complete images for usage with pot. 
-</p>
-<p>This should simplify setting up complex software with many packages and ports in comparison to manual configuration: Potluck aims to provide a content library as an additional layer of abstraction, on top of existing infrastructure like pkg, that pot has to offer.
-</p>
-<p>Pot "flavour" files are provided on [Github]((https://github.com/hny-gd/potluck)) and fed into a Jenkins instance. On the <a href="https://potluck.honeyguide.net/" shape="rect">Potluck Repository</a>, for each flavour, detailed descriptions as well as ready-made images to be imported by pot are provided.
-</p>
-<p>The initial project has been set up, and three simple flavours, along with <a href="https://potluck.honeyguide.net/blog/jitsi-meet-nomad/" shape="rect">a complete Jitsi Meet instance in a jail</a> has been created as a Proof of Concept that should allow running a fully-fledged video conference system with just a few easy commands within a few minutes.
-</p>
-<p>As only the initial versions have been set up and implemented so far, general feedback, tests, as well as additional, useful flavours are very welcome!
-</p><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2020-07-2020-09.html b/website/content/en/status/report-2020-07-2020-09.html
deleted file mode 100644
index 08de9755f4..0000000000
--- a/website/content/en/status/report-2020-07-2020-09.html
+++ /dev/null
@@ -1,1927 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects for the period between
-July and September, and is the third of four planned reports for 2020.
-</p><p>This quarter brings a good mix of additions and changes to the FreeBSD
-Project and community, from a diverse number of teams and people covering
-everything from architectures, continuous integration, wireless networking
-and drivers, over drm, desktop and third-party project work, as well as
-several team reports, along with many other interesting subjects too
-numerous to mention.
-</p><p>As the world is still affected by the epidemic, we hope that this report
-can also serve as a good reminder that there is good work that can be done
-by people working together, even if we're apart.
-</p><p>We hope you'll be as interested in reading it, as we've been in making it.<br clear="none" />
-Daniel Ebdrup Jensen, on behalf of the quarterly team.
-</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Cluster-Administration-Team">Cluster Administration Team</a></li><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#FreeBSD-Office-team---3rd-quarter-2020-report">FreeBSD Office team - 3rd quarter 2020 report</a></li><li><a href="#FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></li><li><a href="#Building-FreeBSD-on-non-FreeBSD-hosts">Building FreeBSD on non-FreeBSD hosts</a></li><li><a href="#Git-Migration-Working-Group">Git Migration Working Group</a></li><li><a href="#Linux-compatibility-layer-update">Linux compatibility layer update</a></li><li><a href="#LLDB-Debugger-Improvements">LLDB Debugger Improvements</a></li><li><a href="#Lua-usage-in-FreeBSD">Lua usage in FreeBSD</a></li><li><a href="#NFS-over-TLS-implementation">NFS over TLS implementation</a></li><li><a href="#syzkaller-on-FreeBSD">syzkaller on FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#DRM-Drivers-Update">DRM Drivers Update</a></li><li><a href="#DTS-Update">DTS Update</a></li><li><a href="#DesignWare-Ethernet-adapter-driver-improvements">DesignWare Ethernet adapter driver improvements</a></li><li><a href="#Google-Summer-of-Code&#8217;20-Project---eBPF-XDP-Hooks">Google Summer of Code&#8217;20 Project - eBPF XDP Hooks</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#IPSec-Extended-Sequence-Number-(ESN)-support">IPSec Extended Sequence Number (ESN) support</a></li><li><a href="#NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></li><li><a href="#Addition-of-PowerPC64LE-Architecture">Addition of PowerPC64LE Architecture</a></li><li><a href="#ure---USB-3.0-Gigabit-Ethernet-Driver-update">ure - USB 3.0 Gigabit Ethernet Driver update</a></li><li><a href="#Stateless-hardware-offloads-for-VXLANs">Stateless hardware offloads for VXLANs</a></li><li><a href="#Wireless-updates">Wireless updates</a></li><li><a href="#ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#CheriBSD-2020-Q3">CheriBSD 2020 Q3</a></li><li><a href="#FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Update-to-grub-bhyve">Update to grub-bhyve</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#DOCNG-on-FreeBSD">DOCNG on FreeBSD</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#Potluck---Flavour-&amp;-Image-Repository-for-pot">Potluck - Flavour &amp; Image Repository for pot</a></li><li><a href="#Puppet">Puppet</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-	Page</a>.</p><br /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p><p>The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
-supporting and promoting the FreeBSD Project and community worldwide.  Funding
-comes from individual and corporate donations and is used to fund and manage
-software development projects, conferences and developer summits, and provide
-travel grants to FreeBSD contributors.  The Foundation purchases and supports
-hardware to improve and maintain FreeBSD infrastructure and provides resources
-to improve security, quality assurance, and release engineering efforts;
-publishes marketing material to promote, educate, and advocate for the FreeBSD
-Project; facilitates collaboration between commercial vendors and FreeBSD
-developers; and finally, represents the FreeBSD Project in executing contracts,
-license agreements, and other legal arrangements that require a recognized
-legal entity.
-</p>
-<p>Here are some highlights of what we did to help FreeBSD last quarter:
-</p>
-<h3>COVID-19 Impact to the Foundation</h3>
-
-<p>Like other organizations, we put policies in place for all of our staff members
-to work from home.  We also put a temporary ban on travel for staff members.
-We are continuing our work supporting the community and Project, but some of
-our work and responses may be delayed because of changes in some of our
-priorities and the impact of limited childcare for a few of our staff members.
-</p>
-<h3>Partnerships and Commercial User Support</h3>
-
-<p>We help facilitate collaboration between commercial users and FreeBSD
-developers.  We also meet with companies to discuss their needs and bring that
-information back to the Project.  Not surprisingly, the stay at home orders,
-combined with our company ban on travel during Q3 made in-person meetings
-non-existent.  However, the team was able to continue meeting with our partners
-and commercial users virtually.  These meetings help us understand some of the
-applications where FreeBSD is used.
-</p>
-<p>We are currently scheduling Zoom company meetings for Q4, please reach out if
-you would like to schedule a meeting with us.
-</p>
-<h3>Fundraising Efforts</h3>
-
-<p>Last quarter we raised $192,874.43!  Thank you to the individuals and
-organizations that stepped in, to help fund our efforts.  We'd like to thank
-Arm for their large contribution last quarter, which helped bring our 2020
-fundraising effort to $521k.  We hope other organizations will follow their
-lead and give back to help us continue supporting FreeBSD.
-</p>
-<p>These are trying times, and we deeply appreciate every donation that has come
-in from $5 to $150,000. We're still here giving 110% to supporting FreeBSD!
-</p>
-<p>We are 100% funded by donations, and those funds go towards software
-development work to improve FreeBSD, FreeBSD advocacy around the world, keeping
-FreeBSD secure, continuous integration improvements, sponsoring BSD-related and
-computing conferences (even the virtual events!), legal support for the
-Project, and many other areas.
-</p>
-<p>Please consider making a
-<a href="https://www.FreeBSDfoundation.org/donate/." shape="rect">donation to help us continue and increase our support for FreeBSD</a>.
-</p>
-<p>We also have the Partnership Program, to provide more benefits for our larger
-commercial donors.  Find out more information about the
-<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">partnership program</a>
-and share with your companies!
-</p>
-<h3>OS Improvements</h3>
-
-<p>A number of FreeBSD Foundation grant recipients started, continued working on,
-or completed projects during the third quarter.  These include:
-</p><ul>
-<li><p>Ongoing WiFi and Linux KPI layer improvements.
-</p></li>
-<li><p>Linuxulator application compatibility.
-</p></li>
-<li><p>DRM / Graphics driver updates.
-</p></li>
-<li><p>Zstd compression for OpenZFS.
-</p></li>
-<li><p>Online RAID-Z expansion.
-</p></li>
-<li><p>Modernized LLDB target support for FreeBSD.
-</p>
-</li></ul>
-You can find more details about most of these projects in other quarterly
-<p>reports.
-</p>
-<p>Staff members also worked on a number of larger projects, including:
-</p><ul>
-<li><p>Run-Time Dynamic Linker (rtld) and kernel ELF loader improvements.
-</p></li>
-<li><p>Rewritten UNIX domain socket locking.
-</p></li>
-<li><p>Build infrastructure.
-</p></li>
-<li><p>Open system call path handling support for O_BENEATH, O_RESOLVE_BENEATH.
-</p></li>
-<li><p>arm64 support.
-</p></li>
-<li><p>Migration to a Git repository.
-</p>
-</li></ul>
-Many of these projects also have detailed entries in other quarterly report
-<p>entries.
-</p>
-<p>Staff members also put in significant effort in many ways other than larger,
-individual projects.  These include assisting with code reviews, bug report
-triage, security report triage and advisory handling, addressing syzkaller
-reports, and ongoing maintenance and bug fixes in functional areas such as the
-tool chain, developer tools, virtual memory kernel subsystem, low-level x86
-infrastructure, sockets and protocols, and others.
-</p>
-<h3>University of Waterloo Co-op</h3>
-
-<p>With the transition to working from home, the Foundation decided to again take
-on three University of Waterloo Co-op students for the Fall 2020 term
-(September to December).  Tiger returns for a second term, joined by new
-students Yang and Zac.  Projects for the term include more work on
-ELF Tool Chain, application of Capsicum to additional utilities, testing and
-integration of FreePBX and Asterisk VOIP software, pkgbase, and exploring
-containerization tooling.
-</p>
-<h3>Continuous Integration and Quality Assurance</h3>
-
-<p>The Foundation provides a full-time staff member and funds projects on
-improving continuous integration, automated testing, and overall quality
-assurance efforts for the FreeBSD project.
-</p>
-<p>During the third quarter of 2020, Foundation staff continued improving and
-monitoring the Project's CI infrastructure, and working with experts to fix
-the failing builds and the regressions found by tests.  The setting up of
-dedicated VM host for running tests is completed.  New feature developments
-and the CI staging environment is in progress.  We are also working with
-other teams in the Project for their testing needs. For example, tests of
-non-x86 architectures now run periodically, and improve the CI of the
-embedded systems. We are also working with many external projects and
-companies to improve the CI between their products and FreeBSD.
-</p>
-<p>See the FreeBSD CI section of this report for completed work items and detailed
-information.
-</p>
-<h3>Supporting FreeBSD Infrastructure</h3>
-
-<p>The Foundation provides hardware and support to improve the FreeBSD
-infrastructure.  Last quarter, we continued supporting FreeBSD hardware located
-around the world.  We coordinated efforts between the new NYI Chicago facility
-and clusteradm to start working on getting the facility prepared for some of
-the new FreeBSD hardware we are planning on purchasing.  NYI generously
-provides this for free to the Project.  We also worked on connecting with the
-new owners of the Bridgewater site, where most of the FreeBSD infrastructure is
-located.
-</p>
-<p>Some of the purchases we made for the Project last quarter to support
-infrastructure includes:
-</p><ul>
-<li><p>Spamhaus spam filtering software to limit the amount of spam on the mailing
-lists.
-</p></li>
-<li><p>5 application servers to run tasks like bugzilla, wiki, website, cgi,
-Phabricator, host git, etc.
-</p></li>
-<li><p>1 server to replace the old pkg server and provide a lot more IOPS to
-   avoid the slowdowns seen during peak times of the day where the disks just
-cannot keep up with the request volume.
-</p></li>
-<li><p>1 server for exp-runs to make them faster.
-</p></li>
-<li><p>1 server to build packages more frequently.
-</p>
-</li></ul>
-<h3>FreeBSD Advocacy and Education</h3>
-
-<p>A large part of our efforts are dedicated to advocating for the Project.  This
-includes promoting work being done by others with FreeBSD; producing advocacy
-literature to teach people about FreeBSD and help make the path to starting
-using FreeBSD or contributing to the Project easier; and attending and getting
-other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD
-tables, and give FreeBSD presentations.
-</p>
-<p>The FreeBSD Foundation sponsors many conferences, events, and summits around
-the globe.  These events can be BSD-related, open source, or technology events
-geared towards underrepresented groups.  We support the FreeBSD-focused events
-to help provide a venue for sharing knowledge, to work together on projects,
-and to facilitate collaboration between developers and commercial users.  This
-all helps provide a healthy ecosystem.  We support the non-FreeBSD events to
-promote and raise awareness of FreeBSD, to increase the use of FreeBSD in
-different applications, and to recruit more contributors to the Project.  As is
-the case for most of us in this industry, COVID-19 has put our in-person events
-on hold.  In addition to attending virtual events, we are continually working
-on new training initiatives and updating our selection of how-to guides to
-facilitate getting more folks to try out FreeBSD.
-</p>
-<p>Check out some of the advocacy and education work we did last quarter:
-</p><ul>
-<li><p>Launched our FreeBSD Fridays series of 101 classes.  Topics included an
-   Introduction to FreeBSD, FreeBSD Installfest, Introduction to Security,
-   Introduction to ZFS and more.  Videos of the past sessions and a schedule of
-   upcoming events can be found <a href="https://freebsdfoundation.org/freebsd-fridays/" shape="rect">here</a>.
-</p></li>
-<li><p>Attended and presented at OSI's State of the Source conference.  The event
-was held virtually, September 9-11, 2020.
-</p></li>
-<li><p>Launched the
-   <a href="https://freebsdfoundation.org/blog/weve-got-a-new-look/" shape="rect">redesign</a>
-of the FreeBSD Foundation Website.
-</p></li>
-<li><p><a href="https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-celebrates-20th-anniversary/" shape="rect">Announced</a>
-the 20th Anniversary of the FreeBSD Foundation.
-</p></li>
-<li><p>Participated as an Admin for Google Summer of Code 2020
-</p></li>
-<li><p>Continued to promote the FreeBSD Office Hours series including holding our
-   own Foundation led office hours.  Videos from the one hour sessions can be
-found on the Project's
-   <a href="https://www.youtube.com/c/FreeBSDProject" shape="rect">YouTube Channel</a>.  You can watch
-   ours <a href="https://www.youtube.com/watch?v=Ji4ux4FWpRU" shape="rect">here</a>.
-</p></li>
-<li><p><a href="https://freebsdfoundation.org/blog/freebsd-core-team-10-in-review/" shape="rect">Interviewed</a>
-   members of the outgoing FreeBSD Core Team to get their thoughts on their
-term.
-</p></li>
-<li><p>Began working with the FreeBSD Vendor Summit planning committee on the
-   <a href="https://wiki.freebsd.org/DevSummit/202011" shape="rect">November 2020 Vendor Summit</a>.
-</p></li>
-<li><p>Promoted the Foundation's 20th Anniversary and our work to support the
-   FreeBSD Project in the It's FOSS Article.
-   <a href="https://itsfoss.com/freebsd-foundation-20-years/" shape="rect">FreeBSD Foundation Celebrates 20 Years of Promoting and Supporting FreeBSD Project</a>.
-</p></li>
-<li><p>Authored a <a href="https://www.fosslife.org/beginners-guide-freebsd" shape="rect">Beginners Guide to FreeBSD</a> for Fosslife.
-</p></li>
-<li><p>Committed to sponsoring All Things Open as a media Sponsor.
-</p></li>
-<li><p>Committed to sponsoring the OpenZFS Developers Summit at the Bronze level.
-</p></li>
-<li><p>Became an International RISC-V Member.
-</p></li>
-<li><p>Committed to giving a FreeBSD talk at the nerdear.la conference on
-   October 20th.
-</p>
-</li></ul>
-Keep up to date with our latest work in our
-<p><a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">monthly newsletters</a>.
-</p>
-<p>Netflix provided an update on how and why they use FreeBSD in our latest
-<a href="https://freebsdfoundation.org/wp-content/uploads/2020/10/netflixcasestudy_final.pdf" shape="rect">Contributor Case Study</a>.
-</p>
-<p>We help educate the world about FreeBSD by publishing the professionally
-produced FreeBSD Journal.  As we mentioned previously, the FreeBSD Journal is
-now a free publication.  Find out more and access the latest issues at
-https://www.FreeBSDfoundation.org/journal/.
-</p>
-<p>You can find out more about events we attended and upcoming events at
-https://www.FreeBSDfoundation.org/news-and-events/.
-</p>
-<h3>Legal/FreeBSD IP</h3>
-
-<p>The Foundation owns the FreeBSD trademarks, and it is our responsibility to
-protect them.  We also provide legal support for the core team to investigate
-questions that arise.  We updated our
-<a href="https://freebsdfoundation.org/legal/trademark-usage-terms-and-conditions/" shape="rect">Trademark Usage Terms and Conditions</a>
-on July 1, 2020.
-</p>
-<p>Go to <a href="http://www.FreeBSDfoundation.org/" shape="rect">the FreeBSD Foundation's web site</a> to
-find out how we support FreeBSD and how we can help you!
-</p>
-<h3>Other</h3>
-
-<p>We welcomed Andrew Wafaa and Kevin Bowling to our board of directors, to help
-govern the Foundation and guide us with our strategic direction.  We have
-<a href="https://freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-board-members-2/" shape="rect">more information about our new board members</a>
-on our website.
-</p><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/12.2R/schedule.html" title="https://www.freebsd.org/releases/12.2R/schedule.html">FreeBSD 12.2-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/12.2R/schedule.html" title="FreeBSD 12.2-RELEASE schedule">https://www.freebsd.org/releases/12.2R/schedule.html</a></td></tr><tr><td><a href="https://www.freebsd.org/where.html#helptest" title="https://www.freebsd.org/where.html#helptest">FreeBSD 12.2 test builds</a></td><td>
-	    URL: <a href="https://www.freebsd.org/where.html#helptest" title="FreeBSD 12.2 test builds">https://www.freebsd.org/where.html#helptest</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Release Engineering Team is responsible for setting
-and publishing release schedules for official project releases
-of FreeBSD, announcing code freezes and maintaining the respective
-branches, among other things.
-</p>
-<p>During the third quarter of 2020, the Release Engineering Team started
-work on the 12.2-RELEASE cycle, the third release from the stable/12
-branch.
-</p>
-<p>As of this writing, two BETA builds have been released, with the
-expectation there will be a third BETA build currently remaining on the
-schedule.
-</p>
-<p>The 12.2-RELEASE cycle will continue throughout October, with two RC
-builds currently planned, and RC3 scheduled on an as-needed basis.  The
-12.2-RELEASE is so far scheduled for final release on October 27.
-</p>
-<p>In addition to the 12.2-RELEASE, Glen Barber of the Release Engineering
-Team finished work to the release build tools and scripts to prepare for
-the conversion from Subversion to Git for the 13.0-RELEASE cycle.  There
-are no plans to merge these changes to stable branches at this time; as
-discussed within the Git working group, we feel such a change on a stable
-branch would be too intrusive to our user base as well as downstream
-FreeBSD consumers.  Development snapshot builds for 13.0-CURRENT have
-recently been built from the Git tree within the project, and further
-snapshot builds for 12.x and 11.x will continue to be built from Subversion.
-</p>
-<p>Additionally throughout the quarter, several development snapshots builds
-were released for the <i>head</i>, <i>stable/12</i>, and <i>stable/11</i> branches.
-</p>
-<p>Finally, the Release Engineering Team would like to thank Marius Strobl
-for his time serving on the team; he had recently stepped down from the
-Deputy RE Lead role due to constraints on his time.  The Team welcomes
-Colin Percival, who has accepted fulfilling this role.
-</p>
-<p>Much of this work was sponsored by Rubicon Communications, LLC (netgate.com)
-and the FreeBSD Foundation.
-</p><hr /><h2><a name="Cluster-Administration-Team" href="#Cluster-Administration-Team" id="Cluster-Administration-Team">Cluster Administration Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/administration.html#t-clusteradm" title="https://www.freebsd.org/administration.html#t-clusteradm">Cluster Administration Team members</a></td><td>
-	    URL: <a href="https://www.freebsd.org/administration.html#t-clusteradm" title="Cluster Administration Team members">https://www.freebsd.org/administration.html#t-clusteradm</a></td></tr></table><p>
-	Contact: Cluster Administration Team &lt;<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Cluster Administration Team consists of the people responsible for
-administering the machines that the Project relies on for its distributed work
- and communications to be synchronised. In this quarter, the team has worked
-on the following:
-</p><ul>
-<li><p>Work with the FreeBSD Foundation on hardware update for web services, mirror and package building servers.
-</p></li>
-<li><p>Disable directory indexing on the package mirrors to resolve performance issues of the machine.
-</p><ul>
-<li><p>This was later relaxed to allow indexing of the parent directories but still disallow the large package directories.
-</p></li></ul>
-</li><li><p>Ongoing systems administration work:
-</p><ul>
-<li><p>Accounts management for committers.
-</p></li>
-<li><p>Backups of critical infrastructure.
-</p></li>
-<li><p>Keeping up with security updates in 3rd party software.
-</p>
-</li></ul>
-</li></ul>
-Work in progress:
-
-<ul>
-<li><p>Setup Malaysia (KUL) mirror.
-</p></li>
-<li><p>Setup Brazil (BRA) mirror.
-</p></li>
-<li><p>Review the service jails and service administrators operation.
-</p></li>
-<li><p>Infrastructure of building aarch64 and powerpc64 packages.
-</p><ul>
-<li><p>NVMe issues on PowerPC64 POWER9 blocking dual socket machine from being used as pkg builder.
-</p></li>
-<li><p>Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation.
-</p></li>
-<li><p>Boot issues with Aarch64 reference machines.
-</p></li></ul>
-</li><li><p>New NYI.net sponsored colocation space in Chicago-land area.
-</p></li>
-<li><p>Work with git working group for the git repository.
-</p></li>
-<li><p>Searching for more providers that can fit the requirements for a <a href="https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout" shape="rect">generic mirrored layout</a> or a <a href="https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror" shape="rect">tiny mirror</a>.
-</p></li></ul>
-<hr /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://ci.FreeBSD.org/hwlab" title="https://ci.FreeBSD.org/hwlab">FreeBSD Hardware Testing Lab</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org/hwlab" title="FreeBSD Hardware Testing Lab">https://ci.FreeBSD.org/hwlab</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org" title="https://artifact.ci.FreeBSD.org">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org</a></td></tr><tr><td><a href="https://hackmd.io/@FreeBSD-CI" title="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackmd.io/@FreeBSD-CI" title="FreeBSD CI weekly report">https://hackmd.io/@FreeBSD-CI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="https://wiki.freebsd.org/3rdPartySoftwareCI">3rd Party Software CI</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="3rd Party Software CI">https://wiki.freebsd.org/3rdPartySoftwareCI</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="FreeBSD CI Repository">https://github.com/freebsd/freebsd-ci</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-ci channel on EFNet<br clear="none" />
-</p>
-<p>The FreeBSD CI team maintains the continuous integration system
-of the FreeBSD project.  The CI system firstly checks the committed changes
-can be successfully built, then performs various tests and analysis over the
-newly built results.
-The artifacts from those builds are archived in the artifact server for
-further testing and debugging needs.  The CI team members examine the
-failing builds and unstable tests and work with the experts in that area to
-fix the codes or adjust test infrastructure.  The details of these efforts
-are available in the <a href="https://hackmd.io/@FreeBSD-CI" shape="rect">weekly CI reports</a>.
-</p>
-<p>During the third quarter of 2020, we continued working with the contributors and
-developers in the project to fulfill their testing needs and also keep
-collaborating with external projects and companies to improve their products
-and FreeBSD.
-</p>
-<p>Important changes:
-</p><ul>
-<li><p>All !x86 -test builds now trigger a new build on 22:00 UTC daily; this was
-   not running very often because running all the tests in qemu takes lots
-   of time.  The work on improving the test execution speed and parallelism is
-   in progress.  The following is a list of the jobs affected:
-</p><ul>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-head-armv7-test/" shape="rect">Test build for FreeBSD HEAD on ARMv7</a>.
-</p></li>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-head-aarch64-test/" shape="rect">Test build for FreeBSD HEAD on AArch64</a>.
-</p></li>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-head-mips64-test/" shape="rect">Test build for FreeBSD HEAD on MIPS64</a>.
-</p></li>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-head-powerpc64-test/" shape="rect">Test build for FreeBSD HEAD on PowerPC64</a>.
-</p></li>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-head-riscv64-test/" shape="rect">Test build for FreeBSD HEAD on RISC-V64</a>.
-</p>
-</li></ul>
-</li><li><p>The build and test results will be sent to the
-   <a href="https://lists.freebsd.org/mailman/listinfo/dev-ci" shape="rect">dev-ci mailing list</a>
-   soon. Feedback and help with analysis is very appreciated!
-</p>
-<ul>
-<li><p>A builder dedicated to run jobs using provisioned VMs is setup, this
-    improves the stableness and reduces the execution time.
-</p>
-</li>
-<li><p>The result of <a href="https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs" shape="rect">FreeBSD-head-amd64-test_zfs</a>
-    is changed after OpenZFS importing; we encourage everyone to check and fix the
-    failing and skipped test cases.
-</p>
-</li></ul>
-</li></ul>
-New jobs added:
-<ul>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-head-powerpc64le-build/" shape="rect">CI build for FreeBSD HEAD on PowerPC64LE</a>.
-</p>
-</li></ul>
-Work in progress:
-<ul>
-<li><p>Collecting and sorting CI tasks and ideas
-    <a href="https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo" shape="rect">here</a>.
-</p></li>
-<li><p>Testing and merging pull requests in the
-    <a href="https://github.com/freebsd/freebsd-ci/pulls" shape="rect">the FreeBSD-ci repo</a>.
-</p></li>
-<li><p>Designing and implementing pre-commit CI building and testing,
-</p></li>
-<li><p>Reduce the procedures of CI/test environment setting up for contributors and
-    developers.
-</p></li>
-<li><p>Setting up the CI stage environment and putting the experimental jobs on it.
-</p></li>
-<li><p>Setting up public network access for the VM guest running tests.
-</p></li>
-<li><p>Implementing automatic tests on bare metal hardware.
-</p></li>
-<li><p>Adding drm ports building tests against -CURRENT.
-</p></li>
-<li><p>Planning to run ztest and network stack tests.
-</p></li>
-<li><p>Adding more external toolchain related jobs.
-</p></li>
-<li><p>Improving the hardware lab to be more mature and adding more hardware.
-</p></li>
-<li><p>Helping more 3rd software get CI on FreeBSD through a hosted CI solution.
-</p></li>
-<li><p>Working with hosted CI providers to have better FreeBSD support.
-</p>
-</li></ul>
-Please see freebsd-testing@ related tickets for more WIP information, and don't hesitate to join the effort!
-
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p><p>The Ports Management Team is responsible for overseeing the
-overall direction of the Ports Tree, building packages, and
-personnel matters.  Below is what happened in the last quarter.
-</p>
-<p>We passed the landmark of 40,000 ports in the Ports Collection
-and are now around 40,400 ports.  The last quarter saw 9335
-commits to the HEAD branch and 481 commits to the 2020Q3 branch
-by respectively 167 and 63 committers.  There are currently 2525
-open problem reports of which 595 are unassigned.  Compared to
-last quarter, this means a slight decrease in activity and also
-a slight increase in open PRs.
-</p>
-<p>During the last quarter we welcomed Rainer Hurling (rhurlin@) and
-said goodbye to Kevin Lo (kevlo@) and Grzegorz Blach (gblach@).
-</p>
-<p>The last three months saw new default versions for Perl (5.32),
-PostgreSQL (12) and PHP (7.4). Various packages also got updated:
-Firefox to 81.0.1, Chromium to 84.0.4147.135, Gnome to 3.36,
-Xorg to 1.20.9, Qt5 to 5.15.0, Emacs to 27.1, KDE Frameworks to
-5.74.0 and pkg itself to 1.15.8.
-</p>
-<p>Never tired, antoine@ ran 30 exp-runs to test port version updates,
-on such diverse matters as:
-</p><ul>
-<li><p>Updating byacc in base to 20200330.
-</p></li>
-<li><p>Check balancing of sed "y" command.
-</p></li>
-<li><p>Use of brackets.
-</p></li>
-<li><p>Removing the now redundant "port" argument from USES=readline.
-</p></li></ul>
-<hr /><h2><a name="FreeBSD-Office-team---3rd-quarter-2020-report" href="#FreeBSD-Office-team---3rd-quarter-2020-report" id="FreeBSD-Office-team---3rd-quarter-2020-report">FreeBSD Office team - 3rd quarter 2020 report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Office" title="https://wiki.freebsd.org/Office">The FreeBSD Office project</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Office" title="The FreeBSD Office project">https://wiki.freebsd.org/Office</a></td></tr></table><p>
-	Contact: FreeBSD Office team ML &lt;<a href="mailto:office@FreeBSD.org">office@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Dima Panov &lt;<a href="mailto:fluffy@FreeBSD.org">fluffy@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Office team works on a number of office-related software suites
-and tools such as OpenOffice and LibreOffice.<br clear="none" />
-</p>
-<p>Work during this quarter focused on providing the latest stable release of
-LibreOffice suite and companion apps to all FreeBSD users.
-</p>
-<ul>
-<li><p>Alongside with updating old stable branch to latest 6.4.x releases,
- current ports-tree now have a full-featured cutting-edge 7.0.1 bundle.<br clear="none" />
-</p></li>
-<li><p>Conservative users can keep 6.4.x stable version by switching to use
- all-in-one editors/libreoffice6 port and even with i18n language pack (off by default).
- It will be kept updated at least till 7.1.0 version is released.<br clear="none" />
-</p>
-</li></ul>
-We are looking for people to help the project.
-<p>All unstable work with LibreOffice snapshots is staged in our <a href="https://github.com/lwhsu/freebsd-ports-libreoffice" shape="rect">WIP repository</a>.<br clear="none" />
-The <a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&amp;email1=office%40FreeBSD.org&amp;emailassigned_to1=1&amp;emailcc1=1&amp;emailreporter1=1&amp;emailtype1=substring&amp;query_format=advanced&amp;list_id=374316" shape="rect">open bugs list</a>
-contains all filed issues which need some attention.
-Patches, comments and objections are always welcome in the mailing list and bugzilla.
-</p>
-<hr /><h2><a name="FreeBSD-Graphics-Team-status-report" href="#FreeBSD-Graphics-Team-status-report" id="FreeBSD-Graphics-Team-status-report">FreeBSD Graphics Team status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop" title="https://github.com/FreeBSDDesktop">Project GitHub page</a></td><td>
-	    URL: <a href="https://github.com/FreeBSDDesktop" title="Project GitHub page">https://github.com/FreeBSDDesktop</a></td></tr></table><p>
-	Contact: FreeBSD Graphics Team &lt;<a href="mailto:x11@freebsd.org">x11@freebsd.org</a>&gt;
-	<br />
-	Contact: Niclas Zeising &lt;<a href="mailto:zeising@freebsd.org">zeising@freebsd.org</a>&gt;
-	</p><p>The FreeBSD X11/Graphics team maintains the lower levels of the FreeBSD graphics
-stack.
-This includes graphics drivers, graphics libraries such as the
-MESA OpenGL implementation, the X.org xserver with related libraries and
-applications, and Wayland with related libraries and applications.
-</p>
-<p>There have been several updates to the FreeBSD graphics stack and related
-libraries since the last report.
-</p>
-<p>Most notably, MESA related ports were changed to use the meson build system,
-instead of the autotools based one.
-This was needed since mesa upstream has deprecated and removed the autotools
-build system, and this paved the way for further mesa updates.
-While there was a need for a few minor corrections after the initial update,
-this update has been successful and made it possible to further update and
-improve the FreeBSD mesa port.
-</p>
-<p>There have also been several security fixes for <code>xorg-server</code> and <code>libX11</code>, so
-these ports have been updated to fix these issues.
-</p>
-<p>During the period, FreeBSD 12 was changed to improve the compatibility with
-input devices using udev/evdev and libinput.
-This change removes the need for local configuration and makes most mice,
-touchpads and keyboards work out of the box.
-This change will be in the upcoming FreeBSD 12.2 release.
-</p>
-<p>There have also been several updates to various libraries, both in the graphics
-and input stacks, and several userland drivers have been updated.
-Libraries such as <code>libdrm</code> and <code>libevdev</code> have been updated to include new
-FreeBSD support, developed by team members and added upstream.
-</p>
-<p>There has also been ongoing work to keep the various drm-kmod ports and packages
-up to date, mostly in response to changes in various FreeBSD versions.
-</p>
-<p>We have also continued our regularly scheduled bi-weekly meetings.
-</p>
-<p>People who are interested in helping out can find us on the x11@FreeBSD.org
-mailing list, or on our <a href="https://gitter.im/FreeBSDDesktop/Lobby" shape="rect">gitter chat</a>.
-We are also available in #freebsd-xorg on EFNet.
-</p>
-<p>We also have a team area <a href="https://github.com/FreeBSDDesktop" shape="rect">on GitHub</a> where our work repositories can be found.
-</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="FreeBSD-on-Microsoft-HyperV-and-Azure" href="#FreeBSD-on-Microsoft-HyperV-and-Azure" id="FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/MicrosoftAzure" title="https://wiki.freebsd.org/MicrosoftAzure">Microsoft Azure article on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/MicrosoftAzure" title="Microsoft Azure article on FreeBSD wiki">https://wiki.freebsd.org/MicrosoftAzure</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HyperV" title="https://wiki.freebsd.org/HyperV">Microsoft HyperV article on FreeBSD wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HyperV" title="Microsoft HyperV article on FreeBSD wiki">https://wiki.freebsd.org/HyperV</a></td></tr></table><p>
-	Contact: FreeBSD Integration Services Team &lt;<a href="mailto:bsdic@microsoft.com">bsdic@microsoft.com</a>&gt;
-	<br />
-	Contact: Wei Hu &lt;<a href="mailto:whu@FreeBSD.org">whu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>Li-Wen is working on the FreeBSD release code related to Azure for
-the -CURRENT, 12-STABLE and 11-STABLE branches.
-The work-in-progress is available <a href="https://reviews.freebsd.org/D23804" shape="rect">here</a>.
-The <a href="https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-11_4" shape="rect">11.4-RELEASE image on Azure Marketplace</a> is published.
-We are testing the releng/12.2 branch and 12.2-RELEASE image will be
-published to Azure Marketplace soon after released.
-</p>
-<p>This project is sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
-</p><hr /><h2><a name="Building-FreeBSD-on-non-FreeBSD-hosts" href="#Building-FreeBSD-on-non-FreeBSD-hosts" id="Building-FreeBSD-on-non-FreeBSD-hosts">Building FreeBSD on non-FreeBSD hosts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/BuildingOnNonFreeBSD" title="https://wiki.freebsd.org/BuildingOnNonFreeBSD">Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/BuildingOnNonFreeBSD" title="Wiki">https://wiki.freebsd.org/BuildingOnNonFreeBSD</a></td></tr></table><p>
-	Contact: Alex Richardson &lt;<a href="mailto:arichardson@freebsd.org">arichardson@freebsd.org</a>&gt;
-	</p><p>Until recently FreeBSD could only be built on a FreeBSD host.
-However, many popular free CI tools only allow building on Linux or macOS and
-therefore can not be used for building the FreeBSD base system. Furthermore, it
-is sometimes useful to cross-build FreeBSD for a remote machine or an emulator
-even if the build machine is not running FreeBSD.
-The goal of this project is to allow building the base system on Linux and macOS
-hosts.
-</p>
-<p>I started this project in 2017 to allow building <a href="https://github.com/CTSRD-CHERI/cheribsd" shape="rect">CheriBSD</a> on the Linux servers
-and desktops that many of us working on the <a href="http://www.cheri-cpu.org" shape="rect">CHERI project</a> use.
-The first few patches were upstreamed in 2018 (see the 2018q3 report) and
-I merged the full set of patches to CheriBSD shortly after. Over the past two
-years I have slowly been upstreaming the remaining patches and finally committed
-the last required change in time for this report.
-</p>
-<p>As of September 2020 it should be possible to use the <code>buildworld</code> and
-<code>buildkernel</code> make targets to build a fully-functional FreeBSD installation
-on macOS and Linux hosts. We use this in our continuous integration system to
-build and test CheriBSD disk images for multiple architectures.
-I have also committed a <a href="https://github.com/features/actions" shape="rect">GitHub Actions</a> configuration upstream
-that takes approximately 10 minutes to build an amd64 kernel.
-This will ensure that changes that break crossbuilding from Linux/macOS
-can be detected easily.
-</p>
-<p>Upstreaming the crossbuilding changes has resulted in various build system
-cleanups. For example, we now <a href="https://reviews.freebsd.org/rS365836" shape="rect">no longer need to use lorder.sh</a>
-when building libraries which speeds up the linking step a bit.
-The portability and bootstrapping changes should also make it easier
-to upgrade from older versions since we no longer rely on host headers in
-<code>/usr/include</code> matching those of the target system (e.g. when bootstrapping
-localedef, etc.).
-</p>
-<p>While this support for building on Linux and macOS should still be considered
-experimental, it should work in many cases. If you would like to give it a try,
-the following command line should successfully build an amd64 world on Linux
-and macOS systems that have packages for LLVM 10 (or newer) installed:
-<code>MAKEOBJDIRPREFIX=/somewhere ./tools/build/make.py TARGET=amd64 TARGET_ARCH=amd64 buildworld</code>
-Builds must be performed using the <code>./tools/build/make.py</code> wrapper script since
-most Linux and macOS systems do not ship an appropriate version of bmake.
-Please let me know if you encounter any issues.
-</p>
-<p>Sponsor: DARPA
-</p><hr /><h2><a name="Git-Migration-Working-Group" href="#Git-Migration-Working-Group" id="Git-Migration-Working-Group">Git Migration Working Group</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/git_conv" title="https://github.com/freebsd/git_conv">Git conversion tooling repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/git_conv" title="Git conversion tooling repo">https://github.com/freebsd/git_conv</a></td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="https://lists.freebsd.org/mailman/listinfo/freebsd-git">FreeBSD-git mailing list</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="FreeBSD-git mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-git</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/doc" title="https://cgit-beta.FreeBSD.org/doc">Beta doc git repo</a></td><td>
-	    URL: <a href="https://cgit-beta.FreeBSD.org/doc" title="Beta doc git repo">https://cgit-beta.FreeBSD.org/doc</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/ports" title="https://cgit-beta.FreeBSD.org/ports">Beta ports git repo</a></td><td>
-	    URL: <a href="https://cgit-beta.FreeBSD.org/ports" title="Beta ports git repo">https://cgit-beta.FreeBSD.org/ports</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/src" title="https://cgit-beta.FreeBSD.org/src">Beta src git repo</a></td><td>
-	    URL: <a href="https://cgit-beta.FreeBSD.org/src" title="Beta src git repo">https://cgit-beta.FreeBSD.org/src</a></td></tr></table><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Warner Losh &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ulrich Sp�rlein &lt;<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>&gt;
-	</p><p>Work continues on FreeBSD's migration from Subversion to Git.  Ulrich has
-addressed all known issues with svn2git and has been able to work around the
-inconsistent metadata and forced commit issues in the Subversion history.
-</p>
-<p>We still have additional documentation to write, and need to finish installing
-commit hooks (e.g. restricting branch creation, or ensuring appropriate data
-exists on cherry-pick commits).
-</p>
-<p>We expect to open the beta repository to test commits before the end of
-October.  This is to allow testing of the commit hooks, and to allow developers
-to test access and become familiar with git operation.  Commits in this
-repository will be deleted and the repository will be recreated at least once
-prior to the final migration.
-</p>
-<p>Those with an interest in the migration to Git are encouraged to subscribe
-to the
-<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" shape="rect">FreeBSD-git mailing list</a>
-and test out the beta src, ports, and/or doc repositories.
-</p>
-<p>You are also welcome check out the wiki, issues, README and other documentation
-at the <a href="https://github.com/freebsd/git_conv" shape="rect">Git conversion tooling repo</a>.
-</p>
-<p>We currently expect to transition the src and doc repositories in mid-November.
-Additional investigation and experimentation with the ports repository is still
-underway.
-</p>
-<p>Sponsor: The FreeBSD Foundation (in part)
-</p><hr /><h2><a name="Linux-compatibility-layer-update" href="#Linux-compatibility-layer-update" id="Linux-compatibility-layer-update">Linux compatibility layer update</a></h2><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	</p><p>Earlier Linuxulator work focused on code cleanups and improving
-diagnostic tools.
-Work has now shifted from cleanups to fixing actual applications.
-Current status is being tracked at <a href="https://wiki.freebsd.org/LinuxApps" shape="rect">Linux app status Wiki page</a>.
-Initial focus was on applications that don't involve X11, mostly
-because they tend to be easier to test and debug, and the bug fixes
-are not application-specific.
-</p>
-<p>Foundation-sponsored work during this quarter included implementing
-a devfs(5) workaround to fix gettynam(3) inside jail/chroot, and
-workaround for the missing splice(2) syscall, which caused problems
-for grep and autotools. The Linux version reported to userspace was bumped
-to 3.10.0, which matches the kernel shipped with RHEL 7 and is neccessary
-for IBM's DB2 database installation to succeed.  The BLKPBSZGET ioctl neccessary for
-Oracle database is supported now.  There is now support for kcov(4),
-neccessary for syzcaller; as well as a number of fixes for issues
-reported by syzcaller, such as futex lock leaks.
-There were also more cleanups, including moving
-some Linuxulator-specific functionality related to error handling off
-from the syscall's fast code paths.  The sysutils/debootstrap port,
-which provides an easy way to create Debian or Ubuntu jail, was updated
-to version 1.0.123.  Finally there were some improvements
-to the <a href="https://wiki.freebsd.org/LinuxJails" shape="rect">documentation</a>.
-</p>
-<p>Most of those changes have been merged to FreeBSD 12-STABLE, in order
-to ship with 12.2-RELEASE.
-</p>
-<p>There is increased involvement from other developers; this includes termios
-performance fixes, improved memfd support, implementing <code>CLOCK_MONOTONIC_RAW</code>
-required for Steam, madvise improvements, new <code>compat.linux.use_emul_path</code>
-sysctl.  There is also ongoing work
-on tracking down the causes of failures related to Steam and WebKit, with
-fixes being first implemented in <a href="https://github.com/shkhln/linuxulator-steam-utils/wiki/Compatibility" shape="rect">linuxulator-steam-utils</a>.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="LLDB-Debugger-Improvements" href="#LLDB-Debugger-Improvements" id="LLDB-Debugger-Improvements">LLDB Debugger Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/" title="https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/">Moritz Systems Project Description</a></td><td>
-	    URL: <a href="https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/" title="Moritz Systems Project Description">https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/</a></td></tr><tr><td><a href="https://github.com/moritz-systems/llvm-project" title="https://github.com/moritz-systems/llvm-project">Git Repository</a></td><td>
-	    URL: <a href="https://github.com/moritz-systems/llvm-project" title="Git Repository">https://github.com/moritz-systems/llvm-project</a></td></tr></table><p>
-	Contact: Kamil Rytarowski &lt;<a href="mailto:kamil@moritz.systems">kamil@moritz.systems</a>&gt;
-	<br />
-	Contact: Micha&#322; G�rny &lt;<a href="mailto:mgorny@moritz.systems">mgorny@moritz.systems</a>&gt;
-	</p><p>FreeBSD includes LLDB, the debugger in the LLVM family, in the base
-system. At present it has some limitations in comparison with the GNU
-GDB debugger, and does not yet provide a complete replacement. It
-relies on an obsolete plugin model in LLDB that causes growing
-technical debt. This project aims to bring LLDB closer to a fully
-featured replacement for GDB, and therefore for FreeBSD to feature a
-modern debugger for software developers.
-</p>
-<p>The legacy monolithic target supports the executed application being
-debugged in the same process space as the debugger. The modern LLDB
-plugin approach, used on other supported targets, executes the
-target process under a separate lldb-server process. This improves
-reliability and simplifies the process / thread model in LLDB itself.
-In addition, remote and local debugging will both be performed using
-the same approach.
-</p>
-<p>After the migration to the new process model is complete, the project
-will include reviewing the results of LLDB's test suite and fixing
-tests as time permits. The work is expected to be complete in 2020.
-</p>
-<p>The project schedule is divided into three milestones, each taking approximately
-one month:
-</p>
-<p>  1. Introduce new FreeBSD Remote Process Plugin for x86_64 with basic support and upstream to LLVM.
-  2. Ensure and add the mandated features in the project (process launch, process attach (pid), process attach (name), userland core files, breakpoints, watchpoints, threads, remote debugging) for FreeBSD/amd64 and FreeBSD/i386.
-  3. Iterate over the LLDB tests. Detect, and as time permits, fix bugs. Ensure bug reports for each non-fixed and known problem. Add missing man pages and update the FreeBSD Handbook.
-</p>
-<p>We are nearing the completion of the first milestone. The new plugin is getting into
-shape, and it can already run simple single-threaded programs. The supported features
-include single-stepping, breakpoints, memory and register I/O on amd64.
-Both plugins are supported simultaneously. The new plugin is used if
-FREEBSD_REMOTE_PLUGIN environment variable is set to any value, or if lldb-server is
-spawned directly. Otherwise, the old plugin is used for compatibility. Once the new
-plugin matures, we are planning to enable it unconditionally on the architectures that
-it is ported to.
-</p>
-<p>Sponsor: The FreeBSD Foundation<br clear="none" />
-</p><hr /><h2><a name="Lua-usage-in-FreeBSD" href="#Lua-usage-in-FreeBSD" id="Lua-usage-in-FreeBSD">Lua usage in FreeBSD</a></h2><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Kyle Evans &lt;<a href="mailto:kevans@FreeBSD.org">kevans@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ryan Moeller &lt;<a href="mailto:freqlabs@FreeBSD.org">freqlabs@FreeBSD.org</a>&gt;
-	</p><p>During this quarter, flua (FreeBSD Lua) <a href="https://svnweb.freebsd.org/base/?view=revision&amp;revision=r364182" shape="rect">was taught</a>
-where to find base .lua modules in order to support <code>require</code> of .lua modules
-to be provided by the base system.  flua also <a href="https://svnweb.freebsd.org/base/?view=revision&amp;revision=r364222" shape="rect">gained support</a>
-for <code>require</code> of binary modules.
-</p>
-<p>A review for <a href="https://reviews.freebsd.org/D26080" shape="rect">libjail bindings</a> has also
-been submitted, pending review.  libjail is an essential component if one wants
-to be able to write jail management utilities in flua.
-</p>
-<p>People interested in working with Lua in FreeBSD are welcome to get in
-contact to discuss other project ideas.  To name a couple of potential
-projects, some interesting modules that have not been started but could
-prove useful (listed in no particular order):
-</p>
-<ul>
-<li><p>libcrypt
-</p></li>
-<li><p>libexpat
-</p></li>
-<li><p>libnv
-</p></li>
-<li><p>libxo
-</p>
-</li></ul>
-There is also a small list of scripts that would do well with a port to flua:
-
-<ul>
-<li><p>certctl(8)
-</p></li></ul>
-<hr /><h2><a name="NFS-over-TLS-implementation" href="#NFS-over-TLS-implementation" id="NFS-over-TLS-implementation">NFS over TLS implementation</a></h2><p>
-	Contact: Rick Macklem &lt;<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>&gt;
-	</p><p>In an effort to improve NFS security, an internet draft
-which I expect will become an RFC soon specifies the
-use of TLS 1.3 to encrypt all data traffic on a Sun RPC
-connection used for NFS.
-</p>
-<p>Although NFS has been able to use sec=krb5p to encrypt data
-on the wire, this requires a Kerberos environment and, as
-such, has not been widely adopted. It also required that
-encryption/decryption be done in software, since only the
-RPC message NFS arguments are encrypted.
-Since Kernel TLS is capable of using hardware assist to
-improve performance and does not require Kerberos, NFS
-over TLS may be more widely adopted, once implementations
-are available.
-</p>
-<p>The coding for this project has now been completed.
-All required changes to the NFS and kernel RPC code have
-been committed to -CURRENT.
-The daemons are now believed to be complete, but will
-remain in base/projects/nfs-over-tls until -CURRENT
-has an OpenSSL library with the kernel TLS support
-incorporated in it.
-If this does not happen for FreeBSD-13, hopefully the
-patched OpenSSL and the daemons can become ports.
-</p>
-<p>To support clients such as laptops, the daemons that perform the TLS
-handshake may optionally handle client X.509 certificates from a
-site local CA. There are now exports(5) options to require client(s) to
-provide a valid X.509 certificate.
-</p>
-<p>While setting up system(s) for testing is still a little awkward,
-<a href="https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt" shape="rect">the documentation is now available for those who want to help with testing</a>.
-</p>
-<p>The main limitation in the current implementation is that it uses TLS1.2
-and not TLS1.3. This should change once the KERN_TLS rx patch includes
-TLS1.3 support.
-</p>
-<p>Third party testing would be appreciated.
-</p>
-<hr /><h2><a name="syzkaller-on-FreeBSD" href="#syzkaller-on-FreeBSD" id="syzkaller-on-FreeBSD">syzkaller on FreeBSD</a></h2><p>
-	Contact: Mark Johnston &lt;<a href="mailto:markj@FreeBSD.org">markj@FreeBSD.org</a>&gt;
-	</p><p>See the syzkaller entry in the 2019q1 quarterly report for an
-introduction to syzkaller.
-</p>
-<p>syzkaller, especially the public syzbot instance, continues to find bugs
-in the FreeBSD kernel.  A number of these bugs have been fixed in
-subsystems such as the VFS name cache, the TCP and SCTP stacks, pf(4),
-the unix domain socket implementation, and the Linuxulator.
-</p>
-<p>The FreeBSD Foundation sponsored some work to enable cross-OS fuzzing.
-This makes it possible to fuzz the Linuxulator using syzkaller's Linux
-target.  This effort quickly found several bugs; once the support is
-committed upstream we will hopefully be able to leverage syzbot to gain
-continuous testing of the Linux system call interface in addition to the
-native and 32-bit compatibility interfaces.
-</p>
-<p>Some work was also done to enable running syzkaller in a FreeBSD jail,
-with the eventual aim of making it easy to distribute binary images
-containing everything required to immediately start running syzkaller on
-a new host.  Currently a number of setup steps are required, making
-deployment somewhat painful.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><h2><a name="DRM-Drivers-Update" href="#DRM-Drivers-Update" id="DRM-Drivers-Update">DRM Drivers Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/drm-kmod/" title="https://github.com/freebsd/drm-kmod/">drm-kmod</a></td><td>
-	    URL: <a href="https://github.com/freebsd/drm-kmod/" title="drm-kmod">https://github.com/freebsd/drm-kmod/</a></td></tr></table><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.Org">manu@FreeBSD.Org</a>&gt;
-	</p><p>The drm drivers for FreeBSD 13-CURRENT have been updated to match Linux 5.4.62
-Then graphics/drm-current-kmod have been updated to follow this LTS release of Linux.
-</p>
-<p>For now graphics/drm-devel-kmod is also tracking this release but will be updated
-to a later revision of Linux drm drivers in the near future.
-</p>
-<p>A lot of linuxkpi code was removed from the ports or replaced with a BSD
-licenced implementation.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="DTS-Update" href="#DTS-Update" id="DTS-Update">DTS Update</a></h2><p>
-	Contact: Emmanuel Vadot &lt;<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>&gt;
-	</p><p>DTS files (Device Tree Sources) were updated to be on par with Linux 5.8 for
-HEAD and 5.6 for the 12-STABLE branch.
-</p><hr /><h2><a name="DesignWare-Ethernet-adapter-driver-improvements" href="#DesignWare-Ethernet-adapter-driver-improvements" id="DesignWare-Ethernet-adapter-driver-improvements">DesignWare Ethernet adapter driver improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/freebsd/tree/rk_eth" title="https://github.com/gonzoua/freebsd/tree/rk_eth">WIP branch</a></td><td>
-	    URL: <a href="https://github.com/gonzoua/freebsd/tree/rk_eth" title="WIP branch">https://github.com/gonzoua/freebsd/tree/rk_eth</a></td></tr></table><p>
-	Contact: Oleksandr Tymoshenko &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;
-	</p><p>DesignWare Ethernet adapter IP is used in Rockchip and Allwinner SoCs.
-The driver was updated with following fixes:
-</p>
-<ul>
-<li><p>Initialize clocks instead of relying on u-boot to do the right thing.
-</p></li>
-<li><p>Sense media type and adjust controller configuration accordingly.
-</p></li>
-<li><p>Add support for RMII PHY mode.
-</p>
-</li></ul>
-Yet uncommitted changes include performance optimisation by adding
-<p>support for multi-segment mbuf transmission. The next step is to
-try to get more performance boost by using interrupt coalescence.
-</p><hr /><h2><a name="Google-Summer-of-Code&#8217;20-Project---eBPF-XDP-Hooks" href="#Google-Summer-of-Code&#8217;20-Project---eBPF-XDP-Hooks" id="Google-Summer-of-Code&#8217;20-Project---eBPF-XDP-Hooks">Google Summer of Code&#8217;20 Project - eBPF XDP Hooks</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/Ankurk99/freebsd/tree/ebpf-import" title="https://github.com/Ankurk99/freebsd/tree/ebpf-import">Github diff link</a></td><td>
-	    URL: <a href="https://github.com/Ankurk99/freebsd/tree/ebpf-import" title="Github diff link">https://github.com/Ankurk99/freebsd/tree/ebpf-import</a></td></tr><tr><td><a href="https://wiki.freebsd.org/SummerOfCode2020Projects/eBPFXDPHooksl" title="https://wiki.freebsd.org/SummerOfCode2020Projects/eBPFXDPHooksl">Project wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/SummerOfCode2020Projects/eBPFXDPHooksl" title="Project wiki">https://wiki.freebsd.org/SummerOfCode2020Projects/eBPFXDPHooksl</a></td></tr></table><p>
-	Contact: Ankur Kothiwal &lt;<a href="mailto:ankur@freebsd.org">ankur@freebsd.org</a>&gt;
-	</p><p>The eBPF eXpress Data Path (XDP) allows eBPF programs to be run to filter
-received packets as early as possible, avoiding unnecessary processing
-overhead before the filter is run. The goal of this project is to extend an
-existing FreeBSD network driver (a virtual NIC like a VirtIO if_vtnet) to
-be able to call into an eBPF program when processing a newly received
-packet. In short, with XDP the driver must PASS (accept and process normally), DROP,
-TX or REDIRECT the packet as specified by the program. eBPF helper
-functions and maps for aiding in packet filtering will also be
-implemented.
-</p>
-<p>Implemented:
-</p><ul>
-<li><p>Register a eBPF probe when an interface is registered with pfil.
-</p></li>
-<li><p>Activating eBPF probe.
-</p></li>
-<li><p>Create hooks and link them to the pfil head when the eBPF XDP probe is
- activated and successfully list the XDP probes.
-</p></li>
-<li><p>Create a xdp_rx function which will pass the received packets to the
- eBPF program where the packets can be further processed. This function will
- return XDP actions: DROP and PASS.
-</p></li>
-<li><p>Register the xdp hook and link it to the pfil head.
-</p></li>
-<li><p>Write an eBPF program to process (currently drop and pass) ICMP traffic -
- This is to test that the hook is working properly.
-</p></li>
-<li><p>Write a loader function to load the ICMP filter program to the kernel.
-</p>
-</li></ul>
-Future Work:
-<ul>
-<li><p>Currently we can only attach the XDP hook to PASS and DROP the packets -
- The work on detaching the hook is left.
-</p></li>
-<li><p>The XDP action to &#8220;TX&#8221; and &#8220;REDIRECT&#8221; the packets.
-</p>
-</li></ul>
-Final Deliverables:
-<ul>
-<li><p>Implemented XDP hook to pass and drop packets.
-</p></li>
-<li><p>Created a loader program to attach the eBPF program to the kernel.
-</p></li>
-<li><p>A test program to DROP ICMP filter.
-</p>
-</li></ul>
-This code was done under the Google Summer of Code 2020 under the guidance
-<p>of Ryan Stone (rstone@). The eBPF implementation for FreeBSD
-is still a work in progress and FreeBSD doesn&#8217;t support eBPF yet. The
-basic implementation for eBPF was a <a href="https://wiki.freebsd.org/SummerOfCode2018Projects/eBPF" shape="rect">GSoC&#8217;18 project</a>,
-and is still under development. This project is based on that implementation so the XDP
-implementation for FreeBSD can only be merged into the FreeBSD source code
-once it supports eBPF.
-</p>
-<p>Currently this code is a work in progress and is merged to Ryan Stone&#8217;s
-<a href="https://github.com/rysto32/freebsd/tree/ebpf-import" shape="rect">branch with support for the eBPF implementation</a>.
-</p>
-<p>Sponsor: Google Summer of Code
-</p><hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p><p>ENA (Elastic Network Adapter) is the smart NIC available in the
-virtualized environment of Amazon Web Services (AWS). The ENA
-driver supports multiple transmit and receive queues and can handle
-up to 100 Gb/s of network traffic, depending on the instance type
-on which it is used.
-</p>
-<p>Completed since the last update:
-</p><ul>
-<li><p>Fix ENA compilation in case it is integrated into the kernel binary.
-</p></li>
-<li><p>MFC of the ENA v2.2.0 driver to the FreeBSD 12.2.
-</p>
-</li></ul>
-Work in progress:
-<ul>
-<li><p>Add feature that allows reading extra ENI (Elastic Network Interface)
-    metrics about exceeding BW/pps limits.
-</p></li>
-<li><p>Introduce full kernel RSS API support.
-</p></li>
-<li><p>Allow reconfiguration of the RSS indirection table and hash key.
-</p></li>
-<li><p>Evaluation and prototyping of the driver port to the iflib framework.
-</p>
-</li></ul>
-Sponsor: Amazon.com Inc
-<hr /><h2><a name="IPSec-Extended-Sequence-Number-(ESN)-support" href="#IPSec-Extended-Sequence-Number-(ESN)-support" id="IPSec-Extended-Sequence-Number-(ESN)-support">IPSec Extended Sequence Number (ESN) support</a></h2><p>
-	Contact: Grzegorz Jaszczyk &lt;<a href="mailto:jaz@semihalf.com">jaz@semihalf.com</a>&gt;
-	<br />
-	Contact: Patryk Duda &lt;<a href="mailto:pdk@semihalf.com">pdk@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p><p>Extended Sequence Number (ESN) is IPSec extension defined in <a href="https://tools.ietf.org/html/rfc4303#section-2.2.1" shape="rect">RFC4303 Section 2.2.1</a>.
-It makes possible to implement high-speed IPSec implementations where standard, 32-bit sequence number is not sufficient.
-A key feature of the ESN is that only low order 32 bits of sequence number are transmitted over the wire.
-High-order 32 bits are maintained by sender and receiver. Additionally high-order bits are included in the computation of Integrity Check Value (ICV) field.
-</p>
-<p>Extended Sequence Number support contains following:
-</p>
-<ul>
-<li><p>Modification of existing anti-replay algorithm to fulfil ESN requirements.
-</p></li>
-<li><p>Trigger soft lifetime expiration at 80% of UINT32_MAX when ESN is disabled.
-</p></li>
-<li><p>Implement support for including ESN into ICV in cryptosoft engine in both
-    encrypt and authenticate mode (eg. AES-CBC and SHA256 HMAC) and combined
-    mode (eg. AES-GCM).
-</p></li>
-<li><p>Implement support for including ESN into ICV in AES-NI engine in both
-    encrypt and authenticate mode and combined mode.
-</p>
-</li></ul>
-Completed since the last update:
-
-<ul>
-<li><p>Adjust implementation of crypto part to the reworked Open Crypto Framework.
-</p></li>
-<li><p>Move the core ESN implementation from the crypto drivers to netipsec layer.
-</p></li>
-<li><p>Make use of the newly introduced crp_aad mechanism for combined modes.
-</p></li>
-<li><p>Introduce minor fixes and improvements.
-</p>
-</li></ul>
-TODO:
-
-<ul>
-<li><p>Complete review process in Phabricator and merge patches in the tree.
-</p>
-</li></ul>
-Sponsor: Stormshield
-
-<hr /><h2><a name="NXP-ARM64-SoC-support" href="#NXP-ARM64-SoC-support" id="NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></h2><p>
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	<br />
-	Contact: Dawid Gorecki &lt;<a href="mailto:dgr@semihalf.com">dgr@semihalf.com</a>&gt;
-	</p><p>The Semihalf team initiated working on FreeBSD support for the
-<a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A" shape="rect">NXP LS1046A SoC</a>
-</p>
-<p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with
-integrated packet processing acceleration and high speed peripherals
-including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide
-range of networking, storage, security and industrial applications.
-</p>
-<p>Completed since the last update:
-</p><ul>
-<li><p>Upstreaming of the QorIQ SDHCI driver (r365054).
-</p>
-</li></ul>
-With above the current Semihalf upstreaming activity is complete.
-
-<p>The major out-of-tree supported components:
-</p><ul>
-<li><p>DPAA network controller support.
-</p></li>
-<li><p>QSPI controller support.
-</p>
-</li></ul>
-They work on 11.2-RELEASE, but still require significant
-<p>effort to adopt to FreeBSD-CURRENT.
-</p>
-<p>Sponsor: Alstom Group
-</p><hr /><h2><a name="Addition-of-PowerPC64LE-Architecture" href="#Addition-of-PowerPC64LE-Architecture" id="Addition-of-PowerPC64LE-Architecture">Addition of PowerPC64LE Architecture</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-ppc/2020-August/012043.html" title="https://lists.freebsd.org/pipermail/freebsd-ppc/2020-August/012043.html">Early notes</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-ppc/2020-August/012043.html" title="Early notes">https://lists.freebsd.org/pipermail/freebsd-ppc/2020-August/012043.html</a></td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-ppc/2020-September/012098.html" title="https://lists.freebsd.org/pipermail/freebsd-ppc/2020-September/012098.html">Announcement</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/pipermail/freebsd-ppc/2020-September/012098.html" title="Announcement">https://lists.freebsd.org/pipermail/freebsd-ppc/2020-September/012098.html</a></td></tr></table><p>
-	Contact: Brandon Bergren &lt;<a href="mailto:bdragon@freebsd.org">bdragon@freebsd.org</a>&gt;
-	</p><p>As of r366063, experimental support for little-endian PowerPC64 (PowerPC64LE)
-is available in -CURRENT for POWER8 and POWER9 machines.
-</p>
-<p>In 2010, when FreeBSD was ported to PowerPC64, the average
-user would have been using a G5 PowerMac, a purely big-endian
-machine.
-</p>
-<p>While, at the time, a 32-bit PowerPC machine could run in little-endian,
-as well as POWER6 and POWER7, in practice, the complexities involved
-in managing it at the kernel level and lack of firmware support made it
-infeasible to support.
-</p>
-<p>When IBM designed POWER8, one main focus was to improve little-endian support,
-and bring it up to parity with big-endian.
-</p>
-<p>This improved support makes it practical to support a little-endian operating
-environment on what is traditionally a primarily big-endian platform.
-</p>
-<p>In 2020, with POWER9 being affordable for many users thanks to the Raptor
-Blackbird, semi-easy access to surplus POWER8 hardware, IBM having
-a major future focus on POWER little-endian, and the decay of big-endian
-support in modern video cards and graphical environments, there is demand for
-a little-endian version of FreeBSD on POWER.
-</p>
-<p>With FreeBSD/PowerPC64's transition in 2019 to the ELFv2 ABI as part of the
-2019q4 PowerPC on Clang effort, the last major barrier to a little-endian
-port was eliminated.
-</p>
-<p>Since nobody else was working on it, and I had the skillset required to do
-the port, I decided to experiment one weekend with a little-endian kernel
-to see how difficult it would be to port.
-</p>
-<p>It turned out to be a lot more trivial than I was expecting. Three days later
-I had console support in qemu, and after another week of debugging, I had it
-fully up and running on hardware.
-</p>
-<p>FreeBSD PowerPC64LE is now an experimental MACHINE_ARCH in base, and is
-continuing to evolve at a rapid pace.
-</p>
-<p>Big-endian PowerPC64 is still the preferred platform for the foreseeable
-future, and will not be deprecated.
-</p>
-<p>Sponsor: Tag1 Consulting, Inc.
-</p><hr /><h2><a name="ure---USB-3.0-Gigabit-Ethernet-Driver-update" href="#ure---USB-3.0-Gigabit-Ethernet-Driver-update" id="ure---USB-3.0-Gigabit-Ethernet-Driver-update">ure - USB 3.0 Gigabit Ethernet Driver update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/365648" title="https://svnweb.freebsd.org/changeset/base/365648">svn commit: r365648</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/changeset/base/365648" title="svn commit: r365648">https://svnweb.freebsd.org/changeset/base/365648</a></td></tr><tr><td><a href="https://www.freebsd.org/security/advisories/FreeBSD-SA-20:27.ure.asc" title="https://www.freebsd.org/security/advisories/FreeBSD-SA-20:27.ure.asc">FreeBSD-SA-20:27.ure</a></td><td>
-	    URL: <a href="https://www.freebsd.org/security/advisories/FreeBSD-SA-20:27.ure.asc" title="FreeBSD-SA-20:27.ure">https://www.freebsd.org/security/advisories/FreeBSD-SA-20:27.ure.asc</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D25809" title="https://reviews.freebsd.org/D25809">D25809 major update to if_ure</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D25809" title="D25809 major update to if_ure">https://reviews.freebsd.org/D25809</a></td></tr></table><p>
-	Contact: John-Mark Gurney &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p><p>The ure is a driver for handling the RealTek ethernet adapters,
-including the RTL8153 USB 3.0 Gigabit ethernet adapters.  It is used
-in many ethernet dongles and docking stations.
-</p>
-<p>Previous to this update, the driver was limited in speed.  In my
-testing, I was only able to get ~91Mbps.  This limit was due to one
-packet per USB transfer.  USB has a limit of 8000 transfers per
-second (1500 bytes/pkt * 8000 pkts/sec * 8bits/byte == 96 Mbps).
-This was acceptable for fast ethernet (RTL8152, 100Mbps), but with
-the additional support for Gigabit ethernet, it became a bottleneck.
-</p>
-<p>The updates add sending and receiving multiple packets in a single
-USB transfer, VLAN hardware tagging, and enable TCP and UDP
-checksum offloading.  This increased the speed on gigabit ethernet
-to ~940 Mbps.
-</p>
-<p>In doing this work, a security vulnerability was discovered in the
-driver.  Due to improper setting of a device register, on some
-devices, it caused packets to be fragmented when they shouldn't be
-and the driver was unable to handle them correctly.  This allowed an
-attacker, who could generate large frames (say, ping packets, or
-large TCP transfers), to inject arbitrary packets into the network
-stack.  This could allow the attacker to spoof traffic from other
-machines, and bypass VLAN protections.  See the SA for more
-information.
-</p>
-<p>As part of this work, a script was created to run tests to
-validate that basic functionality of the driver (w/o options) work
-properly, and then iterate over each option to make sure that they
-function properly.  This will be released at some point in the
-future.
-</p>
-<p>If you're interested in helping out, or testing it, let me know.
-</p><hr /><h2><a name="Stateless-hardware-offloads-for-VXLANs" href="#Stateless-hardware-offloads-for-VXLANs" id="Stateless-hardware-offloads-for-VXLANs">Stateless hardware offloads for VXLANs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365867" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365867">r365867</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365867" title="r365867">https://svnweb.freebsd.org/base?view=revision&amp;revision=r365867</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365868" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365868">r365868</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365868" title="r365868">https://svnweb.freebsd.org/base?view=revision&amp;revision=r365868</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365869" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365869">r365869</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365869" title="r365869">https://svnweb.freebsd.org/base?view=revision&amp;revision=r365869</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365870" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365870">r365870</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365870" title="r365870">https://svnweb.freebsd.org/base?view=revision&amp;revision=r365870</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365871" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365871">r365871</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=r365871" title="r365871">https://svnweb.freebsd.org/base?view=revision&amp;revision=r365871</a></td></tr><tr><td><a href="https://tools.ietf.org/html/rfc6935" title="https://tools.ietf.org/html/rfc6935">RFC6935</a></td><td>
-	    URL: <a href="https://tools.ietf.org/html/rfc6935" title="RFC6935">https://tools.ietf.org/html/rfc6935</a></td></tr></table><p>
-	Contact: Navdeep Parhar &lt;<a href="mailto:np@FreeBSD.org">np@FreeBSD.org</a>&gt;
-	</p><p>VXLAN (Virtual eXtensible LAN) is a tunneling protocol in which Layer 2
-traffic for a virtual LAN is encapsulated in UDP and transferred over
-Layer 3 networks between VTEPs (VXLAN Tunnel End Points).  Traffic on
-the wire has two sets of networking headers: the headers for the
-encapsulation and the headers of the traffic being encapsulated.  VXLANs
-are supported by if_vxlan(4) on FreeBSD.
-</p>
-<p>Modern NICs commonly support header checksum insertion and verification,
-TSO (TCP Segmentation Offload) on transmit, and RSS for load
-distribution on receive.  But the default is to operate on the outermost
-headers.  Some NICs can operate on the inner encapsulated frames as
-well.  The commits listed above allow if_vxlan(4) to take advantage of
-such NICs.
-</p>
-<p>r365867 and r365868 add new mbuf checksum flags and ifnet capabilities.
-r365870 implements the kernel parts of the new capabilities and updates
-if_vxlan(4) to make use of them.  r365871 implements driver support for
-the new capabilities in cxgbe(4).
-</p>
-<p>VXLAN and other tunneling protocols that use UDP explicitly allow zero
-checksum in the outer UDP header, even with IPv6.  r365869 adds support
-for configuring one UDP/IPv6 port where zero checksums are allowed.
-</p>
-<p>This work was sponsored by Chelsio Communications and was implemented
-and tested using T6 (Terminator 6) NICs supported by cxgbe(4).  It is
-available in 13.0-CURRENT (head) right now and will be available in
-12-STABLE in the future.
-</p>
-<p>VXLANs can be created as usual and will automatically have checksum and
-TSO capabilities if the underlying physical interface supports VXLAN
-stateless offloads.  Use ifconfig to list, disable, and enable checksum
-capabilities on the VXLAN interface.  Use https://bugs.freebsd.org/bugzilla/
-to report bugs.
-</p>
-<p>Future work:
-</p><ul>
-<li><p>Direct call into a vxlan input routine from the driver's receive routine.
-</p></li>
-<li><p>LRO support in if_vxlan(4).
-</p></li>
-<li><p>GENEVE support.
-</p>
-</li></ul>
-Sponsor: Chelsio Communications
-<hr /><h2><a name="Wireless-updates" href="#Wireless-updates" id="Wireless-updates">Wireless updates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless">The freebsd-wireless mailing list</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="The freebsd-wireless mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-wireless</a></td></tr><tr><td><a href="https://github.com/erikarn/athp" title="https://github.com/erikarn/athp">athp github repository</a></td><td>
-	    URL: <a href="https://github.com/erikarn/athp" title="athp github repository">https://github.com/erikarn/athp</a></td></tr></table><p>
-	Contact: Adrian Chadd &lt;<a href="mailto:adrian@FreeBSD.org">adrian@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Bjoern A. Zeeb &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p><p>The following works happened in FreeBSD HEAD (some already in Q2) and were
-merged for 12.2-BETA2 and include net80211 and driver updates for better 11n
-and upcoming 11ac support.
-</p>
-<p>In more detail, this includes an ath(4) update, some run(4) 11n support, 11n for otus(4),
-A-MPDU, A-MSDU, A-MPDU+A-MSDU and Fast frames options, scanning fixes,
-enhanced PRIV checks for jails, restored parent device name printing,
-improvements for upcoming VHT support, lots of under-the-hood infrastructure
-improvements, new device IDs, and debug tools updates.
-</p>
-<p>If you have a chance please test before the release.
-</p>
-<h3>Atheros 11ac driver athp</h3>
-
-<p>In the last three months the athp(4) port of the ath10k driver has progressed
-well.  Adrian reports the following important changes:
-</p><ul>
-<li><p>Per-node transmit buffering was implemented, required for correct hostap
-  and QCA6174 behaviour.
-</p></li>
-<li><p>Issues with ignoring sending some management frames got fixed; null-data
-  frames were being filtered out and this caused undesirable hostap behaviour.
-</p></li>
-<li><p>Transmit path refactoring reduced code duplication.
-</p></li>
-<li><p>A fix on firmware start / VAP running tracking no longer stops
-  the first VAP from coming active after VAP creation / ifconfig up.
-</p></li>
-<li><p>Correcting hostap mode PHY configuration now allows non-VHT stations to
-  associate and correctly exchange data with a VHT AP.
-</p></li>
-<li><p>Addition of a crypto key configuration cache in the driver ensures the
-  ieee80211_key details are available after the key is deleted; net80211
-  would reuse or free the state before the driver task would finish the
-  firmware command.
-</p>
-</li></ul>
-<h3>Newer Intel Wireless device support</h3>
-
-<p>Initial work was done to integrate net80211 support in the LinuxKPI compat
-layer to get the wireless parts going.
-In addition, upstreaming code changes and working through problems and review
-started on two sides.  One was trying to get mostly compile time changes
-upstreamed to the iwlwifi driver.  The other is sorting out conflicting
-LinuxKPI changes to not break the DRM graphics drivers.
-Bjoern hopes that with some of that sorted out, he can soon go back to focus
-on the wireless parts and produce a new snapshot.
-</p>
-<h3>rtw88 and brcmfmac</h3>
-
-<p>As the Intel driver port and LinuxKPI advance, both the rtw88, and to a lower
-degree the brcmfmac, ports benefit from that.
-Bjoern lately also got a brcmfmac PCIe card and started to port support for
-that.
-This for the moment remains a free-time project.
-</p>
-<p>Work by Bjoern was sponsored by: Rubicon Communications, LLC (d/b/a "Netgate") and The FreeBSD Foundation
-</p><hr /><h2><a name="ZSTD-Compression-in-ZFS" href="#ZSTD-Compression-in-ZFS" id="ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></h2><p>
-	Contact: Allan Jude &lt;<a href="mailto:allanjude@freebsd.org">allanjude@freebsd.org</a>&gt;
-	</p><p>Zstandard (ZSTD) is a modern high-performance compression
-algorithm designed to provide the compression ratios of gzip
-while offering much better performance. ZSTD has been adopted
-in FreeBSD for a number of other uses, including compressing
-kernel crash dumps, as a replacement for gzip or bzip for
-compressing log files, and for future versions of pkg(8).
-</p>
-<p>This effort to complete the integration of ZSTD into ZFS is
-funded by the FreeBSD Foundation.
-</p>
-<p>During the third quarter the integrating of ZSTD into OpenZFS
-was completed in the upstream OpenZFS repository, and the new
-OpenZFS 2.0 codebase was imported into 13-CURRENT.
-Completed milestones in this project:
-</p>
-<ul>
-<li><p>Importing ZSTD 1.4.5 into OpenZFS, using the recent upstream zstd features that make it easier to embed zstd in other projects.
-</p></li>
-<li><p>Changing the way compression levels are tracked and inherited.
-</p></li>
-<li><p>Save and restore the compression level via an embedded block header.
-</p></li>
-<li><p>Also store the version of zstd used in the embedded block header, for future-proofing. The checksum of a block may not match if zstd is upgraded, since it may compress the block more.
-</p></li>
-<li><p>Add tests to ensure zstd compression and metadata survive ZFS replication.
-</p></li>
-<li><p>Resolve possible negative interactions with L2ARC and ZFS Native Encryption.
-</p></li>
-<li><p>Fix bug with L2ARC if the Compressed ARC feature is disabled.
-</p></li>
-<li><p>Improve the ZFS feature activation code, so that zstd cannot create pools that will panic older versions of ZFS.
-</p>
-</li></ul>
-With these changes, upgraded pools can compress data with zstd
-<p>or zstd-fast, across a wide range of different compression levels.
-This will allow the storage administrator to select the
-performance-vs-compression tradeoff that best suits their needs.
-</p>
-<p>Tasks remaining to be completed:
-</p>
-<ul>
-<li><p>Add a section to the FreeBSD Handbook ZFS chapter about zstd
-</p></li>
-<li><p>Create more documentation around selecting a suitable compression level
-</p></li>
-<li><p>Finish support for ZSTD in the FreeBSD boot loader (Warner Losh <a href="mailto:imp@freebsd.org" shape="rect">imp@freebsd.org</a>)
-</p>
-</li></ul>
-Sponsor: The FreeBSD Foundation
-<hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="CheriBSD-2020-Q3" href="#CheriBSD-2020-Q3" id="CheriBSD-2020-Q3">CheriBSD 2020 Q3</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
-	Contact: Alex Richardson &lt;<a href="mailto:arichardson@FreeBSD.org">arichardson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	<br />
-	Contact: George Neville-Neil &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jessica Clarke &lt;<a href="mailto:jrtc27@FreeBSD.org">jrtc27@FreeBSD.org</a>&gt;
-	<br />
-	Contact: John Baldwin &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	</p><p>CheriBSD extends FreeBSD to implement memory protection and software
-compartmentalization features supported by the CHERI instruction-set
-extensions.  There are three architectural implementations of the
-CHERI protection model: CHERI-MIPS, CHERI-RISC-V, and Arm's forthcoming
-experimental Morello processor (due late 2021).  CheriBSD is a research
-operating system with a stable baseline implementation into which
-various new research features have been, or are currently being, merged:
-</p>
-<ul>
-<li><p>Arm Morello - We are preparing to open source our adaptation of
- CheriBSD to Arm's Morello architecture.  The Morello branch is being
- updated to the most recent CheriBSD baseline, and patches are in review
- for upstreaming to our open-source repository.  CheriBSD currently boots
- and runs statically linked CheriABI binaries on the Morello simulator,
- and dynamic linking support is in progress, with OS and toolchain bugs
- being worked on.  We aim to make a first CheriBSD/Morello snapshot
- available alongside other open-source Morello software in mid-October
- 2020, however, our target for a more mature and usable implementation is
- December 2020.
-</p>
-</li>
-<li><p>Kernel spatial memory safety (pure-capability kernel) - The current
- CheriBSD kernel is a hybrid C program where only pointers to userspace
- are CHERI capabilities. This ensures that the kernel follows the
- intent of the application runtime and cannot be used to defeat
- bounds on application pointers. We have developed and will soon
- merge a pure-capability kernel where all pointers in the kernel are
- appropriately bounded capabilities. This vastly reduces the opportunity
- for buffer overflows. This spatial memory safety lays the
- groundwork for future work such as device driver compartmentalization
- and kernel temporal safety.
-</p>
-</li>
-<li><p>Userspace heap temporal memory safety (Cornucopia) - CHERI
- capabilities provide the necessary features to enable
- robust and efficient revocation of freed pointers.  With <a href="https://www.cl.cam.ac.uk/research/security/ctsrd/pdfs/2020oakland-cornucopia.pdf" shape="rect">Cornucopia</a>
- we have implemented a light-weight revocation framework providing
- protection from use-after-reallocation bugs with an average cost below
- 2%.  We aim to bring these overheads down further over the next year and
- merge this functionality into the mainline CheriBSD.
-</p>
-</li>
-<li><p>We have been working on updating the arm64 bhyve from Politehnica
- University of Bucharest to have it committed to FreeBSD. We have been
- upstreaming initial changes to help support this.
-</p>
-</li>
-<li><p>Baseline FreeBSD improvements - We are upstreaming (to FreeBSD) various
- bug fixes and tweaks for PCIe support, and support for the System MMU (SMMU)
- that will be present on the N1SDP and Morello SoCs.  We have upstreamed
- support for cross-building FreeBSD from macOS and Linux (with some
- limitations; see separate entry on crossbuilding).  We have also fixed
- implementation bugs in the RISC-V ABI.
-</p>
-</li></ul>
-<h3>CHERI Documentation and Exercises</h3>
-
-<ul>
-<li><p>We have released <a href="https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-951.pdf" shape="rect">Capability
- Hardware Enhanced RISC Instructions: CHERI Instruction-Set Architecture (Version 8)</a>.
- Notable changes include promotion of CHERI-RISC-V to non-experimental
- and discussion of Arm's Morello prototype.
-</p>
-</li>
-<li><p>We have developed a set of <a href="https://ctsrd-cheri.github.io/cheri-exercises" shape="rect">Adversarial
- CHERI Exercises and Missions</a> to introduce security
- researchers to CHERI protections.
-</p></li></ul>
-<hr /><h2><a name="FreeBSD/RISC-V-Project" href="#FreeBSD/RISC-V-Project" id="FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/riscv" title="https://wiki.freebsd.org/riscv">Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/riscv" title="Wiki">https://wiki.freebsd.org/riscv</a></td></tr></table><p>
-	Contact: Mitchell Horne &lt;<a href="mailto:mhorne@FreeBSD.org">mhorne@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-riscv" shape="rect">freebsd-riscv Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-riscv on freenode<br clear="none" />
-</p>
-<p>The FreeBSD/RISC-V project is providing support for running FreeBSD on the
-<a href="https://riscv.org/" shape="rect">RISC-V Instruction Set Architecture</a>.
-</p>
-<p>This quarter saw several important bug fixes. A number of hangs in the system
-were identified and addressed, and a bug in QEMU's implementation of the
-Platform Level Interrupt Controller was fixed. This fix is included in the new
-<code>devel/qemu50</code> and <code>devel/qemu-devel</code> ports.
-</p>
-<p>The end result of these fixes is that the test suite can now be reliably run to
-completion in QEMU. The entire run takes several hours, so CI has been
-configured to run the job once a day. There is active effort into reducing the
-time it takes to run the entire test suite.
-</p>
-<p>A new u-boot port was created: <code>sysutils/u-boot-qemu-riscv64</code>. This variant can
-be used as a secondary bootloader alongside OpenSBI to load and launch FreeBSD's
-<code>loader(8)</code> from an EFI System Partition.
-</p>
-<p>Next quarter will likely bring further fixes to address some of the failing test
-cases.
-</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="Update-to-grub-bhyve" href="#Update-to-grub-bhyve" id="Update-to-grub-bhyve">Update to grub-bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/ctuffli/grub" title="https://gitlab.com/ctuffli/grub">grub-bhyve Git Repository</a></td><td>
-	    URL: <a href="https://gitlab.com/ctuffli/grub" title="grub-bhyve Git Repository">https://gitlab.com/ctuffli/grub</a></td></tr></table><p>
-	Contact: Chuck Tuffli &lt;<a href="mailto:chuck@freebsd.org">chuck@freebsd.org</a>&gt;
-	</p><p>bhyve is the hypervisor included in FreeBSD and other operating systems
-used to run virtual machines. When not using a boot ROM (i.e. UEFI), the
-user must load the guest operating system for bhyve. For non-FreeBSD
-guests, the loader is a version of GNU GRUB (a.k.a the GNU GRand Unified
-Bootloader) modified to interface with bhyve. This work is an effort to
-both update the base GRUB code to the latest version as well as improve
-the usability on FreeBSD.
-</p>
-<p>The current <a href="https://www.freshports.org/sysutils/grub2-bhyve/" shape="rect">grub-bhyve</a>
-is based on an older version of GRUB (circa 2015) and thus is missing
-more recent additions such as XFS file system and
-<a href="https://www.syslinux.org/" shape="rect">syslinux</a> support. With the update,
-installing CentOS, for example, now does not require the extra step of
-changing the default file system to something other than XFS.
-</p>
-<p>Internally, the code has been restructured to be its own "platform"
-which should make it easier to keep in sync with upstream development.
-The major improvement is the ability to automatically find and load the
-GRUB configuration file from the guest disk image. With this change, it
-is not necessary to create a device map file or specify which Linux
-kernel or initrd image to use. More importantly, if the guest image
-updates its GRUB configuration, for example after updating the kernel,
-no changes are needed when invoking grub-bhyve. Note, this feature
-requires a new "disk" option:
-</p>
-<p>    # grub-bhyve --disk=/zroot/vms/u18-mini/disk0.img --vm=u18-mini
-</p>
-<p>The automatic configuration file detection works with both GRUB
-configuration files (e.g. CentOS, Ubuntu) as well as syslinux
-configuration (e.g. Alpine). For the adventurous, there is experimental
-support for Fedora's BootLoaderSpec (a.k.a. <code>blscfg</code>) on the blscfg
-branch of the grub-bhyve Git repository.
-</p>
-<p>The code has been tested on a few Linux variants, but it would benefit
-from wider testing (and bug reports!). The new version does not have a
-Port but is easily built on FreeBSD. After cloning / downloading the
-source, run:
-</p>
-<p>    $ PYTHON=python3.7 ./bootstrap
-    $ MAKE=gmake ./configure --with-platform=bhyve
-    $ gmake
-</p>
-<p>The resulting binary, <code>grub-bhyve</code>, will be in the <code>grub-core/</code>
-directory. If you have success or troubles with it, please let me know.
-</p><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://community.kde.org/FreeBSD" title="https://community.kde.org/FreeBSD">KDE Community FreeBSD</a></td><td>
-	    URL: <a href="https://community.kde.org/FreeBSD" title="KDE Community FreeBSD">https://community.kde.org/FreeBSD</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p><p>The KDE on FreeBSD project aims to package all of the software
-produced by the KDE Community for the FreeBSD ports tree.
-The software includes a full desktop environment called KDE Plasma,
-an IDE with the name <a href="https://www.kdevelop.org/" shape="rect">KDevelop</a>,
-a PIM suite known as <a href="https://kontact.kde.org/" shape="rect">Kontact</a>
-and hundreds of other applications that can be used on
-any FreeBSD machine.
-</p>
-<p>With the continuation of the ever-so-peculiar era of
-almost-only-online, the KDE community has shifted gears
-and also gone for online events. The yearly conference,
-<a href="https://akademy.kde.org/2020/" shape="rect">Akademy</a>,
-was conducted online over video calls.
-Meanwhile, software continues to be released,
-so this quarter the kde@ team:
-</p>
-<ul>
-<li><p>Put the beta of the next version of KDE Plasma, scheduled for
-  official release in October 2020, into the
-  <a href="https://community.kde.org/FreeBSD/Setup/Area51" shape="rect">Area51 development</a> tree.
-  Area51 is a fork of the FreeBSD ports tree where new development for
-  KDE ports happens.
-</p></li>
-<li><p>The monthly regular updates to the KDE Plasma desktop landed on-time
-  and safely.
-</p></li>
-<li><p>With three months in a quarter, there were also three releases of
-  KDE Frameworks 5, including a new framework for handling DAV jobs.
-</p></li>
-<li><p>The June applications update and its .1 release landed a bit late,
-  but brings with it the usual raft of updates to KDE applications and libraries,
-</p></li>
-<li><p>A new <a href="https://www.digikam.org/" shape="rect">Digikam</a> release, which arrived in
-  the ports tree on the day of its release.
-</p></li>
-<li><p>A new <a href="https://www.kdevelop.org/" shape="rect">KDevelop</a> release arrived a day
-  after its release. This update contains a number of crash fixes
-  for refactoring support.
-</p></li>
-<li><p>Qt was updated to Qt 5.15, the last in the Qt5 series and an LTS
-  version. Bugfix releases are expected, but the next major Qt will
-  be Qt 6.
-</p>
-</li></ul>
-On the infrastructure front, August saw some minor updates to CMake and ninja.
-<p>As usual, kde@ continues to support the work of xorg@ and gnome@ in maintaining
-the Free Desktop stack on FreeBSD, including XOrg, poppler, and xdg-utils.
-A new <code>MAINTAINER</code> group, desktop@, has been created to provide
-shared ownership of that shared stack.
-</p>
-<p>With Python2 deprecation looming, the build system for QtWebEngine --
-itself a fork of Chromium -- is becoming a pressing issue in Q4
-and will no doubt chew up a lot of time in the coming months.
-</p><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree, in manpages, or in
-      external books/documents.</p><br /><h2><a name="DOCNG-on-FreeBSD" href="#DOCNG-on-FreeBSD" id="DOCNG-on-FreeBSD">DOCNG on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/carlavilla/freebsd-hugo-website" title="https://gitlab.com/carlavilla/freebsd-hugo-website">DOCNG Website Repo</a></td><td>
-	    URL: <a href="https://gitlab.com/carlavilla/freebsd-hugo-website" title="DOCNG Website Repo">https://gitlab.com/carlavilla/freebsd-hugo-website</a></td></tr><tr><td><a href="https://gitlab.com/carlavilla/freebsd-hugo-documentation" title="https://gitlab.com/carlavilla/freebsd-hugo-documentation">DOCNG Documentation Repo</a></td><td>
-	    URL: <a href="https://gitlab.com/carlavilla/freebsd-hugo-documentation" title="DOCNG Documentation Repo">https://gitlab.com/carlavilla/freebsd-hugo-documentation</a></td></tr><tr><td><a href="https://gitlab.com/carlavilla/freebsd-hugo-data" title="https://gitlab.com/carlavilla/freebsd-hugo-data">DOCNG Share Repo</a></td><td>
-	    URL: <a href="https://gitlab.com/carlavilla/freebsd-hugo-data" title="DOCNG Share Repo">https://gitlab.com/carlavilla/freebsd-hugo-data</a></td></tr></table><p>
-	Contact: Sergio Carlavilla &lt;<a href="mailto:carlavilla@FreeBSD.org">carlavilla@FreeBSD.org</a>&gt;
-	</p><p>The Doc New Generation project aims to convert the website and all
-existing documentation to Hugo/AsciiDoctor. Right now almost
-everything is converted as you can see in the repositories.
-</p>
-<p>The objective of using Hugo and AsciiDoctor is to reduce the
-learning curve and let people to start quickly with our documentation
-system. Other benefits of using Hugo is that we can use other
-technologies aside from AsciiDoctor, like MarkDown, RST, Pandoc, etc.
-</p>
-<p>The remaining tasks include:
-</p><ul>
-<li><p>Finish the conversion of some books to AsciiDoctor.
-</p></li>
-<li><p>Get some tweaks in the CSS to be responsive.
-</p></li>
-<li><p>Add AsciiDoctor extensions to create an index of tables and figures.
-</p></li>
-<li><p>Make a general review.
-</p>
-</li></ul>
-The dates for making the migration have yet to be discussed.
-
-<p>Patches, comments and objections are always welcome.
-</p><hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="Potluck---Flavour-&amp;-Image-Repository-for-pot" href="#Potluck---Flavour-&amp;-Image-Repository-for-pot" id="Potluck---Flavour-&amp;-Image-Repository-for-pot">Potluck - Flavour &amp; Image Repository for pot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://potluck.honeyguide.net/" title="https://potluck.honeyguide.net/">Potluck Repository &amp; Project</a></td><td>
-	    URL: <a href="https://potluck.honeyguide.net/" title="Potluck Repository &amp; Project">https://potluck.honeyguide.net/</a></td></tr><tr><td><a href="https://github.com/hny-gd/potluck" title="https://github.com/hny-gd/potluck">Potluck on github</a></td><td>
-	    URL: <a href="https://github.com/hny-gd/potluck" title="Potluck on github">https://github.com/hny-gd/potluck</a></td></tr><tr><td><a href="https://pot.pizzamig.dev" title="https://pot.pizzamig.dev">pot project</a></td><td>
-	    URL: <a href="https://pot.pizzamig.dev" title="pot project">https://pot.pizzamig.dev</a></td></tr></table><p>
-	Contact: Stephan Lichtenauer &lt;<a href="mailto:sl@honeyguide.eu">sl@honeyguide.eu</a>&gt;
-	</p><p>pot is a jail management tool that <a href="https://www.freebsd.org/news/status/report-2020-01-2020-03.html#pot-and-the-nomad-pot-driver" shape="rect">also supports orchestration through nomad</a>.
-</p>
-<p>Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: A repository of pot flavours and complete images for usage with pot.
-</p>
-<p>In the last quarter, an initial set of Nomad, Consul and Traefik images has been created that are sufficient to run a simple virtual datacenter out of the box.  <br clear="none" />
-<a href="https://honeyguide.eu/posts/virtual-dc1/" shape="rect">A three-part article series explaining how to set this up</a> is also available now.
-</p>
-<p>Furthermore, ready-made images suitable for scheduling via Nomad and Consul in such an environment have been created, e.g. a BackupPC or a Postfix Backup MX service.
-</p>
-<p>Future plans include additional images and exposing more configuration options in the existing images to allow a more flexible usage.
-</p>
-<p>Beside general feedback and tests, additional flavours and patches are very welcome!
-</p>
-<p>Sponsors: Honeyguide GmbH &amp; Honeyguide Group (Pty) Ltd
-</p><hr /><h2><a name="Puppet" href="#Puppet" id="Puppet">Puppet</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://puppet.com/docs/puppet/latest/puppet_index.html" title="https://puppet.com/docs/puppet/latest/puppet_index.html">Puppet</a></td><td>
-	    URL: <a href="https://puppet.com/docs/puppet/latest/puppet_index.html" title="Puppet">https://puppet.com/docs/puppet/latest/puppet_index.html</a></td></tr><tr><td><a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="https://puppetcommunity.slack.com/messages/C6CK0UGB1/">Puppet's FreeBSD slack channel</a></td><td>
-	    URL: <a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="Puppet's FreeBSD slack channel">https://puppetcommunity.slack.com/messages/C6CK0UGB1/</a></td></tr><tr><td><a href="https://puppet.com/docs/bolt/latest/bolt.html" title="https://puppet.com/docs/bolt/latest/bolt.html">Bolt</a></td><td>
-	    URL: <a href="https://puppet.com/docs/bolt/latest/bolt.html" title="Bolt">https://puppet.com/docs/bolt/latest/bolt.html</a></td></tr><tr><td><a href="https://choria.io/" title="https://choria.io/">Choria</a></td><td>
-	    URL: <a href="https://choria.io/" title="Choria">https://choria.io/</a></td></tr></table><p>
-	Contact: Puppet Team &lt;<a href="mailto:puppet@FreeBSD.org">puppet@FreeBSD.org</a>&gt;
-	</p><p>Since out last status report a few years ago, the puppet@ team regularly
-updated the various Puppet ports to follow upstream releases of Puppet
-4, Puppet 5 and Puppet 6.  Puppet 4 was removed when it reached EOL.
-</p>
-<p>More recently, an effort was made to enhance Facter 4 so that it can be
-used as a drop-in replacement of Facter 3 on FreeBSD.  Facter 4 is a
-Ruby rewrite of Facter 3, the C++ rewrite of Facter 2 which was
-initially in Ruby.  As a consequence we have two ports for Facter:
-sysutils/facter is the C++ implementation (Facter 3) and
-sysutils/rubygems-facter is the Ruby implementation (updated from Facter
-2 to Facter 4 a few weeks ago).  The Puppet 5 and Puppet 6 ports already
-allow to choose which version of Facter to use.  Facter 4 will be the
-default version of Facter with Puppet 7 which is expected to be released
-soon.
-</p>
-<p>We are getting ready to add a port for Puppet 7 as sysutils/puppet7
-when it is available, along with PuppetServer 7 (sysutils/puppetserver7),
-and PuppetDB 7 (databases/puppetdb7).
-</p>
-<p>Regarding orchestration, most Marionette Collective ports have been
-deprecated for a long time, and the last component sysutils/mcollective
-is expected to be deprecated soon: Marionette Collective was not shipped
-anymore with Puppet 6 and Bolt has been made available as a lightweight
-replacement.
-</p>
-<p>Bolt is already available in the ports tree as sysutils/rubygems-bolt),
-but if you are using Marionette Collective, you are invited to look into
-Choria which will reach the ports tree soon as sysutils/choria.  Choria
-is a direct evolution of Marionette Collective allowing a smooth
-transition from MCollective.  Once Choria is available in the ports
-tree, Marionette Collective will be deprecated.
-</p><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2020-10-2020-12.html b/website/content/en/status/report-2020-10-2020-12.html
deleted file mode 100644
index 1537096bf0..0000000000
--- a/website/content/en/status/report-2020-10-2020-12.html
+++ /dev/null
@@ -1,2364 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
-  <head>
-    <title>FreeBSD Quarterly Status Report</title>
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-    <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
-    <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
-    <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script>
-  </head>
-  <body>
-    <div id="containerwrap">
-      <div id="container">
-        <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
-  <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
-        <div id="headercontainer">
-          <div id="header">
-            <h2 class="blockhide">Header And Logo</h2>
-            <div id="headerlogoleft">
-              <a href="../.." title="FreeBSD">
-                <img src="https://www.FreeBSD.org/layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
-              </a>
-            </div>
-            <div id="headerlogoright">
-              <div class="frontdonateroundbox">
-                <div class="frontdonatetop">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-                <div class="frontdonatecontent">
-                  <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
-                </div>
-                <div class="frontdonatebot">
-                  <div>
-                    <b style="display: none;">.</b>
-                  </div>
-                </div>
-              </div>
-              <h2 class="blockhide">Peripheral Links</h2>
-              <div id="searchnav">
-                <ul id="searchnavlist"></ul>
-              </div>
-              <div id="search">
-                <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
-                  <h2 class="blockhide">
-                    <label for="words">Search</label>
-                  </h2>
-                  <input type="hidden" name="ka" value="v" />
-                  <input type="hidden" name="kt" value="v" />
-                  <input type="hidden" name="kh" value="1" />
-                  <input type="hidden" name="kj" value="r2" />
-                  <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
-                  <span>�</span>
-                  <input id="submit" name="submit" type="submit" value="Search" />
-                </form>
-              </div>
-            </div>
-          </div>
-          <h2 class="blockhide">Site Navigation</h2>
-          <div id="menu">
-            <ul class="first">
-              <li>
-                <a href="../../">Home</a>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../about.html">About</a>
-                <ul>
-                  <li>
-                    <a href="../../projects/newbies.html">Introduction</a>
-                  </li>
-                  <li>
-                    <a href="../../features.html">Features</a>
-                  </li>
-                  <li>
-                    <a href="../../advocacy/">Advocacy</a>
-                  </li>
-                  <li>
-                    <a href="../../marketing/">Marketing</a>
-                  </li>
-                  <li>
-                    <a href="../../privacy.html">Privacy Policy</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../where.html">Get FreeBSD</a>
-                <ul>
-                  <li>
-                    <a href="../../releases/">Release Information</a>
-                  </li>
-                  <li>
-                    <a href="../../releng/">Release Engineering</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../docs.html">Documentation</a>
-                <ul>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
-                  </li>
-                  <li>
-                    <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
-                  </li>
-                  <li>
-                    <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
-                  </li>
-                  <li>
-                    <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
-                  </li>
-                  <li>
-                    <a href="../../docs/books.html">All Books and Articles</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../community.html">Community</a>
-                <ul>
-                  <li>
-                    <a href="../../community/mailinglists.html">Mailing Lists</a>
-                  </li>
-                  <li>
-                    <a href="https://forums.FreeBSD.org">Forums</a>
-                  </li>
-                  <li>
-                    <a href="../../usergroups.html">User Groups</a>
-                  </li>
-                  <li>
-                    <a href="../../events/events.html">Events</a>
-                  </li>
-                  <li>
-                    <a href="http://freebsdjournal.com">FreeBSD Journal</a>
-                  </li>
-                  <li>
-                    <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../projects/index.html">Developers</a>
-                <ul>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
-                  </li>
-                  <li>
-                    <a href="https://cgit.FreeBSD.org">Git Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
-                  </li>
-                  <li>
-                    <a href="https://github.com/freebsd">GitHub Mirror</a>
-                  </li>
-                  <li>
-                    <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
-                  </li>
-                  <li>
-                    <a href="https://wiki.FreeBSD.org">Wiki</a>
-                  </li>
-                  <li>
-                    <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="../../support.html">Support</a>
-                <ul>
-                  <li>
-                    <a href="../../commercial/commercial.html">Vendors</a>
-                  </li>
-                  <li>
-                    <a href="../../security/">Security Information</a>
-                  </li>
-                  <li>
-                    <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
-                  </li>
-                  <li>
-                    <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-            <ul>
-              <li>
-                <a href="https://www.freebsdfoundation.org/">Foundation</a>
-                <ul>
-                  <li>
-                    <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
-                  </li>
-                  <li>
-                    <a href="../../donations/index.html#systems">Hardware Donations</a>
-                  </li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </div>
-        <div id="content">
-          <div id="sidewrap">
-            <div id="sidenav">
-              <h2 class="blockhide">Section Navigation</h2>
-              <ul>
-                <li>
-                  <a href="../../about.html">About</a>
-                </li>
-                <li>
-                  <a href="../../features.html">Features</a>
-                </li>
-                <li>
-                  <a href="../../applications.html">Applications</a>
-                </li>
-                <li>
-                  <a href="../../advocacy/">Advocacy</a>
-                </li>
-                <li>
-                  <a href="../../marketing/">Marketing</a>
-                </li>
-                <li>
-                  <a href="../../administration.html">Administration</a>
-                </li>
-                <li>
-                  <a href="../../news/newsflash.html">News</a>
-                </li>
-                <li>
-                  <a href="../../events/events.html">Events</a>
-                </li>
-                <li>
-                  <a href="../../news/press.html">Press</a>
-                </li>
-                <li>
-                  <a href="../../multimedia/multimedia.html">Multimedia</a>
-                </li>
-                <li>
-                  <a href="../../art.html">Artwork</a>
-                </li>
-                <li>
-                  <a href="../../logo.html">Logo</a>
-                </li>
-                <li>
-                  <a href="../../donations/">Donations</a>
-                </li>
-                <li>
-                  <a href="../../copyright/">Legal Notices</a>
-                </li>
-                <li>
-                  <a href="../../privacy.html">Privacy Policy</a>
-                </li>
-              </ul>
-            </div>
-          </div>
-          <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects for the period between
-October and December, and is the fourth of four planned reports for 2020.
-</p><p>This quarter had quite a lot of work done, including but certainly not
-limited to, in areas relating to everything from multiple architectures
-such as x86, aarch64, riscv, and ppc64 for both base and ports, over kernel
-changes such as vectored aio, routing lookups and multipathing, an
-alternative random(4) implementation, zstd integration for kernel
-dumps, log compression, zfs and preparations for pkg(8), along with
-wifi changes, changes to the toolchain like the new elfctl utility,
-and all the way to big changes like the git migration and moving the
-documentation from DocBook to Hugo/AsciiDoctor, as well as many other
-things too numerous to mention in an introduction.
-</p><p>This report with 42 entries, which don't hold the answer to life, the
-universe and everything, couldn't have happened without all the people
-doing the work also writing an entry for the report, so the quarterly
-team would like to thank them, as otherwise, we wouldn't have anything
-to do.
-</p><p>Please note that the deadline for submissions covering the period
-between January and March is March 31st.
-</p><p>We hope you'll enjoy reading as much as we enjoyed compiling it.<br clear="none" />
-Daniel Ebdrup Jensen, on behalf of the quarterly team.
-</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team
-</a></li><li><a href="#Cluster-Administration-Team">Cluster Administration Team</a></li><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Office-Hours">Office Hours</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#GPL-in-Base">GPL in Base</a></li><li><a href="#Git-Migration-Working-Group">Git Migration Working Group</a></li><li><a href="#Linux-compatibility-layer-update">Linux compatibility layer update</a></li><li><a href="#LLDB-Debugger-Improvements">LLDB Debugger Improvements</a></li><li><a href="#Upstreaming-NetApp-Changes">Upstreaming NetApp Changes</a></li><li><a href="#NFS-over-TLS-implementation">NFS over TLS implementation</a></li><li><a href="#OpenBSM-Synchronisation">OpenBSM Synchronisation</a></li><li><a href="#Tool-Chain">Tool Chain</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#Intel-wireless-update">Intel wireless update</a></li><li><a href="#Fenestras-X-random(4)">Fenestras X random(4)</a></li><li><a href="#pf-performance-improvement">pf performance improvement</a></li><li><a href="#IP-Routing-lookup-improvements">IP Routing lookup improvements</a></li><li><a href="#Scalable-routing-multipath-support">Scalable routing multipath support</a></li><li><a href="#Thunderbolt3/USB4-stack">Thunderbolt3/USB4 stack</a></li><li><a href="#Vectored-AIO">Vectored AIO</a></li><li><a href="#ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#arm64-platform-updates">arm64 platform updates</a></li><li><a href="#FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Dual-stack-ping-command">Dual-stack ping command</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#FreeBSD-Office-team">FreeBSD Office team</a></li><li><a href="#Ports-On-Non-x86-Architectures">Ports On Non-x86 Architectures</a></li><li><a href="#Python-2.7-removal-from-Ports">Python 2.7 removal from Ports</a></li><li><a href="#Xfce-on-FreeBSD">Xfce on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></li><li><a href="#DOCNG-on-FreeBSD">DOCNG on FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#Prometheus-NFS-Exporter">Prometheus NFS Exporter</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#FreeBSD-Aarch64-under-VMWare-ESXi-ARM-Fling">FreeBSD Aarch64 under VMWare ESXi-ARM Fling</a></li><li><a href="#Bastille">Bastille</a></li><li><a href="#CheriBSD">CheriBSD</a></li><li><a href="#Embedded-Lab-Project">Embedded Lab Project</a></li><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#helloSystem">helloSystem</a></li><li><a href="#K8S-bhyve">K8S-bhyve</a></li><li><a href="#Puppet">Puppet</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><p>Entries from the various official and semi-official teams,
-      as found in the <a href="../../administration.html" shape="rect">Administration
-	Page</a>.</p><br /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
-	Contact: Deb Goodkin &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
-	</p><p>The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
-supporting and promoting the FreeBSD Project and community worldwide.  Funding
-comes from individual and corporate donations and is used to fund and manage
-software development projects, conferences and developer summits, and provide
-travel grants to FreeBSD contributors.  The Foundation purchases and supports
-hardware to improve and maintain FreeBSD infrastructure and provides resources
-to improve security, quality assurance, and release engineering efforts;
-publishes marketing material to promote, educate, and advocate for the FreeBSD
-Project; facilitates collaboration between commercial vendors and FreeBSD
-developers; and finally, represents the FreeBSD Project in executing contracts,
-license agreements, and other legal arrangements that require a recognized
-legal entity.
-</p>
-<p>Here are some highlights of what we did to help FreeBSD last quarter:
-</p>
-<h3>COVID-19 Impact to the Foundation</h3>
-
-<p>Like most organizations, we transitioned all of our staff to work from home.
-We also put a temporary ban on travel for staff members, which didn't affect
-our output too much, since most conferences went virtual.  We continued
-supporting the community and Project, even though some of our work and
-responses may have been delayed because of changes in some of our priorities
-and the impact of limited childcare for a few of our staff members.
-</p>
-<h3>Partnerships and Commercial User Support</h3>
-
-<p>We help facilitate collaboration between commercial users and FreeBSD
-developers.  We also meet with companies to discuss their needs and bring that
-information back to the Project.  Not surprisingly, the stay at home orders,
-combined with our company ban on travel during Q4 made in-person meetings
-non-existent.  However, the team was able to continue meeting with our partners
-and commercial users virtually.  These meetings help us understand some of the
-applications where FreeBSD is used.
-</p>
-<p>An event we help plan and organize, that helps with vendor/developer
-engagement, is the annual Bay Area Vendor Summit.  We weren't going to let a
-pandemic stop us from holding this invaluable yearly event, so we went virtual!
-From the feedback we received from the vendor community on how we should run
-this, so it would be beneficial for them, we decided to hold this over 3 half
-days in November.  One unexpected result was that more commercial users from
-around the world attended.  Since a Vendor/Developer Summit is typically
-invitation only, we opened this up to FreeBSD contributors from around the
-world to watch the livestream.  Because of the success and excitement of this
-event, we are planning to hold another one around June or July.
-</p>
-<h3>Fundraising Efforts</h3>
-
-<p>We want to take a moment to say thank you to all the individuals and
-corporations that stepped up to help fund our efforts last year.  As of this
-writing, we raised $1,235,926, and will have the final tally by mid-January.
-The companies that gave generous financial contributions include Arm, NetApp,
-Netflix, Juniper Networks, Beckhoff, VMware, Stormshield, Tarsnap, and Google.
-We also want to say thank you to the Koum Family Foundation for awarding us a
-large grant, and to the employees of Nginx who also made generous financial
-contributions.
-</p>
-<p>We truly appreciate these large contributions, which makes the most impact on
-how much we can contribute back to the Project.  However, it's the individual
-donations that have the most meaning to us.  Those are the folks who are giving
-because they trust we will invest their personal donations, whether large or
-small, into improving the operating system and Project.  As stewards of your
-donations, we want to thank you for your trust in us and your commitment to
-making FreeBSD the best platform for products, education, research, computing,
-and more.
-</p>
-<p>You'll find out how we used your donations for Q4 in our report, as well as in
-individual reports throughout this status report.
-</p>
-<p>Though we know this is a Q4 status report, we are excited about our plans for
-2021, including growing our software development team!  We'll be posting two
-job descriptions for a Senior Software Developer and Project Coordinator soon.
-</p>
-<p>Please consider making a donation to help us continue and increase our support
-for FreeBSD in 2021: <a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">https://www.FreeBSDfoundation.org/donate/</a>.
-</p>
-<p>We also have the Partnership Program, to provide more benefits for our larger
-commercial donors.  Find out more information at
-<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>
-and share with your companies!
-</p>
-<h3>OS Improvements</h3>
-
-<p>The Foundation provided many project grants over the last quarter, and you
-can read about OpenZFS Zstd support, Linuxulator application compatibility
-improvements, LLDB target support, test lab infrastructure, and WiFi projects
-in other entries in this quarterly report.
-</p>
-<p>The Foundation hired six co-op students from the University of Waterloo during
-the 2020 fall term, as well as one intern.  Former co-op student Tiger
-returned, and new students Yang and Zac joined us for the first time.
-</p>
-<p>Tiger worked on improvements to the code-coverage guided kernel fuzzing tool
-Syzkaller, adding new system call definitions so that Syzkaller can expand the
-code it tests.  A number of FreeBSD kernel bug fixes have already resulted from
-this work.  Tiger also contributed a number of improvements to the ELF Tool
-Chain set of binary utilities, and worked on tooling to run tests from other
-tool suites against ELF Tool Chain.
-</p>
-<p>Zac worked on an improvement to the pkg package management tool, investigating
-and upstreaming patches for FreeBSD support in FreePBX, and investigating
-compiler support for addressing the stack clash vulnerability.
-</p>
-<p>Yang investigated and fixed a compilation bug with the kernel's Skein-1024
-assembly implementation (used by ZFS), and then a number of projects related to
-Capsicum: applying Capsicum to sort(1), implementing a Capsicum service to
-execute utilities, and finally working with developers of the Game of Trees
-(got) version control system to adapt it for Capsicum support.
-</p>
-<p>Our intern Ka Ho focused on improving the desktop experience of the FreeBSD.
-He fixed and improved many items of OBS (Open Broadcaster Software) on
-FreeBSD, worked on FreeBSD native audio support on Firefox, adding a facility
-that user-space audio programs could make use of to enumerate a list of audio
-devices.  He also ported the fcitx5 input method framework.
-</p>
-<p>The five Foundation staff members continued contributions in 2020 in both
-ongoing operational tasks (including the Git working group and security team)
-and software development for a number of projects.
-</p>
-<p>Staff members responded to reported security vulnerabilities and release
-errata, prepared patches, and participated in the security advisory process.
-We also worked on proactive security vulnerability mitigations.  Syzkaller
-also provided many reports of kernel issues that resulted in
-Foundation-sponsored bug fixes.  We worked on several issues relating to
-FreeBSD/arm64 to move it along the path of being a Tier-1 architecture.
-</p>
-<p>We participated in code reviews and supported community members in integrating
-changes into FreeBSD, and triaged incoming bug reports.
-</p>
-<p>We contributed enhancements to many kernel and userland subsystems, including
-the x86 pmap layer, ELF run-time linker and kernel loader, the Capsicum
-sandboxing framework and Casper services, the threading library, some RISC-V
-changes, the build system, tool chain and freebsd-update, network stack
-stability improvements, machine-dependent optimizations, new kernel interfaces,
-DTrace bug fixes, documentation improvements, and others.
-</p>
-<h3>Continuous Integration and Quality Assurance</h3>
-
-<p>The Foundation provides a full-time staff member and funds projects on
-improving continuous integration, automated testing, and overall quality
-assurance efforts for the FreeBSD Project.
-</p>
-<p>During the fourth quarter of 2020, Foundation staff continued improving and
-monitoring the Project's CI infrastructure, and working with experts to fix
-the failing builds and the regressions found by tests.  The work was focused
-on pre-commit tests and development of the CI staging environment.  The other
-main working item is working on the VCS migration to change the src and doc
-source from Subversion to Git.  There are also many work-in-progress tasks like
-analysis and improve the tests of non-x86 platforms.
-</p>
-<p>See the FreeBSD CI section of this report for completed work items and detailed
-information.
-</p>
-<h3>Supporting FreeBSD Infrastructure</h3>
-
-<p>The Foundation provides hardware and support to improve the FreeBSD
-infrastructure.  Last quarter, we continued supporting FreeBSD hardware located
-around the world.  We coordinated efforts between the new NYI Chicago facility
-and clusteradm to start working on getting the facility prepared for some of
-the new FreeBSD hardware we are planning on purchasing.  NYI generously
-provides this for free to the Project.  We also worked on connecting with the
-new owners of the NYI Bridgewater site, where most of the existing FreeBSD
-infrastructure is located.
-</p>
-<p>Some of the purchases we made for the Project last quarter to support
-infrastructure includes:
-</p>
-<ul>
-<li><p>5 application servers to run tasks like bugzilla, wiki, website, cgi,
-    Phabricator, host git, etc.
-</p></li>
-<li><p>1 server to replace the old pkg server, which will provide a lot more IOPS
-    to avoid the slowdowns seen during peak times of the day where the disks
-    simply cannot keep up with the request volume.
-</p></li>
-<li><p>1 server for exp-runs and to make them faster.
-</p></li>
-<li><p>1 server to build packages more frequently.
-</p>
-</li></ul>
-<h3>FreeBSD Advocacy and Education</h3>
-
-<p>A large part of our efforts are dedicated to advocating for the Project.  This
-includes promoting work being done by others with FreeBSD; producing advocacy
-literature to teach people about FreeBSD and help make the path to starting
-using FreeBSD or contributing to the Project easier; and attending and getting
-other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD
-tables, and give FreeBSD presentations.
-</p>
-<p>The FreeBSD Foundation sponsors many conferences, events, and summits around
-the globe. These events can be BSD-related, open source, or technology events
-geared towards underrepresented groups. We support the FreeBSD-focused events
-to help provide a venue for sharing knowledge, to work together on projects,
-and to facilitate collaboration between developers and commercial users.  This
-all helps provide a healthy ecosystem. We support the non-FreeBSD events to
-promote and raise awareness of FreeBSD, to increase the use of FreeBSD in
-different applications, and to recruit more contributors to the Project.
-</p>
-<p>While we were still unable to attend in-person meetings due to COVID-19, we
-were able to attend virtual events at new venues and facilitate the first
-online FreeBSD Vendor Summit.  In addition to attending and planning virtual
-events, we are continually working on new training initiatives and updating our
-selection of <a href="https://freebsdfoundation.org/freebsd-project/resources/" shape="rect">how-to guides</a> to facilitate getting more folks to try out FreeBSD.
-</p>
-<p>Check out some of the advocacy and education work we did last quarter:
-</p>
-<ul>
-<li><p>Continued our FreeBSD Fridays series of 101 classes. Topics included an
-    Introduction to Capsicum, Introduction to Bhyve, Introduction to DTrace, and
-    more.  Videos of the past sessions can be found <a href="https://freebsdfoundation.org/freebsd-fridays/" shape="rect">here</a>. We'll be back with new
-    sessions in early 2021.
-</p></li>
-<li><p>Gave a FreeBSD talk at the nerdear.la conference on October 20th.
-</p></li>
-<li><p>Participated in the podcast: <a href="https://freebsdfoundation.org/news-and-events/latest-news/what-the-dev-podcast-a-dive-into-the-freebsd-foundation-on-its-20th-anniversary/" shape="rect">What the Dev: A Dive into the FreeBSD Foundation on its 20th Anniversary</a>
-</p></li>
-<li><p>Promoted the Foundation's 20th Anniversary in the FossBytes article:
-    <a href="https://freebsdfoundation.org/news-and-events/latest-news/fossbytes-20-years-of-the-freebsd-foundation/" shape="rect">20 Years of The FreeBSD Foundation</a>
-</p></li>
-<li><p>Continued to promote the FreeBSD Office Hours series.  Videos from the one hour
-    sessions can be found on the Project's <a href="https://www.youtube.com/channel/UCxLxR_oW-NAmChIcSkAyZGQ" shape="rect">YouTube Channel</a>.  See the Office Hours
-    section of this report for more information.
-</p></li>
-<li><p>Added two new How-To Guides: <a href="https://freebsdfoundation.org/contributing-freebsd-documentation/" shape="rect">Contributing FreeBSD Documentation</a>
-    and <a href="https://freebsdfoundation.org/freebsd-project/resources/how-to-submit-a-bug-report/" shape="rect">How to Submit a Bug Report</a>.
-</p></li>
-<li><p>Worked with the organizing committee to host the <a href="https://wiki.freebsd.org/DevSummit/202011" shape="rect">November 2020 Vendor Summit</a>
-</p></li>
-<li><p>Promoted the <a href="https://freebsdfoundation.org/news-and-events/latest-news/freebsd-essential-to-bringing-cheri-and-arms-morello-processor-to-life/" shape="rect">use of FreeBSD</a> in regards to CHERI and ARM's Morello Processor
-</p></li>
-<li><p>Authored a <a href="https://www.fosslife.org/beginners-guide-freebsd" shape="rect">Beginners Guide to FreeBSD</a> for Fosslife.
-</p></li>
-<li><p>Sponsored All Things Open as a Media Sponsor.
-</p></li>
-<li><p>Sponsored OpenZFS Developers Summit at the Bronze level.
-</p></li>
-<li><p>Applied for a virtual stand at FOSDEM 2021.
-</p></li>
-<li><p>Committed to attend the online Apricot 2021.
-</p>
-</li></ul>
-<p>Keep up to date with our latest work in our newsletters:
-<a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">https://www.freebsdfoundation.org/news-and-events/newsletter/</a>
-</p>
-<p>Netflix provided an update on how and why they use FreeBSD in our latest
-<a href="https://freebsdfoundation.org/blog/freebsd-case-study-netflix/" shape="rect">Contributor Case Study</a>.
-</p>
-<p>We help educate the world about FreeBSD by publishing the professionally
-produced FreeBSD Journal.  As we mentioned previously, the FreeBSD Journal is
-now a free publication.  Find out more and access the latest issues at
-<a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>
-</p>
-<p>You can find out more about events we attended and upcoming events at
-<a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">https://www.FreeBSDfoundation.org/news-and-events/</a>.
-</p>
-<h3>Legal/FreeBSD IP</h3>
-
-<p>The Foundation owns the FreeBSD trademarks, and it is our responsibility to
-protect them.  We also provide legal support for the core team to investigate
-questions that arise.
-</p>
-<p>Go to <a href="http://www.FreeBSDfoundation.org" shape="rect">http://www.FreeBSDfoundation.org</a> to find out how we support FreeBSD and
-how we can help you!
-</p><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team
-</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/12.2R/schedule.html" title="https://www.freebsd.org/releases/12.2R/schedule.html">FreeBSD 12.2-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/12.2R/schedule.html" title="FreeBSD 12.2-RELEASE schedule">https://www.freebsd.org/releases/12.2R/schedule.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/13.0R/schedule.html" title="https://www.freebsd.org/releases/13.0R/schedule.html">FreeBSD 13.0-RELEASE schedule</a></td><td>
-	    URL: <a href="https://www.freebsd.org/releases/13.0R/schedule.html" title="FreeBSD 13.0-RELEASE schedule">https://www.freebsd.org/releases/13.0R/schedule.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
-	    URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
-	Contact: FreeBSD Release Engineering Team &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Release Engineering Team is responsible for setting
-and publishing release schedules for official project releases
-of FreeBSD, announcing code freezes and maintaining the respective
-branches, among other things.
-</p>
-<p>During the fourth quarter of 2020, the Release Engineering Team completed
-work on 12.2-RELEASE, the third release from the stable/12 branch, released
-on October 27.  Thank you to all involved for the hard work that went into
-this release.
-</p>
-<p>Additionally throughout the quarter, several development snapshots builds
-were released for the head, stable/12, and stable/11 branches.
-Development snapshot builds for 13.0-CURRENT have recently been built from
-the Git tree within the project, while further snapshot builds for 12.x and
-11.x will continue to be built from Subversion.  As we approach the end of
-2020, continued preparations are being put in place for the upcoming 13.0
-release, which will be the first release from Git.
-</p>
-<p>Much of this work was sponsored by Rubicon Communications, LLC (netgate.com)
-and the FreeBSD Foundation.
-</p><hr /><h2><a name="Cluster-Administration-Team" href="#Cluster-Administration-Team" id="Cluster-Administration-Team">Cluster Administration Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/administration.html#t-clusteradm" title="https://www.freebsd.org/administration.html#t-clusteradm">Cluster Administration Team members</a></td><td>
-	    URL: <a href="https://www.freebsd.org/administration.html#t-clusteradm" title="Cluster Administration Team members">https://www.freebsd.org/administration.html#t-clusteradm</a></td></tr></table><p>
-	Contact: Cluster Administration Team &lt;<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Cluster Administration Team consists of the people responsible for
-administering the machines that the Project relies on for its distributed work
-and communications to be synchronised. In this quarter, the team has worked
-on the following:
-</p>
-<ul>
-<li><p>Finished setting up the Malaysia mirror site, generously hosted by the
-    <a href="https://myren.net.my/" shape="rect">Malaysian Research &amp; Education Network</a>.  Traffic
-    from Oceania and parts of Asia is now going to this mirror instead of
-    farther away sites like Japan and California.
-</p></li>
-<li><p>Upgraded the package building machines to a version of head from
-    mid-October 2020.
-</p></li>
-<li><p>Upgraded developer machines in the cluster (freefall, ref* and universe*) to
-    a version of head from mid-October 2020.
-</p></li>
-<li><p>Installed eight new x86 servers in our New Jersey site:
-    five application servers, two package builders and one mirror server.
-</p><ul>
-<li><p>The new mirror server is in production (pkg0.nyi.freebsd.org).
-</p></li>
-<li><p>The two package builders are in production.
-</p></li>
-<li><p>Two of the application servers have been put into production as the Git
-source of truth and the cgit web frontend, respectively.
-</p></li></ul>
-</li><li><p>Installed two new aarch64 servers in our New Jersey site.  Both are now
-    building aarch64 packages.
-</p></li>
-<li><p>Fixed package mirror synchronisation for powerpc64 packages.
-</p></li>
-<li><p>Rebuilt the ZFS pool on the UK mirror server (pkg0.bme.freebsd.org) for
-    better I/O parallelism.  This should improve download performance
-    especially at peak times.
-</p></li>
-<li><p>Ongoing systems administration work:
-</p><ul>
-<li><p>Accounts management for committers.
-</p></li>
-<li><p>Backups of critical infrastructure.
-</p></li>
-<li><p>Keeping up with security updates in 3rd party software.
-</p>
-</li></ul>
-</li></ul>
-Work in progress:
-
-<ul>
-<li><p>Hardware refreshing for web services, backup version control system in NYI
-</p></li>
-<li><p>Upgrading production machines in the FreeBSD cluster to 12.2
-</p><ul>
-<li><p>Most machines have been upgraded as of mid-December 2020
-</p></li>
-<li><p>Remaining machines will be decommissioned / repurposed after services
-migrate to newer hardware
-</p></li></ul>
-</li><li><p>Supporting Git migration and infrastructure setup
-</p></li>
-<li><p>powerpc pkgbuilder/ref/universal machines
-</p></li>
-<li><p>Preparations for a new mirror site in Australia, to be hosted by
-    <a href="https://www.ix.asn.au" shape="rect">IX Australia</a>.
-</p></li>
-<li><p>Setup Brazil (BRA) mirror.
-</p></li>
-<li><p>Review the service jails and service administrators operation.
-</p></li>
-<li><p>Searching for more providers that can fit the requirements for a
-    <a href="https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout" shape="rect">generic mirrored layout</a>
-    or a
-    <a href="https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror" shape="rect">tiny mirror</a>.
-</p></li></ul>
-<hr /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://ci.FreeBSD.org/hwlab" title="https://ci.FreeBSD.org/hwlab">FreeBSD Hardware Testing Lab</a></td><td>
-	    URL: <a href="https://ci.FreeBSD.org/hwlab" title="FreeBSD Hardware Testing Lab">https://ci.FreeBSD.org/hwlab</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org" title="https://artifact.ci.FreeBSD.org">FreeBSD CI artifact archive</a></td><td>
-	    URL: <a href="https://artifact.ci.FreeBSD.org" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org</a></td></tr><tr><td><a href="https://hackmd.io/@FreeBSD-CI" title="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</a></td><td>
-	    URL: <a href="https://hackmd.io/@FreeBSD-CI" title="FreeBSD CI weekly report">https://hackmd.io/@FreeBSD-CI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="https://wiki.freebsd.org/3rdPartySoftwareCI">3rd Party Software CI</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="3rd Party Software CI">https://wiki.freebsd.org/3rdPartySoftwareCI</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
-	    URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</a></td><td>
-	    URL: <a href="https://github.com/freebsd/freebsd-ci" title="FreeBSD CI Repository">https://github.com/freebsd/freebsd-ci</a></td></tr></table><p>
-	Contact: Jenkins Admin &lt;<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-ci channel on EFNet<br clear="none" />
-</p>
-<p>The FreeBSD CI team maintains the continuous integration system
-of the FreeBSD project.  The CI system firstly checks the committed changes
-can be successfully built, then performs various tests and analysis over the
-newly built results.
-The artifacts from those builds are archived in the artifact server for
-further testing and debugging needs.  The CI team members examine the
-failing builds and unstable tests and work with the experts in that area to
-fix the code or adjust test infrastructure.  The details of these efforts
-are available in the <a href="https://hackmd.io/@FreeBSD-CI" shape="rect">weekly CI reports</a>.
-</p>
-<p>During the fourth quarter of 2020, we continued working with the contributors and
-developers in the project to fulfil their testing needs and also keep
-collaborating with external projects and companies to improve their products
-and FreeBSD.
-</p>
-<p>Important changes:
-</p>
-<ul>
-<li><p>doc jobs were changed to use git to follow VCS migration:
-</p><ul>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-doc-main/" shape="rect">https://ci.freebsd.org/job/FreeBSD-doc-main/</a>
-</p></li>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-doc-main-igor/" shape="rect">https://ci.freebsd.org/job/FreeBSD-doc-main-igor/</a>
-    Thanks Brandon Bergren (bdragon@)
-</p></li></ul>
-</li><li><p>head and stable/12 build environment have been upgraded to 12.2-RELEASE
-</p>
-</li></ul>
-New jobs added:
-
-<ul>
-<li><p><a href="https://ci.freebsd.org/job/FreeBSD-head-riscv64-LINT" shape="rect">LINT kernel of head on riscv64</a>
-</p>
-</li></ul>
-Work in progress:
-
-<ul>
-<li><p>Follow VCS migration, change src jobs to use Git - PRs are
-    <a href="https://github.com/freebsd/freebsd-ci/pull/121" shape="rect">available</a>
-    Thanks Brandon Bergren (bdragon@)
-</p></li>
-<li><p>Collecting and sorting CI tasks and ideas
-    <a href="https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo" shape="rect">here</a>
-</p></li>
-<li><p>Testing and merging pull requests in the
-    <a href="https://github.com/freebsd/freebsd-ci/pulls" shape="rect">the FreeBSD-ci repo</a>
-</p></li>
-<li><p>Designing and implementing pre-commit CI building and testing
-</p></li>
-<li><p>Reducing the procedures of CI/test environment setting up for contributors and
-    developers
-</p></li>
-<li><p>Setting up the CI stage environment and putting the experimental jobs on it
-</p></li>
-<li><p>Setting up public network access for the VM guest running tests
-</p></li>
-<li><p>Implementing automatic tests on bare metal hardware
-</p></li>
-<li><p>Adding drm ports building tests against -CURRENT
-</p></li>
-<li><p>Planning to run ztest and network stack tests
-</p></li>
-<li><p>Adding more external toolchain related jobs
-</p></li>
-<li><p>Improving the hardware lab to be more mature and adding more hardware
-</p></li>
-<li><p>Helping more software get FreeBSD support in their CI pipeline
-    Wiki pages: <a href="https://wiki.freebsd.org/3rdPartySoftwareCI" shape="rect">3rdPartySoftwareCI</a>,
-    <a href="https://wiki.freebsd.org/HostedCI" shape="rect">HostedCI</a>
-</p></li>
-<li><p>Working with hosted CI providers to have better FreeBSD support
-</p></li>
-<li><p>The build and test results will be sent to the
-    <a href="https://lists.freebsd.org/mailman/listinfo/dev-ci" shape="rect">dev-ci mailing list</a>
-    soon. Feedback and help with analysis is very appreciated!
-</p>
-</li></ul>
-Please see freebsd-testing@ related tickets for more WIP information, and don't hesitate to join the effort!
-
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
-	    URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
-	    URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://ftp.freebsd.org/pub/FreeBSD/ports/ports/" title="http://ftp.freebsd.org/pub/FreeBSD/ports/ports/">Ports Tarball</a></td><td>
-	    URL: <a href="http://ftp.freebsd.org/pub/FreeBSD/ports/ports/" title="Ports Tarball">http://ftp.freebsd.org/pub/FreeBSD/ports/ports/</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p><p>The Ports Management Team is responsible for overseeing the
-overall direction of the Ports Tree, building packages, and
-personnel matters.  Below is what happened in the last quarter.
-</p>
-<p>For the last quarter the dashboard looks like:
-</p>
-<ul>
-<li><p>41500 ports (including flavors)
-</p></li>
-<li><p>2516 open PRs of which 625 are unassigned
-</p></li>
-<li><p>8715 commits to the HEAD branch by 164 committers
-</p></li>
-<li><p>420 commits to the 2020Q4 branch by 59 committers
-</p>
-</li></ul>
-Compared to the third quarter, the PR statistics mostly stayed the same. There
-<p>were slightly fewer commits by the same number of people. The number of ports
-again grew steadily, this time by almost 4 percent.
-</p>
-<p>During the last quarter, we welcomed Juray Lutter (otis@) as a new ports
-committer and said goodbye to cpm, jadawin, knu, araujo, mmokhi and scottl.
-</p>
-<p>Traditionally merges to the quarterly ports branches, which are more
-conservative versions of the HEAD tree, required approval of either the
-Ports Security Team (ports-secteam@) or portgmr@. There were already a number
-of blanket approvals for tested commits, ranging from fixing typing mistakes to
-upgrading web browsers to their latest version. As of last December, all
-ports committers are free to merge on their own, lessening the burden on
-ports-secteam@.
-</p>
-<p>Patent limitations have been disconnected from the license framework, given
-that patents are a complex topic with implications varying from one jurisdiction
-to another.
-</p>
-<p>The last quarter saw a number of updates to default versions of ports:
-</p>
-<ul>
-<li><p>librsvg2: "rust" on supported platforms, "legacy"
-    otherwise
-</p></li>
-<li><p>Mono: 5.10
-</p></li>
-<li><p>FPC switched to 3.2.0
-</p></li>
-<li><p>GCC switched to 10 for powerpc64le
-</p></li>
-<li><p>Lazarus switched to 2.0.10
-</p></li>
-<li><p>Ruby switched to 2.7.X
-</p></li>
-<li><p>Samba switched to 4.12
-</p>
-</li></ul>
-During the last quarter, a new virtual category was added: "education" for ports
-<p>that for instance help the user to learn about a certain topic or help
-facilitating examinations.
-</p>
-<p>The @shell and @sample keywords have been rewritten in Lua which makes root-dir
-compliant (see pkg -r) and ensures they are Capsicum-sandboxed.
-</p>
-<p>The last quarter also saw updates to several user-facing ports:
-</p>
-<ul>
-<li><p>Firefox 84.0.1
-</p></li>
-<li><p>Firefox-esr 78.6.0
-</p></li>
-<li><p>Chromium 87.0.4280.88
-</p></li>
-<li><p>Ruby 2.7.2
-</p></li>
-<li><p>Qt5 5.15.2
-</p></li>
-<li><p>XFce 4.16
-</p>
-</li></ul>
-As always, antoine@ was busy running exp-runs, 37 this quarter, testing:
-
-<ul>
-<li><p>various ports upgrades
-</p></li>
-<li><p>changing sys/cdefs.h in base
-</p></li>
-<li><p>adding "set pipefail" to most framework scripts to catch errors earlier
-</p></li>
-<li><p>changing the default locale to C.UTF-8 in base
-</p></li>
-<li><p>using bsdgrep as /usr/bin/grep
-</p></li></ul>
-<hr /><h2><a name="Office-Hours" href="#Office-Hours" id="Office-Hours">Office Hours</a></h2><p>
-	Contact: Allan Jude &lt;<a href="mailto:allanjude@freebsd.org">allanjude@freebsd.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>&gt;
-	</p><p>During the final quarter of 2020 three office hours sessions were held.
-</p>
-<p>The first was hosted by the core team in a time slot conducive to Asia and
-Australia, covering topics including the transition to git, recruiting for
-project teams, and core's todo list.
-</p>
-<p>The second was hosted by the git transition team, and answered attendee
-questions about the transition to git and how it would impact the project's
-workflows.
-</p>
-<p>The third session was hosted by bhyve maintainers Peter Grehan and John Baldwin
-to present recent development efforts and answer questions about bhyve.
-</p>
-<p>The project is looking for volunteers to host future office hours sessions, as
-well as taking topic suggestions. We also hope to improve the system to allow people
-to submit questions ahead of time, so that we can take maximum advantage of
-subject matter experts when we have them for these calls.
-</p>
-<p>You can find the schedule for future office hours, and videos of past
-office hours on the <a href="https://wiki.freebsd.org/OfficeHours" shape="rect">FreeBSD Wiki</a>
-</p>
-<p>Sponsor: ScaleEngine Inc.
-</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
-      to the Ports Collection or external projects.</p><br /><h2><a name="GPL-in-Base" href="#GPL-in-Base" id="GPL-in-Base">GPL in Base</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/GPLinBase" title="https://wiki.freebsd.org/GPLinBase">GPL Software in the Base System</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/GPLinBase" title="GPL Software in the Base System">https://wiki.freebsd.org/GPLinBase</a></td></tr></table><p>
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Kyle Evans &lt;<a href="mailto:kevans@FreeBSD.org">kevans@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Baptiste Daroussin &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;
-	</p><p>A long-standing goal of the FreeBSD project is for the base system to migrate
-to modern, copyfree or more permissively licensed components.  In this quarter,
-the following components have been successfully removed or replaced:
-</p>
-<ul>
-<li><p>gdb (<a href="https://cgit.freebsd.org/src/commit/?id=1c0ea326aa6d" shape="rect">removed</a> in favor of lldb in base or devel/gdb in ports)
-</p></li>
-<li><p>gnugrep (<a href="https://cgit.freebsd.org/src/commit/?id=b82a9ec5f53e" shape="rect">replaced</a> with bsdgrep)
-</p></li>
-<li><p>libgnuregex (<a href="https://cgit.freebsd.org/src/commit/?id=8aff76fb37b5" shape="rect">removed</a>)
-</p>
-</li></ul>
-The following component(s) have yet to be claimed.  Some replacement prospects
-<p>may be listed on the above-linked wiki page. Interested parties are welcome to
-evaluate the options to restart the discussion:
-</p>
-<ul>
-<li><p>dialog
-</p></li>
-<li><p>gcov (kernel)
-</p>
-</li></ul>
-The following component(s) have a principal investigator to coordinate work.
-<p>Note that partial completion likely means that a component is partially
-compatible, but could use evaluation and patches to bring parity with the
-component that it is replacing.
-</p>
-<ul>
-<li><p>diff3 (Contact bapt@ if interested)
-</p></li></ul>
-<hr /><h2><a name="Git-Migration-Working-Group" href="#Git-Migration-Working-Group" id="Git-Migration-Working-Group">Git Migration Working Group</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://cgit.FreeBSD.org/src" title="https://cgit.FreeBSD.org/src">src (base system) git repo</a></td><td>
-	    URL: <a href="https://cgit.FreeBSD.org/src" title="src (base system) git repo">https://cgit.FreeBSD.org/src</a></td></tr><tr><td><a href="https://cgit.FreeBSD.org/doc" title="https://cgit.FreeBSD.org/doc">doc git repo</a></td><td>
-	    URL: <a href="https://cgit.FreeBSD.org/doc" title="doc git repo">https://cgit.FreeBSD.org/doc</a></td></tr><tr><td><a href="https://cgit-dev.FreeBSD.org/ports" title="https://cgit-dev.FreeBSD.org/ports">Beta ports git repo</a></td><td>
-	    URL: <a href="https://cgit-dev.FreeBSD.org/ports" title="Beta ports git repo">https://cgit-dev.FreeBSD.org/ports</a></td></tr><tr><td><a href="https://github.com/bsdimp/freebsd-git-docs" title="https://github.com/bsdimp/freebsd-git-docs">Warner's git documentation repo</a></td><td>
-	    URL: <a href="https://github.com/bsdimp/freebsd-git-docs" title="Warner's git documentation repo">https://github.com/bsdimp/freebsd-git-docs</a></td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="https://lists.freebsd.org/mailman/listinfo/freebsd-git">FreeBSD-git mailing list</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="FreeBSD-git mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-git</a></td></tr><tr><td><a href="https://github.com/freebsd/git_conv" title="https://github.com/freebsd/git_conv">Git conversion tooling repo</a></td><td>
-	    URL: <a href="https://github.com/freebsd/git_conv" title="Git conversion tooling repo">https://github.com/freebsd/git_conv</a></td></tr><tr><td><a href="http://gameoftrees.org/" title="http://gameoftrees.org/">Game of Trees</a></td><td>
-	    URL: <a href="http://gameoftrees.org/" title="Game of Trees">http://gameoftrees.org/</a></td></tr><tr><td><a href="https://github.com/johnmehr/gitup" title="https://github.com/johnmehr/gitup">gitup</a></td><td>
-	    URL: <a href="https://github.com/johnmehr/gitup" title="gitup">https://github.com/johnmehr/gitup</a></td></tr></table><p>
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Warner Losh &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ulrich Sp�rlein &lt;<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>&gt;
-	</p><p>The Git working group largely completed the migration of the doc and src
-(base system) trees from Subversion to Git in December 2020.  We are currently
-working on some minor outstanding issues and preparing for the ports tree
-migration.
-</p>
-<p>We set up new hosts to serve as the Git repositories and mirrors, and developed
-commit hooks for restrictions on commits to various branches, generation of
-commit mail, and similar needs.
-</p>
-<p>The doc tree migration occurred on December 8th and 9th.  After the conversion
-some minor changes to the documentation build infrastructure were necessary.
-</p>
-<p>The src tree migration occurred between December 20th and 23rd for the main
-branch; some additional tasks occurred over the next week or so.  These
-included enabling the stable branches, vendor (contrib) code updates, and
-the git-&gt;svn gateway.  We are translating stable branch commits to Subversion
-for the stable/11 and stable/12 branches and associated release branches.  This
-allows FreeBSD users who follow stable branches or releases to continue using
-existing processes and tooling.
-</p>
-<p>An experimental Git conversion of the ports tree is available at the link
-above.  There are some unique challenges in the ports tree (that do not impact
-the doc or src repos in the same way), so additional work is ongoing.  The
-window for migrating the ports tree is immediately prior to a quarterly
-branch, so we anticipate a migration at the end of March 2021.  Over the next
-few months testing of the experimental ports repo is very welcome.
-</p>
-<p>Process documentation for developer and user interaction with FreeBSD's
-repositories is currently available in Warner's GitHub repository at the link
-above.  It will be moved to the FreeBSD developer's handbook and/or other
-suitable locations following the documentation project's asciidoc conversion.
-</p>
-<p>The working group is experimenting with two permissively-licensed tools that
-are compatible with Git servers or repositories.  Game of Trees is a version
-control system that is compatible with Git repositories.  It is being developed
-by Stefan Sperling along with some OpenBSD developers and other contributions.
-</p>
-<p>John Mehr's gitup is a minimal, dependency-free program that clones and
-synchronizes a local tree with a remote repository.  It is intended for use
-cases that would otherwise be served by tools like portsnap.
-</p>
-<p>Sponsor: The FreeBSD Foundation (in part)
-</p><hr /><h2><a name="Linux-compatibility-layer-update" href="#Linux-compatibility-layer-update" id="Linux-compatibility-layer-update">Linux compatibility layer update</a></h2><p>
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	</p><p>Linuxulator improvements have been ongoing for the last two years,
-with support from the FreeBSD foundation over a few distinct project
-grants as well as contributions from the community.
-The goal of this project is to improve FreeBSD's ability to execute
-unmodified Linux binaries.
-Current status is being tracked at <a href="https://wiki.freebsd.org/LinuxApps" shape="rect">Linux app status Wiki page</a>.
-The work has now shifted from command-line apps to desktop applications.
-</p>
-<p>There wasn't much Foundation-sponsored work done during this quarter,
-apart from extending fuse(4) to make it possible to run Linux FUSE
-servers, which is one of the things required to run AppImages.
-The Foundation-sponsored effort will continue into the first quarter
-of 2021 in order to make sure the 13.0-RELEASE ships with Linuxulator in a good shape.
-</p>
-<p>There was a very significant contribution from Conrad Meyer in the form
-of <code>SO_PASSCRED</code> setsockopt(2) support, <code>PR_SETDUMPABLE</code> and <code>PR_GETDUMPABLE</code>
-prctl(2) flags, and also <code>CLONE_FS</code> and <code>CLONE_FILES</code> handling.  This,
-along with some more cleanups and improvements, leads to working Linux
-Chromium; it has been tested with Netflix and Spotify clients.  It still
-requires three flags (<code>--no-sandbox --no-zygote --in-process-gpu</code>)
-to be passed on the command line to work around missing functionality, though.  Also,
-the name_to_handle_at(2) and open_by_handle_at(2) syscalls are now supported.
-There are also much better debug messages for unrecognized socket options.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="LLDB-Debugger-Improvements" href="#LLDB-Debugger-Improvements" id="LLDB-Debugger-Improvements">LLDB Debugger Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/" title="https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/">Moritz Systems Project Description</a></td><td>
-	    URL: <a href="https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/" title="Moritz Systems Project Description">https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/</a></td></tr><tr><td><a href="https://freebsdfoundation.org/blog/guest-blog-foundation-sponsors-freebsd-lldb-improvements/" title="https://freebsdfoundation.org/blog/guest-blog-foundation-sponsors-freebsd-lldb-improvements/">FreeBSD Foundation Blog</a></td><td>
-	    URL: <a href="https://freebsdfoundation.org/blog/guest-blog-foundation-sponsors-freebsd-lldb-improvements/" title="FreeBSD Foundation Blog">https://freebsdfoundation.org/blog/guest-blog-foundation-sponsors-freebsd-lldb-improvements/</a></td></tr><tr><td><a href="https://github.com/moritz-systems/llvm-project" title="https://github.com/moritz-systems/llvm-project">Git Repository</a></td><td>
-	    URL: <a href="https://github.com/moritz-systems/llvm-project" title="Git Repository">https://github.com/moritz-systems/llvm-project</a></td></tr></table><p>
-	Contact: Kamil Rytarowski &lt;<a href="mailto:kamil@moritz.systems">kamil@moritz.systems</a>&gt;
-	<br />
-	Contact: Micha&#322; G�rny &lt;<a href="mailto:mgorny@moritz.systems">mgorny@moritz.systems</a>&gt;
-	</p><p>The LLDB project builds on libraries provided by LLVM and Clang to provide a
-great modern debugger. It uses the Clang ASTs and the expression parser, LLVM
-JIT, LLVM disassembler, etc so that it provides an experience that &#8220;just
-works&#8221;. It is also blazing fast and more permissively licensed than GDB, the
-GNU Debugger.
-</p>
-<p>LLDB is the default debugger in Xcode on macOS and supports debugging C,
-Objective-C, and C++ on the desktop and iOS devices and the simulator.
-</p>
-<p>FreeBSD includes LLDB in the base system. At present, it has some limitations
-in comparison with the GNU GDB debugger, and does not yet provide a complete
-replacement. It used to rely on an obsolete plugin model in LLDB that was a
-growing technical debt. This project aimed to bring LLDB closer to a fully
-featured replacement for GDB, and therefore for FreeBSD to feature a modern
-debugger for software developers.
-</p>
-<p>The legacy monolithic target support executed the application being debugged in
-the same process space as the debugger. The modern LLDB plugin approach, used
-on other supported targets, executes the target process under a separate
-lldb-server process. This improves reliability and simplifies the process /
-thread model in LLDB itself. In addition, remote and local debugging is now
-performed using the same approach.
-</p>
-<p>After the migration to the new process model on 32 and 64-bit x86 CPUs, the
-project focused on reviewing the results of LLDB&#8217;s test suite and fixing tests
-as time permits.
-</p>
-<p>During the Moritz Systems work, the FreeBSD Project gained numerous important
-improvements: in the kernel, userland base libraries (the dynamic loader) and
-the LLVM toolchain FreeBSD support.
-</p>
-<p>The introduced changes are expected to be shipped with LLDB 12.0, and where
-applicable in FreeBSD 13.0.
-</p>
-<p>The overall experience of FreeBSD/LLDB developers and advanced users on this
-rock solid Operating System reached the state known from other environments.
-Furthermore, the FreeBSD-focused work also resulted in generic improvements,
-enhancing the LLDB support for Linux and NetBSD.
-</p>
-
-<p>Sponsor: The FreeBSD Foundation<br clear="none" />
-</p><hr /><h2><a name="Upstreaming-NetApp-Changes" href="#Upstreaming-NetApp-Changes" id="Upstreaming-NetApp-Changes">Upstreaming NetApp Changes</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://klarasystems.com/freebsd-development/" title="https://klarasystems.com/freebsd-development/">Klara Inc.</a></td><td>
-	    URL: <a href="https://klarasystems.com/freebsd-development/" title="Klara Inc.">https://klarasystems.com/freebsd-development/</a></td></tr></table><p>
-	Contact: Alexander Sideropoulos &lt;<a href="mailto:Alexander.Sideropoulos@netapp.com">Alexander.Sideropoulos@netapp.com</a>&gt;
-	<br />
-	Contact: Allan Jude &lt;<a href="mailto:allan@klarasystems.com">allan@klarasystems.com</a>&gt;
-	</p><p>NetApp has started an effort to upstream bug fixes and other improvements from
-the ONTAP code line into FreeBSD. These changes benefit the FreeBSD
-community by providing many fixes that NetApp has made over the past few years,
-while allowing NetApp to reduce the number of customizations needed when
-bringing in the latest FreeBSD changes back into the ONTAP tree.
-</p>
-<p>NetApp has partnered with Klara to facilitate this project, to help identify
-interesting and useful changes to send upstream, to rework and generalize those
-changes as required to make them suitable for upstreaming, and to shepherd them
-through the FreeBSD code review process.
-</p>
-<p>During the fourth quarter, Klara has made 40 upstream fixes in the FreeBSD
-kernel in various subsystems including geom, dev, amd64, net, kern, netinet, and
-several other areas of the tree on behalf of NetApp.
-</p>
-<p>NetApp intends to continue to sponsor this effort throughout 2021.
-</p>
-<p>Sponsor: NetApp
-</p><hr /><h2><a name="NFS-over-TLS-implementation" href="#NFS-over-TLS-implementation" id="NFS-over-TLS-implementation">NFS over TLS implementation</a></h2><p>
-	Contact: Rick Macklem &lt;<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>&gt;
-	</p><p>In an effort to improve NFS security, an Internet Draft titled
-"Towards Remote Procedure Call Encryption By Default" specifies
-use of TLS 1.3 to encrypt all data traffic on a Sun RPC
-connection used for NFS.
-</p>
-<p>Although NFS has been able to use sec=krb5p to encrypt data
-on the wire, this requires a Kerberos environment and, as
-such, has not been widely adopted.
-It also required that
-encryption/decryption be done in software, since only the
-RPC message NFS arguments are encrypted.
-Since Kernel TLS is capable of using hardware assist to
-improve performance and does not require Kerberos, NFS
-over TLS may be more widely adopted, once implementations
-are available.
-</p>
-<p>The coding for this project has now been completed.
-All required changes to the NFS and kernel RPC code have
-been committed to the head/current kernel and will be in FreeBSD13.
-The daemons can now be built from a port that depends
-upon the security/openssl-devel port of Openssl3 that
-includes patches for support of ktls.
-The port for the daemons is called sysutils/nfs-over-tls
-and should be committed to the ports framework soon.
-In the meantime, the port can easily be fetched,
-as described in
-<a href="https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt" shape="rect">https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt</a>.
-</p>
-<p>To support clients such as laptops, the daemons that perform the TLS
-handshake may optionally handle client X.509 certificates from a
-site local CA.
-There are now exports(5) options to require client(s) to
-provide a valid X.509 certificate.
-The case where a "user" name is stored in the certificate and is used
-to map all RPC credentials to that user is probably in violation of
-the Internet Draft.
-This is only enabled when the "-u" command line
-option is provided to rpc.tlsservd(8).
-</p>
-<p>The code is now available for testing. See:
-<a href="https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt" shape="rect">https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt</a>
-</p>
-<p>
-Setting up system(s) for testing still requires building a custom kernel
-with "options KERN_TLS" from recent head/FreeBSD13 sources plus installing
-the port for the daemons, as explained by the above document.
-</p>
-<p>The main limitation in the current implementation is that it uses TLS1.2
-and not TLS1.3, as required by the Internet Draft.
-This should change once the KERN_TLS rx patch includes TLS1.3 support.
-</p>
-<p>Third party testing would be appreciated.
-</p><hr /><h2><a name="OpenBSM-Synchronisation" href="#OpenBSM-Synchronisation" id="OpenBSM-Synchronisation">OpenBSM Synchronisation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.trustedbsd.org/openbsm.html" title="http://www.trustedbsd.org/openbsm.html">TrustedBSD / OpenBSM</a></td><td>
-	    URL: <a href="http://www.trustedbsd.org/openbsm.html" title="TrustedBSD / OpenBSM">http://www.trustedbsd.org/openbsm.html</a></td></tr><tr><td><a href="https://github.com/openbsm/openbsm" title="https://github.com/openbsm/openbsm">OpenBSM Github Sources</a></td><td>
-	    URL: <a href="https://github.com/openbsm/openbsm" title="OpenBSM Github Sources">https://github.com/openbsm/openbsm</a></td></tr><tr><td><a href="https://github.com/openbsm/openbsm/commit/54a0c07cf8bac71554130e8f6760ca68e5f36c7f" title="https://github.com/openbsm/openbsm/commit/54a0c07cf8bac71554130e8f6760ca68e5f36c7f">Synchronisation with macOS Catalina</a></td><td>
-	    URL: <a href="https://github.com/openbsm/openbsm/commit/54a0c07cf8bac71554130e8f6760ca68e5f36c7f" title="Synchronisation with macOS Catalina">https://github.com/openbsm/openbsm/commit/54a0c07cf8bac71554130e8f6760ca68e5f36c7f</a></td></tr><tr><td><a href="https://opensource.apple.com" title="https://opensource.apple.com">Apple OpenSource</a></td><td>
-	    URL: <a href="https://opensource.apple.com" title="Apple OpenSource">https://opensource.apple.com</a></td></tr></table><p>
-	Contact: Gordon Bergling &lt;<a href="mailto:gbe@FreeBSD.org">gbe@FreeBSD.org</a>&gt;
-	</p><p>OpenBSM is a crucial part of FreeBSD, which provides auditing features for
-the operating system. OpenBSM is incorporated into FreeBSD and macOS.
-Both Apple and FreeBSD have currently made changes to the OpenBSM framework,
-which weren't upstreamed. This small project aims to consolidate
-these changes and upstream them to the OpenBSM github repository, so that
-both development efforts can be merged to FreeBSD later on. The tricky part
-of this project is the manual comparison, since Apple doesn't provide any
-changelogs.
-</p>
-<p>I am currently working on the macOS Catalina sources and hopefully Apple
-will release the sources of macOS Big Sur in time for FreeBSD 13.
-</p><hr /><h2><a name="Tool-Chain" href="#Tool-Chain" id="Tool-Chain">Tool Chain</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://sourceforge.net/p/elftoolchain" title="https://sourceforge.net/p/elftoolchain">ELF Tool Chain homepage</a></td><td>
-	    URL: <a href="https://sourceforge.net/p/elftoolchain" title="ELF Tool Chain homepage">https://sourceforge.net/p/elftoolchain</a></td></tr></table><p>
-	Contact: Dimitry Andric &lt;<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ed Maste &lt;<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>&gt;
-	</p><p>In October Clang/LLVM was updated to 11.0.0, followed by a number of bug fixes
-from upstream, including improvements for a number of Tier-2 architectures.
-We also enabled the <code>-fstack-clash-protection</code> flag to enable compiler
-mitigation for the "stack clash" vulnerability and are coordinating with
-upstream.
-</p>
-<p>Upstream LLDB support for FreeBSD improved substantially over the last quarter,
-as detailed elsewhere in this report.  These improvements will make it into the
-FreeBSD base system early in 2021 when LLVM is next updated to 12.0.  As also
-mentioned elsewhere, we removed the obsolete copy of GDB 6.1.1.
-</p>
-<p>The ELF Tool Chain received a number of bug fixes, as well as support for
-<code>readelf -z</code> (handling compressed ELF debug sections) and an improvement
-to addr2line to report based on labels when other debug information is not
-available.  We are working to upstream these changes to the ELF Tool Chain
-project.
-</p>
-<p>There are a number of open issues and opportunities for improvements in various
-ELF Tool Chain components.  Contributions in these areas are very welcome,
-</p>
-<p>Sponsor: The FreeBSD Foundation (in part)
-</p><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
-      filesystems, and more.</p><br /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
-	    URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
-	Contact: Michal Krawczyk &lt;<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>&gt;
-	<br />
-	Contact: Artur Rojek &lt;<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>&gt;
-	<br />
-	Contact: Marcin Wojtas &lt;<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>&gt;
-	</p><p>ENA (Elastic Network Adapter) is the smart NIC available in the
-virtualized environment of Amazon Web Services (AWS). The ENA
-driver supports multiple transmit and receive queues and can handle
-up to 100 Gb/s of network traffic, depending on the instance type
-on which it is used.
-</p>
-<p>Completed since the last update:
-</p>
-<ul>
-<li><p>MFC of the ENA v2.3.0 driver to the FreeBSD 11-STABLE branch
-</p></li>
-<li><p>MFC of the ENA v2.3.0 driver to the upcoming FreeBSD 12-STABLE branch
-</p></li>
-<li><p>Add feature that allows reading extra ENI (Elastic Network Interface)
-    metrics about exceeding BW/pps limits
-</p></li>
-<li><p>Add SPDX license tag to the ENA driver files
-</p></li>
-<li><p>Add Rx offsets (hardware feature) support for the ENA driver
-</p></li>
-<li><p>Fix completion descriptors alignment for the ENA device - on some of
-    the platforms ENA needs alignment to 4k
-</p>
-</li></ul>
-Work in progress:
-
-<ul>
-<li><p>Introduce full kernel RSS API support.
-</p></li>
-<li><p>Allow reconfiguration of the RSS indirection table and hash key
-</p></li>
-<li><p>Prototype the driver port to the iflib framework
-</p>
-</li></ul>
-Sponsor: Amazon.com Inc
-<hr /><h2><a name="Intel-wireless-update" href="#Intel-wireless-update" id="Intel-wireless-update">Intel wireless update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless">The freebsd-wireless mailing list</a></td><td>
-	    URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="The freebsd-wireless mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-wireless</a></td></tr></table><p>
-	Contact: Bjoern A. Zeeb &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
-	</p><p>The Intel Wireless driver update project aims to bring support for
-newer chipsets and also get station side to 11ac in a first step.
-</p>
-<p>During the last months connection code between net80211 and the
-Linux driver KPI was implemented and scanning is working.
-Currently the focus is on sending and driving one state machine
-from the other and syncing state between net80211 and the
-Linux compat code.
-</p>
-<p>In addition the driver and firmware was updated from upstream sources
-to include support for the AX210 hardware generation, which was already
-tested to attach.
-</p>
-<p>The hope is that by the time the status report gets published
-authentication and association are working and basic data packet passing
-will work soon.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="Fenestras-X-random(4)" href="#Fenestras-X-random(4)" id="Fenestras-X-random(4)">Fenestras X random(4)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=366620" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=366620">SVN revision 1/3</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=366620" title="SVN revision 1/3">https://svnweb.freebsd.org/base?view=revision&amp;revision=366620</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=366621" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=366621">SVN revision 2/3</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=366621" title="SVN revision 2/3">https://svnweb.freebsd.org/base?view=revision&amp;revision=366621</a></td></tr><tr><td><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=366622" title="https://svnweb.freebsd.org/base?view=revision&amp;revision=366622">SVN revision 3/3</a></td><td>
-	    URL: <a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=366622" title="SVN revision 3/3">https://svnweb.freebsd.org/base?view=revision&amp;revision=366622</a></td></tr><tr><td><a href="https://aka.ms/win10rng" title="https://aka.ms/win10rng">FX Design (PDF)</a></td><td>
-	    URL: <a href="https://aka.ms/win10rng" title="FX Design (PDF)">https://aka.ms/win10rng</a></td></tr><tr><td><a href="https://www.schneier.com/academic/fortuna/" title="https://www.schneier.com/academic/fortuna/">Fortuna Design</a></td><td>
-	    URL: <a href="https://www.schneier.com/academic/fortuna/" title="Fortuna Design">https://www.schneier.com/academic/fortuna/</a></td></tr></table><p>
-	Contact: Conrad Meyer &lt;<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD CSPRNG group &lt;<a href="mailto:csprng@FreeBSD.org">csprng@FreeBSD.org</a>&gt;
-	</p><p>Since FreeBSD 11, the default <code>random(4)</code> implementation is based on the
-<i>Fortuna</i> (2003) design by Ferguson and Schneier.  At a high level, <i>Fortuna</i>
-accumulates entropy into a series of pools, and reseeds a single generator from
-some of these pools according to some criteria.
-</p>
-<p>In 2019, Ferguson (at Microsoft) published a whitepaper on the design of the
-<i>Windows 10</i> system random number generator.  <i>Fenestras X</i> is a <code>random(4)</code>
-implementation based on the published <i>Windows 10</i> design.
-</p>
-<p>The <i>Fenestras X</i> / <i>Windows 10</i> design is similar to <i>Fortuna</i>, so it is
-probably most interesting to describe their differences:
-</p>
-<ul>
-<li><p><i>Fenestras X</i> has per-CPU generators seeded from a root generator.
-    <i>Fortuna</i> only has the root generator.  This change eliminates lock
-    contention between <code>random(4)</code> readers running on multiple cores.
-</p></li>
-<li><p>Generators in <i>Fenestras X</i> form a tree from the root RNG.  When read,
-    generators efficiently check if their parent generator has been seeded with
-    newer entropy.  If so, child generators reseed themselves before serving
-    the read operation.  This is integrated with <code>arc4random(9)</code>, as well as
-    userspace <code>arc4random(3)</code>.
-</p></li>
-<li><p><i>Fenestras X</i> generators are buffered.  Requests smaller than some
-    arbitrary threshold (currently 128 bytes) are served from the buffer.
-    Bytes read from the buffer are securely erased when they are consumed.  The
-    buffer is refreshed if the request consumes more bytes than were available
-    in the buffer.  This amortizes the cost of rekeying and generating output
-    from a cryptographic CTR-mode cipher, which is especially slow with AES.
-</p>
-</li></ul>
-There are other important differences, and readers interested in system CSPRNGs
-<p>should read Ferguson's whitepaper.  It is short and accessible.  For more
-information on the FreeBSD implementation, please see the SVN commit messages
-&#8212; especially <code>r366620</code>.
-</p>
-<p>The <i>Fenestras X</i> implementation is available in <code>CURRENT</code>, but disabled by
-default.  (The default remains <i>Fortuna</i>.)  At this time, you must set the
-<code>RANDOM_FENESTRASX</code> option in your custom kernel configuration and rebuild your
-kernel to use the new design.  There are no known bugs or weaknesses relative
-to the <i>Fortuna</i> implementation.
-</p>
-<p>Future work and call to action:
-</p>
-<ul>
-<li><p>Additional design review, implementation review, and testing is welcome.
-</p></li>
-<li><p>Additional entropy sources: we could use implementations of some of the
-    sources described in the whitepaper, in both <i>Fortuna</i> and <i>Fenestras X</i>.
-    In particular, we're missing a jitter entropy source.
-</p></li></ul>
-<hr /><h2><a name="pf-performance-improvement" href="#pf-performance-improvement" id="pf-performance-improvement">pf performance improvement</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://cgit.freebsd.org/src/commit/?id=1c00efe98ed7d103b9684ff692ffd5e3b64d0237" title="https://cgit.freebsd.org/src/commit/?id=1c00efe98ed7d103b9684ff692ffd5e3b64d0237">First commit</a></td><td>
-	    URL: <a href="https://cgit.freebsd.org/src/commit/?id=1c00efe98ed7d103b9684ff692ffd5e3b64d0237" title="First commit">https://cgit.freebsd.org/src/commit/?id=1c00efe98ed7d103b9684ff692ffd5e3b64d0237</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27707" title="https://reviews.freebsd.org/D27707">D27707</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27707" title="D27707">https://reviews.freebsd.org/D27707</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27756" title="https://reviews.freebsd.org/D27756">D27756</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27756" title="D27756">https://reviews.freebsd.org/D27756</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27757" title="https://reviews.freebsd.org/D27757">D27757</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27757" title="D27757">https://reviews.freebsd.org/D27757</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27758" title="https://reviews.freebsd.org/D27758">D27758</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27758" title="D27758">https://reviews.freebsd.org/D27758</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27759" title="https://reviews.freebsd.org/D27759">D27759</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27759" title="D27759">https://reviews.freebsd.org/D27759</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27760" title="https://reviews.freebsd.org/D27760">D27760</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27760" title="D27760">https://reviews.freebsd.org/D27760</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27761" title="https://reviews.freebsd.org/D27761">D27761</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27761" title="D27761">https://reviews.freebsd.org/D27761</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27762" title="https://reviews.freebsd.org/D27762">D27762</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27762" title="D27762">https://reviews.freebsd.org/D27762</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27763" title="https://reviews.freebsd.org/D27763">D27763</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27763" title="D27763">https://reviews.freebsd.org/D27763</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D27764" title="https://reviews.freebsd.org/D27764">D27764</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27764" title="D27764">https://reviews.freebsd.org/D27764</a></td></tr></table><p>
-	Contact: Kristof Provost &lt;<a href="mailto:kp@freebsd.org">kp@freebsd.org</a>&gt;
-	</p><p>The performance of pf was not as good as it could be. Some investigation with the
-invaluable hwpmc tooling eventually pointed to very poor cache behaviour.
-The longest_lat_cache.miss event was very informative.
-</p>
-<p>This turned out to be due to pf doing packet and byte counting in states, rules and
-interfaces.
-</p>
-<p>The pf code took the very straightforward approach of having a simple uint64_t
-variable and incrementing it for every packet. The downside of this is that
-when multiple cores do it simultaneously the CPU ends up having to write this
-to memory very often, slowing packet processing down greatly. Happily the
-counter(9) framework is designed for this exact situation.
-</p>
-<p>One additional complication is that pf uses the same structure definitions for
-its internal data as it uses for configuration from user space. To avoid
-breaking user space these data structures have been decoupled. That is, where
-pf_rule used to be used both to set rules via the ioctl() interface and to
-evaluate rules while processing packets we now only use pf_rule for
-configuration. The new pf_krule structure is used when evaluating packets.
-This allows us to change the pf_krule structure, to change uint64_t to
-counter_u64_t, without affecting user space.
-</p>
-<p>Olivier Cochard-Labb� tested the full set of changes, and found (depending on
-hardware) <a href="http://dev.bsdrp.net/benchs/kp/pf-patches/" shape="rect">substantial improvements in throughput</a>.
-</p>
-<p>Sponsor: Orange Business Services
-</p><hr /><h2><a name="IP-Routing-lookup-improvements" href="#IP-Routing-lookup-improvements" id="IP-Routing-lookup-improvements">IP Routing lookup improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D27401" title="https://reviews.freebsd.org/D27401">Add modular routing lookup framework.</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D27401" title="Add modular routing lookup framework.">https://reviews.freebsd.org/D27401</a></td></tr></table><p>
-	Contact: Alexander Chernikov &lt;<a href="mailto:melifaro@FreeBSD.org">melifaro@FreeBSD.org</a>&gt;
-	</p><p>This work adds a fib lookup framework, allowing to attach custom IP lookup algorithms to any routing table on the fly. It allows to use more performant and efficient lookup algorithms, dynamically selected based on the number of routes in the routing table. Finally, it provides an implementation of modified DIR-24-8 for IPv4/IPv6, speeding IP lookups for the large-fib use case.
-</p>
-<p>This work is a part of a larger effort to modernise the routing subsystem.
-</p>
-<h3>Background</h3>
-
-<p>FreeBSD runs diverse workloads on both low-end and high-end devices, resulting in different networking/memory requirements for each case.
-Small boxes with a couple of routes are different from routers with full-view.
-IPv4 lookups are different from IPv6 ones.
-Conditions can change dynamically: one may easily reconfigure a system to receive full view instead of a default route.
-</p>
-<p>Currently, FreeBSD uses radix (compressed binary tree) to perform all unicast route manipulations, including routing lookups.
-Radix implementation requires storing key length in each item, allowing to use sockaddrs, transparently supporting virtually any address family.
-This flexibility comes at a cost: radix is <i>relatively slow</i>, <i>cache-unfriendly</i> and adds <i>locking</i> to the hot path.
-Finally, radix is closely coupled to the rest of the system, making it hard to switch to something else.
-</p>
-<h3>Implementation overview</h3>
-
-<h4>Overview</h4>
-
-<p>Modular fib IP lookup framework has been designed to address flexibility and performance requirements.
-</p>
-<p>It keeps system radix as the "control plane" source of truth, simplifying actual algorithms implementation.
-It allows dynamic load new algorithms as the kernel modules and abstracts most OS-specific details, reducing algorithm "glue" code.
-It automatically adapts to the current system state by picking the best matching algorithm for the routing table on-the-fly.
-</p>
-<p>The following algorithms are provided by default.
-</p>
-<p>IPv4:
-</p>
-<ul>
-<li><p>bsearch4 (lockless binary search in a specially-crafted IP array), tailored for small-fib (less than 16 routes)
-</p></li>
-<li><p>radix4_lockless (lockless immutable radix, re-created on every routing table change), tailored for small-fib (less than 1000 routes)
-</p></li>
-<li><p>radix4 (base system radix backend)
-</p></li>
-<li><p>dpdk_lpm4 (DPDK DIR24-8-based lookups), lockless datastructure optimised for large-fib ( <a href="https://reviews.freebsd.org/D27412" shape="rect">D27412</a> )
-</p>
-</li></ul>
-IPv6:
-
-<ul>
-<li><p>radix6_lockless: lockless immutable radix, re-created on every routing table change, tailored for small-fib (less than 1000 routes)
-</p></li>
-<li><p>radix6: wrapper around existing system radix
-</p></li>
-<li><p>dpdk_lpm6: DPDK DIR24-8-based lookups, lockless datastructure optimised for large-fib ( <a href="https://reviews.freebsd.org/D27412" shape="rect">D27412</a> )
-</p>
-</li></ul>
-<h4>Performance changes</h4>
-
-<p>Micro benchmarks (i7-7660U, single-core lookups, 2048 destinations, benchmark code in <a href="https://reviews.freebsd.org/D27604" shape="rect">D27604</a>).
-</p>
-<p>IPv4:
-</p>
-<ul>
-<li><p>8 routes: radix4: ~20mpps, radix4_lockless: ~25mpps, bsearch4: ~69mpps, dpdk_lpm4: ~67 mpps
-</p></li>
-<li><p>700k routes: radix4_lockless: 3.3mpps, dpdk_lpm4: 46mpps
-</p>
-</li></ul>
-IPv6:
-
-<ul>
-<li><p>8 routes: radix6_lockless: ~20mpps, dpdk_lpm6: ~70mpps
-</p></li>
-<li><p>100k routes: radix6_lockless: ~14mpps, dpdk_lpm6: ~57mpps
-</p>
-</li></ul>
-Forwarding performance:
-
-<ul>
-<li><p>+10-15% IPv4: small-fib, bsearch4
-</p></li>
-<li><p>+25% IPv4: full-view, dpdk_lpm4
-</p></li>
-<li><p>+20% IPv6: full-view, dpdk_lpm6
-</p>
-</li></ul>
-<h3>Status</h3>
-
-<ul>
-<li><p>Modular longest-prefix-match lookup algorithms (<a href="https://reviews.freebsd.org/D27401" shape="rect">D27401</a>) [ DONE ]
-</p><ul>
-<li><p>Design control plane framework for attaching algorithms [ DONE ]
-</p></li>
-<li><p>Port DPDK IPv6 lockless lookup algorithm ( <a href="https://reviews.freebsd.org/D27412" shape="rect">D27412</a>) [ DONE ]
-</p></li>
-<li><p>Port DPDK IPv4 lockless lookup algorithm ( <a href="https://reviews.freebsd.org/D27412" shape="rect">D27412</a>) [ DONE ]
-</p></li></ul>
-</li></ul>
-<hr /><h2><a name="Scalable-routing-multipath-support" href="#Scalable-routing-multipath-support" id="Scalable-routing-multipath-support">Scalable routing multipath support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7" title="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7">Implementation of scalable multipath</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7" title="Implementation of scalable multipath">https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7</a></td></tr><tr><td><a href="https://reviews.freebsd.org/D26449" title="https://reviews.freebsd.org/D26449">Introduce scalable route multipath</a></td><td>
-	    URL: <a href="https://reviews.freebsd.org/D26449" title="Introduce scalable route multipath">https://reviews.freebsd.org/D26449</a></td></tr></table><p>
-	Contact: Alexander Chernikov &lt;<a href="mailto:melifaro@FreeBSD.org">melifaro@FreeBSD.org</a>&gt;
-	</p><p>This work targets implementing scalable routing multipath support and enabling it by default.
-It closes the long-standing feature gap with other modern networking OSes.
-</p>
-<p>This work is a part of on-going efforts to modernize the routing subsystem.
-</p>
-<h3>Background</h3>
-
-<p>Initial FreeBSD multipath implementation, <code>RADIX_MPATH</code>,
-was added back in <a href="https://github.com/freebsd/freebsd-legacy/commit/4e8901ea7a04d2d803067647c0641e41494b8868" shape="rect">2008</a>.
-It was based on the radix changes and represented multipath routes as
-a linked-list of chained paths. It was not fully finished and tested,
-resulting in many crash reports.
-</p>
-<h3>Implementation overview</h3>
-
-<p>Multipath-related change changes are based on the introduction of the concept of next hops. Nexthops are separate data structures, containing the necessary information to perform packet forwarding. They are shared among the routes, providing more pre-computed cache-efficient data while requiring less memory.
-Interested readers can find a more detailed description in <a href="https://reviews.freebsd.org/D24141" shape="rect">D24141</a>. They can find another overview in Nexthop objects <a href="https://linuxplumbersconf.org/event/4/contributions/434/attachments/251/436/nexthop-objects-talk.pdf" shape="rect">talk</a> describing Linux kernel implementation.
-</p>
-<p>Multipath implementation extends the nexthop concept further by introducing nexthop groups. Nexthop group is simply an array of nexthops, compiled according to each nexthop relative weight.
-</p>
-<p>Each route has a pointer to either nexthops or a nexthop group, decoupling lookup algorithm from the routing stack internals. Both nexthops and nexthop groups are immutable and use epoch(9)-backed reclamation.
-</p>
-<h3>Status</h3>
-
-<ul>
-<li><p>Nexthop objects (<a href="https://reviews.freebsd.org/D24232" shape="rect">D24232</a>) [ DONE ]
-</p><ul>
-<li><p>Introduction of nexthop objects [ DONE ]
-</p></li>
-<li><p>Conversion of old KPI users to the new one [ DONE ]
-</p><ul>
-<li><p>Conversion of route caching to nexthop caching [ DONE ]
-</p></li></ul>
-</li><li><p>Conversion of struct <code>rtentry</code> field access to nhop field access [ DONE ]
-</p></li>
-<li><p>Eliminating old lookup KPI and hiding struct rtentry [ DONE ]
-</p>
-</li></ul>
-</li><li><p>Multipath routing (<a href="https://reviews.freebsd.org/D26449" shape="rect">D26449</a>) [ DONE ]
-</p><ul>
-<li><p>Switch control plane customers to use (rtentry, nexthop) pairs instead of rtentry to allow multipath changes happen transparently [ DONE ]
-</p></li>
-<li><p>Introduce nexthop group objects [ DONE ]
-</p></li>
-<li><p>Add multipath support for the rib (routing information base) manipulation functions [ DONE ]
-</p></li>
-<li><p>Add flowid generation for outbound traffic to enable load balancing [ DONE ]
-</p>
-</li></ul>
-</li><li><p>Routing daemon support
-</p><ul>
-<li><p>Add net/bird support for multipath routing [ NOT STARTED ]
-</p></li>
-<li><p>Add explicit nexthop/nexthop groups control via rtsock [ IN PROGRESS ]
-</p></li>
-<li><p>Work with FRR developers to add nexthop-based route control [ NOT STARTED ]
-</p></li></ul>
-</li></ul>
-<hr /><h2><a name="Thunderbolt3/USB4-stack" href="#Thunderbolt3/USB4-stack" id="Thunderbolt3/USB4-stack">Thunderbolt3/USB4 stack</a></h2><p>
-	Contact: Scott Long &lt;<a href="mailto:scottl@freebsd.org">scottl@freebsd.org</a>&gt;
-	</p><p>This project implements a driver stack for Thunderbolt3 and USB4.  These
-technologies differ radically from USB3 and prior, and require completely new
-drivers for the host interface adapter and topology as well as configuration
-management layers.  At their most fundamental level, a TBT3/USB4 topology
-appears as PCI bridges and buses, and attached devices appear as either PCI
-devices, USB3 devices, or DisplayPort devices.  Early TBT3 controllers don't
-even appear in the system topology unless a TBT3 device is plugged in.  These
-early TBT3 systems also implement a security policy meant to protect against
-unauthorised or malicious devices, though that scheme has been proven to not
-be effective and has been removed from later TBT3 and USB4 implementations.
-Besides security control, the TBT3/USB4 stack controls power management and
-topology hotplug.
-</p>
-<p>The FreeBSD driver currently supports Alpine Ridge and Ice Lake TBT3
-controllers, and can perform basic security validation and topology awareness.
-USB4 support as well as full connection manager and power management support is
-still being worked on.  The current driver will be committed to FreeBSD in
-early January 2021.
-</p>
-<p>Though this work is not sponsored, it has been done with the encouragement and
-support of the FreeBSD Foundation and Netgate.
-</p><hr /><h2><a name="Vectored-AIO" href="#Vectored-AIO" id="Vectored-AIO">Vectored AIO</a></h2><p>
-	Contact: Alan Somers &lt;<a href="mailto:asomers@FreeBSD.org">asomers@FreeBSD.org</a>&gt;
-	</p><p>POSIX AIO is a facility for asynchronous I/O to files and devices.  FreeBSD's
-implementation is efficient, especially when writing to disk files.  But a
-long-standing defect in the standard API is a lack of vectored functions.  That
-is, there is no asynchronous equivalent of <code>pwritev(2)</code> and <code>preadv(2)</code>.  A
-common workaround is to use <code>lio_listio(2)</code> instead.  However, that has several
-drawbacks.  It's more effort for the programmer, it might return early with
-only a subset of the operations completed, it requires more total syscalls, and
-there is no guarantee that the operations will complete in-order.
-</p>
-<p>This quarter I added two new syscalls: <code>aio_writev(2)</code> and <code>aio_readv(2)</code>.
-They work just like their non-vectored counterparts, but they take an array of
-<code>iovec</code> elements, just like <code>pwritev</code> and <code>preadv</code>.  You can't use them in
-combination with <code>lio_listio</code>, but that could be added in the future.
-</p><hr /><h2><a name="ZSTD-Compression-in-ZFS" href="#ZSTD-Compression-in-ZFS" id="ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></h2><p>
-	Contact: Allan Jude &lt;<a href="mailto:allanjude@freebsd.org">allanjude@freebsd.org</a>&gt;
-	</p><p>Zstandard (ZSTD) is a modern high-performance compression
-algorithm designed to provide the compression ratios of gzip
-while offering much better performance. ZSTD has been adopted
-in FreeBSD for a number of other uses, including compressing
-kernel crash dumps, as a replacement for gzip or bzip for
-compressing log files, and for future versions of pkg(8).
-</p>
-<p>This effort to complete the integration of ZSTD into ZFS is
-funded by the FreeBSD Foundation.
-</p>
-<p>During the four quarter the final tasks in the project to integrate
-ZSTD into OpenZFS were completed.
-</p>
-<p>Completed milestones in this project:
-</p>
-<ul>
-<li><p>Integrated ZSTD in the FreeBSD boot loader (Warner Losh <a href="mailto:imp@freebsd.org" shape="rect">imp@freebsd.org</a>)
-</p></li>
-<li><p>Added a section to the FreeBSD Handbook ZFS chapter explaining ZSTD
-</p></li>
-<li><p>Wrote a FreeBSD Journal Article explaining considerations when selecting a suitable compression level
-</p></li>
-<li><p>Monitored for bug reports after the changes were integrated into -CURRENT
-</p>
-</li></ul>
-With all of these changes in place, it is now possible to boot from pools
-<p>compressed with zstd or zstd-fast. For comparison, a standard installation of
-FreeBSD 13 (without debug symbols) uncompressed is 1175 MB, and when compressed
-with LZ4, is only 570 MB (2.15x) but when compressed with ZSTD's default level
-of 3 is only 417 MB (3.00x), and with the maximum level, 19,
-only 374 MB (3.36x).
-</p>
-<p>Sponsor: The FreeBSD Foundation<br clear="none" />
-</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
-      for new hardware platforms.</p><br /><h2><a name="arm64-platform-updates" href="#arm64-platform-updates" id="arm64-platform-updates">arm64 platform updates</a></h2><p>
-	Contact: Mitchell Horne &lt;<a href="mailto:mhorne@FreeBSD.org">mhorne@FreeBSD.org</a>&gt;
-	</p><p>In the interest of seeing the arm64 architecture promoted to Tier-1 status, an
-effort was undertaken to test building and serving of release and patch-level
-updates via <code>freebsd-update(1)</code>. The conclusion of this investigation is that
-the process works with very few changes required; a small tweak is needed for
-the update build scripts, and a minor bugfix in the <code>bsdiff(1)</code> utility was
-committed. The hope is that the project can begin providing security updates for
-the platform with the release of FreeBSD 13.0, removing the requirement that
-users compile these updates from source.
-</p>
-<p>Added this quarter was arm64 support for the new <code>ossl(4)</code> crypto driver. This
-driver provides acceleration of SHA-1 and SHA-2 cryptographic operations by
-leveraging OpenSSL's assembly routines. These routines will detect and use
-optimized instructions, as supported by the CPU. This support benefits userland
-applications via the <code>cryptodev(4)</code> device, and in-kernel consumers of the
-<code>crypto(9)</code> interface, such as the IPSec Authentication Header protocol and
-kernel TLS.
-</p>
-<p>Finally, work was done to add the necessary machine-dependent bits for the
-kernel's <code>gdb(4)</code> interface. This enables remote debugging of the kernel with
-<code>gdb(1)</code> over a serial line.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="FreeBSD/RISC-V-Project" href="#FreeBSD/RISC-V-Project" id="FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/riscv" title="https://wiki.freebsd.org/riscv">Wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/riscv" title="Wiki">https://wiki.freebsd.org/riscv</a></td></tr></table><p>
-	Contact: Mitchell Horne &lt;<a href="mailto:mhorne@FreeBSD.org">mhorne@FreeBSD.org</a>&gt;
-	</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-riscv" shape="rect">freebsd-riscv Mailing List</a><br clear="none" />
-Contact: IRC #freebsd-riscv on freenode<br clear="none" />
-</p>
-<p>The FreeBSD/RISC-V project is providing support for running FreeBSD on the
-<a href="https://riscv.org/" shape="rect">RISC-V Instruction Set Architecture</a>.
-</p>
-<p>This quarter saw a number of improvements and bugfixes from committers and
-contributors alike. A few small items from this quarter:
-</p>
-<ul>
-<li><p>Added riscv64 LINT kernel config plus CI job (<code>FreeBSD-head-riscv64-LINT</code>)
-</p></li>
-<li><p>Switched <code>emulators/riscv-isa-sim</code> to official upstream and updated to
-    2020-11-02 snapshot
-</p></li>
-<li><p>Created <code>sysutils/u-boot-sifive-fu540</code>, a u-boot port for the HiFive
-    Unleashed
-</p></li>
-<li><p>Improved SBI extension support
-</p>
-</li></ul>
-Further progress was made this quarter in building ports for RISC-V. Build and
-<p>runtime issues with large dependencies <code>devel/python-setuptools</code> and
-<code>devel/glib20</code> were fixed, enabling several thousand skipped ports. There is
-some in-progress work to address failures in other significant ports, such as
-<code>devel/nspr</code> and <code>databases/sqlite3</code>. By addressing some of these small-effort
-issues, some 15000+ ports can now be built for the platform with
-qemu-user-static.
-</p>
-<p>Finally, December saw the arrival of the first <code>riscv64</code> weekly development
-snapshots. This includes the usual memstick installer, a virtual machine image,
-and a generic SD card image. There are still some minor tweaks to be made, but
-this marks a significant step forward for the platform, and lowers the barrier
-of entry for running a FreeBSD/RISC-V system. This also means that FreeBSD 13
-will likely be the first downloadable release for the architecture. For those
-interested in trying out the VM image for themselves, see <url href="https://wiki.freebsd.org/riscv#Quick_Start">the Quick Start instructions</url>
-on the wiki.
-</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><h2><a name="Dual-stack-ping-command" href="#Dual-stack-ping-command" id="Dual-stack-ping-command">Dual-stack ping command</a></h2><p>
-	Contact: Alan Somers &lt;<a href="mailto:asomers@FreeBSD.org">asomers@FreeBSD.org</a>&gt;
-	</p><p>The venerable ping command has until now only supported IPv4.  A separate
-utility, ping6, was originally written by WIDE as a research tool to develop
-IPv6.  As a research tool, it didn't need IPv4 support, but since then, it's
-been put to practical use by countless developers and sysadmins everywhere.
-</p>
-<p>The ping/ping6 split has been a perennial complaint.  It's annoying that two
-separate commands are needed, even though they do almost exactly the same
-thing.  This quarter, I merged J�n Su&#269;an's GSoC work, which merged the two
-commands.  Now ping can handle either protocol, based on the -4 and -6
-switches, or based on the format of the target.  A ping6 hard link is provided
-for backwards compatibility.
-</p>
-<p>Sponsor: Google Summer of Code<br clear="none" />
-</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
-      changes that touch most of the tree, or individual ports
-      themselves.</p><br /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
-	    URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://community.kde.org/FreeBSD" title="https://community.kde.org/FreeBSD">KDE Community FreeBSD</a></td><td>
-	    URL: <a href="https://community.kde.org/FreeBSD" title="KDE Community FreeBSD">https://community.kde.org/FreeBSD</a></td></tr></table><p>
-	Contact: Adriaan de Groot &lt;<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>&gt;
-	</p><p>The KDE on FreeBSD project aims to package all of the software
-produced by the KDE Community for the FreeBSD ports tree.
-The software includes a full desktop environment called KDE Plasma,
-graphics applications, instant-messengers, a video-editing suite,
-as well as a tea timer
-and hundreds of other applications that can be used on
-any FreeBSD machine.
-</p>
-<p>The KDE team (kde@) is part of desktop@ and x11@ as well,
-building the software stack to make FreeBSD beautiful and usable
-as a daily-driver graphics-based desktop machine.
-</p>
-<p>This quarter the kde@ team:
-</p>
-<ul>
-<li><p>Landed the October, November and December updates to KDE Applications
-and to KDE Plasma
-</p></li>
-<li><p>Landed all of the bi-weekly KDE Frameworks releases
-</p></li>
-<li><p>Updated Qt to 5.12.2, including Qt5 WebEngine
-</p></li>
-<li><p>Followed up with two cmake patch releases
-</p></li>
-<li><p>Followed up one ninja patch release
-</p>
-</li></ul>
-There was lots of infrastructural work and individual application
-<p>updates and a new Matrix client from the KDE community
-as well, which we typically fail to administer and write about
-so this report is fairly short with mostly big-ticket items.
-We had fun, we chased the things that are most useful to
-us, and got through the year. Here's to next year with
-actually seeing FreeBSD people again.
-</p>
-<p>I (adridg@) would like to especially thank Kai Knoblich (kai@) for chasing WebEngine:
-that's a huge and painful codebase to deal with, and here we
-are, all up-to-date.
-</p><hr /><h2><a name="FreeBSD-Office-team" href="#FreeBSD-Office-team" id="FreeBSD-Office-team">FreeBSD Office team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Office" title="https://wiki.freebsd.org/Office">The FreeBSD Office project</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/Office" title="The FreeBSD Office project">https://wiki.freebsd.org/Office</a></td></tr></table><p>
-	Contact: FreeBSD Office team ML &lt;<a href="mailto:office@FreeBSD.org">office@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Dima Panov &lt;<a href="mailto:fluffy@FreeBSD.org">fluffy@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Li-Wen Hsu &lt;<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Office team works on a number of office-related software suites
-and tools such as OpenOffice and LibreOffice.<br clear="none" />
-</p>
-<p>Work during this quarter focused on providing the latest stable release of
-LibreOffice suite and companion apps to all FreeBSD users.
-</p>
-<p>Latest and quarterly ports branches got a series of updates of the LibreOffice suite
-from 7.0.1 thru 7.0.4 releases, compilation patches for all Tier 1 architectures,
-and updates of all companion libraries. Some of our local and critical to build patches
-were sent to and accepted by upstream.
-</p>
-<p>Meanwhile, our WIP repository was moved to new home under official github.org/freebsd resources.
-</p>
-<p>The WIP repository also has a major update with development versions of the LibreOffice suite,
-version 7.1.0.0.beta1 for now. Release will be planned in March, 2021.
-</p>
-<p>We are looking for people to help the project.
-All unstable work with LibreOffice snapshots is staged in our <a href="https://github.com/freebsd/freebsd-ports-libreoffice" shape="rect">WIP repository</a>.<br clear="none" />
-The <a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&amp;email1=office%40FreeBSD.org&amp;emailassigned_to1=1&amp;emailcc1=1&amp;emailreporter1=1&amp;emailtype1=substring&amp;query_format=advanced&amp;list_id=374316" shape="rect">open bugs list</a>
-contains all filed issues which need some attention.
-Patches, comments and objections are always welcome in the mailing list and bugzilla.
-</p>
-<hr /><h2><a name="Ports-On-Non-x86-Architectures" href="#Ports-On-Non-x86-Architectures" id="Ports-On-Non-x86-Architectures">Ports On Non-x86 Architectures</a></h2><p>
-	Contact: Mark Linimon &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
-	</p><p>It has been some time since the last report on the status of FreeBSD
-ports on non-x86 architectures.
-</p>
-<p>Traditionally, we have referred to these as "tier-2 architectures".
-However, aarch64 and powerpc64 have aspirations for tier-1.  Also,
-although riscv64 is currently tier-3, it has aspirations for tier-2.
-</p>
-<ul>
-<li><p>The big news is that, thanks to the FreeBSD Foundation (and the
-    assistance of Philip Paeps), FreeBSD now has two new aarch64 boxes,
-    which have replaced the previous, badly-aging, alternatives.  For
-    the first time since August, we once again have up-to-date aarch64
-    packages.
-</p></li>
-<li><p>Thanks to the above, and the work of Emmanuel Vadot and others, some
-    bitrot in aarch64 ports has been reversed.
-</p></li>
-<li><p>Piotr Kubaj (pkubaj@) continues QA on powerpc64 (big-endian) ports.
-    Almost everything that is buildable now does so.  The Linux ports and
-    some of the graphics drivers are excluded.  Otherwise, powerpc64 is
-    up to parity with amd64.
-</p></li>
-<li><p>Piotr has also begun the task of bringing powerpc64le (little-endian)
-    up to parity with powerpc64.  Although several of the powerpc64 src
-    committers (and your author) have a fondness for big-endian, the fact
-    is that our most feasible path to getting graphics capability anywhere
-    near parity with x86 is via the little-endian choice.
-</p></li>
-<li><p>Mark Linimon (linimon@) has begun his own test-builds of ports on
-    riscv64 just to ascertain overall buildability.  Surprisingly, many
-    ports do indeed build.  Thanks to contributions from several people
-    already working on riscv64, including John Baldwin (jhb@) with an LLVM
-    fix, we are now able to build around 20,000 packages.  NB: these packages
-    are <i>unofficial</i> and not guaranteed.
-</p></li>
-<li><p>The work of Kyle Evans (kevans@) on chasing bitrot in qemu has been key
-    to work on both aarch64 and riscv64.  All users are encouraged to
-    update to the latest version.
-</p></li>
-<li><p>Unfortunately mips/mips64 are badly in need of work.  The fact that
-    devel/libffi does not build on mips64 blocks nearly half the ports
-    tree.
-</p>
-</li></ul>
-Tasklist:
-
-<ul>
-<li><p>We need users of riscv64 to actually test the packages that have been
-    built (so far, they have only been tested for buildability).  Contact
-    linimon@ if you are interested.
-</p>
-</li>
-<li><p>If anyone is still using mips/mips64 for other than the most trivial
-    tasks, we would welcome patches.
-</p></li></ul>
-<hr /><h2><a name="Python-2.7-removal-from-Ports" href="#Python-2.7-removal-from-Ports" id="Python-2.7-removal-from-Ports">Python 2.7 removal from Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
-	    URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
-	    URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249337" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249337">[meta] Ports broken by Python 2.7 End-of-Life and removal</a></td><td>
-	    URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249337" title="[meta] Ports broken by Python 2.7 End-of-Life and removal">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249337</a></td></tr></table><p>
-	Contact: Ren� Ladan &lt;<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>&gt;
-	<br />
-	Contact: FreeBSD Ports Management Team &lt;<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>&gt;
-	</p><p>As of January 2020, Python 2.7 reached its end-of-life after several years of extensions.
-Portmgr subsequently started the project of phasing Python 2.7 out of the Ports Tree by tagging lang/python27 for expiration on 2020-12-31.
-Last year, some 740 ports were removed from the Ports Tree as they were incompatible with Python 3, mostly because these ports were either unmaintained or abandoned upstream.
-</p>
-<p>During this process, there were several instances of an upstream still being active but where the upstream have not had the resources yet to upgrade their software to Python 3.
-A noticeable example of this is www/chromium and derived software, such as devel/electron7 and www/qt5-webengine.
-Portmgr is currently looking into ideas on how to minimize the impact of Python 2.7 on the Ports Tree while keeping Chromium and KDE 5 functional.
-As various software packages on the FreeBSD cluster itself also use Python 2.7, portmgr started coordinating with affected parties on upgrade plans.
-Currently there are 40 ports left that directly depend on Python 2.7 to build or run, and an unknown number of indirect ports.
-All those ports should eventually be upgraded to Python 3 or be removed too, ideally some time this year.
-</p>
-<p>Portmgr is currently cleaning up (unused) Python 2.7 code from ports which do not need Python 2.7.
-New ports should not be using Python 2.7 anymore, i.e. they should not have USES=python but instead something like USES=python:3.6+.
-</p>
-<p>So while this all looks rather invasive, it is not feasible to keep Python 2.7 around for much longer.
-Over time security vulnerabilities might show up which will likely no longer be fixed, because the Python Software Foundation no longer supports Python 2.7.
-Other problems are that the software gets outdated over time and thereby loses its usefulness as part of a development kit.
-</p>
-<p>Help needed:
-</p>
-<ul>
-<li><p>Coordinate with postmaster on isolating or migrating away from mail/mailman
-</p></li>
-<li><p>Coordinate with clusteradm (?) for upgrading svnweb and our wiki
-</p></li></ul>
-<hr /><h2><a name="Xfce-on-FreeBSD" href="#Xfce-on-FreeBSD" id="Xfce-on-FreeBSD">Xfce on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://xfce.org/about/news/?post=1608595200" title="https://xfce.org/about/news/?post=1608595200">Xfce 4.16 Upstream Release Announcement</a></td><td>
-	    URL: <a href="https://xfce.org/about/news/?post=1608595200" title="Xfce 4.16 Upstream Release Announcement">https://xfce.org/about/news/?post=1608595200</a></td></tr><tr><td><a href="https://www.freshports.org/x11-wm/xfce4" title="https://www.freshports.org/x11-wm/xfce4">Xfce meta-port on FreshPorts</a></td><td>
-	    URL: <a href="https://www.freshports.org/x11-wm/xfce4" title="Xfce meta-port on FreshPorts">https://www.freshports.org/x11-wm/xfce4</a></td></tr></table><p>
-	Contact: Xfce team &lt;<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Guido Falsi &lt;<a href="mailto:madpilot@FreeBSD.org">madpilot@FreeBSD.org</a>&gt;
-	</p><p>The FreeBSD Xfce team (xfce@) work to ensure the Xfce desktop environment
-is maintained and fully functional on FreeBSD.
-</p>
-<p>This quarter the Xfce team are pleased to welcome Xfce 4.16
-to the FreeBSD ports tree!
-</p>
-<p>Some of the highlights of this Xfce 4.16 release:
-</p>
-<ul>
-<li><p>The panel now supports dark mode (enabled by default) and an animated autohide transition
-</p></li>
-<li><p>A new panel plugin dubbed "statustray" which combines both StatusNotifier and legacy Systray items
-</p></li>
-<li><p>Fractional scaling support was added to the display dialog (helpful on HiDPI displays)
-</p></li>
-<li><p>A new tab in the "About Xfce" dialog shows basic system information like CPU or GPU type
-</p></li>
-<li><p>The settings manager has improved search and filter capabilities
-</p></li>
-<li><p>All settings dialogs now use window decorations drawn by Gtk (client side decorations)
-</p></li>
-<li><p>The "Mime Settings" and "Preferred Applications" dialogs were merged into the "Default Applications" dialog
-</p></li>
-<li><p>The Thunar file manager now supports pause for copy/move operations, and queued file transfer
-</p></li>
-<li><p>Generating thumbnails for .epub (e-book format) was added to tumbler
-</p></li>
-<li><p>A new default wallpaper and icon theme
-</p></li>
-<li><p>The application finder now allows for sorting applications by "frecency" - a combination of frequency and recency
-</p></li>
-<li><p>Dropped GTK2 support from all components and plugins
-</p>
-</li></ul>
-For further details, refer to the <a href="https://xfce.org/about/news/?post=1608595200" shape="rect">Xfce 4.16 upstream release announcement</a>.
-
-<p>Due to GTK2 and libxfce4gui support being removed, some panel plugins
-and libraries will be removed since they no longer work with Xfce 4.16:
-</p>
-<ul>
-<li><p>deskutils/orage
-</p></li>
-<li><p>deskutils/xfce4-volumed
-</p></li>
-<li><p>print/xfce4-print
-</p></li>
-<li><p>science/xfce4-equake-plugin
-</p></li>
-<li><p>x11/xfce4-embed-plugin
-</p></li>
-<li><p>x11/xfce4-quicklauncher-plugin
-</p></li>
-<li><p>x11/xfce4-wmdock-plugin
-</p></li>
-<li><p>x11-toolkits/libxfce4gui
-</p>
-</li></ul>
-
-<p>WARNING: Unfortunately this update can reveal a bug in pkg which can
-cause files from the libexo package to be absent after upgrade.
-To avoid the issue, upgrade the libexo package by itself before
-the rest of the packages, as described in UPDATING entry 20210102.
-</p>
-<p>Thanks also to riggs@, Olivier Duchateau <a href="mailto:duchateau.olivier@gmail.com" shape="rect">duchateau.olivier@gmail.com</a>,
-woodsb02@, Sergey Dyatko <a href="mailto:sergey.dyatko@gmail.com" shape="rect">sergey.dyatko@gmail.com</a>, and ehaupt@ for their help and
-contributions.
-</p><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree, in manpages, or in
-      external books/documents.</p><br /><h2><a name="FreeBSD-Translations-on-Weblate" href="#FreeBSD-Translations-on-Weblate" id="FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="https://wiki.freebsd.org/DocTranslationOnWeblate">Translate FreeBSD on Weblate wiki</a></td><td>
-	    URL: <a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="Translate FreeBSD on Weblate wiki">https://wiki.freebsd.org/DocTranslationOnWeblate</a></td></tr><tr><td><a href="https://translate-dev.freebsd.org/" title="https://translate-dev.freebsd.org/">FreeBSD Weblate Instance</a></td><td>
-	    URL: <a href="https://translate-dev.freebsd.org/" title="FreeBSD Weblate Instance">https://translate-dev.freebsd.org/</a></td></tr></table><p>
-	Contact: Danilo G. Baio &lt;<a href="mailto:dbaio@FreeBSD.org">dbaio@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Edson Brandi &lt;<a href="mailto:ebrandi@FreeBSD.org">ebrandi@FreeBSD.org</a>&gt;
-	</p><p>In search of new contributors an article was published in the
-September/October 2020 issue of the FreeBSD Journal about How to Become a
-FreeBSD Translator.
-</p>
-<p>During the whole year we received new contributors to the effort; numbers are
-still growing and we are receiving translations almost daily on our Weblate
-platform.
-</p>
-<h3>Q4 2020 Status</h3>
-
-<ul>
-<li><p>11 languages (1 new language)
-</p></li>
-<li><p>116 registered users (69 new users since 2020q1)
-</p>
-</li></ul>
-<h4>Languages</h4>
-
-<ul>
-<li><p>Chinese (Simplified) (zh_CN)
-</p></li>
-<li><p>Chinese (Traditional) (zh_TW)
-</p></li>
-<li><p>Dutch (nl_NL) - Added
-</p></li>
-<li><p>French (fr_FR)
-</p></li>
-<li><p>German (de_DE)
-</p></li>
-<li><p>Italian (it_IT)
-</p></li>
-<li><p>Norwegian (nb_NO)
-</p></li>
-<li><p>Persian (fa_IR)
-</p></li>
-<li><p>Portuguese (pt_BR)
-</p></li>
-<li><p>Spanish (es_ES)
-</p></li>
-<li><p>Turkish (tr-TR)
-</p>
-</li></ul>
-We want to thank everyone that contributed, translating or reviewing documents.
-
-<p>And please, help promote this effort on your local user group, we always need
-more volunteers.
-</p><hr /><h2><a name="DOCNG-on-FreeBSD" href="#DOCNG-on-FreeBSD" id="DOCNG-on-FreeBSD">DOCNG on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/carlavilla/freebsd-hugo-website" title="https://gitlab.com/carlavilla/freebsd-hugo-website">DOCNG Website Repo</a></td><td>
-	    URL: <a href="https://gitlab.com/carlavilla/freebsd-hugo-website" title="DOCNG Website Repo">https://gitlab.com/carlavilla/freebsd-hugo-website</a></td></tr><tr><td><a href="https://gitlab.com/carlavilla/freebsd-hugo-documentation" title="https://gitlab.com/carlavilla/freebsd-hugo-documentation">DOCNG Documentation Repo</a></td><td>
-	    URL: <a href="https://gitlab.com/carlavilla/freebsd-hugo-documentation" title="DOCNG Documentation Repo">https://gitlab.com/carlavilla/freebsd-hugo-documentation</a></td></tr><tr><td><a href="https://gitlab.com/carlavilla/freebsd-hugo-data" title="https://gitlab.com/carlavilla/freebsd-hugo-data">DOCNG Share Repo</a></td><td>
-	    URL: <a href="https://gitlab.com/carlavilla/freebsd-hugo-data" title="DOCNG Share Repo">https://gitlab.com/carlavilla/freebsd-hugo-data</a></td></tr></table><p>
-	Contact: Sergio Carlavilla &lt;<a href="mailto:carlavilla@FreeBSD.org">carlavilla@FreeBSD.org</a>&gt;
-	</p><p>The Doc New Generation project is finished. The switch-over date will be Saturday, January 23rd.
-</p>
-<p>The objective of using Hugo and AsciiDoctor is to reduce the
-learning curve and let people to start quickly contributing to our documentation
-system. Other benefits of using Hugo is that we can use other
-technologies aside from AsciiDoctor, like MarkDown, RST, Pandoc, etc.
-</p>
-<p>You can find a <a href="https://github.com/sergio-carlavilla/documentation-project-primer" shape="rect">work in progress on updating the FreeBSD Documentation Project Primer to Hugo/AsciiDoctor</a>.
-</p><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><p>Objects that defy categorization.</p><br /><h2><a name="Prometheus-NFS-Exporter" href="#Prometheus-NFS-Exporter" id="Prometheus-NFS-Exporter">Prometheus NFS Exporter</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/Axcient/freebsd-nfs-exporter" title="https://github.com/Axcient/freebsd-nfs-exporter">FreeBSD NFS statistics exporter for Prometheus</a></td><td>
-	    URL: <a href="https://github.com/Axcient/freebsd-nfs-exporter" title="FreeBSD NFS statistics exporter for Prometheus">https://github.com/Axcient/freebsd-nfs-exporter</a></td></tr></table><p>
-	Contact: Alan Somers &lt;<a href="mailto:asomers@FreeBSD.org">asomers@FreeBSD.org</a>&gt;
-	</p><p>FreeBSD's nfsstat(8) utility provides a wealth of statistics, but I wanted to
-monitor them with Prometheus.  Screen-scraping the --libxo output would've been
-possible, but some of the stats are preprocessed in a way that interferes with
-my Prometheus processing.  So I wrote a separate utility that publishes the raw
-stats provided by the kernel.  Along the way I found and fixed a few bugs in
-nfsstat, too.  If anybody is interested, I can add a port for it.
-</p>
-<p>Sponsor: Axcient<br clear="none" />
-</p><hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of
-      FreeBSD into their project.  As these projects may be of interest
-      to the broader FreeBSD community, we sometimes include brief
-      updates submitted by these projects in our quarterly report.
-      The FreeBSD project makes no representation as to the accuracy or
-      veracity of any claims in these submissions.</p><br /><h2><a name="FreeBSD-Aarch64-under-VMWare-ESXi-ARM-Fling" href="#FreeBSD-Aarch64-under-VMWare-ESXi-ARM-Fling" id="FreeBSD-Aarch64-under-VMWare-ESXi-ARM-Fling">FreeBSD Aarch64 under VMWare ESXi-ARM Fling</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://flings.vmware.com/esxi-arm-edition" title="https://flings.vmware.com/esxi-arm-edition">ESXi-ARM Fling</a></td><td>
-	    URL: <a href="https://flings.vmware.com/esxi-arm-edition" title="ESXi-ARM Fling">https://flings.vmware.com/esxi-arm-edition</a></td></tr><tr><td><a href="https://vincerants.com/freebsd-under-vmware-esxi-on-arm-fling/" title="https://vincerants.com/freebsd-under-vmware-esxi-on-arm-fling/">FreeBSD Under VMWare ESXi-ARM Fling</a></td><td>
-	    URL: <a href="https://vincerants.com/freebsd-under-vmware-esxi-on-arm-fling/" title="FreeBSD Under VMWare ESXi-ARM Fling">https://vincerants.com/freebsd-under-vmware-esxi-on-arm-fling/</a></td></tr><tr><td><a href="https://vincerants.com/freebsd-on-esxi-arm-fling-fixing-virtual-hardware/" title="https://vincerants.com/freebsd-on-esxi-arm-fling-fixing-virtual-hardware/">FreeBSD on ESXi-ARM Fling: Fixing Virtual Hardware</a></td><td>
-	    URL: <a href="https://vincerants.com/freebsd-on-esxi-arm-fling-fixing-virtual-hardware/" title="FreeBSD on ESXi-ARM Fling: Fixing Virtual Hardware">https://vincerants.com/freebsd-on-esxi-arm-fling-fixing-virtual-hardware/</a></td></tr><tr><td><a href="https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/" title="https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/">open-vm-tools for FreeBSD VMWare ESXi-ARM Fling</a></td><td>
-	    URL: <a href="https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/" title="open-vm-tools for FreeBSD VMWare ESXi-ARM Fling">https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/</a></td></tr></table><p>
-	Contact: Vincent Milum Jr &lt;<a href="mailto:freebsd@darkain.com">freebsd@darkain.com</a>&gt;
-	</p><p>VMWare is a company that produces a commercial hypervisor known
-as vSphere ESXi for AMD64 and i386. In early October, they
-released a tech demo hypervisor for ARM Aarch64 which runs
-on ARM ServerReady hardware as well as single board computers
-such as the Raspberry Pi 4b (4GB and 8GB models). This new
-hypervisor is known as VMWare ESXi-ARM Fling.
-</p>
-<p>Since the release of ESXi-ARM Fling, work has been done on
-both the hypervisor as well as FreeBSD, to make the two more
-compatible with one another. Even though the work was
-initially done to make these two work better together, the
-work overall has been more general purpose for FreeBSD
-in support of both bare-metal Aarch64 installations as well
-as running FreeBSD under other hypervisors such as QEMU.
-</p>
-<p>An example of others building off of this work is <url href="https://twitter.com/astr0baby/status/1343354762964717568">Twitter user astr0baby getting FreeBSD working under QEMU on a new Apple M1 system</url>.
-</p>
-<p>When ESXi-ARM Fling first released, to get FreeBSD to work
-under it, the process required taking the Aarch64 premade
-VMDK file, uploading it to the hypervisor storage, and then
-running a series of CLI commands to convert the disk image
-to a supported file format. The initial work done was to
-get the FreeBSD Aarch64 ISO bootable and with the required
-drivers to complete the install process. With this, users
-can do fresh installs of FreeBSD Aarch64 using the same
-methods they would use for AMD64 or i386 under ESXi.
-</p>
-<p>The CD-ROM driver's inclusion into FreeBSD 12 barely missed
-the cut-off date for 12.2-RELEASE. However, the very first
-12.2-STABLE build published for Aarch64 includes the CD-ROM
-driver. FreeBSD 13-CURRENT also includes this driver. Due
-to this, only 12-STABLE and 13-CURRENT support fresh CD ISO
-installations.
-</p>
-<p>The next step was getting the major pieces of virtual
-hardware working. This included adding more USB controllers,
-the vmxnet virtual network card, and pvscsi para-virtual
-SCSI drivers added to Aarch64 GENERIC.
-</p>
-<p>There is a known bug in ESXi-ARM Fling's virtual UEFI that
-prevents booting from pvscsi, so for the time being the boot
-device must be on a virtual disk attached to the SATA
-controller inside the VM.
-</p>
-<p>ESXi-ARM Fling uses a new virtual SVGA device which
-currently does not have working drivers on any platform, as
-the specifications are not finalized yet. Due to this, only
-efi-fb/scfb is available for console and Xorg for the time
-being.
-</p>
-<p>The VMCI driver is currently not compiling at all. This
-driver has sections of x86 assembly code that will need to be
-converted over to ARM. This would be a great area for
-anyone to look into that is experienced with converting assembly
-language!
-</p>
-<p>At ESXi-ARM Fling launch, there was a hypervisor bug
-preventing more than 1 vCPU from working inside FreeBSD.
-This has since been fixed, allowing up to 8 vCPUs. Going
-beyond this requires a <a href="https://github.com/freebsd/freebsd-src/compare/master...claplace:user/claplace/gicv3_mbi" shape="rect">a patch to FreeBSD</a>,
-which was authored by VMWare developer Cypou.
-</p>
-
-<p>Things that are currently fixed/working:
-</p>
-<ul>
-<li><p>Booting from CD ISO image
-</p></li>
-<li><p>Virtual USB 2.0 controller
-</p></li>
-<li><p>Virtual USB 3.1 controller
-</p></li>
-<li><p>Virtual USB Keyboard
-</p></li>
-<li><p>Virtual USB Mouse
-</p></li>
-<li><p>vmxnet3 Virtual Network Card
-</p></li>
-<li><p>pvscsi Para-Virtual SCSI Storage Controller
-</p></li>
-<li><p>open-vm-tools Guest Virtual Machine Tools
-</p></li>
-<li><p>Xorg Enhanced Mouse Driver (untested)
-</p></li>
-<li><p>Multi-Core CPU (up to 8 vCPUs inside guest)
-</p>
-</li></ul>
-Things that are still broken:
-
-<ul>
-<li><p>Booting from pvscsi
-</p></li>
-<li><p>Xorg SVGA Driver
-</p></li>
-<li><p>vmci Virtual Machine Communication Interface
-</p></li>
-<li><p>Multi-Core CPU (more than 8 vCPUs)
-</p>
-
-</li></ul>
-With all of this done, it has made working on the Aarch64 ports
-<p>collection easier by having a high quality virtualization
-environment for development and testing. This environment
-has already been used to update the ZeroTier port and
-Facebook's RocksDB used in the MariaDB port.
-</p>
-<p>FreeBSD now has a Discord chat! Discussion about FreeBSD
-on Aarch64 in general takes place in our
-<a href="https://discord.gg/KHtrpdqE4F" shape="rect">#embedded</a> channel. Despite
-the name, we discuss all levels of ARM development, from
-large servers, to virtualized environments, all the way down
-to single board computers.
-</p><hr /><h2><a name="Bastille" href="#Bastille" id="Bastille">Bastille</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/bastillebsd/bastille" title="https://github.com/bastillebsd/bastille">Bastille GitHub</a></td><td>
-	    URL: <a href="https://github.com/bastillebsd/bastille" title="Bastille GitHub">https://github.com/bastillebsd/bastille</a></td></tr><tr><td><a href="https://gitlab.com/bastillebsd-templates" title="https://gitlab.com/bastillebsd-templates">Bastille Templates</a></td><td>
-	    URL: <a href="https://gitlab.com/bastillebsd-templates" title="Bastille Templates">https://gitlab.com/bastillebsd-templates</a></td></tr><tr><td><a href="https://bastillebsd.org" title="https://bastillebsd.org">Bastille Website</a></td><td>
-	    URL: <a href="https://bastillebsd.org" title="Bastille Website">https://bastillebsd.org</a></td></tr></table><p>
-	Contact: Christer Edwards &lt;<a href="mailto:christer.edwards@gmail.com">christer.edwards@gmail.com</a>&gt;
-	</p><p>Bastille is an open-source system for automating deployment and management of
-containerised applications on FreeBSD.
-</p>
-<p>Bastille Templates automate container setup allowing you to easily reproduce
-containers as needed.
-</p>
-<p>Bastille is available in ports as <code>sysutils/bastille</code>.
-</p>
-<h3>Q4 2020 Status</h3>
-
-<p>In Q4 2020 Bastille merged some exciting new features. Changes include:
-</p>
-<ul>
-<li><p>full adoption of the previously experimental Bastillefile format
-</p></li>
-<li><p>new <code>config</code> sub-command
-</p></li>
-<li><p>default templates included and applied by default
-</p></li>
-<li><p>support for -CURRENT jails on -CURRENT hosts
-</p></li>
-<li><p>support for 32bit containers on 64bit hosts
-</p></li>
-<li><p>support in templates for dynamic arguments &amp; defining variables
-</p></li>
-<li><p>over two dozen bug fixes and general improvements
-</p>
-</li></ul>
-More details about <a href="https://github.com/BastilleBSD/bastille/releases" shape="rect">Bastille Releases</a>.
-
-<p>upstream was updated to <code>0.8.202010101</code> (latest).
-ports (<code>sysutils/bastille</code>) was updated to <code>0.7.20200414</code>.
-</p><hr /><h2><a name="CheriBSD" href="#CheriBSD" id="CheriBSD">CheriBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cheri-cpu.org" title="http://www.cheri-cpu.org">CHERI Project Homepage</a></td><td>
-	    URL: <a href="http://www.cheri-cpu.org" title="CHERI Project homepage">http://www.cheri-cpu.org</a></td></tr><tr><td><a href="https://github.com/CTSRD-CHERI/cheribsd" title="https://github.com/CTSRD-CHERI/cheribsd">CheriBSD GitHub Repo</a></td><td>
-	    URL: <a href="https://github.com/CTSRD-CHERI/cheribsd" title="CHERi github repo">https://github.com/CTSRD-CHERI/cheribsd</a></td></tr><tr><td><a href="https://www.morello-project.org" title="https://www.morello-project.org">Morello Platform Landing Page</a></td><td>
-	    URL: <a href="https://www.morello-project.org" title="Morello Platform landing page">https://www.morello-project.org</a></td></tr><tr><td><a href="https://morello-dist.cl.cam.ac.uk" title="https://morello-dist.cl.cam.ac.uk">CheriBSD Morello Developer Preview</a></td><td>
-	    URL: <a href="https://morello-dist.cl.cam.ac.uk" title="CheriBSD Morello Developer Preview">https://morello-dist.cl.cam.ac.uk</a></td></tr><tr><td><a href="https://developer.arm.com/architectures/cpu-architecture/a-profile/morello" title="https://developer.arm.com/architectures/cpu-architecture/a-profile/morello">Arm Morello Program</a></td><td>
-	    URL: <a href="https://developer.arm.com/architectures/cpu-architecture/a-profile/morello" title="ARM Morello Program">https://developer.arm.com/architectures/cpu-architecture/a-profile/morello</a></td></tr></table><p>
-	Contact: Alex Richardson &lt;<a href="mailto:arichardson@FreeBSD.org">arichardson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Andrew Turner &lt;<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Brooks Davis &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Edward Tomasz Napierala &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
-	<br />
-	Contact: George Neville-Neil &lt;<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Jessica Clarke &lt;<a href="mailto:jrtc27@FreeBSD.org">jrtc27@FreeBSD.org</a>&gt;
-	<br />
-	Contact: John Baldwin &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Robert Watson &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Ruslan Bukin &lt;<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>&gt;
-	</p><p>CheriBSD extends FreeBSD to implement memory protection and software
-compartmentalization features supported by the CHERI instruction-set
-extensions.  There are three architectural implementations of the
-CHERI protection model: CHERI-MIPS, CHERI-RISC-V, and Arm's forthcoming
-experimental Morello processor (due late 2021).  CheriBSD is a research
-operating system with a stable baseline implementation into which
-various new research features have been, or are currently being, merged:
-</p>
-<ul>
-<li><p>Arm Morello - In October, we released a developer preview of CheriBSD
-ported to Arm's Morello architecture.  This release supports a
-dynamically linked runtime and is generally functional.  It was cut
- from a development branch and work is in progress to merge the contents
- of this branch with the CheriBSD main line.  We anticipate producing a
-new release from this branch in early 2021.
-</p></li>
-<li><p>Kernel spatial memory safety (pure-capability kernel) - The current
- CheriBSD kernel is a hybrid C program where only pointers to userspace
-are CHERI capabilities. This ensures that the kernel follows the
-intent of the application runtime and cannot be used to defeat
-bounds on application pointers. We have developed and will soon
-merge a pure-capability kernel where all pointers in the kernel are
- appropriately bounded capabilities. This vastly reduces the opportunity
-for buffer overflows. This spatial memory safety lays the
-groundwork for future work such as device driver compartmentalization
-and kernel temporal safety.
-</p></li>
-<li><p>Userspace heap temporal memory safety (Cornucopia) - CHERI
-capabilities provide the necessary features to enable
- robust and efficient revocation of freed pointers.  With <a href="https://www.cl.cam.ac.uk/research/security/ctsrd/pdfs/2020oakland-cornucopia.pdf" shape="rect">Cornucopia</a>
-we have implemented a light-weight revocation framework providing
- protection from use-after-reallocation bugs with an average cost below
- 2%.  We aim to bring these overheads down further over the next year and
-merge this functionality into the mainline CheriBSD.
-</p></li>
-<li><p>Syncing with upstream FreeBSD - We spent considerable time this
-quarter catching up with FreeBSD-CURRENT.  As of the beginning of
-December, we had caught up.  Merges are currently paused while we
-work to land Morello and pure-capability kernel changes.  In the
-interim, we have performed a test merge between our tree based on
-the legacy export of the FreeBSD tree to git and the new FreeBSD
-git repository.  The process went smoothly and is expected to have
-few impacts.
-</p></li>
-<li><p>We have been working on updating the arm64 bhyve from Politehnica
-University of Bucharest to have it committed to FreeBSD. We have been
-upstreaming initial changes to help support this.
-</p></li></ul>
-<hr /><h2><a name="Embedded-Lab-Project" href="#Embedded-Lab-Project" id="Embedded-Lab-Project">Embedded Lab Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.funkthat.com/gitea/jmg/fbsdembdev" title="https://www.funkthat.com/gitea/jmg/fbsdembdev">FreeBSD Embedded Lab Design</a></td><td>
-	    URL: <a href="https://www.funkthat.com/gitea/jmg/fbsdembdev" title="FreeBSD Embedded Lab Design">https://www.funkthat.com/gitea/jmg/fbsdembdev</a></td></tr><tr><td><a href="https://www.funkthat.com/gitea/jmg/bitelab" title="https://www.funkthat.com/gitea/jmg/bitelab">Lab API code</a></td><td>
-	    URL: <a href="https://www.funkthat.com/gitea/jmg/bitelab" title="Lab API code">https://www.funkthat.com/gitea/jmg/bitelab</a></td></tr></table><p>
-	Contact: John-Mark Gurney &lt;<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>&gt;
-	</p><p>The Embedded Lab Project's goal is to make SBCs and other devices more
-accessible to developers.  Despite SBCs often being inexpensive, it is
-not inexpensive to maintain them, in terms of the cost of time to keep
-them up to date, infrastructure to support them, etc.
-</p>
-<p>The goal of this project is to support and enhance the existing CI work
-but also make it easier for developers to test their code and changes
-on one, or many different boards.
-</p>
-<p>Once the work is [mostly] complete, I will host a lab that will be freely
-available to everyone who has a FreeBSD.org account.  Information about
-this will be sent once it is closer to launch.
-</p>
-<p>The core part of the architecture is each time a board is reserved via
-the API, a new jail is created which contains the serial console tty,
-an interface for internet access, and an interface that is connected
-to the board's ethernet port (assuming it has one).  This allows a
-clean system for each run, and allows complete control over the network
-interfaces to support netbooting and other development.  The jail will
-have a basic set of FreeBSD packages installed that matches the board.
-</p>
-<p>Part of the API will also allow power cycling the board to aid in
-debugging.  This part is relatively extensible, so adding additional
-modules to provide additional support should not be difficult.
-</p>
-<p>The API includes support for running interactive commands in the jail.
-This will make it easy to script control of the environment, such as
-directly running an expect script against the serial console, or even
-just running a script in the jail.
-</p>
-<p>The work is progressing well, and currently a single board, a Pine64
-A64-LTS, is integrated and working.  Board reserves and releases are
-working, along with the ability to run commands in the jail via the API.
-Power control is functional, and is currently using a PoE smart switch
-to control power.
-</p>
-<p>Work has stalled on being able to use the <a href="https://wiki.tizen.org/SDWire" shape="rect">SDWire</a>
-with an environment due to power issues.  USB is not made for power
-isolation, which is causing issues w/ power control.  The existing
-board, the A64-lTS, is using a USB serial console adapter that is
-opto-isolated, ensuring that there is no problems w/ power control.  But
-there I have not found a solution for high speed USB.  I believe that
-cutting the VBUS (power) line of a USB cable would allow fine grain
-power control, but tests have not been conducted yet.
-</p>
-<p>Sponsor: The FreeBSD Foundation
-</p><hr /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freshports.org/" title="http://freshports.org/">FreshPorts</a></td><td>
-	    URL: <a href="http://freshports.org/" title="FreshPorts">http://freshports.org/</a></td></tr><tr><td><a href="http://news.freshports.org/" title="http://news.freshports.org/">FreshPorts blog</a></td><td>
-	    URL: <a href="http://news.freshports.org/" title="FreshPorts blog">http://news.freshports.org/</a></td></tr></table><p>
-	Contact: Dan Langille &lt;<a href="mailto:dan@langille.org">dan@langille.org</a>&gt;
-	</p>
-<p>FreshPorts, and its sister site, FreshSource, have reported
-upon FreeBSD commits for 20 years. They cover all commits,
-not just ports.
-</p>
-<p>FreshPorts tracks the commits and extracts data from the
-port Makefiles to create a database of information useful
-to both port developers and port users.
-</p>
-<p>For example, <a href="https://www.freshports.org/security/acme.sh/" shape="rect">https://www.freshports.org/security/acme.sh/</a>
-shows the history of this port, back to its creation in May 2017.
-</p>
-<h3>git</h3>
-
-<p>The work to become git-ready is mostly complete. Both src and doc commits are
-flowing into <a href="https://devgit.freshports.org" shape="rect">devgit.freshports.org</a>. Some
-work is required on various issues, but nothing that stops the flow of
-commits into the database.
-</p>
-<h3>Help wanted</h3>
-
-<p>Amazon have donated enough to try FreshPorts on AWS. I need help with the
-following:
-</p>
-<ul>
-<li><p>getting IPv6 working
-</p></li>
-<li><p>working with <a href="https://aws.amazon.com/rds/" shape="rect">RDS</a>
-</p>
-</li></ul>
-If you can help with this, please contact me. Thank you.
-
-<p>Thank you
-</p>
-<hr /><h2><a name="helloSystem" href="#helloSystem" id="helloSystem">helloSystem</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://hellosystem.github.io/docs/" title="https://hellosystem.github.io/docs/">Documentation</a></td><td>
-	    URL: <a href="https://hellosystem.github.io/docs/" title="Documentation">https://hellosystem.github.io/docs/</a></td></tr></table><p>
-	Contact: Simon Peter &lt;<a href="mailto:probono@puredarwin.org">probono@puredarwin.org</a>&gt;
-	</p><p>Contact: <code>#helloSystem</code> on <code>irc.freenode.net</code>, mirrored to <a href="https://matrix.to/#/%23helloSystem:matrix.org?via=matrix.org" shape="rect"><code>#helloSystem:matrix.org</code> on Matrix</a>
-</p>
-<p>helloSystem is FreeBSD preconfigured as a desktop operating system
-with a focus on simplicity, elegance, and usability.
-Its design follows the &#8220;Less, but better&#8221; philosophy.
-It is intended as a system for &#8220;mere mortals&#8221;, welcoming to switchers
-from a world in which a global menu bar exists, the Command key is used
-rather than Control, and applications are contained in .app bundles.
-</p>
-<p>helloSystem grew out of frustration with <a href="https://medium.com/@probonopd/make-it-simple-linux-desktop-usability-part-1-5fa0fb369b42" shape="rect">usability shortcomings</a> of existing open source
-desktop environments. FreeBSD was chosen as the base because it offers
-one consistent base system rather than a <a href="https://media.ccc.de/v/ASG2018-174-2018_desktop_linux_platform_issues" shape="rect">fragmented landscape of distributions lacking a common platform</a>.
-</p>
-<p>helloSystem aims at providing a "it just works" out-of-the-box user experience
-in which a non-technical user can just use the system without ever opening
-the terminal, without having to configure anything, and without ever seeing
-white text on a black background scroll by during system boot. Technologies embraced
-include DNS-SD/Zeroconf (also known as Bonjour), IPP Everywhere (also known as AirPrint),
-eSCL (also known as AirScan), etc.
-</p>
-<p>Prerelease installable Live ISO images are available.
-</p>
-<p><a href="https://github.com/helloSystem/hello/blob/master/CONTRIBUTING.md" shape="rect">Help is needed in a number of areas</a>, especially:
-</p>
-<ul>
-<li><p>FreeBSD/kernel: allowing to put the system into a read-only disk image with a writable overlay, e.g., using unionfs
-</p></li>
-<li><p>Qt, Python: writing various easy-to use frontends for FreeBSD/OpenZFS functionality, e.g., Disk Utility.app
-</p></li>
-<li><p>Testing and bugfixing
-</p></li></ul>
-<hr /><h2><a name="K8S-bhyve" href="#K8S-bhyve" id="K8S-bhyve">K8S-bhyve</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://k8s-bhyve.convectix.com" title="https://k8s-bhyve.convectix.com">K8S-bhyve</a></td><td>
-	    URL: <a href="https://k8s-bhyve.convectix.com" title="K8S-bhyve">https://k8s-bhyve.convectix.com</a></td></tr><tr><td><a href="https://github.com/k8s-bhyve" title="https://github.com/k8s-bhyve">K8S-bhyve</a></td><td>
-	    URL: <a href="https://github.com/k8s-bhyve" title="K8S-bhyve">https://github.com/k8s-bhyve</a></td></tr><tr><td><a href="https://kubernetes.io/" title="https://kubernetes.io/">Kubernetes</a></td><td>
-	    URL: <a href="https://kubernetes.io/" title="Kubernetes">https://kubernetes.io/</a></td></tr></table><p>
-	Contact: Kirill Ponomarev &lt;<a href="mailto:krion@FreeBSD.org">krion@FreeBSD.org</a>&gt;
-	<br />
-	Contact: Oleg Ginzburg &lt;<a href="mailto:olevole@olevole.ru">olevole@olevole.ru</a>&gt;
-	</p><p>K8S-bhyve is opensource project concentrating primarily on deploying and use
-of kubernetes on FreeBSD/bhyve in a more agile and more comfortable manner.
-We are going to provide distributed multi-DC environment or just stand-alone
-clusters with native PV/PVC support.
-</p>
-<p>For 2020Q4 we made and published a k8s-bhyve image which
-you might install with <a href="https://k8s-bhyve.convectix.com/kbhyve-latest.iso" shape="rect">ISO/memstick</a>,
-as well as with <a href="http://k8s.bsdstore.ru/auto" shape="rect">bsdinstall</a>.
-</p><hr /><h2><a name="Puppet" href="#Puppet" id="Puppet">Puppet</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://puppet.com/docs/puppet/latest/puppet_index.html" title="https://puppet.com/docs/puppet/latest/puppet_index.html">Puppet</a></td><td>
-	    URL: <a href="https://puppet.com/docs/puppet/latest/puppet_index.html" title="Puppet">https://puppet.com/docs/puppet/latest/puppet_index.html</a></td></tr><tr><td><a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="https://puppetcommunity.slack.com/messages/C6CK0UGB1/">Puppet's FreeBSD slack channel</a></td><td>
-	    URL: <a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="Puppet's FreeBSD slack channel">https://puppetcommunity.slack.com/messages/C6CK0UGB1/</a></td></tr><tr><td><a href="https://puppet.com/docs/bolt/latest/bolt.html" title="https://puppet.com/docs/bolt/latest/bolt.html">Bolt</a></td><td>
-	    URL: <a href="https://puppet.com/docs/bolt/latest/bolt.html" title="Bolt">https://puppet.com/docs/bolt/latest/bolt.html</a></td></tr><tr><td><a href="https://choria.io/" title="https://choria.io/">Choria</a></td><td>
-	    URL: <a href="https://choria.io/" title="Choria">https://choria.io/</a></td></tr></table><p>
-	Contact: Puppet Team &lt;<a href="mailto:puppet@FreeBSD.org">puppet@FreeBSD.org</a>&gt;
-	</p><p>Since our last status report a few months ago, the FreeBSD ports tree
-has seen the addition of the Choria (sysutils/choria) orchestration
-tool, and the Puppet Platform 7 with the Puppet Agent (sysutils/puppet7),
-Puppet Server (sysutils/puppetserver7) and PuppetDB
-(databases/puppetdb7).
-</p>
-<p>Older versions of Puppet (5 and 6) are still in the ports tree, allowing
-a smooth transition, but please note that Puppet 5 will reach EOL soon,
-and as it is not compatible with the recent ecosystem provided by
-FreeBSD (i.e. it is not compatible with the latest version of Ruby and
-depends on old FreeBSD primitives not available anymore), it is
-recommended to update at least to Puppet 6 as soon as possible.
-</p>
-<p>Ports depending on Puppet (e.g. sysutils/rubygem-bolt) have been updated
-to add options allowing to choose which version of Puppet to depend on.
-For now, the default is Puppet 6, but we plan to switch the default to
-Puppet 7 in a few weeks, probably when Puppet 5 will have reached EOL.
-</p><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
-          <br class="clearboth" />
-        </div>
-        <div id="footer">
-          <span><a href="../../search/index-site.html">Site Map</a> |
-  <a href="../../copyright/">Legal Notices</a> | � 1995&#8211;2021 The FreeBSD Project.
-  All rights reserved.</span>
-          <br />
-        </div>
-      </div>
-    </div>
-  </body>
-</html>
diff --git a/website/content/en/status/report-2021-01-2021-03/_index.adoc b/website/content/en/status/report-2021-01-2021-03/_index.adoc
index 529e4ada2c..e8b0e484d5 100644
--- a/website/content/en/status/report-2021-01-2021-03/_index.adoc
+++ b/website/content/en/status/report-2021-01-2021-03/_index.adoc
@@ -1,5 +1,5 @@
 ---
-title: "Introduction"
+title: "FreeBSD Quarterly Status Report 1st Quarter 2021"
 sidenav: about
 ---
 
diff --git a/website/content/en/status/report-2021-04-2021-06/_index.adoc b/website/content/en/status/report-2021-04-2021-06/_index.adoc
index a10dc5b284..5e8af95720 100644
--- a/website/content/en/status/report-2021-04-2021-06/_index.adoc
+++ b/website/content/en/status/report-2021-04-2021-06/_index.adoc
@@ -1,5 +1,5 @@
 ---
-title: "Introduction"
+title: "FreeBSD Quarterly Status Report 2nd Quarter 2021"
 sidenav: about
 ---
 
diff --git a/website/content/en/status/report-2021-10-2021-12/_index.adoc b/website/content/en/status/report-2021-10-2021-12/_index.adoc
new file mode 100644
index 0000000000..2de299e189
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/_index.adoc
@@ -0,0 +1,131 @@
+---
+title: "FreeBSD Quarterly Status Report 4th Quarter 2021"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2021-10-2021-12
+
+This report covers FreeBSD related projects for the period between October and December.  It is the fourth of four planned reports for 2021, and contains 19 entries.  Highlights include faster boot times, more LLDB work, a base OpenSSH update, and more wireless development.
+
+Yours, +
+Pau Amma, Daniel Ebdrup, John-Mark Gurney, and Joe Mingrone
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+Entries from the various official and semi-official teams, as found in the link:../../administration/[Administration Page].
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+include::{reports-path}/www.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects.
+
+
+include::{reports-path}/aslr.adoc[]
+
+'''
+
+include::{reports-path}/boot-performance.adoc[]
+
+'''
+
+include::{reports-path}/lldb.adoc[]
+
+'''
+
+include::{reports-path}/ls1027a.adoc[]
+
+'''
+
+include::{reports-path}/membarrier-rseq.adoc[]
+
+'''
+
+include::{reports-path}/openssh.adoc[]
+
+'''
+
+include::{reports-path}/vdso.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+Updates to kernel subsystems/features, driver support, filesystems, and more.
+
+
+include::{reports-path}/avx-bug.adoc[]
+
+'''
+
+include::{reports-path}/ena.adoc[]
+
+'''
+
+include::{reports-path}/iwlwifi.adoc[]
+
+'''
+
+include::{reports-path}/ocf-wg.adoc[]
+
+'''
+
+
+[[ports]]
+== Ports
+
+Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves.
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/office.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third-Party Projects
+
+Many projects build upon FreeBSD or incorporate components of FreeBSD into their project.
+As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report.
+The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions.
+
+include::{reports-path}/hellosystem.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
+
+'''
diff --git a/website/content/en/status/report-2021-10-2021-12/aslr.adoc b/website/content/en/status/report-2021-10-2021-12/aslr.adoc
new file mode 100644
index 0000000000..21d45d04fe
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/aslr.adoc
@@ -0,0 +1,29 @@
+=== Enable ASLR by default for 64-bit executables
+
+Contact: Dawid Gorecki <dgr@semihalf.com> +
+Contact: Marcin Wojtas <mw@semihalf.com>
+
+Address Space Layout Randomization (ASLR) is an exploit mitigation
+technique implemented in the majority of modern operating systems.
+It involves randomly positioning the base address of an executable
+and the position of libraries, heap, and stack, in a process's address
+space. Although over the years ASLR proved to not guarantee full OS
+security on its own, this mechanism can make exploitation more difficult.
+
+The Semihalf team made an effort to switch on the address map
+randomization for PIE (Position Independent Executables) & non-PIE 64-bit binaries.
+Once the link:https://cgit.freebsd.org/src/commit/?id=b014e0f15bc73d80e[patch] was merged to HEAD,
+the ASLR feature became enabled for all 64-bit architectures.
+
+Additionally, the mentioned change disabled
+link:https://www.freebsd.org/cgi/man.cgi?query=sbrk&sektion=2[SBRK],
+in order to allow utilization of the bss grow region for mappings.
+It has no effect without ASLR, so it was applied to all architectures.
+
+TODO:
+
+* Improve stackgap feature implementation.
+
+* MFC to stable/13 branch.
+
+Sponsor: Stormshield
diff --git a/website/content/en/status/report-2021-10-2021-12/avx-bug.adoc b/website/content/en/status/report-2021-10-2021-12/avx-bug.adoc
new file mode 100644
index 0000000000..4b99fab1ab
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/avx-bug.adoc
@@ -0,0 +1,30 @@
+=== The AVX bug on amd64
+
+Commit: gitref:73b357be92385cbb70ba19e7023a736af2c6b493[repository=src] URL: link:https://cgit.freebsd.org/src/commit/?id=73b357be92385cbb70ba19e7023a736af2c6b493[https://cgit.freebsd.org/src/commit/?id=73b357be92385cbb70ba19e7023a736af2c6b493]
+
+Contact: Konstantin Belousov <kib@FreeBSD.org>
+
+Some CPUs support the so called init optimization for XSAVE, but not all CPUs
+do.  And when they do, 'according to complex internal microarchitectural
+conditions', the optimization might happen or not.  Basically, this
+means that sometimes the CPU does not write all of the state on
+XSAVE and records in xstate_bv that it did not.
+
+On signal delivery, the OS provides the saved context interrupted by
+the signal to the signal handler.  The context includes all CPU state
+available to userspace, including FPU registers (XSAVE area).  Also,
+on return from the signal handler, context is restored, which
+allows the handler to modify the main program flow.
+When init optimization kicks in, the OS tries to hide init state
+optimization from the signal handler, by filling non-saved parts of
+the XSAVE area.
+
+This is where the problem happens.  For states parts 0 (x87) and 1
+(SSE/XMM), Intel CPUs do not provide an enumeration of layout in CPUID,
+assuming that the OS knows about the regions anyway. The bug was that
+the amd64 kernel hardcoded a 32bit size for the XMM save area, effectively
+filling %XMM8-%XMM15 with garbage on signal return when init
+optimization kicked in, because only specified part of the SSE save
+area was copied from the canonical save area.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2021-10-2021-12/boot-performance.adoc b/website/content/en/status/report-2021-10-2021-12/boot-performance.adoc
new file mode 100644
index 0000000000..72e91ff7ea
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/boot-performance.adoc
@@ -0,0 +1,33 @@
+=== Boot Performance Improvements
+
+Links: +
+link:https://wiki.freebsd.org/BootTime[Wiki page] URL: link:https://wiki.freebsd.org/BootTime[https://wiki.freebsd.org/BootTime] +
+link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[OS boot time comparison] URL: link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+Colin Percival is coordinating an effort to speed up the FreeBSD boot process.
+For benchmarking purposes, he is primarily using an EC2 c5.xlarge instance as a
+reference platform and is measuring the time between when the virtual machine
+enters the EC2 "running" state and when it is possible to SSH into the instance.
+
+This work started in 2017, and as of the end of September 2021 the FreeBSD boot
+time was reduced from approximately 30 seconds to approximately 15 seconds.
+
+During 2021Q4, further improvements have shaved more time off the boot process,
+taking it down to roughly 10 seconds.  A further 4 seconds of improvements are
+in process.
+
+In addition, the userland boot process is now being profiled using TSLOG,
+making it possible to see flamecharts of the entire boot process; and the
+ec2-boot-bench tool is now able to generate MP4 videos of the boot process
+by taking snapshots of the EC2 VGA console.
+
+Issues are listed on the wiki page as they are identified; the wiki page also
+has instructions for performing profiling.  Users are encouraged to profile
+the boot process on their own systems, in case they experience delays which
+don't show up on the system Colin is using for testing.
+
+This work is supported by Colin's FreeBSD/EC2 Patreon.
+
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2021-10-2021-12/doceng.adoc b/website/content/en/status/report-2021-10-2021-12/doceng.adoc
new file mode 100644
index 0000000000..93abcd7c39
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/doceng.adoc
@@ -0,0 +1,39 @@
+////
+Quarter:	4th quarter of 2021
+Prepared by:	dbaio
+Reviewed by:	carlavilla, bcr
+Last edit:	$Date: 2022-01-05 20:07:39 -0300 (Wed, 05 Jan 2022) $
+Version:	$Id: doceng-2021-4th-quarter-status-report.adoc 208 2022-01-05 23:07:39Z dbaio $
+////
+
+=== Documentation Engineering Team
+
+Links: +
+link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[https://www.freebsd.org/docproj/] +
+link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[https://docs.freebsd.org/en/books/fdp-primer/] +
+link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[https://www.freebsd.org/administration/#t-doceng]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+No new documentation commit bit was granted during the last quarter, and only one commit bit was safe kept.
+
+Several tasks were completed related to the doc tree during the last quarter:
+
+* A COPYRIGHT file was added in the root directory of the doc repository.  The license was also updated to reflect the current toolchain the project is using now.
+
+* Cleanup of Mailman information in the doc tree.  Following mailing lists migration from Mailman to Mlmmj, very old mailing lists were removed; most of the work was made on English documents.
+
+* Tag FreeBSD docset for 12.3-RELEASE.
+
+* Update all ports/packages misc/freebsd-doc-*.
+
+* Move articles/contributors/contrib-* files to the doc shared directory.
+
+* Add option in documentation Makefile to archive/compress Documentation/HTML offline files, a necessary step before updating https://download.freebsd.org/ftp/.  This was after a discussion with clusteradm@ to update the offline assets (HTML/PDF).
+
+* Add experimental support for EPUB output (books/articles).
+
+* Talking with clusteradm@ to improve the performance of https://www.freebsd.org and https://docs.freebsd.org.
+
diff --git a/website/content/en/status/report-2021-10-2021-12/ena.adoc b/website/content/en/status/report-2021-10-2021-12/ena.adoc
new file mode 100644
index 0000000000..4f2edefd50
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/ena.adoc
@@ -0,0 +1,26 @@
+=== ENA FreeBSD Driver Update
+
+Links: +
+link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README]
+
+Contact: Michal Krawczyk <mk@semihalf.com> +
+Contact: Dawid Gorecki <dgr@semihalf.com> +
+Contact: Marcin Wojtas <mw@semihalf.com>
+
+ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS).
+The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used.
+
+Completed since the last update:
+
+* Add IPv6 layer 4 checksum offload support to the driver
+* Add NUMA awareness to the driver when the RSS kernel option is enabled
+* Rework validation of the Tx request ID
+* Change lifetime of the driver's timer service
+* Avoid reset triggering when the device is unresponsive
+
+Work in progress:
+
+* Prototype the driver port to the iflib framework
+* Tests of the incoming ENA driver release (v2.5.0)
+
+Sponsor: Amazon.com Inc
diff --git a/website/content/en/status/report-2021-10-2021-12/freebsd-foundation.adoc b/website/content/en/status/report-2021-10-2021-12/freebsd-foundation.adoc
new file mode 100644
index 0000000000..59e48b6b46
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/freebsd-foundation.adoc
@@ -0,0 +1,151 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] +
+link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] +
+link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] +
+link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] +
+link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/] +
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
+supporting and promoting the FreeBSD Project and community worldwide. Donations
+from individuals and corporations are used to fund and manage software
+development projects, conferences, and developer summits. We also provide travel
+grants to FreeBSD contributors, purchase and support hardware to improve and
+maintain FreeBSD infrastructure, and provide resources to improve security,
+quality assurance, and release engineering efforts. We publish marketing
+material to promote, educate, and advocate for the FreeBSD Project, facilitate
+collaboration between commercial vendors and FreeBSD developers, and finally,
+represent the FreeBSD Project in executing contracts, license agreements, and
+other legal arrangements that require a recognized legal entity.
+
+Here are some highlights of what we did to help FreeBSD last quarter:
+
+==== Fundraising Efforts
+
+We did it! We met our 2021 fundraising goal by raising $1,281,437!! On behalf
+of the Foundation, I want to thank you for your financial support last year,
+that will help us continue and increase our support for FreeBSD in 2022. In
+addition, folks are already sending us their 2022 contributions, which is
+incredibly heartwarming! We’ll start updating the fundraising meter for 2022
+by the end of January.
+
+In this Quarterly Status report you’ll read about many of the areas we funded
+in Q4 to improve FreeBSD and advocate for the Project (the two main areas we
+spend money on). Check out reports on the externally funded projects like LLDB
+support, Raid-Z Expansion, WireGuard, and wifi, as well as, internally supported
+work like improved security, tier-1 architecture support, and providing online
+opportunities to connect and educate the community.
+
+If you want to help us continue our efforts, please consider making a donation
+towards our 2022 fundraising campaign! https://www.FreeBSDFoundation.org/donate/.
+
+We also have a Partnership Program for larger commercial donors. You can read about
+it at https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program/.
+
+==== OS Improvements
+
+During the fourth quarter, Foundation staff and grant recipients committed 472
+src tree changes, 98 ports tree changes, and 11 doc tree changes.  This
+represents 41%, 41%, and 13% of src, ports, and doc commits identifying a
+sponsor.
+
+You can read about Foundation-sponsored projects in individual quarterly report
+entries:
+
+- The AVX bug on amd64
+- Crypto changes for WireGurard
+- Intel Wireless driver support
+- LLDB Debugger Improvements
+- Base System OpenSSH Update
+- sched_getcpu(2), membarrier(2), and rseq(2) syscalls
+- VDSO on amd64
+
+Here is a small sample of other base system improvements from Foundation
+developers this quarter that do not have separate report entries.
+
+===== kern.proc.pathname canonical hard link
+
+Some programs adjust their behavior depending on which name was used for
+execution.  For these programs, it is often important to have a consistent name
+in argv[0], sysctl kern.proc.pathname, auxv AT_EXECPATH, and any procfs file
+symlink.  Before this work, all listed kernel interfaces tried to calculate some
+name for the text vnode and returned the result.  If the executed binary has
+more than one hardlink, the returned names were arbitrarily chosen from the
+list of valid names for the file.  After work completed this quarter by Foundation
+developer Konstantin Belousov, the system now holds the parent directory and the
+name of the text file for the running image.  This is used to reconstruct the
+correct name of the text file when requested.
+
+===== swapon/swapoff, file swapping
+
+After work to fix asserts for character device vnode locking, there was a report
+that swap on file code broke the VFS locking protocol.  Some other regressions
+in the swap on file were also identified.  For instance, on shutdown,
+filesystems were unmounted before swapoff, which makes swapoff panic on page-in.
+These bugs were fixed and a link:https://www.freebsd.org/cgi/man.cgi?query=swapoff&apropos=0&sektion=2&manpath=FreeBSD+14.0-current&arch=default&format=html[swapoff(2)] feature was added to avoid some very
+conservative estimations for protection against memory and swap space shortages.
+
+===== fcntl(F_KINFO)
+
+Application developers often request an interface to return the file path for an
+open file descriptor.  Our only useful facility for this was kern.proc.filedesc
+sysctl, which is somewhat usable, but incurs too high of an overhead when a
+process has many open files.  A fcntl(F_KINFO) interface was added, which returns
+a struct kinfo_file just for the specified file descriptor.  Among other useful
+data, kinfo_file provides the calculated path, when available.
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve
+continuous integration, automated testing, and overall quality assurance efforts
+for the FreeBSD project.
+
+==== Supporting FreeBSD Infrastructure
+
+The Foundation provides hardware and support for the Project.  In the fourth
+quarter of 2021, we began searching for a new Australian mirror server.  At the
+time of writing, the server is purchased, but with delays obtaining components
+and shipping, it may not be active until the second or third quarter of 2022.
+Better and faster access to our sites for the Australian FreeBSD community is
+coming.
+
+==== FreeBSD Advocacy and Education
+
+Much of our effort is dedicated to Project advocacy.  This may involve highlighting interesting FreeBSD work, producing literature, attending events, or giving presentations.  The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier.  Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe.  These events can be BSD-related, open source, or technology events geared towards underrepresented groups.  We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.  This all helps provide a healthy ecosystem.  We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.  We are continuing to attend virtual events and held a virtual vendor summit this past November.
+
+Check out some of the advocacy and education work we did last quarter:
+
+* Promoted and participated as a media sponsor for link:https://2021.allthingsopen.org/[ALL Things Open 2021]
+* Committed to being a Media Sponsor for link:https://www.socallinuxexpo.org/scale/19x[SCALE 19x]
+* Committed to hosting a link:https://stands.fosdem.org/stands/freebsd_project/[stand at FOSDEM 2022]
+* Sent out the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-fall-2021-update/[Fall 2021 Newsletter]
+* Held a link:https://www.youtube.com/watch?v=BYTNpuinaPU[FreeBSD Friday talk: The Writing Scholar's Guide to FreeBSD], (link:https://www.coreystephan.com/freebsd-friday/[text equivalent])
+* Gave a Foundation talk at link:http://www.semibug.org/[Semi-Bug], November 16, 2021
+* Gave Foundation and FreeBSD talks at Seagate OSPO, December 9, 2021
+* Helped organize the 2 day link:https://wiki.freebsd.org/DevSummit/202111[FreeBSD Virtual Vendor Summit, November 18-19, 2021]. Videos can be found on the link:https://www.youtube.com/c/FreeBSDProject/videos[Project’s Youtube Channel]
+* New blog and video posts:
+** link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-fall-2021-update/[FreeBSD Foundation Fall 2021 Update]
+** link:https://freebsdfoundation.org/blog/2021-in-review-advocacy/[2021 in Review: Advocacy]
+** link:https://freebsdfoundation.org/blog/2021-in-review-infrastructure-support/[2021 in Review: Infrastructure Support]
+** link:https://freebsdfoundation.org/blog/2021-in-review-software-development/[2021 in Review: Software Development]
+** link:https://freebsdfoundation.org/blog/open-source-summit-2021-conference-recap/[Open Source Summit 2021 Conference Recap]
+* New How-To Guide: link:https://freebsdfoundation.org/freebsd-project/resources/freebsd-introduction/[Introduction to FreeBSD]
+
+We help educate the world about FreeBSD by publishing the professionally produced link:https://freebsdfoundation.org/our-work/journal/[FreeBSD Journal]. As we mentioned previously, the FreeBSD Journal is now a free publication. Find out more and access the latest issues at https://www.FreeBSDfoundation.org/journal/.
+
+You can find out more about events we attended and upcoming events at https://www.FreeBSDfoundation.org/news-and-events/.
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to
+protect them. We also provide legal support for the core team to investigate
+questions that arise.
+
+Go to link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org]
+to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2021-10-2021-12/hellosystem.adoc b/website/content/en/status/report-2021-10-2021-12/hellosystem.adoc
new file mode 100644
index 0000000000..514ec958d6
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/hellosystem.adoc
@@ -0,0 +1,27 @@
+=== helloSystem
+
+Links: +
+link:https://hellosystem.github.io/docs/[Documentation] URL: link:https://hellosystem.github.io/[https://hellosystem.github.io/]
+
+Contact: Simon Peter <probono@puredarwin.org> +
+Contact: `\#helloSystem` on `irc.libera.chat`, mirrored to link:https://matrix.to/#/%23helloSystem:matrix.org?via=matrix.org[`#helloSystem:matrix.org` on Matrix]
+
+==== What is helloSystem?
+
+helloSystem is FreeBSD preconfigured as a desktop operating system with a focus on simplicity, elegance, and usability.
+Its design follows the “Less, but better” philosophy.
+
+==== Q4 2021 Status
+
+* Version 0.7.0 of helloSystem has been published including many contributed features and bugfixes
+** helloSystem is now based on FreeBSD 13.0-RELEASE
+** Completely reworked Live ISO architecture, resulting in 1/3rd boot time and under 800 MB size (fits a CD-ROM)
+** Developer Tools are now a separate download
+** Disk Images are increasingly used throughout the system, such as for application distribution and Linuxulator userland deployment
+** Many new features and GUI utilities to make the desktop more usable for "mere mortals" without the need for a terminal
+
+Installable Live ISO images and a full changelog are available at https://github.com/helloSystem/ISO/releases/tag/r0.7.0
+
+==== Contributing
+
+link:https://github.com/helloSystem/hello/blob/master/CONTRIBUTING.md[The project appreciates contributions in various areas].
diff --git a/website/content/en/status/report-2021-10-2021-12/iwlwifi.adoc b/website/content/en/status/report-2021-10-2021-12/iwlwifi.adoc
new file mode 100644
index 0000000000..7f3bcb6126
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/iwlwifi.adoc
@@ -0,0 +1,23 @@
+=== Intel Wireless driver support
+
+Links: +
+link:https://wiki.freebsd.org/WiFi/Iwlwifi[iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.ORG>
+
+The Intel Wireless driver update project aims to bring support for newer chipsets along with mac80211 LinuxKPI compat code.
+The dual-licensed Intel driver code was ported in the past for the iwm(4) native driver; using the LinuxKPI compat framework allows us to use the driver directly, with only very minor modifications that we hope will be incorporated into the original driver.
+
+During December the driver, firmware, and all remaining LinuxKPI compatibility code were committed to FreeBSD main (HEAD) and merged to the stable/13 branch.
+Further fixes, updates, and improvements will go directly into FreeBSD, meaning the need to apply snapshots is gone and changes can be distributed more timely.
+
+During the last months we tried to ensure that the latest AX210 chipsets are supported.
+The compat code was restructured both to be able to better trace and debug the mac80211 compatibility layer, but also to keep the net80211 and mac80211 state machines for stations better in sync.
+
+While we keep updating the driver and all the compat code needed for that, the focus remains on stability and adding support for newer 802.11 standards.
+The driver is still set to 11a/b/g-only and 11n will be next before we look at 11ac.
+
+With the code in FreeBSD git we anticipate broader testing and with that also some fallout.
+For the latest state of the development, please follow the referenced wiki page and the freebsd-wireless mailing list.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2021-10-2021-12/kde.adoc b/website/content/en/status/report-2021-10-2021-12/kde.adoc
new file mode 100644
index 0000000000..fdcfa405af
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/kde.adoc
@@ -0,0 +1,38 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] +
+link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project aims to package the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree.
+That includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@ as well, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine.
+
+
+* Just two CMake updates this quarter, ending up with CMake 3.22.1. Some more patches have landed upstream, and CMake is soon to switch to `share/man` for manpages on FreeBSD. When it does, there will be plenty of `pkg-plist` churn.
+* Monthly releases of KDE Frameworks, KDE Plasma, and KDE Gear kept the exp-runs going. kde@ would like to thank Antoine for overseeing our many exp-run requests. We are now at KDE Frameworks 5.89 (latest release as of December 2021), link:https://kde.org/announcements/plasma/5/5.23.4/[KDE Plasma Desktop 5.23.4] and link:https://kde.org/announcements/gear/21.12.0/[KDE Gear 21.12].
+* Qt 5 is not receiving any open source updates from the Qt Company, but the KDE Community maintains its own set of patches that backport many fixes from Qt 6. Work is underway to import the KDE patch collection.
+* Qt 6 remains tantalizingly close. There hasn't been real progress on the crash-on-exit problem, though.
+* *deskutils/kalendar* is a relatively new port that uses KDE technologies for a desktop (appointments) calendar.
+* *deskutils/latte-dock*, an alternative launcher for KDE Plasma (and other environments) was updated to each of its bugfix releases.
+* *devel/qbs* and *devel/qtcreator* were updated. Qbs (or "Qt Build System") is a declarative build system styled along the lines of declarative QML programs. (Note that Qbs is not used by Qt itself).
+* *graphics/digikam* was updated to the latest release and now supports both ImageMagick 6 and ImageMagick 7. Speaking of which, a new `USES=magick` was introduced to simplify ports that depend in ImageMagick.
+* *graphics/ksnip*, one of several screenshot-applications for KDE Plasma (and other environments) had a lots-of-bugfixes update.
+* *graphics/skanpage* is a new port that scans multiple pages and produces a PDF of the whole.
+* *multimedia/qt5-multimedia* now ignores gstreamer-gl (rather than implicitly building with it as a dependency if it is installed a build time).
+* *net-im/ruqola* is a Rocket Chat client, updated to the latest release.
+* *security/qtkeychain* has a new release.
+
+Elsewhere in the software stack, kde@ also maintains ports that support the desktop in general. Some highlights are:
+
+* *devel/libphonenumber* keeps chasing changes to the world's phone numbers (the FreeBSD foundation can be reached at +1.720.207.5142).
+* *graphics/poppler* updated this much-used PDF-rendering library.
+* *multimedia/pipewire*, the audio-and-video successor to pulseaudio, was updated and now supports SSL as well.
+* *net/py-pytradfri* got several updates so you can control your lights from FreeBSD.
+* *print/freetype2* was updated to the latest release; relatedly, there was am update to *x11-toolkits/libXft*.
+* *print/harfbuzz*, the text-shaping library, was updated for more font type support.
+* *sysutils/bsdisks* is an implementation of DBus interfaces for examining disks (drives, partitions, etc.). It is also used for removable-disk notifications.
+* *x11-themes/adwaita-qt*, which connects the adwaita theme engine to Qt-based applications, was updated.
diff --git a/website/content/en/status/report-2021-10-2021-12/lldb.adoc b/website/content/en/status/report-2021-10-2021-12/lldb.adoc
new file mode 100644
index 0000000000..6ed5b3d60b
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/lldb.adoc
@@ -0,0 +1,40 @@
+=== LLDB Debugger Improvements
+
+Links: +
+link:https://www.moritz.systems/blog/freebsd-kgdb-support-in-lldb/[Moritz Systems Project Description] URL: link:https://www.moritz.systems/blog/freebsd-kgdb-support-in-lldb/[https://www.moritz.systems/blog/freebsd-kgdb-support-in-lldb/] +
+link:https://www.moritz.systems/blog/lldb-serial-port-communication-support/[Progress Report 3] URL: link:https://www.moritz.systems/blog/lldb-serial-port-communication-support/[https://www.moritz.systems/blog/lldb-serial-port-communication-support/] +
+link:https://www.moritz.systems/blog/lldb-freebsd-kernel-core-dump-support/[Progress Report 4] URL: link:https://www.moritz.systems/blog/lldb-freebsd-kernel-core-dump-support/[https://www.moritz.systems/blog/lldb-freebsd-kernel-core-dump-support/] +
+link:https://github.com/moritz-systems/llvm-project[LLVM Git Repository] URL: link:https://github.com/moritz-systems/llvm-project[https://github.com/moritz-systems/llvm-project] +
+link:https://github.com/moritz-systems/libfbsdvmcore[libfbsdvmcore Git Repository] URL: link:https://github.com/moritz-systems/libfbsdvmcore[https://github.com/moritz-systems/libfbsdvmcore]
+
+Contact: Kamil Rytarowski <kamil@moritz.systems> +
+Contact: Michał Górny <mgorny@moritz.systems>
+
+According to the upstream description, "LLDB is a next generation,
+high-performance debugger. It is built as a set of reusable components which
+highly leverage existing libraries in the larger LLVM Project, such as the
+Clang expression parser and LLVM disassembler."
+
+FreeBSD includes LLDB in the base system.  At present, it has some limitations
+compared to the GNU GDB debugger, and does not yet provide a complete
+replacement.  This project spans from July 2021 to January 2022 and aims to
+make LLDB suitable for debugging FreeBSD kernels.
+
+The earlier part of the project was focused on improving compatibility between
+LLDB and other servers implementing the GDB Remote Protocol.  This was followed
+by implementing a fully-featured serial port support and then support
+for FreeBSD kernel core dumps (vmcores).
+
+The LLDB client gained much improved support for connecting to the remote
+server over a serial port, and the LLDB server gained support for accepting
+communication over a serial port.  This opened the possibility of using LLDB
+to debug embedded devices that use the RS232 interface.  It can also aid
+debugging kernels on regular PCs as it does not rely on the network stack.
+
+Support for FreeBSD vmcores has also been added to LLDB.  This makes it
+possible to inspect the crashed kernel state without having to resort to KGDB
+or manually convert the vmcore into the standard ELF format supported by LLDB.
+
+The introduced changes are expected to be shipped with LLDB 14.0.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2021-10-2021-12/ls1027a.adoc b/website/content/en/status/report-2021-10-2021-12/ls1027a.adoc
new file mode 100644
index 0000000000..a1c60beb94
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/ls1027a.adoc
@@ -0,0 +1,35 @@
+=== NXP LS1028A/1027A SoC support
+
+Contact: Kornel Dulęba <mindal@semihalf.com> +
+Contact: Artur Rojek <ar@semihalf.com> +
+Contact: Hubert Mazur <hum@semihalf.com> +
+Contact: Wojciech Macek <wma@semihalf.com>
+
+The Semihalf team has been working on adding the FreeBSD support for the link:https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-processors/layerscape-1028a-applications-processor:LS1028A[NXP LS1028A] SoC, as well as its GPU-less variant (NXP LS1027A).
+
+NXP LS1028A/LS1027A SoC is a dual-core 64-bit ARMv8 Cortex-A72 application processor with high-speed peripherals such as 2 Time-Sensitive Networking-capable (TSN) Ethernet controllers, quad-port TSN-enabled switch, PCIE, SD/MMC, USB3.0 and others.
+
+The original support was extended in the following way:
+
+* ENETC Ethernet link:https://cgit.freebsd.org/src/log/sys/dev/enetc[driver]
+** Add support for PHY interrupts
+** Fix VID/mcast address hash calculation
+** Serialize MDIO transactions
+** Allow loading driver as a module
+* Improvements in the link:https://cgit.freebsd.org/src/log/sys/dev/sdhci/sdhci_fsl_fdt.c[FSL SDHCI driver]
+** Add support for HS200/HS400 modes
+** Add full support for software reset
+** Provide more accurate clk calculation
+** Implement pulse width detection errata
+** Fix vccq reconfiguration
+* FLEX SPI NOR controller link:https://cgit.freebsd.org/src/log/sys/dev/flash/flexspi/flex_spi.c[driver]
+* Additional features:
+** TMP461 thermal sensor link:https://cgit.freebsd.org/src/log/sys/dev/iicbus/tmp461.c[driver]
+** PCF85063 RTC driver link:https://cgit.freebsd.org/src/log/sys/dev/iicbus/rtc/pcf85063.c[driver]
+** TCA6408 I2C GPIO expander link:https://cgit.freebsd.org/src/log/sys/dev/iicbus/gpio/tca6408.c[driver]
+
+TODO:
+
+* Improve MMC HS200/HS400 support for other SoCs using the FSL SDHCI controller.
+
+Sponsor: Alstom Group
diff --git a/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc b/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc
new file mode 100644
index 0000000000..814598c6aa
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc
@@ -0,0 +1,103 @@
+=== sched_getcpu(2), membarrier(2), and rseq(2) syscalls
+
+Contact: Konstantin Belousov <kib@FreeBSD.org>
+
+Links: +
+link:https://kib.kiev.ua/kib/membarrier.pdf[Linux manpage for membarrier(2)] URL: link:https://kib.kiev.ua/kib/membarrier.pdf[https://kib.kiev.ua/kib/membarrier.pdf] +
+link:https://reviews.freebsd.org/D32360[membarrier(2) implementation] URL: link:https://reviews.freebsd.org/D32360[https://reviews.freebsd.org/D32360] +
+link:https://kib.kiev.ua/kib/rseq.pdf[Linux manpage for rseq(2)] URL: link:https://kib.kiev.ua/kib/rseq.pdf[https://kib.kiev.ua/kib/rseq.pdf] +
+link:https://reviews.freebsd.org/D32505[rseq(2) and userspace bindings implementation] URL: link:https://reviews.freebsd.org/D32505[https://reviews.freebsd.org/D32505]
+
+Linux provides a set of syscalls that allow to develop mostly
+syscall-less scalable algorithms in userspace.  The mechanisms are
+based on optimistic execution using CPU-local data with the assumption that
+rare events like context switches or signal delivery do not occur
+for the given calculation, and if they do occur, rollback and restart
+is performed.  This very high-level approach is used, as I understand,
+for implementation of tools like URCU, fast malloc allocators
+(tcmalloc) and other userspace infrastructure projects aimed at
+large partitioned machines.
+
+For instance, sched_getcpu(2) syscall returns the CPU id of the CPU
+where the current thread is currently executing.  On amd64, if
+available, we use a RDTSCP or RDPID instruction to query the CPU id without
+changing CPU mode, otherwise this is a light-weight syscall.  Of
+course, the answer provided is obsolete the moment it is created,
+even before it is returned to userspace.  But it allows seeding values
+in some structures that are valid for a long time (at the
+CPU speed scale) and are automatically corrected on exceptional
+control flow events like context switches, and userspace can either detect
+and rollback or sync and rollback with the exceptions.
+
+There are two cornerstone syscalls that allow userspace to implement
+these efficient algorithms: membarrier(2) and rseq(2).
+
+Membarrier is a facility that helps implementing fast CPU ordering
+barriers, typically used for asymmetric/biased locking.  In these lock
+implementation schemes, the owner of the object often assumes that there
+are contenders/parallel threads that need coordinating with.  If some
+thread starts accessing the same resource, then it is its duty to
+ensure correctness.  Examples of 'traps' that fast code path
+utilize are reads from a dedicated page that is unmapped by contenders,
+to switch the fast path to the slow one.  Or we could send a signal to all
+threads that potentially have access to that object, to insert a
+barrier.  Or we can use the membarrier(2) facility, which incurs
+significantly less overhead than signalling all threads.
+
+Membarrier(2) inserts a barrier, which is the typical underlying
+hardware operation to ensure ordering, into the specified set of CPUs,
+if these CPUs are executing the specified thread.  If these CPUs are not executing
+the targeted threads, it is assumed that sequential consistency guarantees
+from the context switch are enough to fulfill the requirement of
+membarrier(2).  Overall, the fast path can be implemented without slow
+instructions, and the slow path injects required fences into the fast path at
+the cost of IPI.
+
+The facility to detect exceptional conditions in the userspace thread
+execution was developed in Linux and called rseq(2).  It is a feature
+often called Restartable Atomic Sequences, which explains the acronym.
+The ability to cheaply do that allows code longer than a single
+instruction to execute atomically, without the need to propose and
+implement unsafe operations like disabling preemption, which is not
+feasible for userspace.  For instance, code might use CPU-local
+resources, which otherwise does not cope well with context switches.
+There cannot be an analog of critical_enter(9) in userspace.  (A
+facility to cheaply block signal delivery exists in FreeBSD, see
+sigfastblock(2), but correctly using it is provably too hard to
+implement in general-purpose code, esp. because it requires
+version-dependent coordination with rtdl and libthr.)
+
+rseq(2) takes per-thread block of memory, where the thread writes the
+current CPU id (see sched_getcpu(2)) and specifies the block of
+critical code that must be unwound if an exceptional situation like a
+context switch occurred while the block was executing.  The fast code
+path uses per-cpu data and typically does not need any corrections,
+but would a context switch occur, transfer of control to the abort
+handler informs userspace about the event.  So instead of disabling
+context switches, code can cheaply check for one after the calculation
+and retry if needed.
+
+An interesting rseq(2) implementation detail is that it is
+impossible (and not needed) to access/update rseq structures from
+kernel during the actual context switch, because we cannot access
+userspace from under a spinlock.  In other words,
+threads using rseq do not incur any performance cost from
+system-global context switches.  Instead, if the process registered for
+rseq(2), on any return to user mode we check if any exceptional
+events happened while the thread was in the kernel (context switches may happen
+only while the thread is in kernel mode), and if a context switch indeed
+occurred, we fire an ast to check whether the program counter is inside the
+critical section and jump to the abort handler if it is.
+
+The implementations of membarrier(2) and rseq(2) are clean-room: I used
+Linux manual pages as the reference and public discussions of the
+features for clarifying corner cases.  On Linux/glibc, there was no
+stable glibc interface to the rseq facility.  One proposed integration was
+committed then reverted from glibc.  It might be prudent to wait
+some more for the rseq(2) interface to stabilize in glibc before providing
+it in our libc or to rely on tight integration between kernel
+and userspace in our base system, and use ABI tricks like symbol
+versioning to evolve the interface.  There is no goal to be 100%
+compatible with Linux anyway.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2021-10-2021-12/ocf-wg.adoc b/website/content/en/status/report-2021-10-2021-12/ocf-wg.adoc
new file mode 100644
index 0000000000..bad8fe033d
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/ocf-wg.adoc
@@ -0,0 +1,20 @@
+=== Kernel Crypto changes to support WireGuard
+
+Contact: John Baldwin <jhb@FreeBSD.org>
+
+During the past few months, I merged several changes to the kernel to better
+support the WireGuard driver.  These include extensions to the 'struct
+enc_xform' interface to better support AEAD ciphers, changes to 'struct
+enc_xform' to support multi-block operations for improved performance, and the
+addition of the XChaCha20-Poly1305 AEAD cipher suite to OCF.  Additionally, the
+kernel now includes a new "direct" API for ChaCha20-Poly1305 operations on
+small, flat buffers.  A change in review adds an API to support curve25519
+operations.  With these changes, the WireGuard driver is mostly able to use
+crypto APIs from the kernel rather than its internal implementations.
+
+In parallel I have been updating the WireGuard driver to use the new
+APIs verifying interoperability with the existing driver.  One of the
+next tasks is to refine these changes (along with some minor bug
+fixes) as candidates for upstreaming into the WireGuard driver.
+
+Sponsor: The FreeBSD Foundation
\ No newline at end of file
diff --git a/website/content/en/status/report-2021-10-2021-12/office.adoc b/website/content/en/status/report-2021-10-2021-12/office.adoc
new file mode 100644
index 0000000000..9d28d0bcf7
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/office.adoc
@@ -0,0 +1,26 @@
+=== FreeBSD Office Team
+
+Links: +
+link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[https://wiki.freebsd.org/Office]
+
+Contact: FreeBSD Office team ML <office@FreeBSD.org> +
+Contact: Dima Panov <fluffy@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+The FreeBSD Office team works on a number of office-related software suites and tools such as OpenOffice and LibreOffice.
+
+Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users.
+
+Latest and quarterly ports branches got a new branch (7.2) of the LibreOffice suite and updated to the 7.2.4 release while new preleases
+such as 7.2.5.RC2 and 7.3.0.RC1 are cooking in the WIP stage area.
+
+Meanwhile, our link:https://github.org/freebsd/freebsd-ports-libreoffice[WIP repository] got back a working CI instance again, thanks to Li-Wen Hsu.
+
+Also we are still working on the link:https://github.com/fluffykhv/freebsd-ports-boost[Boost WIP repository] to bring the latest Boost library to the ports.
+
+We are looking for people to help with the open tasks:
+
+* The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=office%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailreporter1=1&emailtype1=substring&query_format=advanced&list_id=374316[open bugs list] contains all filed issues which need some attention
+* Upstream local patches in ports
+
+Patches, comments and objections are always welcome in the mailing list and bugzilla.
diff --git a/website/content/en/status/report-2021-10-2021-12/openssh.adoc b/website/content/en/status/report-2021-10-2021-12/openssh.adoc
new file mode 100644
index 0000000000..36bebd2fb9
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/openssh.adoc
@@ -0,0 +1,25 @@
+=== Base System OpenSSH Update
+
+Links: +
+link:https://www.openssh.com/[OpenSSH] URL: link:https://www.openssh.com/[https://www.openssh.com/] +
+link:https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html[Announcement to freebsd-security@] URL: link:https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html[https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html]
+
+Contact: Ed Maste <emaste@freebsd.org>
+
+OpenSSH, a suite of remote login and file transfer tools, was updated from
+version 8.7p1 to 8.8p1 in the FreeBSD base system.
+
+*NOTE*:
+OpenSSH 8.8p1 disables the ssh-rsa signature scheme by default.
+For more information please see the
+link:https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html[Important
+note for future FreeBSD base system OpenSSH update] mailing list post.
+
+OpenSSH supports
+link:https://en.wikipedia.org/wiki/FIDO2_Project[FIDO]/link:https://en.wikipedia.org/wiki/Universal_2nd_Factor[U2F]
+devices, and support is now enabled in the base system.
+
+Next steps include integrating U2F key devd rules into the base system,
+and merging the updated OpenSSH and FIDO/U2F support to stable branches.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2021-10-2021-12/portmgr.adoc b/website/content/en/status/report-2021-10-2021-12/portmgr.adoc
new file mode 100644
index 0000000000..d59e709bd1
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/portmgr.adoc
@@ -0,0 +1,36 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL: link:https://www.FreeBSD.org/ports/[https://www.FreeBSD.org/ports/] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[https://www.freebsd.org/portmgr/] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+We currently have 46,700 ports in the Ports Collection according to FreshPorts.
+There are currently 2,666 open ports PRs of which 611 are unassigned.
+This quarter saw 9,535 commits from 166 committers on the main branch and 644 commits from 62 committers on the quarterly branch.
+Compared to last quarter, this means a slight drop in the number of commits although more committers were active, and a slight increase in the number of open PRs.
+
+During the last quarter, we welcomed Dries Michiels (driesm@) and said goodbye to kuriyama@ and fjoe@.
+There was also a change in portmgr: adamw@ stepped down after five years of service and tcberner@ is now a full member of portmgr@.
+
+Three new USES were introduced:
+
+* magick to handle dependencies on ImageMagick
+
+* nodejs to provide support for NodeJS (with a new default version NODEJS=lts)
+
+* trigger to handle pkg triggers using the TRIGGERS variable
+
+The default version of PGSQL switched to 13.
+Furthermore, INSTALLS_ICONS has been replaced by a trigger on gtk-update-icon-cache and the macro is no longer functional.
+
+As always, there were some updates to "big" packages: pkg was updated to 1.17.5, Chromium to 94.0.4606.81_3, and Firefox to 95.0.2_1,2.
+Ruby 3.1.0 and Python 3.11 are now available for use by users and other ports.
diff --git a/website/content/en/status/report-2021-10-2021-12/pot.adoc b/website/content/en/status/report-2021-10-2021-12/pot.adoc
new file mode 100644
index 0000000000..aee15c4a5a
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/pot.adoc
@@ -0,0 +1,28 @@
+=== Containers & FreeBSD: Pot, Potluck & Potman
+
+Links: +
+link:https://pot.pizzamig.dev[Pot on github] URL: link:https://github.com/pizzamig/pot[https://github.com/pizzamig/pot] +
+link:https://potluck.honeyguide.net/[Potluck Repository & Project] URL: link:https://potluck.honeyguide.net/[https://potluck.honeyguide.net/] +
+link:https://github.com/hny-gd/potluck[Potluck on github] URL: link:https://github.com/hny-gd/potluck[https://github.com/hny-gd/potluck] +
+link:https://github.com/grembo/potman[Potman on github] URL: link:https://github.com/grembo/potman[https://github.com/grembo/potman]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> +
+Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+In the last quarter, a new release link:https://github.com/pizzamig/pot/releases/tag/0.14.0[0.14.0] with a number of fixes and features like the new copy-in-flv command was made available.
+
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+Here we again had a busy quarter. All images have been rebuilt for FreeBSD 12.3 and pot 0.13.0. +
+Also the images that can be used to build a virtual data center like link:https://potluck.honeyguide.net/blog/nomad-server/[Nomad], link:https://potluck.honeyguide.net/blog/consul/[Consul] and link:https://potluck.honeyguide.net/blog/vault/[Vault] have received a lot more tender love and care and are meanwhile in pre-production use on a cluster at a fintech. +
+Not all these changes have yet been committed to the github repository though, this is planned for the next quarter.
+Additionally, new images like link:https://github.com/hny-gd/potluck/tree/master/openldap[multi-master OpenLDAP] have been added, too.
+
+Potman aims to simplify building Pot images with Vagrant and VirtualBox based on the Potluck approach, e.g. as part of a DevOps workflow for software development including testing and publishing them to a repository.
+
+Here we have not yet made a lot of headway with our plan to utilise Potman in the Potluck library build process but this is still on our TODO-list, like improving the documentation for using the Virtual DC images from the Potluck library.
+
+As always, feedback and patches are welcome.
diff --git a/website/content/en/status/report-2021-10-2021-12/vdso.adoc b/website/content/en/status/report-2021-10-2021-12/vdso.adoc
new file mode 100644
index 0000000000..5768a65ec6
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/vdso.adoc
@@ -0,0 +1,82 @@
+=== VDSO on amd64
+
+Contact: Konstantin Belousov <kib@FreeBSD.org>  
+
+A VDSO, or Virtual Dynamic Shared Object, is a shared object (more
+commonly called dynamic library) that is inserted into the executed
+image by a joint effort of the kernel and the dynamic linker.  It does
+not exists on disk as a standalone .so, and there are no instructions
+in the ELF format that cause the insertion.  It is done by the system
+to implement some functionality for the C runtime implementation
+components.
+
+FreeBSD already has a lot of features typically done using VDSO (in
+Linux), but really not requiring that complication.  The main reason
+why it is possible is the often mentioned co-evolution of the kernel
+and C runtime.  We can naturally introduce features that require
+implementation both in kernel, and support in the userspace parts,
+since FreeBSD is developed as a whole.  Surprisingly, it also allows
+the kernel and dynamic linker to know much less (and not enforce
+anything) about userspace consumers of interfaces.
+
+For instance, a syscall-less wall clock was implemented long ago, by
+the kernel providing a time hands blob in the shared page, and the C
+library knowing about its location and the supported algorithms.
+There is no need for a VDSO that interposes some libc symbols or
+provides services that are named by known symbols to userland.
+
+From all the years of experience with this pseudo-VDSO approach, the
+only feature that was impossible to implement without providing real
+VDSO support was the signal trampoline DWARF annotations, for the
+benefit of stack unwinders.
+
+When the kernel delivers signal to userland, it changes some key
+registers (like the instruction pointer, the stack pointer, and
+whatever else is needed by the architecture) and pushes the saved
+image of the whole usermode CPU state (context) onto the user stack.
+Then, control is passed to a small piece of code located in the shared
+page (signal trampoline), which calls the user handler function and on
+return from the handler issues a sigreturn(2) syscall to reload the
+old context.
+
+From this description, it is clear that the state of the machine
+during trampoline execution is quite different from the normal C
+calling frames.  Unwinders that handle things like C++ exceptions,
+Rust panics, or other similar mechanisms in specific language
+runtimes, need to understand the specialness of the trampoline frame.
+The current approach is to hardcode the detection of the trampoline,
+e.g. by matching the instruction pointer against sysctl
+kern.proc.sigtramp.
+
+DWARF annotations are enough to provide the required information to
+unwinders to make the trampoline frame not special anymore, but the
+problem is that there is no way for unwinders to find the annotation
+without introducing even more specialness.  Instead, we can insert a
+VDSO that only serves to appear in the enumeration of DSOs loaded into
+the process, with either dl_iterate_phdr(3) (in-process) or r_debug
+(remote), with PT_GNU_EH_FRAME header pointing to the root of DWARF
+info.
+
+This is exactly what the VDSO on FreeBSD does: it wraps signal
+trampoline bits and their DWARF annotation (.cfi) into a shared
+object, which is put into the shared page and linked by rtld(1) into
+the set of preloaded objects upon image activation.
+
+Efforts were made to strip as many unneeded structures and as much
+padding as possible from the VDSO image, because it consumes space in
+the shared page.  It was pushed as far as the common denominator of
+lld and ld.bfd allowed, with several tricks done by linker scripts and
+some use of seemingly undocumented linker options.
+
+We need at least two VDSOs for amd64: a 64-bit one for native binaries
+and a 32-bit one for ia32 binaries.  With the size of each VDSO around
+1.5KB, space becomes really tight in the shared page, which needs
+space for other stuff as well, like timehands or random generator
+seeds.
+
+Build scripts enforce that VDSOs do not grow larger than 2K; if they
+do, we need to extend shared page to become at least two shared pages.
+Scripts also enforce that VDSO are pure position-independent, not
+requiring relocations for either code or metadata (.cfi).
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2021-10-2021-12/www.adoc b/website/content/en/status/report-2021-10-2021-12/www.adoc
new file mode 100644
index 0000000000..fb99dd5279
--- /dev/null
+++ b/website/content/en/status/report-2021-10-2021-12/www.adoc
@@ -0,0 +1,25 @@
+=== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
++
+Activate an edit link in the Documentation (books/articles) pointing to GitHub and encouraging GitHub pull requests. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Work in progress_)
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Not started_)
diff --git a/website/content/en/status/report-2022-01-2022-03/_index.adoc b/website/content/en/status/report-2022-01-2022-03/_index.adoc
new file mode 100644
index 0000000000..31ad7d85e7
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/_index.adoc
@@ -0,0 +1,152 @@
+---
+title: "FreeBSD Quarterly Status Report First Quarter 2022"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2022-01-2022-03
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+Entries from the various official and semi-official teams, as found in the
+link:../../administration/[Administration Page].
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+Projects that span multiple categories, from the kernel and userspace to the
+Ports Collection or external projects.
+
+include::{reports-path}/accessibility.adoc[]
+
+'''
+
+include::{reports-path}/boot-performance.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+Updates to kernel subsystems/features, driver support, filesystems, and more.
+
+include::{reports-path}/ena.adoc[]
+
+'''
+
+include::{reports-path}/gunion.adoc[]
+
+'''
+
+include::{reports-path}/rtw88.adoc[]
+
+'''
+
+include::{reports-path}/iwlwifi.adoc[]
+
+'''
+
+include::{reports-path}/ocf-wg.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+Updating platform-specific features and bringing in support for the new hardware
+platform.
+
+include::{reports-path}/dpaa2.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+Noteworthy changes in the documentation tree, man-pages, or new external
+books/documents.
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+Changes affecting the Ports Collection, whether sweeping changes that touch most
+of the tree, or individual ports themselves.
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/office.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/portconfig.adoc[]
+
+'''
+
+include::{reports-path}/wifibox.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+Many projects build upon FreeBSD or incorporate components of FreeBSD into their
+project. As these projects may be of interest to the broader FreeBSD community,
+we sometimes include brief updates submitted by these projects in our quarterly
+report. The FreeBSD project makes no representation as to the accuracy or
+veracity of any claims in these submissions.
+
+include::{reports-path}/hellosystem.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
+
+'''
+
+include::{reports-path}/fpart.adoc[]
diff --git a/website/content/en/status/report-2022-01-2022-03/accessibility.adoc b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc
new file mode 100644
index 0000000000..f30384fed2
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc
@@ -0,0 +1,20 @@
+=== FreeBSD Accessibility
+
+Links: +
+link:https://wiki.freebsd.org/Accessibility[Accessibility wiki page] URL: link:https://wiki.freebsd.org/Accessibility[https://wiki.freebsd.org/Accessibility] +
+link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[List introduction, goals, audience, and ground rules] URL: link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html]
+
+Contact: Pau Amma <pauamma@gundo.com> +
+Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org>
+
+Over the past several months, I've started putting together tools and resources to help make the FreeBSD ecosystem (more) accessible to people with disabilities:
+
+* a link:https://lists.freebsd.org/subscription/freebsd-accessibility[mailing list]
+* a link:https://wiki.freebsd.org/Accessibility[set of wiki pages] including link:https://wiki.freebsd.org/Accessibility/Resources[resources] and a link:https://wiki.freebsd.org/Accessibility/Wishlist[categorized wish list]
+* tooling including a link:https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=accessibility&list_id=471790&resolution=---[searchable accessibility Bugzilla keyword] and an link:https://reviews.freebsd.org/project/profile/87/[accessibility Phabricator group]
+
+I need all the help I can get with:
+
+* specifying, designing, implementing, and testing the items on the wishlist
+* adding to the wishlist in areas were have little or no experience or for things I missed
+* moving beyond software and documentation to processes and culture
diff --git a/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc
new file mode 100644
index 0000000000..cb159b69f6
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc
@@ -0,0 +1,28 @@
+=== Boot Performance Improvements
+
+Links: +
+link:https://wiki.freebsd.org/BootTime[Wiki page] URL: link:https://wiki.freebsd.org/BootTime[https://wiki.freebsd.org/BootTime] +
+link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[OS boot time comparison] URL: link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+Colin Percival is coordinating an effort to speed up the FreeBSD boot process.
+For benchmarking purposes, he is primarily using an EC2 c5.xlarge instance as a reference platform and is measuring the time between when the virtual machine enters the EC2 "running" state and when it is possible to SSH into the instance.
+
+This work started in 2017, and as of the end of December 2021 the FreeBSD boot time was reduced from approximately 30 seconds to approximately 10 seconds.
+During 2022Q1, further improvements have shaved more time off the boot process, taking it down to roughly 8 seconds
+
+Two major issues remain outstanding:
+
+. The first time an EC2 instance boots, dhclient takes about 2 seconds longer than normal to get an IPv4 address.  The cause of this is unknown and requires investigation.
+
+. IPv6 configuration includes two one-second-long sleep(1) invocations, one from /etc/rc.d/netif and the other from /etc/rc.d/rtsold.
+It might be possible to simply remove these; but care is needed to avoid progressing too far in the boot process before IPv6 addresses are configured.
+Input from IPv6 experts is required here.
+
+Issues are listed on the wiki page as they are identified; the wiki page also has instructions for performing profiling.
+Users are encouraged to profile the boot process on their own systems, in case they experience delays which don't show up on the system Colin is using for testing.
+
+This work is supported by Colin's FreeBSD/EC2 Patreon.
+
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2022-01-2022-03/ci.adoc b/website/content/en/status/report-2022-01-2022-03/ci.adoc
new file mode 100644
index 0000000000..87bb1a9da1
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/ci.adoc
@@ -0,0 +1,53 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] +
+link:https://wiki.freebsd.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.freebsd.org/Jenkins[https://wiki.freebsd.org/Jenkins] +
+link:https://wiki.freebsd.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.freebsd.org/HostedCI[https://wiki.freebsd.org/HostedCI] +
+link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.freebsd.org/3rdPartySoftwareCI[https://wiki.freebsd.org/3rdPartySoftwareCI] +
+link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] +
+link:https://lists.freebsd.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.freebsd.org/subscription/dev-ci[https://lists.freebsd.org/subscription/dev-ci]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+The FreeBSD CI team maintains the continuous integration system of the FreeBSD project.
+The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results.
+The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs.
+The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure.
+
+During the first quarter of 2022, we continued working with the contributors and developers in the project to fulfil their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD.
+
+Important changes:
+
+* link:https://ci.freebsd.org/job/FreeBSD-main-amd64-dtrace_test/[DTrace tests] are running with KASAN now.
+* Fixed and resumed the powerpc64le test jobs.
+
+Retired jobs:
+
+* The jobs of main branch on mips* were removed.
+
+Work in progress and open tasks:
+
+* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Collecting and sorting CI tasks and ideas link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[here]
+* Testing and merging pull requests in link:https://github.com/freebsd/freebsd-ci/pulls[the FreeBSD-ci repo]
+* Reducing the procedures of CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Setting up public network access for the VM guest running tests
+* Implementing using bare metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Adding more external toolchain related jobs
+* Improving maturity of the hardware lab and adding more hardware under test
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.freebsd.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc b/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc
new file mode 100644
index 0000000000..c78e7c0543
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc
@@ -0,0 +1,49 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications.
+In this quarter, the team has worked on the following:
+
+* Improved web service performance and security
+** Moved some critical services to newer machines
+** Swept all services to ensure the support of TLS v1.2 and v1.3 and disable v1 and v1.1
+** Enabled dual-stack certificates for the primary FreeBSD web services. +
+   ECDSA and RSA certificates, preferring ECDSA, discussed with secteam@, benefit the project in favor of security and performance matter.
+* Infrastructure improvements at primary site
+** Evicted some very old hardware
+** Moved cluster internal services to newer hardware
+*** Build host
+*** Parts of LDAP, kerberos, DNS and NTP
+* Installed an additional aarch64 package builder
+** ampere3.nyi.freebsd.org
+** Identical specs to ampere[12].nyi.freebsd.org
+* Moved ftp0.nyi.freebsd.org to an aarch64 machine.
+* Main distributed mirror site, download.freebsd.org, enhancements
+** Updated link:https://download.freebsd.org/doc/[offline documentation] (PDF and HTML) in the mirrors. +
+   The old directory `/doc` is now on link:http://ftp-archive.freebsd.org/mirror/FreeBSD-Archive/old-docs/[ftp-archive]; it contains files prior to the Hugo/Asciidoctor migration.
+** Moved ports INDEX files to distributed mirror, download.freebsd.org
+** Removed `/ftp` from the canonical URLs of files on download.freebsd.org. +
+   Old URLs are still valid.
+* Cleanup of Handbook/Mirrors section +
+  Much stale information; now there is more info about the official mirrors and locations. Former official mirrors are now named 'Community mirrors'.
+* Ongoing day to day cluster administration
+** Cluster refresh
+** Replacing failed disks
+** Babysitting pkgsync
+
+Work in progress:
+
+* Improve the package building infrastructure
+* Review the service jails and service administrators operation
+* Set up powerpc pkgbuilder/ref/universal machines
+* Search for more providers that can fit the requirements for a link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] or a link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny mirror]
+* Work with doceng@ to improve https://www.freebsd.org and https://docs.freebsd.org
+* Improve the web service architecture
+* Improve the cluster backup plan
+* Improve the log analysis system
+* Set up Australia mirror
+* Hardware refresh
diff --git a/website/content/en/status/report-2022-01-2022-03/doceng.adoc b/website/content/en/status/report-2022-01-2022-03/doceng.adoc
new file mode 100644
index 0000000000..cc74e6d63a
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/doceng.adoc
@@ -0,0 +1,100 @@
+////
+Quarter:	1st quarter of 2022
+Prepared by:	dbaio
+Reviewed by:	carlavilla
+Last edit:	$Date: 2022-04-09 09:51:36 -0300 (Sat, 09 Apr 2022) $
+Version:	$Id: doceng-2022-1st-quarter-status-report.adoc 221 2022-04-09 12:51:36Z dbaio $
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+No new documentation commit bit was granted during the last quarter, and only one commit bit was safe kept.
+
+Several tasks were completed related to the doc tree during the last quarter:
+
+* Fix some issues in the translation workflow with PO files and Weblate related to the po4a program.
++
+More info link:https://lists.freebsd.org/archives/freebsd-translators/2022-February/000029.html[here].
+
+* Update link:https://download.freebsd.org/doc/[offline documentation (PDF and HTML)].
++
+The old directory /doc is now on link:http://ftp-archive.freebsd.org/mirror/FreeBSD-Archive/old-docs/[ftp-archive]; it contains files prior to the Hugo/Asciidoctor migration.
+
+* Remove Google Analytics from documentation and website.
+
+* Add last modified information to the documentation and website pages.
+
+* Tag FreeBSD docset for 13.1-RELEASE.
+
+* Add the first Indonesian translation to the doc tree.
+
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance]
+
+The translation workflow with Weblate is more mature at this point.
+Several issues were fixed between PO files and po4a program.
+
+We welcome everyone to try our Weblate instance to translate a few documents.
+
+The first Indonesian translation was added to the FreeBSD project.
+We thank Azrael JD for the contribution, and we are looking forward to seeing more Indonesian translations.
+
+===== Q1 2022 Status
+
+* 12 languages (1 new language)
+* 142 registered users
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)
+* Chinese (Traditional) (zh-tw)
+* Dutch (nl)
+* French (fr)
+* German (de)
+* Indonesian (id) - Added
+* Italian (it)
+* Norwegian (nb-no)
+* Persian (fa-ir)
+* Portuguese (pt-br)
+* Spanish (es)
+* Turkish (tr)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Work in progress_)
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Not started_)
diff --git a/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc
new file mode 100644
index 0000000000..b7fdc16a03
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc
@@ -0,0 +1,32 @@
+=== NXP DPAA2 support
+
+Links +
+link:https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[Development] URL: https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2] +
+
+Contact: Dmitry Salychev <dsl@mcusim.org> +
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+Some of the NXP SoCs (LX2160A, LS1088A) are shipped with link:https://www.nxp.com/design/qoriq-developer-resources/second-generation-data-path-acceleration-architecture-dpaa2:DPAA2[DPAA2], the second generation of the data path acceleration architecture.
+It allows to dynamically configure and wire packet processing "objects" (like DPNI for a network interface, DPMAC for media access controller, etc.) together to form a network-on-a-chip.
+
+link:https://solidrun.atlassian.net/wiki/spaces/developer/pages/197494288/HoneyComb+LX2+ClearFog+CX+LX2+Quick+Start+Guide[Honeycomb LX2], as one of the powerful ARM64 boards from SolidRun, is also built around NXP LX2160A and lacks on-board GbE support in FreeBSD.
+These drivers are about to change it.
+
+It's still work in progress and a rough implementation of the drivers for some DPAA2 objects is available at the moment.
+A new network interface (dpni) can be used on Honeycomb for testing.
+
+TODO:
+
+* Update dpaa2_mc_fdt driver for the link:https://www.crowdsupply.com/traverse-technologies/ten64[Traverse Ten64] board
+
+* Review and fix DPAA2 resources allocation to support as many DPNIs as possible
+
+* Free driver resources properly
+
+* Implement CPU affinity for DPIOs and DPNIs
+
+* Implement cached memory-backed software portals
+
+* Profile and mitigate bottlenecks
+
+Sponsor: Bare Enthusiasm :)
diff --git a/website/content/en/status/report-2022-01-2022-03/ena.adoc b/website/content/en/status/report-2022-01-2022-03/ena.adoc
new file mode 100644
index 0000000000..4f2edefd50
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/ena.adoc
@@ -0,0 +1,26 @@
+=== ENA FreeBSD Driver Update
+
+Links: +
+link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README]
+
+Contact: Michal Krawczyk <mk@semihalf.com> +
+Contact: Dawid Gorecki <dgr@semihalf.com> +
+Contact: Marcin Wojtas <mw@semihalf.com>
+
+ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS).
+The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used.
+
+Completed since the last update:
+
+* Add IPv6 layer 4 checksum offload support to the driver
+* Add NUMA awareness to the driver when the RSS kernel option is enabled
+* Rework validation of the Tx request ID
+* Change lifetime of the driver's timer service
+* Avoid reset triggering when the device is unresponsive
+
+Work in progress:
+
+* Prototype the driver port to the iflib framework
+* Tests of the incoming ENA driver release (v2.5.0)
+
+Sponsor: Amazon.com Inc
diff --git a/website/content/en/status/report-2022-01-2022-03/fpart.adoc b/website/content/en/status/report-2022-01-2022-03/fpart.adoc
new file mode 100644
index 0000000000..ecd0a060ff
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/fpart.adoc
@@ -0,0 +1,38 @@
+=== Fpart and fpsync
+
+Links: +
+link:https://www.fpart.org[Project site and documentation] URL: link:https://www.fpart.org[https://www.fpart.org] +
+link:https://github.com/martymac/fpart[Development] URL: link:https://github.com/martymac/fpart[https://github.com/martymac/fpart] +
+link:https://www.freshports.org/sysutils/fpart[Port] URL: link:https://www.freshports.org/sysutils/fpart[https://www.freshports.org/sysutils/fpart]
+
+Contact: Ganael Laplanche <martymac@FreeBSD.org>
+
+==== What is fpart ?
+
+Fpart is a *filesystem partitioner*. It helps you sort file trees and pack them into bags ("partitions").
+
+It uses FreeBSD's fts(3) implementation (GNU/Linux builds can also use it as an option), which makes it crawl filesystems very fast.
+
+A hook facility is provided to trigger actions on the partitions produced.
+
+==== What is fpsync ?
+
+Fpsync is a companion script that uses fpart under the hood to parallelize rsync(1) or cpio(1) jobs, making it a simple but powerful data migration tool. Those jobs can be run either locally or remotely (using SSH). Fpsync is link:https://www.fpart.org/links/[often used by researchers and cloud providers] where lots of data need to be moved and clusters are available to speed up transfers.
+
+==== Q1 2022 Status
+
+Both tools continued to evolve and saw several bugs fixed; see the link:https://www.fpart.org/changelog/[changelog].
+
+Also, a user reported a major bug regarding our fts(3) implementation, which ignores readdir(3) errors. I have reported the bug in our Bugzilla:
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262038[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262038]
+
+It should be merged soon (hopefully).
+
+Last but not least, fpart has been link:https://sill.etalab.gouv.fr/fr/software?id=229[referenced in the French Government's 'SILL'].
+
+==== Contributing
+
+If you are interested in contributing, have a look at the link:https://github.com/martymac/fpart/blob/master/TODO[TODO list].
+
+Any contribution is welcome, more especially in the field of unit testing.
diff --git a/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc
new file mode 100644
index 0000000000..fad2959648
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc
@@ -0,0 +1,145 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] +
+link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] +
+link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] +
+link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] +
+link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits.
+We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts.
+We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+Here are some highlights from the Foundation for the first quarter of 2022.
+
+==== Fundraising Efforts
+
+As promised, we updated our fundraising meter for 2022. So far, we’ve raised over $84,000 towards our 2022 goal of $1,400,000.
+We’d like to thank our individual and corporate donors for supporting our efforts this year.
+We’d also like to give a big shout out to our Gold Sponsor, Facebook, Silver Sponsors, VMware and Tarsnap, and the companies that provide free hosting for the Project: Bytemark, 365 Data Centers, NYI, NextArray, Sentex Data Communications, and the Computer Science Department at NCTU.
+
+You can find out how we spent your donations by reading about what we supported in Q1, in this report, and our Spring Newsletter.
+
+If you haven’t made a donation this year, please consider making a donation now at https://freebsdfoundation.org/donate/.
+
+We also have a Partnership Program for larger commercial donors. You can find out more at https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
+
+==== OS Improvements
+
+During the first quarter of 2022, 372 src, 41 ports, and 16 doc tree commits were made that identified The FreeBSD Foundation as a sponsor.
+# This represents 16, 0.4, and 5% of the total number of commits in each repository.
+
+You can read about Foundation-sponsored projects in individual quarterly report entries:
+
+* Crypto changes for WireGuard
+* Intel Wireless driver support
+
+Here is a small sample of other base system improvements from Foundation developers this quarter that do not have separate report entries.
+
+==== riscv: Add support for enabling SV48 mode
+
+SV48 is intended for systems for which a 39-bit virtual address space is insufficient.  This change increases the size of the user map from 256GB to 128TB.
+The kernel map is left unchanged for now.
+
+For now SV48 mode is left disabled by default, but can be enabled with a tunable.
+Note that extant hardware does not implement SV48, but QEMU does.
+
+* In pmap_bootstrap(), allocate a L0 page and attempt to enable SV48 mode.
+  If the write to SATP doesn't take, the kernel continues to run in SV39 mode.
+* Define VM_MAX_USER_ADDRESS to refer to the SV48 limit.
+  In SV39 mode, the region [VM_MAX_USER_ADDRESS_SV39, VM_MAX_USER_ADDRESS_SV48] is not mappable.
+
+==== Add v3 support to CTF tools
+
+CTF, the Compact C Type Format, is a representation of type information most often contained within ELF binaries.
+This type information is helpful for probing tools like DTrace.
+Recent work by Mark Johnston allows different Dtrace providers like the FBT (Function Boundary Tracing) provider to work with version 3 of CTF.
+
+==== FreeBSD on the Framework Laptop
+
+Two Foundation staff members, Ed Maste and Mark Johnston, as well as a few developers and community members now each have access to Framework laptops, which are designed to make hardware upgrades, repairs, and customizations straightforward for the average user.  The goal of this work is to ensure that the experience running FreeBSD on the laptops matches the stability that FreeBSD users expect.
+
+Recent improvements and fixes include:
+
+* Making audio switch appropriately between speakers and the headphone jack when headphones are plugged in or unplugged
+* Fixing bug 259230, which would cause a Framework laptop to reboot or power off when the touchpad was used.
+* Adding the Tempo Semiconductor 92HD95B HDA codec ID
+* Temporarily fixing stalled usb enumeration, bluetooth, and S3 resume.  The temporary fix is to avoid attaching to several newer Intel controllers, which require firmware to be loaded, which is different from that implemented by ng_ubt_intel and iwmbtfw, so they are not usable yet.
+* Avoiding a 16 second boot delay, by probing the TSC frequency earlier.  This lets us use the TSC to implement early DELAY, limiting the use of the sometimes-unreliable 8254 PIT.
+
+You can follow news about FreeBSD work on the Framework laptop at: https://wiki.freebsd.org/Laptops/Framework_Laptop.
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project.
+
+==== Supporting FreeBSD Infrastructure
+
+The Foundation provides hardware and support for the Project.
+At the time of writing, the server that will become the new Australian mirror has arrived in Australia, has a fresh FreeBSD install and will shortly join the cluster.
+
+==== FreeBSD Advocacy and Education
+
+Much of our effort is dedicated to Project advocacy. This may involve
+highlighting interesting FreeBSD work, producing literature, attending
+events, or giving presentations. The goal of the literature we produce
+is to teach people FreeBSD basics and help make their path to adoption
+or contribution easier. Other than attending and presenting at events,
+we encourage and help community members run their own FreeBSD events,
+give presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups.
+We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.
+This all helps provide a healthy ecosystem.
+We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.
+We are continuing to attend virtual events and began planning the June 2022 Developer Summit.
+
+Check out some of the advocacy and education work we did last quarter:
+
+* Committed to hosting a FreeBSD Workshop at SCALE 19x and serve as a Media Sponsor - July 28-31, 2022 in Los Angeles, CA
+
+* Participated in the FLOSS Weekly Podcast - January 5, 2022 https://twit.tv/shows/floss-weekly/episodes/662
+
+* Sent out the 2021 Impact Report showcasing how we supported the Project last year. https://freebsdfoundation.org/blog/2021-freebsd-foundation-impact-report/
+
+* Hosted a stand at FOSDEM 2022 - Videos from the stand can be found at: https://youtube.com/playlist?list=PLugwS7L7NMXxwqIRg1PlhgzhNRi1eVdRQ
+
+* Participated in the Open Source Voices Podcast - Episode to be aired in late April [note from status report team: the episode has indeed be aired and is now available at https://www.opensourcevoices.org/29; unfortunately, there is and will be no transcript.]
+
+* Began planning the June 2022 FreeBSD Developers Summit taking place virtually, June 16-17, 2022 https://wiki.freebsd.org/DevSummit/202206
+
+* Held a new FreeBSD Friday - How to Track FreeBSD Using Git Pt. 2 https://youtu.be/Fe-dJrDMK_0
+
+* Presented at the St. Louis Unix User Group on March 9, 2022 https://ow.ly/1QXn50Ivj75
+
+* Served as Admins and were accepted as a mentoring organization for the 2022 Google Summer of Code
+
+* Held an Office Hours session on Google Summer of Code. https://youtu.be/x-4U1xurmBE
+
+* Hosted a booth at the virtual Open Source 101 conference on March 29, 2022
+
+* New blog posts:
+
+** link:https://freebsdfoundation.org/blog/raid-z-expansion-feature-for-zfs/[RAID-Z Expansion Feature for ZFS In the Home Stretch]
+** link:https://freebsdfoundation.org/blog/whats-ahead-for-freebsd-and-the-foundation-in-2022/[What's Ahead for FreeBSD and the Foundation in 2022]
+** link:https://freebsdfoundation.org/blog/work-with-freebsd-in-google-summer-of-code/[Work with FreeBSD in Google Summer of Code]
+
+* New How-To Guide: link:https://freebsdfoundation.org/freebsd-project/resources/introduction-to-freebsd-jails/[An Introduction to FreeBSD Jails]
+
+* New FreeBSD Journal Article: link:https://freebsdfoundation.org/wp-content/uploads/2022/04/Contributing-to-FreeBSD-Ports-with-Git.pdf[Contributing to FreeBSD ports with Git]
+
+We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal.
+As we mentioned previously, the FreeBSD Journal is now a free publication.
+Find out more and access the latest issues at https://www.FreeBSDfoundation.org/journal/
+
+You can find out more about events we attended and upcoming events at https://www.FreeBSDfoundation.org/news-and-events/.
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2022-01-2022-03/gcc.adoc b/website/content/en/status/report-2022-01-2022-03/gcc.adoc
new file mode 100644
index 0000000000..003d15a7bb
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/gcc.adoc
@@ -0,0 +1,28 @@
+=== lang/gcc* ports need some love and attention
+
+Links: +
+link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/]
+
+Contact: toolchain@FreeBSD.org +
+Contact: Gerald Pfeifer <gerald@pfeifer.com>
+
+After about two decades of maintaining FreeBSD's lang/gcc* ports, the time came to hand over the baton and mostly step back.
+Alas the baton essentially dropped to the floor, despite multiple calls for help.
+
+Here are a few specific tasks looking for help:
+
+ * Upgrade GCC_DEFAULT in Mk/bsd.default-versions.mk from 10 to 11,
+   including fixing the (luckily minor) fall out of an -exp run:
+   link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378]
+
+ * Three changes to work through with upstream GCC (requires src
+   expertise, not ports):
+
+     ** upstreaming lang/gcc11/patch-gets-no-more
+     ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support
+     ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874]
+
+ * We have removed the unmaintained lang/gcc9-devel and lang/gcc10-devel
+   ports, alas kept lang/gcc11-devel and lang/gcc12-devel which would be
+   good to see if not weekly, then somewhat regular updates.
diff --git a/website/content/en/status/report-2022-01-2022-03/gunion.adoc b/website/content/en/status/report-2022-01-2022-03/gunion.adoc
new file mode 100644
index 0000000000..b0058476c7
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/gunion.adoc
@@ -0,0 +1,23 @@
+=== A New GEOM Facility, gunion
+
+Contact: Marshall Kirk McKusick <mckusick@mckusick.com>
+
+The gunion facility is used to track changes to a read-only disk on a writable disk.
+Logically, a writable disk is placed over a read-only disk.
+Write requests are intercepted and stored on the writable disk.
+Read requests are first checked to see if they have been written on the top (writable disk) and if found are returned.
+If they have not been written on the top disk, then they are read from the lower disk.
+
+The gunion facility can be especially useful if you have a large disk with a corrupted filesystem that you are unsure of how to repair.
+You can use gunion to place another disk over the corrupted disk and then attempt to repair the filesystem.
+If the repair fails, you can revert all the changes in the upper disk and be back to the unchanged state of the lower disk thus allowing you to try another approach to repairing it.
+If the repair is successful you can commit all the writes recorded on the top disk to the lower disk.
+
+Another use of the gunion facility is to try out upgrades to your system.
+Place the upper disk over the disk holding your filesystem that is to be upgraded and then run the upgrade on it.
+If it works, commit it; if it fails, revert the upgrade.
+
+The gunion(8) utility is used to create and manage an instance of a gunion. Further details and usage examples can be found in the gunion(8) manual page.
+At this time, gunion(8) is available only in 14.0.
+
+Sponsor: Netflix
diff --git a/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc b/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc
new file mode 100644
index 0000000000..07ba012ddd
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc
@@ -0,0 +1,28 @@
+=== helloSystem
+
+Links: +
+link:https://hellosystem.github.io/docs/[Documentation] URL: link:https://hellosystem.github.io/[https://hellosystem.github.io/]
+
+Contact: Simon Peter <probono@puredarwin.org> +
+Contact: `\#helloSystem` on `irc.libera.chat`, mirrored to link:https://matrix.to/#/%23helloSystem:matrix.org?via=matrix.org[`#helloSystem:matrix.org` on Matrix]
+
+==== What is helloSystem?
+
+helloSystem is FreeBSD preconfigured as a desktop operating system with a focus on simplicity, elegance, and usability.
+Its design follows the “Less, but better” philosophy.
+
+==== Q1 2022 Status
+
+* Version 0.8.0 of helloSystem is under development and test
+** helloSystem 0.8.0 will be based on FreeBSD 13.1-RELEASE
+** Experimental Live ISOs using FreeBSD 13.1-BETA3 are available
+** Initial support for running Linux AppImage files using an optional Debian runtime
+** Initial support for the AppImage format in the user interface
+** Improved reliability and performance of mounted archives by using fuse-archive
+** Various bugfixes
+
+Installable experimental Live ISO images are available at https://github.com/helloSystem/ISO/releases/tag/experimental-13.1.
+
+==== Contributing
+
+link:https://github.com/helloSystem/hello/blob/master/CONTRIBUTING.md[The project appreciates contributions in various areas].
diff --git a/website/content/en/status/report-2022-01-2022-03/intro.adoc b/website/content/en/status/report-2022-01-2022-03/intro.adoc
new file mode 100644
index 0000000000..a24df1bff6
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/intro.adoc
@@ -0,0 +1,11 @@
+As things are yet again settling into a new normal, it's once again time for a status report for the FreeBSD Project.
+
+You may have noticed that this report is also a little on the late side, and it's with regret that it's taken this long to get to it - however, thanks to a few kind souls who've stepped up to the plate, in addition to the folks on the team who do things quietly in the background, future reports should hopefully be more on time.
+
+So let's get some introductions in order, as yours truly is delighted to accept a hand from Pau Amma who already has been helping with reviews for a while, Lorenzo Salvadore who is stepping up to get some tooling in place to make it less of a chore to make the reports, as well as Sergio Carlavilla who is stepping up to help with all the work that can't be easily automated.
+
+This report covers a very diverse set of topics including but not limited to accessibility, system boot speed-up, an implementation of GEOM union, changes to the WiFi situation, and many other things.
+
+We hope you'll enjoy reading it!
+
+Daniel Ebdrup Jensen, on behalf of the status report team.
diff --git a/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc b/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc
new file mode 100644
index 0000000000..f1f9990407
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc
@@ -0,0 +1,26 @@
+=== Intel Wireless driver support and LinuxKPI 802.11 compatibility layer
+
+Links: +
+link:https://wiki.freebsd.org/WiFi/Iwlwifi[iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+The Intel Wireless driver update project aims to bring support for newer chipsets along with mac80211 LinuxKPI compat code.
+The dual-licensed Intel driver code was ported in the past for the iwm(4) native driver; using the LinuxKPI compat framework allows us to use the driver directly and gives support to all the latest chipsets, with only minor local modifications.
+Some of the changes made while porting the driver to FreeBSD were kindly incorporated into the upstream Linux driver already.
+
+During the first quarter work continued with about 70 commits.
+Updating the driver and firmware reduced differences to the Linux version and gave us bugfixes and improvements.
+Changes to the LinuxKPI 802.11 compatibility layer were made to avoid firmware crashes and possible panics for users along with other improvements.
+
+Auto-loading support for LinuxKPI PCI drivers was comitted.
+This means that iwlwifi(4) will now load automatically during boot if a supported card is detected without any user interactions.
+Considering the current state of the driver and the next release a decision was made that iwm(4) supported chipsets will continue to attach to iwm(4) for now and only newer and otherwise unsupported chipsets will use the iwlwifi(4) driver.
+This is likely going to change in CURRENT as soon as iwlwifi(4) provides better support than iwm(4).
+
+The code was merged to the stable/13 branch and the current state will be shipped with the upcoming 13.1-RELEASE.
+
+In addition to The FreeBSD Foundation thanks need to go to all users who have been testing and reporting back or are patiently waiting for the next update.
+For the latest state of the development, please follow the freebsd-wireless mailing list.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-01-2022-03/kde.adoc b/website/content/en/status/report-2022-01-2022-03/kde.adoc
new file mode 100644
index 0000000000..539e8ba58e
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/kde.adoc
@@ -0,0 +1,52 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] +
+link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@ as well, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine.
+
+*KDE Qt Patch Collection* The Qt Company did not release Qt 5.15 updates under Open Source licenses in 2021, leaving the Open Source 5.15 version lagging behind the proprietary release.
+Qt 6 is released under an Open Source license, but for the world of Open Source software that requires Qt 5, there is still a need for updates.
+The KDE Community fills that need by maintaining a curated set of patches -- generally backported from Qt6 -- to maintain the Open Source version of Qt 5.
+FreeBSD ports now use this *KDE Qt Patch Collection*, rather than the outdated last Qt 5.15.2 release from the Qt Company.
+This landed both in main and the last quarterly branch for 2021, since it brings important bugfixes.
+
+==== KDE Stack
+
+* *KDE Plasma Desktop* (all the `*/plasma5-*` ports) was updated to 5.23.5 at the start of the year. Since this happened very shortly after quarterly was branched, this was MFH'ed. The long-term-support release 5.24 landed mid-february. The FreeBSD ports do not stick to LTS releases, and will follow the regular release schedule. 5.24.3 landed on schedule in March.
+* *KDE Gear* (the collection of KDE libraries and applicatious outside of the Frameworks and Plasma Desktop groups) was updated to 21.12.1 and MFH'ed. Monthy releases landed as well: 21.12.2 in February.
+* *KDE Frameworks* have a monthly release cadence, so 5.90 landed in January, 5.91 in February and 5.92 in March.
+* *KDE PIM* currently does not support Contacts stored in a Google account because Google has changed the available REST API.
+* *astro/kstars* received its regularly scheduled updates.
+* *deskutils/kalendar* was updated. It has now reached the 1.0 stage.
+* *deskutils/kodaskanna* was added to the ports tree. It is a simple QR-code scanner for the desktop.
+* *deskutils/latte-dock* is an alternative launcher for use in KDE Plasma Desktop and other environments. It was updated to 0.10.7 as part of its monthly releases.
+* *devel/okteta*, an editor and viewer for binary data, was updated to 0.26.7, a regular bugfix release.
+* *graphics/digikam*, the digital photography manager, was updated to 7.6.0. (Thanks Dima Panov)
+* *graphics/kf5-kimageformats* has a new option enabling libheif and HEIC support.
+* *graphics/kontrast* was added to the 'accessibility' category. This is a tool for checking color-combinations (e.g. for a website) for sufficient contrast and readability.
+* *graphics/krita* was updated to the next big release, Krita 5. (Thanks Max Brazhnikov)
+* *lang/kross-interpreters* was fixed for Ruby 3. (Thanks Yasuhiro Kimura)
+* *sysutils/plasma5-discover* was updated to resolve some denial-of-service bugs in KDE infrastructure.
+* *www/falkon* was updated. After a two-year wait, a new release of the KDE web browser built on Qt WebEngine (itself a wrapper around Chromium internals) arrived upstream and in ports.
+* *x11/plasma5-plasma-workspace* now can properly edit login and account information.
+
+
+==== Related Applications
+
+* *devel/qtcreator* was updated to version 6. A new versioning model has been introduced by upstream, so this will now jump by major release number regularly. (Thanks to Florian Walpen)
+* *irc/quassel* was updated. Quassel is a distributed IRC client (think of it as your own personal IRC bouncer).
+* *misc/tellico* was updated. Tellico is a "collection manager", for instance collections of books, music, stamps, or FreeBSD releases.
+* *net-im/nheko* was updated. This is one of a dozen Matrix clients available in the ports tree.
+
+==== Elsewhere
+
+* *archivers/7-zip* is the preferred tool for dealing with 7zip files; this affacts KDE applications that work with archives (like *archivers/ark*). We would like to thank makc@ for stewarding that update.
+* *devel/libphonenumber* has bi-weekly updates to chase the exciting world of telephony details.
+* *graphics/poppler* was updated to version 22.01. This version requires C{plus}{plus}17, which pushes a number of consumers to the newer C{plus}{plus} standard as well. Most consumers were fixed in advance.
diff --git a/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc b/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc
new file mode 100644
index 0000000000..b8f6f51fc8
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc
@@ -0,0 +1,14 @@
+=== Kernel Crypto changes to support WireGuard
+
+Contact: John Baldwin <jhb@FreeBSD.org>
+
+During the last quarter, I continued my work to improve the FreeBSD WireGuard driver.
+On the FreeBSD side, I added support for the XChaCha20-Poly1305 AEAD cipher.
+I also added a dedicated API to support [X]ChaCha20-Poly1035 on small, flat buffers.
+Finally, I added an API wrapper for the curve25519 implementation from libsodium.
+
+For the WireGuard driver, I wrote a series of patches which updates the driver to use crypto APIs such as those mentioned above in place of internal cipher implementations.
+The series also includes a fix to avoid scheduling excessive crypto tasks as well as a few other small fixes.
+This series is pending review.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-01-2022-03/office.adoc b/website/content/en/status/report-2022-01-2022-03/office.adoc
new file mode 100644
index 0000000000..5b1503d300
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/office.adoc
@@ -0,0 +1,24 @@
+=== FreeBSD Office Team
+
+Links: +
+link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[https://wiki.freebsd.org/Office] +
+link:https://lists.freebsd.org/subscription/freebsd-office[The FreeBSD Office mailing list] URL: link:https://lists.freebsd.org/subscription/freebsd-office[https://lists.freebsd.org/subscription/freebsd-office]
+
+Contact: FreeBSD Office team ML <office@FreeBSD.org> +
+Contact: Dima Panov <fluffy@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+The FreeBSD Office team works on a number of office-related software suites and tools such as OpenOffice and LibreOffice.
+
+Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users.
+
+During the 2022Q1 period we pushed maintenance patches for the LibreOffice 7.2 port to the quarterly branch and brought the latest, 7.3, releases and all companion libraries such as MDDS, libIxion and more to the ports tree.
+
+Also we are still working on the link:https://github.com/fluffykhv/freebsd-ports-boost[Boost WIP repository] to bring the latest Boost library to the ports.
+
+We are looking for people to help with the open tasks:
+
+* The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=office%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailreporter1=1&emailtype1=substring&query_format=advanced&list_id=374316[open bugs list] contains all filed issues which need some attention
+* Upstream link:https://cgit.freebsd.org/ports/tree/editors/libreoffice/files[local patches in ports]
+
+Patches, comments and objections are always welcome in the mailing list and Bugzilla.
diff --git a/website/content/en/status/report-2022-01-2022-03/portconfig.adoc b/website/content/en/status/report-2022-01-2022-03/portconfig.adoc
new file mode 100644
index 0000000000..205201ff8c
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/portconfig.adoc
@@ -0,0 +1,18 @@
+=== PortConfig
+
+Links: +
+link:https://gitlab.com/alfix/portconfig/[Repository portconfig] URL: link:https://gitlab.com/alfix/portconfig/[https://gitlab.com/alfix/portconfig/]
+
+Contact: Alfonso Sabato Siciliano (upstream) <asiciliano@FreeBSD.org> +
+Contact: Baptiste Daroussin (port) <bapt@FreeBSD.org>
+
+FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications.
+It is possible to configure a port before the building and installation.
+PortConfig is an utility for setting the port options via a Text User Interface.
+
+As each terminal has different properties PortConfig can be customized via environment variables to set up the User Interface, for example: menu size, theme, borders, and so on; each feature is documented inside the manual.
+Further, if a port has a specific 'pkg-help' file, PortConfig will show a Help button to open a "popup" with help information.
+
+FreeBSD provides thousands of ports therefore it is not feasible to test PortConfig for each use; please report any problem.
+
+Alfonso would like to thank Baptiste Daroussin for the port, suggestions, help, and testing for this utility and its library.
diff --git a/website/content/en/status/report-2022-01-2022-03/portmgr.adoc b/website/content/en/status/report-2022-01-2022-03/portmgr.adoc
new file mode 100644
index 0000000000..ade42a0bb4
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/portmgr.adoc
@@ -0,0 +1,53 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[https://www.FreeBSD.org/ports/] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[https://www.freebsd.org/portmgr/] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+Before we start with the usual statistics, portmgr is happy to announce it has successfully restarted its lurker program.
+The first two lurkers are pizzamig@ and se@; they will learn about the inner workings of portmgr and bring in new ideas.
+
+Portmgr also started having bi-weekly meetings, some public results are:
+
+* restarting the lurker program
+* fixes to ports going backwards in version
+* dropping DragonFlyBSD version checks in bsd.port.mk
+* dropping deprecation notes from ports transitively using Python 2.7
+
+Currently we have over 46,800 ports in the Ports Tree. There are currently 2,700 open ports PRs of which 680 are unassigned.
+The last quarter saw 9,403 commits to the main branch by 157 committers and 683 commits to the 2022Q1 branch by 63 committers.
+Compared to last quarter, this means a slight drop in activity to the main branch and a slight
+increase in the number of open PRs.
+
+No new committers joined during the last quarter, portmgr took one commit bit in for safekeeping because of a lack of recent commits.
+
+The cluster administration team has provided portmgr with a third aarch64 builder; it is being used for package builds.
+
+Things that happened in git:
+
+* Two new USES were introduced:
+** elfctl to change an ELF binary's feature control note
+** minizip to get the correct library dependency on minizip
+* Two keywords got removed:
+** fcfontsdir (now handled by USES=fonts)
+** glib-schemas, it has been replaced by a trigger
+* Default versions that changed:
+** Lazarus switched to 2.2.0
+** PHP switched to 8.0
+* Some upgrades to major ports:
+** Chromium 100.0.4896.60
+** Electron 13.6.9
+** Firefox 99.0
+** Firefox ESR 91.8.0
+** Gnome 41
+** KDE Frameworks 5.92.0
+** KDE Plasma 5.24.4
diff --git a/website/content/en/status/report-2022-01-2022-03/pot.adoc b/website/content/en/status/report-2022-01-2022-03/pot.adoc
new file mode 100644
index 0000000000..cbcb21123d
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/pot.adoc
@@ -0,0 +1,23 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on github] URL: link:https://github.com/bsdpot[https://github.com/bsdpot]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> +
+Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@freebsd.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+As a result of production testing in a real-world cluster deployment, pot and related projects received stability improvements for controlling the pot lifecycle (i.e., pot prepare/start/stop). +
+Various attributes and commands have been developed to improve support of nomad orchestration and batch jobs (e.g., change dns config during clone, ability to disable tmpfs, new last-run-stats command). A new pot release will follow soon.
+
+Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: a repository of pot flavours and complete container images for usage with pot and in many cases nomad.
+
+Many of the core images like link:https://potluck.honeyguide.net/blog/nomad-server/[Nomad], link:https://potluck.honeyguide.net/blog/consul/[Consul] and link:https://potluck.honeyguide.net/blog/vault/[Vault] that can be used to build a private cloud and orchestration platform, but also e.g. link:https://potluck.honeyguide.net/blog/prometheus/[Prometheus] or link:https://potluck.honeyguide.net/blog/postgresql-patroni/[PostgreSQL Patroni], have reached a stable status over the last quarter and are in production use now.
+
+To make navigating the evolving pot ecosystem easier, most project resources have been centralized in a dedicated github project: link:https://github.com/bsdpot[https://github.com/bsdpot]
+
+There, we plan to release ansible playbooks that allow easily creating a FreeBSD based orchestration environment from scratch based on all these tools.
+
+As always, feedback and patches are welcome.
diff --git a/website/content/en/status/report-2022-01-2022-03/releng.adoc b/website/content/en/status/report-2022-01-2022-03/releng.adoc
new file mode 100644
index 0000000000..4e91252673
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/releng.adoc
@@ -0,0 +1,21 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.1R/schedule/[FreeBSD 13.1-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.1R/schedule/[https://www.freebsd.org/releases/13.1R/schedule/] +
+link:https://www.freebsd.org/releases/13.1R/[FreeBSD 13.1 Release Information] URL: link:https://www.freebsd.org/releases/13.1R/[https://www.freebsd.org/releases/13.1R/] [link added by status report team as this quarterly status report is being published after 13.1-RELEASE has been released] +
+link:https://download.freebsd.org/ftp/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/ftp/releases/ISO-IMAGES/[https://download.freebsd.org/ftp/releases/ISO-IMAGES/] +
+link:https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/[https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the first quarter of 2022, the Release Engineering Team completed work on, and submitted to the developers the 13.1-RELEASE schedule.  This will be the second point release from the stable/13 branch.
+As of this writing, three BETA builds have been run, with at least two RC builds before the final release, currently scheduled for April 21, 2022.
+
+We look forward to another consistently stable release at the end of this cycle, as well as many more to come for other branches moving forward.
+
+Additionally throughout the quarter, several development snapshots builds were released for the *main*, *stable/13*, and *stable/12* branches.
+
+Sponsor: Rubicon Communications, LLC ("Netgate")
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-01-2022-03/rtw88.adoc b/website/content/en/status/report-2022-01-2022-03/rtw88.adoc
new file mode 100644
index 0000000000..8d7a852b40
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/rtw88.adoc
@@ -0,0 +1,24 @@
+=== Realtek Wireless driver support
+
+Links: +
+link:https://wiki.freebsd.org/WiFi/Rtw88[rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88] +
+link:https://wiki.freebsd.org/WiFi/Rtw89[rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+While the Intel Wireless driver update project is the main driver behind the work to bring support for newer chipsets and eventually newer IEEE 802.11 standards support, there is also an ongoing effort to support more drivers.
+The next two drivers in the (already longer) queue are Realtek's rtw88 and rtw89.
+
+While the initial driver porting efforts for rtw88 and rtw89 happened on personal time, the LinuxKPI integration has to be done more and more along the Intel wireless driver work and so thanks are also due to The FreeBSD Foundation.
+
+The rtw88 driver has started to work on some machines with less than 4GB of main memory and was committed to the FreeBSD git repository for broader testing.
+While our version of the driver is aware of these limitations, the problem is currently assumed to be outside the driver in the interactions with LinuxKPI and busdma.
+
+The rtw89 driver has happily started to send packets and has problems receiving frames at this point.
+Further investigation will happen as soon as rtw88 is sorted out and it is expected that rtw89 will then also timely follow into FreeBSD's git repository.
+
+The currently known requirements to compile both drivers have mostly gone into stable/13 and releng/13.1 already.
+
+For the latest state of the development, please check the referenced wiki pages and follow the freebsd-wireless mailing list.
+
+Sponsor: The FreeBSD Foundation (partly)
diff --git a/website/content/en/status/report-2022-01-2022-03/wifibox.adoc b/website/content/en/status/report-2022-01-2022-03/wifibox.adoc
new file mode 100644
index 0000000000..6edbf18e57
--- /dev/null
+++ b/website/content/en/status/report-2022-01-2022-03/wifibox.adoc
@@ -0,0 +1,31 @@
+=== Wifibox: Use Linux to drive your wireless card on FreeBSD
+
+Links: +
+link:https://github.com/pgj/freebsd-wifibox[Project GitHub Page] +
+link:https://cgit.freebsd.org/ports/tree/net/wifibox[``net/wifibox`` port]
+
+Contact: PÁLI Gábor János <pali.gabor@gmail.com>
+
+Wifibox is an experimental project for exploring the ways of deploying a virtualized Linux guest to drive wireless networking cards on the FreeBSD host system.
+There have been guides on the Internet to suggest the use of such techniques to improve the wireless networking experience, of which Wifibox aims to implement as a single easy-to-use software package.
+
+- man:bhyve[8] is utilized to run the embedded Linux system.
+  This helps to achieve low resource footprint.
+  It requires an x64 CPU with I/O MMU (AMD-Vi, Intel VT-d), ~150 MB physical memory, and some disk space available for the guest virtual disk image, which can be even ~30 MB only in certain cases.
+  It works with FreeBSD 12 and later, some cards may require a recent 13-STABLE though.
+
+- The guest is constructed using https://alpinelinux.org/[Alpine Linux], a security-oriented, lightweight distribution based on https://www.musl-libc.org/[musl libc] and https://busybox.net/[BusyBox].
+
+- Configuration files are shared with the host system. The guest uses man:wpa_supplicant[8] so it is possible to import the host's man:wpa_supplicant.conf[8] file without any changes.
+
+- When configured, man:wpa_supplicant[8] control sockets could be exposed by the guest, which enables use of related utilities directly from the host, such as man:wpa_cli[8] or man:wpa_gui[8] from the ``net/wpa_supplicant_gui`` port/package.
+
+- Everything is shipped in a single package that can be easily installed and removed.
+  This comes with an man:rc[8] system service that automatically launches the guest on boot and stops it on shutdown.
+
+- A workaround is supplied for laptops to support suspend/resume.
+
+Wifibox has been mainly tested with Intel chipsets so far, and it has shown great performance and stability.
+Therefore it might serve as an interim solution until the Intel Wireless support becomes mature enough.
+It was confirmed that Wifibox works with Atheros chipsets too, and feedback is more than welcome about others.
+Support for Broadcom chipsets is not yet complete, that is currently a work in progress.
diff --git a/website/content/en/status/report-2022-04-2022-06/_index.adoc b/website/content/en/status/report-2022-04-2022-06/_index.adoc
new file mode 100644
index 0000000000..1d5a0effd4
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/_index.adoc
@@ -0,0 +1,164 @@
+---
+title: "FreeBSD Quarterly Status Report Second Quarter 2022"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2022-04-2022-06
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+Entries from the various official and semi-official teams, as found in the
+link:../../administration/[Administration Page].
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+Projects that span multiple categories, from the kernel and userspace to the
+Ports Collection or external projects.
+
+include::{reports-path}/linuxulator.adoc[]
+
+'''
+
+include::{reports-path}/golang_riscv64.adoc[]
+
+'''
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+Changes affecting the base system and programs in it.
+
+include::{reports-path}/lldb.adoc[]
+
+'''
+
+include::{reports-path}/makefs-zfs.adoc[]
+
+'''
+
+include::{reports-path}/openssh.adoc[]
+
+'''
+
+include::{reports-path}/pf.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+Updates to kernel subsystems/features, driver support, filesystems, and more.
+
+include::{reports-path}/ena.adoc[]
+
+'''
+
+include::{reports-path}/blued.adoc[]
+
+'''
+
+include::{reports-path}/if_ovpn.adoc[]
+
+'''
+
+include::{reports-path}/wifi.adoc[]
+
+'''
+
+include::{reports-path}/shp_rand.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+Updating platform-specific features and bringing in support for the new hardware
+platform.
+
+include::{reports-path}/dpaa2.adoc[]
+
+'''
+
+include::{reports-path}/superpages.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+Noteworthy changes in the documentation tree, manual pages, or new external
+books/documents.
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+Changes affecting the Ports Collection, whether sweeping changes that touch most
+of the tree, or individual ports themselves.
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/valgrind.adoc[]
+
+'''
+
+include::{reports-path}/pantheon.adoc[]
+
+'''
+
+include::{reports-path}/igt-gpu-tools.adoc[]
diff --git a/website/content/en/status/report-2022-04-2022-06/azure.adoc b/website/content/en/status/report-2022-04-2022-06/azure.adoc
new file mode 100644
index 0000000000..3e24bc2407
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/azure.adoc
@@ -0,0 +1,42 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+
+The link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-13_1[13.1-RELEASE image on Azure Marketplace] has been published.
+
+Work in progress tasks:
+
+* Automating the image building and publishing process
+* Building and publishing ZFS-based images to Azure Marketplace
+** The task will be benefited by merging of ZFS support of man:makefs[8] and man:release[7]
+*** https://reviews.freebsd.org/D23334
+*** https://reviews.freebsd.org/D34426
+*** https://reviews.freebsd.org/D35248
+* Building and publishing Hyper-V gen2 VM images to Azure Marketplace
+** Blocked by https://bugs.freebsd.org/264267
+
+The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+
+Wei Hu and his colleagues in Microsoft are working on several tasks sponsored by Microsoft:
+
+* Fixing booting issue on Hyper-V gen2 VM in Azure
+** https://bugs.freebsd.org/264267
+* Porting Hyper-V guest support to aarch64
+
+Open tasks:
+
+* Update FreeBSD related doc at link:https://docs.microsoft.com[]
+* Support FreeBSD in link:https://azure.microsoft.com/services/devops/pipelines/[Azure Pipelines]
+* Update link:https://www.freshports.org/sysutils/azure-agent[Azure agent port] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+
+Sponsor: Microsoft for work by Wei Hu and others in Microsoft, and for resources for the rest
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2022-04-2022-06/blued.adoc b/website/content/en/status/report-2022-04-2022-06/blued.adoc
new file mode 100644
index 0000000000..25fa04fa40
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/blued.adoc
@@ -0,0 +1,54 @@
+=== New Bluetooth(R) configuration daemon: blued
+
+Links: +
+link:https://git.lysator.liu.se/kempe/blued[blued git] URL: https://git.lysator.liu.se/kempe/blued[https://git.lysator.liu.se/kempe/blued]
+
+Contact: +
+Mail: kempe@lysator.liu.se +
+IRC: kempe@libera.chat
+
+==== Introduction
+
+The blued utility provides an IPC interface that lets an unprivileged user connect to and use Bluetooth devices in a user-friendly way and supports secure simple pairing (public-key cryptography and if the device allows it man-in-the-middle protection).
+
+==== What is blued?
+
+There are three parts to blued: a library, a daemon and a command line utility.
+The library abstracts away bluetooth details, the daemon manages Bluetooth devices and the command line utility lets users list or scan for Bluetooth devices, pair with a device, or unpair from one.
+The command line utility communicates with the daemon via a UNIX socket.
+
+Unlike bthidd and hcsecd, blued supports secure simple pairing and
+provides an IPC.
+To get a HID device to work, bthidd is still needed.
+A script is provided to pair a Bluetooth device and appropriately configure bthidd so it just works and reconnects without user intervention.
+
+Once pairing has proven stable and bugs have been ironed out, the plan is to integrate bthidd with/into blued in some way to have HID devices automatically start functioning when paired without the use of an external script.
+A long-term goal is to provide a graphical user interface that can list devices and provide a simple one-click setup to connect them.
+
+==== Installing and using blued v0.1
+
+You need the optional `src` component installed in [.filename]#/etc/src#.
+
+First, make sure link:https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-bluetooth[you have working Bluetooth drivers loaded as explained in the FreeBSD handbook].
+
+To test blued, fetch link:https://git.lysator.liu.se/kempe/blued/-/releases/v0.1[the blued v0.1 source code].
+Then compile it, patch your FreeBSD kernel with the patches in [.filename]#kernel_patches#, and recompile the `hci` module as explained in [.filename]#README#.
+
+I have primarily tested blued on FreeBSD 12.3, but my patches applied cleanly on 13.1 when I tested.
+I am not supplying a port at the moment, but it is possible to run the software straight from the build directory or run "make install" that will install all needed files.
+Both blued and bluecontrol use capsicum and blued can be configured to drop its root privileges.
+
+For more information, refer to the `Running blued` section of [.filename]#README#.
+
+==== Helping out
+
+===== Testing
+
+I have only tried this software with my own mouse and realise that a sample size of one single bluetooth device is pretty small.
+I'm expecting issues and am greatly looking forward to feedback from others!
+
+In case of trouble, output from /var/log/debug.log and /var/log/messages as well as a traffic dump from "hcidump -x" while trying to pair will help with troubleshooting.
+
+===== Contributing
+
+If you want to get involved with the code and submit patches, you're welcome to link:https://git.lysator.liu.se/kempe/blued[visit the repository] on Lysator's Git.
diff --git a/website/content/en/status/report-2022-04-2022-06/ci.adoc b/website/content/en/status/report-2022-04-2022-06/ci.adoc
new file mode 100644
index 0000000000..f09b8f6b77
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/ci.adoc
@@ -0,0 +1,53 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] +
+link:https://wiki.freebsd.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.freebsd.org/Jenkins[https://wiki.freebsd.org/Jenkins] +
+link:https://wiki.freebsd.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.freebsd.org/HostedCI[https://wiki.freebsd.org/HostedCI] +
+link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.freebsd.org/3rdPartySoftwareCI[https://wiki.freebsd.org/3rdPartySoftwareCI] +
+link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] +
+link:https://lists.freebsd.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.freebsd.org/subscription/dev-ci[https://lists.freebsd.org/subscription/dev-ci]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+The FreeBSD CI team maintains the continuous integration system of the FreeBSD project.
+The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results.
+The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs.
+The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure.
+
+During the second quarter of 2022, we continued working with the contributors and developers in the project to fulfill their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD.
+
+Important completed tasks:
+
+* Fixed the hardware failure issue of the CI cluster
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Testing and merging pull requests in link:https://github.com/freebsd/freebsd-ci/pulls[the FreeBSD-ci repo]
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository
+* Updating documents on wiki
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Adding more external toolchain related jobs
+* Improving maturity of the hardware lab and adding more hardware for testing
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.freebsd.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-04-2022-06/clusteradm.adoc b/website/content/en/status/report-2022-04-2022-06/clusteradm.adoc
new file mode 100644
index 0000000000..f775273c41
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/clusteradm.adoc
@@ -0,0 +1,30 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications.
+In this quarter, the team has worked on the following:
+
+* Installed a new mirror in Sydney, Australia hosted by IX Australia
+* Fixed CI cluster hardware failure
+* Set up a new internal monitoring system
+* Regular cluster-wide software upgrades
+* Regular support for FreeBSD.org user accounts
+
+Work in progress:
+
+* Work with the PowerPC team to improve the package builders, universal, and reference machines.
+* Plan Hardware refresh, and fixing misc failures in each sites
+* Improve the package building infrastructure
+* Review the service jails and service administrators operation
+* Working with doceng@ to improve deployment of https://www.freebsd.org and https://docs.freebsd.org
+* Improve the web service architecture
+* Improve the cluster backup plan
+* Improve the log analysis system
+
+We are looking for an additional full mirror site (five servers) in Europe.
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for our needs.
+Offers of additional single-server mirrors (see link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny mirror]) are always welcome too, especially in Europe.
diff --git a/website/content/en/status/report-2022-04-2022-06/core.adoc b/website/content/en/status/report-2022-04-2022-06/core.adoc
new file mode 100644
index 0000000000..c1c5a75543
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/core.adoc
@@ -0,0 +1,26 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+The twelfth FreeBSD Core Team was elected by active developers.
+The core.12 members are:
+
+* Baptiste Daroussin (bapt, incumbent)
+* Benedict Reuschling (bcr)
+* Ed Maste (emaste, incumbent)
+* Greg Lehey (grog)
+* John Baldwin (jhb)
+* Li-Wen Hsu (lwhsu)
+* Emmanuel Vadot (manu)
+* Tobias C. Berner (tcberner)
+* Mateusz Piotrowski (0mp)
+
+On June 10th the outgoing core.11 and incoming core.12 teams held a handover meeting,
+and the new Core Team was link:https://lists.freebsd.org/archives/freebsd-announce/2022-June/000034.html[announced on Jun 18].
+
+The current Core Team secretary, Muhammad Moinur Rahman (bofh), will step down
+after the appointment of a new Core Team secretary and handover tasks completes.
+
+In this quarter, src commit bits of Kornel Dulęba (kd) and Dmitry Salychev (dsl) have been approved.
diff --git a/website/content/en/status/report-2022-04-2022-06/doceng.adoc b/website/content/en/status/report-2022-04-2022-06/doceng.adoc
new file mode 100644
index 0000000000..7aafa770ac
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/doceng.adoc
@@ -0,0 +1,79 @@
+////
+Quarter:	2nd quarter of 2022
+Prepared by:	dbaio
+Reviewed by:	-
+Last edit:	$Date: 2022-07-02 22:35:43 -0300 (Sat, 02 Jul 2022) $
+Version:	$Id: doceng-2022-2nd-quarter-status-report.adoc 241 2022-07-03 01:35:43Z dbaio $
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During the last quarter, Graham Perrin (grahamperrin@) and Pau Amma (pauamma@), were granted documentation commit bits.
+
+Several items are pending and in discussion:
+
+* Mirroring the Website and Documentation portal with the GeoDNS infrastructure of the project.
+* How to handle Trademarks in the documentation.
+* Remove outdated translations from the Website and Documentation portal.
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance]
+
+===== Q2 2022 Status
+
+* 12 languages
+* 152 registered users (9 new users)
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)
+* Chinese (Traditional) (zh-tw)
+* Dutch (nl)
+* French (fr)
+* German (de)
+* Indonesian (id)
+* Italian (it)
+* Norwegian (nb-no)
+* Persian (fa-ir)
+* Portuguese (pt-br)
+* Spanish (es)
+* Turkish (tr)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Work in progress_)
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Not started_)
diff --git a/website/content/en/status/report-2022-04-2022-06/dpaa2.adoc b/website/content/en/status/report-2022-04-2022-06/dpaa2.adoc
new file mode 100644
index 0000000000..5ebaacf990
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/dpaa2.adoc
@@ -0,0 +1,36 @@
+=== NXP DPAA2 support
+
+Links +
+link:https://github.com/mcusim/freebsd-src/commits/lx2160acex7-dev[Change history] +
+link:https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[Tree]
+
+Contact: Dmitry Salychev <dsl@FreeBSD.org> +
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+Some of the NXP SoCs (LX2160A, LS1088A) are shipped with link:https://www.nxp.com/design/qoriq-developer-resources/second-generation-data-path-acceleration-architecture-dpaa2:DPAA2[DPAA2], the second generation of the data path acceleration architecture.
+It allows to dynamically configure and wire packet processing "objects" (DPNI for a network interface, DPMAC for media access controller, etc.) together to form a network-on-a-chip.
+
+During the last quarter the driver started working well enough to be used on link:https://solidrun.atlassian.net/wiki/spaces/developer/pages/197494288/HoneyComb+LX2+ClearFog+CX+LX2+Quick+Start+Guide[SolidRun' Honeycomb LX2] (ACPI test platform) and Traverse Technologies has produced a link:https://forum.traverse.com.au/t/freebsd-preview-for-ten64/173[FreeBSD preview for (their) Ten64] (used as FDT test platform).
+
+The driver is still work-in-progress, but is getting close for a review to get the first version into the tree for everyone to benefit from it.
+
+WIP:
+
+* FDT MDIO support. FreeBSD currently lacks support for the SPF parts.
+
+* Driver resources de-allocation to unload dpaa2.ko properly.
+
+* link:https://github.com/mcusim/freebsd-src/issues[Bug fixes] and improvements.
+
+TODO:
+
+* CPU affinity for DPIOs and DPNIs.
+
+* Cached memory-backed software portals.
+
+* Bottlenecks mitigation.
+
+* Further parts (DPSW, DCE, etc.) supported by the hardware.
+
+Sponsor: Bare Enthusiasm :) +
+Sponsor: Traverse Technologies (providing Ten64 HW for testing)
diff --git a/website/content/en/status/report-2022-04-2022-06/ena.adoc b/website/content/en/status/report-2022-04-2022-06/ena.adoc
new file mode 100644
index 0000000000..e0c9ca6dcb
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/ena.adoc
@@ -0,0 +1,32 @@
+=== ENA FreeBSD Driver Update
+
+Links: +
+link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst]
+
+Contact: Michal Krawczyk <mk@semihalf.com> +
+Contact: Dawid Gorecki <dgr@semihalf.com> +
+Contact: Marcin Wojtas <mw@FreeBSD.org>
+
+ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS).
+The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used.
+
+Completed since the last update:
+
+* Upstream of the ENA driver v2.5.0, which included:
+  * Improvement to the reset routine handling,
+  * Extension of the timer service lifetime in order to be able to detect more
+    hardware failures,
+  * Fix logic for verifying the Tx request ID,
+  * Fix IPv6 L4 checksum offload handling for the Tx,
+  * Add NUMA awareness to the driver.
+* Internal review of the upcoming ENA driver release (v2.6.0), including:
+  * Further reset handling improvements,
+  * Code cleanup and style fixes,
+  * Logging improvements,
+  * Fix to the retrieval of the ENI metrics.
+
+Work in progress:
+
+* Testing of the upcoming ENA driver release (v2.6.0).
+
+Sponsor: Amazon.com Inc
diff --git a/website/content/en/status/report-2022-04-2022-06/freebsd-foundation.adoc b/website/content/en/status/report-2022-04-2022-06/freebsd-foundation.adoc
new file mode 100644
index 0000000000..1ad6eb9179
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/freebsd-foundation.adoc
@@ -0,0 +1,150 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] +
+link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] +
+link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] +
+link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] +
+link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide.
+Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits.
+We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts.
+We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+==== Fundraising Efforts
+
+First, I’d like to send a big thank you to everyone who gave a financial contribution to our efforts.
+We are 100% funded by your donations, so every contribution helps us continue to support FreeBSD in many ways, including some of the work funded and published in this status report.
+
+Our goal this year is to raise at a minimum $1,400,000 towards a spending budget of around $2,000,000.
+As I write this report, we’ve brought in under $200,000 towards that goal.
+So, we obviously need to step up our effort of fundraising.
+It’s by far the hardest part of my job.
+I’d much prefer talking to folks in our community on how we can help you, help create content to recruit more users and contributors to the Project, and understand challenges and painpoints that individuals and organizations have in using FreeBSD, so we can help improve those areas.
+Asking for money is not on that list.
+
+We support FreeBSD in five main areas.
+Software development is the largest area we fund with six software developers on staff who step in to implement new
+features, support tier 1 platforms, review patches, and fix issues.
+You can find out some of the work we did under OS Improvements in this report.
+FreeBSD Advocacy is another area that we support to spread the word about FreeBSD at conferences, in presentations online and in-person, tutorials and how-to guides.
+We purchase and support hardware for the FreeBSD infrastructure that supports the work going on in the Project.
+Virtual and in-person events are organized by the Foundation to help connect and engage community members to share their knowledge and collaborate on projects.
+Finally, we provide legal support to the Project when needed and protect the FreeBSD trademarks.
+
+If you haven't made a donation this year, please consider making one at https://freebsdfoundation.org/donate/.
+
+We also have a Partnership Program for larger commercial donors.
+You can find out more at https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
+
+==== OS Improvements
+
+During the second quarter of 2022, 243 src, 62 ports, and 12 doc tree commits were made that identified The FreeBSD Foundation as a sponsor.
+This represents 10.6, 0.7, and 4.5% of the total number of commits to each repository.
+
+==== Sponsored Work
+
+You can read about some of the Foundation-sponsored work in individual quarterly report entries.
+
+* Base System OpenSSH Update
+* Ongoing work on LLDB multiprocess debugging support
+* Wireless Status
+* ZFS support in makefs
+
+Other ongoing sponsored work is described here.
+
+===== FreeBSD Wireguard Improvements
+
+The aim of the Wireguard project is to improve support for the FreeBSD Wireguard kernel module.
+The work by John Baldwin involved adapting the module to use FreeBSD's OCF rather than Wireguard's internal implementations.
+It also involved adding new ciphers and API support.
+The latest upstream release incorporates this work.
+
+===== Openstack on FreeBSD
+
+OpenStack is a cloud system for different types of resources like virtual machines.
+However, OpenStack only unofficially supports FreeBSD as a guest system.
+That means users can spawn FreeBSD instances on the open cloud platform, but it is not currently possible run OpenStack on FreeBSD hosts.
+The goal of this project is port OpenStack components so that FreeBSD can function as an OpenStack host.
+
+===== Bhyve Issue Support
+
+The Foundation recently signed a new contract for Bhyve support.
+This contract will allow John Baldwin to dedicate time to Bhyve as issues arise, especially security issues.
+
+===== Handbook Improvement Exploration
+
+Under sponsorship from the Foundation, Pau Amma wrapped up a mini-project to explore how the Handbook can be improved.
+A survey was sent out and the results will be shared soon.
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project.
+
+==== Supporting FreeBSD Infrastructure
+
+The Foundation provides hardware and support for the Project.
+A new Australian mirror was brought online by the Cluster Administration team.
+If you are a FreeBSD user in Oceania or southeast Asia, please let us know if download speeds for installer images and packages has improved.
+
+With your donations, the Foundation purchased new hardware to repair two PowerPC package builders, one for little endian packages (powerpc64le) and the second for big endian packages (powerpc64, powerpc).
+The new hardware just arrived at the data center and will be installed soon.
+Expect lots of PowerPC packages in the near future.
+
+==== FreeBSD Advocacy and Education
+
+Much of our effort is dedicated to Project advocacy.
+This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations.
+The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier.
+Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe.
+These events can be BSD-related, open source, or technology events geared towards underrepresented groups.
+We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.
+This all helps provide a healthy ecosystem.
+We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.
+We are continuing to attend virtual events and planning the June 2022 Developer Summit.
+In addition to attending and planning virtual events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD.
+
+Check out some of the advocacy and education work we did last quarter:
+
+* Secured our booth and nonprofit sponsor status for All Things Open, October 30-November 2, 2022, Raleigh, NC.
+* Finalized our booth and workshop at Scale 19x in Los Angeles, CA on July 28-30.
+  The FreeBSD workshop will be held Friday,Jul 29, 2022 and you can visit the Foundation at booth 502.
+* Confirmed our Silver Sponsorship of EuroBSDcon 2022, September 15-18, Vienna, Austria
+* Sponsored and helped organize the June 2022 FreeBSD Developer Summit, June 16-17, 2022.
+  Videos are available on the link:https://www.youtube.com/c/FreeBSDProject[FreeBSD Project YouTube channel].
+* Celebrated FreeBSD Day June 19, 2022 and throughout the following week.
+* Secured our Friends level sponsorship of COSCUP, July30-31, Taiwan
+* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-spring-2022-update/[FreeBSD Foundation Spring 2022 Update]
+* New Blog Posts
+** link:https://freebsdfoundation.org/blog/lets-talk-about-foundation-funding/[Let's Talk About Foundation Funding]
+** link:https://freebsdfoundation.org/blog/new-board-member-interview-cat-allman/[New Board Member Interview: Cat Allman]
+** link:https://freebsdfoundation.org/blog/welcome-freebsd-google-summer-of-code-participants/[Welcome FreeBSD Google Summer of Code Participants]
+** link:https://freebsdfoundation.org/blog/freebsd-foundation-work-in-the-13-1-release/[FreeBSD Foundation Work in the 13.1 Release]
+** link:https://freebsdfoundation.org/blog/foundation-elects-new-officers-interviews-outgoing-board-members/[Foundation Elects New Officers, Interviews Outgoing Board Members]
+** link:https://freebsdfoundation.org/blog/help-us-celebrate-freebsd-day-all-week-long/[Help Us Celebrate FreeBSD Day All Week Long]
+* New and Updated How-To and Quick Guides:
+** link:https://freebsdfoundation.org/freebsd-project/resources/networking-basics-wifi-and-bluetooth/[Networking Basics: WiFi and Bluetooth]
+** link:https://freebsdfoundation.org/freebsd-project/resources/audio-on-freebsd/[Audio on FreeBSD]
+** link:https://freebsdfoundation.org/freebsd/how-to-guides/installing-freebsd-with-virtualbox-video-guide/[Installing FreeBSD with VirtualBox (Mac/Windows) - Video Guide]
+** link:https://freebsdfoundation.org/freebsd-project/resources/an-introduction-to-the-freebsd-operating-system-video/[An Introduction to the FreeBSD Operating System - Video Guide]
+** link:https://freebsdfoundation.org/freebsd-project/resources/installing-a-desktop-environment-on-freebsd-video-guide/[Installing a Desktop Environment on FreeBSD - Video Guide]
+** link:https://freebsdfoundation.org/freebsd-project/resources/installing-a-port-on-freebsd-video-guide/[Installing a Port on FreeBSD - Video Guide]
+
+We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal.
+As we mentioned previously, the FreeBSD Journal is now a free publication.
+Find out more and access the latest issues at link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDfoundation.org/journal/].
+
+You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDfoundation.org/news-and-events/].
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2022-04-2022-06/gcc.adoc b/website/content/en/status/report-2022-04-2022-06/gcc.adoc
new file mode 100644
index 0000000000..7099c4cc4a
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/gcc.adoc
@@ -0,0 +1,28 @@
+=== GCC: updating GCC_DEFAULT and other improvements
+
+Links: +
+link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/]
+
+Contact: <toolchain@FreeBSD.org> +
+Contact: Gerald Pfeifer <gerald@pfeifer.com> +
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> +
+Contact: Piotr Kubaj <pkubaj@FreeBSD.org>
+
+ * salvadore@ worked on the upgrade of GCC_DEFAULT in Mk/bsd.default-versions.mk from 10 to 11, opening bug reports based on antoine@'s exp-runs and fixing some: many thanks to all those that helped with this task.
+   The GCC_DEFAULT update from GCC 10 to GCC 11 has now been committed by gerald@ and happened in time for the next quarterly branch.
+   link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378]
+
+ * pkubaj@ switched GCC bootstrapping to use Link Time Optimization for GCC itself for GCC 11 and newer by introducing a new option enabled by default.
+   Building with LTO_BOOTSTRAP enabled requires significant amounts of memory and time.
+   How much resources are actually needed depends on your configuration (e.g. are you building from ports or with poudriere? What is your architecture?).
+   To give an idea, link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264949#c17[a user reported needing 5 GiB of tmpfs], while in link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254#c2[PR 265254] a need of about 130 GB of memory is estimated due to an excessive amount of processes spawning (see also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106328).
+   Consider disabling LTO_BOOTSTRAP in favor of STANDARD_BOOTSTRAP (or disabling BOOTSTRAP altogether) in case that is a problem.
+
+ * pkubaj@ also added lang/gcc12 and lang/gcc13-devel ports and updated lang/gcc9 to 9.5.
+
+ * Help is still needed with these three changes to work through with upstream GCC (requires src expertise, not ports):
+
+     ** upstreaming lang/gcc11/patch-gets-no-more
+     ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support
+     ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874]
diff --git a/website/content/en/status/report-2022-04-2022-06/golang_riscv64.adoc b/website/content/en/status/report-2022-04-2022-06/golang_riscv64.adoc
new file mode 100644
index 0000000000..2469697485
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/golang_riscv64.adoc
@@ -0,0 +1,12 @@
+=== go on FreeBSD riscv64
+
+Links: +
+link:https://github.com/golang/go[golang Home Page] URL: link:https://github.com/golang/go[https://github.com/golang/go] +
+link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[FreeBSD riscv64 github repo] URL: link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[https://github.com/MikaelUrankar/go/tree/freebsd_riscv64] +
+link:https://github.com/golang/go/issues/53466[FreeBSD riscv64 golang issue] URL: link:https://github.com/golang/go/issues/53466[https://github.com/golang/go/issues/53466]
+
+Contact: Mikaël Urankar <mikael@FreeBSD.org> +
+Contact: Dmitri Goutnik <dmgk@FreeBSD.org>
+
+Work has been done to port go on FreeBSD riscv64 which builds and passes all run.bash tests, including cgo (tested under QEMU and on Unmatched).
+A pull request is created upstream and the proposal has been added to the active column of the proposals project and will be reviewed at the weekly proposal review meetings.
diff --git a/website/content/en/status/report-2022-04-2022-06/if_ovpn.adoc b/website/content/en/status/report-2022-04-2022-06/if_ovpn.adoc
new file mode 100644
index 0000000000..45186d75e1
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/if_ovpn.adoc
@@ -0,0 +1,22 @@
+=== OpenVPN DCO
+
+Links: +
+link:https://reviews.freebsd.org/D34340[D34340] URL: link:https://reviews.freebsd.org/D34340[D34340] +
+link:https://community.openvpn.net/openvpn/wiki/DataChannelOffload[OpenVPN wiki] URL: https://community.openvpn.net/openvpn/wiki/DataChannelOffload[OpenVPN wiki]
+
+Contact: Kristof Provost <kp@FreeBSD.org>
+
+OpenVPN DCO (or Data Channel Offload) moves OpenVPN data packet processing into the kernel.
+
+Traditionally OpenVPN uses a tun(4) interface to transmit and receive packets.
+In this setup received packets are received by the kernel, passed to the OpenVPN application for decryption, then passed back into the kernel for network stack processing.
+This requires several transitions between kernel- and userspace, and naturally imposes a performance cost.
+
+The new if_ovpn OpenVPN DCO offload driver performs the encryption/decryption entirely within the kernel, improving performance.
+
+Initial performance testing shows throughput improved from around 660Mbit/s to around 2Gbit/s.
+
+The userspace OpenVPN code also requires modification to use the new if_ovpn offload driver.
+This is expected to be part of a future 2.6.0 OpenVPN release.
+
+Sponsor: Rubicon Communications, LLC ("Netgate")
diff --git a/website/content/en/status/report-2022-04-2022-06/igt-gpu-tools.adoc b/website/content/en/status/report-2022-04-2022-06/igt-gpu-tools.adoc
new file mode 100644
index 0000000000..f14115788c
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/igt-gpu-tools.adoc
@@ -0,0 +1,28 @@
+=== Feature Complete Port of Intel's igt-gpu-tools
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2022Projects/ImprovingTheLinuxKPICompatibilityLayerForTheFreeBSDGraphicsStack/[FreeBSD Wiki Project Page] URL:
+link:https://wiki.freebsd.org/SummerOfCode2022Projects/ImprovingTheLinuxKPICompatibilityLayerForTheFreeBSDGraphicsStack/[https://wiki.freebsd.org/SummerOfCode2022Projects/ImprovingTheLinuxKPICompatibilityLayerForTheFreeBSDGraphicsStack] +
+link:https://cdaemon.com/tags/gsoc2022/[Status Reports] URL:
+link:https://cdaemon.com/tags/gsoc2022/[https://cdaemon.com/tags/gsoc2022]
+
+Contact: Jake Freeland <jfree@freebsd.org>
+
+Intel’s igt-gpu-tools serves as a generic testing suite for drm drivers on Linux.
+The igt-gpu-tools suite is separated into tests and tools that target kms, memory management, and command submission.
+The utility provides low-level reporting for transparent tracking of kernel changes and efficient debugging of modern drm drivers.
+
+Porting the project to FreeBSD could introduce greater stability in future releases of FreeBSD’s LinuxKPI-driven drm drivers.
+A proper kms-driven testing suite could also increase code output and bring the FreeBSD desktop experience up to speed with the Linux codebase.
+
+The project officially started under FreeBSD's Google Summer of Code program on June 13, 2022.
+My adapted code can compile with non-FreeBSD compatible snippets removed.
+The plan is to reimplement these stripped components in a POSIX compliant fashion.
+
+Notable incompatible code includes: debugfs, libkmod, libprocps, Linux performance events, and Linux userfaultfd.
+If you would like to assist in the porting of libkmod or libprocps into the ports tree, don't hesitate to contact me.
+
+When the FreeBSD compatible code is complete, I will run the modified igt tests using a host of graphics processors on FreeBSD 14.0-CURRENT.
+If all is well, the project's diff will be submitted into the ports tree.
+
+Sponsor: FreeBSD Google Summer of Code
diff --git a/website/content/en/status/report-2022-04-2022-06/intro.adoc b/website/content/en/status/report-2022-04-2022-06/intro.adoc
new file mode 100644
index 0000000000..0a9a81e13a
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/intro.adoc
@@ -0,0 +1,10 @@
+Here is the second quarterly report of 2022, with 26 reports included.
+
+This quarter the quarterly team managed to publish the report much faster and, hopefully, with much fewer mistakes.
+If however you notice some errors, please report them so that we can correct them and also add some automatic checks in our tools to prevent them in the future and stay as efficient as possible in the publication process.
+
+We would also like to remind you that if for any reason you need more time to submit a quarterly report, the team will wait for you, but please warn us so that we are aware that some report is still missing.
+
+Many thanks to all those that have chosen to share their work with the FreeBSD community through the quarterly reports.
+
+Lorenzo Salvadore, on behalf of the status report team.
diff --git a/website/content/en/status/report-2022-04-2022-06/kde.adoc b/website/content/en/status/report-2022-04-2022-06/kde.adoc
new file mode 100644
index 0000000000..e460dbdafa
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/kde.adoc
@@ -0,0 +1,53 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] +
+link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@ as well, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine.
+The notes below describe *mostly* ports for KDE, but also include items of import to the entire desktop stack.
+
+==== KDE Stack
+
+KDE Gear releases happen each quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release each month as well.
+These (large) updates land shortly after their upstream release and are not listed separately.
+
+* *astro/kstars* latest release 3.5.9.
+* *deskutils/grantleetheme* got an entry in UPDATING because of some unusual changes to the installed structure of the port.
+* *deskutils/kalendar* joined the KDE Gear releases.
+* *devel/okteta* updates to the binary (and octal and hexadecimal) data viewer and editor.
+* *finance/kraft* needed specific build-fixes for newer KDE Frameworks.
+* *games/gcompris-qt* expanded, new releases, and now supports more image formats (needed for some activities).
+* *graphics/digikam* no longer needs a SQL server during the build.
+* *graphics/krita* was updated to 5.0.5, likely the last 5.0 version.
+* *math/labplot* has a huge number of new features in recent releases, well worth looking at if you need any kind of data-plotting.
+* *net-im/ruqola* was updated.
+  This is a Qt-styled Rocket chat application.
+* *www/falkon* joined the KDE Gear releases.
+
+==== Related Applications
+
+* *archivers/quazip* was updated.
+* *deskutils/semantik* updated.
+* *devel/py-qt5-pyqt* updated so that the port now pulls in DBus as well.
+  DBus is needed by nearly all desktop Qt applications, including those written in Python.
+* *devel/qcoro* had build issues on certain FreeBSD versions, resolved.
+* *devel/qtcreator* updated with each new release.
+* *devel/qt5* had its infrastructure updated in ports so it does not produce strange error messages during de-installation.
+* *graphics/ksnip* and related libraries updated to recent releases.
+* Matrix clients Nheko (*net-im/nheko*) and Neochat (*net-im/neochat*) were updated following releases and library bumps.
+* *x11/rsibreak* updated; helps prevent injury while writing long quarterly reports.
+
+==== Elsewhere
+
+* *devel/appstream* update supports more application-information.
+* *devel/cmake* prefers generic python3 over versioned-python3, if users have multiple python3 ports *and* lang/python3 installed.
+* *devel/dbus* updated.
+* *graphics/poppler* updated several times.
+* *graphics/ImageMagick* (both 6 and 7) updated several times.
+* *multimedia/gstreamer* updated.
diff --git a/website/content/en/status/report-2022-04-2022-06/linuxulator.adoc b/website/content/en/status/report-2022-04-2022-06/linuxulator.adoc
new file mode 100644
index 0000000000..0d6d159d6b
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/linuxulator.adoc
@@ -0,0 +1,23 @@
+=== Linux compatibility layer update
+
+Contact: Dmitry Chagin <dchagin@FreeBSD.org> +
+Contact: Edward Tomasz Napierala <trasz@FreeBSD.org>
+
+The goal of this project is to improve FreeBSD's ability to execute unmodified Linux binaries.
+Current support status of specific Linux applications is being tracked at the link:https://wiki.freebsd.org/LinuxApps[Linux app status Wiki page].
+
+Implementation of the Y2k38 Linux project is mostly finished; all '*_time64()' system calls are committed.
+
+The state of the arm64 Linux emulation layer was brought to the state of the amd64 Linux emulation layer:
+i.e., implemented the vDSO, machine dependent futexes, signals delivery.
+
+The thread affinity system calls were modified to implement Linux semantics.
+
+In total, over 50 bugs were fixed; glibc-2.35 tests suite reports less than 80 failed tests.
+
+All changes in the Linux emulation layer are merged to the stable/13 branch.
+
+Initial support for fancy Linux system call tracing has been added to libsysdecode and kdump.
+There is ongoing work to make tracing more syscalls work.
+
+Sponsor: EPSRC (Edward’s work)
diff --git a/website/content/en/status/report-2022-04-2022-06/lldb.adoc b/website/content/en/status/report-2022-04-2022-06/lldb.adoc
new file mode 100644
index 0000000000..93a93ab088
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/lldb.adoc
@@ -0,0 +1,24 @@
+=== Ongoing work on LLDB multiprocess debugging support
+
+Links: +
+link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[Moritz Systems Project Description] URL: link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[https://www.moritz.systems/blog/multiprocess-support-for-lldb/] +
+link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[Progress Report 1] URL: link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/]
+
+Contact: Kamil Rytarowski <kamil@moritz.systems> +
+Contact: Michał Górny <mgorny@moritz.systems>
+
+According to the upstream description, "LLDB is a next generation, high-performance debugger. It is built as a set of reusable components which highly leverage existing libraries in the larger LLVM Project, such as the Clang expression parser and LLVM disassembler."
+
+FreeBSD includes LLDB in the base system.
+The previous sponsored projects improved LLDB, to make it a credible debugger for the base system, although it still has a few limitations compared to the contemporary versions of GNU GDB.
+This project started in April 2022.
+It aims to implement full support for debugging multiple processes simultaneously.
+
+At the start of the project, LLDB featured very limited support for multiprocess debugging.
+The client featured support for debugging multiple independent processes simultaneously via maintaining multiple connections to different server instances.
+Thanks to our earlier work, the server was able to process `fork(2)` and `vfork(2)` calls and either detach the newly forked child and continue tracing the parent process, or detach the parent and follow the child (equivalent to GDB's `follow-fork-mode` setting).
+
+Once the project is finished, LLDB will be able to trace an arbitrary number of forked processes simultaneously (equivalent to GDB's `detach-on-fork off`).
+Full support for the multiprocess extension to the GDB Remote Serial Protocol will be implemented, as well as partial support for the non-stop extension that will enable multiple processes to be resumed and stopped independently.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-04-2022-06/makefs-zfs.adoc b/website/content/en/status/report-2022-04-2022-06/makefs-zfs.adoc
new file mode 100644
index 0000000000..7c1cf09fd3
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/makefs-zfs.adoc
@@ -0,0 +1,22 @@
+=== ZFS support in makefs(8)
+
+Links: +
+link:https://lists.freebsd.org/archives/freebsd-hackers/2022-May/001128.html[Mailing list post] URL: link:https://lists.freebsd.org/archives/freebsd-hackers/2022-May/001128.html[https://lists.freebsd.org/archives/freebsd-hackers/2022-May/001128.html] +
+link:https://reviews.freebsd.org/D35248[makefs(8) code review] URL: link:https://reviews.freebsd.org/D35248[link:https://reviews.freebsd.org/D35248]
+link:https://reviews.freebsd.org/D34426[release(7) code review] URL: link:https://reviews.freebsd.org/D34426[link:https://reviews.freebsd.org/D34426]
+
+Contact: Mark Johnston <markj@FreeBSD.org>
+
+makefs(8) is a utility, originating in NetBSD, that creates file system images entirely in userspace.
+It is a useful component of a toolchain to build virtual machine (VM) images since it does not require any special privileges, unlike the approach of formatting a character device, mounting the fresh file system, and copying files onto it.
+Moreover, makefs can create reproducible images and aims to minimize resource consumption.
+Currently, FreeBSD's makefs can build UFS, cd9660, and msdos (FAT) file system images.
+
+Recent work enables the creation of ZFS images by makefs.
+This makes it easier to build ZFS-based VM images.
+makefs' ZFS support includes the ability to create multiple datasets, with each mapped to a directory in the input file hierarchy.
+Many ZFS features are not supported however, as the implementation provides only what is needed to get reproducible root pools.
+
+Follow-up work enables the creation of ZFS-based VM and cloud images by the release(7) framework, using this new makefs extension.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-04-2022-06/openssh.adoc b/website/content/en/status/report-2022-04-2022-06/openssh.adoc
new file mode 100644
index 0000000000..75439f4c9b
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/openssh.adoc
@@ -0,0 +1,19 @@
+=== Base System OpenSSH Update
+
+Links: +
+link:https://www.openssh.com/[OpenSSH] URL: link:https://www.openssh.com/[https://www.openssh.com/] +
+link:https://www.openssh.com/txt/release-8.9[OpenSSH 8.9 release notes] URL:https://www.openssh.com/txt/release-8.9[https://www.openssh.com/txt/release-8.9] +
+link:https://www.openssh.com/txt/release-9.0[OpenSSH 9.0 release notes] URL:https://www.openssh.com/txt/release-9.0[https://www.openssh.com/txt/release-9.0]
+
+Contact: Ed Maste <emaste@freebsd.org>
+
+OpenSSH, a suite of remote login and file transfer tools, was updated from version 8.8p1 to 9.0p1 in the FreeBSD base system.
+
+It has not yet been merged to the stable/13 and stable/12 branches.
+I anticipate doing so in July.
+
+*NOTE*:
+OpenSSH 9.0p1 switches scp(1) from using the legacy scp/rcp protocol to using the SFTP protocol by default.
+The `-O` flag is available to use the previous protocol instead.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-04-2022-06/pantheon.adoc b/website/content/en/status/report-2022-04-2022-06/pantheon.adoc
new file mode 100644
index 0000000000..927e225483
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/pantheon.adoc
@@ -0,0 +1,26 @@
+=== Pantheon desktop on FreeBSD
+
+Links: +
+link:https://elementary.io/[elementary OS] URL: link:https://elementary.io/[https://elementary.io] +
+link:https://codeberg.org/olivierd/freebsd-ports-elementary[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-elementary[https://codeberg.org/olivierd/freebsd-ports-elementary] +
+
+Contact: Olivier Duchateau <duchateau.olivier@gmail.com>
+
+The Pantheon desktop environment is designed for elementary OS.
+It builds on GNOME technologies (such as Mutter, GNOME Shell, GTK 3 and 4) and it is written in Vala.
+
+The goal is to have a new desktop for users.
+Some features are not well supported, but we can have full session.
+
+The repository contains Mk/Uses framework `elementary.mk`, official applications, and curated ports which depend of `x11-toolkits/granite` (total of 56 new ports).
+
+I have submitted several patches, especially:
+
+* `x11-toolkits/granite7`
+* `devel/libgee` update to 0.20.5 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262893[bug #262893]
+* `sysutils/bamf` update to 0.5.6 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264203[bug #264203]
+
+==== Open tasks
+
+* Add support of user settings (it is very Ubuntu-centric)
+* Finish porting wingpanel-indicator-power (power management)
diff --git a/website/content/en/status/report-2022-04-2022-06/pf.adoc b/website/content/en/status/report-2022-04-2022-06/pf.adoc
new file mode 100644
index 0000000000..e2d14b25d6
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/pf.adoc
@@ -0,0 +1,32 @@
+=== pf status update
+
+Contact: Kristof Provost <kp@FreeBSD.org> +
+Contact: Reid Linnemann <rlinnemann@netgate.com>
+
+==== Ethernet
+
+pf recently grew support for filtering on Ethernet layer.
+See the 2021q2 pf_ethernet report.
+
+Since then the Ethernet layer filtering has been extended with:
+
+ * anchor support
+ * ability to look into the layer 3 header, for matching with source/destination IP(v4/v6) addresses
+ * table support for IP address matching
+ * direct dispatch to dummynet
+ * pass Ethernet layer packets directly to dummynet, rather than tagging the packets and relying on layer 3 to handle dummynet
+
+==== Dummynet
+
+pf recently started being able to use dummynet for packet scheduling.
+This support has been extended and improved, and is now believed to be ready for production.
+
+One notable fix is that reply-to/route-to'd traffic is now subject to dummynet scheduling as well.
+
+==== Last match timestamp
+
+pf now tracks when a rule was last matched.
+Similar to ipfw rule timestamps, these timestamps internally are uint32_t snaps of the system "wall time" clock in seconds. (See time(9).)
+The timestamp is CPU local and updated each time a rule or a state is matched.
+
+Sponsor: Rubicon Communications, LLC ("Netgate")
diff --git a/website/content/en/status/report-2022-04-2022-06/portmgr.adoc b/website/content/en/status/report-2022-04-2022-06/portmgr.adoc
new file mode 100644
index 0000000000..ff41db260c
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/portmgr.adoc
@@ -0,0 +1,37 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[https://www.FreeBSD.org/ports/] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[https://www.freebsd.org/portmgr/] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+The number of ports is slightly above 30,000.
+The last quarter saw 9,137 commits by 151 committers on the "main" and 589 commits by 61 committers on the "2022Q2" branch.
+At the time of writing, there are 2,700 open ports PRs of which 682 are unassigned.
+Compared to the previous quarter, there was a slight decrease in commit activity and a constant number of PRs.
+Note: Freshports appears to overcount substantially.
+This quarter's ports count was derived differently and is not comparable with the previous quarter's.
+
+During the last quarter, portmgr
+welcomed back salvadore@ but also said goodbye to seven ports committers due to lack of activity.
+
+In its bi-weekly meetings, portmgr discussed the following topics:
+* the future of ca_root_nss
+* feasibility of the base system providing certain .pc files
+* ways to deal with incompatibilities in kernel module ports on minor version upgrades of the base system
+
+Following a discussion among developers, portmgr decided to grant all documentation and source
+committers approval to fix any documentation-related error in the Ports Tree which does not affect its functionality.
+
+The following changes were made to the Ports Tree during 2022q2:
+* pkg got updated to version 1.18.3, Firefox to version 102.0 and Chromium to version 103.0.50060.53
+* Default versions of GCC, Lazarus, Python and Ruby got updated to respectively 11 (powerpcspe keeps version 8), 2.2.2, 3.9, and 3.0.
+* Two new USES were added, gstreamer to support ports based on GStreamer plugins and pytest to help testing with pytest.
diff --git a/website/content/en/status/report-2022-04-2022-06/releng.adoc b/website/content/en/status/report-2022-04-2022-06/releng.adoc
new file mode 100644
index 0000000000..c0952e35e0
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/releng.adoc
@@ -0,0 +1,23 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.1R/schedule/[FreeBSD 13.1-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.1R/schedule/[https://www.freebsd.org/releases/13.1R/schedule/] +
+link:https://www.freebsd.org/releases/13.1R/announce/[FreeBSD 13.1-RELEASE announcement] URL: link:https://www.freebsd.org/releases/13.1R/announce/[https://www.freebsd.org/releases/13.1R/announce/] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[https://download.freebsd.org/releases/ISO-IMAGES/] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[https://download.freebsd.org/snapshots/ISO-IMAGES/]
+
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the second quarter of 2022, the Release Engineering Team completed work on the 13.1-RELEASE cycle.
+This is the second release from the stable/13 branch.
+Throughout the release cycle, three BETA builds and six RC (release candidate) builds have occurred, moving the final release date from April 21, 2022 to May 16, 2022, as some last-minute issues were identified.
+
+We thank all FreeBSD developers and contributors for testing the 13.1-RELEASE, reporting problems, and being diligent with proposed changes as the cycle progressed.
+
+Additionally throughout the quarter, several development snapshots builds were released for the *main*, *stable/13*, and *stable/12* branches.
+
+Sponsor: Rubicon Communications, LLC ("Netgate")
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-04-2022-06/shp_rand.adoc b/website/content/en/status/report-2022-04-2022-06/shp_rand.adoc
new file mode 100644
index 0000000000..96d351c478
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/shp_rand.adoc
@@ -0,0 +1,17 @@
+=== Shared page address randomization
+
+Links: +
+link:https://reviews.freebsd.org/D35392[D35392] link:https://reviews.freebsd.org/D35393[D35393]
+link:https://reviews.freebsd.org/D35349[D35349]
+
+Contact: Kornel Duleba <mindal@semihalf.com> +
+Contact: Marcin Wojtas <mw@FreeBSD.org>
+
+The shared page is an R/X page that is mapped into each process by the image activator.
+It stores the signal trampoline, as well as other metadata e.g. information needed to implement user space timecounters.
+Previously it was mapped at the top of the process virtual address space.
+With the described changes its address will be randomized.
+We plan to turn the feature on by default for 64bit binaries, across all architectures.
+Currently the patches are under review and await approval.
+
+Sponsor: Stormshield
diff --git a/website/content/en/status/report-2022-04-2022-06/superpages.adoc b/website/content/en/status/report-2022-04-2022-06/superpages.adoc
new file mode 100644
index 0000000000..c6e4d3783a
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/superpages.adoc
@@ -0,0 +1,19 @@
+=== Medium-sized superpages on arm64 and beyond
+
+Contact: Eliot H. Solomon <ehs3@rice.edu> +
+Contact: Alan L. Cox <alc@rice.edu> +
+
+The 64-bit ARM architecture's page table descriptor format contains a flag called the Contiguous bit.
+This tells the MMU that it can cache an aligned, physically contiguous group of 16 page table entries which have identical permissions and attributes using only 1 TLB entry.
+
+The Contiguous bit, as well as the conceptually similar Svnapot extension to the RISC-V architecture, allows for the use of 64 KiB superpages.
+These medium-sized superpages can bring to smaller memory objects the address-translation speedup typically associated with more traditional 2 MiB superpages.
+
+This project focuses on bringing support for medium-sized superpages to FreeBSD.
+So far, we have modified the arm64 pmap code to automatically utilize 64 KiB superpages by detecting physically contiguous page table entries and promoting them using the Contiguous bit.
+Now, we are working to adapt the kernel's superpage reservation module to support 64 KiB reservations in addition to the current 2 MiB ones.
+Adding medium-sized reservations will allow the virtual memory system to explicitly allocate pieces of memory which fit the requirements for superpage promotion, rather than just hoping that they occur by chance.
+
+Our goal is to accomplish this in a general way that makes it possible to specify multiple arbitrary power-of-two reservation sizes, making it easier to take advantage of hardware features on other architectures like Ryzen's PTE Coalescing, which transparently merges groups of 4 KiB page table entries into medium-sized superpages.
+
+Sponsor: Department of Computer Science, Rice University
diff --git a/website/content/en/status/report-2022-04-2022-06/valgrind.adoc b/website/content/en/status/report-2022-04-2022-06/valgrind.adoc
new file mode 100644
index 0000000000..b14521de2a
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/valgrind.adoc
@@ -0,0 +1,46 @@
+=== Valgrind - Numerous bugfixes and updates for 13.1 / 14.0
+
+Links +
+link:https://www.valgrind.org/[Valgrind Home Page] URL:
+link:https://www.valgrind.org/[https://www.valgrind.org/] +
+link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News]
+URL:
+link:https://www.valgrind.org/docs/manual/dist.news.html[https://www.valgrind.org/docs/manual/dist.news.html]
+
+Contact: Paul Floyd <pjfloyd@wanadoo.fr>
+
+A quite significant number of bug fixes have been made to Valgrind on FreeBSD over the past few months.
+In particular, the i386 version has largely 'caught up' with its bigger brother amd64.
+
+The devel/valgrind-devel port has been bumped up to 3.20.0.g20220612,1 which includes all of the following changes.
+If you use Valgrind regularly please switch to valgrind-devel.
+
+Here is a list of changes since the release of Valgrind 3.19.0 (which is the version available with the devel/valgrind port).
+
+* incorrect signal resumption if a signal arrives when Valgrind is saving the carry flag for a syscall
+* fixed reading DWARF debuginfo from PT_LOADs generated by lld post version 9, which splits the RW segment into two parts, this affects mainly shared libraries (.so files)
+* on i386 implement correctly the management of thread GDTs which was limiting applications to only ever creating 8192 threads
+* make the first page of the 'brk' invalid for addressing
+* analysis and cleanup of the regression test suite and in particular tweak the i386 leak tests to not detect possible leaks due to left over pointers in ECX.
+* make coredumps readable by lldb
+* improve the setting of errno by C allocating functions
+* fix building of Valgrind with llvm-devel (15.0.0)
+
+For FreeBSD 13.1 / 14.0 there are
+
+* syscall wrappers for funlinkat, copy_file_range, swapoff, shm_open2
+* add K_INFO handling to fcntl
+* add handling for new auxv entries
+* added some default suppressions for DRD and Helgrind
+
+There is now an initial version of vgdb invoker support - this allows vgdb to use ptrace to force valgrind to poll for gdb commands.
+This is not yet available in the ports versions.
+
+That does not leave much in the way of outstanding issues.
+I expect that 14.0 and newer versions of llvm will keep on requiring support.
+Apart from that there is
+
+* some small problems with error messages getting the correct source
+information
+* better core dumps (low priority)
+* TLS (thread local storage) handling for Helgrind (difficult if not impossible)
diff --git a/website/content/en/status/report-2022-04-2022-06/wifi.adoc b/website/content/en/status/report-2022-04-2022-06/wifi.adoc
new file mode 100644
index 0000000000..6d70d54153
--- /dev/null
+++ b/website/content/en/status/report-2022-04-2022-06/wifi.adoc
@@ -0,0 +1,35 @@
+=== Wireless updates
+
+Links: +
+link:https://wiki.freebsd.org/WiFi/Iwlwifi[Intel iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi]
+link:https://wiki.freebsd.org/WiFi/Rtw88[Realtek rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88]
+link:https://wiki.freebsd.org/WiFi/Rtw89[Realtek rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+The overall project aims to bring support for newer chipsets to FreeBSD currently using LinuxKPI compat code backed by native net80211 and kernel code.
+In addition the aim is to continue work towards supporting newer wireless standards.
+During the second quarter 40 commits went into FreeBSD CURRENT.
+With more users trying multiple drivers support time has also gone up.
+
+An earlier version of the Intel iwlwifi-derived wireless driver shipped in 13.1-RELEASE bringing this work into a first FreeBSD release.
+The iwlwifi driver and firmware were since updated in CURRENT and stable/13 again as part of ongoing development.
+Changes in files shared with the upstream Intel Linux version of the driver are now less than 400 lines.
+Lately a longer-standing problem for older chipsets was (hopefully) solved allowing iwm(4)-supported cards to work with iwlwifi(4) again after almost three months.
+The main focus for the project until the end of the year will most exclusively be getting us to contemporary speeds.
+
+On April 1st, using the same LinuxKPI infrastructure built mostly with the iwlwifi work, Realtek's rtw88(4) driver got committed into CURRENT.
+Due to an issue with DMA the next weeks a workaround was developed and put into the tree so users no longer have to patch the kernel.
+The driver still needs a tunable set in loader.conf for machines with more than 4GB of physical memory.
+This tunable allowed the driver to be merged to stable/13 in June followed by further updates in CURRENT and stable/13.
+As the USB parts for rtw88 based chipsets are prepared to be included in Linux, work has started (needing more time) to prepare FreeBSD to be able to support the USB parts as well.
+
+During the last months Realtek's rtw89 has already been compiling and remains a work in progress to run stably and associate before it can be enabled in CURRENT.
+
+Thanks to all the users for testing and reporting back, patiently waiting for the next update, bugfix, or just a reply from me.
+It is a great pleasure to work with you!
+Keep sending the bug reports to me, but remember that your thanks should go to the FreeBSD Foundation for making most of this possible.
+
+For the latest state of the development, please follow the freebsd-wireless mailing list and check the wiki pages.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-07-2022-09/_index.adoc b/website/content/en/status/report-2022-07-2022-09/_index.adoc
new file mode 100644
index 0000000000..75c2b97022
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/_index.adoc
@@ -0,0 +1,168 @@
+---
+title: "FreeBSD Quarterly Status Report Third Quarter 2022"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2022-07-2022-09
+:lang:	en
+
+include::shared/{lang}/urls.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+Entries from the various official and semi-official teams, as found in the
+link:../../administration/[Administration Page].
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+Projects that span multiple categories, from the kernel and userspace to the
+Ports Collection or external projects.
+
+include::{reports-path}/openstack-on-freebsd.adoc[]
+
+'''
+
+include::{reports-path}/cloud-init.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+Changes affecting the base system and programs in it.
+
+include::{reports-path}/bhyve-debug-server-enhancements.adoc[]
+
+'''
+
+include::{reports-path}/pjdfstest.adoc[]
+
+'''
+
+include::{reports-path}/lldb.adoc[]
+
+'''
+
+include::{reports-path}/kinst.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+Updates to kernel subsystems/features, driver support, filesystems, and more.
+
+include::{reports-path}/ena.adoc[]
+
+'''
+
+include::{reports-path}/wtap.adoc[]
+
+'''
+
+include::{reports-path}/iwlwifi.adoc[]
+
+'''
+
+include::{reports-path}/wifi.adoc[]
+
+'''
+
+include::{reports-path}/ufs_snapshots.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+Updating platform-specific features and bringing in support for the new hardware
+platform.
+
+include::{reports-path}/firecracker.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+Noteworthy changes in the documentation tree, manual pages, or new external
+books/documents.
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+Changes affecting the Ports Collection, whether sweeping changes that touch most
+of the tree, or individual ports themselves.
+
+include::{reports-path}/calendar-data.adoc[]
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/lsof.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+Many projects build upon FreeBSD or incorporate components of FreeBSD into their
+project. As these projects may be of interest to the broader FreeBSD community,
+we sometimes include brief updates submitted by these projects in our quarterly
+report. The FreeBSD project makes no representation as to the accuracy or
+veracity of any claims in these submissions.
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2022-07-2022-09/bhyve-debug-server-enhancements.adoc b/website/content/en/status/report-2022-07-2022-09/bhyve-debug-server-enhancements.adoc
new file mode 100644
index 0000000000..bc3f14f68f
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/bhyve-debug-server-enhancements.adoc
@@ -0,0 +1,24 @@
+=== bhyve debug server enhancements
+
+Links: +
+link: https://wiki.freebsd.org/SummerOfCode2022Projects/BhyveDebugServerEnhancements[Wiki project page] +
+link: https://reviews.freebsd.org/D35826[Differential] +
+Contact: Bojan Novković <bojan.novkovic@kset.org>
+
+The goal of this project was to enhance the functionality of bhyve’s debug server.
+Several existing features related to single-stepping are tied to Intel-specific VM mechanisms, which severely impairs bhyve’s debugging functionality on other x86 platforms.
+The first goal dealt with extending single-stepping support to AMD hosts.
+The second goal was to add support for hardware watchpoints using the guest OS's hardware debugging registers.
+
+The project was carried out under Google's Summer of Code program and was finished around the end of July.
+The project's wiki also contains detailed documentation regarding several implemented mechanisms.
+
+The changes can be summarized as follows:
+
+* Support for placing software breakpoints inside virtual machines on AMD platforms,
+* Support for single-stepping virtual machines on AMD platforms,
+* Support for placing hardware watchpoints inside virtual machines on Intel and AMD platforms.
+
+Any feedback, comments and discussions are welcome and would be greatly appreciated.
+
+Sponsor: Google Summer of Code
diff --git a/website/content/en/status/report-2022-07-2022-09/calendar-data.adoc b/website/content/en/status/report-2022-07-2022-09/calendar-data.adoc
new file mode 100644
index 0000000000..7800956771
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/calendar-data.adoc
@@ -0,0 +1,20 @@
+=== Calendar-data: License added
+
+Links +
+link:https://github.com/freebsd/calendar-data[GitHub calendar-data repository] URL:
+link:https://github.com/freebsd/calendar-data[https://github.com/freebsd/calendar-data] +
+
+Contact: Stefan Eßer <se@FreeBSD.org> +
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> +
+Contact: Warner Losh <imp@FreeBSD.org>
+
+The port deskutils/calendar-data contains calendar files for the BSD calendar program and is maintained by se@.
+The data for this port lives in a link:https://github.com/freebsd/calendar-data[GitHub repository], which at the moment is maintained mainly by salvadore@.
+
+About two years ago, the calendar files in the base repository were removed from there and a new repository was created on GitHub; see also this link:https://reviews.freebsd.org/D26883[Phabricator review about the creation of the associated port].
+This improvement allows calendar files to be updated independently from the base system.
+
+Unfortunately, when the repository was created, it was forgotten to add a license to it.
+The issue has been solved this quarter with this link:https://github.com/freebsd/calendar-data/pull/9[pull request] submitted by salvadore@ and merged by imp@.
+Since the data originally came from the src repository, the same licence applies.
+If in the past you have contributed to the calendar files with different licensing assumptions, please inform us so that we can license your contributions accordingly or remove them.
diff --git a/website/content/en/status/report-2022-07-2022-09/ci.adoc b/website/content/en/status/report-2022-07-2022-09/ci.adoc
new file mode 100644
index 0000000000..57957443a2
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/ci.adoc
@@ -0,0 +1,55 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] +
+link:https://wiki.freebsd.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.freebsd.org/Jenkins[https://wiki.freebsd.org/Jenkins] +
+link:https://wiki.freebsd.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.freebsd.org/HostedCI[https://wiki.freebsd.org/HostedCI] +
+link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.freebsd.org/3rdPartySoftwareCI[https://wiki.freebsd.org/3rdPartySoftwareCI] +
+link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] +
+link:https://lists.freebsd.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.freebsd.org/subscription/dev-ci[https://lists.freebsd.org/subscription/dev-ci]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+The FreeBSD CI team maintains the continuous integration system of the FreeBSD project.
+The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results.
+The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs.
+The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure.
+
+During the third quarter of 2022, we continued working with the contributors and developers in the project to fulfill their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD.
+
+Important completed tasks:
+
+* Expand the artifact storage space for adding more types of artifacts and longer retention period.
+* Present Testing/CI Status Update in link:https://wiki.freebsd.org/DevSummit/202209[EuroBSDcon 2022 Developer Summit]
+* Add link:https://ci.freebsd.org/job/FreeBSD-main-powerpc-images/[main-powerpc-images] and link:https://ci.freebsd.org/job/FreeBSD-main-powerpcspe-images/[main-powerpcspe-images]
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Testing and merging pull requests in link:https://github.com/freebsd/freebsd-ci/pulls[the FreeBSD-ci repo]
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository
+* Updating documents on wiki
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Adding more external toolchain related jobs
+* Improving maturity of the hardware lab and adding more hardware for testing
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.freebsd.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-07-2022-09/cloud-init.adoc b/website/content/en/status/report-2022-07-2022-09/cloud-init.adoc
new file mode 100644
index 0000000000..0a9236bba9
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/cloud-init.adoc
@@ -0,0 +1,22 @@
+=== FreeBSD as a Tier 1 cloud-init Platform
+
+Links: +
+link:https://https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[https://cloud-init.io/] +
+link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[https://cloudinit.readthedocs.io/en/latest/] +
+link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst] +
+
+Contact: Mina Galić <me+FreeBSD@igalic.co>
+
+cloud-init is the standard way of provisioning servers in the cloud.
+Unfortunately, cloud-init support for operating systems other than Linux is rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform.
+To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support.
+The broader plan is to lift support across all BSDs.
+
+The project deliverables include completing an extraction of certain networking classes, implementing man:ifconfig[8] and man:login.conf[5] parsers, implementing IPv6 configuration, creating man:devd.conf[5] rules for Azure, and link:{handbook}[FreeBSD Handbook] documentation about productionizing FreeBSD.
+
+On the way there, any BSD-related bugs found in modules and documentation will also be fixed.
+
+People interested in helping with the project can help with testing new features and fixes through package:net/cloud-init-devel[], which will be updated on a weekly basis.
+Further, people with access to, and experience with, OpenBSD and NetBSD are also highly welcome to help.
+
+Sponsor: The FreeBSD Foundation +
diff --git a/website/content/en/status/report-2022-07-2022-09/clusteradm.adoc b/website/content/en/status/report-2022-07-2022-09/clusteradm.adoc
new file mode 100644
index 0000000000..207b0c47e9
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/clusteradm.adoc
@@ -0,0 +1,35 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications.
+In this quarter, the team has worked on the following:
+
+* Added additional storage to the CI system.
+It will help store more artifacts.
+* link:https://www.vuxml.org/freebsd/index.html[VuXML] deployed in all official mirrors.
+It speeds up the `pkg audit` functionality.
+* A new (and additional) monitoring system is in place.
+* A few old and faulty machines were decommissioned.
+* Moved several services to newer hardware.
+* Regular cluster-wide software upgrades
+* Regular support for FreeBSD.org user accounts
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+
+Work in progress:
+
+* git infra: Add `--filter` support.
+* Work with the PowerPC team to improve the package builders, universal, and reference machines.
+* Site audit at our primary site: inventory of spares and other miscellanea occupying space in our cabinets.
+* Discussions with link:https://www.juniper.net/[Juniper] about a donation of new switches for our primary site.
+* Plan for a large scale network upgrade at our primary site.
+* Cluster refresh (more extended project).
+Most cluster machines are running FreeBSD `13-STABLE` or `14-CURRENT` as of 2022-09-30.
+Only a handful of machines are still on FreeBSD `12-STABLE`.
+
+We are looking for an additional full mirror site (five servers) in Europe.
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for our needs.
+Offers of link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[additional single-server mirrors] are always welcome too, especially in Europe.
diff --git a/website/content/en/status/report-2022-07-2022-09/core.adoc b/website/content/en/status/report-2022-07-2022-09/core.adoc
new file mode 100644
index 0000000000..d09d031861
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/core.adoc
@@ -0,0 +1,37 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== Completed Items
+
+===== New Core Team Secretary
+
+All members of the Core Team express publicly their gratitude to Muhammad Moinur Rahman (bofh) for serving as the Core Team Secretary for the past two years.
+
+The Core Team approved Sergio Carlavilla (carlavilla) as the new Core Team secretary.
+
+===== Procedure to handle GDPR deletion request
+
+The Core Team has reviewed the procedure to handle GDPR deletions requests with help from Foundation lawysers.
+The document is currently being written and will be published after completion.
+
+===== New Privacy Policy
+
+The Core Team is working closely with the FreeBSD Foundation to update the Privacy Policy to properly align with current laws and practices found on similar websites such as ours.
+
+===== Bruce Evans memorial plaque
+
+The Core Team unanimously votes to allow the memorial plaque for Bruce Evans mentioning him as co-founder of FreeBSD.
+
+===== EuroBSDCon core team office hour
+
+On Friday, September 16, the new Core Team presented at link:https://wiki.freebsd.org/DevSummit/202209[EuroBSDcon 2022 Developer Summit].
+The Core Team introduced themselves and talked a bit about their plans for this term.
+There were discussions, Q & A, and suggestions from the attendees about the details.
+
+==== Commit bits
+
+Core approved reactivating the source commit bit for Konrad Witaszczyk (def@).
+Right now Konrad is working at Cambridge University, where he is responsible for developing CheriBSD.
diff --git a/website/content/en/status/report-2022-07-2022-09/doceng.adoc b/website/content/en/status/report-2022-07-2022-09/doceng.adoc
new file mode 100644
index 0000000000..25b1437bc6
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/doceng.adoc
@@ -0,0 +1,110 @@
+////
+Quarter:	3rd quarter of 2022
+Prepared by:	fernape
+Reviewed by:	gjb, dbaio
+Last edit:	$Date: 2022-09-24 14:24:33 +0200 (Sat, 24 Sep 2022) $
+Version:	$Id: doceng-2022-3rd-quarter-status-report.adoc 272 2022-09-24 12:24:33Z dbaio $
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During the last quarter:
+
+* 0mp@ stepped down as Doceng's Secretary, fernape@ joined as the new Secretary.
+  Doceng would like to thank 0mp@ for his service.
+
+* eadler@'s doc bit was taken in for safekeeping per his request.
+
+* A git commit message template was added for the doc repository.
+
+Items pending and in the discussion:
+
+* Remove outdated translations from the Website and Documentation portal.
+
+==== FreeBSD's Documentation Project Primer
+
+The FDP was link:https://cgit.freebsd.org/doc/commit/?id=311e6e3d5e7476cda9107107d779a145241f11fa[expanded with information on trademark handling].
+
+==== Porter's Handbook:
+
+* The documentation on link:https://cgit.freebsd.org/doc/commit/?id=08dd1185b44003d698b267851f704820c9d492c6[porting Haskell programs was updated].
+
+* The link:https://reviews.freebsd.org/D36369[move of WWW from pkg-descr to Makefile was documented].
+
+* link:https://cgit.freebsd.org/doc/commit/?id=78deabd3b1b2aabe9960c24d0c7e8df3fb57e607[Qt 6-related documentation has been added] following the import of the library in the ports framework.
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance]
+
+===== Q3 2022 Status
+
+* 12 languages
+* 148 registered users
+
+ - Gasol Wu joined the Chinese translation team.
+ - Alvaro Felipe Calle joined the Spanish translation team.
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 8%)
+* Chinese (Traditional) (zh-tw)	(progress: 4%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 4%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 3%)
+* Portuguese (pt-br)		(progress: 16%)
+* Spanish (es)			(progress: 15%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone who contributed, translating or reviewing documents.
+
+Please, promote this effort in your local user group, we always need more volunteers.
+
+==== FreeBSD Manual Pages Portal
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+The Manual Pages Portal has been redesigned to use man:mandoc[1] for rendering.
+A link:https://www.carlavilla.es/[portal preview] is available.
+Feedback has been collected and addressed where possible.
+There are some remaining non-blocking issues.
+Doceng@ would like to move forward with the migration to this new portal.
+
+Thanks to all of those who reviewed it and provided feedback.
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Complete_)
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Not started_)
diff --git a/website/content/en/status/report-2022-07-2022-09/ena.adoc b/website/content/en/status/report-2022-07-2022-09/ena.adoc
new file mode 100644
index 0000000000..e2c01fffd6
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/ena.adoc
@@ -0,0 +1,22 @@
+=== ENA FreeBSD Driver Update
+
+Links: +
+link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst]
+
+Contact: Michal Krawczyk <mk@semihalf.com> +
+Contact: David Arinzon <darinzon@amazon.com> +
+Contact: Marcin Wojtas <mw@FreeBSD.org>
+
+ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS).
+The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used.
+
+Completed since the last update:
+
+* Upstream of the ENA driver v2.6.0 and v2.6.1, included:
+** Fix for the performance degradation after reset issue on 6-gen instances,
+** Fix of the false netmap assertions with KASSERT enabled,
+** Code cleanup and style fixes,
+** Logging improvements,
+** Fix to the retrieval of the ENI metrics.
+
+Sponsor: Amazon.com Inc
diff --git a/website/content/en/status/report-2022-07-2022-09/firecracker.adoc b/website/content/en/status/report-2022-07-2022-09/firecracker.adoc
new file mode 100644
index 0000000000..797b9f1e0f
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/firecracker.adoc
@@ -0,0 +1,29 @@
+=== FreeBSD/Firecracker
+
+Links: +
+link:https://firecracker-microvm.github.io/[Firecracker VM]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+Firecracker is an open source "microVM" developed by Amazon Web Services; it
+is designed for the needs of "serverless" compute environments and has a
+particular focus on security and minimalism.
+
+Starting in June 2022, Colin Percival has been working to port FreeBSD to run
+in the Firecracker environment, with significant assistance from other FreeBSD
+developers.  As of this quarterly report, a set of patches are pending review
+which collectively add the needed support to make FreeBSD functional in a
+patched version of Firecracker.
+
+In Q4 Colin intends to finish committing the relevant patches to FreeBSD,
+release a kernel and disk image so other FreeBSD users can experiment with
+Firecracker, and update and merge Firecracker patches which add PVH boot
+support (used by FreeBSD).
+
+This work has already produced "spinoff" benefits in revealing ways to speed
+up the FreeBSD boot process; due to its low overhead and minimal environment,
+Firecracker is an excellent context to work on this.
+
+This work is supported by Colin's FreeBSD/EC2 Patreon.
+
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2022-07-2022-09/freebsd-foundation.adoc b/website/content/en/status/report-2022-07-2022-09/freebsd-foundation.adoc
new file mode 100644
index 0000000000..1d5bcaa638
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/freebsd-foundation.adoc
@@ -0,0 +1,201 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] +
+link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] +
+link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] +
+link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] +
+link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
+supporting and promoting the FreeBSD Project and community worldwide.  Donations
+from individuals and corporations are used to fund and manage software
+development projects, conferences, and developer summits.  We also provide
+travel grants to FreeBSD contributors, purchase and support hardware to improve
+and maintain FreeBSD infrastructure, and provide resources to improve security,
+quality assurance, and release engineering efforts.  We publish marketing
+material to promote, educate, and advocate for the FreeBSD Project, facilitate
+collaboration between commercial vendors and FreeBSD developers, and finally,
+represent the FreeBSD Project in executing contracts, license agreements, and
+other legal arrangements that require a recognized legal entity.
+
+==== Fundraising Efforts
+
+First, I’d like to send a big thank you to everyone who gave a financial
+contribution to our efforts.  We are 100% funded by your donations, so every
+contribution helps us continue to support FreeBSD in many ways, including some
+of the work funded and published in this status report.
+
+We support FreeBSD in five main areas. Software development is the largest area
+we fund through staff developers and contractors who implement new features,
+support tier 1 platforms, review patches, and fix issues.  You can read about
+some of the work we did under OS Improvements in this report.  FreeBSD Advocacy
+is another area that we support to spread the word about FreeBSD at conferences,
+in presentations online and in-person, and through tutorials and how-to guides.
+We purchase and support hardware for the FreeBSD infrastructure that supports
+the work going on in the Project.  Virtual and in-person events are organized by
+the Foundation to help connect and engage community members to share their
+knowledge and collaborate on projects.  Finally, we provide legal support to the
+Project when needed and protect the FreeBSD trademarks.
+
+Our goal this year is to raise at a minimum $1,400,000 towards a spending budget
+of around $2,000,000.  As we enter the last quarter of 2022, our donation total
+sits at $167,348, so we still need your help.  If you haven't made a donation
+this year, please consider making one at https://freebsdfoundation.org/donate/.
+We also have a Partnership Program for larger commercial donors.  You can find
+out more at
+https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/
+
+==== OS Improvements
+
+During the third quarter of 2022, 300 src, 36 ports, and 13 doc tree commits
+were made that identified The FreeBSD Foundation as a sponsor.  Some of that
+work has dedicated report entries.
+
+* FreeBSD as a Tier I cloud-init Platform
+* Intel wireless towards 11ac
+* LLDB multiprocess debugging support
+* OpenStack on FreeBSD
+* Snapshots on Filesystems Using Journaled Soft Updates
+
+The other sponsored work is challenging to concisely summarize.  It varies from
+complex new features to various bug fixes spanning the src tree.  Here is a
+small sample to give a flavor of last quarter's work.
+
+- 240afd8 makefs: Add ZFS support
+
+  This allows one to take a staged directory tree and create a file consisting
+  of a ZFS pool with one or more datasets that contain the contents of the
+  directory tree.  This is useful for creating virtual machine images without
+  using the kernel to create a pool; "zpool create" requires root privileges and
+  currently is not permitted in jails.  makefs -t zfs also provides reproducible
+  images by using a fixed seed for pseudo-random number generation, used for
+  generating GUIDs and hash salts.  makefs -t zfs requires relatively little by
+  way of machine resources.
+
+-  36f1526 Add experimental 16k page support on arm64
+
+   Add initial 16k page support on arm64. It is considered experimental, with no
+   guarantee of compatibility with userspace or kernel modules built with the
+   current 4k page size. Testing has shown good results in kernel workloads that
+   allocate and free large amounts of memory as only a quarter of the number of
+   calls into the VM subsystem are needed in the best case.
+
+- 1424f65 vm_pager: Remove the default pager
+
+  It's unused now.  Keep the OBJ_DEFAULT identifier, but make it an alias of
+  OBJT_SWAP for the benefit of out-of-tree code.
+
+- a889a65 eventtimer: Fix several races in the timer reload code
+
+  In handleevents(), lock the timer state before fetching the time for the next
+  event.  A concurrent callout_cc_add() call might be changing the next event
+  time, and the race can cause handleevents() to program an out-of-date time,
+  causing the callout to run later (by an unbounded period, up to the idle
+  hardclock period of 1s) than requested.
+
+===== Bhyve Issue Support
+
+The Foundation contracted John Baldwin to dedicate time to Bhyve as issues
+arise, especially security issues.  Here is a summary of his 2022q3 work on that
+contract.
+
+- bb31aee bhyve virtio-scsi: Avoid out of bounds accesses to guest requests.
+- 62806a7 bhyve virtio-scsi: Tidy warning and debug prints.
+- 7afe342 bhyve e1000: Sanitize transmit ring indices.
+- c94f30e bhyve: Validate host PAs used to map passthrough BARs.
+- 16bedf5 pci: Add helper routines to iterate over a device's BARs.
+- baf753c bhyve: Support other schemes for naming pass-through devices.
+- fa46f37 bhyve e1000: Skip packets with a small header.
+- e7439f6 bhyve xhci: Cache the value of MaxPStreams when initializing an endpoint.
+
+===== RISC-V Improvements
+
+At the end of the quarter, the Foundation contracted Mitchell Horne to add and
+improve support for RISC-V hardware.  Mitchell will also perform general
+maintenance such as fixing bugs, handling reports, providing review for new code
+changes, and improving source code legibility and documentation.
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve
+continuous integration, automated testing, and overall quality assurance efforts
+for the FreeBSD project.  You can read about CI activities this quarter in a
+dedicated entry.
+
+==== FreeBSD Advocacy and Education
+
+Much of our effort is dedicated to Project advocacy.  This may involve
+highlighting interesting FreeBSD work, producing literature and video tutorials,
+attending events, or giving presentations.  The goal of the literature we
+produce is to teach people FreeBSD basics and help make their path to adoption
+or contribution easier.  Other than attending and presenting at events, we
+encourage and help community members run their own FreeBSD events, give
+presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the
+globe.  These events can be BSD-related, open source, or technology events
+geared towards underrepresented groups.  We support the FreeBSD-focused events
+to help provide a venue for sharing knowledge, working together on projects, and
+facilitating collaboration between developers and commercial users.  This all
+helps provide a healthy ecosystem.  We support the non-FreeBSD events to promote
+and raise awareness of FreeBSD, to increase the use of FreeBSD in different
+applications, and to recruit more contributors to the Project. We are continuing
+to attend events both in person and virtual as well as planning the November
+Vendor Summit. In addition to attending and planning virtual events, we are
+continually working on new training initiatives and updating our selection of
+link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to
+facilitate getting more folks to try out FreeBSD.
+
+Check out some of the advocacy and education work we did last quarter:
+
+* Held a FreeBSD Workshop and Staffed a booth at Scale 19x in Los Angeles, CA on
+  July 28-30. You can read more about our participation in the
+  link:https://freebsdfoundation.org/blog/scale19x-conference-report/[SCALE19X
+  Conference Report]
+* Sponsored and attended link:https://coscup.org/2022/en/[COSCUP], July 30-31, Taiwan
+* Attended the EuroBSDCon Developer Summit and sponsored and attended
+  link:https://2022.eurobsdcon.org/[EuroBSDcon 2022], September 15-18, Vienna,
+  Austria
+* link:http://toilers.mines.edu/RMCWiC/2022/home.html[Sponsored and Presented at the Rocky Mountain Celebration of Women in
+  Computing], September 29-30, 2022. Slides from Deb’s presentation can be found
+  link:http://toilers.mines.edu/RMCWiC/2022/program.html[here].
+* Published the
+  link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-summer-2022-update/[FreeBSD
+  Foundation Summer 2022 Update]
+* Continued our participation in Google Summer of Code as both an admin and
+  mentors. Interviews with some of the Google Summer of Code Students can be
+  found link:https://freebsdfoundation.org/our-work/latest-updates/[here].
+* Introduced a new
+  link:https://freebsdfoundation.org/freebsd-project/resources/[FreeBSD
+  Resources] page that allows for search by type of subject, type of content and
+  difficulty level.
+* New Blog Posts:
+
+** Guest Post: link:https://freebsdfoundation.org/blog/guest-post-freebsd-in-science/[FreeBSD in Science]
+** link:https://freebsdfoundation.org/blog/advocating-for-freebsd-in-2022-and-beyond/[Advocating for FreeBSD in 2022 and Beyond]
+** link:https://freebsdfoundation.org/blog/august-foundation-fundraising-update/[August Foundation Fundraising Update]
+** link:https://freebsdfoundation.org/blog/sharing-dual-licensed-drivers-between-linux-and-freebsd/[Sharing Dual-Licensed Drivers between Linux and FreeBSD]
+* New and Updated How-To and Quick Guides:
+** link:https://freebsdfoundation.org/blog/new-freebsd-quick-guide-video-playback-on-freebsd-quick-guide/[FreeBSD Quick Guide: Video Playback on FreeBSD]
+** link:https://freebsdfoundation.org/resource/binary-package-management-on-freebsd/[Binary Package Management on FreeBSD]
+
+We help educate the world about FreeBSD by publishing the professionally
+produced FreeBSD Journal.  As we mentioned previously, the FreeBSD Journal is
+now a free publication.  Find out more and access the latest issues at
+link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDfoundation.org/journal/].
+
+You can find out more about events we attended and upcoming events at
+link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDfoundation.org/news-and-events/].
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to
+protect them.  We also provide legal support for the core team to investigate
+questions that arise.
+
+Go to link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org]
+to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2022-07-2022-09/gcc.adoc b/website/content/en/status/report-2022-07-2022-09/gcc.adoc
new file mode 100644
index 0000000000..3d42964623
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/gcc.adoc
@@ -0,0 +1,36 @@
+=== GCC: New maintainer, GCC 12.2 and more
+
+Links: +
+link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[https://gcc.gnu.org/gcc-12/]
+
+Contact: <toolchain@FreeBSD.org> +
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> +
+
+ * salvadore@ adopted all existing ports corresponding to supported versions of gcc, namely: lang/gcc10, lang/gcc11, lang/gcc11-devel, lang/gcc12, lang/gcc12-devel and lang/gcc13-devel.
+   At the moment -devel ports are updated weekly, unless a build failure makes it impossible.
+   Of course, in the latter case, the build failure is fixed and/or reported upstream as soon as possible.
+
+ * link:https://gcc.gnu.org/gcc-12/changes.html[GCC 12.2 has been released].
+   Traditionally, FreeBSD waits for the release of the second minor version of GCC to use it as default GCC version, so that most of the software needing to be compiled with GCC has already been ported to the latest major version.
+   Thus, work has started to update the default GCC version to version 12.
+   Thank you very much to antoine@ who has already run the first exp-run and to all the contributors, maintainers and committers involved in the process.
+   link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265948[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2659548]
+
+ * Discussion about LTO keeps going with many different points of view.
+   If interested, you can read the latest contributions to the topic: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264949[lang/gcc11: Needs build time warning for /tmp consumption] and link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254[lang/gcc11: build gets stuck].
+   Reminder: LTO_BOOTSTRAP is an option enabled by default.
+   If you build the port on your machine and its resources consumption is not acceptable, disabling this option will get you a lighter compilation.
+
+ * jbeich@ submitted a patch to expose non-default -stdlib=libc++ support, which has been successfully committed to all relevant ports (gcc >= 11).
+   link: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265962[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265962]
+
+ * diizzy@ refreshed the mirrors list in the MASTER_SITE_GCC variables, also removing ftp mirrors. The main GCC site is used as fallback.
+   link: https://reviews.freebsd.org/D36372[https://reviews.freebsd.org/D36372]
+
+ * Help is still needed with these three changes to work through with upstream GCC (requires expertise with the GCC sources and upstream, not with the ports framework):
+
+     ** upstreaming lang/gcc11/patch-gets-no-more
+     ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support
+     ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874]
diff --git a/website/content/en/status/report-2022-07-2022-09/intro.adoc b/website/content/en/status/report-2022-07-2022-09/intro.adoc
new file mode 100644
index 0000000000..f8a991319d
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/intro.adoc
@@ -0,0 +1,11 @@
+Here is the third quarterly report for year 2022, with 24 reports included, which is slightly fewer than last quarter.
+
+I notice that in the past we had quarters with many more reports: often more than 30, sometimes even more than 40.
+Thus I would like to encourage all of you to submit reports: reports are useful to share your work, to find help, to have more eyes reviewing your changes, to have more people testing your software, to reach a wider audience whenever you need to tell something to all of the FreeBSD community and in many other cases.
+Please do not be shy and do not worry if you are not a native English speaker or if you are not proficient in AsciiDoc syntax: the quarterly team will be glad to help you in whatever you need.
+
+On the other hand, if you really do not have anything to report, then maybe you might like to join one of the interesting projects described below, or you might be inspired from one of them to do something new, thus having something to report in the future.
+
+We wish you all a pleasant read.
+
+Lorenzo Salvadore, on behalf of the status report team.
diff --git a/website/content/en/status/report-2022-07-2022-09/iwlwifi.adoc b/website/content/en/status/report-2022-07-2022-09/iwlwifi.adoc
new file mode 100644
index 0000000000..d608e7427b
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/iwlwifi.adoc
@@ -0,0 +1,25 @@
+=== Intel wireless towards 11ac
+
+Links: +
+link:https://wiki.freebsd.org/WiFi/Iwlwifi[Intel iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+The ongoing project aims to support the latest Intel wireless chipsets on FreeBSD using LinuxKPI compat code backed by native net80211 and kernel code.
+In addition work is on the way to support 11n and 11ac standards in the LinuxKPI 802.11 compat code and fill gaps for mostly 11ac in the native net80211 wireless stack.
+
+For the Intel iwlwifi wireless driver there were no major updates in the last months.
+We updated the firmware to the latest publicly available version and fixed some of the most visible bugs.
+Work is also on the way to support the D3 power saving code.
+
+LinuxKPI compat code also got some improvements and fixes which at times were only observable on certain generations of iwlwifi chipsets.
+
+Changes in net80211 and LinuxKPI compat code for 11n and 11ac have little public visibility so far in order to not break basic support.
+Updates to constants based on newer 802.11 standards and other changes without user-visible effect were merged, and
+functional changes will follow in the coming months, initially hidden behind compile-time or runtime options.
+
+Improvements and updates were largely merged back to stable/13 for the benefit of the users tracking this branch and to help with more testing.
+
+For the latest state of the development, please follow the freebsd-wireless mailing list and check the wiki pages.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-07-2022-09/kde.adoc b/website/content/en/status/report-2022-07-2022-09/kde.adoc
new file mode 100644
index 0000000000..91a6500c7e
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/kde.adoc
@@ -0,0 +1,43 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] +
+link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine.
+The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack.
+
+==== Qt6 Landed
+
+The big news in the KDE ports is not directly KDE-related.
+Qt6 has landed, which prepares us for the next generation of Qt-based applications.
+
+It is now possible to have `USES=qt:6` to select the new Qt version.
+Some ports have been flavorized to make use of the new version.
+
+KDE itself is not affected: the upstream work on KDE Frameworks for Qt6 is not yet completed.
+Most of the KDE Frameworks will compile with Qt6, but that is not important for FreeBSD ports yet.
+With package:devel/qt6[] you get Qt 6.4.0, released at the end of the quarter.
+
+==== KDE Stack
+
+KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well.
+These (large) updates land shortly after their upstream release and are not listed separately.
+
+* KDE Frameworks 5 is now at version 5.98 (latest monthly release from September 2022).
+* KDE Gear is now version 22.08.1 (update for September 2022).
+* KDE Plasma is now version 5.24.6 (update for July 2022).
+
+Note that KDE Plasma 5.25 has been released upstream, but is waiting on fixes before it can land in the ports tree (for example, link:https://bugs.kde.org/show_bug.cgi?id=458356[this KActivityManager bug] in KDE's bug-tracker).
+
+==== Related Ports
+
+* package:accessibility/qt5-speech[] now supports multiple backends, as well as no-backends, for speech synthesis.
+* package:devel/cmake[] was reorganized, so that package:devel/cmake[] is now a metaport that installs package:devel/cmake-core[] and the rest of the CMake suite. (Thanks to diizzy@) The CMake ports were also updated to version 3.24, with attendant changes in ports all over the tree.
+* package:net/qt5-network[] has improved compatibility with libressl.
+* package:x11/plasma-wayland-protocols[] was updated in advance of KDE Plasma Desktop updates in the next quarter.
diff --git a/website/content/en/status/report-2022-07-2022-09/kinst.adoc b/website/content/en/status/report-2022-07-2022-09/kinst.adoc
new file mode 100644
index 0000000000..5a8834bd92
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/kinst.adoc
@@ -0,0 +1,48 @@
+=== DTrace: Instruction-level dynamic tracing
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2022Projects/InstructionLevelDynamicTracing[Wiki article] URL: link:https://wiki.freebsd.org/SummerOfCode2022Projects/InstructionLevelDynamicTracing[https://wiki.freebsd.org/SummerOfCode2022Projects/InstructionLevelDynamicTracing] +
+link:https://reviews.freebsd.org/D36851[Final code review] URL: link:https://reviews.freebsd.org/D36851[https://reviews.freebsd.org/D36851] +
+
+Contact: Christos Margiolis <christos@FreeBSD.org> +
+Contact: Mark Johnston <markj@FreeBSD.org>
+
+kinst is a new DTrace provider that allows for arbitrary kernel instruction tracing.
+
+The provider is currently implemented only for amd64, but we plan to port it to other architectures in the future as well.
+
+kinst probes are created on demand by libdtrace, and a probe can be created for nearly every instruction in the kernel.
+Probes take the form of:
+
+	kinst:<module>:<function>:<offset>
+
+where "module" is the kernel module containing the named function, "function" is the kernel function to be traced, and "offset" is the offset to a specific instruction.
+Omitting "offset" causes all instructions in the function to be traced.
+Omitting "module" causes DTrace to search all kernel modules for the function.
+
+For example, to trace the second instruction in amd64_syscall(), first determine the offset of the second instruction:
+
+	# kgdb
+	(kgdb) disas /r amd64_syscall
+	Dump of assembler code for function amd64_syscall:
+	   0xffffffff809256c0 <+0>:     55      push   %rbp
+	   0xffffffff809256c1 <+1>:     48 89 e5        mov    %rsp,%rbp
+	   0xffffffff809256c4 <+4>:     41 57   push   %r15
+
+The offset is 1.
+Then, to trace it:
+
+	# dtrace -n 'kinst::amd64_syscall:1'
+
+A new "regs" keyword was also added to the D language, providing read-only access to CPU registers at the point where the probe fired.
+For example, to trace the contents of the frame pointer (register %rbp on amd64) when the kinst::amd64_syscall:1 probe fires:
+
+	# dtrace -n 'kinst::amd64_syscall:1 {printf("0x%x", regs[R_RBP]);}'
+
+kinst works similarly to the FBT (function boundary tracing) provider in that it places a breakpoint on the target instruction and hooks into the kernel's breakpoint handler.
+It is more powerful than FBT since it can be used to create probes at arbitrary points within a function, rather than at function boundaries.
+Because kinst has to be able to trace arbitrary instructions, it does not emulate most of them in software but rather causes the traced thread to execute a copy of the instruction before returning to the original code.
+
+Planned future work includes porting kinst to additional platforms, especially arm64 and riscv, and developing tooling that can use kinst to trace calls to inline functions using the kernel's debugging symbols.
+
+Sponsor: Google, Inc. (GSOC 2022)
diff --git a/website/content/en/status/report-2022-07-2022-09/lldb.adoc b/website/content/en/status/report-2022-07-2022-09/lldb.adoc
new file mode 100644
index 0000000000..04c7a1b761
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/lldb.adoc
@@ -0,0 +1,24 @@
+=== Ongoing work on LLDB multiprocess debugging support
+
+Links: +
+link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[Moritz Systems Project Description] URL: link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[https://www.moritz.systems/blog/multiprocess-support-for-lldb/] +
+link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[Progress Report 1] URL: link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/] +
+link:https://www.moritz.systems/blog/full-multiprocess-support-in-lldb-server/[Progress Report 2] URL: link:https://www.moritz.systems/blog/full-multiprocess-support-in-lldb-server/[https://www.moritz.systems/blog/full-multiprocess-support-in-lldb-server/]
+
+Contact: Kamil Rytarowski <kamil@moritz.systems> +
+Contact: Michał Górny <mgorny@moritz.systems>
+
+According to the upstream description, "LLDB is a next generation, high-performance debugger. It is built as a set of reusable components which highly leverage existing libraries in the larger LLVM Project, such as the Clang expression parser and LLVM disassembler."
+
+FreeBSD includes LLDB in the base system.
+The previous sponsored projects improved LLDB, to make it a credible debugger for the base system, although it still has a few limitations compared to the contemporary versions of GNU GDB.
+This project started in April 2022.
+It aims to implement full support for debugging multiple processes simultaneously.
+
+At the start of the project, LLDB featured very limited support for multiprocess debugging.
+Currently, the server is already able to monitor multiple processes using the multiprocess extension to the GDB Remote Serial Protocol.
+The work on implementing the client-side counterpart for this protocol is ongoing.
+
+Once the project is finished, LLDB will be able to trace an arbitrary number of forked processes simultaneously (equivalent to GDB's `detach-on-fork off`).
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-07-2022-09/lsof.adoc b/website/content/en/status/report-2022-07-2022-09/lsof.adoc
new file mode 100644
index 0000000000..136f204feb
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/lsof.adoc
@@ -0,0 +1,19 @@
+=== sysutils/lsof major upgrade
+
+Link: +
+link:https://github.com/lsof-org/lsof[lsof project repo] URL: link:https://github.com/lsof-org/lsof[https://github.com/lsof-org/lsof]
+
+Contact: +
+Larry Rosenman <ler@FreeBSD.org>
+
+package:sysutils/lsof[] had a major upgrade to no longer look in `/dev/kmem` for data, and to use the userland API.
+This took a long time to hit the tree, but is finally done.
+It fixes man:lsof[8] to work with ZFS again for the first time since 13.0-RELEASE.
+
+This will make maintenance much easier going forward.
+
+To the kernel folks: if you make changes that break lsof, please submit a GitHub pull request to https://github.com/lsof-org/lsof.
+Please test any changes to the interfaces that lsof uses and make sure they still work.
+These all should be userland interfaces now, but please test.
+
+My thanks to Warner Losh <imp@FreeBSD.org>, Mateusz Guzik <mjg@FreeBSD.org>, and Ed Maste <emaste@FreeBSD.org> for help getting this major change landed.
diff --git a/website/content/en/status/report-2022-07-2022-09/openstack-on-freebsd.adoc b/website/content/en/status/report-2022-07-2022-09/openstack-on-freebsd.adoc
new file mode 100644
index 0000000000..6624da25e4
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/openstack-on-freebsd.adoc
@@ -0,0 +1,42 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] +
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+OpenStack is an open-source cloud operating system for different types of resources like virtual and bare-metal machines.
+Users can spawn FreeBSD instances on the open cloud platform, but it is not currently possible to run OpenStack control plane on FreeBSD hosts.
+The goal of this project is to port key OpenStack components so that FreeBSD can function as an OpenStack host.
+
+Academic and industrial research groups have been evaluating CHERI-enabled Morello boards since mid-2022.
+A resource orchestration platform like OpenStack can improve the speed and cost of provisioning, managing, and recycling those boards.
+
+Starting in January 2022, Chih-Hsin Chang has been working to port several OpenStack components to run on FreeBSD, including:
+
+* Keystone (identity service)
+* Glance (image service)
+* Placement (resource tracking and inventory service)
+* Neutron (networking service)
+* Nova (compute service)
+
+Some of the items are still under heavy development.
+For instance, due to the design of Neutron, the DHCP servers are placed inside Linux network namespaces.
+It is necessary to find an alternative, e.g. `vnet`, on FreeBSD and adapt it.
+Most of the time the porting strategy is to make as small of an impact as possible by working around obstacles.
+But something like `oslo.privsep` deserves a true porting.
+`oslo.privsep` is rooted in Linux capabilities to do the privilege separation work.
+Right now we just bypassed any Linux capabilities-related operation inside `oslo.privsep`.
+So there is plenty of hackish spots in the source code and configurations currently.
+All of these along with the building and installation steps will be collected in the https://github.com/openstack-on-freebsd[project repositories].
+
+In Q4 Chih-Hsin plans to focus on porting Neutron and Nova in order to complete the VM lifecycle operations.
+The highlights include:
+
+* DHCP integration
+* FreeBSD bridge driver/agent
+* Bhyve + Libvirt integration
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc b/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc
new file mode 100644
index 0000000000..84b680b904
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc
@@ -0,0 +1,24 @@
+=== Rewrite of pjdfstest
+
+Links: +
+link:https://github.com/musikid/pjdfstest[Github] URL: link:https://github.com/musikid/pjdfstest[https://github.com/musikid/pjdfstest] +
+link:https://musikid.github.io/blog/rewrite-pjdfstest/[Blog] URL: https://musikid.github.io/blog/rewrite-pjdfstest/[https://musikid.github.io/blog/rewrite-pjdfstest/] +
+Contact: Alan Somers <asomers@FreeBSD.org>
+
+Back in 2007, Pawel Jakub Dawidek <pjd@FreeBSD.org> wrote pjdfstest, a POSIX file system conformance test tool.
+He originally wrote it to validate the port of ZFS to FreeBSD, but it has subsequently been used for other file systems and other operating systems.
+
+This year, Sayafdine Said <musikid@outlook.com> rewrote it under Google's sponsorship.
+The new version has several improvements:
+
+* More configurable, for better use with other file systems.
+* Much faster, largely thanks to said configurability.
+* Better test case isolation, making failure easy to debug.
+* No longer requires root privileges for all test cases.
+* Test cases can be run in a debugger.
+* More maintainable, less duplication.
+
+There are still a couple of lingering PRs to complete, but we expect to wrap those up and add pjdfstest to the ports collection soon.
+From there, it will be used both by `/usr/tests` for ZFS and UFS, and by external developers for other file systems.
+
+Sponsor: Google Summer of Code
diff --git a/website/content/en/status/report-2022-07-2022-09/portmgr.adoc b/website/content/en/status/report-2022-07-2022-09/portmgr.adoc
new file mode 100644
index 0000000000..62655e0d66
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/portmgr.adoc
@@ -0,0 +1,56 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[https://www.FreeBSD.org/ports/] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[https://www.freebsd.org/portmgr/] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+Currently there are just over 30,500 ports in the Ports Tree.
+There are currently just under 2,800 open ports PRs of which 750 are unassigned.
+The last quarter saw 9,137 commits by 151 committers on the main branch and 589 commits by 61 committers on the 2022Q3 branch.
+Compared to two quarters ago, this means a slight increase in the number of ports, but also a slight increase in the number of (unassigned) ports PRs and a slight decrease in the number of commits made.
+
+In the last quarter, we welcomed Felix Palmen (zirias@) as a new ports committer, welcomed back Akinori MUSHA (knu@), and said goodbye to Olli Hauer (ohauer@).
+We also welcomed Luca Pizzamiglio (pizzamig@) as an official member of portmgr.
+
+Some large changes in the Ports Tree were made during the last quarter:
+
+* "Created by" lines have been removed from the top of each Makefile, as a lot of those were outdated.
+* WWW: has been moved from each pkg-descr into each Makefile as a variable; the below write-up is from Stefan Eßer (se@) who did the work:
+
+The description of a port's functionality should end with the URL of a web page that provides further information, such as best practices for usage or configuration.
+This information can be displayed with `pkg query -e` for installed packages or `pkg rquery -e` for available packages.
+The URL used to be appended to the end of the ports' pkg-descr files, with the prefix "WWW: ", so that tools could extract the URL from the description.
+Over time, many of these URLs have become stale, since port updates generally change only the Makefile, not the pkg-descr file.
+By moving the definition of these URLs into the Makefiles, maintainers are more likely to update the URL along with other port changes, and tools have easier access to them.
+The URLs are now assigned to the WWW macro in the Makefile and can be queried with `make -V WWW` in the port directory.
+Tools that process the description contained in the package files still work because the "WWW: " lines at the end are generated from the WWW values in the Makefiles.
+
+During EuroBSDCon, portmgr@ had a discussion about improving the situation for kernel module packages.
+Various possibilities have been discussed.
+
+The following happened under the hood:
+
+* one new USES, "vala", was added.
+* The default version of Go got bumped to 1.19
+* CMake is now a meta-port
+* Initial support for Qt 6 was added, at version 6.3.2
+* Vim no longer installs a system-wide vimrc
+* A number of major ports got updated:
+** pkg 1.18.4
+** Chromium 106.0.5249.91
+** Firefox 105.0.1
+*** Firefox ESR 102.3.0
+** KDE Applications 22.8.1
+** KDE Frameworks 5.98
+** Rust 1.63.0
+** SDL 2.24.0
+** Xorg server 21.1.4 (overhaul)
diff --git a/website/content/en/status/report-2022-07-2022-09/pot.adoc b/website/content/en/status/report-2022-07-2022-09/pot.adoc
new file mode 100644
index 0000000000..8d80107ccd
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/pot.adoc
@@ -0,0 +1,24 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on github] URL: link:https://github.com/bsdpot[https://github.com/bsdpot]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> +
+Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@freebsd.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+During the last quarter, link:https://github.com/bsdpot/pot/releases/tag/0.15.3[pot 0.15.3] was released.
+It contains a number of improvements like mount-out to remove or unmount a previously mount-in folder or filesystem, signal and exec commands, better jail lifecycle handling, and many bug fixes.
+
+A new version of the Nomad driver, link:https://github.com/bsdpot/nomad-pot-driver/releases/tag/v0.9.0[nomad-pot-driver 0.9.0], was also released with signal and exec support and stability fixes.
+
+Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: a repository of pot flavours and complete container images for usage with pot and in many cases Nomad.
+
+Since the last status report, link:https://github.com/bsdpot/potluck/commits/master[many changes were committed], including many fixes and improvements to core images like link:https://github.com/bsdpot/potluck/tree/master/grafana[grafana], link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[postgresql-patroni] or link:https://github.com/bsdpot/potluck/tree/master/loki[loki].
+Additionally, all images have been rebuilt for FreeBSD 13.1 and 12.3 and to include the current quarterly versions of the packages being used.
+
+Last not least, Luca held the pot implementation and ecosystem talk link:https://2022.eurobsdcon.org/program/[How far a naive FreeBSD container implementation can go] at EuroBSDCon 2022.
+
+As always, feedback and patches are welcome.
diff --git a/website/content/en/status/report-2022-07-2022-09/releng.adoc b/website/content/en/status/report-2022-07-2022-09/releng.adoc
new file mode 100644
index 0000000000..e5589c2543
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/releng.adoc
@@ -0,0 +1,18 @@
+=== FreeBSD Release Engineering Team

+

+Links: +

+link:https://www.freebsd.org/releases/12.4R/schedule/[FreeBSD 12.4-RELEASE schedule] URL: link:https://www.freebsd.org/releases/12.4R/schedule/[https://www.freebsd.org/releases/12.4R/schedule/] +

+link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[https://www.freebsd.org/releases/13.2R/schedule/] +

+link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[https://www.freebsd.org/releases/14.0R/schedule/] +

+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[https://download.freebsd.org/snapshots/ISO-IMAGES/]

+

+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>

+

+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.

+

+During the third quarter of 2022, the Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/13*, and *stable/12* branches.

+

+Additionally, the schedules for the upcoming 12.4, 13.2, and 14.0 release cycles were published on the Project website.

+

+Sponsor: Rubicon Communications, LLC ("Netgate")

+Sponsor: The FreeBSD Foundation

diff --git a/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc b/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc
new file mode 100644
index 0000000000..97aa9e5d1f
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc
@@ -0,0 +1,30 @@
+=== Enabling Snapshots on Filesystems Using Journaled Soft Updates
+
+Links: +
+link:https://reviews.freebsd.org/D36491[Milestone 1 Core Changes] URL: link:https://reviews.freebsd.org/D36491[https://reviews.freebsd.org/D36491]
+
+Contact: Kirk McKusick <mckusick@FreeBSD.org>
+
+This project will make UFS/FFS filesystem snapshots available when running with journaled soft updates.
+
+The UFS/FFS filesystem has the ability to take snapshots.
+Because the taking of snapshots was added after soft updates were written they were fully integrated with soft updates.
+When journaled soft updates were added in 2010, they were never integrated with snapshots.
+So snapshots cannot be used on filesystems running with journaled soft updates.
+
+Snapshots became less important with the support for ZFS on FreeBSD since ZFS can take snapshots quickly and easily.
+However there remain two instances where UFS snapshots are still important.
+The first is that they allow reliable dumps of live filesystems which avoids possibly hours of down time.
+The second is that they allow the running of background fsck.
+Similar to the need for scrub in ZFS, fsck needs to be run periodically to find undetected disk failures.
+Snapshots allow fsck to be run on live filesystems rather than needing to schedule down time to run it.
+
+This project has two milestones:
+
+1. enable snapshots when running with journaled soft updates and ensure that they can be used for doing background dumps on a live filesystem.
+This milestone should be completed by the end of 2022.
+
+2. extend fsck_ffs to be able to do a background check using a snapshot on a filesystem running with journaled soft updates.
+This milestone is expected by Q3 of 2023.
+
+Sponsored by: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-07-2022-09/wifi.adoc b/website/content/en/status/report-2022-07-2022-09/wifi.adoc
new file mode 100644
index 0000000000..5b7a5dd00a
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/wifi.adoc
@@ -0,0 +1,31 @@
+=== More wireless updates
+
+Links: +
+link:https://people.freebsd.org/~bz/wireless/[Bjoern's Wireless Work In Progress landing page] URL: link:https://people.freebsd.org/\~bz/wireless/[https://people.freebsd.org/~bz/wireless/] +
+link:https://wiki.freebsd.org/WiFi/Rtw88[Realtek rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88] +
+link:https://wiki.freebsd.org/WiFi/Rtw89[Realtek rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89] +
+link:https://wiki.freebsd.org/WiFi/Mt76[MediaTek mt76 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Mt76[https://wiki.freebsd.org/WiFi/Mt76] +
+link:https://wiki.freebsd.org/WiFi/Ath11k[QCA ath11k status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Ath11k[https://wiki.freebsd.org/WiFi/Ath11k]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+Currently development is mostly driven by Intel's iwlwifi driver again (see other report).
+As the saying goes ''each one helps the other'' so has work on Realtek's rtw89 driver helped find a bug in LinuxKPI bothering iwlwifi users.
+For this status report the topic is mostly more drivers, which do need more LinuxKPI support.
+
+Various work in progress:
+
+ * Realtek's rtw88 PCI is in-tree as-is and after a fruitful discussion with Hans Petter Selasky at EuroBSDCon work on LinuxKPI USB support for the rtw88 USB WiFi dongles will continue.
+
+ * Realtek's rtw89 driver was committed to main but is not connected to the build yet.  Scanning already works but packets are not yet passing. Having the driver in-tree already eased testing for users having that chipset in order to identify more unimplemented LinuxKPI bits (some of which will help the other drivers as well) and reduced work for me.
+
+ * The next drivers to probably hit the tree will be based on MediaTek's mt76 driver (for 7921 and 7915) which I have compiling and started testing.
+
+ * Based on requests I am also working on ath11k to support STA mode given some vendors seem to ship Laptops with those chips.
+
+While some of this clearly benefits from work sponsored by The FreeBSD Foundation for iwlwifi and newer standard support, a lot of this is just free-time work.
+If you are interested in any of these drivers I would greatly appreciate if some more hands would help with one or the other.
+This could be regularly testing updates to main, writing documentation and updating wiki pages, tracking PRs, trying out patches, helping with work on individual LinuxKPI bits with or without 802.11 work, or simply debugging problems with individual drivers and/or chipsets.
+If you are interested in helping with any one of the above, please drop me an email.
+
+For the latest state of the development, please follow the freebsd-wireless mailing list and check the wiki pages (as soon as they exist).
diff --git a/website/content/en/status/report-2022-07-2022-09/wtap.adoc b/website/content/en/status/report-2022-07-2022-09/wtap.adoc
new file mode 100644
index 0000000000..e963aac9f6
--- /dev/null
+++ b/website/content/en/status/report-2022-07-2022-09/wtap.adoc
@@ -0,0 +1,18 @@
+=== wtap(4) enhancement
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2022Projects/AddStaHostapAndAdhocModeToWtapWlanSimulator[Add sta, hostap and adhoc mode to wtap wlan simulator]
+
+Contact: En-Wei Wu <enweiwu@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+wtap(4) is a net80211(4) Wi-Fi simulator introduced by Monthadar Al Jaberi <monthadar@gmail.com> and Adrian Chadd <adrian@FreeBSD.org> in 2012.
+It originally supported 802.11s mesh mode and was used for verification.
+During the 2022 Google Summer of Code, En-Wei had been working on bringing sta, hostap, adhoc and monitor modes to it.
+The work also covers adding basic tests for net80211(4) with wtap(4), written in atf(7).
+
+For more details, please check the link:https://wiki.freebsd.org/SummerOfCode2022Projects/AddStaHostapAndAdhocModeToWtapWlanSimulator[project wiki page].
+
+Sponsor: Google Summer of Code
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/FreshPorts.adoc b/website/content/en/status/report-2022-10-2022-12/FreshPorts.adoc
new file mode 100644
index 0000000000..87cc9f7e2c
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/FreshPorts.adoc
@@ -0,0 +1,53 @@
+=== FreshPorts - help wanted
+
+Links: +
+link:https://freshports.org/[FreshPorts] URL: link:https://freshports.org/[https://freshports.org/] +
+link:https://news.freshports.org/[FreshPorts blog] URL: link:https://news.freshports.org/[https://news.freshports.org/]
+
+Contact: Dan Langille <dvl@FreeBSD.org>
+
+FreshPorts and FreshSource have reported upon FreeBSD commits for 20 years.
+They cover all commits, not just ports.
+
+FreshPorts tracks the commits and extracts data from the port Makefiles to create a database of information useful to both port maintainers and port users.
+
+For example, link:https://www.freshports.org/security/acme.sh/[https://www.freshports.org/security/acme.sh/] shows the history of the _acme.sh_ port, back to its creation in May 2017.
+
+==== Converting the backend repository
+
+This topic deals with the FreshPorts code repository.
+The front end (website) was converted from Subversion to Git several years ago.
+The back end, which processes FreeBSD commits and updates the database, is still on Subversion.
+I have wanted to convert these repositories to Git for some time.
+
+I would like help with this please.
+I'll give you a copy of the repositories and you give me back several Git repos (one for each).
+They will be uploaded to link:https://github.com/FreshPorts[https://github.com/FreshPorts] (our project on GitHub).
+
+These are the existing Subversion repos:
+
+* ingress (code for the back end)
+* database schema
+* backend - monitoring code
+* packaging - scripts for cutting new tarballs - deprecated via Git
+* daemontools - now misnamed, because the scripts use man:daemon[8]
+* periodics - scripts started by man:periodic[8]
+* ports - for the FreeBSD packages which install the above.
+
+==== I won't be running FreshPorts forever
+
+It's been over 22 years and I know others must take over eventually.
+I'd like to start that process now.
+There are several aspects to FreshPorts:
+
+* FreeBSD admin (updating the OS and packages)
+* front end code (website - mostly PHP)
+* back end code (commit processing - Perl, Python, shell)
+* database design (PostgreSQL).
+
+The database does not change very often and requires little maintenance compared to the applications and OS.
+The website pretty much runs itself.
+From time to time, a change to the FreeBSD ports infrastructure breaks something or requires a modification, but there is rarely any urgency to fix that.
+This is not a huge time commitment.
+There is a lot of learning.
+While not a complex application, FreshPorts is also not trivial.
diff --git a/website/content/en/status/report-2022-10-2022-12/NFS-in-prisons.adoc b/website/content/en/status/report-2022-10-2022-12/NFS-in-prisons.adoc
new file mode 100644
index 0000000000..d81a384b57
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/NFS-in-prisons.adoc
@@ -0,0 +1,24 @@
+=== Enable the NFS server to run in a vnet prison
+
+Links: +
+link:https://people.freebsd.org/%7Ermacklem/vnet.patch[Source patch for main] URL: link:https://people.freebsd.org/%7Ermacklem/vnet.patch[https://people.freebsd.org/~rmacklem/vnet.patch] +
+link:https://people.freebsd.org/%7Ermacklem/nfsd-vnet-prison-setup.txt[Simple Setup Doc] URL: link:https://people.freebsd.org/%7Ermacklem/nfsd-vnet-prison-setup.txt[https://people.freebsd.org/~rmacklem/nfsd-vnet-prison-setup.txt]
+
+Contact: Rick Macklem <rmacklem@freebsd.org>
+
+Several users of FreeBSD identified a need to run the NFS server inside a vnet prison.
+This turned into a small project, where I now have a patch that does this.
+It is currently available at the above link for testing or on Phabricator as link:https://reviews.freebsd.org/D37519[D37519].
+Without this patch, the NFS server cannot be run in a prison.
+
+Not included in the above patch is the ability to run the man:rpc.tlsservd[8] and man:nfsuserd[8] daemons within the vnet prison.
+I do now have patches that allow these daemons to run in the vnet prison along with man:mountd[8] and man:nfsd[8], but I would like to get the above patch into main before adding support for man:rpc.tlsservd[8] or man:nfsuserd[8].
+
+At this time, the code needs reviewing and testing.
+Hopefully this can be completed in the next few weeks, so that the patch can be committed to `main` and possibly also MFC'd to `stable/13`.
+
+==== To do
+
+* Testing the above patch.
+* Reviewing the above patch.
+* Doing the same for the man:rpc.tlsservd[8] and man:nfsuserd[8] patches.
diff --git a/website/content/en/status/report-2022-10-2022-12/_index.adoc b/website/content/en/status/report-2022-10-2022-12/_index.adoc
new file mode 100644
index 0000000000..d6ff60e63f
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/_index.adoc
@@ -0,0 +1,203 @@
+---
+title: "FreeBSD Status Report Fourth Quarter 2022"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2022-10-2022-12
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+Entries from the various official and semi-official teams, as found in the link:../../administration/[Administration Page].
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+include::{reports-path}/status.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects.
+
+include::{reports-path}/accessibility.adoc[]
+
+'''
+
+include::{reports-path}/vessel-status-report.adoc[]
+
+'''
+
+include::{reports-path}/NFS-in-prisons.adoc[]
+
+'''
+
+include::{reports-path}/pytest-for-atf.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+Changes affecting the base system and programs in it.
+
+include::{reports-path}/openssh.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+Updates to kernel subsystems/features, driver support, filesystems, and more.
+
+include::{reports-path}/ufs_snapshots.adoc[]
+
+'''
+
+include::{reports-path}/wifi.adoc[]
+
+'''
+
+include::{reports-path}/netlink.adoc[]
+
+'''
+
+include::{reports-path}/ddb_ctf.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+Updating platform-specific features and bringing in support for the new hardware platform.
+
+include::{reports-path}/cheribsd.adoc[]
+
+'''
+
+include::{reports-path}/riscv.adoc[]
+
+'''
+
+include::{reports-path}/golang_riscv64.adoc[]
+
+'''
+
+include::{reports-path}/xen.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+Updating cloud-specific features and bringing in support for new cloud platforms.
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/cloud-init.adoc[]
+
+'''
+
+include::{reports-path}/openstack-on-freebsd.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+Noteworthy changes in the documentation tree, manual pages, or new external books/documents.
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+include::{reports-path}/papers.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves.
+
+include::{reports-path}/FreshPorts.adoc[]
+
+'''
+
+include::{reports-path}/portsdb.adoc[]
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/xfce.adoc[]
+
+'''
+
+include::{reports-path}/pantheon.adoc[]
+
+'''
+
+include::{reports-path}/budgie.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/biology.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+Many projects build upon FreeBSD or incorporate components of FreeBSD into their project.
+As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report.
+The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions.
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2022-10-2022-12/accessibility.adoc b/website/content/en/status/report-2022-10-2022-12/accessibility.adoc
new file mode 100644
index 0000000000..287fd03e7c
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/accessibility.adoc
@@ -0,0 +1,22 @@
+=== Console screen reader infrastructure
+
+Links: +
+link:https://reviews.freebsd.org/D35776[console speaker daemon] URL: link:https://reviews.freebsd.org/D35776[https://reviews.freebsd.org/D35776] +
+link:https://reviews.freebsd.org/D35754[kernel support for console screen reader] URL: link:https://reviews.freebsd.org/D35754[https://reviews.freebsd.org/D35754] +
+link:https://wiki.freebsd.org/Accessibility/Wishlist/Base[base system accessibility wishlist] URL: link:https://wiki.freebsd.org/Accessibility/Wishlist/Base[https://wiki.freebsd.org/Accessibility/Wishlist/Base]
+
+Contact: Hans Petter Selasky <hps@selasky.org> +
+Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org>
+
+This project aims at providing a very basic screen reader usable in console mode (without a GUI) for FreeBSD.
+This is an important first step for system administrators using speech to access computers, who previously would have needed a second computer running a terminal emulator to install or configure a FreeBSD server or character-based desktop computer.
+
+The third and fourth quarters of 2022 saw basic design and some feature testing which looks promising, and a link:https://lists.freebsd.org/archives/freebsd-accessibility/2022-October/000014.html[detailed call for testing with installation procedure] posted.
+
+This project needs help with the following:
+
+* Code reviewing
+* Usability testing
+* Integrating with the FreeBSD installer.
+
+Sponsor: NVIDIA Networking (for the kernel development part)
diff --git a/website/content/en/status/report-2022-10-2022-12/azure.adoc b/website/content/en/status/report-2022-10-2022-12/azure.adoc
new file mode 100644
index 0000000000..d694296d43
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/azure.adoc
@@ -0,0 +1,42 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[https://wiki.freebsd.org/MicrosoftAzure] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[https://wiki.freebsd.org/HyperV]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+
+In this quarter, the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-12_4[12.4-RELEASE image] has been published to Azure Marketplace.
+
+Work in progress tasks:
+
+* Automating the image building and publishing process and merge to src/release/.
+* Building and publishing ZFS-based images to Azure Marketplace
+** All the required codes are merged to main branch, and can create ZFS-based images by specifying `VMFS=zfs`.
+** Need to make the build process more automatic and collaborating with release engineering to start generating snapshots.
+* Building and publishing Hyper-V gen2 VM images to Azure Marketplace
+** Blocked by https://bugs.freebsd.org/264267
+
+The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+
+Wei Hu and his colleagues in Microsoft are working on several tasks sponsored by Microsoft:
+
+* Fixing booting issue on Hyper-V gen2 VM in Azure
+** https://bugs.freebsd.org/264267
+* Porting Hyper-V guest support to aarch64
+** https://bugs.freebsd.org/266248
+** https://bugs.freebsd.org/267654
+
+Open tasks:
+
+* Update FreeBSD related doc at link:https://docs.microsoft.com[https://docs.microsoft.com]
+* Support FreeBSD in link:https://azure.microsoft.com/services/devops/pipelines/[Azure Pipelines]
+* Update link:https://www.freshports.org/sysutils/azure-agent[Azure agent port] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+
+Sponsor: Microsoft for work by Wei Hu and others in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2022-10-2022-12/biology.adoc b/website/content/en/status/report-2022-10-2022-12/biology.adoc
new file mode 100644
index 0000000000..6e685ef73b
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/biology.adoc
@@ -0,0 +1,28 @@
+=== Another milestone for biology ports
+
+Links: +
+link:https://github.com/auerlab/biolibc-tools[Biolibc-tools] URL: link:https://github.com/auerlab/biolibc-tools[https://github.com/auerlab/biolibc-tools] +
+link:https://github.com/auerlab/fasda[Fast And Simple Differential Analysis] URL: link:https://github.com/auerlab/fasda[https://github.com/auerlab/fasda]
+
+Contact: Jason Bacon <jwb@FreeBSD.org>
+
+The biology category in ports continues to grow and mature, and reached another milestone in 2022q4 with the introduction of the rna-seq metaport.
+
+The fields of genomics, and more generally, bioinformatics, are often referred to as the "wild west" of computational science.
+Analyses are typically mired by a lack of clear documentation, and difficulties deploying and using software.
+Many scientific software developers do not understand the potential of package managers to simplify their lives and the lives of their users.
+As a result, much scientific software is deployed using ad hoc "caveman" installations involving overly complicated and unreliable build systems that either bundle dependencies or attempt to work with random installations thereof.
+
+Work has been ongoing to make FreeBSD ports a model of how easy scientific software deployment should be.
+It now contains a solid core of many of the most commonly used open source applications in biological research.
+
+This quarter saw the completion of a tool chain for one of the most important types of analysis, known as RNA-Seq.
+RNA-Seq measures the abundance of RNA, and hence gene activity, in tissue samples.
+All of the tools needed to perform a typical RNA-Seq analysis can now be installed on FreeBSD using:
+
+`pkg install rna-seq`
+
+This includes many mature existing tools as well as new tools developed on FreeBSD, such as FASDA and biolibc-tools, easy-to-use replacements for some of the more troublesome tools traditionally used in an RNA-Seq pipeline.
+
+Software deployments for RNA-Seq that traditionally have taken weeks or longer can now be performed on FreeBSD in a few minutes with a single command.
+Scientists can spend their time doing science rather than struggling with IT issues.
diff --git a/website/content/en/status/report-2022-10-2022-12/budgie.adoc b/website/content/en/status/report-2022-10-2022-12/budgie.adoc
new file mode 100644
index 0000000000..30d6275d47
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/budgie.adoc
@@ -0,0 +1,37 @@
+=== Budgie desktop on FreeBSD
+
+Links: +
+link:https://blog.buddiesofbudgie.org/[Buddies of Budgie news] URL: link:https://blog.buddiesofbudgie.org/[https://blog.buddiesofbudgie.org/] +
+link:https://codeberg.org/olivierd/freebsd-ports-budgie[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-budgie[https://codeberg.org/olivierd/freebsd-ports-budgie] +
+
+Contact: Olivier Duchateau <duchateau.olivier@gmail.com>
+
+Budgie initially developed as the default desktop environment for the former Evolve OS.
+Since the 10.6.x releases, improvements have been made to be "agnostic".
+
+It is built on top of GNOME technologies such as GTK >= 3, GLib, Mutter, libpeas.
+
+The goal is to have a new desktop for end users.
+I have submitted 2 reviews (link:https://reviews.freebsd.org/D37224[D37224] and link:https://reviews.freebsd.org/D37286[D37286] for The FreeBSD Porter's Handbook) so committers can import it.
+
+These reviews include:
+
+* Mk/Uses framework `budgie.mk`
+* new virtual category (*budgie*)
+* 6 applications
+* icon theme `x11-themes/tela-icon-theme`.
+
+During this quarter, I have also submitted several patches (related to this desktop) especially:
+
+* `x11/gnome-terminal` update to 3.44.2 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267928[bug #267928]
+* `x11-wm/mutter` update to 42.6 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267899[bug #267899]
+* `x11-toolkits/libwnck3` update to 40.1 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267898[bug #267898].
+
+These bugs are also still open:
+
+* `devel/libpeas` link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267420[bug #267420]
+* `sysutils/gnome-settings-daemon` link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265107[bug #265107].
+
+==== Open task
+
+* Add support of LightDM in FreeBSD Handbook
diff --git a/website/content/en/status/report-2022-10-2022-12/cheribsd.adoc b/website/content/en/status/report-2022-10-2022-12/cheribsd.adoc
new file mode 100644
index 0000000000..7f70f17729
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/cheribsd.adoc
@@ -0,0 +1,32 @@
+=== CheriBSD 22.12 release
+
+Links: +
+link:https://www.cheribsd.org[CheriBSD] URL: link:https://www.cheribsd.org[https://www.cheribsd.org] +
+link:https://lists.cam.ac.uk/sympa/info/cl-cheribsd-announce[CheriBSD Announcements list] URL: link:https://lists.cam.ac.uk/sympa/info/cl-cheribsd-announce[https://lists.cam.ac.uk/sympa/info/cl-cheribsd-announce]
+
+Contact: Brooks Davis <brooks@FreeBSD.org> +
+Contact: Edward Tomasz Napierala <trasz@FreeBSD.org> +
+Contact: George Neville-Neil <gnn@FreeBSD.org> +
+Contact: Jessica Clarke <jrtc27@FreeBSD.org> +
+Contact: John Baldwin <jhb@FreeBSD.org> +
+Contact: Robert Watson <rwatson@FreeBSD.org> +
+Contact: Ruslan Bukin <br@FreeBSD.org>
+
+CheriBSD extends FreeBSD to implement memory protection and software compartmentalization features supported by the CHERI instruction-set extensions.
+There are two active architectural implementations of the CHERI protection model: CHERI-RISC-V and Arm's Morello.
+A sketch of CHERI-x86 is also under development.
+CheriBSD is a research operating system with a stable baseline implementation into which various new research features have been, or are currently being, merged.
+
+We have published the 22.12 release of CheriBSD including:
+
+* A general update of the baseline FreeBSD OS to August 2022.
+* Memory-safe adaptation of Direct Rendering Manager (DRM) and Panfrost device driver, which enable a Morello-based desktop system using on-board GPU and HDMI.
+These drivers may be used with hybrid or pure-capability kernels.
+* An initial set of graphics and desktop CheriABI software packages such as Wayland and portions of KDE to get you up and running with a memory-safe desktop environment.
+These components remain under active development, and we anticipate continuing package updates after the CheriBSD release.
+* An early research prototype of link:https://github.com/CTSRD-CHERI/cheripedia/wiki/Library-based-Compartmentalisation[library-based compartmentalization], which implements an alternative run-time linker running shared objects in libraries.
+This implementation is very much a work-in-progress, and is provided to enable research at other collaborator institutions needing easy access to the prototype.
+It is neither complete nor intended to be secure.
+* Improved pluggability of experimental heap temporal memory-safety support, which is not yet merged into the main development branch, but will now be easier to use by downloading an alternative kernel and heap allocator libraries provided by Microsoft.
+* An updated version of GDB with support for Morello instructions and inspecting memory tags.
+* Alpha support for ZFS file systems including support for boot environments.
diff --git a/website/content/en/status/report-2022-10-2022-12/ci.adoc b/website/content/en/status/report-2022-10-2022-12/ci.adoc
new file mode 100644
index 0000000000..1136a051b6
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/ci.adoc
@@ -0,0 +1,53 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] +
+link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[https://wiki.FreeBSD.org/Jenkins] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[https://wiki.FreeBSD.org/HostedCI] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[https://wiki.FreeBSD.org/3rdPartySoftwareCI] +
+link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[https://lists.FreeBSD.org/subscription/dev-ci]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+The FreeBSD CI team maintains the continuous integration system of the FreeBSD project.
+The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results.
+The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs.
+The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure.
+
+During the fourth quarter of 2022, we continued working with the contributors and developers in the project to fulfill their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD.
+
+Important completed tasks:
+
+* link:https://ci.FreeBSD.org/job/FreeBSD-main-amd64-gcc9_build/[FreeBSD-main-amd64-gcc9_build] now sends failing reports to the committers whose commits may be related.
+* link:https://ci.FreeBSD.org/job/FreeBSD-main-amd64-gcc12_build/[FreeBSD-main-amd64-gcc12_build] has been added.
+* link:https://ci.FreeBSD.org/job/FreeBSD-main-powerpc64-images/[FreeBSD-main-powerpc64-images] now also builds bootable APM disk image for Apple G5 baremetal and QEMU -M mac99 (by alfredo@)
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository
+* Improving the hardware test lab and adding more hardware for testing
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Adding more external toolchain related jobs
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/cloud-init.adoc b/website/content/en/status/report-2022-10-2022-12/cloud-init.adoc
new file mode 100644
index 0000000000..ead9082e65
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/cloud-init.adoc
@@ -0,0 +1,23 @@
+=== FreeBSD as a Tier 1 cloud-init Platform
+
+Links: +
+link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[https://cloud-init.io/] +
+link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[https://cloudinit.readthedocs.io/en/latest/] +
+link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst]
+
+Contact: Mina Galić <me+FreeBSD@igalic.co>
+
+cloud-init is the standard way of provisioning servers in the cloud.
+Unfortunately, cloud-init support for operating systems other than Linux is rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform.
+To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support.
+The broader plan is to lift support across all BSDs.
+
+The first milestone has been delivered.
+Along with many bug fixes, we now have link:https://github.com/canonical/cloud-init/pull/1779[merged] an man:ifconfig[8] parser, which allows us to retrieve all the information of all network devices, similarly to how on Linux this is done by parsing the contents of `/sys/class/net/<dev>/`.
+In the coming weeks, this project will align itself with the Azure developers to do some crucial refactoring.
+This will move our new parser further into cloud-init's main execution paths.
+
+People interested in helping with the project can help with testing new features and fixes through package:net/cloud-init-devel[], which will be updated whenever we make significant commits.
+Further, people with access to, and experience with, OpenBSD and NetBSD are also highly welcome to help.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/clusteradm.adoc b/website/content/en/status/report-2022-10-2022-12/clusteradm.adoc
new file mode 100644
index 0000000000..9c6697be91
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/clusteradm.adoc
@@ -0,0 +1,74 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular cluster-wide software upgrades +
+Two full upgrades to fix and prevent some impacting issues (FreeBSD-EN-22:25.tcp and FreeBSD-EN-22:28.heimdal).
+* Regular support for FreeBSD.org user accounts
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* Site audit at our primary site
+** Inventory of spares and other miscellanea occupying space in our cabinets.
+** Inventory of PDUs/power outlet usage and identifying faulty PSUs.
+* Identify and fix major DNS issue impacting the project +
+The primary DNS servers hosted on HE.net suffered outages for a few days, and new DNS servers were deployed worldwide.
+We thank our sponsor link:https://www.metapeer.com/[Metapeer] for providing anycast infrastructure.
+* Deploy a new mirror in Frankfurt, Germany +
+A replacement for our mirror in Amsterdam (site decommissioned).
+Former and new mirror hosted and sponsored by link:https://deploy.equinix.com/[Equinix].
+* Reuse parts of three broken CI machines +
+No replacements for these at this moment, awaiting a cluster refresh soon.
+* Work with the PowerPC team to improve the PowerPC cluster machines
+** Parts like mainboard, NVMe and Power 9 CPU bought through the FreeBSD Foundation.
+** Former package builder fixed, and re-deployed as powerpc and powerpc64 package builder.
+** Former devref machine reinstalled as a new powerpc64le package builder.
+** The cluster has now only these two PowerPC machines in operation.
+* Several rounds to free up disk space usage in the cluster machines
+* Setup of an experimental search engine for the mailing lists: https://lists.freebsd.org/search
+* Fix a bug in the mailing lists archiver, which resulted in some broken links +
+All mailing lists archives have been regenerated.
+
+Work in progress:
+
+* Large-scale network upgrade at our primary site +
+New link:https://www.juniper.net/[Juniper] switches arrived at our primary site to replace the former ones.
+We thank link:https://www.juniper.net/[Juniper] for the donation.
+* Replace old servers in our primary site and a few mirrors +
+Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs.
+This task is in conjunction with the FreeBSD Foundation and donors/sponsors.
+* Create a new database for the mailing list search engine to allow searching for mail in the archives from mailman's time
+
+FreeBSD Official Mirrors Overview:
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America (California, New Jersey [the primary site], and Washington).
+
+The hardware and network connection have been generously provided by:
+
+* https://www.bytemark.co.uk/[Bytemark Hosting]
+* https://www.bbtower.co.jp[Cloud and SDN Laboratory at BroadBand Tower, Inc]
+* https://www.cs.nycu.edu.tw[Department of Computer Science, National Yang Ming Chiao Tung University]
+* https://deploy.equinix.com[Equinix]
+* https://internet.asn.au/[Internet Association of Australia]
+* https://www.isc.org/[Internet Systems Consortium]
+* https://www.inx.net.za[INX-ZA]
+* https://www.kddi-webcommunications.co.jp/[KDDI Web Communications Inc]
+* https://myren.net.my[Malaysian Research & Education Network]
+* https://www.metapeer.com[Metapeer]
+* https://www.nyi.net/[New York Internet]
+* https://nic.br[Nic.br]
+* https://your.org[Your.org]
+
+The Frankfurt single server mirror is now the primary Europe mirror in bandwidth and usage.
+
+We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site.
+
+We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch.
+United States (West Coast) and Europe (anywhere) are preferable places.
+
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site.
diff --git a/website/content/en/status/report-2022-10-2022-12/core.adoc b/website/content/en/status/report-2022-10-2022-12/core.adoc
new file mode 100644
index 0000000000..601f5983ca
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/core.adoc
@@ -0,0 +1,32 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== Items
+
+===== Core Team Charter
+
+A delegation of the current core team is working together with some members of the previous Core Team to draft a core team charter.
+There was a face-to-face meeting in the US on December 3 - 4 to discuss the new charter.
+The delegation will present to the rest of the core team and discuss the details in the first quarter of 2023.
+The same delegation also had a meeting with the FreeBSD Foundation board on December 5th to discuss the collaboration details.
+
+===== Experimental Matrix IM solution
+
+The core team is working on evaluating Matrix as an instant messaging tool for the project.
+This will make the project's communication channels less dependant on third parties.
+The service will be made available to the FreeBSD community to test and evaluate its validity at a later date.
+
+===== Committer's Guide
+
+Deprecate BSD-2-Clause-FreeBSD and use BSD-2-Clause.
+For more information please refer to the link:https://cgit.freebsd.org/doc/commit/?id=a6e5d24925949785122a9f37f163d58239fd5484[commit].
+
+==== Commit bits
+
+* Core approved the src commit bit for Zhenlei Huang (zlei@)
+* Core approved the src commit bit for Corvin Köhne (corvink@)
+* Core approved the src commit bit for Sumit Saxon (ssaxena@)
+* Core approved the restore of the source commit bit for Paweł Jakub Dawidek (pjd@).
diff --git a/website/content/en/status/report-2022-10-2022-12/ddb_ctf.adoc b/website/content/en/status/report-2022-10-2022-12/ddb_ctf.adoc
new file mode 100644
index 0000000000..a479c73dac
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/ddb_ctf.adoc
@@ -0,0 +1,15 @@
+=== Adding basic CTF support to ddb
+
+Links: +
+link:https://reviews.freebsd.org/D37898[Differential 1] URL: link:https://reviews.freebsd.org/D37898[https://reviews.freebsd.org/D37898] +
+link:https://reviews.freebsd.org/D37899[Differential 2] URL: link:https://reviews.freebsd.org/D37899[https://reviews.freebsd.org/D37899]
+
+Contact: Bojan Novković <bojan.novkovic@kset.org>
+
+The goal of this project was to extend the ddb kernel debugger to use the kernel's Compact C Type Format (CTF) data and use the newly added features to implement a pretty-printing command in ddb.
+
+Due to a restrictive execution environment (no IO or memory allocation), ddb can not use existing kernel linker methods to retrieve the kernel's CTF data.
+Instead, the first patch adds the ability to load the kernel's CTF data during boot and adds a new kernel linker method used for accessing CTF data from ddb.
+The second patch adds a basic interface for using CTF data in ddb and a pretty-printing command built using the newly added interfaces.
+
+Any feedback, comments, and reviews are welcome and would be greatly appreciated.
diff --git a/website/content/en/status/report-2022-10-2022-12/doceng.adoc b/website/content/en/status/report-2022-10-2022-12/doceng.adoc
new file mode 100644
index 0000000000..7cd1aab35c
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/doceng.adoc
@@ -0,0 +1,92 @@
+////
+Quarter:	4th quarter of 2022
+Prepared by:	fernape
+Reviewed by:	carlavilla@
+Last edit:	
+Version:	
+////
+
+=== Documentation Engineering Team
+
+Links: +
+link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[https://www.freebsd.org/docproj/] +
+link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[https://docs.freebsd.org/en/books/fdp-primer/] +
+link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[https://www.freebsd.org/administration/#t-doceng]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During the last quarter:
+
+* crees@ and zeising@ doc bits were taken in for safekeeping.
+
+Items pending and in the discussion:
+
+* link:https://cgit.freebsd.org/doc/commit/?id=4c50528a8678246a6d01765acac8c395434b8c7e[A new document about licensing] has been added to the documentation set.
+
+==== Porter's Handbook:
+
+Two new `USES` knobs have been added to the Handbook:
+
+* link:https://cgit.freebsd.org/doc/commit/?id=0870d76e67a3a4ca2d1169e0fbc0cd8e5b378f7f[New USES = luajit].
+* link:https://cgit.freebsd.org/doc/commit/?id=c94edcebb622c4a35405f591f242132db534cd7b[New USES = llvm].
+
+Also:
+
+* link:https://cgit.freebsd.org/doc/commit/?id=f55bb91726b6ad07362bf8aedb6a3aa9d62bd41f[Erlang facilities] have been documented
+* link:https://cgit.freebsd.org/doc/commit/?id=ef23f41eb565c84fc675bc9dbf1810e51c616799[The new CABAL_REVISION knob] has been documented.
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance]
+
+===== Q4 2022 Status
+
+* 12 languages
+* 150 registered users
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 8%)
+* Chinese (Traditional) (zh-tw)	(progress: 4%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 4%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 3%)
+* Portuguese (pt-br)		(progress: 16%)
+* Spanish (es)			(progress: 19%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone who contributed by translating or reviewing documents.
+
+And please, help promote this effort on your local user group; we always need more volunteers.
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Complete_)
+Public instance on https://man-dev.FreeBSD.org
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Work in progress_)
diff --git a/website/content/en/status/report-2022-10-2022-12/freebsd-foundation.adoc b/website/content/en/status/report-2022-10-2022-12/freebsd-foundation.adoc
new file mode 100644
index 0000000000..504c03b973
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/freebsd-foundation.adoc
@@ -0,0 +1,121 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[https://www.freebsdfoundation.org] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://freebsdfoundation.org/blog/technology-roadmap/] +
+link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.freebsdfoundation.org/donate/[https://www.freebsdfoundation.org/donate/] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/] +
+link:https://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[https://www.freebsdfoundation.org/journal/] +
+link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[https://www.freebsdfoundation.org/news-and-events/]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide.
+Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits.
+We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts.
+We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+==== Fundraising Efforts
+
+Thank you to everyone who made a financial contribution in 2022!
+We're still tallying up the totals and will have final numbers soon.
+Unfortunately, we did not meet our fundraising goal, which reinforced our need of having someone who can focus on encouraging organizations to invest in FreeBSD.
+We will bring someone on board soon to help with that effort.
+
+In this Quarterly Status report you'll read about many of the areas we funded in Q4 to improve FreeBSD and advocate for the Project (the two main areas we spend money on).
+Check out reports on the internally and externally funded projects like Openstack on FreeBSD, Enabling Snapshots on Filesystems Using Journaled Soft Updates, FreeBSD as a Tier 1 cloud-init Platform, and FreeBSD/riscv64 Improvements.
+In addition, we provided tons of community engagement and education opportunities virtually and in-person!
+
+If you want to help us continue our efforts, please consider making a donation towards our 2023 fundraising campaign!
+link:https://www.freebsdfoundation.org/donate/[https://www.freebsdfoundation.org/donate/]
+
+We also have a Partnership Program for larger commercial donors.
+You can read about it at link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/].
+
+==== OS Improvements
+
+During the last quarter of 2022, 218 src, 45 ports, and 12 doc tree commits identified the Foundation as a sponsor.
+Work was committed under Foundation sponsorship to repositories outside of FreeBSD as well, e.g., to the cloud-init project.
+Some of this sponsored work is described in separate report entries:
+
+* FreeBSD as a Tier 1 cloud-init Platform
+* OpenStack on FreeBSD project update
+* Wireless Report
+* Enabling Snapshots on Filesystems Using Journaled Soft Updates
+
+Other Foundation work in the src tree included:
+
+- a variety of additions and fixes from Konstantin Belousov including commits to the virtual memory system (e.g., link:https://cgit.freebsd.org/src/commit/?id=ec201dddfbddd3a77dd3f3afc9b007d0e13e7ad1[ec201dd], link:https://cgit.freebsd.org/src/commit/?id=cd086696c2cb6d23bac3bc749836d36a9280ae98[cd08669], and link:https://cgit.freebsd.org/src/commit/?id=d537d1f12e8829faccd395115193b03b578f1176[d537d1f]), and file systems (e.g., link:https://cgit.freebsd.org/src/commit/?id=37aea2649ff707f23d35309d882b38e9ac818e42[37aea26], link:https://cgit.freebsd.org/src/commit/?id=83aff0f08c525ea3c394f3dd6598665cd369d53c[83aff0f], link:https://cgit.freebsd.org/src/commit/?id=860399eb86cc431412bfbce0ab76c6652e5b6c07[860399e], and link:https://cgit.freebsd.org/src/commit/?id=4d903a1a74d9526aba4d177e89c10f97df5662f2[4d903a1])
+- work from Andrew Turner on arm64 such as link:https://cgit.freebsd.org/src/commit/?id=c15085278cb55bd3c1ea252adf5635bb6800b431[an implementation of per-superpage locks] and link:https://cgit.freebsd.org/src/commit/?id=969935b86b179b2b517ab5d35d943fcb761203c1[the addition of support for an array of hwresets]
+- more RISC-V improvements from Mitchell Horne, including link:https://cgit.freebsd.org/src/commit/?id=701923e2a4105be606c5263181b6eb6f546f1a84[improvements to parsing of ISA property strings], link:https://cgit.freebsd.org/src/commit/?id=95b1c27069775dd969cd045888b4ea5aeb53cb7f[optimizations to memory allocation], and various documentation additions and improvements
+- follow-up commits to Mark Johnston's work to add ZFS Support to makefs(8) (e.g., link:https://cgit.freebsd.org/src/commit/?id=89585511cc052643a774f64f6450d18e7dd51d4a[work to easily provide ZFS-based VM and cloud images] and link:https://cgit.freebsd.org/src/commit/?id=72a1cb05cd230ce0d12a7180ae65ddbba2e0cb6d[automation for better defaults] from Li-Wen Hsu)
+- a variety of work from Ed Maste, including link:https://cgit.freebsd.org/src/commit/?id=38a52bd3b5cac3da6f7f6eef3dd050e6aa08ebb3[an ssh update] and link:https://cgit.freebsd.org/src/commit/?id=86edb11e7491e657e6c75ef6814867021665c377[a switch to LLVM objdump].
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project.
+You can read about the latest activity for that work in a separate report entry.
+
+==== FreeBSD Advocacy and Education
+
+Much of our effort is dedicated to Project advocacy.
+This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations.
+The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier.
+Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe.
+These events can be BSD-related, open source, or technology events geared towards underrepresented groups.
+We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.
+This all helps provide a healthy ecosystem.
+We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.
+We are continuing to attend events both in person and virtual as well as planning the November Vendor Summit.
+In addition to attending and planning virtual events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD.
+
+Check out some of the advocacy and education work we did last quarter:
+
+* Sponsored the OpenZFS Developer Summit, October 24-25, 2022 in San Francisco, CA
+
+* Sponsored All Things Open, October 30-November 2, 2022 in Raleigh, NC
+
+* Sponsored and helped organize the November 2022 FreeBSD Vendor Summit.
+link:https://youtube.com/playlist?list=PLugwS7L7NMXwVfBq5eDRky450jp7LTRJj[Videos from the Summit are available].
+
+* Held a new FreeBSD Friday: link:https://youtu.be/t2VLTtHYIcA[An Introduction to FreeBSD Services] by Drew Gurkowski
+
+* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-fall-2022-update/[Fall] and link:https://freebsdfoundation.org/news-and-events/newsletter/11982/[Winter] Newsletter updates
+
+* New Blog Posts
+
+** link:https://freebsdfoundation.org/blog/meet-the-2022-freebsd-google-summer-of-code-students-koichi-imai/[Meet the 2022 FreeBSD Google Summer of Code Students: Koichi Imai]
+** link:https://freebsdfoundation.org/blog/meet-the-2022-freebsd-google-summer-of-code-students-bojan-novkovic/[Meet the 2022 FreeBSD Google Summer of Code Students: Bojan Novković]
+** link:https://freebsdfoundation.org/blog/keeping-freebsd-secure-learn-the-whys-and-hows-with-the-freebsd-sec-team/[Keeping FreeBSD Secure: Learn the Whys and Hows with the FreeBSD Sec Team]
+** link:https://freebsdfoundation.org/blog/the-freebsd-journal-is-still-free/[The FreeBSD Journal is still Free!]
+** link:https://freebsdfoundation.org/blog/eurobsdcon-2022-trip-report-muhammad-moinur-rahman/[EuroBSDCon 2022 Trip Report: Muhammad Moinur Rahman]
+** link:https://freebsdfoundation.org/blog/eurobsdcon-2022-trip-report-patrick-mcevoy/[EuroBSDCon 2022 Trip Report: Patrick McEvoy]
+** link:https://freebsdfoundation.org/blog/fall-foundation-software-development-update/[Fall Foundation Software Development Update]
+** link:https://freebsdfoundation.org/blog/invest-in-freebsd/[Invest in FreeBSD]
+** link:https://freebsdfoundation.org/blog/2022-in-review-advocacy/[2022 in Review: Advocacy]
+** link:https://freebsdfoundation.org/blog/foundation-sponsors-update-to-wireguard-kernel-port-for-freebsd/[Foundation Sponsors Update to WireGuard Kernel Port for FreeBSD]
+** link:https://freebsdfoundation.org/blog/2022-in-review-fundraising-update/[2022 in Review: Fundraising Update]
+** link:https://freebsdfoundation.org/blog/2022-in-review-software-development/[2022 in Review: Software Development]
+** link:https://freebsdfoundation.org/blog/2022-in-review-continuous-integration-and-quality-assurance-update/[2022 in Review: Continuous Integration and Quality Assurance Update]
+
+* FreeBSD in the news:
+
+** link:https://freebsdfoundation.org/news-and-events/latest-news/ampere-getting-cloud-native-with-freebsd-on-oci-ampere-a1-with-terraform/[Ampere: Getting Cloud-Native with FreeBSD on OCI Ampere A1 with Terraform]
+** link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-is-well-supported-on-4th-gen-amd-epyc-processors/[FreeBSD is Well Supported on 4th Gen AMD EPYC™ Processors]
+
+* For a quick review of all the Foundation efforts in 2022, check out our link:https://youtu.be/6ybbeFXFm-I[2022 Thank You Video].
+
+We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal.
+As we mentioned previously, the FreeBSD Journal is now a free publication.
+Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[https://www.freebsdfoundation.org/journal/].
+
+You can find out more about events we attended and upcoming events at link:https://www.freebsdfoundation.org/news-and-events/[https://www.freebsdfoundation.org/news-and-events/].
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://www.freebsdfoundation.org[https://www.freebsdfoundation.org] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2022-10-2022-12/gcc.adoc b/website/content/en/status/report-2022-10-2022-12/gcc.adoc
new file mode 100644
index 0000000000..47ed95c948
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/gcc.adoc
@@ -0,0 +1,50 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[https://gcc.gnu.org/gcc-12/]
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> +
+
+==== Update GCC default version to 12
+
+Thank you very much to antoine@ for running the necessary exp-runs and to all the contributors, maintainers and committers involved in the process.
+
+As was noted last quarter, for every major version of GCC, FreeBSD usually awaits the release of the second minor version to update GCC default version.
+However next time I would like to attempt to update the default version as soon as the first minor version of GCC 13 is out.
+The rationale for awaiting the second minor release was to wait for other operating systems (in particular Linux distributions) to find, report, and fix bugs, so that FreeBSD could focus mainly on FreeBSD-specific cases.
+But this also meant that upstream software developers only heard from FreeBSD rarely, and mostly when it concerned FreeBSD only, thus our operating system risks being considered minor and unimportant for them.
+
+My hope is that software authors can value supporting FreeBSD more as the number of its contributions to other projects also increases.
+Of course I understand that this will imply more work for all ports maintainers and I will do my best to help them as much as I can.
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265948[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2659548]
+
+==== Resolution of a conflict preventing the installation of multiple GCC versions simultaneously
+
+Now, lang/gcc11 and lang/gcc12 can be installed at the same time.
+This was particularly important for the update of the GCC default version, since a few ports have been kept to compile with GCC 11 for now.
+
+Note however that at the moment only one -devel GCC port at the time can be installed on your system.
+This is because I have patched the standard ports only: for the -devel port I expect upstream to fix the issue soon, by using a link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491[patch submitted by a FreeBSD user] or link:https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html[my own patch], or using some other solution.
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257060[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257060]
+
+==== D language
+
+D is now enabled in lang/gcc11 and lang/gcc11-devel, thanks to diizzy.
+I plan to include D support for higher versions of GCC too, but this cannot be done as easily as for GCC 11 due to bootstrapping issues: starting from GCC 12, the D compiler GDC needs a working GDC to be built.
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266825[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266825]
+
+==== Crashes with -fsanitize=address
+
+Software compiled with GCC using the `-fsanitize=address` switch has been reported to crash.
+I have fixed the issue for lang/gcc11, lang/gcc11-devel, lang/gcc12, and lang/gcc12-devel.
+I am still working on lang/gcc13-devel.
+
+Use of the address sanitizer requires ASLR to be disabled.
+As GCC gets the code that I am modifying from LLVM, and LLVM is also included in the FreeBSD src repository with some patches that improve ASLR detection and automatically re-run programs with ASLR disabled when necessary, I am also merging those patches.
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751]
diff --git a/website/content/en/status/report-2022-10-2022-12/golang_riscv64.adoc b/website/content/en/status/report-2022-10-2022-12/golang_riscv64.adoc
new file mode 100644
index 0000000000..e61a41b111
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/golang_riscv64.adoc
@@ -0,0 +1,12 @@
+=== go on FreeBSD riscv64
+
+Links: +
+link:https://github.com/golang/go[golang Home Page] URL: link:https://github.com/golang/go[https://github.com/golang/go] +
+link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[FreeBSD riscv64 github repo] URL: link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[https://github.com/MikaelUrankar/go/tree/freebsd_riscv64] +
+link:https://github.com/golang/go/issues/53466[FreeBSD riscv64 golang issue] URL: link:https://github.com/golang/go/issues/53466[https://github.com/golang/go/issues/53466]
+
+Contact: Mikaël Urankar <mikael@FreeBSD.org> +
+Contact: Dmitri Goutnik <dmgk@FreeBSD.org>
+
+The proposal to add support for FreeBSD riscv64 has been accepted and the patches merged.
+golang on FreeBSD riscv64 will be available in golang v1.20 (to be released in February 2023).
diff --git a/website/content/en/status/report-2022-10-2022-12/intro.adoc b/website/content/en/status/report-2022-10-2022-12/intro.adoc
new file mode 100644
index 0000000000..24751438ea
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/intro.adoc
@@ -0,0 +1,11 @@
+The New Year has started and here is the last status report of 2022, including 34 reports.
+You will also notice that for the first time a new category has been introduced: the Cloud category.
+As FreeBSD keeps up to date with the latest technologies in IT, projects dealing with the cloud make steady improvements, and thus it has been judged that they deserve their own category in the status reports.
+
+The new category is not the only change about status reports.
+Indeed, the status team is revisiting its own workflow to become more efficient.
+If you are a report submitter, please ensure to read carefully the report authored by the status team as well as the next Call for Reports emails to keep up with the most recent changes.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the status team.
diff --git a/website/content/en/status/report-2022-10-2022-12/kde.adoc b/website/content/en/status/report-2022-10-2022-12/kde.adoc
new file mode 100644
index 0000000000..c36dc83dae
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/kde.adoc
@@ -0,0 +1,35 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] +
+link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine.
+The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack.
+
+==== Infrastructure
+
+* CMake ports now share a single version number. Various build-flags have been updated for FreeBSD ports builds: under some circumstances, release-flags were ignored and debug-flags applied, which is undesirable. CMake now also refuses to fetch remote sources during a ports build.
+* Qt versions are now Qt 5.15.7 (used by KDE) and Qt 6.4.1. Some applications in the ports tree are now "flavored" for Qt5 and Qt6.
+
+==== KDE Stack
+
+KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well.
+These (large) updates land shortly after their upstream release and are not listed separately.
+
+* KDE Frameworks 5 is now at version 5.101 (latest monthly release from December 2022). This is likely one of the last "Frameworks 5" releases, as the next major series comes closer.
+* KDE Gear is now version 22.12.0 (update for December 2022).
+* KDE Plasma is now version 5.24.7 (update for October 2022).
+
+Note that KDE Plasma 5.25 has been released upstream, but is still waiting on fixes before it can land in the ports tree (for example, link:https://bugs.kde.org/show_bug.cgi?id=458356[this KActivityManager bug] in KDE's bug-tracker).
+
+==== Related Ports
+
+* package:graphics/krita[] is now version 5.1.3.
+* package:graphics/poppler[] was updated multiple times, now at version 22.11. It supports Qt5 and Qt6 through separate ports.
+* package:net-im/telegram-desktop[] was now supports Qt5 and Qt6 through flavors.
diff --git a/website/content/en/status/report-2022-10-2022-12/netlink.adoc b/website/content/en/status/report-2022-10-2022-12/netlink.adoc
new file mode 100644
index 0000000000..b9b307ac96
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/netlink.adoc
@@ -0,0 +1,45 @@
+=== Netlink on FreeBSD
+
+Links: +
+link:https://reviews.freebsd.org/D36002[Initial review] URL: link:https://reviews.freebsd.org/D36002[https://reviews.freebsd.org/D36002] +
+link:https://static.ipfw.ru/files/netlink.pdf[Netlink talk] URL: link:https://static.ipfw.ru/files/netlink.pdf[https://static.ipfw.ru/files/netlink.pdf]
+
+Contact: Alexander Chernikov <melifaro@FreeBSD.org>
+
+Netlink is a communication protocol defined in RFC 3549.
+It is an async, TLV-based protocol, providing 1-1 and 1-many communications between kernel and userland.
+Netlink is currently used in the Linux kernel to modify, read and subscribe for nearly all networking states.
+Interface state, addresses, routes, firewall, rules, fibs, etc, are controlled via Netlink.
+
+==== Why is Netlink important for FreeBSD?
+
+POSIX defines an API for base functions/system calls.
+There is no such standard for the plethora of protocol/device-level/subsystem-level ioctls.
+Each subsystem/driver invents its own protocol, handling format and compatibility.
+Extendability is a notable problem in the networking control plane.
+For example, it is extremely hard to add properties to the routing socket messages without breaking compatibility.
+
+Netlink offers unification by providing a standard communication layer and basic easily-extendable message formatting.
+It can serve as a "broker", automatically combining requested data from different sources in a single request (example: interface state dump).
+Netlink APIs lower the bar for application developers to support FreeBSD, while providing the desired extendability.
+
+==== Current status
+
+Netlink has been committed to HEAD.
+The code implements a subset of the `NETLINK_ROUTE` subsystem and `NETLINK_GENERIC` framework.
+
+`NETLINK_ROUTE` supports add/delete/replace operations for routes, nexthops and link-level addresses.
+Partial support exists for the interface addresses and interfaces.
+
+Linuxulator support for Netlink has been committed to HEAD.
+It is possible to use the unmodified ip from iproute2 with routes, nexthops, addresses and interfaces.
+
+The simple userland library, snl(3), that provides convenient abstractions on the netlink socket, has been committed to HEAD.
+
+The first third-party software, BIRD, link:https://gitlab.nic.cz/labs/bird/-/commit/1e47b9f203aaaad0fb658d40a1670f1d0437f1f8[added experimental FreeBSD Netlink support].
+
+==== Next steps
+
+* Add Netlink to GENERIC
+* Make `netstat/route/arp/ndp/ifconfig` use Netlink interfaces (help is appreciated)
+* Add FreeBSD Netlink support to ports of FreeRangeRouting (FRRouting (FRR)).
diff --git a/website/content/en/status/report-2022-10-2022-12/openssh.adoc b/website/content/en/status/report-2022-10-2022-12/openssh.adoc
new file mode 100644
index 0000000000..0a0374de34
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/openssh.adoc
@@ -0,0 +1,15 @@
+=== Base System OpenSSH Update
+
+Links: +
+link:https://www.openssh.com/[OpenSSH] URL: link:https://www.openssh.com/[https://www.openssh.com/] +
+link:https://www.openssh.com/txt/release-9.1[OpenSSH 9.1 release notes] URL: link:https://www.openssh.com/txt/release-9.1[https://www.openssh.com/txt/release-9.1]
+
+Contact: Ed Maste <emaste@freebsd.org>
+
+OpenSSH, a suite of remote login and file transfer tools, was updated from version 9.0p1 to 9.1p1 in the FreeBSD base system.
+
+It has been merged to the stable branches, is available in FreeBSD 12.4, and will be in the upcoming FreeBSD 13.2.
+
+A number of bug fixes and minor improvements have been submitted upstream to OpenSSH, and this process will continue with subsequent updates.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/openstack-on-freebsd.adoc b/website/content/en/status/report-2022-10-2022-12/openstack-on-freebsd.adoc
new file mode 100644
index 0000000000..3c085974db
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/openstack-on-freebsd.adoc
@@ -0,0 +1,54 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[https://www.openstack.org] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[https://github.com/openstack-on-freebsd] +
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+OpenStack is an open-source cloud operating system for different resource types like virtual and bare-metal machines.
+Users can spawn FreeBSD instances on the open cloud platform, but it is not currently possible to run the OpenStack control plane on FreeBSD hosts.
+This project aims to port key OpenStack components so that FreeBSD can function as an OpenStack host.
+
+In 2022 Q4, we have almost completed the porting work regarding the crucial OpenStack components.
+Most of the components/services composing an essential OpenStack cluster are now able to run on FreeBSD hosts, including:
+
+* Keystone (identity service)
+** keystone server
+* Glance (image service)
+** glance-api
+* Placement (resource tracking and inventory service)
+** placement-api
+* Neutron (networking service)
+** neutron-server
+** neutron-metadata-agent
+** neutron-dhcp-agent
+** neutron-openvswitch-agent
+* Nova (compute service)
+** nova-api
+** nova-conductor
+** nova-scheduler
+** nova-compute
+** nova-novncproxy
+
+The step-by-step documents for constructing a POC can be found link:https://github.com/openstack-on-freebsd/docs[in the `docs` repository].
+
+In its design, most of the OpenStack components provide an abstraction layer for the underlying implementations.
+For nova, we choose the combination of the `libvirt` driver with the `bhyve` virtualization type enabled.
+For neutron, it is the `openvswitch` mechanism driver.
+We solved several runtime dependencies and porting issues against the Libvirt, bhyve, and Open vSwitch combinations with minimal effort.
+We still have lots of work to undertake to make the changes back to OpenStack upstream.
+
+TODOs include:
+
+* Develop a proper alternative execution path in the `oslo_privsep` module for FreeBSD environments
+* Develop a new virtualization type, `bhyve`, for nova-compute's `libvirt` driver
+* Develop the IP library for FreeBSD under `neutron/agent/freebsd`
+
+In the first few weeks of 2023, we will focus on breaking through the last mile of the instance spawn path and wrapping up the documentation regarding POC site construction.
+We will also try rebasing the porting work to the master branch of OpenStack (now Xena).
+
+People interested in helping with the project can first help check the documentation by following the installation guide.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/pantheon.adoc b/website/content/en/status/report-2022-10-2022-12/pantheon.adoc
new file mode 100644
index 0000000000..422ada8d08
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/pantheon.adoc
@@ -0,0 +1,43 @@
+=== Pantheon desktop on FreeBSD
+
+Links: +
+link:https://elementary.io/[elementary OS] URL: link:https://elementary.io/[https://elementary.io] +
+link:https://codeberg.org/olivierd/freebsd-ports-elementary[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-elementary[https://codeberg.org/olivierd/freebsd-ports-elementary]
+
+Contact: Olivier Duchateau <duchateau.olivier@gmail.com>
+
+The Pantheon desktop environment is designed for elementary OS.
+It builds on GNOME technologies (such as Mutter, GTK 3 and 4) and it is written in Vala.
+The goal is to have a new desktop for users.
+
+*13.1-RELEASE or higher is required*, because several core components depend on package:deskutils/xdg-desktop-portal[].
+
+The repository contains Mk/Uses framework `elementary.mk`, official applications, and curated ports which depend on package:x11-toolkits/granite[].
+
+Since the previous report, we have been updating its related ports, especially:
+
+* package:deskutils/elementary-calendar[] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267797[update to 6.1.2]
+* package:deskutils/iconbrowser[]
+* package:graphics/elementary-photos[]
+* package:math/elementary-calculator[]
+* package:multimedia/elementary-videos[]
+* package:x11/elementary-terminal[]
+* package:x11-themes/gnome-icons-elementary[]
+* package:x11-toolkits/granite7[].
+
+Power manager plugins for top panel (wingpanel) and control center (switchboard) are finished.
+
+A new switchboard plugin is also available, package:net/switchboard-plug-sharing[].
+Ported *Rygel*, GNOME UPnP/DLNA services.
+
+Submitted other patches for low level libraries such as:
+
+* package:print/cups-pk-helper[] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266067[update to 0.2.7] required by package:print/switchboard-plus-printers[]
+* package:devel/libgee[] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266585[update to 0.20.6] heavily used by the desktop
+* package:sysutils/polkit[] update to 122 (https://reviews.freebsd.org/D37137[D37137])
+* package:sysutils/accountsservice[] update to 22.08.8 (https://reviews.freebsd.org/D37679[D37679]).
+
+==== Open tasks
+
+* Improve documentation.
+* Continue to work on user settings.
diff --git a/website/content/en/status/report-2022-10-2022-12/papers.adoc b/website/content/en/status/report-2022-10-2022-12/papers.adoc
new file mode 100644
index 0000000000..e83b7ee077
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/papers.adoc
@@ -0,0 +1,19 @@
+=== FreeBSD Presentations and Papers
+
+Links: +
+link:https://papers.FreeBSD.org/[FreeBSD Presentations and Papers] URL: link:https://papers.FreeBSD.org/[https://papers.FreeBSD.org]
+
+Contact: Allan Jude <allanjude@FreeBSD.org> +
+Contact: Greg White <gkwhite@gmail.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: Philip Paeps <philip@FreeBSD.org>
+
+In this quarter, the presentations and papers from those events have been added:
+
+* BSDCan 2022
+* EuroBSDCon 2022.
+
+Open tasks:
+
+* Find and upload missing FreeBSD related presentations and papers
+* Issues listed at link:https://github.com/freebsd/freebsd-papers/issues[Open Issues].
diff --git a/website/content/en/status/report-2022-10-2022-12/portmgr.adoc b/website/content/en/status/report-2022-10-2022-12/portmgr.adoc
new file mode 100644
index 0000000000..91d2723194
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/portmgr.adoc
@@ -0,0 +1,71 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL: link:https://www.FreeBSD.org/ports/[https://www.FreeBSD.org/ports/] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[https://www.freebsd.org/portmgr/] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages (through its subsidiary pkgmgr), and personnel matters.
+Below is what happened in the last quarter.
+
+Currently we have just over 31,000 ports in the Ports Tree.
+There are currently close to 2900 open ports PRs of which almost 800 are unassigned.
+The last quarter saw 8194 commits by 159 committers on the main branch and 657 commits by 53 committers on the 2022Q4 branch.
+Compared to the quarter before, this means a small increase in the number of available ports but also in the number of open PRs and a decreasing number of commits made.
+
+On the personnel front, we welcomed Ronald Klop (ronald@) and said goodbye to bar@ and bhughes@.
+We welcomed pizzamig@ as a new official member after a successful lurking period.
+We also welcomed three new lurkers: bofh@, ler@, and ygy@.
+
+Portmgr split itself up into portmgr and pkgmgr.
+The new pkgmgr team, currently consisting of antoine@ and bdrewery@, is responsible for building packages and maintaining the package building cluster.
+
+Four new USES were introduced:
+
+* llvm to canonicalize ports dependencies on LLVM
+* luajit to select a LuaJIT runtime
+* octave to help ports depend on Octave and Octave-Forge
+* tex to define dependencies on TeX and its various components.
+
+The following default versions were bumped:
+
+* Firebird to 3.0
+* GCC to 12
+* Lazarus to 2.2.4
+* Lua to 5.4
+* PHP to 8.1
+* Samba to 4.13
+* Varnish to 6
+* LuaJIT is new and set at "luajit-openresty" for PowerPC64 and "luajit-devel" for all other architectures.
+
+Three new features were introduced, PIE, RELRO, and BIND_NOW.
+Each port can opt out of them by setting the <feature>_UNSAFE variable.
+Users can activate or deactivate them globally by setting WITH_<feature> or WITHOUT_<feature>.
+
+The following major ports were updated to new versions:
+
+* Chromium 108.0.5359.124
+* Electron 18.3.11, 19.0.15, and 21.2.0
+* Firefox 108.0.1
+* Firefox-ESR 102.6.0
+* gcc 12
+* KDE Plasma 5.24.7, Frameworks 5.101.0, Applications 22.12.0
+* Qt 5.15.7 and 6.4.1
+* Rust 1.66.0
+* SDL 2.26.1
+* Sway 1.8
+* wlroots 0.16.1
+* Wine 7.0.1.
+
+The exp-run reports are available again.
+During the last quarter, antoine@ ran 38 exp-runs to:
+
+* test port updates
+* change default versions
+* identify use of IPPROTO_DIVERT in ports
+* support PF_DIVERT in Python for FreeBSD 14.
diff --git a/website/content/en/status/report-2022-10-2022-12/portsdb.adoc b/website/content/en/status/report-2022-10-2022-12/portsdb.adoc
new file mode 100644
index 0000000000..59ad8e5bd0
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/portsdb.adoc
@@ -0,0 +1,32 @@
+=== PortsDB: Program that imports the ports tree into an SQLite database
+
+Links: +
+link:https://github.com/yurivict/freebsd-portsdb/[PortsDB] URL: link:https://github.com/yurivict/freebsd-portsdb/[https://github.com/yurivict/freebsd-portsdb/]
+
+Contact: Yuri Victorovich <yuri@FreeBSD.org>
+
+I developed the PortsDB project that imports FreeBSD ports into an SQLite database.
+The port is package:ports-mgmt/portsdb[].
+
+The database can be fully rebuilt in around 20 minutes, after which it can be quickly (in seconds) updated with new commits.
+
+The database is currently updated hourly: link:https://people.freebsd.org/%7Eyuri/ports.sqlite[https://people.freebsd.org/~yuri/ports.sqlite].
+
+PortsDB can be used to query ports using SQL, as a relational database.
+External services like Repology, FreshPorts, Portscout, and other similar services can use PortsDB to access information in the ports tree.
+
+Users can, for example, easily find their broken ports, or port duplicates, or all ports that they maintain that use gmake, among many other possible queries.
+Such queries aren't easy to perform by grepping the ports tree.
+
+Cross-DB queries are also easy to do.
+They can combine PortsDB, /var/db/pkg/repo-FreeBSD.sqlite, and /var/db/pkg/local.sqlite.
+
+All that needs to be done to run PortsDB is ./import.sh, and then ./update.sh after more commits are pulled into the ports repository.
+
+The periodic script is provided that can simplify integration with cron.
+Multiple ready to use SQL queries are also included.
+
+One particular immediate problem that PortsDB aims to solve is to fix incorrect FreeBSD port versions displayed by Repology.
+Repology uses ports INDEX which is missing some required information.
+This leads to Repology not being able to distinguish between real versions, and intermediate and made-up versions.
+PortsDB should allow Repology to solve this problem.
diff --git a/website/content/en/status/report-2022-10-2022-12/pot.adoc b/website/content/en/status/report-2022-10-2022-12/pot.adoc
new file mode 100644
index 0000000000..9868faa5dc
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/pot.adoc
@@ -0,0 +1,29 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[https://github.com/bsdpot]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> +
+Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@freebsd.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+During the last quarter, link:https://github.com/bsdpot/pot/releases/tag/0.15.4[pot 0.15.4] was released.
+It again contains a number of improvements like signing pot images as well as many bug fixes.
+Also, we welcome two new pot contributors: link:https://github.com/zilti[@zilti] and link:https://github.com/reezer[@reezer].
+
+Additionally, there is a new link:https://galaxy.ansible.com/zilti/pot[Ansible pot collection] available.
+
+Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: a repository of pot flavours and complete container images for usage with pot and in many cases Nomad.
+
+As you can see, we link:https://github.com/bsdpot/potluck/commits/master[had a busy quarter again], this time including improvements to the link:https://github.com/bsdpot/potluck/tree/master/nextcloud-nginx-nomad[Nextcloud] as well as link:https://github.com/bsdpot/potluck/tree/master/jitsi-meet[Jitsi] images.
+
+Furthermore, we landed pot-based FreeBSD support for sccache-dist server (the server component for distributed compilation of rust and C++ using sccache) and it will be part of the upcoming sccache 0.4.0, see link:https://github.com/mozilla/sccache/pull/1184[mozilla/sccache#1184].
+Once released, this will become available through devel/sccache.
+
+This means one can build rust projects on FreeBSD targeting a cluster of machines, something that could potentially be integrated into poudriere as well.
+
+Last but not least, link:https://www.youtube.com/watch?v=b0IB0mc2KTE[Luca's EuroBSDCon 2022 talk] is now available on YouTube.
+
+As always, feedback and patches are welcome.
diff --git a/website/content/en/status/report-2022-10-2022-12/pytest-for-atf.adoc b/website/content/en/status/report-2022-10-2022-12/pytest-for-atf.adoc
new file mode 100644
index 0000000000..0d2653aa92
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/pytest-for-atf.adoc
@@ -0,0 +1,28 @@
+=== Pytest support for the FreeBSD testing framework
+
+Links: +
+link:https://reviews.freebsd.org/D31084[Initial review] URL: link:https://reviews.freebsd.org/D31084[https://reviews.freebsd.org/D31084] +
+link:https://cgit.freebsd.org/src/tree/tests/examples/test_examples.py[Test examples] URL: link:https://cgit.freebsd.org/src/tree/tests/examples/test_examples.py[https://cgit.freebsd.org/src/tree/tests/examples/test_examples.py]
+
+Contact: Alexander Chernikov <melifaro@FreeBSD.org>
+
+Native pytest support for man:atf[7] enhances the capabilities of the FreeBSD test suite.
+
+Pytest simplifies test writing by reducing the amount of boiler-plate code.
+It offers several advantages over the existing atf-c and atf-shell bindings.
+One of the most important ones is the test parametrization, which allows improving coverage with writing nearly no code.
+The other is a rich assert system, offering detailed errors description.
+Python man:atf[7] support comes with a number of libraries that abstract a number of commonly-used tasks.
+For example, running a test within a VNET jail with man:epair[4] requires adding a single line of code.
+Such helpers are especially handy in the networking area, where tests with complex VNET setups are not uncommon.
+
+==== Current status
+
+Python support has been committed to HEAD.
+Currently, ~80 tests use the Python framework and the number is rising.
+Example tests have been committed to show the handling of the typical cases.
+
+==== Next steps
+
+* Work on increasing the adoption of the framework
+* Rewrite some of the older Python/shell tests in the netinet[6] to pytest (help is appreciated)
diff --git a/website/content/en/status/report-2022-10-2022-12/releng.adoc b/website/content/en/status/report-2022-10-2022-12/releng.adoc
new file mode 100644
index 0000000000..6a7ff7ec9b
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/releng.adoc
@@ -0,0 +1,24 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/12.4R/schedule/[FreeBSD 12.4-RELEASE schedule] URL: link:https://www.freebsd.org/releases/12.4R/schedule/[https://www.freebsd.org/releases/12.4R/schedule/] +
+link:https://www.freebsd.org/releases/12.4R/announce/[FreeBSD 12.4-RELEASE announcement] URL: link:https://www.freebsd.org/releases/12.4R/announce/[https://www.freebsd.org/releases/12.4R/announce/] +
+link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[https://www.freebsd.org/releases/13.2R/schedule/] +
+link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[https://www.freebsd.org/releases/14.0R/schedule/] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[https://download.freebsd.org/snapshots/ISO-IMAGES/]
+
+Contact: FreeBSD Release Engineering Team <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the fourth quarter of 2022, the Release Engineering Team completed work on the 12.4-RELEASE cycle.
+This is the final release from the stable/12 branch.
+During the release cycle, only one BETA build and two RC (release candidate) builds were needed; overall the release cycle went very smoothly and the release took place on December 5th.
+
+During the fourth quarter of 2022, the Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/13*, and *stable/12* branches.
+
+In the first quarter of 2023, the Release Engineering Team will start work on the upcoming 13.2-RELEASE.
+
+Sponsors: +
+Rubicon Communications, LLC ("Netgate") +
+The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/riscv.adoc b/website/content/en/status/report-2022-10-2022-12/riscv.adoc
new file mode 100644
index 0000000000..a2fe509ea5
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/riscv.adoc
@@ -0,0 +1,32 @@
+=== FreeBSD/riscv64 Improvements
+
+Links: +
+link:https://wiki.freebsd.org/riscv[Wiki Homepage] URL: link:https://wiki.freebsd.org/riscv[https://wiki.freebsd.org/riscv]
+
+Contact: Mitchell Horne <mhorne@FreeBSD.org>
+
+The FreeBSD/RISC-V project is providing support for running FreeBSD on the link:https://riscv.org[RISC-V Instruction Set Architecture].
+
+This quarter I resumed work on improvements to FreeBSD's RISC-V architecture support (riscv64).
+Work was focused primarily on small bug-fixes and improvements, and tooling.
+A handful of known panics and bug reports were fixed and closed.
+
+On the performance tooling side, some issues with the use of DTrace on riscv64 were found and addressed.
+Specifically, backtraces produced by the `stack()` function were not being captured correctly.
+First, a change was made to the compiler flags to ensure that kernel modules always make use of the frame pointer, so that unwinding the kernel stack works as expected.
+Second, some tweaks were made to machine-dependent DTrace code in the `profile` and `fbt` providers, making the correct number of frames appear in each backtrace.
+Now, DTrace can be used to accurately capture profiling data on this platform, enabling the generation of flamegraphs.
+
+I also began porting the `hwpmc(4)` driver to run on this platform.
+Unlike other ISAs, RISC-V does not standardize the set of counter events that a CPU must support, nor are the programmable event selection registers accessible to the kernel.
+To work around this, there is an link:https://github.com/riscv-non-isa/riscv-sbi-doc/blob/master/riscv-sbi.adoc#performance-monitoring-unit-extension-eid-0x504d55-pmu[SBI "Performance Monitoring Unit" extension] which provides an abstracted interface for managing such functionality.
+The new `hwpmc(4)` class is written to use this interface.
+Current generation RISC-V hardware supports incrementing performance counters, but lacks the counter overflow interrupts required to enable sampling PMCs.
+
+Work is expected to continue next quarter.
+Aside from the in-progress items mentioned, focus will be given to the following areas:
+
+* Support for newer OS-level extensions such as Page-Based Memory Types (Svpbmt)
+* Profiling system performance.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/status.adoc b/website/content/en/status/report-2022-10-2022-12/status.adoc
new file mode 100644
index 0000000000..dcc1682c0a
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/status.adoc
@@ -0,0 +1,61 @@
+=== Status reports: New workflow
+
+Links: +
+link:https://www.freebsd.org/status/[FreeBSD status reports] URL: link:https://www.freebsd.org/status/[https://www.freebsd.org/status/] +
+link:https://github.com/freebsd/freebsd-quarterly[Status reports GitHub repository] URL: link:https://github.com/freebsd/freebsd-quarterly[https://github.com/freebsd/freebsd-quarterly]
+
+Contact: <status@FreeBSD.org>
+
+==== Goals of the new workflow
+
+This quarter the status team has been discussing with doceng@ some improvements to its workflow.
+In particular, the team is attempting to merge its GitHub repository into the FreeBSD doc/ repository.
+
+Here are the reasons for such a change:
+
+* having two independent repositories requires spending some time to make sure that both are in sync, which is being done manually.
+See for example commits such as link:https://github.com/freebsd/freebsd-quarterly/commit/4b8255e604dd0513e841aa8f3dce7741e78b999c[https://github.com/freebsd/freebsd-quarterly/commit/4b8255e604dd0513e841aa8f3dce7741e78b999c], which are not immediately clear in their commit messages about what is being done unless more time is invested to copy commit messages properly;
+
+* the FreeBSD doc/ repository is self-hosted, while the status repository is hosted on GitHub.
+Since the contents of the self-hosted repository are mirrored, nothing is being lost in visibility with the repository merging.
+
+Some inconsistencies about the name of the team have also been found: the team has been referred to as "quarterly", "quarterly status team", "status", "status team", "monthly" etc.
+So this issue is also being addressed.
+
+Please note that we are still working on these changes and that they might not be completed within the next quarter.
+The status team will take care to keep all information about report submissions up to date so that you always know how to submit your reports.
+
+==== Team naming
+
+Since "quarterly" might refer to quarterly reports but also to quarterly branches, using "quarterly" only could cause some confusion in some contexts.
+"quarterly-status" is likely a bad idea as well, as the frequency of reports publication might need to change in the future.
+Thus just "status" has been chosen: this is correct as quarterly status reports contain information about the status of the development of FreeBSD, it is frequency-agnostic and consistent with link:https://www.freebsd.org/status/[its FreeBSD website section].
+
+The following link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267813[email addresses have been created]:
+
+* the main contact address for the status team is now <status@FreeBSD.org>.
+Mails sent to `quarterly@FreeBSD.org` will still reach the team, but you are encouraged to use the new address;
+* the email address for the status report submissions is now <status-submissions@FreeBSD.org>.
+Mails sent to `quarterly-submissions@FreeBSD.org` will still reach the team, but you are encouraged to use the new address;
+* the `quarterly-calls` mailing list has been renamed to link:https://lists.freebsd.org/subscription/freebsd-status-calls[status-calls].
+If you were already subscribed to `quarterly-calls`, you do not need to resubscribe.
+
+==== Report submission
+
+Three different ways to submit reports will be provided:
+
+* submitting a review on Phabricator.
+A new link:https://reviews.freebsd.org/project/profile/88/[Phabricator group] called "status" link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267812[has been created].
+If you would like to give a hand to the team by reviewing reports we suggest you add yourself to the group 'watchers';
+
+* submitting a pull request at link:https://github.com/freebsd/freebsd-doc/pulls[https://github.com/freebsd/freebsd-doc/pulls];
+
+* sending an email to `status-submissions@FreeBSD.org`.
+
+Reviewing processes will proceed as they usually do on each of these channels.
+
+==== Other changes
+
+* The repository merging will require reworking some of the existing tools to better integrate with the existent structure of the FreeBSD doc/ repository.
+
+* The link:https://github.com/freebsd/freebsd-quarterly[status reports GitHub repository] will be archived once the new workflow implementation is completed.
diff --git a/website/content/en/status/report-2022-10-2022-12/ufs_snapshots.adoc b/website/content/en/status/report-2022-10-2022-12/ufs_snapshots.adoc
new file mode 100644
index 0000000000..de625efb1d
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/ufs_snapshots.adoc
@@ -0,0 +1,40 @@
+=== Enabling Snapshots on Filesystems Using Journaled Soft Updates
+
+Links: +
+link:https://reviews.freebsd.org/D36491[Milestone 1 Core Changes] URL: link:https://reviews.freebsd.org/D36491[https://reviews.freebsd.org/D36491]
+
+Contact: Kirk McKusick <mckusick@FreeBSD.org>
+
+The goal of this project is to make UFS/FFS filesystem snapshots available when running with journaled soft updates.
+
+First a bit of background.
+Soft updates have been available for UFS/FFS since the mid 1990s.
+They eliminate the need for most synchronous disk writes and keep the state of the filesystem sufficiently consistent that it can be put back online after a crash without the need to run fsck(8).
+However, it may incorrectly assume that some of its blocks are still in use when in fact they are free.
+So, eventually it is necessary to take the filesystem offline to run fsck(8) to reclaim these lost blocks.
+The time to run fsck(8) is a function of the number of files in the filesystem and the size of the filesystem.
+Large filesystems may take hours to complete an fsck(8).
+
+Enabling journaling reduces the time spent by fsck(8) cleaning up a filesystem after a crash to a few seconds.
+With journaling, the time to recover after a crash is a function of the amount of activity in the filesystem in the minute before the crash.
+Journaled recovery time is usually only a few seconds and never exceeds a minute.
+
+The drawback to using journaling is that the writes to its log add an extra write load to the media containing the filesystem.
+Thus a write-intensive workload will have reduced throughput on a filesystem running with journaling.
+
+Like all journaling filesystems, the journal recovery will only fix issues known to the journal.
+Specifically if a media error occurs, the journal will not know about it and hence will not fix it.
+Thus when using journaling, it is still necessary to run a full fsck every few months or after a filesystem panic to check for and fix any errors brought on by media failure.
+
+A full fsck(8) is normally done on an offline filesystem.
+However, it can be done by running fsck(8) on a snapshot of a live filesystem.
+When running fsck(8) in the background on a live filesystem, the filesystem performance will be about half of normal during the time that the background fsck(8) is running.
+Running a full fsck on a UFS filesystem is the equivalent of running a scrub on a ZFS filesystem.
+
+The first milestone of this project has been completed.
+It is now possible to take snapshots when running with journaled soft updates and they can be used for doing background dumps on a live filesystem.
+
+The second milestone of this project is to extend fsck(8) to be able to do a background check using a snapshot on a filesystem running with journaled soft updates.
+This milestone is expected by Q3 of 2023.
+
+Sponsored by: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/vessel-status-report.adoc b/website/content/en/status/report-2022-10-2022-12/vessel-status-report.adoc
new file mode 100644
index 0000000000..653231a8fc
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/vessel-status-report.adoc
@@ -0,0 +1,40 @@
+=== Vessel - Integrated Application Containers for FreeBSD
+
+Links: +
+link:https://github.com/ssteidl/vessel[Vessel] URL: link:https://github.com/ssteidl/vessel[https://github.com/ssteidl/vessel]
+
+Contact: Shane Steidley <ssgriffonuser@gmail.com>
+
+==== What is Vessel?
+
+The goal of vessel is to expose the many powerful features of FreeBSD to application developers.
+Vessel accomplishes this goal by:
+
+* Providing a "Docker-like" interface familiar to most application developers for building, running, publishing and pulling container images.
+* Tightly integrating with FreeBSD system level interfaces (kqueue process tracing, signal handling, devd.seqpacket, rctl, cpuset) to manage running jails.
+
+==== How is Vessel different from other jail management systems?
+
+There are some awesome jail management systems already.
+These existing systems do a great job of configuring the jail runtime environment (ZFS dataset, networking, resource control, etc).
+After the environment is configured though, it is just handed off to the `jail` program via an exec call.
+
+In addition to jail configuration and creation, Vessel aims to take the next step and implement an event loop to manage jails based on system events.
+An instance of vessel runs alongside each jail to assist with management.
+This allows "Fat Jails" and single process jails to run in the foreground and be managed by the vessel-supervisor.
+
+==== Why make Vessel?
+
+Vessel has been a side project for a few years.
+I initially started it because it was a fun hobby project and I was surprised something similar did not already exist.
+It has now become a viable tool that I use for all of my projects.
+I believe it will be useful to others as well.
+
+==== Is help needed?
+
+Help is always appreciated.
+It's a fun project to work on because it can touch on so many portions of FreeBSD.
+
+* Just using it and reporting any bugs on GitHub would be very useful.
+* Whatever sounds fun.
+I'm happy to help get people started.
diff --git a/website/content/en/status/report-2022-10-2022-12/wifi.adoc b/website/content/en/status/report-2022-10-2022-12/wifi.adoc
new file mode 100644
index 0000000000..69267c8714
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/wifi.adoc
@@ -0,0 +1,34 @@
+=== Wireless updates
+
+Links: +
+link:https://people.freebsd.org/%7Ebz/wireless/[Bjoern's Wireless Work In Progress landing page] URL: link:https://people.freebsd.org/%7Ebz/wireless/[https://people.freebsd.org/~bz/wireless/] +
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+During the quarter not much work was publicly visible and admittedly slightly slow.
+Behind the scenes wireless work was happening on two fronts:
+
+ * 11n, 11ac, and wpa,
+
+ * more drivers and firmware, problems, testing, and filling gaps for these.
+
+While the main development for newer standards and the Intel iwlwifi driver is sponsored by the FreeBSD Foundation, I find myself spending a lot of private time with Realtek rtw88 and rtw89, Atheros, and Mediatek mt76 (7921 and 7915) drivers now as well.
+Testing changes on bare metal and using bhyve VMs using passthru has become more time-consuming, with the amount of supported chipsets increasing, in order not to break other drivers.
+Even different (generations of) chipsets supported by the same driver, at times, behave differently with the same change.
+
+A separate discussion was brought to me about the size of firmware added to the tree for the already existing drivers and the firmware for more drivers coming.
+The chicken-egg problem to solve is having firmware available on the release media; without firmware, a lot of modern laptops will not have any sort of outside communications available at the time of install in their default configuration.
+This will be a larger discussion to have to also solve firmware for other drivers, but that discussion will be for another day and place.
+
+Slightly belatedly I have started to push LinuxKPI and 802.11 changes into the tree at the end of the year and that work will continue into early 2023 at which point more of the aforementioned remaining drivers will also hit the tree.
+
+One of the main remaining problems to solve is the firmware crashes on interface down/up cycles currently experienced with at least two drivers.
+
+Thankfully during the last weeks, after my call for help, multiple people have stood up wanting to help with various drivers (especially Realtek and Mediatek).
+I hope that after me catching up and pushing things out this can accelerate progress again.
+
+Thanks again to everyone doing testing, providing debug output, sending in feedback, or using the drivers at this point.
+
+For the latest state of the development, please use the freebsd-wireless mailing list, and check the landing page, which has links to all wiki pages for each driver status.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-10-2022-12/xen.adoc b/website/content/en/status/report-2022-10-2022-12/xen.adoc
new file mode 100644
index 0000000000..3070e9b08c
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/xen.adoc
@@ -0,0 +1,36 @@
+=== FreeBSD/ARM64 on Xen
+
+Links: +
+link:https://www.xenproject.org/[Xen Project] URL: link:https://www.xenproject.org/[https://www.xenproject.org/] +
+link:https://wiki.freebsd.org/Xen[FreeBSD wiki page on Xen] URL: link:https://wiki.freebsd.org/Xen[https://wiki.freebsd.org/Xen]
+
+Contact: Elliott Mitchell <ehem+freebsd@m5p.com>
+
+Xen is an open source hypervisor.
+Xen is one of the earliest hypervisors and has support for many OSes.
+Since FreeBSD 8.0, GENERIC FreeBSD/x86 has been able to run on Xen.
+Near the time FreeBSD was ported to run on Xen, work was started on running Xen on ARM.
+For a number of years Linux has run fine on Xen/ARM, but FreeBSD hasn't been available.
+
+Having FreeBSD/ARM64 on Xen means any system capable of having Xen can also have FreeBSD in operation.
+Of note, the Raspberry PI 4B has hardware (GICv3) which Xen works with.
+If you're okay with Linux handling the hardware, you can use all the hardware of a Raspberry PI 4B.
+
+In 2014 a proof of concept of running FreeBSD/ARM64 on Xen was done by Julien Grall, but this was never polished for release.
+During the past 2 years I've been working towards having this in FreeBSD's tree, so released versions of FreeBSD/ARM64 would run on Xen.
+At this point all changes which need to be shared with the x86 Xen source code have been reviewed (not all reviews are on Phabricator).
+This now awaits testing by Roger Pau Monné before being committed to FreeBSD's tree.
+
+I now urgently need someone with a high level of familiarity with the interrupt subsystem of FreeBSD on ARM64 to review (and commit) the ARM-specific portions.
+My builds are functional far more often than they fail, and most failures are temporary problems in FreeBSD's tree.
+Some significant issues will need to be addressed regarding FreeBSD's interrupt subsystem.
+
+There is substantial hope of having FreeBSD/ARM64 available for "DomU" (unprivileged) operation for FreeBSD 14.0.
+There is potential for FreeBSD/ARM and FreeBSD/RISC-V to run on Xen in short order.
+No plans currently exist for having FreeBSD/ARM64 operating as the controlling VM (someone could try to sponsor this).
+
+==== Thanks
+
+Thanks to Julien Grall <julien@xen.org> for the Proof of Concept. +
+Thanks to Roger Pau Monné <royger@FreeBSD.org> for reviewing changes involving x86. +
+Thanks to Mitchell Horne <mhorne@FreeBSD.org> for helping with various FreeBSD/ARM64 issues and addressing a key problem with FreeBSD/ARM64.
diff --git a/website/content/en/status/report-2022-10-2022-12/xfce.adoc b/website/content/en/status/report-2022-10-2022-12/xfce.adoc
new file mode 100644
index 0000000000..5d011bcbda
--- /dev/null
+++ b/website/content/en/status/report-2022-10-2022-12/xfce.adoc
@@ -0,0 +1,18 @@
+=== Xfce on FreeBSD
+
+Links: +
+link:https://xfce.org/about/news/?post=1671062400[Xfce 4.18 Upstream Release Announcement] URL: link:https://xfce.org/about/news/?post=1671062400[https://xfce.org/about/news/?post=1671062400] +
+link:https://www.freshports.org/x11-wm/xfce4[Xfce meta-port on FreshPorts] URL: link:https://www.freshports.org/x11-wm/xfce4[https://www.freshports.org/x11-wm/xfce4]
+
+Contact: Xfce team <xfce@FreeBSD.org> +
+Contact: Guido Falsi <madpilot@FreeBSD.org>
+
+The FreeBSD Xfce team (xfce@) works to ensure the Xfce desktop environment is maintained and fully functional on FreeBSD.
+
+This quarter the Xfce team members are pleased to welcome Xfce 4.18 to the FreeBSD ports tree!
+
+This new release includes many improvements in various parts of the environment, especially in the Thunar file manager.
+
+Also various upstream packages now include patches that were present in the ports tree.
+
+For further details, refer to the link:https://xfce.org/about/news/?post=1671062400[Xfce 4.18 Upstream Release Announcement].
diff --git a/website/content/en/status/report-2023-01-2023-03/_index.adoc b/website/content/en/status/report-2023-01-2023-03/_index.adoc
new file mode 100644
index 0000000000..bf901affd9
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/_index.adoc
@@ -0,0 +1,163 @@
+---
+title: "FreeBSD Status Report First Quarter 2023"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2023-01-2023-03
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+include::{reports-path}/status.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+include::{reports-path}/daemon.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+include::{reports-path}/ufs_snapshots.adoc[]
+
+'''
+
+include::{reports-path}/kinst.adoc[]
+
+'''
+
+include::{reports-path}/timerfd.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+include::{reports-path}/aarch64-kasan.adoc[]
+
+'''
+
+include::{reports-path}/bsd-user.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+include::{reports-path}/cloud-init.adoc[]
+
+'''
+
+include::{reports-path}/openstack-on-freebsd.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+include::{reports-path}/frdp.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+include::{reports-path}/freshports.adoc[]
+
+'''
+
+include::{reports-path}/drm-drivers.adoc[]
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/fsx.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/valgrind.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+include::{reports-path}/pkgbase.live.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2023-01-2023-03/aarch64-kasan.adoc b/website/content/en/status/report-2023-01-2023-03/aarch64-kasan.adoc
new file mode 100644
index 0000000000..01b46dc37b
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/aarch64-kasan.adoc
@@ -0,0 +1,23 @@
+=== Kernel Address Sanitizer on AArch64
+
+Contact: Kyle Evans <kevans@FreeBSD.org>
+
+Sanitizers are bug detection facilities which use a combination of instrumentation inserted by the compiler (LLVM in this case) and runtime state tracking to detect bugs in C code.
+They can automatically detect many types of C programming bugs, such as use-after-frees and uses of uninitialized variables, which may otherwise require substantial effort to identify.
+They are particularly effective in combination with regression testing suites or fuzzing tools such as link:https://github.com/google/syzkaller[syzkaller].
+Unlike tools such as Valgrind, software must be recompiled to enable a given sanitizer, but sanitizers can be used in the kernel.
+Kernels with sanitizers enabled incur a significant performance overhead from the runtime, in both CPU utilization and memory usage.
+
+As of gitref:89c52f9d59fa[repository=src], the kernel address sanitizer that was previously exclusive to amd64 is ported to arm64.
+
+Prior testing has been done on a decent variety of machines, including:
+
+- Various Ampere Altra machines
+- QEMU
+- Microsoft's "Volterra" Devkit
+- bhyve (WIP).
+
+Further testing on other hardware would be both welcomed and appreciated.
+
+Sponsor: Juniper Networks, Inc. +
+Sponsor: Klara, Inc.
diff --git a/website/content/en/status/report-2023-01-2023-03/bsd-user.adoc b/website/content/en/status/report-2023-01-2023-03/bsd-user.adoc
new file mode 100644
index 0000000000..987183c59f
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/bsd-user.adoc
@@ -0,0 +1,55 @@
+=== bsd-user: Upstreaming and Status Report
+
+Links: +
+link:https://qemu.org[QEMU Project] URL: link:https://qemu.org[] +
+link:https://github.com/qemu-bsd-user/qemu-bsd-user[FreeBSD bsd-user qemu fork] URL: link:https://github.com/qemu-bsd-user/qemu-bsd-user[] +
+link:https://gitlab.com/qemu-project/qemu[QEMU Project's gitlab mirror] URL: link:https://gitlab.com/qemu-project/qemu[]
+
+Contact: Warner Losh <imp@FreeBSD.org>
+
+In this quarter, Warner upstreamed two patch sets in the qemu-project repo (with a third pending).
+Doug Rabson submitted some optimizations to save a handle to the qemu-user emulator in the kernel for future exec.
+Contact has been made with some folks interested in getting bsd-user working on NetBSD.
+Summer of Code project to upstream shows some interest.
+
+==== Upstreaming Efforts
+
+The sysctl system call was upstreamed this quarter.
+Doug's changes were also upstreamed (see below).
+Some cleanups around NetBSD and OpenBSD and to generate syscalls on the fly are pending.
+
+==== Doug Rabson's Changes
+
+As part of his container work, Doug submitted changes that allows the kernel to cache the emulator used to run programs.
+This allows the kernel to directly exec the new binary with that cached emulator.
+This simplifies bsd-user and removes one source of difference between it and linux-user.
+Doug also provided an important fix that prevented aarch64 from running.
+
+==== Bug Fixes and Improvements
+
+In addition to Doug's fixes, Warner cleaned up things a bit this quarter.
+
+* Warner removed the final bits of 'run on any BSD code' that was present in the emulator.
+* While the basic system calls could be emulated between all the BSDs, their system call interface has diverged too much, and it is too feature rich for this to be feasible any time soon.
+* Warner had planned to just remove the NetBSD and OpenBSD bits, but there is some interest from at least the NetBSD folks for making things build.
+* Now that the NetBSD folks have contact information, and know direction, Warner hopes they will submit a pull request to build bsd-user on NetBSD for NetBSD.
+* Warner added SIGSYS support so that we can catch unimplemented system calls sooner, and improved reporting of them to get more data about what fails.
+* Warner cleaned up some code in the `blitz` branch.
+* We're merged up to 8.0rc1 in upstream in the `blitz` branch we're using to stay current.
+
+==== Summer of Code Projects
+
+There's much interest in the bsd-user upstreaming task Warner added to Qemu's project list.
+With luck, we'll have a student to fund to do the job of upstreaming all the system calls needed to run simple programs.
+With a lot of luck, we'll be able to run any program that does the same thing(s) that clang does (one goal is to have it compile hello world).
+Future quarterly reports will provide details, should we be fortunate enough to get a slot for this.
+
+==== Help Needed
+
+We can always use help with bsd-user.
+
+* Pull requests for new system calls are welcome.
+* Automation in generating many of the things we do by hand would be helpful (like system call argument tracing).
+* Enthusiastic volunteers who want to help me with the upstreaming (many tasks are easy and quick if you don't want to commit).
+* Coordination with the NetBSD folks and cleanup they come up with.
+* Bug fixes (especially thread bugs) are needed.
diff --git a/website/content/en/status/report-2023-01-2023-03/ci.adoc b/website/content/en/status/report-2023-01-2023-03/ci.adoc
new file mode 100644
index 0000000000..10b9d26b2e
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/ci.adoc
@@ -0,0 +1,52 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the first quarter of 2023, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* link:https://ci.FreeBSD.org/job/FreeBSD-main-aarch64-KASAN_test/[FreeBSD-main-aarch64-KASAN_test] and its supporting jobs have been added.
+* link:https://ci.FreeBSD.org/job/FreeBSD-stable-13-amd64-KASAN_test/[FreeBSD-stable-13-amd64-KASAN_test] and its supporting jobs have been added.
+* link:https://ci.FreeBSD.org/job/FreeBSD-main-amd64-gcc12_build/[FreeBSD-main-amd64-gcc12_build] now sends failing reports to the committers whose commits may be related.
+* Various fixes or workarounds to the tests of non-x86 architectures from trasz@
+* Present Testing/CI Status Update in link:https://wiki.freebsd.org/DevSummit/202303[AsiaBSDCon 2023 Developer Summit]
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository
+* Improving the hardware test lab and adding more hardware for testing
+* Merge https://reviews.freebsd.org/D38815
+* Merge https://reviews.freebsd.org/D36257
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-01-2023-03/cloud-init.adoc b/website/content/en/status/report-2023-01-2023-03/cloud-init.adoc
new file mode 100644
index 0000000000..54683f6b46
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/cloud-init.adoc
@@ -0,0 +1,31 @@
+=== FreeBSD as a Tier 1 cloud-init Platform
+
+Links: +
+link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[] +
+link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[] +
+link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[]
+
+Contact: Mina Galić <freebsd@igalic.co>
+
+cloud-init is the standard way of provisioning servers in the cloud.
+Unfortunately, cloud-init support for operating systems other than Linux is rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform.
+To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support.
+The broader plan is to lift support across all BSDs.
+
+This quarter has been going very, very slowly, for personal reasons -- also for lack of access to the right resources.
+I have been trying to link:https://github.com/canonical/cloud-init/pull/2003[port the Infiniband functions].
+This has proven difficult, because it falsified my thesis that man:ifconfig[8] is all that is needed to figure out network interfaces on FreeBSD.
+
+While waiting for resources, I link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269767[debugged a boot panic] and got it fixed: gitref:499171a98c8813e4dc6e085461d5c47750efa555[repository=src].
+This now makes it possible to boot FreeBSD on LXD -- cloud-init's CI platform.
+We still need to fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269823[the high CPU usage problem], but there is already an accepted review: link:https://reviews.freebsd.org/D38898[D38898]
+
+A cloud-init colleague who works for Azure managed to give me access to an link:https://learn.microsoft.com/en-us/azure/architecture/topics/high-performance-computing[HPC VM on Azure].
+Unfortunately, it was only for a limited time, and that was not enough to figure out how to get Infiniband up and running on FreeBSD — a task handled by link:https://github.com/Azure/WALinuxAgent/[Azure Agent] on Linux, but FreeBSD's package:sysutils/azure-agent[] is rather lacking.
+
+People interested in helping with this project could provide man:ifconfig[8], man:ibstat[8], man:ibv_devinfo[1], etc… link:https://lists.freebsd.org/archives/freebsd-infiniband/2023-February/000005.html[pastes from their Infiniband systems].
+I would also be very happy about getting access to hardware with Infiniband NICs, or hearing from people who have successfully used FreeBSD on Azure HPC with Infiniband.
+
+If there is interest in that platform, I will direct some energy to fixing Azure Agent.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-01-2023-03/clusteradm.adoc b/website/content/en/status/report-2023-01-2023-03/clusteradm.adoc
new file mode 100644
index 0000000000..f10cc05ff6
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/clusteradm.adoc
@@ -0,0 +1,59 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular support for FreeBSD.org user accounts.
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* Improve the PowerPC package builders.
+** With new parts obtained through the FreeBSD Foundation, the builders now have new NVMEs with heatsinks and more memory.
+It helped to solve the heat issue, and they are building packages faster now.
+* Decouple dynamic resources from the main websites.
+** Work in coordination with doceng and webmaster to decouple dynamic resources from the websites, www.FreeBSD.org, and docs.FreeBSD.org.
+
+==== Work in progress
+
+* Large-scale network upgrade at our primary site.
+** New link:https://www.juniper.net/[Juniper] switches arrived at our primary site to replace the former ones.
+We thank Juniper for the donation.
+* Replace old servers in our primary site and a few mirrors.
+** Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs.
+This task is in conjunction with the FreeBSD Foundation and donors/sponsors.
+* Deploy infrastructure to mirror the websites.
+** Since the FreeBSD website is now mostly static, we have begun deploying infrastructure to mirror www.FreeBSD.org and docs.FreeBSD.org around the world in FreeBSD project-managed mirrors.
+* Create a new search database engine for internal FreeBSD.org searching needs like mailing list and docs.
+
+==== FreeBSD Official Mirrors Overview
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America -- California, New Jersey (primary site), and Washington.
+
+The hardware and network connection have been generously provided by:
+
+* https://www.bytemark.co.uk/[Bytemark Hosting]
+* Cloud and SDN Laboratory at https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc]
+* https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University]
+* https://deploy.equinix.com/[Equinix]
+* https://internet.asn.au/[Internet Association of Australia]
+* https://www.isc.org/[Internet Systems Consortium]
+* https://www.inx.net.za/[INX-ZA]
+* https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc]
+* https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network]
+* https://www.metapeer.com/[Metapeer]
+* https://www.nyi.net/[New York Internet]
+* https://nic.br/[NIC.br]
+* https://your.org/[Your.Org].
+
+The Frankfurt single server mirror is the primary Europe mirror in bandwidth and usage.
+
+We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site.
+
+We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch.
+United States (West Coast) and Europe (anywhere) are preferable places.
+
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site.
diff --git a/website/content/en/status/report-2023-01-2023-03/core.adoc b/website/content/en/status/report-2023-01-2023-03/core.adoc
new file mode 100644
index 0000000000..af73a27605
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/core.adoc
@@ -0,0 +1,26 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD. 
+
+==== Items
+
+===== Core Team Charter: Draft
+
+At the first Core Team meeting of 2023, Team delegates from the December 2022 meeting in Boulder, US presented the delegation's conclusions to the entire Team.
+The Team will continue to discuss the issues and work together with the FreeBSD Foundation.
+
+===== FreeBSD annual developers survey
+
+The Core Team together with the FreeBSD Foundation have decided that the FreeBSD Foundation will be in charge of conducting the annual developers survey.
+
+===== Matrix IM solution
+
+The Core Team continues to evaluate Matrix as an IM solution for FreeBSD developers.
+An instance has already been prepared and tests are underway.
+
+==== Commit bits
+
+* Core approved the src commit bit for Cheng Cui (cc@)
+* Core approved the restore of the src commit bit for Joseph Koshy (jkoshy@).
diff --git a/website/content/en/status/report-2023-01-2023-03/daemon.adoc b/website/content/en/status/report-2023-01-2023-03/daemon.adoc
new file mode 100644
index 0000000000..e941a5cb32
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/daemon.adoc
@@ -0,0 +1,27 @@
+=== daemon(8) improvements
+
+Links: +
+man:daemon[8] URL: link:https://man.freebsd.org/daemon/8[] +
+link:https://libera.chat/[Libera IRC] URL: link:https://libera.chat/[]
+
+Contact: Ihor Antonov <mailto:ihor@antonovs.family[]> +
+Contact: Kyle Evans <kevans@FreeBSD.org>
+
+An ongoing effort to improve code quality and supervision capabilities of the `daemon` utility.
+Daemon is a tool that can daemonize (send to background) or supervise any running process, automatically restarting it if it crashes.
+Daemon is widely used in the ports tree and can be used more in base.
+
+This quarter `long_opts` support was added and the codebase went through an initial refactoring phase to prepare it for further changes.
+There are no functional changes so far but more changes are coming.
+Please contact directly or on `#freebsd-dev` on Libera IRC if you encounter unexpected bugs.
+
+Planned work items for the next quarter:
+
+- use of kqueue for all event sources
+- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580[Bug #268580]
+- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236117[Bug #236117]
+- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254511[Bug #254511]
+- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212829[Bug #212829]
+- `procctl PROC_REAP_ACQUIRE`
+
+We are looking for feedback, bug reports (old and new) and feature requests.
diff --git a/website/content/en/status/report-2023-01-2023-03/doceng.adoc b/website/content/en/status/report-2023-01-2023-03/doceng.adoc
new file mode 100644
index 0000000000..3d565d37d7
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/doceng.adoc
@@ -0,0 +1,104 @@
+////
+Quarter:	1st quarter of 2023
+Prepared by:	fernape
+Reviewed by:	carlavilla@
+Last edit:	
+Version:	
+////
+
+=== Documentation Engineering Team
+
+Links: +
+link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[] +
+link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] +
+link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During the last quarter:
+
+* The doc commit bit for Pau Amma was taken in.
+* Lorenzo Salvadore has been proposed as doc committer. carlavilla@ and dbaio@ will mentor him.
+* Ryusuke SUZUKI steps down from doceng. doceng would like to thank ryusuke@ for his service.
+
+Items pending and in the discussion:
+
+* link:https://cgit.freebsd.org/doc/commit/?id=4c50528a8678246a6d01765acac8c395434b8c7e[A new document about licensing] has been added to the documentation set.
+
+==== Porter's Handbook:
+
+Three new `Uses` knobs have been added to the Handbook:
+
+* link:https://cgit.freebsd.org/doc/commit/?id=407dbb9254e7b6b379b8257f34f7732ed1afc71f[New Uses = ruby].
+* link:https://cgit.freebsd.org/doc/commit/?id=afa1a31005978bac63874fff8a1833f69a81dae3[New Uses = ldap].
+* link:https://cgit.freebsd.org/doc/commit/?id=689f1b026a02bf6d7039bdfec59353196d83ccef[New Uses = budgie].
+
+Also:
+
+ * link:https://cgit.freebsd.org/doc/commit/?id=9af61238fc24d4772b3c9e5fbd63fcaee2526699[The NVIDIA install and configure options have been fixed]
+ * link:https://cgit.freebsd.org/doc/commit/?id=3c6d3dea4a3ee60e7f0033afc9c5bf74e9ae1d31[The Advanced Networking chapter has been improved]
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance]
+
+===== Q4 2022 Status
+
+* 12 languages
+* 150 registered users
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 14%)
+* Chinese (Traditional) (zh-tw)	(progress: 11%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 10%)
+* Korean (ko)			(progress: 11%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 6%)
+* Portuguese (pt-br)		(progress: 29%)
+* Sinhala (si)			(progress: 1%)
+* Spanish (es)			(progress: 37%)
+* Turkish (tr)			(progress: 5%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+==== FreeBSD Handbook working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Chapters 1 to 6 have been updated.
+Chapter 7 is work in progress.
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Complete_)
+Public instance on https://man-dev.FreeBSD.org
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Work in progress_)
diff --git a/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc b/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc
new file mode 100644
index 0000000000..4f46a41f13
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc
@@ -0,0 +1,51 @@
+=== DRM drivers (i.e. GPU drivers)
+
+Links: +
+link:https://github.com/freebsd/drm-kmod[Git repository on GitHub] URL: link:https://github.com/freebsd/drm-kmod[] +
+
+Contact: Emmanuel Vadot <manu@FreeBSD.org> +
+Contact: Jean-Sébastien Pédron <dumbbell@FreeBSD.org> +
+Contact: The Graphics team <freebsd-x11@FreeBSD.org>
+
+GPUs are driven by DRM drivers.
+They are developed specifically for Linux using a permissive license.
+Our mission is to port those drivers to FreeBSD to make sure modern GPUs are fully supported.
+
+We didn't publish a report to share our progress for a long time.
+Therefore this status report entry will cover more than just the last quarter.
+
+==== Update to Linux 5.15 LTS and Linux 5.16
+
+As of this status report, the package:graphics/drm-kmod[] meta port still installs the DRM drivers from Linux 5.10 (released on December 13, 2020) on FreeBSD 13.1 and greater.
+This version of the driver lacks support for recent GPUs, in particular Intel 12th gen Alder Lake ones.
+In the past months, we worked to update the DRM drivers to bring support for more modern AMD and Intel GPUs.
+
+The `drm-kmod` Git repository `master` branch was first updated to Linux 5.15 (released on October 31, 2021).
+This is an LTS branch in Linux and we wanted to take advantage of that.
+Thus at that point, we followed two paths:
+
+* A `5.15-lts` branch was created to backport all bug fixes from Linux 5.15.x patch releases. This work is now available in the `drm-515-kmod` port.
+* The porting effort from subsequent Linux versions continued. The `master` branch is now at Linux 5.16 (release on January 9, 2022).
+
+The Intel driver from Linux 5.15 LTS supports 12th gen GPUs (Alder Lake).
+It looks to work on FreeBSD but we only tested it lightly so far.
+We still need more of that, that's why package:graphics/drm-kmod[] still installs package:graphics/drm-510-kmod[] instead of package:graphics/drm-515-kmod[].
+At last, FreeBSD should run as a desktop on this GPU generation and several new AMD GPUs, though problems will surely appear through real test and use.
+
+In the process, we updated firmwares to link:https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git[linux-firmware] 20230210.
+
+==== Linux 5.17 and future work
+
+DRM drivers from Linux 5.17 (released on March 20, 2022) were already ported but link:https://github.com/freebsd/drm-kmod/pull/236[this work still sits in its own branch].
+
+A couple of issues block further testing and the merge into the `master` branch:
+
+* Our current integration with man:vt[4], the console/terminal driver, is quite far from the DRM drivers expectations which are based on Linux' fbdev KPI. Something changed in both the Intel and AMD drivers, meaning that man:vt[4] breaks with the 5.17 update.
+* The initial Linux 5.17 release does not contain the fixes backported to Linux 5.15 LTS. It seems quite unstable with the Intel 12th gen GPU mentioned earlier.
+
+To address the issue with our man:vt[4] integration layer, we started to link:https://github.com/freebsd/drm-kmod/pull/243[write a new vt backend specifically to use the fbdev callbacks exposed by the DRM drivers].
+This backend will be provided with the DRM drivers, not the FreeBSD kernel, to make it easier to maintain as the drivers evolve.
+This is still a work in progress and locking in particular is tricky to get right.
+
+Regarding the bad support of Intel 12th gen in the 5.17 update, bug fixes backported to Linux 5.17.x patch releases will probably not be ported as part of this work.
+Instead we will focus on Linux 5.18 (released on May 22, 2022) and following.
diff --git a/website/content/en/status/report-2023-01-2023-03/frdp.adoc b/website/content/en/status/report-2023-01-2023-03/frdp.adoc
new file mode 100644
index 0000000000..69e64ceb15
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/frdp.adoc
@@ -0,0 +1,21 @@
+=== The FreeBSD Russian Documentation Project
+
+Links: +
+link:https://docs.freebsd.org/ru/books/faq/[FAQ] URL: link:https://docs.freebsd.org/ru/books/faq/[] +
+link:https://www.freebsd.org/ru/[Web] URL: link:https://www.freebsd.org/ru/[]
+
+Contact: Andrey Zakhvatov <andrey.zakhvatov@gmail.com>
+
+The FreeBSD Russian Documentation Project current goal is to provide up-to-date Russian translations of the most significant parts of FreeBSD documentation (FAQ, Handbook, Web).
+It is important to support Russian-speaking persons with high-quality official technical materials and increase acceptance of the operating system around the globe.
+We hope that this activity will receive some support within the Russian-speaking FreeBSD community and lead to an increased number of translated materials.
+
+FAQ translation was updated and synched with the latest original version.
+There is also a very slight progress with web pages updates.
+
+Check the link:https://docs.freebsd.org/en/books/fdp-primer/translations/[official translation guide] in case you are willing to help.
+We will appreciate your help with translation of the following materials:
+
+* Web pages (easy)
+* Handbook sections (only the X11 section is in progress right now)
+* Articles
diff --git a/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc b/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc
new file mode 100644
index 0000000000..60f88ce1d2
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc
@@ -0,0 +1,125 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[] +
+link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide.
+Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits.
+We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts.
+We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+==== Fundraising Efforts
+
+We finally have our 2022 fundraising numbers in and we raised a total of $1,231,096!
+We were short of our goal, which forced us to pull around $74,000 from our longer term investments.
+
+Besides receiving a lot of donations from you our users and contributors, we received larger donations from Juniper, Meta, Arm, Netflix, Beckhoff, Tarsnap, Modirum, Koum Family Foundation, and Stormshield.
+I’d like to extend a heartfelt thank you on behalf of the Foundation to everyone, including individuals and corporations, for your financial contributions in 2022!
+
+This year our budget is around $2,230,000, which includes increased spending towards FreeBSD advocacy and software development.
+More than half our budget is allocated towards work directly related to improving FreeBSD and keeping it secure.
+To fund the 2023 budget, we increased our fundraising goal and plan on using some of our investment money.
+When we received our first million dollar donation, the plan was to use up to 10% of it each year to increase our work to improve FreeBSD, so this has been part of our funding plan for a few years now.
+
+The 2023 budget is in the process of being approved by the board of directors and will be published once it is approved.
+
+This quarter we received donations from Juniper, Tarsnap, Microsoft, and Stormshield.
+So, we are already off to a great start!
+But, we definitely need more to support our planned efforts for 2023.
+
+If you want to help us continue our efforts, please consider making a donation towards our 2023 fundraising campaign!
+link:https://www.freebsdfoundation.org/donate/[]
+
+We also have a Partnership Program for larger commercial donors.
+You can read about it at link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[].
+
+==== OS Improvements
+
+During the first quarter of 2023, 226 src, 39 ports, and 12 doc tree commits identified the Foundation as a sponsor.
+Some of this sponsored work is described in separate report entries:
+
+* Continuous Integration
+* Enabling Snapshots on Filesystems Using Journaled Soft Updates
+* FreeBSD as a Tier 1 cloud-init Platform
+* FreeBSD Release Engineering Team
+* Improve the kinst DTrace provider
+* OpenStack on FreeBSD
+
+Other Foundation-sponsored work included:
+
+* OpenSSH fixes and updates to versions 9.2p1 and 9.3p1
+* a vendor import and update of libpcap to version 1.10.3
+* improvements to tmpfs, msdosfs, and makefs
+* the addition of a new kqueue1 syscall
+* man page updates
+* dtrace and bhyve fixes
+* LinuxKPI work
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project.
+You can read more about CI work in a dedicated report entry.
+A current project that is being funded by the FreeBSD Foundation is one to develop a set of scripts to help src developers conduct CI tests themselves.
+One of the main goals is to offer more visibility at the pre-commit stage.
+link:https://reviews.freebsd.org/D38815[A review for the first milestone] has been submitted.
+
+==== FreeBSD Advocacy and Education
+
+Much of our effort is dedicated to the FreeBSD Project advocacy.
+This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations.
+The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier.
+Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe.
+These events can be BSD-related, open source, or technology events geared towards underrepresented groups.
+We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.
+This all helps provide a healthy ecosystem.
+We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.
+We are back to attending events mostly in person and began planning the in person May 2023 Developer Summit, co-located with BSDCan.
+In addition to attending and planning events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD.
+
+Check out some of our advocacy and education work:
+
+* Hosted a stand at FOSDEM 2023, February 4-5, 2023 in Brussels, Belgium.
+Check out the link:https://freebsdfoundation.org/blog/fosdem-2023-conference-report/[trip report].
+* Hosted a table at State of Open Con 2023, February, 7-8, 2023, in London, England.
+link:https://freebsdfoundation.org/blog/advocating-for-freebsd-around-the-world/[Read more] about it.
+* Sponsored, held a workshop and hosted a booth at SCALE 20x, in March 9-12, 2023, Pasadena, California.
+Check out the link:https://freebsdfoundation.org/blog/freebsd-at-scale-20x/[trip report].
+* Sponsored Open Source 101, March 23 2023, in Charlotte, NC.
+* Sponsored and began planning the in-person link:https://wiki.freebsd.org/DevSummit/202305[May 2023 Developer Summit] taking place May 17-18, 2023 in Ottawa, Ontario
+* Secured our Media Partner sponsorship status and submitted a workshop for link:https://2023.allthingsopen.org/[All Things Open], October 15-17, 2023 in Raleigh, NC.
+* Submitted a Workshop proposal for link:https://sfconservancy.org/fossy/[FOSSY], July 13-16, 2023, in Portland, OR.
+* The FreeBSD Project was accepted as a link:https://summerofcode.withgoogle.com/programs/2023/organizations/the-freebsd-project[Participating Organization] for Google Summer of Code.
+* We held link:https://youtu.be/NpOkTR_d8os[GSoC Office Hours] to help prospective participants with questions.
+* Published link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-march-2023/[March Newsletter]
+
+* Additional Blog Posts
+
+** link:https://freebsdfoundation.org/blog/under-the-hood-with-freebsd-and-ampere-altra/[Under the Hood with FreeBSD and Ampere Altra]
+** link:https://freebsdfoundation.org/blog/under-the-hood-with-freebsd-and-ampere-altra/[New Open Position: FreeBSD Userland Software Developer] - Note: Posting is closed.
+** link:https://freebsdfoundation.org/blog/bsdcan-2023-travel-grant-application-now-open/[BSDCan 2023 Travel Grant Application Now Open] - Note: Applications are closed
+
+* FreeBSD in the News:
+
+** link:https://freebsdfoundation.org/news-and-events/latest-news/vmblog-state-of-open-con-qa-with-deb-goodkin/[VMBlog State of Open Con Q&A with Deb Goodkin]
+
+We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal.
+As we mentioned previously, the FreeBSD Journal is now a free publication.
+Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[].
+
+You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[].
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://www.freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2023-01-2023-03/freshports.adoc b/website/content/en/status/report-2023-01-2023-03/freshports.adoc
new file mode 100644
index 0000000000..4cf385c706
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/freshports.adoc
@@ -0,0 +1,49 @@
+=== Freshports: SQL Injection Attack and Help Request
+
+Links: +
+link:https://freshports..org[FreshPorts] URL: link:freshports.org[] +
+link:https://news.freshports.org/[FreshPorts blog] URL: link:https://news.freshports.org/[]
+
+Contact: Dan Langille <dvl@FreeBSD.org>
+
+FreshPorts and FreshSource have reported upon FreeBSD commits for 20 years.
+They cover all commits, not just ports.
+
+FreshPorts tracks the commits and extracts data from the port Makefiles to create a database of information useful to both port maintainers and port users.
+
+For example, link:https://www.freshports.org/security/acme.sh/[] shows the history of the package:security/acme.sh[] port, back to its creation in May 2017.
+Also available are dependencies, flavors, configuration options, and available packages.
+All of this is useful for both users and developers of ports.
+
+==== SQL Injection Attack
+
+In March, an SQL injection attack was noticed and the website was patched.
+Notices were sent out via our Twitter account, our status page, and a notice on the top of each page of the website.
+The immediate attack vector was shutdown and soon patched.
+Additional preventative patches were added across the website.
+Everything we know about has been fixed.
+Users were notified and advised to change their passwords.
+
+Details at:
+
+* link:https://news.freshports.org/2023/03/24/sql-inejection-issues-fixed/[]
+* link:https://news.freshports.org/2023/03/24/freshsource-code-fixes/[]
+
+==== Help Needed
+
+It has been over 22 years since FreshPorts started.
+Others must take over eventually.
+I’d like to start that process now.
+There are several aspects to FreshPorts:
+
+* FreeBSD admin (updating the OS and packages)
+* front end code (website - mostly PHP)
+* back end code (commit processing - Perl, Python, shell)
+* database design (PostgreSQL).
+
+The database does not change very often and requires little maintenance compared to the applications and OS.
+The website pretty much runs itself.
+From time to time, a change to the FreeBSD ports infrastructure breaks something or requires a modification, but there is rarely any urgency to fix that.
+This is not a huge time commitment.
+There is a lot of learning.
+While not a complex application, FreshPorts is also not trivial.
diff --git a/website/content/en/status/report-2023-01-2023-03/fsx.adoc b/website/content/en/status/report-2023-01-2023-03/fsx.adoc
new file mode 100644
index 0000000000..def3b68468
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/fsx.adoc
@@ -0,0 +1,18 @@
+=== FSX
+
+Links: +
+link:https://github.com/asomers/fsx-rs[GitHub] URL: https://github.com/asomers/fsx-rs[]
+link:https://www.freshports.org/devel/fsx/[FreshPorts] URL: https://www.freshports.org/devel/fsx/[]
+
+Contact: Alan Somers <asomers@freebsd.org>
+
+The venerable FSX (File System eXerciser) tool, first written at Apple Computer in the nineties, has been a part of FreeBSD since 5.0.
+It stress tests file systems with a stream of randomly generated operations, verifying file data after every read.
+However, it has never been installed as part of the OS; it only exists in the source tree.
+That makes it difficult to use in CI pipelines.
+It has some other limitations, too.
+
+So this quarter I rewrote the entire tool in Rust.
+The rewrite is byte-for-byte compatible with the original, given identical seed values.
+Future versions will break backwards-compatibility, however, in order to add new features like `fspacectl` and `copy_file_range`.
+The new version can be found in the ports tree, and in time I'll remove the original.
diff --git a/website/content/en/status/report-2023-01-2023-03/gcc.adoc b/website/content/en/status/report-2023-01-2023-03/gcc.adoc
new file mode 100644
index 0000000000..f5936fef0f
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/gcc.adoc
@@ -0,0 +1,24 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[]
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> +
+Contact: Gerald Pfeifer <gerald@pfeifer.com>
+
+The main news this quarter is the cleaning of old GCC versions from the ports tree: this will allow for a more efficient approach to bugs.
+
+==== Deprecation of old GCC ports
+
+The ports tree still contains several ports related to old and unsupported GCC versions.
+They are usually needed as dependencies for a few old ports, that it would be better to either update to use a supported GCC release, or deprecate.
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269644[Bug reports] have been created to track the issue and work has already started towards its resolution.
+Thanks to all ports contributors who are helping.
+
+==== Deprecation of USE_GCC=X+
+
+Gerald, who maintained the GCC ports for many years until recently, still contributes to the GCC maintenance on FreeBSD by helping simplify the GCC infrastructure in the ports tree, for example by removing special cases that deal with old unsupported GCC versions.
+
+This quarter the most significant of his changes is probably link:https://cgit.freebsd.org/ports/commit/?id=9b5f5ab8482f105311d01a32260ef32bba4a2628[the removal of support for the `USE_GCC=X+` construct]: any port depending on GCC should set `USE_GCC=yes` if `GCC_DEFAULT` works; if not, it should require a specific version (e.g. `USE_GCC=11`); it cannot ask for a minimal version anymore (e.g. `USE_GCC=11+`).
diff --git a/website/content/en/status/report-2023-01-2023-03/intro.adoc b/website/content/en/status/report-2023-01-2023-03/intro.adoc
new file mode 100644
index 0000000000..1e233aca94
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/intro.adoc
@@ -0,0 +1,8 @@
+Here is the first status report of 2023, including 25 reports: we have our usual team reports, some news about cloud projects, progress in the src, ports and doc trees and more.
+
+We also provide some information about link:../../releases/13.2R/announce/[13.2-RELEASE], which was postponed to the beginning of 2023Q2; but since this report is being published after the new version release, it is already available for installation.
+Users of RELEASE versions can now take advantage of many improvements such as better support for the man:iwlwifi[4] driver or the new man:rtw88[4] driver, topics that have been covered in past status reports.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the status team.
diff --git a/website/content/en/status/report-2023-01-2023-03/kde.adoc b/website/content/en/status/report-2023-01-2023-03/kde.adoc
new file mode 100644
index 0000000000..18ef0b3a7b
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/kde.adoc
@@ -0,0 +1,52 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[] +
+link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL:link:https://community.kde.org/FreeBSD[]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine.
+The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack.
+
+==== Infrastructure
+
+* The Qt5 ports were updated to the KDE patch collection release 5.15.8.
+* The Qt6 ports -- these are not used by KDE yet, but there are many ports that can use Qt6 and have Qt6 flavors -- were updated to release 6.4.2.
+Python bindings for the Qt6 release of WebEngine were added.
+* The cmake ports were updated to release 3.25.1 and the CPack generator for FreeBSD packages was repaired.
+* The package:graphics/poppler[] port -- used by many PDF-viewers -- was updated to release 23.01.
+* The package:sysutils/bsdisks[] port -- used as a shim for applications that expect Linux udisks, which means most desktop environments -- was updated to release 0.29.
+
+==== KDE Stack
+
+KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well.
+These (large) updates land shortly after their upstream release and are not listed separately.
+
+* KDE Frameworks updated to 5.104.
+* KDE Gear updated to 22.12.3.
+* KDE Plasma Desktop was updated to version 5.27.
+This was a long delayed update, due to unresolved issues in the support stack and a misplaced patch from an earlier release of KDE Plasma.
+Thanks to arrowd@ and Serenity Cybersecurity, LLC for sorting that out.
+* New port package:devel/ktextaddons[] was added to the tree.
+This is part of the KDE PIM suite, and slated to become a new KDE Framework in some future release.
+
+==== Related Ports
+
+* package:audio/amarok[], one of the most popular KDE audio players of the early 2000's, has been marked deprecated in the ports tree.
+It is no longer maintained upstream.
+* package:astro/kstars[], an interactive planetarium, was updated to release 3.6.3.
+* package:devel/gitqlient[], a graphical user interface for git, was updated to release 1.6.1 with support for new git commands.
+* package:devel/okteta[], a hex viewer and editor for binary files, was updated to release 0.26.10.
+* package:devel/qcoro[], C++ coroutines with Qt support, was updated to release 0.8.0.
+* package:graphics/krita[], an application for painting and graphical work, was updated to release 5.1.5.
+* package:graphics/quickqanava[], a graph visualization library, got a real release and an update in the ports tree.
+* package:irc/kvirc[], an IRC client, was updated to the latest commit; there is no real release but there are bugfixes.
+* package:multimedia/haruna[], a video and audio player, was updated to release 0.10.3.
+* package:net-im/neochat[], one of a handful of Matrix clients, was updated to chase a new release of package:net-im/libquotient[].
+There are continuing troubles with compatibility with older FreeBSD releases, leading to the KDE-FreeBSD team to declare FreeBSD 12 releases "effectively unsupported".
+* package:net-im/ruqola[], a Rocket Chat client, was updated to release 1.9.1.
+* package:security/keysmith[], a two-factor-authentication support application, was updated to release 23.01.0.
diff --git a/website/content/en/status/report-2023-01-2023-03/kinst.adoc b/website/content/en/status/report-2023-01-2023-03/kinst.adoc
new file mode 100644
index 0000000000..9320736896
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/kinst.adoc
@@ -0,0 +1,66 @@
+=== Improve the kinst DTrace provider
+
+Links: +
+link:https://reviews.freebsd.org/D38825[libdtrace: implement inline function tracing] URL: link:https://reviews.freebsd.org/D38825[] +
+link:https://reviews.freebsd.org/D38732[dtrace(1): add -d flag to dump D script post-dt_sugar] URL: link:https://reviews.freebsd.org/D38732[]
+
+Contact: Christos Margiolis <christos@FreeBSD.org> +
+Contact: Mark Johnston <markj@FreeBSD.org>
+
+kinst is a new DTrace provider created by christos@ and markj@ that allows for arbitrary instruction tracing in a kernel function.
+kinst has been added to the base system in FreeBSD 14.0.
+
+link:../report-2022-07-2022-09/#_dtrace_instruction_level_dynamic_tracing[The 2022Q3 status report gives a brief introduction to kinst.]
+We're now working on inline function tracing (see review D38825 above) -- a much-requested DTrace feature -- by using kernel DWARF and ELF info to find the call sites of each inline copy and use that information to transform D syntax by turning kinst probes of the form:
+
+....
+	kinst::<inline_func>:<entry/return>
+	/<pred>/
+	{
+		<acts>
+	}
+....
+
+To:
+
+....
+	kinst::<caller_func1>:<offset>,
+	kinst::<caller_func2>:<offset>,
+	kinst::<caller_func3>:<offset>
+	/<pred>/
+	{
+		<acts>
+	}
+....
+
+For example:
+
+....
+	# dtrace -dn 'kinst::cam_iosched_has_more_trim:entry { printf("\t%d\t%s", pid, execname); }'
+	kinst::cam_iosched_get_trim:13,
+	kinst::cam_iosched_next_bio:13,
+	kinst::cam_iosched_schedule:40
+	{
+		printf("\t%d\t%s", pid, execname);
+	}
+
+	dtrace: description 'kinst::cam_iosched_has_more_trim:entry ' matched 3 probes
+	CPU     ID                    FUNCTION:NAME
+	  2  79315          cam_iosched_next_bio:13     0       kernel
+	  2  79316          cam_iosched_schedule:40     0       kernel
+	  0  79316          cam_iosched_schedule:40     12      intr
+	  2  79315          cam_iosched_next_bio:13     0       kernel
+	  2  79316          cam_iosched_schedule:40     0       kernel
+	  0  79316          cam_iosched_schedule:40     12      intr
+	^C
+....
+
+A new `-d` flag has also been added to man:dtrace[1] which dumps the D script after libdtrace has applied syntactic transformations.
+
+Further goals include:
+
+* Implement a `locals` structure in D which stores the local variables of the traced function.
+  For example with `kinst::foo:<x>`, we could print the local variable `bar` by doing `print(locals->bar)` inside a D script.
+* Port kinst to riscv and/or arm64.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-01-2023-03/openstack-on-freebsd.adoc b/website/content/en/status/report-2023-01-2023-03/openstack-on-freebsd.adoc
new file mode 100644
index 0000000000..b59cf6731d
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/openstack-on-freebsd.adoc
@@ -0,0 +1,37 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] +
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+This project aims to port key OpenStack components so that FreeBSD can function as an OpenStack host.
+
+In 2023 Q1, the big news is that we're able to spawn FreeBSD instances with man:bhyve[8] on the OpenStack platform.
+But there are still some major limitations regarding the capabilities of the spawned instances that need to be resolved:
+
+* No self-service networks (only support the flat network)
+* No network connectivity inside the instance
+* Only support FreeBSD raw images (`FreeBSD-13.1-RELEASE-amd64.raw` tested)
+* No disk resize
+* No console integration (need to use man:cu[1] command manually)
+
+The step-by-step documents for constructing a POC site can be found link:https://github.com/openstack-on-freebsd/docs[in the `docs` repository].
+The patched version of each OpenStack component is under the same GitHub organization.
+
+Also, we attended AsiaBSDCon 2023 at the end of March and gave a short talk about the current project status at the developer summit.
+We got precious feedback at the event and will focus on the following for the next quarter:
+
+* Resolve the Open vSwitch networking issue
+* Convert each OpenStack component into FreeBSD ports
+
+People interested in helping with the project can first help check the documentation by following the installation guide.
+And here is an open task for the project:
+
+* FreeBSD-specific implementation for the oslo.privsep library
+
+Feedback and help are always welcome.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc b/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc
new file mode 100644
index 0000000000..d06ac09bf3
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc
@@ -0,0 +1,24 @@
+=== PkgBase.live
+
+Links: +
+link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/[Website (archive.org)] URL: link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/[] +
+link:https://codeberg.org/pkgbase/website[Website source] URL: link:https://codeberg.org/pkgbase/website[]
+
+Contact: Mina Galić <freebsd@igalic.co>
+
+PkgBase.live _was_ an unofficial repository for the FreeBSD link:https://wiki.freebsd.org/PkgBase[PkgBase project].
+As a service, PkgBase.live was inspired by link:https://up.bsd.lv/[], which provides man:freebsd-update[8] for STABLE and CURRENT branches.
+
+Hardware for PkgBase was kindly sponsored by a member of the FreeBSD community.
+However, as life and projects moved on, they had to decommission the hardware, giving me three months' notice.
+In that time, my own life was rather turbulent after a recent move to a different country so I haven't been able to find a replacement.
+
+For the time being, PkgBase.live is dead.
+
+The website, and with it the link:https://codeberg.org/pkgbase/website/src/branch/main/howto/howdo.md[How Did She Do it?!] are still available in link:https://codeberg.org/pkgbase/website[Git].
+I highly encourage copy-cats.
+
+I will also happily accept a new hardware sponsor!
+
+Please note that I _have_ contacted the FreeBSD Project, and they _are_ working on integrating PkgBase into release engineering.
+However, they are not yet ready, they also cannot "simply" take over PkgBase.live because it uses a completely different process.
diff --git a/website/content/en/status/report-2023-01-2023-03/portmgr.adoc b/website/content/en/status/report-2023-01-2023-03/portmgr.adoc
new file mode 100644
index 0000000000..3859809186
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/portmgr.adoc
@@ -0,0 +1,37 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL: link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages (through its subsidiary pkgmgr), and personnel matters.
+Below is what happened in this quarter.
+
+Currently we have around 33,500 ports in the tree.
+For these ports, there are 3,021 open problem reports, of which 764 are unassigned.
+The first three months of this year saw 9,021 commits by 163 committers for the `main` branch and 701 commits by 55 committers for the `2023Q1` branch.
+Compared to `2022Q4`, this means a slight increase in the number of ports, port PRs, ports commits, and active port committers.
+
+During this quarter, we welcomed Robert Clausecker (fuz@), Vladimir Druzenko (vvd@), Robert Nagy (rnagy@), welcomed back Norikatsu Shigemura (nork@), and said goodbye to Marius Strobl (marius@).
+Portgmr added Muhammad Moinur Rahman (bofh@) as a new member after a successful lurkership.
+
+During the bi-weekly portmgr meetings, the following topics were discussed:
+
+* improving the situation of binary packages for kernel modules
+* ways to measure the impact of ports on their dependencies and how to maintain high-impact ports.
+
+During this quarter, 32 exp-runs were run to test port updates, updating default versions (LLVM to 15, MySQL to 8.0, Ruby to 3.1), and updating byacc in base.
+Furthermore, the default version of Go switched to 1.20 and that of Lazarus to 2.2.6.
+
+Four new USES were introduced:
+
+* `budgie` to support ports related to the Budgie Desktop
+* `ldap` to provide support for OpenLDAP, with a new default version of 26 (i.e. 2.6)
+* `nextcloud` to support Nextcloud applications
+* `ruby` to provide support for Ruby ports (formerly `bsd.ruby.mk`).
diff --git a/website/content/en/status/report-2023-01-2023-03/pot.adoc b/website/content/en/status/report-2023-01-2023-03/pot.adoc
new file mode 100644
index 0000000000..951eb14541
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/pot.adoc
@@ -0,0 +1,20 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@freebsd.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+During the last quarter, link:https://github.com/bsdpot/pot/commits/master[pot] received a number of minor fixes but no new version has been released yet.
+
+Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: a repository of pot flavours and complete container images for usage with pot and in many cases Nomad.
+
+All Potluck images have been rebuilt to include the latest FreeBSD security advisories, a new link:https://github.com/bsdpot/potluck/tree/master/smokeping[Smokeping network latency monitoring image has been added], again a lot of work went into the link:https://github.com/bsdpot/potluck/tree/master/jitsi-meet[Jitsi] image, which unfortunately still seems to have some reliability issues.
+
+Also, two new blog posts are available showing how easy it is to use Potluck images, link:https://honeyguide.eu/posts/minio-beast-nextcloud/[one explaining how to set up Nextcloud with Minio as object storage and Prometheus for monitoring], link:https://honeyguide.eu/posts/openldap-matrix-blog-post/[one showing how to run your own Matrix Synapse server using OpenLDAP for access management].
+
+As always, feedback and patches are welcome.
diff --git a/website/content/en/status/report-2023-01-2023-03/releng.adoc b/website/content/en/status/report-2023-01-2023-03/releng.adoc
new file mode 100644
index 0000000000..c0ba1045cf
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/releng.adoc
@@ -0,0 +1,20 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[] +
+link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the first quarter of 2023, the Release Engineering Team started work on the upcoming 13.2-RELEASE.
+As of this writing, the 13.2 cycle has followed the originally set schedule, with the addition of fourth, fifth and sixth RC builds, postponing the final release from the end of March to early April.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/13*, and *stable/12* branches.
+
+Sponsor: Rubicon Communications, LLC ("Netgate") +
+Sponsor: Tarsnap +
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-01-2023-03/status.adoc b/website/content/en/status/report-2023-01-2023-03/status.adoc
new file mode 100644
index 0000000000..361e73e617
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/status.adoc
@@ -0,0 +1,43 @@
+=== Status Team
+
+Links: +
+link:https://www.freebsd.org/status/[FreeBSD status reports] URL: link:https://www.freebsd.org/status/[] +
+link:https://docs.freebsd.org/en/articles/freebsd-status-report-process/[FreeBSD Status Report Process] URL: https://docs.freebsd.org/en/articles/freebsd-status-report-process/[] +
+link:https://github.com/freebsd/freebsd-quarterly[Archived status reports GitHub repository] URL: link:https://github.com/freebsd/freebsd-quarterly[]
+
+Contact: <status@FreeBSD.org>
+
+==== The new workflow has started
+
+In the first quarter of this year, the link:https://reviews.freebsd.org/project/profile/88/[status team] has started implementing the new workflow that was announced at the end of 2022.
+Here are some details.
+
+==== New email addresses
+
+Last quarter we have announced the creation of new email addresses:
+
+- <status@FreeBSD.org>, for interacting with the _status_ team directly;
+- <status-submissions@FreeBSD.org, for sending reports submissions;
+- <freebsd-status-calls@FreeBSD.org>, a mailing list to which you can link:https://lists.freebsd.org/subscription/freebsd-status-calls[subscribe] to get reminders about status report submission deadlines.
+
+Unfortunately, the mailing list does not work as expected at the moment.
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269893[The issue has been reported] but no solution could be found yet.
+However, a work around allowed to send the second and the last reminder to the link:https://lists.freebsd.org/archives/freebsd-status-calls/2023-March/[list].
+
+==== Automation
+
+Some automation has been introduced to ensure that no report submission is lost:
+
+- on Phabricator a link:https://reviews.freebsd.org/H166[herald rule] automatically blocks any review touching the status reports directory: even if a report submitter forgets to add the _status_ team as reviewer, salvadore@ (member of the _status_ team) will block the patch anyway.
+The same rule will also block any review that includes the _status_ team as reviewer, to ensure that at least one member of _status_ has reviewed the patch before commit.
+- a link:https://github.com/freebsd/freebsd-doc/blob/main/.github/workflows/label-pull-requests.yml[GitHub action] automatically adds the newly introduced link:https://github.com/freebsd/freebsd-doc/pulls?q=label%3A%22status+report%22[status report] label to any pull request touching the status reports directory.
+The GitHub action should be easily modifiable by anyone wanting to apply more labels automatically depending on the path of the modified files.
+
+More automation is planned.
+
+==== Documentation reorganization
+
+The status report link:https://cgit.freebsd.org/doc/diff/website/content/en/status/README?id=7cd49b34af842b2cf247c944b7d8bc3c1bef8fc8[README] and link:https://cgit.freebsd.org/doc/diff/website/content/en/status/howto/_index.adoc?id=7cd49b34af842b2cf247c944b7d8bc3c1bef8fc8[How To] have been updated and merged in one unique document: the link:https://docs.freebsd.org/en/articles/freebsd-status-report-process/[FreeBSD status report process].
+You can check it out to read details about reports submission and publication.
+It will be updated regularly as the status team proceeds with the implementation of its new workflow.
+In particular, new material about automation is coming soon.
diff --git a/website/content/en/status/report-2023-01-2023-03/timerfd.adoc b/website/content/en/status/report-2023-01-2023-03/timerfd.adoc
new file mode 100644
index 0000000000..b6d9ec7ee6
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/timerfd.adoc
@@ -0,0 +1,20 @@
+=== Native Linux timerfd
+
+Links: +
+link:https://reviews.freebsd.org/D38459[Differential revision] URL: link:https://reviews.freebsd.org/D38459[]
+
+Contact: Jake Freeland <jfree@FreeBSD.org>
+
+The timerfd facility is a set of Linux-standard system calls that operate on interval timers.
+These timers are analogous to per-process timers but are represented by a file descriptor, rather than a process.
+These file descriptors may be passed to other processes, are preserved across man:fork[2], and may be monitored via man:kevent[2], man:poll[2], or man:select[2].
+
+A timerfd implementation in FreeBSD already exists for Linux compatibility, but link:https://reviews.freebsd.org/D38459[this differential revision] makes the interface native.
+The goal behind this change is to ease the FreeBSD porting process for programs that include timerfd.
+
+This specific implementation avoids adding new names to the system call table.
+Instead, `timerfd_create()` is wrapped by the `specialfd()` system call.
+The `timerfd_gettime() and `timerfd_settime()` calls are wrapped `ioctl()` s.
+
+Developers that wish to support FreeBSD should avoid using timerfd.
+The `kqueue()` `EVFILT_TIMER` filter is preferred for establishing arbitrary timers.
diff --git a/website/content/en/status/report-2023-01-2023-03/ufs_snapshots.adoc b/website/content/en/status/report-2023-01-2023-03/ufs_snapshots.adoc
new file mode 100644
index 0000000000..fab82ef0dd
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/ufs_snapshots.adoc
@@ -0,0 +1,13 @@
+=== Enabling Snapshots on Filesystems Using Journaled Soft Updates in 13.2
+
+Contact: Marshall Kirk McKusick <mckusick@freebsd.org>
+
+The ability to make UFS/FFS filesystem snapshots when running with journaled soft updates, and using them for doing background dumps on a live filesystem, was merged to `releng/13.2` during the first quarter of 2023, and lands in FreeBSD 13.2-RELEASE.
+
+Background dumps are requested by using the `-L` flag to man:dump[8].
+
+The details of this project were
+link:../report-2022-10-2022-12/#_enabling_snapshots_on_filesystems_using_journaled_soft_updates[described
+in the 2022 fourth quarter report].
+
+Sponsored by: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-01-2023-03/valgrind.adoc b/website/content/en/status/report-2023-01-2023-03/valgrind.adoc
new file mode 100644
index 0000000000..f3aa176ee4
--- /dev/null
+++ b/website/content/en/status/report-2023-01-2023-03/valgrind.adoc
@@ -0,0 +1,29 @@
+=== Valgrind - Preparing for Valgrind 3.21
+
+Links: +
+link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] +
+link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[]
+
+Contact: Paul Floyd <pjfloyd@wanadoo.fr>
+
+The package:devel/valgrind-devel[] port had an intermediate update which was submitted on 2023-02-20.
+This contains most of what will be in the official release of Valgrind 3.21 which is due out shortly after this status report.
+
+There is a nice improvement to the vgdb interface.
+It's now much easier to see which bits of memory are initialized or not.
+There are a couple of fixes to the thread checks done by Helgrind.
+
+For FreeBSD specifically, the address space limit has been raised to be the same as Linux and Solaris on amd64.
+It was 32Gbytes and now it is 128Gbytes.
+The `kern.proc.pathname.PID` man:sysctl[3] has been fixed so that it returns the path of the guest exe and not that of the Valgrind host.
+At the same time I fixed some `_umtx_op` false positives and corrected auxv `AT_EXECPATH` in a way similar to `kern.proc.pathname.PID`.
+Syscall wrappers have been added for man:sctp_generic_sendmsg[2] and man:sctp_generic_recvmsg[2].
+
+Not yet available in the ports versions of Valgrind, there is a workaround for the use of man:rfork[2].
+Previously, since it is not supported, it would cause Valgrind to abort.
+Now it fails gracefully setting either EINVAL or ENOSYS.
+The main use of this system call is in man:posix_spawn[3], which will fall back to using man:vfork[2].
+
+The man:mknodat[2] syscall wrapper was incorrectly implemented on i386 and has now been fixed.
+
+There is a reworking of all of the aligned allocation functions so that they behave less like Linux glibc and more like the Valgrind build platform.
diff --git a/website/content/en/status/report-2023-04-2023-06/_index.adoc b/website/content/en/status/report-2023-04-2023-06/_index.adoc
new file mode 100644
index 0000000000..70a11b6038
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/_index.adoc
@@ -0,0 +1,234 @@
+---
+title: "FreeBSD Status Report Second Quarter 2023"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2023-04-2023-06
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+'''
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+{projects-desc}
+
+'''
+
+include::{reports-path}/cirrus.adoc[]
+
+'''
+
+include::{reports-path}/batman.adoc[]
+
+'''
+
+include::{reports-path}/kboot.adoc[]
+
+'''
+
+include::{reports-path}/lldb-kmod.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+'''
+
+include::{reports-path}/openssl3.adoc[]
+
+'''
+
+include::{reports-path}/linuxulator.adoc[]
+
+'''
+
+include::{reports-path}/service-jails.adoc[]
+
+'''
+
+include::{reports-path}/capsicum-ktracing.adoc[]
+
+'''
+
+include::{reports-path}/nvmf.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+'''
+
+include::{reports-path}/boot-performance.adoc[]
+
+'''
+
+include::{reports-path}/ci-bootloader.adoc[]
+
+'''
+
+include::{reports-path}/compaction.adoc[]
+
+'''
+
+include::{reports-path}/maxcpu.adoc[]
+
+'''
+
+include::{reports-path}/squashfs.adoc[]
+
+'''
+
+include::{reports-path}/pf.adoc[]
+
+'''
+
+include::{reports-path}/ifapi.adoc[]
+
+'''
+
+include::{reports-path}/epoch-netgraph.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+'''
+
+include::{reports-path}/simd.adoc[]
+
+'''
+
+include::{reports-path}/mfsbsd.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+'''
+
+include::{reports-path}/cloud-init.adoc[]
+
+'''
+
+include::{reports-path}/openstack.adoc[]
+
+'''
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/ec2.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+'''
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/puppet.adoc[]
+
+'''
+
+include::{reports-path}/caldera.adoc[]
+
+'''
+
+include::{reports-path}/wazuh.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+'''
+
+include::{reports-path}/pkgbase.live.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2023-04-2023-06/azure.adoc b/website/content/en/status/report-2023-04-2023-06/azure.adoc
new file mode 100644
index 0000000000..425eab7b02
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/azure.adoc
@@ -0,0 +1,51 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+
+In this quarter, we have worked mainly on ARM64 architecture support and building and publishing images to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+There are some testing images available in the project's testing public gallery, named `FreeBSDCGTest-d8a43fa5-745a-4910-9f71-0c9da2ac22bf`:
+
+* FreeBSD-CURRENT-testing
+* FreeBSD-CURRENT-gen2-testing
+* FreeBSD-CURRENT-arm64-testing
+
+To use them, when creating a virtual machine:
+
+. In `Select an Image` step, choose `Community Images (PREVIEW)` in `Other items`
+. Search `FreeBSD`
+
+Work in progress tasks:
+
+* Automating the image building and publishing process and merge to src/release/.
+* Building and publishing ZFS-based images to Azure Marketplace
+** All the required codes are merged to main branch, and can create ZFS-based images by specifying `VMFS=zfs`.
+** Need to make the build process more automatic and collaborating with release engineering to start generating snapshots.
+* Building and publishing Hyper-V gen2 VM images to Azure Marketplace
+* Building and publishing snapshot builds to Azure community gallery
+
+The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+
+Wei Hu and Souradeep Chakrabarti in Microsoft are working on several tasks sponsored by Microsoft:
+
+* Porting Hyper-V guest support to aarch64
+** https://bugs.freebsd.org/267654
+** https://bugs.freebsd.org/272461
+
+Open tasks:
+
+* Update FreeBSD related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Support FreeBSD in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+* Update link:https://www.freshports.org/sysutils/azure-agent[Azure agent port] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2023-04-2023-06/batman.adoc b/website/content/en/status/report-2023-04-2023-06/batman.adoc
new file mode 100644
index 0000000000..500e7afea6
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/batman.adoc
@@ -0,0 +1,21 @@
+=== BATMAN support in the FreeBSD kernel
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/CallingTheBatmanFreeNetworksOnFreeBSD[Wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/CallingTheBatmanFreeNetworksOnFreeBSD[] +
+link:https://github.com/obiwac/freebsd-gsoc/pull/1[Source code (Pull Request)] URL: https://github.com/obiwac/freebsd-gsoc/pull/1[]
+
+Contact: Aymeric Wibo <obiwac@FreeBSD.org>
+
+BATMAN (Better Approach to Mobile Ad-hoc Networking), as developed and used by the Freifunk project, is a routing protocol for (primarily wireless) multi-hop ad-hoc networks.
+Freifunk is a German initiative to build an open Wi-Fi network at city-scale, based on the principles of net-neutrality.
+BATMAN's motive is to be a completely decentralized protocol; no one node in the network knows or has to care about the topology of the whole network.
+
+Support for this protocol is provided by the batman-adv kernel module on Linux, and this project aims to bring that to FreeBSD.
+This includes the kernel module itself, but also userland networking libraries and tools necessary to create BATMAN networks.
+
+Currently, creating interfaces and interacting with them works (with both Linux and FreeBSD userspaces), and packet transmission (kind of) works, although it is incomplete as of yet.
+Support for batadv interfaces has been added to man:ifconfig[8] too.
+
+Mentor: mailto:mmokhi@FreeBSD.org[Mahdi Mokhtari]
+
+Sponsor: The Google Summer of Code '23 program
diff --git a/website/content/en/status/report-2023-04-2023-06/boot-performance.adoc b/website/content/en/status/report-2023-04-2023-06/boot-performance.adoc
new file mode 100644
index 0000000000..01ecf983f0
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/boot-performance.adoc
@@ -0,0 +1,19 @@
+=== Boot Performance Improvements
+
+Links: +
+link:https://wiki.freebsd.org/BootTime[Wiki page] URL: link:https://wiki.freebsd.org/BootTime[] +
+link:https://www.bsdcan.org/events/bsdcan_2023/sessions/session/116/slides/44/BSDCan23-Firecracker.pdf[BSDCan talk slides] URL: link:https://www.bsdcan.org/events/bsdcan_2023/sessions/session/116/slides/44/BSDCan23-Firecracker.pdf[]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+Colin is coordinating efforts to speed up the FreeBSD boot process.
+
+Recent efforts have moved from EC2 to the Firecracker virtual machine manager, which provides a very minimalist environment; stripping the boot process down to the bare minimum makes it easier to identify the remaining time and determine whether it can be optimized further.
+
+With some experimental patches to both FreeBSD and Firecracker, it is now possible to boot a FreeBSD kernel in under 20 ms.
+
+Some of the recent improvements were discussed in Colin's _Porting FreeBSD to Firecracker_ session at BSDCan.
+
+This work is supported by his FreeBSD/EC2 Patreon.
+
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2023-04-2023-06/caldera.adoc b/website/content/en/status/report-2023-04-2023-06/caldera.adoc
new file mode 100644
index 0000000000..6aa99cb033
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/caldera.adoc
@@ -0,0 +1,29 @@
+=== MITRE Caldera on FreeBSD
+
+Links: +
+link:https://caldera.mitre.org/[MITRE Caldera] URL: link:https://caldera.mitre.org/[] +
+link:https://www.redcanary.com/[Red Canary] URL: link:https://www.redcanary.com/[]
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+MITRE Caldera is a cybersecurity platform designed to easily automate adversary emulation, assist manual red teams, and automate incident response.
+
+It is built on the MITRE ATT&CK(R) framework and is an active research project at MITRE.
+
+MITRE Caldera (package:security/caldera[]) was added to the ports tree in April 2023.
+This port includes support for the link:https://github.com/redcanaryco/atomic-red-team[Atomic Red Team Project] used by the link:https://github.com/mitre/atomic[MITRE Caldera atomic plugin].
+
+The main goal of this work is enhancing visibility of FreeBSD as a useful platform for information security or cybersecurity.
+
+Additionally, you can test a MITRE Caldera infrastructure easily using link:https://github.com/alonsobsd/caldera-makejail[] or link:https://github.com/AppJail-makejails/caldera[] from link:https://github.com/DtxdF/AppJail[AppJail].
+AppJail is a good tool for managing jail containers from the command line.
+
+People interested in helping with the project are welcome.
+
+Current version: 4.2.0
+
+==== To Do
+
+* Add Caldera testing infrastructure makejail.
+* Add FreeBSD to platforms officially supported by MITRE Caldera, see link:https://github.com/mitre/caldera/pull/2752[].
+* Add FreeBSD to platforms officially supported by Red Canary, see link:https://github.com/redcanaryco/atomic-red-team/pull/2450[].
diff --git a/website/content/en/status/report-2023-04-2023-06/capsicum-ktracing.adoc b/website/content/en/status/report-2023-04-2023-06/capsicum-ktracing.adoc
new file mode 100644
index 0000000000..05e7bc6825
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/capsicum-ktracing.adoc
@@ -0,0 +1,230 @@
+=== Security Sandboxing Using man:ktrace[1]
+
+Links: +
+link:https://github.com/jakesfreeland/freebsd-src/tree/ff/ktrace[ktrace branch] URL: link:https://github.com/jakesfreeland/freebsd-src/tree/ff/ktrace[] +
+
+Contact: Jake Freeland <jfree@FreeBSD.org>
+
+==== Capsicumization With man:ktrace[1]
+
+This report introduces an extension to man:ktrace[1] that logs capability violations for programs that have not been Capsicumized.
+
+The first logical step in Capsicumization is determining where your program is raising capability violations.
+You could approach this issue by looking through the source and removing Capsicum-incompatible code, but this can be tedious and requires the developer to be familiar with everything that is not allowed in capability mode.
+
+An alternative to finding violations manually is to use man:ktrace[1].
+The man:ktrace[1] utility logs kernel activity for a specified process.
+Capsicum violations occur inside of the kernel, so man:ktrace[1] can record and return extra information about your program's violations with the `-t p` option.
+
+Programs traditionally need to be put into capability mode before they will report violations.
+When a restricted system call is entered, it will fail and return with `ECAPMODE: Not permitted in capability mode`.
+If the developer is doing error checking, then it is likely that their program will terminate with that error.
+This behavior made violation tracing inconvenient because man:ktrace[1] would only report the first capability violation, and then the program would terminate.
+
+Luckily, a new extension to man:ktrace[1] can record violations when a program is **NOT** in capability mode.
+This means that any developer can run capability violation tracing on their program with no modification to see where it is raising violations.
+Since the program is never actually put into capability mode, it will still acquire resources and execute normally.
+
+==== Violation Tracing Examples
+
+The `cap_violate` program, shown below, attempts to raise every type of violation that man:ktrace[1] can capture:
+
+[source, shell]
+----
+# ktrace -t p ./cap_violate
+# kdump
+1603 ktrace   CAP   system call not allowed: execve
+1603 foo      CAP   system call not allowed: open
+1603 foo      CAP   system call not allowed: open
+1603 foo      CAP   system call not allowed: open
+1603 foo      CAP   system call not allowed: open
+1603 foo      CAP   system call not allowed: readlink
+1603 foo      CAP   system call not allowed: open
+1603 foo      CAP   cpuset_setaffinity: restricted cpuset operation
+1603 foo      CAP   openat: restricted VFS lookup: AT_FDCWD
+1603 foo      CAP   openat: restricted VFS lookup: /
+1603 foo      CAP   system call not allowed: bind
+1603 foo      CAP   sendto: restricted address lookup: struct sockaddr { AF_INET, 0.0.0.0:5000 }
+1603 foo      CAP   socket: protocol not allowed: IPPROTO_ICMP
+1603 foo      CAP   kill: signal delivery not allowed: SIGCONT
+1603 foo      CAP   system call not allowed: chdir
+1603 foo      CAP   system call not allowed: fcntl, cmd: F_KINFO
+1603 foo      CAP   operation requires CAP_WRITE, descriptor holds CAP_READ
+1603 foo      CAP   attempt to increase capabilities from CAP_READ to CAP_READ,CAP_WRITE
+----
+
+The first 7 `system call not allowed` entries did not explicitly originate from the `cap_violate` program code.
+Instead, they were raised by FreeBSD's C runtime libraries.
+This becomes apparent when you trace namei translations alongside capability violations using the `-t np` option:
+
+[source, shell]
+----
+# ktrace -t np ./cap_violate
+# kdump
+1632 ktrace   CAP   system call not allowed: execve
+1632 ktrace   NAMI  "./cap_violate"
+1632 ktrace   NAMI  "/libexec/ld-elf.so.1"
+1632 foo      CAP   system call not allowed: open
+1632 foo      NAMI  "/etc/libmap.conf"
+1632 foo      CAP   system call not allowed: open
+1632 foo      NAMI  "/usr/local/etc/libmap.d"
+1632 foo      CAP   system call not allowed: open
+1632 foo      NAMI  "/var/run/ld-elf.so.hints"
+1632 foo      CAP   system call not allowed: open
+1632 foo      NAMI  "/lib/libc.so.7"
+1632 foo      CAP   system call not allowed: readlink
+1632 foo      NAMI  "/etc/malloc.conf"
+1632 foo      CAP   system call not allowed: open
+1632 foo      NAMI  "/dev/pvclock"
+1632 foo      CAP   cpuset_setaffinity: restricted cpuset operation
+1632 foo      NAMI  "ktrace.out"
+1632 foo      CAP   openat: restricted VFS lookup: AT_FDCWD
+1632 foo      NAMI  "/"
+1632 foo      CAP   openat: restricted VFS lookup: /
+1632 foo      CAP   system call not allowed: bind
+1632 foo      CAP   sendto: restricted address lookup: struct sockaddr { AF_INET, 0.0.0.0:5000 }
+1632 foo      CAP   socket: protocol not allowed: IPPROTO_ICMP
+1632 foo      CAP   kill: signal delivery not allowed: SIGCONT
+1632 foo      CAP   system call not allowed: chdir
+1632 foo      NAMI  "."
+1632 foo      CAP   system call not allowed: fcntl, cmd: F_KINFO
+1632 foo      CAP   operation requires CAP_WRITE, descriptor holds CAP_READ
+1632 foo      CAP   attempt to increase capabilities from CAP_READ to CAP_READ,CAP_WRITE
+----
+
+In practice, capability mode is always entered following the initialization of the C runtime libraries, so a program would never trigger those first 7 violations.
+We are only seeing them because man:ktrace[1] starts recording violations before the program starts.
+
+This demonstration makes it clear that violation tracing is not always perfect.
+It is a helpful guide for detecting restricted system calls, but may not always parody your program's actual behavior in capability mode.
+In capability mode, violations are equivalent to errors; they are an indication to stop execution.
+Violation tracing is ignoring this suggestion and continuing execution anyway, so invalid violations may be reported.
+
+The next example traces violations from the man:unzip[1] utility (pre-Capsicumization):
+
+[source, shell]
+----
+# ktrace -t np unzip foo.zip
+Archive:  foo.zip
+creating: bar/
+extracting: bar/bar.txt
+creating: baz/
+extracting: baz/baz.txt
+# kdump
+1926 ktrace   CAP   system call not allowed: execve
+1926 ktrace   NAMI  "/usr/bin/unzip"
+1926 ktrace   NAMI  "/libexec/ld-elf.so.1"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/etc/libmap.conf"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/usr/local/etc/libmap.d"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/var/run/ld-elf.so.hints"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libarchive.so.7"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/usr/lib/libarchive.so.7"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libc.so.7"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libz.so.6"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libbz2.so.4"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/usr/lib/libbz2.so.4"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/liblzma.so.5"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/usr/lib/liblzma.so.5"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libbsdxml.so.4"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libprivatezstd.so.5"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/usr/lib/libprivatezstd.so.5"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libcrypto.so.111"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libmd.so.6"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libthr.so.3"
+1926 unzip    CAP   system call not allowed: readlink
+1926 unzip    NAMI  "/etc/malloc.conf"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/dev/pvclock"
+1926 unzip    NAMI  "foo.zip"
+1926 unzip    CAP   openat: restricted VFS lookup: AT_FDCWD
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/etc/localtime"
+1926 unzip    NAMI  "bar"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    CAP   system call not allowed: mkdir
+1926 unzip    NAMI  "bar"
+1926 unzip    NAMI  "bar"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "bar/bar.txt"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "bar/bar.txt"
+1926 unzip    CAP   openat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "baz"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    CAP   system call not allowed: mkdir
+1926 unzip    NAMI  "baz"
+1926 unzip    NAMI  "baz"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "baz/baz.txt"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "baz/baz.txt"
+1926 unzip    CAP   openat: restricted VFS lookup: AT_FDCWD
+----
+
+The violation tracing output for man:unzip[1] is more akin to what a developer would see when tracing their own program for the first time.
+Most programs link against libraries.
+In this case, man:unzip[1] is linking against man:libarchive[3], which is reflected here:
+
+[source, shell]
+----
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/lib/libarchive.so.7"
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/usr/lib/libarchive.so.7"
+----
+
+The violations for man:unzip[1] can be found below the C runtime violations:
+
+[source, shell]
+----
+1926 unzip    NAMI  "foo.zip"
+1926 unzip    CAP   openat: restricted VFS lookup: AT_FDCWD
+1926 unzip    CAP   system call not allowed: open
+1926 unzip    NAMI  "/etc/localtime"
+1926 unzip    NAMI  "bar"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    CAP   system call not allowed: mkdir
+1926 unzip    NAMI  "bar"
+1926 unzip    NAMI  "bar"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "bar/bar.txt"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "bar/bar.txt"
+1926 unzip    CAP   openat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "baz"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    CAP   system call not allowed: mkdir
+1926 unzip    NAMI  "baz"
+1926 unzip    NAMI  "baz"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "baz/baz.txt"
+1926 unzip    CAP   fstatat: restricted VFS lookup: AT_FDCWD
+1926 unzip    NAMI  "baz/baz.txt"
+1926 unzip    CAP   openat: restricted VFS lookup: AT_FDCWD
+----
+
+In this instance, man:unzip[1] is recreating the file structure contained in the zip archive.
+Violations are being raised because the `AT_FDCWD` value cannot be used in capability mode.
+The bulk of these violations can be fixed by opening `AT_FDCWD` (the current directory) before entering capability mode and passing that descriptor into man:openat[2], man:fstatat[2], and man:mkdirat[2] as a relative reference.
+
+Violation tracing may not automatically Capsicumize programs, but it is another tool in the developer's toolbox.
+It only takes a few seconds to run a program under man:ktrace[1] and the result is almost always a decent starting point for sandboxing your program using Capsicum.
+
+Sponsor: FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc b/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc
new file mode 100644
index 0000000000..d38c25afb3
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc
@@ -0,0 +1,21 @@
+=== CI Test Harness For Bootloader
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/CITestHarnessForBootloader[FreeBSD Wiki GSoC Page] URL: https://wiki.freebsd.org/SummerOfCode2023Projects/CITestHarnessForBootloader[] +
+link:https://github.com/mightyjoe781/freebsd-src/tree/bootloader-smk/tools/boot/bootloader_test[GitHub Project Link] URL: https://github.com/mightyjoe781/freebsd-src/tree/bootloader-smk/tools/boot/bootloader_test[]
+
+Contact: Sudhanshu Mohan Kashyap <smk@FreeBSD.org>
+
+FreeBSD supports multiple architectures, file systems, and disk-partitioning schemes.
+I am trying to write a Lua script which would allow for testing boot loader of all the architecture combinations supported in the first and second-tier support, and provide a report on any broken combinations and expected functionality.
+If time permits, further exploration could be done to integrate the script into the existing build infrastructure (either Jenkins or GitHub Actions) to generate a comprehensive summary of the test results.
+
+Currently any changes made by developer might inhibit the ability of the operating system to boot in some specific environment.
+These scripts provide assurance that changes do not cause regressions for the tested environments.
+The scripts are designed to be efficient and much less expensive than a full make universe required today.
+These attributes allow developers to routinely use the script, and allow integration into the CI pipelines without undue cost.
+
+Currently script related work seems to be on track, but certainly ahead I will need to find all different kinds of QEMU recipes to test different environments.
+If anyone has any kind of working QEMU recipe for currently released versions of FreeBSD, feel free to send to me via mail at smk@FreeBSD.org .
+
+Sponsor: The Google Summer of Code '23 program
diff --git a/website/content/en/status/report-2023-04-2023-06/ci.adoc b/website/content/en/status/report-2023-04-2023-06/ci.adoc
new file mode 100644
index 0000000000..1bec18c9bc
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/ci.adoc
@@ -0,0 +1,51 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the second quarter of 2023, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* link:https://ci.FreeBSD.org/job/FreeBSD-stable-13-amd64-gcc12_build/[FreeBSD-stable-13-amd64-gcc12_build] job has been added.
+* Build environment of main and stable/13 branches has been changed to 13.2-RELEASE, and stable/12 has been changed to 12.4-RELEASE.
+* *-build jobs using gcc12 are sending failure reports to link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List].
+* Present Testing/CI Status Update in link:https://wiki.freebsd.org/DevSummit/202305[BSDCan 2023 Developer Summit]
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository
+* Improving the hardware test lab and adding more hardware for testing
+* Merge link:https://reviews.freebsd.org/D38815[]
+* Merge link:https://reviews.freebsd.org/D36257[]
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/cirrus.adoc b/website/content/en/status/report-2023-04-2023-06/cirrus.adoc
new file mode 100644
index 0000000000..b0a91ec5ff
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/cirrus.adoc
@@ -0,0 +1,24 @@
+=== Cirrus-CI
+
+Links: +
+link:https://cirrus-ci.com/github/freebsd/[FreeBSD Cirrus-CI Repositories] URL: link:https://cirrus-ci.com/github/freebsd/[] +
+link:https://cirrus-ci.com/github/freebsd/freebsd-src[FreeBSD src CI] URL: link:https://cirrus-ci.com/github/freebsd/freebsd-src[] +
+link:https://cirrus-ci.com/github/freebsd/freebsd-doc[FreeBSD doc CI] URL: link:https://cirrus-ci.com/github/freebsd/freebsd-doc[]
+
+Contact: Brooks Davis <brooks@FreeBSD.org> +
+Contact: Ed Maste <emaste@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+Cirrus-CI is a hosted continuous integration service that supports open source projects with CI services on Linux, Windows, macOS, and FreeBSD.
+It complements our own Jenkins CI infrastructure by supporting other use cases, including testing GitHub pull requests and FreeBSD forks.
+We added Cirrus-CI configuration to the FreeBSD src tree in 2019 and to doc in 2020.
+A number of additional FreeBSD projects hosted on GitHub (such as drm-kmod, kyua, pkg, and poudriere) also make use of Cirrus-CI.
+
+Cirrus-CI configs received ongoing maintenance updates (moving to the most recent FreeBSD release images).
+In the src tree we have added some additional checks.
+These ensure that generated files are updated when needed (`make sysent` and `make makeman`) and check for missing directories.
+We have added jobs that build using the Clang/LLVM 16 toolchain package, mirroring the Clang version now in the base system.
+The GCC job is now run on the GitHub mirror by default, for all commits.
+
+Sponsor: DARPA +
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/cloud-init.adoc b/website/content/en/status/report-2023-04-2023-06/cloud-init.adoc
new file mode 100644
index 0000000000..d4a16af4e9
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/cloud-init.adoc
@@ -0,0 +1,35 @@
+=== FreeBSD as a Tier 1 cloud-init Platform
+
+Links: +
+link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[] +
+link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[] +
+link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[]
+
+Contact: Mina Galić <freebsd@igalic.co>
+
+cloud-init is the standard way of provisioning servers in the cloud.
+Unfortunately, cloud-init support for operating systems other than Linux has been rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform.
+To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support.
+The broader plan is to lift support across all BSDs.
+
+This quarter has been going quite slowly, but I have managed to deliver a new milestone:
+
+- Ephemeral Networking classes have been rewritten and made platform independent.
+These are used by several cloud providers to initialize a temporary network before retrieving the actual configuration.
+
+- cloud-init has been successfully tested on Vultr.
+I hope that with the next release I can convince Vultr to switch their FreeBSD images to cloud-init.
+
+In addition to that, I have expanded rsyslog support for BSD.
+I've also added an rc script for cloud-init's ds-identify, which should make zero-configuration setups orders of magnitude faster:
+ds-identify runs first and very quickly guesses the cloud provider the machine is running on.
+cloud-init then uses only that guess, instead of iterating and failing through a full list of all possible cloud providers.
+People building custom images can easily disable this (by removing ``/usr/local/etc/rc.d/dsidentify``), and providing a specific listing themselves, shave off a few more milliseconds from their boot.
+
+The next steps will be to keep hacking away at the network refactoring tasks, and to add LXD support for FreeBSD, so it can be included in CI tests.
+The latter will include work on link:https://github.com/canonical/lxd/pull/11761[LXD], as well as work on the link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271793[FreeBSD virtio subsystem].
+
+As always, I highly welcome early testers to checkout package:net/cloud-init-devel[], and report bugs.
+Since the last report, cloud-init's bug tracker has moved from Launchpad to GitHub, so this might reduce some friction.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/clusteradm.adoc b/website/content/en/status/report-2023-04-2023-06/clusteradm.adoc
new file mode 100644
index 0000000000..3843104b3a
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/clusteradm.adoc
@@ -0,0 +1,55 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular support for FreeBSD.org user accounts.
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* Enable mirroring of link:https://www.FreeBSD.org[] and link:https://docs.FreeBSD.org[] in the FreeBSD project-managed mirrors.
+* Cluster refresh, upgrading all hosts and jails to the most recent versions of 14-CURRENT, 13-STABLE, and 12-STABLE.
+
+==== Work in progress
+
+* Large-scale network upgrade at our primary site.
+** New link:https://www.juniper.net/[Juniper] switches arrived at our primary site to replace the former ones.
+We thank Juniper for the donation.
+* Replace old servers in our primary site and a few mirrors.
+** Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs.
+This task is in conjunction with The FreeBSD Foundation and donors/sponsors.
+* Install new CI (Continuous Integration) machines repurposed from the package builders.
+* Review the backup configuration of the services running in the FreeBSD cluster.
+
+==== FreeBSD Official Mirrors Overview
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America -- California, New Jersey (primary site), and Washington.
+
+The hardware and network connection have been generously provided by:
+
+* https://www.bytemark.co.uk/[Bytemark Hosting]
+* Cloud and SDN Laboratory at https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc]
+* https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University]
+* https://deploy.equinix.com/[Equinix]
+* https://internet.asn.au/[Internet Association of Australia]
+* https://www.isc.org/[Internet Systems Consortium]
+* https://www.inx.net.za/[INX-ZA]
+* https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc]
+* https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network]
+* https://www.metapeer.com/[Metapeer]
+* https://nic.br/[NIC.br]
+* https://your.org/[Your.Org]
+* https://365datacenters.com/[365 Data Centers]
+
+The Frankfurt single server mirror is the primary Europe mirror in bandwidth and usage.
+
+We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site.
+
+We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch.
+United States (West Coast) and Europe (anywhere) are preferable places.
+
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site.
diff --git a/website/content/en/status/report-2023-04-2023-06/compaction.adoc b/website/content/en/status/report-2023-04-2023-06/compaction.adoc
new file mode 100644
index 0000000000..fb3eb1f24a
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/compaction.adoc
@@ -0,0 +1,21 @@
+=== Physical memory compaction for the FreeBSD kernel
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms[GSoC project wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms[] +
+link:https://reviews.freebsd.org/D40575[Differential revision 40575] URL: link:https://reviews.freebsd.org/D40575[] +
+link:https://reviews.freebsd.org/D40772[Differential revision 40772] URL: link:https://reviews.freebsd.org/D40772[]
+
+Contact: Bojan Novković <bnovkov@FreeBSD.org>
+
+Most modern CPU architectures offer performance boosts by supporting pages that are larger than the standard page size.
+Unfortunately, allocating such pages can fail due to a high degree of physical memory fragmentation.
+This work implements physical memory compaction as a means of actively reducing fragmentation in running systems.
+This work is part of an ongoing Google Summer of Code project, the goal of which is to add various physical memory anti-fragmentation measures to the virtual memory subsystem.
+
+Differential link:https://reviews.freebsd.org/D40575[D40575] implements a well-known metric used for quantifying the degree of physical memory fragmentation.
+Differential link:https://reviews.freebsd.org/D40772[D40772] implements physical memory compaction and adds a daemon that monitors the system and performs compaction when needed.
+
+Planned future work includes designing an appropriate benchmarking suite, running tests, and tweaking the code using feedback from reviews and test results.
+This is still a work in progress, so any testing, reviews, and feedback would be greatly appreciated.
+
+Sponsor: The Google Summer of Code '23 program
diff --git a/website/content/en/status/report-2023-04-2023-06/core.adoc b/website/content/en/status/report-2023-04-2023-06/core.adoc
new file mode 100644
index 0000000000..8e97a662f4
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/core.adoc
@@ -0,0 +1,40 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== DevSummit 202305
+
+The Core Team has presented the status update at the FreeBSD Developer Summit, 17th–18th May.
+Slides are available at link:https://wiki.freebsd.org/DevSummit/202305[].
+
+==== FreeBSD 14
+
+The Core Team is working with other teams to ensure that FreeBSD 14.0-RELEASE will be of the highest quality.
+
+The Core Team has no objection to mark riscv64sf (64-bit RISC-V soft-float) as https://www.freebsd.org/platforms/[unsupported in 14].
+
+==== Meetings with The FreeBSD Foundation
+
+The Core Team and The FreeBSD Foundation continue to meet regularly to discuss the next steps to take for the management, development, and future of FreeBSD.
+The Core Team had two meetings with the Board of Directors of, and employees of, the Foundation.
+They discussed how the Foundation can help the Core Team and the Project in general.
+
+==== Matrix IM solution
+
+One of the major items in the Core Team updates in DevSummit 202305 was proposing a new project communication solution.
+
+There is currently a testing instance at matrix-dev.FreeBSD.org setup by clusteradm.
+All developers can access the instance with their kerberos credentials, and some public rooms can be joined through Matrix's federation feature.
+Please note this instance is for testing and evaluating so no backup or availability is guaranteed.
+
+The Core Team is still discussing the scope and administration of this service, and collecting feedback from the community.
+
+==== Code of Conduct Committee
+
+Code of Conduct Committee (conduct@) is managed by the Core Team now.
+
+==== Commit bits
+
+Core approved the src commit bit for Christos Margiolis (christos@).
diff --git a/website/content/en/status/report-2023-04-2023-06/doceng.adoc b/website/content/en/status/report-2023-04-2023-06/doceng.adoc
new file mode 100644
index 0000000000..2cae11159f
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/doceng.adoc
@@ -0,0 +1,104 @@
+////
+Quarter:	2nd quarter of 2023
+Prepared by:	fernape
+Reviewed by:	dbaio, carlavilla
+Last edit:	$Date: 2023-06-25 15:11:08 +0200 (Sun, 25 Jun 2023) $
+Version:	$Id: doceng-2023-2nd-quarter-status-report.adoc 415 2023-06-25 13:11:08Z carlavilla $
+////
+
+=== Documentation Engineering Team
+
+Links: +
+link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj[] +
+link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] +
+link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see the link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During this quarter:
+
+* fernape@ has been appointed as a new Doceng team member.
+* The package:www/gohugo[] port maintainership has been transferred to doceng@ since it is a critical part of our documentation infrastructure.
+This was agreed with the former maintainer.
+* Improvements to the translation workflow (described in the following sections).
+
+==== Porter's Handbook
+
+link:https://cgit.freebsd.org/doc/commit/?id=634a34b7bb37650e4f8fcbea9fd7428b3f5b911a[`USES=nextcloud`] has been documented.
+
+==== FDP Primer
+
+A new chapter focusing on Weblate has been added to the link:https://docs.freebsd.org/en/books/fdp-primer/weblate/[FreeBSD Documentation Project Primer for New Contributors].
+This comprehensive chapter provides step-by-step guidance on joining the FreeBSD translators team, both for translating online on Weblate and offline.
+It offers valuable insights and practical suggestions for efficient translation, proofreading, and testing processes.
+Furthermore, this chapter equips contributors with the necessary knowledge to formally submit their translations to the documentation repository, ensuring a seamless integration of their work.
+
+==== FreeBSD Translations on Weblate
+
+Links: +
+link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblate[] +
+link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/[]
+
+===== Q2 2023 Status
+
+* 15 languages
+* 183 registered users
+* link:https://lists.freebsd.org/archives/freebsd-translators/2023-April/000111.html[New Weblate server]
+
+The FreeBSD Weblate instance now operates on a dedicated server, significantly improving its speed and enhancing the efficiency of translation work.
+Our heartfelt appreciation goes to ebrandi@ for providing this hardware upgrade.
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 7%)
+* Chinese (Traditional) (zh-tw)	(progress: 3%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 5%)
+* Korean (ko)			(progress: 32%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 3%)
+* Polish			(progress: 1%)
+* Portuguese (pt-br)		(progress: 22%)
+* Sinhala (si)			(progress: 1%)
+* Spanish (es)			(progress: 33%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+==== FreeBSD Handbook working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+link:https://reviews.freebsd.org/D40546[The Network chapter is being reworked].
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work is divided into four phases:
+
+. Redesign of the Documentation Portal
++
+Create a new design, responsive and with global search. (_Complete_)
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Complete_)
+Public instance on https://man-dev.FreeBSD.org
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Work in progress_)
diff --git a/website/content/en/status/report-2023-04-2023-06/ec2.adoc b/website/content/en/status/report-2023-04-2023-06/ec2.adoc
new file mode 100644
index 0000000000..d2d209c598
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/ec2.adoc
@@ -0,0 +1,19 @@
+=== FreeBSD on EC2
+
+Links: +
+link:https://www.patreon.com/cperciva[FreeBSD/EC2 Patreon]	URL: https://www.patreon.com/cperciva[]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+FreeBSD is available on both x86 (Intel and AMD) and ARM64 (Graviton) EC2 instances.
+Work continues to ensure that upcoming instance types will be supported, including the recently announced M7a "EPYC" instances, which should be supported in FreeBSD 14.0-RELEASE.
+
+Weekly FreeBSD snapshots were recently changed from "UEFI" boot mode to "UEFI Preferred" boot mode, allowing them to gain the boot performance improvement offered by UEFI while still supporting "bare metal" and "previous generation" instance types which are not compatible with UEFI.
+This change will be present in FreeBSD 14.0-RELEASE.
+
+The EC2 boot scripts were recently updated to support IMDSv2.
+This change will be present in FreeBSD 14.0-RELEASE.
+
+If users of FreeBSD 13.2 require any of these updates, the author can provide FreeBSD "13.2-RELEASE plus updates" AMIs.
+
+This work is supported by Colin's FreeBSD/EC2 Patreon.
diff --git a/website/content/en/status/report-2023-04-2023-06/epoch-netgraph.adoc b/website/content/en/status/report-2023-04-2023-06/epoch-netgraph.adoc
new file mode 100644
index 0000000000..786d2bc164
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/epoch-netgraph.adoc
@@ -0,0 +1,32 @@
+=== Making Netgraph Lock-Free
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/LocklessSynchronizationBetweenNodesInNetgraph[Wiki Page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/LocklessSynchronizationBetweenNodesInNetgraph[] +
+link:https://github.com/zinh88/epoch-netgraph[Repo] URL: link:https://github.com/zinh88/epoch-netgraph[]
+
+Contact: Zain Khan <zain@FreeBSD.org>
+
+Netgraph helps us implement custom or complex networking functions by letting us arrange kernel objects called nodes in a graph connected using hooks.
+Nodes may perform a well-defined set of actions on incoming packets, and may send the output to another connected node.
+To 'send' a packet to a neighbour can also be seen as calling a function on that neighbouring node.
+
+Now in a pre-SMP world, a thread (or *the* thread) would always see nodes as idle (not busy), so that their functions can immediately be called.
+Concurrency introduced the possibility of a busy node.
+Moreover, a journey of a packet also needs to take heed of changes in the structure of the graph, for example: the addressed node's path may not remain intact due to no-longer-existing hooks or nodes in between, which may lead to cases such as referring to an object that has been freed.
+To counter such disasters, the existing source code uses a topology read-write mutex which protects data flow from restructuring events (and restructuring events from other restructuring events).
+
+We want to regain the same smooth flow for data which existed when concurrent cpus were not a thing.
+That is, data should simply never wait every time there is a restructuring event.
+At the same time we also obviously do not want to give the kernel reasons to panic.
+
+FreeBSD has its own set of concurrency-safe data structures and mechanisms.
+One of these mechanisms is Epoch.
+Epoch-based reclamation involves waiting for existing read-side critical sections to finish before the data structures need to be modified or reclaimed.
+
+Because the base system is being modified, this is also going to affect the design choices made before, such as queuing on messages, reference counting.
+
+This project involves a lot of testing.
+For now, some topology protection locks have been removed, and only simple graphs have been tested (with FreeBSD running on a VM).
+The real tests should be run on hardware with at least 4 CPU cores, I will do that when I get my hands on one.
+
+Sponsor: The Google Summer of Code '23 program
diff --git a/website/content/en/status/report-2023-04-2023-06/freebsd-foundation.adoc b/website/content/en/status/report-2023-04-2023-06/freebsd-foundation.adoc
new file mode 100644
index 0000000000..4673ee207e
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/freebsd-foundation.adoc
@@ -0,0 +1,169 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[] +
+link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide.
+Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits.
+We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts.
+We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+==== Happy 30th birthday, FreeBSD!
+
+For more than 23 years, we have proudly backed this remarkable operating system and its vibrant community, and we eagerly anticipate supporting them for many more years.
+In this update, we will outline our contributions to FreeBSD across multiple domains.
+We will touch upon project development initiatives, some of which have detailed reports of their own.
+Additionally, we will showcase our advocacy for FreeBSD, our efforts to foster community engagement, and our expansion of partnership endeavors.
+Lastly, we will delve into our ongoing work to secure increased funding, enabling us to allocate additional resources to address any gaps within the Project.
+
+==== Fundraising
+
+During this quarter, we made significant progress in engaging with commercial FreeBSD users.
+To enhance our partnerships with existing and potential commercial users, we hired Greg Wallace as the Director of Partnerships and Research.
+His primary objective is to expand our collaborations with commercial users.
+Since assuming this position, Greg has hit the ground running, meeting with numerous companies in just one quarter.
+These interactions have provided valuable insights into how FreeBSD is being utilized, the challenges faced by users, and areas where the Project can improve.
+By understanding these aspects, we can make informed decisions on where to allocate our funding and recognize FreeBSD's unique strengths.
+Additionally, the role involves conducting research to identify target markets, explore new opportunities for FreeBSD, and ensure our voice is heard in relevant discussions.
+For more details on Greg's objectives and accomplishments, you can refer to his status update below.
+
+The Foundation extends its heartfelt gratitude to everyone who made financial contributions to support our work.
+Besides many individual contributions, we were pleased to receive larger donations from NetApp and Blackberry.
+In addition, we received FreeBSD Developer Summit sponsorships from Tarsnap, iXsystems, and LPI.
+These sponsorships greatly assist in offsetting our expenses and enable us to offer affordable registration fees to attendees.
+
+This year our budget is around $2,230,000, which includes increased spending toward FreeBSD advocacy and software development.
+More than half of our budget is allocated toward work directly related to improving FreeBSD and keeping it secure.
+
+By having a dedicated individual focused on partnerships, we can effectively emphasize the significance of investing in our efforts and underscore the long-term viability of the Project to companies.
+
+Your support plays a crucial role in our mission, and we deeply appreciate your commitment to the FreeBSD community.
+Please consider making a donation toward our 2023 fundraising campaign!
+link:https://www.freebsdfoundation.org/donate/[]
+
+For more prominent commercial donors we have the link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[FreeBSD Foundation Partnership Program], which was established in 2017.
+
+==== Partnership Program
+
+Hello FreeBSD community.
+My name is Greg Wallace.
+I joined the Foundation as Director of Partnerships and Research in early April.
+link:https://freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-team-members/[This blog introduced me and the role].
+For Partnerships, I am focused on building connections with companies that use FreeBSD.
+I have met with several companies to learn about how they use FreeBSD.
+Some of these meetings have generated discussions about potential partnership.
+I continue to find out about interesting companies using FreeBSD and I am reaching out to them.
+
+My objective is to get in touch with every company building with and using FreeBSD to listen to their stories.
+If this is you and we have not yet connected, please schedule a call on link:https://calendly.com/greg-freebsdfound/30min[my calendar].
+
+Some other partnership-related activities this quarter:
+
+* I created link:https://docs.google.com/presentation/d/1tDCpbfxbqIucmJF6H15vK-ETrQsCMOVtxoqLem_V0Z0/edit?usp=sharing[these slides] about how partnering with the Foundation helps advance FreeBSD.
+  If you have ideas for how I can improve these slides, or would like me to present them to your organization, please mailto:greg@freebsdfoundation.org[send me an email], or link:https://calendly.com/greg-freebsdfound/30min[schedule a call].
+  And please feel free to share the presentation liberally, in whole or in part.
+* I worked with my Foundation colleagues to create a number of industry-specific use case slides for a presentation to an industry analyst.
+* I am also pursuing grant opportunities with bodies including:
+** NSF Secure and Trustworthy Cyberspace (SaTC)
+** Sovereign Tech Fund
+** NGI.
+
+In terms of research, my broad aim is to make sure that all of the expertise in this community is reflected in the global conversations on computing performance, security, and energy efficiency.
+As a community, we have much to bring to this work.
+
+So far, I have been tracking and plugging into the following threads:
+
+* link:https://openforumeurope.org/open-source/[Open Forum Europe]
+* link:https://www.nist.gov/chips/research-and-development-program[CHIPS Research and Development].
+
+If you have research ideas or are interested in working together in this area, please mailto:greg@freebsdfoundation.org[send me an email], or link:https://calendly.com/greg-freebsdfound/30min[schedule a call].
+
+==== OS Improvements
+
+During the second quarter of 2023, 339 src, 155 ports, and 20 doc tree commits identified The FreeBSD Foundation as a sponsor.
+Some of this and other Foundation-sponsored work is described in separate report entries:
+
+* <<_continuous_integration,Continuous Integration>>
+* <<_freebsd_as_a_tier_1_cloud_init_platform,FreeBSD as a Tier 1 cloud-init Platform>>
+* <<_openssl_3_in_base,OpenSSL 3 in base>>
+* <<_openstack_on_freebsd,OpenStack on FreeBSD>>
+* <<_security_sandboxing_using_ktrace1,Security Sandboxing Using ktrace(1)>>
+* <<_simd_enhancements_for_amd64,SIMD enhancements for amd64>>
+
+Here is a sampling of other Foundation-sponsored work:
+
+* Bug fixes for man:fsck_ffs[8]
+* Bug fixes for man:killpg[2]
+* Improvements to hwpmc
+* Improvements to vmm
+* Port fixes and workarounds for LLVM 16 and OpenSSL 3.0
+* Port kinst to RISC-V and related DTrace work
+* Update of libfido2 to version 1.9.0
+* Various LinuxKPI 802.11 improvements
+* Various RISC-V improvements
+* Vendor import and update of tcpdump from version 4.9.3 to version 4.99.4.
+
+The status of current and past Foundation-contracted work can be viewed on the link:https://freebsdfoundation.org/our-work/projects/[Foundation Projects page].
+
+Members of the Foundation's technology team presented at the Developer Summit held in Ottawa, Canada from May 17-18.
+This included hosting the GSoC, link:https://wiki.freebsd.org/DevSummit/202305?action=AttachFile&do=view&target=FreeBSD_Foundation_Devsummit_Spring_2023_Day_2.pdf[FreeBSD Foundation] link:https://wiki.freebsd.org/DevSummit/202305?action=AttachFile&do=view&target=FreeBSD_Foundation_Devsummit_Spring_2023_Day_2_part1.pdf[Technical Review], and link:https://docs.google.com/presentation/d/e/2PACX-1vSnEW5Z0ttQOAeqEEY8KHkfiRGeFUm4i8XrYsfY8TNYD--yx1P6MUu2_u-mCcpe6PMMITjeDIgT31CC/pub[Workflow] working group sessions.
+Pierre Pronchery spoke about link:https://www.bsdcan.org/events/bsdcan_2023/schedule/speaker/89-pierre-pronchery/[driver harmony between the BSDs] and En-Wei Wu discussed link:https://www.bsdcan.org/events/bsdcan_2023/schedule/session/139-add-operating-modes-to-wtap4/[wtap work] completed under contract with the Foundation.
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project.
+You can read more about CI work in a dedicated report entry.
+
+==== Advocacy
+
+Much of our effort is dedicated to the FreeBSD Project advocacy.
+This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations.
+The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier.
+Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe.
+These events can be BSD-related, open source, or technology events geared towards underrepresented groups.
+We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.
+This all helps provide a healthy ecosystem.
+We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.
+We are grateful to be back to attending events mostly in person.
+In addition to attending and planning events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD.
+
+Check out some of the advocacy and education work we did:
+
+* Helped to organize and attended the link:https://wiki.freebsd.org/DevSummit/202305[May 2023 Developer Summit] which took place May 17-18, 2023 in Ottawa, Ontario
+* Hosted a table and was the Tote Bag Sponsor of link:https://www.bsdcan.org/2023/[BSDCan], May 17-20, 2023 in Ottawa, Ontario
+** Trip reports can be found on the link:https://freebsdfoundation.org/our-work/latest-updates/[blog]
+* Celebrated the Project’s 30th Birthday at BSDCan with cake and printed copies of the special link:https://freebsdfoundation.org/past-issues/freebsd-30th-anniversary-special-edition/[30th Anniversary Edition] of the FreeBSD Journal
+* Secured a FreeBSD Workshop and Talk at link:https://sfconservancy.org/fossy/[FOSSY], July 13-16, 2023, in Portland, Oregon
+* Secured our Silver Sponsorship for link:https://2023.eurobsdcon.org/[EuroBSDCon 2023] taking place September 14-17, 2023 in Coimbra, Portugal
+* Secured our booth for link:https://2023.allthingsopen.org/[All Things Open], October 15-17, 2023 in Raleigh, North Carolina
+* Began planning the FreeBSD Fall Vendor Summit
+* Welcomed two link:https://freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-team-members/[New Team Members]: Greg Wallace and Pierre Pronchery
+* Published link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-april-2023/[April] and link:https://freebsdfoundation.org/news-and-events/newsletter/12518/[June] Newsletters
+* Celebrated the link:https://freebsdfoundation.org/national-freebsd-day/[FreeBSD Day] and the Project's 30th Anniversary on June 19 and through the week with special videos and blog posts
+* Additional Blog Posts:
+** link:https://freebsdfoundation.org/blog/eurobsdcon-2023-travel-grant-application-now-open/[EuroBSDcon 2023 Travel Grant Application Now Open] - Note: Applications close August 2, 2023
+** link:https://freebsdfoundation.org/blog/asiabsdcon-2023-trip-report/[AsiaBSDcon Trip Report]
+* FreeBSD in the News:
+** link:https://freebsdfoundation.org/news-and-events/latest-news/infoworld-happy-30th-freebsd/[InfoWorld: Happy 30th FreeBSD!].
+
+We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal.
+As we mentioned previously, the FreeBSD Journal is now a free publication.
+Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[].
+
+You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[].
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://www.freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2023-04-2023-06/gcc.adoc b/website/content/en/status/report-2023-04-2023-06/gcc.adoc
new file mode 100644
index 0000000000..9c410652c0
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/gcc.adoc
@@ -0,0 +1,48 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[]
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+Upstream has released link:https://gcc.gnu.org/gcc-13[GCC 13].
+As announced in the past status report, I plan to attempt an update of GCC_DEFAULT right from the first GCC 13 release, thus much of this quarter's work has been in preparation of this.
+
+With the release of GCC 13.1 (first GCC 13 release: I remind that GCC counts minor version releases starting from 1), two new ports have been created in the ports tree:
+
+* package:lang/gcc13[], tracking GCC 13 releases;
+* package:lang/gcc14-devel[], tracking snapshots from the new GCC 14 upstream branch.
+
+==== The *-devel ports
+
+Support for .init_array and .fini_array has been enabled.
+FreeBSD supports both since commit gitref:83aa9cc00c2d83d05a0efe7a1496d8aab4a153bb[repository=src].
+
+The default bootstrap option on i386, amd64, and aarch64 has been reverted from LTO_BOOTSTRAP to STANDARD_BOOTSTRAP:
+
+- LTO bootstrap produces too many failures on the package builders for those architectures
+- LTO_BOOTSTRAP remains available for users who want it.
+
+Those changes will be forwarded to the production ports.
+
+==== The production ports
+
+Upstream has released GCC 13, for which the new port package:lang/gcc13[] has been created.
+GCC 11 and GCC 12 have been updated upstream and a new release of GCC 10 is planned.
+All corresponding ports now need to be updated.
+
+To ease the work of both ports maintainers and users, I plan to test and update together all the following changes:
+
+* updates of package:lang/gcc10[], package:lang/gcc11[], package:lang/gcc12[];
+* update of GCC_DEFAULT to 13;
+* enabling of .init_array and .fini_array on the production ports;
+* switching back from LTO_BOOTSTRAP to STANDARD_BOOTSTRAP on the production ports.
+
+This will provide the following advantages:
+
+* more testing with less exp-runs;
+* fewer builds for ports users.
diff --git a/website/content/en/status/report-2023-04-2023-06/ifapi.adoc b/website/content/en/status/report-2023-04-2023-06/ifapi.adoc
new file mode 100644
index 0000000000..8a9b22a242
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/ifapi.adoc
@@ -0,0 +1,17 @@
+=== Network Interface API (IfAPI)
+
+Link: +
+link:https://wiki.freebsd.org/projects/ifnet[Original project page] URL: link:https://wiki.freebsd.org/projects/ifnet[]
+
+Contact: Justin Hibbits <jhibbits@FreeBSD.org>
+
+Started back in 2014, the IfAPI (formerly DrvAPI) goal is to hide the man:ifnet[9] structure from network drivers.
+Instead, all accesses to members will go through accessor functions.
+This allows the network stack to be changed without recompiling drivers, as well as potentially allowing a single driver to support multiple versions of FreeBSD.
+
+As of now this goal has been achieved in the base system, but several ports need to be updated to use the IfAPI.
+There is a tool to automate most of the conversion, in [.filename]#tools/ifnet/convert_ifapi.sh#.
+Documentation is also forthcoming, but could use help on that.
+man:ifnet[9] needs a lot of cleanup, as even some information in it currently is out of date.
+
+Sponsor: Juniper Networks, Inc.
diff --git a/website/content/en/status/report-2023-04-2023-06/intro.adoc b/website/content/en/status/report-2023-04-2023-06/intro.adoc
new file mode 100644
index 0000000000..d88d819a89
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/intro.adoc
@@ -0,0 +1,10 @@
+Here is the second 2023 status report, with 37 entries.
+
+As you might notice, we have several more reports than last quarter.
+This is a great news and shows how much the FreeBSD community is active and always working on providing high quality software.
+
+In particular, please note that Summer has started and do not miss the amazing projects shared by our Google Summer of Code students.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2023-04-2023-06/kboot.adoc b/website/content/en/status/report-2023-04-2023-06/kboot.adoc
new file mode 100644
index 0000000000..c24745351d
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/kboot.adoc
@@ -0,0 +1,56 @@
+=== FreeBSD support on LinuxBoot
+
+Contact: Warner Losh <imp@bsdimp.com>
+
+Links: +
+link:https://www.linuxboot.org/[LinuxBoot Project] URL: link:https://www.linuxboot.org/[] +
+link:https://docs.google.com/presentation/d/1N5Jp6XzYWv9Z9RhhETC-e6tFkqRHvp-ldRDW_9h2JCw/edit?usp=sharing[BSDCan 2023 kboot talk slides] URL: link:https://docs.google.com/presentation/d/1N5Jp6XzYWv9Z9RhhETC-e6tFkqRHvp-ldRDW_9h2JCw/edit?usp=sharing[]
+
+LinuxBoot is an effort to create a clean, robust, auditable and repeatable boot firmware.
+What originally started as a specific project at Google has grown to encompass any boot environment that uses Linux to launch the final operating system.
+Many platforms now support this environment, and in some cases it is the only available boot environment.
+In addition, some embedded boxes have a LinuxBoot environment hard-coded that is quite hard to change, and being able to reboot into FreeBSD is desirable.
+
+The old Sony PlayStation 3 port used a boot loader called 'kboot' to boot the FreeBSD port from its Linux kernel (all predating the LinuxBoot project).
+That code has been greatly expanded, made generic with easily replaceable per-architecture plug ins.
+The normal FreeBSD [.filename]#/boot/loader# is built as a Linux binary that reads in the FreeBSD kernel, modules and tunables.
+It places them into memory as if it were running in a pre-boot environment, then loads that image into the Linux kernel with man:kexec_load[2] and does a special reboot to that image.
+For UEFI-enabled systems, it passes the UEFI memory table and pointer to UEFI runtime services to the new kernel.
+
+It supports loading files from the host's filesystem, from any man:loader[8]-supported filesystem on the host's block devices (including pools that span multiple devices), from ram disk images and from files downloaded over the network.
+Any mix of these is available.
+So, for example, configuration overrides can be loaded from the host's filesystem whilst the kernel loads from dedicated storage (say NVME) or a ram disk image.
+It supports a host console running over stdin/stdout.
+It supports explicit locations such as `/dev/nvme0ns1:/boot/loader/gerbil.conf` for where to load filesystems from.
+It supports ZFS boot environments, including the boot-once feature.
+
+Additional details about kboot, what it supports and some general background can be found in Warner's BSDcan talk (slides linked above).
+
+FreeBSD/aarch64 now can boot from Linux in a LinuxBoot environment, with support and functionality comparable to man:loader.efi[8].
+Memory layout passed in for GICv3 workarounds.
+Need patch for aarch64 kernel for the GICv3 workaround (link:https://reviews.freebsd.org/D40902[]).
+
+FreeBSD/amd64 support is in progress and is maybe 80% done.
+The amd64 boot environment places more requirements on the boot loader to provide data for the kernel than aarch64, due to amd64 being an older port.
+All sources for data in the BIOS environment had to be provided by the boot loader since the kernel had no access to them from long mode.
+While UEFI and ACPI provide ways for the kernel to get this data, much of the data must still be provided by the boot loader.
+The kernel panics during initialization since all these prerequisites have not been discovered and implemented.
+
+PowerPC builds, but nothing more of its state is known.
+Attempts to acquire a suitable Playstation 3 proved to be too time consuming for the author.
+
+==== Help Needed
+
+1. man:loader.kboot[8] needs to be written.
+It should document how to use [.filename]#loader.kboot#, how to create images, and the use cases that work today.
+2. Finish amd64 support.
+3. The current elf arch-specific metadata code is copied from efi.
+Unifying the kboot and efi copies is needed.
+While they are mostly the same, sharing is complicated by remaining compile-time differences.
+In addition, the build infrastructure makes sharing awkward.
+4. It would be nice to add riscv64 support.
+5. PowerPC testing (it has been untested since the refactoring started).
+6. Creating a script to repackage EDK-II image (say, from QEMU) as a linux-boot image with a Linux kernel built on FreeBSD for CI testing.
+7. Testing it from the coreboot LinuxBoot.
+
+Sponsored by: Netflix, Inc
diff --git a/website/content/en/status/report-2023-04-2023-06/kde.adoc b/website/content/en/status/report-2023-04-2023-06/kde.adoc
new file mode 100644
index 0000000000..63fdde9ef6
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/kde.adoc
@@ -0,0 +1,70 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] +
+link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation.
+The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack.
+
+==== Infrastructure
+
+Qt5 ports had various updates:
+
+* package:devel/qt5-webengine[] was repaired when building with Clang 16.
+This is in preparation for the upcoming release of FreeBSD 14.
+* package:devel/qt5-qmake[] was repaired to deal with an edge case where installing qmake on an otherwise Qt-less system would cause weird errors.
+
+Qt6 ports had various updates:
+
+* package:devel/qt6-tools[] was repaired when building with Clang 16.
+This is preparation for the upcoming release of FreeBSD 14.
+
+The package:accessibility/at-spi2-core[] port -- essential for accessible technologies on the desktop -- was updated to release 2.48.0.
+
+The package:accessibility/at-spi2-core[] port now has better support for non-X11 desktops.
+This is an improvement for Wayland-based systems.
+Thanks to Jan Beich for landing that.
+
+The package:graphics/poppler[] port -- a base for many PDF viewers -- was updated to 23.05.
+
+The package:ports-mgmt/packagekit-qt[] port is a new addition to the tree to pave the way for graphical package managers on FreeBSD.
+
+==== KDE Stack
+
+KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well.
+These (large) updates land shortly after their upstream release and are not listed separately.
+
+* KDE Frameworks updated to 5.105, .106 and .107.
+* KDE Gear updated to 23.04.0, then .1 and .2 with bugfixes.
+* KDE Plasma Desktop was updated to version 5.27.4, then .5 and .6 with bugfixes.
+
+==== Related Ports
+
+Deprecations:
+
+* package:graphics/ikona[], an icon-viewer written in Rust with Qt bindings, has been abandoned upstream.
+* package:polish/kadu[], a chat application once popular in Poland, is deprecated and upstream has disappeared.
+* package:sysutils/plasma5-ksysguard[], a system monitoring application, is deprecated upstream and will no longer update.
+
+Updates:
+
+* package:astro/kstars[], an interactive planetarium, was updated to release 3.6.4.
+* package:devel/qcoro[], a C++ coroutines implementation, was updated to 0.9.0.
+* package:devel/qtcreator[], an integrated development environment for Qt, C++, and more, was updated to release 10.0.2.
+* package:games/gcompris-qt[], an education suite for children aged 3-12, was updated to release 3.2.
+* package:graphics/kphotoalbum[], a photo album and display utility, was updated to release 5.10.0.
+* package:net-im/tokodon[], a Mastodon social network client, joins KDE Gear.
+* package:textproc/kdiff3[], a text-differencing utility, was updated to release 1.10.1.
+
+New Software:
+
+* package:devel/kommit[], a Git client, was added.
+It is a rename of previous package gitklient.
+* package:multimedia/kasts[] is a new podcast-listening and enjoyment application from the KDE community.
+* package:textproc/arianna[] is a mobile-oriented e-book reader from the KDE community that makes reading FreeBSD documentation a joy.
diff --git a/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc b/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc
new file mode 100644
index 0000000000..a359e0d1da
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc
@@ -0,0 +1,19 @@
+=== Linux compatibility layer update
+
+Links: +
+link:https://wiki.freebsd.org/Linuxulator[Linuxulator status Wiki page] URL: link:https://wiki.freebsd.org/Linuxulator[] +
+link:https://wiki.freebsd.org/LinuxApps[Linux app status Wiki page] URL: link:https://wiki.freebsd.org/LinuxApps[]
+
+Contact: Dmitry Chagin <dchagin@FreeBSD.org>
+
+The goal of this project is to improve FreeBSD's ability to execute unmodified man:linux[4] binaries.
+
+As of gitref:cbbac5609115[repository=src], preserving an fpu xsave state across signal delivery on amd64 is implemented.
+That makes it possible to run modern golang with preemptive scheduler on.
+
+The new facility to specify an alternate ABI root path was added to man:namei[9].
+Previously, to dynamically reroot lookups, every man:linux[4] syscall where path names translation is needed required a bit of ugly code and used `kern_alternate_path()` which does not properly resolve symlinks with leading `/` in the target.
+For now a non-native ABI (i.e., man:linux[4]) uses one call to `pwd_altroot()` during exec-time into that ABI to specify its root directory (e.g., [.filename]#/compat/ubuntu#) and forget about path names translation.
+That makes possible chroot into the Ubuntu compat without having to fix such symlinks by hand.
+
+In total, over 10 bugs were fixed; glibc-2.37 tests suite reports less than 70 failed tests.
diff --git a/website/content/en/status/report-2023-04-2023-06/lldb-kmod.adoc b/website/content/en/status/report-2023-04-2023-06/lldb-kmod.adoc
new file mode 100644
index 0000000000..af10d04ffe
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/lldb-kmod.adoc
@@ -0,0 +1,20 @@
+=== LLDB Kernel Module Improvement
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[GSoC Wiki Project] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[] +
+link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[Project Codebase] URL: link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[]
+
+Contact: Sheng-Yi Hong <aokblast@FreeBSD.org>
+
+FreeBSD project uses LLVM as its toolchain.
+The LLVM  project has bundled with a debugger called LLDB.
+In LLDB, the userspace debugging facilities has been well implemented.
+However, in the kernel space, there are still some works have to be done.
+One of the work is the kernel module debug facility for LLDB - that is, parse the loaded module data provided by the kernel core dump and loading the module objects.
+The goal is to implement such plugin for LLDB, and this is an ongoing GSoC Project for now.
+
+https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[Project Codebase] is the whole code of my work.
+
+Currently, this is still a work in progress and I am still debugging on it.
+
+Sponsor: The Google Summer of Code '23 program
diff --git a/website/content/en/status/report-2023-04-2023-06/maxcpu.adoc b/website/content/en/status/report-2023-04-2023-06/maxcpu.adoc
new file mode 100644
index 0000000000..3c0485946c
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/maxcpu.adoc
@@ -0,0 +1,18 @@
+=== Increasing MAXCPU
+
+Links: +
+link:https://reviews.freebsd.org/D36838[Review D36838: amd64: Bump MAXCPU to 1024 (from 256)] URL: https://reviews.freebsd.org/D36838[]
+
+Contact: Ed Maste <emaste@FreeBSD.org>
+
+The default amd64 and arm64 FreeBSD kernel configurations currently support a maximum of 256 CPUs.
+A custom kernel can be built with support for larger core counts by setting the `MAXCPU` kernel option.
+However, commodity systems with more than 256 CPUs are becoming available and will be increasingly common during FreeBSD 14's support lifecycle.
+We want to increase the default maximum CPU count to 1024 to support these systems "out of the box" on FreeBSD 14.
+
+A number of changes have been made to support a larger default `MAXCPU`, including fixing the userland maximum for `cpuset_t` at 1024.
+Changes have also been made to avoid static `MAXCPU`-sized arrays, replacing them with on-demand memory allocation.
+
+Additional work is required to continue reducing static allocations sized by `MAXCPU` and addressing scalability bottlenecks on very high core count systems, but the goal is to release FreeBSD 14 with a stable ABI and KBI with support for large CPU counts.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/mfsbsd.adoc b/website/content/en/status/report-2023-04-2023-06/mfsbsd.adoc
new file mode 100644
index 0000000000..b901fd6612
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/mfsbsd.adoc
@@ -0,0 +1,30 @@
+=== Integrate mfsBSD into the release building tools
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[Wiki Article] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[] +
+link:https://github.com/soobinrho/freebsd-src/tree/integrate-mfsBSD-building[Project repository (integrate-mfsBSD-building branch)] URL: link:https://github.com/soobinrho/freebsd-src/tree/integrate-mfsBSD-building[]
+
+Contact: Soobin Rho <soobinrho@FreeBSD.org>
+
+==== What is mfsBSD?
+
+"mfsBSD is a toolset to create small-sized but full-featured mfsroot based distributions of FreeBSD that store all files in memory (MFS) [Memory File System] and load from hard drive, usb storage device or optical media.
+It can be used for a variety of purposes, including diskless systems, recovery partitions and remotely overwriting other operating systems."
+
+mailto:mm@FreeBSD.org[Martin Matuska] is both the author of the link:https://people.freebsd.org/~mm/mfsbsd/mfsbsd.pdf[mfsBSD white paper] and the maintainer of the link:https://github.com/mmatuska/mfsbsd[mfsBSD repository].
+
+==== Purpose
+
+This project creates an additional target of the weekly snapshots of -current and -stable versions of mfsBSD images in the src/release makefile.
+Currently, only the release versions of mfsBSD images are produced, which means they tend to get out of sync with the tools in base.
+This project aims to address that problem.
+
+==== Location
+
+This is a GSoC 2023 (Google Summer of Code) project.
+As such, the official coding period is between May 29, 2023 and August 28, 2023.
+As a humble beginner in the open-source community, the author welcomes all comments / suggestions / pull requests in the project repository, which will be the location for all code throughout this period.
+
+Mentors: mailto:otis@FreeBSD.org[Juraj Lutter] and mailto:jrm@FreeBSD.org[Joseph Mingone]
+
+Sponsor: The Google Summer of Code '23 program
diff --git a/website/content/en/status/report-2023-04-2023-06/nvmf.adoc b/website/content/en/status/report-2023-04-2023-06/nvmf.adoc
new file mode 100644
index 0000000000..f9477918e4
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/nvmf.adoc
@@ -0,0 +1,40 @@
+=== NVMe over Fabrics
+
+Links: +
+link:https://github.com/bsdjhb/freebsd/tree/nvmf2[nvmf2 branch]	URL: link:https://github.com/bsdjhb/freebsd/tree/nvmf2[]
+
+Contact: John Baldwin <jhb@FreeBSD.org>
+
+NVMe over Fabrics enables communication with a storage device using the NVMe protocol over a network fabric.
+This is similar to using iSCSI to export a storage device over a network using SCSI commands.
+
+NVMe over Fabrics currently defines network transports for Fibre Channel, RDMA, and TCP.
+
+The work in the nvmf2 branch includes a userland library ([.filename]#lib/libnvmf#) which contains an abstraction for transports and an implementation of
+a TCP transport.
+It also includes changes to man:nvmecontrol[8] to add 'discover', 'connect', and 'disconnect' commands to manage connections to a remote controller.
+
+The branch also contains an in-kernel Fabrics implementation.
+[.filename]#nvmf_transport.ko# contains a transport abstraction that sits in between the nvmf host (initiator in SCSI terms) and the individual transports.
+[.filename]#nvmf_tcp.ko# contains an implementation of the TCP transport layer.
+[.filename]#nvmf.ko# contains an NVMe over Fabrics host (initiator) which connects to a remote controller and exports remote namespaces as disk devices.
+Similar to the man:nvme[4] driver for NVMe over PCI-express, namespaces are exported via [.filename]#/dev/nvmeXnsY# devices which only support simple operations, but are also exported as ndaX disk devices via CAM.
+Unlike man:nvme[4], man:nvmf[4] does not support the man:nvd[4] disk driver.
+man:nvmecontrol[8] can be used with remote namespaces and remote controllers, for example to fetch log pages, display identify info, etc.
+
+Note that man:nvmf[4] is currently a bit simple and some error cases are still a TODO.
+If an error occurs, the queues (and backing network connections) are dropped, but the devices stay around, with I/O requests paused.
+`nvmecontrol reconnect` can be used to connect a new set of network connections to resume operation.
+Unlike iSCSI which uses a persistent daemon (man:iscsid[8]) to reconnect after an error, reconnections must be made manually.
+
+The current code is very new and likely not robust.
+It is certainly not ready for production use.
+Experienced users who do not mind all their data vanishing in a puff of smoke after a kernel panic, and who have an interest in NVMe over Fabrics, can start testing it at their own risk.
+
+The next main task is to implement a Fabrics controller (target in SCSI language).
+Probably a simple one in userland first followed by a "real" one that offloads the data handling to the kernel but is somewhat integrated with man:ctld[8] so that individual disk devices can be exported via iSCSI or NVMe, or via both using a single config file and daemon to manage all of that.
+This may require a fair bit of refactoring in ctld to make it less iSCSI-specific.
+Working on the controller side will also validate some of the currently under-tested API design decisions in the transport-independent layer.
+I think it probably does not make sense to merge any of the NVMe over Fabrics changes into the tree until after this step.
+
+Sponsored by: Chelsio Communications
diff --git a/website/content/en/status/report-2023-04-2023-06/openssl3.adoc b/website/content/en/status/report-2023-04-2023-06/openssl3.adoc
new file mode 100644
index 0000000000..c939fdb790
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/openssl3.adoc
@@ -0,0 +1,38 @@
+=== OpenSSL 3 in base
+
+Links: +
+link:https://www.openssl.org/source/[OpenSSL Downloads] URL: link:https://www.openssl.org/source/[] +
+link:https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/[OpenSSL 3.0 Has Been Released!] URL: link:https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/[] +
+link:https://www.openssl.org/docs/man3.0/man1/openssl-fipsinstall.html[openssl-fipsinstall] URL: link:https://www.openssl.org/docs/man3.0/man1/openssl-fipsinstall.html[]
+
+Contact: Pierre Pronchery <pierre@freebsdfoundation.org>
+
+Pierre has been tasked with importing OpenSSL 3 into the base system.
+
+OpenSSL is a library for general-purpose cryptography and secure communication.
+It provides an open source implementation of the SSL and TLS network protocols, which are widely used in applications such as e-mail, instant messaging, Voice over IP (VoIP), or more prominently the global Web (aka HTTPS).
+Assuming that the Apache and nginx web servers use OpenSSL, their combined market share for web traffic exceeds 50%, cementing the leadership and critical importance of OpenSSL as part of the infrastructure of the Internet.
+
+Since its initial release in August 2016, the 1.1 branch of OpenSSL has been adopted by most Linux and BSD systems, while remaining supported by the upstream maintainers through an LTS (long term support) policy.
+However, official support is planned to end in the middle of September this year, and it became urgent and necessary to consider adopting its successor for LTS, the 3.0 branch.
+
+OpenSSL has largely outgrown its ancestor SSLeay, now shipping over half a million single lines of code (SLOC) split in over two thousand files.
+Perhaps as a consequence, its build system is relatively complex and normally requires Perl, which was removed from base more than twenty years ago for FreeBSD 5.0-RELEASE.
+Thankfully however, it was possible to import and setup OpenSSL 3.0.9 the FreeBSD way, and it is now part of the base system as planned for FreeBSD 14.0-RELEASE.
+
+To describe OpenSSL 3 as a major release is an understatement.
+First, its problematic licensing model has finally been solved, with a complete switch to the Apache License 2.0.
+Then, OpenSSL 3 introduces the concept of provider modules.
+While obsolete cryptographical algorithms have been isolated to a _legacy_ module, it is also possible to restrict the implementation to the standards part of link:https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards[FIPS] with the _fips_ module.
+The latter can then benefit from a dedicated certification process, and be validated officially (like the 3.0.8 release at the time of writing).
+
+Moreover, the updated library comes with a version bump, as applications using OpenSSL 1.1 need to be recompiled to use 3.0.
+Many API functions have been deprecated and replaced with newer, more generic alternatives, however it is still possible to explicitly request older APIs and have OpenSSL 3 expose them accordingly.
+This possibility has been leveraged in FreeBSD to help with the transition, where a number of libraries and applications have simply been configured to request the OpenSSL 1.1 API.
+These components will be updated progressively over time in order to consume OpenSSL 3's native API instead.
+
+While there is a known performance impact associated with the update when consuming small input block sizes, it was found to be marginal when working with blocks of 1 KB and above.
+Another challenge lies with the FIPS provider module, which currently requires some manual steps in order to have it working.
+We are currently looking for a solution to ship FreeBSD with a functional FIPS provider by default.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/openstack.adoc b/website/content/en/status/report-2023-04-2023-06/openstack.adoc
new file mode 100644
index 0000000000..b95a65099c
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/openstack.adoc
@@ -0,0 +1,30 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[]
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+This project aims to port key OpenStack components such as keystone, nova, and neutron, so that FreeBSD can function as an OpenStack host.
+
+We started porting `nova-novncproxy` and `nova-serialproxy` to increase the ways to access the instance console.
+To lower the threshold for people who want to give it a try on the project, we also migrated our development environment from a physical machine to a virtual one.
+There is still a problem running bhyve VMs on top of Linux KVM.
+A detailed writeup for the issue can be found link:https://hackmd.io/@starbops/SkdJON2un[here].
+Other achievements include:
+
+* Sorting out network connectivity issues inside the instances
+* Able to spawn multiple instances
+* Porting from Python 3.8 to 3.9.
+
+In the next quarter, we will continue working on the console proxy services to make the overall workflow more fluent.
+
+The step-by-step documents for constructing a POC site can also be found link:https://github.com/openstack-on-freebsd/docs[in the `docs` repository].
+The patched version of each OpenStack component is under the same GitHub organization.
+
+People interested in helping with the project can first help check the documentation by following the installation guide.
+Feedback and help are always welcome.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/pf.adoc b/website/content/en/status/report-2023-04-2023-06/pf.adoc
new file mode 100644
index 0000000000..0e572983cf
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/pf.adoc
@@ -0,0 +1,45 @@
+=== Pf Improvements
+
+Links: +
+link:https://reviews.freebsd.org/D40911[D40911] URL: link:https://reviews.freebsd.org/D40911[] +
+link:https://reviews.freebsd.org/D40861[D40861] URL: link:https://reviews.freebsd.org/D40861[] +
+link:https://reviews.freebsd.org/D40862[D40862] URL: link:https://reviews.freebsd.org/D40862[] +
+link:https://reviews.freebsd.org/D40863[D40863] URL: link:https://reviews.freebsd.org/D40863[] +
+link:https://reviews.freebsd.org/D40864[D40864] URL: link:https://reviews.freebsd.org/D40864[] +
+link:https://reviews.freebsd.org/D40865[D40865] URL: link:https://reviews.freebsd.org/D40865[] +
+link:https://reviews.freebsd.org/D40866[D40866] URL: link:https://reviews.freebsd.org/D40866[] +
+link:https://reviews.freebsd.org/D40867[D40867] URL: link:https://reviews.freebsd.org/D40867[] +
+link:https://reviews.freebsd.org/D40868[D40868] URL: link:https://reviews.freebsd.org/D40868[] +
+link:https://reviews.freebsd.org/D40869[D40869] URL: link:https://reviews.freebsd.org/D40869[] +
+link:https://reviews.freebsd.org/D40870[D40870] URL: link:https://reviews.freebsd.org/D40870[]
+
+Contact: Kajetan Staszkiewicz <vegeta@tuxpowered.net> +
+Contact: Naman Sood <naman@freebsdfoundation.org> +
+Contact: Kristof Provost <kp@FreeBSD.org>
+
+man:pf[4] is one of the firewalls included in FreeBSD, and is probably the most popular.
+pf was created by the OpenBSD project and subsequently ported to FreeBSD.
+
+==== Backport OpenBSD Syntax
+
+Kajetan introduced the OpenBSD syntax of "scrub" operations in "match" and "pass" rules.
+Existing rules remain supported, but now OpenBSD style "scrub" configuration is also supported.
+
+==== pfsync Protocol Versioning
+
+The man:pfsync[4] protocol version can now be configured, allowing for protocol changes while still supporting state synchronisation between disparate kernel versions.
+The primary benefit is to allow protocol changes enabling new functionality.
+
+==== pfsync: Transport over IPv6
+
+pfsync traffic can now be carried over IPv6 as well.
+Naman finished the work started by Luiz Amaral.
+
+==== SCTP
+
+There is work in progress to support SCTP in pf.
+That support includes filtering on port numbers, state tracking, pfsync failover and returning ABORT chunks for rejected connections.
+
+Sponsor: InnoGames GmbH +
+Sponsor: Orange Business Services +
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/pkgbase.live.adoc b/website/content/en/status/report-2023-04-2023-06/pkgbase.live.adoc
new file mode 100644
index 0000000000..b2a8717328
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/pkgbase.live.adoc
@@ -0,0 +1,37 @@
+=== PkgBase.live
+
+Links: +
+link:https://alpha.pkgbase.live/[Website] URL: link:https://alpha.pkgbase.live/[] +
+link:https://codeberg.org/pkgbase[Source] URL: link:https://codeberg.org/pkgbase[]
+
+Contact: Mina Galić <freebsd@igalic.co>
+
+PkgBase.live, an unofficial repository for the FreeBSD link:https://wiki.freebsd.org/PkgBase[PkgBase project], is back alive.
+
+As a service, PkgBase.live was inspired by link:https://up.bsd.lv/[], which provided man:freebsd-update[8] for STABLE and CURRENT branches.
+up.bsd.live itself has gone on hiatus, so it was all the more reason to bring back PkgBase.live.
+
+Right now, we provide builds for:
+
+- FreeBSD 13.2-RELEASE
+- FreeBSD 13-STABLE
+- FreeBSD 14-CURRENT
+
+each for the following platforms:
+
+- amd64
+- aarch64
+- armv7
+- i386
+
+You may notice that RISCv64 is gone for now.
+
+The hardware is a powerful VPS in Vultr.
+The server and the jails running build jobs and serving packages are "self-hosting", meaning they were installed and are kept up-to-date with PkgBase.
+
+Because we have not figured out yet how to configure Vultr's IPv6 in FreeBSD jails, PkgBase.live is not available over IPv6 for now.
+If you have experience with that, please contact us!
+
+Along with users and testers, we still link:https://alpha.pkgbase.live/howto/howdo.html[highly encourage copy-cats].
+
+Hardware for PkgBase is kindly sponsored by a member of the FreeBSD community.
diff --git a/website/content/en/status/report-2023-04-2023-06/portmgr.adoc b/website/content/en/status/report-2023-04-2023-06/portmgr.adoc
new file mode 100644
index 0000000000..8e420d374d
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/portmgr.adoc
@@ -0,0 +1,29 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+elow is what happened in this quarter.
+
+Currently there are just over 34,400 ports in the Ports Tree.
+There are currently 3,019 open ports PRs of which 746 are unassigned.
+This quarter saw 10,439 commits on the `main` branch by 151 committers and 745 commits on the `2023Q2` branch by 55 committers.
+Compared to the previous quarter, this means a slight increase in the number of ports, a tiny decrease in the number of open PRs, and a fair increase in the number of ports commits.
+
+During this quarter, we welcomed back Tom Judge (tj@) and said goodbye to Steve Wills (swills@).
+Steve was also on portmgr.
+As part of the portmgr lurker program, we welcomed Ronald Klop (ronald@), Renato Botelho (garga@), and Matthias Andree (mandree@).
+
+Portmgr has resumed work on introducing sub-packages into the Tree, but various things still need to be fleshed out.
+
+On the software side, pkg was updated to 1.19.2, Firefox to 114.0.2, Chromium to 114.0.5735.198, and KDE Gear to 23.04.2.
+During this quarter, antoine@ ran 23 exp-runs to test package updates, bump CPU_MAXSIZE to 1024, fix armv7 failures for devel/cmake-core and add --auto-features=enabled to USES=meson
+Lastly, the Ports Tree was updated to support LLVM 16 and OpenSSL 3 in FreeBSD-CURRENT.
diff --git a/website/content/en/status/report-2023-04-2023-06/pot.adoc b/website/content/en/status/report-2023-04-2023-06/pot.adoc
new file mode 100644
index 0000000000..97966e5c34
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/pot.adoc
@@ -0,0 +1,25 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+During this quarter, link:https://github.com/bsdpot/pot/releases/tag/0.15.5[Pot 0.15.5] was released, containing a number of bugfixes and link:https://github.com/bsdpot/pot/pull/263[features to set attributes (i.e. jail sysctl variables)] from various contributors.
+It will be available in the 2023Q3 quarterly package set.
+
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+All Potluck containers have been rebuilt as FreeBSD 13.2 based images and are signed with link:https://github.com/bsdpot/pot/pull/242[Pot signify] now.
+
+link:https://honeyguide.eu/posts/ansible-pot-foundation/[A Beginner's Guide to Building a Virtual Datacenter on FreeBSD with Ansible, Pot and More] has been written, explaining how a complex environment based on Pot and Potluck can be deployed with Ansible playbooks, including example nodes like MariaDB, Prometheus, Grafana, nginx, OpenLDAP or Traefik and container orchestration managed by Nomad and Consul.
+
+A link:https://github.com/hashicorp/nomad/pull/13343[patch by the pot team] to improve Nomad security, a scheduler and orchestrator which supports Pot through package:sysutils/nomad-pot-driver[], has been accepted upstream and will be part of Nomad 1.6.0.
+
+As always, feedback and patches are welcome.
+
+Sponsor: Honeyguide Group
diff --git a/website/content/en/status/report-2023-04-2023-06/puppet.adoc b/website/content/en/status/report-2023-04-2023-06/puppet.adoc
new file mode 100644
index 0000000000..031d5cc981
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/puppet.adoc
@@ -0,0 +1,21 @@
+=== Puppet
+
+Links: +
+link:https://puppet.com/docs/puppet/latest/puppet_index.html[Puppet] URL: link:https://puppet.com/docs/puppet/latest/puppet_index.html[] +
+
+Contact: Puppet Team <puppet@FreeBSD.org>
+
+Puppet is a Free Software configuration management tool, composed of a source of trust (Puppet Server) that describes the expected configuration of machines with a domain-specific language, and an agent (Puppet Agent) on each node which enforces that the actual configuration matches the expected one.
+An optional database (PuppetDB) can be setup for reporting and describing advanced schemas where the configuration of a machine depends on the configuration of another one.
+
+The Puppet team is maintaining ports for Puppet and related tools.
+
+Puppet 8 has been recently released and has been added to the ports tree.
+
+Puppet 6 has reached End of Life and has been deprecated.
+It is now expired.
+Users of Puppet 6 are therefore advised to update to Puppet 7 or Puppet 8.
+
+For now, Puppet 7 remains the default Puppet version for ports depending on Puppet.
+The Puppet Community is hard at work making sure the various Puppet modules work with the latest code and at the time of writing this report, updating to Puppet 8 may be challenging.
+The situation is getting better every day, and we expect to switch to Puppet 8 as the default version of Puppet in a few months, when the wave of module updates is finished.
diff --git a/website/content/en/status/report-2023-04-2023-06/releng.adoc b/website/content/en/status/report-2023-04-2023-06/releng.adoc
new file mode 100644
index 0000000000..6cbf1a8cb6
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/releng.adoc
@@ -0,0 +1,24 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[] +
+link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the second quarter of 2023, the Team continued work on 13.2-RELEASE.
+The 13.2 cycle had closely followed the set schedule, with the addition of three additional RC builds at the end, and the final RELEASE build and announcement in mid-April.
+
+In coordination with various teams within the Project management, the FreeBSD Release Engineering Team reconsidered the original schedule for the upcoming 14.0-RELEASE, primarily due to work that was in progress.
+The updated schedule was discussed and adjusted slightly to account for some concerns, and ultimately published on the FreeBSD Project website.
+The new schedule targets 14.0-RELEASE for October, 2023.
+
+The Team continued providing weekly development snapshot builds for the `main`, `stable/13`, and `stable/12` branches.
+Note, there will no longer be snapshot builds against `stable/12` moving forward.
+
+Sponsor: Tarsnap +
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/service-jails.adoc b/website/content/en/status/report-2023-04-2023-06/service-jails.adoc
new file mode 100644
index 0000000000..5a66d24a20
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/service-jails.adoc
@@ -0,0 +1,26 @@
+=== Service Jails -- automatic jailing of rc.d services
+
+Links: +
+link:https://reviews.freebsd.org/D40369[D40369: Extend /usr/bin/service with the possibility to set ENV vars] URL: link:https://reviews.freebsd.org/D40369[] +
+link:https://reviews.freebsd.org/D40370[D40370: Infrastructure for automatic jailing of rc.d-services] URL: link:https://reviews.freebsd.org/D40370[] +
+link:https://reviews.freebsd.org/D40371[D40371: automatic service jails: some setup for full functionality of the services in automatic service jails] URL: link:https://reviews.freebsd.org/D40371[]
+
+Contact: Alexander Leidinger <netchild@FreeBSD.org>
+
+Service jails extend the man:rc[8] system to allow automatic jailing of rc.d services.
+A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, ...) by default.
+Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (man:vmm[4]).
+
+If you want to put e.g. local_unbound into a service jail and allow IPv4 and IPv6 access, simply change man:rc.conf[5] to have:
+----
+local_unbound_svcj_options=net_basic
+local_unbound_svcj=YES
+----
+
+While this does not have the same security benefits of a manual jail setup with a separate filesystem and IP/VNET, it is much easier to setup, while providing some of the security benefits of a jail like hiding other processes of the same user.
+
+The patches in the links are a rewrite of link:https://lists.freebsd.org/pipermail/freebsd-jail/2019-February/003710.html[what I presented in 2019].
+The main difference is that an ENV variable is used to do more rational tracking and as such, requires a change to man:service[8].
+
+My intent is to commit link:https://reviews.freebsd.org/D40369[D40369] before the branch of `stable/14`.
+I will not commit link:https://reviews.freebsd.org/D40370[D40370] or link:https://reviews.freebsd.org/D40371[D40371] before 14.0 is released and both will benefit from more eyes.
diff --git a/website/content/en/status/report-2023-04-2023-06/simd.adoc b/website/content/en/status/report-2023-04-2023-06/simd.adoc
new file mode 100644
index 0000000000..682724a37a
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/simd.adoc
@@ -0,0 +1,23 @@
+=== SIMD enhancements for amd64
+
+Links: +
+link:https://reviews.freebsd.org/D40693[SIMD dispatch framework draft] URL: link:https://reviews.freebsd.org/D40693[] +
+link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt[Project proposal] URL: link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt[]
+
+Contact: Robert Clausecker <clausecker@FreeBSD.org>
+
+SIMD instruction set extensions such as SSE, AVX, and NEON are ubiquitous on modern computers and offer performance advantages for many applications.
+The goal of this project is to provide SIMD-enhanced versions of common libc functions (mostly those described in man:string[3]), speeding up most C programs.
+
+For each function optimised, up to four implementations will be provided:
+
+ * a *scalar* implementation optimised for amd64, but without any SIMD usage,
+ * a *baseline* implementation using SSE and SSE2 or alternatively an *x86-64-v2* implementation using all SSE extensions up to SSE4.2,
+ * an *x86-64-v3* implementation using AVX and AVX2, and
+ * an *x86-64-v4* implementation using AVX-512F/BW/CD/DQ.
+
+Users will be able to select which level of SIMD enhancements to use by setting the `AMD64_ARCHLEVEL` environment variable.
+
+While the current project only concerns amd64, the work may be expanded to other architectures like arm64 in the future.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-04-2023-06/squashfs.adoc b/website/content/en/status/report-2023-04-2023-06/squashfs.adoc
new file mode 100644
index 0000000000..874062ac88
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/squashfs.adoc
@@ -0,0 +1,20 @@
+=== SquashFS port for FreeBSD kernel
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[Wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[] +
+link:https://github.com/Mashijams/freebsd-src/tree/gsoc/squashfs[Source code] URL:  link:https://github.com/Mashijams/freebsd-src/tree/gsoc/squashfs[]
+
+Contact: Raghav Sharma <raghav@FreeBSD.org>
+
+SquashFS is a read-only file system that lets you compress whole file systems or single directories very efficiently.
+Support for it has been built into the Linux kernel since 2009 and is very common in embedded Linux distributions.
+The goal of this project is to add SquashFS support for the FreeBSD kernel, with the aim of being able to boot FreeBSD from an in-memory SquashFS file system.
+
+Currently, the driver is compatible with the 13.2 FreeBSD release.
+The driver is able to correctly parse the SquashFS disk file with working man:mount[8] support.
+Linux SquashFS supports many compression options like zstd, lzo2, zlib, etc... based on the user's preference, and of course, our driver supports all those compressions as well.
+
+Planned future work includes adding directories, files, extended attributes, and symlinks read support.
+The project is still a work in progress under the mentorship from mailto:chuck@FreeBSD.org[Chuck Tuffli] and is expected to complete by the end of the Google Summer of Code program.
+
+Sponsor: The Google Summer of Code 2023 program
diff --git a/website/content/en/status/report-2023-04-2023-06/wazuh.adoc b/website/content/en/status/report-2023-04-2023-06/wazuh.adoc
new file mode 100644
index 0000000000..9f75482dba
--- /dev/null
+++ b/website/content/en/status/report-2023-04-2023-06/wazuh.adoc
@@ -0,0 +1,39 @@
+=== Wazuh on FreeBSD
+
+Links: +
+link:https://www.wazuh.com/[Wazuh] URL: link:https://www.wazuh.com/[]
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+Wazuh is a free and open source platform used for threat prevention, detection, and response.
+It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments.
+
+The Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents.
+Wazuh features include full integration with https://www.elastic.co/elastic-stack/[Elastic Stack] and https://opensearch.org/[OpenSearch], providing a search engine and data visualization tool through which users can navigate security alerts.
+
+Wazuh porting to FreeBSD was started by mailto:m.muenz@gmail.com[Michael Muenz].
+His first Wazuh addition to the ports tree was package:security/wazuh-agent[] in September 2021.
+In July 2022, I took maintainership of this port and started porting other Wazuh components.
+
+Currently, all Wazuh components are ported or adapted: package:security/wazuh-manager[], package:security/wazuh-agent[], package:security/wazuh-server[], package:security/wazuh-indexer[], and package:security/wazuh-dashboard[].
+
+On FreeBSD, package:security/wazuh-manager[] and package:security/wazuh-agent[] are compiled from Wazuh source code.
+package:security/wazuh-indexer[] is an adapted package:textproc/opensearch[] used for storing agents data.
+package:security/wazuh-server[] includes FreeBSD-oriented adaptions to configuration files.
+Runtime dependencies comprise package:security/wazuh-manager[], package:sysutils/beats8[] (filebeat), and package:sysutils/logstash8[].
+package:security/wazuh-dashboard[] uses an adapted package:textproc/opensearch-dashboards[] and the wazuh-kibana-app plugin generated from wazuh-kibana-app source code for FreeBSD.
+
+The main goal of this work is enhancing visibility of FreeBSD as a useful platform for information security or cybersecurity.
+
+Additionally, you can easily test a Wazuh single-node infrastructure (All-in-one) using link:https://github.com/alonsobsd/wazuh-makejail[] or link:https://github.com/AppJail-makejails/wazuh[] from link:https://github.com/DtxdF/AppJail[AppJail].
+AppJail is a good tool for managing jail containers from the command line.
+
+People interested in helping with the project are welcome.
+
+Current version: 4.4.4
+
+TODO
+
+* Add Wazuh cluster-mode infrastructure makejail (Work in progress)
+* Add FreeBSD to platforms officially supported by Wazuh Inc; see link:https://github.com/wazuh/wazuh-kibana-app/pull/5413[]
+* Add FreeBSD SCA Policy (Work in progress)
diff --git a/website/content/en/status/report-2023-07-2023-09/_index.adoc b/website/content/en/status/report-2023-07-2023-09/_index.adoc
new file mode 100644
index 0000000000..4287d0b3fb
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/_index.adoc
@@ -0,0 +1,212 @@
+---
+title: "FreeBSD Status Report Third Quarter 2023"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2023-07-2023-09
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+'''
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+{projects-desc}
+
+include::{reports-path}/desktop-convenience.adoc[]
+
+'''
+
+include::{reports-path}/lldb-kmod.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+'''
+
+include::{reports-path}/openssl3.adoc[]
+
+'''
+
+include::{reports-path}/login_classes.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+'''
+
+include::{reports-path}/ufs_snapshots.adoc[]
+
+'''
+
+include::{reports-path}/squashfs.adoc[]
+
+'''
+
+include::{reports-path}/process_visibility.adoc[]
+
+'''
+
+include::{reports-path}/linuxulator.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+'''
+
+include::{reports-path}/dpaa2.adoc[]
+
+'''
+
+include::{reports-path}/simd.adoc[]
+
+'''
+
+include::{reports-path}/mfsbsd.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+'''
+
+include::{reports-path}/openstack.adoc[]
+
+'''
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/ec2.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+'''
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-online-editor.adoc[]
+
+'''
+
+include::{reports-path}/expert-system.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/pantheon.adoc[]
+
+'''
+
+include::{reports-path}/office.adoc[]
+
+'''
+
+include::{reports-path}/wifibox.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/valgrind.adoc[]
+
+'''
+
+include::{reports-path}/gitlab.adoc[]
+
+'''
+
+include::{reports-path}/portoptscli.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+'''
+
+include::{reports-path}/bsd-cafe.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2023-07-2023-09/azure.adoc b/website/content/en/status/report-2023-07-2023-09/azure.adoc
new file mode 100644
index 0000000000..4fabe12eee
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/azure.adoc
@@ -0,0 +1,56 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+
+In this quarter, we have worked mainly on ARM64 architecture support and building and publishing both UFS and ZFS based images to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+There are some testing images available in the project's testing public gallery, named `FreeBSDCGTest-d8a43fa5-745a-4910-9f71-0c9da2ac22bf`:
+
+* FreeBSD-CURRENT-testing
+* FreeBSD-CURRENT-gen2-testing
+* FreeBSD-CURRENT-arm64-testing
+* FreeBSD-CURRENT-zfs-testing
+* FreeBSD-CURRENT-zfs-gen1-testing
+
+To use them, when creating a virtual machine:
+
+. In `Select an Image` step, choose `Community Images` in `Other items`
+. Search `FreeBSD`
+
+We are aiming to provide all those images for 14.0-RELEASE.
+
+Work in progress tasks:
+
+* Automating the image building and publishing process and merge to src/release/.
+* Building and publishing all supported VM images to Azure Marketplace
+* Building and publishing snapshot builds to Azure community gallery
+
+The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+
+Wei Hu and Souradeep Chakrabarti have fixed several critical bugs in arm64:
+
+* https://bugs.freebsd.org/267654
+* https://bugs.freebsd.org/272461
+* https://bugs.freebsd.org/272666
+
+The root cause was identified and fixed in link:https://cgit.freebsd.org/src/commit/?id=e7a9817b8d328dda04069b65944ce2ed6f54c6f0[e7a9817b8d32: Hyper-V: vmbus: implementat bus_get_dma_tag in vmbus]
+
+And continue working on improving Microsoft Azure Network Adapter (MANA) support.
+
+Open tasks:
+
+* Update FreeBSD related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Support FreeBSD in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+* Update link:https://www.freshports.org/sysutils/azure-agent[Azure agent port] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2023-07-2023-09/bsd-cafe.adoc b/website/content/en/status/report-2023-07-2023-09/bsd-cafe.adoc
new file mode 100644
index 0000000000..5b92d195ee
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/bsd-cafe.adoc
@@ -0,0 +1,41 @@
+=== Introducing the BSD Cafe project
+
+Links: +
+link:https://wiki.bsd.cafe/[BSD Cafe project homepage] URL: link:https://wiki.bsd.cafe/[] +
+link:https://mastodon.bsd.cafe/[BSD Cafe Mastodon instance] URL: link:https://mastodon.bsd.cafe/[]
+
+Contact: Stefano Marinelli <stefano@dragas.it>
+
+We are thrilled to unveil the inaugural component of the BSD Cafe project!
+
+Months ago, when I first registered the link:https://bsd.cafe/[bsd.cafe] domain, I envisioned a themed bar where friends, acquaintances, and patrons could gather for casual conversations about ++*++BSD systems, Linux, and open-source technology.
+Just like any bar, our discussions can encompass a wide array of topics, all while maintaining a spirit of mutual respect.
+
+BSD Cafe is poised to become a hub for a variety of tools and services, all powered by ++*++BSD.
+
+Our initial offering is a brand-new instance of link:https://joinmastodon.org/[Mastodon] (open-source
+microblogging software and service), serving as a gateway to the fediverse -- a federation of services, many of which use the link:https://www.w3.org/TR/activitypub[ActivityPub] decentralised social networking protocol.
+Registration is now open.
+The server operates under clearly defined guidelines that promote positive conduct and unequivocally prohibit any form of hate.
+Inclusiveness, respect, and constructive dialogue stand as the cornerstones of this instance.
+
+Our primary server is currently hosted in Finland on a small VM, running on FreeBSD.
+Services are partitioned into VNET jails, interconnected within a local area network through a dedicated bridge.
+Additionally, we implement a VPN system and have the flexibility to migrate individual jails to more robust machines.
+
+For multimedia data and cache hosting, we employ a separate physical server (also FreeBSD-based, within a jail), fronted by Cloudflare.
+The goal here is to cache and geodistribute data, effectively reducing network congestion on the main VPS.
+
+Our reverse proxy (frontend), mail server, media server, and the instance itself are all accessible via IPv6.
+
+At its inception, this Mastodon instance was devoid of preloaded content.
+Our intention is for it to grow organically, based on the interests and followers of its users.
+At this stage, we have refrained from preemptive blocks.
+We strongly encourage users to promptly report anything that they believe requires attention.
+
+We invite you to join us at link:https://mastodon.bsd.cafe/[] in order to cultivate a community that values constructive interactions and embraces inclusiveness -- a secure and serene space meant for all.
+
+Furthermore, we have established a website at link:https://wiki.bsd.cafe/[], which will provide an overview of our tools, services, rules, uptime, and more.
+
+Recently, a Miniflux installation has been performed, so the BSD Cafe users can use it as a personal RSS Feed Reader.
+More information: link:https://wiki.bsd.cafe/miniflux-bsd-cafe[].
diff --git a/website/content/en/status/report-2023-07-2023-09/ci.adoc b/website/content/en/status/report-2023-07-2023-09/ci.adoc
new file mode 100644
index 0000000000..b237cada8e
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/ci.adoc
@@ -0,0 +1,50 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://https://tinderbox.freebsd.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the third quarter of 2023, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* Add jobs for stable/14 branch
+* Update the link:https://tinderbox.freebsd.org["Tinderbox" view] of the CI results, now includes test results and the "starting point" of the current failing or unstable series.
+  * This is mainly done by the Foundation intern, Yan-Hao Wang. His other contributions are in the other entry of this report.
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing and pull/merged-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+  * Proof of concept system is in progress.
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Improving the hardware test lab and adding more hardware for testing
+* Merge link:https://reviews.freebsd.org/D38815[]
+* Merge link:https://reviews.freebsd.org/D36257[]
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-07-2023-09/core.adoc b/website/content/en/status/report-2023-07-2023-09/core.adoc
new file mode 100644
index 0000000000..e77d53003e
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/core.adoc
@@ -0,0 +1,41 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== Demise of Hans Petter Selasky
+
+The FreeBSD Core Team would like to thank Hans Petter Selasky for his years of service.
+We were saddened by his death and joined the community in mourning.
+
+link:https://lists.freebsd.org/archives/freebsd-announce/2023-July/000076.html[In Memoriam].
+
+==== Meetings with The FreeBSD Foundation
+
+The Core Team and The FreeBSD Foundation continue to meet to discuss the next steps to take for the management, development, and future of FreeBSD.
+The Core Team had two meetings with the Board of Directors, and employees of, the Foundation.
+They discussed how the Foundation can help the Core Team and the Project in general.
+
+==== Portmgr termlimits
+
+The Core Team discussed with the Ports Management Team the introduction of a time limit in which a developer can belong to the team.
+The proposal was approved by the Ports Management Team and will take effect at the beginning of 2024, with regular lurker programs to have a steady stream of new Ports Management Team members.
+
+==== Deprecation of 32-bit platforms for FreeBSD 15
+
+Work is underway to mark support for 32-bit platforms as "deprecated" for FreeBSD 15.
+
+==== Matrix IM
+
+The testing of the Matrix instance and the Element-web client is still in progress.
+
+The beta is planned to be released after EuroBSDCon in September.
+
+==== Improve Commit Bit Expiration Policy
+
+The Core Team will clarify how to update the PGP key once a developer has become Alumni.
+
+==== EuroBSDCon
+
+Core Team members met with the FreeBSD Foundation in Coimbra during EuroBSDcon to discuss the direction of the Project.
diff --git a/website/content/en/status/report-2023-07-2023-09/desktop-convenience.adoc b/website/content/en/status/report-2023-07-2023-09/desktop-convenience.adoc
new file mode 100644
index 0000000000..f20a86311e
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/desktop-convenience.adoc
@@ -0,0 +1,25 @@
+=== Filling gaps in the FreeBSD desktop experience
+
+Links: +
+link:https://github.com/outpaddling/qmediamanager[External media manager] URL: link:https://github.com/outpaddling/qmediamanager[] +
+link:https://github.com/outpaddling/devd-mount[devd-based automounter] URL: link:https://github.com/outpaddling/devd-mount[] +
+link:https://github.com/outpaddling/npmount[SUID mount tool] URL: link:https://github.com/outpaddling/npmount[] +
+link:https://github.com/outpaddling/freebsd-update-notify[Popup notification for updates] URL: link:https://github.com/outpaddling/freebsd-update-notify[]
+
+Contact: Jason Bacon <jwb@FreeBSD.org>
+
+The package:sysutils/desktop-installer[] port, available for over a decade now, quickly configures a bare FreeBSD system with any desktop environment or window manager.
+However, the FreeBSD base and ports collection has been missing some common features that end users expect from a desktop OS.
+
+The desktop-installer battery monitor script has been enhanced to display popup notifications at various levels of charge/discharge.
+
+package:deskutils/qmediamanager[], in conjunction with package:sysutils/devd-mount[] and package:sysutils/npmount[], mounts inserted media upon notification from devd, and displays a popup window offering the user options to show filesystem information, open a file manager, reformat, copy a disk image to the device, or unmount.
+It provides a convenient and secure way to work with external media such as USB sticks.
+
+A fourth new port -- package:deskutils/freebsd-update-notify[] -- displays a popup when new base updates are available, or when a configurable time limit has elapsed.
+If the user chooses to proceed with updates, the entire system is updated (packages, ports, and base) with man:auto-update-system[1] (a feature of package:sysutils/auto-admin[]).
+
+These new tools bring the FreeBSD desktop experience a step closer to the convenience of the most popular desktop operating systems.
+
+The tools are effectively prototypes, stable and reliable, but in need of review.
+Feedback from users regarding default behavior and configuration options will be appreciated.
diff --git a/website/content/en/status/report-2023-07-2023-09/doceng.adoc b/website/content/en/status/report-2023-07-2023-09/doceng.adoc
new file mode 100644
index 0000000000..1488da6997
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/doceng.adoc
@@ -0,0 +1,105 @@
+////
+Quarter:	3rd quarter of 2023
+Prepared by:	fernape
+Reviewed by:	carlavilla
+Last edit:	$Date: 2023-06-30 13:48:30 +0200 (Fri, 30 Jun 2023) $
+Version:	$Id: doceng-2023-2nd-quarter-status-report.adoc 416 2023-06-30 11:48:30Z fernape $
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see the link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During this quarter:
+
+* The search functionality of the documentation portal was moved from DuckDuckGo to our own search engine; for more information, see link:https://cgit.freebsd.org/doc/commit/?id=ac4fd34edfa1e5e2edb6fb9fc61acd782a0ed33b[this commit]
+* grahamperrin@'s doc commit bit was taken for safekeeping as per his request
+* pluknet@'s doc commit bit was taken for safekeeping as per his request.
+
+==== Porter's Handbook
+
+New `USES` knobs have been added to the Handbook:
+
+* link:https://cgit.freebsd.org/doc/commit/?id=ee08121ef177489c031870601de1cc728de646e5[`USES= ebur128`].
+* link:https://cgit.freebsd.org/doc/commit/?id=4f16184d81f1c02196d91e8d2511f23fd48e8822[`USES= guile`].
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblate[] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/[]
+
+===== Q3 2023 Status
+
+* 17 team languages
+* 189 registered users
+
+Four new translators joined Weblate:
+
+* minso in Korean (ko) and French (fr_FR)
+* strgalt-t in German (de_DE)
+* bsdmeg in German (de_DE)
+* mvsf in Portuguese (pt_BR)
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 7%)
+* Chinese (Traditional) (zh-tw)	(progress: 3%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 5%)
+* Korean (ko)			(progress: 33%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 2%)
+* Polish			(progress: 1%)
+* Portuguese			(progress: 0%)
+* Portuguese (pt-br)		(progress: 22%)
+* Spanish (es)			(progress: 35%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+==== FreeBSD Handbook Working Group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+* link:https://reviews.freebsd.org/D40546[The Network chapter has been rewritten]
+* link:https://cgit.freebsd.org/doc/commit/?id=612b7cc1721224c494c5b2600188e1508bb5611b[The Jails chapter has been rewritten]
+* The next section to work on will be the file systems part: UFS, OpenZFS, Other File Systems.
+ 
+==== FAQ Working Group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+The idea is to write a new FAQ.
+Will be released alongside FreeBSD 14.0.
+
+==== FreeBSD Website Revamp -- WebApps Working Group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into three phases:
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Complete, Approved by Doceng, Deploy Date Not Decided Yet_)
+Public instance on https://man-dev.FreeBSD.org
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Almost Complete, Presented at EuroBSDCon_)
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
diff --git a/website/content/en/status/report-2023-07-2023-09/dpaa2.adoc b/website/content/en/status/report-2023-07-2023-09/dpaa2.adoc
new file mode 100644
index 0000000000..ca15bfdaf0
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/dpaa2.adoc
@@ -0,0 +1,35 @@
+=== NXP DPAA2 support
+
+Links: +
+link:https://cgit.freebsd.org/src/tree/sys/dev/dpaa2[DPAA2 in the FreeBSD source tree] URL: link:https://cgit.freebsd.org/src/tree/sys/dev/dpaa2[] +
+link:https://github.com/mcusim/freebsd-src[DPAA2 on Github] URL: link:https://github.com/mcusim/freebsd-src[]
+
+Contact: Dmitry Salychev <dsl@FreeBSD.org> +
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org>
+
+==== What is DPAA2?
+
+DPAA2 is a hardware-level networking architecture found in some NXP SoCs which contains hardware blocks including Management Complex (MC, a command interface to manipulate DPAA2 objects), Wire Rate I/O processor (WRIOP, packets distribution, queuing, drop decisions), Queues and Buffers Manager (QBMan, Rx/Tx queues control, Rx buffer pools) and others.
+The Management Complex runs NXP-supplied firmware which provides DPAA2 objects as an abstraction layer over those blocks to simplify access to the underlying hardware.
+
+==== Changes from the previous report
+
+* Isolation between DPAA2 channels link:https://cgit.freebsd.org/src/commit/?id=58983e4b0253ad38a3e1ef2166fedd3133fdb552[improved].
+* Panic under heavy network load link:https://github.com/mcusim/freebsd-src/issues/19[fixed].
+* FDT/ACPI MDIO support.
+* NFS root mount link:https://github.com/mcusim/freebsd-src/issues/7[do not hang] on netboot over DPAA2 anymore.
+* Drivers link:https://github.com/mcusim/freebsd-src/issues/2[started] to communicate with MC via their own command portals (DPMCP).
+* link:https://github.com/mcusim/freebsd-src/issues?q=is%3Aissue+is%3Aclosed[List of all closed issues].
+
+==== Work in Progress
+
+Work on link:https://cgit.freebsd.org/src/commit/?id=2a9021898c4ee2154787da862c238cfeccd655df[dev/sff] started to support SFF/SFP modules in order to test DPAA2 drivers on links above 1 Gbit/s.
+
+==== Plan
+
+* Heavy network load tests (2.5 Gbit/s, 10 Gbit/s) and bottlenecks mitigation.
+* Cached memory-backed software portals.
+* Driver resources de-allocation to unload dpaa2.ko properly.
+* Further parts (DPSW, DCE, etc.) supported by the hardware.
+
+Sponsor: Traverse Technologies (providing Ten64 HW for testing)
diff --git a/website/content/en/status/report-2023-07-2023-09/ec2.adoc b/website/content/en/status/report-2023-07-2023-09/ec2.adoc
new file mode 100644
index 0000000000..4d8bd061f7
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/ec2.adoc
@@ -0,0 +1,17 @@
+=== FreeBSD on EC2
+
+Links: +
+link:https://www.patreon.com/cperciva[FreeBSD/EC2 Patreon]	URL: https://www.patreon.com/cperciva[]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+FreeBSD is available on both x86 (Intel and AMD) and ARM64 (Graviton) EC2 instances.
+Work continues to ensure that upcoming instance types will be supported.
+
+Weekly FreeBSD snapshots now include experimental ZFS-root AMIs for 14.0 and 15.0.
+This change will be present in FreeBSD 14.0-RELEASE.
+
+Work is underway to start publishing experimental "cloud-init" AMIs.
+This is expected to arrive in time for FreeBSD 14.0-RELEASE.
+
+This work is supported by Colin's FreeBSD/EC2 Patreon.
diff --git a/website/content/en/status/report-2023-07-2023-09/expert-system.adoc b/website/content/en/status/report-2023-07-2023-09/expert-system.adoc
new file mode 100644
index 0000000000..5108604d51
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/expert-system.adoc
@@ -0,0 +1,18 @@
+=== FreeBSD Expert System
+
+Links: +
+link:https://github.com/Wang-Yan-Hao/freebsd_expert_system[FreeBSD Expert System] URL: https://github.com/Wang-Yan-Hao/freebsd_expert_system[]
+
+Contact: Yan-Hao Wang <bses30074@gmail.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+Machine Learning and Deep Learning technologies have become increasingly prevalent in today's world, much like the proliferation of ChatGPT.
+We are working on developing a ChatGPT plugin that can access the latest FreeBSD data, transforming ChatGPT into a FreeBSD expert system.
+We have already scripted data cleaning and built an embedded model to search for relevant information.
+
+Nevertheless, we require assistance for the following aspect of this project:
+
+* While I am not an expert in Machine Learning or Deep Learning, we encounter numerous challenges in these domains, such as the adequacy of data cleaning and uncertainties in the final plugin development process.
+We would appreciate guidance in this regard.
+
+Sponsor: FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-07-2023-09/freebsd-foundation.adoc b/website/content/en/status/report-2023-07-2023-09/freebsd-foundation.adoc
new file mode 100644
index 0000000000..c0afdc79b0
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/freebsd-foundation.adoc
@@ -0,0 +1,164 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] +
+link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide.
+Donations from individuals and corporations fund and manage software development projects, conferences, and developer summits.
+We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and cluster administration efforts.
+We publish marketing material to promote, educate, and advocate for FreeBSD, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+This quarter we helped FreeBSD celebrate its 30th anniversary!
+This excitement has propelled us to accelerate our efforts to move FreeBSD forward in growth and innovation, which has focused us on identifying key areas we can invest our resources.
+At our board meeting in September, we refined our goals to focus on increasing FreeBSD adoption and visibility, diversifying our funding stream, and investing in the community health and long-term stability of the Project.
+We are in the process of identifying the key audiences and markets to target, while putting measurable outcomes to these goals.
+
+In this status report, you will read more about our work to help further FreeBSD's growth and innovation.
+We will highlight all the technical work we are doing to improve FreeBSD, both by our internal staff of software developers, as well as external project funding efforts.
+You will read about our advocacy work to promote FreeBSD to audiences outside of our community.
+Finally, you will see the great efforts made to connect with current and potential commercial users.
+
+==== Fundraising
+
+We would like to express our sincere gratitude to all those who generously donated to support our work.
+In addition to numerous individual contributions, we are especially grateful for the significant donations from NetApp, Netflix, and ARM.
+In Q3 alone, we received $183,842, bringing our total for the year to $375,000.
+This year our budget is around $2,230,000, which includes increased spending toward FreeBSD advocacy and software development.
+More than half of our budget is allocated toward work directly related to improving FreeBSD and keeping it secure.
+By providing a dedicated individual focused on partnerships, we can effectively emphasize the significance of investing in our efforts and underscore the long-term viability of FreeBSD to companies.
+Your support is crucial to our mission, and we deeply appreciate your commitment to the FreeBSD community.
+Please consider making a donation toward our 2023 fundraising campaign! link:https://freebsdfoundation.org/donate/[]
+For our larger commercial donors, check out our updated link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[FreeBSD Foundation Partnership Program].
+
+==== Partnerships and Research
+
+For Partnerships and Research this quarter, progress was made in three key areas:
+
+First, the link:https://wiki.freebsd.org/EnterpriseWorkingGroup[Enterprise Working Group] started to gather steam with growth up to 58 participants and active projects in four work streams.
+These are cloud native, Samba, bhyve manageability, and support for AI workloads.
+There is interest in several additional areas and I expect that by the end of this year and Q1 of next year, we will see meaningful feature updates in multiple areas of focus.
+
+Second, we made good progress working with other open source community members and organizations, notably the link:https://opensource.org/[Open Source Initiative], to advance proposals and technology from the FreeBSD community.
+Working with the Open Source Initiative’s link:https://opensource.org/programs/open-policy-alliance/[Open Policy Alliance], we are submitting a response to the US government's request for information on how the US government can support open source security and sustainability.
+As part of this, Greg Wallace participated on a panel organized by the Open Policy Alliance at the recent All Things Open conference in Raleigh, North Carolina.
+Greg Wallace has also been tracking how the US government incorporates CHERI into its policy recommendations for security by default, link:https://www.cisa.gov/sites/default/files/2023-10/Shifting-the-Balance-of-Cybersecurity-Risk-Principles-and-Approaches-for-Secure-by-Design-Software.pdf[such as this recent report from US and global government security agencies].
+On Page 28, CHERI is listed right after Rust as a key 'Secure by Design' tactic.
+
+Finally, we continue to strengthen partnerships with a growing number of companies using FreeBSD.
+Several conferences aided these relationships, including EuroBSDCon, Open Source Summit, and All Things Open.
+We have also developed a new program to support vendor/cloud users that work with the US government.
+The program details will be announced at the FreeBSD Vendor Summit.
+
+==== Advocacy
+
+Much of our effort is dedicated to the FreeBSD Project advocacy.
+This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations.
+The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier.
+Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables.
+
+The FreeBSD Foundation sponsors many conferences, events, and summits around the globe.
+These events can be BSD-related, open source, or technology events geared towards underrepresented groups.
+We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users.
+This all helps provide a healthy ecosystem.
+We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project.
+We continue to add new events to our yearly roster.
+This July, we held a workshop and staffed a table at FOSSY, a new open source conference in Portland, Oregon.
+In addition to attending and planning conferences, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD.
+
+Check out some of our advocacy work:
+
+* Held a workshop and hosted a table at link:https://sfconservancy.org/fossy/[FOSSY], July 13-16, 2023, in Portland, Oregon.
+* Friend-level sponsor of COSCUP, July 27-29, 2023, in New Taipei, Taiwan
+* Presented at the EuroBSDCon FreeBSD Developer Summit, and sponsored and staffed a table at link:https://2023.eurobsdcon.org/[EuroBSDCon 2023], September 14-17, 2023 in Coimbra, Portugal
+* Attended the link:https://events.linuxfoundation.org/open-source-summit-europe/[Open Source Summit, Europe], September 19-21, Bilbao, Spain
+* Continued planning the link:https://freebsdfoundation.org/news-and-events/event-calendar/november-2023-freebsd-vendor-summit/[November 2023 FreeBSD Vendor Summit], taking place November 2-3, 2023, in San Jose, California
+* Continued to administer our Google Summer of Code program
+* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-july-2023/[July Newsletter]
+* Additional Blog Posts
+** link:https://freebsdfoundation.org/blog/advocating-at-events-may-2023-freebsd-dev-summit-and-bsdcan/[Advocating at Events: May 2023 FreeBSD Dev Summit and BSDCan]
+** link:https://freebsdfoundation.org/blog/top-ten-reasons-to-upgrade-to-freebsd-13-2/[Top Ten Reasons to Upgrade to FreeBSD 13.2]
+** link:https://freebsdfoundation.org/blog/july-2023-software-development-projects-update/[July 2023 Software Development Projects Update]
+** https://freebsdfoundation.org/blog/freebsd-for-research-cheri-morello/[FreeBSD for Research: CHERI/Morello]
+** Meet the FreeBSD Google Summer of Code Students
+*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-soobin-rho/[Soobin Rho]
+*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-raghav-sharma/[Raghav Sharma]
+*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-sudhanshu-mohan-kashyap/[Sudhanshu Mohan Kashyap]
+*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-aymeric-wibo/[Aymeric Wibo]
+** link:https://freebsdfoundation.org/blog/meet-the-summer-2023-university-of-waterloo-co-op-student-naman-sood/[Meet The Summer 2023 University of Waterloo Co-Op Student: Naman Sood]
+** link:https://freebsdfoundation.org/blog/meet-freebsd-foundation-2023-summer-intern-jake-freeland/[Meet FreeBSD Foundation 2023 Summer Intern: Jake Freeland]
+* FreeBSD in the News
+** link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-joins-osis-open-policy-alliance/[FreeBSD Foundation Joins OSI's Open Policy Alliance]
+** link:https://freebsdfoundation.org/news-and-events/latest-news/hackernoon-5-reasons-we-use-open-source-freebsd-as-our-enterprise-os/[Hackernoon: 5 Reasons We Use Open Source FreeBSD as Our Enterprise OS]
+** link:https://freebsdfoundation.org/news-and-events/latest-news/what-the-dev-podcast-the-evolution-of-the-freebsd-project/[What the Dev Podcast: The Evolution of the FreeBSD Project].
+
+We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal.
+As we mentioned previously, the FreeBSD Journal is now a free publication.
+Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[].
+
+You can find out more about events we attended and upcoming events at link:https://freebsdfoundation.org/our-work/events/[].
+
+==== OS Improvements
+
+During the third quarter of 2023, 282 src, 652 ports, and 24 doc tree commits identified The FreeBSD Foundation as a sponsor.
+Some of this Foundation-sponsored work is described in separate report entries:
+
+* <<_enabling_snapshots_on_filesystems_using_journaled_soft_updates,Enabling Snapshots on Filesystems Using Journaled Soft Updates>>
+* <<_login_classes_fixes_and_improvements,Login Classes Fixes and Improvements>>
+* <<_openssl_3_in_baseimproved,OpenSSL 3 in base -- Improved>>
+* <<_openstack_on_freebsd,OpenStack on FreeBSD>>
+* <<_process_visibility_security_policies,Process Visibility Security Policies>>
+* <<_simd_enhancements_for_amd64,SIMD enhancements for amd64>>.
+
+Members of the Technology Team attended EuroBSDCon 2023 in Coimbra, Portugal.
+Li-Wen Hsu gave a tutorial to help newcomers contribute to FreeBSD.
+Before the conference, the FreeBSD Developer Summit took place, where the team presented a link:https://wiki.freebsd.org/DevSummit/202309?action=AttachFile&do=view&target=Foundation_Technology_Team_Devsummit_Fall_2023.pdf[short update on their recent work].
+
+Six summer internships or projects wrapped up.
+
+* link:https://freebsdfoundation.org/blog/meet-freebsd-foundation-2023-summer-intern-jake-freeland/[Jake Freeland] spent the summer working on a link:https://freebsdfoundation.org/project/capsicum-internship/[a Capsicum project] to trace violations, adapt various daemons such as man:syslogd[8], and write documentation.
+* link:https://freebsdfoundation.org/blog/meet-the-summer-2023-university-of-waterloo-co-op-student-naman-sood/[Naman Sood] worked on link:https://freebsdfoundation.org/project/networking-summer-internship/[various tasks, mostly related to networking].
+* En-Wei Wu completed link:https://freebsdfoundation.org/project/wireless-internship/[another wireless internship] to improve and extend wtap, the net80211(4) Wi-Fi simulator.
+* Yan-Hao Wang worked on a link:https://freebsdfoundation.org/project/documentation-and-testing-internship/[documentation and testing project] to, e.g., build an online man page editor and add test cases for some userspace tools.
+* Christos Margiolis completed his link:https://freebsdfoundation.org/project/improving-the-kinst-dtrace-provider/[project to improve the kinst DTrace provider] by implementing inline function tracing and porting kinst to arm64 and riscv.
+* In preparation for FreeBSD 14.0, Muhammad Moinur (Moin) Rahman committed over 700 fixes or workarounds for ports affected by recent OpenSSL and LLVM updates.
+
+For more information about current and past Foundation-contracted work, visit the link:https://freebsdfoundation.org/our-work/projects/[Foundation Projects page].
+
+Here is a sampling of other Foundation-sponsored work completed over the quarter:
+
+* Improved riscv64 CPU identity and feature detection
+* Rewrote man:intro[9] man page from scratch
+* Performed code maintenance and fixed bugs in the man:hwpmc[4] module and the man:pmc[3] library and tools
+* Committed various man:freebsd-update[8] fixes in preparation for FreeBSD 14.0
+* Committed many (37) updates and fixes to the LinuxKPI, iwlwifi, and net802.11 code
+* Updated SSH first to OpenSSH 9.3p2, then 9.4p1
+* Patched ssh-keygen to generate Ed25519 keys when invoked without arguments
+* Added a clean-room implementation of the Linux man:membarrier[2] system call
+* Increased MAXCPU to 1024 on amd64 and arm64
+* Committed fixes for automatic Zenbleed misbehavior/data leaks prevention on affected machines (via chicken bit)
+* Reviewed the use of scheduling priorities throughout the kernel for work in progress to harden the rtprio() system call and make it more useful in some cases.
+
+==== Supporting FreeBSD Infrastructure
+
+The Foundation provides hardware and two staff members to help support the FreeBSD cluster.
+With your donations, the Foundation, in coordination with the Cluster Administration Team, purchased five new package builders, three new web servers, a new firewall/router, two package mirrors, and two new servers for continuous integration.
+With the exception of one of the package mirrors, all the new hardware will be located on the east coast of the USA.
+
+==== Continuous Integration and Quality Assurance
+
+The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project.
+You can read more about CI work in a dedicated report entry.
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2023-07-2023-09/freebsd-online-editor.adoc b/website/content/en/status/report-2023-07-2023-09/freebsd-online-editor.adoc
new file mode 100644
index 0000000000..e733ad42e2
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/freebsd-online-editor.adoc
@@ -0,0 +1,27 @@
+=== FreeBSD Online Editor and Man Page Editor
+
+Links: +
+link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[FreeBSD Online Document Editor] URL: link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[] +
+link:https://github.com/Wang-Yan-Hao/man_page_editor[FreeBSD Online Man Page Editor] URL: link:https://github.com/Wang-Yan-Hao/man_page_editor[]
+
+Contact: Yan-Hao Wang <bses30074@gmail.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+Currently, our document translation process involves using Weblate and direct editing of the link:https://cgit.freebsd.org/doc/[doc] repository.
+We acknowledge that this process can be somewhat cumbersome, so we are striving to offer a more convenient alternative, similar to what the wiki community does.
+Introducing the Online Document Editor and Man Page Editor, a user-friendly, WYSIWYG static site designed for translating documents and man pages.
+Our goal is to consolidate all translation functions within a single platform, making the translation process as straightforward as possible.
+
+However, we still require assistance with these two projects, as follows:
+
+1. The Document editor and Man page editor were developed using simple JavaScript.
+We are seeking a web developer to assess the code's efficiency since I (Yan-Hao Wang) am not well-versed in front-end development.
+
+2. We are also seeking a cybersecurity developer to assist us in identifying and addressing security issues within these two projects.
+This is crucial to ensure the secure hosting of these projects and mitigate any potential vulnerabilities.
+
+3. As there is currently no existing JavaScript library to render mandoc, I had to create my own.
+However, there are still some concealed errors during the editing process.
+We are in need of a JavaScript developer to help rectify these rendering issues.
+
+Sponsor: FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-07-2023-09/gcc.adoc b/website/content/en/status/report-2023-07-2023-09/gcc.adoc
new file mode 100644
index 0000000000..31bbde0246
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/gcc.adoc
@@ -0,0 +1,25 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[]
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+The process to update GCC default version to GCC 13 has started with an link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[exp-run]. Thanks to mailto:antoine@FreeBSD.org[Antoine Brodin] who ran the exp-run and to all other developers and ports maintainers involved.
+
+The same exp-run contains additional patches as anticipated in last quarterly status report.
+In particular, it contains patches to update
+
+* package:lang/gcc11[] to version 11.4.0;
+* package:lang/gcc12[] to version 12.3.0;
+* package:lang/gcc13[] to version 13.2.0.
+
+The reader might remember that I had planned to update GCC default version to GCC 13 as soon as 13.1.0 was out, but as it can be noted the GCC developers were faster to release 13.2.0 than I was working on the GCC ports.
+
+Most of the bugs reported in the exp-run are due to the same error: `error: expected identifier before '__is_convertible'`.
+It seems that the issue is an incompatibility between FreeBSD 12's libcxx and GCC 13 headers.
+Please check the link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[discussion in the exp-run] for more information and to provide your feedback.
diff --git a/website/content/en/status/report-2023-07-2023-09/gitlab.adoc b/website/content/en/status/report-2023-07-2023-09/gitlab.adoc
new file mode 100644
index 0000000000..7b2d0e6d83
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/gitlab.adoc
@@ -0,0 +1,19 @@
+=== GitLab 16.3 Available
+
+Link: +
+link:https://about.gitlab.com/releases/2023/08/22/gitlab-16-3-released/[Gitlab 16.3 New Features] URL: link:https://about.gitlab.com/releases/2023/08/22/gitlab-16-3-released/[]
+
+Contact: Matthias Fechner <mfechner@FreeBSD.org>
+
+GitLab is a DevOps platform.
+It brings velocity with confidence, security without sacrifice, and visibility into DevOps success.
+
+Version 16.3 is now available on FreeBSD: please check the package:www/gitlab-ce[] port.
+The upgrade is very important as version 16.3 will be required for all further upgrades.
+Upgrade to 16.4 is only possible from GitLab 16.3.
+
+Documentation for installation can be found at link:https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/install/16.3-freebsd.md?ref_type=heads[].
+Documentation for upgrading is available at https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.1-16.3-freebsd.md?ref_type=heads[].
+
+I will wait for the upgrade to 16.4 (which will be released around 20.9. or 22.9., not sure) until ports _quarterly_ branch 2023Q4 is created, to avoid breaking systems that do not use the main branch (_latest_).
+GitLab users should always choose the main branch, as described in the installation manual.
diff --git a/website/content/en/status/report-2023-07-2023-09/intro.adoc b/website/content/en/status/report-2023-07-2023-09/intro.adoc
new file mode 100644
index 0000000000..567a1428fc
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/intro.adoc
@@ -0,0 +1,9 @@
+Here is the third 2023 status report, with 32 entries.
+
+This is the summer quarter and thus it includes many interesting news from Google Summer of Code.
+Of course, we also have our usual team reports and many projects share with us their latest news.
+Much important work has been done for the first release of FreeBSD 14.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2023-07-2023-09/kde.adoc b/website/content/en/status/report-2023-07-2023-09/kde.adoc
new file mode 100644
index 0000000000..c5b242b096
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/kde.adoc
@@ -0,0 +1,60 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] +
+link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation.
+The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack.
+
+==== Infrastructure
+
+Qt5 is now on long-term support and updates only rarely.
+There was an update to 5.15.10 in this quarter.
+Qt6 is now updated with the regular upstream releases, with the 6.5.2 release landing at the end of July and 6.5.3 following later.
+
+CMake saw no updates this quarter, so we are now lagging by at least one minor release.
+The changelog for the latest releases does not have much for FreeBSD, so there is no special reason to upgrade.
+
+package:sysutils/polkit[] and package:sysutils/consolekit2[] were both updated, bringing improved security policy and console handling to the FreeBSD desktop.
+package:x11/sddm[] was updated to provide a better graphical login manager.
+
+package:multimedia/pipewire[] was updated to version 0.3.81.
+This provides multimedia support for desktops such as KDE and GNOME.
+
+
+==== KDE Stack
+
+KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well.
+These (large) updates land shortly after their upstream release and are not listed separately.
+
+* KDE Frameworks reached version 5.110. The KDE Frameworks 5 series is winding down, although it will be six months or so before it enters long-term support upstream.
+* KDE Plasma Desktop was updated to version 5.27.8. Just like frameworks, work on KDE Plasma 5 is winding down upstream in favor of KDE Plasma 6.
+* KDE Gear updated to 23.08.1.
+
+==== Related Ports
+
+The KDE ecosystem includes a wide range of ports -- most maintained by kde@, all building on a shared base of Qt and KDE Frameworks.
+The kde@ team updates them all as needed.
+This quarter, for instance, tcberner@ and arrowd@ updated or fixed (much more than) this selection of ports:
+
+* package:astro/merkaartor[]
+* package:devel/massif-visualizer[]
+* package:finance/alkimia[]
+* package:irc/quassel[]
+* package:net-im/kaidan[]
+* package:sysutils/bsdisks[]
+* package:sysutils/k3b[]
+
+Thanks to jhale@, package:devel/qtcreator[] was updated to 11.0.3, providing another featureful integrated development environment for creating Qt and KDE applications.
+
+==== Deprecations
+
+Web browsers are huge, and have a considerable security surface.
+The venerable package:www/qt5-webkit[] WebKit port has been slated for removal and consumers have been moved to WebEngine.
+The fork of WebKit that we relied on is no longer actively maintained.
diff --git a/website/content/en/status/report-2023-07-2023-09/linuxulator.adoc b/website/content/en/status/report-2023-07-2023-09/linuxulator.adoc
new file mode 100644
index 0000000000..080e37b4a7
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/linuxulator.adoc
@@ -0,0 +1,15 @@
+=== Linux compatibility layer update
+
+Links: +
+link:https://wiki.freebsd.org/Linuxulator[Linuxulator status Wiki page] URL: link:https://wiki.freebsd.org/Linuxulator[] +
+link:https://wiki.freebsd.org/LinuxApps[Linux app status Wiki page] URL: link:https://wiki.freebsd.org/LinuxApps[]
+
+Contact: Dmitry Chagin <dchagin@FreeBSD.org>
+
+The goal of this project is to improve FreeBSD's ability to execute unmodified man:linux[4] binaries.
+
+As of gitref:22dca7acf775[repository=src], xattr system calls are implemented.
+That makes it possible to use Linux rsync.
+
+As of gitref:bbe017e0415a[repository=src], ioprio system calls are implemented.
+That makes it possible to debootstrap Ubuntu 23.04.
diff --git a/website/content/en/status/report-2023-07-2023-09/lldb-kmod.adoc b/website/content/en/status/report-2023-07-2023-09/lldb-kmod.adoc
new file mode 100644
index 0000000000..7c4b8a9d71
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/lldb-kmod.adoc
@@ -0,0 +1,19 @@
+=== LLDB Kernel Module Improvement
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[GSoC Wiki Project] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[] +
+link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[Project Codebase] URL: link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[] +
+link:https://github.com/llvm/llvm-project/pull/67106[LLVM PullRequest] URL: link:https://github.com/llvm/llvm-project/pull/67106[]
+
+Contact: Sheng-Yi Hong <aokblast@FreeBSD.org>
+
+The LLDB Kernel Module Improvement Project described in the previous quarter report implements DynamicLoader Plugin for FreeBSD Kernel on LLDB.
+
+All of the work is done -- that is, this plugin can correctly load all kernel modules and their debug files extracted from kernel coredump.
+
+This plugin has been tested on both x86-64 for relocatable type kernel module and arm64(EC2) for shared library type kernel module.
+Both of these platforms show this plugin works well.
+
+Currently, this plugin prepares to be landed to LLVM codebase in https://github.com/llvm/llvm-project/pull/67106[LLVM PullRequest]
+
+Sponsor: The Google Summer of Code '23 program
diff --git a/website/content/en/status/report-2023-07-2023-09/login_classes.adoc b/website/content/en/status/report-2023-07-2023-09/login_classes.adoc
new file mode 100644
index 0000000000..c68fbbe13c
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/login_classes.adoc
@@ -0,0 +1,37 @@
+=== Login Classes Fixes and Improvements
+
+Links: +
+link:https://reviews.freebsd.org/D40339[Start of the reviews stack] URL: link:https://reviews.freebsd.org/D40339[]
+
+Contact: Olivier Certner <olce.freebsd.statusreports@certner.fr>
+
+==== Context
+
+Login classes are a mechanism mainly used to set various process properties and attributes at login, depending on the user logging in and the login class he is a member of.
+A login class typically specifies resource limits, environment variables and process properties such as scheduling priority and umask.
+See man:login.conf[5] for more information.
+
+==== Changes
+
+The `priority` and `umask` capabilities now accept the `inherit` special value to explicitly request property inheritance from the login process.
+This is useful, e.g., when temporarily logging in as another user from a process with a non-default priority to ensure that processes launched by this user still have the same priority level.
+
+Users can now override the global setting for the `priority` capability (in [.filename]#/etc/login.conf#) in their local configuration file ([.filename]#~/.login_conf#).
+Note however that they cannot increase their priority if they are not privileged, and that using `inherit` in this context makes no sense, since the global setting is always applied first.
+
+Fixes:
+
+- Fix a bug where, when the `priority` capability specifies a realtime priority, the final priority used was off-by-one (and the numerically highest priority in the real time class (31) could never be set).
+- Security: Prevent a setuid/setgid process from applying directives from some user's [.filename]#~/.login_conf# (directives there that cannot be applied because of a lack of privileges could suddenly become applicable in such a process).
+
+We have also updated the relevant manual pages to reflect the new functionality, and improved the description of the `priority` and `umask` capabilities in man:login.conf[5].
+
+==== Status
+
+Some of the patches in the series have been reviewed thanks to mailto:kib@FreeBSD.org[Konstantin Belousov] and mailto:imp@FreeBSD.org[Warner Losh].
+Other patches are waiting for reviews (and reviewers, volunteers welcome!), which are not expected to be labored.
+
+We plan to improve consistency by deprecating the priority reset to 0 when no value for the capability `priority` is explicitly specified, which has been the case for `umask` for 15+ years.
+
+Sponsor: Kumacom SAS (for development work) +
+Sponsor: The FreeBSD Foundation (for some reviews)
diff --git a/website/content/en/status/report-2023-07-2023-09/mfsbsd.adoc b/website/content/en/status/report-2023-07-2023-09/mfsbsd.adoc
new file mode 100644
index 0000000000..7dca0c593e
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/mfsbsd.adoc
@@ -0,0 +1,33 @@
+=== Integrate mfsBSD into the Release Building Tools
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[Wiki Article] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[] +
+link:https://reviews.freebsd.org/D41705[Code Review on Phabricator] URL: link:https://reviews.freebsd.org/D41705[] +
+link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-soobin-rho/[FreeBSD Foundation Blog Post] URL: link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-soobin-rho/[]
+
+Contact: Soobin Rho <soobinrho@FreeBSD.org>
+
+==== What is mfsBSD?
+
+"mfsBSD is a toolset to create small-sized but full-featured mfsroot based distributions of FreeBSD that store all files in memory (MFS) [Memory File System] and load from hard drive, USB storage device, or optical medium.
+It can be used for a variety of purposes, including diskless systems, recovery partitions and remotely overwriting other operating systems."
+
+mailto:mm@FreeBSD.org[Martin Matuška] is the creator of mfsBSD.
+He is also author of the original (2009) link:https://people.freebsd.org/~mm/mfsbsd/mfsbsd.pdf[mfsBSD white paper], from which the excerpt above is taken.
+Upstream mfsBSD is maintained in the link:https://github.com/mmatuska/mfsbsd[repository on GitHub].
+
+==== Purpose of this Project
+
+This project integrates mfsBSD into the FreeBSD release tool set, creating an additional target of mfsBSD images ([.filename]#.img# and [.filename]#.iso# files) in [.filename]#/usr/src/release/Makefile#.
+Prior to integration, mfsBSD only existed outside the FreeBSD release tool chain, and only -RELEASE versions were produced.
+
+With this project, mfsBSD images will be available at the official FreeBSD release page.
+You will also be able to build mfsBSD yourself by invoking `cd /usr/src/release && make release WITH_MFSBSD=1`, which will then create [.filename]#mfsbsd-se.img# and [.filename]#mfsbsd-se.iso# at [.filename]#/usr/obj/usr/src/${ARCH}/release/#.
+
+==== Changes from last quarter
+
+The code is ready, and is currently under review.
+If you would like to get involved with the review process, please feel free to do so!
+Here is link:https://reviews.freebsd.org/D41705[my revision].
+
+Sponsor: Google, Inc. (GSoC 2023)
diff --git a/website/content/en/status/report-2023-07-2023-09/office.adoc b/website/content/en/status/report-2023-07-2023-09/office.adoc
new file mode 100644
index 0000000000..b6019f48e1
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/office.adoc
@@ -0,0 +1,26 @@
+=== FreeBSD Office Team
+
+Links: +
+link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[] +
+link:https://lists.freebsd.org/subscription/freebsd-office[The FreeBSD Office mailing list] URL: link:https://lists.freebsd.org/subscription/freebsd-office[]
+
+Contact: FreeBSD Office team ML <office@FreeBSD.org> +
+Contact: Dima Panov <fluffy@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+The FreeBSD Office team works on a number of office-related software suites and tools such as OpenOffice and LibreOffice.
+
+Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users.
+
+During the 2023Q3 period we pushed maintenance patches for the LibreOffice port and brought the latest, 7.6.2, release and all companion libraries such as MDDS, libIxion and more to the ports tree.
+All prerelease development of LibreOffice ports is carried out in the in link:https://github.com/freebsd/freebsd-ports-libreoffice[LibreOffice WIP repo].
+
+Together with LibreOffice, we also updated Boost to the latest, 1.83 release.
+Everyone interested in Boost porting can submit patches to the link:https://github.com/fluffykhv/freebsd-ports-boost[Boost WIP repository].
+
+We are looking for people to help with the open tasks:
+
+* The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=office%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=substring&list_id=650685&order=Bug+Number&query_format=advanced[open bugs list] contains all filed issues which need some attention
+* Upstream link:https://cgit.freebsd.org/ports/tree/editors/libreoffice/files[local patches in ports]
+
+Patches, comments and objections are always welcome in the mailing list and Bugzilla.
diff --git a/website/content/en/status/report-2023-07-2023-09/openssl3.adoc b/website/content/en/status/report-2023-07-2023-09/openssl3.adoc
new file mode 100644
index 0000000000..b5e8b44bee
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/openssl3.adoc
@@ -0,0 +1,18 @@
+=== OpenSSL 3 in base -- Improved
+
+Links: +
+link:https://www.openssl.org/source/[OpenSSL Downloads] URL: link:https://www.openssl.org/source/[]
+
+Contact: Pierre Pronchery <pierre@freebsdfoundation.org>
+
+This is a follow-up to the link:https://www.freebsd.org/status/report-2023-04-2023-06/[previous quarterly report] on the link:https://www.freebsd.org/status/report-2023-04-2023-06/#_openssl_3_in_base[integration of OpenSSL 3 into the base system].
+
+The most obvious updates since the previous report are certainly the 3.0.10 and then 3.0.11 releases, fixing CVE issues with low to medium severity (link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2975[CVE-2023-2975], link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3446[CVE-2023-3446], link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3817[CVE-2023-3817], link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4807[CVE-2023-4807]).
+
+However these are not the only changes, and this quarter some issues specific to the integration were fixed, most of which were found while building ports with OpenSSL 3 in the base system.
+
+Fixes included:
+
+* Linking the engines and the legacy provider with the libcrypto.so shared object, for proper visibility of symbols, and for which a link:https://cgit.freebsd.org/src/commit/Makefile.inc1?id=1a18383a52bc373e316d224cef1298debf6f7e25[hack was required in the build system].
+* Correcting the list of source files for the FIPS provider.
+* Ensuring backward compatibility for the deprecated 0.9.8 API, which was notably helpful for the PAM authentication module from package:security/pam_ssh_agent_auth[], based on OpenSSH's man:ssh-agent[1] authentication mechanism.
diff --git a/website/content/en/status/report-2023-07-2023-09/openstack.adoc b/website/content/en/status/report-2023-07-2023-09/openstack.adoc
new file mode 100644
index 0000000000..465f875d76
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/openstack.adoc
@@ -0,0 +1,36 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[]
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+OpenStack, an open-source cloud operating system, has been a valuable resource for deploying various resource types on cloud platforms.
+However, the challenge has been running OpenStack's control plane on FreeBSD hosts.
+Our project's mission is to enable FreeBSD to function seamlessly as an OpenStack host.
+
+Throughout this quarter, we focused on the last bit of the entire proof of concept (POC), the VM console integration.
+The goal is to let users get serial consoles via the OpenStack client to access the VM instances running on the FreeBSD-based OpenStack cluster.
+This is also important because right now we do not have a port for the managed DHCP service in Neutron.
+Users need to manually configure the correct IP addresses for the VM instances to have network connectivity.
+However, man:bhyve[8] does not natively expose serial consoles, so we need to instead export the man:nmdm[4] device over the network.
+This is done by a custom proxy called link:https://github.com/openstack-on-freebsd/socat-manager/blob/main/server.py[`socat-manager`], and yes, we leverage man:socat[1] to listen on specific ports allocated by OpenStack `nova-compute` to be integrated into their workflow.
+With the aid of another critical part, the link:https://github.com/openstack-on-freebsd/socat-manager/tree/main/hooks[custom Libvirt hook for bhyve], we can connect the two endpoints and make the consoles accessible to the users.
+During development of the hook script, we found that the hook interface provided by Libvirt specifically for bhyve was link:https://gitlab.com/libvirt/libvirt/-/issues/528[not well implemented].
+Fortunately, the Libvirt developer link:https://gitlab.com/libvirt/libvirt/-/commit/ad8c4d9d6d09d51a9530ed84fcd2220713aab928[fixed the issue] promptly, and we plan to refine our hook script when the fix is released in the future.
+
+We also addressed the nested bhyve issue (running bhyve VMs on top of Linux KVM) in our development environment mentioned in link:https://www.freebsd.org/status/report-2023-04-2023-06/#_openstack_on_freebsd[the last quarterly report].
+It is caused by the APIC emulation of the two VT-x features: `VID` and `PostIntr`.
+
+Our host's CPUs have these two features so we need to disable them at the L1 guest, which acts as a bhyve host, in [.filename]#/boot/loader.conf# to make L2 guests not hanging.
+It is crucial for us to be able to work on the project in a fully virtualized environment due to the lack of physical resources.
+This could be equally important for people interested in the project, lowering the bar for them to try out or validate the entire POC on their environment without too demanding setup requirements.
+
+Looking ahead to Q4, our focus is wrapping up the POC with revised documentation and porting to FreeBSD 14.0-RELEASE.
+Dependencies that lack the corresponding FreeBSD packages will be ported one by one.
+We also aim to rebase our work with OpenStack link:https://releases.openstack.org/antelope/index.html[2023.1 Antelope].
+We invite those interested to explore our documentation and contribute to this project's success.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-07-2023-09/pantheon.adoc b/website/content/en/status/report-2023-07-2023-09/pantheon.adoc
new file mode 100644
index 0000000000..6a66de6a03
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/pantheon.adoc
@@ -0,0 +1,37 @@
+=== Pantheon desktop on FreeBSD
+
+Links: +
+link:https://elementary.io/[elementary OS] URL: link:https://elementary.io/[] +
+link:https://codeberg.org/olivierd/freebsd-ports-elementary[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-elementary[]
+
+Contact: Olivier Duchateau <duchateau.olivier@gmail.com>
+
+The Pantheon desktop environment is designed for elementary OS.
+It builds on GNOME technologies (such as Mutter, GTK 3 and 4) and it is written in Vala.
+The goal is to have a complete desktop environment for end users.
+
+*13.2-RELEASE or higher is required*, because several core components depend on package:deskutils/xdg-desktop-portal[].
+
+The repository contains a file called [.filename]#elementary.mk# for the [.filename]#Mk/Uses# framework, official applications, and curated ports which depend on package:x11-toolkits/granite7[].
+
+I have submitted several patches in order to keep these ports up-to-date:
+
+* package:deskutils/iconbrowser[]
+* package:multimedia/elementary-videos[]
+* package:x11-themes/gnome-icons-elementary[]
+* package:editors/elementary-code[]
+
+The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&query_format=advanced&short_desc=elementary-calendar%20elementary-terminal%20granite7&short_desc_type=anywordssubstr[bug reports] for updating the following ports are still open on bugzilla:
+
+* package:x11-toolkits/granite7[]: Update to 7.3.0
+* package:deskutils/elementary-calendar[]: Update to 7.0.0
+* package:x11/elementary-terminal[]: Update to 6.1.2
+
+In the same time, I have also worked on updating the GNOME stack (especially WebKitGTK, libwnck, Mutter, Vala).
+I noticed several regressions particularly with package:x11/plank[] (it is related to monitoring open applications).
+
+Three new applications have been added to the development repository:
+
+* deskutils/atlas, a map viewer
+* deskutils/nimbus, a weather applet
+* audio/leopod, podcasts client
diff --git a/website/content/en/status/report-2023-07-2023-09/portmgr.adoc b/website/content/en/status/report-2023-07-2023-09/portmgr.adoc
new file mode 100644
index 0000000000..1e15ed00e3
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/portmgr.adoc
@@ -0,0 +1,45 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: René Ladan <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+* According to INDEX, there are currently 34,600 ports in the Ports Collection.
+There are currently 3,000 open ports PRs of which some 730 are unassigned.
+The last quarter saw 11,454 commits by 130 committers on the main branch and 828 commits by 37 committers on the 2023Q3 branch.
+Compared to last quarter, this means a slight decrease in the number of unassigned PRs, a 10% increase in the number of commits on the main branch but also less backports to the quarterly branch.
+The number of ports also grew a bit.
+
+During Q3 we welcomed Joel Bodenmann (jbo@) as a new ports committer, granted a ports commit bit to mizhka@ who was already a src committer, and took the commit bits of knu@ and uqs@ in for safe-keeping after a year of inactivity.
+
+Portgmr discussed and worked on the following things during Q3:
+
+* Some progress has been made on sub-packages and a lightning talk was given by pizzamig@ at EuroBSDCon
+* Overhauling some parts of the ports tree (LIB_DEPENDS, PREFIX, MANPREFIX, MANPATH)
+
+Support for FreeBSD 13.1 was removed from the ports tree as it reached its end-of-life on August 1st.
+
+The following happened on the infrastructure side:
+
+* USES for ebur128 and guile were added
+* Default versions for Mono, Perl, and PostgreSQL were updated to respectively 5.20, 5.34, and 15
+* Default versions for ebur128, guile, and pycryptography were added at respectively "rust", 2.2, and "rust"
+* Updates to major ports that happened were:
+
+** pkg to 1.20.7
+** chromium to 117.0.5938.132
+** Firefox to 118.0.1
+** KDE to 5.27.8
+** Rust to 1.72.0
+** Wine to 8.0.2
+
+During the last quarter, pgkmgr@ ran 18 exp-runs to test various ports upgrades, updates to default versions of ports, and changes to pycryptography.
diff --git a/website/content/en/status/report-2023-07-2023-09/portoptscli.adoc b/website/content/en/status/report-2023-07-2023-09/portoptscli.adoc
new file mode 100644
index 0000000000..9f5e28fd06
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/portoptscli.adoc
@@ -0,0 +1,22 @@
+=== PortOptsCLI -- Ports Collection Accessibility
+
+Link: +
+link:https://gitlab.com/alfix/portoptscli[Project repository] URL: link:https://gitlab.com/alfix/portoptscli[]
+
+Contact: Alfonso Sabato Siciliano <asiciliano@FreeBSD.org> +
+Contact: FreeBSD Accessibility mailing list <freebsd-accessibility@FreeBSD.org>
+
+FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications.
+It is possible to configure a port before the building and installation.
+The command `make config` uses package:ports-mgmt/dialog4ports[] and package:ports-mgmt/portconfig[] to set up a port interactively via a text user interface (TUI).
+
+Unfortunately, screen readers perform poorly with a TUI; it is a well-known accessibility problem.
+FreeBSD provides tens of thousands of ports; port configuration is a key feature, but it is inaccessible to users with vision impairment.
+
+PortOptsCLI (Port Options CLI) is a new utility for setting port options via a command line interface.
+Properly, PortOptsCLI provides commands to navigate configuration dialogues (checklists and/or radio buttons) and set up their items interactively.
+It is also suitable for a speech synthesizer; currently it is tested with package:accessibility/orca[].
+PortOptsCLI can be installed via the package:ports-mgmt/portoptscli[] port or package.
+
+Tips and new ideas are welcome.
+If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place.
diff --git a/website/content/en/status/report-2023-07-2023-09/pot.adoc b/website/content/en/status/report-2023-07-2023-09/pot.adoc
new file mode 100644
index 0000000000..66bece95ab
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/pot.adoc
@@ -0,0 +1,27 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+During this quarter, link:https://github.com/bsdpot/pot/pull/274[Pot 0.15.6] was finished, adding custom man:pf[4] rule configuration hooks.
+
+Additionally, link:https://github.com/bsdpot/nomad-pot-driver/releases/tag/v0.9.1[Nomad Pot Driver 0.9.1] that allows setting Pot attributes in Nomad job descriptions was released.
+
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+Quite a few new container images were made available, e.g. a link:https://github.com/bsdpot/potluck/tree/master/caddy-s3-nomad[Caddy S3 proxy], a link:https://github.com/bsdpot/potluck/tree/master/mastodon-s3[Mastodon instance], and a link:https://github.com/bsdpot/potluck/tree/master/redis-single[Redis container].
+In total there are now 50 containers available that can either be downloaded as ready-made images at link:https://potluck.honeyguide.net/[the Potluck image registry], if you trust our build process, or that you can build yourself from the Pot flavour files stored in the link:https://github.com/bsdpot/potluck[Potluck GitHub repository].
+
+The July/August 2023 edition of the FreeBSD Journal contains Luca's link:https://freebsdfoundation.org/wp-content/uploads/2023/08/Pizzamiglio.pdf[Jail Orchestration with pot and nomad] article, explaining how to use Pot and Potluck together with Nomad to orchestrate containers on multiple hosts.
+
+Last but not least, a patch (gitref:90b1184d93c8[repository=ports]) added build cluster support to the package:devel/sccache[] port.
+
+As always, feedback and patches are welcome.
+
+Sponsors: Nikulipe UAB, Honeyguide Group
diff --git a/website/content/en/status/report-2023-07-2023-09/process_visibility.adoc b/website/content/en/status/report-2023-07-2023-09/process_visibility.adoc
new file mode 100644
index 0000000000..06cf80b33f
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/process_visibility.adoc
@@ -0,0 +1,49 @@
+=== Process Visibility Security Policies
+
+Links: +
+link:https://reviews.freebsd.org/D40626[Start of the reviews stack] URL: link:https://reviews.freebsd.org/D40626[]
+
+Contact: Olivier Certner <olce.freebsd.statusreports@certner.fr>
+
+==== Context
+
+FreeBSD implements three built-in security policies that limit which processes are visible to particular users, with the goal of preventing information leaks and unwanted interactions.
+
+The first one can prevent an unprivileged user from seeing or interacting with processes that do not have the user's UID as their real UID.
+It can be activated by setting the sysctl `security.bsd.see_other_uids` to 0 (default is 1).
+
+The second one can prevent an unprivileged user from seeing or interacting with processes whose credentials do not have any group that the user is a member of.
+It can be activated by setting the sysctl `security.bsd.see_other_gids` to 0 (default is 1).
+
+The third one can prevent an unprivileged user's process from seeing or interacting with processes that are in a jail that is a strict sub-jail of the former.
+The jail subsystem already prevents such a process to see processes in jails that are not descendant of its own (see man:jail[8] and in particular the section "Hierarchical Jails").
+One possible use of this policy is, in conjunction with the first one above, to hide processes in sub-jails that have the same real UID as some user in an ancestor jail, because users having identical UIDs in these different jails are logically considered as different users.
+It can be activated by setting the sysctl `security.bsd.see_jail_proc` to 0 (default is 1).
+
+After a review of these policies' code and real world testing, we noticed a number of problems and limitations which prompted us to work on this topic.
+
+==== Changes
+
+The policy controlled by the `security.bsd.see_jail_proc` sysctl has received the following fixes and improvements:
+
+- Harden the `security.bsd.see_jail_proc` policy by preventing unauthorized users from attempting to kill, change priority of or debug processes with same (real) UID in a sub-jail at random, which, provided the PID of such a process is guessed correctly, would succeed even if these processes are not visible to them.
+- Make this policy overridable by MAC policies, as are the others.
+
+The policy controlled by `security.bsd.see_other_gids` was fixed to consider the real group of a process instead of its effective group when determining whether the user trying to access the process is a member of one of the process' groups.
+The rationale is that some user should continue to see processes it has launched even when they acquire further privileges by virtue of the setgid bit.
+Conversely, they should not see processes launched by a privileged user that temporarily enters the user's primary group.
+This new behavior is consistent with what `security.bsd.see_other_uids` has always been doing for user IDs (i.e., considering some process' real user ID and not the effective ID).
+
+We have updated manual pages related to these security policies, including man:security[7], man:sysctl[8], and man:ptrace[2].
+Several manual pages of internal functions either implementing or leveraging these policies have also been revamped.
+
+==== Status
+
+Thanks to the help of mailto:mhorne@FreeBSD.org[Mitchell Horne], mailto:pauamma@gundo.com[Pau Amma], mailto:bcr@FreeBSD.org[Benedict Reuschling] and mailto:emaste@FreeBSD.org[Ed Maste], most of the submitted changes have been reviewed and approved, so they should reach the tree soon.
+The patch series starts with https://reviews.freebsd.org/D40626[review D40626].
+From there, click on the "Stack" tab to see the full list of reviews implementing the changes.
+
+As a later step, we are considering turning the `security.bsd.see_jail_proc` policy on by default (i.e., the default value of the sysctl would become 0) unless there are objections.
+
+Sponsor: Kumacom SAS (for development work) +
+Sponsor: The FreeBSD Foundation (for most of the reviews)
diff --git a/website/content/en/status/report-2023-07-2023-09/releng.adoc b/website/content/en/status/report-2023-07-2023-09/releng.adoc
new file mode 100644
index 0000000000..c1c52d1bee
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/releng.adoc
@@ -0,0 +1,19 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the third quarter of the year, the FreeBSD Release Engineering Team started work on the upcoming 14.0-RELEASE cycle.
+As of this writing, BETA3 had been released, with BETA4 to follow shortly after.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main* and *stable/13* branches.
+
+Sponsor: Tarsnap +
+Sponsor: https://www.gofundme.com/f/gjbbsd/ +
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-07-2023-09/simd.adoc b/website/content/en/status/report-2023-07-2023-09/simd.adoc
new file mode 100644
index 0000000000..f07bee3912
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/simd.adoc
@@ -0,0 +1,28 @@
+=== SIMD enhancements for amd64
+
+Links: +
+link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt[Project proposal] URL: link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt[] +
+link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[simd(7)] URL: link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[]
+
+Contact: Robert Clausecker <fuz@FreeBSD.org>
+
+SIMD instruction set extensions such as SSE, AVX, and NEON are ubiquitous on modern computers and offer performance advantages for many applications.
+The goal of this project is to provide SIMD-enhanced versions of common libc functions (mostly those described in man:string[3]), speeding up most C programs.
+
+For each function optimised, up to four implementations will be provided:
+
+ * a *scalar* implementation optimised for amd64, but without any SIMD usage,
+ * either a *baseline* implementation using SSE and SSE2, or an *x86-64-v2* implementation using all SSE extensions up to SSE4.2,
+ * an *x86-64-v3* implementation using AVX and AVX2, and
+ * an *x86-64-v4* implementation using AVX-512F/BW/CD/DQ.
+
+Users will be able to select which level of SIMD enhancements to use by setting the `ARCHLEVEL` environment variable.
+
+While the current project only concerns amd64, the work may be expanded to other architectures like arm64 in the future.
+
+During the last few months, significant progress has been made on this project.
+SIMD-enhanced versions of man:bcmp[3], man:index[3], man:memchr[3], man:memcmp[3], man:stpcpy[3], man:strchr[3], man:strchrnul[3], man:strcpy[3], man:strcspn[3], man:strlen[3], man:strnlen[3], and man:strspn[3] have landed.
+Functions man:memcpy[3], man:memmove[3], man:strcmp[3], man:timingsafe_bcmp[3] (see link:https://reviews.freebsd.org/D41673[D41673]), and man:timingsafe_memcmp[3] (see link:https://reviews.freebsd.org/D41696[D41696]) are work in progress.
+Unfortunately, the work has not made the cut for FreeBSD 14.0, but it is slated to be part of FreeBSD 14.1.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-07-2023-09/squashfs.adoc b/website/content/en/status/report-2023-07-2023-09/squashfs.adoc
new file mode 100644
index 0000000000..70fd1484a4
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/squashfs.adoc
@@ -0,0 +1,29 @@
+=== SquashFS driver for FreeBSD kernel
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[Wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[] +
+link:https://github.com/Mashijams/freebsd-src/tree/gsoc/testing[Source code] URL: link:https://github.com/Mashijams/freebsd-src/tree/gsoc/testing[]
+
+Contact: Raghav Sharma <raghav@FreeBSD.org>
+
+This quarter we finished SquashFS driver work for the kernel.
+We now can mount SquashFS archives on FreeBSD 13.2-RELEASE or greater, and perform all basic read-only filesystem operations.
+
+Code work includes:
+
+* Implementing vop_lookup() and vop_readdir() hooks for directory read support.
+* Implementing vop_read() and vop_strategy() hooks for files read support.
+* Implementing vop_readlink() hook for symlinks read support.
+
+We also implemented extended attributes interface functions for SquashFS.
+All that remains is to implement their kernel interface hooks.
+
+There were a lot of bug fixes as well.
+One major issue was to find out why we can not list the first entry of the root directory, it transpires that SquashFS could have `inode_number` as zero, which the kernel, for some reason, skips while listing dirents.
+For now, we fixed it by passing dummy `inode_number`, instead of zero, to dirent.
+
+The code review is currently ongoing with my mentor mailto:chuck@FreeBSD.org[Chuck Tuffli].
+
+I am happy to say that SquashFS will find its place in upcoming FreeBSD releases.
+
+Sponsor: The Google Summer of Code 2023 program
diff --git a/website/content/en/status/report-2023-07-2023-09/ufs_snapshots.adoc b/website/content/en/status/report-2023-07-2023-09/ufs_snapshots.adoc
new file mode 100644
index 0000000000..fb755ab7c9
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/ufs_snapshots.adoc
@@ -0,0 +1,18 @@
+=== Enabling Snapshots on Filesystems Using Journaled Soft Updates
+
+Contact: Marshall Kirk McKusick <mckusick@FreeBSD.org>
+
+This project has made UFS/FFS filesystem snapshots available when running with journaled soft updates.
+The details of this project were link:https://www.freebsd.org/status/report-2022-10-2022-12/#_enabling_snapshots_on_filesystems_using_journaled_soft_updates[described in the 2022 fourth quarter report].
+
+This project had two milestones:
+
+The first milestone of this project was to make it possible to take snapshots when running with journaled soft updates and to use them for doing background dumps on a live filesystem.
+Background dumps are requested by using the -L flag to man:dump[8].
+This milestone was completed in Q4 of 2022 and was made available in the 13.2 release as link:https://www.freebsd.org/status/report-2023-01-2023-03/#_enabling_snapshots_on_filesystems_using_journaled_soft_updates_in_13_2[described in the 2023 first quarter report].
+
+The second milestone of this project was to do a background check using a snapshot on a filesystem running with journaled soft updates.
+This milestone was completed in the third quarter of 2023 in time to be included as part of the 14.0 release.
+It was also made available in the 13.2-STABLE release.
+
+Sponsored by: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-07-2023-09/valgrind.adoc b/website/content/en/status/report-2023-07-2023-09/valgrind.adoc
new file mode 100644
index 0000000000..2433adc4de
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/valgrind.adoc
@@ -0,0 +1,24 @@
+=== Valgrind: valgrind-devel updated for FreeBSD 15
+
+Links: +
+link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] +
+link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[]
+
+Contact: Paul Floyd <pjfloyd@wanadoo.fr>
+
+package:devel/valgrind-devel[] is in the process of being updated.
+This contains most of what will be in the official release of Valgrind 3.22 due out in October.
+
+`memcheck` has been enhanced with some more checks.
+It will now report usage of `realloc` with a size of zero.
+Such usage is not portable and is deprecated (C23 will make it Undefined Behaviour).
+`memcheck` now validates the values used for alignment and sized delete for `memalign`, `posix_memalign`, `aligned_alloc` and all aligned and sized overloads of `operator new` and `operator delete`.
+Reading `DWARF` debuginfo is now done in a lazy manner which can improve performance.
+
+As usual there are numerous small bugfixes.
+
+Specific to FreeBSD there is now support for FreeBSD 15.
+Two extra `_umtx_op` operations are now supported, `UMTX_OP_GET_MIN_TIMEOUT` and `UMTX_OP_SET_MIN_TIMEOUT`.
+There is a fix for the use of sysctl kern proc pathname with the guest pid or -1, which previously returned the path of the Valgrind host.
+The sysctl will now return the path of the guest.
+Support for the `close_range` system call has been added.
diff --git a/website/content/en/status/report-2023-07-2023-09/wifibox.adoc b/website/content/en/status/report-2023-07-2023-09/wifibox.adoc
new file mode 100644
index 0000000000..bba1507c68
--- /dev/null
+++ b/website/content/en/status/report-2023-07-2023-09/wifibox.adoc
@@ -0,0 +1,30 @@
+=== Wifibox: Use Linux to Drive your Wireless Card on FreeBSD
+
+Links: +
+link:https://github.com/pgj/freebsd-wifibox[Project GitHub Page] URL: link:https://github.com/pgj/freebsd-wifibox[] +
+link:https://cgit.freebsd.org/ports/tree/net/wifibox[net/wifibox port] URL: link:https://cgit.freebsd.org/ports/tree/net/wifibox[]
+
+Contact: PÁLI Gábor János <pali.gabor@gmail.com>
+
+Wifibox is an experimental project for exploring the ways of deploying a virtualized Linux guest to drive wireless networking cards on the FreeBSD host system.
+There have been guides to describe how to set this up manually, and Wifibox aims to implement those ideas as a single easy-to-use software package.
+
+* It uses man:bhyve[8] to run the embedded Linux system.
+This helps to achieve low resource footprint.
+It requires an x64 CPU with I/O MMU (AMD-Vi, Intel VT-d), ~150 MB physical memory, and some disk space available for the guest virtual disk image, which can be even ~30 MB only in certain cases.
+It works with FreeBSD 12 and later, some cards may require FreeBSD 13 though.
+* The guest is constructed using link:https://alpinelinux.org/[Alpine Linux], a security-oriented, lightweight distribution based on link:https://www.musl-libc.org/[musl libc] and link:https://busybox.net/[BusyBox], with some custom extensions and patches imported from link:https://archlinux.org/[Arch Linux] most notably.
+It is shipped with a number of diagnostic tools for better management of the hardware in use.
+The recent version features Linux 6.1, but Linux 6.5 is also available as an alternative.
+* Configuration files are shared with the host system.
+The guest uses man:wpa_supplicant[8] or man:hostapd[8] (depending on the configuration) so it is possible to import the host's man:wpa_supplicant.conf[5] or man:hostapd.conf[5] file without any changes.
+* When configured, man:wpa_supplicant[8] and man:hostapd[8] control sockets could be exposed by the guest, which enables use of related utilities directly from the host, such as man:wpa_cli[8] or man:wpa_gui[8] from the package:net/wpa_supplicant_gui[] package, or man:hostapd_cli[8].
+* Everything is shipped in a single package that can be easily installed and removed.
+This comes with an man:rc[8] system service that automatically launches the guest on boot and stops it on shutdown.
+* It can be configured to forward IPv6 traffic, which is currently an experimental option but turned on by default.
+
+Wifibox has been mainly tested with Intel chipsets, and it has shown great performance and stability.
+Therefore, it might serve as an interim solution whilst FreeBSD matures its support for these chipsets.
+
+It was confirmed that Wifibox works with Atheros, Realtek, and Mediatek chipsets too, and feedback is more than welcome about others.
+Broadcom chips (that are often found in MacBook Pros) can also work, but there are known stability issues.
diff --git a/website/content/en/status/report-2023-10-2023-12/_index.adoc b/website/content/en/status/report-2023-10-2023-12/_index.adoc
new file mode 100644
index 0000000000..019143f8a0
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/_index.adoc
@@ -0,0 +1,163 @@
+---
+title: "FreeBSD Status Report Fourth Quarter 2023"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2023-10-2023-12
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+'''
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+include::{reports-path}/bugmeister.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+'''
+
+include::{reports-path}/service-jails.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+'''
+
+include::{reports-path}/packrat.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+'''
+
+include::{reports-path}/armv7.adoc[]
+
+'''
+
+include::{reports-path}/simd.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+'''
+
+include::{reports-path}/openstack.adoc[]
+
+'''
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/ec2.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+'''
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-online-editor.adoc[]
+
+'''
+
+include::{reports-path}/wiki.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/gnome-contributions.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+'''
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2023-10-2023-12/armv7.adoc b/website/content/en/status/report-2023-10-2023-12/armv7.adoc
new file mode 100644
index 0000000000..b093019b52
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/armv7.adoc
@@ -0,0 +1,17 @@
+=== armv7 Ports Quality Assurance
+
+Contact: Robert Clausecker <fuz@FreeBSD.org>
+
+As part of a long term project to improve the quality of the FreeBSD ports collection for the armv7 architecture, a number of issues in the base system and in various ports have been fixed.
+Through this action, the number of binary packages that could be successfully built from the 2023Q4 branch of the ports collection was increased from 30018 (as of 2023-10-04) to 31118 (as of 2023-11-24).
+
+Two kernel bugs affecting package builds (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267788[PR 267788] and link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274705[PR 274705]) were identified and addressed, with these two alone being responsible for around 900 failed packages.
+The most common other causes for build failures include
+
+ * lack of FreeBSD-specific armv7 support code
+ * data alignment issues (armv7 being one of the few architectures for which we do not support unaligned memory accesses)
+ * address space exhaustion during the build processes (usually LTO related; link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274705[PR 274705] addressed many cases)
+ * lack of OpenMP support on armv7 FreeBSD
+
+If you are a user of the FreeBSD ports collection on armv7, do not hesitate to file a bug report on our link:https://bugzilla.freebsd.org[bug tracker] should there be any issues.
+
diff --git a/website/content/en/status/report-2023-10-2023-12/azure.adoc b/website/content/en/status/report-2023-10-2023-12/azure.adoc
new file mode 100644
index 0000000000..26331823a0
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/azure.adoc
@@ -0,0 +1,32 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+
+In this quarter, we have solved all the blocking issues and published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-14_0[14.0-RELEASE on Azure Marketplace], with complete architecture (amd64, arm64) and VM generation (gen1, gen2) support, available in both UFS and ZFS as the root file system.
+
+Work in progress tasks:
+
+* Automating the image building and publishing process and merging to [.filename]#src/release/#.
+* Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+
+The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+
+Open tasks:
+
+* Update FreeBSD related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Support FreeBSD in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+* Update link:https://www.freshports.org/sysutils/azure-agent[Azure agent port] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure]
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2023-10-2023-12/bugmeister.adoc b/website/content/en/status/report-2023-10-2023-12/bugmeister.adoc
new file mode 100644
index 0000000000..d023aa8e5f
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/bugmeister.adoc
@@ -0,0 +1,47 @@
+=== Bugmeister Team and Bugzilla
+
+Links: +
+link:https://www.freebsd.org/administration/#t-bugmeister[Bugmeister team] URL: link:https://www.freebsd.org/administration/#t-bugmeister[] +
+link:https://bugs.freebsd.org/bugzilla/[FreeBSD Bugzilla] URL: link:https://bugs.freebsd.org/bugzilla/[]
+
+Contact: Bugmeister <bugmeister@FreeBSD.org>
+
+Some recent maintenance has been done on our Bugzilla instance:
+
+* the weekly reminder emails now include the correct values for mfc-* Flags queries;
+* the Dashboard page has had an obsolete query removed.
+(We no longer use the 'patch-ready' Keyword; it was too much paperwork.
+Thus, the query on that field was useless.);
+* the limit that capped the maximum number of reported PRs at 10000 has been raised to 12500.
+
+In addition, the Wiki documentation on our Bugzilla has been
+updated:
+
+* the page link:https://wiki.freebsd.org/Bugzilla/SearchQueries[] has been substantially reworked:
+** In particular, documentation about how to search on Flag values has been added.
+(This may not have been done before.)
+Example: search for PRs with Flag 'mfc-stable14' set;
+** This page may be of interest to all committers and contributors;
+
+* the page https://wiki.freebsd.org/Bugmeister/BugmeisterQA has also been updated;
+While similar to the above, it is of more specific interest to bugmeister and triagers.
+
+As well, PRs that are specific to FreeBSD 12 are being culled, as 12 has gone out of support as of 20231231.
+
+A further effort is being made to document our setup of Bugzilla itself, especially with respect to our customizations.
+This is needed to bring our own repository up to date with what is running
+on production.
+
+The number of PRs over the past quarter (and year) has remained consistent.
+However, we do seem to be closing incoming PRs more quickly these days.
+For reference: link:https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90[].
+
+The overall number of PRs remains around 11,400.
+
+Bugmeister is also working towards restarting the Bugathons.
+See the updated page link:https://wiki.freebsd.org/Bugathons[].
+
+Bugmeister would like to thank a number of people who have assisted with bugbusting, including Mina Galić, Graham Perrin, mailto:salvadore@FreeBSD.org[Lorenzo Salvadore], and mailto:fernape@FreeBSD.org[Fernando Apesteguìa], among others.
+
+In addition, bugmeister would like to thank all the FreeBSD committers who help process the PRs as they come in.
+Over the last few months we seem to be much closer to steady-state.
diff --git a/website/content/en/status/report-2023-10-2023-12/ci.adoc b/website/content/en/status/report-2023-10-2023-12/ci.adoc
new file mode 100644
index 0000000000..fec13a4c7b
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/ci.adoc
@@ -0,0 +1,50 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://tinderbox.freebsd.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the fourth quarter of 2023, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* Adding job to build amd64 architecture with GCC 13 (thanks jhb@)
+* Adding powerpc64le jobs config for stable-14 (thanks alfredo@)
+* Updating the build env of jobs of main and stable/14 branches to 14.0-RELEASE
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing and pull/merged-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+** Proof of concept system is in progress
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Redesigning the hardware test lab and adding more hardware for testing
+* Merge link:https://reviews.freebsd.org/D38815[]
+* Merge link:https://reviews.freebsd.org/D36257[]
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-10-2023-12/clusteradm.adoc b/website/content/en/status/report-2023-10-2023-12/clusteradm.adoc
new file mode 100644
index 0000000000..da3375e991
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/clusteradm.adoc
@@ -0,0 +1,46 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular support for FreeBSD.org user accounts.
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* Enable mirroring of link:https://www.FreeBSD.org[] and link:https://docs.FreeBSD.org[] in the FreeBSD project-managed mirrors.
+* Cluster refresh, upgrading all hosts and jails to the most recent versions of 15-CURRENT, 14-STABLE, 13-STABLE, and 12-STABLE.
+* Begin sunsetting 12-STABLE infrastructure as the branch approaches its end of life.
+
+In addition to these projects, with link:https://www.modirum.com[Modirum] generously link:https://github.com/sponsors/ppaeps/[sponsoring Philip's time] for most of October, we were able to bring pkgbase into "preview" production in time for 14.0-RELEASE in November.
+
+We also installed a new European mirror site in Sjöbo, Sweden, sponsored by Teleservice Skåne AB.
+Traffic in Europe is now directed roughly equally between our existing mirror in Frankfurt (sponsored by Equinix) and the new mirror in Sweden.
+After well over ten years in service, we plan to decommission our mirror site in the UK during first quarter of 2024.
+We would like to thank link:https://www.bytemark.co.uk/[Bytemark Hosting] for supporting this mirror for all this time.
+
+Next quarter, supported by the FreeBSD Foundation, we plan to bring up a new primary cluster site in Chicago.
+
+==== FreeBSD Official Mirrors Overview
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America -- California, New Jersey (primary site), and Washington.
+
+The hardware and network connection have been generously provided by:
+
+* https://www.bytemark.co.uk/[Bytemark Hosting] (decommissioned during 2024Q1)
+* Cloud and SDN Laboratory at https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc]
+* https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University]
+* https://deploy.equinix.com/[Equinix]
+* https://internet.asn.au/[Internet Association of Australia]
+* https://www.isc.org/[Internet Systems Consortium]
+* https://www.inx.net.za/[INX-ZA]
+* https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc]
+* https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network]
+* https://www.metapeer.com/[Metapeer]
+* https://nic.br/[NIC.br]
+* https://your.org/[Your.Org]
+* https://365datacenters.com/[365 Data Centers]
+* https://www.teleservice.net/[Teleservice Skåne AB] (new since 2023Q4)
diff --git a/website/content/en/status/report-2023-10-2023-12/core.adoc b/website/content/en/status/report-2023-10-2023-12/core.adoc
new file mode 100644
index 0000000000..b94d88473d
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/core.adoc
@@ -0,0 +1,30 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+Along the release engineering team, the project dedicates the 14.0-RELEASE to the memory of Hans Petter Selasky.
+
+==== 14.0-RELEASE
+
+FreeBSD 14.0 was released at the end of 2023Q4.
+
+The release notes can be found at
+
+        https://www.freebsd.org/releases/14.0R/relnotes/
+
+
+==== New Release Engineering Team
+
+After years of serving as the release engineer gjb@ stepped down.
+
+cperciva@ took over as the new release engineer.
+karels@ is serving as the new deputy release engineer.
+
+Core would like to thank gjb@ for his long tenure and the many timely releases he created.
+
+==== FreeBSD 2024 Community Survey
+
+In the end of 2023, Core Team works with the Foundation to do the 2024
+community survey.
diff --git a/website/content/en/status/report-2023-10-2023-12/doceng.adoc b/website/content/en/status/report-2023-10-2023-12/doceng.adoc
new file mode 100644
index 0000000000..8dfc307351
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/doceng.adoc
@@ -0,0 +1,99 @@
+////
+Quarter:	4th quarter of 2023
+Prepared by:	fernape
+Reviewed by:	
+Last edit:	$Date$
+Version:	$Id$
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During the last quarter:
+
+Glen Barber stepped down from doceng.
+doceng would like to thank gjb@ for his service.
+
+Ceri Davies' commit bit was taken for safekeeping as per his request.
+doceng would like to thank ceri@ for his contributions.
+
+mhorne@ to be mentored by carlavilla@ to obtain a documentation commit bit.
+
+==== FreeBSD Handbook:
+
+The Handbook was updated to show that FreeBSD 14.0 is the latest release.
+
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblate[] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/[]
+
+===== Q4 2023 Status
+
+* 17 team languages
+* 203 registered users
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 7%)
+* Chinese (Traditional) (zh-tw)	(progress: 3%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 5%)
+* Korean (ko)			(progress: 33%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 2%)
+* Polish			(progress: 1%)
+* Portuguese			(progress: 0%)
+* Portuguese (pt-br)		(progress: 22%)
+* Spanish (es)			(progress: 35%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+==== FreeBSD Handbook working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+ * link:https://reviews.freebsd.org/D40546[The Network chapter has been rewritten]
+ * link:https://cgit.freebsd.org/doc/commit/?id=612b7cc1721224c494c5b2600188e1508bb5611b[The Jails chapter has been rewritten]
+ * The next section to work on will be the file systems part: UFS, ZFS, Other File Systems
+
+==== FAQ Working Group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+A new FAQ was released alongside FreeBSD 14.0.
+
+==== FreeBSD Website Revamp - WebApps working group
+
+Contact: Sergio Carlavilla <carlavilla@FreeBSD.org>
+
+Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components.
+FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21.
+The work will be divided into three phases:
+
+. Redesign of the Manual Pages on web
++
+Scripts to generate the HTML pages using mandoc. (_Complete, Approved by Doceng, Deploy Date Not Decided Yet_)
+Public instance on https://man-dev.FreeBSD.org
+
+. Redesign of the FreeBSD main website
++
+New design, responsive and dark theme. (_Almost Complete, Presented at EuroBSDCon_)
+
+. Redesign of the Ports page on web
++
+Ports scripts to create an applications portal. (_Work in progress_)
diff --git a/website/content/en/status/report-2023-10-2023-12/ec2.adoc b/website/content/en/status/report-2023-10-2023-12/ec2.adoc
new file mode 100644
index 0000000000..5528094687
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/ec2.adoc
@@ -0,0 +1,18 @@
+=== FreeBSD on EC2
+
+Links: +
+link:https://www.patreon.com/cperciva[FreeBSD/EC2 Patreon]	URL: https://www.patreon.com/cperciva[]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances.
+Work continues to ensure that upcoming instance types will be supported; most recently, changes were needed to support "7th generation" Intel and AMD instances.
+
+FreeBSD 14.0-RELEASE shipped with experimental ZFS-root AMIs and "cloud-init" AMIs.
+Additional "flavored" FreeBSD AMIs are planned, including "AMI Builder" and "minimal" (no debug symbols).
+
+A bug in the release-building process which resulted in 14.0-RELEASE AMIs shipping with duplicate lines in /etc/rc.conf has been corrected and future releases should not be affected.
+
+A bug in the ec2-aws-imdsv2-get utility which resulted in 14.0-RELEASE AMIs not supporting binary user-data files has been corrected and future releases should not be affected.
+
+This work is supported by Colin's FreeBSD/EC2 Patreon.
diff --git a/website/content/en/status/report-2023-10-2023-12/freebsd-foundation.adoc b/website/content/en/status/report-2023-10-2023-12/freebsd-foundation.adoc
new file mode 100644
index 0000000000..b2f2eb8237
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/freebsd-foundation.adoc
@@ -0,0 +1,133 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] +
+link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD.
+We do this in both technical and non-technical ways.
+We are 100% supported by donations from individuals and corporations and those investments help us fund the:
+
+* Software development projects to implement features and functionality in FreeBSD
+* Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD
+* Purchase and support of hardware to improve and maintain FreeBSD infrastructure,
+* Resources to improve security, quality assurance, and continuous integration efforts.
+* Materials and staff needed to promote, educate, and advocate for FreeBSD,
+* Collaboration between commercial vendors and FreeBSD developers,
+* Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity.
+
+We supported FreeBSD in the following ways during the last quarter of 2023:
+
+==== OS Improvements
+
+During the fourth quarter of 2023, 236 src, 47 ports, and 33 doc tree commits identified The FreeBSD Foundation as a sponsor.
+Some of this Foundation-sponsored work is described in separate report entries:
+
+* <<_openstack_on_freebsd,OpenStack on FreeBSD>>
+* <<_simd_enhancements_for_amd64,SIMD enhancements for amd64>>.
+
+Three new contractors started.
+Cheng Cui began working full-time on wireless networking.
+A main goal for Cheng's project is to assist Bjoern Zeeb with 802.11ac support in iwlwifi.
+Tom Jones began work to port the Vector Packet Processor (VPP) to FreeBSD.
+VPP is an open-source, high-performance user space networking stack that provides fast packet processing suitable for software-defined networking and network function virtualization applications.
+Olivier Certner joined the FreeBSD Foundation as a general FreeBSD developer.
+Some of Olivier's contributions so far include:
+
+* reviewing, fixing, and hardening several security policies aimed at limiting process visibility, policies that are based on user identity, group membership, or sub-jail membership
+* committing fixes in the login class code, including one that allowed unprivileged users to bypass resource limits
+* implementing a secure hardware fix for the Zenbleed issue affecting AMD Zen2 processors.
+
+Here is a sampling of other Foundation-sponsored work completed over the last quarter of 2023:
+
+* arm64: Add Armv8 rndr random number provider
+* net80211, LinuxKPI, and iwlwifi fixes and improvements
+* OpenSSL: updates to 3.0.11 and 3.0.12
+* Various freebsd-update fixes in preparation for 14.0
+* ssh: Update to OpenSSH 9.5p1
+* Various iommu fixes
+* Various makefs/zfs fixes
+
+Learn more about our software development work for all of 2023 at https://freebsdfoundation.org/blog/2023-in-review-software-development/.
+
+==== FreeBSD Infrastructure
+
+We approved over $100,000 for a cluster refresh that began in late 2023 and will carry over into the new year by purchasing and shipping 15 new servers to 4 racks generously donated by NYI in their new Chicago facility.
+The systems specifications were determined by the Cluster Administration team and consist of:
+
+* 5 package builders
+* 3 web servers
+* 2 package mirrors
+* 2 CI servers
+* 2 firewall/router
+* 1 admin bastion
+
+More on our 2023 infrastructure support can be found at: https://freebsdfoundation.org/blog/2023-in-review-infrastructure/.
+
+==== Continuous Integration and Workflow Improvement
+
+As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project's continuous integration system and the test infrastructure.
+The full update can be found within the quarterly status report.
+
+==== Partnerships and Research
+
+In Q4 I connected with the following people, companies, and organizations: Phil Shafer, who works at Juniper Networks, and I met at All Things Open.
+He told me about the libxo library and his continuing work on related issues, like rewriting and filtering output to allow richer options that regular expressions provide.
+Sticking with Juniper, I also met Simon Gerraty at the Vendor Summit and heard his talk on link:https://www.youtube.com/live/k-AzShVdAHo?si=otJvsMLc3gqilZSU&t=22069[SecureBoot].
+In alphabetical order, I also met with AMD, Ampere, Center for Internet Security (CIS), Innovate UK, Michael Dexter, Metify, Microsoft, several people at NetApp when I attended their annual conference (Thank you for the invitation!!), NetScaler, NIST, Nozomi Networks, NVIDIA, members of the Open Container Initiative community, OpenSSF, RG Nets, Doug Rabson.
+
+I greatly appreciated the opportunity to attend NetApp's annual conference in October.
+I heard from and connected with experts at NetApp and their partners and customers on topics such as AI and seamless AI data pipelines, hybrid cloud, and green computing.
+I took the opportunity to hand out some FreeBSD lapel pins 🙂 and I connected with a FreeBSD user and member of the Enterprise WG whose company is a NetApp Customer.
+
+In Q4 we link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-announces-ssdf-attestation/[announced the new FreeBSD SSDF Attestation] program to help commercial users of FreeBSD comply with new US Government procurement regulations.
+This program was informed by valuable feedback from NetApp, Metify, and NIST, and the genesis of the idea came thanks to my involvement with open source policy experts, in particular via the OSI's Open Policy Alliance.
+
+The link:https://github.com/opencontainers/tob/pull/133[Open Container Initiative Technical Oversight Board voted] in December to approve Doug Rabson's proposal to create a Working Group to extend the OCI runtime specification to support FreeBSD.
+Huge thanks to all involved!
+An OCI runtime extension for FreeBSD is one of the most frequently requested capabilities and I was happy to play a small role in helping to coordinate this effort so far.
+
+The Vendor Summit in November was a great event.
+Huge props to John Baldwin and Anne Dickison for all the work to organize and orchestrate.
+I got a lot out of the event.
+Personal highlights were conversations with a diversity of users, the CHERI talk, the end user panel, and Allan's talk on being an upstream first company.
+For a full recap on our efforts to strengthen partnerships and increase funding in 2023, check out: link:https://freebsdfoundation.org/blog/2023-in-review-partnerships-and-research/[].
+
+==== Advocacy
+
+From organizing and attending events, to creating technical content that educates, and expanding the coverage of FreeBSD in the media, here is a sample of what we did last quarter to support FreeBSD.
+
+* Helped organize and sponsor the November 2023 Vendor Summit held at NetApp in San Jose.
+  Many consider this one of the best summits to date.
+  Be sure to check out the link:https://youtube.com/playlist?list=PLugwS7L7NMXzSalaF4l_78sfRa2l8xvag&feature=shared[videos].
+* Introduced FreeBSD to new and returning folks at link:https://freebsdfoundation.org/blog/all-things-open-2023-conference-report/[All Things Open] in North Carolina.
+* Provided an overview of FreeBSD 14: link:https://freebsdfoundation.org/blog/security-performance-and-interoperability-introducing-freebsd-14/[Security, Performance, and Interoperability; Introducing FreeBSD 14]
+* In collaboration with the Core team, released the link:https://freebsdfoundation.org/blog/2024-freebsd-community-survey-is-here/[2024 FreeBSD Community Survey]
+* Participated in an interview about FreeBSD: link:https://freebsdfoundation.org/news-and-events/latest-news/what-the-dev-podcast-the-evolution-of-the-freebsd-project/[What the Dev Podcast: The Evolution of the FreeBSD Project]
+* Release the link:https://freebsdfoundation.org/past-issues/13099/[September/October 2023] issue of the FreeBSD Journal now with HTML versions of the articles.
+
+For a full recap of what we did to advocate for FreeBSD in 2023, please check out the Advocacy Year in Review: link:https://freebsdfoundation.org/blog/2023-in-review-advocacy/[] or the monthly  newsletters: link:https://freebsdfoundation.org/our-work/latest-updates/?filter=newsletter[].
+
+==== Fundraising
+
+Thank you to everyone who gave us a financial contribution last quarter to help fund our work to support the Project.
+You brought us even closer to our goal and we are grateful for your investment in FreeBSD!
+We are still receiving donations in the mail and will post the final number in mid-February.
+
+Please consider supporting our efforts in 2024 by making a donation here: link:https://freebsdfoundation.org/donate/[].
+
+Or, check out our Partnership opportunities here:
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[].
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2023-10-2023-12/freebsd-online-editor.adoc b/website/content/en/status/report-2023-10-2023-12/freebsd-online-editor.adoc
new file mode 100644
index 0000000000..88bae2050c
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/freebsd-online-editor.adoc
@@ -0,0 +1,21 @@
+=== FreeBSD Online Editor and Man Page Editor
+
+Links: +
+link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[FreeBSD Online Document Editor] URL: link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[] +
+link:https://github.com/Wang-Yan-Hao/man_page_editor[FreeBSD Online Man Page Editor] URL: link:https://github.com/Wang-Yan-Hao/man_page_editor[]
+
+Contact: Yan-Hao Wang <bses30074@gmail.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+This report provides a continued overview of the FreeBSD online editor and man page editor project, outlining recent efforts to enhance the documentation and manual page editing processes.
+In order to optimize the project's structural integrity, we enlisted the expertise of a professional front-end programmer.
+We plan to release the editor soon and currently have some tasks that require additional support.
+
+1. We are actively seeking a qualified individual to conduct a comprehensive front-end security review of the project.
+
+2. A meticulous inspection of the JavaScript code is imperative to ensure its robustness and efficiency.
+We are looking for someone with expertise to thoroughly examine the codebase, identify any issues, and propose enhancements for optimal performance.
+
+3. Since there is currently no existing JavaScript library for rendering mandoc, I had to create my own.
+However, there are still some hidden errors that emerge during the editing process.
+We are seeking assistance to fix these rendering issues.
diff --git a/website/content/en/status/report-2023-10-2023-12/gcc.adoc b/website/content/en/status/report-2023-10-2023-12/gcc.adoc
new file mode 100644
index 0000000000..c9bef54c0d
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/gcc.adoc
@@ -0,0 +1,25 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[]
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[Updating GCC default version to 13] is moving ahead.
+Thanks to mailto:antoine@FreeBSD.org[Antoine Brodin] who ran the exp-runs and to all other developers and ports maintainers involved.
+
+As you might remember from last quarter, additional patches were tested together with the default version updates.
+Some of them have already been merged:
+
+* package:lang/gcc11[] has switched back to STANDARD_BOOTSTRAP and has been updated to 11.4.0;
+* package:lang/gcc13[] has been updated to version 13.2.0.
+
+About half of the open bugs have been fixed, but another half remains.
+If you maintain any of the affected ports, please try to fix your port(s) and/or get your port buildable with the compiler in base.
+
+This quarter many bug reports have also been opened about GCC.
+As soon as the default GCC version update is finished, all of those bugs will be addressed.
diff --git a/website/content/en/status/report-2023-10-2023-12/gnome-contributions.adoc b/website/content/en/status/report-2023-10-2023-12/gnome-contributions.adoc
new file mode 100644
index 0000000000..077c854883
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/gnome-contributions.adoc
@@ -0,0 +1,47 @@
+=== State of GNOME 44
+
+Links: +
+link:https://www.gnome.org/[GNOME] URL: link:https://www.gnome.org/[] +
+link:https://codeberg.org/olivierd/freebsd-ports-gnome[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-gnome[]
+
+Contact: FreeBSD GNOME Team <gnome@FreeBSD.org> +
+Contact: Olivier Duchateau <duchateau.olivier@gmail.com>
+
+GNOME is a full desktop environment which is mainly based on GLib, GTK3/GTK4, and libadwaita.
+It provides two window managers or compositors: package:x11-wm/mutter[] and package:x11-wm/metacity[].
+
+Currently in the ports collection, package:x11/gnome-shell[] is not supported by upstream anymore.
+As it is a lot of work, in order to have GNOME 44 available for users, I decided to split this update, because it impacts several ports.
+
+As a maintainer of package:x11/budgie[] and Pantheon desktop (a window manager based on package:x11-wm/mutter[], developed for link:https://elementary.io/[elementary OS]) I need more recent versions of some GNOME libraries.
+
+Firstly I worked on WebKitGTK.
+The 4.0 "legacy" API is almost not used by GNOME's libraries.
+The bare minimum is the 4.1 API.
+I created [.filename]#webkit.mk# for the [.filename]#Mk/Uses# framework, in order to _flavorize_ package:www/webkit2-gtk3[].
+There is an link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275914[ongoing effort], but currently it is too unstable.
+Often applications such as Epiphany, mail clients (Geary, Evolution), or the online accounts panel in package:sysutils/gnome-control-center dump core.
+
+Nonetheless, remainder of desktop is usable and the latest release (44.7) of GNOME Shell is functional.
+I have begun sending my first patches for review (as well as those in Bugzilla).
+
+* link:https://reviews.freebsd.org/D43183[D43183]
+* link:https://reviews.freebsd.org/D43230[D43230]
+* link:https://reviews.freebsd.org/D43244[D43244]
+* link:https://reviews.freebsd.org/D40489[D40489]
+
+I have also ported the link:https://wiki.gnome.org/Projects/GnomeFlashback[GNOME Flashback] session module.
+It depends on package:x11-wm/metacity[] and package:x11-toolkits/libwnck3[].
+
+I also maintain a link:https://codeberg.org/olivierd/freebsd-ports-gnome/wiki[documentation], and we can link:https://codeberg.org/olivierd/freebsd-ports-gnome/src/branch/screenshots[see] various desktops available.
+
+GNOME 45 is almost finished, except for GNOME Shell extensions.
+For this release I will focus on Wayland support (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258042[bug #258042] and link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271836[bug #271836]).
+
+Tests and patches are welcomed, especially for WebKitGTK.
+
+Next months I plan to work on:
+
+* Allowing selecting a session in display manager (gdm), it is regression with our patches.
+* Fixing sharing network (VNC, SSH) panel in package:sysutils/gnome-control-center[] and backport for link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275900[bug #275900].
+* Continuing to update applications and libraries for GNOME 45.
diff --git a/website/content/en/status/report-2023-10-2023-12/intro.adoc b/website/content/en/status/report-2023-10-2023-12/intro.adoc
new file mode 100644
index 0000000000..0e49ade0a6
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/intro.adoc
@@ -0,0 +1,11 @@
+Here is the fourth 2023 status report, with 18 entries.
+
+This is the last 2023 quarter.
+As you have probably noticed, this status report comes later than usual and with fewer reports than the preceding quarter.
+Indeed, please keep in mind that the last quarter of every year is for many members of our community the quarter of the celebrations for Christmas and for the New Year, which implies that those members will spend more time with their families and will have less time for their favorite voluntary software projects.
+Thus there is less to report and reports tend to arrive later.
+But finally, here they are.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2023-10-2023-12/kde.adoc b/website/content/en/status/report-2023-10-2023-12/kde.adoc
new file mode 100644
index 0000000000..5cbadf30fe
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/kde.adoc
@@ -0,0 +1,62 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] +
+link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+
+The mailto:kde@FreeBSD.org[KDE team] is part of mailto:desktop@FreeBSD.org[desktop@] and mailto:x11@FreeBSD.org[x11@], building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation.
+The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack.
+
+==== Infrastructure
+
+CMake was updated several times and is now version 3.28.1, the latest upstream release.
+FreeBSD ports are once again fully up-to-date.
+
+Qt5 is now on long-term support and updates only rarely.
+The KDE patch collection is a community-supported branch of Qt which pulls in upstream patches and fixes from the KDE community, and updated to 5.15.12.
+There were several deprecations (see below) in the Qt5 ports.
+
+Qt6 and KDE's upcoming megarelease of KDE Plasma 6 (scheduled for 2024q1) are the next major milestone for the KDE team.
+Qt6 was updated to version 6.6.1 along with the Python bindings for Qt, PySide.
+An alpha-release of KDE Frameworks 6 was added to the ports tree.
+
+==== KDE Stack
+
+KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well.
+These (large) updates land shortly after their upstream release and are not listed separately.
+
+* KDE Frameworks reached version 5.112.
+  The KDE Frameworks 5 series is winding down, although it will a few months still until it enters long-term support upstream.
+* KDE Plasma Desktop was updated to version KDE Plasma 5.27.10.
+* KDE Gear updated to 23.08.4.
+* KDE Frameworks 6 (alpha) 5.247 was updated in the ports tree.
+* KDE Plasma Desktop 6 (beta 2) 5.91.0 was updated in the ports tree.
+
+==== Related Ports
+
+The KDE ecosystem includes a wide range of ports -- most maintained by mailto:kde@FreeBSD.org[kde@], all building on a shared base of Qt and KDE Frameworks.
+The mailto:kde@FreeBSD.org[KDE team] updates them all as needed.
+This quarter the KDE team would like to thank mailto:tcberner@FreeBSD.org[Tobias C. Berner], mailto:arrowd@FreeBSD.org[Gleb Popov] and mailto:jhale@FreebSD.org[Jason E. Hale] again for keeping things up-to-date.
+
+Many ports have been "flavorized" to support a Qt5 and a Qt6 flavor in the ports tree.
+
+Special mention to:
+
+* New port package:x11/xwaylandvideobridge[].
+  By design, X11 applications can’t access window or screen contents for Wayland clients.
+  The video bridge improves Wayland support for screen sharing tools like Discord, MS Teams, Skype, and more.
+  Screen sharing is fully under the control of the Wayland user.
+* Update for package:multimedia/mlt7[] which was updated to 7.20.0.
+* Update for package:sysutils/bsdisks[] which was updated to 0.33.
+* Bugfix for package:devel/llvm15[] to make package:devel/kdevelop[] work again.
+* Security fixes for package:www/qt5-webengine[] and package:www/qt6-webengine[].
+
+==== Deprecations
+
+Web browsers are huge, and have a considerable security surface.
+The venerable package:www/qt5-webkit[] WebKit port was removed on the last day of 2023.
diff --git a/website/content/en/status/report-2023-10-2023-12/openstack.adoc b/website/content/en/status/report-2023-10-2023-12/openstack.adoc
new file mode 100644
index 0000000000..b46fc13337
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/openstack.adoc
@@ -0,0 +1,21 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[]
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+In the fourth quarter, we successfully migrated the originally virtualized OpenStack platform to physical machines running FreeBSD 14.0-STABLE.
+The ported OpenStack components include Keystone, Glance, Placement, Neutron, and Nova.
+As part of this process, we took the opportunity to update link:https://github.com/openstack-on-freebsd/docs[the installation documentation and the list of dependencies].
+
+Moving forward, we encourage users and developers interested in this project to effortlessly recreate the OpenStack platform in their FreeBSD environments following this documentation.
+Any issues or difficulties encountered are welcome to be reported on the link:https://github.com/openstack-on-freebsd/admin/issues[GitHub project page].
+Your contributions will contribute to the refinement of our installation documentation and the overall porting efforts.
+
+In the upcoming quarter, our focus will shift towards incorporating various patches and workarounds generated during the migration process into the project in a more structured code form.
+Additionally, we plan to develop FreeBSD ports for each OpenStack component, further streamlining the installation process.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-10-2023-12/packrat.adoc b/website/content/en/status/report-2023-10-2023-12/packrat.adoc
new file mode 100644
index 0000000000..be08b5c467
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/packrat.adoc
@@ -0,0 +1,63 @@
+=== Packrat - NFS client caching on non-volatile storage
+
+Contact: Rick Macklem <rmacklem@FreeBSD.org>
+
+NFSv4.1/4.2 provides support for a feature called delegations.
+When a NFSv4.1/4.2 client holds a delegation, the client has certain rights to a file, including a guarantee that no other client will make changes to the file unless the delegation is recalled.
+As such, when a client holds a delegation for a file, it can aggressively cache the file's data, knowing that it will not be modified by other clients until it returns the delegation.
+
+This project is intended to allow the NFSv4.1/4.2 client to aggressively cache file data on client local non-volatile storage, when the client holds a delegation for the file.
+I created a patch long ago to try and do this for NFSv4.0, but it was never at a stage where it was worth using.
+This project is a complete rewrite of the patch, done in part because NFSv4.1/4.2 plus other recent NFSv4-related changes make doing this more feasible.
+
+I now have code running fairly well and hope to have a patch ready for others to test this winter.
+Early testing shows promise.
+For a test run of "make buildkernel", the test with and without packrat enabled performed as follows:
+
+.NFS operation counts
+[cols="1,1,1,1,1,1", frame="none", options="header"]
+|===
+| NFS operation counts
+| Getattr
+| Lookup
+| Read
+| Write
+| Total RPCs
+
+|with packrats
+|433506
+|99254
+|0
+|0
+|371736
+
+|without packrats
+|2359913
+|97954
+|10748
+|0
+|2318810
+
+|===
+
+.Elapsed Run Time
+[cols="1,1,1", frame="none", options="header"]
+|===
+| Elapsed Run Time (sec)
+| with packrat
+| without packrat
+
+| 
+|5561
+|6203
+
+|===
+
+As you can see, the packrat case ran a little faster and with fewer RPCs.
+Although this test was run on my little LAN, it is hoped that a NFSv4.1/4.2 mount over a WAN would show a larger difference in performance.
+I will note that the packrat cache was primed by unrolling a tarball of FreeBSD's [.filename]#/usr/src# into the NFSv4.1/4.2 mount.
+
+This will be very much an experimental feature, but it is hoped it will allow NFS mounts to be used more effectively, particularly in WAN situations, such as a mobile laptop.
+
+There is still work to be done, particularly with respect to recovery of delegations after a NFSv4.1/4.2 client restart.
+Hopefully, the next status report will include a URL that allows downloading of a patch for user testing.
diff --git a/website/content/en/status/report-2023-10-2023-12/portmgr.adoc b/website/content/en/status/report-2023-10-2023-12/portmgr.adoc
new file mode 100644
index 0000000000..b2e497dfd2
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/portmgr.adoc
@@ -0,0 +1,71 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL: link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[]
+
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: Tobias C. Berner <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the quarter.
+
+* According to INDEX, there are currently 31,942 ports in the Ports Collection.
+There are currently ~3,100 open ports PRs.
+The quarter saw 9,424 commits by 157 committers on the main branch and 781 commits by 71 committers on the 2023Q4 branch.
+Compared to last quarter, this means a hefty decrease in the number of commits on the main branch (down from 11,454) and slightly fewer backports to the quarterly branch (down from 828).
+The number of ports also fell a bit (down from 34,600).
+
+In Q4 there were around 9424 commits to main.
+The most active committers were:
+
+        sunpoet   2946
+        yuri       861
+        bofh       793
+        jbeich     419
+        fuz        324
+        eduardo    168
+        fernape    160
+        jhale      153
+        thierry    146
+        diizzy     123
+
+During Q4 we welcomed Michael Osipov (michaelo) and  Timothy Beyer (beyert) as new committers, but sadly also had to say goodbye to bland, sbruno, hselasky and gjb.
+
+We invited arrowd, flo and riggs to be part of portmgr-lurkers for the next months.
+
+Support for FreeBSD 12.x was removed at the end of the quarter.
+
+The end of Q4 also saw the introduction of subpackages to the ports tree.
+Similar to when flavors were introduced, new subpackages will require an approval by portmgr before being pushed to the tree.
+With subpackages it is possible to create multiple packages from a single build of a port.
+
+The following happened on the infrastructure side:
+
+* Packages for 14.0-RELEASE were built
+* Poudriere was updated to release-3.4
+
+The no-longer maintained package:www/qt5-webkit[] was removed.
+
+postgresql11, php80, mysql57, percona57, ghostscript9 were removed.
+
+The following default versions changed:
+
+* perl                    to 5.36
+* ghostcript              to 10
+* corosync                to 3
+
+Updates to major ports that happened were:
+
+* package:ports-mgmt/pkg[]          to 1.20.9
+* package:ports-mgmt/poudriere[]    to 3.4.0 (subpackage support)
+* KDE-bits                to plasma-5.27.10, frameworks-5.112, gear-23.08.4, and beta-2
+* package:www/chromium[]            to 120.0.6099.129
+* package:www/firefox[]             to 121.0 (rc1)
+* package:lang/rust[]               to 1.74.1
+* ... and many more ...
+
+During the last quarter, pkgmgr@ ran 26 exp-runs to test various ports upgrades, updates to default versions of ports, subpackage support and base system changes.
diff --git a/website/content/en/status/report-2023-10-2023-12/pot.adoc b/website/content/en/status/report-2023-10-2023-12/pot.adoc
new file mode 100644
index 0000000000..e82a5eec72
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/pot.adoc
@@ -0,0 +1,25 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+
+During this quarter, link:https://github.com/bsdpot/pot/pull/285[Pot 0.16.0] was released containing link:https://github.com/bsdpot/pot/blob/master/CHANGELOG.md[a number of features and fixes], including link:https://github.com/bsdpot/pot/pull/283[a new setting to prevent direct traffic between VNET pots] and link:https://github.com/bsdpot/pot/pull/275[new attributes] to configure pot stop behavior.
+There were also maintenance/stability releases to link:https://github.com/bsdpot/potnet/pull/56[potnet (0.5.0)] and a link:https://github.com/bsdpot/nomad-pot-driver/pull/52[nomad-pot-driver (0.10.0)].
+
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+One of the new container images that have been added during the last quarter is link:https://github.com/bsdpot/potluck/tree/master/zincsearch[Zincsearch], a more light-weight alternative to Elasticsearch written in Go.
+
+The link:https://github.com/bsdpot/potluck/tree/master/mastodon-s3[Mastodon container] is meanwhile powering the public link:https://mastodon.africa[mastodon.africa] instance.
+
+Also, we got some more publicity: link:https://www.bsdnow.tv/536[BSD Now Episode 536] is titled "Pot-flavored Jails".
+
+As always, feedback and patches are welcome.
+
+Sponsors: Nikulipe UAB, Honeyguide Group
diff --git a/website/content/en/status/report-2023-10-2023-12/releng.adoc b/website/content/en/status/report-2023-10-2023-12/releng.adoc
new file mode 100644
index 0000000000..85b73abbd7
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/releng.adoc
@@ -0,0 +1,17 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.3R/schedule/[FreeBSD 13.3-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.3R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the fourth quarter of the year, the Team continued work on 14.0-RELEASE, leading to the final RELEASE build and announcement in November.
+Planning has started for the upcoming 13.3-RELEASE and 14.1-RELEASE cycles.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main* and *stable/13* branches, and (after 14.0-RELEASE) started weekly builds for *stable/14*.
+
+After over a decade as Release Engineering Lead, Glen Barber has retired from the role; his Deputy, Colin Percival, has moved into the Lead role, while Mike Karels has assumed the position of Deputy Release Engineer.
diff --git a/website/content/en/status/report-2023-10-2023-12/service-jails.adoc b/website/content/en/status/report-2023-10-2023-12/service-jails.adoc
new file mode 100644
index 0000000000..ce0d7fcb6c
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/service-jails.adoc
@@ -0,0 +1,33 @@
+=== Service jails -- Automatic jailing of rc.d services
+
+Links: +
+link:https://reviews.freebsd.org/D40370[D40370: Infrastructure for automatic jailing of rc.d-services] URL: link:https://reviews.freebsd.org/D40370[] +
+link:https://reviews.freebsd.org/D40371[D40371: automatic service jails: some setup for full functionality of the services in automatic service jails] URL: link:https://reviews.freebsd.org/D40371[]
+link:https://reviews.freebsd.org/D42779[D42779: Handbook / rc-article update for Service Jails] URL: link:https://reviews.freebsd.org/D42779[]
+
+Contact: Alexander Leidinger <netchild@FreeBSD.org>
+
+Service jails extend the man:rc[8] system to allow automatic jailing of rc.d services.
+A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, ...) by default.
+Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (man:vmm[4]).
+
+If you want to put e.g. local_unbound into a service jail and allow IPv4 and IPv6 access, simply change man:rc.conf[5] to have:
+----
+local_unbound_svcj_options=net_basic
+local_unbound_svcj=YES
+----
+Note: all base system services are covered in the patches with either name_svcj_options or a hard-coded disabling of the service jails feature where it does not make sense (e.g. pure services which change the runtime configuration but do not start daemons, or where things are run which can not be run in a sensible way inside a jail).
+As such the local_unbound_svcj_options line above is superfluous and serves just as an example about the amount of configuration needed in total.
+
+While this does not have the same security benefits as a manual jail setup with a separate filesystem and IP/VNET, it is much easier to set up, while providing some of the security benefits of a jail like hiding other processes of the same user.
+
+Since the link:../report-2023-04-2023-06/#_service_jailsautomatic_jailing_of_rc_d_services[previous service jails status report], the following were added:
+
+* support for NFS inside jails in the service jails framework (untested),
+* the possibility of jailing other service commands than `start` and `stop`,
+* service jails options / config for all base system services in the patch in D40371,
+* a first step at documenting the service jails in the Handbook.
+
+Not all services are tested, but all services are covered with a config.
+
+Any testing and feedback (even as simple as "service X works in a service jail") is welcome.
diff --git a/website/content/en/status/report-2023-10-2023-12/simd.adoc b/website/content/en/status/report-2023-10-2023-12/simd.adoc
new file mode 100644
index 0000000000..533787f764
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/simd.adoc
@@ -0,0 +1,20 @@
+=== SIMD enhancements for amd64
+
+Links: +
+link:https://freebsdfoundation.org/blog/a-sneak-peek-simd-enhanced-string-functions-for-amd64/[FreeBSD Foundation blog post] URL: link:https://freebsdfoundation.org/blog/a-sneak-peek-simd-enhanced-string-functions-for-amd64/[] +
+link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[simd(7)] URL: link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[] +
+link:https://github.com/clausecker/freebsd-src/commits/acceptance-testing[Work currently under acceptance testing] URL: link:https://github.com/clausecker/freebsd-src/commits/acceptance-testing[]
+
+Contact: Robert Clausecker <fuz@FreeBSD.org>
+
+The project to enhance the libc with SIMD implementations of string functions for amd64 has now concluded.
+In total, SIMD implementations for 17 libc functions have been written, complemented by scalar implementations where needed.
+Through this rewrite, performance of these functions on strings with an average length of 64 characters was improved by an average factor of 5.54.
+In addition, 9 other library functions were rewritten to call into the SIMD-enhanced routines, conveying benefits without requiring additional assembly implementations.
+Please see the FreeBSD Foundation blog post linked above for more details.
+
+Parts of the SIMD work are already found in the CURRENT branch.
+The rest is currently undergoing acceptance testing and will be merged if no problems emerge.
+It is planned to back port all improvements to 14-STABLE for inclusion into FreeBSD 14.1.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2023-10-2023-12/wiki.adoc b/website/content/en/status/report-2023-10-2023-12/wiki.adoc
new file mode 100644
index 0000000000..9dee9803c1
--- /dev/null
+++ b/website/content/en/status/report-2023-10-2023-12/wiki.adoc
@@ -0,0 +1,16 @@
+=== FreeBSD Wiki
+
+Links: +
+link:https://wiki.freebsd.org[Wiki]	URL: link:https://wiki.freebsd.org[]
+
+Contact: Wiki administration <wiki-admin@FreeBSD.org>
+
+Plans are underway to familiarize our audience on Discord with the wiki (there are too many "silos" in our FreeBSD community).
+Contact Setesh on the FreeBSD Discord for more information.
+
+Preliminary work is being done on updating the wiki software itself.
+Continuing to run MoinMoin requires a jail with a downrev version of Python.
+The MoinMoin project itself seems to have stalled in the middle of a redesign; at a minimum, a complete upgrade of the backend database would be needed.
+
+Alternatives that are under consideration include MediaWiki and DocuWiki; see link:https://wiki.freebsd.org/Wiki/NextGeneration[].
+Most of the discussion is occurring on Matrix; please contact wiki-admin@FreeBSD.org if you would like to participate.
diff --git a/website/content/en/status/report-2024-01-2024-03/_index.adoc b/website/content/en/status/report-2024-01-2024-03/_index.adoc
new file mode 100644
index 0000000000..a5775e1b8e
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/_index.adoc
@@ -0,0 +1,151 @@
+---
+title: "FreeBSD Status Report First Quarter 2024"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2024-01-2024-03
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+{projects-desc}
+
+include::{reports-path}/audio.adoc[]
+
+'''
+
+include::{reports-path}/bhyve.adoc[]
+
+'''
+
+include::{reports-path}/bsdinstall.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+include::{reports-path}/libsys.adoc[]
+
+'''
+
+include::{reports-path}/packagekit.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+include::{reports-path}/wireless.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+include::{reports-path}/ten64-whle-honeycomb.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/cloud-init.adoc[]
+
+'''
+
+include::{reports-path}/openstack.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+include::{reports-path}/freshports.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/valgrind.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2024-01-2024-03/audio.adoc b/website/content/en/status/report-2024-01-2024-03/audio.adoc
new file mode 100644
index 0000000000..29c5dc9aa2
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/audio.adoc
@@ -0,0 +1,32 @@
+=== Audio Stack Improvements
+
+Contact: Christos Margiolis <christos@FreeBSD.org>
+
+The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement -- from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs.
+This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature.
+
+So far, my focus has been towards the kernel side of the audio stack, with link:https://reviews.freebsd.org/D43545[D43545] being probably the most requested and notable patch.
+I am also working on scrapping the rather outdated "snd_clone" audio device cloning framework of man:sound[4], and replacing it with DEVFS_CDEVPRIV(9) (link:https://reviews.freebsd.org/D44411[D44411]).
+
+Some of the future tasks include:
+
+* Attempt to find a better (ideally automatic) way to handle man:snd_hda[4] pin-patching.
+* Implement an man:oss[3] library and man:audio[8] utility, in similar fashion to man:mixer[3] and man:mixer[8].
+* Write a bluetooth device management utility.
+* Improve man:mixer[3] and man:mixer[8].
+* Improve documentation and test suite where needed.
+
+A more detailed description can be found link:https://lists.freebsd.org/archives/freebsd-multimedia/2023-December/002088.html[here].
+
+You can also follow the development process in link:https://lists.freebsd.org/subscription/freebsd-multimedia[freebsd-multimedia@], where I post regular reports:
+
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002158.html[Report #1]
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002179.html[Report #2]
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002209.html[Report #3]
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002229.html[Report #4]
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-February/002248.html[Report #5]
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-February/002252.html[Report #6]
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-March/002273.html[Report #7]
+* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-March/002286.html[Report #8]
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-01-2024-03/azure.adoc b/website/content/en/status/report-2024-01-2024-03/azure.adoc
new file mode 100644
index 0000000000..a1e24f66e7
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/azure.adoc
@@ -0,0 +1,32 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.freebsd.org/subscription/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+
+In this quarter, we have solved all the blocking issues and published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-13_3[13.3-RELEASE on Azure Marketplace].
+
+Work in progress tasks:
+
+* Automating the image building and publishing process and merging to [.filename]#src/release/#.
+* Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+
+The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+
+Open tasks:
+
+* Update FreeBSD-related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Support FreeBSD in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+* Update link:https://www.freshports.org/sysutils/azure-agent[Azure agent port] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure]
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2024-01-2024-03/bhyve.adoc b/website/content/en/status/report-2024-01-2024-03/bhyve.adoc
new file mode 100644
index 0000000000..23fd2b6e62
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/bhyve.adoc
@@ -0,0 +1,72 @@
+=== Bhyve Improvements
+
+Links: +
+link:https://callfortesting.org/[bhyve production users calls] URL: link:https://callfortesting.org[] +
+link:https://wiki.freebsd.org/EnterpriseWorkingGroup[FreeBSD Wiki - Enterprise Working Group] URL: link:https://wiki.freebsd.org/EnterpriseWorkingGroup[] +
+link:https://wiki.freebsd.org/ChrisMoerz/bhyve_management[FreeBSD Wiki - EWG - bhyve and jails management tooling] URL: link:https://wiki.freebsd.org/ChrisMoerz/bhyve_management[] +
+link:http://static.bultmann.eu/s6-talk/#(1)[Jan Bramkamp's work on s6rc] URL: link:http://static.bultmann.eu/s6-talk/[] +
+link:https://github.com/christian-moerz/vmstated[vmstated on GitHub] URL: link:https://github.com/christian-moerz/vmstated[] +
+link:https://www.youtube.com/watch?v=f60NCrunXyw[YouTube - vmstated explained] URL: link:https://www.youtube.com/watch?v=f60NCrunXyw[]
+
+Contact: Chris Moerz <freebsd@ny-central.org>
+
+==== Bhyve I/O Performance Measurements
+
+
+Participants of the weekly bhyve production users calls recently discussed bhyve's I/O performance.
+Various ways of measuring and comparing were brought up, however it was quickly clear that there is currently no formal analysis and report on this.
+So, we started this effort in the hopes of better understanding the various impacts of configuration options for a guest on its I/O performance.
+We created a set of shell scripts that harness a FreeBSD guest for running package:benchmarks/fio[] I/O performance measurements under various configurations.
+This allows us to compare multiple criteria like bandwidth, latency, IOPS, and more.
+
+So far, we are testing for
+
+* different storage backends (i.e. ahci-hd, nvme, virtio-blk)
+* different memory settings
+* different CPU pinning options
+* different block sizes for the backing storage
+* different block sizes for accessing virtual disks
+
+We are also pitting results for different CPU manufacturers against each other and contrasting guest vs host performance to better understand the performance impact of virtualization.
+
+We plan to continue discussing our results during Michael Dexter's weekly bhyve production users call - come join us if you are interested.
+We also hope to be able to present the results at EuroBSDCon in Q3.
+
+==== Bhyve Virtual Machine Tooling
+
+Last year, Greg Wallace at the FreeBSD Foundation founded the Enterprise Working Group with the specific goal of addressing pain points of Enterprise users of FreeBSD.
+One of the work groups that emerged clustered around bhyve and jails management tooling.
+After collecting a set of desired features and functionality, one overarching key point for bhyve emerged: the desire to have configuration concepts and tooling for bhyve like the ones available for jails.
+
+While other desirable features were identified as well, i.e. TPM software emulation and snapshot/restore/host-migration, the conceptual tooling question won over those due to the lower degree of complexity and its clarity on goal and the path on how to take steps towards it.
+
+Technically, this means working out existing gaps around process supervision and virtual machine state management.
+First steps were taken by experimenting with existing frameworks (i.e. s6rc work by Jan Bramkamp) and eventually -- through discussions in the weekly bhyve production user's calls (organized by Michael Dexter) -- this led to a proof-of-concept implementation of "vmstated".
+
+Started as an experiment to better understand the problem space of process supervision and virtual machine state handling, vmstated is constructed of a daemon and vmstatedctl management utility.
+It is built with base-only tooling and libraries and leverages FreeBSD specific constructs like kqueue to minimize its resource impact.
+
+vmstated is configured via a UCL configuration file (similar to [.filename]#jails.conf#) and -- in combination with a man:bhyve_config[5] configuration file -- already provides highest flexibility in configuring virtual machines.
+vmstatedctl provides a jail-like command set to start, stop, and retrieve status information about guests.
+State transitions can easily be hooked via shell scripts and allow running additional commands for network or storage set up and tear down when relevant state changes occur.
+
+An initial release is already in ports as package:sysutils/vmstated[] and updates are pending commit; however, the newest version can be found on GitHub.
+We are considering expanding the work; we would also like to invite anyone interested to join us in this work!
+Patches, suggestions, feedback, etc. are all very much welcome!
+
+If you want to know more about our work, come join us at one of Michael Dexter's weekly bhyve production users calls or reach me mailto:freebsd@ny-central.org[by email].
+
+==== Documentation
+
+We managed to update a few parts of the Handbook and Porter's Handbook (thanks to mailto:emaste@FreeBSD.org[Ed Maste], mailto:jrm@FreeBSD.org[Joseph Mingrone], mailto:pauamma@gundo.com[Pau Amma], and mailto:rgrimes@FreeBSD.org[Rodney W. Grimes]):
+
+* several improvements and expansions to the virtualization chapter in the FreeBSD Handbook
+** using a man:bhyve_config[5] configuration file
+** jailing bhyve
+** experimental snapshot and restore feature
+** setting up a Windows guest
+* we also have a review (link:https://reviews.freebsd.org/D43940[D43940]) up for an initial step to improving the bhyve man page
+** this was intentionally started with a structural update first to separate the many `-s` flag options
+** once this lands, we can move to a more widespread update to the overall content
+
+Feedback is obviously very welcome -- on the existing content as well as any additional content we should be looking into!
diff --git a/website/content/en/status/report-2024-01-2024-03/bsdinstall.adoc b/website/content/en/status/report-2024-01-2024-03/bsdinstall.adoc
new file mode 100644
index 0000000000..ea1af0086c
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/bsdinstall.adoc
@@ -0,0 +1,66 @@
+=== Graphical Installer for FreeBSD
+
+Links: +
+link:https://people.defora.org/~khorben/FreeBSD/bsdinstall/bsdinstall%20-%20Now%20with%20Graphics!%20-%20AsiaBSDCon%202024%20-%20WIP%20Session.pdf[Slides from AsiaBSDCon 2024] URL: link:https://people.defora.org/~khorben/FreeBSD/bsdinstall/bsdinstall%20-%20Now%20with%20Graphics!%20-%20AsiaBSDCon%202024%20-%20WIP%20Session.pdf[] +
+link:https://github.com/khorben/gbsddialog[gbsddialog] URL: link:https://github.com/khorben/gbsddialog[] +
+link:https://youtu.be/jm6byc7N2O4[preview video] URL: link:https://youtu.be/jm6byc7N2O4[]
+
+Contact: Pierre Pronchery <pierre@freebsdfoundation.org>
+
+The first hurdle to overcome when testing a new Operating System is to get it installed.
+What is more, the first impression new users gather from an Operating System is its installation process.
+The state of the art for Operating System installers nowadays definitely involves a graphical process.
+This is the case for mainstream systems but also for other UNIX systems comparable to link:https://www.freebsd.org[FreeBSD]: link:https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux[RedHat Enterprise Linux], link:https://ubuntu.com/[Ubuntu], https://www.debian.org[Debian GNU/Linux], or even link:https://www.devuan.org[Devuan GNU+Linux]
+Regardless of the technical level of the actual user, this is how the platform will be compared in the public eye.
+
+In practice, FreeBSD has already been derived as a desktop-oriented Operating System by different projects.
+Of these, I only found link:https://www.ghostbsd.org[GhostBSD] as a maintained project offering a graphical procedure to install the system.
+The objective here was to consider a procedure that FreeBSD could adopt as part of its base system, in order to ship a graphical installer much like the current installer.
+However, link:https://ghostbsd-documentation-portal.readthedocs.io/en/latest/user/installation-guide/custom-installation.html#installing-ghostbsd[GhostBSD's installer] relies on a Gtk+ interface driven with Python, implying a hefty footprint on the installation media when adopting FreeBSD's usual image generation procedure.
+It would also imply importing and maintaining new projects into the ports tree.
+
+Instead, with knowledge of the current man:bsdinstall[8] and man:bsdconfig[8] utilities, I envisioned a BSD-licensed replacement for man:Xdialog[1].
+Just like when invoking bsdconfig with the -X switch for graphical mode, it could be dropped in instead of man:bsddialog[1] and allow graphical installation - while sharing the infrastructure of the current installer.
+To avoid confusion with the current implementation of Xdialog from the x11/xdialog port, I have named its replacement man:gbsddialog[1].
+It also has to be said that Xdialog is quite obsolete (latest release in 2006) and this shows visually too.
+
+After creating a Proof-of-Concept prototype past the 14.0 release, I was provided with a 2-months window by the link:https://www.freebsdfoundation.org[FreeBSD Foundation], in order to complete a working implementation.
+Thanks to a few shortcuts, I was glad to present the outcome of this effort during the WIP session of link:https://2024.asiabsdcon.org/program.html[AsiaBSDCon 2024], including a working graphical installer.
+
+Most of the necessary patches are already available for review in link:https://reviews.freebsd.org[FreeBSD's Phabricator]:
+
+* link:https://reviews.freebsd.org/D44279[D44279 bsdinstall: implement adduser with bsddialog]
+* link:https://reviews.freebsd.org/D44280[D44280 bsdinstall: implement rootpass with bsddialog]
+* link:https://reviews.freebsd.org/D44670[D44670 bsdinstall: implement timezone with bsddialog]
+* link:https://reviews.freebsd.org/D44671[D44671 bsdinstall: allow forcing a specific partitioning mode]
+* link:https://reviews.freebsd.org/D44672[D44672 bsdinstall: obtain the dialog binary from $DIALOG]
+* link:https://reviews.freebsd.org/D44673[D44673 bsdinstall: handle command-line options in targets]
+* link:https://reviews.freebsd.org/D44674[D44674 bsdinstall: add support for graphical mode]
+
+I have tried to keep these patches in growing order of friction expected before integration.
+
+The most important objective of this project was to improve bsdinstall, regardless of the success of this integration.
+From the items above, it should be noted that D44279, D44280, D44670 are expecting to improve the general look & feel of the installer, even while in text mode.
+Similarly, D44671 and D44672 improve the overall versatility of the installer when scripted or customized.
+D44673 and D44674 bring it on par with bsdconfig -X, even allowing the graphical installation of jails.
+
+Some parts are still missing, or made use of shortcuts still unsuitable for integration:
+
+* The "fetchmissingdists" target was avoided by shipping every component on the installation media;
+* The "checksum" and "extract" targets had to be re-implemented with simpler code, degrading the user experience also with the regular installer;
+* Creation of the installation media generates an additional, heavy image (almost 8 GB), and is suspected to be hindered by a bug in man:makefs[8].
+
+The corresponding code can be found in my link:https://github.com/khorben/freebsd-src/[GitHub fork] in the link:https://github.com/khorben/freebsd-src/tree/khorben/bsdinstall-graphical4[khorben/bsdinstall-graphical4] branch.
+As can be guessed from the branch name, depending on the complexity of rebasing operations, combined with the (hopefully) progressive integration of the changes proposed, new branches may be added to keep track of the progress.
+(In fact a link:https://github.com/khorben/freebsd-src/tree/khorben/bsdinstall-graphical5[khorben/bsdinstall-graphical5] branch already exists.)
+
+Still, a lot needs to be done for the installer to reach a new level of maturity overall.
+While working on this project, I have received general complaints on the installer, and calls for a complete rewrite.
+It is true that the current code base suffers from a number of issues and limitations.
+The lack of a graphical installer is one of many symptoms, which range from the lack of recovery from errors, of navigability to previous steps, of a general vision of the installation progress, or of a network-based installer.
+In the meantime, this is the installer we have and are familiar with, and I think it can still be saved and improved.
+
+Special thanks go to mailto:emaste@FreeBSD.org[Ed Maste] and mailto:jrm@FreeBSD.org[Joe Mingrone] for the opportunity, and to mailto:jadawin@FreeBSD.org[Philippe Audeoud], mailto:tcberner[Tobias C. Berner], mailto:olce@FreeBSD.org[Olivier Certner], mailto:jrtc27@FreeBSD.org[Jessica Clarke], mailto:olivier@FreeBSD.org[Olivier Cochard-Labbé], mailto:bapt@FreeBSD.org[Baptiste Daroussin], mailto:brd@FreeBSD.org[Brad Davis], mailto:dexter@FreeBSD.org[Michael Dexter], mailto:lwhsu@FreeBSD.org[Li-Wen Hsu], mailto:0mp@FreeBSD.org[Mateusz Piotrowski], mailto:asiciliano@FreeBSD.org[Alfonso Siciliano], mailto:manu@FreeBSD.org[Emmanuel Vadot], and mailto:rwatson@FreeBSD.org[Robert Watson] for the feedback, reviews, and encouragements.
+(If I missed anyone, you know I did not mean to!)
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-01-2024-03/ci.adoc b/website/content/en/status/report-2024-01-2024-03/ci.adoc
new file mode 100644
index 0000000000..72ed57b362
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/ci.adoc
@@ -0,0 +1,51 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://https://tinderbox.freebsd.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the first quarter of 2024, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* With help from clusteradm, the host running test VMs had disk and memory upgraded by reusing the parts of decommissioned machines.
+* Update the build environment of stable/13 jobs to 13.3-RELEASE.
+* Turn i386 build on main branch to use cross build on amd64.
+
+Work in progress tasks:
+
+* Merging link:https://reviews.freebsd.org/D43786[]
+* Merging link:https://reviews.freebsd.org/D36257[]
+* Adding new hardware purchased by the FreeBSD Foundation to the CI cluster
+* Designing and implementing pre-commit CI building and testing and pull/merge-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+  * Proof of concept system is in progress.
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Redesigning the hardware test lab and adding more hardware for testing
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-01-2024-03/cloud-init.adoc b/website/content/en/status/report-2024-01-2024-03/cloud-init.adoc
new file mode 100644
index 0000000000..1410966cf0
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/cloud-init.adoc
@@ -0,0 +1,34 @@
+=== FreeBSD as a Tier 1 cloud-init Platform
+
+Links: +
+link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[] +
+link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[] +
+
+Contact: Mina Galić <freebsd@igalic.co>
+
+cloud-init is the standard way of provisioning servers in the cloud.
+Over the past year and a half, thanks to this FreeBSD support has steadily improved.
+This year, together with cloud-init developers and the FreeBSD Foundation, we decided to explicitly focus on making improvements in FreeBSD itself, that will aid the cloud-init team to test future changes to FreeBSD code-paths themselves.
+To achieve this goal, I need to make FreeBSD run in LXD (and Incus), under the control of ``lxd-agent`` (or ``incus-agent``).
+
+Here are some improvements from the recent weeks:
+
+- I have written a small link:https://codeberg.org/meena/test-cloud-init[testing-framework] (in sh, and I'm slowly porting it to OpenTofu/Terraform), which installs the latest version of package:net/cloud-init-devel[] or package:net/cloud-init[] and runs a couple of standard cloud-init tests.
+- To do this, I have created a link:https://pkg.igalic.co/[dedicated public repository] which contains the latest versions of package:net/cloud-init-devel[] and package:net/cloud-init[] for FreeBSD 13 and 14 on amd64 and aarch64.
+- I have link:https://codeberg.org/meena/vsock-tests[ported Linux's vsock testing framework to FreeBSD]
+- I created a driver skeleton for a link:https://codeberg.org/meena/freebsd-src/src/branch/vsock/sys/dev/virtio/socket[VirtIO Socket driver], based on the HyperV Socket driver.
+- In doing so, I made numerous link:https://reviews.freebsd.org/D44517[improvements to HyperV sockets], some of which are accepted, others still need more work.
+- I have tested and released the latest 24.1 series cloud-init, where the cloud-init team and I have finally fixed some longstanding bugs, such as link:https://github.com/canonical/cloud-init/pull/4820[moving ``/run/cloud-init``] to [.filename]#/var/run/cloud-init# on BSD, as well as fixing the link:https://github.com/canonical/cloud-init/pull/5061[``homedir`` argument] to ``user_groups`` to actually do something.
+- This release also sees numerous fixes to the OpenBSD code-paths from the community and not just me.
+- I have also started an official port for OpenBSD, but link:https://marc.info/?l=openbsd-ports&m=170508174230708&w=2[that work has stalled].
+
+The work to come, in broad strokes:
+
+- Finish the FreeBSD VirtIO Socket driver.
+- Fix Go's runtime to support VirtIO on FreeBSD.
+- Port lxd-agent's dependencies to FreeBSD.
+- Port lxd-agent to FreeBSD.
+
+That work will be interspersed with more improvements to cloud-init on BSDs, and more tests on different cloud providers.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-01-2024-03/clusteradm.adoc b/website/content/en/status/report-2024-01-2024-03/clusteradm.adoc
new file mode 100644
index 0000000000..47caf623b2
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/clusteradm.adoc
@@ -0,0 +1,42 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular support for FreeBSD.org user accounts.
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* link:https://freebsdfoundation.org/blog/powering-up-the-future-the-new-freebsd-cluster-in-chicago/[Set up a new mirror in Chicago].
+
+==== FreeBSD Official Mirrors Overview
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America -- California, Chicago, New Jersey (primary site), and Washington.
+
+The hardware and network connection have been generously provided by:
+
+* link:https://www.bytemark.co.uk/[Bytemark Hosting] (being decommissioned)
+* Cloud and SDN Laboratory at link:https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc]
+* link:https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University]
+* link:https://deploy.equinix.com/[Equinix]
+* link:https://internet.asn.au/[Internet Association of Australia]
+* link:https://www.isc.org/[Internet Systems Consortium]
+* link:https://www.inx.net.za/[INX-ZA]
+* link:https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc]
+* link:https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network]
+* link:https://www.metapeer.com/[MetaPeer]
+* link:https://www.nyi.net/[New York Internet]
+* link:https://nic.br/[NIC.br]
+* link:https://www.teleservice.net/[Teleservice Skåne AB] (new since 2023Q4)
+* link:https://your.org/[Your.Org]
+
+New official mirrors are always welcome.
+We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa.
+If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us.
+We are particularly interested in locations on the United States West Coast and throughout Europe.
+
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site.
diff --git a/website/content/en/status/report-2024-01-2024-03/core.adoc b/website/content/en/status/report-2024-01-2024-03/core.adoc
new file mode 100644
index 0000000000..52157c9da8
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/core.adoc
@@ -0,0 +1,25 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== 13.3-RELEASE
+
+FreeBSD 13.3 was released on March 5th, 2024.
+
+The release announcement is at:
+
+link:https://www.freebsd.org/releases/13.3R/announce/[]
+
+Along the release engineering team, the project dedicates the 13.3-RELEASE to Glen Barber, with thanks for his many years of contributions as Release Engineer.
+
+==== Future of 32-bit platform support
+
+Core announced link:https://lists.freebsd.org/archives/freebsd-announce/2024-February/000117.html[Future of 32-bit platform support in FreeBSD] for deprecating 32-bit platforms over the next couple of major
+releases.
+
+==== Commit bits
+
+* Core approved the src commit bit for mailto:bnovkov@FreeBSD.org[Bojan Novković]
+* Core reactivated the src commit bits for mailto:mp@FreeBSD.org[Mark Peek], mailto:markm@FreeBSD.org[Mark Murray], and mailto:lstewart@FreeBSD.org[Lawrence Stewart]
diff --git a/website/content/en/status/report-2024-01-2024-03/doceng.adoc b/website/content/en/status/report-2024-01-2024-03/doceng.adoc
new file mode 100644
index 0000000000..b60906f4a4
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/doceng.adoc
@@ -0,0 +1,61 @@
+////
+Quarter:	1st quarter of 2024
+Prepared by:	fernape
+Reviewed by:	carlavilla
+Last edit:	$Date$
+Version:	$Id:$
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The mailto:doceng@FreeBSD.org[doceng team] is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+During the last quarter:
+
+mailto:trasz@FreeBSD.org[Edward Tomasz Napierała]'s doc commit bit was taken for safekeeping.
+mailto:trhodes@FreeBSD.org[Tom Rhodes]'s doc commit bit was taken for safekeeping.
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblateurl[] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/url[]
+
+===== Q1 2024 Status
+
+* 17 team languages
+* 189 registered users
+
+Three new translators joined Weblate:
+
+* piker3 in Polish team (pl)
+* chrislongros in Greek team (el)
+* grip in Italian team (it_IT)
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 7%)
+* Chinese (Traditional) (zh-tw)	(progress: 3%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Greek (el)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 5%)
+* Korean (ko)			(progress: 32%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 3%)
+* Polish			(progress: 2%)
+* Portuguese			(progress: 0%)
+* Portuguese (pt-br)		(progress: 22%)
+* Spanish (es)			(progress: 36%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
diff --git a/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc b/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc
new file mode 100644
index 0000000000..6fbd95e971
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc
@@ -0,0 +1,146 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] +
+link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD.
+We do this in both technical and non-technical ways.
+We are 100% supported by donations from individuals and corporations and those investments help us fund the:
+
+* Software development projects to implement features and functionality in FreeBSD
+* Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD
+* Purchase and support of hardware to improve and maintain FreeBSD infrastructure
+* Resources to improve security, quality assurance, and continuous integration efforts
+* Materials and staff needed to promote, educate, and advocate for FreeBSD
+* Collaboration between commercial vendors and FreeBSD developers
+* Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity
+
+==== Operations
+We kicked off the new year with ambitious goals to help move the FreeBSD Project forward by identifying features and functionality to support in the operating system and increasing our advocacy efforts to increase and expand the visibility of FreeBSD.
+Stay tuned for a blog post that will provide more information on our 2024 goals and plans.
+
+We also published the 2024 Budget.
+In order to provide greater transparency about the budgeting process, we wrote a link:https://freebsdfoundation.org/blog/on-starting-the-2024-freebsd-foundation-budget-journey/[blog post] that provides more details on how funding is allocated, new breakouts of some of the project expense categories, and more details on where the funding is going.
+
+==== OS Improvements
+During the first quarter of 2024, 180 src, 65 ports, and 18 doc tree commits identified The FreeBSD Foundation as a sponsor.
+
+Three new projects began this quarter.
+
+* Work began to improve FreeBSD's audio stack and provide audio developers with useful tools and frameworks to make sound development on FreeBSD easier.
+  Read more in mailto:christos@FreeBSD.org[Christos Margiolis] <<_audio_stack_improvements,Audio Stack Improvements>> report entry.
+
+* mailto:olce@FreeBSD.org[Olivier Certner] began his second contract with the Foundation, and this time around, the main goal is to make unionfs stable and useful on FreeBSD.
+  Other work may include revamping VFS lookups, improving out-of-memory handling, implementing a notification system for en-masse detection of filesystem changes such as inotify, and improving console usability.
+
+* This quarter, a new project to add hierarchical rate limits to the OpenZFS file system began.
+  mailto:pjd@FreeBSD.org[Pawel Dawidek] will add support for limits that will be configurable, similar to quotas, but would limit the number of read/write operations and read/write bandwidth.
+
+Six projects continued this quarter.
+
+* You can read about the continued work to port OpenStack components to FreeBSD in Chih-Hsin Chang's <<_openstack_on_freebsd,OpenStack on FreeBSD>> report entry.
+
+* Work continued to improve cloud-init support for FreeBSD.
+  You can read about Mina Galić's work in her <<_freeBSD_as_a_tier_1_cloud-init_platform,FreeBSD as a Tier 1 cloud-init Platform>> report entry.
+
+* A new joint project began between Advanced Micro Devices (AMD) and The FreeBSD Foundation to develop a complete FreeBSD AMD IOMMU driver.
+  This work will allow FreeBSD to fully support greater than 256 cores with features such as CPU mapping and will also include bhyve integration.
+  For those interested in the technical details, follow mailto:kib@FreeBSD.org[Konstantin Belousov] commits tagged with Sponsored by fields for Advanced Micro Devices (AMD) and The FreeBSD Foundation.
+
+* Refer to Pierre Pronchery's <<_graphical_installer_for_freebsd,Graphical Installer for FreeBSD>> report entry to read about the status of FreeBSD's new graphical installer.
+
+* Work continues to port the Vector Packet Processor (VPP) to FreeBSD.
+  VPP is an open-source, high-performance user space networking stack that provides fast packet processing suitable for software-defined networking and network function virtualization applications.
+  Look for a pending article from the developer working on the project, mailto:thj@FreeBSD.org[Tom Jones], that details the experience of porting VPP to FreeBSD.
+
+* mailto:bz@FreeBSD.org[Björn Zeeb] and mailto:cc@FreeBSDd.org[Cheng Cui] continue their wireless work.
+  This quarter was mostly focused on bug fixes and stability improvements to LinuxKPI 802.11 and net80211.
+  Much of this work made it into the 13.3 release.
+
+Here is a sampling of other Foundation-sponsored development completed over the first quarter of 2024:
+
+* FreeBSD was accepted in Google Summer of Code 2024 after receiving 22 contributor proposals; on May 1, we will learn how many projects we will be awarded
+* OpenSSH: update to 9.6p1 then 9.7p1
+* Deprecate bsdlabel
+* Import the kernel parts of bhyve/arm64
+* Various RISC-V improvements
+
+==== FreeBSD Infrastructure
+A contract was completed to set up a new cluster site at NYI Chicago.
+You can read about the details of that project on the link:https://freebsdfoundation.org/blog/powering-up-the-future-the-new-freebsd-cluster-in-chicago/[Foundation's blog].
+
+==== Continuous Integration and Workflow Improvement
+As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project's continuous integration system and the test infrastructure.
+The full update can be found within the quarterly status report.
+
+==== Partnerships and Research
+A focus of Partnerships this Quarter has been to educate the industry about the innovations in the FreeBSD community and the impact that FreeBSD continues to have as a cornerstone to our digital society.
+This is an ongoing priority, and one we invite (encourage) everyone using and working on FreeBSD to join us in.
+Greg Wallace, the Foundation Partnerships lead, is grateful for the opportunities he has had to meet with open source and industry leaders at Microsoft, Google, AWS, OpenSSF, Alpha-Omega, CISA, Eclipse Foundation, Open Source Initiative, Apache Software Foundation, Rust Foundation, Red Hat, Linux Foundation and many others to ensure they have visibility into the key role FreeBSD plays in the global digital infrastructure.
+This is a role FreeBSD has earned through its technical excellence, security by design, high availability, simplicity of operations, commitment to open source collaboration, and cohesiveness.
+
+One sees these characteristics of FreeBSD in the important ongoing funded development work such as porting VPP to FreeBSD, sponsored by RG Nets.
+
+Ensuring industry visibility to the excellence and impact of FreeBSD is vital to ensuring tier one support for FreeBSD across all key hardware and software platforms.
+As a community, every conversation we have with people outside the BSD communities, and every piece of content we publish, that attest to how FreeBSD powers our individual and corporate success, brings us one step closer.
+
+To this end, the Foundation is working on a FreeBSD Impact Report that will aggregate the core and often mission critical role FreeBSD plays in society, from embedded systems powered by QNX, to payments and check processing, to digital entertainment, internet and cybersecurity infrastructure.
+
+Our community is stepping up in innumerable ways, including to make sure FreeBSD supports industry-standard containerized workloads -- check out the link:https://github.com/opencontainers/wg-freebsd-runtime[Open Container Initiative FreeBSD runtime extension working group].
+
+The recently opened hardware vendor support survey will feed into a hardware support guide that reflects the collective experience of all respondents that is intended to help everyone identify hardware vendors that prioritize FreeBSD; it will also help focus Partnerships' outreach on the priority vendors.
+
+To close, please *TELL THE WORLD YOU USE FREEBSD AND WHY. There is no wrong way to do this* -- put it on your blog, on your favorite social media channel, list FreeBSD on your company’s Open Source page, contact the Foundation about a Case Study, etc.
+
+link:https://www.stormshield.com/news/a-short-history-of-open-source/[Stormshield, a leading cybersecurity company based in Europe, provides a great example of how vendors that use FreeBSD can do this]. The footer of their blogs says: "A strong supporter of Open Source, Stormshield is an active member (and sponsor) of the FreeBSD community...Whenever we modify Open Source software, make patches or add features, we offer them to the community for inclusion."
+
+==== Advocacy
+The first quarter of 2024 marked the beginning of a link:https://freebsdfoundation.org/blog/march-2024-advocacy-update/[new era] for the Foundation Advocacy team.
+We welcomed link:https://freebsdfoundation.org/blog/kim-mcmahon-to-join-freebsd-foundation-as-senior-director-of-advocacy-and-community/[Kim McMahon] in the role of Senior Director of Advocacy and Community and also brought on two new technical writers to help increase the frequency and depth of the FreeBSD-related content we produce.
+Just some of our expanded Q1 efforts to support FreeBSD are below.
+
+* Began work planning the on the link:https://freebsdfoundation.org/news-and-events/event-calendar/may-2024-freebsd-developer-summit/[May 2024 FreeBSD Developer Summit], co-located with BSDCan, taking place May 29-30, 2024 in Ottawa, Canada
+* Introduced FreeBSD to new and returning folks at link:https://stateofopencon.com/soocon-2024/[State of Open Con 24] in London, UK, February 6-7, 2024
+* Held an Introduction to FreeBSD half-day workshop and staffed a booth at link:https://www.socallinuxexpo.org/scale/21x[SCaLE21x], which took place March 14-17, 2024 in Pasadena, CA.
+  Thanks to Gordon Tetlow for his help with the workshop
+* The Foundation team also worked on a common message on the improvement and benefits of FreeBSD to ensure consistency between the FreeBSD Foundation and Core Team
+* Members of the Foundation team served as Administrators for the 2024 Google Summer of Code.
+  This year marks the 20th anniversary of Google Summer of Code and the 20th year that the link:https://freebsdfoundation.org/blog/the-freebsd-project-participating-in-google-summer-of-code-2024-2/[FreeBSD Project was accepted as a mentoring organization].
+  The Project received 23 applications from prospective interns
+* Provided an link:https://freebsdfoundation.org/blog/freebsd-13-3-whats-new-and-how-did-we-get-here/[overview of FreeBSD 13.x] including the 13.3 release
+* Worked on the final report of the 2024 FreeBSD Community Survey.
+  Be on the lookout for the report at the end of April
+* In partnership with Innovate UK and Digital Security by Design (DSbD), the Foundation held the first annual link:https://www.globenewswire.com/news-release/2024/04/03/2856691/0/en/FreeBSD-Foundation-and-Digital-Security-by-Design-DSbD-Announce-Beacon-Award-Winners-for-Innovations-and-Improvements-to-CheriBSD.html[Digital Security by Design (DSbD) Ecosystem Beacon Awards] to celebrate innovators working with and enhancing CheriBSD
+* Published numerous blogs including:
+** link:https://freebsdfoundation.org/blog/what-makes-the-freebsd-governance-model-successful/[What Makes the FreeBSD Governance Model Successful]
+** link:https://freebsdfoundation.org/blog/guiding-the-future-of-freebsd-releases-colin-percival-the-new-release-engineering-team-lead/[Guiding the future of FreeBSD releases: Colin Percival, the new Release Engineering Team Lead]
+* Authored or participated in a number of Thought Leadership and News articles including:
+** link:https://freebsdfoundation.org/news-and-events/latest-news/the-cybersecurity-battle-has-come-to-hardware/[The Cybersecurity Battle Has Come to Hardware]
+** link:https://freebsdfoundation.org/news-and-events/latest-news/ampere-in-the-wild-how-freebsd-employs-ampere-arm64-servers-in-the-data-center/[Ampere in the Wild: How FreeBSD Employs Ampere Arm64 Servers in the Data Center]
+** link:https://freebsdfoundation.org/news-and-events/latest-news/isas-and-the-dawning-hardware-security-revolution/[ISAs and the Dawning Hardware Security Revolution]
+** Published the link:https://freebsdfoundation.org/news-and-events/newsletter/march-2024-foundation-update/[March 2024 FreeBSD Update] with a new look
+** Released the link:https://freebsdfoundation.org/past-issues/freebsd-14-0/[November/December 2023] and link:https://freebsdfoundation.org/past-issues/networking-10th-anniversary/[January/February 2024] issues of the FreeBSD Journal now with HTML versions of the articles
+
+==== Fundraising
+Thank you to everyone who gave us a financial contribution last quarter to help fund our work to support the Project.
+2024 started strong with a total of $250,855 raised this quarter.
+We are grateful for your investment in FreeBSD!
+
+Please consider supporting our efforts in 2024 by making a donation here: link:https://freebsdfoundation.org/donate/[].
+
+Or, check out our Partnership opportunities here:
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[].
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2024-01-2024-03/freshports.adoc b/website/content/en/status/report-2024-01-2024-03/freshports.adoc
new file mode 100644
index 0000000000..088670806e
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/freshports.adoc
@@ -0,0 +1,50 @@
+=== FreshPorts: Notification of new packages
+
+Links: +
+link:https://freshports.org/[FreshPorts] URL: link:https://freshports.org/[] +
+link:https://news.freshports.org/[FreshPorts blog] URL: link:https://news.freshports.org/[]
+
+Contact: Dan Langille <dvl@FreeBSD.org>
+
+FreshPorts and FreshSource have reported upon FreeBSD commits for 20 years.
+They cover all commits, not just ports.
+
+FreshPorts tracks the commits and extracts data from the port Makefiles to create a database of information useful to both port maintainers and port users.
+
+For example, link:https://www.freshports.org/security/acme.sh/#history[] shows the history of the package:security/acme.sh[] port, back to its creation in May 2017.
+Also available are dependencies, flavors, configuration options, and available packages.
+All of this is useful for both users and developers of ports.
+
+==== Notification: New Package Available
+
+One of the original features of FreshPorts is notification of ports updates.
+You can create a list of ports and receive notifications about those ports.
+This new feature can also notify when a new package is available for that port.
+The use case: a known security vulnerability has been patched.
+FreshPorts will tell you the port has been patched, and then you wait for the package.
+This new feature will tell you when that package is available.
+
+Details at:
+
+* link:https://github.com/FreshPorts/freshports/issues/542[]
+
+==== Help Needed
+
+It has been over 23 years since FreshPorts started.
+Others must take over eventually.
+I have started that process recently.
+There are several aspects to FreshPorts:
+
+* FreeBSD admin (updating the OS and packages)
+* front end code (website - mostly PHP)
+* back end code (commit processing - Perl, Python, shell)
+* database design (PostgreSQL).
+
+The database does not change very often and requires little maintenance compared to the applications and OS.
+The website pretty much runs itself.
+From time to time, a change to the FreeBSD ports infrastructure breaks something or requires a modification, but there is rarely any urgency to fix that.
+This is not a huge time commitment.
+There is a lot of learning.
+While not a complex application, FreshPorts is also not trivial.
+
+To contribute, please join the link:https://lists.freshports.org/mailman/listinfo/freshports-coders[] mailing list and let us know what you would like to help with.
diff --git a/website/content/en/status/report-2024-01-2024-03/gcc.adoc b/website/content/en/status/report-2024-01-2024-03/gcc.adoc
new file mode 100644
index 0000000000..1f39cb172e
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/gcc.adoc
@@ -0,0 +1,25 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[]
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[Updating GCC default version to 13] is finally finished.
+Thanks to mailto:antoine@FreeBSD.org[Antoine Brodin] who ran the exp-runs and to all other developers and ports maintainers involved.
+
+As promised in the preceding report, the next goal is to reduce the number of open bugs for GCC ports.
+Some work on existing bugs has already started.
+
+In particular, package:lang/gcc14-devel[] has long stayed out of date due to some issues with building the port without any BOOTSTRAP option.
+Thanks to the help of other developers and contributors (a special thank to Mark Millard), I noticed that according to the official documentation link:https://gcc.gnu.org/install/prerequisites.html[building GCC without bootstrap requires a working GCC binary] and thus I switched package:lang/gcc14-devel[] to require that a BOOTSTRAP option is set.
+However it has later been stated that bootstrapping GCC using clang and libc++ is link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632[officially supported].
+But it has also been stated that this is not a high priority.
+
+At the moment package:lang/gcc14-devel[] is the only GCC port requiring a BOOTSTRAP option to be set.
+The plan is to have all GCC ports for versions greater or equal than 14 (i.e. future GCC ports) to require such an option: even if building without bootstrap is more or less officially supported, being low priority for upstream it increases the burden of maintaining GCC ports for low results.
+In case lower versions start to have issues building without bootstrap, I am going to require bootstrap for those as well.
diff --git a/website/content/en/status/report-2024-01-2024-03/intro.adoc b/website/content/en/status/report-2024-01-2024-03/intro.adoc
new file mode 100644
index 0000000000..42a25bb1c8
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/intro.adoc
@@ -0,0 +1,9 @@
+Here is the first 2024 status report, with 21 entries.
+
+The New Year brings us many new interesting projects, such as the new `libsys` that separates system calls from `libc` and `libpthread` or work on a graphical installer for FreeBSD, which will help making our OS more user-friendly.
+Of course, the usual projects keep going on, such as the work on cloud-init, OpenStack, or the GCC ports.
+As usual our main teams share their progress with us.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2024-01-2024-03/libsys.adoc b/website/content/en/status/report-2024-01-2024-03/libsys.adoc
new file mode 100644
index 0000000000..791aed0974
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/libsys.adoc
@@ -0,0 +1,42 @@
+=== libsys
+
+Contact: Brooks Davis <brooks@FreeBSD.org>
+
+The libsys project removes direct system calls from [.filename]#libc.so# and [.filename]#libpthread.so# (aka [.filename]#libthr.so#) to a separate [.filename]#libsys.so#.
+This will:
+
+ * Isolate language runtimes from the details of system call implementations.
+ * Better support logging and replay frameworks for systems calls.
+ * Support elimination of the ability to make system calls outside trusted code in the runtime linker and `libsys`.
+
+This work was initially inspired by a compartmentalization prototype in CheriBSD in 2016.
+Ali Mashtizadeh and Tal Garfinkel picked that work up and attempted to upstream it (link:https://reviews.freebsd.org/D14609[D14609]).
+Unfortunately we could not figure out how to review and land the massive reorganization required through a phabricator review so it languished.
+Last year the CHERI project once again found a need for system call separation in a new library-based compartmentalization framework in CheriBSD so I rebuilt the patch from scratch, committing dozens of `libc` cleanups along the way.
+I landed the first batch of changes on February 5th.
+Since then I have made a number of refinements to the way we link `libsys` as well as which symbols are provided in which library.
+
+Thanks to mailto:kib@FreeBSD.org[Konstantin Belousov] for many rounds of review and feedback as well as runtime linker fixes.
+Thanks to mailto:markj@FreeBSD.org[Mark Johnston] for runtime linker debugging and mailto:dim@FreeBSD.org[Dimitry Andric] for sanitizer fixes.
+Thanks also to everyone who reported bugs and helped debug issues.
+
+==== Known issues (as of the end of the reporting period)
+
+ * The `libsys` ABI is not yet considered stable (it is safe to assume `__sys_foo()` will be supported so language runtimes can use it now).
+ * Programs using the address sanitizer must be linked with `-lsys` (resolved in base at publication time).
+
+==== TODO
+
+ * Add a [.filename]#libsys.h#.  (See link:https://reviews.freebsd.org/D44387[D44387] and other reviews in the stack.)
+ * Update man:intro[2] for `libsys`.
+ * Finalize the ABI.
+   I am likely to reduce the set of `_` (underscore) prefixed symbols we expose.
+ * MFC the existence of `libsys`?
+   It is not clear this is practical, but it might be possible to MFC something useful for language runtimes.
+
+==== Help wanted
+
+ * Port language runtimes that do not use `libc` to use `libsys` for system calls rather than rolling their own interfaces.
+ * Explore limitations on where system calls can be made similar to OpenBSD's link:https://man.openbsd.org/OpenBSD-7.3/msyscall[msyscall(2)] (now obsolete) and link:https://man.openbsd.org/pinsyscalls[pinsyscalls(2)] (not an obvious match to our `libsys`).
+
+Sponsor: AFRL, DARPA
diff --git a/website/content/en/status/report-2024-01-2024-03/openstack.adoc b/website/content/en/status/report-2024-01-2024-03/openstack.adoc
new file mode 100644
index 0000000000..367b4a7d12
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/openstack.adoc
@@ -0,0 +1,24 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[]
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+The OpenStack on FreeBSD project aims to seamlessly integrate OpenStack cloud infrastructure with the FreeBSD operating system.
+It uses FreeBSD's unique features while ensuring compatibility with OpenStack standards.
+
+In the first quarter of 2024, we made significant progress on the OpenStack on FreeBSD project.
+This included submitting a proposal for BSDCan 2024 and attending AsiaBSDCon 2024 to link:https://papers.freebsd.org/2024/asiabsdcon/chang-towards-a-robust-freebsd-based-cloud-porting-openstack-components/[share our porting experiences and gain exposure for the project].
+The feedback received at AsiaBSDCon was particularly valuable and helped in refining the project's direction.
+During this period, we also reviewed the project's phase 1 tasks and made necessary adjustments.
+We also planned for phases 2 and 3, aligning them with the project's long-term goals.
+One technical achievement was verifying the functionality of bhyve serial console over TCP, an important part of the project's infrastructure.
+Additionally, we created a link:https://asciinema.org/a/647308[demo video] showcasing the project's progress and features.
+
+Looking ahead, our focus for the next quarter includes confirming the feasibility of implementing FreeBSD privilege-management user space tools leveraging man:mac[4] and man:priv[9], simplifying installation steps by transitioning to FreeBSD ports, and porting OpenStack Ironic to FreeBSD.
+These tasks will enhance the project's capabilities and compatibility.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-01-2024-03/packagekit.adoc b/website/content/en/status/report-2024-01-2024-03/packagekit.adoc
new file mode 100644
index 0000000000..5757fdde1e
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/packagekit.adoc
@@ -0,0 +1,12 @@
+=== PackageKit backend for FreeBSD pkg
+
+Contact: Gleb Popov <arrowd@FreeBSD.org>
+
+PackageKit is a small D-Bus daemon program that serves as a backend for "application store" type of apps - most notably Plasma Discover and Gnome Software Center.
+The latest PackageKit release features a libpkg backend, which means that you can now use PackageKit-enabled programs on FreeBSD to manage software.
+Plasma Discover is already switched to using PackageKit, so you will get it working out of the box once you update your ports/packages.
+
+If you observe any crashes or bugs in PackageKit please let me know by link:https://github.com/PackageKit/PackageKit/issues[opening an issue upstream].
+If you are interested in contributing, there is a lot of work to do too!
+
+Sponsor: Serenity Cybersecurity, LLC
diff --git a/website/content/en/status/report-2024-01-2024-03/portmgr.adoc b/website/content/en/status/report-2024-01-2024-03/portmgr.adoc
new file mode 100644
index 0000000000..485d177247
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/portmgr.adoc
@@ -0,0 +1,61 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: Tobias C. Berner <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+According to INDEX, there are currently 32,244 ports in the Ports Collection.
+There are currently ~3,300 open ports PRs.
+The last quarter saw 12,991 commits by 158 committers on the main branch and 888 commits by 61 committers on the 2024Q1 branch.
+Compared to last quarter, this means a large increase in the number of commits on the main branch (up from 9,424) and slightly more backports to the quarterly branch (up from 781).
+The number of ports also increased (up from 31,942).
+
+In Q1 there were around 14,127 commits to main:
+The most active committers were:
+
+* 2934 sunpoet
+* 2676 bofh
+* 1297 yuri
+* 748 eduardo
+* 545 jbeich
+* 347 arrowd
+* 233 diizzy
+* 195 yasu
+* 170 ehaupt
+* 164 wen
+
+A lot has happened in the ports tree in the last quarter, an excerpt of the major software upgrades are:
+
+* pkg 1.21.0
+* New USES: ocaml
+* Default version of gcc switched to 13
+* Default version of ruby switched to 3.2
+* Default version of lazarus switched to 3.2.0
+* Default version of go switched to 1.21
+* Chromium updated to 123.0.6312.105
+* Electron-28 updated to 28.2.10
+* Electron-27 updated to 27.3.9
+* Firefox updated to 124.0.2
+* Firefox-esr updated to 115.9.1
+* KDE updated to Frameworks 5 5.115, Frameworks 6 to 6.0.0 Plasma Desktop 5 to 5.27.11, Plasma Desktop 6 to 6.0.2
+* Qt5 updated to 5.15.13
+* Qt6 updated to 6.6.3
+* Python updated to 3.11.9, 3.10.14 and 3.8.10
+* Ruby updated to 3.2.3
+* Rust updated to 1.77.0
+* SDL updated to 2.30.2
+* Sway updated to 1.9
+* wlroots updated to 1.17.2
+* Wine updated to 9.0
+* Xorg server updated to 0.17.2
+
+
+During the last quarter, mailto:pkgmgr@FreeBSD.org[FreeBSD Packages Management Team] ran 17 exp-runs to test various ports upgrades, updates to default versions of ports, subpackage support and base system changes.
diff --git a/website/content/en/status/report-2024-01-2024-03/pot.adoc b/website/content/en/status/report-2024-01-2024-03/pot.adoc
new file mode 100644
index 0000000000..1bb3823a5a
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/pot.adoc
@@ -0,0 +1,23 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+During this quarter, there were no new link:https://github.com/bsdpot/pot[Pot] releases.
+
+Potluck saw quite some activity though.
+Not only have the images been rebuilt for FreeBSD 14, but also the new link:https://github.com/bsdpot/potluck/tree/master/adminer[Adminer] container has been submitted by first-time contributor link:https://github.com/Sidicer[Sidicer].
+Additionally a large number of additional features, updates and fixes have been committed to containers like link:https://github.com/bsdpot/potluck/tree/master/haproxy-consul[HAProxy-Consul], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[PostgreSQL-Patroni], or link:https://github.com/bsdpot/potluck/tree/master/prometheus[Prometheus].
+
+For the link:https://github.com/bsdpot/potluck/tree/master/mastodon-s3[Mastodon container], a link:https://honeyguide.eu/posts/run-your-own-mastodon-server/[blog post] has been published explaining how to use it to run your own instance.
+
+As always, feedback and patches are welcome.
+
+Sponsors: Nikulipe UAB, Honeyguide Group
diff --git a/website/content/en/status/report-2024-01-2024-03/releng.adoc b/website/content/en/status/report-2024-01-2024-03/releng.adoc
new file mode 100644
index 0000000000..15a4febc98
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/releng.adoc
@@ -0,0 +1,16 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.3R/announce/[FreeBSD 13.3-RELEASE announcement] URL: link:https://www.freebsd.org/releases/13.3R/announce/[] +
+link:https://www.freebsd.org/releases/14.1R/schedule/[FreeBSD 14.1-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.1R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the first quarter of the year, the Team managed 13.3-RELEASE, leading to the final RELEASE build and announcement in March.
+Planning has started for the upcoming 14.1-RELEASE cycle.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/14*, and *stable/13* branches.
diff --git a/website/content/en/status/report-2024-01-2024-03/ten64-whle-honeycomb.adoc b/website/content/en/status/report-2024-01-2024-03/ten64-whle-honeycomb.adoc
new file mode 100644
index 0000000000..cdfbfbc72f
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/ten64-whle-honeycomb.adoc
@@ -0,0 +1,41 @@
+=== Ten64, WHLE-LS1, and HoneyComb
+
+Links: +
+link:https://wiki.freebsd.org/BjoernZeeb/[My wiki page with links to some status] URL: link:https://wiki.freebsd.org/BjoernZeeb/[] +
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.ORG>
+
+Solid-Run's HoneyComb, Traverse Technologies's Ten64 and some versions of Conclusive Engineering's WHLE-LS1 all are NXP based platforms with the Data Path Acceleration Architecture Gen2 (DPAA2).
+
+Work has happened to support or improve support for peripherals on these boards.
+
+For DPAA2 I have local changes which will need review (or further discussion):
+
+* Cleanup of memac (MDIO) code reducing bus attachment (ACPI and FDT specific) code into more common code.
+* Cleanup of MC bus attachment code (again ACPI, FDT).
+* For reasons of mii_fdt.c support on some PHYs on FDT-based platforms restructure MAC/MII code and mostly migrate it out of the network interface (NI).
+* Improve Dmitry Salychev's (dsl) initial SFF/SFP code, prototyping a bus similar to MII for SFP with the hope that with more work it can grow into a larger, general FreeBSD framework and hooked it up to DPMAC.
+* With this, minimal support (still fairly hacked up) for "managed" SFP+ mode (using the Ten64 terminology) is usable on FDT-based systems using DAC and fiber cables.
+* Add more sysctl statistics to DPMAC and NI.
+
+In short, I mostly cleaned up some of the mess I contributed to during the initial bring-up.
+
+For the LS1088a based WHLE-LS1 systems changes include:
+
+* device-tree file updates.
+* Added support for the PCA9546 I2C Switch (committed).
+* Added basic support for the PCAL6524 24-bit Fm+ I2C-bus/SMBus I/O expander.
+* Added basic support for the PCA9633 4-bit Fm+ I2C-bus LED driver to drive the status LEDs.
+* Added support to program the man:rgephy[4] LEDs (which needs to be validated).
+* Started testing the eMMC with MMCCAM and GENERIC but had trouble (needs further investigation, seemed fine from firmware for updates).
+* Tested one of three PCIe slots and USB fine.
+
+For the Ten64:
+
+* Most of the basic lifting happened a while ago and it has generally been usable.
+* Detecting the VSC8514 PHY as such went in end of last year.
+* Used as the default platform to test the DPAA2 changes and SFP/SFP+ code.
+
+In addition Pierre-Luc Drouin has overhauled the Vybrid I2C support now attaching and working on both FDT- and ACPI-based systems (committed).
+
+Sponsor: Traverse Technologies (Ten64 hardware a while ago, support)
diff --git a/website/content/en/status/report-2024-01-2024-03/valgrind.adoc b/website/content/en/status/report-2024-01-2024-03/valgrind.adoc
new file mode 100644
index 0000000000..ff98cf1c7d
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/valgrind.adoc
@@ -0,0 +1,34 @@
+=== Valgrind: port to arm64 on its way
+
+Links: +
+link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] +
+link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[] +
+link:https://github.com/paulfloyd/freebsdarm64_valgrind[arm64 port] URL: link:https://github.com/paulfloyd/freebsdarm64_valgrind[]
+
+Contact: Paul Floyd <pjfloyd@wanadoo.fr>
+
+The major news, as per the title, is that a port to FreeBSD arm64 (or aarch64) is now ready.
+The next steps are to get it reviewed and pushed upstream.
+
+Valgrind 3.23 is due out at the end of April 2024 and package:devel/valgrind[] will be updated shortly after that.
+
+package:devel/valgrind-devel[] will get an update as soon as I have pushed the changes for arm64.
+
+`--track-fds=yes` now checks for and warns about attempts to close a file descriptor more than once.
+Handling of closefrom has been improved to use this feature.
+
+There are some important fixes for FreeBSD 15, in particular handling the new `libsys`.
+
+Here is a list of smaller bugfixes:
+
+* Support for FreeBSD 13.3 has been added.
+* Added a redirect for `reallocarray`.
+* Several fixes for `aio*` functions.
+* Added a redirect for `memccpy`.
+* There is a fix for `_umtx_op OP_ROBUST_LISTS`.
+* Added redirects for C23 `free_sized` and `free_aligned_sized`.
+* Correctly propagate the ELF stack protection flags to the guest stack that Valgrind synthesizes.
+* Fixes for `--sanity-level-3` and above (only used for Valgrind self-testing at runtime).
+* Several fixes to checking done for `semctl`.
+* Fixed argument checking for `utrace`.
+* Fixed argument checking for `clock_nanosleep`.
diff --git a/website/content/en/status/report-2024-01-2024-03/wireless.adoc b/website/content/en/status/report-2024-01-2024-03/wireless.adoc
new file mode 100644
index 0000000000..43c585d683
--- /dev/null
+++ b/website/content/en/status/report-2024-01-2024-03/wireless.adoc
@@ -0,0 +1,21 @@
+=== iwlwifi(4) and wireless for 13.3-RELEASE
+
+Links: +
+link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[Categorised Wireless Problem Reports] URL: link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org> +
+Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>
+
+In the first weeks of 2024 focus was on stability for 13.3-RELEASE to finally make man:iwlwifi[4] usable.
+The upcoming 14.1-RELEASE will benefit from this work too.
+The response has since generally been positive and man:iwlwifi[4] supporting chipsets up to BE200 seems mostly stable, yet still slow.
+
+A lot of testing was provided by the FreeBSD Foundation and by many users.
+Massive thanks to everyone who tested, reported back, updated PRs and helped other users.
+
+I have also slowly started to "categorise" more (old) wireless problem reports and will try to continue with some spring cleaning throughout the year.
+
+If you have questions or feedback please use the link:https://lists.freebsd.org/subscription/freebsd-wireless[freebsd-wireless mailing list].
+That way everyone will see, be able to join in, and the answers will be publicly archived.
+
+Sponsor: minipci.biz (BE200 hardware)
diff --git a/website/content/en/status/report-2024-04-2024-06/_index.adoc b/website/content/en/status/report-2024-04-2024-06/_index.adoc
new file mode 100644
index 0000000000..a9e3c3b0de
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/_index.adoc
@@ -0,0 +1,147 @@
+---
+title: "FreeBSD Status Report Second Quarter 2024"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2024-04-2024-06
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+{projects-desc}
+
+include::{reports-path}/audio.adoc[]
+
+'''
+
+include::{reports-path}/github.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+include::{reports-path}/capsicum-rs.adoc[]
+
+'''
+
+include::{reports-path}/service-jails.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+include::{reports-path}/openzfs.adoc[]
+
+'''
+
+include::{reports-path}/zcond.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+include::{reports-path}/riscv.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/openstack.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/erlang.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2024-04-2024-06/audio.adoc b/website/content/en/status/report-2024-04-2024-06/audio.adoc
new file mode 100644
index 0000000000..502c8a16fe
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/audio.adoc
@@ -0,0 +1,33 @@
+=== Audio Stack Improvements
+
+Contact: Christos Margiolis <christos@FreeBSD.org>
+
+The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement -- from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs.
+This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature.
+
+Important work since link:https://www.freebsd.org/status/report-2024-01-2024-03/#_audio_stack_improvements[last report]:
+
+* Asynchronous audio device detach link:https://cgit.freebsd.org/src/commit/?id=44e128fe9d92c1a544b801cb56e907a66ef34691[is now possible].
+This functionality already ships with FreeBSD 14.1-RELEASE, as well as 14-STABLE.
+* Got rid of the "snd_clone" device cloning framework used in man:sound[4] and replaced it with DEVFS_CDEVPRIV(9).
+More info about behavior changes in the link:https://cgit.freebsd.org/src/commit/?id=e8c0d15a64fadb4a330f2da7244becaac161bb70[commit description].
+Also ships with 14.1-RELEASE and 14-STABLE.
+* Several man:sound[4] crash and bug fixes.
+* More out of the box support for man:snd_hda[4] laptop sound.
+* Series of commits that clean up and simplify parts of man:sound[4].
+* Several fixes regarding the OSS API, with the most notable so far being a link:https://cgit.freebsd.org/src/commit/?id=e07f9178502b7cbc0769fc10e99ad0d013f437fd[proper implementation] of the `SNDCTL_AUDIOINFO` and `SNDCTL_ENGINEINFO` IOCTLs.
+* Started implementing man:audio[3], an OSS audio and MIDI library.
+* Took over maintenance of man:virtual_oss[8].
+
+Future work includes:
+
+* Implementation of an man:audio[8] utility, in similar fashion to man:mixer[8].
+* Implementation of a bluetooth device management utility.
+* Improve man:mixer[3] and man:mixer[8].
+* Improve documentation and test suite where needed.
+* Attempt to find a better (ideally automatic) way to handle man:snd_hda[4] pin-patching.
+This is an experimental attempt and is not guaranteed to actually yield a working result.
+
+You can also follow the development process in link:https://lists.freebsd.org/subscription/freebsd-multimedia[freebsd-multimedia@], where I post regular reports.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-04-2024-06/azure.adoc b/website/content/en/status/report-2024-04-2024-06/azure.adoc
new file mode 100644
index 0000000000..9fea5b843b
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/azure.adoc
@@ -0,0 +1,34 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.freebsd.org/subscription/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+
+In this quarter, we have published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-14_1[14.1-RELEASE on Azure Marketplace].
+Souradeep Chakrabarti from Microsoft has improved the TLB flushing mechanism in Azure.
+
+Work in progress tasks:
+
+* Automating the image building and publishing process and merging to [.filename]#src/release/#.
+* Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+* Testing adding FreeBSD support in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+** https://github.com/microsoft/azure-pipelines-agent/pull/3266[]
+
+The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+
+Open tasks:
+
+* Update FreeBSD-related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Update package:sysutils/azure-agent[] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure]
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2024-04-2024-06/capsicum-rs.adoc b/website/content/en/status/report-2024-04-2024-06/capsicum-rs.adoc
new file mode 100644
index 0000000000..4197e746f7
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/capsicum-rs.adoc
@@ -0,0 +1,14 @@
+=== Capsicum-rs
+
+Links: +
+link:https://github.com/dlrobertson/capsicum-rs[capsicum-rs on GitHub] URL: https://github.com/dlrobertson/capsicum-rs[]
+link:https://github.com/asomers/capsicum-net[capsicum-net on GitHub] URL: https://github.com/asomers/capsicum-net[]
+
+Contact: Alan Somers <asomers@FreeBSD.org>
+
+Capsicum is a lightweight OS capability and sandbox framework implementing a hybrid capability system model.
+
+I have adopted the library providing Rust bindings for Capsicum, and extended it with support for man:libcasper[3] and man:cap_net[3].
+It is already being used by package:net-mgmt/nfs-exporter[] and by a TLS-enabled FTP server (the FTP server is closed-source, but all of the interesting bits reside in an open source library, and an example server can be found at link:https://github.com/bolcom/libunftp/tree/master/crates/unftp-sbe-fs/examples[]).
+
+Sponsor: Axcient
diff --git a/website/content/en/status/report-2024-04-2024-06/ci.adoc b/website/content/en/status/report-2024-04-2024-06/ci.adoc
new file mode 100644
index 0000000000..0aa491e3ae
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/ci.adoc
@@ -0,0 +1,52 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://https://tinderbox.freebsd.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the second quarter of 2024, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* Added new hardware purchased by the FreeBSD Foundation in Chicago site to the CI cluster
+* Repurposed decommissioned pkg builder as build agent and added to the CI cluster
+* Adjusted the job dispatching mechanism based on the machine capability
+* bofh@ merged link:https://reviews.freebsd.org/D43786[] as https://cgit.freebsd.org/src/commit/?id=cb9d4bb1fbb9ac0eb9f211656e91f9d5254c166c[Add preliminary in-tree CI infrastructure for developers] so they can replicate an environment or
+results similar to https://ci.FreeBSD.org[]
+* Decommission armv6 jobs for the main branch
+
+Work in progress tasks:
+
+* Merging link:https://reviews.freebsd.org/D36257[Pre-commit CI with CIRRUS-CI]
+* Designing and implementing pre-commit CI building and testing and pull/merge-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+  * Proof of concept system is in progress.
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Redesigning the hardware test lab and adding more hardware for testing
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Planning to run ztest tests
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-04-2024-06/clusteradm.adoc b/website/content/en/status/report-2024-04-2024-06/clusteradm.adoc
new file mode 100644
index 0000000000..9febfa1340
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/clusteradm.adoc
@@ -0,0 +1,73 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular support for FreeBSD.org user accounts.
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* Cluster software refresh.
+* Moving cluster services to Chicago.
+
+==== Cluster software refresh
+
+Except for the package builders and developer-facing ("dogfood") machines, the FreeBSD cluster mostly tracks stable/X branches.
+This quarter, we started moving the stable/13 hosts to stable/14.
+
+At the time of this writing, there are 133 physical machines in the cluster, 48 run current, and 64 have been upgraded to stable/14.
+The remaining machines are slated for upgrading or decommissioning in the near future.
+Of the 290 jails in the cluster, 206 run stable/14.
+
+[.screen]
+----
+ 12.x: Regular   2, Jails   8
+ 13.x: Regular  19, Jails  68
+ 14.x: Regular  64, Jails 206
+>15.x: Regular  48, Jails   8
+-----------------------------
+Total: Regular 133, Jails 290
+Total installations:      423
+Running -RELEASE|{-p*}:    0
+Total geographic sites:    16
+----
+
+==== Moving cluster services to Chicago
+
+Earlier this year, we started building up our new site in Chicago.
+This quarter, we began decommissioning older machines in New Jersey and moving services to the newer machines in Chicago.
+Our long-term goal is for Chicago to become our primary location.
+This work will take several more months to complete.
+
+==== FreeBSD Official Mirrors Overview
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America -- California, Chicago, New Jersey (primary site), and Washington.
+
+The hardware and network connection have been generously provided by:
+
+* Cloud and SDN Laboratory at link:https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc]
+* link:https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University]
+* link:https://deploy.equinix.com/[Equinix]
+* link:https://internet.asn.au/[Internet Association of Australia]
+* link:https://www.isc.org/[Internet Systems Consortium]
+* link:https://www.inx.net.za/[INX-ZA]
+* link:https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc]
+* link:https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network]
+* link:https://www.metapeer.com/[MetaPeer]
+* link:https://www.nyi.net/[New York Internet]
+* link:https://nic.br/[NIC.br]
+* link:https://www.teleservice.net/[Teleservice Skåne AB]
+* link:https://your.org/[Your.Org]
+
+New official mirrors are always welcome.
+We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa.
+If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us.
+We are particularly interested in locations on the United States West Coast and throughout Europe.
+
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site.
+
+Sponsors: The FreeBSD Foundation and Netzkommune
diff --git a/website/content/en/status/report-2024-04-2024-06/core.adoc b/website/content/en/status/report-2024-04-2024-06/core.adoc
new file mode 100644
index 0000000000..81fdb261f4
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/core.adoc
@@ -0,0 +1,58 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== DevSummit 202405
+
+The Core Team has presented the status update at the DevSummit 202405.
+Details are available at link:https://wiki.freebsd.org/DevSummit/202405[]
+
+==== Passing of Mike Karels
+
+It is with a heavy heart that we have learned of Mike Karels' recent passing.
+We want to offer our sincere condolences to his family, friends, and the community for this loss.
+Mike was an inspirational fellow developer and will be sorely missed.
+
+link:https://lists.freebsd.org/archives/freebsd-announce/2024-June/000135.html[In Memory of Mike Karels].
+
+For more details about him, please visit the FreeBSD Foundation's page at:
+
+link:https://freebsdfoundation.org/mike_karels/[]
+
+==== 2024 Core Team Election
+
+Core.12 appointed Muhammad Moinur Rahman (bofh@) and Allan Jude (allanjude@) as the managers of the 2024 Core Team election.
+After Allan decided to run for Core, Moin continued to handle all the election tasks independently.
+
+The result was announced on June 12th, with 8 members:
+
+* Allan Jude (allanjude@)
+* Dave Cottlehuber (dch@)
+* Gleb Smirnoff (glebius@)
+* Hiroki Sato (hrs@)
+* Li-Wen Hsu (lwhsu@)
+* Mathieu Arnold (mat@)
+* Olivier Cochard (olivier@)
+* Tobias C. Berner (tcberner@)
+
+Mike Karels has run for the 2024 Core Team election, and was in the top nine candidates in the result.
+After a discussion, core.13 came to the conclusion that the eight members will serve as the new team.
+
+Core.13 takes office on June 12th, and hold the handover meeting with core.12 on June 21st.
+
+The project thanks the outgoing core.12 members for their service in the last two years:
+
+* Baptiste Daroussin (bapt@)
+* Benedict Reuschling (bcr@)
+* Ed Maste (emaste@)
+* Greg Lehey (grog@)
+* John Baldwin (jhb@)
+* Emmanuel Vadot (manu@)
+* Mateusz Piotrowski (0mp@)
+
+==== Commit bits
+
+* Core approved the src commit bit for Osama Abboud (osamaabb@)
+* Core reactivated the src commit bit for Ryan Libby (rlibby@)
diff --git a/website/content/en/status/report-2024-04-2024-06/doceng.adoc b/website/content/en/status/report-2024-04-2024-06/doceng.adoc
new file mode 100644
index 0000000000..de6a91d4f9
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/doceng.adoc
@@ -0,0 +1,96 @@
+////
+Quarter:	2nd quarter of 2024
+Prepared by:	fernape
+Reviewed by:	
+Last edit:	$Date$
+Version:	$Id:$
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/url[] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/url[] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-docengurl[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+==== Document changes
+
+During this quarter multiple pieces of the documentation were updated including the removal of mentions to ports that were removed from the ports tree, typos, URL corrections, and asciidoc improvements.
+
+These are three highlighted contributions in this quarter:
+
+ * Best practices related to vendor import were documented. URL: link:https://cgit.freebsd.org/doc/commit/?id=fe494e72df138266f6da2b9170cf0215275a6aaf[]
+ * A section about service jails was added to the handbook. URL: https://cgit.freebsd.org/doc/commit/?id=8f4754a9a6ee8f2503cfb68d14afa99b17729e7f[]
+ * bhyve documentation was improved. URL: https://cgit.freebsd.org/doc/commit/?id=68cbd16c4e7c199cfdfb2b54110ad1470b4d7a2e[]
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblateurl[] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/url[]
+
+===== Q2 2024 Status
+
+* 17 team languages
+* 214 registered users
+
+9 new translators joined Weblate:
+
+* BFR (de_DE)
+* Elwood (de_DE)
+* Freebsd-Freund (de_DE)
+* MSantos (pt)
+* SINF-KEN (fr_FR, nl_NL)
+* aperechnev (ru)
+* edsonwolf
+* fdecunta (es_ES)
+* wheatfox (zh_CN, zh_HANS)
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 7%)
+* Chinese (Traditional) (zh-tw)	(progress: 3%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Greek (el)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 5%)
+* Korean (ko)			(progress: 32%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 3%)
+* Polish			(progress: 2%)
+* Portuguese			(progress: 0%)
+* Portuguese (pt-br)		(progress: 22%)
+* Spanish (es)			(progress: 36%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+==== Packages maintained by DocEng
+
+During this quarter the following work was done in packages maintained by
+doceng@:
+
+* package:textproc/docproj-legacy[]: Fix build with DBLATEX
+* package:textproc/docproj-legacy[]: Fix poudriere warning
+* package:textproc/rubygem-asciidoctor-epub3[]: Add missing run dependency
+* package:www/gohugo[]: Update to 0.125.4
+
+==== Open issues
+
+There are 3 Open PRs in bugzilla assigned to doceng@:
+
+ * link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279815[279815 status reports: ERR_TOO_MANY_REDIRECTS]
+ * link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276923[276923 www/gohugo link error under poudriere]
+ * link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267274[267274 Please remove the zh-CN Handbook of the current FreeBSD website]
+
+During this quarter doceng@ closed 3 PRs:
+
+ * link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278904[278904 misc/freebsd-doc-en: HTML should be single page]
+ * link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278732[278732 www/gohugo: Update to v125.5]
+ * link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278504[278504 textproc/rubygem-asciidoctor-epub3: A run-time dependency is missing for rubygem-asciidoctor-epub3 port]
diff --git a/website/content/en/status/report-2024-04-2024-06/erlang.adoc b/website/content/en/status/report-2024-04-2024-06/erlang.adoc
new file mode 100644
index 0000000000..94ff33c1a7
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/erlang.adoc
@@ -0,0 +1,28 @@
+=== FreeBSD Erlang Ecosystem Ports update
+
+Links: +
+link:https://wiki.freebsd.org/Erlang[FreeBSD Erlang wiki] URL: link:https://wiki.freebsd.org/Erlang[] +
+link:https://erlang.org/[Erlang/OTP language] URL: link:https://erlang.org/[] +
+link:https://elixir-lang.org/[Elixir language] URL: link:https://elixir-lang.org/[] +
+link:https://gleam.run/[Gleam language] URL: link:https://gleam.run/[] +
+
+Contact: FreeBSD Erlang mailing list <erlang@FreeBSD.org>
+
+The Erlang runtime system, commonly known as the BEAM, provides a runtime that is used by a number of programming languages and applications in the FreeBSD ports collection.
+
+Notable changes in 2024 include:
+
+* adding OTP27, the latest Erlang runtime release, Elixir 1.17, and Gleam 1.20
+* more than 57 point release updates so far in 2024
+* improved inline documentation within Erlang ports
+* moved RabbitMQ port to the generic UNIX build, decoupling this from Elixir as a build-time dependency.
+This enables moving RabbitMQ to the latest supported release.
+Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ
+
+Note that as the upstream Erlang OTP team only commit to supporting the two latest major releases, more and more point updates are arriving for OTP26-27, but not for the older Erlang runtime releases, which are now unlikely to get security and bug fixes.
+
+During 2024Q3, the Erlang team is planning to:
+
+* migrate the base package:lang/erlang[] port to OTP26 and update related dependencies
+
+Additional testing and community contributions are welcome, please reach out on the mailing list, especially if you are able to help testing of specific port updates.
diff --git a/website/content/en/status/report-2024-04-2024-06/freebsd-foundation.adoc b/website/content/en/status/report-2024-04-2024-06/freebsd-foundation.adoc
new file mode 100644
index 0000000000..4d5b396d10
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/freebsd-foundation.adoc
@@ -0,0 +1,174 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] +
+link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD.
+We do this in both technical and non-technical ways.
+We are 100% supported by donations from individuals and corporations and those investments help us fund the:
+
+* Software development projects to implement features and functionality in FreeBSD
+* Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD
+* Purchase and support of hardware to improve and maintain FreeBSD infrastructure
+* Resources to improve security, quality assurance, and continuous integration efforts
+* Materials and staff needed to promote, educate, and advocate for FreeBSD
+* Collaboration between commercial vendors and FreeBSD developers
+* Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity
+
+Last quarter we helped FreeBSD celebrate its 31st anniversary!
+This community sure loves to celebrate milestones like this one.
+We not only saw more users sharing their stories on social media, but many commercial users stepped in to promote their use cases and love for FreeBSD.
+It is exciting to see the growth of this project through the improvements made to FreeBSD, as well as the increase in users and contributors.
+
+Over the past few quarters, we have built up our technology, advocacy, and partnership teams to accelerate our work in improving the operating system, increasing the adoption and visibility of FreeBSD, and increasing the number of partners who help fund our work.
+
+Below you will find updates from each team to see the work we have accomplished to support you, the community and the operating system we all love.
+But, first I want to share a fundraising update.
+Last quarter we raised $41,154 towards our goal of raising over $2,000,000.
+You can see our 2024 budget to understand how we are spending your donations here: link:https://freebsdfoundation.org/wp-content/uploads/2024/03/Budget2024-Approved-Public.pdf[].
+
+Over half the budget goes directly into improving and securing FreeBSD.
+If there is a security vulnerability out there, we have software developers on staff who can quickly step in, evaluate the situation, and put in a change or workaround if needed.
+We have a full-time developer who leads the continuous integration efforts and investigates ways to improve the tools to test code, improve test coverage, and help developers be more efficient.
+We have also allocated more funding towards our advocacy efforts.
+This includes creating content to highlight FreeBSD's strengths and differentiators, talking to commercial users and documenting their use cases, and promoting the work you are doing.
+
+Please consider funding our efforts to help keep FreeBSD innovative, secure, and stable by making a donation here: link:https://freebsdfoundation.org/donate/[].
+
+If you are a corporate user, please consider becoming a partner!
+Go here to find out more information about our partnership opportunities: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[].
+
+==== OS Improvements
+During the second quarter of 2024, 204 src, 50 ports, and 11 doc tree commits identified The FreeBSD Foundation as a sponsor.
+
+The Foundation is sponsoring 13 projects.
+
+* mailto:christos@FreeBSD.org[Christos Margiolis] continued to improve FreeBSD's audio stack and provide audio developers with useful tools and frameworks to facilitate sound development on FreeBSD.
+Refer to the <<_audio_stack_improvements,Audio Stack Improvements>> entry for details.
+
+* mailto:pjd@FreeBSD.org[Pawel Dawidek] is in the final stages of a project to add hierarchical rate limits to OpenZFS.
+For details, refer to the <<_hierarchical_rate_limits_for_openzfs,Hierarchical rate limits for OpenZFS>> report entry and the link:https://github.com/openzfs/zfs/pull/16205[pull request in the OpenZFS repository].
+
+* Long-term contractor mailto:olce@FreeBSD.org[Olivier Certner] was active in a few different parts of the tree:
+** man:rtprio[2]: Updating the number of queues per runqueue from 64 to 256
+** UnionFS: reviewed work from mailto:jah@FreeBSD.org[Jason A. Harmening].
+   Jason's work fixes many locking problems (wild accesses without locks, deadlocks, etc.), particularly in unionfs_rename() and improves locking logic.
+** Vnode recycling/ZFS ARC reclaim: Reviewed a fix for link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275594[bug #275594], liaised with upstream to obtain and test a backport, had an EN issued and applied as 13.3-RELEASE-p2, and started longer-term work to improve the vnode reclaiming mechanisms and have ZFS pass the right information
+** ULE scheduler: Updated to work on a single runqueue instead of 3 for POSIX compliance with respect to the number of distinct SCHED_FIFO/SCHED_RR priority levels
+** Miscellaneous: Many (26) reviews, ports updates, and investigated DRM problems
+** Published a link:https://freebsdfoundation.org/eurobsdcon-2023/[EuroBSDCon 2023 conference report in the FreeBSD Journal].
+
+* mailto:pierre@freebsdfoundation.org[Pierre Pronchery] continued work on a security-focused project with the Foundation that included:
+** working on a conversion tool from link:https://vuxml.freebsd.org/freebsd/index.html[VuXML] to link:https://ossf.github.io/osv-schema/[OSV]
+** automating the generation of VuXML reports across all ports with link:https://www.freshports.org/security/osv-scanner/[security/osv-scanner]
+** running Coverity Scan reports around bhyve and assisting in rectifying the reported defects
+
+* Work continued on a joint project between Advanced Micro Devices (AMD) and The FreeBSD Foundation to develop a complete FreeBSD AMD IOMMU driver.
+  This work will allow FreeBSD to fully support greater than 256 cores with features such as CPU mapping and will also include bhyve integration.
+  mailto:kib@FreeBSD.org[Konstantin Belousov] has been working on various parts of the project, including driver attachment, register definitions, an ACPI table parser, and utility functions.
+  Two key components that need to be completed are context handling, which is mostly a generalization of Intel DMAR code, and page table creation.
+  After this, the AMD driver's enable bit can be turned on for testing.
+  To follow all of Konstantin's work, look for src commits tagged with Sponsored by fields for Advanced Micro Devices (AMD) and The FreeBSD Foundation.
+
+* The Vector Packet Processor (VPP) is an open-source, high-performance user space networking stack that provides fast packet processing suitable for software-defined networking and network function virtualization applications.
+  mailto:thj@FreeBSD.org[Tom Jones] is wrapping up his part on a project to port VPP to FreeBSD.
+  The code has been shared with RG Nets, a co-sponsor of the work, for extensive testing.
+
+* mailto:bz@FreeBSD.org[Björn Zeeb] continued to improve wireless networking on FreeBSD.
+  As with last quarter, the focus was mainly on bug fixes and stability improvements.
+  Most of Bjoern's 30+ src commits were to LinuxKPI and net80211 code.
+
+* mailto:philip@FreeBSD.org[Philip Paeps] is working on a 20-hour-per-month, six-month contract to continue modernizing the FreeBSD cluster.
+This work includes moving more servers to our newest cluster site at NYI in Chicago.
+
+* mailto:bofh@FreeBSD.org[Moin Rahman] is under two contracts.
+Moin is nearing completion of a Center for Internet Security (CIS) hardening guide and continues work to establish pre-commit CI.
+
+* mailto:freebsd@igalic.co[Mina Galić] continues efforts to put FreeBSD cloud-init support on par with Linux support.
+
+* mailto:mhorne@FreeBSD.org[Mitchell Horne] presented his RISC-V work at the FreeBSD developer summit.
+You can read about the latest developments in the <<_freebsd_riscv64,FreeBSD/riscv64>> report entry.
+
+* Refer to mailto:starbops@hey.com[Chih-Hsin Chang]'s <<_openstack_on_freebsd,OpenStack on FreeBSD>> report entry for the latest updates on the project to port OpenStack components so that OpenStack can be run on FreeBSD hosts.
+
+Other members of the Foundation's technology team contributed to FreeBSD development efforts.
+For example, Mark Johnston, along with Andrew Turner, authored basic routines to build a Flattened Device Tree (FDT) for arm64 bhyve guests.
+The FDT describes various hardware components like CPUs, memory, UART, PCIe controller, interrupt controller, and platform timer, which the guest OS needs to know about.
+Ed Maste committed a variety of src contributions, including modernization of man:tzsetup[8] and correcting an issue with man:diff[1] options.
+Balancing their regular responsibilities, Li-Wen Hsu and Joe Mingrone contributed updates and fixes to various ports, including addressing pressing security issues.
+
+link:https://www.freebsd.org/projects/summerofcode/[FreeBSD is participating in the 20th consecutive Google Summer of Code].
+The link:https://wiki.freebsd.org/SummerOfCode2024Projects[11 projects for this summer] are well underway.
+
+==== Continuous Integration and Workflow Improvement
+As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project's continuous integration system and test infrastructure.
+
+==== Partnerships and Research
+
+In the Second Quarter, Greg Wallace, the Foundation Partnerships lead, attended the Open Source Summit event in Seattle.
+There he joined Doug Rabson who gave a talk on the work of the FreeBSD OCI Runtime Extension working Group.
+link:https://youtu.be/pggcc6fi-ow?si=0veLZJ5J4rXCWAHY[You can check it out here].
+Greg also used the event to connect with a number of key tech companies to advance major joint technology initiatives.
+link:[Greg's write up on the event is here].
+
+Work continues on other highly-requested features.
+RG Nets and others have been making great strides to bring CUDA and related AI stack components to FreeBSD.
+The Foundation is seeking ways to coordinate across users of FreeBSD to get support for a variety of AI technologies on FreeBSD.
+One idea is to launch a FreeBSD AI lab that would pool money from supporters to get CUDA fully supported on FreeBSD and to round out DPU driver support.
+mailto:partnerships@freebsdfoundation.org[Please contact us if you would like to support such an initiative].
+
+Work continues to leverage the heroic work from the FreeBSD Community to get .NET supported on FreeBSD so that downstream dependencies can in turn better support FreeBSD.
+More to come on this front soon.
+
+Thanks to the generous grant from Alpha-Omega, the FreeBSD Foundation has undertaken two code audits of important subsystems carried out by Synactiv.
+Alpha-Omega is an open source project with a mission to protect society by catalyzing sustainable security improvements to the most critical open source software projects and ecosystems.
+link:https://github.com/khorben/alpha-omega/blob/freebsd/alpha/engagements/2024/FreeBSD/update-2024-06.md[Our most recent monthly update can be found here].
+The code audits will conclude in July and then we will then undertake a process audit and will also run a 2FA pilot.
+
+In Q1 and Q2, Greg participated in several meetings about various government regulations.
+In March, he represented FreeBSD at the link:https://www.cisa.gov/news-events/news/cisa-announces-new-efforts-help-secure-open-source-ecosystem[CISA two-day Open Source Software (OSS) Security Summit] alongside other link:https://opensource.org/programs/open-policy-alliance[Open Policy Alliance members].
+Previously, Greg collaborated with OPA to submit comments to CISA's RFC on how the US Government can support the security and sustainability of Open Source.
+And in June, The FreeBSD Foundation joined the link:https://outreach.eclipse.foundation/open-regulatory-compliance[Open Regulatory Compliance Working Group] at the Eclipse Foundation.
+This group aims to accelerate the development of cohesive cybersecurity processes required for regulatory compliance while offering a neutral environment for hosting technical discussions with the open source community at large.
+
+We are thrilled to welcome Alice Sowerby as a part time, contract Partnerships Program Manager.
+Alice is an experienced, multi-skilled leader, currently active in a number of open source domains.
+She is the co-host of the CHAOSS podcast and chair of the TODO group review team for the OSPO Book.
+Alice is providing program and project management for partnership initiatives, like Alpha-Omega, OCI FreeBSD Runtime Extension WG, and the Enterprise Working Group.
+
+==== Advocacy
+During the second quarter of 2024, we continued growing our efforts to drive awareness, advocate for the project, highlight users, and bring educational content to the FreeBSD community.
+Below are some of those efforts.
+
+* Organized the link:https://freebsdfoundation.org/news-and-events/event-calendar/may-2024-freebsd-developer-summit/[May 2024 FreeBSD Developer Summit], co-located with link:https://www.bsdcan.org/2024/[BSDCan].
+Check out both the videos and link:https://freebsdfoundation.org/blog/highlights-from-the-freebsd-developer-summit-2024-innovations-and-future-directions/[write ups] from Summit.
+* Celebrated FreeBSD's 31st Birthday with link:https://freebsdfoundation.org/freebsd-day/[FreeBSD Week], which included many new user stories, and an interview with Beastie!
+* Released the link:https://freebsdfoundation.org/blog/results-from-the-2024-freebsd-community-survey-report/[Final Report] from the 2024 FreeBSD Community Survey.
+* Announced the winners of the first annual link:https://www.globenewswire.com/news-release/2024/04/03/2856691/0/en/FreeBSD-Foundation-and-Digital-Security-by-Design-DSbD-Announce-Beacon-Award-Winners-for-Innovations-and-Improvements-to-CheriBSD.html[Digital Security by Design (DSbD) Ecosystem Beacon Awards] to celebrate innovators working with and enhancing link:https://www.globenewswire.com/Tracker?data=AqFv3m-G_PnXTakUHpA34riXXjhMCVgNSpwO99D5k4M7kT-0a6VExR0Fquv5oEcrgKs63RvmsH216VVudEa37mjZdDlZM2T-ySeVWUkJRMAgwt8-gc8RTgGWqjEd69fkAd0jDAYhTBzYItmcGkUkdgJvw-XOeoIGU1F-cb4Vn7yoefproJMVamLYOH5wJJfh1cD-65ey2Acl3WmtVfwInQ==[CheriBSD].
+  The Beacon awards are sponsored by the Foundation in partnership with Innovate UK and Digital Security by Design (DSbD).
+* Provided an overview of link:https://freebsdfoundation.org/blog/freebsd-14-1-whats-new-and-how-did-we-get-here/[FreeBSD 14.1].
+* Updated the link:https://freebsdfoundation.org/end-user-stories/[FreeBSD End User page] with new interviews and a number of new case studies including ones from link:https://freebsdfoundation.org/netflix-case-study/[Netflix], link:https://freebsdfoundation.org/end-user-stories/metify-case-study/[Metify], and link:https://freebsdfoundation.org/end-user-stories/rg-nets-case-study/[RGNets].
+* Published numerous blogs including:
+** link:https://freebsdfoundation.org/blog/freebsd-foundation-delivers-v1-of-freebsd-ssdf-attestation-to-support-cybersecurity-compliance/[FreeBSD Foundation Delivers V1 of FreeBSD SSDF Attestation to Support Cybersecurity Compliance]
+** link:https://freebsdfoundation.org/blog/freebsd-the-torchbearer-of-the-original-operating-system-distribution/[FreeBSD: The torchbearer of the original operating system distribution]
+** link:https://freebsdfoundation.org/blog/the-2024-freebsd-foundation-budget-journey-choosing-where-we-invest/[The 2024 FreeBSD Foundation Budget Journey: Choosing Where We Invest]
+** link:https://freebsdfoundation.org/blog/why-freebsd-continues-to-innovate-and-thrive/[Why FreeBSD Continues to Innovate and Thrive]
+** link:https://freebsdfoundation.org/blog/innovating-the-future-arms-strategic-embrace-of-freebsd/[Innovating the Future: Arm's Strategic Embrace of FreeBSD]
+** link:https://freebsdfoundation.org/blog/why-freebsd-events-are-important-to-furthering-the-development-of-freebsd/[Why FreeBSD Events are Important to Furthering the Development of FreeBSD]
+* Participated in the following contributed articles, interviews and podcasts:
+** link:https://cioinfluence.com/technology/operating-systems/cio-influence-interview-with-deb-goodkin-director-of-freebsd-foundation/[CIO Influence interview with Deb Goodkin]
+** link:https://podcast.sustainoss.org/239[SustainOSS Podcast interview with Deb Goodkin]
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2024-04-2024-06/gcc.adoc b/website/content/en/status/report-2024-04-2024-06/gcc.adoc
new file mode 100644
index 0000000000..f55cf4a21a
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/gcc.adoc
@@ -0,0 +1,22 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[] +
+link:https://gcc.gnu.org/gcc-14/[GCC 14 release series] URL: link:https://gcc.gnu.org/gcc-14/[] +
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+Upstream has released link:https://gcc.gnu.org/gcc-14[GCC 14.1].
+Therefore port package:lang/gcc-14[] has been created, as well as package:lang/gcc15-devel[] which tracks the new latest development GCC version.
+Previous major versions of GCC are being updated as well.
+
+Only very little work has been done on existing bugs for GCC ports this quarter, contrary to the original plan stated in the precedent report.
+This is due to the fact that I noticed an increasing interest in upstream to support GCC on FreeBSD, which however gets blocked by the fact that GCC sources do not build out-of-the-box on our platform, but needs instead many patches which are in our ports tree framework.
+It is then necessary to focus on upstreaming all of those patches, possibly at once and not one at the time as it has been done until now, and to also regularly run the tests suite, fixing all tests that fail.
+Then I am working on a new setup of automation that allows me to build and test all supported GCC versions as efficiently as possible, including GCC from sources but without the ports tree framework support.
+All of this has significantly slowed down usual GCC ports maintainership (users of the -devel ports have probably noticed that they are being updated much less frequently), but I am confident that it will eventually pay off.
+
+It should also be noted that mailto:fuz@FreeBSD.org[Robert Clausecker] has enabled package:lang/gcc11[], package:lang/gcc12[], and package:lang/gcc13[] for riscv64 architecture as the ports build fine on 15-CURRENT.
diff --git a/website/content/en/status/report-2024-04-2024-06/github.adoc b/website/content/en/status/report-2024-04-2024-06/github.adoc
new file mode 100644
index 0000000000..be5a1348fa
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/github.adoc
@@ -0,0 +1,39 @@
+=== FreeBSD GitHub Pull Request Report
+
+Links: +
+link:https://wiki.freebsd.org/WorkingGroup/Github[GitHub Working Group wiki page] URL: link:https://wiki.freebsd.org/WorkingGroup/GitHub[] +
+link:https://github.com/freebsd/freebsd-src/pulls[FreeBSD Base System Pull Requests] URL: link:https://github.com/freebsd/freebsd-src/pulls[]
+
+Contact: Warner Losh <imp@FreeBSD.org>
+
+The FreeBSD Project has been trying an experiment to accept contributions via GitHub pull requests.
+We have learned a lot in the last year that we've been doing this.
+We have created a number of rules relating to the pull requests.
+In general, pull requests should only be for things that are user-visible, add value to the project and are ready to go, modulo final review.
+
+Current status:
+
+ * We are able to keep up with the pull requests doing everything by hand, but only if we do it at least weekly.
+ * We have discovered the by-hand process is tedious and error-prone.
+ * We can stage multiple pull requests in a testing branch so we can batch-up testing.
+ * We can automatically land the result so merged pull requests show up as merged in GitHub infrastructure.
+
+We need help with automating the process:
+
+ * Add automated testing that is context specific (for example, run igor over man pages).
+ * Add build/install tests that test-boot the resulting image.
+ * Automate common tasks, like man page corrections, into staging process.
+ * Add simple smoke testing for the staging branch for tier 1 architectures.
+ * Investigate optionally integrating Jenkins testing to scale up the size of changes we can accept.
+ * Integrate with Bugzilla problem reports and Phabricator reviews.
+ * Improve the submitter experience on GitHub by automating common feedback to mistakes in the pull requests.
+ * Create checklists for submitters to reduce errors.
+ * Create better reporting about pull requests, especially the frequent contributors of good pull requests.
+
+We are coordinating on FreeBSD's Discord in the #github-hacking channel.
+Join us there to pitch in, or just chat about the project.
+
+Once things are fine-tuned, we want to publicity to steer contributors, at least the base system, to GitHub pull requests.
+We need more developers looking at the FreeBSD GitHub pull requests.
+We will also need more developers to review and land pull requests once it is automated and the automation has matured.
+We sincerely hope that we can improve the FreeBSD contribution experience with this, as well as gain useful fixes from the community.
diff --git a/website/content/en/status/report-2024-04-2024-06/intro.adoc b/website/content/en/status/report-2024-04-2024-06/intro.adoc
new file mode 100644
index 0000000000..5d92c3a999
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/intro.adoc
@@ -0,0 +1,9 @@
+Here is the second 2024 status report, with 20 entries.
+
+It has been very difficult to publish this status report within the usual schedule: indeed we are late.
+Unfortunately many of us have been busy with a lot of stuff, both inside and outside FreeBSD, thus some reports arrived late and report publication was slower than usual.
+Hopefully, this quarter was an exception and next quarter we will already be back on track, with 2024Q3 report published within October 2024.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2024-04-2024-06/kde.adoc b/website/content/en/status/report-2024-04-2024-06/kde.adoc
new file mode 100644
index 0000000000..981fb6c324
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/kde.adoc
@@ -0,0 +1,39 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] +
+link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[]
+
+Contact: Adriaan de Groot <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+The mailto:kde@FreeBSD.org[KDE team] is part of mailto:desktop@FreeBSD.org[desktop@], building the software stack to make FreeBSD beautiful and usable as a daily driver graphical desktop workstation.
+
+We missed a quarter, while the broader KDE community celebrated the KDE Megarelease of KDE Frameworks 6, KDE Plasma 6 and KDE Gear.
+The latest software is still not available on FreeBSD, pending more testing and some integration work.
+
+==== Infrastructure
+
+CMake was updated several times and is now version 3.29.6, the latest upstream release.
+CMake in the ports framework now supports setting parallel-build for tests.
+
+Qt5 is now on long-term support and updates only rarely.
+An update to 5.15.14 and WebEngine to 5.15.17 was landed in May.
+
+Qt6 and the Python bindings for Qt, Pyside, were updated to version 6.7.2.
+
+==== KDE Stack
+
+KDE Gear, Plasma and Frameworks release happen very regularly.
+These updates arrive in the FreeBSD ports tree only piecemeal, due to lagging work on compatibility and testing.
+
+* KDE Frameworks reached version 6.3.0
+* KDE Plasma 6 Desktop was updated to version 6.0.4
+* KDE Gear 6 has not yet arrived in the ports tree
+
+==== Related Ports
+
+The KDE ecosystem includes a wide range of ports -- most maintained by mailto:kde@FreeBSD.org[kde@], all building on a shared base of Qt and KDE Frameworks.
+The mailto:kde@FreeBSD.org[KDE team] updates them all as needed.
+This quarter the KDE team would like to thank mailto:tcberner@FreeBSD.org[Tobias C. Berner], mailto:arrowd@FreeBSD.org[Gleb Popov] and mailto:jhale@FreebSD.org[Jason E. Hale] again for keeping things up-to-date.
diff --git a/website/content/en/status/report-2024-04-2024-06/openstack.adoc b/website/content/en/status/report-2024-04-2024-06/openstack.adoc
new file mode 100644
index 0000000000..4543c41236
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/openstack.adoc
@@ -0,0 +1,27 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[]
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+The OpenStack on FreeBSD project aims to integrate OpenStack cloud infrastructure with the FreeBSD operating system, utilizing FreeBSD's unique features while maintaining compatibility with OpenStack standards.
+
+In the second quarter of 2024, we continued to advance the project significantly.
+One of our key activities was attending BSDCan 2024, where we presented on link:https://youtu.be/TUHfTw6OX-8?si=2ramynfxOwa9MgYe["Towards a Robust FreeBSD-based Cloud: Porting OpenStack Components"].
+This presentation helped increase the project's visibility and attracted interest from potential contributors.
+
+We expanded the current single-node proof-of-concept (POC) site to a three-node setup.
+This involved detailed environment setup and network planning.
+Additionally, we began migrating the base to FreeBSD 15.0-CURRENT to ensure our project stays aligned with the latest advancements in FreeBSD.
+
+We also started working on adapting the manual installation steps and code patches into FreeBSD ports, aiming to streamline the installation process for future users.
+Another major milestone was initiating work on making bare-metal provisioning function on both FreeBSD instances and service hosts for OpenStack Ironic.
+
+Looking forward to the next quarter, our focus will be on refining these advancements and further enhancing the project's robustness and ease of use.
+Specifically, we aim to upgrade our OpenStack components from the Xena version to a more recent release, as Xena has entered the "unmaintained" phase and will soon reach EOL.
+We welcome any suggestions and contributions from the community to help us achieve our goals.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-04-2024-06/openzfs.adoc b/website/content/en/status/report-2024-04-2024-06/openzfs.adoc
new file mode 100644
index 0000000000..979cb31434
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/openzfs.adoc
@@ -0,0 +1,26 @@
+=== Hierarchical rate limits for OpenZFS
+
+Links: +
+link:https://github.com/openzfs/zfs/pull/16205[Pull request] URL: link:https://github.com/openzfs/zfs/pull/16205[]
+
+Contact: Pawel Dawidek <pawel@dawidek.net>
+
+Rate limits allow to limit bandwidth and number of metadata operations per dataset.
+
+Hierarchical rate limits allow for granular resource control especially in shared environments, eg. when a single ZFS pool serves data to multiple, independent virtual machines or jails.
+
+Because the limits are hierarchical, they are enforced like the quota property: the children datasets must obey the limits of the parent dataset.
+
+The limits can be configured using six new properties:
+limit_bw_read, limit_bw_write, limit_bw_total, limit_op_read, limit_op_write, limit_op_total
+The limit_bw_* properties limit the read, write, or combined bandwidth, respectively, that a dataset and its descendants can consume.
+Those limits are in bytes per second.
+The limit_op_* properties limit the read, write, or both metadata operations, respectively, that a dataset and its descendants can generate.
+Those limits are in number of operations per second.
+
+Limits are applied to file systems and ZFS volumes (and their snapshots).
+
+The initial work is done and the pull request is up for review.
+
+Sponsor: Klara Systems
+Sponsor: FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-04-2024-06/portmgr.adoc b/website/content/en/status/report-2024-04-2024-06/portmgr.adoc
new file mode 100644
index 0000000000..9998705ca9
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/portmgr.adoc
@@ -0,0 +1,55 @@
+=== Ports Collection
+
+Links: +
+link:https://ports.FreeBSD.org[About FreeBSD Ports] URL:link:https://ports.FreeBSD.org[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: Tobias C. Berner <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+According to INDEX, there are currently 32,471 ports in the Ports Collection.
+There are currently ~3,497 open ports PRs.
+The last quarter saw 10,525 commits by 160 committers on the main branch and 1771 commits by 107 committers on the 2024Q2 branch.
+Compared to last quarter, this means a large decrease in the number of commits on the main branch (down from 12,991) and backports to the quarterly branch (compared to 888).
+The number of ports also increased (up from 32,244).
+
+The most active committers to main were:
+
+* sunpoet   3739
+* yuri      1450
+* jbeich     491
+* eduardo    220
+* bofh       200
+* diizzy     197
+* rene       188
+* fernape    156
+* jhale      133
+* arrowd     129
+
+A lot has happened in the ports tree in the last three quarter, an excerpt of the major software upgrades is:
+
+* pkg 1.21.3
+* Default version of lazarus switched to 3.4.0
+* Default version of fpc switched to 3.2.3
+* Default version of python switched to 3.11
+* chromium      updated from   123.0.6312.86 to  126.0.6478.126
+* firefox       updated from         124.0.1 to         127.0.2
+* firefox-esr   updated from        115.9.0 to         115.12.1
+* rust          updated from          1.77.0 to          1.79.0
+* sdl2          updated from           2.6.3 to           2.8.2
+* wlroots       updated from          0.17.2 to          0.17.4
+* wine          updated from           8.0.2 to             9.0
+* wine-devel    updated from            9.4 to             9.11
+* xorg-server   updated from         21.1.11 to         21.1.13
+* qt5           updated from         5.15.13 to         5.15.14
+* qt6           updated from           6.6.3 to           6.7.2
+* kf5           updated from         5.115.0 to         5.116.0
+* kf6           updated from           6.0.0 to           6.3.0
+* plasma6       updated from           6.0.2 to           6.1.1
+
+During the last quarter, pkgmgr@ ran 24 exp-runs to test various ports upgrades, updates to default versions of ports, subpackage support and base system changes.
diff --git a/website/content/en/status/report-2024-04-2024-06/pot.adoc b/website/content/en/status/report-2024-04-2024-06/pot.adoc
new file mode 100644
index 0000000000..1acf536d56
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/pot.adoc
@@ -0,0 +1,23 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+During this quarter, there were no new link:https://github.com/bsdpot/pot[Pot] releases.
+
+Potluck images saw some updates again though.
+All images have been rebuilt for the new quarterly packages, a new link:https://github.com/bsdpot/potluck/tree/master/opensearch[Opensearch] container has been added.
+Additional features, updates and fixes have been committed to containers like link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[PostgreSQL-Patroni] or link:https://github.com/bsdpot/potluck/tree/master/nomad-server-tls[Nomad-Server-TLS].
+
+In total, there are 58 container images and templates available now.
+
+As always, feedback and patches are welcome.
+
+Sponsors: Nikulipe UAB, Honeyguide Group
diff --git a/website/content/en/status/report-2024-04-2024-06/releng.adoc b/website/content/en/status/report-2024-04-2024-06/releng.adoc
new file mode 100644
index 0000000000..114bdbc2b2
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/releng.adoc
@@ -0,0 +1,19 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/14.1R/announce/[FreeBSD 14.1-RELEASE announcement] URL: link:https://www.freebsd.org/releases/14.1R/announce/[] +
+link:https://www.freebsd.org/releases/13.4R/schedule/[FreeBSD 13.4-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.4R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+The Team mourns the loss of Mike Karels, who was the Deputy Release Engineering Lead and mere days before his death agreed to take the role of Release Engineer for 13.4-RELEASE.
+
+The Team managed 14.1-RELEASE, leading to the final RELEASE build and announcement in June.
+During the second quarter of the year, the Team has gained new members: Ed Maste (Deputy Release Engineer Lead), Dave Cottlehuber, John Hixson, Mahdi Mokhtari, Doug Rabson, Muhammad Moinur Rahman.
+Planning has started for the upcoming 13.4-RELEASE cycle.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/14*, and *stable/13* branches.
diff --git a/website/content/en/status/report-2024-04-2024-06/riscv.adoc b/website/content/en/status/report-2024-04-2024-06/riscv.adoc
new file mode 100644
index 0000000000..79013da519
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/riscv.adoc
@@ -0,0 +1,71 @@
+=== FreeBSD/riscv64
+
+Links: +
+link:https://wiki.freebsd.org/riscv[Wiki Homepage] URL: link:https://wiki.freebsd.org/riscv[] +
+
+Contact: Mitchell Horne <mhorne@FreeBSD.org> +
+Contact: Ruslan Bukin <br@FreeBSD.org> +
+Contact: Jari Sihvola <jsihv@gmx.com>
+
+The FreeBSD/RISC-V project is providing support for running FreeBSD on the link:https://riscv.org[RISC-V Instruction Set Architecture].
+
+==== BSDCan Devsummit Updates
+
+Mitchell gave a presentation on the status of the FreeBSD/riscv64 platform at the June developers' summit, part of BSDCan 2024.
+The presentation discussed the challenges of supporting the evolving RISC-V ISA, and gave a brief overview of some available hardware targets.
+It is informal in nature, but available to watch on youtube.
+
+link:https://www.youtube.com/watch?v=O7zW7Z9U0ns[]
+
+==== StarFive JH7110 SoC / VisionFive v2
+
+Work has been ongoing to support the JH7110 RISC-V SoC in FreeBSD.
+This SoC is present in several existing RISC-V SBCs.
+The primary support target is the VisionFive v2, but this work is likely to benefit similar hardware such as the Pine64 Star64 and the Milk-V Mars.
+
+At present, the support in CURRENT is partially complete.
+What is working:
+ * UART
+ * clk/reset drivers
+ * MMC/SD
+
+The next target is working ethernet, which is supported with extensions to the `if_eqos` driver.
+This code is functional, but still in review.
+
+Work on this has been performed by Jari, with review, testing, and integration from Mitchell.
+
+link:https://wiki.freebsd.org/riscv/StarFive[]
+
+==== T-HEAD/XuanTie CPU Support
+
+As discussed in the devsummit presentation, these CPUs present several barriers to support.
+The problems come primarily from custom vendor extensions: non-coherent device I/O with custom cache management instructions, and a custom (spec-violating) implementation of page-based memory types.
+Combined, these quirks require difficult and invasive changes to pmap, busdma, and early boot code.
+
+At the same time, we are seeing an increasing amount of available hardware based on this IP, and so support becomes a repeated question and incentive.
+
+Work on page-based memory types is underway and expected to land soon in CURRENT.
+This feature allows individual virtual memory pages to be assigned specific properties, e.g. cacheability requirements.
+The riscv64 pmap has been extended to support the official RISC-V 'Svpbmt' extension, and the T-HEAD version of PBMT.
+These alternative encodings are incompatible, but provide similar functionality.
+
+Work on the device coherence and cache management challenges will begin next quarter.
+
+The hope is that this foundational work will (eventually) enable board support for available RISC-V hardware such as:
+ * Allwinner D1 (Nehza)
+ * Sipeed Lichee Pi 4A
+ * Beagle-V Ahead
+ * Milk-V Pioneer
+
+==== RISC-V Hypervisor
+
+Experimental support for the RISC-V hypervisor in bhyve/`vmm(4)` is under active development.
+Currently, single-core VMs are possible, and the guest can boot to multi-user.
+
+Note: the "H" (hypervisor) extension is not implemented by any known existing or upcoming RISC-V hardware.
+It is fully supported by software simulators such as Spike or QEMU.
+
+link:https://wiki.freebsd.org/riscv/bhyve[]
+
+Sponsor: The FreeBSD Foundation (mhorne's work)
+Sponsor: UKRI (br's work)
diff --git a/website/content/en/status/report-2024-04-2024-06/service-jails.adoc b/website/content/en/status/report-2024-04-2024-06/service-jails.adoc
new file mode 100644
index 0000000000..0fec2ab32f
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/service-jails.adoc
@@ -0,0 +1,23 @@
+=== Service jails -- Automatic jailing of rc.d services
+
+Links: +
+link:https://docs.freebsd.org/en/articles/rc-scripting/#rcng-service-jails[rc-article part for Service Jails] URL: link:https://docs.freebsd.org/en/articles/rc-scripting/#rcng-service-jails[]
+
+Contact: Alexander Leidinger <netchild@FreeBSD.org>
+
+Service jails extend the man:rc[8] system to allow automatic jailing of rc.d services.
+A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, ...) by default.
+Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (man:vmm[4]).
+
+The base system infrastructure and the basesystem rc.d services are committed to 15-current, and the handbook / rc article updates are committed to the documentation.
+Next steps are to extend services in the ports collection to be able to make use of it.
+
+If you want to put e.g. nginx into a service jail and allow IPv4 and IPv6 access, simply change man:rc.conf[5] to have:
+----
+nginx_svcj_options=net_basic
+nginx_svcj=YES
+----
+
+While this does not have the same security benefits as a manual jail setup with a separate filesystem and IP/VNET, it is much easier to set up, while providing some of the security benefits of a jail like hiding other processes of the same user.
+
+Any testing and feedback (even as simple as "service X works in a service jail") is welcome.
diff --git a/website/content/en/status/report-2024-04-2024-06/zcond.adoc b/website/content/en/status/report-2024-04-2024-06/zcond.adoc
new file mode 100644
index 0000000000..f93c55c31f
--- /dev/null
+++ b/website/content/en/status/report-2024-04-2024-06/zcond.adoc
@@ -0,0 +1,43 @@
+=== A low-cost conditional execution mechanism
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2024Projects/ZeroCostConditionalExecutionMechanism[FreeBSD wiki] URL: https://wiki.freebsd.org/SummerOfCode2024Projects/ZeroCostConditionalExecutionMechanism[] +
+
+Contact: Marko Vlaić <mvlaic@freebsd.org>
+Contact: Bojan Novković (mentor) <bnovkov@freebsd.org>
+
+This project aims to implement a low-cost conditional execution mechanism, similar to the `static_key` interface in Linux.
+The current working name is `zcond`, as in zero-cost conditional.
+The idea is to reduce the overhead of rarely used features in performance sensitive kernel code paths.
+Specifically, code blocks of the following, simple structure, are targeted:
+
+[source, c]
+----
+if(some_global_flag == true) {
+    do_some_additional_task();
+}
+----
+
+A block like this can cause performance overhead in a frequently executed piece of code.
+
+The motivating use case for the mechanism is tracing (as outlined here in the link:https://wiki.freebsd.org/SummerOfCodeIdeas#Unified_kernel_tracing_interface[wiki]), but the project will identify more areas where this mechanism could be applied.
+
+The backbone of the mechanism is runtime instruction hot patching, making it highly architecture dependent.
+Great care has to be given to security, because kernel instructions are overwritten at runtime.
+More details and some implementation ideas can be found in the project proposal on the link:https://wiki.freebsd.org/SummerOfCode2024Projects/ZeroCostConditionalExecutionMechanism[project wiki page].
+More documents describing the implementation and design decisions will be produced, as the project moves along.
+
+The goal of the project is to produce a working implementation of the mechanism for the x86-64 architecture.
+It will then be applied to an existing piece of kernel code and benchmarked.
+If the benchmark results come out positive, it will be ported to other architectures.
+
+This project is a part of the link:https://summerofcode.withgoogle.com/[Google Summer of Code 2024.].
+The project is still in its early stages, but any feedback would be highly appreciated.
+
+==== Help wanted
+* General feedback on the mechanism, API and implementation
+* More use cases besides tracing are welcome
+* Code review
+* Name suggestions
+
+Sponsor: Google LLC (GSoC 2024)
diff --git a/website/content/en/status/report-2024-07-2024-09/_index.adoc b/website/content/en/status/report-2024-07-2024-09/_index.adoc
new file mode 100644
index 0000000000..c2172524ca
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/_index.adoc
@@ -0,0 +1,195 @@
+---
+title: "FreeBSD Status Report Third Quarter 2024"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2024-07-2024-09
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+include::{reports-path}/bugmeister.adoc[]
+
+'''
+
+include::{reports-path}/samba.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+{projects-desc}
+
+include::{reports-path}/audio.adoc[]
+
+'''
+
+include::{reports-path}/bhyvemgr.adoc[]
+
+'''
+
+include::{reports-path}/dhclient.adoc[]
+
+'''
+
+include::{reports-path}/code-audit.adoc[]
+
+'''
+
+include::{reports-path}/eim-nat.adoc[]
+
+'''
+
+include::{reports-path}/kyua.adoc[]
+
+'''
+
+include::{reports-path}/sourcecompat.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+include::{reports-path}/service-jails.adoc[]
+
+'''
+
+include::{reports-path}/fuse-ufs.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+include::{reports-path}/uvc.adoc[]
+
+'''
+
+include::{reports-path}/mac_do.adoc[]
+
+'''
+
+include::{reports-path}/sched_prio-256_queue_runqueue.adoc[]
+
+'''
+
+include::{reports-path}/wireless.adoc[]
+
+'''
+
+include::{reports-path}/vsock.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+include::{reports-path}/pinephone.adoc[]
+
+'''
+
+include::{reports-path}/simd.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/ec2.adoc[]
+
+'''
+
+include::{reports-path}/openstack.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+include::{reports-path}/wiki.adoc[]
+
+'''
+
+include::{reports-path}/frdp.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/fpc-lazarus.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2024-07-2024-09/audio.adoc b/website/content/en/status/report-2024-07-2024-09/audio.adoc
new file mode 100644
index 0000000000..4d113f7fcb
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/audio.adoc
@@ -0,0 +1,32 @@
+=== Audio Stack Improvements
+
+Contact: Christos Margiolis <christos@FreeBSD.org>
+
+The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement -- from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs.
+This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature.
+
+Important work since link:https://www.freebsd.org/status/report-2024-04-2024-06/#_audio_stack_improvements[last report]:
+
+* Several man:sound[4] fixes.
+* Wrote link:https://cgit.freebsd.org/src/tree/usr.sbin/mixer/tests[mixer(8)] and link:https://cgit.freebsd.org/src/tree/tests/sys/sound[sound(4)] tests.
+* link:https://cgit.freebsd.org/src/commit/?id=9aac27599acaffa21ff69c5be8a2d71d29cc3d6b[mixer(8): Implement hot-swapping]
+* link:https://reviews.freebsd.org/D46227[audio(8): Initial revision]
+* link:https://cgit.freebsd.org/src/commit/?id=c15c9315b2cb7601cc337f7d5a8e124f4b2d5861[sound: Implement dummy driver]
+* Improved and added link:https://cgit.freebsd.org/src/tree/share/examples/sound[sound examples].
+* link:https://reviews.freebsd.org/D46418[mididump(1): Initial revision]
+* virtual_oss patches.
+* Gave a talk at the 09/2024 DevSummit in Dublin, Ireland.
+
+Future work includes:
+
+* More bug fixes and improvements.
+* Finalize and commit of man:audio[8] and man:mididump[1].
+* Implement a generic MIDI layer, similar to pcm/, and improve/modernize the MIDI codebase in general.
+* Implement a bluetooth device management utility.
+* More virtual_oss patches and improvements.
+* Attempt to implement an man:snd_hda[4] pin-patching mechanism.
+* Investigate SOF/DMIC support.
+
+You can also follow the development process in link:https://lists.freebsd.org/subscription/freebsd-multimedia[freebsd-multimedia@], where I post regular reports.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-07-2024-09/azure.adoc b/website/content/en/status/report-2024-07-2024-09/azure.adoc
new file mode 100644
index 0000000000..a3a80f1bc5
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/azure.adoc
@@ -0,0 +1,40 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.freebsd.org/subscription/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Colin Su <yuas@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+In this quarter, we have published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-13_4[13.4-RELEASE on Azure Marketplace].
+
+Souradeep Chakrabarti from Microsoft has added a feature to use hypercalls for TLB shootdown on Hyper-V and Azure.
+Micro-benchmark shows 30-40% performance improvement on TLB shootdown.
+This has been presented at the link:https://wiki.freebsd.org/DevSummit/202409[DevSummit 202409]
+
+Wei Hu root-caused an issue on missing CDROM device when booting FreeBSD on the latest Azure v6 VM SKU.
+V6 type only offers NVMe disks to guest OS.
+He also continues bug fixing for FreeBSD MANA NIC device.
+
+Work in progress tasks:
+
+* Automating the image publishing process and merging to [.filename]#src/release/#. (Li-Wen Hsu)
+* Colin Su is testing adding FreeBSD support in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+** https://github.com/microsoft/azure-pipelines-agent/pull/3266[]
+** Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+
+Open tasks:
+
+* Update FreeBSD-related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Update package:sysutils/azure-agent[] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure]
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2024-07-2024-09/bhyvemgr.adoc b/website/content/en/status/report-2024-07-2024-09/bhyvemgr.adoc
new file mode 100644
index 0000000000..ee473ed0f6
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/bhyvemgr.adoc
@@ -0,0 +1,26 @@
+=== A bhyve management GUI written in Freepascal/Lazarus
+
+Links: +
+link:https://github.com/alonsobsd/bhyvemgr[Bhyvemgr] URL: link:https://github.com/alonsobsd/bhyvemgr/[] +
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+Bhyvemgr is a bhyve management GUI written in Freepascal/Lazarus on FreeBSD.
+It needs a bunch of tools mostly installed by the base system and some installed from ports/packages.
+The main goal is to be a desktop application focus on desktop user to easily and quickly setup and run virtual machines on FreeBSD hosts.
+
+It should be used for virtual machines testing purpose (not for production).
+For a tool for production virtual machines management, take a look at package:sysutils/vm-bhyve[], package:sysutils/bmd[], or package:sysutils/cbsd[].
+
+Bhyvemgr supports aarch64 on 15-CURRENT only, and amd64 from FreeBSD 13.x to 15-CURRENT.
+It can be compiled from package:sysutils/bhyvemgr[] as a port, or installed as packages with gtk2, qt5, or qt6 interface support.
+
+People interested in helping the project are welcome.
+
+Version at the end of 2024Q3: 1.1.0
+
+TODO
+
+* Test on real aarch64 hardware
+* Add uart device support
+* Add missing global setting entries (bios, board, chassis, system)
diff --git a/website/content/en/status/report-2024-07-2024-09/bugmeister.adoc b/website/content/en/status/report-2024-07-2024-09/bugmeister.adoc
new file mode 100644
index 0000000000..9f7ccae56c
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/bugmeister.adoc
@@ -0,0 +1,43 @@
+=== Bugmeister Team
+
+Links: +
+link:https://wiki.freebsd.org/Bugzilla[FreeBSD Bugzilla] URL: link:https://wiki.freebsd.org/Bugzilla[]
+
+Contact: Bugmeister <bugmeister@FreeBSD.org>
+
+==== Charts and graphs
+
+link:mailto:emaste@FreeBSDFoundation.org[Ed Maste from the FreeBSD Foundation] has expressed an interest in seeing useful charts and graphs added to Bugzilla.
+The few that we have now are not very informative.
+Many of the link:https://wiki.freebsd.org/Bugzilla/SearchQueries[interesting Bugzilla queries] for them have been documented, but the information there is really dense.
+
+If you are interested in working on this task, contact Ed directly.
+
+==== Bugzilla version upgrade
+
+Recently, upstream Bugzilla has released 5.0.4.1, which is a minor bugfix release.
+Preliminary work suggests that the update will be unobtrusive.
+Work is continuing.
+
+==== PR statistics
+
+PRs continue to come in and get triaged.
+Over the longer term, we are nearly at steady-state.
+
+The number of PRs over the past quarter (and year) has fluctuated.
+Vladimir Druzenko pointed out that the number dropped by around 200 during 2023Q4.
+(We have not done the data analysis to find out why that was.)
+However, slowly, the number has come back to where it was a year ago.
+But we do seem to be closing incoming PRs more quickly these days.
+For reference:
+
+link:https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=365[]
+
+The overall number of PRs remains at slightly over 11,600.
+We do have a lot of technical debt.
+
+Bugmeister is also working towards restarting the link:https://wiki.freebsd.org/Bugathons[Bugathons].
+
+==== Acknowledgements
+
+Bugmeister would like to thank a number of people who have assisted with bugbusting, including new triagers Alexander Vereeken, Alexander Ziaee, and Frederick Lee.
diff --git a/website/content/en/status/report-2024-07-2024-09/ci.adoc b/website/content/en/status/report-2024-07-2024-09/ci.adoc
new file mode 100644
index 0000000000..8d5be4af60
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/ci.adoc
@@ -0,0 +1,47 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://tinderbox.freebsd.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the fourth quarter of 2024, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* Update main and stable/14 build environment to 14.1-RELEASE
+
+Work in progress tasks:
+
+* Improving the [.filename]#src/tests/ci# work to support running test suites
+* Merging link:https://reviews.freebsd.org/D36257[Pre-commit CI with CIRRUS-CI]
+* Designing and implementing pre-commit CI building and testing and pull/merge-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+  * Proof of concept system is in progress.
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Redesigning the hardware test lab and adding more hardware for testing
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-07-2024-09/code-audit.adoc b/website/content/en/status/report-2024-07-2024-09/code-audit.adoc
new file mode 100644
index 0000000000..05b5957c45
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/code-audit.adoc
@@ -0,0 +1,26 @@
+=== Capsicum and Bhyve Code Audit
+
+Contact: Ed Maste <emaste@FreeBSD.org>
+Contact: Pierre Pronchery <pierre@freebsdfoundation.org>
+
+With the support of the link:https://alpha-omega.dev/[Alpha-Omega project], the FreeBSD Foundation undertook code audits of two important subsystems -- the bhyve hypervisor, and the Capsicum sandboxing framework.
+In addition to uncovering vulnerabilities in these systems to correct, the audits look to identify classes of vulnerabilities and/or suboptimal coding practices that we can look to address across the project.
+
+The Foundation interviewed several firms, and selected Synacktiv to perform the audit.
+A number of issues with critical and high severity were identified, which have been fixed as documented in security advisories:
+
+* link:https://www.freebsd.org/security/advisories/FreeBSD-SA-24:09.libnv.asc[FreeBSD-SA-24:09.libnv]
+* link:https://www.freebsd.org/security/advisories/FreeBSD-SA-24:10.bhyve.asc[FreeBSD-SA-24:10.bhyve]
+* link:https://www.freebsd.org/security/advisories/FreeBSD-SA-24:11.ctl.asc[FreeBSD-SA-24:11.ctl]
+* link:https://www.freebsd.org/security/advisories/FreeBSD-SA-24:12.bhyve.asc[FreeBSD-SA-24:12.bhyve]
+* link:https://www.freebsd.org/security/advisories/FreeBSD-SA-24:14.umtx.asc[FreeBSD-SA-24:14.umtx]
+* link:https://www.freebsd.org/security/advisories/FreeBSD-SA-24:15.bhyve.asc[FreeBSD-SA-24:15.bhyve]
+* link:https://www.freebsd.org/security/advisories/FreeBSD-SA-24:16.libnv.asc[FreeBSD-SA-24:16.libnv]
+
+Fixes are in progress for a number of lower-severity issues.
+The code audit report will be shared in the near future, after issues above a severity threshold have been addressed.
+The FreeBSD Foundation will also publish a report including commentary on the impact of the Synacktiv code audit report, classes of vulnerabilities identified, and lessons learned.
+
+More information is available in the link:https://github.com/ossf/alpha-omega/tree/main/alpha/engagements/2024/FreeBSD[Alpha-Omega repository].
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-07-2024-09/core.adoc b/website/content/en/status/report-2024-07-2024-09/core.adoc
new file mode 100644
index 0000000000..36354bdf5b
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/core.adoc
@@ -0,0 +1,50 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+Core welcomes René Ladan (rene@) as their new secretary.
+
+==== Liaisons
+
+Core selected new liaisons for the various teams among themselves:
+
+* bugmeister:   glebius
+* ci:           olivier
+* clusteradm:   mat
+* doceng:       lwhsu
+* foundation:   hrs
+* portmgr:      tcberner
+* re:           dch
+* secteam:      allanjude
+* srcmgr:       glebius
+
+==== DevSummit 202409
+
+* The Core Team was almost fully present at EuroBSDCon 2024 in Dublin.
+  The following people were present: allanjude, dch, glebius, hrs, lwhsu, mat, olivier, rene
+
+* Slides are available at link:https://wiki.freebsd.org/DevSummit/202409[]
+
+* Core met with the FreeBSD Foundation to have their periodic meeting and take the change to do it in face-to-face.
+  Topics included improving alignment and communications between the two groups and the community.
+
+==== New support timeline for FreeBSD releases
+
+* Core approves the proposal by re@ to reduce the support timeline for FreeBSD releases from five to four years, after which the release is supported on a best-effort basis.
+  This proposal is also backed by portmgr and secteam.
+
+==== srcmgr
+
+* Core helped in forming a new srcmgr team.
+  Their charter is not fully set in stone yet, it can be adjusted if needed in 6-12 months from now.
+* Nominations for new src commit bits should from now on be sent to srcmgr@ instead of core@
+* A lurker program is suggested to keep an influx of new members.
+* Core announced srcmgr during DevSummit 202409 and sent a follow-up to developers@ on September 29.
+
+==== Commit bits
+
+* Core welcomes Igor Ostapenko (igoro) as a new src committer.
+
+* Core extended the text that the grim reaper script sends to include ways on how to get commit bits of developers re-activated.
diff --git a/website/content/en/status/report-2024-07-2024-09/dhclient.adoc b/website/content/en/status/report-2024-07-2024-09/dhclient.adoc
new file mode 100644
index 0000000000..9d6468aa54
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/dhclient.adoc
@@ -0,0 +1,19 @@
+=== Changes to dhclient to speed up the FreeBSD boot process
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2024Projects/SpeedingUpTheFreeBSDBootProcess[Speeding up the FreeBSD boot process] URL: link:https://wiki.freebsd.org/SummerOfCode2024Projects/SpeedingUpTheFreeBSDBootProcess[] +
+
+link:https://github.com/freebsd/freebsd-src/pull/1368[dhclient Pull Request] URL: link:https://github.com/freebsd/freebsd-src/pull/1368[] +
+
+Contact: Isaac Cilia Attard <icattard@FreeBSD.org>
+
+As part of my Google Summer of Code 2024 project, involving speeding up the FreeBSD boot process, I have worked on decreasing the time it takes for ARP resolution within dhclient to happen.
+This involved reducing the default ARP resolution timeout from 2000 ms to 250 ms, and adding an option to disable it altogether.
+The latter is useful within cloud environments, where a node is certain to have an IP address allotted to it.
+
+As a consequence of this, connecting to a DHCP network is now faster, including the boot process during which this happens.
+The speedup experienced is about 2 seconds.
+
+This causes FreeBSD systems to boot significantly faster than before.
+
+Sponsor: Google LLC (GSoC 2024)
diff --git a/website/content/en/status/report-2024-07-2024-09/doceng.adoc b/website/content/en/status/report-2024-07-2024-09/doceng.adoc
new file mode 100644
index 0000000000..2f3f0eee8e
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/doceng.adoc
@@ -0,0 +1,92 @@
+////
+Quarter:	
+Prepared by:	
+Reviewed by:	
+Last edit:	$Date$
+Version:	$Id:$
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+Benedict Reuschling steps down from doceng@.
+doceng@ would like to thank bcr@ for his service.
+
+==== Document changes
+
+* Handbook: Document the automatic creation of XDG directories starting with
+  FreeBSD 14.1.
+  The VNET config example script has been fixed.
+
+* Architecture Handbook: remove K&R prototypes in MAC chapter.
+
+* Website: Some improvements regarding the top banner and layout, visually
+  rearrange buttons and more.
+
+* Documentation repository: fix of all malformed tables warnings.
+  Removal of deprecated attributes to conform to new gohugo releases.
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblate[] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/[]
+
+===== Q3 2024 Status
+
+* 17 team languages
+* 214 registered users
+
+1 new translator joined Weblate:
+
+* matthew (id)
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 7%)
+* Chinese (Traditional) (zh-tw)	(progress: 3%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Greek (el)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 5%)
+* Korean (ko)			(progress: 32%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 3%)
+* Polish			(progress: 2%)
+* Portuguese			(progress: 0%)
+* Portuguese (pt-br)		(progress: 24%)
+* Spanish (es)			(progress: 36%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+==== Packages maintained by DocEng
+
+During this quarter the following work was done in packages maintained by
+doceng@:
+
+* textproc/docproj: Bump gohugo dependency to 0.133.1
+* www/gohugo: update to 0.134.3
+
+==== Open issues
+
+There are 2 Open PRs in bugzilla assigned to doceng@:
+
+ * 276923 www/gohugo link error under poudriere
+ * 267274 Please remove the zh-CN Handbook of the current FreeBSD website
+
+During this quarter doceng@ closed 3 PRs:
+
+ * 266107 FreeBSD Handbook and other books: PDF: broken links – crossref
+ * 279815 status reports: ERR_TOO_MANY_REDIRECTS
+ * 281396 handbook: ERROR: <stdin>: line 149: dropping cells from incomplete row detected
diff --git a/website/content/en/status/report-2024-07-2024-09/ec2.adoc b/website/content/en/status/report-2024-07-2024-09/ec2.adoc
new file mode 100644
index 0000000000..cd3e907ed4
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/ec2.adoc
@@ -0,0 +1,13 @@
+=== FreeBSD on EC2
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances.
+
+In the past quarter, a new "small" flavour of EC2 AMI has been added, without debug symbols, tests, 32-bit compatibility libraries, or the LLVM debugger, and without the Amazon SSM Agent pre-installed or the AWS CLI installed by default at first boot.
+
+Build performance tests are now being performed weekly using the snapshot AMIs built by the release engineering team.
+These tests revealed several performance regressions which have now been fixed; in particular a bug fix to the use of the EFI RNG in the boot loader produced a dramatic speedup on Graviton instances.
+
+Sponsor: Amazon +
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2024-07-2024-09/eim-nat.adoc b/website/content/en/status/report-2024-07-2024-09/eim-nat.adoc
new file mode 100644
index 0000000000..dadd78f027
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/eim-nat.adoc
@@ -0,0 +1,21 @@
+=== Endpoint-Independent NAT
+
+Contact: Tom Jones <thj@freebsd.org>
+
+This project aims to add support for Endpoint-Independent Mappings for UDP to the pf and ipfw firewalls.
+
+End Point Independent NAT enables applications behind a NAT speaking to multiple remote hosts to receive the same mappings.
+This allows an application without any NAT traversal mechanisms to work around NAT issues to perform peer discovery.
+From the remote hosts perspective the NAT is transparent and it is as-if there is no NAT at all.
+This form of NAT has been given several names over the last few decades and might be known as 'full-cone' NAT.
+
+Patches to pf landed in early September based on work by Damjan Jovanovic and Naman Sood with updates to work on pf in main.
+The patches add a new 'endpoint-independent' suffix to UDP pf nat rules.
+
+ipfw support for endpoint-independent is going to be made available via libalias, allowing any system which uses libalias for address translation to benefit from the change.
+There is an in-progress review https://reviews.freebsd.org/D46689[D46689] to add support to libalias.
+
+The in-progress change and the committed pf change could both benefit from testing in more and diverse environments.
+
+Sponsor: The FreeBSD Foundation
+Sponsor: Tailscale
diff --git a/website/content/en/status/report-2024-07-2024-09/fpc-lazarus.adoc b/website/content/en/status/report-2024-07-2024-09/fpc-lazarus.adoc
new file mode 100644
index 0000000000..8c09748e67
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/fpc-lazarus.adoc
@@ -0,0 +1,28 @@
+=== Freepascal and Lazarus on FreeBSD aarch64
+
+Links: +
+link:https://www.freepascal.org/[Freepascal Project] URL: link:https://www.freepascal.org/[] +
+link:https://www.lazarus-ide.org/[Lazarus IDE] URL: link:https://www.lazarus-ide.org/[]
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+Free Pascal is a mature, versatile, open source Pascal compiler.
+It can target many operating systems and processor architectures: Intel x86 (16 and 32 bit), AMD64/x86-64, PowerPC, PowerPC64, SPARC, SPARC64, ARM, AArch64, MIPS, Motorola 68k, AVR, and the JVM.
+Additionally, support for RISC-V (32/64), Xtensa, and Z80 architectures, and for the LLVM compiler infrastructure is available in the development version.
+Also, the Free Pascal team maintains a transpiler for pascal to Javascript called pas2js.
+
+Lazarus is a Delphi compatible cross-platform IDE for Rapid Application Development.
+It has a variety of components ready for use and a graphical form designer to easily create complex graphical user interfaces.
+
+Three years ago, Mikaël Urankar <mikael@FreeBSD.org> began porting the Free Pascal compiler to FreeBSD aarch64 and it was merged into Free Pascal source code (main branch).
+Some months ago, I added package:lang/fpc-devel[] (3.3.1) and package:editors/lazarus-devel[] (3.99) to the ports tree only for i386 and amd64 because aarch64 was not ready yet.
+The binaries generated on aarch64 did not run because of ELF issues.
+Finally, some days ago the issues were resolved and support for FreeBSD aarch64 was completed.
+
+package:lang/fpc-devel[] and package:editors/lazarus-devel[] were updated to 3.3.1.20240913 and 3.99.20240913 with support for aarch64 respectively.
+It brings to FreeBSD users a new language and platform working on FreeBSD aarch64 for console, graphic, or any kind of apps development.
+
+TODO
+
+* Update package:fpc/lazarus[] based ports (such as package:sysutils/bhyvemgr[] and package:archivers/peazip[]) to support FreeBSD/aarch64
+* Push FreeBSD RISC-V support
diff --git a/website/content/en/status/report-2024-07-2024-09/frdp.adoc b/website/content/en/status/report-2024-07-2024-09/frdp.adoc
new file mode 100644
index 0000000000..c47daf9680
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/frdp.adoc
@@ -0,0 +1,26 @@
+=== The FreeBSD Russian Documentation Project
+
+Links: +
+link:https://docs.freebsd.org/ru/books/faq/[FAQ] URL: link:https://docs.freebsd.org/ru/books/faq/[] +
+link:https://docs.freebsd.org/ru/books/handbook/[Handbook] URL: link:https://docs.freebsd.org/ru/books/handbook/[] +
+link:https://www.freebsd.org/ru/[Web] URL: link:https://www.freebsd.org/ru/[]
+
+Contact: Andrei Zakhvatov <andrey.zakhvatov@gmail.com>
+
+The FreeBSD Russian Documentation Project's current goal is to provide up-to-date Russian translations of the most important parts of FreeBSD documentation (FAQ, Handbook, Web).
+It is important to support Russian speakers with high-quality official technical materials and increase acceptance of the operating system around the globe.
+We hope that this activity will receive some support from the Russian-speaking FreeBSD community and lead to more translated materials.
+
+There is some progress in document translation:
+
+* FAQ: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277008[PR #277008] and link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282062[PR #282062]
+* Handbook: Chapter 1. Introduction: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276334[PR #276334]
+* Handbook: Chapter 2. Installing FreeBSD: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280610[PR #280610]
+* Handbook: Chapter 3. FreeBSD Basics: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282059[PR #282059]
+
+Check link:https://docs.freebsd.org/en/books/fdp-primer/translations/[the official translation guide] if you are willing to help.
+We always appreciate your help with translation of the following materials:
+
+* Handbook chapters and sections
+* Articles
+* Web pages
diff --git a/website/content/en/status/report-2024-07-2024-09/freebsd-foundation.adoc b/website/content/en/status/report-2024-07-2024-09/freebsd-foundation.adoc
new file mode 100644
index 0000000000..fc4d73ded9
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/freebsd-foundation.adoc
@@ -0,0 +1,184 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] +
+link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD.
+We do this in both technical and non-technical ways.
+We are 100% supported by donations from individuals and corporations and those investments help us fund the:
+
+* Software development projects to implement features and functionality in FreeBSD
+* Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD
+* Purchase and support of hardware to improve and maintain FreeBSD infrastructure
+* Resources to improve security, quality assurance, and continuous integration efforts
+* Materials and staff needed to promote, educate, and advocate for FreeBSD
+* Collaboration between commercial vendors and FreeBSD developers
+* Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity
+
+Even though the summer months tend to be slower, we accomplished a lot of work and you will see that in our Q3 report!
+Some highlights include raising over $135,000 from individual donors, and kicking off two major projects.
+First, thanks to a large investment from the Sovereign Tech Fund, we will be doing even more to improve our infrastructure.
+Second, thanks to a large investment by Quantum Leap Research and the Foundation, we will be working to accelerate a FreeBSD on Modern Laptops project.
+We also continued work on the Alpha-Omega funded project, hired a userland software developer, and opened a job position for a solutions specialist.
+
+As you will see below, spreading the word about FreeBSD through advocacy and community is still an important part of our mission.
+Over the summer, we sponsored  EuroBSDCon, and the upcoming FreeBSD and OpenZFS Summits, and provided travel grants to around eight FreeBSD contributors to attend EuroBSDCon.
+Our advocacy team was busy producing content that promotes the benefits and strengths of FreeBSD, why companies are using FreeBSD, and why you should use FreeBSD if you care about security.
+We also promoted work within the Project and Foundation on social media.
+
+During EuroBSDCon, Foundation and Core Team members met to discuss Core's questions as they navigate what they want to accomplish during their term.
+We identified 2 key areas to work on in the near term:
+
+. Financial reporting transparency - Break out operating system improvements spending in our quarterly reports.
+We are working with our accountant so that starting in 2025, we can report how much we are spending on certain projects and key areas, like laptop, enterprise, security...
+In the meantime, we will add notes to our financial reports that document which projects are included in the OS Improvement expense category.
+We are aware that we have not posted financials this year.
+Our accounting team is introducing us to improved reporting, while integrating our books into a new accounting system.
+
+. The projects we are funding are not mentioned on the Project's website.
+We document these on our website, because we want to show our donors where their financial contributions are being spent.
+We recognize that we need to also add documentation about these projects on FreeBSD.org, so we will investigate how to better connect our software development work with the Project.
+
+We are funding a lot of software development work to advance, improve, and keep FreeBSD secure.
+We received funding for some of this work, but most of it is being funded by your donations and our investments.
+Our purpose is to focus on the long-term sustainability of FreeBSD.
+To do this, we need more companies stepping in to help fund our efforts.
+Our investments will only carry on this work for a year or two at most.
+If your company relies on FreeBSD, please consider giving a financial contribution so we can ensure it stays the secure, reliable, and innovative platform you depend on.
+Not sure how to go about asking?
+Please mailto:deb@freebsdfoundation.org[reach out].
+We can help you navigate the process.
+
+Please go here to make a donation: link:https://freebsdfoundation.org/donate/[].
+To find out more about our Partnership Program, go here: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[].
+
+==== OS Improvements
+During the third quarter of 2024, 263 src, 37 ports, and 11 doc tree commits identified The FreeBSD Foundation as a sponsor.
+
+Several members of the FreeBSD Foundation's development team attended the link:https://wiki.freebsd.org/DevSummit/202409[FreeBSD Developer Summit] in Dublin, Ireland prior to link:https://2024.eurobsdcon.org/[EuroBSDCon 2024].
+You can watch a video of the link:https://www.youtube.com/watch?v=CDEb_0CSur4[Hello From the Foundation] talk to open the Summit, when:
+
+* Deb Goodkin introduced the FreeBSD Foundation
+* Joe Mingrone introduced members of the development team and said a few words about FreeBSD's 2024 Google Summer Code campaign
+* Ed Maste described some of the current or recently completed Foundation development projects.
+
+Alice Sowerby, who recently began supporting the Foundation in Technical Program Management role, gave link:https://www.youtube.com/watch?v=Xb1ptoPfawM[a talk to introduce the CHAOSS (Community Health Analytics for Open Source Software) project] and how to start collecting and working with community health metrics.
+
+The Foundation, along with new funding and investment partners, is currently supporting four major projects.
+
+* The first, partially funded by link:https://alpha-omega.dev/[Alpha-Omega], is to improve FreeBSD security.
+As part of this effort, the Foundation enlisted link:https://www.synacktiv.com/en[Synacktiv] to run a code audit on two significant subsystems: bhyve and Capsicum.
+For details, refer to the dedicated <<_capsicum_and_bhyve_code_audit,Capsicum and Bhyve Code Audit>> report entry.
+
+* The second project, jointly funded by AMD and the Foundation, is to develop an AMD IOMMU driver for FreeBSD.
+The impetus for the project was to better support large core AMD systems.
+However, the driver will be useful in different scenarios when interrupt remapping is required.
+The work is nearing completion, and developer Konstantin Belousov is testing the driver on some of AMD's large-core-count systems before committing.
+
+* The third project, backed by an investment from the link:https://www.sovereigntechfund.de[Sovereign Tech Fund], is to improve FreeBSD through five key sub-projects:
+** Zero Trust Builds: Enhance tooling and processes
+** CI/CD Automation: Streamline software delivery and operations
+** Reduce Technical Debt: Implement tools and processes to keep technical debt low
+** Security Controls: Modernize and extend security artifacts, including the FreeBSD Ports and Package Collection, to assist with regulatory compliance
+** SBOM Improvements: Enhance and implement new tooling and processes for FreeBSD SBOM
+
++
+To reduce technical debt, we have partnered with link:https://bitergia.com/[Bitergia] to analyze and assess our open Bugzilla bugs.
+By implementing improved issue management processes and establishing open-source tooling for the long term, our goal is to achieve and sustain a manageable bug backlog.
+The remaining four sub-projects will begin in 2025.
+
+* The fourth project, which will be funded by both the Foundation and Quantum Leap Research, is to link:https://freebsdfoundation.org/blog/why-laptop-support-why-now-freebsds-strategic-move-toward-broader-adoption/[improve FreeBSD laptop usability].
+  We have begun (or will soon start) supporting developers working in the following areas:
+
+** Enhanced wireless chipset support: Expanding chipset compatibility to ensure reliable wireless connectivity and support for newer wireless standards.
+** Power management: Implementing modern power-saving states (such as s2idle and s0ix) to improve battery life and energy efficiency.
+** Graphics enhancements: Improving support for Intel and AMD graphics by integrating the latest DRM drivers.
+** Audio improvements: Enhancing audio routing, headphone switching, and digital microphone (DMIC) functionality for a more user-friendly multimedia experience.
+** Laptop-specific hardware features: Addressing specialty buttons, touchpad gestures, and other unique hardware components found in modern laptops.
+
+link:https://www.freebsd.org/projects/summerofcode/[FreeBSD completed our 20th consecutive year participating in Google Summer of Code].
+The link:https://wiki.freebsd.org/SummerOfCode2024Projects[11 projects for this summer] are now complete; nine passed.
+
+The Foundation has been providing project management support for the FreeBSD Open Container Initiative (OCI) Working Group, with Alice Sowerby hosting the bi-weekly meeting, and running the recent link:https://github.com/oci-playground/freebsd-podman-testing/blob/main/README.md[Podman on FreeBSD testing project].
+The link:https://opencontainers.org/[OCI] develops open industry standards for cloud native container formats and runtimes, ensuring platform consistency.
+The FreeBSD OCI Working Group is defining these standards for FreeBSD, with implementations using jails and potentially lightweight VMs with bhyve.
+Refer to the Foundation's link:https://freebsdfoundation.org/project/oci-container-support/[OCI Container Support Project page] for details.
+
+In other Foundation news:
+
+* Isaac Freund joined the Foundation's development team as a Userland Developer.
+  As the lead developer of the River Wayland Compositor and a member of the Core Zig Team, we are excited about the experience Isaac will be bringing to FreeBSD.
+
+* Alfonso Sabato Siciliano is working on a Vision Accessibility Subsystem for blind, low-vision, and color blind users.
+  New features will include a Braille refreshable display framework, a communication channel for the virtual terminal console, a speech synthesizer, high-contrast TUI utilities, and an accessibility book to document assistive technologies available on FreeBSD.
+
+* Tom Jones, completed his work with RGNets to port the Vector Packet Processor (VPP), a layer 2-4 multi-platform network stack in userspace, to FreeBSD.
+  You can read about Tom's next project to support full-cone NAT for FreeBSD firewalls in his <<_endpoint_independent_nat,Endpoint-Independent NAT>> report entry.
+
+* Christos Margiolis continued to improve FreeBSD's audio stack and provide audio developers with useful tools and frameworks to facilitate sound development on FreeBSD.
+  Refer to the <<_audio_stack_improvements,Audio Stack Improvements>> entry for the latest news.
+
+* Olivier Certner has two entries in this report.
+  You can read about his latest work in the <<_scheduling_priorities_256_queue_runqueues_sub_project,Scheduling Priorities: 256-queue Runqueues Sub-Project>> and <<_mac_do4_setcred2_mdo1,mac_do(4), setcred(2), mdo(1)>> report entries.
+
+* Bjoern Zeeb continued to improve wireless networking on FreeBSD.
+  You can read the latest news in Bjoern's <<_wireless_update,Wireless Update>> entry.
+
+* Philip Paeps continued work on a contract to modernize the FreeBSD cluster.
+
+* Chih-Hsin Chang has continued work to port OpenStack components so that the cloud computing platform can be run on FreeBSD hosts.
+  Refer to the <<_openstack_on_freebsd,OpenStack on FreeBSD>> entry for the latest information.
+
+* Other members of the Foundation's technology team contributed to FreeBSD development efforts.  For example:
+** Mitchell Horne committed work for RISC-V, including adding support for the Supervisor-mode: Page-Based Memory Types (Svpbmt) extension
+** Ed Maste removed the deprecated mergemaster tool in favor of man:etcupdate[8] for updating files not managed by install world
+** Joe Mingrone updated our base libpcap and man:tcpdump[1]
+** Li-Wen Hsu kept our Jenkins port tracking the latest upstream versions with a number of port updates.
+
+==== Continuous Integration and Workflow Improvement
+As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project's continuous integration system and test infrastructure.
+
+==== Advocacy
+
+During the third quarter of 2024, we continued growing our efforts to drive awareness, advocate for the project, highlight users, and bring educational content to the FreeBSD community.
+Below are some of those efforts.
+
+* Presented at the EuroBSDcon 2024 FreeBSD Developer Summit.
+  Slides and the Live stream are https://wiki.freebsd.org/DevSummit/202409[now available].
+* Attended and exhibited at https://2024.eurobsdcon.org/[EuroBSDCon 2024].
+  The Foundation was again a Silver Sponsor.
+* Finalized our Bronze Sponsorship of the https://freebsdfoundation.org/news-and-events/event-calendar/openzfs-developer-summit-2024/[OpenZFS User and Developer Summit]
+* Began planning the https://freebsdfoundation.org/news-and-events/event-calendar/fall-2024-freebsd-summit/[Fall 2024 FreeBSD Summit] taking place November 7-8, 2024 in San Jose, CA.
+  The program is now available and registration is open.
+* Updated the community on the new release schedule: https://freebsdfoundation.org/blog/navigating-freebsds-new-quarterly-and-biennial-release-schedule/[Navigating FreeBSD's New Quarterly and Biennial Release Schedule]
+* Announced: https://freebsdfoundation.org/blog/new-cis-freebsd-14-benchmark-secure-your-systems-with-expert-guided-best-practices/[New CIS® FreeBSD 14 Benchmark: Secure Your Systems with Expert-Guided Best Practices]
+* Shared more information about the Sovereign Tech Fund's investment in the Foundation: https://freebsdfoundation.org/blog/sovereign-tech-fund-to-invest-e686400-in-freebsd-infrastructure-modernization/[Sovereign Tech Fund to Invest €686,400 in FreeBSD Infrastructure Modernization]
+* Announced the joint investment by https://freebsdfoundation.org/news-and-events/latest-news/quantum-leap-research-and-freebsd-foundation-to-invest-750000-to-improve-laptop-support-and-usability/[Quantum Leap Research and FreeBSD Foundation to Improve Laptop Support and Usability] and more on https://freebsdfoundation.org/blog/why-laptop-support-why-now-freebsds-strategic-move-toward-broader-adoption/[why we are making this investment].
+* Published additional blogs including:
+** https://freebsdfoundation.org/blog/freebsd-ports-and-packages-what-you-need-to-know/[FreeBSD Ports and Packages: What you need to know]
+** https://freebsdfoundation.org/blog/why-you-should-use-freebsd/[Why You Should Use FreeBSD]
+** https://freebsdfoundation.org/blog/enhancing-memory-safety-in-programming-insights-from-the-freebsd-vendor-summit/[Enhancing Memory Safety in Programming: Insights from the FreeBSD Vendor Summit]
+** https://freebsdfoundation.org/blog/freebsd-as-a-platform-for-your-future-technology/[FreeBSD as a Platform for Your Future Technology]
+** https://freebsdfoundation.org/blog/celebrating-freebsd-insights-from-deb-goodkin/[Celebrating FreeBSD: Insights from Deb Goodkin]
+* Participated in the following contributed articles, interviews and podcasts:
+** https://freebsdfoundation.org/news-and-events/latest-news/get-to-know-deb-goodkin-executive-director-freebsd-foundation/[Get to Know: Deb Goodkin, Executive Director, FreeBSD Foundation]
+** https://freebsdfoundation.org/news-and-events/latest-news/all-things-open-blog-unlocking-the-potential-of-freebsd/[All Things Open Blog: Unlocking the Potential of FreeBSD]
+** https://freebsdfoundation.org/news-and-events/latest-news/why-open-source-can-be-the-perfect-place-for-new-developers-and-how-to-get-started-with-deb-goodkin-from-the-freebsd-foundation/[Why Open Source Can Be the Perfect Place for New Developers – and How to Get Started, with Deb Goodkin from the FreeBSD Foundation]
+** https://freebsdfoundation.org/news-and-events/latest-news/steady-in-a-shifting-open-source-world-freebsds-enduring-stability/[Steady in a shifting Open Source world: FreeBSD's enduring stability]
+** https://freebsdfoundation.org/news-and-events/latest-news/apples-open-source-roots-the-bsd-heritage-behind-macos-and-ios/[Apple's Open Source Roots: The BSD Heritage Behind macOS and iOS]
+* Published the https://freebsdfoundation.org/news-and-events/newsletter/july-2024-foundation-update/[July 2024], https://freebsdfoundation.org/news-and-events/newsletter/august-2024-foundation-update/[August 2024], and https://freebsdfoundation.org/news-and-events/newsletter/september-newsletter/[September 2024] FreeBSD Foundation Updates.
+* Released the https://freebsdfoundation.org/our-work/journal/browser-based-edition/configuration-management-2/[May/June 2024] and https://freebsdfoundation.org/our-work/journal/browser-based-edition/storage-and-filesystems/[July/August 2024] issues of the FreeBSD Journal with HTML versions of the articles.
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2024-07-2024-09/fuse-ufs.adoc b/website/content/en/status/report-2024-07-2024-09/fuse-ufs.adoc
new file mode 100644
index 0000000000..38c40831a6
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/fuse-ufs.adoc
@@ -0,0 +1,27 @@
+=== Userspace UFS Driver (fuse-ufs)
+
+Links +
+link:https://github.com/realchonk/fuse-ufs[fuse-ufs GitHub] URL: link:https://github.com/realchonk/fuse-ufs[]
+
+Contact: Benjamin Stürz <benni@stuerz.xyz>
+
+During this year's Summer of Code, I wrote a userspace UFS driver using FUSE and Rust.
+The project was meant to ease the process of mounting FreeBSD UFS filesystems on other operating systems.
+Up to this point, only read-only filesystem access has been implemented.
+But as a bonus, fuse-ufs has the ability to mount filesystems with endianness different from the host's endianness.
+
+I am currently working on splitting the project into a binary and library part, to make it easier to integrate it into other operating systems.
+As part of this refactoring, an additional FUSE2 backend will be implemented, to be able to run it on OpenBSD.
+Currently there is testing infrastructure for Linux and FreeBSD with OpenBSD coming in the future.
+Although there is no CI for MacOS, a friend of mine tested it with MacFUSE and it works.
+
+Once the big refactor is done, I will start concentrating on implementing write support.
+Thanks to being bribed by mailto:fuz@FreeBSD.org[Robert Clausecker], I will also add soft-updates and mounting Sun's UFS in the future.
+
+The driver can be installed using `cargo install fuse-ufs`, or (if on Arch Linux) using your favorite AUR helper.
+Thanks to Robert Clausecker a port for FreeBSD exists in package:sysutils/fusefs-ufs[].
+
+A big thanks to mailto:asomers@FreeBSD.org[Alan Somers] and mailto:mckusick@FreeBSD.org[Kirk McKusick] for mentoring me and thanks to Robert Clausecker for the FreeBSD port and suggesting this GSoC project to me in the first place.
+Another thanks to Davids Paskevics for writing a fuzzer for me.
+
+Sponsor: Google Summer of Code 2024
diff --git a/website/content/en/status/report-2024-07-2024-09/gcc.adoc b/website/content/en/status/report-2024-07-2024-09/gcc.adoc
new file mode 100644
index 0000000000..6ecf2a4391
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/gcc.adoc
@@ -0,0 +1,23 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[] +
+link:https://gcc.gnu.org/gcc-14/[GCC 14 release series] URL: link:https://gcc.gnu.org/gcc-14/[] +
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+This quarter the main news is about the new GCC releases:
+
+* package:lang/gcc11[] has been updated to 11.5.0, which is the last GCC 11 planned released;
+* package:lang/gcc12[] has been updated to 12.4.0;
+* package:lang/gcc13[] has been updated to 13.3.0;
+* package:lang/gcc14[] has been updated to 14.2.0.
+
+The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281091[exp-run] to update GCC default version from 13 to 14 has started.
+As usual, thanks to everyone involved.
+
+If you maintain any of the affected ports or want to give a hand preparing and testing some patches, please consider trying adding `-fpermissive` to `CFLAGS` in affected ports: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds.
+The `-fpermissive` flag switches those errors back to warnings.
diff --git a/website/content/en/status/report-2024-07-2024-09/intro.adoc b/website/content/en/status/report-2024-07-2024-09/intro.adoc
new file mode 100644
index 0000000000..a9f531ad9d
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/intro.adoc
@@ -0,0 +1,9 @@
+Here is the third 2024 status report, with 32 entries.
+
+Unfortunately we are late this quarter, just like last quarter.
+As our readers know, many FreeBSD contributors are volunteers, so it is natural that less important deadlines like the status reports ones are not always met.
+Indeed, if you are not a FreeBSD contributor yet, link:https://docs.freebsd.org/en/articles/contributing/[please consider joining us]: you could help lighten someone's burden while learning new skills, working side by side with developers all over the world.
+
+Have a nice read.
+
+Lorenzo Salvadore, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2024-07-2024-09/kyua.adoc b/website/content/en/status/report-2024-07-2024-09/kyua.adoc
new file mode 100644
index 0000000000..42e3f42ee3
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/kyua.adoc
@@ -0,0 +1,40 @@
+=== Kyua Jail Support
+
+Contact: Igor Ostapenko <igoro@FreeBSD.org>
+
+The FreeBSD test suite is executed by the man:kyua[1] utility.
+Kyua supports parallel execution of tests with `kyua -v parallelism=<n> test`, however many network tests leverage man:jail[8] features like man:VNET[9] and have conflicts with jail naming and network configuration.
+As a result they are marked with the `is_exclusive=true` metadata property to prevent them from running at the same time and interfering with each other.
+It creates a dilemma when a project aims to increase test coverage, but the accumulation of exclusive tests proportionally increases the time required to run them.
+This, in turn, affects the development process from multiple angles.
+
+Kyua has recently got a change in 15-CURRENT to support a new concept called "execution environment".
+By default, tests run in the so-called "host" execution environment, where they are executed as before.
+A test can opt-in to use a brand new execution environment, the "jail" one.
+In this case, kyua creates a jail before running the test, and then executes the test within the jail.
+That opens up the opportunity to run more tests in parallel due to the extra isolation provided by the jail concept itself, and specifically by the VNET.
+It depends on hardware and configuration, but there are reports that having the same environment [.filename]#netpfil/pf# tests can be run around 4 times faster -- a few minutes instead of half an hour.
+
+The following Makefile change is a quick demo of how [.filename]#netpfil/pf# tests were switched to run in parallel with jail execution environment:
+
+  -# Tests reuse jail names and so cannot run in parallel.
+  -TEST_METADATA+=        is_exclusive=true
+  +# Allow tests to run in parallel in their own jails
+  +TEST_METADATA+= execenv="jail"
+  +TEST_METADATA+= execenv_jail_params="vnet allow.raw_sockets"
+
+More details:
+
+* The key commit with detailed description: link:https://cgit.freebsd.org/src/commit/?id=257e70f1d5ee61037c8c59b116538d3b6b1427a2[257e70f1d5ee61037c8c59b116538d3b6b1427a2]
+* The man pages covering the "execenv" feature: man:kyuafile[5], man:kyua.conf[5]
+
+This change also brings new sysctl read-only variables, which expose more details about current jail, and may be generally useful:
+
+* `security.jail.children.max: Maximum number of child jails`
+* `security.jail.children.cur: Current number of child jails`
+
+A hint: the `sysctl -n security.jail.children.cur` run from `prison0` provides the number of all jails in the system.
+
+Further improvements to Kyua, such as requirements definition and automatic resolution, are currently in the design phase.
+Potentially new metadata properties like `required_klds` and `required_pkgs` provide a clue to these topics.
+Please contact Igor to discuss ideas and use cases that can help shape these upcoming Kyua enhancements.
diff --git a/website/content/en/status/report-2024-07-2024-09/mac_do.adoc b/website/content/en/status/report-2024-07-2024-09/mac_do.adoc
new file mode 100644
index 0000000000..7fb834021b
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/mac_do.adoc
@@ -0,0 +1,40 @@
+=== mac_do(4), setcred(2), mdo(1)
+
+Contact: Olivier Certner <olce.freebsd.statusreports@certner.fr>
+Contact: Baptiste Daroussin <bapt@FreeBSD.org>
+
+This project aims at allowing controlled process credentials transitions without using setuid executables but instead leveraging our MAC framework.
+
+Traditional programs for credentials change have to execute preliminary operations as root (if not as the effective UID, at a minimum as the saved UID).
+Some of these programs (e.g., man:sudo[8]) have lots of lines of codes and comprise features (e.g., loadable security modules) that can be dangerous from a security standpoint.
+Thus, they have a non-negligible attack surface and are difficult to prove correct.
+Additionally, in most scenarios, the extra features they bring are not necessary.
+
+More generally, the threat model for the man:mac_do[4] kernel module part is that of compromised userland programs, be they credentials changers or credentials providers ones.
+This stance implies that calls to the kernel's credentials-changing API must be monitored by the kernel without upcalls to userland.
+In practice, man:mac_do[4] must be configured beforehand by the administrator to indicate which transitions of credentials are valid (through a man:sysctl[8] knob, `security.mac.do.rules`).
+
+Currently, the companion userland program, man:mdo[1], is the only one that can be authorized to proceed by man:mac_do[4] (for now, based on the executable path).
+This tiny program simply establishes the new credentials via calls to man:setuid[2], and optionally man:initgroups[3] (calling man:setgroups[2]) and man:setgid[2] (if `-i` was not passed).
+
+The resulting set of groups is either that of the target UID based on the password database, or that before the change in UID (when using `-i`).
+The second alternative can be a security hazard in some cases (as the effective GID is not changed either), whereas the first contradicts the threat model above.
+The current man:mac_do[4] rules specification indeed only allows to express simple UID transitions towards explicit UIDs from other explicit UIDs or GIDs, without taking into account groups.
+Consequently, the kernel module currently cannot check the content of man:setgroups[2] and man:setgid[2] system calls' parameters, relying completely on man:mdo[1] passing the right information.
+
+A new version of man:mac_do[4] has been in the works for approximately a month.
+Besides fixing concurrency, per-jail settings and MAC policies composition problems, it features a revamp of the rules specification in order to make it possible to finely control which groups are allowed in the resulting credentials.
+Notably, primary and secondary groups can now be specified independently, and for the latter, GIDs can be tagged as allowed, mandatory or forbidden.
+A special alias, `.`, can be used to indicate the current process' UIDs or GIDs depending on the context.
+
+These new features imply that the man:mac_do[4] module is able to apply credentials change at once, since the allowed final credentials depend on the initial ones through the configured rules.
+The traditional userland interface (e.g., man:setuid[2], man:setuid[2], man:setgroups[2], etc.) is at odds with this requirement as it necessitates multiple calls to reach the desired final credentials, making the process pass by several successive states that themselves may not be allowed by man:mac_do[4]'s rules.
+We overcome this limitation by introducing a new system call, man:setcred[2], which allows to request arbitrary transitions of credentials at once.
+Beside its usefulness in conjunction with man:mac_do[4], it has the benefit of simplifying coding of credentials change in userland.
+Since it is also extensible, it may have the potential to be adopted later by other systems.
+
+Pre-requisite changes are currently under review (see in particular revisions link:https://reviews.freebsd.org/D46886[D46886] to link:https://reviews.freebsd.org/D46889[D46889] and link:https://reviews.freebsd.org/D46896[D46896] to link:https://reviews.freebsd.org/D46923[D46923]).
+The bulk of changes in man:mac_do[4]/man:mdo[1] proper will soon be pushed under review as well.
+An older version of the full series can be seen on link:https://github.com/OlCe2/freebsd-src/tree/oc-mac_do[GitHub].
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-07-2024-09/openstack.adoc b/website/content/en/status/report-2024-07-2024-09/openstack.adoc
new file mode 100644
index 0000000000..a35cbb454c
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/openstack.adoc
@@ -0,0 +1,30 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[]
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+The OpenStack on FreeBSD project aims to bring OpenStack cloud infrastructure to the FreeBSD operating system, using FreeBSD's special features while keeping it compatible with OpenStack.
+
+In the third quarter of 2024, we continued working on several important tasks.
+Our work on porting OpenStack Ironic is still ongoing, with tests now running on arm64 servers.
+In this setup, the service node is amd64, and the provisioning node is arm64.
+This helps us explore more options for running mixed environments in OpenStack on FreeBSD.
+
+In August, we gave link:https://coscup.org/2024/en/session/CKQC9P[a presentation at COSCUP 2024] to share the project's progress and our experiences.
+This helped us get more attention and interest from people in the community.
+
+We also updated some of the OpenStack components, like Keystone, Glance, and Placement, from FreeBSD 14.0-STABLE to FreeBSD 15.0-CURRENT.
+This update helps us keep up with the latest changes in FreeBSD, making the project run better.
+
+Another notable item was testing the link:https://cgit.FreeBSD.org/src/commit/?id=1f903953fbf8615bb611db059417177f6cee07bd[bhyve serial console over TCP patch] and using it in the OpenStack workflow.
+This brings us closer to stopping the use of the custom socat-manager solution and moving to a built-in serial console solution.
+
+Although we are still planning to turn the OpenStack manual installation process into FreeBSD ports, there has not been much progress yet.
+We hope to work more on this in the next few months.
+Existing work can be found in the link:https://github.com/openstack-on-freebsd/openstack[openstack repository].
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-07-2024-09/pinephone.adoc b/website/content/en/status/report-2024-07-2024-09/pinephone.adoc
new file mode 100644
index 0000000000..31b82dad25
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/pinephone.adoc
@@ -0,0 +1,23 @@
+=== Pinephone Pro Support
+
+Links: +
+link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[Repository on Codeberg] URL: link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[]
+
+Contact: Toby Kurien <toby@tobykurien.com>
+
+A new project trying to make FreeBSD usable on the Pinephone Pro has been started during August.
+
+The current FreeBSD RELEASE images already boot on a Pinephone Pro, but no screen output or other devices are supported.
+The aim is to step by step support additional components so that the device one day might be usable as a highly mobile FreeBSD device.
+
+Over the last few weeks, the groundwork has been implemented like getting used to the device, cross-compiling and booting a 15.0-CURRENT custom kernel as well as toggling the LEDs (red/green/blue in the front).
+Also, the LCD backlight can be turned on already and the USB-C hub is enabled even though it is not yet functional due to missing power management support.
+
+The next step is to write a driver for the RK818 power management chip.
+Without it, most of the hardware will not power on like the USB-C port above.
+This will be done by trying to modify the existing RK808 driver.
+RK818 support should then make it possible to access a lot more of the devices, e.g. allowing to enable the screen, USB peripherals or WiFi.
+
+Additional feedback and testers are welcome.
+
+Sponsor: Honeyguide Group
diff --git a/website/content/en/status/report-2024-07-2024-09/portmgr.adoc b/website/content/en/status/report-2024-07-2024-09/portmgr.adoc
new file mode 100644
index 0000000000..720226fe0e
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/portmgr.adoc
@@ -0,0 +1,49 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: Tobias C. Berner <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+According to INDEX, there are currently 36,504 ports in the Ports Collection.
+There are currently ~3,379 open ports PRs.
+The last quarter saw 11,594 commits by 154 committers on the main branch and 832 commits by 78 committers on the 2024Q3 branch.
+Compared to last quarter, this means a slight increase in the number of commits on the main branch (from 10,525) and about half of the backports to the quarterly branch (compared to 1,771).
+The number of ports also increased (up from 32,471).
+
+The most active committers to main were:
+
+- 5133 sunpoet@FreeBSD.org
+- 1262 yuri@FreeBSD.org
+-  375 jbeich@FreeBSD.org
+-  357 vvd@FreeBSD.org
+-  331 bofh@FreeBSD.org
+- 192 uzsolt@FreeBSD.org
+- 185 eduardo@FreeBSD.org
+- 172 diizzy@FreeBSD.org
+- 148 mfechner@FreeBSD.org
+- 131 arrowd@FreeBSD.org
+
+A lot has happened in the ports tree in the last three quarter, an excerpt of the major software upgrades are:
+
+- Default version of PostgreSQL switched to 16
+- chromium      updated from  126.0.6478.126 to 129.0.6668.100
+- firefox       updated from         127.0.2 to 131.0-rc1
+- firefox-esr   updated from         115.9.1 to 128.3.0-rc1
+- rust          updated from          1.79.0 to 1.81.0
+- sdl2          updated from          2.30.3 to 2.30.7
+- wlroots       updated from          0.17.4 to 0.18.1
+- wine-devel    updated from             9.4 to 9.16
+- qt5           updated from         5.15.14 to 5.15.15
+- qt6           updated from           6.7.2 to 6.7.3
+- plasma6       updated from           6.1.1 to 6.1.2
+
+During the last quarter, pkgmgr@ ran 24 exp-runs to test various ports
+upgrades, updates to default versions of ports, and base system changes.
diff --git a/website/content/en/status/report-2024-07-2024-09/pot.adoc b/website/content/en/status/report-2024-07-2024-09/pot.adoc
new file mode 100644
index 0000000000..220704d40e
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/pot.adoc
@@ -0,0 +1,24 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+Potluck aims to be to FreeBSD and Pot (and potentially one day also Podman) what Dockerhub is to Linux and Docker: a repository of container descriptions and complete container images for usage with Pot and in many cases Nomad.
+
+During this quarter, there were two bugfixes to link:https://github.com/bsdpot/pot[Pot] that will be released soon.
+
+Potluck images saw some updates again.
+All images have been rebuilt again to include the latest fixes and quarterly packages.
+Additionally, some images like link:https://github.com/bsdpot/potluck/tree/master/loki[Loki] or link:https://github.com/bsdpot/potluck/tree/master/vault[Vault] have also received additional updates and bugfixes.
+
+Also, we have done some research regarding potential future support of OCI, Buildah and Podman images in Potluck.
+Two blog posts, one describing link:https://honeyguide.eu/posts/build-own-containers-buildah-podman-freebsd/[a basic Buildah and Podman setup] and one describing link:https://honeyguide.eu/posts/micropod-blog-post/[how to orchestrate Podman containers with Nomad and Consul] have been published.
+
+As always, feedback and patches are welcome.
+
+Sponsors: Nikulipe UAB, Honeyguide Group
diff --git a/website/content/en/status/report-2024-07-2024-09/releng.adoc b/website/content/en/status/report-2024-07-2024-09/releng.adoc
new file mode 100644
index 0000000000..6426d7407c
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/releng.adoc
@@ -0,0 +1,16 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.4R/announce/[FreeBSD 13.4-RELEASE announcement] URL: link:https://www.freebsd.org/releases/13.4R/announce/[] +
+link:https://www.freebsd.org/releases/14.2R/schedule/[FreeBSD 14.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.2R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+The Team managed 13.4-RELEASE, leading to the final RELEASE build and announcement in September.
+Planning has started for the upcoming 14.2-RELEASE cycle.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/14*, and *stable/13* branches.
diff --git a/website/content/en/status/report-2024-07-2024-09/samba.adoc b/website/content/en/status/report-2024-07-2024-09/samba.adoc
new file mode 100644
index 0000000000..4eb3fe8ca0
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/samba.adoc
@@ -0,0 +1,40 @@
+=== FreeBSD Samba Team
+
+Links: +
+link:https://wiki.freebsd.org/Samba[FreeBSD Samba Team Wiki] URL: link:https://wiki.freebsd.org/Samba[] +
+link:https://www.samba.org/[Samba Homepage] URL: https://www.samba.org/[] +
+
+Contact: FreeBSD Samba Team <samba@FreeBSD.org>
+
+Samba provides secure, stable and fast file and print services for all clients using the SMB/CIFS protocol.
+It is an important component to seamlessly integrate FreeBSD/Linux/Unix Servers and Desktops into Active Directory environments.
+It can function both as a domain controller or as a regular domain member.
+
+The new FreeBSD Samba Team was created to better coordinate maintenance efforts of the Samba ports and its dependencies, in particular:
+
+* package:databases/ldb22[]
+* package:databases/ldb25[]
+* package:databases/ldb28[]
+* package:databases/tdb[]
+* package:devel/talloc[]
+* package:devel/tevent[]
+* package:net/samba416[]
+* package:net/samba419[]
+
+Notable changes in the last quarter include:
+
+* Creation of the FreeBSD Samba Team by mailto:timur@FreeBSD.org[Timur Bakeyev], mailto:kiwi@oav.net[Xavier Beaudouin], mailto:yasu@freebsd.org[Yasuhiro Kimura], mailto:0mp@FreeBSD.org[Mateusz Piotrowski], and mailto:mikael@FreeBSD.org[Mikaël Urankar].
+* Added `SAMBA_LDB_PORT` to [.filename]#Mk/Uses/samba.mk# (sponsored by Klara, Inc.)
+* Switching package:net/samba419[] to use external dependencies by default instead of vendoring (sponsored by Klara, Inc.)
+* Updating package:net/samba419[] to 4.19.8
+
+Currently, the FreeBSD Samba team is coordinating efforts in the following areas:
+
+* Switching the default version of Samba from 4.16 to 4.19 (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280769[Bugzilla PR#280769]).
+  * Current blockers are:
+    * Broken `fruit:posix_rename = yes` (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281360[Bugzilla PR#281360])
+    * Broken replication in Samba 4.19.8_1 (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281672[Bugzilla PR#281672])
+* Adding Samba 4.20 to the ports tree (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280533[Bugzilla PR#280533])
+* Adding Samba 4.21 to the ports tree (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281262[Bugzilla PR#281262])
+
+Testing and community contributions are welcome, please reach out on Bugzilla or via the team email.
diff --git a/website/content/en/status/report-2024-07-2024-09/sched_prio-256_queue_runqueue.adoc b/website/content/en/status/report-2024-07-2024-09/sched_prio-256_queue_runqueue.adoc
new file mode 100644
index 0000000000..3e39a9163b
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/sched_prio-256_queue_runqueue.adoc
@@ -0,0 +1,25 @@
+=== Scheduling Priorities: 256-queue Runqueues Sub-Project
+
+Contact: Olivier Certner <olce.freebsd.statusreports@certner.fr>
+
+The goal of the 256-queue runqueues sub-project is to fix FreeBSD's POSIX compliance in that different priority levels in the `SCHED_FIFO` or `SCHED_RR` scheduling classes must lead to immediate preemption by threads having higher priority.
+It is part of the bigger scheduling priorities revamp project aiming at rationalizing FreeBSD scheduling interfaces, including having consistent man:rtprio[2] and POSIX interface behaviors (where it makes sense), enhancing POSIX compliance, removing duplicate code and fixing existing bugs, and enhancing the non-standard parts both for better control and security.
+Expected benefits are increased usage of FreeBSD as a soft real-time platform, e.g., for video and audio processing in casual desktop uses to professional settings.
+Readers interested in this topic are invited to consult link:https://papers.freebsd.org/2024/asiabsdcon/certner-Scheduling_priorities_in_FreeBSD.files/AsiaBSDCon2024-Certner-Scheduling_priorities_in_FreeBSD-Article.pdf[AsiaBSDCon 2024's paper] and link:https://papers.freebsd.org/2024/eurobsdcon/certner-Scheduling_Priorities_and_FreeBSD.files/EuroBSDCon2024-Certner-Scheduling_Priorities_and_FreeBSD.pdf[EuroBSDCon 2024's slides] for a wider view, and to contact me for questions, feedbacks or discussions.
+
+Currently, priority levels specified either through the `prio` field of `struct rtprio` (man:rtprio[2] interface) or the `sched_priority` one of `struct sched_param`, for real-time scheduling classes (`RTP_PRIO_FIFO` and `RTP_PRIO_REALTIME` for the former, `SCHED_FIFO` and `SCHED_RR` for the latter) as well as idle-time ones (`RTP_PRIO_IDLE`), are conflated as follows: Each priority level that has the same quotient when divided by 4 is internally treated the same.
+In particular, threads being in the same such equivalence class but having higher priority will not preempt other threads in the same class, violating POSIX expectations for `SCHED_FIFO` and `SCHED_RR`.
+
+To remedy this situation, we have chosen an impacting internal change on the number of queues per runqueue, and defer to the above-mentioned EuroBSDCon 2024's slides for more details.
+
+The switch to 256-queue runqueues having non-trivial impacts on the ULE scheduler, we have been analyzing it and tuning the scheduler to preserve its previous behavior with respect to anti-starvation and the effect of nice values.
+With the goal to perform further testing, we have revived Jeff Roberson's initial ULE's test tool, called `late` (currently available on link:https://github.com/OlCe2/late[GitHub]).
+
+All the modifications made as part of this sub-project are currently under review, starting with Phabricator's link:https://reviews.freebsd.org/D45387[review D45387] (click on the "Stack" tab to see the full series of reviews).
+
+In the course of this project, we have noticed that the effect of nice values is especially weak, and consequently have produced experimental patches to make their effect stronger.
+However, it is not clear at this point whether we can increase their effect satisfactorily enough in the current ULE setting.
+
+We have also started another scheduler project about adapting ULE to hybrid architectures, which might also trigger more drastic scheduler changes.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-07-2024-09/service-jails.adoc b/website/content/en/status/report-2024-07-2024-09/service-jails.adoc
new file mode 100644
index 0000000000..ef1f6dbe85
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/service-jails.adoc
@@ -0,0 +1,19 @@
+=== Service jails -- Automatic jailing of rc.d services

+

+Links: +

+link:https://docs.freebsd.org/en/articles/rc-scripting/#rcng-service-jails[rc-article part for Service Jails] URL: link:https://docs.freebsd.org/en/articles/rc-scripting/#rcng-service-jails[] +

+link:https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=service+jail+aware[service jail patches for ports in our bugtracker] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=service+jail+aware[]

+

+Contact: Alexander Leidinger <netchild@FreeBSD.org>

+

+Service jails extend the man:rc[8] system to allow automatic jailing of rc.d services.

+A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, ...) by default.

+Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (man:vmm[4]).

+

+Since the last report several ports have been modified to come with a service jail config.

+Out of about 1460 start scripts in the ports collection, about 80 start scripts are changed.

+Prominent examples out of those are postgresql, DNS servers, FTP servers, PHP, dovecot, postfix, rspamd, amavisd-new and clamav.

+Some more changes are waiting for a treatment by the corresponding port maintainers.

+

+Any help in changing more start scripts (most of the time just one line to add) is welcome.

+If you want to help, you can check the bugtracker link above for changes which are already under review.

diff --git a/website/content/en/status/report-2024-07-2024-09/simd.adoc b/website/content/en/status/report-2024-07-2024-09/simd.adoc
new file mode 100644
index 0000000000..52143067c9
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/simd.adoc
@@ -0,0 +1,19 @@
+=== SIMD enhancements for aarch64
+
+Links: +
+link:https://www.youtube.com/live/OzX38cWdivc?si=VsMrEmT_IdKpjv7W&t=22070[EuroBSDCon 2024 presentation] URL: link:https://www.youtube.com/live/OzX38cWdivc?si=VsMrEmT_IdKpjv7W&t=22070[] +
+link:http://fuz.su/~fuz/talks/eurobsdcon-str-talk.pdf[Slides from presentation (PDF)] URL: link:http://fuz.su/~fuz/talks/eurobsdcon-str-talk.pdf[] +
+link:https://summerofcode.withgoogle.com/programs/2024/projects/TKRS35FA[Google Summer of Code (GSoC) project description] URL: link:https://summerofcode.withgoogle.com/programs/2024/projects/TKRS35FA[] +
+link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[simd(7)] URL: link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[] +
+
+Contact: Getz Mikalsen <getz@FreeBSD.org>
+
+The porting effort of the SIMD enhanced libc string functions from amd64 to aarch64 has been successfully completed.
+There are now optimized implementations for 16 libc string functions in addition to those with implementations already available as part of the ARM optimized subroutines library.
+There is also a presentation regarding the general method for these methods from EuroBSDCon 2024 available on YouTube with a short description in the end of how the porting has been done with regards to the aarch64 architecture.
+
+These enhancements significantly improve performance of string functions for all FreeBSD systems on the aarch64 platform.
+
+The code is currently undergoing acceptance testing in the form of an exp-run building all the ports, once without and once with the patch set applied to see if it has caused any new failures.
+
+Sponsor: Google LLC (GSoC 2024)
diff --git a/website/content/en/status/report-2024-07-2024-09/sourcecompat.adoc b/website/content/en/status/report-2024-07-2024-09/sourcecompat.adoc
new file mode 100644
index 0000000000..157cac54e0
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/sourcecompat.adoc
@@ -0,0 +1,27 @@
+=== Linux Source Compatibility Wiki page
+
+Links: +
+link:https://wiki.freebsd.org/LinuxSourceCompatibility[Linux Source Compatibility] URL: link:https://wiki.freebsd.org/LinuxSourceCompatibility[]
+
+Contact: Edward Tomasz Napierala <trasz@freebsd.org>
+
+There is now a wiki page to track source compatibility differences between FreeBSD and Linux -- and it needs your input!
+
+FreeBSD and Linux are already largely compatible at the source code level due to both being Unix systems and following the same standards.
+There are however certain system calls specific to Linux; there are also differences in header files, constants and so on.
+Implementing them in FreeBSD would make porting software easier.
+
+Not all of the items there are fixable.
+Some differences cannot be eliminated due to naming clashes, disagreements on how the system is supposed to work, or because it would make autoconf pick up a less functional compatibility API instead of the native one.
+In such cases we should document it and advise what API to use instead.
+
+The wiki page aims to provide an overview and help track progress.
+That is where your help is needed.
+I need people who actually port software to FreeBSD to add missing APIs, based on their experiences.
+This also includes non-syscall items, like missing headers and unsupported constants.
+Preferably also mention the name of the software that could use them.
+
+ * Add missing items
+ * Add prospective API consumers
+
+Sponsor: Innovate UK
diff --git a/website/content/en/status/report-2024-07-2024-09/uvc.adoc b/website/content/en/status/report-2024-07-2024-09/uvc.adoc
new file mode 100644
index 0000000000..58edec0b56
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/uvc.adoc
@@ -0,0 +1,30 @@
+=== FreeBSD V4L2 & kernel USB Video Class driver
+
+Links: +
+link:https://github.com/AlvinChen1028/freebsd-src/tree/feature-uvc[Public development repository] URL: link:https://github.com/AlvinChen1028/freebsd-src/tree/feature-uvc[] +
+link:https://github.com/lwhsu/freebsd-src/pull/2[Upstreaming preparation repository] URL: link:https://github.com/lwhsu/freebsd-src/pull/2[] +
+
+Contact: Alvin Chen <weike_chen@dell.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+This work is to create FreeBSD UVC (USB Video Class) kernel driver and follow v4l2 APIs, so that most of the Linux camera applications can be easily ported to FreeBSD.
+
+The code is still cleaning up and will be submitted to official review after completing.
+
+Current Status:
+
+1. The key functions of the UVC driver are enabled.
+2. The key v4l2 IOCTLs are implemented.
+3. Support most of USB cameras (up to 4K resolution): Jabra, Logitech, etc.
+4. Some applications validated: VLC, Cheese, pwcview.
+
+Future Work:
+
+1. A couple of v4l2 IOCTLs need be implemented: make all cases in v4l2-compliance test suite be passed.
+2. Some UVC APIs need be implemented: uvc control mapping callbacks, etc.
+3. UVC lock issue related to USB.
+4. PCI based AI camera supporting.
+5. Code refactoring if needed.
+
+Sponsor: Dell Technologies for the development +
+Sponsor: The FreeBSD Foundation for assistance of upstreaming
diff --git a/website/content/en/status/report-2024-07-2024-09/vsock.adoc b/website/content/en/status/report-2024-07-2024-09/vsock.adoc
new file mode 100644
index 0000000000..a67ed7d8dd
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/vsock.adoc
@@ -0,0 +1,25 @@
+=== VirtIO Sockets and AF_VSOCK support
+
+Links: +
+link:https://github.com/daniloegea/freebsd-src/tree/virtio_vsocks[Source code] URL: link:https://github.com/daniloegea/freebsd-src/tree/virtio_vsocks[]
+
+Contact: Danilo Egea Gondolfo <danilo@FreeBSD.org>
+
+The VirtIO Socket device is used to enable communication between guests and host without networking.
+The AF_VSOCK protocol family enables it to be used through the sockets API.
+
+For the past many months I have been working on a guest driver for the link:https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.html#x1-43600010[VirtIO Socket] device and an implementation of the AF_VSOCK protocol family.
+Originally, I wanted to get the link:https://github.com/canonical/lxd/[lxd-agent] daemon link:https://github.com/canonical/lxd/issues/11603[working on FreeBSD] but the communication with the LXD host daemon is done through VSOCKs.
+LXD is a nice container and virtual machine manager based on Linux/KVM and my end goal is to make FreeBSD a LXD first-class citizen.
+
+At the moment I have it working well enough to enable the lxd-agent to work.
+I adapted the `golang.org/x/sys` library and the lxd-agent to support AF_VSOCK on FreeBSD.
+Features such as command execution, interactive consoles and file transfer are working.
+
+On Linux, AF_VSOCK can be used with VirtIO, HyperV and VMware sockets as transports.
+I am trying to design my implementation so it will also be possible to use it with different transports in the future.
+
+After getting the current work in a good shape, ideas for future work include integration of AF_VSOCK and HyperV Sockets (which is already supported on FreeBSD through AF_HYPERV), VIRTIO_VSOCK_F_SEQPACKET, VirtIO Socket device for bhyve and the host side of the driver.
+
+I will continue to slowly work on this on my limited free time and hopefully have something more concrete for the next time.
+There is still a lot of work to be done until it become ready for code review.
diff --git a/website/content/en/status/report-2024-07-2024-09/wiki.adoc b/website/content/en/status/report-2024-07-2024-09/wiki.adoc
new file mode 100644
index 0000000000..49d615d1ab
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/wiki.adoc
@@ -0,0 +1,45 @@
+=== FreeBSD Wiki
+
+Links: +
+link:https://wiki.freebsd.org/FrontPage[FreeBSD wiki front page] URL: link:https://wiki.freebsd.org/FrontPage[]
+
+Contact: Mark Linimon <linimon@freebsd.org>
+Contact: Wiki admin <wiki-admin@freebsd.org>
+
+The FreeBSD wiki is a repository of information that does not fit well in the link:https://docs.freebsd.org/en/[official project documentation] because it is too specific, too disparate, or too transient.
+
+==== Current projects:
+
+Mark Linimon has started attacking various stale pages.
+The focus has been on pages that we show to new, interested, users.
+(Recent Foundation newsletters refer to some of these pages directly.)
+Unfortunately, many of these pages have become stale, to the point where they were actually not good recommendations.
+
+The pages that have received the most work are:
+
+* link:https://wiki.freebsd.org/IdeasPage[IdeasPage] (referenced in Foundation documentation)
+* link:https://wiki.freebsd.org/JuniorJobs[JuniorJobs] (referenced in Foundation documentation)
+* link:https://wiki.freebsd.org/SummerOfCodeIdeas[SummerOfCodeIdeas]
+* various pages under link:https://wiki.freebsd.org/CategoryProject[CategoryProject]
+* various pages under link:https://wiki.freebsd.org/CategoryTodo[CategoryTodo]
+* link:https://wiki.freebsd.org/MentorMatch[MentorMatch]
+
+In addition to removing obviously stale entries, all entries have now been datestamped with the time that they were added to the various pages.
+link:mailto:wiki-admin@freebsd.org[wiki-admin@] would like to request that we carry forward this tradition into the future.
+
+As well, link:mailto:wiki-admin@freebsd.org[wiki-admin@] has been sending email to ask committers/contributors to the above pages "should we keep this entry?"
+This task will continue until the pages have been cleaned up.
+
+(NB: the fact that content in the wiki was stale was mentioned by numerous respondents in the FreeBSD Foundation 2024 Community Survey Report.)
+
+==== Previous plans that have stalled
+
+Plans are still underway to familiarize our audience on Discord with the wiki (there are too many "silos" in our FreeBSD community).
+The team has simply not had enough cycles to do this.
+However, contact Setesh on the FreeBSD Discord for more information.
+
+Preliminary work was being done on updating the wiki software itself.
+Earlier, we were looking at switching implementations because MoinMoin development seemed to have stalled, leaving us with an unwanted hanging python2 dependency.
+However, MoinMoin now claims that they are nearing a 2.0 release.
+We have not yet tried an install of their latest beta version to test compatibility.
+Testers welcome.
diff --git a/website/content/en/status/report-2024-07-2024-09/wireless.adoc b/website/content/en/status/report-2024-07-2024-09/wireless.adoc
new file mode 100644
index 0000000000..220b14c728
--- /dev/null
+++ b/website/content/en/status/report-2024-07-2024-09/wireless.adoc
@@ -0,0 +1,26 @@
+=== Wireless Update
+
+Links: +
+link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[Categorised Wireless Problem Reports] URL: link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org> +
+Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>
+
+The ongoing wireless efforts are trying to bring more support for recent chipsets as well as newer standards.
+
+With man:iwlwifi[4] and man:rtw88[4] being supported we received patches and initial reports for rtw89 and ath10k working for some people.
+Additionally ath11k, ath12k and various chipsets supported by mt76 are waiting for someone to find the time to finish compat code, test and debug.
+
+Work is ongoing to update drivers to Linux v6.11 using the now bootstrapped vendor branches, which should help maintenance a lot in the future.
+One particular focus for this update is also to find ways to minimize incompatibilities between wireless compat code versions in order to support multiple Linux versions as needed.
+
+After the native kern_malloc changes got committed, LinuxKPI is seeing ongoing work for memory allocation to play better by the rules set out in Linux which should help with DMA problems seen.
+There is further work pending to add missing bus_dmamap_sync() calls.
+
+There is work to support man:rtw88[4] SDIO devices (being tested on an r2s-plus) and ongoing work to stabilize updated USB support which should start landing once the driver updates have finished.
+Lastly there are more updates in the queue to finish 11n support for LinuxKPI 802.11 compat code as well as improving native net80211 code.
+
+If you have questions or feedback please use the link:https://lists.freebsd.org/subscription/freebsd-wireless[freebsd-wireless mailing list].
+That way everyone will see, be able to join in, and the answers will be publicly archived.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/_index.adoc b/website/content/en/status/report-2024-10-2024-12/_index.adoc
new file mode 100644
index 0000000000..e1029c14a5
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/_index.adoc
@@ -0,0 +1,262 @@
+---
+title: "FreeBSD Status Report Fourth Quarter 2024"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2024-10-2024-12
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+'''
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+include::{reports-path}/bugmeister.adoc[]
+
+'''
+
+include::{reports-path}/srcmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects.
+
+'''
+
+include::{reports-path}/foundation-infrastructure-modernization.adoc[]
+
+'''
+
+include::{reports-path}/foundation-laptop.adoc[]
+
+'''
+
+include::{reports-path}/foundation-security.adoc[]
+
+'''
+
+include::{reports-path}/foundation-security-audit.adoc[]
+
+'''
+
+include::{reports-path}/framework.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+'''
+
+include::{reports-path}/pkg-pkgbase.adoc[]
+
+'''
+
+include::{reports-path}/installer.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+'''
+
+include::{reports-path}/audio.adoc[]
+
+'''
+
+include::{reports-path}/mac_do.adoc[]
+
+'''
+
+include::{reports-path}/suspend.adoc[]
+
+'''
+
+include::{reports-path}/umb.adoc[]
+
+'''
+
+include::{reports-path}/lkpi-wireless.adoc[]
+
+'''
+
+include::{reports-path}/wireless-iwx.adoc[]
+
+'''
+
+include::{reports-path}/syzkaller.adoc[]
+
+'''
+
+include::{reports-path}/uvc.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+'''
+
+include::{reports-path}/pinephone.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+'''
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/openstack.adoc[]
+
+'''
+
+include::{reports-path}/buildpacks.adoc[]
+
+'''
+
+include::{reports-path}/ec2.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+'''
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+'''
+
+include::{reports-path}/ports-collection-accessibility-colors.adoc[]
+
+'''
+
+include::{reports-path}/appjail.adoc[]
+
+'''
+
+include::{reports-path}/common-lisp.adoc[]
+
+'''
+
+include::{reports-path}/erlang.adoc[]
+
+'''
+
+include::{reports-path}/openjdk.adoc[]
+
+'''
+
+include::{reports-path}/xfce.adoc[]
+
+'''
+
+include::{reports-path}/lxqt.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/torbrowser.adoc[]
+
+'''
+
+include::{reports-path}/gvm.adoc[]
+
+'''
+
+include::{reports-path}/wazuh.adoc[]
+
+'''
+
+include::{reports-path}/bhyvemgr.adoc[]
+
+'''
+
+include::{reports-path}/qemu_l4b.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+'''
+
+include::{reports-path}/ldwg.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2024-10-2024-12/appjail.adoc b/website/content/en/status/report-2024-10-2024-12/appjail.adoc
new file mode 100644
index 0000000000..ebac7efb90
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/appjail.adoc
@@ -0,0 +1,32 @@
+=== Containers and FreeBSD: AppJail, Director, OCI and more
+
+Links: +
+link:https://github.com/DtxdF/AppJail[AppJail on GitHub] URL: link:https://github.com/DtxdF/AppJail[] +
+link:https://github.com/DtxdF/Director[Director on GitHub] URL: link:https://github.com/DtxdF/Director[] +
+link:https://github.com/DtxdF/LittleJet[LittleJet on GitHub] URL: link:https://github.com/DtxdF/LittleJet[] +
+link:https://github.com/DtxdF/reproduce[Reproduce on GitHub] URL: link:https://github.com/DtxdF/reproduce[]
+
+Contact: Jesús Daniel Colmenares Oviedo <DtxdF@disroot.org>
+
+AppJail is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application.
+
+Director is a tool for running multi-jail environments on AppJail using a simple YAML specification.
+A Director file is used to define how one or more jails that make up your application are configured.
+Once you have a Director file, you can create and start your application with a single command: `appjail-director up`.
+
+LittleJet is an open source, easy-to-use orchestrator for managing, deploying, scaling and interconnecting FreeBSD jails anywhere in the world.
+
+Their goals are to simplify life for sysadmins and developers by providing a unified interface that automates the jail workflow by combining the base FreeBSD tools.
+
+AppJail and all its meta-projects extensively follow link:https://man.freebsd.org/cgi/man.cgi?query=appjail-ephemeral&apropos=0&sektion=0&manpath=FreeBSD+14.2-RELEASE+and+Ports&arch=default&format=html[The Ephemeral Concept] which helps update/upgrade jails more easily as they become disposable.
+I have used this extensively to deploy my jails with services since this concept was implemented in AppJail.
+
+Although there have been great people working on OCI for a long time, this month the featured topic is OCI, and the advances related to this technology in FreeBSD make it possible to implement it in AppJail.
+The latest release adds more useful features, improves on existing things and link:https://appjail.readthedocs.io/en/latest/OCI[implements OCI].
+
+I'm continually adding more Makejails, a simple text file that automates the deployment of services in jails.
+There is an organization on GitHub that I call link:https://github.com/AppJail-makejails[The Centralized Repository] if you want to make a contribution.
+link:https://github.com/AppJail-makejails/#status[The last improvement was to implement BuildBot as the CI/CD of AppJail images], so any change made to a repository that is tracked by BuildBot will generate a new task to build and deploy an image to the mirrors.
+And if mirrors are not an option, link:https://github.com/DtxdF/reproduce[appjail-reproduce] can be used to build images using your own resources.
+
+Sponsor: https://www.patreon.com/appjail
diff --git a/website/content/en/status/report-2024-10-2024-12/audio.adoc b/website/content/en/status/report-2024-10-2024-12/audio.adoc
new file mode 100644
index 0000000000..3df1584e41
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/audio.adoc
@@ -0,0 +1,29 @@
+=== Audio Stack Improvements
+
+Contact: Christos Margiolis <christos@FreeBSD.org>
+
+The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement -- from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs.
+This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature.
+
+Important work since link:https://www.freebsd.org/status/report-2024-07-2024-09/#_audio_stack_improvements[last report]:
+
+* man:sound[4] and driver bug fixes, including panics and races.
+  Several cleanup and refactor patches.
+* Committed man:mididump[1].
+  Ships with 14.2-RELEASE and 14-STABLE.
+* Implementing link:https://reviews.freebsd.org/D47638[AFMT_FLOAT] support.
+  This fixes ports, such as package:emulators/wine[], that require `AFMT_FLOAT` support from OSS.
+  Related bug reports: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184380[PR 184380], link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281390[PR 281390], link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264973[PR 264973], link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157050[PR 157050].
+
+Future work includes:
+
+* More bug fixes, optimizations and general improvements.
+* Implement a generic MIDI layer, similar to pcm/, and improve/modernize the MIDI codebase in general.
+* Implement a bluetooth device management utility.
+* virtual_oss patches and improvements.
+* Attempt to automate man:snd_hda[4] pin-patching.
+* Investigate SOF/DMIC support.
+
+You can also follow the development process in link:https://lists.freebsd.org/subscription/freebsd-multimedia[freebsd-multimedia@], where I post regular reports.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/azure.adoc b/website/content/en/status/report-2024-10-2024-12/azure.adoc
new file mode 100644
index 0000000000..f550b50fdd
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/azure.adoc
@@ -0,0 +1,40 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.freebsd.org/subscription/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org>, <weh@microsoft.com> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Colin Su <yuas@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+In this quarter, we have published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-14_2[14.2-RELEASE on Azure Marketplace].
+
+Colin Su has presented at the FreeBSD 2024 Fall Summit about Azure DevOps Pipeline.
+
+Souradeep Chakrabarti from Microsoft has added a feature to use hypercalls for TLB shootdown on Hyper-V and Azure.
+
+Wei Hu root-caused an issue on missing CDROM device when booting FreeBSD on the latest Azure v6 VM SKU.
+V6 type only offers NVMe disks to guest OS.
+He also continues bug fixing for FreeBSD MANA NIC device.
+
+Work in progress tasks:
+
+* Automating the image publishing process and merging to [.filename]#src/release/#. (Li-Wen Hsu)
+* Colin Su is testing adding FreeBSD support in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+** link:https://github.com/microsoft/azure-pipelines-agent/pull/3266[]
+** Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+
+Open tasks:
+
+* Update FreeBSD-related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Update package:sysutils/azure-agent[] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure]
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2024-10-2024-12/bhyvemgr.adoc b/website/content/en/status/report-2024-10-2024-12/bhyvemgr.adoc
new file mode 100644
index 0000000000..ceb21c9395
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/bhyvemgr.adoc
@@ -0,0 +1,34 @@
+=== A bhyve management GUI written in Freepascal/Lazarus
+
+Links: +
+link:https://github.com/alonsobsd/bhyvemgr[Bhyvemgr] URL: link:https://github.com/alonsobsd/bhyvemgr/[] +
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+Bhyvemgr is a bhyve management GUI written in Freepascal/Lazarus on FreeBSD.
+It needs a bunch of tools mostly installed on base system and some installed from ports/packages.
+The application is being developed for desktop users to easily and quickly setup and run virtual machines on FreeBSD hosts.
+
+During this quarter, there were many bugfixes and improvements to Bhyvemgr.
+
+These are some new features that were added:
+
+- Support for Trusted Platform Module (TPM through software via swtpm) on CURRENT
+- Bootvars support
+- Bios, system, board and chassis information can be modified
+- Systray icon support on almost all desktop environment (tested on Plasma, Gnome, Xfce, LXQt and IceWM)
+
+Bhyvemgr supports aarch64 only on 15-CURRENT and amd64 from FreeBSD 13.x to 15-CURRENT.
+Also bhyvemgr can be
+
+* compiled and installed from link:https://www.freshports.org/sysutils/bhyvemgr[ports],
+* installed as binaries through `pkg` with gtk2, qt5 or qt6 interface support.
+
+Anyone interested in helping or supporting the project are welcome.
+
+Current version: 1.3.1
+
+TODO
+
+* Testing on real aarch64 hardware (aarch64 device donation for testing is welcome)
+* Add uart device support
diff --git a/website/content/en/status/report-2024-10-2024-12/bugmeister.adoc b/website/content/en/status/report-2024-10-2024-12/bugmeister.adoc
new file mode 100644
index 0000000000..3bdc5bd802
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/bugmeister.adoc
@@ -0,0 +1,72 @@
+=== Bugmeister Team
+
+Links: +
+link:https://wiki.freebsd.org/Bugzilla[FreeBSD Bugzilla] URL: link:https://wiki.freebsd.org/Bugzilla[]
+
+Contact: Bugmeister <bugmeister@FreeBSD.org>
+
+In this quarter we came even closer to steady-state; we are dealing
+with incoming PRs more quickly these days.
+For reference:
+
+link:https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90[]
+
+The overall number of PRs came down from slightly over 11,600 to right
+at 11,000.
+This was due to work from several people to go over entire groups of PRs (see below).
+
+Mark Linimon attended several video calls with various src committers.
+They are doing some experimentation to learn what kind of effort is sustainable.
+The most recent effort was to evaluate the latest incoming src PRs;
+you will note that many of them from the past few weeks have been marked as requesting feedback.
+
+Bugmeister folks also did some passes through the database to clean up metadata:
+
+ * reassigned bugs away from committers who had had their commit bits safekept over the last year.
+
+ * cleaned up bugs for Product: `Base` System Status: `In Progress`.
+   A number of these were not being actively worked on.
+   The count is down to 184.
+   ** In particular, Mark Linimon believes "assigned to mailing list" means "it is not really In Progress".
+   Perhaps it has been discussed, but we do not really have a state for that.
+   (We can make an argument that that itself is a bug.)
+   ** We are now down to only a handful of the above, from "too many".
+   The concept is to make sure `In Progress` has some real meaning.
+
+ * evaluated PRs for mfc-stableN.
+   In particular, any having mfc-stable12 had that flag cleared.
+   ** The concept is to make sure these metadata have some real meaning as well:
+   e.g. "a commit has been made and should be evaluated for MFCs".
+   ** There are now a much smaller number of these.
+
+ * closed numerous PRs as "Overcome By Events":
+   ** (old version) + (contains the string "boot")
+   ** (old version) + (contains the strings "alpha" or "beta")
+
+ * evaluated "PR shows a commit" (possibly via Phabricator)" and "there was no trailing discussion".
+   ** In a few cases of the above we simply assigned them and made sure that mfc-stable[13|14] was set, if it seemed appropriate.
+   ** This does leave many that have a commit and then have trailing discussion.
+   I think we will need more volunteers to go through those.
+
+ * removed many of the 'patch' keywords from PRs.
+   In the optimal case these should now be imputed by metadata in each attachment.
+   In a few cases where patches are submitted inline instead of as an attachment, the keyword stays.
+   There may be a few of these left over from the GNATS conversion.
+   The use of inline patches should be discouraged, as automation has no way to detect them.
+   Thanks to our triagers, especially Alexander Ziaee.
+
+There were various discussions about bug futures that came up in various video chats.
+One is that there is a (supported) successor to Phabricator, which itself is now no longer developed.
+Multiple groups will need to coordinate to evaluate it.
+
+Jan Bramkamp has volunteered to help with the task "automate harvesting PRs and evaluating whether they still apply".
+Mark Linimon to collaborate.
+
+Clusteradm@ helped us fend off yet another crawler site.
+While that was ongoing, bugzilla was nearly unusable due to timeouts, as were other services hosted on the same machine (wiki and cgit among others).
+
+We also welcomed our newest Triage member, Lexi (aka 'ivy' on Discord).
+
+Finally, glebius was added to bugmeister@ alias as core.13 liaison.
+
+See also: link:https://wiki.freebsd.org/Bugzilla/SearchQueries[]
diff --git a/website/content/en/status/report-2024-10-2024-12/buildpacks.adoc b/website/content/en/status/report-2024-10-2024-12/buildpacks.adoc
new file mode 100644
index 0000000000..28d4768b3c
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/buildpacks.adoc
@@ -0,0 +1,33 @@
+=== Containers and FreeBSD: Cloud Native Buildpacks
+
+Contact: Robert Gogolok <gogolok@gmail.com>
+
+link:https://buildpacks.io/[Cloud Native Buildpacks (CNBs)] transform application source code into container images.
+Those images can run on any cloud.
+With buildpacks, organizations can concentrate the knowledge of container build best practices within a specialized team, instead of having application developers across the organization individually maintain their own Dockerfiles.
+
+A few weeks ago, I've started to look into FreeBSD support for buildpacks.
+My goal is to have working versions of the tools link:https://buildpacks.io/docs/for-platform-operators/concepts/lifecycle/[lifecycle] and link:https://buildpacks.io/docs/for-platform-operators/how-to/integrate-ci/pack/[pack] in the next few months.
+
+There were previous attempts to bring support for FreeBSD to buildpacks, for example to `lifecycle`:
+
+* link:https://github.com/buildpacks/lifecycle/pull/1087[Add support for FreeBSD #1087]
+* link:https://github.com/buildpacks/lifecycle/pull/1271[Add FreeBSD Support #1271]
+
+After looking into those changes, I've decided to first introduce some general cleanup steps to keep the required changes for FreeBSD small.
+
+This resulted in the following changes that were successfully integrated:
+
+* link:https://github.com/buildpacks/lifecycle/pull/1431[Remove obsolete // +build lines #1431]
+* link:https://github.com/buildpacks/lifecycle/pull/1432[Use unix build constraint #1432]
+* link:https://github.com/buildpacks/lifecycle/pull/1439[Support FreeBSD build phase #1439]
+
+With these steps, it is now possible to compile `lifecycle` under FreeBSD.
+
+The next steps are:
+
+- Provide missing FreeBSD functionality to `lifecycle`.
+- Further investigate FreeBSD as a build target in `lifecycle`.
+- Investigate and get the tool `pack` to compile and run under FreeBSD.
+- Provide `lifecycle` and/or `pack` via FreeBSD ports.
+- Investigate the idea of FreeBSD buildpacks for some popular languages, similar to link:https://paketo.io/[paketo buildpacks].
diff --git a/website/content/en/status/report-2024-10-2024-12/ci.adoc b/website/content/en/status/report-2024-10-2024-12/ci.adoc
new file mode 100644
index 0000000000..ac1f82f89b
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/ci.adoc
@@ -0,0 +1,49 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://tinderbox.freebsd.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:++https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals++[Tickets related to freebsd-testing@] URL: link:++https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals++[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the fourth quarter of 2024, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* Update main and stable/14 build environment to 14.2-RELEASE
+* Update stable/13 build environment to 13.4-RELEASE
+* Fixed an old but not revealed bug about pw(1) usage in jail setup.
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing and pull/merge-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+** Improving the [.filename]#src/tests/ci# work to support running test suites
+**** Merging link:https://reviews.freebsd.org/D48015[CI: Add full test support]
+** Merging link:https://reviews.freebsd.org/D36257[Pre-commit CI with CIRRUS-CI]
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Redesigning the hardware test lab and adding more hardware for testing
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm ports building tests against -CURRENT
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:++https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals++[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/clusteradm.adoc b/website/content/en/status/report-2024-10-2024-12/clusteradm.adoc
new file mode 100644
index 0000000000..83ebf5891c
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/clusteradm.adoc
@@ -0,0 +1,81 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular support for FreeBSD.org user accounts.
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* Cluster software refresh.
+* Moving more cluster services to Chicago.
+* Supporting the Grimoirelab dashboard effort.
+
+==== Cluster software refresh
+
+Except for the package builders and developer-facing ("dogfood") machines, the FreeBSD cluster mostly tracks stable/X branches.
+
+At the time of this writing, there are 131 physical machines in the cluster.
+We have 54 machines on current, 61 on stable/14 and 14 on stable/13.
+Work continues to upgrade the remaining stable/13 machines to stable/14.
+The stable/12 machines have been slated for decommissioning for a while; they do not run production workloads.
+The remaining machines are slated for upgrading or decommissioning in the near future.
+
+Of the 297 jails in the cluster, 222 are now on stable/14.
+
+[.screen]
+----
+ 12.x: Regular   2, Jails   7
+ 13.x: Regular  14, Jails  59
+ 14.x: Regular  61, Jails 222
+>15.x: Regular  54, Jails   9
+Total: Regular 131, Jails 297
+Total installations: 428
+Running -RELEASE|{-p*}: 0
+Total geographic sites: 15
+----
+
+==== Moving cluster services to Chicago
+
+Earlier this year, we started building up our new site in Chicago.
+This quarter, we began decommissioning older machines in New Jersey and moving services to the newer machines in Chicago.
+Our long-term goal is for Chicago to become our primary location.
+This work will take several more months to complete.
+
+==== FreeBSD Official Mirrors Overview
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America -- California, Chicago, New Jersey (primary site), and Washington.
+
+Our mirror site in Taiwan is experiencing an extended outage.
+We hope to have it back online during the first quarter of 2025.
+
+Also during the first quarter of 2025, we expect a second mirror site in California, generously hosted by link:https://sonic.net[Sonic].
+
+The hardware and network connection have been generously provided by:
+
+* Cloud and SDN Laboratory at link:https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc]
+* link:https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University]
+* link:https://deploy.equinix.com/[Equinix]
+* link:https://internet.asn.au/[Internet Association of Australia]
+* link:https://www.isc.org/[Internet Systems Consortium]
+* link:https://www.inx.net.za/[INX-ZA]
+* link:https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc]
+* link:https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network]
+* link:https://www.metapeer.com/[MetaPeer]
+* link:https://www.nyi.net/[New York Internet]
+* link:https://nic.br/[NIC.br]
+* link:https://www.teleservice.net/[Teleservice Skåne AB]
+* link:https://your.org/[Your.Org]
+
+New official mirrors are always welcome.
+We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa.
+If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us.
+We are particularly interested in locations on the United States West Coast and throughout Europe.
+
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site.
+
+Sponsors: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/common-lisp.adoc b/website/content/en/status/report-2024-10-2024-12/common-lisp.adoc
new file mode 100644
index 0000000000..b4564258dc
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/common-lisp.adoc
@@ -0,0 +1,50 @@
+=== Improving Common Lisp Infrastructure in FreeBSD Ports
+
+Contact: Joe Mingrone <jrm@FreeBSD.org>
+
+link:https://lisp-lang.org/[Common Lisp] (CL) is a general-purpose, multi-paradigm programming language first conceived in the early 1980s.
+Although it predates many modern programming languages, it remains a viable option for many different projects.
+One contemporary example is Grammarly, a widely used grammar engine reportedly implemented in CL and capable of processing over a thousand sentences per second.
+
+The FreeBSD ports tree has provided CL support for many years.
+The initial work was contributed by Henrik Motakef in 2003, and then enhanced and maintained by Jimmy Olgeni.
+The infrastructure facilitated building and installing CL libraries using link:https://asdf.common-lisp.dev/[ASDF] so that multiple CL implementations could load compiled object code files (fasl) at run-time without conflicts.
+
+However, many issues crept in over the years.
+Support dwindled to only one CL implementation, link:https://www.sbcl.org/[SBCL], and users encountered longstanding bugs such as conflicting ASDF versions and write errors when loading libraries outside the ports tree.
+Also, managing dependencies was cumbersome because most infrastructure code was included as part of the package:devel/cl-asdf[] port.
+
+A long overdue update of the FreeBSD CL infrastructure was completed this quarter.
+The primary outcome is that users can, once again, easily and reliably work with CL on FreeBSD.
+For example, installing and loading the popular Alexandria library under SBCL requires only a few simple steps.
+
+[source, shell]
+----
+% pkg install cl-alexandria-sbcl
+% sbcl
+* (asdf:load-system :alexandria)
+----
+
+Similar steps can be used to load libraries for the other two newly supported implementations: link:https://ccl.clozure.com/[CCL], and link:https://clisp.sourceforge.io/[CLISP].
+Most users will likely prefer to work with the fasl ports, although there is no obligation to do so.
+Because ASDF is now configured to fall back to its default caching mechanism of writing fasl to a cache under `${HOME}`, users can also install CL source ports without the associated fasl port or load CL sources from outside of the ports tree.
+
+Other highlights of the update include:
+
+- decoupling ASDF initialization from package:devel/cl-asdf[] by creating a dedicated port: package:devel/freebsd-cl-asdf-init[]
+- creating `USES=cl`
+- adding and updating various CL library ports for the three supported implementations
+- updating and modernizing package:lang/ccl[] and package:lang/clisp[]
+
+For details, refer to these commit logs:
+
+- link:https://cgit.freebsd.org/ports/commit/?id=4c954c1522cbf4d05013caaf40c36458d82f1480[4c954c1522cbf4d05013caaf40c36458d82f1480]
+- link:https://cgit.freebsd.org/ports/commit/?id=f6a75a8f9bf20dbf1e9a4d5bc171d58f595c1ec1[f6a75a8f9bf20dbf1e9a4d5bc171d58f595c1ec1]
+- link:https://cgit.freebsd.org/ports/commit/?id=1d7c75a5cde6792b3872340edeaf8f278add291a[1d7c75a5cde6792b3872340edeaf8f278add291a]
+- link:https://cgit.freebsd.org/ports/commit/?id=148251b431b8d972623bb3adaa5a71355f47ac26[148251b431b8d972623bb3adaa5a71355f47ac26]
+- link:https://cgit.freebsd.org/ports/commit/?id=7f68336ed19be61027dfb7b461aacd056733eba4[7f68336ed19be61027dfb7b461aacd056733eba4]
+
+The tentative plan is to add support for link:https://ecl.common-lisp.dev/[ECL] after an ASDF output translation issue is solved and to create ports for other CL libraries.
+Feedback, testing, and contributions are welcome.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/core.adoc b/website/content/en/status/report-2024-10-2024-12/core.adoc
new file mode 100644
index 0000000000..0ca2b420ae
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/core.adoc
@@ -0,0 +1,20 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== Following up with the FreeBSD Foundation
+
+Core had a video conference with the FreeBSD Foundation on 2024-12-12 to follow-up on their in-person meeting held in Dublin during EuroBSDCon.
+Core and the Foundation continue discussing how to improve the collaboration and how to support developers and contributors:
+
+* The next round of community survey
+* Identifying projects where core would like help from the Foundation
+* Work on the technical roadmap with the Foundation
+
+==== Work in Progress
+
+Core is currently working on the following items:
+
+* Policy on generative AI created code and documentation
diff --git a/website/content/en/status/report-2024-10-2024-12/doceng.adoc b/website/content/en/status/report-2024-10-2024-12/doceng.adoc
new file mode 100644
index 0000000000..502eb77d92
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/doceng.adoc
@@ -0,0 +1,89 @@
+////
+Quarter:	4th
+Prepared by:	fernape
+Reviewed by:	carlavilla
+Last edit:	$Date$
+Version:	$Id:$
+////
+
+=== Documentation Engineering Team
+
+Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[] +
+Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] +
+Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+==== Document changes
+
+* Handbook:
+  ** Add warning about custom kernel configurations.
+  ** Mention Rocky Linux 9 userland.
+  ** Add notes to VMWare related setup guide.
+
+* Committer's guide: Document "Discussed with"
+  Improve "Fixes:" metadata.
+
+* Porter's Handbook: Document new `TCL_` variables.
+
+* Website: Remove Turkish links.
+
+* Documentation repository:
+  ** Added OpenBSD 7.6 manual pages.
+  ** Updated Debian 11/12 manpages.
+
+
+==== FreeBSD Translations on Weblate
+
+Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblateurl[] +
+Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/url[]
+
+===== Q4 2024 Status
+
+* 18 team languages
+* 215 registered users
+
+1 new translator joined Weblate:
+
+* Sean Markham (ES)
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 14%)
+* Chinese (Traditional) (zh-tw)	(progress: 11%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Greek (el)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 11%)
+* Korean (ko)			(progress: 30%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 6%)
+* Polish			(progress: 2%)
+* Portuguese			(progress: 0%)
+* Portuguese (pt-br)		(progress: 31%)
+* Sinhala			(progress: 1%)
+* Spanish (es)			(progress: 39%)
+* Spanish (Chile)		(progress: 0%)
+* Turkish (tr)			(progress: 5%)
+
+We want to thank everyone who contributed, translating, or reviewing documents.
+
+And please, help promote this effort on your local user group; we always need more volunteers.
+
+==== Packages maintained by DocEng
+
+During this quarter the following work was done in packages maintained by doceng@:
+
+* www/gohugo: update to 0.140.2
+* misc/freebsd-doc-ja: fix build
+
+==== Open issues
+
+There is 1 open PR in Bugzilla assigned to doceng@:
+
+ * 276923 www/gohugo link error under poudriere
+
diff --git a/website/content/en/status/report-2024-10-2024-12/ec2.adoc b/website/content/en/status/report-2024-10-2024-12/ec2.adoc
new file mode 100644
index 0000000000..8538353217
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/ec2.adoc
@@ -0,0 +1,17 @@
+=== FreeBSD on EC2
+
+Links: +
+link:https://www.daemonology.net/freebsd-ec2-boot-performance/[EC2 Boot performance over time] URL: link:https://www.daemonology.net/freebsd-ec2-boot-performance/[]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances.
+
+In the past quarter, first boot performance of ZFS AMIs has been significantly improved, e.g. from about 22 seconds to about 11 seconds for 15.0 "base" AMIs on amd64.
+Graphs of boot performance over time are now being generated and published automatically; typical times are around 9-12 seconds for "base" and "small" AMIs and 14-18 seconds for "cloud-init" AMIs.
+
+On Graviton systems, the EC2 "shutdown" and "reboot" operations now work as intended (starting with FreeBSD 14.2).
+On Graviton systems, adding new devices (e.g. EBS volumes) while the system is running now works in HEAD and support is expected to be merged in time for FreeBSD 14.3.
+
+Sponsor: Amazon +
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2024-10-2024-12/erlang.adoc b/website/content/en/status/report-2024-10-2024-12/erlang.adoc
new file mode 100644
index 0000000000..017e18c87c
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/erlang.adoc
@@ -0,0 +1,24 @@
+=== FreeBSD Erlang Ecosystem Ports update
+
+Links: +
+link:https://wiki.freebsd.org/Erlang[FreeBSD Erlang wiki] URL: link:https://wiki.freebsd.org/Erlang[] +
+link:https://erlang.org/[Erlang/OTP language] URL: link:https://erlang.org/[] +
+link:https://elixir-lang.org/[Elixir language] URL: link:https://elixir-lang.org/[] +
+link:https://gleam.run/[Gleam language] URL: link:https://gleam.run/[] +
+
+Contact: FreeBSD Erlang mailing list <erlang@FreeBSD.org>
+
+The Erlang runtime system, commonly known as the BEAM, provides a runtime that is used by a number of programming languages and applications in the FreeBSD ports collection.
+
+In the final update for 2024, the Erlang ecosystem team has been busy:
+
+* Regular updates to all Erlang/OTP releases, to stay current
+* Elixir 1.18.1, Gleam 1.6.3, and RabbitMQ updates
+
+Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ, without a supported migration path.
+
+Note that as the upstream Erlang OTP team only commit to supporting the two latest major releases, more and more point updates are arriving for OTP26-27, but not for the older Erlang runtime releases, which are now unlikely to get security and bug fixes.
+
+The Erlang team will be updating the default Erlang runtime to OTP26, to package:lang/erlang[], along with the usual dependencies and tooling.
+
+Additional testing and community contributions are welcome; please reach out on the mailing list, especially if you are able to help testing of specific port updates.
diff --git a/website/content/en/status/report-2024-10-2024-12/foundation-infrastructure-modernization.adoc b/website/content/en/status/report-2024-10-2024-12/foundation-infrastructure-modernization.adoc
new file mode 100644
index 0000000000..f0dcb3d9ae
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/foundation-infrastructure-modernization.adoc
@@ -0,0 +1,26 @@
+=== Infrastructure Modernization
+
+Contact: Ed Maste <emaste@FreeBSD.org> +
+Contact: Alice Sowerby <alice@freebsdfoundation.org>
+
+The project started in Q3 of 2024 and was commissioned by the Sovereign Tech Agency with a budget of $745,000, to be spent over about one year.
+The main goals are to improve security tools for the base system, ports, and packages, update the project's infrastructure to speed up development, enhance build security, and make it easier for new developers to get started.
+
+Q4 update
+
+* Work Package A: Technical Debt reduction.
+The Foundation collaborated with the Source Management team to commission and deploy a number of dashboards that characterize the bug backlog for the FreeBSD Project.
+These were created to the team's specifications by our project partner, Bitergia, who used an open source tool called GrimoireLab to create the dashboards.
+Foundation staff have hosted the dashboards on a FreeBSD deployment and they can be seen at https://grimoire.freebsd.org/.
+More information about the dashboards can be found at https://github.com/freebsd/grimoire.
++
+The Source Management team has also used these dashboards to support their new, evolving approach to bug triage and it has been included as a key tool for collaborative bug-squashing events.
+
+* Work Package B: Zero Trust Builds, and Work Package C: CI/CD Automation.
+The Foundation collaborated with various key management and administration teams within the FreeBSD Project to co-create the details of the scope for these two projects.
+They are scheduled to start in January and will conclude in Q2/3.
+
+* Work Package D: Security Controls in Ports and Packages, and Work Package E: Improve Software Bill of Materials (SBOM).
+These have not started yet as they are scheduled for February and March starts respectively.
+
+Commissioning body: link:https://www.sovereign.tech/[Sovereign Tech Agency]
diff --git a/website/content/en/status/report-2024-10-2024-12/foundation-laptop.adoc b/website/content/en/status/report-2024-10-2024-12/foundation-laptop.adoc
new file mode 100644
index 0000000000..b0dacc37e3
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/foundation-laptop.adoc
@@ -0,0 +1,32 @@
+=== Laptop Support and Usability Improvements Project
+
+Contact: Ed Maste <emaste@FreeBSD.org> +
+Contact: Alice Sowerby <alice@freebsdfoundation.org>
+
+The project began in Q4 of 2024 and is funded by the FreeBSD Foundation and Quantum Leap Research.
+It has a budget of $750,000, which will be used over one to two years.
+The goal is to improve key features like WiFi, audio usability, suspend and resume functions, graphics, and Bluetooth.
+The team will also create clear documentation and step-by-step guides to help people use the new features.
+
+Q4 Update
+
+* The Foundation link:https://freebsdfoundation.org/blog/why-laptop-support-why-now-freebsds-strategic-move-toward-broader-adoption/[initiated the project], created link:https://github.com/FreeBSDFoundation/proj-laptop[a public roadmap], and allocated contractors to relevant workstreams.
+December was the first monthly iteration of development, covering:
+
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/32[Implement S0ix low power states]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/9[Put a VM into hibernation]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/24[Create a list of supported laptops]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/30[Create a translation layer for Linux drivers on FreeBSD]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/28[Create a list of supported window environments]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/45[wireless_update,POC driver for Intel WiFi interfaces (based on OpenBSD/Haiku)]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/46[Resolve tech debt in pkg to enable PkgBase development]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/12[Document how to update graphic drivers]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/35[Implement s2idle low power state]
+** link:https://github.com/FreeBSDFoundation/proj-laptop/issues/39[Bring in camera code donation from Dell]
+
+* The FreeBSD project started a community group called the link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup["Laptop and Desktop Working Group" (LDWG)] to help people working on Laptop- and Desktop-related projects to connect and collaborate with others in the community working on similar efforts.
+The group held its first monthly meeting in December 2024.
+To stay updated on LDWG activities, you can link:https://lists.freebsd.org/subscription/freebsd-desktop[join the Desktop mailing list].
+
+Sponsor: The FreeBSD Foundation +
+Sponsor: link:https://www.ql-research.com/[Quantum Leap Research]
diff --git a/website/content/en/status/report-2024-10-2024-12/foundation-security-audit.adoc b/website/content/en/status/report-2024-10-2024-12/foundation-security-audit.adoc
new file mode 100644
index 0000000000..8b59947248
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/foundation-security-audit.adoc
@@ -0,0 +1,33 @@
+=== Security Audits
+
+Contact: Ed Maste <emaste@FreeBSD.org> +
+Contact: Alice Sowerby<alice@freebsdfoundation.org>
+
+The project began in Q2 of 2024 and was funded by Alpha Omega with a budget of $137,500, which was used over about six months and is now complete.
+The focus was on conducting a code audit for key subsystems, bhyve and Capsicum, as well as performing a security audit of the development process.
+The funds were used to hire a specialist offensive security firm to perform the code audit, to contract developers to address issues found, and for Foundation staff's work on both audits.
+
+Q4 update +
+The project is complete.
+
+The Code Audit and link:https://freebsdfoundation.org/wp-content/uploads/2024/11/2024_Code_Audit_Capsicum_Bhyve_FreeBSD_Foundation.pdf[subsequent reports] were released after the related Security Advisories were published.
+
+The Process Audit is complete.
+It was created by FreeBSD Foundation staff who ran an outreach exercise to gather information about the current FreeBSD development process.
+The teams consulted were: Security Team, Source Management Team, Cluster Administrators, Release Engineering Team.
+
+Information was gathered through an online long-form survey which was structured around existing frameworks for analysing security in software development.
+Teams were asked to describe current development processes and appraise the current security practices, as well as to make suggestions for improvements.
+
+The responses were collated and synthesised into the report by Foundation staff.
+The report was reviewed for accuracy by the original respondents.
+
+The report will now be made available to the Security Team and other teams previously mentioned, as well as to the Foundation executive team.
+This will be a useful tool in identifying areas for investment and prioritisation going forward as more security projects are planned and funded.
+
+The report is intended primarily for FreeBSD Project and Foundation planning purposes and as such there is no plan to promote it to an external audience.
+Interested readers should contact the Security Team to request a copy of the report.
+
+To learn about the project, and to see historical monthly updates visit: link:https://github.com/ossf/alpha-omega/tree/main/alpha/engagements/2024/FreeBSD[].
+
+Sponsor: link:https://alpha-omega.dev/[Alpha Omega Project]
diff --git a/website/content/en/status/report-2024-10-2024-12/foundation-security.adoc b/website/content/en/status/report-2024-10-2024-12/foundation-security.adoc
new file mode 100644
index 0000000000..7b250c27f4
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/foundation-security.adoc
@@ -0,0 +1,23 @@
+=== Security engineering at the FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-releases-bhyve-and-capsicum-security-audit-funded-by-alpha-omega-project/[FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by Alpha-Omega Project] URL: link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-releases-bhyve-and-capsicum-security-audit-funded-by-alpha-omega-project/[] +
+link:https://fosdem.org/2025/schedule/event/fosdem-2025-6152-how-freebsd-security-audits-have-improved-our-security-culture/[How FreeBSD security audits have improved our security culture] URL: link:https://fosdem.org/2025/schedule/event/fosdem-2025-6152-how-freebsd-security-audits-have-improved-our-security-culture/[] +
+link:https://github.com/orcwg/orcwg[Home of the ORC WG] URL: link:https://github.com/orcwg/orcwg[] +
+link:https://freebsdfoundation.org/about-us/contact-us/[FreeBSD Foundation: Contact Us] URL: link:https://freebsdfoundation.org/about-us/contact-us/[] +
+link:https://openssf.org/projects/osv-schema/[Open Source Vulnerability schema (OSV Schema)] URL: link:https://openssf.org/projects/osv-schema/[] +
+link:https://github.com/ossf/osv-schema/pull/237[ossf/osv-schema tools: import a conversion tool to and from VuXML (#237)] URL: link:https://github.com/ossf/osv-schema/pull/237[]
+
+Contact: Pierre Pronchery <pierre@freebsdfoundation.org>
+
+My tasks at the FreeBSD Foundation continue to revolve around Security Engineering for the FreeBSD Project.
+
+First, we keep working on the outcome of the source code audit on bhyve and Capsicum, documenting and researching how to prevent and mitigate similar issues from occurring again in the future.
+This includes the processes relevant for contributions to the FreeBSD Project, as well as the preparation of a joint presentation with Alpha-Omega at the BSD Devroom during the coming FOSDEM conference in 2025.
+
+At the same time, I am liaising with the Open Regulatory Compliance Working Group (ORC WG), where an FAQ is being elaborated jointly by a number of stakeholders on the European Union's newly introduced Cyber Resilience Act (CRA).
+This is all related to our ongoing collaboration with OpenSSF, notably the self-assessment initiative; note that the FreeBSD Foundation can provide assistance in this regard for projects deploying FreeBSD.
+
+Finally, possibilities around the integration of OSV tooling into the FreeBSD ecosystem are under investigation as well.
+
+Sponsored by:	The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/framework.adoc b/website/content/en/status/report-2024-10-2024-12/framework.adoc
new file mode 100644
index 0000000000..ff48095260
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/framework.adoc
@@ -0,0 +1,27 @@
+=== Framework Laptop support
+
+Links: +
+link:https://wiki.freebsd.org/Laptops/Framework_Laptop/[Framework Laptop page on FreeBSD Wiki] URL: https://wiki.freebsd.org/Laptops/Framework_Laptop/[] +
+link:https://github.com/FrameworkComputer/freebsd-on-framework[Guide on installing and using FreeBSD on Framework systems] URL: https://github.com/FrameworkComputer/freebsd-on-framework[] +
+link:https://bugs.freebsd.org/262152[Tracking ticket: Framework Laptop: Feature support, bugs and improvements] URL: https://bugs.freebsd.org/262152[]
+
+Contact: Daniel Schaefer <dhs@frame.work> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: Sheng-Yi Hong <aokblast@FreeBSD.org>
+
+For a long time, Framework Laptop Inc is friendly to the FreeBSD project in many aspects, including providing engineering samples to Foundation for testing and working on support.
+
+Since 2024 summer, there are several small hackathons in Framework's Taipei office on testing FreeBSD on different models of Framework laptop, and the peripheral devices.
+
+Sheng-Yi is using the laptop provided by Framework Computer to add more device support, e.g. https://cgit.freebsd.org/src/commit/?id=d3b05d0ea10abe059dc63c6fb6ef3f061b758af2[d3b05d0ea10a: Add smbus and i2c device IDs for Meteor Lake].
+
+Daniel from Framework Computer Inc started link:https://github.com/FrameworkComputer/freebsd-on-framework[a repository under Framework Computer's GitHub organization] to keep the notes of installation and miscellaneous information.
+He fixed fingerprint readers (libfprint) not just for Framework, but in general on FreeBSD.
+And working on the support and fix to many related drivers on FreeBSD.
+
+In November, Foundation people and some FreeBSD developers visited Framework's San Francisco office and had a meeting for checking the current FreeBSD support status and discussing the possible future collaboration plans.
+
+Foundation will continue working on improving the general laptop support and using Framework as one of the link:https://github.com/FreeBSDFoundation/proj-laptop/blob/main/supported/laptops.md[target platforms] for the link:https://github.com/FreeBSDFoundation/proj-laptop/[Laptop Support and Usability Project].
+
+Sponsor: The FreeBSD Foundation for Li-Wen's work +
+Sponsor: Framework Computer Inc for Daniel's work, hardware and space support
diff --git a/website/content/en/status/report-2024-10-2024-12/freebsd-foundation.adoc b/website/content/en/status/report-2024-10-2024-12/freebsd-foundation.adoc
new file mode 100644
index 0000000000..d774712da6
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/freebsd-foundation.adoc
@@ -0,0 +1,154 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] +
+link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to advancing FreeBSD through technical and non-technical support.
+Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters.
+The following report covers just some of the ways we supported FreeBSD in Q4.
+
+Deb Goodkin here.
+On behalf of the Foundation, I want to start out by saying thank you to this amazing community!
+Your financial contributions have allowed us to step up and take on some significant projects, including large, multi-phase software development work, greater security improvements, and important infrastructure improvements that will continue through 2025.
+We also increased our FreeBSD advocacy efforts over many different technical and social media platforms, including creating more content to promote and advocate for FreeBSD.
+You'll find more information about all of this work below.
+For a more in-depth look at our efforts in 2024, be sure to check out the year-end blog posts and my year-end reflections in the advocacy section below.
+
+We are hiring!
+Check out our jobs page here for our Solutions Specialist and Technical Marketing Manager job postings.
+Plus, we are looking for part-time technical writers and will be opening up another position soon, so keep an eye on this page link:https://freebsdfoundation.org/open-positions/[].
+
+We are still finalizing our 2024 fundraising numbers, but at this writing, we have raised around $1,324,000.
+You might be thinking, why do not we have a final tally now that it is 2025?
+First, we have not yet received all the checks postmarked 2024 .
+We are also waiting on a few payments from invoices issued last year.
+We will have a final report in the next quarterly status report.
+
+Thank you to the individuals and organizations that made a financial contribution in Q4!
+We received 325 donations from individuals totaling $120,841 and six financial contributions from organizations totaling $326,000.
+We also received a grant from the Silicon Valley Community Fund.
+
+I would also like to send a shoutout to the anonymous donor who wanted us to help get Framework laptops into developers' hands.
+Pietro Cerutti has been coordinating that effort, and we are close to finalizing the process with Framework so developers can place their orders directly with them.
+
+We also funded almost $5,000 worth of AV equipment for the BSDCon AV team to minimize the amount of equipment needed to rent at each of the two main BSD conferences.
+
+Now, back to our financials.
+We will be publishing 2024 financial documents and reports in Q1.
+Our updated Q1-Q3 2024 Financial reports will be published by the end of January and will better match the budget format.
+The Final 2024 financial reports will be published in early Q2.
+Going forward, our budget and financial reports will provide more details on how funding is allocated to the major software development projects.
+For example, we will include how much was spent on the laptop project each quarter.
+We are working with our accountant to improve our accounting systems to be more transparent on how we spend our money.
+
+We are excited about the opportunities for FreeBSD in 2025 and beyond, and are growing our team to help support the work needed to take advantage of these opportunities.
+However, we need your help to sustain this.
+Our investments will only carry on this work for a year or two at most.
+If your company is invested in the long-term sustainability of FreeBSD, please consider giving a financial contribution so we can ensure it stays the secure, reliable, and innovative platform you depend on.
+Not sure how to go about asking?
+Please reach out.
+We can help you navigate the process.
+
+Please go here to make a donation: link:https://freebsdfoundation.org/donate/[].
+To find out more about our Partnership Program, go here: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[].
+
+==== Advocacy
+
+During the 4th quarter of 2024, we continued to raise awareness, advocate for the project, showcase users, while also providing educational content to the FreeBSD community.
+Here are some highlights of those efforts.
+
+* Sponsored and helped to organize the link:https://freebsdfoundation.org/news-and-events/event-calendar/fall-2024-freebsd-summit/[Fall 2024 FreeBSD Summit] which took place November 7-8, 2024 in San Jose, CA.
+  Check out the link:https://freebsdfoundation.org/blog/reflecting-on-the-fall-2024-freebsd-summit-insights-and-innovations/[event recap].
+  Videos are available on the link:https://youtube.com/playlist?list=PLugwS7L7NMXwhtfVdd3m2Ro0TV1XDzl3t&si=FjFDkeaiXqRKS1Lq[FreeBSD YouTube channel].
+* Updated the community on two of the new releases:
+** link:https://freebsdfoundation.org/blog/freebsd-13-4-whats-new-and-how-did-we-get-here/[FreeBSD 13.4: What's new, and how did we get here?]
+** link:https://freebsdfoundation.org/blog/freebsd-14-2-whats-new-and-how-did-we-get-here/[FreeBSD 14.2: What's new, and how did we get here?]
+* link:https://freebsdfoundation.org/end-user-stories/case-study-how-freebsd-fuels-nyis-success-as-a-managed-infrastructure-services-provider/[Published the NYI Case Study]
+* Shared link:https://freebsdfoundation.org/wp-content/uploads/2024/11/2024_Code_Audit_Capsicum_Bhyve_FreeBSD_Foundation.pdf[the FreeBSD Foundation 2024 Report on the Security Audit of the Capsicum and bhyve subsystems].
+  Learn more in the Security Audit.
+* Created a series of year end retrospectives on the work we did in 2024.
+** link:https://freebsdfoundation.org/blog/your-impact-on-freebsd-2024-milestones-and-whats-next/[Your Impact on FreeBSD: 2024 Milestones and What's Next]
+** link:https://freebsdfoundation.org/blog/2024-a-year-of-advocacy-and-growth-for-the-freebsd-foundation/[2024: A Year of Advocacy and Growth for the FreeBSD Foundation]
+** link:https://freebsdfoundation.org/blog/celebrating-2024s-collaborative-achievements-at-the-freebsd-foundation/[Celebrating 2024's Collaborative Achievements at the FreeBSD Foundation]
+** link:https://freebsdfoundation.org/blog/freebsd-foundation-a-year-of-sponsored-development-in-2024/[FreeBSD Foundation: A Year of Sponsored Development in 2024]
+** link:https://freebsdfoundation.org/blog/reflecting-on-a-successful-2024/[Reflecting on a Successful 2024]
+* Published additional blogs including:
+** link:https://freebsdfoundation.org/blog/why-your-open-source-project-should-prioritize-security-lessons-from-freebsds-proactive-approach/[Why Your Open Source Project Should Prioritize Security: Lessons from FreeBSD's Proactive Approach]
+** link:https://freebsdfoundation.org/blog/why-freebsd-should-be-the-foundation-for-your-security-product/[Why FreeBSD Should Be the Foundation for Your Security Product]
+** link:https://freebsdfoundation.org/blog/celebrating-freebsd-day-with-tara-stella-a-journey-from-linux-to-freebsd/[Celebrating FreeBSD Day with Tara Stella: A Journey from Linux to FreeBSD]
+** link:https://freebsdfoundation.org/blog/advancing-cloud-native-containers-on-freebsd-podman-testing-highlights/[Advancing Cloud Native Containers on FreeBSD: Podman Testing Highlights]
+* Participated in the following contributed articles, interviews and podcasts:
+** link:https://freebsdfoundation.org/news-and-events/latest-news/all-things-open-blog-prioritizing-security-lessons-from-freebsds-proactive-approach/[All Things Open Blog: Prioritizing Security: Lessons from FreeBSD's Proactive Approach]
+** link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-releases-bhyve-and-capsicum-security-audit-funded-by-alpha-omega-project/[FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by Alpha-Omega Project]
+** link:https://freebsdfoundation.org/news-and-events/latest-news/why-we-use-freebsd-over-linux-a-ctos-perspective/[Why We Use FreeBSD Over Linux: A CTO's Perspective]
+* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/october-2024-newsletter/[October 2024], link:https://freebsdfoundation.org/our-work/latest-updates/?filter=newsletter#:~:text=November%202024%20Newsletter[November 2024], and link:https://freebsdfoundation.org/our-work/latest-updates/?filter=newsletter#:~:text=December%202024%20Newsletter[December 2024] FreeBSD Foundation Newsletters.
+* Released the link:https://freebsdfoundation.org/our-work/journal/browser-based-edition/kernel-development/[September/October 2024] issue of the FreeBSD Journal with HTML versions of the articles.
+
+==== OS Improvements
+
+During the fourth quarter of 2024, 382 `src`, 135 `ports`, and 17 `doc` tree commits identified The FreeBSD Foundation as a sponsor.
+
+The Foundation and its investment partners supported four major projects:
+
+* mailto:kib@FreeBSD.org[Konstantin Belousov] continued work on an AMD IOMMU driver for FreeBSD, a project jointly funded by AMD and the Foundation.
+This effort aims to enhance support for large-core AMD systems and other scenarios requiring interrupt remapping.
+The driver was link:https://cgit.freebsd.org/src/commit/?id=0f5116d7efe33c81f0b24b56eec78af37898f500[pushed to the src tree] in early November and continues to undergo testing and refinement.
+
+* link:https://alpha-omega.dev/[Alpha-Omega] and the Foundation have been jointly funding a project to improve FreeBSD security.
+For the latest updates, refer to the <<_security_engineering_at_the_FreeBSD_Foundation,Security Engineering at the FreeBSD Foundation>> entry for the latest updates.
+
+* A project to link:https://freebsdfoundation.org/blog/why-laptop-support-why-now-freebsds-strategic-move-toward-broader-adoption/[improve FreeBSD laptop usability] began this quarter.
+For details, refer to the <<_laptop_support_and_usability_improvements_project,Laptop Support and Usability Improvements Project>> report entry.
+
+* <<_infrastructure_modernization,Work commissioned by the Sovereign Tech Agency to modernize FreeBSD's infrastructure>> continued this quarter.
+The goal of this work is to help achieve and sustain a manageable bug backlog.
+As part of this effort, The Foundation worked with link:https://bitergia.com/[Bitergia] to analyze and assess open Bugzilla bugs.
+mailto:bofh@FreeBSD.org[Muhammad Moinur Rahman] finished porting Grimoirelab and deploying link:https://grimoire.freebsd.org/[Grimoire] in the FreeBSD cluster.
+
+Other projects:
+
+* mailto:asiciliano@FreeBSD.or[Alfonso S. Siciliano] provided a <<_ports_collection_accessibility_colors_low_vision,FreeBSD Accessibility Project update>>.
+* mailto:obiwac@FreeBSD.org[Aymeric Wibo] began implementing <<_suspendresume_improvements,suspend-to-idle and S0ix sleep support>>.
+* mailto:bz@FreeBSD.org[Bjoern A. Zeeb] shared a <<_linuxkpi_802_11_wireless_update, LinuxKPI 802.11 Wireless Update>>.
+* mailto:starbops@hey.com[Chih-Hsin Chang] continued work to <<_openstack_on_freebsd,improve OpenStack on FreeBSD>>.
+* mailto:christos@FreeBSD.org[Christos Margiolis] shared an update on work to <<_audio_stack_improvements,improve the FreeBSD audio stack>>.
+* mailto:haraldei-fbsd@anduin.net[Harald Eilersten] began working on a project to <<_improve_openjdk_on_freebsd,improve OpenJDK on FreeBSD>>.
+* mailto:ifreund@freebsdfoundation.org[Isaac Freund] worked on <<_pkgbase_motivated_improvements_to_pkg,PkgBase-motivated improvements to pkg>>.
+* mailto:ljianlin99@gmail.com[Jian-Lin Li] began a project to <<_syzkaller_improvement_on_freebsd,improve Syzkaller on FreeBSD>>.
+* mailto:jrm@FreeBSD.org[Joseph Mingrone] spent time on a personal project to <<_improving_common_lisp_infrastructure_in_freebsd_ports,improve Common Lisp support in the ports tree>>.
+* mailto:olce@FreeBSD.org[Olivier Certner] submitted a report entry describing the work he completed with Baptiste Daroussin to <<_mac_do4_setcred2_mdo1, allow controlled process credentials transitions using the MAC framework>>.
+* mailto:pierre@freebsdfoundation.org[Pierre Pronchery] returned to working on a <<_umb4_driver_for_mbim_usb_4g5g_modems,umb(4) driver for MBIM USB 4G/5G modems>> and he shared <<_progress_on_the_freebsd_installer,an update on work to improve the FreeBSD Installer>>.
+* mailto:thj@FreeBSD.org[Tom Jones] started <<_wireless_update,porting the iwx WiFi driver from OpenBSD (via Haiku)>>.
+
+Other members of the Foundation's development team contributed to FreeBSD development efforts.
+For example:
+
+* mailto:mhorne@FreeBSD.org[Mitchell Horne] worked with community contributor Julien Cassette to add link:https://cgit.freebsd.org/src/commit/?id=c5c02a131a0e2ef52771e683269bc8778fe511f3[a RISC-V Allwinner D1 clock and reset driver].
+* mailto:chuck@FreeBSD.org[Chuck Tuffli], mailto:jhb@FreeBSD.org[John Baldwin], and mailto:pierre@freebsdfoundation.org[Pierre Pronchery] fixed a few bhyve issues:
+** link:https://cgit.freebsd.org/src/commit/?id=e94a1d6a7f2eb932850e1db418bf34d5c6991ce8[bounds checks in hda_codec]
+** link:https://cgit.freebsd.org/src/commit/?id=b0a24be007d83f7929de5b3fc320a29e6868067d[out-of-bounds read in NVMe log page]
+** link:https://cgit.freebsd.org/src/commit/?id=5374b9e146811757540e35553a7712c5b9b29239[infinite loop in queue processing]
+** link:https://cgit.freebsd.org/src/commit/?id=b34a4edefb0a40ced9b17ffd640f52fe55edc1f5[buffer overflow in pci_vtcon_control_send]
+** link:https://cgit.freebsd.org/src/commit/?id=8c8ebbb045185396083cd3e4d333fe1851930ee7[robustness of TRIM handling].
+* In the ports tree, mailto:bofh@FreeBSD.org[Muhammad Moinur Rahman] converted `USE_OCAML` and `USE_JAVA` to the `USES` framework.
+* mailto:emaste@FreeBSD.org[Ed Maste] squashed a couple of man:makefs[8] bugs related to creating ISO9660 filesystems via the man:cd9660[4] driver:
+** link:https://cgit.freebsd.org/src/commit/?id=2e09cef8dc6f46faba8bab87c42c3f19ba2ffe87[cd9660 filename buffer maximum length]
+** link:https://cgit.freebsd.org/src/commit/?id=1f31d437428014e864bcce1223cf7017180e2608[cd9660 duplicate directory names].
+
+==== Continuous Integration and Workflow Improvement
+
+As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to <<_ci,improving the Project's continuous integration system and test infrastructure>>.
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2024-10-2024-12/gcc.adoc b/website/content/en/status/report-2024-10-2024-12/gcc.adoc
new file mode 100644
index 0000000000..35d14e8c8e
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/gcc.adoc
@@ -0,0 +1,27 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[] +
+link:https://gcc.gnu.org/gcc-14/[GCC 14 release series] URL: link:https://gcc.gnu.org/gcc-14/[] +
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281091[exp-run to update GCC default version from 13 to 14] is getting forward.
+As usual, thanks to everyone involved.
+
+If you maintain any of the affected ports or want to give a hand preparing and testing some patches, you can consider trying adding `-fpermissive` to `CFLAGS` in affected ports as a temporary solution: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds.
+The `-fpermissive` flag switches those errors back to warnings.
+However, it is preferable that upstream updates its code to remove those warnings completely so that `-fpermissive` is not necessary, possibly with FreeBSD ports maintainers support.
+If the code is not maintained upstream anymore, the time might have come to deprecate the port.
+
+Work has been done on some bugs too, mainly upstream:
+
+- link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210[] has been fixed: a recent change in the FreeBSD headers caused a regression in the GCC 15 development version;
+- link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115008[] has been fixed: this was an issue with posix_fallocate failing on FreeBSD on a ZFS filesystem;
+- an attempt to fix bug link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282797[] specific to aarch64 for -devel ports has failed.
+If you are able to give a hand on this, it would be very much appreciated.
+
+Thanks to everyone who has helped with these issues.
diff --git a/website/content/en/status/report-2024-10-2024-12/gvm.adoc b/website/content/en/status/report-2024-10-2024-12/gvm.adoc
new file mode 100644
index 0000000000..402a197464
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/gvm.adoc
@@ -0,0 +1,30 @@
+=== Greenbone Vulnerability Management Community Edition
+
+Links: +
+link:https://www.greenbone.net/en/[Greenbone] URL: link:https://www.greenbone.net/en/[] +
+link:https://github.com/greenbone/[Greenbone GitHub] URL: link:https://github.com/greenbone/[] +
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+The Greenbone Community Edition (GVM) covers the actual source code of the Greenbone Vulnerability Management software stack, which is also known as OpenVAS scanner, a security feed with more than 160.000 vulnerability tests, a vulnerability management application, and much more.
+
+During this quarter, package:security/gvm[] metaport was updated to 24.1.2.
+This update includes the following:
+
+- package:databases/pg-gvm[]: Updated to 22.6.6
+- package:security/gsa[]: Updated to 24.1.0 (Only amd64 and aarch64)
+- package:security/gsad[]: Updated to 24.1.0
+- package:security/openvas[]: Updated to 23.14.0
+- package:security/gvmd[]: Updated to 24.1.2
+- package:security/gvm-libs[]: Updated to 22.15.0
+- package:security/py-notus-scanner[]: Updated to 22.6.5
+- package:security/py-greenbone-feed-sync[]: Updated to 24.9.0
+- package:security/py-ospd-openvas[]: Bump PORTREVISION
+- package:security/py-gvm-tools[]: Updated to 24.12.1
+- package:security/py-python-gvm[]: Updated to 24.12.0
+
+A quick GVM jail installation to test it can be done using link:https://github.com/DtxdF/AppJail[AppJail], link:https://github.com/alonsobsd/greenbone-openvas-makejail[makejail], or link:https://github.com/AppJail-makejails/greenbone-openvas[].
+
+Anyone interested in helping with the project or interested in aarch64 device donation for testing is welcome.
+
+Current version: 24.1.2
diff --git a/website/content/en/status/report-2024-10-2024-12/installer.adoc b/website/content/en/status/report-2024-10-2024-12/installer.adoc
new file mode 100644
index 0000000000..5bfcc8c232
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/installer.adoc
@@ -0,0 +1,23 @@
+=== Progress on the FreeBSD installer
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2024Projects/ImprovingRepairAbilityOfTheFreeBSDInstaller[Improving Repair Ability of the FreeBSD Installer] URL: link:https://wiki.freebsd.org/SummerOfCode2024Projects/ImprovingRepairAbilityOfTheFreeBSDInstaller[] +
+link:https://github.com/freebsd/freebsd-src/pull/1395[GSoC 2024 - Improving Installer with Repair and Upgrade Ability (#1395)] URL: link:https://github.com/freebsd/freebsd-src/pull/1395[] +
+link:https://github.com/freebsd/freebsd-src/pull/1424[bsdinstall: Add pkg install support in live env (#1424)] URL: link:https://github.com/freebsd/freebsd-src/pull/1424[] +
+link:https://github.com/freebsd/freebsd-src/pull/1427[bsdinstall: Add repair scripts to installer menu (#1427)] URL: link:https://github.com/freebsd/freebsd-src/pull/1427[] +
+link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[Laptop and Desktop Working Group] URL: link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[]
+
+Contact: Pierre Pronchery <pierre@freebsdfoundation.org>
+
+As part of 2024's GSoC Project on the FreeBSD installer, I had the pleasure to mentor Chun Cheng Yeh (aka "Leaf") with his implementation of additional capabilities.
+The aim was to add support for repairing or updating an existing installation of FreeBSD, as well as allowing packages to be installed in the Live environment.
+This work has been consolidated into three distinct pull-requests, available on GitHub.
+While some aspects probably still require additional polishing before a possible merge, the possibility to significantly extend the installer images into a potentially life-saving tool is within reach.
+
+This is particularly relevant given the ongoing efforts to improve support for laptop and desktop use of FreeBSD.
+In this context, I am currently resuming work on the graphical version of the installer.
+The most immediate challenge includes shaping it suitably for integration into the next major release.
+
+Combining the two initiatives above should help FreeBSD close some gaps with its competition amongst other modern Operating Systems, for the enterprise as well as for laptop and desktop use.
+
+Sponsored by:	The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/intro.adoc b/website/content/en/status/report-2024-10-2024-12/intro.adoc
new file mode 100644
index 0000000000..67063bd0b4
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/intro.adoc
@@ -0,0 +1,13 @@
+Here is the fourth and last 2024 status report, with 44 entries.
+
+It shows: 2024 has been a tremendously successful and busy year.
+Usually, one would expect the final months in a year to be less busy, with people leaving for holidays and New Years celebration.
+We still managed to deliver and see great progress on so many things!
+
+Collecting and compiling this report took longer than planned, but it was worth the wait.
+
+Thank you to the whole community for your amazing work and an especially big thanks to those who contributed updates to this report!
+
+Enjoy the read!
+
+Chris Moerz, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2024-10-2024-12/ldwg.adoc b/website/content/en/status/report-2024-10-2024-12/ldwg.adoc
new file mode 100644
index 0000000000..5b467cd29c
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/ldwg.adoc
@@ -0,0 +1,46 @@
+=== Laptop and Desktop Work Group (LDWG)
+
+Links: +
+link:https://lists.freebsd.org/archives/freebsd-desktop/[Desktop mailing list] URL: link:https://lists.freebsd.org/archives/freebsd-desktop/[] +
+link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[Wiki Page] URL: link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[]
+
+Contact: Chris Moerz <freebsd@ny-central.org>
+
+October 2024 marked the inception of the Laptop and Desktop Work Group (LDWG), affectionately known as "Ludwig".
+This initiative provides a collaborative platform for the community to engage in development, testing, knowledge exchange, and advocacy for FreeBSD on laptops and desktops.
+Everyone is welcome to join, if interested.
+
+Scope of Work:
+
+* Content Creation: Develop recordings, articles, tutorials, documentation, and system configurations for stakeholders interested in FreeBSD on laptops and desktops.
+* Encouraging Contributions: Invite developers, testers, and industry experts to enhance the usability of FreeBSD on laptops and desktops.
+* Facilitating Collaboration: Promote code contributions, testing initiatives, operational support, and hardware insights.
+* Supporting User Stories and Ongoing Projects: Assist in the creation, validation, prioritization, and delivery of user stories identified in the FreeBSD Foundation’s “Laptop” investment work package.
+
+On November 16, 2024, the LDWG held its inaugural virtual meeting.
+The strong interest in FreeBSD for laptops and desktops was evident from the diverse group of participants, including developers, contributors, Discord community moderators, users, and FreeBSD Foundation members.
+Meeting slides, minutes, and recordings are available on the Group’s link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[wiki page].
+
+During the meeting, the group identified prioritized gaps and potential improvements in the following areas:
+
+* Console
+* Desktop Environment
+* Documentation
+* Hardware
+  ** Graphics
+  ** Wireless (WiFi and Bluetooth)
+  ** USB/Thunderbolt
+* Installer
+* Performance
+* Software and Port Availability
+
+All activities are documented on the link:https://docs.google.com/spreadsheets/d/15btrze2sZrprSBd3Hb3YG27cZqG0AFjcvLlcTTifpIE/edit?gid=0#gid=0[Group's worksheet].
+The Group encourages anyone interested in contributing to add their name.
+If there is any planned or ongoing work, please include it in the worksheet.
+
+Alice Sowerby provided an update on the link:https://github.com/FreeBSDFoundation/proj-laptop[The Foundation’s Laptop project], highlighting the need for volunteers to support testing efforts.
+
+The Group is running an link:https://docs.google.com/forms/d/e/1FAIpQLSd6-AOHpnae4o40CSr0tt6GlmfgfP7A9REdulJmPw9Nn0Uo_w/viewform?usp=sf_link[online survey] to gather input from non-participants.
+The survey will remain open until the next call in January, where results will be presented and discussed.
+
+Hope to see you there!
diff --git a/website/content/en/status/report-2024-10-2024-12/lkpi-wireless.adoc b/website/content/en/status/report-2024-10-2024-12/lkpi-wireless.adoc
new file mode 100644
index 0000000000..ffc3c90138
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/lkpi-wireless.adoc
@@ -0,0 +1,37 @@
+=== LinuxKPI 802.11 Wireless Update
+
+Links: +
+link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[Categorised Wireless Problem Reports] URL: link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[] +
+link:https://people.freebsd.org/~bz/wireless/[Overview of drivers] URL: link:https://people.freebsd.org/~bz/wireless/[]
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org> +
+Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>
+
+With multiple wireless projects ongoing, this report focuses on the efforts using permissively licensed Linux wireless drivers mostly unmodified on FreeBSD.
+
+Drivers previously committed directly to FreeBSD src.git were retroactively imported in vendor branches and merged to main.
+This makes maintenance and identifying local changes a lot easier.
+The man:iwlwifi[4], man:rtw88[4], and man:rtw89[4] drivers got updated in main to match Linux 6.11.
+
+The man:rtw89[4] driver, which had been ported and in the tree for a while, got connected to the build.
+Thanks for that goes to the efforts of the community finding two bugs preventing it from working before.
+
+Wireless firmware in ports got updated and a release flavor was added.
+The release building framework got enhanced to install the firmware packages onto the release media.
+The installer grew support to run man:fwget[8] on the installed system to install the firmware.
+This all together ensures that (wireless) drivers with external firmware can be used from the installer and right away on the installed system without the need for alternate connectivity.
+With the framework in place for man:iwlwifi[4], man:rtw88[4], and man:rtw89[4] support for more drivers can easily be added in the future.
+These changes shipped the first time with 14.2-RELEASE.
+
+Having a lot of these requested necessities out of the way, time was spent on HT(802.11n) and VHT(802.11ac) improvements to the LinuxKPI framework synching between driver and net80211.
+Hardware crypto offload got sorted along with A-MPDU RX/BA offload right at the end of the year.
+Both were needed towards the goal to achieve higher throughput with man:iwlwifi[4].
+
+A half-year old bug, which stayed unnoticed preventing packets to be sent beyond scanning with man:rtw88[4] in main and stable/14, received a patch to fix the situation.
+
+Work for the first quarter of 2025 should include:
+
+* finishing basic HT and VHT support, and
+* looking at finishing the code for generic LinuxKPI 802.11 suspend/resume support
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/lxqt.adoc b/website/content/en/status/report-2024-10-2024-12/lxqt.adoc
new file mode 100644
index 0000000000..5b4c14d8af
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/lxqt.adoc
@@ -0,0 +1,19 @@
+=== LXQt on FreeBSD
+
+Links: +
+link:https://lxqt-project.org/[LXQt Project] URL: link:https://lxqt-project.org/[] +
+link:https://github.com/lxqt/[LXQt Project GitHub] URL: link:https://github.com/lxqt[] +
+
+Contact: LXQt Team <lxqt@FreeBSD.org>
+
+LXQt is an advanced, easy-to-use, and fast desktop environment based on Qt technologies.
+It has been tailored for users who value simplicity, speed, and an intuitive interface.
+Unlike most desktop environments, LXQt also works fine with less powerful machines.
+
+During this quarter, the package:x11-wm/lxqt[] metaport was updated to 2.1.0.
+This update adds initial link:https://github.com/lxqt/lxqt/wiki/ConfigWaylandSettings/[Wayland support] to the LXQt desktop.
+You can link:https://lxqt-project.org/release/2024/11/05/release-lxqt-2-1-0/[read some release highlights here].
+
+Anyone interested in helping with the project is welcome.
+
+Current version: 2.1.0
diff --git a/website/content/en/status/report-2024-10-2024-12/mac_do.adoc b/website/content/en/status/report-2024-10-2024-12/mac_do.adoc
new file mode 100644
index 0000000000..eac353656b
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/mac_do.adoc
@@ -0,0 +1,44 @@
+=== mac_do(4), setcred(2), mdo(1)
+
+Contact: Olivier Certner <olce.freebsd.statusreports@certner.fr> +
+Contact: Baptiste Daroussin <bapt@FreeBSD.org>
+
+This project aims at allowing controlled process credentials transitions without using setuid executables but instead leveraging our MAC framework.
+For an overall presentation, we refer the reader to the link:../report-2024-07-2024-09/#_mac_do4_setcred2_mdo1[previous quarter's report].
+As this is a progress report, we only recall the outline here.
+
+In a nutshell, this project comprises two components:
+
+* man:mac_do[4] is the kernel module that checks credentials transition requests and authorizes those that match rules configured by the administrator.
+* man:mdo[1] is the userland program playing the role of a mediator between processes wanting to launch other processes with changed credentials and man:mac_do[4], whose function is to authorize only specific such changes.
+man:setcred[2] is the new system call at the interface between them.
+It enables userland to request various credentials changes atomically, allowing man:mac_do[4] to base its decision on the transition between the initial and desired final credentials.
+
+Both prerequisite commits and changes in MAC/do proper have been reviewed and all commits have finally been pushed to FreeBSD's main branch, including documentation in the form of a new manual page for man:setcred[2] and changes to the man:mac_do[4] one to match the new man:sysctl[8] knobs and rules syntax.
+
+Rules can now express finely which groups are allowed in the resulting credentials for a given UID or GID, notably making it possible to specify which target primary and supplementary groups the final credentials can, or must, or must not include.
+Please consult man:mac_do[4] for a description of the new syntax and examples.
+
+Future work, in no particular order and timeframe, may include:
+
+* For the man:mac_do[4] component:
+** Currently, it can only grant credentials transitions for processes spawned from the `/usr/bin/mdo` executable.
+   The possibility to tweak this path may be interesting for custom thin jail layouts.
+   The ability to have several such paths is one of the missing pieces to be able to use man:mac_do[4] in conjunction with other credentials-granting programs such as man:sudo[1] and man:doas[1].
+** man:mac_do[4] currently can only grant new credentials if they are requested via the new man:setcred[2], as it needs to see the current and desired final credentials to make a decision.
+   However, each call to traditional and standard credentials-changing functions, such as man:setuid[2], man:seteuid[2], etc., can be considered as a (limited) full transition on its own, which man:mac_do[4] could decide upon.
+   This functionality could allow to more finely control transitions to `root` and, combined with that of the previous point, to install and use credentials-granting programs without the "setuid" bit.
+   However, the full power of this new man:mac_do[4] module version cannot be harnessed without modifying these programs to use man:setcred[2].
+* For the man:mdo[1] component:
+** The credentials transitions that can be requested are fairly limited compared to what man:mac_do[4]'s rules can allow.
+   It would be useful to make it possible to:
+*** Specify any list of target groups (primary or supplementary), possibly based on user names (with the implicit list coming from the contents of [.filename]#/etc/passwd# and [.filename]#/etc/group#) but allowing some tweaks (such as excluding a particular group in the final credentials).
+*** Allow changes of groups only.
+*** Request a password before calling man:setcred[2] in certain cases.
+    This weakens the security paradigm of the man:mac_do[4]/man:mdo[1] combination, as it would now rely on userland for part of the gating process, but seems acceptable in many cases.
+*** Grow a mode producing the target part of rules corresponding to the contents of the password and group databases for some users.
+
+We welcome any feedback on this new version and the future-work list above.
+
+Sponsor: The FreeBSD Foundation +
+Sponsor: Kumacom SARL
diff --git a/website/content/en/status/report-2024-10-2024-12/openjdk.adoc b/website/content/en/status/report-2024-10-2024-12/openjdk.adoc
new file mode 100644
index 0000000000..fe1e8b80fb
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/openjdk.adoc
@@ -0,0 +1,18 @@
+=== Improve OpenJDK on FreeBSD
+
+Links: +
+link:https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[Project description] URL: link:https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[]
+
+Contact: Harald Eilertsen <haraldei-fbsd@anduin.net>
+
+The aim of this project is to improve support for Java in FreeBSD, by working with the upstream OpenJDK community, as well as the FreeBSD community in getting the changes and additions needed for fully supporting FreeBSD accepted upstream.
+
+As this is a new project, there is not much to report yet, but here's what has been achieved so far:
+
+* The Java Test Regression harness (jtreg) now link:https://github.com/snake66/jtreg/tree/freebsd-port[builds and runs] on FreeBSD, and the process of link:https://github.com/openjdk/jtreg/pull/237[upstreaming the changes] has started.
+
+* OpenJDK 23 builds and runs on FreeBSD, and work on adding it to the ports collection has started; this is still considered experimental. link:https://reviews.freebsd.org/D48194[]
+
+* Work on porting the next OpenJDK (version 24) has started. link:https://github.com/snake66/jdk/tree/jdk24-freebsd[]
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/openstack.adoc b/website/content/en/status/report-2024-10-2024-12/openstack.adoc
new file mode 100644
index 0000000000..a0fcb116f2
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/openstack.adoc
@@ -0,0 +1,25 @@
+=== OpenStack on FreeBSD
+
+Links: +
+link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] +
+link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[]
+
+Contact: Chih-Hsin Chang <starbops@hey.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+The OpenStack on FreeBSD project aims to merge the capabilities of the OpenStack cloud infrastructure with the robust features of FreeBSD.
+Our objective is to harness FreeBSD's unique features while ensuring compatibility with OpenStack's operations.
+
+In the fourth quarter, our primary goal was to finalize the tasks promised under milestone 1 by establishing a new environment for a demonstrable Proof of Concept (POC) site.
+However, the simultaneous aim to set up another deployment based on FreeBSD Jail within the same environment led us to spend considerable time on network design and tuning.
+Fortunately, we successfully established external network connectivity for guest VMs by the end of this period.
+The remaining challenge now is to enable guest VMs to automatically acquire IP addresses through cloud-init.
+
+On another note, we attempted to obtain the domain XML of VMs from the Linux-based OpenStack to compare with the XML used for bhyve VMs.
+These domain XMLs are utilized by Libvirt, defining each virtual machine's configuration and operational parameters.
+Comparing the differences between the two will aid in developing the "bhyve serial console over TCP" work.
+
+In the first quarter of the upcoming year, we will continue to conclude the tasks related to milestone 1 of our project.
+Additionally, we will persist in developing FreeBSD Ports for OpenStack components, further integrating and enhancing the system’s capabilities.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/pinephone.adoc b/website/content/en/status/report-2024-10-2024-12/pinephone.adoc
new file mode 100644
index 0000000000..6c92fe0ade
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/pinephone.adoc
@@ -0,0 +1,24 @@
+=== Pinephone Pro Support
+Links: +
+link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[Repository on Codeberg] URL: link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[]
+
+Contact: Toby Kurien <toby@tobykurien.com>
+
+The project to port FreeBSD over to the Pinephone Pro is progressing.
+The aim of this project is to step by step support components of the Pinephone Pro in FreeBSD so that the device one day might be usable as a highly mobile FreeBSD device.
+
+In this quarter:
+
+* A driver for the RK818 power management IC was implemented, enabling the device regulators.
+* A driver for the real-time clock was also implemented, allowing the system to keep time between reboots.
+* A driver for the RK818 battery charger and battery monitor was written to allow the battery to be charged via USB, and to retrieve some battery information like voltage and charging status via sysctl.
+* The code repository has been updated with scripts and documentation on how to compile the custom kernel and device tree, and patch a FreeBSD 15-CURRENT image with them so that it boots on the Pinephone Pro.
+
+The next steps are to enable UEFI-based framebuffer support to enable output to the screen, and to enable USB on-the-go functionality, which might allow for plugging in a USB keyboard and/or Ethernet.
+Porting the Linux driver for WiFi will also be looked into.
+Any developers wanting to assist are encouraged to get in touch.
+Additional feedback and testers are welcome.
+
+Also see link:https://forums.freebsd.org/threads/porting-freebsd-to-pinephone-pro-help-needed.95948/[this thread on the FreeBSD Forum if you want to participate.]
+
+Sponsor: Honeyguide Group
diff --git a/website/content/en/status/report-2024-10-2024-12/pkg-pkgbase.adoc b/website/content/en/status/report-2024-10-2024-12/pkg-pkgbase.adoc
new file mode 100644
index 0000000000..86b3c84265
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/pkg-pkgbase.adoc
@@ -0,0 +1,34 @@
+=== PkgBase-motivated improvements to pkg
+
+Contact: Isaac Freund <ifreund@freebsdfoundation.org>
+
+Some problems blocking progress on the link:https://wiki.freebsd.org/PkgBase[PkgBase project] are caused by shortcomings of man:pkg[8].
+The primary goal of my work on pkg is to unblock PkgBase progress.
+However, all users of pkg will benefit even if they do not use PkgBase.
+
+The scheduler for pkg's install/upgrade/delete jobs has been link:https://github.com/freebsd/pkg/pull/2330[rewritten], motivated by solving link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259785[PR259785].
+The new scheduler models the scheduling problem as a directed graph and splits upgrade jobs into delete/install halves only when necessary to break a cycle in the graph.
+This formal model gives strong guarantees about ordering that the old scheduler was not able to provide and prevents unnecessary splitting of upgrade jobs.
+It also fixes longstanding bugs where the old scheduler would bail out and cause the entire upgrade to fail.
+The new scheduler is included in pkg version 1.21.99.3 (pkg-devel).
+
+The rest of my work this quarter has been related to pkg's automatic tracking of shared library dependencies, which PkgBase heavily relies on.
+The initial motivating problem was link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265061[PR265061] but it was necessary to make more fundamental changes to how pkg tracks shlibs before cleanly solving that problem became possible.
+
+When a package is created with man:pkg-create[8], pkg scans the included files and generates shlibs_provided/shlibs_required lists based on the executables/shared libraries found.
+Before my changes, pkg would use the elf hints file of the host system as an input to pkg-create in order to filter out shlibs provided by the base system from the generated shlibs_required list.
+An ALLOW_BASE_SHLIBS option disabled this filtering for the purpose of building PkgBase packages.
+
+After my changes, pkg-create no longer reads the elf hints file of the host system and base system shlibs are included in the generated shlibs_required list.
+When man:pkg-install[8]/man:pkg-upgrade[8]/etc. invoke the solver on an non-PkgBase system, pkg generates a list of shlibs provided by the base system as an input to the solver by scanning /lib and /usr/lib.
+On a PkgBase system, the PkgBase packages provide all base system shlibs.
+
+This allows the ALLOW_BASE_SHLIBS option to be eliminated.
+It also gives better integration between the ports packages and PkgBase packages as shlib dependencies of ports packages on PkgBase packages are now tracked rather than ignored.
+Finally, this change significantly simplifies the pkg codebase and improves portability.
+This change was implemented in link:https://github.com/freebsd/pkg/pull/2386[] and is not yet included in a pkg release.
+
+With that change and other link:https://github.com/freebsd/pkg/pull/2376[internal improvements] I was able to add support for tracking lib32 and Linuxulator shlibs, which should resolve the problem that originally motivated my work on pkg's shlib handling (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265061[PR265061]).
+This support is implemented in link:https://github.com/freebsd/pkg/pull/2387[] and is not yet included in a pkg release.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/portmgr.adoc b/website/content/en/status/report-2024-10-2024-12/portmgr.adoc
new file mode 100644
index 0000000000..a9c08d2f1c
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/portmgr.adoc
@@ -0,0 +1,64 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: Tobias C. Berner <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+In the last quarter, we welcomed Xavier Beaudouin (kiwi@) as a new ports committer.
+
+According to INDEX, there are currently 36,332 (down from 36,504) ports in the Ports Collection.
+There are currently about 3,368 (down from 3,379) open ports PRs, of which 809 are unassigned.
+
+The last quarter saw 10,640 commits (down from 11,594) by 155 committers (one less) on the main branch and 733 commits (down from 832) by 61 committers (down from 78) on the 2024Q4 branch.
+
+The number of ports also decreased (down from 36,504).
+
+The most active committers to main were:
+
+* 3867 sunpoet@FreeBSD.org
+* 1156 yuri@FreeBSD.org
+* 368 jbeich@FreeBSD.org
+* 361 bofh@FreeBSD.org
+* 273 fuz@FreeBSD.org
+* 247 fluffy@FreeBSD.org
+* 209 vvd@FreeBSD.org
+* 206 eduardo@FreeBSD.org
+* 201 rene@FreeBSD.org
+* 157 uzsolt@FreeBSD.org
+
+A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are:
+
+* Default version of Lazarus switched to 3.6.0
+* Default version of PHP switched to 8.3
+* Chromium 131.0.6778.204
+* Electron 33.3.0
+* Firefox 134.0
+* Firefox-esr 128.6.0
+* KDE Frameworks 6.9.0
+* KDE Plasma 6.2.4
+* Qt6 6.8.1
+* Python 3.9.21
+* Python 3.10.16
+* Python 3.11.11
+* Ruby 3.2.6
+* Ruby 3.3.6
+* Rust 1.83.0
+* SDL 2.30.10
+* SDL 3.1.6
+* Sway 1.10
+
+Three new `USES` were introduced:
+
+* `cl` to provide support for Common Lisp ports.
+* `java` to provide support for Java.
+* `sbrk` to handle ports requiring `sbrk()`
+
+During the last quarter, pkgmgr@ ran 14 exp-runs to test various ports upgrades and changes to `bsd.port.mk`.
diff --git a/website/content/en/status/report-2024-10-2024-12/ports-collection-accessibility-colors.adoc b/website/content/en/status/report-2024-10-2024-12/ports-collection-accessibility-colors.adoc
new file mode 100644
index 0000000000..bf72031d32
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/ports-collection-accessibility-colors.adoc
@@ -0,0 +1,23 @@
+=== Ports Collection Accessibility - Colors Low Vision
+
+Link: +
+link:https://wiki.freebsd.org/portconfig[Project wiki page] URL: link:https://wiki.freebsd.org/portconfig[]
+
+Contact: FreeBSD Accessibility mailing list <freebsd-accessibility@FreeBSD.org> +
+Contact: Alfonso Sabato Siciliano <asiciliano@FreeBSD.org>
+
+FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications.
+The collection provides tens of thousands of ports; port configuration is a key feature.
+It is possible to configure a port before the building and installation.
+The command "make config" uses a text user interface (TUI) to set up port options interactively.
+
+Recently low vision users (mainly with cataracts) have requested new features to easily change the colors of the TUI.
+Several features have been implemented to allow changing colors, for example: a new environment variable to set the UI to black and white, or the ability to set colors by reading a configuration file at runtime.
+All features have been described in man:portconfig[1] since version 0.6.2.
+
+To note, blind users can refer to https://www.freebsd.org/status/report-2023-07-2023-09/#_portoptscliports_collection_accessibility[PortOptsCLI - Ports Collection Accessibility, Status Report Third Quarter 2023] to use the Ports Collection.
+
+Tips and new ideas are welcome.
+If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place.
+
+Sponsored by: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/pot.adoc b/website/content/en/status/report-2024-10-2024-12/pot.adoc
new file mode 100644
index 0000000000..12cfff4313
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/pot.adoc
@@ -0,0 +1,23 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+During this quarter, there was no new link:https://github.com/bsdpot/pot[Pot] release.
+The tool is stable and used in production for quite some time already.
+
+Potluck got a new link:https://github.com/bsdpot/potluck/tree/master/netbox[Netbox] image.
+Additionally, various images have received improvements and bug fixes, e.g. improving their syslog-ng integration.
+
+Last not least, all images have been rebuilt several times: for FreeBSD 14.1, to include security fixes, then again for 14.2 and also for the new quarterly packages.
+
+As always, feedback and patches are welcome.
+
+Sponsors: Nikulipe UAB, Honeyguide Group
diff --git a/website/content/en/status/report-2024-10-2024-12/qemu_l4b.adoc b/website/content/en/status/report-2024-10-2024-12/qemu_l4b.adoc
new file mode 100644
index 0000000000..99e6fd14fc
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/qemu_l4b.adoc
@@ -0,0 +1,33 @@
+=== BSD-USER 4 LINUX
+
+Contact: Maksym Sobolyev <sobomax@FreeBSD.org>
+
+Links:
+link:https://github.com/sobomax/qemu-bsd-user-l4b[Project Page] URL: link:https://github.com/sobomax/qemu-bsd-user-l4b[] +
+link:https://github.com/sobomax/qemu_l4b[Tooling] URL: link:https://github.com/sobomax/qemu_l4b[]
+
+The `bsd-user-4-linux` project ports BSD user-mode emulation for QEMU to Linux.
+The primary goal is to enable unmodified FreeBSD binaries to run on modern Linux systems.
+Additionally, the project aims to provide multi-platform container images with a functional FreeBSD environment and ready-to-use GitHub Actions templates.
+
+Current Status:
+
+* The initial port successfully runs `make -jN buildworld`.
+* Most command-line tools are working as expected (`sh`, `bash`, `find`, `grep`, `git`, `clang`, etc).
+* A link:https://github.com/sobomax/qemu-bsd-user-l4b/actions[GitHub Actions pipeline] builds x86_64 emulation images for:
+  ** linux/386
+  ** linux/amd64
+  ** linux/arm/v5
+  ** linux/arm64/v8
+
+Next Steps:
+* Implement container integration.
+
+How You Can Help:
+
+* Test with your preferred toolchain, report issues, or contribute fixes.
+* Build and test non-x86_64 emulation images (e.g., FreeBSD/arm64 on Linux/x86_64).
+  The code works on BSD but needs testing on Linux.
+* Support us on link:https://patreon.com/sippylabs[Patreon].
+
+Sponsor: Sippy Software, Inc.
diff --git a/website/content/en/status/report-2024-10-2024-12/releng.adoc b/website/content/en/status/report-2024-10-2024-12/releng.adoc
new file mode 100644
index 0000000000..9f40821dbd
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/releng.adoc
@@ -0,0 +1,18 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/14.2R/announce/[FreeBSD 14.2-RELEASE announcement] URL: link:https://www.freebsd.org/releases/14.2R/announce/[] +
+link:https://www.freebsd.org/releases/13.5R/schedule/[FreeBSD 13.5-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.5R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+The Team managed 14.2-RELEASE, leading to the official RELEASE build and announcement in December.
+Planning has started for the upcoming 13.5-RELEASE cycle, which is expected to be the final release from the legacy *stable/13* branch; as such it will include updates to "contrib" code and some bug fixes, but is not expected to have any significant new features.
+
+In addition to previously shipped release artifacts (ISO and memory stick images, VM images, cloud offerings, etc.) the Team is now also providing OCI compatible container images.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/14*, and *stable/13* branches.
diff --git a/website/content/en/status/report-2024-10-2024-12/srcmgr.adoc b/website/content/en/status/report-2024-10-2024-12/srcmgr.adoc
new file mode 100644
index 0000000000..f617b670b6
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/srcmgr.adoc
@@ -0,0 +1,16 @@
+=== New srcmgr team
+
+Contact: srcmgr <srcmgr@FreeBSD.org>
+
+A new link:https://www.freebsd.org/administration/#t-srcmgr[source management team] has been ratified by core@ to handle management of the FreeBSD src tree, akin to portmgr@ and doceng@ for the ports and docs trees, respectively.
+The initial members are Ed Maste, Mark Johnston, John Baldwin, and Warner Losh.
+srcmgr@ is currently focused on finding ways to make src developers more productive, and to try and manage the large numbers of bug reports and pull requests that we receive.
+The team meets every two weeks to discuss src-related issues and spend time triaging bug reports and pull requests.
+link:https://github.com/freebsd/meetings/tree/master/srcmgr[Meeting minutes] are available on GitHub.
+The srcmgr@ team has a link:https://www.freebsd.org/srcmgr/charter/[charter] and is working on developing and documenting policies to help manage the src tree.
+
+In December, srcmgr@ ran an online bug-busting session, attended by 15 developers.
+We spent time going through recent bug reports, plus a list of older ones with patches.
+The team plans to host monthly sessions of this type, and aims to open them to a wider audience in the future.
+
+The team plans to develop a lurker program similar to portmgr@'s in the first half of 2025.
diff --git a/website/content/en/status/report-2024-10-2024-12/suspend.adoc b/website/content/en/status/report-2024-10-2024-12/suspend.adoc
new file mode 100644
index 0000000000..3e0c27bf65
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/suspend.adoc
@@ -0,0 +1,19 @@
+=== Suspend/Resume Improvements
+
+Links: +
+link:https://obiw.ac/s0ix/[Blog] URL: link:https://obiw.ac/s0ix/[] +
+link:https://github.com/obiwac/freebsd-s0ix[Working Branch] URL: link:https://github.com/obiwac/freebsd-s0ix[]
+
+Contact: obiwac <obiwac@freebsd.org>
+
+Suspend-to-idle and support for S0ix sleep is in the process of being added to FreeBSD.
+
+This will allow modern Intel and AMD laptops (e.g. AMD and newer Intel Framework laptops), some of which do not support ACPI S3 sleep, to enter low power states to increase battery life.
+
+Ben Widawsky from Intel started working on this in 2018 but his work was never finished and is now outdated.
+His work has now been picked up and the first goal is to get suspend/resume working on the Framework 13 AMD Ryzen 7040 series by end of January.
+There are plans for presenting initial results at a talk at FOSDEM.
+
+Currently, all device power constraints on AMD can already be parsed to enter a system's low power states.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/syzkaller.adoc b/website/content/en/status/report-2024-10-2024-12/syzkaller.adoc
new file mode 100644
index 0000000000..8b00748fe6
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/syzkaller.adoc
@@ -0,0 +1,24 @@
+=== Syzkaller Improvement on FreeBSD
+
+Links: +
+link:https://github.com/google/syzkaller[google/syzkaller] URL: link:https://github.com/google/syzkaller[] +
+
+Contact: Jian-Lin Li <ljianlin99@gmail.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+Syzkaller is an operating system kernel fuzzer that can look for vulnerabilities in the kernel.
+
+This project aims to improve the support of Syzkaller on FreeBSD.
+Based on the existing WiFi fuzzer designed for Linux, we drafted a WiFi fuzzer for FreeBSD.
+We planned to use man:wtap[4], a virtual wifi driver for testing, in order to support WiFi fuzzing.
+
+Some of the design details include:
+
+* Introduce a new netlink command to wtap in order to realize frame injection, which is essential for WiFi fuzzing.
+* Initialize wtap devices in Syzkaller before WiFi fuzzing.
+
+We are developing some prototypes and discussing the feasible design plan with some experts.
+There is not much progress yet.
+We hope to have more progress on this project in the next few months.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/torbrowser.adoc b/website/content/en/status/report-2024-10-2024-12/torbrowser.adoc
new file mode 100644
index 0000000000..ecd05f52fa
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/torbrowser.adoc
@@ -0,0 +1,31 @@
+=== Tor-Browser
+
+Links: +
+link:https://www.torproject.org/[Tor Project Homepage] URL: link:https://www.torproject.org/[] +
+link:https://gitlab.torproject.org/tpo/applications/tor-browser[GitLab Repository] URL: link:https://gitlab.torproject.org/tpo/applications/tor-browser[]
+
+Contact: Martin Filla <freebsd@sysctl.cz>
+
+Since the last report, significant progress has been made in building and packaging Tor Browser for FreeBSD.
+Additionally, the Tor Browser version has been updated to 14.0.3, which is now available from the link:https://www.torproject.org/download/[Tor Browser download page] and also from our link:https://www.torproject.org/dist/[distribution directory].
+
+This update includes important security updates to Firefox, ensuring that users benefit from enhanced security and privacy features.
+Expanding FreeBSD compatibility remains a priority to provide seamless and native privacy solutions for the platform.
+
+What is new:
+Tor Browser version 14.0.3 includes:
+
+* Rebase to Firefox 128.5.0esr.
+* Backporting of security fixes from Firefox 133.
+* Platform-specific updates such as disabling Microsoft SSO on macOS and updating GeckoView for Android.
+* Updated Go to version 1.22.9 in the build system.
+
+Help Needed:
+To move forward, assistance is required in the following areas:
+
+Code Review: Ensure patches meet the required coding and security standards.
+Testing: Volunteers are needed to test Tor Browser 14.0.3 on FreeBSD to identify edge cases.
+Bug Fixing: Developers familiar with FreeBSD and Firefox’s codebase are encouraged to resolve known issues.
+
+Feedback:
+If you find a bug or have suggestions for improving this release, please let us know through the link:https://gitlab.torproject.org/tpo/applications/tor-browser[GitLab Repository] or the provided contact email.
diff --git a/website/content/en/status/report-2024-10-2024-12/umb.adoc b/website/content/en/status/report-2024-10-2024-12/umb.adoc
new file mode 100644
index 0000000000..72745b9800
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/umb.adoc
@@ -0,0 +1,33 @@
+=== umb(4) driver for MBIM USB 4G/5G modems
+
+Links: +
+link:https://man.openbsd.org/umb[UMB(4) - OpenBSD Device Drivers Manual] URL: link:https://man.openbsd.org/umb[] +
+link:https://man.netbsd.org/umb.4[UMB(4) - NetBSD Kernel Interfaces Manual] URL: link:https://man.netbsd.org/umb.4[] +
+link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263783[Bug 263783 - USB MBIM: Support for LTE/4G USB modems] URL: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263783[] +
+link:https://reviews.freebsd.org/D48167[Introduce the USB umb(4) network driver] URL: link:https://reviews.freebsd.org/D48167[]
+
+Contact: Pierre Pronchery <pierre@freebsdfoundation.org>
+
+The Mobile Broadband Interface Model (MBIM) is a protocol for communication with network USB devices, transmitting packet data over mobile broadband networks.
+Implementing this protocol adds support for a whole range of USB devices providing connectivity to mobile networks, such as 4G, 5G, and their subsequent technological evolutions.
+
+A first implementation for this protocol was performed for OpenBSD in 2016, under the name umb(4).
+I have ported it myself to NetBSD under the same name, back in 2019.
+I was then contracted to make it work with OPNSense, and authorized to publish it as Open Source in 2022.
+Unfortunately, by this time, some changes in FreeBSD effectively broke the driver, and it could not be merged until fixed.
+
+This quarter I have managed to offer an updated version and confirmed it working (thanks Mike and Zhenlei!).
+This version is now under review in Phabricator as D48167.
+The submission is still based on code from 2020, and behind progress made by OpenBSD since that time.
+As such, it is currently restricted to IPv4.
+However, I believe it makes sense to keep the review simple and focus on the design decisions and integration, before progressively importing the improvements made upstream since then in OpenBSD (notably IPv6 support).
+
+In its current form, the driver was modified from being out of tree and available as a plug-in for OPNSense, into a kernel module and its companion binary, umbconfig(8).
+This management binary effectively allows the umb(4) driver to be configured beyond the capabilities of ifconfig(8): the PIN or PUK code, APN, username/password, or roaming parameters can be setup, and the connectivity tracked as well (network provider, speed...).
+
+Should you want to give it a spin yourself and get hardware supported by this driver, the single most important feature to look for is support for the MBIM specification.
+The manual page for OpenBSD provides a list of devices that should be compliant; note that some of them require preliminary configuration in order to effectively expose the MBIM interface.
+The exact procedure is vendor-specific, and can also depend on the model and current configuration of the device.
+You should refer to the documentation offered for your device for any steps necessary.
+
+Sponsored by: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/uvc.adoc b/website/content/en/status/report-2024-10-2024-12/uvc.adoc
new file mode 100644
index 0000000000..9421f0632b
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/uvc.adoc
@@ -0,0 +1,17 @@
+=== FreeBSD V4L2 & kernel USB Video Class driver
+
+Links: +
+link:https://github.com/AlvinChen1028/freebsd-src/tree/feature-uvc[Public development repository] URL: link:https://github.com/AlvinChen1028/freebsd-src/tree/feature-uvc[] +
+link:https://github.com/lwhsu/freebsd-src/pull/3[Upstreaming preparation repository] URL: link:https://github.com/lwhsu/freebsd-src/pull/3[]
+
+Contact: Alvin Chen <weike_chen@dell.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+This work is to create FreeBSD UVC (USB Video Class) kernel driver and follow v4l2 APIs, so that most of the Linux camera applications can be easily ported to FreeBSD.
+
+The code is still cleaning up and will be submitted to official review system after completing.
+
+The Dell ThinOS team is currently working on MIPI Webcam support, including intel XPU.
+
+Sponsor: Dell Technologies for the development +
+Sponsor: The FreeBSD Foundation for assistance of upstreaming
diff --git a/website/content/en/status/report-2024-10-2024-12/wazuh.adoc b/website/content/en/status/report-2024-10-2024-12/wazuh.adoc
new file mode 100644
index 0000000000..5632312e0b
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/wazuh.adoc
@@ -0,0 +1,36 @@
+=== Wazuh on FreeBSD
+
+Links: +
+link:https://www.wazuh.com/[Wazuh] URL: link:https://www.wazuh.com/[] +
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+Wazuh is a free and open source platform used for threat prevention, detection, and response.
+It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments.
+
+Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents.
+Besides, Wazuh has been fully integrated with the Elastic Stack or OpenSearch Stack, providing a search engine and data visualization tool that allows users to navigate through their security alerts.
+
+After a long break, ports has been updated to include Wazuh version 4.9.2.
+This version of Wazuh uses Python 3.11 instead of 3.10, and it includes some new features:
+
+* support to get ports info,
+* support to get processes info,
+* improved memory info,
+* FreeBSD decoder and rule files, and
+* link:https://github.com/alonsobsd/wazuh-freebsd[FreeBSD Security Configuration Assessment files] for 13.x, 14.x and 15-CURRENT.
+
+Also, FreeBSD ports include a custom version of wazuh-dashboard-plugins for a better integration with FreeBSD.
+
+Wazuh can easily be installed in a jail by following the link:https://github.com/AppJail-makejails/wazuh[Wazuh AppJail-Makejails] tutorial.
+
+Anyone interested in helping with the project or interested in aarch64 device donation for testing/packaging is welcome.
+
+Current version: 4.9.2
+
+TODO
+
+* Add Wazuh cluster-mode infrastructure AppJail makejails
+* Add vulnerability detection support to FreeBSD Wazuh agent
+* Add FreeBSD as officially supported platform by Wazuh Inc
+* Update FreeBSD SCA Policies to new FreeBSD CIS Benchmark
diff --git a/website/content/en/status/report-2024-10-2024-12/wireless-iwx.adoc b/website/content/en/status/report-2024-10-2024-12/wireless-iwx.adoc
new file mode 100644
index 0000000000..756cf8078e
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/wireless-iwx.adoc
@@ -0,0 +1,20 @@
+=== Wireless Update
+
+Contact: Tom Jones <thj@FreeBSD.org> +
+Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>
+
+With Support from the FreeBSD Foundation this quarter I started working on porting the iwx WiFi driver from OpenBSD (via Haiku).
+The iwx driver supports many of the chipsets supported by iwlwifi, but rather than make that driver more complex the OpenBSD developers decided to support these devices in a new driver.
+
+iwx on OpenBSD currently supports running as a station in 80211abgn and ac, it does not yet support ax rates.
+The goals of this project are to import a maintainable driver from OpenBSD and to gradually increase support until we have a native driver in FreeBSD with support for 80211ac (and potentially 80211ax).
+
+Currently the driver supports 80211a and 80211g and is able to saturate the practical limits of the rates these standards offers (roughly 28Mbit down and 25 Mbit up).
+The driver is under active development and moving quite quickly.
+
+The plan for the next quarter is to add support for high throughput rates, implement monitor mode and stabilise the driver for a public call for testing.
+
+Once the driver is stable enough a call for testing will be posted to the link:https://lists.freebsd.org/subscription/freebsd-current[freebsd-current] and link:https://lists.freebsd.org/subscription/freebsd-wireless[freebsd-wireless] mailing lists.
+
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2024-10-2024-12/xfce.adoc b/website/content/en/status/report-2024-10-2024-12/xfce.adoc
new file mode 100644
index 0000000000..6e822d7608
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/xfce.adoc
@@ -0,0 +1,20 @@
+=== Xfce on FreeBSD
+
+Links: +
+link:https://xfce.org/about/news/?post=1734220800[Xfce 4.20 Upstream Release Announcement] URL: link:https://xfce.org/about/news/?post=1734220800[] +
+link:https://www.freshports.org/x11-wm/xfce4[Xfce meta-port on FreshPorts] URL: link:https://www.freshports.org/x11-wm/xfce4[]
+
+Contact: Xfce team <xfce@FreeBSD.org> +
+Contact: Guido Falsi <madpilot@FreeBSD.org>
+
+The FreeBSD Xfce team (xfce@) works to ensure the Xfce desktop environment is maintained and fully functional on FreeBSD.
+
+This quarter the Xfce team members are pleased to welcome Xfce 4.20 to the FreeBSD ports tree!
+
+This new release adds many stability improvements and some new functionality.
+
+Upstream work for this release was focused on getting the code base ready for Wayland support.
+
+This release brings experimental Wayland support, although not all components have been migrated, so it may not work for you.
+
+For further details, refer to the link:https://xfce.org/about/news/?post=1734220800[Xfce 4.20 Upstream Release Announcement].
diff --git a/website/content/en/status/report-2025-01-2025-03/_index.adoc b/website/content/en/status/report-2025-01-2025-03/_index.adoc
new file mode 100644
index 0000000000..5de7013d72
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/_index.adoc
@@ -0,0 +1,244 @@
+---
+title: "FreeBSD Status Report First Quarter 2025"
+sidenav: about
+---
+
+= Introduction
+:doctype: article
+:toc: macro
+:toclevels: 2
+:icons: font
+:!sectnums:
+:source-highlighter: rouge
+:experimental:
+:reports-path: content/en/status/report-2025-01-2025-03
+
+include::content/en/status/categories-desc.adoc[]
+
+include::{reports-path}/intro.adoc[]
+
+'''
+
+toc::[]
+
+
+'''
+
+[[FreeBSD-Team-Reports]]
+== FreeBSD Team Reports
+
+{FreeBSD-Team-Reports-desc}
+
+'''
+
+include::{reports-path}/core.adoc[]
+
+'''
+
+include::{reports-path}/freebsd-foundation.adoc[]
+
+'''
+
+include::{reports-path}/releng.adoc[]
+
+'''
+
+include::{reports-path}/clusteradm.adoc[]
+
+'''
+
+include::{reports-path}/ci.adoc[]
+
+'''
+
+include::{reports-path}/portmgr.adoc[]
+
+'''
+
+include::{reports-path}/bugmeister.adoc[]
+
+'''
+
+include::{reports-path}/srcmgr.adoc[]
+
+'''
+
+[[projects]]
+== Projects
+
+{projects-desc}
+
+'''
+
+include::{reports-path}/foundation-infrastructure-modernization.adoc[]
+
+'''
+
+include::{reports-path}/pkgbasify.adoc[]
+
+'''
+
+include::{reports-path}/framework.adoc[]
+
+'''
+
+include::{reports-path}/hackathon.adoc[]
+
+'''
+
+include::{reports-path}/sylve.adoc[]
+
+'''
+
+[[userland]]
+== Userland
+
+{userland-desc}
+
+'''
+
+include::{reports-path}/jailmeta.adoc[]
+
+'''
+
+[[kernel]]
+== Kernel
+
+{kernel-desc}
+
+'''
+
+include::{reports-path}/audio.adoc[]
+
+'''
+
+include::{reports-path}/drm-drivers.adoc[]
+
+'''
+
+include::{reports-path}/suspend.adoc[]
+
+'''
+
+include::{reports-path}/syzkaller-wifi.adoc[]
+
+'''
+
+include::{reports-path}/lkpi-wireless.adoc[]
+
+'''
+
+include::{reports-path}/wireless-iwx.adoc[]
+
+'''
+
+[[architectures]]
+== Architectures
+
+{architectures-desc}
+
+'''
+
+include::{reports-path}/pinephone.adoc[]
+
+'''
+
+[[cloud]]
+== Cloud
+
+{cloud-desc}
+
+'''
+
+include::{reports-path}/azure.adoc[]
+
+'''
+
+include::{reports-path}/buildpacks.adoc[]
+
+'''
+
+include::{reports-path}/ec2.adoc[]
+
+'''
+
+[[documentation]]
+== Documentation
+
+{documentation-desc}
+
+'''
+
+include::{reports-path}/doceng.adoc[]
+
+'''
+
+include::{reports-path}/wiki.adoc[]
+
+'''
+
+include::{reports-path}/vision-accessibility-handbook.adoc[]
+
+'''
+
+[[ports]]
+== Ports
+
+{ports-desc}
+
+'''
+
+include::{reports-path}/bhyvemgr.adoc[]
+
+'''
+
+include::{reports-path}/container-orchestration.adoc[]
+
+'''
+
+include::{reports-path}/gcc.adoc[]
+
+'''
+
+include::{reports-path}/ipv6-support-on-ng_ksocket.adoc[]
+
+'''
+
+include::{reports-path}/kde.adoc[]
+
+'''
+
+include::{reports-path}/openbgpd-fix-fib-handling.adoc[]
+
+'''
+
+include::{reports-path}/openjdk.adoc[]
+
+'''
+
+include::{reports-path}/wazuh.adoc[]
+
+'''
+
+[[third-Party-Projects]]
+== Third Party Projects
+
+{third-Party-Projects-desc}
+
+include::{reports-path}/cfc.adoc[]
+
+'''
+
+include::{reports-path}/discord.adoc[]
+
+'''
+
+include::{reports-path}/framework-kmod.adoc[]
+
+'''
+
+include::{reports-path}/ldwg.adoc[]
+
+'''
+
+include::{reports-path}/pot.adoc[]
diff --git a/website/content/en/status/report-2025-01-2025-03/audio.adoc b/website/content/en/status/report-2025-01-2025-03/audio.adoc
new file mode 100644
index 0000000000..d4fb6b1d54
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/audio.adoc
@@ -0,0 +1,37 @@
+=== Audio Stack Improvements
+
+Contact: Christos Margiolis <christos@FreeBSD.org>
+
+I have been working on the audio stack since 2024Q1. Below is a list of the previous status reports:
+
+* link:https://www.freebsd.org/status/report-2024-01-2024-03/#_audio_stack_improvements[2024Q1]
+* link:https://www.freebsd.org/status/report-2024-04-2024-06/#_audio_stack_improvements[2024Q2]
+* link:https://www.freebsd.org/status/report-2024-07-2024-09/#_audio_stack_improvements[2024Q3]
+* link:https://www.freebsd.org/status/report-2024-10-2024-12/#_audio_stack_improvements[2024Q4]
+
+Important work since link:https://www.freebsd.org/status/report-2024-10-2024-12/#_audio_stack_improvements[last report]:
+
+* Large refactor in man:sound[4]'s format conversion framework: link:https://cgit.freebsd.org/src/commit/?id=433e270f341cf660b2fe125c2e0f733073829188[433e270f341c].
+  Further simplifications and refactors in the rest of the processing chain.
+* Implemented link:https://cgit.freebsd.org/src/commit/?id=e1bbaa71d62c8681a576f9f5bedf475c7541bd35[AFMT_FLOAT] support.
+* More out-of-the-box laptop support, especially Framework models.
+* Virtual channels are now allocated on-demand: link:https://cgit.freebsd.org/src/commit/?id=02d4eeabfd73e6a827f5d42601e99aad92060b04[02d4eeabfd73]
+* Re-implementing `/dev/dsp` as a virtual/router device: link:https://reviews.freebsd.org/D49216[D49216].
+  Apart from the standalone benefits of this change, it will also help us improve automatic sound redirection in man:snd_hda[4].
+* More man:sound[4] cleanups, fixes and improvements.
+* New virtual_oss release: https://github.com/freebsd/virtual_oss/releases/tag/v1.3.2
+* Got my audio-related BSDCan 2025 talk proposal accepted.
+* Put porting SOF to FreeBSD on the backburner for now.
+  See link:https://lists.freebsd.org/archives/freebsd-multimedia/2025-March/002889.html[here] for an explanation.
+* In contact with potential GSOC students interested in link:https://wiki.freebsd.org/SummerOfCodeIdeas#Port_virtual_oss_to_base[porting virtual_oss to base].
+
+Future work includes:
+
+* Finish currently open tasks.
+* More bug fixes, support, optimizations and general improvements, in all areas of the sound stack.
+* Get back to link:https://reviews.freebsd.org/D46227[audio(8)]
+* Implement a generic MIDI layer, similar to pcm/, and improve/modernize the MIDI codebase in general.
+
+You can also follow the development process in link:https://lists.freebsd.org/subscription/freebsd-multimedia[freebsd-multimedia@], where I post regular reports.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/azure.adoc b/website/content/en/status/report-2025-01-2025-03/azure.adoc
new file mode 100644
index 0000000000..0e8e97ecaf
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/azure.adoc
@@ -0,0 +1,35 @@
+=== FreeBSD on Microsoft HyperV and Azure
+
+Links: +
+link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] +
+link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[]
+
+Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> +
+Contact: link:https://lists.freebsd.org/subscription/freebsd-cloud[freebsd-cloud Mailing List] +
+Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> +
+Contact: Wei Hu <whu@FreeBSD.org>, <weh@microsoft.com> +
+Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+In this quarter, we have published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-13_5[13.5-RELEASE on Azure Marketplace].
+
+Wei Hu continues bug fixing for FreeBSD MANA NIC device.
+
+Work in progress tasks:
+
+* Automating the image publishing process and merging to [.filename]#src/release/#.
+* Making the process of publishing to Azure Marketplace more smoothly.
+* Support FreeBSD in link:https://github.com/Azure/azure-vm-utils/[Azure VM utilities].
+
+Open tasks:
+
+* Update FreeBSD-related doc at link:https://learn.microsoft.com[Microsoft Learn]
+* Update package:sysutils/azure-agent[] to the latest version
+* Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent]
+* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure]
+* Adding FreeBSD support in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines]
+** link:https://github.com/microsoft/azure-pipelines-agent/pull/3266[]
+** Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery].
+
+Sponsor: Microsoft for people in Microsoft, and for resources for the rest +
+Sponsor: The FreeBSD Foundation for everything else
diff --git a/website/content/en/status/report-2025-01-2025-03/bhyvemgr.adoc b/website/content/en/status/report-2025-01-2025-03/bhyvemgr.adoc
new file mode 100644
index 0000000000..d0214f3788
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/bhyvemgr.adoc
@@ -0,0 +1,43 @@
+=== A bhyve management GUI written in Freepascal/Lazarus
+
+Links: +
+link:https://github.com/alonsobsd/bhyvemgr[Bhyvemgr] URL: link:https://github.com/alonsobsd/bhyvemgr/[] +
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+Bhyvemgr is a bhyve management GUI written in Freepascal/Lazarus on FreeBSD.
+It needs a bunch of tools mostly installed on base system and some installed from ports/packages.
+The main goal is to be a desktop application focus on desktop user to easily and quickly setup and run virtual machines on FreeBSD hosts.
+
+During this quarter, there were many bugfixes and improvements to Bhyvemgr.
+
+These are some highlights that were added:
+
+- Improve aarch64 support
+- RDP Login form keeps data of resolution and username used on previous connection while bhyvemgr is running
+- Support for selecting TCP remote connection at com1 of LPC device
+- Fix zombie process bug when xfreerdp and remote-viewer are running from bhyvemgr.
+  Now bhyvemgr uses Tthread instead of only TProcess for it
+- VM name and com1 connection strings can be copied to clipboard from Virtual Machine popup menu
+- Now xfreerdp3 loads arguments from rdp.args file
+- Re-use device forms.
+  It avoids to consume memory each time that device forms are opened/used
+- Network device name can be added/modified manually from Network device form.
+  Take on mind that valid names are tapX or vmnetX (e.g tap0, vmnet0)
+- Log messages support
+
+Bhyvemgr supports aarch64 only on 15-CURRENT and amd64 from FreeBSD 13.x to 15-CURRENT.
+Also, bhyvemgr can be compiled or installed from link:https://www.freshports.org/sysutils/bhyvemgr[ports] or pkg binaries with gtk2, qt5 or qt6 interface support.
+
+A big thank to link:https://www.entersekt.com/[Entersekt] for sponsor my work.
+Now I can use a RockPro64 (aarch64) for testing bhyvemgr on aarch64.
+
+People interested in helping or supporting the project are welcome.
+
+Current version: 1.5.0
+
+TODO
+
+* Add uart device support
+
+Sponsor: Entersekt
diff --git a/website/content/en/status/report-2025-01-2025-03/bugmeister.adoc b/website/content/en/status/report-2025-01-2025-03/bugmeister.adoc
new file mode 100644
index 0000000000..75320b8a9d
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/bugmeister.adoc
@@ -0,0 +1,53 @@
+=== Bugmeister Team
+
+Links: +
+link:https://wiki.freebsd.org/Bugzilla[FreeBSD Bugzilla] URL: link:https://wiki.freebsd.org/Bugzilla[]
+
+Contact: Bugmeister <bugmeister@FreeBSD.org>
+
+In this quarter we made major progress on Base System PRs, closing over 1,000 old ones that no longer apply.
+Many of these were detected by carefully going over all entries in [.filename]#ObsoleteFiles.inc#.
+
+Also in this quarter we came even closer to steady-state for ports/doc; we are dealing with incoming PRs more quickly these days.
+For reference: link:https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90[].
+
+The overall number of PRs came down from slightly over 11,000 to just under 10,000.
+This was due to work from several people to go over entire groups of PRs.
+
+Mark Linimon attended several video calls with various src committers.
+They are doing some experimentation to learn what kind of effort is sustainable.
+The most recent effort was to evaluate the latest incoming src PRs; you will note that many of them from the past few weeks have been marked as requesting feedback.
+
+Bugmeister folks also did some passes through the database to clean up metadata:
+
+- re-checked bugs for Product: Base System, Status: In Progress.
+  A few of these were not being actively worked on.
+  The count is essentially holding at 186.
+  The concept is to make sure "In Progress" has some real meaning.
+
+- edited up the 'application/mbox' patches to be 'text/plain', which Bugzilla is then able to understand.
+
+- obsoleted many stale patches where more than one patch was in the PR.
+
+The "automate harvesting PRs and evaluating whether they still apply" task has resulted in the release of link:https://github.com/linimon/patchQA[patchQA.py] as beta.
+The program can take either a number (as a single PR number), or, with some work, a full REST query.
+
+The main current problem is that the py-patch algorithm does not correctly handle fuzz.
+Until this is fixed, it will stay in beta.
+
+Almost all of the PRs with patches have been processed by patchQA.py and several hundreds of them have been rebased (e.g. Base System patches to be relative to the top of the src tree).
+We now have a sense of how many Ports patches are not actually patches to the FreeBSD port itself, but instead need to be manually applied to an extracted work/ directory.
+A script to try to automate this is in alpha.
+
+The other problem known with patchQA.py is that it does not know the origins of files that are installed into /etc by installworld.
+
+However, it does know enough to internally rebase Ports patches to the ports tree base if necessary.
+
+We also created 120+ new Bugzilla accounts by user request.
+(We no longer create them automatically because of the spammers.)
+
+Clusteradm@ helped us fend off yet more crawler sites.
+OTOH, we seem to be losing the war against AI bots.
+
+See also: link:https://wiki.freebsd.org/Bugzilla/SearchQueries[]
+
diff --git a/website/content/en/status/report-2025-01-2025-03/buildpacks.adoc b/website/content/en/status/report-2025-01-2025-03/buildpacks.adoc
new file mode 100644
index 0000000000..828b3d10b9
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/buildpacks.adoc
@@ -0,0 +1,26 @@
+=== Containers and FreeBSD: Cloud Native Buildpacks
+
+Links: +
+link:https://buildpacks.io/[Cloud Native Buildpacks (CNBs)] URL: link:https://buildpacks.io/[] +
+link:https://github.com/buildpacks/pack[GitHub Buildpacks repository] URL: link:https://github.com/buildpacks/pack[]
+
+Contact: Robert Gogolok <gogolok@gmail.com>
+
+link:https://buildpacks.io/[Cloud Native Buildpacks (CNBs)] transform application source code into container images.
+Those images can run on any cloud.
+With buildpacks, organizations can concentrate the knowledge of container build best practices within a specialized team, instead of having application developers across the organization individually maintain their own Dockerfiles.
+
+My goal for this quarter was to enable building the tool link:https://buildpacks.io/docs/for-platform-operators/how-to/integrate-ci/pack/[pack] on FreeBSD.
+
+With the following changes, it is now possible to compile `pack` on FreeBSD:
+
+* link:https://github.com/buildpacks/pack/pull/2337[Remove obsolete // +build lines #2337]
+* link:https://github.com/buildpacks/pack/pull/2339[Use unix build constraint #2339]
+* link:https://github.com/buildpacks/pack/pull/2357[Support FreeBSD build phase #2357]
+
+The next steps are:
+
+- Provide missing FreeBSD functionality to `lifecycle` and `pack`.
+- Further investigate FreeBSD as a build target in `lifecycle`.
+- Provide `lifecycle` and/or `pack` via FreeBSD ports.
+- Investigate the idea of FreeBSD buildpacks for some popular languages, similar to link:https://paketo.io/[paketo buildpacks].
diff --git a/website/content/en/status/report-2025-01-2025-03/cfc.adoc b/website/content/en/status/report-2025-01-2025-03/cfc.adoc
new file mode 100644
index 0000000000..969fc97024
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/cfc.adoc
@@ -0,0 +1,44 @@
+=== Chinese FreeBSD Community (CFC)
+
+link:https://bsdcn.org/[Chinese FreeBSD Community (CFC)] URL: link:https://bsdcn.org/[]
+
+Community member count: QQ group 249 members, WeChat group 175 members
+
+==== FreeBSD-Ask
+
+Links: +
+link:https://github.com/FreeBSD-Ask/FreeBSD-Ask[FreeBSD-Ask on GitHub] URL: link:https://github.com/FreeBSD-Ask/FreeBSD-Ask[] +
+link:https://book.bsdcn.org/[FreeBSD-Ask on Website] URL: link:https://book.bsdcn.org/[]
+
+Contact: ykla <yklaxds@gmail.com> +
+Contact: Voosk <roisfrank@icloud.com>
+
+*FreeBSD-Ask* is an open-source FreeBSD introductory guide written in Simplified Chinese, initiated by ykla from the Chinese FreeBSD Community (CFC).
+*FreeBSD-Ask* was established on March 14, 2021.
+
+Updates in this quarter:
+
+* Added:
+  ** Installing package:x11/budgie[]
+  ** package:sysutils/bsdconfig[] System Configuration Tool
+  ** Installing package:x11-wm/fluxbox[]
+  ** Installing package:x11-wm/icewm[]
+  ** Installing package:net-mgmt/prometheus2[]
+  ** package:security/py-fail2ban[] (Based on IPFW, PF, IPF)
+  ** Installing package:x11-wm/windowmaker[]
+  ** Manual Dual-Boot Installation (Installing FreeBSD First)
+  ** Installing FreeBSD - Based on Apple M1 & Parallels Desktop 20
+  ** Command Line Basics
+  ** Installing package:zabbix7-server[] (Based on PostgreSQL)
+  ** etc.
+
+* Rewritten:
+  ** Installing package:ftp/pure-ftpd[] (Based on MySQL)
+  ** Installing package:ftp/proftpd[] (Based on MySQL)
+  ** Installing package:ftp/vsftpd[]
+
+* Added several GitHub Actions, such as automatic PDF generation, dead link checking, etc.
+
+As always, feedback and patches are welcome.
+
+Sponsors: Chinese FreeBSD Community (CFC)
diff --git a/website/content/en/status/report-2025-01-2025-03/ci.adoc b/website/content/en/status/report-2025-01-2025-03/ci.adoc
new file mode 100644
index 0000000000..fca95f19f2
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/ci.adoc
@@ -0,0 +1,50 @@
+=== Continuous Integration
+
+Links: +
+link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] +
+link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://tinderbox.freebsd.org[] +
+link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] +
+link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] +
+link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] +
+link:++https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals++[Tickets related to freebsd-testing@] URL: link:++https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals++[] +
+link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] +
+link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[]
+
+Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] +
+Contact: IRC #freebsd-ci channel on EFNet
+
+In the first quarter of 2025, we worked with the project contributors and developers to address their testing requirements.
+Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD.
+
+Important completed tasks:
+
+* Add jobs to build amd64 main, stable/14, and stable/13 with GCC 14 (jhb@)
+* Working with intern students to fix the failing and skipped test cases (lwhsu@)
+* Upgrade and switch the Jenkins server to LTS version.
+* Participate the Foundation's Sovereign Tech Agency (STA) work package C: improve the project's CI/CD
+
+Work in progress tasks:
+
+* Designing and implementing pre-commit CI building and testing and pull/merge-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group])
+** Improving the [.filename]#src/tests/ci# work to support running test suites
+*** Merging link:https://reviews.freebsd.org/D48015[CI: Add full test support]
+** Merging link:https://reviews.freebsd.org/D36257[Pre-commit CI with CIRRUS-CI]
+* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds
+* Simplifying CI/test environment setting up for contributors and developers
+* Setting up the CI stage environment and putting the experimental jobs on it
+* Redesigning the hardware test lab and adding more hardware for testing
+
+Open or queued tasks:
+
+* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas]
+* Setting up public network access for the VM guest running tests
+* Implementing use of bare-metal hardware to run test suites
+* Adding drm-kmod ports building tests against -CURRENT
+* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI])
+* Working with hosted CI providers to have better FreeBSD support
+
+Please see link:++https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals++[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort!
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/clusteradm.adoc b/website/content/en/status/report-2025-01-2025-03/clusteradm.adoc
new file mode 100644
index 0000000000..1e54e5e0b9
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/clusteradm.adoc
@@ -0,0 +1,62 @@
+=== Cluster Administration Team
+
+Links: +
+link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[]
+
+Contact: Cluster Administration Team <clusteradm@FreeBSD.org>
+
+FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications.
+
+In this quarter, the team has worked on the following:
+
+* Regular support for FreeBSD.org user accounts.
+* Regular disk and parts support (and replacement) for all physical hosts and mirrors.
+* Cluster software refresh.
+* Moving more cluster services to Chicago.
+* Supporting the Grimoirelab dashboard effort.
+* Coordinate community mirrors.
+
+==== Moving cluster services to Chicago
+
+We started building up our new site in Chicago 2024, with a long-term goal to have Chicago as our primary location.
+Since 2024Q4, we began decommissioning older machines in New Jersey and moving services to the newer machines in Chicago.
+In 2025Q1, we started upgrading critical services in the cluster and testing to setup in Chicago.
+
+==== Git web interface mirrors
+
+While the project's public read-only git repository is built by a globally distributed mirror, the web interface (cgit) is not.
+We found there is increasing requirement of accessing it, and for improving the response time and reliability, we setup the cgit on the mirrors around the world.
+
+==== FreeBSD official mirrors
+
+Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America -- California, Chicago, New Jersey (primary site), and Washington.
+
+Our mirror site in Taiwan is experiencing an extended outage.
+The effort of bringing it back is in progress.
+We hope to have it back online during the second quarter of 2025.
+
+The hardware and network connection have been generously provided by:
+
+* Cloud and SDN Laboratory at link:https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc]
+* link:https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University]
+* link:https://deploy.equinix.com/[Equinix]
+* link:https://internet.asn.au/[Internet Association of Australia]
+* link:https://www.isc.org/[Internet Systems Consortium]
+* link:https://www.inx.net.za/[INX-ZA]
+* link:https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc]
+* link:https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network]
+* link:https://www.metapeer.com/[MetaPeer]
+* link:https://www.nyi.net/[New York Internet]
+* link:https://nic.br/[NIC.br]
+* link:https://sonic.net[Sonic]
+* link:https://www.teleservice.net/[Teleservice Skåne AB]
+* link:https://your.org/[Your.Org]
+
+New official mirrors are always welcome.
+We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa.
+If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us.
+We are particularly interested in locations on the United States West Coast and throughout Europe.
+
+See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site.
+
+Sponsors: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/container-orchestration.adoc b/website/content/en/status/report-2025-01-2025-03/container-orchestration.adoc
new file mode 100644
index 0000000000..275da2aec3
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/container-orchestration.adoc
@@ -0,0 +1,22 @@
+=== Container orchestration: Overlord, Director and AppJail
+
+Links: +
+link:https://github.com/DtxdF/AppJail[AppJail on GitHub] URL: link:https://github.com/DtxdF/AppJail[] +
+link:https://github.com/DtxdF/Director[Director on GitHub] URL: link:https://github.com/DtxdF/Director[] +
+link:https://github.com/DtxdF/Overlord[Overlord on GitHub] URL: link:https://github.com/DtxdF/Overlord[]
+
+Contact: Jesús Daniel Colmenares Oviedo <DtxdF@disroot.org>
+
+**AppJail** is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application.
+
+**Director** is a tool for running multi-jail environments on AppJail using a simple YAML specification.
+A Director file is used to define how one or more jails that make up your application are configured.
+Once you have a Director file, you can create and start your application with a single command: `appjail-director up`.
+
+**Overlord** is a fast, distributed orchestrator for FreeBSD jails oriented to GitOps.
+You define a file with the service intended to run on your cluster and deployment takes seconds to minutes.
+This orchestration tool uses AppJail, Director and can even create VMs with vm-bhyve, but as its philosophy is "deploy using code" you can create a single file once and deploy many times.
+Through a tree chaining system Overlord deploys jails on connected systems sharing their resources almost infinitely.
+See the link:https://github.com/DtxdF/Overlord/wiki[wiki] for articles that use Overlord.
+
+Sponsor: https://www.patreon.com/appjail
diff --git a/website/content/en/status/report-2025-01-2025-03/core.adoc b/website/content/en/status/report-2025-01-2025-03/core.adoc
new file mode 100644
index 0000000000..cca1b176af
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/core.adoc
@@ -0,0 +1,20 @@
+=== FreeBSD Core Team
+
+Contact: FreeBSD Core Team <core@FreeBSD.org>
+
+The FreeBSD Core Team is the governing body of FreeBSD.
+
+==== Project roadmap
+
+Core is collecting ideas and comments to draft Project's roadmap.
+It is an item core.13 thinks is worth to continue from core.12.
+The roadmap is not about restricting or limiting what developers and contributors can do, but about the compiled goals and expectations of the Project and things the community can collaborate on.
+It will also let the FreeBSD Foundation help the Project more effectively, so, this is an important discussion item for the meetings between core and the FreeBSD Foundation.
+
+==== Work in Progress
+
+Core is currently working on the following items:
+
+* Policy on generative AI created code and documentation
+* Core and the FreeBSD Foundation are working on the 2025 edition of the Community survey
+* Privacy-friendly web analytics, proposed by the Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/discord.adoc b/website/content/en/status/report-2025-01-2025-03/discord.adoc
new file mode 100644
index 0000000000..a40b10ba28
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/discord.adoc
@@ -0,0 +1,52 @@
+=== FreeBSD Discord Server
+
+Links: +
+link:https://wiki.freebsd.org/Discord/DiscordServer[Discord Server] URL: link:https://wiki.freebsd.org/Discord/DiscordServer[]
+
+Contact: Setesh Strong <setesh.strong@gmail.com>
+
+The FreeBSD Community Discord server has grown to over 5.3K members, with over 3K members active in the last month.
+To help support our community’s health and pursue growth in project contribution and engagement, the BSDlabs group developed the Helper program, more than two years ago now.
+After several phases of growth, we have reached the point where the team has thrived enough that it has become necessary to divide it into three distinct functional teams.
+
+Our community health and culture helpers (@moderators) are led by Alexander Vereeken.
+Our newcomer onboarding and training helpers (@mentors) are led by mailto:ziaee@FreeBSD.org[Alexander Ziaee].
+Our event organizer and outreach helpers (@organizers) are led by Ahmad Abdulla.
+
+Since the creation of the new teams, all of our helpers have been hard at work, driving growth within the areas of their remit within the program.
+We are proud to share some of the outcomes of their efforts with you, as well as several of the areas of focus and objectives we will tackle in the upcoming quarter.
+
+Antranig Vartanian led the development of our recurring series of Ask the Greybeards AMAs (Ask Me Anything) with the support of other veteran sysadmins and developers.
+This recurring event provides an opportunity for users and those still gaining mastery of our platform to meet and learn from the depth of experience our community offers.
+Special thanks to mailto:dexter@FreeBSD.org[Michael Dexter] and many others for their engagement and support of this event.
+Your expertise and skills help nurture the future of our ecosystem.
+
+Significant progress into onboarding new contributors has occurred through the efforts of the newcomer helper team under Alexander Ziaee’s leadership.
+His work has brought newly increased activity to our docs tree.
+
+At the request of mailto:imp@FreeBSD.org[Warner Losh], we have created a workspace for #google-summer-of-code on the server.
+This space provides a location for those engaged with GSoC to ask questions and receive feedback and assistance.
+In further pursuit of our desire to bridge between silos, we are in the process of establishing a matterbridge bot.
+This will serve to connect with the #freebsd-gsoc IRC channel, as well as other potential links in the future with FreeBSD’s IRC and Matrix communities.
+
+We are proud to welcome developers working on FreeBSD’s wifi stack to our server.
+We have created the #wifi-hacking workspace to facilitate their efforts.
+Special thanks to mailto:adrian@FreeBSD.org[Adrian Chadd] for bringing this opportunity to us, and leading the way in the thriving activity in this workspace.
+
+We are currently in the process of developing our new Co-op Study Club, driven by the leadership of mailto:jsm@FreeBSD.org[Jesper Schmitz Mouridsen].
+This will provide members of our community with the opportunity to build their skills in side-by-side study, under the guidance of our newcomer helper team.
+As a project driven study group, it will develop our members’ passions into strengths, while building comfort and familiarity with contributing to the project via porting, src development, and documentation testing and patching.
+Experienced mentorship will be on hand to provide learning resources for those who join this study group, answer questions that cannot be answered by peer support, and aiding in overcoming blockers.
+Our objective is to provide a roadmap and environment for achieving excellence as both developers and FreeBSD contributors.
+
+Thanks to the efforts of community helper Jessica Hawkwell, with the support of events team leader Ahmad Abdulla, we have seen the addition of a #foss-ecosystem channel.
+This development marks the beginning of the process of bridging between the various silos, both within the FreeBSD community, and in the larger FOSS ecosystem.
+If you want us to add a link to your segment of the community and it is not already contained in our directory in this channel, please reach out to us.
+
+In addition to the existing tools afforded by Discord for our server, we are currently in the process of upgrading and expanding our infrastructure.
+This effort focuses on ensuring the availability of Discord bot infrastructure and tooling, as well as restoring etherpad and dpaste functionality for collaboration.
+We seek to improve support for all of the dedicated developers within the workspaces of our community.
+
+If you are a member of the FreeBSD ecosystem and have not yet connected to our Discord presence, we invite you to do so via the invite link available on the wiki at the top of this report.
+If you have experience or passion for any of the areas of our current helper teams, or a passion for Discord bot infrastructure development, we would love to have you on our teams.
+We invite you to contact us via the above contact email, or by sending a DM on Discord (@setesh.strong).
diff --git a/website/content/en/status/report-2025-01-2025-03/doceng.adoc b/website/content/en/status/report-2025-01-2025-03/doceng.adoc
new file mode 100644
index 0000000000..cceef962af
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/doceng.adoc
@@ -0,0 +1,117 @@
+////
+Quarter:	1st
+Prepared by:	fernape
+Reviewed by:	
+Last edit:	$Date$
+Version:	$Id:$
+////
+
+=== Documentation Engineering Team
+
+Links: +
+link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/url[] +
+link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/url[] +
+link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-docengurl[]
+
+Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>
+
+The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter].
+
+==== Document changes
+
+===== Handbook
+
+ * The Filesystems chapter has been reworked.
+ * The information about official mirrors have been updated.
+ * Multiple examples have been updated including vnet, jails, git, etc.
+
+===== Porter's Handbook
+
+The following `USES` were documented:
+
+ * `ansible`
+ * `angr`
+ * `apache`
+ * `azurepy`
+ * `electronfix`
+ * `elixir`
+ * `emacs`
+ * `fpc`
+ * `jpeg`
+ * `kodi`
+ * `lazarus`
+ * `mlt`
+ * `mpi`
+ * `ocaml`
+ * `trigger`
+ * `waf`
+
+New variables were documented for `USES=samba`:
+
+ * `SAMBA_TALLOC_PORT`,
+ * `SAMBA_TDB_PORT`
+ * `SAMBA_TEVENT_PORT`
+
+===== Website
+ * Manual pages for NetBSD 10.1 have been added.
+ * Manual pages for Rocky Linux 8.10, 9.4 and 9.5 have been added.
+ * Manual pages for FreeBSD 13.5 have been added.
+ * Pages for OpenSolaris 2010.03 have been added.
+
+==== FreeBSD Translations on Weblate
+
+Links: +
+link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblateurl[] +
+link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/url[]
+
+===== Q1 2025 Status
+
+* 18 team languages
+* 246 registered users
+
+7 new translators joined Weblate:
+
+* Squirrel-hue (ES, ES_CL)
+* Javier Faig (ES)
+* Сергей (RU)
+* Renan Birck Pinheiro (PT)
+* Davi Rodrigues (PT)
+* laiis akibo
+* Raoul Taddei (FR_FR)
+
+===== Languages
+
+* Chinese (Simplified) (zh-cn)	(progress: 7%)
+* Chinese (Traditional) (zh-tw)	(progress: 3%)
+* Dutch (nl) 			(progress: 1%)
+* French (fr)			(progress: 1%)
+* German (de)			(progress: 1%)
+* Greek (el)			(progress: 1%)
+* Indonesian (id)		(progress: 1%)
+* Italian (it)			(progress: 4%)
+* Korean (ko)			(progress: 30%)
+* Norwegian (nb-no)		(progress: 1%)
+* Persian (fa-ir)		(progress: 2%)
+* Polish			(progress: 2%)
+* Portuguese			(progress: 0%)
+* Portuguese (pt-br)		(progress: 23%)
+* Spanish (es)			(progress: 36%)
+* Turkish (tr)			(progress: 2%)
+
+We want to thank everyone that contributed, translating or reviewing documents.
+
+And please, help promote this effort on your local user group, we always need more volunteers.
+
+==== Packages maintained by DocEng
+
+During this quarter the following work was done in packages maintained by doceng@:
+
+ * package:www/gohugo[]: updated to 0.145.0
+
+==== Open issues
+
+There are no open PRs assigned to doceng@.
+
+During this quarter the following PR was closed:
+
+ * link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276923[276923] www/gohugo link error under poudriere
diff --git a/website/content/en/status/report-2025-01-2025-03/drm-drivers.adoc b/website/content/en/status/report-2025-01-2025-03/drm-drivers.adoc
new file mode 100644
index 0000000000..22fbcd663e
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/drm-drivers.adoc
@@ -0,0 +1,36 @@
+=== DRM drivers
+
+Links: +
+link:https://github.com/freebsd/drm-kmod/pull/332[Update to Linux 6.7 DRM drivers] URL: https://github.com/freebsd/drm-kmod/pull/332[] +
+link:https://github.com/freebsd/drm-kmod/pull/344[Update to Linux 6.8 DRM drivers] URL: https://github.com/freebsd/drm-kmod/pull/344[]
+
+Contact: Jean-Sébastien Pédron <dumbbell@FreeBSD.org>
+
+DRM drivers are **kernel drivers for integrated and discrete GPUs**.
+They are maintained in the Linux kernel and we port them to FreeBSD.
+As of this report, we take the AMD and Intel DRM drivers only (NVIDIA FreeBSD drivers are proprietary and provided by NVIDIA themselves).
+
+We usually port them one Linux version at a time.
+This allows us to ship updates more often and it eases porting and debugging because we have a smaller delta compared to a bigger jump skipping several versions.
+
+This quarter, we **ported DRM drivers from Linux 6.7 and 6.8**.
+This effort did not hit the Ports tree yet because several patches to the FreeBSD kernel (the `linuxkpi` compatibility layer specifically) are still being reviewed and improved.
+
+So far, the feedback was good for GPUs that were already supported by previous versions of the drivers.
+For newer GPUs, especially Intel ones, panics and display corruptions were reported.
+At this point, it is difficult to say if we just miss fixes from Linux that were published in a later version, or if these issues are actual bugs on FreeBSD.
+
+These updates target the FreeBSD 15-CURRENT development branch for now.
+Once kernel patches are accepted and the DRM drivers updates merged, we will evaluate if/how we can backport the kernel patches to earlier release branches (namely 14-STABLE).
+
+If you want to try them, you will find instructions to build and install a kernel with the non-committed changes, the drivers and the firmwares, in the pull requests’ descriptions.
+
+The next steps are:
+
+1. Finish the polishing of kernel patches and commit them
+2. Review and merge the DRM drivers updates
+3. Evaluate a backport of the kernel patches to release branches to allow to use these updates on older versions of FreeBSD.
+
+This work is kindly sponsored by the FreeBSD Foundation as part of the Laptop and Desktop Project.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/ec2.adoc b/website/content/en/status/report-2025-01-2025-03/ec2.adoc
new file mode 100644
index 0000000000..78535e422d
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/ec2.adoc
@@ -0,0 +1,14 @@
+=== FreeBSD on EC2
+
+Links: +
+link:https://www.daemonology.net/freebsd-ec2-boot-performance/[EC2 Boot performance over time] URL: link:https://www.daemonology.net/freebsd-ec2-boot-performance/[]
+
+Contact: Colin Percival <cperciva@FreeBSD.org>
+
+FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances.
+
+In the past quarter, considerable effort has gone into making "hot unplug" (e.g. detaching EBS volumes) work correctly, with several different fixes required on different instance types.
+This is expected to be fully functional in the upcoming FreeBSD 14.3.
+
+Sponsor: Amazon +
+Sponsor: https://www.patreon.com/cperciva
diff --git a/website/content/en/status/report-2025-01-2025-03/foundation-infrastructure-modernization.adoc b/website/content/en/status/report-2025-01-2025-03/foundation-infrastructure-modernization.adoc
new file mode 100644
index 0000000000..e06ab5d2be
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/foundation-infrastructure-modernization.adoc
@@ -0,0 +1,41 @@
+=== Infrastructure Modernization
+
+Contact: Ed Maste <emaste@FreeBSD.org> +
+Contact: Alice Sowerby <alice@freebsdfoundation.org>
+
+The project started in Q3 of 2024 and was commissioned by the Sovereign Tech Agency with a budget of $745,000, to be spent over about one year.
+The main goals are to improve security tools for the base system, ports, and packages, update the project's infrastructure to speed up development, enhance build security, and make it easier for new developers to get started.
+
+==== Q1 update
+Three of the five work packages are now in progress, with the remaining two to start in April.
+The overall schedule has been re-planned to run through to December 2025, allowing for a more sustainable pace of work.
+
+===== Work Package A: Technical Debt reduction
+The Foundation and the FreeBSD Project's Source Management team is working together to make bug management easier and more sustainable.
+There is now a link:https://grimoire.freebsd.org[bug backlog dashboard], which helps make the backlog easier to understand during "bug busting" sessions, and is already showing that more bugs are being closed than being opened.
+This is hosted on FreeBSD and link:https://github.com/chaoss/grimoirelab/blob/main/FreeBSD.md[documentation] has been submitted upstream to the GrimoireLab project so others can do the same.
+
+One way to learn more about the project is to listen to the link:https://podcast.chaoss.community/103[CHAOSScast episode] where we talked about this work package.
+
+We have also been upgrading Bugzilla by applying patches from 2023 onward and improving the upgrade process to ensure smoother future updates.
+
+===== Work Package B: Zero Trust Builds
+Much of the foundational work has been completed to standardize all source release build cases using no-root for creation of release artifacts.
+We are formalizing and documenting make world and [.filename]#release.sh# to provide joined-up documentation for users.
+In order to get src to build reproducibly we are creating CI tests and are working with link:https://reproducible-builds.org[Reproducible-Builds.org] to restore the link:https://tests.reproducible-builds.org/freebsd/freebsd.html[FreeBSD reproducible CI].
+Read their link:https://reproducible-builds.org/reports/2025-02/[February report].
+
+===== Work Package C: CI/CD Automation
+The high-level goal is to improve CI/CD automation to streamline software delivery and operations for new and existing software.
+Work so far is focusing on:
+
+* Improving the quality of incoming commits by providing system-agnostic tooling and documentation so that maintainers and developers can run CI without requiring a 3rd-party service (link:https://reviews.freebsd.org/D48015[]).
+* Making it possible to run pre-merge CI on proposed submissions (e.g. Pull Requests) (link:https://reviews.freebsd.org/D36257[]).
+* Documenting the CI management process to make it easier to keep tooling up to date and patched.
+* Updating the Source and Ports tests to include standard linters and other relevant automated analysis tools.
+
+===== Work Package D: Security Controls in Ports and Packages and Work Package E: Improve Software Bill of Materials (SBOM)
+These work packages are scheduled to start in April.
+The Foundation has been collaborating with FreeBSD Project teams to scope the projects appropriately.
+
+Commissioning body: Sovereign Tech Agency
diff --git a/website/content/en/status/report-2025-01-2025-03/framework-kmod.adoc b/website/content/en/status/report-2025-01-2025-03/framework-kmod.adoc
new file mode 100644
index 0000000000..4f5455ac12
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/framework-kmod.adoc
@@ -0,0 +1,31 @@
+=== Framework Kernel Module
+
+Links: +
+link:https://github.com/christian-moerz/framework-kmod[GitHub] URL: https://github.com/christian-moerz/framework-kmod[] +
+link:https://bugs.freebsd.org/285448[Bugzilla] URL: https://bugs.freebsd.org/285448[]
+
+Contact: Chris Moerz <freebsd@ny-central.org>
+
+The development of the `framework-kmod` kernel module originated from discussions and collaborative efforts within the link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[FreeBSD Laptop and Desktop Workgroup (LDWG)].
+This module addresses a specific need for dynamic screen dimming functionality, particularly suited for environments where full-featured desktop environments are not in use.
+
+The primary feature of the framework-kmod kernel module is to dynamically dim the screen when the computer is not in use and to restore brightness upon detecting user activity.
+This functionality is designed to enhance power efficiency and user experience, especially in minimalistic setups.
+
+By default, the module dims the screen very aggressively, dimming it after approximately one second of inactivity.
+This behavior ensures immediate power savings but may need adjustment based on user preferences.
+The module's settings can be customized through sysctls, allowing users to tailor the behavior to their needs.
+Users can set different brightness levels for the dimmed and bright states, adjust the length of time that needs to pass without any input signal before dimming the screen, and apply different settings depending on whether the laptop is running on a power outlet or battery.
+Brightness levels can also be adjusted through the use of the keyboard's brightness control keys.
+
+The module tracks input signals through man:evdev[4].
+If no input is detected within the set timeout period, the screen brightness is reduced.
+Upon detecting user input, the brightness is immediately restored to the previous level.
+The module requires drm-kmod drivers to be loaded in advance, ensuring compatibility with the necessary graphics drivers.
+
+The framework-kmod is not a general-purpose screen dimming driver.
+It is specifically designed for use with tty consoles or simple window managers like suckless' dwm or i3.
+Users of full-featured desktop environments like Gnome or KDE are advised to use the built-in screen dimming functions provided by those environments.
+
+The development of this module was driven by the needs identified during LDWG calls, highlighting the collaborative nature of the workgroup.
+A link:https://bugs.freebsd.org/285448[port of the framework-kmod] has been submitted, making it accessible for broader use and further development by the FreeBSD community.
diff --git a/website/content/en/status/report-2025-01-2025-03/framework.adoc b/website/content/en/status/report-2025-01-2025-03/framework.adoc
new file mode 100644
index 0000000000..30a6b3f847
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/framework.adoc
@@ -0,0 +1,22 @@
+=== Framework Laptop support
+
+Links: +
+link:https://wiki.freebsd.org/Laptops/Framework_Laptop/[Framework Laptop page on FreeBSD Wiki] URL: https://wiki.freebsd.org/Laptops/Framework_Laptop/[] +
+link:https://github.com/FrameworkComputer/freebsd-on-framework[Guide on installing and using FreeBSD on Framework systems] URL: https://github.com/FrameworkComputer/freebsd-on-framework[] +
+link:https://bugs.freebsd.org/262152[Tracking ticket: Framework Laptop: Feature support, bugs and improvements] URL: https://bugs.freebsd.org/262152[]
+
+Contact: Daniel Schaefer <dhs@frame.work> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> +
+Contact: Sheng-Yi Hong <aokblast@FreeBSD.org>
+
+For a long time, Framework Computer Inc. has been very supportive of the FreeBSD project in many ways, including providing engineering samples to the Foundation for testing and working on compatibility.
+
+The Foundation continues to work on improving overall laptop support, and Framework laptops are one of the link:https://github.com/FreeBSDFoundation/proj-laptop/blob/main/supported/laptops.md[target platforms] for the link:https://github.com/FreeBSDFoundation/proj-laptop/[Laptop Support and Usability Project].
+
+In March, some FreeBSD developers visited Framework's Taipei office again to test FreeBSD on pre-release Framework products, the Framework Desktop and Framework Laptop 12.
+The results of these tests will be used to help shape FreeBSD's development plans, and the FreeBSD support status will be updated in document after further verification.
+
+Sheng-Yi is using the laptop provided by Framework Computer to add more device support, e.g. https://reviews.freebsd.org/D49587[hwpstate: add CPPC support for pstate driver on AMD].
+
+Sponsor: The FreeBSD Foundation for Li-Wen and Sheng-Yi's work +
+Sponsor: Framework Computer Inc for Daniel's work, hardware and space support
diff --git a/website/content/en/status/report-2025-01-2025-03/freebsd-foundation.adoc b/website/content/en/status/report-2025-01-2025-03/freebsd-foundation.adoc
new file mode 100644
index 0000000000..c14ef0336f
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/freebsd-foundation.adoc
@@ -0,0 +1,120 @@
+=== FreeBSD Foundation
+
+Links: +
+link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] +
+link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] +
+link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] +
+link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] +
+link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] +
+link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[]
+
+Contact: Deb Goodkin <deb@FreeBSDFoundation.org>
+
+The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to advancing FreeBSD through technical and non-technical support.
+Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters.
+The following report covers just some of the ways we supported FreeBSD in Q1
+
+Deb Goodkin here.
+Is it Q2 already?
+Last quarter was a whirlwind of activity supporting the FreeBSD Project and community.
+In our report, we will highlight the work we are currently doing to ensure that FreeBSD stays viable and secure for the long term.
+
+As you know, the Foundation is here to support the project in many ways, including software development, security, legal, conferences, and infrastructure.
+I want to keep this section short, because we have reports throughout this status report to get more details on the work we are doing.
+
+Here is a snapshot of what we worked on last quarter, by the numbers:
+
+* 2024 funding raised (final amount is determined by February or March): $1,524,259
+* Q1 2025 fundraising: $211,000
+* Active software development projects: 20+
+* Number of commits: 456
+* Amount of technical content published: 8
+* Conferences sponsored/attended: 2
+* Foundation employees: 7
+* Foundation contractors: 19
+* Foundation's 25th Anniversary: We are thrilled to celebrate 25 years of supporting the FreeBSD Project and community!
+
+Exciting News: Mark Phillips joined the Foundation as our Technical Marketing Manager.
+Get prepared for some information and helpful technical content coming your way!
+We also brought on another part-time developer who stepped into our Solutions Specialist role.
+We will announce that person soon.
+
+==== Advocacy
+
+In the first quarter of 2025, the Foundation continued its work to support and promote FreeBSD.
+In addition to our regular activities such as publishing educational and informational content, attending events, and providing travel grants to help FreeBSD contributors participate in conferences we also welcomed a new team member.
+Mark Phillips joined us in March as our Technical Marketing Manager.
+With a background in engineering and a passion for storytelling, Mark describes himself as "an engineer by training, a marketer by chance."
+He has already made connections within the FreeBSD community, and we are excited to see his impact grow.
+To learn more about Mark, visit our link:https://freebsdfoundation.org/about-us/our-team/[team page].
+
+Other highlights of our Q1 2025 advocacy efforts include:
+
+* Helped represent FreeBSD at FOSDEM 2025.
+  Check out the link:https://freebsdfoundation.org/blog/advocating-for-freebsd-a-fosdem-2025-trip-report/[trip report].
+* Began planning the link:https://wiki.freebsd.org/DevSummit/202506[June 2025 FreeBSD Developer Summit], taking place June 11-12, 2025, co-located with link:https://www.bsdcan.org/2025[BSDCan 2025].
+  Registration is now open
+* Finalized our Silver Sponsorship of BSDCan and opened the link:https://freebsdfoundation.org/what-we-do/grants/travel-grants/[BSDCan 2025 Travel Grant Application].
+* Provided updates and announcements about our Software Development work including:
+** link:https://freebsdfoundation.org/blog/zero-trust-builds-for-freebsd/[Zero-Trust Builds for FreeBSD]
+** link:https://freebsdfoundation.org/blog/improvements-to-the-freebsd-ci-cd-systems/[Improvements to the FreeBSD CI/CD systems]
+** link:https://freebsdfoundation.org/blog/laptop-support-and-usability-project-update-first-monthly-report-community-initiatives/[Laptop Support and Usability Project Update: First Monthly Report & Community Initiatives]
+** link:https://freebsdfoundation.org/blog/january-2025-laptop-support-and-usability-project-update/[January 2025 Laptop Support and Usability Project Update]
+** link:https://freebsdfoundation.org/blog/february-2025-laptop-support-and-usability-project-update/[February 2025 Laptop Support and Usability Project Update]
+** link:https://freebsdfoundation.org/blog/openzfs-raid-z-expansion-a-new-era-in-storage-flexibility/[OpenZFS RAID-Z Expansion: A New Era in Storage Flexibility]
+* Participated in CHAOSScast Episode: GrimoireLab at FreeBSD.
+  Learn more at: link:https://freebsdfoundation.org/blog/from-chaos-to-clarity-how-we-tackled-freebsds-7000-bug-backlog/[From Chaos to Clarity: How We Tackled FreeBSD's 7,000 Bug Backlog]
+* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/19851/[January 2025] and link:https://freebsdfoundation.org/news-and-events/newsletter/february-2025-newsletter/[February 2025] FreeBSD Foundation Newsletters.
+* Released the link:https://freebsdfoundation.org/our-work/journal/browser-based-edition/virtualization-2/[November/December 2024] issue of the FreeBSD Journal with HTML versions of the articles.
+
+==== OS Improvements
+
+The FreeBSD Foundation continued to support two major projects this quarter.
+
+The Foundation's Laptop Support and Usability project began in Q4 of 2024 and is funded by the FreeBSD Foundation and link:https://www.ql-research.com/[Quantum Leap Research].
+It has a budget of $750,000, which will be used over one to two years.
+The goal is to deliver its public roadmap to improve key features like WiFi, audio usability, suspend and resume functions, graphics, and Bluetooth.
+The team will also create clear documentation and step-by-step guides to help people use the new features.
+Work done this quarter includes improvements to the pkg package manager and pkgbase installation, suspend/resume, USB debugging, newer WiFi standards and drivers, updated graphics drivers, performance/efficiency using heterogeneous cores, support for virtual and non-standard audio devices, and integrating donated code to support UVC webcam drivers.
+Refer to these dedicated report entries for details:
+
+* <<_audio_stack_improvements,Audio Stack Improvements>>
+* <<_automatic_pkgbase_conversion_tool,Automatic pkgbase conversion tool>>
+* <<_drm_drivers,DRM drivers>>
+* <<_linuxkpi_802_11_wireless_update,LinuxKPI 802.11 Wireless Update>>
+* <<_suspendresume_improvement,Suspend/Resume Improvements>>
+* <<_wireless_update,Wireless Update>>
+
+The other major project, commissioned by the link:https://www.sovereign.tech/[Sovereign Tech Agency] is to modernize FreeBSD's infrastructure.
+To learn more about the project and the updates from this quarter, refer to the <<_infrastructure_modernization,Infrastructure Modernization report entry>>.
+
+Updates are available for three other projects in separate report entries:
+
+* <<_improve_openjdk_on_freebsd,Improve OpenJDK on FreeBSD>>
+* <<_sylvea_unified_system_management_platform_for_freebsd,Sylve -- A Unified System Management Platform for FreeBSD>>
+* <<_vision_accessibilityaccessibility_handbook,Vision Accessibility and the Accessibility Handbook>>
+
+Overall, there were 346 `src`, 96 `ports`, and 14 `doc` tree commits identifying the FreeBSD Foundation as a sponsor.
+A sampling of that work includes:
+
+* Enhancements to SMBIOS handling, including favoring version 3 (64-bit) entry points, adding diagnostics, and improving code robustness
+* Ongoing work to optimize memory usage during early VM initialization
+* Continued development toward supporting heterogeneous CPU cores
+* Enabling USB driver support for the Allwinner D1 SoC
+* Improvements to man:makefs[8] for generating reproducible `cd9660` images
+
+The Foundation is managing FreeBSD’s participation in the link:https://summerofcode.withgoogle.com/[Google Summer of Code (GSoC)] program.
+At the end of February, we were excited to learn that FreeBSD was once again selected as a mentoring organization for GSoC 2025.
+That marks our 21st consecutive year in the program.
+We received 64 applications, and we will learn which projects will be awarded slots on May 8.
+
+==== Continuous Integration and Workflow Improvement
+
+As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to <<_continuous_integration,improving the Project's continuous integration system and test infrastructure>>.
+
+==== Legal/FreeBSD IP
+
+The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them.
+We also provide legal support for the core team to investigate questions that arise.
+
+Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you!
diff --git a/website/content/en/status/report-2025-01-2025-03/gcc.adoc b/website/content/en/status/report-2025-01-2025-03/gcc.adoc
new file mode 100644
index 0000000000..0c91355edc
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/gcc.adoc
@@ -0,0 +1,20 @@
+=== GCC on FreeBSD
+
+Links: +
+link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] +
+link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] +
+link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] +
+link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[] +
+link:https://gcc.gnu.org/gcc-14/[GCC 14 release series] URL: link:https://gcc.gnu.org/gcc-14/[]
+
+Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>
+
+The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281091[exp-run to update GCC default version from 13 to 14] has been suspended.
+Indeed it has been noticed that FreeBSD 13.4 lacks symbols that are used by GCC 14 for linking, please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284499#c0 for a more detailed explanation.
+The symbols are however already present in higher FreeBSD version.
+Since FreeBSD 13.4 is expected to go out of support soon (on June 30th), it has been decided that it is preferable to suspend the exp-run until then.
+I plan to put it back on track on July 1st.
+
+In the meantime, work is being done on bugs.
+Bugs link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276070[276070] and https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284441[284441] have been fixed.
+At the time this report is written, some bugs are being discussed addressing special values of the CPUTYPE variable, please see for example https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285711[285711].
diff --git a/website/content/en/status/report-2025-01-2025-03/hackathon.adoc b/website/content/en/status/report-2025-01-2025-03/hackathon.adoc
new file mode 100644
index 0000000000..16ed6d10b8
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/hackathon.adoc
@@ -0,0 +1,50 @@
+=== Hackathon 202503 Tokyo, Japan
+
+Links: +
+link:https://wiki.freebsd.org/Hackathon/202503[Hackathon/202503 Wiki Page] URL: link:https://wiki.freebsd.org/Hackathon/202503[]
+link:https://wiki.freebsd.org/Hackathon[FreeBSD Hackathon Wiki Page] URL: link:https://wiki.freebsd.org/Hackathon[]
+
+Before the link:https://hackmd.io/@AsiaBSDCon/2025lite[AsiaBSDCon-Lite 2025] event, some members of the community gathered and held a hackathon in Tokyo.
+
+Thanks to Christoff Visser and Internet Initiative Japan Inc. who sponsored the venue.
+
+==== The work done or progressed in the hackathon
+
+===== Sheng-Yi Hung
+
+- man:ipheth[4]: The iPhone tethering uses NCM on newer iOS, modified man:ipheth[4] to supporting it.
+  Patch: link:https://reviews.freebsd.org/D49431[]
+- Sccahe for FreeBSD base: the FreeBSD base supports ccache to cache the build result.
+  For cross machine build, we need a distributed cache mechanism -- that is -- sccache.
+  In Hackathon, the patch for adding sccache support is created: link:https://reviews.freebsd.org/D49417[]
+
+===== Kristof Provost
+
+Wrote a test case for bsnmpd’s snmp_pf module.
+This revealed that the BEGEMOT-PF-MIB.txt MIB file could not be parsed by bsnmpwalk, which was also fixed.
+Commits: gitref:712309a64512c7e4ebf0e10de8a5c59d5a185ae8[repository=src], gitref:c849f533326026501c28cb2c344b16723862551a[repository=src] and gitref:36586800803d24f1137d861bbaf487a6bde16a09[repository=src]
+
+===== Aymeric Wibo
+
+- Got writing to config space of USB4 routers working and successive reads on AMD USB4 controllers.
+- First steps to suspending USB4 routers.
+- Put up a bunch of preliminary patches regarding the USB4 stuff.
+- Tried passing through USB4 devices to Linux guest to suspend them (did not work).
+
+===== Mark Johnston
+
+- Worked on various syzkaller reports, e.g.: gitref:fe7fe3b175b626dd1402cd06745b1e3f070c3edd[repository=src]
+- Looked for races in pf after getting some vague bug reports from the OPNsense developers and, with Gleb and Kristof, found and fixed a rare race which could cause a use-after-free: gitref:8efd2acf07bc0e1c3ea1f7390e0f1cfb7cf6f86c[repository=src]
+
+===== Philip Paeps
+
+- Fixed the libtrue website -- we now have libtrue.so :-)
+- Worked on clusteradm technical debt
+- Good progress on our LDAP update
+- Updated a couple of internal machines
+
+===== Li-Wen Hsu
+- Project's Git infrastructure improvements, including system updating, maintenance scripts and git hooks fixes
+- Plan the cluster goals and roadmap for 2025 and longer with Philip Paeps
+
+Sponsor: Christoff Visser and Internet Initiative Japan Inc. for the venue
diff --git a/website/content/en/status/report-2025-01-2025-03/intro.adoc b/website/content/en/status/report-2025-01-2025-03/intro.adoc
new file mode 100644
index 0000000000..f6f5877d2e
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/intro.adoc
@@ -0,0 +1,13 @@
+Here is the first 2025 status report, with 40 entries.
+
+As we step into a new year, the FreeBSD community continues its work with unwavering speed, intent, and purpose.
+
+The first quarter has been remarkable, with numerous reports highlighting progress across various areas.
+Engaging with the community through forums, mailing lists, and conversations has revealed to me more advancements than can ever be captured in a single quarterly report.
+
+We extend our heartfelt thanks to everyone who submitted reports and helped raise awareness of our activities.
+Your contributions are invaluable in showcasing our collective efforts.
+
+Let us build on the success of 2024 and make this the best year yet for FreeBSD and our community!
+
+Chris Moerz, on behalf of the Status Team.
diff --git a/website/content/en/status/report-2025-01-2025-03/ipv6-support-on-ng_ksocket.adoc b/website/content/en/status/report-2025-01-2025-03/ipv6-support-on-ng_ksocket.adoc
new file mode 100644
index 0000000000..5b8d59dc10
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/ipv6-support-on-ng_ksocket.adoc
@@ -0,0 +1,20 @@
+=== IPv6 Support on ksocket Netgraph Module
+
+Links: +
+link:https://reviews.freebsd.org/D48204[Add IPv6 support for address parsing and unparsing in ng_ksocket] URL: link:https://reviews.freebsd.org/D48204[]
+
+Contact: Seyed Pouria Mousavizadeh Tehrani <info@spmzt.net>
+
+Support for IPv6 has been added to the man:ng_ksocket[4] module.
+
+The `ng_ksocket` node type allows users to open a socket inside the kernel and have it appear as a `netgraph` node.
+While attempting to export traffic flow using man:ng_netflow[4], I recognized the need for IPv6 implementation within the `ng_ksocket` module.
+
+There was a previous attempt to add IPv6 support to the `ng_ksocket` module (see Phabricator review link:https://reviews.freebsd.org/D23788[D23788]).
+
+After looking into those changes, I decided to complete the efforts and also add validation to comply with standards.
+
+The result is now available as an link:https://reviews.freebsd.org/D48204[updated review on Phabricator].
+
+Now, we can create IPv6 sockets using the ksocket module directly within the `netgraph` framework.
+After my changes, I was able to export my traffic flows directly using `netgraph` without the need to enable IPv4 on my network links.
diff --git a/website/content/en/status/report-2025-01-2025-03/jailmeta.adoc b/website/content/en/status/report-2025-01-2025-03/jailmeta.adoc
new file mode 100644
index 0000000000..b87553624c
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/jailmeta.adoc
@@ -0,0 +1,29 @@
+=== Jail metadata feature
+
+Links: +
+link:https://cgit.freebsd.org/src/commit/?id=30e6e008bc06385a66756bebb41676f4f9017eca[The main commit] URL: link:https://cgit.freebsd.org/src/commit/?id=30e6e008bc06385a66756bebb41676f4f9017eca[]
+
+Contact: Igor Ostapenko <igoro@FreeBSD.org> +
+Contact: Dave Cottlehuber <dch@FreeBSD.org>
+
+The `meta` and `env` new parameters of man:jail[8] have been introduced.
+Each one is an arbitrary string associated with a jail.
+It can be set upon jail creation or added/modified later:
+
+  # jail -cm ... meta="tag1=value1 tag2=value2" env="configuration"
+
+The values are not inherited from the parent jail.
+A parent jail can read both metadata parameters, while a child jail can read only `env` via the newly added `security.jail.env` sysctl.
+
+The maximum size of `meta` or `env` per jail is controlled by the global `security.jail.meta_maxbufsize` sysctl.
+Decreasing it does not alter the existing meta information.
+
+Each metadata buffer can optionally be handled as a set of `key=value\n` strings:
+
+  # jail -cm ... meta="$(echo k1=v1; echo k2=v2)" env.1=one
+  # jls meta.k2 env.1 meta.k1
+
+While `meta.k1=""` or `meta.k1=` resets the value to an empty string, the `meta.k1` without the equal sign removes the given key.
+The flua's libjail has been updated respectively to support the key-based handling.
+
+Sponsor: SkunkWerks GmbH
diff --git a/website/content/en/status/report-2025-01-2025-03/kde.adoc b/website/content/en/status/report-2025-01-2025-03/kde.adoc
new file mode 100644
index 0000000000..c5cc1a3749
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/kde.adoc
@@ -0,0 +1,32 @@
+=== KDE on FreeBSD
+
+Links: +
+link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] +
+link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[]
+
+Contact: KDE on FreeBSD Mailing List <kde@FreeBSD.org>
+
+The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree.
+The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine.
+The mailto:kde@FreeBSD.org[KDE team] is part of mailto:desktop@FreeBSD.org[desktop@], building the software stack to make FreeBSD beautiful and usable as a daily driver graphical desktop workstation.
+
+
+==== It Goes to 6!
+
+The KDE ports have caught up with the current generation of upstream development and now deliver up-to-date KDE Frameworks 6, KDE Plasma 6, and KDE Gear.
+Where possible, the default version of every KDE application has been updated to a recent one that uses KDE Frameworks 6.
+Many Qt-based applications have also been updated to default to a Qt6 flavor.
+
+This positions FreeBSD alongside OpenBSD and Linux distributions with a modern KDE experience.
+
+Qt5 remains in the ports tree.
+KDE Frameworks 5 remain in the ports tree for some consumers.
+Qt5 reaches end-of-life from its upstream on May 26, 2025, so it is not recommended for use.
+KDE Frameworks 5 is in a similar security-only maintenance mode.
+
+Thanks to makc@, arrowd@, and kenrap@ for landing this KDE update in ports.
+
+==== Infrastructure
+
+* CMake received several patch-level updates
+* Qt and PySide (the Python bindings for Qt) were updated to 6.8.2
diff --git a/website/content/en/status/report-2025-01-2025-03/ldwg.adoc b/website/content/en/status/report-2025-01-2025-03/ldwg.adoc
new file mode 100644
index 0000000000..a7eebf1cf6
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/ldwg.adoc
@@ -0,0 +1,44 @@
+=== Laptop and Desktop Work Group (LDWG)
+
+Links: +
+link:https://lists.freebsd.org/archives/freebsd-desktop/[Desktop mailing list] URL: link:https://lists.freebsd.org/archives/freebsd-desktop/[] +
+link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[Wiki Page] URL: link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[] +
+link:https://www.youtube.com/watch?v=U9SdSkfqH9U&list=PLugwS7L7NMXwHlYfDKNMXwJrjFrYVA9ca[YouTube] URL: https://www.youtube.com/watch?v=U9SdSkfqH9U&list=PLugwS7L7NMXwHlYfDKNMXwJrjFrYVA9ca[]
+
+Contact: Chris Moerz <freebsd@ny-central.org>
+
+The FreeBSD Laptop and Desktop Workgroup (LDWG) has continued its dedicated efforts throughout the first quarter.
+
+LDWG holds monthly meetings to discuss the state of FreeBSD on laptops and desktops and to review progress.
+These meetings are scheduled every second Monday at 5 PM UTC.
+The next meeting is set for Wednesday, May 14, at 10 AM PST / 1 PM EDT / 5 PM UTC.
+
+A survey has been initiated to explore alternative calling options that would enable participants from APAC regions to join the calls more conveniently.
+
+All calls are now available on YouTube, allowing broader access for interested parties to stay updated on the group's activities.
+
+The group's participants have made notable advancements in several areas:
+
+* ***Audio Improvements:*** Enhancements have been made to improve audio quality.
+* ***Documentation:*** Significant improvements have been made to the documentation, making it more comprehensive and user-friendly.
+* ***Wireless Speed and Stability:*** Efforts have led to better wireless speed and stability, enhancing overall connectivity.
+
+All activities are meticulously documented on the group's worksheet.
+LDWG encourages anyone interested in contributing to add their name to the worksheet.
+If there is any planned or ongoing work, participants are welcome to include it in the worksheet.
+
+The established LDWG's call agenda includes:
+
+* ***News Updates:*** Sharing news around FreeBSD on desktops and laptops, including work not otherwise covered by the workgroup.
+* ***FreeBSD Foundation Laptop Project:*** The project continues to progress well, with reports highlighting the need for volunteers to support testing efforts and the formation of a UX test group.
+* ***Project Reviews and Announcements:*** Reviewing and presenting progress, announcing new projects, and calling for actions.
+* ***Q&A Sessions:*** Providing a platform to ask questions about ongoing projects; serving as a rallying point to organize developers, users, and stakeholders on focus areas.
+
+LDWG is working to improve the call's agenda in collaboration with the Enterprise Working Group.
+Both groups face the challenge of having more areas of interest and work streams than available resources.
+Therefore, a process is being developed to ensure that available time is spent on matters that have the required resources and attention.
+
+The group is open to anyone interested in the matter.
+We welcome anyone who wants to join the group and/or calls to do so.
+
+Hope to see you there!
diff --git a/website/content/en/status/report-2025-01-2025-03/lkpi-wireless.adoc b/website/content/en/status/report-2025-01-2025-03/lkpi-wireless.adoc
new file mode 100644
index 0000000000..8ba182ee6a
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/lkpi-wireless.adoc
@@ -0,0 +1,25 @@
+=== LinuxKPI 802.11 Wireless Update
+
+Contact: Bjoern A. Zeeb <bz@FreeBSD.org> +
+Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>
+
+With multiple wireless projects ongoing, this report focuses on the efforts using permissively licensed Linux wireless drivers mostly unmodified on FreeBSD.
+The currently supported drivers are man:iwlwifi[4], man:rtw88[4], and man:rtw89[4].
+
+The man:rtw88[4] driver was made to work (associate) again (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283142[Bugzilla PR#283142]).
+In addition, thanks to the massive help debugging and testing by the community, the cause for leaking memory got resolved (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903[Bugzilla PR#283903]).
+
+Tunables to selectively control HT and VHT support in man:rtw88[4], and man:rtw89[4] were added.
+HW crypto offload was enabled by default for CCMP.
+It turns out that a lot of users are still using TKIP.
+Work is in on the way to support this and will hopefully land early in Q2.
+
+HT (11n) and VHT (11ac) support are now also compiled in by default for the LinuxKPI based drivers.
+The drivers and entire framework changes were merged from main to stable/14 so both branches have the same level of support.
+
+People installing firmware using man:fwget[8] will get HT and VHT automatically enabled for man:iwlwifi[4] 2200 (mostly AX200), AX210, and BE200 chipset generations.
+Older man:iwlwifi[4] chipset generations, man:rtw88[4], and man:rtw89[4] will need extra work in LinuxKPI or the driver to provide working support.
+
+It was announced that man:iwlwififw[4] will follow man:rtw88[4], and man:rtw89[4] firmware and be removed from the base system in April 2025 for both main and stable/14 in favor of the ports based solution and man:fwget[8] support (link:https://lists.freebsd.org/archives/freebsd-stable/2025-March/002763.html[Announcement]).
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/openbgpd-fix-fib-handling.adoc b/website/content/en/status/report-2025-01-2025-03/openbgpd-fix-fib-handling.adoc
new file mode 100644
index 0000000000..231d3930b0
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/openbgpd-fix-fib-handling.adoc
@@ -0,0 +1,15 @@
+=== OpenBGPd Fix FIB handling on FreeBSD
+
+Links: +
+link:https://undeadly.org/cgi?action=article;sid=20250207192657[OpenBGPD 8.8 released] URL: https://undeadly.org/cgi?action=article;sid=20250207192657[] +
+link:https://github.com/openbgpd-portable/openbgpd-portable/pull/93[Fix crash on interface destroy] URL: link:https://github.com/openbgpd-portable/openbgpd-portable/pull/93[]
+
+Contact: Seyed Pouria Mousavizadeh Tehrani <info@spmzt.net>
+
+This work fixes FIB handling on FreeBSD when an interface is destroyed.
+
+I encountered this issue on one of our OpenBGPd-enabled FreeBSD servers, where destroying an interface caused all our BGP sessions to drop due to a crash in OpenBGPd.
+
+I decided to debug the issue and fix the problem; the results can be found in this link:https://github.com/openbgpd-portable/openbgpd-portable/pull/93[GitHub pull request].
+
+Now, we can safely create or destroy virtual or cloned interfaces alongside OpenBGPd without worrying about our BGP sessions.
diff --git a/website/content/en/status/report-2025-01-2025-03/openjdk.adoc b/website/content/en/status/report-2025-01-2025-03/openjdk.adoc
new file mode 100644
index 0000000000..74447188ac
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/openjdk.adoc
@@ -0,0 +1,30 @@
+=== Improve OpenJDK on FreeBSD
+
+Links: +
+link:https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[Project description] URL: https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[] +
+link:https://github.com/freebsd/openjdk[Project repository] URL: https://github.com/freebsd/openjdk[]
+
+Contact: +
+Harald Eilertsen <haraldei@freebsdfoundation.org> +
+FreeBSD Java mailing list <freebsd-java@lists.freebsd.org>
+
+The main goal of this project is to improve OpenJDK support on FreeBSD/amd64 and FreeBSD/arm64.
+
+Java is an important runtime environment for many high performance, critical enterprise systems.
+Making sure Java based applications run correctly and efficiently on FreeBSD is important to ensure that FreeBSD will continue to be a viable and attractive platform for enterprises, as well as businesses and organizations of all sizes.
+
+We released https://cgit.freebsd.org/ports/commit/?id=aa17c509fe7c4a011e832bd1e67257cf5d0ebc81[a port for OpenJDK 23] for FreeBSD at the very end of last year, and have since then fixed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284503[issues with font management] and some other minor improvements.
+We have also been following the development of OpenJDK 24 closely, and are just finishing a https://reviews.freebsd.org/D49354[port for it] that should be available by the time this status update is published.
+
+In parallel with porting OpenJDK 24 work has been ongoing on moving the BSD port also to the mainline OpenJDK development tree, and the first patches have been accepted upstream.
+Currently the focus is on reviving the https://openjdk.org/projects/bsd-port/[OpenJDK BSD port project], as well as getting a separate project repository set up under it.
+
+A lot of the work of this quarter has gone into cleaning up the patches of the BSD port based on the development in the upstream mainline and jdk24 branches.
+Also a lot of time has been spent on improving the results of the built in test suites (jtreg and gtest) on FreeBSD.
+This has involved both changes to the tests themselves, but also various parts of the low level OpenJDK code.
+More work is needed to get the final few tests passing, especially on Aarch64, but compared to previous OpenJDK releases on FreeBSD the results have been improving.
+
+Finally, a significant amount of time has been spent on communicating and discussing how to approach the goal of integrating the BSD support in the mainline OpenJDK codebase.
+The OpenJDK project has been very open, welcoming and supportive of the effort, and seems more than willing to help make this happen in a good way.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/pinephone.adoc b/website/content/en/status/report-2025-01-2025-03/pinephone.adoc
new file mode 100644
index 0000000000..896b48bb7f
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/pinephone.adoc
@@ -0,0 +1,27 @@
+=== Pinephone Pro Support
+
+Links: +
+link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[Repository on Codeberg] URL: link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[]
+
+Contact: Toby Kurien <toby@tobykurien.com>
+
+The project to port FreeBSD over to the Pinephone Pro is progressing.
+The aim of this project is to step by step support components of the Pinephone Pro in FreeBSD so that the device one day might be usable as a highly mobile FreeBSD device.
+ 
+In this quarter, console output to the screen was enabled, using EFI framebuffer support.
+This requires using a specific version of U-boot that sets up the EFI framebuffer, which FreeBSD's kernel is then able to use for output while booting up.
+While this comes with limitations (like no hardware acceleration), it is a big step forward in making FreeBSD usable on the PinePhone Pro.
+To make it easier to try the current code changes out, a script was added to the repository to create a flashable image for booting from an SD card.
+This script downloads and patches a FreeBSD CURRENT mini-memstick image with the custom device tree and kernel.
+The resulting image can then be copied to an SD card using dd and booted up on the phone.
+See the repo for details.
+
+Work on enabling the USB port was started but has stalled and help is needed, particularly from someone who understands the USB subsystem and can help move this forward.
+Currently, some USB controllers are detected by FreeBSD but no USB devices are visible, e.g. the internally connected modem.
+Help is also needed to port the WiFi driver from Linux, which would be the same driver needed for Raspberry Pi 3b+/4/5 (Broadcom 43455 wifi module connected via SDIO).
+Anyone wanting to assist can contact me by e-mail.
+
+See the post on the FreeBSD Forum for more:
+https://forums.freebsd.org/threads/porting-freebsd-to-pinephone-pro-help-needed.95948/
+
+Sponsor: Honeyguide Group
diff --git a/website/content/en/status/report-2025-01-2025-03/pkgbasify.adoc b/website/content/en/status/report-2025-01-2025-03/pkgbasify.adoc
new file mode 100644
index 0000000000..01d9c7c733
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/pkgbasify.adoc
@@ -0,0 +1,16 @@
+=== Automatic pkgbase conversion tool
+
+Links: +
+link:link:https://github.com/FreeBSDFoundation/pkgbasify[pkgbasify] URL: link:https://github.com/FreeBSDFoundation/pkgbasify[] +
+link:https://wiki.freebsd.org/PkgBase[pkgbase] URL: link:https://wiki.freebsd.org/PkgBase[]
+
+Contact: Isaac Freund <ifreund@freebsdfoundation.org>
+
+The new link:https://github.com/FreeBSDFoundation/pkgbasify[pkgbasify] tool automatically converts an existing FreeBSD 14+ system to use link:https://wiki.freebsd.org/PkgBase[pkgbase].
+
+I've done my best to make pkgbasify as robust as possible and currently believe it to be as reliable as manual conversion if not better.
+
+That said, pkgbasify could use testing on more diverse systems!
+See the link:https://github.com/FreeBSDFoundation/pkgbasify[README] for usage instructions and details on pkgbasify's behavior.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/portmgr.adoc b/website/content/en/status/report-2025-01-2025-03/portmgr.adoc
new file mode 100644
index 0000000000..919ce0fc19
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/portmgr.adoc
@@ -0,0 +1,57 @@
+=== Ports Collection
+
+Links: +
+link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] +
+link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] +
+link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] +
+link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[]
+
+Contact: Tobias C. Berner <portmgr-secretary@FreeBSD.org> +
+Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org>
+
+The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters.
+Below is what happened in the last quarter.
+
+In the last quarter, we welcomed Austin Shafer (ashafer@) as a new ports committer, and welcomed back Eygene Ryabinkin (rea@) and Mark Linimon (linimon@).
+
+According to INDEX, there are currently 36,450 (up from 36,332) ports in the Ports Collection.
+There are currently about 3,333 (down from 3,368) open ports PRs, of which 887 are unassigned.
+The last quarter saw 10,733 (up from 10,640) commits by 158 (up from 155) committers on the main branch and 707 (down from 733) commits by 54 (down from 61) committers on the 2025Q1 branch.
+
+The most active committers to main were:
+
+- 3029 sunpoet@FreeBSD.org
+- 1171 yuri@FreeBSD.org
+-  358 vvd@FreeBSD.org
+-  340 bofh@FreeBSD.org
+-  313 rene@FreeBSD.org
+-  297 jbeich@FreeBSD.org
+-  288 eduardo@FreeBSD.org
+-  243 pkubaj@FreeBSD.org
+-  223 fuz@FreeBSD.org
+-  212 diizzy@FreeBSD.org
+
+A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are:
+
+- pkg 2.1.0
+- Default version of Lazarus switched to 3.8.0 (aarch64 at 4.99)
+- Chromium 134.0.6998.165
+- Electron 31 removed, Electron 34 added
+- Firefox 137.0-rc2
+- Firefox-esr 128.9.0-rc2
+- Gnome desktop 44.1
+- KDE Frameworks 6.12.0
+- KDE Plasma 6.3.3
+- KDE Gear 24.12.3
+- Qt6 6.8.3
+- Python 3.8 removed
+- Ruby 3.1 removed
+- Ruby 3.3.7
+- Rust 1.85.1
+- SDL 2.32.2
+- SDL 3.2.8, added to USES=sdl
+- Wine 10.0
+
+One USES was removed: qca
+
+During the last quarter, pkgmgr@ ran 20 exp-runs to test infrastructure changes and various ports upgrades.
diff --git a/website/content/en/status/report-2025-01-2025-03/pot.adoc b/website/content/en/status/report-2025-01-2025-03/pot.adoc
new file mode 100644
index 0000000000..990359cc82
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/pot.adoc
@@ -0,0 +1,23 @@
+=== Containers and FreeBSD: Pot, Potluck and Potman
+
+Links: +
+link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[]
+
+Contact: Luca Pizzamiglio (Pot) <pizzamig@FreeBSD.org> +
+Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> +
+Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org>
+
+Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad].
+Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad.
+
+During this quarter, there was a new link:https://github.com/bsdpot/pot/releases/tag/0.16.1[Pot release 0.16.1] which includes a number of minor fixes.
+The FreeBSD port was updated accordingly.
+
+Potluck got a new link:https://github.com/bsdpot/potluck/tree/master/onlyoffice-documentserver[OnlyOffice Documentserver] image that can be used together with the link:https://github.com/bsdpot/potluck/tree/master/nextcloud-nginx-nomad[Nextcloud] image.
+Additionally, a large number of images have received improvements and bug fixes again, e.g. link:https://github.com/bsdpot/potluck/tree/master/nextcloud-spreed-signalling[Nextcloud Spreed], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/vault[Vault] or link:https://github.com/bsdpot/potluck/tree/master/consul[Consul] and all images have been rebuilt for an updated base image.
+
+Last not least, we are in the process of moving the main repository to Codeberg with GitHub acting as a mirror.
+
+As always, feedback and patches are welcome.
+
+Sponsors: Nikulipe UAB, Honeyguide Group
diff --git a/website/content/en/status/report-2025-01-2025-03/releng.adoc b/website/content/en/status/report-2025-01-2025-03/releng.adoc
new file mode 100644
index 0000000000..bee620cf0c
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/releng.adoc
@@ -0,0 +1,16 @@
+=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/13.5R/announce/[FreeBSD 13.5-RELEASE announcement] URL: link:https://www.freebsd.org/releases/13.5/announce/[] +
+link:https://www.freebsd.org/releases/14.3R/schedule/[FreeBSD 14.3-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.3R/schedule/[] +
+link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+The Team managed 13.5-RELEASE, leading to the official RELEASE build and announcement in March; this was the final release from the legacy *stable/13* branch.
+Planning has started for the upcoming 14.3-RELEASE cycle.
+
+The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/14*, and *stable/13* branches.
diff --git a/website/content/en/status/report-2025-01-2025-03/srcmgr.adoc b/website/content/en/status/report-2025-01-2025-03/srcmgr.adoc
new file mode 100644
index 0000000000..1480da2670
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/srcmgr.adoc
@@ -0,0 +1,15 @@
+=== Source Management Team
+
+Contact: srcmgr <srcmgr@FreeBSD.org>
+
+srcmgr@ is focused on finding ways to make src developers more productive, and to try and manage the large numbers of bug reports and pull requests that we receive.
+The team meets every two weeks to discuss src-related issues and spend time triaging bug reports and pull requests.
+The current members are Ed Maste, Mark Johnston, John Baldwin, and Warner Losh.
+link:https://github.com/freebsd/meetings/tree/master/srcmgr[Meeting minutes] are available on GitHub.
+
+In January and February, srcmgr@ ran two online bug-busting sessions, each attended by roughly 12 developers.
+The sessions ran for three hours and focused on triaging new src bug reports.
+The team plans to resume hosting these sessions in the next month.
+
+The srcmgr@ team plans to lead a session at the link:https://wiki.freebsd.org/DevSummit/202506[FreeBSD Developer Summit] in June.
+Topics will include deprecation of 32-bit platforms, and pkgbase support for the upcoming FreeBSD 15.0 release.
diff --git a/website/content/en/status/report-2025-01-2025-03/suspend.adoc b/website/content/en/status/report-2025-01-2025-03/suspend.adoc
new file mode 100644
index 0000000000..b72a132f58
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/suspend.adoc
@@ -0,0 +1,26 @@
+=== Suspend/Resume Improvement
+
+Links: +
+link:https://obiw.ac/s0ix/[Blog] URL: link:https://obiw.ac/s0ix/[] +
+link:https://youtu.be/mBxj_EkAzV0[FOSDEM talk on S0ix] URL: https://youtu.be/mBxj_EkAzV0[] +
+link:https://github.com/obiwac/freebsd-s0ix[Working Repository] URL: link:https://github.com/obiwac/freebsd-s0ix[] +
+link:https://reviews.freebsd.org/D48721[Tip of the S0ix + AMD SMU stack] URL: https://reviews.freebsd.org/D48721[] +
+link:https://reviews.freebsd.org/D49453[USB4 suspend stack] URL: https://reviews.freebsd.org/D49453[]
+
+Contact: obiwac <obiwac@FreeBSD.org>
+
+Suspend-to-idle and support for S0ix sleep is in the process of being added to FreeBSD.
+
+This will allow modern Intel and AMD laptops (e.g. AMD and newer Intel Framework laptops), some of which do not support ACPI S3 sleep, to enter low power states to increase battery life.
+
+Suspending and resuming is working on the Framework 13 AMD Ryzen 7040 series, though the deepest S0ix state (S0i3), necessary for significant power savings, cannot yet be entered on AMD systems.
+The major blocker for this at the moment is being able to suspend all the USB4 routers correctly, without which the power management firmware will refuse to enter S0i3.
+USB4 suspend support in FreeBSD is necessary as the BIOS wakes them up and runs a pre-OS connection manager for USB4 to work before an OS loads with its own connection manager, so they start off in an awake state.
+
+Work has been picked up from the initial USB4 driver Scott Long started writing, but it is not yet at a stage where the routers are being fully suspended.
+
+An amdsmu driver was written to read last suspend statistics and sleep-state residency counters (which were unavailable in the ACPI _LPI objects).
+The SMU is a small coprocessor on AMD CPUs which runs the power management firmware and is ultimately what decides to enter S0i3 or not.
+These statistics can tell us if the system entered S0i3 during the last suspend, how much time it took to enter, and which proportion of suspended time was spent in S0i3.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/sylve.adoc b/website/content/en/status/report-2025-01-2025-03/sylve.adoc
new file mode 100644
index 0000000000..8da359a9e3
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/sylve.adoc
@@ -0,0 +1,39 @@
+=== Sylve -- A Unified System Management Platform for FreeBSD
+
+Links: +
+link:https://github.com/AlchemillaHQ/Sylve[GitHub] URL: link:https://github.com/AlchemillaHQ/Sylve[] +
+link:https://sylve-ci.alchemilla.io[CI] URL: link:https://sylve-ci.alchemilla.io[] +
+link:https://discord.gg/bJB826JvXK[Discord] URL: link:https://discord.gg/bJB826JvXK[]
+
+Contact: Hayzam Sherif <hayzam@alchemilla.io>
+
+Sylve is a modern, unified system management platform for FreeBSD, inspired by Proxmox.
+It intends to provide an integrated web interface for managing virtual machines (via Bhyve), Jails, ZFS storage, networking, and firewalling.
+The backend is implemented in Go, while the frontend uses SvelteKit with Tailwind CSS and ShadCN UI components.
+
+The project emphasizes a minimal system footprint, currently requiring only package:sysutils/smartmontools[] and package:sysutils/tmux[] as runtime dependencies.
+
+Sylve addresses a key gap in the FreeBSD ecosystem: a user-friendly, full-featured web interface for system management.
+By unifying virtualization, storage, and network management, it aims to lower the barrier for users and administrators deploying FreeBSD in complex environments.
+
+We started working on the project since February and have made significant progress across several areas:
+
+* PAM-Based Authentication: Integrated support for FreeBSD's native PAM system, with optional fallback to local authentication.
+* Disk Management: Users can view and manage physical disks and partitions through the web UI, with SMART-based health monitoring included.
+* Frontend Infrastructure: Continued development of reusable UI components and layout structure, with a responsive and accessible design.
+
+The project remains under active development and is not yet production-ready.
+
+Planned tasks for the upcoming quarter include:
+
+* ZFS Management: Implementing full support for creating and managing ZFS pools and datasets via the web interface.
+* Virtual Machine Management: Continuing the Bhyve integration to support VM creation, monitoring, and control.
+* Basic Network and Firewalling: Providing web-based interfaces for NAT, port forwarding, and firewall rule configuration.
+
+Contributions, testing, and feedback are very welcome.
+If you are interested in contributing, consider helping with:
+
+* UI testing and accessibility feedback
+* Bug reports and feature requests via GitHub
+
+Sponsor: FreeBSD Foundation and Alchemilla (development and infrastructure support)
diff --git a/website/content/en/status/report-2025-01-2025-03/syzkaller-wifi.adoc b/website/content/en/status/report-2025-01-2025-03/syzkaller-wifi.adoc
new file mode 100644
index 0000000000..a741bbee5f
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/syzkaller-wifi.adoc
@@ -0,0 +1,27 @@
+=== Syzkaller Improvement for WiFi on FreeBSD
+
+Links: +
+link:https://github.com/google/syzkaller[google/syzkaller] URL: link:https://github.com/google/syzkaller[] +
+link:https://github.com/estarriol43/syzkaller/tree/freebsd/frame-injection-v2[work repository] URL: link:https://github.com/estarriol43/syzkaller/tree/freebsd/frame-injection-v2[]
+
+Contact: Jian-Lin Li <ljianlin99@gmail.com> +
+Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>
+
+Syzkaller is an operating system kernel fuzzer that can look for vulnerabilities in the kernel.
+
+This project aims to improve the support of Syzkaller on FreeBSD.
+Based on the existing WiFi fuzzer designed for Linux, we drafted a WiFi fuzzer for FreeBSD.
+We planned to use man:wtap[4], a virtual wifi interface for testing, in order to support WiFi fuzzing.
+
+Some of the design details include:
+
+* Initialize wtap devices in Syzkaller before WiFi fuzzing
+* Inject 802.11 frames via the existing ioctl interface provided by wtap
+* Inject 802.11 frames via the Netlink interface, which is not supported by FreeBSD for now
+
+We have developed a WiFi fuzzer using existing ioctl interface provided by wtap.
+One can check out the result in this link:https://github.com/estarriol43/syzkaller/tree/freebsd/frame-injection-v2[branch].
+
+We hope to introduce Netlink interface, which is adopted by the Syzkaller to inject 802.11 frames into Linux kernel, to FreeBSD to improve the compatibilities between Linux and FreeBSD.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/vision-accessibility-handbook.adoc b/website/content/en/status/report-2025-01-2025-03/vision-accessibility-handbook.adoc
new file mode 100644
index 0000000000..6a37578915
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/vision-accessibility-handbook.adoc
@@ -0,0 +1,31 @@
+=== Vision Accessibility -- Accessibility Handbook
+
+Link: +
+link:https://gitlab.com/alfix/freebsd-accessibility[Project Repository] URL: link:https://gitlab.com/alfix/freebsd-accessibility[]
+
+Contact: FreeBSD Accessibility mailing list <freebsd-accessibility@FreeBSD.org> +
+Contact: Alfonso Sabato Siciliano <asiciliano@FreeBSD.org>
+
+The FreeBSD Foundation is supporting a series of projects to enhance accessibility for users with visual impairments.
+
+FreeBSD offers several assistive technologies, thanks to the dedicated work of contributors and committers.
+An ongoing effort focuses on listing and documenting these accessibility features in a new handbook.
+Currently, the project centers on documenting features for blind, low-vision, and colorblind users, covering both PORTS and BASE system functionalities.
+For example: ports for screen magnification, screen readers (which aid users who cannot see the screen), as well as tools for adjusting colors in desktop environments.
+Additionally, accessibility features available in the BASE system to enhance visibility are also being documented with examples and tips: such as the ability to modify colors, fonts, and sizes in the system's virtual console man:vt[4].
+
+The new handbook will be organized into sections.
+The first section will serve as an introduction, while the second will delve into assistive technologies for visual accessibility.
+The repository mentioned above provides access to the handbook's work-in-progress, including the code (in a fork of the FreeBSD "doc" repository, accessibility-book branch) and an HTML preview.
+Completion and review for publication are expected soon.
+Future plans include adding a Section 3 for hearing accessibility, a Section 4 for interaction accessibility, and a "Miscellaneous" chapter in Section 1 to cover general aspects.
+A discussion on this topic is available on the accessibility mailing list.
+
+Furthermore, during this quarter, the port package:www/edbrowse[] has been updated.
+This is a fully command-line web browser designed for compatibility with screen readers.
+A solution is also being developed to facilitate easy color customization for TUI utilities in the BASE system, with the potential to set high contrast directly from the system installer man:bsdinstall[8].
+
+Tips and new ideas are welcome.
+If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place.
+
+Sponsored by: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-01-2025-03/wazuh.adoc b/website/content/en/status/report-2025-01-2025-03/wazuh.adoc
new file mode 100644
index 0000000000..2953a40af4
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/wazuh.adoc
@@ -0,0 +1,37 @@
+=== Wazuh on FreeBSD
+
+Links: +
+link:https://www.wazuh.com/[Wazuh] URL: link:https://www.wazuh.com/[] +
+
+Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>
+
+Wazuh is a free and open source platform used for threat prevention, detection, and response.
+It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments.
+
+Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents.
+Besides, Wazuh has been fully integrated with the Elastic Stack or OpenSearch Stack, providing a search engine and data visualization tool that allows users to navigate through their security alerts.
+
+During this quarter, there were many bugfixes and improvements to wazuh ports.
+
+- Update bundle python to 3.11.11
+- Update package:textproc/opensearch[] dependency to 2.16.x
+- Update package:textport/opensearch-dashboards[] dependency to 2.16.x
+- Update package:databases/py-pyarrow[] whl to 19.0.1
+
+A quickly Wazuh jail installation to test it can be done using link:https://github.com/AppJail-makejails/wazuh[Wazuh AppJail-Makejails].
+
+A big thank to link:https://www.entersekt.com/[Entersekt] for sponsor my work.
+Now I can use a RockPro64 (aarch64) for Wazuh testing/packaging.
+
+People interested in helping with the project are welcome.
+
+Current version: 4.11.0
+
+TODO
+
+* Add Wazuh cluster-mode infrastructure AppJail makejails
+* Add vulnerability detection support to FreeBSD Wazuh agent
+* Add FreeBSD like official support platform by Wazuh Inc
+* Update FreeBSD SCA Policies to new FreeBSD CIS Benchmark
+
+Sponsor: Entersekt
diff --git a/website/content/en/status/report-2025-01-2025-03/wiki.adoc b/website/content/en/status/report-2025-01-2025-03/wiki.adoc
new file mode 100644
index 0000000000..937cf1993d
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/wiki.adoc
@@ -0,0 +1,28 @@
+=== FreeBSD Wiki
+
+Links: +
+link:https://wiki.freebsd.org/FrontPage[FreeBSD wiki front page] URL: link:https://wiki.freebsd.org/FrontPage[]
+
+Contact: Mark Linimon <linimon@FreeBSD.org> +
+Contact: Wiki admin <wiki-admin@FreeBSD.org>
+
+The wiki team needs new blood.
+
+Since the last status report (2024Q3) forward progress has stalled.
+We have given out several dozen new accounts but most of the changes by these new authors have been to individual pages, not to the overall structure.
+
+Mark Linimon still thinks the wiki could be a great resource if people were willing to put time into it.
+But right now, there are more complaints about stale data than there are new contributors and new ideas.
+
+It is fair to say that right now, the wiki is on autopilot.
+
+==== Previous plans that have stalled
+
+Preliminary work was being done on updating the wiki software itself.
+Earlier, we were looking at switching implementations because MoinMoin development seemed to have stalled, leaving us with an unwanted hanging python2 dependency.
+However, MoinMoin now claims that they are nearing a 2.0 release.
+We have not yet tried an install of their latest beta version to test compatibility.
+
+==== Specific short-term requests for help
+
+If anyone knows about MoinMoin markup, contact Mark.
diff --git a/website/content/en/status/report-2025-01-2025-03/wireless-iwx.adoc b/website/content/en/status/report-2025-01-2025-03/wireless-iwx.adoc
new file mode 100644
index 0000000000..ba5b63de81
--- /dev/null
+++ b/website/content/en/status/report-2025-01-2025-03/wireless-iwx.adoc
@@ -0,0 +1,20 @@
+=== Wireless Update
+
+Contact: Tom Jones <thj@FreeBSD.org> +
+Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org>
+
+At the end of 2024 Future Crew LLC provided the source for their iwx port from OpenBSD.
+I opted to merge the two drivers together using the Future Crew driver as a base and importing my modifications.
+
+I worked on this driver, tidying up and removing a lot of development code and expanding support for more devices.
+iwx in FreeBSD should now attach to any device supported by OpenBSD.
+Firmware is available thanks to mailto:bz@FreeBSD.org[bz@] in the package:net/wifi-firmware-iwlwifi-kmod[] package.
+
+iwx landed in FreeBSD on the final day of the quarter.
+iwx probes with a lower priority than iwlwifi to avoid breaking deployed configurations.
+
+iwx supports legacy, HT and VHT rates and some users have reported significant throughputs in test.
+There remain many issues around rate selection and development is continuing.
+
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-04-2025-06/drm-drivers.adoc b/website/content/en/status/report-2025-04-2025-06/drm-drivers.adoc
new file mode 100644
index 0000000000..7ba18092d6
--- /dev/null
+++ b/website/content/en/status/report-2025-04-2025-06/drm-drivers.adoc
@@ -0,0 +1,36 @@
+=== DRM drivers
+
+Links: +
+link:https://github.com/freebsd/drm-kmod/pull/361[Update to Linux 6.9 DRM drivers] URL: link:https://github.com/freebsd/drm-kmod/pull/361[]
+
+Contact: Jean-Sébastien Pédron <dumbbell@FreeBSD.org>
+
+DRM drivers are **kernel drivers for integrated and discrete GPUs**.
+They are maintained in the Linux kernel and we port them to FreeBSD.
+As of this report, we take the AMD and Intel DRM drivers only (NVIDIA FreeBSD drivers are proprietary and provided by NVIDIA themselves).
+
+We port them one Linux version at a time.
+This allows us to ship updates more often and it eases porting and debugging because we have a smaller delta compared to a bigger jump skipping several versions.
+
+This quarter, we finally merged the drivers from Linux 6.7 and 6.8 that were done during the first quarter into *drm-kmod*.
+The **porting for DRM drivers from Linux 6.9 was finished** and is now ready for review and testing;
+https://github.com/freebsd/drm-kmod/pull/361[see the pull request for instructions] if you want to try them.
+The pull request also lists all the patches needed to `linuxkpi`, the Linux drivers compatibility layer in the FreeBSD kernel.
+Several patches were already reviewed but there is still work.
+
+These updates target the FreeBSD 15-CURRENT development branch for now.
+Once kernel patches are accepted and the DRM drivers updates merged, we will evaluate if/how we can backport the kernel patches to earlier release branches (namely 14-STABLE).
+
+While waiting for review, we also started to work on two features which were unsupported on FreeBSD:
+* https://github.com/freebsd/drm-kmod/pull/357[`DMA_BUF_IOCTL_EXPORT_SYNC_FILE` and `DMA_BUF_IOCTL_IMPORT_SYNC_FILE` ioctls]
+* https://github.com/freebsd/drm-kmod/pull/358[`DRM_IOCTL_SYNCOBJ_EVENTFD` ioctl]
+
+They are apparently required to allow the use of wlroots-based Wayland compositors with the Vulkan API (see link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286311[]).
+wlroots will need a patch as well because it only expects these features on Linux for now.
+
+Both pull requests as well as the patches to `linuxkpi` they rely on are ready for review and testing.
+The `linuxkpi` patches are linked in the pull requests.
+
+This work is kindly sponsored by the FreeBSD Foundation as part of the Laptop and Desktop Project.
+
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2025-04-2025-06/geomman.adoc b/website/content/en/status/report-2025-04-2025-06/geomman.adoc
new file mode 100644
index 0000000000..fd6ad08676
--- /dev/null
+++ b/website/content/en/status/report-2025-04-2025-06/geomman.adoc
@@ -0,0 +1,32 @@
+=== Geomman Development
+
+Links: +
+link:https://wiki.freebsd.org/SummerOfCode2025Projects/FullDiskAdministrationToolForFreeBSD[Geomman GSoC wiki] URL: link:https://wiki.freebsd.org/SummerOfCode2025Projects/FullDiskAdministrationToolForFreeBSD[] +
+link:https://gitlab.com/brauliorivas/geomman[geomman Gitlab repository] URL: link:https://gitlab.com/brauliorivas/geomman[] +
+link:https://gitlab.com/alfix/bsddialog[bsddialog repository] URL: link:https://gitlab.com/alfix/bsddialog[] +
+link:https://man.freebsd.org/cgi/man.cgi?query=sade&manpath=FreeBSD+14.3-RELEASE+and+Ports[sade] URL: link:https://man.freebsd.org/cgi/man.cgi?query=sade&manpath=FreeBSD+14.3-RELEASE+and+Ports[]
+
+Contact: Braulio Rivas <brauliorivas@FreeBSD.org>
+
+Geomman is a new partition tool based on man:sade[8] that brings more functionality such as moving, copying, and pasting partitions.
+Geomman is part of Google Summer of Code 2025.
+Currently, it is available in a Gitlab repository.
+But at some future time, it is expected to become a tool in the base system.
+
+Geomman is a TUI designed to allow to growing, shrinking, moving, copying, and pasting partitions with filesystems other than UFS.
+For example, users may be able to create an exFAT partition, as well as to resize an ext4 filesystem.
+This would make partition management easier, because there are tools for each individual task (mainly depending on the filesystem), but none that concentrates all cases in a single tool.
+
+For the moment, geomman only allows copying and pasting partitions.
+However, for the next report the tool should be almost finished.
+
+Currently, I am working on a mechanism to move partitions using man:dd[1].
+Other approaches may be possible, so any help is very welcome.
+
+The next steps for geomman are:
+
+* Develop a way of moving partitions.
+* Handle duplicate UUIDs between partitions when using dd.
+* Add options to create, grow, and shrink more filesystem types.
+
+Sponsor: Google Summer of Code
diff --git a/website/content/en/status/report-2025-04-2025-06/named-attributes.adoc b/website/content/en/status/report-2025-04-2025-06/named-attributes.adoc
new file mode 100644
index 0000000000..d6f5e0e54d
--- /dev/null
+++ b/website/content/en/status/report-2025-04-2025-06/named-attributes.adoc
@@ -0,0 +1,27 @@
+=== Named attribute support (Solaris style extended attributes)
+
+Contact: Rick Macklem <rmacklem@FreeBSD.org>
+
+Named attributes is the NFSv4 term for what is also known as Solaris style extended attributes.
+Since ZFS has its origins in Solaris, the wiring for these exists in OpenZFS.
+This little project consists of connecting that wiring up.
+This is not intended to replace the extended attribute support already in FreeBSD.
+It provides an alternate mechanism for manipulating extended attributes that will be supported for ZFS and NFSv4.
+There are a few reasons I think this could be useful (as indicated via email discussion).
+This mechanism allows for extended attributes as large as any regular file, which can be partially updated.
+Some NFSv4 clients, such as MacOS and Windows, can use these extended attributes but not the FreeBSD/Linux style ones.
+(I think MacOS calls these extended attributes fork files and Windows calls them alternate data streams.)
+There is software, such as bash, that know how to manipulate these extended attributes.
+
+The fundamental difference is that this mechanism provides a directory that is not in the file system's namespace, but is associated with a file object.
+This named attribute directory can then be read via man:readdir[3] to get the list of extended attributes, which are really just regular files.
+These extended attributes are then read/written like any regular file.
+
+The top level system call interface is man:open[2]/man:openat[2] with the new O_NAMEDATTR flag (called O_XATTR on Solaris).
+
+Most of the work has been committed to FreeBSD's main for FreeBSD 15.
+Once the ZFS patch makes it through review and gets pulled into OpenZFS, the ZFS and NFSv4 support should work.
+There are also a couple of manual pages currently under review in phabricator.
+
+The main thing left to do is update libarchive/tar so that large extended attributes can be archived/retrieved.
+(The current FreeBSD extended attribute mechanism is supported by libarchive, but will have size constraints.)
diff --git a/website/content/en/status/report-2025-04-2025-06/packrat.adoc b/website/content/en/status/report-2025-04-2025-06/packrat.adoc
new file mode 100644
index 0000000000..f496bccc9c
--- /dev/null
+++ b/website/content/en/status/report-2025-04-2025-06/packrat.adoc
@@ -0,0 +1,23 @@
+=== Packrat - NFS client caching on non-volatile storage
+
+Contact: Rick Macklem <rmacklem@freebsd.org>
+
+NFSv4.1/4.2 provides support for a feature called delegations.
+When a NFSv4.1/4.2 client holds a delegation, the client has certain rights to a file, including a guarantee that no other client will make changes to the file unless the delegation is recalled.
+As such, when a client holds a delegation for a file, it can aggressively cache the file's data, knowing that it will not be modified by other clients until it returns the delegation.
+
+This project is intended to allow the NFSv4.1/4.2 client to aggressively cache file data on client local non-volatile storage, when the client holds a delegation for the file.
+I created a patch long ago to try and do this for NFSv4.0, but it was never at a stage where it was worth using.
+This project is a complete rewrite of the patch, done in part because NFSv4.1/4.2 plus other recent NFSv4 related changes makes doing this more feasible.
+
+The patch is getting stable now, but I am not sure if it will be ready for inclusion in FreeBSD 15 as an experimental feature enabled via a new mount option called "packrat".
+
+The main thing I still need to do is code a writeback kernel thread.
+Right now, dirty chunks stored on client local non-volatile storage get written back to the NFSv4.1/4.2 server upon umount.
+This can result in the umount taking a long time (as in many minutes).
+To alleviate this, I am planning on implementing a writeback kernel process that will walk the non-volatile storage and write the dirty chunks back.
+The trick is to make it aggressive enough that most dirty chunks have been written back when a umount is done, but not so aggressive that it impedes the performance of synchronous NFSv4.1/4.2 RPCs.
+
+This will be very much an experimental feature, but it is hoped it will allow NFS mounts to be used more effectively, particularly in WAN situations, such as a mobile laptop.
+
+There is still work to be done, particularly with respect to recovery of delegations after a NFSv4.1/4.2 client restart.
diff --git a/website/content/en/status/report-2025-04-2025-06/ports-security.adoc b/website/content/en/status/report-2025-04-2025-06/ports-security.adoc
new file mode 100644
index 0000000000..8fb04f26d6
--- /dev/null
+++ b/website/content/en/status/report-2025-04-2025-06/ports-security.adoc
@@ -0,0 +1,24 @@
+=== Security Hardening Compiler Options for the Ports Collection
+
+Links: +
+link:https://cgit.freebsd.org/ports/commit/Mk/Features/fortify.mk?id=7a489e95c51f47f5e25a5613e375ec000618e52a[Commit of the features] URL: link:https://cgit.freebsd.org/ports/commit/Mk/Features/fortify.mk?id=7a489e95c51f47f5e25a5613e375ec000618e52a[] +
+link:https://www.leidinger.net/blog/2025/05/24/freebsd-security-hardening-with-compiler-options/[FreeBSD security hardening with compiler options] URL: link:https://www.leidinger.net/blog/2025/05/24/freebsd-security-hardening-with-compiler-options/[]
+
+Contact: Alexander Leidinger <netchild@FreeBSD.org>
+
+The Ports Collection gained the possibility to enable some security features of modern compilers for package builds.
+As not all ports are compatible with them, this is not enabled by default.
+
+The 3 new features which can be enabled for the Ports Collection in [.filename]#make.conf# are:
+
+- WITH_FORTIFY=yes::
+This enables mitigations of common memory safety issues, such as buffer overflows, by adding checks to functions like memcpy, strcpy, sprintf, and others when the compiler can determine the size of the destination buffer at compile time.
+This requires support from the FreeBSD base system and may only be available in FreeBSD 15 onwards.
+WITH_STACK_AUTOINIT=yes::
+This enables a compiler specific option to automatically initialize local (automatic) variables to prevent the use of uninitialized memory.
+WITH_ZEROREGS=yes::
+Zero call-used registers at function return to increase program security by either mitigating Return-Oriented Programming (ROP) attacks or preventing information leakage through registers.
+This depends upon support from the compiler for a given architecture.
+This is disabled for python ports; currently there are issues.
+
+The blog post referenced in the links section explains how to use them, how to exclude certain ports if needed, and provides a more detailed explanation of those 3 new features along the already existing build-time security options of the Ports Collection and the basesystem build.