aboutsummaryrefslogtreecommitdiff
path: root/website/content/en/status/report-2009-10-2009-12.html
diff options
context:
space:
mode:
Diffstat (limited to 'website/content/en/status/report-2009-10-2009-12.html')
-rw-r--r--website/content/en/status/report-2009-10-2009-12.html1457
1 files changed, 0 insertions, 1457 deletions
diff --git a/website/content/en/status/report-2009-10-2009-12.html b/website/content/en/status/report-2009-10-2009-12.html
deleted file mode 100644
index a04cc49f05..0000000000
--- a/website/content/en/status/report-2009-10-2009-12.html
+++ /dev/null
@@ -1,1457 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
- <head>
- <title>FreeBSD Quarterly Status Report</title>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
- <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
- <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" />
- </head>
- <body>
- <div id="containerwrap">
- <div id="container">
- <span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
- <a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
-</span>
- <div id="headercontainer">
- <div id="header">
- <h2 class="blockhide">Header And Logo</h2>
- <div id="headerlogoleft">
- <a href="../.." title="FreeBSD">
- <img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
- </a>
- </div>
- <div id="headerlogoright">
- <div class="frontdonateroundbox">
- <div class="frontdonatetop">
- <div>
- <b style="display: none;">.</b>
- </div>
- </div>
- <div class="frontdonatecontent">
- <a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
- </div>
- <div class="frontdonatebot">
- <div>
- <b style="display: none;">.</b>
- </div>
- </div>
- </div>
- <h2 class="blockhide">Peripheral Links</h2>
- <div id="searchnav">
- <ul id="searchnavlist"></ul>
- </div>
- <div id="search">
- <form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
- <h2 class="blockhide">
- <label for="words">Search</label>
- </h2>
- <input type="hidden" name="ka" value="v" />
- <input type="hidden" name="kt" value="v" />
- <input type="hidden" name="kh" value="1" />
- <input type="hidden" name="kj" value="r2" />
- <input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
- <span> </span>
- <input id="submit" name="submit" type="submit" value="Search" />
- </form>
- </div>
- </div>
- </div>
- <h2 class="blockhide">Site Navigation</h2>
- <div id="menu">
- <ul class="first">
- <li>
- <a href="../../">Home</a>
- </li>
- </ul>
- <ul>
- <li>
- <a href="../../about.html">About</a>
- <ul>
- <li>
- <a href="../../projects/newbies.html">Introduction</a>
- </li>
- <li>
- <a href="../../features.html">Features</a>
- </li>
- <li>
- <a href="../../advocacy/">Advocacy</a>
- </li>
- <li>
- <a href="../../marketing/">Marketing</a>
- </li>
- <li>
- <a href="../../privacy.html">Privacy Policy</a>
- </li>
- </ul>
- </li>
- </ul>
- <ul>
- <li>
- <a href="../../where.html">Get FreeBSD</a>
- <ul>
- <li>
- <a href="../../releases/">Release Information</a>
- </li>
- <li>
- <a href="../../releng/">Release Engineering</a>
- </li>
- </ul>
- </li>
- </ul>
- <ul>
- <li>
- <a href="../../docs.html">Documentation</a>
- <ul>
- <li>
- <a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
- </li>
- <li>
- <a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
- </li>
- <li>
- <a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
- </li>
- <li>
- <a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
- </li>
- <li>
- <a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
- </li>
- <li>
- <a href="https://papers.FreeBSD.org">Presentations and Papers</a>
- </li>
- <li>
- <a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
- </li>
- <li>
- <a href="../../docs/books.html">All Books and Articles</a>
- </li>
- </ul>
- </li>
- </ul>
- <ul>
- <li>
- <a href="../../community.html">Community</a>
- <ul>
- <li>
- <a href="../../community/mailinglists.html">Mailing Lists</a>
- </li>
- <li>
- <a href="https://forums.FreeBSD.org">Forums</a>
- </li>
- <li>
- <a href="../../usergroups.html">User Groups</a>
- </li>
- <li>
- <a href="../../events/events.html">Events</a>
- </li>
- <li>
- <a href="http://freebsdjournal.com">FreeBSD Journal</a>
- </li>
- <li>
- <a href="http://serverfault.com/questions/tagged/freebsd">Q&amp;A (external)</a>
- </li>
- </ul>
- </li>
- </ul>
- <ul>
- <li>
- <a href="../../projects/index.html">Developers</a>
- <ul>
- <li>
- <a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
- </li>
- <li>
- <a href="https://cgit.FreeBSD.org">Git Repository</a>
- </li>
- <li>
- <a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
- </li>
- <li>
- <a href="https://github.com/freebsd">GitHub Mirror</a>
- </li>
- <li>
- <a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
- </li>
- <li>
- <a href="https://wiki.FreeBSD.org">Wiki</a>
- </li>
- <li>
- <a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
- </li>
- </ul>
- </li>
- </ul>
- <ul>
- <li>
- <a href="../../support.html">Support</a>
- <ul>
- <li>
- <a href="../../commercial/commercial.html">Vendors</a>
- </li>
- <li>
- <a href="../../security/">Security Information</a>
- </li>
- <li>
- <a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
- </li>
- <li>
- <a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
- </li>
- </ul>
- </li>
- </ul>
- <ul>
- <li>
- <a href="https://www.freebsdfoundation.org/">Foundation</a>
- <ul>
- <li>
- <a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
- </li>
- <li>
- <a href="../../donations/index.html#systems">Hardware Donations</a>
- </li>
- </ul>
- </li>
- </ul>
- </div>
- </div>
- <div id="content">
- <div id="sidewrap">
- <div id="sidenav">
- <h2 class="blockhide">Section Navigation</h2>
- <ul>
- <li>
- <a href="../../about.html">About</a>
- </li>
- <li>
- <a href="../../features.html">Features</a>
- </li>
- <li>
- <a href="../../applications.html">Applications</a>
- </li>
- <li>
- <a href="../../advocacy/">Advocacy</a>
- </li>
- <li>
- <a href="../../marketing/">Marketing</a>
- </li>
- <li>
- <a href="../../administration.html">Administration</a>
- </li>
- <li>
- <a href="../../news/newsflash.html">News</a>
- </li>
- <li>
- <a href="../../events/events.html">Events</a>
- </li>
- <li>
- <a href="../../news/press.html">Press</a>
- </li>
- <li>
- <a href="../../multimedia/multimedia.html">Multimedia</a>
- </li>
- <li>
- <a href="../../art.html">Artwork</a>
- </li>
- <li>
- <a href="../../logo.html">Logo</a>
- </li>
- <li>
- <a href="../../donations/">Donations</a>
- </li>
- <li>
- <a href="../../copyright/">Legal Notices</a>
- </li>
- <li>
- <a href="../../privacy.html">Privacy Policy</a>
- </li>
- </ul>
- </div>
- </div>
- <div id="contentwrap"><h1>Introduction</h1><p>This report covers FreeBSD related projects between October and
- December 2009. This is the last of the four reports covering 2009,
- which has shown to be a very important year for the FreeBSD Project. Besides
- other notable things, a new major version of FreeBSD, 8.0-RELEASE, has been
- released, while the release process for 7.3-RELEASE is soon to begin.</p><p>Thanks to all the reporters for the excellent work! We hope you
- enjoy reading. Let us also take this opportunity to wish you all a
- happy and successful new year for 2010.</p><p>Please note that the deadline for submissions covering the
- period between January and March 2010 is April 15th, 2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#BSD-licensed-iconv">BSD-licensed iconv</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#3G-USB-support">3G USB support</a></li><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></li><li><a href="#HAST-&#8212;-Highly-Available-Storage">HAST &#8212; Highly Available Storage</a></li><li><a href="#Intel-XScale-hwpmc(9)-support">Intel XScale hwpmc(9) support</a></li><li><a href="#POSIX-utmpx-for-FreeBSD">POSIX utmpx for FreeBSD</a></li><li><a href="#SUJ-&#8212;-Journaled-SoftUpdates">SUJ &#8212; Journaled SoftUpdates</a></li><li><a href="#The-webcamd-deamon">The webcamd deamon</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#bwn(4)-&#8212;-Broadcom-Wireless-driver">bwn(4) &#8212; Broadcom Wireless driver</a></li><li><a href="#IP-Payload-Compression-Protocol-support">IP Payload Compression Protocol support</a></li><li><a href="#Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver">Ralink wireless RT2700U/2800U/3000U run(4) USB driver</a></li><li><a href="#Syncing-pf(4)-with-OpenBSD-4.5">Syncing pf(4) with OpenBSD 4.5</a></li><li><a href="#Wireless-mesh-networking">Wireless mesh networking</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#CAM-based-ATA-implementation">CAM-based ATA implementation</a></li><li><a href="#Group-Limit-Increase">Group Limit Increase</a></li><li><a href="#NFSv4-ACL-support">NFSv4 ACL support</a></li><li><a href="#V4L-support-in-Linux-emulator">V4L support in Linux emulator</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li><li><a href="#The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Flattened-Device-Tree-for-embedded-FreeBSD">Flattened Device Tree for embedded FreeBSD</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#FreeBSD/mips">FreeBSD/mips</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium-web-browser">Chromium web browser</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#DAHDI-(Zaptel)-support-for-FreeBSD">DAHDI (Zaptel) support for FreeBSD</a></li><li><a href="#NVIDIA-amd64-driver">NVIDIA amd64 driver</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#AsiaBSDCon-2010-&#8212;-The-BSD-Conference">AsiaBSDCon 2010 &#8212; The BSD Conference</a></li><li><a href="#BSDCan-2010-&#8212;-The-BSD-Conference">BSDCan 2010 &#8212; The BSD Conference</a></li><li><a href="#meetBSD-2010-&#8212;-The-BSD-Conference">meetBSD 2010 &#8212; The BSD Conference</a></li><li><a href="#The-FreeBSD-Forums">The FreeBSD Forums</a></li></ul><h3><a href="#Userland-utilities">Userland utilities</a></h3><ul><li><a href="#BSD-licensed-text-processing-tools">BSD-licensed text processing tools</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="BSD-licensed-iconv" href="#BSD-licensed-iconv" id="BSD-licensed-iconv">BSD-licensed iconv</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv">Sources in the Perforce repository</a></td><td>
- URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv" title="Sources in the Perforce repository">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv</a></td></tr></table><p>
- Contact:
- Gábor
- Kövesdán
- &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
- </p>
- <p>Good compatibility has been ensured and there are only few pending
- items that have to be reviewed/enhanced. Recently, an enhancement
- has been completed, which makes it possible to accomplish better
- transliteration, just like in the GNU version. An initial testing
- patch is expected at the beginning of February.</p>
- <h3>Open tasks:</h3><ol><li>Enhance conversion tables to make use of enhanced
- transliteration.</li><li>A performance optimization might be done later.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="3G-USB-support" href="#3G-USB-support" id="3G-USB-support">3G USB support</a></h2><p>
- Contact:
- Andrew
-
- Thompson
- &lt;<a href="mailto:thompsa@FreeBSD.org">thompsa@FreeBSD.org</a>&gt;
- </p>
- <p>Recently, a bunch of new device IDs have been added for the
- u3g(4) cellular wireless driver; the list should be comparable now with
- other operating systems around. A lot of these devices have a
- feature where the unit first attaches as a disk or CD-ROM that
- contains the Win/Mac drivers. This state should be detected by the
- u3g driver and the usb device is sent a command to switch to modem
- mode. This has been working for quite some time but as it is
- implemented differently for each vendor I am looking for feedback
- on any units where the auto switchover is not working (or the init
- is not recognized at all). Please ensure you are running an up to
- date kernel, like r201681 or later from 9.0-CURRENT, or 8-STABLE
- after the future merge of this revision.</p>
- <hr /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr></table><p>
- Contact:
- Ed
- Schouten
- &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Roman
- Divacky
- &lt;<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Brooks
- Davis
- &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Pawel
- Worach
- &lt;<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>&gt;
- </p>
- <p>We are again able to build bootable i386/amd64 kernel. Nathan
- Whitehorn committed a fix to FreeBSD, which enabled LLVM/clang to
- work mostly fine on PowerPC. There is some preliminary testing
- of LLVM/clang on ARM and MIPS being done. We have some ideas
- about sparc64 support which are currently being investigated.
- You are welcome to contact us if you want to help.</p>
-
- <p>Since the last report, a lot has happened mostly in the area of
- C++; clang is currently able to build working groff, gperf and
- devd, i.e. all of the C++ apps we have in base. Unfortunately,
- it still cannot build any of the C++ libraries &#8212; two of
- them are missing builtins and libstdc++ is broken for other
- reasons.</p>
-
- <p>Not much happened in the clangbsd branch as we cannot
- upgrade the clang/llvm there because we are blocked by a bug
- that requires using newer assembler than we can ship. This
- might be solved by either fixing this (short term) or using
- llvm-mc instead of GNU as for assembling (longer term).</p>
- <h3>Open tasks:</h3><ol><li>Help with ARM/MIPS/sparc64.</li><li>More testing of clang on 3rd party apps (ports).</li><li>Discussion on integrating LLVM/clang into FreeBSD.</li></ol><hr /><h2><a name="FreeBSD-TDM-Framework" href="#FreeBSD-TDM-Framework" id="FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></h2><p>
- Contact:
- Rafal
- Czubak
- &lt;<a href="mailto:rcz@semihalf.com">rcz@semihalf.com</a>&gt;
- <br />
- Contact:
- Michal
- Hajduk
- &lt;<a href="mailto:mih@semihalf.com">mih@semihalf.com</a>&gt;
- </p>
- <p>Important changes regarding FreeBSD TDM Framework since the last status
- report:</p>
-
- <ul>
- <li>Fully functional TDM controller driver for Marvell Kirkwood and
- Discovery SoCs.</li>
-
- <li>Working voiceband channel character device driver.</li>
-
- <li>Working Si3215, Si3050 codec drivers on corresponding FXS, FXO
- ports.</li>
-
- <li>Demo application, which is capable of manipulating voiceband
- channel and codec state, starting/stopping channel transfers and
- echoing on single channel.</li>
-
- <li>Preliminary version of driver bridging the voiceband
- infrastructure with Zaptel/DAHDI.</li>
- </ul>
- <h3>Open tasks:</h3><ol><li>Improve various issues regarding working drivers and demo
- application.</li><li>Test Si3050 codec driver operation with PSTN.</li><li>Fully integrate voiceband infrastructure with Zaptel/DAHDI telephony
- hardware drivers.</li></ol><hr /><h2><a name="HAST-&#8212;-Highly-Available-Storage" href="#HAST-&#8212;-Highly-Available-Storage" id="HAST-&#8212;-Highly-Available-Storage">HAST &#8212; Highly Available Storage</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html" title="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html">Announcement</a></td><td>
- URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html" title="Announcement">http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html</a></td></tr></table><p>
- Contact:
- Pawel Jakub
-
- Dawidek
- &lt;<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>&gt;
- </p>
- <p>HAST software will provide synchronous replication of any GEOM
- provider (eg. disk, partition, mirror, etc.) or file from one FreeBSD
- machine (primary node) to another one (secondary node).</p>
-
- <p>Because data is replicated at the block level neither applications, nor
- file systems have to be modified to take advantage of this
- functionality.</p>
-
- <p>The functionality that HAST software will provide is very similar
- to the functionality provided by the DRBD project for Linux.</p>
-
- <p>The HAST project is sponsored by the FreeBSD Foundation.</p>
-
- <p>Work is progressing well; first milestone was reached in December
- 2009 and the expected project completion date is January 31,
- 2010.</p>
-
- <p>Check out FreeBSD mailing lists for patches to test in February and
- wish me good luck!</p>
-
- <p>And by the way, do not forget to donate to the FreeBSD Foundation, as your
- donations make projects like this possible.</p>
-
- <p>Thank you!</p>
- <hr /><h2><a name="Intel-XScale-hwpmc(9)-support" href="#Intel-XScale-hwpmc(9)-support" id="Intel-XScale-hwpmc(9)-support">Intel XScale hwpmc(9) support</a></h2><p>
- Contact:
- Rui
- Paulo
- &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
- </p>
- <p>Preliminary Hardware Performance Counter support for Intel
- XScale ARM processors was committed to FreeBSD 9.0-CURRENT
- in December. This adds another supported architecture to hwpmc(9).
- The system works for basic performance counter usage but more
- advanced usage scenarios, namely callchain support, are not
- yet implemented.</p>
- <hr /><h2><a name="POSIX-utmpx-for-FreeBSD" href="#POSIX-utmpx-for-FreeBSD" id="POSIX-utmpx-for-FreeBSD">POSIX utmpx for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html" title="http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html">Announcement</a></td><td>
- URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html" title="Announcement">http://lists.FreeBSD.org/pipermail/freebsd-current/2010-January/014893.html</a></td></tr><tr><td><a href="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html" title="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html">POSIX specification</a></td><td>
- URL: <a href="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html" title="POSIX specification">http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html</a></td></tr><tr><td><a href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c" title="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c">NetBSD's implementation</a></td><td>
- URL: <a href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c" title="NetBSD's implementation">http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c</a></td></tr><tr><td><a href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c" title="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c">OpenSolaris' implementation</a></td><td>
- URL: <a href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c" title="OpenSolaris' implementation">http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c</a></td></tr></table><p>
- Contact:
- Ed
- Schouten
- &lt;<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>&gt;
- </p>
- <p>On January 13, I removed the utmp user accounting database and
- replaced it with a new POSIX utmpx implementation. Unfortunately, the upgrade path is a bit
- complex, because the utmp interface provided almost no library
- interface to interact with the database files.</p>
-
- <p>This change may have caused some regressions. Some ports may fail
- to build, while there could also be bugs in the library
- functions.</p>
- <h3>Open tasks:</h3><ol><li>Get a list of broken ports.</li><li>Fix them to comply to standards.</li><li>Send patches upstream.</li></ol><hr /><h2><a name="SUJ-&#8212;-Journaled-SoftUpdates" href="#SUJ-&#8212;-Journaled-SoftUpdates" id="SUJ-&#8212;-Journaled-SoftUpdates">SUJ &#8212; Journaled SoftUpdates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeffr_tech.livejournal.com/" title="http://jeffr_tech.livejournal.com/"></a></td><td>
- URL: <a href="http://jeffr_tech.livejournal.com/" title="">http://jeffr_tech.livejournal.com/</a></td></tr></table><p>
- Contact:
- Jeff
-
- Roberson
- &lt;<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>&gt;
- </p>
- <p>I have been adding a small intent log to SoftUpdates to
- eliminate the requirement for fsck after an unclean shutdown. This
- work has been funded by Yahoo!, iXsystems, and Juniper. Kirk
- McKusick has been aiding me with design critiques and helping me
- better understand SoftUpdates.</p>
-
- <p>Extensive testing by myself and Peter Holm has yielded a stable
- patch. Current users are encouraged to follow the instructions
- posted to the current@FreeBSD.org mailing list to verify stability in your own workloads.
- Updates are forthcoming and it is expected to be merged to
- 9.0-CURRENT before the end of January. Ports to older versions of FreeBSD
- will be available in SVN under alternate branches. Official
- backports will be decided by re@ when 9.0-CURRENT is stable.</p>
-
- <p>The changes are fully backwards and forwards compatible as there
- are very few metadata changes to the filesystem. The journal may be
- enabled or disabled on existing FFS filesystems using tunefs(8).
- The log consumes 64 MB of space at maximum and fsck time is
- bounded by the size of the log rather than the size of the
- filesystem. Other details are available in my technical
- journal.</p>
- <hr /><h2><a name="The-webcamd-deamon" href="#The-webcamd-deamon" id="The-webcamd-deamon">The webcamd deamon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.selasky.org/hans_petter/video4bsd/" title="http://www.selasky.org/hans_petter/video4bsd/"></a></td><td>
- URL: <a href="http://www.selasky.org/hans_petter/video4bsd/" title="">http://www.selasky.org/hans_petter/video4bsd/</a></td></tr></table><p>
- Contact:
- Hans Petter
-
- Selasky
- &lt;<a href="mailto:hselasky@FreeBSD.org">hselasky@FreeBSD.org</a>&gt;
- </p>
- <p>The webcamd daemon enables hundreds of different USB based
- webcam devices to be used under the FreeBSD-8/9 operating system. The
- webcam daemon is basically an application, which is a port of
- Video4Linux USB webcam drivers into userspace on FreeBSD. The daemon
- currently depends on libc, pthreads, libusb and the VIDEO4BSD
- kernel module.</p>
- <h3>Open tasks:</h3><ol><li>Add support for the remaining Video4Linux USB devices.</li><li>Make patches for increased buffer sizes, due to higher
- latency in userspace. Especially for High Speed USB.</li></ol><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Bugbusting-Team" href="#FreeBSD-Bugbusting-Team" id="FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/support.html#gnats" title="http://www.FreeBSD.org/support.html#gnats">GNATS</a></td><td>
- URL: <a href="http://www.FreeBSD.org/support.html#gnats" title="GNATS">http://www.FreeBSD.org/support.html#gnats</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/BugBusting" title="http://wiki.FreeBSD.org/BugBusting">BugBusting</a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="BugBusting">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/">Experimental report pages</a></td><td>
- URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="Experimental report pages">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html">PRs recommended for committer evaluation by the bugbusting team</a></td><td>
- URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="PRs recommended for committer evaluation by the bugbusting team">http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt">Subscription list for the above report)</a></td><td>
- URL: <a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="Subscription list for the above report)">http://people.FreeBSD.org/~linimon/recommended_subscribers.txt</a></td></tr></table><p>
- Contact:
- Gavin
- Atkinson
- &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Mark
- Linimon
- &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Remko
- Lodder
- &lt;<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Volker
- Werth
- &lt;<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>&gt;
- </p>
- <p>Bugmeister Gavin Atkinson has now been granted a src commit
- bit, and is now starting to work through some of our
- backlog.</p>
-
- <p>The list of PRs recommended for committer evaluation by the
- Bugbusting Team continues to receive new additions; however, it
- has not yet achieved high visibility. (This list contains PRs,
- mostly with patches, that the Bugbusting Team consider potentially
- ready to be committed as-is, or are probably trivially resolved
- in the hands of a committer with knowledge of the particular
- subsystem.) One of the suggestions at the Cambridge devsummit
- was to create a way for people to be emailed the weekly summary
- that is posted to freebsd-bugs@, and this has now been implemented.
- Please email linimon@FreeBSD.org to ask to be added to the
- recommended_subscribers.txt file (see above).</p>
-
- <p>We continue to classify PRs as they arrive, adding 'tags' to the
- subject lines corresponding to the kernel subsystem involved, or
- man page references for userland PRs. These tags, in turn, produce
- lists of PRs sorted both by tag and by manpage. At this point
- most of the PRs that refer to supported versions of FreeBSD have
- been converted, and we are keeping up as new ones come in. We
- hope that this is making it easier to browse the PR database.</p>
-
- <p>The overall PR count jumped to over 6,200 during the 8.0-RELEASE release
- cycle but seems to have stabilized at around 6,100. As in the
- past, we have a fairly good clearance rate for ports PRs but
- much less so for other PRs. (Partly this is due to the concept
- of individual ports having 'maintainers'.)</p>
- <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with
- closing PRs that the team has already analyzed.</li></ol><hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td>
- URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p>
- Contact:
- Release Engineering Team
- &lt;<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>&gt;
- </p>
- <p>The Release Engineering Team announced FreeBSD 8.0-RELEASE on
- November 26th, 2009. With 8.0-RELEASE completed planning has
- begun for 7.3-RELEASE. The schedule has been set with the
- release date planned for early March 2010.</p>
-
- <p>The Release Engineering Team would like to thank George
- Neville-Neil (gnn@) for his service on the team. George
- continues to work with the FreeBSD Project but has stepped down
- from the Release Engineering Team to focus on other
- activities.</p>
- <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">The FreeBSD Foundation</a></td><td>
- URL: <a href="http://www.FreeBSDFoundation.org/" title="The FreeBSD Foundation">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="https://twitter.com/freebsdfndation" title="https://twitter.com/freebsdfndation">Follow us on Twitter</a></td><td>
- URL: <a href="https://twitter.com/freebsdfndation" title="Follow us on Twitter">https://twitter.com/freebsdfndation</a></td></tr></table><p>
- Contact:
- Deb
- Goodkin
- &lt;<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>&gt;
- </p>
- <p>Despite a difficult economy, we more than doubled our number
- of donors, we raised $269K towards our goal of $300K, and with
- an improved economy hope to surpass that this year.</p>
-
- <p>We have funded two new projects. One is the Flattened Device Tree by
- Rafal Jaworowski. And, the second one is Highly Available Storage
- by Pawel Jakub Dawidek. We continued supporting the New Console
- Driver by Ed Schouten and Improvements to the FreeBSD TCP Stack by
- Lawrence Stewart. We also purchased equipment for several
- projects.</p>
-
- <p>We have big plans for the new year! We are going to significantly
- increase our project development and equipment spending. Stay
- tuned for a project proposal submission announcement soon. We
- just announced that we are accepting travel grant applications
- for AsiaBSDCon and will be accepting them soon for BSDCan. And,
- we are working on infrastructure projects to beef up hardware
- for package-building, network-testing, etc.</p>
-
- <p>Read more about how we supported the project and community by
- reading our end-of-year newsletter available at <a href="http://www.FreeBSDFoundation.org/press/2009Dec-newsletter.shtml" shape="rect">http://www.FreeBSDFoundation.org/press/2009Dec-newsletter.shtml</a>.</p>
-
- <p>We are fund-raising for 2010 now! Find out more at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">http://www.FreeBSDFoundation.org/donate/</a>.</p>
- <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="bwn(4)-&#8212;-Broadcom-Wireless-driver" href="#bwn(4)-&#8212;-Broadcom-Wireless-driver" id="bwn(4)-&#8212;-Broadcom-Wireless-driver">bwn(4) &#8212; Broadcom Wireless driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO">bwn(4) sources in P4</a></td><td>
- URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO" title="bwn(4) sources in P4">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&amp;HIDEDEL=NO</a></td></tr></table><p>
- Contact:
- Weongyo
- Jeong
- &lt;<a href="mailto:weongyo@FreeBSD.org">weongyo@FreeBSD.org</a>&gt;
- </p>
- <p>bwn(4) is replacing bwi(4) driver for to the following
- reasons:</p>
-
- <ul>
- <li>Uses latest v4 firmware image instead of using the much older v3
- firmware. In this way, we have some great benefits, such as
- support for N-PHYs and the fixes of various earlier firmware bugs.</li>
-
- <li>Supports PIO mode. This is important because &#8212; as you might
- know &#8212; the Broadcom Wireless Driver is created by
- reverse-engineering so some pieces of hardware might not
- work with DMA operations.</li>
-
- <li>Supports 64 bit DMA operations.</li>
-
- <li>Separates bwi(4) driver into two parts; siba(4) driver and
- bwn(4) driver. Many Broadcom wireless and NIC devices
- are based on Silicon Sonics Backplane, such as bwi(4), which
- implemented the SIBA operations internally. This resulted in
- code duplication as other drivers had to implement their
- own routines to deal with SIBA. In the case of bwn(4),
- these two parts have been separated and implemented in their
- own kernel modules to avoid this problem and help further
- development by providing a standalone siba(4) driver.</li>
- </ul>
-
- <p>Currently, it is tested on big/little endian machines and 32/64-bit
- DMA operation with STA mode. A major patch for siba(4)
- is being reviewed before committing into 9.0-CURRENT.</p>
- <h3>Open tasks:</h3><ol><li>MESH/IBSS/HOSTAP mode is not supported.</li><li>LP/N PHYs are not supported.</li></ol><hr /><h2><a name="IP-Payload-Compression-Protocol-support" href="#IP-Payload-Compression-Protocol-support" id="IP-Payload-Compression-Protocol-support">IP Payload Compression Protocol support</a></h2><p>
- Contact:
- Bjoern A.
- Zeeb
- &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;
- </p>
- <p>One of the longer outstanding feature problems with the FreeBSD
- IP security stack, broken IP Payload Compression Protocol
- (IPcomp) support, has been fixed.</p>
-
- <p>While working on the fix, various problems had been
- identified:</p>
-
- <ul>
- <li>Problems with the IPcomp packet handling in IPsec.</li>
-
- <li>opencrypto compression handling and deflate implementation
- limitations. These were debugged using DTrace SDT
- probes.</li>
-
- <li>Problems due to an outdated version of zlib used in some
- parts of the network stack and by the opencrypto
- framework.</li>
- </ul>
-
- <p>Patches for all but the zlib support have been committed to
- 9.0-RELEASE and merged to all supported stable branches including
- 6-STABLE. Special thanks to Eugene Grosbein for helping with
- testing.</p>
- <h3>Open tasks:</h3><ol><li>Fix ng_deflate so that we can make use of Kip Macy's work
- on an up-to-date unified zlib version in the kernel, which
- would also fix the last occasional IPcomp hiccups.</li></ol><hr /><h2><a name="Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver" href="#Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver" id="Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver">Ralink wireless RT2700U/2800U/3000U run(4) USB driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.FreeBSD.org/showthread.php?t=7562" title="http://forums.FreeBSD.org/showthread.php?t=7562">Announcement on the FreeBSD Forums</a></td><td>
- URL: <a href="http://forums.FreeBSD.org/showthread.php?t=7562" title="Announcement on the FreeBSD Forums">http://forums.FreeBSD.org/showthread.php?t=7562</a></td></tr></table><p>
- Contact:
- Akinori
-
- Furukoshi
- &lt;<a href="mailto:moonlightakkiy@yahoo.ca">moonlightakkiy@yahoo.ca</a>&gt;
- </p>
- <p>The run(4) driver brings support for Ralink RT2700U/2800U/3000U
- USB wireless devices. For detailed information and list of all the
- supported devices, please see the above mentioned URL. The source
- code has been imported to the USB P4 repository on January 10, 2010
- (172906).</p>
- <h3>Open tasks:</h3><ol><li>Solve USB_TIMEOUT problem when sending beacons, and/or
- confirm which chipsets supports AP mode if all of them do not
- support it.</li><li>Read TX stats for AMRR on AP mode, and/or confirm which
- chipsets supports AP mode if all of them do not support
- it.</li><li>Maintain the code.</li></ol><hr /><h2><a name="Syncing-pf(4)-with-OpenBSD-4.5" href="#Syncing-pf(4)-with-OpenBSD-4.5" id="Syncing-pf(4)-with-OpenBSD-4.5">Syncing pf(4) with OpenBSD 4.5</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/">Viewing the changes.</a></td><td>
- URL: <a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="Viewing the changes.">http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="http://svn.FreeBSD.org/base/user/eri/pf45/head/">The actual repo to build from.</a></td><td>
- URL: <a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="The actual repo to build from.">http://svn.FreeBSD.org/base/user/eri/pf45/head/</a></td></tr></table><p>
- Contact:
- Ermal
-
- Luçi
- &lt;<a href="mailto:eri@FreeBSD.org">eri@FreeBSD.org</a>&gt;
- </p>
- <p>This import is based on OpenBSD 4.5 state of pf(4). It includes
- many improvements over the code currently present in FreeBSD. The
- actual new feature present in pf45 repository is support for
- divert(4), which should allow tools like snort_inline to work with
- pf(4) too.</p>
-
- <p>Currently, the pf(4) import is considered stable with normal
- kernel, as well as VIMAGE enabled kernels.</p>
- <h3>Open tasks:</h3><ol><li>pflow(4)/pflog(4)/pfsync(4) need to be made VIMAGE
- aware.</li><li>More regression testing is needed.</li></ol><hr /><h2><a name="Wireless-mesh-networking" href="#Wireless-mesh-networking" id="Wireless-mesh-networking">Wireless mesh networking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/WifiMesh" title="http://wiki.FreeBSD.org/WifiMesh"></a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/WifiMesh" title="">http://wiki.FreeBSD.org/WifiMesh</a></td></tr></table><p>
- Contact:
- Rui
- Paulo
- &lt;<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>&gt;
- </p>
- <p>Development of the FreeBSD 802.11s stack continues. The code in
- FreeBSD HEAD has been updated to comply with draft 4.0. Merge to
- FreeBSD 8-STABLE will be done soon.</p>
-
- <p>The developer is looking for funding to be able to implement mesh
- link security algorithms and/or coordinated channel access
- (performance improvement).</p>
- <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="CAM-based-ATA-implementation" href="#CAM-based-ATA-implementation" id="CAM-based-ATA-implementation">CAM-based ATA implementation</a></h2><p>
- Contact:
- Alexander
-
- Motin
- &lt;<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Scott
-
- Long
- &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;
- </p>
- <p>Existing ata(4) infrastructure, which has been around many years,
- has various problems and limitations when compared to modern
- controllers/device support. Although the CAM subsystem (used for SCSI)
- is almost as old as ata(4), it is more eligible to solve the current
- problems. To reduce code duplication and better support border cases
- such as ATAPI and SAS, we have started to develop a new CAM based
- ATA implementation.</p>
-
- <p>As such, CAM infrastructure has been extended to support different
- transports. New transport has been implemented to support PATA/SATA
- buses. To support ATA disks, a new CAM driver (ada) has been written. ATAPI
- devices are supported by existing SCSI drivers cd, da, sa, etc. To
- support SATA port-multipliers another new CAM driver (pmp) has been written. To
- support most featured and widespread SATA controllers, new drivers
- ahci(4) and siis(4) have been developed.</p>
-
- <p>To support legacy ATA controllers, a kernel option ATA_CAM has been
- added. When used, it makes all ata(4) controllers directly
- available to CAM, deprecating ata(4) peripheral drivers and external
- APIs. To make this possible, ata(4) code has been heavily refactored,
- making controller driver API stricter.</p>
-
- <p>Command queuing support gives new ATA implementation up to
- double performance benefit on some workloads, with 20-30% improvement
- quite usual.</p>
-
- <p>SATA Port Multiplier support makes it easy to build fast and
- cheap storage with huge capacities, by using dozens of SATA drives
- in one system or external enclosures,</p>
-
- <p>Some of that code has been presented in the recently released FreeBSD 8.0-RELEASE but
- 8-STABLE now includes a much improved version.</p>
- <h3>Open tasks:</h3><ol><li>Improve timeout and transport error recovery.</li><li>Improve hot-plug support.</li><li>Find and fix any show stoppers for legacy ata(4)
- deprecation.</li><li>Write a new, more featured driver for Marvell SATA controllers
- (specifications desired).</li><li>Write SAS-specific transport and drivers for SAS HBAs (specifications
- desired). SAS controllers can support SATA devices and
- multipliers, so it should fit nicely into the new
- infrastructure.</li></ol><hr /><h2><a name="Group-Limit-Increase" href="#Group-Limit-Increase" id="Group-Limit-Increase">Group Limit Increase</a></h2><p>
- Contact:
- Brooks
- Davis
- &lt;<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>&gt;
- </p>
- <p>Historically, FreeBSD has limited the number of supplemental
- groups per process to 15 (NGROUPS_MAX was incorrectly declared to be
- 16). In FreeBSD 8.0-RELEASE we raised the limit to 1023, which should be
- sufficient for most users and will be acceptably efficient for
- incorrectly written applications that statically allocate
- NGROUPS_MAX + 1 entries.</p>
-
- <p>Because some systems such as Linux 2.6 support a larger
- group limit, we have further relaxed this restriction in 9.0-CURRENT and
- made kern.ngroups a tunable value, which supports values between 1023
- and INT_MAX - 1. We plan to merge this to 8-STABLE before
- 8.1-RELEASE.</p>
- <hr /><h2><a name="NFSv4-ACL-support" href="#NFSv4-ACL-support" id="NFSv4-ACL-support">NFSv4 ACL support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/NFSv4_ACLs" title="http://wiki.FreeBSD.org/NFSv4_ACLs"></a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/NFSv4_ACLs" title="">http://wiki.FreeBSD.org/NFSv4_ACLs</a></td></tr></table><p>
- Contact:
- Edward Tomasz
-
- Napierala
- &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;
- </p>
- <p>Native NFSv4 ACL support in ZFS and UFS has been committed into 9.0-CURRENT. It
- is expected to be MFCed in order to make it into FreeBSD 8.1-RELEASE.</p>
- <h3>Open tasks:</h3><ol><li>Support for NFSv4 ACLs in tar(1).</li><li>MFC.</li></ol><hr /><h2><a name="V4L-support-in-Linux-emulator" href="#V4L-support-in-Linux-emulator" id="V4L-support-in-Linux-emulator">V4L support in Linux emulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://opal.com/freebsd/sys/compat/linux/" title="http://opal.com/freebsd/sys/compat/linux/"></a></td><td>
- URL: <a href="http://opal.com/freebsd/sys/compat/linux/" title="">http://opal.com/freebsd/sys/compat/linux/</a></td></tr></table><p>
- Contact:
- J.R.
-
- Oldroyd
- &lt;<a href="mailto:fbsd@opal.com">fbsd@opal.com</a>&gt;
- </p>
- <p>V4L video support in the Linux emulator is now available.</p>
-
- <p>This work allows Linux applications using V4L video calls to
- work with existing FreeBSD video drivers that provide V4L interfaces.
- It is tested and working with the net/skype port and also with
- browser-based Flash applications that access webcams. An early version has been
- committed to 9.0-CURRENT and work is in progress to commit the latest
- version and then MFC. It is also tested on FreeBSD-8.0/amd64 and
- FreeBSD-7.2/i386.</p>
-
- <p>Note: to be clear, this does not add V4L support to all webcams.
- The FreeBSD camera driver must already offer V4L support itself in
- order for a Linux application to be able to use that camera. The
- multimedia/pwcbsd port provides the pwc(4) driver that already has
- V4L support. If your camera is supported by a different driver, you
- will need to enhance that driver to add V4L support.</p>
- <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">German Documentation Project Homepage</a></td><td>
- URL: <a href="http://doc.bsdgroup.de" title="German Documentation Project Homepage">http://doc.bsdgroup.de</a></td></tr></table><p>
- Contact:
- Johann
-
- Kois
- &lt;<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Benedict
-
- Reuschling
- &lt;<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Martin
-
- Wilke
- &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
- </p>
- <p>We are happy to announce that Benedict Reuschling is now free
- from mentorship and can commit to the documentation tree on his own.</p>
-
- <p>Since the last status report, the German Documentation Team has
- chased updates to various sections of the FreeBSD Handbook, FAQ and
- the German website. Many handbook pages have been updated to the latest
- version, including chapters about configuration, disks, kernel
- configuration, printing, multimedia and virtualization.</p>
-
- <p>We require help from volunteers that are willing to contribute
- bug fixes or translations. The following documents need active
- maintainership and are a good training ground for those willing to
- join the translation team:</p>
-
- <ul>
- <li>arch-handbook/jail/</li>
-
- <li>developers-handbook/I10n/</li>
-
- <li>developers-handbook/policies/</li>
-
- <li>developers-handbook/sockets/ (translation from scratch)</li>
-
- <li>handbook/firewalls/ (translation from scratch)</li>
-
- <li>handbook/security/</li>
-
- <li>porters-handbook/</li>
- </ul>
- <h3>Open tasks:</h3><ol><li>Read the translations and report bugs to
- de-bsd-translators@de.FreeBSD.org.</li><li>Translate articles or missing sections listed above.</li></ol><hr /><h2><a name="The-FreeBSD-Hungarian-Documentation-Project" href="#The-FreeBSD-Hungarian-Documentation-Project" id="The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/hu/" title="http://www.FreeBSD.org/hu/">Hungarian Web Page for FreeBSD</a></td><td>
- URL: <a href="http://www.FreeBSD.org/hu/" title="Hungarian Web Page for FreeBSD">http://www.FreeBSD.org/hu/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/hu/" title="http://www.FreeBSD.org/doc/hu/">Hungarian Documentation for FreeBSD</a></td><td>
- URL: <a href="http://www.FreeBSD.org/doc/hu/" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td>
- URL: <a href="http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.FreeBSD.org/@md=d&amp;cd=//depot/projects/docproj_hu/&amp;c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p>
- Contact:
- Gábor
- Kövesdán
- &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Gábor
- Páli
- &lt;<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>&gt;
- </p>
- <p>In the last months, no new translation has been added.
- Lacking human resources, we can only manage to keep the existing
- documentation and web page translations up to date. If you are interested
- in helping us, please contact us via the email addresses
- noted above.</p>
- <h3>Open tasks:</h3><ol><li>Translate release notes.</li><li>Add more article translations.</li></ol><hr /><h2><a name="The-FreeBSD-Spanish-Documentation-Project" href="#The-FreeBSD-Spanish-Documentation-Project" id="The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="http://www.FreeBSD.org/doc/es/articles/fdp-es/">Introduction to the Spanish Documentation Project</a></td><td>
- URL: <a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="Introduction to the Spanish Documentation Project">http://www.FreeBSD.org/doc/es/articles/fdp-es/</a></td></tr><tr><td><a href="https://listas.es.FreeBSD.org/mailman/listinfo/doc" title="https://listas.es.FreeBSD.org/mailman/listinfo/doc">Translators' Mailing List</a></td><td>
- URL: <a href="https://listas.es.FreeBSD.org/mailman/listinfo/doc" title="Translators' Mailing List">https://listas.es.FreeBSD.org/mailman/listinfo/doc</a></td></tr></table><p>
- Contact:
- Gábor
- Kövesdán
- &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
- </p>
- <p>There is one article translation pending review. Apart from this,
- neither translations nor maintenance work have been done. We need
- more volunteers, mostly translators but we are glad to have
- more reviewers, as well. One can join by simply subscribing to
- the translators' mailing list where all the work is done.</p>
- <h3>Open tasks:</h3><ol><li>Update Handbook translation.</li><li>Update webpage translation.</li><li>Add more article translations.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Flattened-Device-Tree-for-embedded-FreeBSD" href="#Flattened-Device-Tree-for-embedded-FreeBSD" id="Flattened-Device-Tree-for-embedded-FreeBSD">Flattened Device Tree for embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="http://wiki.FreeBSD.org/FlattenedDeviceTree">Project wiki pages</a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="Project wiki pages">http://wiki.FreeBSD.org/FlattenedDeviceTree</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/..." title="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...">Project P4 branch</a></td><td>
- URL: <a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/..." title="Project P4 branch">http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...</a></td></tr></table><p>
- Contact:
- Rafal
- Jaworowski
- &lt;<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>&gt;
- </p>
- <p>The purpose of this project is to provide FreeBSD with support for the
- Flattened Device Tree (FDT) technology, the mechanism for describing
- computer hardware resources, which cannot be probed or self enumerated, in
- a uniform and portable way. The primary consumers of this technology are
- embedded FreeBSD platforms (ARM, AVR32, MIPS, PowerPC), where a lot of
- designs are based on similar chips but have different assignment of pins,
- memory layout, addresses bindings, interrupts routing and other resources.</p>
-
- <p>Current state highlights:</p>
-
- <ul>
- <li>Environment, supported tools</li>
-
- <ul>
- <li>Integrated device tree compiler (dtc) and libfdt into FreeBSD
- userspace, kernel and loader build</li>
- </ul>
-
- <li>loader(8)</li>
-
- <ul>
- <li>Full support for device tree blob handling</li>
-
- <li>Load, traverse, modify (including add/remove) device tree
- nodes and properties</li>
-
- <li>Pass the device tree blob to the kernel</li>
-
- <li>Both ARM and PowerPC loader(8) supported</li>
- </ul>
-
- <li>Kernel side FDT support (common)</li>
-
- <ul>
- <li>Developed OF interface for FDT-backed platforms</li>
-
- <li>ofw_bus I/F (and /dev/openfirm) available with FDT</li>
-
- <li>Integrated FDT resources representation with newbus (fdtbus
- and simplebus drivers)</li>
- </ul>
-
- <li>PowerPC kernel (Freescale MPC85XX SOC)</li>
-
- <ul>
- <li>MPC8555CDS and MPC8572DS successfully converted to FDT
- conventions</li>
- </ul>
-
- <li>ARM kernel (Marvell Orion, Kirkwood and Discovery SOC)</li>
-
- <ul>
- <li>Work in progress on integrating FDT infrastructure with ARM
- platform code</li>
- </ul>
- </ul>
-
- <p>Work on this project has been sponsored by the FreeBSD Foundation.</p>
- <h3>Open tasks:</h3><ol><li>Complete missing pieces for PowerPC (PCI bridge driver conversion to
- FDT).</li><li>Complete ARM support.</li><li>Merge to SVN.</li></ol><hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><p>
- Contact:
- Marcel
- Moolenaar
- &lt;<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>&gt;
- </p>
- <p>Work continues on our ia64 port. Many recent commits to
- help improve stability have been made to 9.0-CURRENT and MFCed
- to 8-STABLE.</p>
-
- <p>Due to interest from a very motivated user, package builds
- have been restarted for ia64-8. This is primarily intended as
- a QA step to discover and fix bugs on ia64, rather than to
- create packages for upload.</p>
-
- <p>Based on the above, Mark Linimon documented how to add more
- architectures to the package cluster scheduler. (This work will
- also be of use in an upcoming effort to start powerpc package
- builds.)</p>
-
- <p>There are currently 3 ia64 machines online and building
- packages. The machines seem stable as long as multiple
- simultaneous package builds are not attempted, in which case
- they get machine checks. This is puzzling, since other heavy
- workloads seem stable on the same machines.</p>
- <h3>Open tasks:</h3><ol><li>Continue to try to understand why multiple simultaneous
- package builds bring the machines down.</li><li>Upgrade the firmware on the two machines at Yahoo! to
- see if that helps the problem.</li><li>Configure a fourth machine that has been made available
- to us.</li><li>Figure out the problems with the latest GCC port on
- ia64.</li><li>We can use some help with reviewing the ia64 platform pages
- and bringing them up-to-date.</li></ol><hr /><h2><a name="FreeBSD/mips" href="#FreeBSD/mips" id="FreeBSD/mips">FreeBSD/mips</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/mips/index.html" title="http://www.FreeBSD.org/projects/mips/index.html"></a></td><td>
- URL: <a href="http://www.FreeBSD.org/projects/mips/index.html" title="">http://www.FreeBSD.org/projects/mips/index.html</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/FreeBSD/mips" title="http://wiki.FreeBSD.org/FreeBSD/mips"></a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/FreeBSD/mips" title="">http://wiki.FreeBSD.org/FreeBSD/mips</a></td></tr></table><p>
- Contact:
- The FreeBSD/mips mailing list
- &lt;<a href="mailto:mips@FreeBSD.org">mips@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Warner
-
- Losh
- &lt;<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>&gt;
- </p>
- <p>The base/projects/mips branch has been merged into 9.0-CURRENT.
- The merge is complete and the sanity tests have passed. The code
- has booted on both a Ubiquiti RouterStation (big endian) as well as
- in gxemul (little endian).</p>
-
- <p>The branch lived for one year, minus a day, and accumulated much
- work:</p>
-
- <ul>
- <li>A new port to the Atheros AR71xx series of processors. This
- port supports the RouterStation and RouterStation PRO boards from
- Ubiquiti. Other boards should work with minimal tweaking. This
- port should be considered as nearing production quality, and has
- been used extensively by the developers. The primary author of
- this port is Oleksandr Tymoshenko (gonzo@FreeBSD.org).</li>
-
- <li>A new port to the SiByte BCM1250 SoC on the BCM91250
- evaluation board (aka SWARM). This port is reported to be stable,
- but this hardware is a little old and not widely available. The
- primary author of this port is Neel Natu (neel@FreeBSD.org). Only
- one core is presently supported.</li>
-
- <li>A port, donated by Cavium, to their Octeon and Octeon plus
- series of SoC (CN3xxx and CN5xxx). This code is preliminary,
- supporting only a single core right now. It has been lightly
- tested on the CN3860 evaluation board only in 32-bit mode. Warner
- Losh (imp@FreeBSD.org) has been driving the efforts to get this
- code into the tree.</li>
-
- <li>A port, donated by RMI, to their XLR series of SoCs. This
- port is single core only, as well. The code reaches multi-user but
- should be considered beta quality for the moment. Randal Stewart
- (rrs@FreeBSD.org) has been driving the efforts to integrate this
- into the tree.</li>
-
- <li>Preliminary support for building a mips64 kernel from this
- source base. More work is needed here, but at least two kernels
- successfully build in 64-bit mode (OCTEON1 and MALTA64).</li>
-
- <li>Very early support for N32 and N64 ABIs</li>
-
- <li>Support for booting compressed kernels has been added
- (gonzo@).</li>
-
- <li>Improved support for debugging</li>
-
- <li>Improved busdma and bus_space support</li>
-
- <li>Many bug fixes</li>
-
- <li>More types of MIPS cores are recognized</li>
-
- <li>Expanded cache handling for newer processors</li>
-
- <li>Beginning of a port to the alchemy au1XXX cpus is present,
- but experimental.</li>
-
- <li>Work on SMP is underway to support multicore processors like
- the SiByte, Octeon and XLR processors.</li>
- </ul>
-
- <p>The development branch had been updated incorrectly several times over the
- past year, and the damage was too much to repair. We have retired the
- branch and will do further mips development in 9.0-CURRENT for the time
- being. If you have a checked out tree, the suggested way to update
- the projects/mips tree you have is to do a "svn switch
- svn://svn.FreeBSD.org/base/head" in that tree.</p>
-
- <p>I would like to thank everybody that has contributed time, code
- or hardware to make FreeBSD/mips better.</p>
-
- <p>As development proceeds, I will keep posting updates. In
- addition, I hope to have some mini "how-to" wiki pages done for
- people that want to try it out.</p>
- <h3>Open tasks:</h3><ol><li>We are still investigating how feasible merging all this work
- into 8-STABLE will be, as it represents a huge leap forward in code
- stability and quality.</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p>
- Contact:
- Marius
-
- Strobl
- &lt;<a href="mailto:marius@FreeBSD.org">marius@FreeBSD.org</a>&gt;
- </p>
- <p>The main thing that has taken place since the last Status Report
- is that I have gotten to the bottom of the remaining PCI problems
- with Sun Fire V215/V245 and support for these has been completed
- and since r202023 now is part of 9.0-CURRENT. With some luck it will also
- be part of the upcoming 7.3-RELEASE.</p>
-
- <p>Some other news:</p>
-
- <ul>
- <li>Two bugs in the NFS server causing unaligned access and
- thus panics on sparc64 and all other architectures with strict
- alignment requirements (basically all Tier-2 ones) have been
- fixed. There likely will be a 8.0-RELEASE Erratum Notice released
- for these.</li>
-
- <li>FreeBSD has been adopted to the changed firmware of newer Sun
- Fire V480 (those equipped with version 7 Schizo bridges) and has been
- reported to now run fine on these. The necessary change will be
- part of 7.3-RELEASE. Unfortunately, using the on-board NICs in
- older models of Sun Fire V480 (at least those equipped with
- version 4 Schizo bridges) under FreeBSD still leads to the firmware
- issuing a FATAL RESET due to what appears to be a CPU bug, which
- needs to be worked around.</li>
-
- <li>Work on supporting Sun Fire V1280 has been started but still
- is in very early stages. Unfortunately, these are rather quirky
- machines. After solving two firmware specialties the loader now
- is able to boot the kernel but the latter currently still fails
- in early cycles as trying to take the trap table over from the
- firmware results in a solid hang.</li>
- </ul>
- <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium-web-browser" href="#Chromium-web-browser" id="Chromium-web-browser">Chromium web browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://chromium.jaggeri.com" title="http://chromium.jaggeri.com">test builds and port progress</a></td><td>
- URL: <a href="http://chromium.jaggeri.com" title="test builds and port progress">http://chromium.jaggeri.com</a></td></tr><tr><td><a href="http://www.links.org/?p=724" title="http://www.links.org/?p=724">first build information</a></td><td>
- URL: <a href="http://www.links.org/?p=724" title="first build information">http://www.links.org/?p=724</a></td></tr></table><p>
- Contact:
- Ben
-
- Laurie
- &lt;<a href="mailto:ben@links.org">ben@links.org</a>&gt;
- </p>
- <p>Chromium is a Webkit-based web browser that is largely BSD
- licensed. It has been ported from Linux to FreeBSD in October and we have been
- posting patches and test builds periodically since then. Chromium
- works well on FreeBSD &#8212; it is very fast and stable but there
- are a handful of rough edges that need to be polished up. Two
- remaining bugs should probably be fixed before releasing a
- chromium-devel port. We are looking for volunteers to test and
- maintain this port to make this BSD browser a viable option on
- FreeBSD desktop systems.</p>
- <h3>Open tasks:</h3><ol><li>Fix sporadic rendering freezes.</li><li>Fix JavaScript interpreter, v8, on i386 architecture.</li></ol><hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">The FreeBSD Ports Collection</a></td><td>
- URL: <a href="http://www.FreeBSD.org/ports/" title="The FreeBSD Ports Collection">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/">Contributing to the FreeBSD Ports Collection</a></td><td>
- URL: <a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="Contributing to the FreeBSD Ports Collection">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.FreeBSD.org/index.html" title="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring system</a></td><td>
- URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td>
- URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td>
- URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p>
- Contact:
- Mark
-
- Linimon
- &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;
- </p>
- <p>Most of the recent activity has been dealing with the 8.0-RELEASE
- process. As an experiment, we have tried to decouple the ports QA
- timeline as much as possible from the src QA timeline. Although
- this meant that the impact on people actively maintaining and using
- ports has been much less than in previous releases, it still has not
- solved the problem of the release going out with a stale set of
- packages. We are still trying to come up with a better solution for
- the problem.</p>
-
- <p>The ports count is over 21,000. The PR count jumped to over
- 1,000 but is now back to around 950.</p>
-
- <p>We are currently building packages for amd64-6, amd64-7,
- amd64-8, i386-6, i386-7, i386-8, i386-9, ia64-8, sparc64-7, and
- sparc64-8. This represents the addition of i386-9 and ia64-8 since
- the last report.</p>
-
- <p>There has been some discussion of when to drop regular package
- builds for 6.X but no decision has been made yet. The cluster and
- the port managers are struggling to keep up with so many branches being
- active all at the same time.</p>
-
- <p>Mark Linimon continues to make progress on the cluster nodes.
- Almost every node that does not have a hard disk failure is now
- online. In addition, he continues to make progress debugging
- problems that occasionally take nodes offline.</p>
-
- <p>The next task is to characterize the overall performance of the
- build cluster. The question has been asked of us, "what would it
- take to speed up package builds?" There is no one simple answer. It
- is not merely a matter of having a larger number of package
- building machines, so before asking for funding we first need to
- identify the current bottlenecks. While we are starting to
- understand the problems on the nodes, the problems on the dispatch
- machine itself are much harder. Complicating the matter is that
- there are several periodic processes (ZFS backup, ZFS expiration,
- and errorlog compression, among others) that can combine to slow
- that machine significantly. The simultaneous interaction of all these
- is proving difficult to quantify.</p>
-
- <p>Between Pav Lucistnik and Martin Wilke, many more experimental ports runs have
- been completed and committed.</p>
-
- <p>We have added 3 new committers since the last report, and 1
- older one has rejoined us.</p>
- <h3>Open tasks:</h3><ol><li>We are still trying to set up ports tinderboxes that can be
- made available to committers for pre-testing.</li><li>Most of the remaining ports PRs are "existing port/PR
- assigned to committer". Although the maintainer-timeout policy is
- helping to keep the backlog down, we are going to need to do more
- to get the ports in the shape they really need to be in.</li><li>Although we have added many maintainers, we still have more
- than 4,700 unmaintained ports. (See, for instance, the list on
- portsmon. The percentage remains steady at just over 22%.) We are
- always looking for dedicated volunteers to adopt at least a few
- unmaintained ports. As well, the packages on amd64 and especially
- sparc64 lag behind i386, and we need more testers for those.</li></ol><hr /><h2><a name="VirtualBox-on-FreeBSD" href="#VirtualBox-on-FreeBSD" id="VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/VirtualBox" title="http://wiki.FreeBSD.org/VirtualBox"></a></td><td>
- URL: <a href="http://wiki.FreeBSD.org/VirtualBox" title="">http://wiki.FreeBSD.org/VirtualBox</a></td></tr></table><p>
- Contact:
- Beat
- Gaetzi
- &lt;<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Bernhard
- Froehlich
- &lt;<a href="mailto:decke@bluelife.at">decke@bluelife.at</a>&gt;
- <br />
- Contact:
- Juergen
- Lock
- &lt;<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>&gt;
- <br />
- Contact:
- Martin
- Wilke
- &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;
- </p>
- <p>VirtualBox 3.1.2 has been committed to the ports tree.</p>
-
- <p>Several changes to the port have been performed with this
- update including:</p>
-
- <ul>
- <li>Port has been renamed to virtualbox-ose to reflect that we
- are now using the OSE version.</li>
-
- <li>A separate port for the kernel modules has been created
- &#8212; virtualbox-ose-kmod.</li>
-
- <li>A separate port for guest additions for FreeBSD guests has
- been created &#8212; virtualbox-ose-additions.</li>
-
- <li>Proper FreeBSD support for PulseAudio has been added.</li>
-
- <li>Procfs is not required anymore because vbox uses sysctl(3)
- now.</li>
-
- <li>Juergen Lock's FreeBSD host networking patches have been added. They
- are now also in the upstream vbox SVN (modulo vbox variable
- naming style adjustments).</li>
-
- <li>Allow direct tap networking again (for users that need the
- best network performance and/or need more complex network
- setups, like when they want to use routing instead of bridging
- to e.g. protect guests from messing with the lan's ARP tables;
- a tap + routing + proxy arp example is in the above
- freebsd-emulation@ posting.)</li>
-
- <li>Enable vbox's shared MAC feature when using bridged mode on
- a Wifi interface, together with the virtualbox-ose-kmod
- change this should fix bridged mode for Wifi users.</li>
- </ul>
-
- <p>We would like to say thanks to all the people that helped us
- by reporting bugs and submitting fixes. We also thank the
- VirtualBox developers for their help with the ongoing effort
- to port VirtualBox to FreeBSD</p>
- <hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="DAHDI-(Zaptel)-support-for-FreeBSD" href="#DAHDI-(Zaptel)-support-for-FreeBSD" id="DAHDI-(Zaptel)-support-for-FreeBSD">DAHDI (Zaptel) support for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html" title="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html">Official Announcement</a></td><td>
- URL: <a href="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html" title="Official Announcement">http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html</a></td></tr><tr><td><a href="http://svn.digium.com/svn/dahdi/freebsd/trunk/" title="http://svn.digium.com/svn/dahdi/freebsd/trunk/">SVN repository</a></td><td>
- URL: <a href="http://svn.digium.com/svn/dahdi/freebsd/trunk/" title="SVN repository">http://svn.digium.com/svn/dahdi/freebsd/trunk/</a></td></tr></table><p>
- Contact:
- Max
-
- Khon
- &lt;<a href="mailto:fjoe@FreeBSD.org">fjoe@FreeBSD.org</a>&gt;
- </p>
- <p>A DAHDI support module for FreeBSD has been created in the
- official Asterisk SVN repository.</p>
-
- <p>The following drivers are currently ported:</p>
-
- <ul>
- <li>main DAHDI driver</li>
-
- <li>all software echo cancellation drivers</li>
-
- <li>dahdi_dynamic</li>
-
- <li>dahdi_dynamic_loc</li>
- </ul>
-
- <p>The following HW drivers are currently ported and tested:</p>
-
- <ul>
- <li>wct4xxp, including HW echo cancellation support
- (Octasic)</li>
-
- <ul>
- <li>Digium TE205P/TE207P/TE210P/TE212P: PCI dual-port
- T1/E1/J1</li>
-
- <li>Digium TE405P/TE407P/TE410P/TE412P: PCI quad-port
- T1/E1/J1</li>
-
- <li>Digium TE220: PCI-Express dual-port T1/E1/J1</li>
-
- <li>Digium TE420: PCI-Express quad-port T1/E1/J1</li>
- </ul>
-
- <li>wcb4xxp</li>
-
- <ul>
- <li>Digium B410: PCI quad-port BRI</li>
-
- <li>Junghanns.NET HFC-2S/4S/8S duo/quad/octoBRI</li>
-
- <li>OpenVox B200P/B400P/B800P</li>
-
- <li>BeroNet BN2S0/BN4S0/BN8S0</li>
- </ul>
- </ul>
- <h3>Open tasks:</h3><ol><li>The port for dahdi_dynamic_eth and dahdi_dynamic_ethmf is
- underway.</li><li>More HW drivers need to be ported.</li><li>Please let me know if you can provide remote access with
- serial console to any box with ISDN/T1/E1 HW not currently
- supported by DAHDI for FreeBSD but supported by DAHDI for Linux. I
- am also interested in porting drivers for FXO/FXS cards. Please
- let me know if you can provide a remote access or donate a
- card.</li></ol><hr /><h2><a name="NVIDIA-amd64-driver" href="#NVIDIA-amd64-driver" id="NVIDIA-amd64-driver">NVIDIA amd64 driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nvnews.net/vbulletin/showthread.php?t=142120" title="http://www.nvnews.net/vbulletin/showthread.php?t=142120">Release Announcement</a></td><td>
- URL: <a href="http://www.nvnews.net/vbulletin/showthread.php?t=142120" title="Release Announcement">http://www.nvnews.net/vbulletin/showthread.php?t=142120</a></td></tr></table><p>
- Contact:
- John
- Baldwin
- &lt;<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>&gt;
- </p>
- <p>NVIDIA has released the first BETA version of its graphics
- drivers for FreeBSD/amd64. Note that this driver will work on FreeBSD
- versions 7.3-RELEASE or 8.0-RELEASE and later. It also works on very recent
- versions of 7.2-STABLE. More details are provided in the
- official release announcement.</p>
- <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="AsiaBSDCon-2010-&#8212;-The-BSD-Conference" href="#AsiaBSDCon-2010-&#8212;-The-BSD-Conference" id="AsiaBSDCon-2010-&#8212;-The-BSD-Conference">AsiaBSDCon 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2010.AsiaBSDCon.org/" title="http://2010.AsiaBSDCon.org/"></a></td><td>
- URL: <a href="http://2010.AsiaBSDCon.org/" title="">http://2010.AsiaBSDCon.org/</a></td></tr></table><p>
- Contact:
- AsiaBSDCon Information
- &lt;<a href="mailto:secretary@AsiaBSDCon.org">secretary@AsiaBSDCon.org</a>&gt;
- </p>
- <p>AsiaBSDCon is a conference for users and developers on BSD
- based systems. AsiaBSDCon is a technical conference and aims
- to collect the best technical papers and presentations
- available to ensure that the latest developments in our open
- source community are shared with the widest possible audience.
- The conference is for anyone developing, deploying and using
- systems based on FreeBSD, NetBSD, OpenBSD, DragonFlyBSD, Darwin
- and MacOS X.</p>
-
- <p>The next conference will be held at the Tokyo University of
- Science, Tokyo, Japan, on 11th to 14th March, 2010.</p>
-
- <p>For more detailed information, please check the conference
- web site.</p>
- <hr /><h2><a name="BSDCan-2010-&#8212;-The-BSD-Conference" href="#BSDCan-2010-&#8212;-The-BSD-Conference" id="BSDCan-2010-&#8212;-The-BSD-Conference">BSDCan 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.BSDCan.org/2010/" title="http://www.BSDCan.org/2010/"></a></td><td>
- URL: <a href="http://www.BSDCan.org/2010/" title="">http://www.BSDCan.org/2010/</a></td></tr></table><p>
- Contact:
- BSDCan Information
- &lt;<a href="mailto:info@BSDCan.org">info@BSDCan.org</a>&gt;
- </p>
- <p>BSDCan, a BSD conference held in Ottawa, Canada, has quickly
- established itself as the technical conference for people
- working on and with 4.4BSD based operating systems and related
- projects. The organizers have found a fantastic formula that
- appeals to a wide range of people from extreme novices to
- advanced developers.</p>
-
- <p>BSDCan 2010 will be held on 13-14 May 2010 at the University of
- Ottawa, and will be preceded by two days of Tutorials on 11-12
- May 2010.</p>
-
- <p>There will be related events (of a social nature, for the most
- part) on the day before and after the conference.</p>
-
- <p>Please check the conference web site for more information.</p>
- <hr /><h2><a name="meetBSD-2010-&#8212;-The-BSD-Conference" href="#meetBSD-2010-&#8212;-The-BSD-Conference" id="meetBSD-2010-&#8212;-The-BSD-Conference">meetBSD 2010 &#8212; The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.meetBSD.org" title="http://www.meetBSD.org"></a></td><td>
- URL: <a href="http://www.meetBSD.org" title="">http://www.meetBSD.org</a></td></tr></table><p>
- Contact:
- meetBSD
- Information
- &lt;<a href="mailto:info@meetBSD.org">info@meetBSD.org</a>&gt;
- </p>
- <p>The meetBSD conference is an annual event gathering users and
- developers of the BSD operating system family, mostly FreeBSD,
- NetBSD and OpenBSD. Afer the special California edition,
- meetBSD Wintercamp in Livigno, this year we are back to
- Krakow, Poland.</p>
-
- <p>In 2010, meetBSD will be held on 2-3 July at the Jagiellonian
- University.</p>
-
- <p>See the conference main web site for more details.</p>
- <hr /><h2><a name="The-FreeBSD-Forums" href="#The-FreeBSD-Forums" id="The-FreeBSD-Forums">The FreeBSD Forums</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.FreeBSD.org/" title="http://forums.FreeBSD.org/"></a></td><td>
- URL: <a href="http://forums.FreeBSD.org/" title="">http://forums.FreeBSD.org/</a></td></tr></table><p>
- Contact:
- FreeBSD Forums
-
- Admins
- &lt;<a href="mailto:forum-admins@FreeBSD.org">forum-admins@FreeBSD.org</a>&gt;
- <br />
- Contact:
- FreeBSD Forums
-
- Moderators
- &lt;<a href="mailto:forum-moderators@FreeBSD.org">forum-moderators@FreeBSD.org</a>&gt;
- </p>
- <p>Since the last report we have seen a growth of 2,000 users on our
- forums resulting in approximately 10,000 registered users at this time. The
- posts count is about to reach 60,000 soon, which are contained in
- almost 9,000 threads.</p>
-
- <p>The sign-up rate still hovers between 50-100 each week. The
- total number of visitors (including 'guests') is currently hard to
- gauge, but is likely to be a substantial multiple of the registered
- userbase.</p>
-
- <p>New topics and posts are actively 'pushed out' to search
- engines. This in turn makes the forums show up in search results
- more and more often, making it a valuable and very accessible
- source of information for the FreeBSD community.</p>
-
- <p>One of the contributing factors to the forums' success is their
- 'BSD-style' approach when it comes to administration and
- moderation. The forums have a strong and unified identity and are
- very actively moderated, spam-free, and with a core group of very
- active and helpful members, dispensing many combined decades' worth
- of knowledge to starting, intermediate and professional users of
- FreeBSD.</p>
- <hr /><br /><h1><a name="Userland-utilities" href="#Userland-utilities" id="Userland-utilities">Userland utilities</a></h1><br /><h2><a name="BSD-licensed-text-processing-tools" href="#BSD-licensed-text-processing-tools" id="BSD-licensed-text-processing-tools">BSD-licensed text processing tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc">Perforce repository</a></td><td>
- URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="Perforce repository">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc</a></td></tr></table><p>
- Contact:
- Gábor
- Kövesdán
- &lt;<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>&gt;
- </p>
- <p>As 8.0-RELEASE is out, BSD bc/dc can be now committed to 9.0-CURRENT. We are
- only waiting for an experimental package building to make sure there are no
- regressions after this change. BSD grep is complete but it cannot be integrated yet because of
- some regex library issues. We need first a fast and modern regex
- library so that we can change to BSD grep. BSD sort has few
- incomplete features and needs some performance review.</p>
- <h3>Open tasks:</h3><ol><li>Commit BSD bc/dc.</li><li>Implement remaining features for sort and optimize
- performance.</li></ol><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
- <br class="clearboth" />
- </div>
- <div id="footer">
- <span><a href="../../search/index-site.html">Site Map</a> |
- <a href="../../copyright/">Legal Notices</a> | © 1995&#8211;2021 The FreeBSD Project.
- All rights reserved.</span>
- <br />
- </div>
- </div>
- </div>
- </body>
-</html>