diff options
Diffstat (limited to 'website/content/en/status/report-2015-04-2015-06.html')
| -rw-r--r-- | website/content/en/status/report-2015-04-2015-06.html | 2423 |
1 files changed, 0 insertions, 2423 deletions
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 e7b59d8b3d..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" /> - - </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&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>—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 <<a href="mailto:clusteradm@">clusteradm@</a>> - </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 <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>> - </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 <<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>> - </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 - <<a href="mailto:shawn.webb@hardenedbsd.org">shawn.webb@hardenedbsd.org</a>> - <br /> - Contact: - Oliver - Pinter - <<a href="mailto:oliver.pinter@hardenedbsd.org">oliver.pinter@hardenedbsd.org</a>> - <br /> - Contact: HardenedBSD <<a href="mailto:core@hardenedbsd.org">core@hardenedbsd.org</a>> - </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 - <<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>> - <br /> - Contact: - Neel - Natu - <<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>> - <br /> - Contact: - Tycho - Nightingale - <<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>> - <br /> - Contact: - Allan - Jude - <<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>> - <br /> - Contact: - Alexander - Motin - <<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>> - <br /> - Contact: - Marcelo - Araujo - <<a href="mailto:araujo@FreeBSD.org">araujo@FreeBSD.org</a>> - </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 - <<a href="mailto:AllanJude@FreeBSD.org">AllanJude@FreeBSD.org</a>> - <br /> - Contact: - Dmitry - Chagin - <<a href="mailto:dchagin@FreeBSD.org">dchagin@FreeBSD.org</a>> - <br /> - Contact: - Ed - Maste - <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>> - <br /> - Contact: - Edward Tomasz - Napierała - <<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>> - <br /> - Contact: - Johannes - Meixner - <<a href="mailto:xmj@FreeBSD.org">xmj@FreeBSD.org</a>> - <br /> - Contact: FreeBSD Emulation Team <<a href="mailto:emulation@FreeBSD.org">emulation@FreeBSD.org</a>> - </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ł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 - <<a href="mailto:maxg@mellanox.com">maxg@mellanox.com</a>> - <br /> - Contact: - Sagi - Grimberg - <<a href="mailto:sagig@mellanox.com">sagig@mellanox.com</a>> - </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 - <<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>> - </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 - <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>> - <br /> - Contact: - Christian - Brueffer - <<a href="mailto:brueffer@FreeBSD.org">brueffer@FreeBSD.org</a>> - <br /> - Contact: TrustedBSD audit mailing list <<a href="mailto:trustedbsd-audit@TrustedBSD.org">trustedbsd-audit@TrustedBSD.org</a>> - </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 - <<a href="mailto:franco@opnsense.org">franco@opnsense.org</a>> - <br /> - Contact: - Ad - Schellevis - <<a href="mailto:ad@opnsense.org">ad@opnsense.org</a>> - <br /> - Contact: - Jos - Schellevis - <<a href="mailto:jos@opnsense.org">jos@opnsense.org</a>> - </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ła - <<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>> - </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 - <<a href="mailto:sub.mesa@gmail.com">sub.mesa@gmail.com</a>> - </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 - <<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>> - </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 - <<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>> - </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 - <<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>> - </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&revision=282684" title="https://svnweb.freebsd.org/base?view=revision&revision=282684">Commit r282684</a></td><td> - URL: <a href="https://svnweb.freebsd.org/base?view=revision&revision=282684" title="Commit r282684">https://svnweb.freebsd.org/base?view=revision&revision=282684</a></td></tr></table><p> - Contact: - Konstantin - Belousov - <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>> - </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&revision=282678" title="https://svnweb.freebsd.org/base?view=revision&revision=282678">Commit r282678</a></td><td> - URL: <a href="https://svnweb.freebsd.org/base?view=revision&revision=282678" title="Commit r282678">https://svnweb.freebsd.org/base?view=revision&revision=282678</a></td></tr></table><p> - Contact: - Konstantin - Belousov - <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>> - </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 >= 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 - <<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>> - </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 - <<a href="mailto:der@semihalf.com">der@semihalf.com</a>> - <br /> - Contact: - Wojciech - Macek - <<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>> - <br /> - Contact: - Michal - Stanek - <<a href="mailto:mst@semihalf.com">mst@semihalf.com</a>> - <br /> - Contact: - Zbigniew - Bodek - <<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>> - </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 - <<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>> - <br /> - Contact: - Ed - Maste - <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>> - <br /> - Contact: - Ruslan - Bukin - <<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>> - </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 - <<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>> - </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 <<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>> - </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 - <<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>> - <br /> - Contact: Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> - <br /> - Contact: - Sean - Bruno - <<a href="mailto:sbruno@FreeBSD.org">sbruno@FreeBSD.org</a>> - </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 - <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>> - <br /> - Contact: FreeBSD Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> - </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 - <<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>> - </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 - <<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>> - <br /> - Contact: - David - Naylor - <<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>> - </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 - <<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>> - </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 <<a href="mailto:freebsd-doc@FreeBSD.org">freebsd-doc@FreeBSD.org</a>> - </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 - <<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>> - </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 - <<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>> - </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 <<a href="mailto:doceng@FreeBSD.org">doceng@FreeBSD.org</a>> - </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 - <<a href="mailto:bhd@FreeBSD.org">bhd@FreeBSD.org</a>> - <br /> - Contact: - Johann - Kois - <<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>> - <br /> - Contact: - Benedict - Reuschling - <<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>> - </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 - <<a href="mailto:pfg@FreeBSD.org">pfg@FreeBSD.org</a>> - <br /> - Contact: - Oliver - Pinter - <<a href="mailto:op@FreeBSD.org">op@FreeBSD.org</a>> - </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 - <<a href="mailto:btw@FreeBSD.org">btw@FreeBSD.org</a>> - <br /> - Contact: - Hiren - Panchasara - <<a href="mailto:hiren@FreeBSD.org">hiren@FreeBSD.org</a>> - </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 - <<a href="mailto:dvl@FreeBSD.org">dvl@FreeBSD.org</a>> - </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 - <<a href="mailto:venture37@geeklan.co.uk">venture37@geeklan.co.uk</a>> - </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 - <<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>> - </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ł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 - <<a href="mailto:emc2@metricspace.net">emc2@metricspace.net</a>> - </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–2021 The FreeBSD Project. - All rights reserved.</span> - <br /> - </div> - </div> - </div> - </body> -</html> |