diff options
Diffstat (limited to 'website/content/en/status/report-2010-10-2010-12.html')
| -rw-r--r-- | website/content/en/status/report-2010-10-2010-12.html | 1438 |
1 files changed, 0 insertions, 1438 deletions
diff --git a/website/content/en/status/report-2010-10-2010-12.html b/website/content/en/status/report-2010-10-2010-12.html deleted file mode 100644 index ce80ac375d..0000000000 --- a/website/content/en/status/report-2010-10-2010-12.html +++ /dev/null @@ -1,1438 +0,0 @@ -<?xml version="1.0" encoding="iso-8859-1"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook"> - <head> - <title>FreeBSD Quarterly Status Report</title> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> - <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> - <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - - </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>This report covers FreeBSD-related projects between October and - December 2010. It is the last of the four reports planned for 2010. - The work on the new minor versions of FreeBSD, 7.4 and 8.2, has been - progressing well and they should be released around the end of this - month.</p><p>Thanks to all the reporters for the excellent work! This report - contains 37 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period - between January and March 2011 is April 15th, 2011.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BSDInstall">BSDInstall</a></li><li><a href="#Non-executable-Stacks">Non-executable Stacks</a></li><li><a href="#Webcamd">Webcamd</a></li><li><a href="#xz-Compression-for-Packages-and-Log-Files">xz Compression for Packages and Log Files</a></li><li><a href="#ZFS-pool-version-28">ZFS pool version 28</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team-Status-Report">FreeBSD Bugbusting Team Status Report</a></li><li><a href="#Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical - Evidence (DIFFUSE)</a></li><li><a href="#Ethernet-Switch-Framework">Ethernet Switch Framework</a></li><li><a href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></li><li><a href="#FreeBSD-802.11n">FreeBSD 802.11n</a></li><li><a href="#FreeBSD-VirtIO-Network-Driver">FreeBSD VirtIO Network Driver</a></li><li><a href="#Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)">Generic IEEE 802.3 annex 31B full duplex flow control support - for Ethernet in mii(4)</a></li><li><a href="#IPv6-and-VIMAGE">IPv6 and VIMAGE</a></li><li><a href="#TCP-SMP-scalability-project">TCP SMP scalability project</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Resource-Containers">Resource Containers</a></li><li><a href="#SYSCTL-Type-Safety">SYSCTL Type Safety</a></li><li><a href="#TRIM-support-for-UFS">TRIM support for UFS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#mdocml-Replacing-groff-For-manpage-Rendering">mdocml Replacing groff For manpage Rendering</a></li><li><a href="#The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></li><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></li><li><a href="#GEOM-based-ataraid(4)-Replacement-—-geom_raid">GEOM-based ataraid(4) Replacement — geom_raid</a></li><li><a href="#gpart-Improvements">gpart Improvements</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Bringing-up-OMAP3">Bringing up OMAP3</a></li><li><a href="#FreeBSD-on-the-Playstation-3">FreeBSD on the Playstation 3</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium">Chromium</a></li><li><a href="#FreeBSD-as-Home-Theater-PC">FreeBSD as Home Theater PC</a></li><li><a href="#Port-Sandbox">Port-Sandbox</a></li><li><a href="#Portmaster">Portmaster</a></li><li><a href="#Ports-Additions">Ports Additions</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Robot-Operating-System">Robot Operating System</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FOSDEM-2011">FOSDEM 2011</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BSDInstall" href="#BSDInstall" id="BSDInstall">BSDInstall</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BSDInstall" title="http://wiki.FreeBSD.org/BSDInstall">BSDInstall Wiki Page</a></td><td> - URL: <a href="http://wiki.FreeBSD.org/BSDInstall" title="BSDInstall Wiki Page">http://wiki.FreeBSD.org/BSDInstall</a></td></tr></table><p> - Contact: - Nathan - Whitehorn - <<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>> - </p> - <p>BSDInstall is a replacement for the venerable sysinstall - installer. It is designed to be modular and easily extensible, - while being fully scriptable and streamlining the installation - process. It is mostly complete, and installs working systems on - i386, amd64, sparc64, powerpc, and powerpc64, with untested PC98 - support.</p> - - <p>New Features:</p> - - <ul> - <li>Allows installation onto GPT disks on x86 systems</li> - - <li>Can do installations spanning multiple disks</li> - - <li>Allows installation into jails</li> - - <li>Eases PXE installation</li> - - <li>Virtualization friendly: can install from a live system onto - disk images</li> - - <li>Works on PowerPC</li> - - <li>Streamlined system installation</li> - - <li>More flexible scripting</li> - - <li>Easily tweakable</li> - - <li>All install CDs are live CDs</li> - </ul> - <h3>Open tasks:</h3><ol><li>Wireless networking configuration wizard.</li><li>ZFS installation support.</li><li>Itanium disk setup.</li></ol><hr /><h2><a name="Non-executable-Stacks" href="#Non-executable-Stacks" id="Non-executable-Stacks">Non-executable Stacks</a></h2><p> - Contact: - Konstantin - Belousov - <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>> - </p> - <p>The support for non-executable stacks, using the approach - identical to one used by GNU toolchain and Linux'es, is implemented - for amd64 and PowerPC. The support is already committed to HEAD. - For now, non-executable stacks are turned off by default.</p> - - <p>I plan to provide a detailed information to ports@ and switch - the knob after port tree is unfrozed for 7.4/8.2 releases.</p> - <hr /><h2><a name="Webcamd" href="#Webcamd" id="Webcamd">Webcamd</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.selasky.org/hans_petter/video4bsd" title="http://www.selasky.org/hans_petter/video4bsd"></a></td><td> - URL: <a href="http://www.selasky.org/hans_petter/video4bsd" title="">http://www.selasky.org/hans_petter/video4bsd</a></td></tr><tr><td><a href="http://www.freshports.org/multimedia/webcamd/" title="http://www.freshports.org/multimedia/webcamd/"></a></td><td> - URL: <a href="http://www.freshports.org/multimedia/webcamd/" title="">http://www.freshports.org/multimedia/webcamd/</a></td></tr></table><p> - Contact: - Hans Petter - Selasky - <<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>> - </p> - <p>Webcamd is a small daemon that enables about 1500 different USB - based webcam, DVB and remote control USB devices under the - FreeBSD-8.0 and later operating system. The webcam daemon is - basically an application which is a port of Video4Linux USB drivers - into userspace on FreeBSD. The daemon currently depends on libc, - pthreads, libusb and libcuse4bsd.</p> - - <p>During Q3 2010 webcamd got manpages thanks to Dru Lavigne.</p> - <h3>Open tasks:</h3><ol><li>I hope to get a Google summer of code project this year - building the default Linux Kernel 2.6.37+ and allowing use of - relevant Linux USB device drivers under FreeBSD. Webcamd is not a - replacement for native FreeBSD kernel drivers and will only be used - when no existing FreeBSD drivers exist for a given device staying - clear of any GPLv2 issues. If you are a student and/or is - interested in participating in such a project feel free to send an - e-mail to hselasky@FreeBSD.org.</li></ol><hr /><h2><a name="xz-Compression-for-Packages-and-Log-Files" href="#xz-Compression-for-Packages-and-Log-Files" id="xz-Compression-for-Packages-and-Log-Files">xz Compression for Packages and Log Files</a></h2><p> - Contact: - Martin - Matuska - <<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>> - </p> - <p>Creating and processing xz-compressed packages is now supported - by pkg_create(1), pkg_add(1) and bsdtar(1) in both 9-CURRENT and - 8-STABLE. Users can test working with .txz packages by adding - "PKG_SUFX=.txz" into /etc/make.conf.</p> - - <p>The ports-mgmt/portupgrade utility supports .txz packages from - version 2.4.8 and a patch for ports-mgmt/portmaster has been - submitted but not yet accepted by the author.</p> - - <p>A patch for newsyslog(8) with a rewrite of the use of - compression tools supporting xz compression is under maintainer - review.</p> - <h3>Open tasks:</h3><ol><li>Import xz(1) compression support into newsyslog(8).</li><li>Add .txz package support to ports-mgmt/portmaster.</li><li>Add .txz package support to the FreeBSD port building - cluster (pointyhat).</li><li>Test building all packages in .txz format and compare - results with .tbz.</li></ol><hr /><h2><a name="ZFS-pool-version-28" href="#ZFS-pool-version-28" id="ZFS-pool-version-28">ZFS pool version 28</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html" title="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html"></a></td><td> - URL: <a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html" title="">http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010292.html</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html" title="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html"></a></td><td> - URL: <a href="http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html" title="">http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010321.html</a></td></tr></table><p> - Contact: - Pawel Jakub - Dawidek - <<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>> - <br /> - Contact: - Martin - Matuska - <<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>> - </p> - <p>A new version of the ZFS pool v28 patch was released for - testing, this time for 9-CURRENT and 8-STABLE. Compared to - the previous patch it does include updated boot support, - improved sendfile(2) handling, a compatibility layer with - older ZFS and several other bugfixes.</p> - - <p>If there are no major issues we can expect ZFS v28 imported - into the FreeBSD-CURRENT after 8.2 is released.</p> - <h3>Open tasks:</h3><ol><li>Import of ZFS v28 into FreeBSD-CURRENT.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team-Status-Report" href="#FreeBSD-Bugbusting-Team-Status-Report" id="FreeBSD-Bugbusting-Team-Status-Report">FreeBSD Bugbusting Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats"></a></td><td> - URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting"></a></td><td> - URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/"></a></td><td> - URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr></table><p> - Contact: - Gavin - Atkinson - <<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>> - <br /> - Contact: - Mark - Linimon - <<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>> - <br /> - Contact: - Remko - Lodder - <<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>> - <br /> - Contact: - Volker - Werth - <<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>> - </p> - <p>The number of non-ports PRs has held relatively steady over - the last three months, with a slightly improved resolution rate - being offset by a slightly increased rate of new arrivals. - Ports PRs have increased slightly in numbers, due in part to - the ports freeze in the lead up to the release of FreeBSD 7.4 and - FreeBSD 8.2. The numbers traditionally drop quickly again once the - freeze is lifted.</p> - - <p>In October, Gavin Atkinson and Mark Linimon held a session at - the FreeBSD Developers' Summit at EuroBSDCon, which led to some - productive discussions, and a number of people expressing - interest in becoming more involved with PR triaging and - resolution.</p> - - <p>The bugbusting team continue work on trying to make the - contents of the GNATS PR database cleaner, more accessible and - easier for committers to find and resolve PRs, by tagging PRs - to indicate the areas involved, and by ensuring that there is - sufficient info within each PR to resolve each issue.</p> - - <p>Reports continue to be produced from the PR database, all of - which can be found from the links above. Committers interested - in custom reports are encouraged to discuss requirements with - bugmeister@ - we are happy to create new reports where needs are - identified.</p> - - <p>As always, anybody interested in helping out with the PR queue - is encouraged to do so, the easiest way being to join us on IRC - in #freebsd-bugbusters on EFnet. We are always looking for - additional help, whether your interests lie in triaging incoming - PRs, generating patches to resolve existing problems, or simply - helping with the database housekeeping (identifying duplicate - PRs, ones that have already been resolved, etc). This is a - great way of getting more involved with FreeBSD!</p> - <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with - closing PRs that the team has already analyzed.</li><li>Try to get more non-committers involved with the triaging - of PRs as they come in, and generating patches to fix reported - problems.</li></ol><hr /><h2><a name="Release-Engineering-Team-Status-Report" href="#Release-Engineering-Team-Status-Report" id="Release-Engineering-Team-Status-Report">Release Engineering Team Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td> - URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p> - Contact: - Release Engineering Team - <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>> - </p> - <p>The Release Engineering Team reports the joint release of - FreeBSD 7.4 and 8.2 has been delayed slightly but should be - completed within a week or two of the original schedule: - http://www.FreeBSD.org/releases/7.4R/schedule.html - http://www.FreeBSD.org/releases/8.2R/schedule.html</p> - <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org" title="http://www.FreeBSDFoundation.org"></a></td><td> - URL: <a href="http://www.FreeBSDFoundation.org" title="">http://www.FreeBSDFoundation.org</a></td></tr></table><p> - Contact: - Deb - Goodkin - <<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>> - </p> - <p>We raised $325,000 towards our goal of $350,000 for 2010! This - will allow us to increase our project development and equipment - spending for 2011.</p> - - <p>We were proud to be a sponsor for EuroBSDCon 2010, BSDDay - Argentina 2010, MeetBSD California 2010, and NYBSDCon 2010.</p> - - <p>Completed the Foundation funded projects: DAHDI Project by Max - Khon and BSNMP Improvements by Shteryana Sotirova.</p> - - <p>We kicked off a new project by the University of Melbourne - called Feed-Forward Clock Synchronization Algorithms Project. The - Five New TCP Congestion Control Algorithms for FreeBSD Project by - Swinburne University also officially started.</p> - - <p>We continued our work on infrastructure projects to beef up - hardware for package-building, network-testing, etc. This includes - purchasing equipment as well as managing equipment donations.</p> - - <p>Stop by and visit with us at FOSDEM (Feb 5-6), SCALE (Feb 26), - AsiaBSDCon (March 17-20), and Indiana Linuxfest (March 26).</p> - - <p>Read more about how we supported the project and community by - reading our end-of-year newsletter at: <a href="http://www.FreeBSDFoundation.org/press/2010Dec-newsletter.shtml" shape="rect"> - http://www.FreeBSDFoundation.org/press/2010Dec-newsletter.shtml</a>.</p> - - <p>We are fund-raising for 2011 now! Find out more at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect"> - http://www.FreeBSDFoundation.org/donate/</a>.</p> - <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" href="#DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)" id="DIstributed-Firewall-and-Flow-shaper-Using-Statistical-Evidence-(DIFFUSE)">DIstributed Firewall and Flow-shaper Using Statistical - Evidence (DIFFUSE)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/" title="http://caia.swin.edu.au/urp/diffuse/"></a></td><td> - URL: <a href="http://caia.swin.edu.au/urp/diffuse/" title="">http://caia.swin.edu.au/urp/diffuse/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="http://caia.swin.edu.au/urp/diffuse/downloads.html"></a></td><td> - URL: <a href="http://caia.swin.edu.au/urp/diffuse/downloads.html" title="">http://caia.swin.edu.au/urp/diffuse/downloads.html</a></td></tr></table><p> - Contact: - Sebastian - Zander - <<a href="mailto:szander@swin.edu.au">szander@swin.edu.au</a>> - <br /> - Contact: - Grenville - Armitage - <<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>> - </p> - <p> - <p>DIFFUSE is a system enabling FreeBSD's IPFW firewall subsystem - to classify IP traffic based on statistical traffic - properties.</p> - - <p>With DIFFUSE, IPFW computes statistics (such as packet lengths - or inter-packet time intervals) for observed flows, and uses ML - (machine learning) techniques to assign flows into classes. In - addition to traditional packet inspection rules, IPFW rules may - now also be expressed in terms of traffic statistics or classes - identified by ML classification. This can be helpful when direct - packet inspection is problematic (perhaps for administrative - reasons, or because port numbers do not reliably identify - applications).</p> - - <p>DIFFUSE also enables one instance of IPFW to send flow - information and classes to other IPFW instances, which then can - act on such traffic (e.g. prioritise, accept, deny, etc) - according to its class. This allows for distributed - architectures, where classification at one location in your - network is used to control fire-walling or rate-shaping actions - at other locations.</p> - - <p>In December 2010 we released DIFFUSE v0.1, a set of patches - for FreeBSD-CURRENT. It can be downloaded from the project's web - site. The web site also contains a more comprehensive - introduction, including application examples, links to related - work and documentation describing the software design.</p> - - <p>We hope to release DIFFUSE v0.2 soon. Keep an eye on the - freebsd-ipfw and freebsd-net mailing lists for project-related - announcements.</p> - </p> - <hr /><h2><a name="Ethernet-Switch-Framework" href="#Ethernet-Switch-Framework" id="Ethernet-Switch-Framework">Ethernet Switch Framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://loos.no-ip.org/rspro/switch-1.diff" title="http://loos.no-ip.org/rspro/switch-1.diff"></a></td><td> - URL: <a href="http://loos.no-ip.org/rspro/switch-1.diff" title="">http://loos.no-ip.org/rspro/switch-1.diff</a></td></tr></table><p> - Contact: - Luiz - Otavio O. Souza - <<a href="mailto:loos.br@gmail.com">loos.br@gmail.com</a>> - </p> - <p>Implementation of a framework for ethernet switch control - (directly connected to the ethernet MAC controller) usually found - on embedded systems. Currently based on ifconfig keywords, adds the - vlan control (filter/pass) on each switch port and adds the - possibility for the management of media state on interfaces with - multiple PHYs.</p> - - <p>Currently, the code supports the IP175D (from some mikrotik - routerboards) and AR8316 (from Ubiquiti RSPRO) switches.</p> - <h3>Open tasks:</h3><ol><li>Finish the IP175C driver (and maybe IP178x).</li><li>Better integration with miibus (rewrite of switchbus).</li><li>Fix (some) ifconfig keywords (better keywords, better usage - compatibility).</li><li>Export the ports statistics through SNMP (if available on - switch chip).</li><li>Add a swctl tool (?) for global settings management.</li><li>Write usage examples and the man page information about the - new ifconfig(8) keywords.</li></ol><hr /><h2><a name="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" href="#Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD" id="Five-New-TCP-Congestion-Control-Algorithms-for-FreeBSD">Five New TCP Congestion Control Algorithms for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/freebsd/5cc/" title="http://caia.swin.edu.au/freebsd/5cc/"></a></td><td> - URL: <a href="http://caia.swin.edu.au/freebsd/5cc/" title="">http://caia.swin.edu.au/freebsd/5cc/</a></td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td> - URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/projects.shtml" title="http://www.FreeBSDFoundation.org/projects.shtml"></a></td><td> - URL: <a href="http://www.FreeBSDFoundation.org/projects.shtml" title="">http://www.FreeBSDFoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="http://people.FreeBSD.org/~lstewart/patches/5cc/"></a></td><td> - URL: <a href="http://people.FreeBSD.org/~lstewart/patches/5cc/" title="">http://people.FreeBSD.org/~lstewart/patches/5cc/</a></td></tr></table><p> - Contact: - David - Hayes - <<a href="mailto:dahayes@swin.edu.au">dahayes@swin.edu.au</a>> - <br /> - Contact: - Lawrence - Stewart - <<a href="mailto:lastewart@swin.edu.au">lastewart@swin.edu.au</a>> - <br /> - Contact: - Grenville - Armitage - <<a href="mailto:garmitage@swin.edu.au">garmitage@swin.edu.au</a>> - <br /> - Contact: - Rui - Paulo - <<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>> - <br /> - Contact: - Bjoern - Zeeb - <<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>> - </p> - <p>The project is nearing completion, with the following code - already available in the svn head branch:</p> - - <ul> - <li>Modular congestion control framework.</li> - - <li>Modularised implementations of NewReno, CUBIC and HTCP - congestion control algorithms.</li> - - <li>Khelp (Kernel Helper) and Hhook (Helper Hook) - frameworks.</li> - - <li>Basic Khelp/Hhook integration with the TCP stack.</li> - </ul> - - <p>The ERTT (Enhanced Round Trip Time) Khelp module is days away - from being imported, which will then pave the way for the delay - based congestion control algorithms to follow. Finally, a large - documentation dump will be committed in the form of new and - updated man pages.</p> - - <p>We anticipate the project will conclude around the end of - January 2011.</p> - <h3>Open tasks:</h3><ol><li>Import the ERTT Khelp module.</li><li>Import the VEGAS, HD and CHD delay based congestion control - algorithm modules.</li><li>Import the documentation dump for all the code - contributed/developed as part of the project.</li></ol><hr /><h2><a name="FreeBSD-802.11n" href="#FreeBSD-802.11n" id="FreeBSD-802.11n">FreeBSD 802.11n</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff" title="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff"></a></td><td> - URL: <a href="http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff" title="">http://wiki.FreeBSD.org/AdrianChadd/AtherosStuff</a></td></tr></table><p> - Contact: - Adrian - Chadd - <<a href="mailto:adrian@FreeBSD.org">adrian@FreeBSD.org</a>> - </p> - <ul> - <li>Net80211 station mode works in 2.4ghz HT/20 mode. HT/40 and - 5ghz do not currently work.</li> - - <li>Basic 802.11 TX and RX on the AR9160 works, from MCS0 to - MCS15</li> - - <li>TX A-MPDU and A-MSDU do not currently implemented - so no - aggregate TX will happen</li> - - <li>RX A-MPDU and A-MSDU is implemented and is supposed to work - but does not — this needs to be debugged</li> - - <li>802.11n RTS/CTS protection for legacy packets does not - currently work. There is some magic required to fix the TX packet - length. This is in progress.</li> - - <li>WPA2 now works - a commit which enabled the hardware - multicast broke AES-CCMP encryption on at least the AR9160. - Further investigation is needed to fix this (and any other - hardware encryption bugs that are lurking.</li> - </ul> - <hr /><h2><a name="FreeBSD-VirtIO-Network-Driver" href="#FreeBSD-VirtIO-Network-Driver" id="FreeBSD-VirtIO-Network-Driver">FreeBSD VirtIO Network Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.linux-kvm.org/page/Virtio" title="http://www.linux-kvm.org/page/Virtio"></a></td><td> - URL: <a href="http://www.linux-kvm.org/page/Virtio" title="">http://www.linux-kvm.org/page/Virtio</a></td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html" title="http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html"></a></td><td> - URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html" title="">http://lists.FreeBSD.org/pipermail/freebsd-current/2011-January/022036.html</a></td></tr></table><p> - Contact: - Bryan - V. - <<a href="mailto:deboomerang@gmail.com">deboomerang@gmail.com</a>> - </p> - <p>VirtIO is a device framework offered by KVM/Qemu and Virtualbox - to allow guests to achieve better I/O performance. A beta - network driver was made available earlier this month, and work - continues on completing the block device and refinements the - existing network driver.</p> - <hr /><h2><a name="Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)" href="#Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)" id="Generic-IEEE-802.3-annex-31B-full-duplex-flow-control-support-for-Ethernet-in-mii(4)">Generic IEEE 802.3 annex 31B full duplex flow control support - for Ethernet in mii(4)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://en.wikipedia.org/wiki/Ethernet_flow_control" title="http://en.wikipedia.org/wiki/Ethernet_flow_control"></a></td><td> - URL: <a href="http://en.wikipedia.org/wiki/Ethernet_flow_control" title="">http://en.wikipedia.org/wiki/Ethernet_flow_control</a></td></tr></table><p> - Contact: - Marius - Strobl - <<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>> - </p> - <p>In r213878 a NetBSD-compatible mii_attach() was added to mii(4) - as an replacement for mii_phy_probe() and subsequently all Ethernet - device drivers in the tree which use this framework were converted - to take advantage of the former. This allowed to considerably clean - up mii(4) as well as the converted MAC and PHY drivers and get rid - of quite a few hacks, amongst others the infamous "EVIL HACK". - However, the main motivation of this change was to allow the - addition of generic IEEE 802.3 annex 31B full duplex flow control - support to mii(4), which was ported from NetBSD but also enhanced - and fixed quite a bit and committed in r215297. Along with this - bge(4), bce(4), msk(4), nfe(4) and stge(4) as well as brgphy(4), - e1000phy(4) and ip1000phy(4), which previously all implemented - their own flow control support based on mostly undocumented special - media flags separately, were converted to take advantage of the - generic support. At least for CURRENT this means that these drivers - now no longer unconditionally advertise support for flow control - but only do so if flow control was selected as media option. The - reason for implementing the generic flow control support that way - was to allow it to be switched on and off via ifconfig(8) with the - PHY specific default to typically being off in order to protect - from unwanted effects. Subsequently support for flow control based - on the generic support was added to alc(4), fxp(4), cas(4), gem(4), - jme(4), re(4) and xl(4) as well as atphy(4), bmtphy(4), gentbi(4), - inphy(4), jmphy(4), nsgphy(4), nsphyter(4) and rgephy(4). For - several of the remaining Ethernet drivers it also would only - require minor changes to enable flow control support if supported - by the respective MAC. Due to the fact that each implementation - should be thoroughly tested and tuned this was only done for - drivers were hardware was available though.</p> - - <p>An example for identifying support for flow control based on the - generic implementation in the dmesg-output for a certain - MAC-PHY-combination would be:</p> - - <blockquote>bge0: <Broadcom NetXtreme Gigabit Ethernet - Controller, ASIC rev. 0x002003> mem 0 - xfe010000-0xfe01ffff,0xfe000000-0xfe00ffff irq 25 at device 2.0 on - pci2 - <br clear="none" /> - - bge0: CHIP ID 0x00002003; ASIC REV 0x02; CHIP REV 0x20; PCI-X - <br clear="none" /> - - miibus0: <MII bus> on bge0 - <br clear="none" /> - - brgphy0: <BCM5704 10/100/1000baseTX PHY> PHY 1 on miibus0 - <br clear="none" /> - - brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, - 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, - <strong>auto-flow</strong> - </blockquote> - - <p>or in the output of <kbd>ifconfig -m</kbd> for a given device:</p> - - <blockquote>supported media: - <blockquote>media autoselect - <em>mediaopt flowcontrol</em> - </blockquote> - </blockquote> - - <p>The latter also is what one would use to enable flow control for - such a device, i.e.:</p> - - <blockquote>ifconfig bge0 media autoselect mediaopt - flowcontrol</blockquote> - - <p>or in order to turn it off again:</p> - - <blockquote>ifconfig bge0 media autoselect -mediaopt - flowcontrol</blockquote> - - <p>Note that some PHY drivers, currently only rgephy(4) though, also - support enabling flow control support when using manual media - configuration like in the following example:</p> - - <blockquote>ifconfig re0 media autoselect mediaopt - full-fuplex,flowcontrol</blockquote> - - <p>In CURRENT this can also be further abbreviated (support for this - will eventually be merged back into the supported stable branch(es) - but not be present in 7.4-RELEASE or 8.2-RELEASE) as:</p> - - <blockquote>ifconfig re0 media auto mediaopt fdx,flow</blockquote> - - <p>For a device which has successfully negotiated flow control support - with its link partner will report it in the output of - <kbd>ifconfig</kbd> along with the available directions like in the - following example:</p> - - <blockquote>media: Ethernet autoselect <flowcontrol> - (100baseTX <full-duplex, - <em>flowcontrol,rxpause,txpause</em>>)</blockquote> - - <p>Another thing that was introduced with r215297 was generic support - for setting 1000baseT master mode via a media option when using - manual media configuration. Consequently, brgphy(4), ciphy(4), - e1000phy(4) as well as ip1000phy(4) have been converted to take - advantage of this generic support. At least for CURRENT this means - that these drivers now no longer take the link0 parameter for - selecting master mode but the master media option has to be used - instead like in the following example:</p> - - <blockquote>ifconfig bge0 media 1000baseT mediaopt - full-duplex,master</blockquote> - - <p>Selection of master mode now is also available with all other PHY - drivers supporting 1000baseT.</p> - - <p>With the exception of the media option abbreviations all of the - above mentioned changes were merged into 7-STABLE in r215879 and - into 8-STABLE in r215881 respectively. This means that they will be - part of 7.4-RELEASE and 8.2-RELEASE. In order to no break POLA, - unlike as in CURRENT bge(4), bce(4), msk(4), nfe(4) and stge(4) - were changed to continue to always advertise support of flow - control to their link partners in these stable branches with no way - to turn that off as they also did before with their custom - implementations. Additionally, brgphy(4), ciphy(4), e1000phy(4) as - well as ip1000phy(4) were changed to still also accept the link0 - parameter in addition to the master media option for setting master - mode.</p> - <h3>Open tasks:</h3><ol><li>We actually miserably fail to properly document the available - media types and options in manual pages. For example several of the - media lists in manual pages of MAC drivers like bge(4) already were - outdated and with the addition of generic flow control and - 1000baseT master mode support these are now even more outdated. Yet - worse is the fact that for MAC drivers which use the mii(4) - framework it is technically just plain wrong to include these lists - in their manual page as the PHY drivers actually are responsible - for handling the media types and options. However, given that the - PHY drivers determine the available media types and options mostly - dynamically at run-time it generally makes no sense to have static - documentation of these in their manual pages (apart from the fact - that we currently have no manual pages for PHY drivers). One good - way out of this should be to replace the media lists in MAC drivers - using mii(4) with just a note to check the output of - <kbd>ifconfig -m</kbd> - to get a list of the media types and options actually supported by - a given device and to add a generic ifmedia(4) manual page which - provides some general background information about media types and - options similar to what NetBSD and OpenBSD also have.</li></ol><hr /><h2><a name="IPv6-and-VIMAGE" href="#IPv6-and-VIMAGE" id="IPv6-and-VIMAGE">IPv6 and VIMAGE</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://ecdysis.viagenie.ca/" title="http://ecdysis.viagenie.ca/">NAT64 patches for pf</a></td><td> - URL: <a href="http://ecdysis.viagenie.ca/" title="NAT64 patches for pf">http://ecdysis.viagenie.ca/</a></td></tr></table><p> - Contact: - Bjoern A. - Zeeb - <<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>> - </p> - <p>During the last quarter a lot of work was spent on quality time - hunting down and fixing open bugs and races in the network stack, - mostly IPv6, as well as testing and getting virtualized network - stack parts more stable. Tests for the pf(4) firewall update were - started with VIMAGE. In addition Viagenie's NAT64 patch was ported - over.</p> - <hr /><h2><a name="TCP-SMP-scalability-project" href="#TCP-SMP-scalability-project" id="TCP-SMP-scalability-project">TCP SMP scalability project</a></h2><p> - Contact: - Robert - Watson - <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>> - </p> - <p>A long-running TCP SMP scalability project is beginning to wrap - up, with the goal of committing a large outstanding patch to the - FreeBSD 9.x tree in the next month. This work implements a - derivative of Willman, Rixner, and Cox's TCP connection group - model, blended with support for hardware load distribution - features in contemporary NICs (including RSS). Additional - software distribution support can do work redistribution based - on new notions of CPU affinity for individual TCP - connections.</p> - - <p>On-going work is refining performance on non-RSS supporting - configurations, and adding APIs to allow socket affinity to be - queried (and where supported) set by applications. These - changes significantly improve network scalability by reducing - global lock contention, encouraging CPU affinity for - connections, and avoiding cache line contention. The goal is - to allow steady-state TCP connections to use only CPU-local - cache lines, with work distributed to all CPUs. Current - performance results are extremely promising.</p> - - <p>This project has been sponsored by Juniper Networks.</p> - <h3>Open tasks:</h3><ol><li>Allow the hash model to be selected at boot-time or run-time - rather than compile-time; currently "options RSS" enables RSS - support unconditionally — for systems without RSS NICs, - this leads to a small one-time performance penalty at the - creation of each call to bind() or connect().</li><li>Add missing socket options to query (and override) default - CPU affinity for connections, which is derived from the active - software or hardware hash model.</li><li>Teach the network stack and appropriate NIC drivers to - propagate software-overridden connection affinity to hardware - using new device driver ioctls for managing TCAMs and hardware - hash tables.</li><li>Refine software redistribution of work in the event that - there are fewer hardware queues than available CPU threads in - which to process packets; the current prototype is able to do - this with significant performance benefits, but the model - requires refining.</li><li>Experiment with (and measure) software work redistribution - at run-time based on RSS bucket rearrangement. This will - require a new event notification to device drivers so that - they can update hardware caches of the network stack's - authoritative table.</li><li>Commit.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="Resource-Containers" href="#Resource-Containers" id="Resource-Containers">Resource Containers</a></h2><p> - Contact: - Edward Tomasz - Napierala - <<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>> - </p> - <p>The goal of this project is to implement resource containers and - a per-jail resource limits mechanism, so that system administrators - can partition resources like memory or CPU between jails and - prevent users from DoS-ing the whole system. Project is close to - completion. One big item that needs to be fixed before releasing a - patch for people to test is %CPU accounting; initial idea of just - using %CPU calculated by the scheduler turned out to be useless. - Implementing it cleanly will also make it easier to support other - similar resources (e.g. writes-per-second) in the future.</p> - <hr /><h2><a name="SYSCTL-Type-Safety" href="#SYSCTL-Type-Safety" id="SYSCTL-Type-Safety">SYSCTL Type Safety</a></h2><p> - Contact: - Matthew - Fleming - <<a href="mailto:mdf@FreeBSD.org">mdf@FreeBSD.org</a>> - </p> - <p>I started upstreaming a patch from Isilon that adds - type-checking to the various SYSCTL_FOO and SYSCTL_ADD_FOO macros - for various scalar types, which has turned into quite the - discussion on the src mailing list. The type-checking macros are - committed to sys/sysctl.h but under #if 0.</p> - <h3>Open tasks:</h3><ol><li>As of right now, it looks like I will be rolling a new sysctl - macro for the kernel that detects they type at compile time and - does the Right Thing. Existing uses of the legacy SYSCTL_FOO and - SYSCTL_ADD_FOO for scalar types can be replaced, and will probably - turn into invocations of the new interface via preprocessor - macro.</li></ol><hr /><h2><a name="TRIM-support-for-UFS" href="#TRIM-support-for-UFS" id="TRIM-support-for-UFS">TRIM support for UFS</a></h2><p> - Contact: - Kirk - McKusick - <<a href="mailto:mckusick@FreeBSD.org">mckusick@FreeBSD.org</a>> - <br /> - Contact: - Konstantin - Belousov - <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>> - </p> - <p>TRIM support for UFS is implemented in HEAD. Potentially, this - may increase the steady speed and longevity of SSDs.</p> - - <p>Due to concerns with the speed of TRIM operations on many SSDs, - and not a lot of experience with the real-world behaviour, the - support is off by default, and should be enabled on the - per-filesystem basis.</p> - <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="mdocml-Replacing-groff-For-manpage-Rendering" href="#mdocml-Replacing-groff-For-manpage-Rendering" id="mdocml-Replacing-groff-For-manpage-Rendering">mdocml Replacing groff For manpage Rendering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mdocml.bsd.lv/" title="http://mdocml.bsd.lv/"></a></td><td> - URL: <a href="http://mdocml.bsd.lv/" title="">http://mdocml.bsd.lv/</a></td></tr><tr><td><a href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml" title="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml"></a></td><td> - URL: <a href="https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml" title="">https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=mdocml</a></td></tr></table><p> - Contact: - Ulrich - Spörlein - <<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>> - </p> - <p>Kristaps' groff-replacement (only for rendering manual pages) is - already available in NetBSD and OpenBSD, and used to render the - base system manpages for the latter. This project aims to do - similar things for FreeBSD. Since the last status report, mdocml - has grown rudimentary tbl(1) support and a whole lot of bugfixes - have gone in. A groff port has been created and needs some more - testing before it can be committed to the tree. Also the - WITHOUT_GROFF support in base has been fleshed out and is awaiting - review before commit.</p> - <h3>Open tasks:</h3><ol><li>Get ru@ to review WITHOUT_GROFF changes.</li><li>Get textproc/groff tested and committed.</li><li>Push more mdoc fixes into the tree.</li><li>Import mandoc(1), switch to catpages for base. Discuss future - of groff in base wrt. share/doc.</li><li>Supply necessary ports infrastructure to opt-in to - mandoc(1).</li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project-Status-Report" href="#The-FreeBSD-German-Documentation-Project-Status-Report" id="The-FreeBSD-German-Documentation-Project-Status-Report">The FreeBSD German Documentation Project Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">Website of the FreeBSD German Documentation Project.</a></td><td> - URL: <a href="http://doc.bsdgroup.de" title="Website of the FreeBSD German Documentation Project.">http://doc.bsdgroup.de</a></td></tr></table><p> - Contact: - Johann - Kois - <<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 committers to the German Documentation Project managed to - update the German documentation just in time to get the changes - included into the next FreeBSD releases. The website translations - were also kept in sync with the ones on FreeBSD.org.</p> - - <p>We tried to re-activate committers who did not contribute for - some time but most of them are currently unable to free up enough - time. We hope to gain fresh contributor blood as we are getting - occasional reports about bugs and grammar in the german - translation.</p> - <h3>Open tasks:</h3><ol><li>Submit grammar, spelling or other errors you find in the - german documents and the website.</li><li>Translate more articles and other open handbook - sections.</li></ol><hr /><h2><a name="The-FreeBSD-Japanese-Documentation-Project" href="#The-FreeBSD-Japanese-Documentation-Project" id="The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ja/" title="http://www.FreeBSD.org/ja/">Japanese FreeBSD Web Pages</a></td><td> - URL: <a href="http://www.FreeBSD.org/ja/" title="Japanese FreeBSD Web Pages">http://www.FreeBSD.org/ja/</a></td></tr><tr><td><a href="http://www.jp.FreeBSD.org/doc-jp/" title="http://www.jp.FreeBSD.org/doc-jp/">The FreeBSD Japanese Documentation Project Web Page</a></td><td> - URL: <a href="http://www.jp.FreeBSD.org/doc-jp/" title="The FreeBSD Japanese Documentation Project Web Page">http://www.jp.FreeBSD.org/doc-jp/</a></td></tr></table><p> - Contact: - Hiroki - Sato - <<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>> - <br /> - Contact: - Ryusuke - Suzuki - <<a href="mailto:ryusuke@FreeBSD.org">ryusuke@FreeBSD.org</a>> - </p> - <p>Although there is no radical change in this effort since the - last report, the www/ja and doc/ja_JP.eucJP/books/handbook have - constantly been updated. During this period, generating translated - RSS feed for newsflash was started and links to the manual pages - were fixed in the Books and Articles documentation. Some more - progress has been made in the Porter's Handbook and Contributing to - FreeBSD as well.</p> - <h3>Open tasks:</h3><ol><li>Further translation of the FreeBSD <a href="http://www.FreeBSD.org/doc/ja_JP.eucJP/books/handbook/" shape="rect"> - Handbook</a> and contents of the - <a href="http://www.FreeBSD.org" shape="rect">www.FreeBSD.org</a> - website to the Japanese language.</li><li>Pre-/post-commit review of the translation.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="FreeBSD-Services-Control-(fsc)" href="#FreeBSD-Services-Control-(fsc)" id="FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p> - Contact: - Tom - Rhodes - <<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>> - </p> - <p>FreeBSD Services Control is a mix of binaries which - integrate into the rc.d system and provide for service - (daemon) monitoring. It knows about signals, pidfiles, - and uses very little resources.</p> - - <p>The fscd utilities will be set up as a port and, hopefully, - dropped into the ports collection in the coming weeks. This - will allow easier testing by everyone and it should make - migration into -CURRENT much easier.</p> - <hr /><h2><a name="GEOM-based-ataraid(4)-Replacement-—-geom_raid" href="#GEOM-based-ataraid(4)-Replacement-—-geom_raid" id="GEOM-based-ataraid(4)-Replacement-—-geom_raid">GEOM-based ataraid(4) Replacement — geom_raid</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~mav/graid_design.h" title="http://people.FreeBSD.org/~mav/graid_design.h">General design description.</a></td><td> - URL: <a href="http://people.FreeBSD.org/~mav/graid_design.h" title="General design description.">http://people.FreeBSD.org/~mav/graid_design.h</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/projects/graid/" title="http://svn.FreeBSD.org/viewvc/base/projects/graid/">Project SVN branch.</a></td><td> - URL: <a href="http://svn.FreeBSD.org/viewvc/base/projects/graid/" title="Project SVN branch.">http://svn.FreeBSD.org/viewvc/base/projects/graid/</a></td></tr></table><p> - Contact: - Alexander - Motin - <<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>> - <br /> - Contact: - M. Warner - Losh - <<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>> - </p> - <p>New project started to create GEOM-based replacement for - ataraid(4) — software RAID, that will be obsoleted by - migration to the new CAM-based ATA implementation.</p> - - <p>This implementation planned with accent to modular design, - that includes common core and two sets of modules, handling data - transformations (RAID levels) and on-disk metadata formats - specifics. Such design should make further extension easier.</p> - - <p>At this moment work focused around RAID0/RAID1 transformations - and Intel metadata format. Module is now able to read, write and - create Intel volumes. Error recovery and rebuild work is now in - progress. Support for other RAID levels and metadata formats, - supported by ataraid(4), planned later.</p> - - <p>This project is sponsored by Cisco Systems, Inc.</p> - <h3>Open tasks:</h3><ol><li>Complete error recovery/rebuild work and stabilize modules - API.</li><li>Implement metadata modules for other formats.</li><li>Implement transformation modules for other RAID - levels.</li></ol><hr /><h2><a name="gpart-Improvements" href="#gpart-Improvements" id="gpart-Improvements">gpart Improvements</a></h2><p> - Contact: - Andrey V. - Elsukov - <<a href="mailto:ae@FreeBSD.org">ae@FreeBSD.org</a>> - </p> - <p>GEOM class PART is the default disk partitioning class since - FreeBSD 8.0. Compared to 8.1 now it does have several new features: - Partition resizing. New "gpart resize" subcommand was implemented - for all partitioning schemes but EBR. GPT recovering. Guid - Partition Table does have redundant metadata and it can be - recovered when some of them is damaged. New "gpart recover" - subcommand was implemented for that purpose. Ability to - backup/restore of partition table. New "gpart backup" and "gpart - restore" subcommands were implemented.</p> - <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Bringing-up-OMAP3" href="#Bringing-up-OMAP3" id="Bringing-up-OMAP3">Bringing up OMAP3</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff" title="http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff">an old patch for arm</a></td><td> - URL: <a href="http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff" title="an old patch for arm">http://people.FreeBSD.org/~raj/patches/arm/dove_v6.diff</a></td></tr></table><p> - Contact: - Warner - Losh - <<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>> - <br /> - Contact: - Mohammed - Farrag - <<a href="mailto:mfarrag@FreeBSD.org">mfarrag@FreeBSD.org</a>> - </p> - <p>The attached file is an old patch for ARM. We are developing new - patch and then we are going toward Porting OMAP3.</p> - <hr /><h2><a name="FreeBSD-on-the-Playstation-3" href="#FreeBSD-on-the-Playstation-3" id="FreeBSD-on-the-Playstation-3">FreeBSD on the Playstation 3</a></h2><p> - Contact: - Nathan - Whitehorn - <<a href="mailto:nwhitehorn@FreeBSD.org">nwhitehorn@FreeBSD.org</a>> - </p> - <p>On January 5, support for the Playstation 3 was imported into - FreeBSD 9.0-CURRENT. This port is still somewhat raw (only - netbooting is supported, no access to the SPUs, etc.), but hardware - support should be more fleshed out by the time FreeBSD 9.0 is - released. The port uses the OtherOS mechanism, and so requires a - "fat" console with firmware earlier than 3.21.</p> - <h3>Open tasks:</h3><ol><li>SATA driver.</li><li>Sound support.</li><li>SPU driver.</li></ol><hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-on-ec2/" title="http://www.daemonology.net/freebsd-on-ec2/">FreeBSD/EC2 status page</a></td><td> - URL: <a href="http://www.daemonology.net/freebsd-on-ec2/" title="FreeBSD/EC2 status page">http://www.daemonology.net/freebsd-on-ec2/</a></td></tr></table><p> - Contact: - Colin - Percival - <<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>> - </p> - <p>FreeBSD is now able to run on t1.micro instances in the Amazon - EC2 cloud. FreeBSD 9.0 is not very stable, but it seems likely that - FreeBSD 8.2-RELEASE will approach the stability normally expected - of FreeBSD.</p> - - <p>A list of available FreeBSD AMIs (EC2 machine images) appears on - the FreeBSD/EC2 status page.</p> - <h3>Open tasks:</h3><ol><li>Bring FreeBSD to a wider range of EC2 instance types.</li><li>Completely rework the locking in head/sys/i386/xen/pmap.c to - eliminate races and make 9.0-CURRENT stable under - paravirtualization.</li><li>Track down several possibly-related problems with scheduling - and timekeeping.</li><li>Fix other issues shown on the FreeBSD/EC2 status page.</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p> - Contact: - Marius - Strobl - <<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>> - </p> - <p>CPUTYPE support for sparc64 has been added to CURRENT in - r216820. The three flavors currently supported are - "ultrasparc", "ultrasparc3" and "v9". So it is now possible to - let the compiler produce code optimize for the family of - UltraSPARC-III CPUs by setting CPUTYPE to "ultrasparc3". - Setting it to "ultrasparc" as well as omitting it completely - optimizes for UltraSPARC-I/II family CPUs as before. Support - for generating generic 64-bit V9 code was mainly added for - reference purposes. As it turned out, at least for SPARC64-V - CPUs running code optimized for UltraSPARC-III CPUs does not - perform measurably better than UltraSPARC-I/II one though so - the default is just fine for these. This change was merged into - 7-STABLE in r217005 and into 8-STABLE in r217004 respectively, - neither 7.4-RELEASE nor 8.2-RELEASE will include it - though.</p> - - <p>Support for a certain feature available with - UltraSPARC-III+ and greater, i.e. with all sun4u CPUs following - the original UltraSPARC-III, has been added to CURRENT in - r216803. The net effect of this change is that we now can use a - kernel TSB and thus a kernel address space of virtually any - size up to the full 64-bit address space on machines equipped - with these CPUs, apart from the fact that 1GB of address space - still takes up 4MB worth of data structures. Before, the - theoretical limit was 16GB due to the fact that the MMUs of - these UltraSPARC CPUs only have 16 lockable TLB slots - (UltraSPARC-I/II have 64 and SPARC64 CPUs again have at least - 32), with the actual limit being several GB below that because - we need some of these slots also for mapping the PROM, the - kernel itself and in MP-systems the per-CPU page. Currently, - the kernel TSB and thus the kernel virtual address space is now - always sized one time the physical memory present in these - machines with the plan being to actually allow to it extend - beyond the size of the RAM as this helps especially ZFS. Most - of this is implemented by patching the instructions used to - access the kernel TSB based on the CPU present, so the run-time - overhead of this change is rather low. Once it is also enabled - and successfully tested with SPARC64 CPUs this change will be - merged back into the supported stable branch(es).</p> - - <p>Theoretically it should be also possible to use the same - approach for the user TSB, which already is not locked into the - TLB but can cause nested traps. However, for reasons I do not - understand yet, OpenSolaris only does this with SPARC64 CPUs. - On the other hand I think that also using it for the user TSB - and thus avoiding nested traps would get us closer to running - the FreeBSD/sparc64 code on machines equipped with sun4v CPUs, - which only supports trap level 0 and 1, too, so eventually we - could have a single kernel which runs on both sun4u and sun4v - machines (as does Linux and OpenBSD).</p> - - <p>Work on adding support for Sun Fire 3800 and similar models - has begun but still is in its early stages.</p> - <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium" href="#Chromium" id="Chromium">Chromium</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.chromium.org/Home" title="http://www.chromium.org/Home">Chromium homepage</a></td><td> - URL: <a href="http://www.chromium.org/Home" title="Chromium homepage">http://www.chromium.org/Home</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~bapt/chrome9-fbsd.png" title="http://people.FreeBSD.org/~bapt/chrome9-fbsd.png">Screenshot</a></td><td> - URL: <a href="http://people.FreeBSD.org/~bapt/chrome9-fbsd.png" title="Screenshot">http://people.FreeBSD.org/~bapt/chrome9-fbsd.png</a></td></tr></table><p> - Contact: - René - Ladan - <<a href="mailto:freebsd-chromium@FreeBSD.org">freebsd-chromium@FreeBSD.org</a>> - </p> - <p>We are working on updating the Chromium web browser in our ports - to stay up to date with the latest supported release. We currently - have the Chromium 9 beta running, but not all features are fully - implemented and the port still needs some polish before it can be - committed to the Ports Collection. We have also been making - arrangements with Google to merge our work with their upstream, - which should ease the number of features and fixes we have to - maintain for ourselves in the future. Our first release should be - in a few weeks and coincide with the official release of Chromium - 9.</p> - <hr /><h2><a name="FreeBSD-as-Home-Theater-PC" href="#FreeBSD-as-Home-Theater-PC" id="FreeBSD-as-Home-Theater-PC">FreeBSD as Home Theater PC</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/HTPC" title="http://wiki.FreeBSD.org/HTPC"></a></td><td> - URL: <a href="http://wiki.FreeBSD.org/HTPC" title="">http://wiki.FreeBSD.org/HTPC</a></td></tr></table><p> - Contact: - Bernhard - Froehlich - <<a href="mailto:decke@FreeBSD.org">decke@FreeBSD.org</a>> - <br /> - Contact: - Juergen - Lock - <<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>> - </p> - <p>FreeBSD could be a much better platform for a Home Theater PC - than it currently is. We are focusing on improving support for - media center applications. Extending the major ports (MythTV, VDR, - XBMC) and create some documentation to guide interested people.</p> - <h3>Open tasks:</h3><ol><li>Improve remote control support in webcamd and with - lirc.</li><li>Port more Media Center applications (Enna, me-tv, ...).</li><li>Create a small guide on how to build a great FreeBSD Home - Theater PC.</li></ol><hr /><h2><a name="Port-Sandbox" href="#Port-Sandbox" id="Port-Sandbox">Port-Sandbox</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html" title="http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html">A little bit about</a></td><td> - URL: <a href="http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html" title="A little bit about">http://www.arjmobile.com/Marcelo_Araujo/Blog/Entries/2010/11/22_Port-sandbox.html</a></td></tr><tr><td><a href="http://gitorious.org/port-sandbox/port-sandbox/trees/master" title="http://gitorious.org/port-sandbox/port-sandbox/trees/master">Source</a></td><td> - URL: <a href="http://gitorious.org/port-sandbox/port-sandbox/trees/master" title="Source">http://gitorious.org/port-sandbox/port-sandbox/trees/master</a></td></tr><tr><td><a href="http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html" title="http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html">Screenshots</a></td><td> - URL: <a href="http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html" title="Screenshots">http://www.arjmobile.com/Marcelo_Araujo/My_Albums/Pages/Port-Sandbox.html</a></td></tr></table><p> - Contact: - Marcelo - Araujo - <<a href="mailto:araujo@FreeBSD.org">araujo@FreeBSD.org</a>> - </p> - <p>Port-Sandbox now works properly and it is able to run by itself - through an embedded web server and bring a lot of information about - the port build process and all dependencies related. Currently - Port-Sandbox is in the final stage and needs only only a few code - changes, more tests and should also be included in the ports - tree.</p> - <h3>Open tasks:</h3><ol><li>Change the way how it connects to database, fix it to maintain - a persistent connection.</li><li>Remove any kind of internal configuration from source code to - an external file configuration.</li><li>Create a Port-Sandbox port with all dependencies related to - it and test it in a clean system.</li><li>Create some documentation to let other people to keep - helping Port-Sandbox to grow up.</li><li>Finally, release it.</li></ol><hr /><h2><a name="Portmaster" href="#Portmaster" id="Portmaster">Portmaster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster-proposal.html" title="http://dougbarton.us/portmaster-proposal.html"></a></td><td> - URL: <a href="http://dougbarton.us/portmaster-proposal.html" title="">http://dougbarton.us/portmaster-proposal.html</a></td></tr></table><p> - Contact: - Doug - Barton - <<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>> - </p> - <p>Portmaster version 3.6.1 is now in the ports tree, and the - emphasis in the last year has been on improving the stability and - performance of existing features, with a few new features sprinkled - in. A lot of work has gone into error handling, both for unexpected - states in the ports system and for user input. For example, all - prompts are now wrapped in code to verify that what was entered was - one of the valid options.</p> - - <p>Perhaps the most interesting new element is that for the - features -e, -s, --clean-distfiles, --clean-packages, - --check-depends and --check-port-dbdir you can now specify either - -y or -n to automatically provide the corresponding answer to the - yes/no questions. The -o, -r, and --index-only options have - received major overhauls, and now either work better or at least as - advertised.</p> - - <p>There has also been a lot of work put into reducing the memory - footprint, especially in the environment variables that are shared - between the parent and child processes. And for those operating - without a local ports tree (--index-only/--packages-only) all of - the features that <em>can</em> - work without the ports tree now do.</p> - - <p>Significant support for the upgrading of operating without a - ports tree was provided by GridFury, LLC. Their support, as well as - the support received from other members of the community continues - to be greatly appreciated.</p> - <h3>Open tasks:</h3><ol><li>There are still interesting features that have been suggested - by users listed on the page above that I have not been able to work - on, but would like to be able to.</li></ol><hr /><h2><a name="Ports-Additions" href="#Ports-Additions" id="Ports-Additions">Ports Additions</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://bigbluebutton.org" title="http://bigbluebutton.org"></a></td><td> - URL: <a href="http://bigbluebutton.org" title="">http://bigbluebutton.org</a></td></tr><tr><td><a href="http://smb4k.berlios.de/" title="http://smb4k.berlios.de/"></a></td><td> - URL: <a href="http://smb4k.berlios.de/" title="">http://smb4k.berlios.de/</a></td></tr><tr><td><a href="http://www.freeswitch.org/" title="http://www.freeswitch.org/"></a></td><td> - URL: <a href="http://www.freeswitch.org/" title="">http://www.freeswitch.org/</a></td></tr></table><p> - Contact: - Josh - Paetzel - <<a href="mailto:jpaetzel@FreeBSD.org">jpaetzel@FreeBSD.org</a>> - </p> - <p>Bigbluebutton has joined the list of ready to run applications - in the ports tree. Dru Lavigne has been instrumental on getting it - to run, as well as offering suggestions for improvements to the - port.</p> - - <p>smb4k was updated to the latest release version, which requires - kde4. This was enough of a change that a new port was created, - net/smb4k-kde4. the initial port went through a number of quick - changes, including a patch to the source code to fix a FreeBSD - source code submitted by PC-BSD's Kris Moore. This application - greatly eases the task of working with samba shares in a FreeBSD - environment.</p> - - <p>Freeswitch is the result of 3 Asterisk developers working on a - VoIP package that fulfills their goals. They have switched away from - a release model to a "just run latest SVN checkout" model. With - the help of Richard Neese and Eric Crist, static snapshots of their - SVN repo have been taken, the port has been modified to use the - newer version, and extensive build and run testing has been - done.</p> - <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> - URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td> - URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html"></a></td><td> - URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td> - URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.FreeBSDish.org/portmgr/" title="http://blogs.FreeBSDish.org/portmgr/"></a></td><td> - URL: <a href="http://blogs.FreeBSDish.org/portmgr/" title="">http://blogs.FreeBSDish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td> - URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/group.php?gid=135441496471197" title="http://www.facebook.com/group.php?gid=135441496471197"></a></td><td> - URL: <a href="http://www.facebook.com/group.php?gid=135441496471197" title="">http://www.facebook.com/group.php?gid=135441496471197</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/"></a></td><td> - URL: <a href="http://tinderbox.marcuscom.com/" title="">http://tinderbox.marcuscom.com/</a></td></tr></table><p> - Contact: - Thomas - Abthorpe - <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>> - <br /> - Contact: - Port - Management Team - <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> - </p> - <p>The ports tree slowly moves up closer to 23,000. The PR count - still remains at about 1000.</p> - - <p>In Q4 we added 2 new committers, took in 2 commit bit for safe - keeping, and welcomed back 4 returning committers.</p> - - <p>The Ports Management team bid farewell to Kris Kennaway in - November 2010. Kris was the root of krismail, the mail we all got - from time to time when ports broke on pointyhat. Kris did a lot - of work benchmarking and testing FreeBSD for stability, scalability - and usability.</p> - - <p>Mark Linimon has put a lot of effort into refactoring and - refining the code that runs the 'pointyhat' package build - dispatch system. In 2010, the FreeBSD Foundation purchased for - portmgr a pair of new machines, pointyhat-west and - pointyhat-east, to take over from the existing machine. (The - new machines have much greater RAM, CPU, and disk capacity.) - However, to properly utilize them, the existing code needed - to be generalized.</p> - - <p>Persistent bugs, and some hardware troubles, have delayed the - rollout far beyond what was originally planned, but there - appears to be light at the end of the tunnel. (And, this time, - it does not appear to be an oncoming train.)</p> - - <p>A document entitled "Mentoring Guidelines" as been circulated - among ports developers, and has been greeted with a lot of positive - feedback, and updates have been included. In the short term, - updated copies will be maintained at - http://people.FreeBSD.org/~portmgr/mentor_guidelines.txt.asc.</p> - - <p>The Ports Management team have been running -exp runs on an - ongoing basis, verifying how base system updates may affect the - ports tree, as well as providing QA runs for major ports updates. - Of note, -exp runs were done for:</p> - - <ul> - <li>ade: multiple runs for autotools refactoring</li> - - <li>ed: test to replace libgcc.a with libcompiler_rt.a</li> - - <li>jiles: test sh(1) against r212508</li> - - <li>kde: Qt 4.7.0 update</li> - - <li>kde: KDE 4.5.4 updte</li> - - <li>kwm: Gnome 2.32 update</li> - - <li>ports/144164: ensure package-noinstall target include rc.d - scripts</li> - - <li>ports/145598: include etc/devd in mtree</li> - - <li>ports/145955: silence make fetch-required-list</li> - - <li>ports/147701: perform DESKTOP_ENTRIES sanity check</li> - - <li>ports/149657: removal of MD5 checksums</li> - - <li>ports/149670: remove checks in _OPTIONSFILE</li> - - <li>ports/150303: for INSTALL_LIBS</li> - - <li>ports/150337: for PLIST_DIRSTRY</li> - - <li>ports/151047: pass CPP to CONFIGURE/MAKE_ENV</li> - - <li>ports/151799: fix PLIST_DIRSTRY</li> - - <li>ports/151806: remove 2004 legacy hack</li> - - <li>ports/152055 and ports/152059: for pear infrastructure</li> - - <li>ports/152558: boost update</li> - - <li>ports/152626: fix pkg-message display if installed from - package</li> - - <li>ports/152964: embed LICENSE name for STDOUT</li> - - <li>ports/153018: implement variables in Mozilla - dependencies</li> - - <li>ports/153033: fix un-escaped shell metacharacters</li> - - <li>ports/153041: clean up ruby plists</li> - - <li>ports/153132: autotools cleanup</li> - - <li>ports/153318: set PGSQL default to 8.4</li> - </ul> - <h3>Open tasks:</h3><ol><li>Looking for help fixing <url link="http://wiki.FreeBSD.org/PortsBrokenOnCurrent">ports - broken on CURRENT</url>.</li><li>Looking for help with <url link="http://wiki.FreeBSD.org/PortsBrokenOnTier2Architectures"> - Tier-2 architectures</url>.</li><li>Most ports PRs are assigned, we now need to focus on testing, - committing and closing.</li></ol><hr /><h2><a name="Robot-Operating-System" href="#Robot-Operating-System" id="Robot-Operating-System">Robot Operating System</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.ros.org/wiki/" title="http://www.ros.org/wiki/">ROS website</a></td><td> - URL: <a href="http://www.ros.org/wiki/" title="ROS website">http://www.ros.org/wiki/</a></td></tr><tr><td><a href="ftp://rene-ladan.nl/pub/ros-freebsd.pdf" title="ftp://rene-ladan.nl/pub/ros-freebsd.pdf">Presentation</a></td><td> - URL: <a href="ftp://rene-ladan.nl/pub/ros-freebsd.pdf" title="Presentation">ftp://rene-ladan.nl/pub/ros-freebsd.pdf</a></td></tr></table><p> - Contact: - René - Ladan - <<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>> - </p> - <p>Porting ROS to FreeBSD started in March 2010. In May 2010, it - was possible to build <filename role="package">devel/ros</filename> - without needing to apply patches, but some more changes were - necessary to be able to write a port for it. Currently this and - several other ports related to ROS are available, most notably - <filename role="package">devel/ros-tutorials</filename> - to get up and running with ROS and - <filename role="package">devel/ros-nxt</filename> - to use LEGO Mindstorms NXT robots with ROS and FreeBSD.</p> - <h3>Open tasks:</h3><ol><li>Port the software required for nxt-rviz-plugin, which is part - of devel/ros-nxt but currently excluded from the build.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="FOSDEM-2011" href="#FOSDEM-2011" id="FOSDEM-2011">FOSDEM 2011</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FOSDEM.org" title="http://www.FOSDEM.org"></a></td><td> - URL: <a href="http://www.FOSDEM.org" title="">http://www.FOSDEM.org</a></td></tr></table><p> - Contact: - Marius - Nuennerich - <<a href="mailto:marius@nuenneri.ch">marius@nuenneri.ch</a>> - <br /> - Contact: - Daniel - Seuffert - <<a href="mailto:ds@FreeBSD.org">ds@FreeBSD.org</a>> - </p> - <p>FOSDEM 2011 will be held from Saturday, February 5th to - Sunday February 6th in Brussels, Belgium. We will have a FreeBSD - booth and a developers room. At the booth there will be - friendly supporters and a FreeBSD Foundation member answering - questions. The devroom will have 6 1-hour long talks about - different topics, technical and social. FOSDEM is one of the - biggest open-source events in Europe. It is completly free and - no registration is required.</p> - <h3>Open tasks:</h3><ol><li>Get more people involved as helpers for the booth and the - devroom are still needed. Please contact Daniel or Marius if - you want to help out.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div> - <br class="clearboth" /> - </div> - <div id="footer"> - <span><a href="../../search/index-site.html">Site Map</a> | - <a href="../../copyright/">Legal Notices</a> | © 1995–2021 The FreeBSD Project. - All rights reserved.</span> - <br /> - </div> - </div> - </div> - </body> -</html> |